From: "Bjørn Mork" <bjorn@mork.no>
To: "Brown\, Aaron F" <aaron.f.brown@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"lkml\@pengaru.com" <lkml@pengaru.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"vcaputo\@pengaru.com" <vcaputo@pengaru.com>,
"linux-pci\@vger.kernel.org" <linux-pci@vger.kernel.org>,
"intel-wired-lan\@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>, khalidm <khalidm@cisco.com>,
"David Singleton" <davsingl@cisco.com>, "Kirsher\,
Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: [BUG] 4.11.0-rc1 panic on shutdown X61s
Date: Tue, 14 Mar 2017 09:40:24 +0100 [thread overview]
Message-ID: <87pohki747.fsf@miraculix.mork.no> (raw)
In-Reply-To: <87varci7om.fsf@miraculix.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork"'s message of "Tue, 14 Mar 2017 09:28:09 +0100")
Bjørn Mork <bjorn@mork.no> writes:
> "Brown, Aaron F" <aaron.f.brown@intel.com> writes:
>>> From: Bjørn Mork [mailto:bjorn@mork.no]
>>>
>>> Already did that a week ago:
>>> https://www.spinics.net/lists/netdev/msg423379.html
>>>
>>> Haven't heard anything back yet. Wondering if they are waiting for
>>> someone else to submit the pretty obvious revert? Don't understand why
>>> that should take more than a minute to figure out. It's not like they
>>> are testing these changes anyway...
>>
>> Believe it or not we actually do test these changes.
>
> Yes, I know you did. Sorry. I should stop throwing such comments around.
So I have made that mistake before, and never learn. But the good thing
about that is that it now rang a bell. I once had suspend issues with a
completely different Intel device on another Lenovo laptop, which turned
out to be caused by the Lenovo firmware accessing the device while it is
in D3: https://lkml.org/lkml/2015/3/2/183
I don't have a clue about how these things work so this might be
completely unrelated. Just thought I'd mention it as an example of how
the Lenovo firmware can do unexpected things.
>From the reports so far, it looks like the issue at hand affects most
(all?) Lenovo Thinkpads with an e1000e part. If you haven't tried
already, it might be interesting to see if you can reproduce it on a
Thinkpad.
Bjørn
next prev parent reply other threads:[~2017-03-14 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 5:37 lkml
2017-03-12 11:57 ` Borislav Petkov
2017-03-12 12:26 ` Borislav Petkov
2017-03-12 13:55 ` Andy Shevchenko
2017-03-12 22:23 ` Borislav Petkov
2017-03-13 16:46 ` Bjørn Mork
2017-03-14 1:20 ` Brown, Aaron F
2017-03-14 1:43 ` Borislav Petkov
2017-03-14 2:40 ` lkml
2017-03-16 20:13 ` [Intel-wired-lan] " Bowers, AndrewX
2017-03-22 2:04 ` lkml
2017-03-22 2:13 ` lkml
2017-03-22 19:00 ` Borislav Petkov
2017-03-24 6:18 ` Jeff Kirsher
2017-03-24 8:47 ` Borislav Petkov
2017-03-14 7:49 ` Neftin, Sasha
2017-03-14 8:28 ` Bjørn Mork
2017-03-14 8:40 ` Bjørn Mork [this message]
2017-03-12 18:24 ` lkml
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=87pohki747.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=aaron.f.brown@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=davsingl@cisco.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=khalidm@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkml@pengaru.com \
--cc=vcaputo@pengaru.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
all inboxes | Powered by JetHome®