Date: Wed, 30 May 2001 01:02:17 -0700 From: scanner@apricot.com To: stable@freebsd.org Subject: problems with the new fxp(4) driver.. Message-ID: <200105300802.f4U82Hn06027@matsubue.apricot.com>
next in thread | raw e-mail | index | archive | help
Hello,
I recently ran into a very annoying situation where I upgraded from
a May 8th copy of 4.3-stable to a May 26th version of stable.
The problem was that my ethernet adapter that is on my MB started
flipping out.
Depending on the amount of traffic (and it would not take much)
the system would soon become unuseable and need a reboot. To the order
of over 12 times in a 8 hour period.
Basically you would start seeing messages like:
fxp0: SCB timeout
on the console. Eventually you would get:
fxp0: device timeout
The motherboard is both an i815EEAAL and an i815EEA2.
On the May 8th 4.3-stable the device identifies as:
fxp0: <Intel PLC 10/100 Ethernet>
On the May 25th 4.3-stable it identifies as:
May 29 06:14:46 kamidake
/kernel: fxp0: <Intel Pro/100 Ethernet> port 0xdf00-0xdf3f mem \
0xff8fe000-0xff8fefff irq 11 at device 8.0 on pci1
/kernel: inphy0: <i82562ET 10/100 media interface> on miibus0
People I know have things like the intel i810E mb have no problems.
Theirs identifies as:
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xdf00-0xdf3f mem \
0xff700000-0xff7fffff,0xff8fe000-0xff8fefff irq 10 at device \
1.0 on pci1
inphy0: <i82555 10/100 media interface> on miibus0
So it looks like support for the i82562ET vs. the i82555 is broken
in some fashion under 4.3-stable.
Does anyone have any advice or recommendations, besides "do not use
those MB's". (And yes I have miibus defined.. otherwise I would never have gotten that "inphy0" line.)
--Scanner (scanner@apricot.com)
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?200105300802.f4U82Hn06027>