Bug 22134 - x11-drivers/xf86-video-ati causes kernel panic on suspend-to-ram
Summary: x11-drivers/xf86-video-ati causes kernel panic on suspend-to-ram
Status: RESOLVED DUPLICATE of bug 22140
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.2 (2007.02)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-07 03:35 UTC by Ivan Baidakov
Modified: 2009-06-08 10:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Ivan Baidakov 2009-06-07 03:35:02 UTC
When I do hibernate-ram and than resume, my kernel hangs. Sorry, my there are no messages left in /var/log/messages. I tried in-kernel drm and linux-drm-20090320-kernelsource.tar.bz2.

My video card is : ati radeon xpress 200M.
X.Org X Server 1.5.3
Comment 1 Alex Deucher 2009-06-08 07:15:58 UTC
Can you take a picture of the kernel panic or console output?
Comment 2 Alex Deucher 2009-06-08 07:19:51 UTC
This may be a dup of bug 22140.  Can you confirm?
Comment 3 Ivan Baidakov 2009-06-08 10:10:43 UTC
It probably much more bug 19581, but I'm not sure. Mores exact problem description:
My PC does resume after hibernate-ram, even X desktop is displayed correctly, but all newly launched programs do "coredumps" and some time after even launched-before-hibernate programs do coredumps. I'm not sure, but kernel log (alt+f12) displays always new stack traces. 

Here are some logs (with with unloaded drm/radeon modules it happens not). For vanilla kernel:
Jun  1 01:31:01 logos ata1.00: configured for UDMA/100
Jun  1 01:31:01 logos sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors: (40.0 GB/37.2 GiB)
Jun  1 01:31:01 logos sd 0:0:0:0: [sda] Write Protect is off
Jun  1 01:31:01 logos sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jun  1 01:31:01 logos sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun  1 01:31:01 logos Restarting tasks ... done.
Jun  1 01:31:01 logos logger: ACPI group processor / action CPU is not defined
Jun  1 01:31:01 logos udevd[7432]: segfault at 80db948 ip 080513df sp bfcd9850 error 4 in udevd[8048000+f000]
Jun  1 01:31:01 logos udevd[7435]: segfault at 80db948 ip 080513df sp bfcd9850 error 4 in udevd[8048000+f000]
Jun  1 01:31:01 logos udevd[7441]: segfault at 80db948 ip 080513df sp bfcd9850 error 4 in udevd[8048000+f000]
Jun  1 01:31:01 logos udevd[7442]: segfault at 80db948 ip 080513df sp bfcd9850 error 4 in udevd[8048000+f000]

For tux-on-ice pactched kernel:
Jun  1 00:45:16 logos Restarting all filesystems ...
Jun  1 00:45:16 logos acpid: client 4621[0:0] has disconnected
Jun  1 00:45:16 logos Restarting tasks ... done.
Jun  1 00:45:16 logos default.sh[6024]: segfault at c08510c4 ip 080846d1 sp bfb64570 error 7 in bash
[8048000+85000]
Jun  1 00:45:16 logos udevd[6038]: segfault at 80db948 ip 080513df sp bff4cb10 error 4 in udevd[8048
000+f000]
Jun  1 00:45:16 logos runscript.sh[6034]: segfault at c08510c4 ip 080846d1 sp bfcab010 error 7 in ba
sh[8048000+85000]
Jun  1 00:45:16 logos udevd[6039]: segfault at 80db948 ip 080513df sp bff4cb10 error 4 in udevd[8048
000+f000]
Jun  1 00:45:16 logos runscript.sh[6042]: segfault at c08510c4 ip 080846d1 sp bfd400a0 error 7 in ba
sh[8048000+85000]
Jun  1 00:45:16 logos udevd[6045]: segfault at 80db948 ip 080513df sp bff4cb10 error 4 in udevd[8048
000+f000]
Jun  1 00:45:16 logos udevd[6046]: segfault at 80db948 ip 080513df sp bff4cb10 error 4 in udevd[8048
000+f000]

How can I grab console output? Could you point me some docs, how can I do than (I'm not kernel hacker)? If it is ok for, you I can do a photo of my screen... 

BTW, when linux hangs with backtraces it says something about "vblank"...?
Comment 4 Ivan Baidakov 2009-06-08 10:12:36 UTC
Btw, some people report that error disappeared on latest drm sources.... 
http://forums.gentoo.org/viewtopic.php?p=5778632#5778632
Comment 5 Alex Deucher 2009-06-08 10:15:38 UTC

*** This bug has been marked as a duplicate of bug 22140 ***


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.