Re: Something is wrong with the fxp network driver
On Sat, Sep 27, 2003 at 12:12:40AM -0400, Mike Tancsa wrote: At 11:32 PM 26/09/2003, Glenn Johnson wrote: On Fri, Sep 26, 2003 at 08:07:38PM -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. No, five of them are MSI dual Athlon-MP boards (can not remember the what does pciconf -v -l show for the cards ? I will not be able to answer that until Monday. Are all on the same switch ? Yes, they are all on the same switch. Other machines with an xl interface are fine though. Is it a flow control issue perhaps ? I am not sure what you mean? -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
pciconf -v -l output is: # pciconf -v -l [EMAIL PROTECTED]:0:0: class=0x06 card=0x25788086 chip=0x25788086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x25798086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:3:0: class=0x060400 card=0x chip=0x257b8086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x34278086 chip=0x24d28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x34278086 chip=0x24d48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x34278086 chip=0x24d78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:3:class=0x0c0300 card=0x34278086 chip=0x24de8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x34278086 chip=0x24dd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:30:0:class=0x060400 card=0x chip=0x244e8086 rev=0xc2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB (ICH2/3/4) Hub Interface to PCI Bridge (244E)' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:31:0:class=0x060100 card=0x chip=0x24d08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:31:1: class=0x01018a card=0x34278086 chip=0x24db8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:31:2: class=0x01018f card=0x34278086 chip=0x24d18086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x34278086 chip=0x24d38086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = SMBus [EMAIL PROTECTED]:1:0: class=0x02 card=0x34278086 chip=0x10198086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class= network subclass = ethernet [EMAIL PROTECTED]:6:0: class=0x03 card=0x34278086 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage XL PCI' class= display subclass = VGA [EMAIL PROTECTED]:7:0: class=0x010400 card=0x34278086 chip=0x3319105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20319? FastTrak SATA150 TX4 Controller' class= mass storage subclass = RAID [EMAIL PROTECTED]:8:0: class=0x02 card=0x34278086 chip=0x10508086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class= network subclass = ethernet ifconfig fxp0 is: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::207:e9ff:fe39:d437%fxp0 prefixlen 64 scopeid 0x2 ether 00:07:e9:39:d4:37 media: Ethernet autoselect (100baseTX full-duplex) status: active -Derek At 04:17 PM 9/27/2003 -0500, Glenn Johnson wrote: On Sat, Sep 27, 2003 at 12:12:40AM -0400, Mike Tancsa wrote: At 11:32 PM 26/09/2003, Glenn Johnson wrote: On Fri, Sep 26, 2003 at 08:07:38PM -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. No, five of them are MSI dual Athlon-MP boards (can not remember the what does pciconf -v -l show for the cards ? I will not be able to answer that until Monday. Are all on the same switch ? Yes, they are all on the same switch. Other machines with an xl interface are fine though. Is it a flow control issue perhaps ? I am not sure what you mean? -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
Revised output from pciconf -v -l [EMAIL PROTECTED]:8:0: class=0x02 card=0x34278086 chip=0x10508086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82562EZ Pro 10/100 Mb/s VE Fast Ethernet MAC PHY' class= network subclass = ethernet -Derek At 10:40 PM 9/27/2003 -0500, Derek Ragona wrote: pciconf -v -l output is: # pciconf -v -l [EMAIL PROTECTED]:0:0: class=0x06 card=0x25788086 chip=0x25788086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x25798086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:3:0: class=0x060400 card=0x chip=0x257b8086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x34278086 chip=0x24d28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x34278086 chip=0x24d48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x34278086 chip=0x24d78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:3:class=0x0c0300 card=0x34278086 chip=0x24de8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x34278086 chip=0x24dd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = USB [EMAIL PROTECTED]:30:0:class=0x060400 card=0x chip=0x244e8086 rev=0xc2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB (ICH2/3/4) Hub Interface to PCI Bridge (244E)' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:31:0:class=0x060100 card=0x chip=0x24d08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:31:1: class=0x01018a card=0x34278086 chip=0x24db8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:31:2: class=0x01018f card=0x34278086 chip=0x24d18086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x34278086 chip=0x24d38086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= serial bus subclass = SMBus [EMAIL PROTECTED]:1:0: class=0x02 card=0x34278086 chip=0x10198086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class= network subclass = ethernet [EMAIL PROTECTED]:6:0: class=0x03 card=0x34278086 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage XL PCI' class= display subclass = VGA [EMAIL PROTECTED]:7:0: class=0x010400 card=0x34278086 chip=0x3319105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20319? FastTrak SATA150 TX4 Controller' class= mass storage subclass = RAID [EMAIL PROTECTED]:8:0: class=0x02 card=0x34278086 chip=0x10508086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class= network subclass = ethernet ifconfig fxp0 is: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::207:e9ff:fe39:d437%fxp0 prefixlen 64 scopeid 0x2 ether 00:07:e9:39:d4:37 media: Ethernet autoselect (100baseTX full-duplex) status: active -Derek At 04:17 PM 9/27/2003 -0500, Glenn Johnson wrote: On Sat, Sep 27, 2003 at 12:12:40AM -0400, Mike Tancsa wrote: At 11:32 PM 26/09/2003, Glenn Johnson wrote: On Fri, Sep 26, 2003 at 08:07:38PM -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. No, five of them are MSI dual Athlon-MP boards (can not remember the what does pciconf -v -l show for the cards ? I will not be able to answer that until Monday. Are all on the same switch ? Yes, they are all on the same switch. Other machines with an xl interface are fine though. Is it a flow control issue perhaps ? I am not sure what you mean? -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Something is wrong with the fxp network driver
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. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
Hi Glenn, We have several FreeBSD boxes here. Some run -current and some run -5.1-P4 and all have fxp* and em* You must have something else going wrong that is causing you the grief. fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::202:b3ff:fe96:c64b%fxp0 prefixlen 64 scopeid 0x1 ether 00:02:b3:96:c6:4b media: Ethernet autoselect (10baseT/UTP) status: active The above is on: gw-tor# uname -a FreeBSD gw-tor.FreeBSDsystems.COM 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Sep 24 11:07:47 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GW-TOR i386 Because of our network setup, fxp0 does not have any ip address bound to it. Check your logs, like I said, something else is causing the problem. Lanny =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Lanny Baron Proud to be 100% FreeBSD http://www.FreeBSDsystems.COM Toll Free: 1.877.963.1900 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= - Original Message - From: Glenn Johnson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 26, 2003 12:40 PM Subject: Something is wrong with the fxp network driver 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. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
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.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
On Fri, Sep 26, 2003 at 08:07:38PM -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. No, five of them are MSI dual Athlon-MP boards (can not remember the exact model and am not near the machines now), and one is an Epox Athlon-XP board. The five MSI boards are using a built-in LAN interface and the Epox is using a PCI card. I do have some machines with Tyan motherboards but they have 3Com xl interfaces in them. 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. -- Glenn Johnson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something is wrong with the fxp network driver
At 11:32 PM 26/09/2003, Glenn Johnson wrote: On Fri, Sep 26, 2003 at 08:07:38PM -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. No, five of them are MSI dual Athlon-MP boards (can not remember the what does pciconf -v -l show for the cards ? Are all on the same switch ? Is it a flow control issue perhaps ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
