I've followed Keith's suggestions and added
to lilo.conf and built a new kernel to go with it (kdb enabled). I've run
tests this morning and get either : good iozone run, or lockup/hang
(3). There were no more panics. I'll try more tests after lunch, but
if nobody's got any more ideas, I'll throw in the towel and check back
in a couple weeks (maybe this bug will get fixed by then).
The xfs code is what I downloaded yesterday after lunch and my kernel is
> Hmm, I see there were a couple of followups on the xfs hang during run 4,
> I would really like to chase this one down if there is any chance of help
> from your end in following Keith Owens' suggestions. The tricky part here
> is determining if this is xfs itself, or xfs driving the linux vm system
> up the wall. xfs itself did not change in the read/write path between 2.4.2
> and 2.4.4, but the kernel does have relevent changes, and there are probably
> more to make yet.