Date: Tue, 31 Oct 2000 15:53:09 -0500 From: Paul Magwene <paul.magwene@yale.edu> To: freebsd-stable@freebsd.org Subject: 'dc' device broken in -STABLE? Message-ID: <39FF3135.E6C316B5@yale.edu>
next in thread | raw e-mail | index | archive | help
Hi All,
I've been tracking -STABLE, rebuilding once every 1-2 weeks. This
afternoon I cvsup'ed, made world, and built a new kernel, all of which
went without hiccups.
However, at reboot one of my NIC's (Kingston KNE110TX) which previously
worked with the 'dc' device driver no longer is properly configured at
boot time.
Here's the relevant info from the offending dmesg:
FreeBSD 4.2-BETA #25: Tue Oct 31 14:41:23 EST 2000
pmagwene@sluggo:/usr/src/sys/compile/SLUGGO
<< SNIP >>
dc0: <82c169 PNIC 10/100BaseTX> irq 17 at device 16.0 on pci0
dc0: couldn't map ports/memory
device_probe_and_attach: dc0 attach returned 6
And here's the comparable info from a build a week ago:
FreeBSD 4.1.1-STABLE #24: Mon Oct 23 16:54:39 EDT 2000
pmagwene@sluggo:/usr/src/sys/compile/SLUGGO
<< SNIP >>
dc0: <82c169 PNIC 10/100BaseTX> port 0xb000-0xb0ff mem
0xfedfd800-0xfedfd8ff irq
17 at device 16.0 on pci0
dc0: Ethernet address: 00:c0:f0:59:04:f3
miibus0: <MII bus> on dc0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
I've sumbitted this as a bug report, but thought folks on this mailing
list might have some pointers/suggestions/ideas.
Thanks,
Paul
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39FF3135.E6C316B5>