From nobody@FreeBSD.org  Sat Jul  6 13:10:43 2002
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 45DDD37B400
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  6 Jul 2002 13:10:43 -0700 (PDT)
Received: from www.freebsd.org (www.FreeBSD.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E2F6B43E52
	for <freebsd-gnats-submit@FreeBSD.org>; Sat,  6 Jul 2002 13:10:42 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.4/8.12.4) with ESMTP id g66KAgOT066652
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 6 Jul 2002 13:10:42 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.4/8.12.4/Submit) id g66KAg9e066651;
	Sat, 6 Jul 2002 13:10:42 -0700 (PDT)
Message-Id: <200207062010.g66KAg9e066651@www.freebsd.org>
Date: Sat, 6 Jul 2002 13:10:42 -0700 (PDT)
From: John Mechalas <seagull@aracnet.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: "fxp: device timeout" errors during heavy, sustained network activity
X-Send-Pr-Version: www-1.0

>Number:         40274
>Category:       kern
>Synopsis:       [fxp] "fxp: device timeout" errors during heavy, sustained network activity (still on 5.4)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 06 13:20:01 PDT 2002
>Closed-Date:    Tue Jun 12 04:46:19 GMT 2007
>Last-Modified:  Tue Jun 12 04:46:19 GMT 2007
>Originator:     John Mechalas
>Release:        4.6-RELEASE
>Organization:
n/a
>Environment:
FreeBSD medley 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Wed Jul  3 18:55:16 PDT 2002
     root@medley:/usr/src/sys/compile/MEDLEY  i386

>Description:
During heavy, sustained network activity, the fxp driver reports a "device timeout" error, and the interface basically "goes away".  Existing connections ot the machine (that route through that interface) hang for a period of several seconds to less than a minute, at which point it comes back up.

A look back through my messages logs of old shows that this did happen once or twice under 4.5-RELEASE, though I don't recall actually seeing application troubles during day-to-day work.  It may have been a problem before then, too.  But, under 4.6-RELEASE, it happens frequently (every two or three attempts to do large file transfers), and I can see the effects of it quite clearly.  So whle the phenomenon may not be new,
the upgrade to 4.6 has drastically increased the frequency of occurance.

