From: Meelis Roos <mroos@linux.ee>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: 4.7-rc6: NMI in intel_idle on HP Proliant G6
Date: Wed, 13 Jul 2016 10:21:27 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1607131018150.20366@math.ut.ee> (raw)
In-Reply-To: <alpine.LRH.2.20.1607121654490.2088@math.ut.ee>
> > > > On HP Proliant DL360 G6, Debian unstable 4.6 kernel runs fine but
> > > > selfcompiled 4.7-rc6 and 4.7-rc7 sometimes crash with NMI from
> > > > intel_idle. Sometimes it boots fine. With intel_idle disabled, it has
> > > > booted successful so far in 2 tries, one with rc6 and one with rc7.
> > >
> > > More testing shows it can NMI on acpi_idle too, not just intel_idle.
> > >
> > > > Screenshot with some backtrace:
> > > > http://kodu.ut.ee/~mroos/intel-idle-NMI.png
> > >
> > > http://kodu.ut.ee/~mroos/acpi-idle-NMI.png
> >
> > There were almost no changes in the ACPI idle driver between 4.6 and
> > 4.7-rc, so the reason is somewhere else.
> >
> > Have you tried any earlier 4.7-rc?
>
> I tried selfcompiled 4.6.0 now with the same conf that 4.7-rc's have and
> after multiple tries I got the same NMI out of 4.6 too, from kernfs
> lookup (that seems to just a random victim).
>
> So this is not a 4.7 regression and probably not idle-releated.
Confirmed this is about IOMMU+DMAR, I'm continuing in another reply
thread with other CC-s to not bother linux-pm people with it.
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2016-07-13 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 12:05 4.7-rc6: NMI in intel_idle on HP Proliant G6 Meelis Roos
2016-07-12 12:27 ` Meelis Roos
2016-07-12 12:40 ` Rafael J. Wysocki
2016-07-12 14:22 ` Meelis Roos
2016-07-13 7:21 ` Meelis Roos [this message]
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=alpine.LRH.2.20.1607131018150.20366@math.ut.ee \
--to=mroos@linux.ee \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).