linux-kernel - Re: [regression] 3.7 ends in APIC panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121216113505.GA25304@gmail.com>
Date:	Sun, 16 Dec 2012 12:35:05 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Bernd Schubert <bernd.schubert@...m.fraunhofer.de>
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


* 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.

Thanks,

	Ingo
--
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/