From: Greg KH <greg@kroah.com>
To: Marc Haber <mh+stable-kernel@zugschlus.de>,
Thomas Gleixner <tglx@linutronix.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
jarkko.nikula@linux.intel.com
Cc: stable@vger.kernel.org
Subject: Re: PC Engines APU panics on boot since 4.2.4
Date: Sun, 1 Nov 2015 10:34:18 -0800 [thread overview]
Message-ID: <20151101183418.GA15500@kroah.com> (raw)
In-Reply-To: <20151101182628.GL4392@torres.zugschlus.de>
On Sun, Nov 01, 2015 at 07:26:28PM +0100, Marc Haber wrote:
> Hi,
>
> On Sat, Oct 31, 2015 at 03:23:45PM -0700, Greg KH wrote:
> > On Sat, Oct 31, 2015 at 10:15:51PM +0100, Marc Haber wrote:
> > > I run a PC Engines APU in my basement for local infrastructure with
> > > KVM. Kernels 4.2.4 and 4.2.5 panic on bootup pretty fast after the
> > > usual "x86: Booted up 1 node, 2 CPUs", "smpboot: Total of 2 processors
> > > activated (3999.89 BogoMIPS)" message. The message I would expect
> > > instead of the kernel panic would be "devtmpfs: initialized", as one
> > > can see on a successful 4.2.3 boot with identical kernel configuration.
> >
> > If you use 'git bisect' between 4.2.3 and 4.2.5, can you find the
> > problem commit for us to help track this down?
>
> The winner is ...
> [21f751a634f3b5eaf916f940e47f327fbc6e9727] x86/ioapic: Force affinity setting in setup_ioapic_dest()
>
> After rolling this back in 4.2.5, the APU now runs fine.
Ok, this matches up with commit 21f751a634f3b5eaf916f940e47f327fbc6e9727
in Linus's tree.
Thomas and Mika, any thoughts about this?
Marc, do you have this same problem with Linus's tree at the moment as
well?
thanks,
greg k-h
next prev parent reply other threads:[~2015-11-01 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 21:15 PC Engines APU panics on boot since 4.2.4 Marc Haber
2015-10-31 22:23 ` Greg KH
2015-11-01 14:18 ` Marc Haber
2015-11-01 18:26 ` Marc Haber
2015-11-01 18:34 ` Greg KH [this message]
2015-11-01 18:57 ` Thomas Gleixner
2015-11-01 20:03 ` Marc Haber
2015-11-02 10:36 ` Marc Haber
2015-11-01 19:58 ` Marc Haber
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=20151101183418.GA15500@kroah.com \
--to=greg@kroah.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jiang.liu@linux.intel.com \
--cc=mh+stable-kernel@zugschlus.de \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).