I'm helping another company debug some network issues. They are seeing a hang on a 3.7.10+ kernel. It only happens on a few systems, so the suspicion is that is really is a hardware/driver issue, but of course it could be something else. The kernel is patched with some hacks to the bridging code, but no driver tweaks.
They had same problem with built-in kernel and with the 2.4.14 driver. The logs below appear to be from the out-of-tree driver. The OS is 64-bit debian. Any idea if this is a known problem? From dmesg: e1000e: Intel(R) PRO/1000 Network Driver - 2.4.14-NAPI e1000e: Copyright(c) 1999 - 2013 Intel Corporation. e1000e 0000:00:19.0: setting latency timer to 64 e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e 0000:00:19.0: irq 41 for MSI/MSI-X ... e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:25:90:7c:37:c7 e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF e1000e 0000:02:00.0: Disabling ASPM L0s L1 ACPI Warning: 0x0000000000000580-0x000000000000059f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120913/utaddress-251) ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20120913/utaddress-251) ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver e1000e 0000:02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich e1000e 0000:02:00.0: irq 42 for MSI/MSI-X e1000e 0000:02:00.0: irq 43 for MSI/MSI-X e1000e 0000:02:00.0: irq 44 for MSI/MSI-X iTCO_vendor_support: vendor-support=0 ..... e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: TDH <28> TDT <2c> next_to_use <2c> next_to_clean <26> buffer_info[next_to_clean]: time_stamp <10007f067> next_to_watch <28> jiffies <10007f9d5> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: TDH <28> TDT <2c> next_to_use <2c> next_to_clean <26> buffer_info[next_to_clean]: time_stamp <10007f067> next_to_watch <28> jiffies <1000801a5> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: TDH <28> TDT <2c> next_to_use <2c> next_to_clean <26> buffer_info[next_to_clean]: time_stamp <10007f067> next_to_watch <28> jiffies <100080975> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> ------------[ cut here ]------------ WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xe5/0x156() Hardware name: X9SCL/X9SCM NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Modules linked in: bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd fscache sunrpc ipv6 iTCO_wdt iTCO_vendor_support coretemp hwmon acpi_cpufreq mperf kvm_intel kvm video serio_raw lpc_ich mgag200 ttm drm_kms_helper drm i2c_algo_bit pcspkr i2c_i801 i2c_core microcode e1000e(O) Pid: 0, comm: swapper/0 Tainted: G O 3.7.10+ #1 Call Trace: <IRQ> [<ffffffff8103d83c>] warn_slowpath_common+0x7e/0x97 [<ffffffff813f83d9>] ? netif_tx_lock+0x85/0x85 [<ffffffff8103d8e9>] warn_slowpath_fmt+0x41/0x43 [<ffffffff813f84be>] dev_watchdog+0xe5/0x156 [<ffffffff810480f7>] call_timer_fn.isra.34+0x24/0x7d [<ffffffff813f83d9>] ? netif_tx_lock+0x85/0x85 [<ffffffff810486f3>] run_timer_softirq+0x15b/0x1a0 [<ffffffff81043811>] __do_softirq+0x9b/0x143 [<ffffffff810799b2>] ? clockevents_program_event+0x9b/0xb8 [<ffffffff8149859c>] call_softirq+0x1c/0x30 [<ffffffff8100bc1d>] do_softirq+0x40/0x7f [<ffffffff81043989>] irq_exit+0x3d/0x9e [<ffffffff8102471d>] smp_apic_timer_interrupt+0x76/0x84 [<ffffffff81497e5d>] apic_timer_interrupt+0x6d/0x80 <EOI> [<ffffffff8100fa85>] ? paravirt_read_tsc+0x9/0xd [<ffffffff8125e63c>] ? intel_idle+0xdd/0x10c [<ffffffff8125e61d>] ? intel_idle+0xbe/0x10c [<ffffffff813aa7df>] cpuidle_enter+0x12/0x14 [<ffffffff813aabf7>] cpuidle_enter_state+0xf/0x39 [<ffffffff813aac8e>] cpuidle_idle_call+0x6d/0x9b [<ffffffff8101128b>] cpu_idle+0x52/0xb0 [<ffffffff8146e472>] rest_init+0x76/0x7a [<ffffffff81a9cb49>] start_kernel+0x365/0x372 [<ffffffff81a9c5eb>] ? repair_env_string+0x5a/0x5a [<ffffffff81a9c2d6>] x86_64_start_reservations+0xb1/0xb5 [<ffffffff81a9c3d8>] x86_64_start_kernel+0xfe/0x10b ---[ end trace 13ac6b4fb42de363 ]--- e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly Thanks, Ben -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
