[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50CDE9CD.5050309@itwm.fraunhofer.de>
Date: Sun, 16 Dec 2012 16:33:33 +0100
From: Bernd Schubert <bernd.schubert@...m.fraunhofer.de>
To: Ingo Molnar <mingo@...nel.org>
CC: linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Yinghai Lu <yinghai@...nel.org>
Subject: Re: [regression] 3.7 ends in APIC panic
On 12/16/2012 12:35 PM, Ingo Molnar wrote:
>
> * Bernd Schubert <bernd.schubert@...m.fraunhofer.de> wrote:
>
>> On 12/13/2012 01:16 PM, Bernd Schubert wrote:
>>> Hello,
>>>
>>> I just tried to boot 3.7 and it ends in an APIC panic. I
>>> tried to use the recommended "apic=debug", but that does not
>>> change anything in the output, at least not in the visible
>>> part. The last known kernel to boot was 3.5. If it matters I
>>> can try to boot 3.6.
>>
>> So linux-3.6 also boots. Any idea what is going on or do I
>> really need to bisect?
>
> Yeah, it's hard to tell based on that info alone - would be nice
> to send in a log/screen capture of the crash and of course
> bisecting would be useful as well, if the crash is
> deterministic.
I already sent a screen capture in my first mail, but now uploaded two
pictures here:
http://www.aakef.fastmail.fm/linux/
I think the 2nd one is with apic=debug.
Unfortunately the system does not have ipmi, which would allow me to do
the bisecting now. It is also my desktop system at work and I don't know
yet when (and if at all) I will find the time to do the reboot cycles.
Cheers,
Bernd
--
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