[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B68D4CA.2010803@gmail.com>
Date: Tue, 02 Feb 2010 17:43:38 -0800
From: "Justin P. Mattock" <justinmattock@...il.com>
To: Stefan Richter <stefanr@...6.in-berlin.de>
CC: Dan Carpenter <error27@...il.com>,
linux1394-devel@...ts.sourceforge.net,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Jan Beulich <jbeulich@...ell.com>
Subject: Re: ohci1394_dma=early crash since 2.6.32 (was Re: [Bug #14487] PANIC:
early exception 08 rip 246:10 error ffffffff810251b5 cr2 0)
o.k. finally finished with the bisect:
reverting this gets things going on 2.6.33-rc5
789d03f584484af85dbdc64935270c8e45f36ef7 is the first bad commit
commit 789d03f584484af85dbdc64935270c8e45f36ef7
Author: Jan Beulich <JBeulich@...ell.com>
Date: Tue Jun 30 11:52:23 2009 +0100
x86: Fix fixmap ordering
The merge of the 32- and 64-bit fixmap headers made a latent
bug on x86-64 a real one: with the right config settings
it is possible for FIX_OHCI1394_BASE to overlap the FIX_BTMAP_*
range.
Signed-off-by: Jan Beulich <jbeulich@...ell.com>
Cc: <stable@...nel.org> # for 2.6.30.x
LKML-Reference: <4A4A0A8702000078000082E8@....id2.novell.com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
The only thing I can think of at this point
is maybe the CFLAGS I used to build this system.
(as for the x86_32 working and x86_64 failing not sure);
I'm curious to see if anybody else is hitting this?
Justin P. Mattock
--
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