Something is wrong with the fxp network driver
Derek Ragona
derek at computinginnovations.com
Fri Sep 26 17:30:07 PDT 2003
This worked until I went beyond p4 on 5.1 release
I found a PR that suggested adding:
{ 0x1050, "Intel 82801EB (ICH5) Pro/100 Ethernet" },
line to the if_fxp.c file, in the struct:
/*
* Claim various Intel PCI device identifiers for this driver. The
* sub-vendor and sub-device field are extensively used to identify
* particular variants, but we don't currently differentiate between
* them.
*/
static struct fxp_ident fxp_ident_table[] = {
{ 0x1029, "Intel 82559 PCI/CardBus Pro/100" },
{ 0x1030, "Intel 82559 Pro/100 Ethernet" },
{ 0x1031, "Intel 82801CAM (ICH3) Pro/100 VE Ethernet" },
{ 0x1032, "Intel 82801CAM (ICH3) Pro/100 VE Ethernet" },
{ 0x1033, "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1034, "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1035, "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1036, "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1037, "Intel 82801CAM (ICH3) Pro/100 Ethernet" },
{ 0x1038, "Intel 82801CAM (ICH3) Pro/100 VM Ethernet" },
{ 0x1039, "Intel 82801DB (ICH4) Pro/100 VE Ethernet" },
{ 0x103A, "Intel 82801DB (ICH4) Pro/100 Ethernet" },
{ 0x103B, "Intel 82801DB (ICH4) Pro/100 VM Ethernet" },
{ 0x103C, "Intel 82801DB (ICH4) Pro/100 Ethernet" },
{ 0x103D, "Intel 82801DB (ICH4) Pro/100 VE Ethernet" },
{ 0x103E, "Intel 82801DB (ICH4) Pro/100 VM Ethernet" },
{ 0x1050, "Intel 82801EB (ICH5) Pro/100 Ethernet" },
{ 0x1059, "Intel 82551QM Pro/100 M Mobile Connection" },
{ 0x1209, "Intel 82559ER Embedded 10/100 Ethernet" },
{ 0x1229, "Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet" },
{ 0x2449, "Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet" },
{ 0, NULL },
};
-Derek
At 07:15 PM 9/26/2003 -0500, Derek Ragona wrote:
>Mine is an Intel® Server Board S875WP1-E, I was using a patch but it quite
>working on the fxp0 interface.
>
> -Derek
>
>
>At 08:07 PM 9/26/2003 -0400, Mike Tancsa wrote:
>
>>Are they Tyan motherboards by chance ? There was a thread in stable
>>about this a few weeks ago. The problems seem specific to those
>>motherboards. Someone posted a potential workaround as well.
>>
>> ---Mike
>>
>>On Fri, 26 Sep 2003 11:40:08 -0500, in sentex.lists.freebsd.current
>>you wrote:
>>
>> >I am having a problem with recent builds of -current with the fxp
>> >driver. A couple of days ago, the 6 machines in my cluster with fxp
>> >interfaces all died at about the same time with fxp timeout errors. The
>> >machines with 3Com xl interfaces kept on going. Today, I am observing
>> >that the throughput is about half of what I am seeing on my machines
>> >with a 3Com xl interface. Is anybody else observing this? What other
>> >information do I need to provide?
>> >
>> >Thanks.
>>
>>_______________________________________________
>>freebsd-current at freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>_______________________________________________
>freebsd-current at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
More information about the freebsd-current
mailing list