>-----Original Message-----
>From: Stephen Hemminger [mailto:[email protected]]
>Sent: Thursday, March 17, 2011 9:45 AM
>To: Kirsher, Jeffrey T; Jesse Brandeburg
>Cc: [email protected]
>Subject: [E1000-devel] transmit hang under load 82574L
>
>Running Intel n450 development board as a network based backup server,
>I saw the following transmit lockup under load (SMB backup).
>Kernel is 2.6.37.4.  Device did not recover, required a power cycle
>to get back online.
>
>$ /sbin/ethtool -i eth0
>driver: e1000e
>version: 1.2.7-k2
>firmware-version: 2.1-0
>bus-info: 0000:04:00.0
>$ lspci -vv -s 0000:04:00.0
>04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
>Connection
>       Subsystem: Intel Corporation Device 0000
>       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-
>       Latency: 0, Cache Line Size: 64 bytes
>       Interrupt: pin A routed to IRQ 16
>       Region 0: Memory at 50100000 (32-bit, non-prefetchable) [size=128K]
>       Region 2: I/O ports at 2000 [size=32]
>       Region 3: Memory at 50120000 (32-bit, non-prefetchable) [size=16K]
>       Capabilities: <access denied>
>       Kernel driver in use: e1000e
>
>[94504.992046] ------------[ cut here ]------------
>[94504.992068] WARNING: at net/sched/sch_generic.c:258 
>dev_watchdog+0xc9/0x15d()
>[94504.992076] Hardware name: Lobster Rock
>[94504.992084] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
>[94504.992091] Modules linked in: nfsd exportfs nfs lockd fscache nfs_acl
>auth_rpcgss sunrpc ext2 loop pl2303 tpm_tis usbserial psmouse i2c_i801 tpm
>i2c_core evdev pcspkr tpm_bios serio_raw video processor button ac output 
>sd_mod
>crc_t10dif ata_generic uhci_hcd ahci libahci ata_piix libata scsi_mod ehci_hcd
>usbcore thermal fan e1000e thermal_sys nls_base [last unloaded: scsi_wait_scan]
>[94504.992201] Pid: 0, comm: kworker/0:0 Not tainted 2.6.37.4 #5
>[94504.992208] Call Trace:
>[94504.992225]  [<c102be95>] ? warn_slowpath_common+0x6a/0x7b
>[94504.992236]  [<c1202154>] ? dev_watchdog+0xc9/0x15d
>[94504.992249]  [<c102bf0c>] ? warn_slowpath_fmt+0x28/0x2c
>[94504.992260]  [<c1202154>] ? dev_watchdog+0xc9/0x15d
>[94504.992272]  [<c1029cdc>] ? try_to_wake_up+0x131/0x13b
>[94504.992284]  [<c1030c8f>] ? __do_softirq+0x0/0x155
>[94504.992296]  [<c103c907>] ? __queue_work+0x1e7/0x201
>[94504.992308]  [<c1034acd>] ? cascade+0x46/0x57
>[94504.992319]  [<c1030c8f>] ? __do_softirq+0x0/0x155
>[94504.992331]  [<c1035ec2>] ? run_timer_softirq+0x169/0x208
>[94504.992342]  [<c120208b>] ? dev_watchdog+0x0/0x15d
>[94504.992353]  [<c1030c8f>] ? __do_softirq+0x0/0x155
>[94504.992363]  [<c1030d2d>] ? __do_softirq+0x9e/0x155
>[94504.992374]  [<c1030c8f>] ? __do_softirq+0x0/0x155
>[94504.992381]  <IRQ>  [<c1030c13>] ? irq_exit+0x26/0x59
>[94504.992401]  [<c10153b4>] ? smp_apic_timer_interrupt+0x6b/0x75
>[94504.992414]  [<c12832f1>] ? apic_timer_interrupt+0x31/0x38
>[94504.992428]  [<c102007b>] ? ftrace_raw_output_sched_stat_runtime+0x3b/0xab
>[94504.992442]  [<c116e8ec>] ? intel_idle+0xe2/0x103
>[94504.992455]  [<c11e19ed>] ? cpuidle_idle_call+0x73/0xd2
>[94504.992466]  [<c1001b40>] ? cpu_idle+0x93/0xd7
>[94504.992479]  [<c127f09e>] ? start_secondary+0x1d7/0x1dc
>[94504.992489] ---[ end trace 6735082c1e91fdc7 ]---
>[94504.992534] e1000e 0000:04:00.0: eth0: Reset adapter

Hi Stephen,

Could you please provide even more verbosity from lspci, i.e. with -vvv
run as root?  And the full dmesg log if you still have it might provide
additional useful information.

Thanks,
Bruce.

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to