[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1231838731.4823.2.camel@leto.intern.saout.de>
Date: Tue, 13 Jan 2009 10:25:31 +0100
From: Christophe Saout <christophe@...ut.de>
To: Bryan Donlan <bdonlan@...il.com>
Cc: linux-kernel@...r.kernel.org, Nick Piggin <npiggin@...e.de>,
linux-mm@...ck.org, xen-devel@...ts.xensource.com
Subject: Re: [Xen-devel] Re: OOPS and panic on 2.6.29-rc1 on xen-x86
Hi Bryan,
> I've bisected the bug in question, and the faulty commit appears to be:
> commit e97a630eb0f5b8b380fd67504de6cedebb489003
> Author: Nick Piggin <npiggin@...e.de>
> Date: Tue Jan 6 14:39:19 2009 -0800
>
> mm: vmalloc use mutex for purge
>
> The vmalloc purge lock can be a mutex so we can sleep while a purge is
> going on (purge involves a global kernel TLB invalidate, so it can take
> quite a while).
>
> Signed-off-by: Nick Piggin <npiggin@...e.de>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
>
> The bug is easily reproducable by a kernel build on -j4 - it will
> generally OOPS and panic before the build completes.
> Also, I've tested it with ext3, and it still occurs, so it seems
> unrelated to btrfs at least :)
Nice!
Reverting this also fixes the BUG() I was seeing when testing the Dom0
patches on 2.6.29-rc1+tip. It just ran stable for an hour compiling
gimp and playing music on my notebook (and then I had to leave).
Thanks,
Christophe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists