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:28:09 +0100 [thread overview]
Message-ID: <87varci7om.fsf@miraculix.mork.no> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C5B3F9B@ORSMSX101.amr.corp.intel.com> (Aaron F. Brown's message of "Tue, 14 Mar 2017 01:20:27 +0000")
[-- Attachment #1: Type: text/plain, Size: 4409 bytes --]
"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.
>This one was tested by me and I did not have the same results you and
>the other people reporting this trace did. I made it back in the lab
>today and have spent a good part of the day attempting to reproduce
>this bug without success. Freeze / resume works for me on all the
>systems I have tried, which includes a sampling of all the current
>parts and many older ones. Given there are several other reports of
>this it is obviously an issue and I would like to be able to reproduce
>it in case another patch to resolve the issue this attempts to fix
>comes back in another form. So I want to know what's different between
>the systems that hit this and my bank of systems that don't.
>
> What exact part (or parts) are we looking at (lspci|grep -i eth) that
> trigger this? Could it be a difference in .config files? The trace
> says it is falling back to legacy interrupts, does the system continue
> to work and does the network continue to function in that mode? In
> case it's related to user space what is the base distro? Any other
> information you think can help me reproduce the issue would be
> appreciated.
I have a somewhat newer laptop than Borislav. But mine is also a Lenovo
Thinkpad, so that might be a thing. My system is a Lenovo Thinkpad X1
Carbon Gen4, which is a Skylake generation laptop. lspci output as
configured in v4.9:
root@miraculix:/tmp# lspci -vvvnnxxxs 1f.6
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
Subsystem: Lenovo Ethernet Connection I219-LM [17aa:2233]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 134
Region 0: Memory at e1300000 (32-bit, non-prefetchable) [disabled] [size=128K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00378 Data: 0000
Capabilities: [e0] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: e1000e
Kernel modules: e1000e
00: 86 80 6f 15 00 04 10 00 21 00 00 02 00 00 00 00
10: 00 00 30 e1 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 aa 17 33 22
30: 00 00 00 00 c8 00 00 00 00 00 00 00 ff 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 28 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 1f 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 01 00 00 00 03 10 03 10 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 01 d0 23 c8 0b 21 00 00
d0: 05 e0 81 00 78 03 e0 fe 00 00 00 00 00 00 00 00
e0: 13 00 06 03 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Attaching the .config. The laptop is running Debian sid, which is more
or less "stretch" now. But I usually build my kernels on a Debian
stable ("jessie") system if that matters.
As for whether it works or not, I must admit that I haven't tested.
Wired ethernet is not something I use on a daily basis on this laptop.
Will test it when I find time, but sending this now so you have
something to start working with.
Thanks
Bjørn
[-- Attachment #2: config-v4.11.0-rc1.gz --]
[-- Type: application/gzip, Size: 29480 bytes --]
next prev parent reply other threads:[~2017-03-14 8:28 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 [this message]
2017-03-14 8:40 ` Bjørn Mork
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=87varci7om.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
Powered by JetHome