[RV100] suspend failure with kernel driver "radeon" (ATI Technologies Inc Radeon Mobility M6 LY)

[PhilippeDePass]

The system fails to suspend both to ram and to disk. I believe it is a problem with the video driver "radeon", as the screen never turns off.

I followed the instructions from
https://wiki.ubuntu.com/DebuggingKernelSuspend

After performing
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"

The output from dmesg points to
[ 0.333831] hash matches /build/buildd/linux-2.6.32/drivers/base/power/main.c:433
[ 0.333853] block loop5: hash matches
[ 0.333921] pci 0000:01:00.0: hash matches

sudo lspci -vvnn | grep -A 17 01:00.0
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M6 LY [1002:4c59]
 Subsystem: IBM Device [1014:052f]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 66 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at 3000 [size=256]
 Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
  Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
  Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: radeon
 Kernel modules: radeonfb, radeon

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: phil 4497 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1QHT23WW-1.08'
   Mixer name : 'ThinkPad EC 1QHT23WW-1.08'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 4 [29%] [on]
Date: Sat Apr 17 17:04:56 2010
HibernationDevice: RESUME=UUID=3337d611-1642-45e5-b992-c61577a4235f
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 2672PBU
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=7240df37-503f-4eeb-832f-a46f9d5a5b4b ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 09/22/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1QET97WW (3.02 )
dmi.board.name: 2672PBU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1QET97WW(3.02):bd09/22/2005:svnIBM:pn2672PBU:pvrThinkPadX31:rvnIBM:rn2672PBU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2672PBU
dmi.product.version: ThinkPad X31
dmi.sys.vendor: IBM

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03)
 Subsystem: IBM Device [1014:0529]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M6 LY [1002:4c59]
 Subsystem: IBM Device [1014:052f]

[PhilippeDePass (depassp)]

After disabling KMS, the problem is improved somewhat. The system now successfully suspends. However, after resume, graphics are messed up. Virtual Terminal is almost unreadable, Xorg windows seem to have "static".

[PhilippeDePass (depassp)]

Using Ubuntu 10.04 with kernel 2.6.32

In KMS mode the system fails to suspend both to ram and to disk.

The problem persists in single-user mode.

I followed the instructions from
https://wiki.ubuntu.com/DebuggingKernelSuspend

After performing
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"

The output from dmesg points to
[ 0.333831] hash matches /build/buildd/linux-2.6.32/drivers/base/power/main.c:433
[ 0.333853] block loop5: hash matches
[ 0.333921] pci 0000:01:00.0: hash matches

sudo lspci -vvnn | grep -A 17 01:00.0
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M6 LY [1002:4c59]
 Subsystem: IBM Device [1014:052f]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 66 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at 3000 [size=256]
 Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
  Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
  Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: radeon
 Kernel modules: radeonfb, radeon

[agd5f (agd5f)]

Does s/r work if you disable kms? (boot with radeon.modeset=0) Does s/r work if you enable KMS but disable AGP gart? (boot with radeon.agpmode=-1)

[Bryce Harrington (bryce)]

That corruption sort of sounds like this might be caused by an incorrect AGPMode setting, which is relevant when DRI is enabled. You should test if changing this makes the issue go away. In your /etc/X11/xorg.conf set AGPMode to various values like this:

 Section "Device"
    ...
    Option "AGPMode" "2"
 EndSection

Possible values include 1, 2, 4, 8. You can see what it's currently set to by looking in /var/log/Xorg.0.log. It's worthwhile to test all four values even once you find one that works. If this takes care of it for you, we may be able to establish a quirk to set it for your hardware combo, if you can provide the following data:

   * AGPMode value(s) that work
   * Make/Model of laptop or motherboard
   * Output of lspci -vvnn
   * Is the system all factory hardware, or have any parts been replaced?
   * Is there an AGP Mode in the system BIOS?
     - If so, is it set to the factory default?

For more details on this, please see the "ATI AGP Mode Quirk" section at https://wiki.ubuntu.com/X/Quirks

For the case where KMS is being used, you enable agpmodes via the radeon.agpmode=X parameter (where X can be -1 for bios-detect, or 1,2,4,8 to specify an agp mode.)

[PhilippeDePass (depassp)]

Yes, both s/r work if I disable KMS, but I lose the joy of KMS :(

No, s/r do not work if I disable AGP gart.

I have also tested with the mainline Ubuntu kernel
linux-image-2.6.34-999-generic_2.6.34-999.201004211003_i386.deb
from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-04-21-lucid/

I have also tested using the xorg-edgers PPA, specifically, the package
xserver-xorg-video-radeon
Version: 1:6.13.99+git20100416.a69e749d-0ubuntu0sarvatt

Please let me know if there's anything else I can do to help.

[PhilippeDePass (depassp)]

Well, I cannot reproduce the video corruption problem I was having before.

It seems disabling KMS is the workaround (for now), possibly requiring a quirk. Once I can reproduce the corruption I will test and see which quirk solves in.

I suppose this is a bug with KMS, then. I have also created a bug upstream at
https://bugs.freedesktop.org/show_bug.cgi?id=27785

By the way, Bryce, setting radeon.agpmode=-1 is not bios-detect. It disables the AGP gart.

$modinfo radeon | grep agpmode
parm: agpmode:AGP Mode (-1 == PCI) (int)

[Bryce Harrington (bryce)]

Thanks for forwarding the bug upstream. Since it looks like there's already a linux task for this bug, and since it sounds pretty certain to be a drm bug, I'll close out the ddx driver task.

[Rafał Miłecki (zajec5)]

Does anyone know if pm-suspend performs any tricks on suspending?

What about "pm-suspend --quirk-none"?

[PhilippeDePass (depassp)]

(In reply to comment #3)
> Does anyone know if pm-suspend performs any tricks on suspending?
>
> What about "pm-suspend --quirk-none"?

Yes. By default it will store its quirks in /var/cache/pm-utils/last_known_working.quirkdb (source: man pm-utils)

Also, from /usr/share/doc/pm-utils/README.debugging:

* If a parameter (or lack thereof) passed to pm-suspend and friends is causing
  problems, or you need to debug the suspend/resume process to work out what
  quirks are causing problems, you can use the ADD_PARAMETERS and
  DROP_PARAMETERS environment variables. To do this, create a file in
  /etc/pm/config.d, and add the following lines to it:
  ADD_PARAMETERS="--parameter-to-add --another-parameter"
  DROP_PARAMETERS="--parameter-to-drop --another-parameter-to-drop"

  If you want to drop all parameters (for testing purposes, or to work around
  bugs in HAL), you can use DROP_PARAMETERS="all"

[Jeremy Foshee (jeremyfoshee)]

Hi PhilippeDePass,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[PhilippeDePass (depassp)]

The problem persists with the latest mainline kernel, namely,

linux-image-2.6.34-999-generic_2.6.34-999.201004281008_i386.deb

[penalvch (penalvch)]

PhilippeDePass, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[PhilippeDePass (depassp)]

I no longer own the hardware (laptop) so am unable to test anymore.

[penalvch (penalvch)]

PhilippeDePass, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/565607/comments/14 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[penalvch (penalvch)]

<email address hidden>, Ubuntu 10.04 Desktop reached EOL on May 9, 2013. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.