Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Jul 2002 13:10:42 -0700 (PDT)
From:      John Mechalas <seagull@aracnet.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   i386/40274: "fxp: device timeout" errors during heavy, sustained network activity
Message-ID:  <200207062010.g66KAg9e066651@www.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         40274
>Category:       i386
>Synopsis:       "fxp: device timeout" errors during heavy, sustained network activity
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 06 13:20:01 PDT 2002
>Closed-Date:
>Last-Modified:
>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:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207062010.g66KAg9e066651>