From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Justin P. Mattock" 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) Date: Mon, 01 Feb 2010 23:03:44 -0800 Message-ID: <4B67CE50.8000001@gmail.com> References: <4B6630CA.9010207@gmail.com> <20100201125441.GB2576@bicker> <4B671606.3080405@gmail.com> <4B673233.8000300@s5r6.in-berlin.de> <4B6740B5.5070601@gmail.com> <4B675534.5070107@s5r6.in-berlin.de> <4B676917.2080506@gmail.com> <4B67BC12.4080709@s5r6.in-berlin.de> <4B67C4D2.5050205@gmail.com> <4B67CC55.40301@s5r6.in-berlin.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=TdCVh+OjBTzqPrati5y1A+4Ao1BVx0aEFwSsrnjmzXI=; b=qmviSC2e8xVc8h6kzcgsL2Ss/gIdEYaRNBk5xaqhN4DKfZn8rs8ZmvEKPz+WIRwAWg Oo8tmUA9Jf5rXlC/ewUwXPyMfXKICedq+0XjZfVtnVv1ka/zmUM3DueviH9NPi2AXmok oFO2nja81/Pv4Jjji964lEAXcxKz97zQ0aMa8= In-Reply-To: <4B67CC55.40301-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Stefan Richter Cc: Dan Carpenter , linux1394-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List On 02/01/10 22:55, Stefan Richter wrote: > Justin P. Mattock wrote: >> As for anything changed in the kernel >> (2.6.31 - present), tough to say >> from what I remember I had created a new fresh >> lfs system using these CFLAGS: >> >> CFLAGS="-mtune=core2 -march=core2 -O2 -pipe -fomit-frame-pointer" >> CXXFLAGS="${CFLAGS}" MAKEOPTS="{-j3}" >> (without -m option gcc defaults(I think)to -m32). >> >> which booted with ohci1394_dma=early just fine. >> >> then decided to build another lfs system with the same CFLAGS except >> added -m64 (pure64) to the build process. >> (then this showed up). >> >> What I can try is do a git revert to 2.6.29/27 to see if this thing >> fires off(before going any further). if the system boots then do a bisect. > > Do I understand correctly that at this moment it is only known that the > bug could be > - *either* a 2.6.31 -> 2.6.32 regression > - *or* an x86-64 specific bug that does not occur on x86-32, > right? > at first I was under the impression this was an arch thing because of building an x86_32, and then building x86_64(and hitting this). but now after reverting to 2.6.27 I'm thinking other wise.(my bad, should of done this at first but didn't even think too); > I have an Core 2 Duo based PC with x86-32 kernel and userland and an AMD > based x86-64 PC and could give ohci1394_dma=early a try on both (never > tested it myself before). I could furthermore attempt to build and > install an x86-64 kernel on the Core 2 Duo PC but I am afraid I am far > too short of spare time for that. no.. I need to do a bisect from 2.6.27 to present to see (just need to crash for a few hrs, then can start); then I'll go from there. Justin P. Mattock