i386/125195: fxp(4) driver failed to initialize device Intel 82801DB

[Francis Gendreau]

>Number:         125195
>Category:       i386
>Synopsis:       fxp(4) driver failed to initialize device Intel 82801DB
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 02 19:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Francis Gendreau
>Release:        RELENG_&_)
>Organization:
>Environment:
FreeBSD laptop 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:53 UTC 2008 root at logan.cse.buffalo.edu:/usr/obj/src/sys/GENERIC i386
>Description:
Hi everyone.

During the setup of my network's latest addition, an Asus M3000N M3N laptop, I encountered a severe problem regarding the fxp(4) driver. The system comes with an Intel 82801DB chipset that includes the 82801DB (ICH4) PRO/100 VM Network Connection.

To enable the different devices, I load the ipw(4) and snd_ich(4). The devices work fine but I keep having the following message:

ipw0: <Intel(R) PRO/Wireless 2100 MiniPCI> mem 0xff7fd000-0xff7fdfff irq4 at device 4.0 pci1
ipw0: Ethernet address: 00:04:23:71:77:46
ipw0: [ITHREAD]
fxp0: <Intel 82801DB (ICH4) Pro/100 VM Ethernet> port 0xcc00-0xcc3f mem 0xff7ff000-0xff7fffff irq 11 at device 8.0 on pci1
fxp0: fxp_miibus_readreg: timed out
.. 31 times more ...
fxp0: MII without any PHY!
device_attach: fxp0 attach returned 6

pcm0: <Intel ICH4 (82801DB)> port 0xe000-0xe0ff,0xe100-0xe13f at device 31.5 on pci0
pcm0: [ITHREAD]
pcm0: <Sigmatel STAC9750/51 AC97 Codec>
fxp0: <Intel 82801DB (ICH4) Pro/100 VM Ethernet> port 0xcc00-0xcc3f mem 0xff7ff000-0xff7fffff irq 11 at device 8.0 on pci1
fxp0: fxp_miibus_readreg: timed out
.. 31 times more ...
fxp0: MII without any PHY!
device_attach: fxp0 attach returned 6

I booted the system using the RELENG_6_3 disc1 and was having the same messages regarding the fxp(4) driver.

Might it be possible that the driver is having trouble with this chipset or the device is broken on the system.

Anyway, if anyone have a clue about how to fix this, I would really appreciate any information.

Sincerely

Francis Gendreau

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: