public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4, b44 transmit timeout
Date: Wed, 10 Sep 2003 01:13:49 +0300	[thread overview]
Message-ID: <20030909221349.GA22387@ee.oulu.fi> (raw)
In-Reply-To: <200309081134.17013.lkml@kcore.org>

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...
Hi

(I was quite far away from civilization for a few days, which is why
I've been quiet on this topic for a while :-) )

Culd you try the patch Jeff Garzik posted as a fix for tg3 
ifconfig down/up problems, I believe it fixes the same problem since
it's a generic thing with NAP

What I believe should happen after applying this patch is that the
b44 driver shouldn't hang as a result of doing tricks like the ones
mentioned. pump might not work even with it (If I understood correctly,
(pump & tg3 don't mix well either due to pump having some wrong assumptions
on when it can send packets). dhcpcd definately should work though.



--- SNIP --
Note that people seeing "ifconfig down ... ifconfig up" problems need to
apply this patch.  (to 2.4.23-pre, too)
                                                                                
        Jeff
                                                                                
                                                                                
                                                                                
[-- Attachment #2: patch --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.5K --]
                                                                                
diff -Nru a/net/core/dev.c b/net/core/dev.c
--- a/net/core/dev.c    Mon Sep  8 18:14:36 2003
+++ b/net/core/dev.c    Mon Sep  8 18:14:36 2003
@@ -851,7 +851,11 @@
         * engine, but this requires more changes in devices. */
                                                                                
        smp_mb__after_clear_bit(); /* Commit netif_running(). */
-       netif_poll_disable(dev);
+       while (test_bit(__LINK_STATE_RX_SCHED, &dev->state)) {
+               /* No hurry. */
+               current->state = TASK_INTERRUPTIBLE;
+               schedule_timeout(1);
+       }

-- SNIP --



  reply	other threads:[~2003-09-09 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08  9:34 2.4, b44 transmit timeout Jan De Luyck
2003-09-09 22:13 ` Pekka Pietikainen [this message]
2003-09-28 16:48 ` Pekka Pietikainen
  -- strict thread matches above, loose matches on Subject: below --
2003-09-01 19:32 Norbert Preining
2003-09-01 20:00 ` Pekka Pietikainen
2003-09-02  7:33   ` Norbert Preining
2003-09-02  8:31     ` Pekka Pietikainen

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=20030909221349.GA22387@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.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