System fails to hibernate with: 01:00.1 Display controller: ATI Technologies Inc RV370 secondary [Sapphire X550 Silent] Was working fine with an nVidia card. /var/log/pm-suspend.log ends with: Tue Oct 23 09:41:42 MDT 2012: performing hibernate Nothing of note in /var/log/messages. Screen goes blank even with no suspend console, but system does not hibernate. kernel 3.6.3-1.fc17.i686.PAE xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.i686 mesa-dri-drivers-8.0.4-1.fc17.i686 [ 5.972923] [drm] Initialized drm 1.1.0 20060810 [ 6.005177] [drm] radeon defaulting to kernel modesetting. [ 6.005182] [drm] radeon kernel modesetting enabled. [ 6.005275] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [ 6.009395] [drm] initializing kernel modesetting (RV380 0x1002:0x5B63 0x17AF:0x3000). [ 6.009431] [drm] register mmio base: 0xDFDE0000 [ 6.009435] [drm] register mmio size: 65536 [ 6.009576] [drm] Generation 2 PCI interface, using max accessible memory [ 6.009633] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 6.009637] [drm] Driver supports precise vblank timestamp query. [ 6.009763] [drm] radeon: irq initialized. [ 6.012413] [drm] Detected VRAM RAM=256M, BAR=256M [ 6.012421] [drm] RAM width 128bits DDR [ 6.014950] [drm] radeon: 256M of VRAM memory ready [ 6.014955] [drm] radeon: 512M of GTT memory ready. [ 6.014987] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 6.016566] [drm] radeon: 1 quad pipes, 1 Z pipes initialized. [ 6.019858] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000). [ 6.031353] [drm] Loading R300 Microcode [ 6.035532] [drm] radeon: ring at 0x00000000A0001000 [ 6.035557] [drm] ring test succeeded in 1 usecs [ 6.035921] [drm] ib test succeeded in 0 usecs [ 6.036254] [drm] Radeon Display Connectors [ 6.036258] [drm] Connector 0: [ 6.036260] [drm] DVI-I-1 [ 6.036262] [drm] HPD2 [ 6.036265] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 6.036266] [drm] Encoders: [ 6.036268] [drm] CRT1: INTERNAL_DAC1 [ 6.036270] [drm] DFP2: INTERNAL_DVO1 [ 6.036272] [drm] Connector 1: [ 6.036274] [drm] DVI-I-2 [ 6.036276] [drm] HPD1 [ 6.036278] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 6.036280] [drm] Encoders: [ 6.036281] [drm] CRT2: INTERNAL_DAC2 [ 6.036283] [drm] DFP1: INTERNAL_TMDS1 [ 6.036285] [drm] Connector 2: [ 6.036287] [drm] SVIDEO-1 [ 6.036288] [drm] Encoders: [ 6.036290] [drm] TV1: INTERNAL_DAC2 [ 6.115216] [drm] fb mappable at 0xC00C0000 [ 6.115220] [drm] vram apper at 0xC0000000 [ 6.115222] [drm] size 7680000 [ 6.115224] [drm] fb depth is 24 [ 6.115225] [drm] pitch is 6400 [ 6.115334] fbcon: radeondrmfb (fb0) is primary device [ 6.165930] [drm] crtc 1 is connected to a TV [ 6.276745] fb0: radeondrmfb frame buffer device [ 6.276748] drm: registered panic notifier [ 6.276755] [drm] Initialized radeon 2.24.0 20080528 for 0000:01:00.0 on minor 0 [ 51.816328] [drm] crtc 1 is connected to a TV
Does the system hibernate ok if you blacklist the radeon module and use vesa?
Yes, it hibernates fine with vesa.
Does it hibernate if you disable acceleration? Option "NoAccel" "True" in the device section of your xorg.conf? Also, does suspend work or does it behave the same as hibernate?
NoAccel make no difference. Suspend works fine.
Suspend and hibernate are treated the same in the driver. Are you sure there isn't something else happening with hibernate?
I'm not sure nothing else is going on, but I started having the problem when I switched to this graphics card. And unfortunately I don't seem to get any messages to indicate where it might be failing.
FWIW I've got the same card and hibernation has been working reliably for at least two years and it's still working with current git.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/308.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.