From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Walle Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller Date: Sun, 20 Jul 2008 14:51:32 +0200 Message-ID: <20080720145132.1df6b10d@kopernikus.site> References: <20080718195352.e562a00f.sfr@canb.auug.org.au> <200807190928.33978.m.kozlowski@tuxland.pl> <19f34abd0807190255x304173d4wf2bfabb2d5bce511@mail.gmail.com> <19f34abd0807190559y2fe5ebf9h7095793e82de3122@mail.gmail.com> <20080719221723.GB5578@suse.de> <19f34abd0807191527u61c5ed61kffe2279c8d46915d@mail.gmail.com> <19f34abd0807191544nfd73be5nf7dde4b61992a7e8@mail.gmail.com> <20080719225817.GA6264@suse.de> <19f34abd0807191611y7cabf405iad307ba79591e04f@mail.gmail.com> <20080719232021.GA6476@suse.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080719232021.GA6476@suse.de> Sender: linux-next-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Greg KH Cc: Vegard Nossum , Mariusz Kozlowski , Dave Hansen , Stephen Rothwell , kernel-testers@vger.kernel.org, linux-next@vger.kernel.org, LKML , Pekka Enberg , Ingo Molnar , Vivek Goyal * Greg KH [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