Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751156AbdCNI2y (ORCPT ); Tue, 14 Mar 2017 04:28:54 -0400 Received: from canardo.mork.no ([148.122.252.1]:48539 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750855AbdCNI2w (ORCPT ); Tue, 14 Mar 2017 04:28:52 -0400 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: "Brown\, Aaron F" Cc: Borislav Petkov , Andy Shevchenko , "lkml\@pengaru.com" , linux-kernel , "vcaputo\@pengaru.com" , "linux-pci\@vger.kernel.org" , "intel-wired-lan\@lists.osuosl.org" , khalidm , "David Singleton" , "Kirsher\, Jeffrey T" Subject: Re: [BUG] 4.11.0-rc1 panic on shutdown X61s Organization: m References: <20170312053723.GH802@shells.gnugeneration.com> <20170312115703.GA18197@nazgul.tnic> <20170312122621.GA2823@nazgul.tnic> <20170312222333.hm54nl2ul5iuixap@pd.tnic> <87shmhjfap.fsf@miraculix.mork.no> <309B89C4C689E141A5FF6A0C5FB2118B8C5B3F9B@ORSMSX101.amr.corp.intel.com> Date: Tue, 14 Mar 2017 09:28:09 +0100 In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C5B3F9B@ORSMSX101.amr.corp.intel.com> (Aaron F. Brown's message of "Tue, 14 Mar 2017 01:20:27 +0000") Message-ID: <87varci7om.fsf@miraculix.mork.no> User-Agent: Gnus/5.130015 (Ma Gnus v0.15) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 44419 Lines: 624 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable "Brown, Aaron F" writes: >> From: Bj=C3=B8rn Mork [mailto:bjorn@mork.no] >> >> Already did that a week ago: >> https://www.spinics.net/lists/netdev/msg423379.html >>=20 >> 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 I= 219-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=3Dfast >TAbort- SERR-