[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080720145132.1df6b10d@kopernikus.site>
Date: Sun, 20 Jul 2008 14:51:32 +0200
From: Bernhard Walle <bwalle@...e.de>
To: Greg KH <gregkh@...e.de>
Cc: Vegard Nossum <vegard.nossum@...il.com>,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
Dave Hansen <haveblue@...ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
kernel-testers@...r.kernel.org, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Ingo Molnar <mingo@...e.hu>, Vivek Goyal <vgoyal@...hat.com>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068
trace_hardirqs_on_caller
* Greg KH <gregkh@...e.de> [2008-07-19 16:20]:
>
> > Maybe the firmware memmap code can simply run a little later in the
> > boot sequence?
>
> Possibly. I wonder why this is only a problem on your machine and not
> on anything that Ingo tested?
It also was on my machine when I tested it on linux-next. That's why I
made the patch as described in
http://article.gmane.org/gmane.linux.kernel.kexec/1882.
However, it was not in tip tree. It seems to be the combination of
patches, but I don't know why and I didn't have the time to find it
out, the fix was much easier.
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--
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