From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755950AbbFRRGi (ORCPT ); Thu, 18 Jun 2015 13:06:38 -0400 Received: from outbound.smtp.vt.edu ([198.82.183.121]:39551 "EHLO omr1.cc.vt.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753126AbbFRRGf (ORCPT ); Thu, 18 Jun 2015 13:06:35 -0400 X-Greylist: delayed 1169 seconds by postgrey-1.27 at vger.kernel.org; Thu, 18 Jun 2015 13:06:35 EDT X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6+dev To: Yanir Lubetkin , Jeff Kirsher Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: e1000e driver - hang after 4 hours of uptime - finally bisected! From: Valdis Kletnieks Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1434646014_2109P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 18 Jun 2015 12:46:54 -0400 Message-ID: <5284.1434646014@turing-police.cc.vt.edu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --==_Exmh_1434646014_2109P Content-Type: text/plain; charset=us-ascii (follow up to a report from last week - bisecting took a while as I could only do 1 or 2 tests an evening) My Dell Latitude E6530 crashes with a specific kernel lockup almost exactly 4 hours after boot if there isn't a cable connected to the Ethernet port: [14508.846327] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 [14468.229720] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 [14463.254791] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 [14491.134413] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1 [14463.396593] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2 [14490.390223] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1 [14494.680591] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 [14513.365378] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1 [14482.271716] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 3 [14479.906820] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0 As far as I can tell, the timestamp jitter is just how long it takes me to enter the cryptLUKS passphrase for the hard drive at boot... lspci tells me: lspci -vvv -s "00:19.0" 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) DeviceName: Onboard LAN Subsystem: Dell Device 0535 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [] dump_stack+0x50/0xa8 [14479.906930] [] panic+0xcd/0x1e4 [14479.906940] [] ? perf_event_task_disable+0xc0/0xc0 [14479.906952] [] watchdog_overflow_callback+0x9b/0xa0 [14479.906959] [] __perf_event_overflow+0xc4/0x1f0 [14479.906968] [] perf_event_overflow+0x14/0x20 [14479.906976] [] intel_pmu_handle_irq+0x1e1/0x430 [14479.906990] [] perf_event_nmi_handler+0x26/0x40 [14479.906999] [] nmi_handle+0x103/0x340 [14479.907005] [] ? nmi_handle+0x5/0x340 [14479.907017] [] default_do_nmi+0xc3/0x120 [14479.907032] [] do_nmi+0xe8/0x130 [14479.907044] [] end_repeat_nmi+0x1e/0x2e [14479.907055] [] ? e1000e_cyclecounter_read+0x16/0xc0 [14479.907061] [] ? e1000e_cyclecounter_read+0x16/0xc0 [14479.907069] [] ? e1000e_cyclecounter_read+0x16/0xc0 [14479.907075] <> [] timecounter_read+0x19/0x60 [14479.907088] [] e1000e_phc_gettime+0x2e/0x60 [14479.907098] [] e1000e_systim_overflow_work+0x31/0x70 [14479.907105] [] process_one_work+0x3c9/0x980 [14479.907115] [] ? process_one_work+0x312/0x980 [14479.907125] [] ? worker_thread+0x78/0x760 [14479.907134] [] worker_thread+0x2cc/0x760 [14479.907144] [] ? process_one_work+0x980/0x980 [14479.907154] [] kthread+0xfe/0x120 [14479.907163] [] ? finish_task_switch+0x50/0x1c0 [14479.907173] [] ? kthread_create_on_node+0x270/0x270 [14479.907179] [] ret_from_fork+0x3f/0x70 [14479.907188] [] ? kthread_create_on_node+0x270/0x270 [14479.907243] Kernel Offset: 0x39000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) Bisection tells me it's this commit: commit 83129b37ef35bb6a7f01c060129736a8db5d31c4 Author: Yanir Lubetkin Date: Tue Jun 2 17:05:45 2015 +0300 e1000e: fix systim issues Two issues involving systim were reported. 1. Clock is not running in the correct frequency 2. In some situations, systim values were not incremented linearly This patch fixes the hardware clock configuration and the spurious non-linear increment. --==_Exmh_1434646014_2109P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Exmh version 2.5 07/13/2001 iQIVAwUBVYL1/QdmEQWDXROgAQJbig/8Cqcf/hSsjC/dt/gYU+99bcGDup4Tkfdo S/C5nb/bUsZkBEr5/0K3OPAFY10ofq5PqDehjlZquKuMDRYq4nGtCTzZVKV8djSX II4swbfRkDCg0O8TQGi20cwdWxFt1YKCKrL9of2Yzwenbxx3YZ4kG3c0v90UkUCq Rn5OcWLbJS6S/RwSu8ieIuW/8FB+BEmH3m4yYkhUkndvG0dUuqSI6VnXg2KsN6z+ DKgeQ0i4+eCkRP55Br426dAgi8UFwzIAb4Br7uWpXt05nR45Ta03mBjN843EBsQE t+krUGwHIuCNHXYEe6L6T7Dn8FPgX2xgfgj+LXmOSPqoKHZ1bD9b6FPcz2Te9UL0 EwNjvl/CYMk2cruuVwwyb0UzP2hwX4gRbLzkpr64haKTm8/oclHlRVwYm75qAnvr ZlcAbXUtaj1b52uApFlayMpRh+gEMDQ9Po90+V5V1qHyILitHolLb8LkFAj7Bvt7 j8KWqw8EaU2jKGaQw+17LRj6YY0FrIWcHnyznx13807+G38N1RD6RnIoZatBsfms 9jPMJgvjsNlXzubDDR5bvCvwz0upuCHOvIIqfNfGzZOHRJkeAXIPXq4hYsMc3aLU VSgmFHHDTR7pgNa0sNg9gYjKESmGPqDQ61lldZrMigcx52RNpfnQqA0MvgYdsVQw 73P2W/vE6Ms= =Z0qc -----END PGP SIGNATURE----- --==_Exmh_1434646014_2109P--