From: Komuro <komurojun-mbn@nifty.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: RE: NETDEV WATCHDOG: wifi0: transmit timed out
Date: Tue, 29 Jul 2008 21:53:15 +0900 [thread overview]
Message-ID: <20080729215315.5a505fe7.komurojun-mbn@nifty.com> (raw)
In-Reply-To: <20080525112308.03a5fda7.komurojun-mbn@nifty.com>
Hi,
Please try to comment out the "WARN_ON_ONCE"
at net/sched/sched_generic.c.
--- linux-2.6.27-rc1/net/sched/sch_generic.c.orig 2008-07-29 21:45:36.000000000 +0900
+++ linux-2.6.27-rc1/net/sched/sch_generic.c 2008-07-29 21:45:54.000000000 +0900
@@ -216,7 +216,6 @@ static void dev_watchdog(unsigned long a
printk(KERN_INFO "NETDEV WATCHDOG: %s (%s): transmit timed out\n",
dev->name, netdev_drivername(dev, drivername, 64));
dev->tx_timeout(dev);
- WARN_ON_ONCE(1);
}
if (!mod_timer(&dev->watchdog_timer,
round_jiffies(jiffies +
>I should'nt be posting this, due to
>having tainted modules(madwifi), but
>I figured I might as well:(below)
>
>[ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
>[ 5000.991959] ------------[ cut here ]------------
>[ 5000.991964] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x95/0xe7()
Best Regards
Komuro
next prev parent reply other threads:[~2008-07-29 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 2:23 [PLEASE REVERT] "Add a WARN_ON_ONCE" at net/sched/sch_generic.c: Komuro
2008-05-25 12:10 ` David Miller
2008-05-27 12:34 ` Komuro
2008-05-27 13:14 ` David Miller
2008-07-29 12:53 ` Komuro [this message]
2008-07-29 13:43 ` NETDEV WATCHDOG: wifi0: transmit timed out Justin Mattock
2008-07-29 13:58 ` Arjan van de Ven
2008-07-29 20:47 ` David Miller
2008-07-29 22:48 ` Justin Mattock
2008-07-30 11:41 ` Dan Williams
2008-07-30 11:48 ` Komuro
2008-07-30 13:22 ` Arjan van de Ven
2008-07-30 14:55 ` Justin Mattock
2008-07-28 7:10 Justin Mattock
2008-07-28 13:12 ` Arjan van de Ven
2008-07-28 13:53 ` Justin Mattock
2008-07-28 15:22 ` Alistair John Strachan
2008-07-28 17:27 ` Justin Mattock
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=20080729215315.5a505fe7.komurojun-mbn@nifty.com \
--to=komurojun-mbn@nifty.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®