[Pkg-sysvinit-devel] Bug#454147: Stuck bootlogd causes kernel crash

[Gabor Gombas]

clone 454147 -1
reassign -1 linux-image-2.6.26-1-xen-amd64
retitle -1 Stuck bootlogd causes kernel crash
thanks

Hi,

After upgrading some Xen domUs from the 2.6.18 etch kernel to the lenny
kernel, I got hit by bug #454147, but so far only when the dom0 kernel
is also from lenny. Moreover, if I do not kill the runaway bootlogd
process, then after about a day the domU crashes quite reliably. I now
managed to capture the OOPS:

Feb 17 02:10:18 host kernel: [60252.521849] ------------[ cut here ]------------
Feb 17 02:10:19 host kernel: [60252.521868] kernel BUG at drivers/char/tty_io.c:811!
Feb 17 02:10:19 host kernel: [60252.521874] invalid opcode: 0000 [1] SMP 
Feb 17 02:10:19 host kernel: [60252.521881] CPU 0 
Feb 17 02:10:19 host kernel: [60252.521886] Modules linked in: ipv6 evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod thermal_sys
Feb 17 02:10:19 host kernel: [60252.521909] Pid: 896, comm: bootlogd Not tainted 2.6.26-1-xen-amd64 #1
Feb 17 02:10:19 host kernel: [60252.521915] RIP: e030:[<ffffffff80359f91>]  [<ffffffff80359f91>] tty_ldisc_put+0x34/0x5e
Feb 17 02:10:19 host kernel: [60252.521933] RSP: e02b:ffff8800016e1e18  EFLAGS: 00010046
Feb 17 02:10:19 host kernel: [60252.521939] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb 17 02:10:19 host kernel: [60252.521945] RDX: 0000000000000000 RSI: ffff880001d0fb00 RDI: ffffffff806000a4
Feb 17 02:10:19 host kernel: [60252.521952] RBP: 0000000000000000 R08: ffffffff805081a1 R09: ffff88000207e000
Feb 17 02:10:19 host kernel: [60252.521958] R10: ffff88000ec9c980 R11: 0000000000000003 R12: 0000000000000000
Feb 17 02:10:19 host kernel: [60252.521965] R13: 0000000000000000 R14: 0000000000000000 R15: ffff880000e98a80
Feb 17 02:10:19 host kernel: [60252.521974] FS:  00007fd23107a6e0(0000) GS:ffffffff80539000(0000) knlGS:0000000000000000
Feb 17 02:10:19 host kernel: [60252.521983] CS:  e033 DS: 0000 ES: 0000
Feb 17 02:10:19 host kernel: [60252.521989] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 17 02:10:19 host kernel: [60252.521995] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 17 02:10:19 host kernel: [60252.522003] Process bootlogd (pid: 896, threadinfo ffff8800016e0000, task ffff88000e1d9780)
Feb 17 02:10:19 host kernel: [60252.522011] Stack:  ffff880000e98a80 ffff88000ec9c800 0000000000000000 ffffffff8035cad0
Feb 17 02:10:19 host kernel: [60252.522024]  0000000c39082430 0000000000000000 0000000200000003 0000000080436597
Feb 17 02:10:19 host kernel: [60252.522035]  0000000000000003 ffff88000fc16080 ffff88000fc16080 ffff88000f95a7d0
Feb 17 02:10:19 host kernel: [60252.522044] Call Trace:
Feb 17 02:10:19 host kernel: [60252.522053]  [<ffffffff8035cad0>] release_dev+0x546/0x5ce
Feb 17 02:10:19 host kernel: [60252.522061]  [<ffffffff8035cb69>] tty_release+0x11/0x1a
Feb 17 02:10:19 host kernel: [60252.522069]  [<ffffffff8028b1a2>] __fput+0xa1/0x16b
Feb 17 02:10:19 host kernel: [60252.522076]  [<ffffffff802888bb>] filp_close+0x5d/0x65
Feb 17 02:10:19 host kernel: [60252.522082]  [<ffffffff80289c25>] sys_close+0xa5/0x109
Feb 17 02:10:19 host kernel: [60252.522090]  [<ffffffff8020b528>] system_call+0x68/0x6d
Feb 17 02:10:19 host kernel: [60252.522096]  [<ffffffff8020b4c0>] system_call+0x0/0x6d
Feb 17 02:10:19 host kernel: [60252.522102] 
Feb 17 02:10:19 host kernel: [60252.522106] 
Feb 17 02:10:19 host kernel: [60252.522110] Code: ff 11 76 04 0f 0b eb fe 48 c7 c7 a4 00 60 80 e8 ec c0 0d 00 48 89 c5 48 63 c3 48 69 d0 90 00 00 00 8b 82 48 01 60 80 85 c0 75 04 <0f> 0b eb fe 48 8b ba 40 01 60 80 ff c8 89 82 48 01 60 80 e8 c3 

After logging the OOPS the domU becomes unresponsive both on the console
and over the network.

Gabor

-- 
     ---------------------------------------------------------
     MTA SZTAKI Computer and Automation Research Institute
                Hungarian Academy of Sciences
     ---------------------------------------------------------