I hate hardware (Dell 2950 edition)
The Dell 2950 is a decent 2U server that has recently started being popular around here; like most recent servers, it has dispensed with PS/2 connectors and only has USB for the keyboard and mouse. It has four USB connectors, two on the front and two on the back.
If you plug your keyboard into the back USB connectors, the Ubuntu
6.06.1 x86_64 server kernel hangs with '
BUG: soft lockup detected
on CPU#0!'. (Sometimes it recovers from this hang, sometimes not.)
If you plug your keyboard into the front USB connectors, everything works great.
I love hardware. I really do.
(Don't ask how long it took to find out just why our 2950s were locking up when we tried to install Ubuntu, or how close we came to pitching Ubuntu out a window, as other distributions had kernels that worked fine.)
Sidebar: where this error message comes from
This message comes from
kernel/softlockup.c and gets generated if
the CPU's kernel watchdog thread hasn't run in ten seconds. (Kernel
watchdog threads are the '
watchdog/<N>' processes in ps output.)
This means that some bit of code has locked out scheduling for those ten seconds. Usually this means both that the code has a bug and that it has run into some sort of hardware problem it wasn't expecting, since people writing kernel code rarely knowingly allow ten second stalls.
An inspection of what stack backtrace I can recover from the system is not particularly revealing as to what driver or bit of hardware might be at fault. It runs more or less:
atkbd_connect → atkbd_activate → i8042_interrupt → ps2_command → ps2_sendbyte → i8042_kbd_write → _spin_unlock_irqrestore → idr_get_new <interrupt>
(Transcribed by hand and accuracy not guaranteed, especially as I
have omitted the offsets, which means that the code might actually be
in a nearby static function or something. The Ubuntu 6.06.1 server
install kernel is some version of 2.6.15, and there have been fixes to
lib/idr.c since then.)