b44 transmit timeout with kernel 2.6

[Norbert Preining]

Dear Pekka, dear developers!

Some time ago I reported problems with transmit timeouts with b44 and
kernel 2.4 (http://lkml.org/lkml/2003/9/1/197 and followin discussion).

Now I have very similar problems with kernel 2.6:
Aug  2 09:53:15 gandalf vmunix: b44: eth0: Link is up at 100 Mbps, full duplex.
Aug  2 09:53:15 gandalf vmunix: b44: eth0: Flow control is off for TX and off for RX.
Aug  2 09:53:15 gandalf ifplugd(eth0)[3291]: Link beat detected.
Aug  2 09:53:20 gandalf dnsmasq[3005]: reading /var/run/dnsmasq/resolv.conf
Aug  2 09:53:20 gandalf dnsmasq[3005]: using nameserver 193.205.4.2#53
Aug  2 09:53:20 gandalf dnsmasq[3005]: using nameserver 193.205.4.11#53
Aug  2 09:53:25 gandalf vmunix: NETDEV WATCHDOG: eth0: transmit timed out
Aug  2 09:53:25 gandalf vmunix: b44: eth0: transmit timed out, resetting
Aug  2 09:53:26 gandalf kernel: b44: eth0: Link is down.
Aug  2 09:53:26 gandalf ifplugd(eth0)[3291]: Link beat lost.
Aug  2 09:53:28 gandalf vmunix: b44: eth0: Link is up at 100 Mbps, full duplex.
Aug  2 09:53:28 gandalf vmunix: b44: eth0: Flow control is off for TX and off for RX.

and wanted to ask what I can do to overcome this problems again.

Currently I am running 2.6.13-rc4-mm1 on an acer travelmate 654LCi.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining AT logic DOT at>             Università di Siena
sip:preining@xxxxxxxxxxxxxxxxx                             +43 (0) 59966-690018
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
`I am so amazingly cool you could keep a side of meat in
me for a month. I am so hip I have difficulty seeing over
my pelvis.'
                 --- Zaphod being cool.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/