[savage] drm ERROR and hang after resume

Bug #43007 reported by Tormod Volden on 2006-05-04
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
linux-source-2.6.17 (Ubuntu)

Bug Description

I have troubles with sleep/hibernation. Sometimes it hangs (completely, not even sysrq works) just as it resumes, sometimes when I leave the laptop for a while (can it be the screensaver?).

I enabled debug=1 for the drm module and ssh'ed from another computer. The laptop doesn't have a serial port, so no serial console. I don't know how to use a net console.

Just before the hang, this message appears:
[drm:savage_bci_wait_event_shadow] *ERROR* failed!

This was captured with tail -f syslog through ssh as it hung.

lspci output is attached and the dmidecode output is here: http://librarian.launchpad.net/2341493/dmidecode.out

This is Dapper Beta 2 by the way.

Tormod Volden (tormodvolden) wrote :

Possibly related upstream bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=3835 (supposedly fixed in drm 1.0.1)
https://bugs.freedesktop.org/show_bug.cgi?id=2941 (but I don't have a supersavage)

Tormod Volden (tormodvolden) wrote :

Thanks a lot for the drm 1.0.1 update! I haven't yet seen any DRM errors since. But I am so bitten by bug #35410 and bug #36944 that I can not really say for sure.

Tormod Volden (tormodvolden) wrote :

Unfortunately I get the "[drm:savage_bci_wait_event_shadow] *ERROR* failed!" when I try to play the "trigger" 3D game.

Tormod Volden (tormodvolden) wrote :

I still get this with edgy beta:
kernel 2.6.17-10.28
drm 1.0.1 20051102
savage 2.4.1 20050313
xserver-xorg-video-savage 1:2.1.1-0ubuntu3

Oct 10 02:42:14 viki kernel: [17192405.404000] [drm:savage_bci_wait_event_shadow] *ERROR* failed!
Oct 10 02:42:14 viki kernel: [17192405.404000] [drm] status=0x00003d7e, e=0x3d88

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.