Date: Wed, 31 May 2006 17:53:23 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org, thierry@herbelot.com Subject: Re: [PATCH] if_dc cleanups.. Message-ID: <200605311753.23976.jhb@freebsd.org> In-Reply-To: <200605271830.50724.thierry@herbelot.com> References: <200605241556.44483.jhb@freebsd.org> <200605251023.34963.thierry@herbelot.com> <200605271830.50724.thierry@herbelot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 27 May 2006 12:30, Thierry Herbelot wrote: > Le Thursday 25 May 2006 10:23, Thierry Herbelot a =E9crit : >=20 > > my dc is still probed and detected with your patch : > > dc0: <82c169 PNIC 10/100BaseTX> port 0x9400-0x94ff mem > > 0xd8000000-0xd80000ff irq 19 at device 9.0 on pci0 > > dc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x9400 > > miibus0: <MII bus> on dc0 > > bmtphy0: <BCM5201 10/100baseTX PHY> on miibus0 > > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > dc0: bpf attached > > dc0: Ethernet address: 00:02:e3:08:63:af > > dc0: [MPSAFE] > > > > the same dc is currently used to update the -current sources over NFS, > > without any visible side effects. >=20 > one side effect seems to be more watchdog timeouts : >=20 > dc0: watchdog timeout > dc0: failed to force tx and rx to idle state >=20 > on a macroscopic level, the NIC is still usable (enough to get a cvs upda= te=20 of=20 > the full world from an NFS repository). It shouldn't have affect the operation of the device at all. Do the probe= =20 messages in dmesg match the dmesg lines w/o the patch exactly? Do you have= =20 before and after dmesg's that I can compare? =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605311753.23976.jhb>