[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120714134849.GA1175@localhost>
Date: Sat, 14 Jul 2012 21:48:49 +0800
From: Fengguang Wu <wfg@...ux.intel.com>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Kernel boot hangs on commit "switch fput to task_work_add"
On Sat, Jul 14, 2012 at 02:05:10PM +0100, Al Viro wrote:
> On Tue, Jul 10, 2012 at 10:18:30PM +0800, wfg@...ux.intel.com wrote:
> > Hi Al,
> >
> > The linux-next kernel reliably hung after this line:
> >
> > [ 4.846260] debug: unmapping init [mem 0xffff88000182a000-0xffff8800019fffff]
> >
> > And it's bisected to commit:
> >
> > commit 4a9ffe81385c2af04f296bea05482f34e02ea10d
> > Author: Al Viro <viro@...iv.linux.org.uk>
> > Date: Sun Jun 24 09:56:45 2012 +0400
> >
> > switch fput to task_work_add
> >
> > ... and schedule_work() for interrupt/kernel_thread callers
> > (and yes, now it *is* OK to call from interrupt).
> >
> > I tried add this debug aid:
> >
> > init_post(void):
> > + printk(KERN_WARNING "flush_delayed_fput\n");
> > flush_delayed_fput();
> > + printk(KERN_WARNING "flush_delayed_fput done\n");
> >
> > And then it hangs after "flush_delayed_fput done". So it's not directly
> > freezing inside flush_delayed_fput()..
>
> Could you post a stack trace, etc.? I'll try to reproduce that one, obviously,
> but...
Hi Al, here I got the output for
(qemu) sendkey alt-sysrq-l
(qemu) sendkey alt-sysrq-t
Thanks,
Fengguang
View attachment "dmesg-kvm_bisect-waimea-3828-2012-07-14-21-46-27" of type "text/plain" (103779 bytes)
Powered by blists - more mailing lists