Bug 708047 - NETDEV WATCHDOG: eth0 (skge): transmit queue 0 timed out
Summary: NETDEV WATCHDOG: eth0 (skge): transmit queue 0 timed out
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 740619 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-26 16:00 UTC by redhat-bugzilla
Modified: 2012-07-11 17:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 17:52:34 UTC
Type: ---


Attachments (Terms of Use)

Description redhat-bugzilla 2011-05-26 16:00:59 UTC
Description of problem:
When booted into the 2.6.38.6-27.fc15.x86_64 kernel, my built-in network connections do not work properly and give extreme packet loss (~52%), my pci-e addon intel card did not have any issues. Soon after NETDEV WATCHDOG started complaining about transmit queue 0 timed out.


Version-Release number of selected component (if applicable):
2.6.38.6-27.fc15.x86_64

How reproducible:
every boot (tried 3 times)

Steps to Reproduce:
1. boot into the affected kernel
try to ping something
  
Actual results:
PING modem.home (192.168.100.1) 56(84) bytes of data.
64 bytes from modem.home (192.168.100.1): icmp_req=2 ttl=64 time=4.80 ms
64 bytes from modem.home (192.168.100.1): icmp_req=4 ttl=64 time=1.30 ms
64 bytes from modem.home (192.168.100.1): icmp_req=5 ttl=64 time=1.41 ms
64 bytes from modem.home (192.168.100.1): icmp_req=8 ttl=64 time=1.29 ms
64 bytes from modem.home (192.168.100.1): icmp_req=10 ttl=64 time=1.29 ms
64 bytes from modem.home (192.168.100.1): icmp_req=11 ttl=64 time=1.29 ms


May 26 04:39:42 localhost kernel: [   84.720009] ------------[ cut here ]------------
May 26 04:39:42 localhost kernel: [   84.720017] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x108/0x17c()
May 26 04:39:42 localhost kernel: [   84.720020] Hardware name: P5Q-E
May 26 04:39:42 localhost kernel: [   84.720022] NETDEV WATCHDOG: eth0 (skge): transmit queue 0 timed out
May 26 04:39:42 localhost kernel: [   84.720024] Modules linked in: xt_limit nf_conntrack_ftp nf_conntrack_irc ip6table_mangle nfnetlink ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle ipt_ULOG cpufreq_ondemand sunrpc acpi_cpufreq freq_table mperf bridge stp llc sit tunnel4 bonding coretemp adt7475 hwmon_vid snd_hda_codec_analog arc4 snd_hda_intel ath9k snd_hda_codec mac80211 ath9k_common ath9k_hw snd_hwdep ath snd_seq snd_seq_device snd_pcm cfg80211 snd_timer rfkill sky2 snd soundcore microcode asus_atk0110 snd_page_alloc skge i2c_i801 e1000e iTCO_wdt iTCO_vendor_support virtio_net kvm_intel kvm ipv6 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 firewire_ohci firewire_core pata_acpi ata_generic crc_itu_t sata_mv pata_marvell nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
May 26 04:39:42 localhost kernel: [   84.720088] Pid: 0, comm: swapper Not tainted 2.6.38.6-27.fc15.x86_64 #1
May 26 04:39:42 localhost kernel: [   84.720090] Call Trace:
May 26 04:39:42 localhost kernel: [   84.720092]  <IRQ>  [<ffffffff8105510e>] warn_slowpath_common+0x83/0x9b
May 26 04:39:42 localhost kernel: [   84.720100]  [<ffffffff810551c9>] warn_slowpath_fmt+0x46/0x48
May 26 04:39:42 localhost kernel: [   84.720104]  [<ffffffff813db4c5>] ? netif_tx_lock+0x4a/0x7c
May 26 04:39:42 localhost kernel: [   84.720108]  [<ffffffff813db653>] dev_watchdog+0x108/0x17c
May 26 04:39:42 localhost kernel: [   84.720112]  [<ffffffff8105b255>] ? raise_softirq+0x2e/0x35
May 26 04:39:42 localhost kernel: [   84.720116]  [<ffffffff8106131c>] run_timer_softirq+0x1a4/0x266
May 26 04:39:42 localhost kernel: [   84.720120]  [<ffffffff81010150>] ? sched_clock+0x9/0xd
May 26 04:39:42 localhost kernel: [   84.720123]  [<ffffffff813db54b>] ? dev_watchdog+0x0/0x17c
May 26 04:39:42 localhost kernel: [   84.720127]  [<ffffffff8105ae40>] __do_softirq+0xd2/0x19d
May 26 04:39:42 localhost kernel: [   84.720131]  [<ffffffff8100fc99>] ? paravirt_read_tsc+0x9/0xd
May 26 04:39:42 localhost kernel: [   84.720134]  [<ffffffff81010150>] ? sched_clock+0x9/0xd
May 26 04:39:42 localhost kernel: [   84.720138]  [<ffffffff8100aadc>] call_softirq+0x1c/0x30
May 26 04:39:42 localhost kernel: [   84.720141]  [<ffffffff8100c101>] do_softirq+0x46/0x81
May 26 04:39:42 localhost kernel: [   84.720145]  [<ffffffff8105afc4>] irq_exit+0x49/0x8b
May 26 04:39:42 localhost kernel: [   84.720149]  [<ffffffff8147bf5b>] smp_apic_timer_interrupt+0x7e/0x8c
May 26 04:39:42 localhost kernel: [   84.720153]  [<ffffffff8100a593>] apic_timer_interrupt+0x13/0x20
May 26 04:39:42 localhost kernel: [   84.720155]  <EOI>  [<ffffffff81010ee4>] ? mwait_idle+0x92/0xbf
May 26 04:39:42 localhost kernel: [   84.720161]  [<ffffffff81010ed7>] ? mwait_idle+0x85/0xbf
May 26 04:39:42 localhost kernel: [   84.720165]  [<ffffffff81008321>] cpu_idle+0xa5/0xdf
May 26 04:39:42 localhost kernel: [   84.720169]  [<ffffffff81454d4e>] rest_init+0x72/0x74
May 26 04:39:42 localhost kernel: [   84.720173]  [<ffffffff81b58c2f>] start_kernel+0x3f2/0x3fe
May 26 04:39:42 localhost kernel: [   84.720177]  [<ffffffff81b582c4>] x86_64_start_reservations+0xaf/0xb3
May 26 04:39:42 localhost kernel: [   84.720180]  [<ffffffff81b58140>] ? early_idt_handler+0x0/0x71
May 26 04:39:42 localhost kernel: [   84.720183]  [<ffffffff81b583cf>] x86_64_start_kernel+0x107/0x116
May 26 04:39:42 localhost kernel: [   84.720186] ---[ end trace 0f7d795044deb99b ]---

