From: Tuomas Vainikka <tuomas.vainikka@aalto.fi>
To: Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: watchdog (?) on linux 3.0.0 and 2.6.39.3
Date: Mon, 1 Aug 2011 15:12:36 +0300 [thread overview]
Message-ID: <4E369834.9070707@aalto.fi> (raw)
Hello,
This happens with both stable 3.0.0 and 2.6.39.3 kernels:
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x1a4/0x1c4()
NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
Modules linked in: nfsd exportfs ipv6 gayle parport_amiga amiflop
dmasound_paula ide_core parport dmasound_core amimouse soundcore
Call Trace: [<0001c134>] warn_slowpath_common+0x48/0x6a
[<0001c142>] warn_slowpath_common+0x56/0x6a
[<0001c1ce>] warn_slowpath_fmt+0x2a/0x32
[<001cbff6>] dev_watchdog+0x1a4/0x1c4
[<001cbff6>] dev_watchdog+0x1a4/0x1c4
[<00025b9c>] run_timer_softirq+0xce/0x224
[<0000ffff>] _060_fpsp_effadd+0x83e3/0xd518
[<00044424>] rcu_bh_qs+0x0/0x2e
[<0023eb90>] printk+0x0/0x18
[<000208fc>] __do_softirq+0x88/0xc8
[<002406b4>] schedule+0x0/0x34e
[<00020a0c>] do_softirq+0x28/0x2c
[<000025f0>] ret_from_exception+0x0/0xc
[<00002892>] default_idle+0x0/0xc
[<000028e2>] cpu_idle+0x16/0x20
[<0023eb90>] printk+0x0/0x18
[<002fefd0>] start_kernel+0x33a/0x348
[<0000f9a2>] _060_fpsp_effadd+0x7d86/0xd518
[<0000f9a2>] _060_fpsp_effadd+0x7d86/0xd518
[<002fe2fc>] _sinittext+0x2fc/0x988
---[ end trace 9649de43a8c19796 ]---
The message above comes only once.
Then, there's a lot of these:
eth0: Tx timed out, lost interrupt? TSR=0x4, ISR=0x15, t=52.
eth0: Tx timed out, lost interrupt? TSR=0x5, ISR=0x3, t=33.
eth0: Tx timed out, lost interrupt? TSR=0x5, ISR=0x3, t=36.
but the PCMCIA network card of mine can also be flakey.
Both kernels have been cross-compiled with gcc 4.6.1.
I'll be happy to provide you with the kernel config and the full dmesg
output if you need them.
Regards,
Tuomas
next reply other threads:[~2011-08-01 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:12 Tuomas Vainikka [this message]
2011-08-01 19:03 ` watchdog (?) on linux 3.0.0 and 2.6.39.3 Geert Uytterhoeven
2011-08-02 5:33 ` Finn Thain
2011-08-04 16:59 ` Tuomas Vainikka
2011-08-04 20:45 ` Michael Schmitz
2011-08-05 2:44 ` Finn Thain
2011-08-05 11:53 ` Tuomas Vainikka
2011-08-05 22:32 ` Michael Schmitz
2011-08-06 9:56 ` Geert Uytterhoeven
2011-08-07 20:01 ` Michael Schmitz
2011-08-07 22:07 ` Christian T. Steigies
2011-08-08 0:23 ` Michael Schmitz
2011-08-08 10:52 ` Tuomas Vainikka
2011-08-14 4:26 ` Michael Schmitz
2011-08-14 8:29 ` Geert Uytterhoeven
2011-08-14 20:40 ` Michael Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E369834.9070707@aalto.fi \
--to=tuomas.vainikka@aalto.fi \
--cc=linux-m68k@lists.linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox