On Thu, 2008-02-07 at 19:26 -0600, Jay Cliburn wrote: > On Thu, 07 Feb 2008 21:24:47 +0100 > Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> The trace isn't from me; it's from Zan. He's running -mm, I'm not, if > that makes a difference. > > > > > Call Trace: > > [schedule_timeout+149/208] schedule_timeout+0x95/0xd0 > > [<ffffffff8057dde5>] schedule_timeout+0x95/0xd0 > > [tty_poll+145/160] tty_poll+0x91/0xa0 > > [<ffffffff80430f11>] tty_poll+0x91/0xa0 > > [do_sys_poll+617/880] do_sys_poll+0x269/0x370 > > [<ffffffff802bbe69>] do_sys_poll+0x269/0x370 > > [__pollwait+0/304] __pollwait+0x0/0x130 > > [<ffffffff802bcb30>] __pollwait+0x0/0x130 > > Now that my computer is back on the air again, I'll be happy to help > track this down. Just tell me what to do. First would be to see if you could get a sysrq-t dump of the blocked process. I'm curious if yours would point to the same spot. Also, could you describe how to reproduce it, given that you managed to have it reproducable enough to bisect, I'd say you have a good case. I installed gnome-terminal, started it and wiggled it about while doing find / - that didn't manage to get it to lock up - but I'll try again if that is the right way. -- 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/
