Hello
After upgrading a server from 2.4.23 to 2.4.24 (no changes to the driver code)
and rebooting it one of the network cards, a Broadcom on-board which
uses the b44.o driver, suddenly starts to loose connection for 3s every
couple of hours:
kernel: b44: eth0: Link is down.
kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
kernel: b44: eth0: Flow control is off for TX and off for
What I just realized was that
- the Cisco switch said:
Auto-duplex (Half), Auto Speed (100), 100BaseTX/FX
although ethtool showed
Supports auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: off
- when trying to alter the speed, duplex and autoneg values with
ethtool I got either no response and no visible change or this one
# ethtool -s eth0 autoneg on
Cannot update new settings: Invalid argument
Any ideas if the wrong duplex setting causes a link flappnig and why
autonegotiating does not work?
Moreover I think I remember that the interface error counters were all
zero when the link flaps started (they are no longer due to the duplex
problems).
bye,
-christian-
# lspci -v
02:05.0 Ethernet controller: BROADCOM Corporation: Unknown device 4401 (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 80a8
Flags: bus master, fast devsel, latency 32, IRQ 20
Memory at ed000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
--
Christian Hammers WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Lütticher Straße 10 Tel 0241/701333-11
ch@westend.com D-52064 Aachen Fax 0241/911879
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