Note that this is a dual-proc system.  Here's dmesg from my most recent boot:

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 4.6-RELEASE #0: Wed Jul  3 18:55:16 PDT 2002
    root@medley:/usr/src/sys/compile/MEDLEY
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (696.41-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x683  Stepping = 3
  Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
OV,PAT,PSE36,PN,MMX,FXSR,SSE>
real memory  = 134152192 (131008K bytes)
avail memory = 127057920 (124080K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc0371000.
Pentium Pro MTRR support enabled
Using $PIR table, 12 entries at 0xc00fdf00
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443GX host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <Intel 82443GX (440 GX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pcib3: <PCI to PCI bridge (vendor=1011 device=0023)> at device 15.0 on pci1
pci2: <PCI bus> on pcib3
pcib4: <DEC 21154 PCI-PCI bridge> at device 11.0 on pci0
pci3: <PCI bus> on pcib4
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0x2000-0x203f mem 0xf4200000-0xf421ffff,0xf4240000-0xf4240fff irq 5 at device 4.0 on pci3
fxp0: Ethernet address 00:d0:b7:11:80:88
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0x2040-0x207f mem 0xf4220000-0xf423ffff,0xf4241000-0xf4241fff irq 11 at device 5.0 on pci3
fxp1: Ethernet address 00:d0:b7:11:80:89
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ahc0: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0x1400-0x14ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0
aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0x1800-0x18ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0
aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs
fxp2: <Intel Pro 10/100B/100+ Ethernet> port 0x1080-0x10bf mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0
fxp2: Ethernet address 00:a0:c9:fb:31:38
inphy2: <i82555 10/100 media interface> on miibus2
inphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <Intel 82371AB PCI to ISA bridge> at device 18.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0x1050-0x105f at device 18.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1060-0x107f irq 10 at device 18.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Timecounter "PIIX"  frequency 3579545 Hz
chip1: <Intel 82371AB Power management controller> port 0x1040-0x104f at device 18.3 on pci0
pci0: <Cirrus Logic GD5480 SVGA controller> at 20.0
pcib1: <Intel 82443GX host to AGP bridge> on motherboard
pci4: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcd7ff,0xcd800-0xcdfff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
ata0-slave: ATAPI identify retries exceeded
SMP: AP CPU #1 Launched!
ad2: 8297MB <Maxtor 90871U2> [16858/16/63] at ata1-master UDMA33
ad3: 78167MB <Maxtor 98196H8> [158816/16/63] at ata1-slave UDMA33
acd0: CDROM <FX810T> at ata0-master PIO3
Waiting 3 seconds for SCSI devices to settle
Mounting root from ufs:/dev/da0s1a
da0 at ahc1 bus 0 target 0 lun 0
da0: <SEAGATE ST32550N 0021> Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C)

Here's the error as it appears in the logs:

fxp2: device timeout

>How-To-Repeat:
I have been most successful repeating this problem using Samba to transfer large data files or data file sets to a Windows PC.  Anywhere from 100 Mb to 400 Mb into the transfers, the connection drops and the BSD system reports a device timeout.

I have been able to reproduce this both on a dual Intel network adapter (either an 82558 or an 82559, I don't remember which) as well as on the on-board LAN (an Intel 82559 on an L440GX+ motherboard).
>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: dwmalone 
State-Changed-When: Sun Jul 14 15:29:41 PDT 2002 
State-Changed-Why:  
There have been some changes to the fxp driver which may help this 
problem which have been made since 4.6. Could you try a more recent 
version of the driver and let us know what happens? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=40274 

From: "Chris Guthrie" <cguthrie@clubphoto.com>
To: <freebsd-gnats-submit@FreeBSD.org>, <seagull@aracnet.com>
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Sat, 14 Sep 2002 09:50:34 -0700

 Another datapoint.  I'm getting the same problem on an old Compaq Proliant
 running
 a very recent version (4.7 Release-candidate).  I can cause the timeouts
 pretty reliably
 by doing a make installworld on another machine via NFS.
 
 Sep 14 07:52:31 edgeware /kernel: Copyright (c) 1992-2002 The FreeBSD
 Project.
 Sep 14 07:52:31 edgeware /kernel: Copyright (c) 1979, 1980, 1983, 1986,
 1988, 1989, 1991, 1992, 1993, 1994
 Sep 14 07:52:31 edgeware /kernel: The Regents of the University of
 California. All rights reserved.
 Sep 14 07:52:31 edgeware /kernel: FreeBSD 4.7-PRERELEASE #1: Thu Sep 12
 08:33:25 PDT 2002
 Sep 14 07:52:31 edgeware /kernel:
 cguthrie@edgeware.digiproofs.com:/usr/obj/usr/src/sys/COMPAQ
 Sep 14 07:52:31 edgeware /kernel: Timecounter "i8254"  frequency 1193182 Hz
 Sep 14 07:52:31 edgeware /kernel: CPU: Pentium II/Pentium II Xeon/Celeron
 (398.79-MHz 686-class CPU)
 Sep 14 07:52:31 edgeware /kernel: Origin = "GenuineIntel"  Id = 0x651
 Stepping = 1
 Sep 14 07:52:31 edgeware /kernel:
 Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
 CMOV,PAT,PSE36,MMX,FXSR>
 Sep 14 07:52:31 edgeware /kernel: real memory  = 469745664 (458736K bytes)
 Sep 14 07:52:31 edgeware /kernel: avail memory = 452841472 (442228K bytes)
 Sep 14 07:52:31 edgeware /kernel: Changing APIC ID for IO APIC #0 from 0 to
 8 on chip
 Sep 14 07:52:31 edgeware /kernel: Programming 35 pins in IOAPIC #0
 Sep 14 07:52:31 edgeware /kernel: IOAPIC #0 intpin 2 -> irq 0
 Sep 14 07:52:31 edgeware /kernel: FreeBSD/SMP: Multiprocessor motherboard
 Sep 14 07:52:31 edgeware /kernel: cpu0 (BSP): apic id:  1, version:
 0x00040011, at 0xfee00000
 Sep 14 07:52:31 edgeware /kernel: cpu1 (AP):  apic id:  0, version:
 0x00040011, at 0xfee00000
 Sep 14 07:52:31 edgeware /kernel: io0 (APIC): apic id:  8, version:
 0x00220011, at 0xfec00000
 Sep 14 07:52:31 edgeware /kernel: Preloaded elf kernel "kernel" at
 0xc03fc000.
 Sep 14 07:52:31 edgeware /kernel: Pentium Pro MTRR support enabled
 Sep 14 07:52:31 edgeware /kernel: md0: Malloc disk
 Sep 14 07:52:32 edgeware /kernel: npx0: <math processor> on motherboard
 Sep 14 07:52:32 edgeware /kernel: npx0: INT 16 interface
 Sep 14 07:52:32 edgeware /kernel: pcib0: <Intel 82443BX host to PCI bridge
 (AGP disabled)> on motherboard
 Sep 14 07:52:32 edgeware /kernel: pci0: <PCI bus> on pcib0
 Sep 14 07:52:32 edgeware /kernel: sym0: <875> port 0x2000-0x20ff mem
 0xc6dff000-0xc6dfffff,0xc6dfbf00-0xc6dfbfff irq 10 at device 6.0 on pci0
 Sep 14 07:52:32 edgeware /kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity
 checking
 Sep 14 07:52:32 edgeware /kernel: sym1: <875> port 0x2400-0x24ff mem
 0xc6dfe000-0xc6dfefff,0xc6dfbe00-0xc6dfbeff irq 11 at device 6.1 on pci0
 Sep 14 07:52:32 edgeware /kernel: sym1: No NVRAM, ID 7, Fast-20, SE, parity
 checking
 Sep 14 07:52:32 edgeware /kernel: tl0: <Compaq Netelligent 10/100 Proliant>
 port 0x2c60-0x2c6f mem 0xc6dfbcf0-0xc6dfbcff irq 15 at device 7.0 on pci0
 Sep 14 07:52:32 edgeware /kernel: tl0: Ethernet address: 00:08:c7:4c:b9:fa
 Sep 14 07:52:32 edgeware /kernel: miibus0: <MII bus> on tl0
 Sep 14 07:52:32 edgeware /kernel: lxtphy0: <LXT970 10/100 media interface>
 on miibus0
 Sep 14 07:52:32 edgeware /kernel: lxtphy0:  100baseFX, 100baseFX-FDX,
 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 Sep 14 07:52:32 edgeware /kernel: tlphy0: <ThunderLAN 10baseT media
 interface> on miibus0
 Sep 14 07:52:32 edgeware /kernel: tlphy0:  10base2/BNC, 10base5/AUI
 Sep 14 07:52:32 edgeware /kernel: pci0: <ATI Mach64-GV graphics accelerator>
 at 8.0
 Sep 14 07:52:32 edgeware /kernel: pci0: <unknown card> (vendor=0x0e11,
 dev=0xa0f0) at 9.0
 Sep 14 07:52:32 edgeware /kernel: fxp0: <Intel Pro 10/100B/100+ Ethernet>
 port 0x2c40-0x2c5f mem 0xc6f00000-0xc6ffffff,0xc4fff000-0xc4ffffff irq 5 at
 device 15.0 on pci0
 Sep 14 07:52:32 edgeware /kernel: fxp0: Ethernet address 00:08:c7:07:05:b8
 Sep 14 07:52:32 edgeware /kernel: inphy0: <i82555 10/100 media interface> on
 miibus1
 Sep 14 07:52:32 edgeware /kernel: inphy0:  10baseT, 10baseT-FDX, 100baseTX,
 100baseTX-FDX, auto
 Sep 14 07:52:32 edgeware /kernel: fxp1: <Intel Pro 10/100B/100+ Ethernet>
 port 0x2c00-0x2c3f mem 0xc6e00000-0xc6efffff,0xc6dfc000-0xc6dfcfff irq 5 at
 device 16.0 on pci0
 Sep 14 07:52:32 edgeware /kernel: fxp1: Ethernet address 00:90:27:de:9f:1b
 Sep 14 07:52:32 edgeware /kernel: inphy1: <i82555 10/100 media interface> on
 miibus2
 Sep 14 07:52:32 edgeware /kernel: inphy1:  10baseT, 10baseT-FDX, 100baseTX,
 100baseTX-FDX, auto
 Sep 14 07:52:32 edgeware /kernel: isab0: <Intel 82371AB PCI to ISA bridge>
 at device 20.0 on pci0
 Sep 14 07:52:32 edgeware /kernel: isa0: <ISA bus> on isab0
 Sep 14 07:52:32 edgeware /kernel: atapci0: <Intel PIIX4 ATA33 controller>
 port 0xf100-0xf10f at device 20.1 on pci0
 Sep 14 07:52:32 edgeware /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Sep 14 07:52:32 edgeware /kernel: ata1: at 0x170 irq 15 on atapci0
 Sep 14 07:52:32 edgeware /kernel: uhci0: <Intel 82371AB/EB (PIIX4) USB
 controller> irq 0 at device 20.2 on pci0
 Sep 14 07:52:32 edgeware /kernel: uhci0: Could not map ports
 Sep 14 07:52:32 edgeware /kernel: device_probe_and_attach: uhci0 attach
 returned 6
 Sep 14 07:52:32 edgeware /kernel: piix0: <Intel 82371AB Power management
 controller> at device 20.3 on pci0
 Sep 14 07:52:32 edgeware /kernel: eisa0: <EISA bus> on motherboard
 Sep 14 07:52:32 edgeware /kernel: mainboard0: <CPQ0679 (System Board)> on
 eisa0 slot 0
 Sep 14 07:52:32 edgeware /kernel: orm0: <Option ROMs> at iomem
 0xc0000-0xc7fff,0xe8000-0xedfff,0xee000-0xeffff on isa0
 Sep 14 07:52:32 edgeware /kernel: fdc0: <NEC 72065B or clone> at port
 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 Sep 14 07:52:32 edgeware /kernel: fdc0: FIFO enabled, 8 bytes threshold
 Sep 14 07:52:32 edgeware /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 Sep 14 07:52:32 edgeware /kernel: atkbdc0: <Keyboard controller (i8042)> at
 port 0x60,0x64 on isa0
 Sep 14 07:52:32 edgeware /kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 on
 atkbdc0
 Sep 14 07:52:32 edgeware /kernel: kbd0 at atkbd0
 Sep 14 07:52:32 edgeware /kernel: vga0: <Generic ISA VGA> at port
 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 Sep 14 07:52:32 edgeware /kernel: sc0: <System console> at flags 0x100 on
 isa0
 Sep 14 07:52:32 edgeware /kernel: sc0: VGA <16 virtual consoles,
 flags=0x300>
 Sep 14 07:52:32 edgeware /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10
 on isa0
 Sep 14 07:52:32 edgeware /kernel: sio0: type 16550A
 Sep 14 07:52:32 edgeware /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
 Sep 14 07:52:32 edgeware /kernel: sio1: type 16550A
 Sep 14 07:52:32 edgeware /kernel: ppc0: cannot reserve I/O port range
 Sep 14 07:52:32 edgeware /kernel: APIC_IO: Testing 8254 interrupt delivery
 Sep 14 07:52:32 edgeware /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin
 2
 Sep 14 07:52:32 edgeware /kernel: IP packet filtering initialized, divert
 enabled, rule-based forwarding enabled, default to deny, unlimited logging
 Sep 14 07:52:32 edgeware /kernel: IPsec: Initialized Security Association
 Processing.
 Sep 14 07:52:32 edgeware /kernel: SMP: AP CPU #1 Launched!
 Sep 14 07:52:32 edgeware /kernel: ad1: timeout waiting for interrupt
 Sep 14 07:52:32 edgeware /kernel: ad1: 156334MB <Maxtor 4G160J8>
 [317632/16/63] at ata0-slave UDMA33
 Sep 14 07:52:32 edgeware /kernel: acd0: CDROM <CD-224E> at ata0-master PIO4
 Sep 14 07:52:32 edgeware /kernel: Waiting 5 seconds for SCSI devices to
 settle
 Sep 14 07:52:32 edgeware /kernel: Mounting root from ufs:/dev/da0s1a
 Sep 14 07:52:32 edgeware /kernel: da0 at sym1 bus 0 target 0 lun 0
 Sep 14 07:52:32 edgeware /kernel: da0: <IBM IC35L018UWD210-0 S5BS> Fixed
 Direct Access SCSI-3 device
 Sep 14 07:52:32 edgeware /kernel: da0: 40.000MB/s transfers (20.000MHz,
 offset 16, 16bit), Tagged Queueing Enabled
 Sep 14 07:52:32 edgeware /kernel: da0: 17501MB (35843670 512 byte sectors:
 255H 63S/T 2231C)
 Sep 14 07:52:32 edgeware named[83]: starting (/etc/namedb/named.conf).
 named 8.3.3-REL Fri Sep  6 19:31:23 PDT 2002
 cguthrie@freebsd.clubphoto.local:/usr/obj/usr/src/usr.sbin/named
 Sep 14 07:52:32 edgeware named[83]: limit files set to fdlimit (1024)
 Sep 14 07:52:32 edgeware named[83]: db_load could not open: localhost.rev:
 No such file or directory
 Sep 14 07:52:32 edgeware named[83]: db_load could not open:
 localhost-v6.rev: No such file or directory
 Sep 14 07:52:32 edgeware named[84]: Ready to answer queries.
 Sep 14 07:52:33 edgeware ntpd[86]: ntpd 4.1.0-a Fri Sep  6 19:30:53 PDT 2002
 (1)
 Sep 14 07:52:33 edgeware ntpd[86]: kernel time discipline status 2040
 Sep 14 07:52:33 edgeware /kernel: arplookup 216.218.198.2 failed: host is
 not on local network
 Sep 14 07:54:00 edgeware login: ROOT LOGIN (root) ON ttyv0
 Sep 14 07:56:00 edgeware ntpd[86]: time set -0.106732 s
 Sep 14 08:05:00 edgeware /kernel: fxp0: device timeout
 Sep 14 08:06:03 edgeware /kernel: fxp0: device timeout
 Sep 14 08:06:16 edgeware /kernel: fxp1: device timeout
 Sep 14 08:07:04 edgeware /kernel: fxp0: device timeout
 Sep 14 08:07:38 edgeware /kernel: fxp0: device timeout
 Sep 14 08:07:53 edgeware ntpd[86]: sendto(131.216.22.15): No route to host
 Sep 14 08:07:58 edgeware ntpd[86]: sendto(140.162.8.3): No route to host
 Sep 14 08:07:59 edgeware ntpd[86]: sendto(132.239.1.6): No route to host
 Sep 14 08:08:13 edgeware /kernel: fxp0: device timeout
 Sep 14 08:09:40 edgeware /kernel: fxp0: device timeout
 Sep 14 08:09:47 edgeware reboot: rebooted by root
 

From: John Mechalas <seagull@aracnet.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained
 network activity
Date: Sat, 05 Oct 2002 09:35:59 -0700

 As of FreeBSD 4.6.2, I have not seen thie problem re-occur.
 
 
 Cheers,
 John
 
 

From: "Gilbert Gong" <ggong@tch.org>
To: <freebsd-gnats-submit@freebsd.org>
Cc: <jlemon@freebsd.org>
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Thu, 21 Nov 2002 19:57:27 -0800

 I saw this problem today, on a dual cpu 4.7 RELEASE box w/ 2 nics as well.
 It was basically a fresh clean install, with a few apps installed.
 
 I can't get much info, as it's a production box, and I quickly reverted to a
 single CPU kernel once I saw the problem occur twice in a row.
 
 My problem also appeared to be triggered by samba traffic.  This happened
 twice at least before I switched back to the CPU kernel.  The machine become
 unreachable (would not respond to pings), and console response was extremely
 slow (I sat for a while even waiting for a password prompt to show up after
 typing in a username).
 
 It happened very quickly once I started a large samba copy.  The machine
 works fine when using a single CPU kernel, and does not show the timeout
 problem at all in any way shape or form.  I have yet to remove the 2nd nic
 (as it is removable) and see if the dual CPU kernel will work without fault.
 
 It is connected to a Cisco 3548 switch.
 
 This history of this box (in case ppl are wondering if it happened in prior
 versions) is that it was a Windows 2k box up until yesterday (I'm still
 somewhat surprised my boss let me migrate it to FreeBSD after the machine
 was compromised).
 Gilbert
 
 (dmesg equivalent output)
 
 Nov 21 11:15:33 ion /kernel: Copyright (c) 1992-2002 The FreeBSD Project.
 Nov 21 11:15:33 ion /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
 1989, 1991, 1992, 1993, 1994
 Nov 21 11:15:33 ion /kernel: The Regents of the University of California.
 All rights reserved.
 Nov 21 11:15:33 ion /kernel: FreeBSD 4.7-RELEASE #0: Thu Nov 21 10:08:19 PST
 2002
 Nov 21 11:15:33 ion /kernel: root@ion.lithium.com:/usr/src/sys/compile/ION
 Nov 21 11:15:33 ion /kernel: Timecounter "i8254"  frequency 1193182 Hz
 Nov 21 11:15:33 ion /kernel: CPU: Pentium III/Pentium III Xeon/Celeron
 (448.88-MHz 686-class CPU)
 Nov 21 11:15:33 ion /kernel: Origin = "GenuineIntel"  Id = 0x673  Stepping =
 3
 Nov 21 11:15:33 ion /kernel:
 Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
 CMO
 V,PAT,PSE36,PN,MMX,FXSR,SSE>
 Nov 21 11:15:33 ion /kernel: real memory  = 1073676288 (1048512K bytes)
 Nov 21 11:15:33 ion /kernel: avail memory = 1041670144 (1017256K bytes)
 Nov 21 11:15:33 ion /kernel: Programming 24 pins in IOAPIC #0
 Nov 21 11:15:33 ion /kernel: IOAPIC #0 intpin 2 -> irq 0
 Nov 21 11:15:33 ion /kernel: FreeBSD/SMP: Multiprocessor motherboard
 Nov 21 11:15:33 ion /kernel: cpu0 (BSP): apic id:  1, version: 0x00040011,
 at 0xfee00000
 Nov 21 11:15:33 ion /kernel: cpu1 (AP):  apic id:  0, version: 0x00040011,
 at 0xfee00000
 Nov 21 11:15:33 ion /kernel: io0 (APIC): apic id:  2, version: 0x00170011,
 at 0xfec00000
 Nov 21 11:15:33 ion /kernel: Preloaded elf kernel "kernel" at 0xc0358000.
 Nov 21 11:15:33 ion /kernel: Pentium Pro MTRR support enabled
 Nov 21 11:15:33 ion /kernel: md0: Malloc disk
 Nov 21 11:15:33 ion /kernel: Using $PIR table, 8 entries at 0xc00fdf40
 Nov 21 11:15:33 ion /kernel: npx0: <math processor> on motherboard
 Nov 21 11:15:33 ion /kernel: npx0: INT 16 interface
 Nov 21 11:15:33 ion /kernel: pcib0: <Intel 82443BX host to PCI bridge (AGP
 disabled)> on motherboard
 Nov 21 11:15:33 ion /kernel: pci0: <PCI bus> on pcib0
 Nov 21 11:15:33 ion /kernel: pcib1: <PCI to PCI bridge (vendor=8086
 device=0960)> at device 11.0 on pci0
 Nov 21 11:15:33 ion /kernel: pci1: <PCI bus> on pcib1
 Nov 21 11:15:33 ion /kernel: mlx0: <Mylex version 4 RAID interface> mem
 0xfa206000-0xfa207fff irq 11 at devi
 ce 11.1 on pci0
 Nov 21 11:15:33 ion /kernel: mlx0: DAC960PG, 3 channels, firmware 4.08-0-33,
 8MB RAM
 Nov 21 11:15:33 ion /kernel: mlxd0: <Mylex System Drive> on mlx0
 Nov 21 11:15:33 ion /kernel: mlxd0: 8748MB (17915904 sectors) RAID 1
 (online)
 Nov 21 11:15:33 ion /kernel: mlxd1: <Mylex System Drive> on mlx0
 Nov 21 11:15:33 ion /kernel: mlxd1: 70004MB (143368192 sectors) RAID 5
 (online)
 Nov 21 11:15:33 ion /kernel: fxp0: <Intel Pro 10/100B/100+ Ethernet> port
 0x1080-0x10bf mem 0xfa000000-0xfa0
 fffff,0xfa200000-0xfa200fff irq 11 at device 12.0 on pci0
 Nov 21 11:15:33 ion /kernel: fxp0: Ethernet address 00:90:27:91:a0:db
 Nov 21 11:15:33 ion /kernel: inphy0: <i82555 10/100 media interface> on
 miibus0
 Nov 21 11:15:33 ion /kernel: inphy0:  10baseT, 10baseT-FDX, 100baseTX,
 100baseTX-FDX, auto
 Nov 21 11:15:33 ion /kernel: sym0: <875> port 0x1400-0x14ff mem
 0xfa201000-0xfa201fff,0xfa205000-0xfa2050ff
 irq 10 at device 13.0 on pci0
 Nov 21 11:15:33 ion /kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity
 checking
 Nov 21 11:15:33 ion /kernel: sym1: <875> port 0x1800-0x18ff mem
 0xfa202000-0xfa202fff,0xfa205400-0xfa2054ff
 irq 5 at device 13.1 on pci0
 Nov 21 11:15:33 ion /kernel: sym1: No NVRAM, ID 7, Fast-20, SE, parity
 checking
 Nov 21 11:15:33 ion /kernel: ahc0: <Adaptec 2944 Ultra SCSI adapter> port
 0x2000-0x20ff mem 0xfa203000-0xfa2
 03fff irq 11 at device 14.0 on pci0
 Nov 21 11:15:33 ion /kernel: aic7880: Ultra Wide Channel A, SCSI Id=7,
 16/253 SCBs
 Nov 21 11:15:33 ion /kernel: fxp1: <Intel Pro 10/100B/100+ Ethernet> port
 0x1060-0x107f mem 0xfa100000-0xfa1
 Nov 21 11:15:33 ion /kernel: inphy1: <i82555 10/100 media interface> on
 miibus1
 Nov 21 11:15:33 ion /kernel: inphy1:  10baseT, 10baseT-FDX, 100baseTX,
 100baseTX-FDX, auto
 Nov 21 11:15:33 ion /kernel: isab0: <Intel 82371AB PCI to ISA bridge> at
 device 18.0 on pci0
 Nov 21 11:15:33 ion /kernel: isa0: <ISA bus> on isab0
 Nov 21 11:15:33 ion /kernel: atapci0: <Intel PIIX4 ATA33 controller> port
 0x1050-0x105f at device 18.1 on pc
 i0
 Nov 21 11:15:33 ion /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Nov 21 11:15:34 ion /kernel: ata1: at 0x170 irq 15 on atapci0
 Nov 21 11:15:34 ion /kernel: uhci0: <Intel 82371AB/EB (PIIX4) USB
 controller> port 0x10c0-0x10df irq 5 at de
 vice 18.2 on pci0
 Nov 21 11:15:34 ion /kernel: usb0: <Intel 82371AB/EB (PIIX4) USB controller>
 on uhci0
 Nov 21 11:15:34 ion /kernel: usb0: USB revision 1.0
 Nov 21 11:15:34 ion /kernel: uhub0: Intel UHCI root hub, class 9/0, rev
 1.00/1.00, addr 1
 Nov 21 11:15:34 ion /kernel: uhub0: 2 ports with 2 removable, self powered
 Nov 21 11:15:34 ion /kernel: Timecounter "PIIX"  frequency 3579545 Hz
 Nov 21 11:15:34 ion /kernel: chip1: <Intel 82371AB Power management
 controller> port 0x1040-0x104f at device
  18.3 on pci0
 Nov 21 11:15:34 ion /kernel: pci0: <Cirrus Logic GD5480 SVGA controller> at
 20.0
 Nov 21 11:15:34 ion /kernel: orm0: <Option ROMs> at iomem
 0xc0000-0xc7fff,0xc8000-0xc87ff,0xc8800-0xc8fff,0x
 c9000-0xc9fff,0xca000-0xca7ff,0xca800-0xccfff on isa0
 Nov 21 11:15:34 ion /kernel: fdc0: <NEC 72065B or clone> at port
 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 Nov 21 11:15:34 ion /kernel: fdc0: FIFO enabled, 8 bytes threshold
 Nov 21 11:15:34 ion /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 Nov 21 11:15:34 ion /kernel: atkbdc0: <Keyboard controller (i8042)> at port
 0x60,0x64 on isa0
 Nov 21 11:15:34 ion /kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 on
 atkbdc0
 Nov 21 11:15:34 ion /kernel: kbd0 at atkbd0
 Nov 21 11:15:34 ion /kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
 Nov 21 11:15:34 ion /kernel: psm0: model Generic PS/2 mouse, device ID 0
 Nov 21 11:15:34 ion /kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df
 iomem 0xa0000-0xbffff on isa0
 Nov 21 11:15:34 ion /kernel: sc0: <System console> at flags 0x100 on isa0
 Nov 21 11:15:34 ion /kernel: sc0: VGA <16 virtual consoles, flags=0x300>
 Nov 21 11:15:34 ion /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on
 isa0
 Nov 21 11:15:34 ion /kernel: sio0: type 16550A
 Nov 21 11:15:34 ion /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
 Nov 21 11:15:34 ion /kernel: sio1: type 16550A
 Nov 21 11:15:34 ion /kernel: ppc0: <Parallel port> at port 0x378-0x37f irq 7
 on isa0
 Nov 21 11:15:34 ion /kernel: ppc0: Generic chipset (ECP/PS2/NIBBLE) in
 COMPATIBLE mode
 Nov 21 11:15:34 ion /kernel: ppc0: FIFO with 16/16/8 bytes threshold
 Nov 21 11:15:34 ion /kernel: plip0: <PLIP network interface> on ppbus0
 Nov 21 11:15:34 ion /kernel: lpt0: <Printer> on ppbus0
 Nov 21 11:15:34 ion /kernel: lpt0: Interrupt-driven port
 Nov 21 11:15:34 ion /kernel: ppi0: <Parallel I/O> on ppbus0
 Nov 21 11:15:34 ion /kernel: APIC_IO: Testing 8254 interrupt delivery
 Nov 21 11:15:34 ion /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2
 Nov 21 11:15:34 ion /kernel: SMP: AP CPU #1 Launched!
 Nov 21 11:15:34 ion /kernel: acd0: CDROM <TOSHIBA CD-ROM XM-6602B> at
 ata0-master PIO4
 Nov 21 11:15:34 ion /kernel: Waiting 15 seconds for SCSI devices to settle
 Nov 21 11:15:34 ion /kernel: sa0 at ahc0 bus 0 target 1 lun 0
 Nov 21 11:15:34 ion /kernel: sa0: <QUANTUM DLT7000 2560> Removable
 Sequential Access SCSI-2 device
 Nov 21 11:15:34 ion /kernel: sa0: 20.000MB/s transfers (10.000MHz, offset 8,
 16bit)
 Nov 21 11:15:34 ion /kernel: pass0 at ahc0 bus 0 target 0 lun 0
 Nov 21 11:15:34 ion /kernel: pass0: <ATL L500     6320000 0021> Removable
 Changer SCSI-2 device
 Nov 21 11:15:34 ion /kernel: pass0: 10.000MB/s transfers (10.000MHz, offset
 15)
 Nov 21 11:15:34 ion /kernel: Mounting root from ufs:/dev/mlxd0s1a
 Nov 21 11:15:34 ion /kernel: WARNING: / was not properly dismounted
 
 kernel config file (eg grep -v "^#" /usr/src/sys/i386/conf/ION)
 machine         i386
 cpu             I686_CPU
 ident           ION
 maxusers        0
 
 
 options         INET                    #InterNETworking
 options         FFS                     #Berkeley Fast Filesystem
 options         FFS_ROOT                #FFS usable as root device [keep
 this!]
 options         SOFTUPDATES             #Enable FFS soft updates support
 options         UFS_DIRHASH             #Improve performance on big
 directories
 options         CD9660                  #ISO 9660 Filesystem
 options         CD9660_ROOT             #CD-ROM usable as root, CD9660
 required
 options         PROCFS                  #Process filesystem
 options         COMPAT_43               #Compatible with BSD 4.3 [KEEP
 THIS!]
 options         SCSI_DELAY=15000        #Delay (in ms) before probing SCSI
 options         UCONSOLE                #Allow users to grab the console
 options         USERCONFIG              #boot -c editor
 options         VISUAL_USERCONFIG       #visual boot -c editor
 options         KTRACE                  #ktrace(1) support
 options         SYSVSHM                 #SYSV-style shared memory
 options         SYSVMSG                 #SYSV-style message queues
 options         SYSVSEM                 #SYSV-style semaphores
 options         P1003_1B                #Posix P1003_1B real-time extensions
 options         _KPOSIX_PRIORITY_SCHEDULING
 options         ICMP_BANDLIM            #Rate limit bad replies
 options         KBD_INSTALL_CDEV        # install a CDEV entry in /dev
 options         AHC_REG_PRETTY_PRINT    # Print register bitfields in debug
                                         # output.  Adds ~128k to driver.
 options         AHD_REG_PRETTY_PRINT    # Print register bitfields in debug
                                         # output.  Adds ~215k to driver.
 
 options         SMP                     # Symmetric MultiProcessor Kernel
 options         APIC_IO                 # Symmetric (APIC) I/O
 
 device          isa
 device          pci
 
 device          fdc0    at isa? port IO_FD1 irq 6 drq 2
 device          fd0     at fdc0 drive 0
 device          fd1     at fdc0 drive 1
 
 device          ata0    at isa? port IO_WD1 irq 14
 device          ata1    at isa? port IO_WD2 irq 15
 device          ata
 device          atadisk                 # ATA disk drives
 device          atapicd                 # ATAPI CDROM drives
 device          atapifd                 # ATAPI floppy drives
 device          atapist                 # ATAPI tape drives
 options         ATA_STATIC_ID           #Static device numbering
 
 device          ahc             # AHA2940 and onboard AIC7xxx devices
 device          sym             # NCR/Symbios Logic (newer chipsets)
 options         SYM_SETUP_LP_PROBE_MAP=0x40
                                 # Allow ncr to attach legacy NCR devices
 when
                                 # both sym and ncr are configured
 
 
 
 device          scbus           # SCSI bus (required)
 device          da              # Direct Access (disks)
 device          sa              # Sequential Access (tape etc)
 device          cd              # CD
 device          pass            # Passthrough device (direct SCSI access)
 
 
 device          mlx             # Mylex DAC960 family
 
 device          atkbdc0 at isa? port IO_KBD
 device          atkbd0  at atkbdc? irq 1 flags 0x1
 device          psm0    at atkbdc? irq 12
 
 device          vga0    at isa?
 
 
 device          sc0     at isa? flags 0x100
 
 
 device          npx0    at nexus? port IO_NPX irq 13
 
 device          apm0    at nexus? disable flags 0x20 # Advanced Power
 Management
 
 
 device          sio0    at isa? port IO_COM1 flags 0x10 irq 4
 device          sio1    at isa? port IO_COM2 irq 3
 
 device          ppc0    at isa? irq 7
 device          ppbus           # Parallel port bus (required)
 device          lpt             # Printer
 device          plip            # TCP/IP over parallel
 device          ppi             # Parallel port interface device
 
 
 device          de              # DEC/Intel DC21x4x (``Tulip'')
 device          em              # Intel PRO/1000 adapter Gigabit Ethernet
 Card (
 ``Wiseman'')
 device          txp             # 3Com 3cR990 (``Typhoon'')
 device          vx              # 3Com 3c590, 3c595 (``Vortex'')
 
 device          miibus          # MII bus support
 device          fxp             # Intel EtherExpress PRO/100B (82557, 82558)
 
 
 pseudo-device   loop            # Network loopback
 pseudo-device   ether           # Ethernet support
 pseudo-device   pty             # Pseudo-ttys (telnet etc)
 pseudo-device   md              # Memory "disks"
 pseudo-device   gif             # IPv6 and IPv4 tunneling
 pseudo-device   faith   1       # IPv6-to-IPv4 relaying (translation)
 
 pseudo-device   bpf             #Berkeley packet filter
 
 device          uhci            # UHCI PCI->USB interface
 device          ohci            # OHCI PCI->USB interface
 device          usb             # USB Bus (required)
 device          ugen            # Generic
 device          uhid            # "Human Interface Devices"
 device          ukbd            # Keyboard
 device          ulpt            # Printer
 device          umass           # Disks/Mass storage - Requires scbus and da
 device          ums             # Mouse
 device          uscanner        # Scanners
 device          urio            # Diamond Rio MP3 Player
 
 

From: Yar Tikhiy <yar@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org, seagull@aracnet.com
Cc: jlemon@FreeBSD.org
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Fri, 31 Jan 2003 19:53:19 +0300

 I'd like to add to this PR's audit trail that I was observing "fxp0:
 device timeout" errors in 5.0-RELEASE with simple patterns of high
 traffic.  I was ready to write a PR when I tried changing the
 motherboard and the problem disappeared.  So I'm afraid this problem
 might have to do more with buggy hardware than with the fxp driver.
 
 -- 
 Yar

From: Yar Tikhiy <yar@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org, seagull@aracnet.com
Cc: jlemon@FreeBSD.org
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Fri, 31 Jan 2003 21:26:46 +0300

 UPDATE: After I'd installed the old motherboard back and played
 with its BIOS settings (turned off tricky PCI acceleration features,)
 I could see the "fxp0: device timeout" message no longer!
 
 I'd rather close this PR.
 
 -- 
 Yar

From: "Seagull" <seagull@aracnet.com>
To: yar@FreeBSD.org (Yar Tikhiy)
Cc: freebsd-gnats-submit@FreeBSD.org, jlemon@FreeBSD.org
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Mon, 3 Feb 2003 06:25:28 -0800 (PST)

 > UPDATE: After I'd installed the old motherboard back and played
 > with its BIOS settings (turned off tricky PCI acceleration features,)
 > I could see the "fxp0: device timeout" message no longer!
 > 
 > I'd rather close this PR.
 
 I am not convinced that you have found the root cause for this problem.
 Enabling "tricky PCI acceleration features" may make the system more
 susceptible to this issue, but I see no reason to believe that this is the
 source of the problem.
 
 My system is built around an Intel L440GX+ motherboard, and has only
 one expansion card: an Intel PCI NIC to provide a network interface in
 addition to the on-board LAN.  Intel motherboards are known for their
 conservatism and stability, particularly in the server and workstation
 lines.  There are no options in the BIOS for "PCI acceleration" or other
 envelope-pushing system tuning.
 
 And, there is still the issue that this device timeout problem first
 became noticeable in 4.6-RELEASE, on the same hardware configuration.
 
 Now, as per my reports in the PR, this problem was _alleviated_ by
 something in 4.6.2-RELEASE (the frequency of occurance is much lower),
 but it most definitely has not gone away.
 
 
 Cheers,
 John
 
 -- 
                                 \                carpe cavy!
 seagull @ aracnet.com            \
 http://www.aracnet.com/~seagull/  \        (seize the guinea pig!)

From: Gary Hanson <garyh@agora.rdrop.com>
To: freebsd-gnats-submit@FreeBSD.org, seagull@aracnet.com
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained
 network activity
Date: Fri, 18 Apr 2003 12:33:53 -0700 (PDT)

 Also seen on 4.8-RELEASE and 5.0-RELEASE; very easy and quick to reproduce.
 
 System is an Intel N440BX dual proc mobo with integrated 82557 (Pro100B) NIC on
 a dedicated IRQ.
 
 On SMP kernels, I could ping for as long as I wanted to, even with large
 (64000 byte) packets. Didn't try flood ping though. But try to do some real I/O
 like an ftp or Samba file copy and the transfer would die almost immediately and
 the console would start reporting fxp: device timeout messages every few seconds,
 even after disconnecting the ethernet cable. The system was then in a very weird
 state; it was acting like it was very busy (sluggish) but wasn't totally 
 unresponsive, and it could not be shutdown properly - that would seem to hang (or
 I wasn't willing to wait long enough).
 
 With a single-processor kernel, 4.8 and 5.0 both had no problems.
 
 The hardware is good; it works fine with SMP OSes from Redmond; I'll try a
 penguin 'OS' for amusement purposes. [The penguin 'e100' driver is vastly better
 than the rather old FreeBSD fxp driver, but I'm not competent to adapt/port/steal
 it.]

From: "Joshua Sargent" <jsargent@meridianitsolutions.com>
To: "seagull@aracnet.com" <freebsd-gnats-submit@FreeBSD.org,>,
	<freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Mon, 14 Jul 2003 13:58:20 -0500

 Just wanted to submit my experience here.  I've got a Tyan Tiger MP dual =
 proc motherboard with an Intel 82557/8/9 EtherExpress Pro/100(B) card =
 (this is a dual-port 10/100 card, with the dual-port daughter-card added =
 to make it a 4-port card).  I experience similar problems as reported by =
 other users when I try to do any real i/o (not specific to any type of =
 traffic), although I can ping to my heart's content with excellent =
 response times.  I'm running a fresh 5.1-release install with the =
 GENERIC kernel (so SMP is not yet enabled).  I don't know what to revert =
 to since I've noticed people posting similar problems in 4.x.  I'll be =
 glad to provide more detail upon request.
 
 Josh Sargent

From: Dominik Brettnacher <domi@saargate.de>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errorss duringg heavy, sustained
 network activity
Date: Mon, 11 Aug 2003 13:08:15 +0200 (CEST)

 Hi there,
 
 I am experiencing similar errors. As far as I can see, PR #50683 is
 related.
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/50683
 
 -- 
 Yours,
 
 Dominik
 

From: ceo@privhosting.com
To: freebsd-gnats-submit@FreeBSD.org, seagull@aracnet.com
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Thu, 23 Oct 2003 16:08:51 +0300

   I've faced with the same problem on 4.8-RELEASE
 
   fxp0 is Intel Pro 10/100B/100+ Ethernet
   
   I've tried 3 different options:
   no SMP with device_polling
   no SMP without device_polling
   SMP without device_polling
 
   Each configuration gives device timeout on high packet flow.  
 

From: "Thomas Sandford" <freebsduser@paradisegreen.co.uk>
To: <freebsd-gnats-submit@FreeBSD.org>, <seagull@aracnet.com>
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Date: Sun, 7 Mar 2004 18:02:02 -0000

 Another datapoint:
 
 I'm seeing this problem under 4.9-RELEASE on a Compaq Proliant 1600.
 
 The usual trigger in my case is copies of large files using Samba.
 
 dmesg extract:
 
 fxp0: <Intel 82559 Pro/100 Ethernet> port 0x2800-0x283f mem
 0xc6e00000-0xc6efffff,0xc6dfd000-0xc6dfdfff irq 15 at device 11.0 on pci1
 
 The kernel is GENERIC with the following changes (diff -u extracts):
 -cpu            I386_CPU
 -cpu            I486_CPU
 -cpu            I586_CPU
 ...
 +options        SMP
 +options        APIC_IO
 
 -- 
 Thomas Sandford
 

From: "Doug Poland" <doug@polands.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/40274: "fxp: device timeout" errors during heavy,
      sustained network activity
Date: Fri, 17 Sep 2004 10:42:43 -0500 (CDT)

 Still a problem with 4.10-STABLE with SMP kernel:
 
 Running Compaq ProLiant DL380 with dual Intel(R) Pentium(R) III CPUs.  NIC
 in question is:
 
 fxp0@pci0:2:0:  class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08
 hdr=0x00
     vendor   = 'Intel Corporation'
     device   = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
     class    = network
     subclass = ethernet
 
 
 Also on a problem on latest 5.3-BETA4 environment.  Except here, it occurs
 more frequently.
 
 
 -- 
 Regards,
 Doug
 

From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/40274: [fxp] "fxp: device timeout" errors during heavy,
	sustained network activity (still on 5.4)
Date: Mon, 04 Jun 2007 18:51:51 +0100

 Hi,
 
 [sent to everyone in the PR who were still experiencing the issue after
 April 2003]
 
 Have any of you seen this problem with a more recent version of FreeBSD?
 Testing on 5.5 or 6.x would be sufficient.  If so, please respond with
 the output of both "uname -a" and "pciconf -l" in order to try and start
 diagnosing exactly which systems are affected.  Please reply, leaving
 bug-followup cc'd.
 
 Thanks,
 
 Gavin

From: Dominik Brettnacher <domi@saargate.de>
To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/40274: [fxp] "fxp: device timeout" errors during heavy,
 sustained network activity (still on 5.4)
Date: Mon, 4 Jun 2007 19:59:17 +0200 (CEST)

 On Mon, 4 Jun 2007, Gavin Atkinson wrote:
 
 > Have any of you seen this problem with a more recent version of FreeBSD?
 
 Gavin,
 
 I haven't seen this problem for a few years now.
 
 -- 
 Dominik
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jun 12 04:45:30 UTC 2007 
State-Changed-Why:  
The most recent response indicated that this was solved. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=40274 
>Unformatted:
