On Wed, 6 Dec 2006 16:17:10 +0100 (CET) Igmar Palsenberg <[EMAIL PROTECTED]> wrote:
> > > > It's rather large, but for those who want to look at it : > > > http://www.jdi-ict.nl/plain/serial-28112006.txt > > > > The same problem, this time with 2.6.19. I've done a show tasks, a show > > locks, a show regs, and after that, a sync + reboot :) > > > > Log is at http://www.jdi-ict.nl/plain/serial-04122006.txt . > > > > If anyone needs more info : please tell me. > > Done some more digging : isn't http://lkml.org/lkml/2006/10/13/139 somehow > related ? I do see pagefaults, and inode locks and mmap_locks. > I thought it was, but from my look through yout 8-billion-task backtrace, no task was stuck in D-state with the appropriate call trace. So I don't know what's causing this. In the first trace you have at least four D-state kjournalds and a lot of processes stuck on an i_mutex. I guess it's consistent with an IO system which is losing completion interrupts. AFAICT in the second trace all you have is a lot of processes stuck on i_mutex for no obvious reason - I don't know why that would happen. How long does it take for this to happen? Yes, lockdep might find something. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/