[lkml]   [2003]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: 2.4, b44 transmit timeout
On Mon, Sep 08, 2003 at 11:34:17AM +0200, Jan De Luyck wrote:
> On Tue, Sep 02, 2003 at 09:33:53AM +0200, Norbert Preining wrote:
> > A-ha! Thanks, I think this should be enough to figure out what the problem
> > is... Looks like the driver doesn't even get the packets pump tries to send,
> > pump is a bit special in the way it bounces the interface up and down when
> > doing its work, that probably triggers a race in b44..
> I can also easily recreate this by calling dhcpcd e.g. when the cable isn't in
> the socket yet. If i attach the cable then I see the interface coming up,
> going down, and then the NETDEV watchdog message.
> Unfortunatly this usually means that dhcpcd goes hanging. ifconfig hangs too
> if I try to use it, and rebooting must be forced with sysrq and an oops a
> alt-sysrq-o for poweroff...
This could help (tm) :-)

--- b44.c.orig 2003-09-28 19:36:48.000000000 +0300
+++ b44.c 2003-09-28 19:37:07.000000000 +0300
@@ -870,6 +870,7 @@


+ b44_enable_ints(bp);

at least I could do some pretty dirty things to the poor chip and it still
seems to recover after this patch.
rmmod still has some problems, occasionally I get a "usage count 2" thing
(currently running the rawhide 2.4.22-1.2061.nptl, I've seen similar with
2.6.0-test5ish too, I suspect ipv6 might be involved, but sometimes I can rmmod
it even with ipv6 loaded so it's a bit random).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:48    [W:0.048 / U:5.472 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site