On Thu, 2005-06-23 at 12:34 -0400, Dan Williams wrote:
> Netapplet doesn't have problems because it doesn't talk to the card
> much, it just does a few iwconfigs and some scanning. NetworkManager is
> touching the card quite a bit, in regular intervals, and probably
> exposes more bugs in drivers because nobody's really automated wireless
> stuff like this before in Linux.
It seems to only happen with encrypted networks.
> I hear you've got a little bit of kernel experience here and there, want
> to take a look at the driver? :)
I have this rule: No Drivers.
But maybe I should take a look ... :)
> When I was looking at it, what I described was more or less the sequence
> of events. The card gets wedged for some reason, but the driver keeps
> sending the card packets for a bit. Each packet that the kernel network
> layer adds to the outgoing tx queue, it increments the module's
> refcount. Since the card never can send those packets, the refcount
> never gets decreased. I've seen the usage counts as high as 21 or 22
> before.
>
> I have no idea what gets the card into this state, it seems to be fairly
> random how long it takes. See issuecommand() in airo.c where the error
> comes from. The CLEARCOMMANDBUSY stuff doesn't seem to unwedge the
> card.
This is a great start!
Robert Love
_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list
