Date: Wed, 07 Jun 2000 23:31:49 +0200 From: Palle Girgensohn <girgen@partitur.se> To: freebsd-questions@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: fxp0: device timeout - reboot required Message-ID: <393EBF45.B67A6655@partitur.se>
next in thread | raw e-mail | index | archive | help
Hi!
I've seen it happen twice in a weeks time on our server, that
has always been rock stable before:
fxp0: device timeout (many many times, repeated in syslog)
The machine does not answer to ping.
This time, it think it started during a secure copy (scp(1)) of
a ~70MB file over my cable modem (128 kbit/s upstream) to our
file server, which is another freebsd machine (4-stable) on the
same network. (I mention this since I found other people have
had problems when moving large files.)
ifconfig fxp0 down && sleep 2 && ifconfig fxp0 up
did *not* help!
neither did ifconfig fxp0 delete && ifconfig fxp0 inet ...
When this happened last week, we switched cables and hub port.
This didn't seem to help then, and since it happened again,
this is probably not the case, right?
The system was very sluggish when running from the console last
time, which might be due to syslog working hard fetch all the
timeouts? I dunno what happened this time. My colleague did the
hands-on.
Anyway, the fastest solution I could come up with was
rebooting! It is amazing that it actually helped; I suspect
this indicates software problems (or more likely, a
combination?).
It's an SMP machine, intel dual server motherboard (bx, if
memory server me), FreeBSD 3.3-RELEASE, intel etherexpress
10/100B running half duplex 100Mbit/s.
Will upgrading to 3.4-RELEASE help? I didn't see anything
interesting in the if_fxp.c diffs, but there might be stuff
done in other areas?
Upgrading to 4.0 is not really an option at the moment.
Side note: I have seen a few single device timeouts the weeks
before the first major incident. I asked on the questions list,
and got the advice to check the cabling. I didn't find the time
to do this before the first incident.
--
Palle
Here's a dmesg:
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights
reserved.
FreeBSD 3.3-RELEASE #0: Thu Oct 7 05:27:00 CEST 1999
root@:/usr/src/sys/compile/PUKA
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (686-class CPU)
Origin = "GenuineIntel" Id = 0x652 Stepping = 2
Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory = 268435456 (262144K bytes)
avail memory = 258318336 (252264K bytes)
Programming 24 pins in IOAPIC #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 0xc02a8000.
Pentium Pro MTRR support enabled
Probing for devices on PCI bus 0:
chip0: <Intel 82443BX host to PCI bridge (AGP disabled)> rev
0x02 on pci0.0.0
ncr0: <ncr 53c875 fast20 wide scsi> rev 0x37 int a irq 11 on
pci0.13.0
ncr1: <ncr 53c875 fast20 wide scsi> rev 0x37 int b irq 10 on
pci0.13.1
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a
irq 5 on pci0.15.0
fxp0: Ethernet address 00:a0:c9:d4:38:fa
chip1: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.18.0
chip2: <Intel 82371AB Power management controller> rev 0x02 on
pci0.18.3
vga0: <Cirrus Logic model 00bc VGA-compatible display device>
rev 0x23 on pci0.20.0
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 not found
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
Waiting 3 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
changing root device to da0s1a
da0 at ncr0 bus 0 target 8 lun 0
da0: <SEAGATE ST39102LW 0005> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
Queueing Enabled
da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?393EBF45.B67A6655>