From: Arjan van de Ven <arjan@infradead.org>
To: Komuro <komurojun-mbn@nifty.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: wifi0: transmit timed out
Date: Wed, 30 Jul 2008 06:22:20 -0700 [thread overview]
Message-ID: <20080730062220.08b2779a@infradead.org> (raw)
In-Reply-To: <16453842.205951217418535898.komurojun-mbn@nifty.com>
On Wed, 30 Jul 2008 20:48:55 +0900 (JST)
Komuro <komurojun-mbn@nifty.com> wrote:
>
> >
> >"I have a hardware failure so I'll comment out the message that says
> >so, and then I won't have a failure". Yeah that'll work well.
>
>
> O.K. The madwifi should be fixed.
> Thanks,
madwifi has many bigger issues; it's been number 1 in the kerneloops
top 10 for months and months now.
Feel free to fix it.. I can't.. it's a proprietary/binary driver.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-07-30 13:22 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 ` NETDEV WATCHDOG: wifi0: transmit timed out Komuro
2008-07-29 13:43 ` 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 [this message]
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=20080730062220.08b2779a@infradead.org \
--to=arjan@infradead.org \
--cc=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;
as well as URLs for NNTP newsgroup(s).