On Thu, Sep 21, 2006 at 12:18:40AM -0700, Bill Huey wrote:> On Thu, Sep 21, 2006 at 08:54:02AM +0200, Ingo Molnar wrote:> > that you saw crashes under 2.6.17 - but did you manage to figure out > > what the reason is for those crashes, and do those reasons really > > necessiate the pushing of task-reapdown into yet another set of kernel > > threads?> > Unfortunately no. I even used Robert's .config on my machine. I added a> disk controller and networking device driver just to boot into his> configuration and I still couldn't replicated any of his kjournald problems> at all. If I had his hardware I'd have a better way of replicating those> problems and pound it out.

Robert's stack traces looked completely wrong as well which is why I gave up.Symbols showing up in this stack traces should have been completely compiledout.

Also, triggering a panic() at the beginning of the rt mutex acquire wasvery useful since it made "in_atomic()" violations an explicit error stoppingthe machine. Stack traces started to get really crazy in this preemptivekernel with all sorts of things running unlike the non-preemptive kernel andit was time consuming to figure out the real stuff from the noise in thestack trace.

It made the stack traces smaller and more immediately local to the problemlogic. Then I discovered panic() didn't work correctly in -rt so I fixed thatas well. There were a lot of little breakdowns in 2.6.17-rt...