desktop-packages team mailing list archive

Thread
Date

[Bug 383176] Re: radeon: Unsuspend does not turn screen on (vbetool called, but never returns)

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: "Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>
Date: Thu, 11 Dec 2014 08:26:56 -0000
Reply-to: Bug 383176 <383176@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** This bug is no longer a duplicate of bug 130979
   vbetool 100% cpu usage on resume

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vbetool in Ubuntu.
https://bugs.launchpad.net/bugs/383176

Title:
  radeon: Unsuspend does not turn screen on (vbetool called, but never
  returns)

Status in vbetool package in Ubuntu:
  New

Bug description:
  Binary package hint: pm-utils

  I am using Jaunty with ~tormodvolden's -radeon driver.
  This does not occur with fglrx.
  Switching to a tty with Ctrl-Alt-F1 and switching back to the X display turns the screen on. ps output shows the following, which suggests that "vbetool post" is incorrectly called. Is the "quirk" not needed on this card?

  31590 ?        S      0:00 /bin/sh /usr/lib/pm-utils/sleep.d/99video resume suspend
  31592 ?        R      6:30 vbetool post

  xserver-xorg-video-ati:
    Installed: 1:6.12.99+git20090531.7599dc40-0ubuntu0tormod

  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4]
  	Subsystem: Dell Device [1028:029f]
  	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
  	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- INTx-
  	Latency: 0, Cache Line Size: 64 bytes
  	Interrupt: pin A routed to IRQ 16
  	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
  	Region 1: I/O ports at 2000 [size=256]
  	Region 2: Memory at cfef0000 (32-bit, non-prefetchable) [size=64K]
  	[virtual] Expansion ROM at cfe00000 [disabled] [size=128K]
  	Capabilities: <access denied>

  
  Relevant lines from dmesg after resume:

  [46786.933471] [drm] Resetting GPU
  [46795.967413] Modules linked in: usblp aes_x86_64 aes_generic ecb binfmt_misc ppdev radeon drm bridge stp bnep vboxnetflt vboxdrv kqemu input_polldev dm_crypt sbp2 lp parport joydev btusb psmouse dcdbas iTCO_wdt iTCO_vendor_support serio_raw pcspkr ricoh_mmc sdhci_pci sdhci ieee80211_crypt_tkip wl(P) ieee80211_crypt uvcvideo compat_ioctl32 videodev v4l1_compat snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event video output snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc intel_agp usbhid ohci1394 ieee1394 tg3 fbcon tileblit font bitblit softcursor
  [46816.902145] [drm] Loading RV620 CP Microcode
  [46816.902478] [drm] Loading RV620 PFP Microcode
  [46816.917417] [drm] Resetting GPU

  Perhaps the delay between 46786 and 46816 (~30s) is due to my waiting
  for the screen to turn on, and the "Loading RV620 [CP|PFP] Microcode"
  occurs when I switch back to the X server?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vbetool/+bug/383176/+subscriptions