[Cc'ing Ingo just in case] I demand that I definitely did write... > I demand that Andrew Morton may or may not have written... >> Darren Salt wrote: >>> I'm seeing bouts of log flooding caused by something presumably not >>> releasing a lock. I've looked at some of the messages, but at around >>> 100/s, I'm not too keen to look through the whole lot :-) >>> scheduling while atomic: swapper/0xafbfffff/0 >>> [show_trace+19/32] >>> [dump_stack+30/32] >>> [schedule+1278/1472] >>> [cpu_idle+88/96] > [snip] >> Thanks for the report. >> The below patch (against 2.6.17-rc3) should, if it still works, tell us >> which lock didn't get unlocked. > [snip Ingo's CONFIG_DEBUG_PREEMPT patch] [snip] > Since [two previous unrecorded crashes], I've had no problems, and I'd got > this message queued for sending. With impeccable timing, the bug is > triggered... > Unfortunately, all that's been logged by the preempt debug code is this: > kernel BUG at lib/preempt.c:32! WE HAVE A BACKTRACE. I repeat, WE HAVE A BACKTRACE. Attached: dmesg (with boring routine agpgart/drm me-playing-with-X bits removed) post-crash task log (looks truncated?) kernel config The logging was done via netconsole. Patches applied: CONFIG_DEBUG_PREEMPT, my USB mouse buttons hack, and the FP exception fix which was posted to lkml. The mouse patch is attached for completeness. -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. The time is right to make new friends.