Expected results:
no packet loss and no NETDEV WATCHDOG errors :P

Additional info: everything works fine when i boot back into the older fedora 14 kernels such as 2.6.35.13-91.fc14.x86_64 or 2.6.35.11-83.fc14.x86_64

Comment 1 redhat-bugzilla 2011-07-05 17:38:12 UTC
why has this not been looked into at all? its still happening in the latest kernel release (kernel-2.6.38.8-32.fc15.x86_64), fedora 15 should not have even been released with this bug, it is a total network blocker. this relates to bug #693442 which was put in before fedora 15 release, and the reports of it being only local connections is not correct. i have been forced to use my intel addon card for the time being...


07:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 14)
        Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet Controller (Asus)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (5750ns min, 7750ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at febec000 (32-bit, non-prefetchable) [size=16K]
        Region 1: I/O ports at e800 [size=256]
        Expansion ROM at febc0000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
                Product Name: Marvell Yukon 88E8001 Gigabit Ethernet Controller
                Read-only fields:
                        [PN] Part number: Yukon 88E8001
                        [EC] Engineering changes: Rev. 1.4
                        [MN] Manufacture ID: 4d 61 72 76 65 6c 6c
                        [SN] Serial number: AbCdEfG8DED4D
                        [CP] Extended capability: 01 10 cc 03
                        [RV] Reserved: checksum good, 9 byte(s) reserved
                Read/write fields:
                        [RW] Read-write area: 121 byte(s) free
                End
        Kernel driver in use: skge
        Kernel modules: skge

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
        Subsystem: ASUSTeK Computer Inc. Device 81f8
        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: 32 bytes
        Interrupt: pin A routed to IRQ 47
        Region 0: Memory at fe7fc000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at b800 [size=256]
        Expansion ROM at fe7c0000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
                Product Name: Marvell Yukon 88E8056 Gigabit Ethernet Controller
                Read-only fields:
                        [PN] Part number: Yukon 88E8056
                        [EC] Engineering changes: Rev. 1.2
                        [MN] Manufacture ID: 4d 61 72 76 65 6c 6c
                        [SN] Serial number: AbCdEfG8DE505
                        [CP] Extended capability: 01 10 cc 03
                        [RV] Reserved: checksum good, 9 byte(s) reserved
                Read/write fields:
                        [RW] Read-write area: 121 byte(s) free
                End
        Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee0100c  Data: 41a1
        Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 unlimited
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 1f, GenCap- CGenEn- ChkCap- ChkEn-
        Kernel driver in use: sky2
        Kernel modules: sky2

Comment 2 Dave Jones 2011-09-22 18:28:20 UTC
*** Bug 740619 has been marked as a duplicate of this bug. ***

Comment 3 Josh Boyer 2012-06-06 13:11:08 UTC
Is this still happening with the 2.6.43/3.3 kernel updates in F15/F16?

Comment 4 Josh Boyer 2012-07-11 17:52:34 UTC
Fedora 15 has reached it's end of life as of June 26, 2012.  As a result, we will not be fixing any remaining bugs found in Fedora 15.

In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with.  Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered.

Thank you for taking the time to file a report.  We hope newer versions of Fedora suit your needs.


Note You need to log in before you can comment on or make changes to this bug.