netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	arjan@infradead.org, komurojun-mbn@nifty.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: wifi0: transmit timed out
Date: Wed, 30 Jul 2008 07:41:30 -0400	[thread overview]
Message-ID: <1217418091.11432.24.camel@localhost.localdomain> (raw)
In-Reply-To: <dd18b0c30807291548u285bb00eqd376e0e96cede86c@mail.gmail.com>

On Tue, 2008-07-29 at 15:48 -0700, Justin Mattock wrote:
> On Tue, Jul 29, 2008 at 1:47 PM, David Miller <davem@davemloft.net> wrote:
> > From: Arjan van de Ven <arjan@infradead.org>
> > Date: Tue, 29 Jul 2008 06:58:59 -0700
> >
> >> On Tue, 29 Jul 2008 21:53:15 +0900
> >> Komuro <komurojun-mbn@nifty.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Please try to comment out the "WARN_ON_ONCE"
> >> > at net/sched/sched_generic.c.
> >> >
> >>
> >> "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.
> >
> > Yes, this is indeed a recidulious suggestion, to hide the problem
> > instead of trying to figure out what it might actually be.
> >
> > Komuro has a serious problem accepting the fact that this condition is
> > in fact an abnormal error should should be logged, and he keeps
> > pushing to get this WARN_ON() removed over and over again.
> >
> > I'm just ignoring him at this point.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
> 
> I should of mentioned the madwifi module I've been
> using is from february, so maybe madwifi took care of this already.
> As for experimanting with ath9k I pulled yesterday and compiled,
> but from what I saw ath9k seems to not handle wpa keys that well.
> so back to madwifi until later on.

ath9k certainly should handle WPA keys; the hardware and driver really
don't care what the key type is because all that is taken care of by
mac80211.  What specific issues were you having with ath9k?  There's
some generic mac80211 breakage going on right now while people figure
out how to fix the skb->cb situation that Dave's multiqueue stuff
exposed, which might be screwing up ath9k for you.

Dan



  reply	other threads:[~2008-07-30 11:44 UTC|newest]

Thread overview: 13+ 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 [this message]
2008-07-30 11:48   ` Komuro
2008-07-30 13:22     ` Arjan van de Ven
2008-07-30 14:55       ` 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=1217418091.11432.24.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=justinmattock@gmail.com \
    --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).