On Wed, Sep 30, 2009 at 03:42:52PM +0200, Thomas Gleixner wrote: | On Wed, 30 Sep 2009, Thomas Gleixner wrote: | | > On Wed, 30 Sep 2009, Luis Claudio R. Goncalves wrote: | > | > > Hello, | > > | > > This is apparently a new manifestation of the same issue I have been chasing | > > for quite a while and have been failing in a very shameful way to fix. In | > > the original issue, whenever I run deluge (bit torrent client) at | > > SCHED_FIFO, I got the error message below and system would freeze / panic | > > during shutdown: | > > | > > ================================================ | > > [ BUG: lock held when returning to user space! ] | > > ------------------------------------------------ | > > deluged/3035 is leaving the kernel with locks still held! | > > 1 lock held by deluged/3035: | > > #0: (&lock->lock){......}, at: [<ffffffffa02ae965>] ipt_do_table+0x10c/0x5f3 [ip_tables] | > | > Yikes. Can you please decode the code line for ffffffffa02ae965 ? Does | > the bug happen with function tracer enabled ? If yes, enable | > ftrace_dump_on_oops hook up a serial console and capture the dump. | | I'm quite sure that I know what breaks. Working on a fix. I will get the ftrace data anyway. I tried at first converting xt_info_lock to atomic_spin_lock but it lead to a bigger series of warnings :) Thanks for looking at this issue! Luis -- [ Luis Claudio R. Goncalves Bass - Gospel - RT ] [ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ] -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html