linux-kernel - Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 14 Mar 2017 09:40:24 +0100
From:   Bjørn Mork <bjorn@...k.no>
To:     "Brown\, Aaron F" <aaron.f.brown@...el.com>
Cc:     Borislav Petkov <bp@...en8.de>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        "lkml\@pengaru.com" <lkml@...garu.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "vcaputo\@pengaru.com" <vcaputo@...garu.com>,
        "linux-pci\@vger.kernel.org" <linux-pci@...r.kernel.org>,
        "intel-wired-lan\@lists.osuosl.org" 
        <intel-wired-lan@...ts.osuosl.org>, khalidm <khalidm@...co.com>,
        "David Singleton" <davsingl@...co.com>,
        "Kirsher\, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Subject: Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

Bjørn Mork <bjorn@...k.no> writes:
> "Brown, Aaron F" <aaron.f.brown@...el.com> writes:
>>> From: Bjørn Mork [mailto:bjorn@...k.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