[fglrx] soft lockup, CPU0 stuck for 11s!

Bug #212897 reported by Zenigata
18
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Won't Fix
Undecided
Unassigned
xorg (Ubuntu)
Invalid
Undecided
Unassigned
Hardy
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg

Since a few days, when I leave my laptop for a big while, it has a black screen and seems unresponsive to anything but the sys requests alt+printscr+e/s/b, but I have to say that the screen remains all black till the alt+printscr+b.

I tried to log on it using ssh acces, but no response even thought it responded to ping.

I did not find revelent info in dmesg, but syslog seems to report a sof lockup involving xorg...

In the logs I am joining there, the bug seems to have happened at 16h40.

Normally, my laptop is not configured to suspend or such things like this, and I also had a music player running that had stopped.

Let me know if there is need for any other details.

Regards.

--
Z.

[lspci]
00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950] (rev 10)
     Subsystem: Fujitsu Siemens Computers Unknown device [1734:10b8]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS485 [Radeon Xpress 1100 IGP] [1002:5975] (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Siemens Computers Unknown device [1734:10b8]

Revision history for this message
Zenigata (drebon) wrote :
Revision history for this message
Zenigata (drebon) wrote :
Revision history for this message
Zenigata (drebon) wrote :
Revision history for this message
Zenigata (drebon) wrote :
Revision history for this message
Zenigata (drebon) wrote :
Zenigata (drebon)
description: updated
Revision history for this message
alphabeta (cvitone) wrote :

This happens on my IBM T60 laptop whenever I blank the screen (e.g. close the latop lid) and, sometimes, when I suspend to RAM. I'm running Ubuntu v8.04 with the fglrx v8.4 binary driver. I can provide any other details needed.

--alphabeta

Revision history for this message
Craig Harding (craigwharding) wrote :

I also get the same behavior if I leave my laptop idle. I come back to it and it's frozen and I need to hard reset.

I've attached my syslog. It seems to repeat the lines in my syslog over and over (approximately 100 times per second) until it freezes. dmesg does not give any relevant information.

Switching back to the 2.6.22-14-generic kernel does not give me any issues.

Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach your /var/log/Xorg.0.log.
It would also be useful to have a full backtrace on this issue - please see http://wiki.ubuntu.com/X/Backtracing.

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

Probably don't need the xorg component.

Changed in xorg:
status: New → Invalid
Revision history for this message
Andrew E (aeleneski) wrote :

I am also experiencing this when trying to do a standby. I am running Kubuntu 8.04 and ATI 8.5 drivers.

Revision history for this message
Harry H (bernhard-mueller11) wrote :

I have exactly the same problem on my Lenovo T60 / Ubuntu 8.04, linux kernel 2.6.24-16-generic and fglrx 2.1.7412. The system freezes about twice a day when left idle for some time.
Lots of soft lockup errors are written to the syslog ("BUG: soft lockup - CPU#0 stuck for 11s! [Xorg:5856]").

Revision history for this message
mehturt (mehturt) wrote :

I started to get the same problems on my Toshiba laptop with Ati Radeon X1400, soft lockups, e.g.:
Jun 21 08:21:50 pyty2 kernel: [ 1942.999751] BUG: soft lockup - CPU#0 stuck for 11s! [Xorg:5517]
I can provide more info if necessary..

Revision history for this message
mehturt (mehturt) wrote :

Perhaps the difference from other reporters is that it does not need to be idle.. it also happens when I work on the laptop..

Revision history for this message
mehturt (mehturt) wrote :
Revision history for this message
Andrew E (aeleneski) wrote :

Well I have updated to the latest 8.6 drivers. The problem appears to go away. Does anyone else see this after updating?

Revision history for this message
Craig Harding (craigwharding) wrote :

This has not happened to me since an upgrade to the newer kernel(s) in 8.04

Revision history for this message
Bryce Harrington (bryce) wrote :

Zenigata, please indicate if you're still seeing this problem, and if so attach your /var/log/Xorg.0.log and a backtrace.

Revision history for this message
Jordi Ferran (jordi-ferran) wrote :

I confirm this issue and I attach text/plain with a similar stack trace.

I do not play with hibernate/suspend/standby options. I have a workstation Opteron 1222 running 24 hours. It usually happens when running Multimedia player (Kaffeine, VLC, and mplayer), often with H264.

Nonetheless I saw a similar Bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240071

and last message says kernel 2.6.27 solves it!
It is related to a networking issue -not a fglrx-
(I can confirm I always had a networking client with heavy input/output when crash occurs).

I consider this issue critical because it locks the computer completely, and renders the kernel useless (all threads and processes hangs).

> More info: "uname -a"
Linux ubuntu 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Revision history for this message
Zenigata (drebon) wrote :

Well I did not encounter that bug in intrepid, I don't know if it's fglrx or the kernel, but intrepid seems much more stable than hardy on my cpu, no more black screens etc..

Bryce Harrington (bryce)
description: updated
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Marking fixed then. Glad it worked out for you.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Fix Released
Revision history for this message
moli (f-launchpad-moli-hu) wrote :

hello, is this fixed in the hardy LTS (long term support)?
my hardy crashes at least once every week.
attached syslog, if you need more information, tell me.

Revision history for this message
Michael Mess (michael-mess) wrote :

I am suffering from this problem from time to time since some weeks, too.

My notebook is a Lenovo R60.

This is the syslog from today's crash.

Revision history for this message
Michael Mess (michael-mess) wrote :

I have hardy and installed updates today. The crash occurred after applying these updates.

uname -a says:

Linux musca 2.6.24-28-generic #1 SMP Fri Jun 18 12:02:15 UTC 2010 i686 GNU/Linux

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in linux-restricted-modules-2.6.24 (Ubuntu Hardy):
status: New → Won't Fix
Changed in xorg (Ubuntu Hardy):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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