Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 May 2001 10:27:16 -0500 (CDT)
From:      Jonathan Lemon <jlemon@flugsvamp.com>
To:        mike@sentex.net, stable@freebsd.org
Subject:   Re: Continuing ahc problems - also cause fxp failure
Message-ID:  <200105231527.f4NFRGs46131@prism.flugsvamp.com>
In-Reply-To: <local.mail.freebsd-stable/4.2.2.20010522203343.01dc3ea0@192.168.0.12>
References:  <local.mail.freebsd-stable/00e301c0e314$0a46ff50$03d5a8c0@oryon> <local.mail.freebsd-stable/200105220925.f4M9Paf00409@earth.backplane.com> <local.mail.freebsd-stable/3B0AE7A5.3DB34788@DougBarton.net> <local.mail.freebsd-stable/00e301c0e314$0a46ff50$03d5a8c0@oryon> <local.mail.freebsd-stable/20010522170545.B12931@nexus.root.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-stable/4.2.2.20010522203343.01dc3ea0@192.168.0.12> you write:
>At 05:05 PM 5/22/2001 -0700, David Greenman wrote:
>> >Hello all,
>> >
>> >bad news.. Matt is not the only one who had problem with fxp device.
>> >Yesterday I have in dmesg and messages lines like this:
>> >
>> >May 22 16:30:24 db /kernel: fxp0: SCB timeout
>>
>>    You didn't mention which motherboard you were using. There are known
>
> From the dmesg he provided in another message, this looks not to be an 
>815E based on the phy
>
>
>>May 22 19:12:37 db /kernel: fxp0: <Intel Pro 10/100B/100+ Ethernet> port 
>>0x5400-0x543f mem 0xfb000000-0xfb0fffff,0xfb101000-0xfb101f
>>ff irq 7 at device 3.0 on pci0
>>May 22 19:12:37 db /kernel: fxp0: Ethernet address 00:d0:b7:b6:51:97
>>May 22 19:12:37 db /kernel: inphy0: <i82555 10/100 media interface> on miibus0
>>May 22 19:12:37 db /kernel: inphy0:  10baseT, 10baseT-FDX, 100baseTX, 
>>100baseTX-FDX, auto
>>I have this motherboard http://www.intel.com/design/servers/STL2/
>>
>>As you can see, he is equiped with onboard Intel® PRO/100+ Fast Ethernet
>>Controller and Ultra160 SCSI storage controller.
>>
>>This motherboard have 82559 NIC chip.
>
>
>However, I wonder if its being miss identified ? Or is the 82555 the same 
>as the 82559 ?

Nope.  The 82559 is the actual NIC itself.  The 82555 is the PHY.
The problems with the 815E motherboards are (as far as I know) 
restricted to those that have the 82562EM and 82562ET chips; these
should show up in the inphy identification line.

The problems with ahc & fxp don't appear to be related to the 815E
problems, this seems to be something else.

Matt has seen the problems with both the old & new fxp drivers; the 
problem seems to have popped up with the ahc driver updates.  So 
my guess is that it is an unfortunate interaction between the drivers.

What's interesting to note, is that both Matt and Vladislav's 
systems are using the same RCC chipset:
   <ServerWorks NB6635 3.0LE host to PCI bridge>

I wonder if this is related?  Dell did have some problems with APIC
rotuing on the boards, but I was under the impression that this had
been resolved already.

Is anyone else running fxp + ahc combination on this chipset?
--
Jonathan

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?200105231527.f4NFRGs46131>