lockdep warning

[Anders Eriksson]

I found this is a newly booted 2.6.25-rc2's syslog.

Feb 21 20:46:33 tippex BUG: rwlock wrong owner on CPU#0, runscript.sh/2633, d2c04084
Feb 21 20:46:33 tippex Pid: 2633, comm: runscript.sh Not tainted 2.6.25-rc2 #3
Feb 21 20:46:33 tippex [<c02342d0>] rwlock_bug+0x50/0x60
Feb 21 20:46:33 tippex [<c0234356>] _raw_write_unlock+0x56/0x60
Feb 21 20:46:33 tippex [<c040365d>] _write_unlock+0x1d/0x50
Feb 21 20:46:33 tippex [<c03289be>] neigh_timer_handler+0x18e/0x2d0
Feb 21 20:46:33 tippex [<c0125449>] run_timer_softirq+0x119/0x180
Feb 21 20:46:33 tippex [<c013856d>] ? lock_release_holdtime+0x5d/0x80
Feb 21 20:46:33 tippex [<c0328830>] ? neigh_timer_handler+0x0/0x2d0
Feb 21 20:46:33 tippex [<c0121a64>] __do_softirq+0x54/0xb0
Feb 21 20:46:33 tippex [<c0121af5>] do_softirq+0x35/0x40
Feb 21 20:46:33 tippex [<c0121cb4>] irq_exit+0x44/0x50
Feb 21 20:46:33 tippex [<c0105757>] do_IRQ+0x47/0x80
Feb 21 20:46:33 tippex [<c01039c3>] common_interrupt+0x23/0x28
Feb 21 20:46:33 tippex =======================


It doesn't make any sens to me but I guess it does to others.

The other bad thing is that the machine hangs shortly after boot bitching 
about 'hdb: lost interrupt' on the console. Kown problem?

/A

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/