Re: Net watchdog triggering on r8169

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Michael Buesch
Date: Thursday, March 19, 2009 - 10:35 am

On Saturday 21 February 2009 16:25:55 Michael Buesch wrote:


It happened again. But b43 was _not_ running this time. So it clearly is r8169's fault.

Is this simply due to r8169 being cheap-ass hardware, or could this
be a real driver bug?


[528699.780019] ------------[ cut here ]------------
[528699.780059] WARNING: at net/sched/sch_generic.c:226 dev_watchdog+0x22e/0x240
()
[528699.780095] NETDEV WATCHDOG: eth0 (r8169): transmit timed out
[528699.780118] Modules linked in: b43 ssb mac80211 cfg80211
[528699.780154] Pid: 0, comm: swapper Tainted: G        W  2.6.28.7 #9
[528699.780178] Call Trace:
[528699.780196]  <IRQ>  [<ffffffff80240aed>] warn_slowpath+0xcd/0x110
[528699.780231]  [<ffffffff806c7372>] ipt_do_table+0x242/0x5c0
[528699.780256]  [<ffffffff8023778c>] find_busiest_group+0x1dc/0x970
[528699.780282]  [<ffffffff80236ca8>] enqueue_task_fair+0x178/0x180
[528699.780309]  [<ffffffff80235042>] activate_task+0x22/0x30
[528699.780335]  [<ffffffff8024b904>] lock_timer_base+0x34/0x70
[528699.780360]  [<ffffffff8024baea>] __mod_timer+0xaa/0xc0
[528699.780385]  [<ffffffff8025d838>] getnstimeofday+0x58/0xe0
[528699.780412]  [<ffffffff8040ba61>] strlcpy+0x41/0x50
[528699.780436]  [<ffffffff80629dfe>] dev_watchdog+0x22e/0x240
[528699.780461]  [<ffffffff8023dba2>] scheduler_tick+0xd2/0x230
[528699.780486]  [<ffffffff80629bd0>] dev_watchdog+0x0/0x240
[528699.780511]  [<ffffffff8024b1ee>] run_timer_softirq+0x12e/0x200
[528699.780536]  [<ffffffff8025acfc>] ktime_get+0xc/0x50
[528699.780561]  [<ffffffff80246833>] __do_softirq+0x93/0x160
[528699.780586]  [<ffffffff8020d49c>] call_softirq+0x1c/0x30
[528699.780611]  [<ffffffff8020ee45>] do_softirq+0x35/0x70
[528699.780635]  [<ffffffff80246525>] irq_exit+0x95/0xa0
[528699.780660]  [<ffffffff802200b6>] smp_apic_timer_interrupt+0x86/0xd0
[528699.780687]  [<ffffffff8020ceeb>] apic_timer_interrupt+0x6b/0x70
[528699.780710]  <EOI>  [<ffffffff8021f7e0>] lapic_next_event+0x0/0x20
[528699.780743]  [<ffffffff8021468c>] mwait_idle+0x3c/0x50
[528699.780767]  [<ffffffff8020b34e>] cpu_idle+0x5e/0xb0
[528699.780789] ---[ end trace 7be3855cebbcf43d ]---
[528699.798309] r8169: eth0: link up
[531183.797758] r8169: eth0: link up
[539655.802759] r8169: eth0: link up

mb@quimby:~$ uname -a
Linux quimby 2.6.28.7 #9 SMP Fri Mar 13 12:32:49 CET 2009 x86_64 GNU/Linux


-- 
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Net watchdog triggering on r8169, Michael Buesch, (Sat Feb 21, 8:25 am)
Re: Net watchdog triggering on r8169, Michael Buesch, (Thu Mar 19, 10:35 am)
Re: Net watchdog triggering on r8169, Francois Romieu, (Thu Mar 19, 3:27 pm)
Re: Net watchdog triggering on r8169, Michael Buesch, (Fri Mar 20, 1:04 pm)