netconsole lockup with current kernel 2.6.13-rc6-git3

[Olaf Hering <olh@suse.de>]

on the system to debug do:

girgendwas:~ # netconsole-server boettger:12346
verify the loglevel. otherwise no message may appear on the remove host, see man
dmesg(1)
now run 'netcat -l -u -p 12346' on host 10.10.125.16 to see further kernel messages
girgendwas:~ # echo 8 > /proc/sysrq-trigger
girgendwas:~ # echo t > /proc/sysrq-trigger

on the system to retrieve kernel messages from client above do:

netcat -l -u -p 12346
SysRq : Changing Loglevel
Loglevel set to 8
SysRq : Show State

                                               sibling
  task             PC      pid father child younger older
init          S 00000286     0     1      0     2               (NOTLB)
dfe1fec8 00000082 dfe1e000 00000286 0000002c 00000058 4f924352 00007b27
       ffff037f 00000bca 4f924ace 00007b27 c15d3b88 c15d3a60 c15d3540 c140d160
       4f92b4eb 00007b27 dfe1e000 00000000 00000282 c012f350 0204f514 c140dfe0
Call Trace:
 [<c012f350>] lock_timer_base+0x20/0x50
 [<c012f428>] __mod_timer+0xa8/0xd0
 [<c0342d7e>] schedule_timeout+0x4e/0xc0
 [<c012fed0>] process_timeout+0x0/0x10
 [<c018541f>] do_select+0x2af/0x360
 [<c0184f90>] __pollwait+0x0/0xd0


this is all I get, then the system is dead. I see it also on G5, no interrupts
served. Will check if older kernels work ok, it does at least work in SLES9
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/