RE: Very weird problem with dc driver

From: Niels Piersma (niels_at_piersma.com)
Date: 12/25/03

Next message: David Malone: "Re: Very weird problem with dc driver"

Previous message: Shawn K. Quinn: "Very weird problem with dc driver"
Maybe in reply to: Shawn K. Quinn: "Very weird problem with dc driver"
Next in thread: David Malone: "Re: Very weird problem with dc driver"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Thu, 25 Dec 2003 09:24:28 +0100
To: "Shawn K. Quinn" <skquinn@xevious.kicks-ass.net>, <stable@freebsd.org>

Shawn,

I think this could be a speed miss-match on you switch. See if you can use
a fixed speed. You can configure your switch for a fixed speed (preferred)
or you can use the interface options in the rc.conf line.

Take care,

Niels

-----Original Message-----
From: owner-freebsd-stable@freebsd.org
[mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Shawn K. Quinn
Sent: donderdag 25 december 2003 8:38
To: stable@freebsd.org
Subject: Very weird problem with dc driver

Is this a bad network card or a bug in the dc driver?

Dec 24 23:12:32 xevious /kernel: dc0: <82c169 PNIC 10/100BaseTX> port
0xc400-0xc4ff mem 0xeffef700-0xeffef7ff irq 9 at device 14.0 on pci0
Dec 24 23:12:32 xevious /kernel: dc0: Ethernet address:
00:a0:c4:27:c4:27
Dec 24 23:12:32 xevious /kernel: miibus0: <MII bus> on dc0
Dec 24 23:12:32 xevious /kernel: ukphy0: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy0: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:12:32 xevious /kernel: ukphy1: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy1: no media present
Dec 24 23:12:32 xevious /kernel: ukphy2: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy2: no media present
Dec 24 23:12:32 xevious /kernel: ukphy3: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy3: no media present
Dec 24 23:12:32 xevious /kernel: ukphy4: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy4: no media present
Dec 24 23:12:32 xevious /kernel: ukphy5: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy5: no media present
Dec 24 23:12:32 xevious /kernel: ukphy6: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy6: no media present
Dec 24 23:12:32 xevious /kernel: ukphy7: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy7: no media present
Dec 24 23:12:32 xevious /kernel: ukphy8: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy8: no media present
Dec 24 23:12:32 xevious /kernel: ukphy9: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy9: no media present
Dec 24 23:12:32 xevious /kernel: ukphy10: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy10: no media present
Dec 24 23:12:32 xevious /kernel: ukphy11: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy11: no media present
Dec 24 23:12:32 xevious /kernel: ukphy12: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy12: no media present
Dec 24 23:12:32 xevious /kernel: ukphy13: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy13: no media present
Dec 24 23:12:32 xevious /kernel: ukphy14: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:12:32 xevious /kernel: ukphy14: no media present

And then later...

Dec 24 23:18:10 xevious /kernel: dc0: <82c169 PNIC 10/100BaseTX> port
0xc000-0xc0ff mem 0xeffef700-0xeffef7ff irq 9 at device 14.0 on pci0
Dec 24 23:18:10 xevious /kernel: dc0: Ethernet address:
00:00:00:a0:00:a0
Dec 24 23:18:10 xevious /kernel: miibus0: <MII bus> on dc0
Dec 24 23:18:10 xevious /kernel: ukphy0: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy0: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy1: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy1: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy2: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy2: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy3: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy3: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy4: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy4: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy5: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy5: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy6: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy6: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy7: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy7: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy8: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy8: no media present
Dec 24 23:18:10 xevious /kernel: ukphy9: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy9: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy10: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy10: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy11: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy11: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy12: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy12: no media present
Dec 24 23:18:10 xevious /kernel: ukphy13: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy13: no media present
Dec 24 23:18:10 xevious /kernel: ukphy14: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy14: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy15: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy15: 10baseT-FDX, 100baseTX,
100baseTX-FDX, 100baseT4, auto
Dec 24 23:18:10 xevious /kernel: ukphy16: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy16: no media present
Dec 24 23:18:10 xevious /kernel: ukphy17: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy17: no media present
Dec 24 23:18:10 xevious /kernel: ukphy18: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy18: no media present
Dec 24 23:18:10 xevious /kernel: ukphy19: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy19: no media present
Dec 24 23:18:10 xevious /kernel: ukphy20: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy20: no media present
Dec 24 23:18:10 xevious /kernel: ukphy21: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy21: no media present
Dec 24 23:18:10 xevious /kernel: ukphy22: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy22: no media present
Dec 24 23:18:10 xevious /kernel: ukphy23: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy23: no media present
Dec 24 23:18:10 xevious /kernel: ukphy24: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy24: no media present
Dec 24 23:18:10 xevious /kernel: ukphy25: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy25: no media present
Dec 24 23:18:10 xevious /kernel: ukphy26: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy26: no media present
Dec 24 23:18:10 xevious /kernel: ukphy27: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:18:10 xevious /kernel: ukphy27: no media present

A power-off/power-on reboot fixed this, then it returned, then another
power-off/power-on reboot fixed it which is where I stand when I write
this.

Oh, I also found this little gem after the first power-off/power-on
reboot:

Dec 25 00:32:58 xevious /kernel: dc0: TX underrun -- increasing TX
threshold

And this is what the "normal" boots I've managed to pull off look like:

Dec 24 23:44:00 xevious /kernel: dc0: <82c169 PNIC 10/100BaseTX> port
0xc000-0xc0ff mem 0xeffeff00-0xeffeffff irq 9 at device 14.0 on pci0
Dec 24 23:44:00 xevious /kernel: dc0: Ethernet address:
00:a0:cc:27:4b:6b
Dec 24 23:44:00 xevious /kernel: miibus0: <MII bus> on dc0
Dec 24 23:44:00 xevious /kernel: ukphy0: <Generic IEEE 802.3u media
interface> on miibus0
Dec 24 23:44:00 xevious /kernel: ukphy0: 10baseT, 10baseT-FDX,
100baseTX, 100baseTX-FDX, auto

--
Shawn K. Quinn
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

application/x-pkcs7-signature attachment: smime.p7s

Next message: David Malone: "Re: Very weird problem with dc driver"

Previous message: Shawn K. Quinn: "Very weird problem with dc driver"
Maybe in reply to: Shawn K. Quinn: "Very weird problem with dc driver"
Next in thread: David Malone: "Re: Very weird problem with dc driver"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

5.5-stable network interface rl0 stops working
... interface on the maschine, rl1 is for backups/internal use only) stops ... traffic for the services in that specific jail. ... <ACPI PCI bus> on pcib0 ... on miibus0 ...
(freebsd-stable)
Re: [fw-wiz] PIX 515E 7.2 Duplex problem
... The switch it connects to is configured for full duplex but the ... PIX still shows half duplex when in auto negotiate mode. ... half duplex on both the switch and PIX works but the PIX interface ...
(Firewall-Wizards)
autoneg on e1000g0 in Solaris 10
... e1000g0 is not able to auto-negotiate. ... Switch has set to auto for both ... while the other interface e1000g1 is running as 1000mbps. ...
(comp.unix.solaris)
1801 VPN multiple clients
... interface FastEthernet0 ... duplex auto ... switchport trunk allowed vlan 1,2,1002-1005 ... deny ip x.x.x.x 0.0.0.15 any ...
(comp.dcom.sys.cisco)
837 dialin - getting assigned DNS addresses - TWICE!
... interface ATM0 ... dsl operating-mode auto ... ip nat inside source list 102 interface Dialer1 overload ...
(comp.dcom.sys.cisco)