X server quits "BUG: scheduling while atomic:"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Xserver falls and if fglrx driver is used, it writes "BUG: scheduling while atomic:" and some 4 digit number and then a small hexadecimal 0x0000002 number. If not using 3d accelerated driver (fglrx), Xserver respawns to gdm login screen.
Bug is repeatable on 2.6.27-11 distribution kernel as well as on 2.6.24.4 and 2.6.27.10 vanilla kernels.
When I launch cadsoft's eagle and click on menu, it happens all the time.
I suppose it is in Xserver, not in kernel or fglrx driver itself.
It started to behave this way after upgrade to 8.10 from 8.04 LTS
Eagle is version 5.3.0
I could downgrade some package and try to find out if it persists.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.24.0-0ubuntu2
ProcEnviron:
PATH=/
LANG=cs_CZ.UTF-8
SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux 2.6.27-11-generic i686
Now it happened again, randomly. It keeps writing (in text mode) microseconds] BUG: scheduling while atomic: Xorg/5278/ 0x000000002
[seconds.
where 5278 is PID of Xorg process. Last view in process manages has shown do_select next to Xorg process, then kaboom - it fell. But Amarok played a song till its end.
When I ssh to this machine from another, I see this:
top - 06:41:43 up 5:41, 2 users, load average: 3.86, 2.82, 1.52
Tasks: 120 total, 5 running, 113 sleeping, 0 stopped, 2 zombie
Cpu(s): 20.0%us, 76.3%sy, 3.7%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 904032k total, 895776k used, 8256k free, 24936k buffers
Swap: 2245280k total, 661376k used, 1583904k free, 294284k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5278 root 20 0 0 0 0 R 34.3 0.0 4:09.18 Xorg
4606 root 20 0 1828 432 412 R 30.0 0.0 0:48.23 dd
4608 klog 20 0 3660 472 420 S 23.7 0.1 0:37.50 klogd
4554 syslog 20 0 1888 660 540 S 8.0 0.1 0:12.43 syslogd
11902 root 30 10 120m 115m 4172 R 3.3 13.0 1:28.33 update-apt-xapi
5701 lada 20 0 28040 3560 2840 S 0.3 0.4 11:28.86 pulseaudio
1 root 20 0 2948 548 492 S 0.0 0.1 0:04.68 init
2 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 15 -5 0 0 0 S 0.0 0.0 0:01.46 ksoftirqd/0
4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
5 root 15 -5 0 0 0 S 0.0 0.0 0:00.06 events/0
6 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 khelper
45 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kintegrityd/0
47 root 15 -5 0 0 0 S 0.0 0.0 0:00.80 kblockd/0
49 root 15 -5 0 0 0 S 0.0 0.0 0:00.01 kacpid
50 root 15 -5 0 0 0 S 0.0 0.0 0:00.01 kacpi_notify
130 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 cqueue
Load seemed high before it fell, so maybe it was on a brink of collapse.