From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: 2.4, b44 transmit timeout
Date: Tue, 2 Sep 2003 11:31:07 +0300 [thread overview]
Message-ID: <20030902083107.GA4065@ee.oulu.fi> (raw)
In-Reply-To: <20030902073353.GA935@gamma.logic.tuwien.ac.at>
On Tue, Sep 02, 2003 at 09:33:53AM +0200, Norbert Preining wrote:
> * pinging the gateway (.1.1), working
> Sep 2 09:20:22 gandalf vmunix: b44_start_xmit ctrl: e000002a addr: 5cea5d82 entry: 0 skb: d935b480
> Sep 2 09:20:22 gandalf vmunix: b44_tx cons: 0 cur: 1 skb: d935b480
> Sep 2 09:20:22 gandalf vmunix: b44_start_xmit ctrl: e0000062 addr: 5f982982 entry: 1 skb: d935b680
> Sep 2 09:20:22 gandalf vmunix: b44_tx cons: 1 cur: 2 skb: d935b680
> Sep 2 09:20:23 gandalf vmunix: b44_start_xmit ctrl: e0000062 addr: 5f982682 entry: 2 skb: d935b480
> Sep 2 09:20:23 gandalf vmunix: b44_tx cons: 2 cur: 3 skb: d935b480
> Sep 2 09:20:24 gandalf vmunix: b44_start_xmit ctrl: e0000062 addr: 5f982682 entry: 3 skb: d935b480
> Sep 2 09:20:24 gandalf vmunix: b44_tx cons: 3 cur: 4 skb: d935b480
> Sep 2 09:20:25 gandalf vmunix: b44_start_xmit ctrl: e0000062 addr: 5f982982 entry: 4 skb: d935b480
> Sep 2 09:20:25 gandalf vmunix: b44_tx cons: 4 cur: 5 skb: d935b480
> Sep 2 09:20:26 gandalf vmunix: b44_start_xmit ctrl: e0000062 addr: 5f982682 entry: 5 skb: d935b480
> Sep 2 09:20:26 gandalf vmunix: b44_tx cons: 5 cur: 6 skb: d935b480
> Sep 2 09:20:27 gandalf vmunix: b44_start_xmit ctrl: e000002a addr: 5cea5082 entry: 6 skb: d935ba80
> Sep 2 09:20:27 gandalf vmunix: b44_tx cons: 6 cur: 7 skb: d935ba80
> Sep 2 09:20:27 gandalf kernel: b44_start_xmit ctrl: e0000062 addr: 5f982982 entry: 7 skb: d935ba80
> Sep 2 09:20:27 gandalf kernel: b44_tx cons: 7 cur: 8 skb: d935ba80
> Sep 2 09:20:28 gandalf kernel: b44_start_xmit ctrl: e0000062 addr: 5f982682 entry: 8 skb: d935b480
> Sep 2 09:20:28 gandalf kernel: b44_tx cons: 8 cur: 9 skb: d935b480
> Sep 2 09:20:29 gandalf kernel: b44_start_xmit ctrl: e0000062 addr: 5f982982 entry: 9 skb: d935b480
> Sep 2 09:20:29 gandalf kernel: b44_tx cons: 9 cur: 10 skb: d935b480
> * stopping ping, ifconfig eth0 down, starting pump for getting dhcp
> * address, no success!
> Sep 2 09:20:41 gandalf pumpd[7584]: starting at (uptime 0 days, 2:04:19) Tue Sep 2 09:20:41 2003
> Sep 2 09:20:41 gandalf pumpd[7584]: PUMP: sending discover
> Sep 2 09:20:44 gandalf vmunix: b44: eth0: Link is up at 100 Mbps, full duplex.
> Sep 2 09:20:44 gandalf vmunix: b44: eth0: Flow control is on for TX and on for RX.
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..
next prev parent reply other threads:[~2003-09-02 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 19:32 2.4, b44 transmit timeout Norbert Preining
2003-09-01 20:00 ` Pekka Pietikainen
2003-09-02 7:33 ` Norbert Preining
2003-09-02 8:31 ` Pekka Pietikainen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-08 9:34 Jan De Luyck
2003-09-09 22:13 ` Pekka Pietikainen
2003-09-28 16:48 ` 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=20030902083107.GA4065@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.