From: "Brown, Aaron F" <aaron.f.brown@intel.com>
To: Shawn Starr <shawn.starr@rogers.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [4.10][regression][PM] Oops pci_restore_msi_state() e1000e? (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s)
Date: Thu, 16 Mar 2017 06:52:43 +0000 [thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B8C5B4FB3@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <cb090040-8648-534f-8712-ca2b6b1d8e94@rogers.com>
> From: Shawn Starr [mailto:shawn.starr@rogers.com]
> Sent: Tuesday, March 14, 2017 1:43 PM
> To: linux-kernel@vger.kernel.org
> Cc: Brown, Aaron F <aaron.f.brown@intel.com>
> Subject: Re: [4.10][regression][PM] Oops pci_restore_msi_state() e1000e?
> (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s)
>
> This isn't just Lenovo,
>
> My Dell laptop experiences same problem, there is bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=194801
Yes, I had noticed a Dell laptop in one of the reports in addition to the Thinkpads. As it turns out one of the systems I have been trying to reproduce it on is a Lenova with an 82677LM, a newer chipset than the one Vito Caputo is seeing the problem on (82566) and a slightly older one than the one Boris Petkov reported (82579LM.) I also have been trying with a SuperMicro that has an 82579LM that matches Boris's lspci output very closely and still have not managed to trigger it. I used the config Boris provided to build a kernel and tried it on those systems (and a number of other ones) and still have not succeeded in making it break. Given I've tried with the same config as one that's breaking and the range of chipsets it is appearing on I'm suspicious it's more to do with the system environment than the exact kernel config or e1000e chipset, but really don't know. If I try to pursue it more I guess I'll try installing a Debian build on some of the systems.
Regardless, Sasha Neftin weighed in on it agreeing it needs to be reverted and the upstream people were included, so hopefully it will get reverted in one of the next dot releases.
-Aaron
prev parent reply other threads:[~2017-03-16 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 9:53 [4.10][regression][PM] Oops pci_restore_msi_state() e1000e? Shawn Starr
2017-03-14 20:43 ` [4.10][regression][PM] Oops pci_restore_msi_state() e1000e? (Re: [BUG] 4.11.0-rc1 panic on shutdown X61s) Shawn Starr
2017-03-16 6:52 ` Brown, Aaron F [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=309B89C4C689E141A5FF6A0C5FB2118B8C5B4FB3@ORSMSX101.amr.corp.intel.com \
--to=aaron.f.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.com \
/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).