Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759506AbZANVF4 (ORCPT ); Wed, 14 Jan 2009 16:05:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754054AbZANVFs (ORCPT ); Wed, 14 Jan 2009 16:05:48 -0500 Received: from mail-qy0-f11.google.com ([209.85.221.11]:46339 "EHLO mail-qy0-f11.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754130AbZANVFr (ORCPT ); Wed, 14 Jan 2009 16:05:47 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lX36draEbFC7wZyT3lZURBGX4PAFraG1+LK0AcI+cv8H6aroCZaX5L+WQPNDpWIVrB yB9OCAPj+3b8OanQZsZ9QqQtPWcisze/zEWJxpe+E+Fo120m2i/8afh6Lff4l+FK/p5h P8EljdfpuXfltoQajZqYQtRVYkT0LMMPzlSgw= Message-ID: <3e8340490901141305x7155cf10ueed386646d6e21ee@mail.gmail.com> Date: Wed, 14 Jan 2009 16:05:45 -0500 From: "Bryan Donlan" To: "Nick Piggin" Subject: Re: OOPS and panic on 2.6.29-rc1 on xen-x86 Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, linux-mm@kvack.org In-Reply-To: <20090114025910.GA17395@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20090112172613.GA8746@shion.is.fushizen.net> <3e8340490901122054q4af2b4cm3303c361477defc0@mail.gmail.com> <20090114025910.GA17395@wotan.suse.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2340 Lines: 62 On Tue, Jan 13, 2009 at 9:59 PM, Nick Piggin wrote: > On Mon, Jan 12, 2009 at 11:54:32PM -0500, Bryan Donlan wrote: >> On Mon, Jan 12, 2009 at 12:26 PM, Bryan Donlan wrote: >> > [resending with log/config inline as my previous message seems to have >> > been eaten by vger's spam filters] >> > >> > Hi, >> > >> > After testing 2.6.29-rc1 on xen-x86 with a btrfs root filesystem, I >> > got the OOPS quoted below and a hard freeze shortly after boot. >> > Boot messages and config are attached. >> > >> > This is on a test system, so I'd be happy to test any patches. >> > >> > Thanks, >> > >> > Bryan Donlan >> >> I've bisected the bug in question, and the faulty commit appears to be: >> commit e97a630eb0f5b8b380fd67504de6cedebb489003 >> Author: Nick Piggin >> 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 >> Signed-off-by: Andrew Morton >> Signed-off-by: Linus Torvalds >> >> 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 :) >> >> > >> > ------------[ cut here ]------------ >> > Kernel BUG at c05ef80d [verbose debug info unavailable] >> > invalid opcode: 0000 [#1] SMP >> > last sysfs file: /sys/block/xvdc/size >> > Modules linked in: > > It is bugging in schedule somehow, but you don't have verbose debug > info compiled in. Can you compile that in and reproduce if you have > the time? Sure - which config option would that be? CONFIG_DEBUG_BUGVERBOSE? > Going bug here might indicate that there is some other problem with > the Xen and/or vmalloc code, regardless of reverting this patch. > > Thanks, > Nick > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/