From: Ingo Molnar <mingo@kernel.org>
To: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [regression] 3.7 ends in APIC panic
Date: Sun, 16 Dec 2012 12:35:05 +0100 [thread overview]
Message-ID: <20121216113505.GA25304@gmail.com> (raw)
In-Reply-To: <50CB3EAB.309@itwm.fraunhofer.de>
* Bernd Schubert <bernd.schubert@itwm.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
next prev parent reply other threads:[~2012-12-16 11:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:58 [regression] 3.7 ends in APIC panic Bernd Schubert
2012-12-16 11:35 ` Ingo Molnar [this message]
2012-12-16 15:33 ` Bernd Schubert
2012-12-16 17:43 ` Yinghai Lu
2012-12-16 17:45 ` Yinghai Lu
2012-12-16 18:01 ` Bernd Schubert
2012-12-16 18:07 ` Yinghai Lu
2012-12-16 18:28 ` Bernd Schubert
2012-12-16 19:13 ` Borislav Petkov
2012-12-16 19:46 ` Bernd Schubert
2012-12-16 20:39 ` Borislav Petkov
2012-12-17 9:34 ` Bernd Schubert
2012-12-17 10:00 ` Borislav Petkov
2012-12-17 13:11 ` Bernd Schubert
2012-12-17 9:27 ` Bernd Schubert
2012-12-17 14:02 ` Ingo Molnar
2012-12-17 16:53 ` Yinghai Lu
2012-12-17 16:56 ` H. Peter Anvin
2012-12-17 17:03 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2012-12-13 12:16 Bernd Schubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121216113505.GA25304@gmail.com \
--to=mingo@kernel.org \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox