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: Mon, 1 Sep 2003 23:00:22 +0300 [thread overview]
Message-ID: <20030901200022.GA3070@ee.oulu.fi> (raw)
In-Reply-To: <20030901193235.GA8280@gamma.logic.tuwien.ac.at>
On Mon, Sep 01, 2003 at 09:32:35PM +0200, Norbert Preining wrote:
> Hi!
>
> I have the following problem since I switched from bcm4400 to the
> `in-kernel' driver b44:
> Sep 1 17:37:11 gandalf vmunix: b44: eth0: Link is up at 10 Mbps, half duplex.
> Sep 1 17:37:11 gandalf vmunix: b44: eth0: Flow control is off for TX and off for RX.
> Sep 1 17:37:16 gandalf vmunix: NETDEV WATCHDOG: eth0: transmit timed out
> Sep 1 17:37:16 gandalf vmunix: b44: eth0: transmit timed out, resetting
> Sep 1 17:37:17 gandalf vmunix: b44: eth0: Link is down.
> Sep 1 17:37:20 gandalf vmunix: b44: eth0: Link is up at 10 Mbps, half duplex.
> Sep 1 17:37:20 gandalf vmunix: b44: eth0: Flow control is off for TX and off for RX.
>
> and so on. This didn't (and still does not) happen with the bcm4400
> (from debian sid bcm4400-source).
>
> I compiled the kernel myself on debian/sid, it is a laptop (acer tm654).
>
> If you need more information I will provide all I can do.
Argh, I had hoped the driver was BugFree (tm)!
Could you try adding some debug printk's to b44_tx and b44_start_xmit
say something like:
in b44_tx()
for (cons = bp->tx_cons; cons != cur; cons = NEXT_TX(cons)) {
struct ring_info *rp = &bp->tx_buffers[cons];
struct sk_buff *skb = rp->skb;
+ printk(KERN_DEBUG "b44_tx cons: %d cur: %d skb: %p\n",cons,cur,skb);
and in b44_start_xmit something like:
bp->tx_ring[entry].addr = cpu_to_le32((u32) mapping+bp->dma_offset);
+ printk(KERN_DEBUG "b44_start_xmit ctrl: %x addr: %p entry: %d skb: %p",bp->tx_ring[entry].ctrl,bp->tx_ring[entry].addr,entry,skb);
(that should hopefully be enough to see what's happening)
Also setting B44_FLAG_BUGGY_TXPTR and B44_FLAG_REORDER_BUG in
b44_get_invariants() might be worth a shot. I'm not sure where those
flags came from, my A7V8X works fine without them and bcm4400 doesn't have
that stuff either.
next prev parent reply other threads:[~2003-09-01 20:00 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 [this message]
2003-09-02 7:33 ` Norbert Preining
2003-09-02 8:31 ` Pekka Pietikainen
-- 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=20030901200022.GA3070@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.