Date: Sat, 8 Dec 2001 19:10:46 +0000 (GMT) From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net> To: net@freebsd.org, smp@freebsd.org Subject: dc watchdog timeout on 4.4-R Message-ID: <Pine.LNX.4.20.0112081908500.5497-100000@www.everquick.net>
next in thread | raw e-mail | index | archive | help
Greetings all,
Sorry for the hefty cross-post... I've been digging through
archives, and it seems that there was talk of this on -current
late October of 2000, including speculation that this was an
SMPng issue.
I'm running a D-Link DFE570TX four-port dc (21143xx, where xx is
TD if memory serves) on a dual-PII Micronics PTSAM motherboard.
See /var/run/dmesg.boot following .signature for details.
After my machine runs successfully for some while, I receive
continuous "watchdog timeout" messages on a 10baseT/UTP HDX dc
port. It doesn't seem to happen on 100baseTX FDX ports; however,
being an infrequent event, I cannot vouch for the statistical
validity of this claim.
Once I receive these timeouts, "netstat -I dc3 -w 1" shows an
output error each time I try to send traffic. A reboot is the
only "cure" that I have found... i.e., it's not a cable issue.
I don't recall experiencing this 4.3-R; I believe that I used the
same motherboard for three months under 4.3-R, and that this is
a new event since upgrading to 4.4-R. However, I'm a bit fuzzy
on this, too.
Anyone have any ideas?
Please keep me CCed. I'm not currently subscribed. My email
address is valid. However, please un-CC lists as appropriate --
if this is an SMP issue, I don't want to chew up -net, or vice
versa. Again, I apologize for the large crosspost, but it's
unclear to me which avenue is the correct one...
TIA,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Copyright (c) 1992-2001 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.4-RELEASE #1: Wed Oct 31 14:19:51 GMT 2001
root@kaetzchen.brotsman.test:/usr/src/sys/compile/KAETZCHEN
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x634 Stepping = 4
Features=0x80fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX>
real memory = 134217728 (131072K bytes)
avail memory = 127569920 (124580K 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 0xc0305000.
Pentium Pro MTRR support enabled
Using $PIR table, 6 entries at 0xc00f6380
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
IOAPIC #0 intpin 19 -> irq 2
pci0: <PCI bus> on pcib0
isab0: <Intel 82371AB PCI to ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xfcd0-0xfcdf at device 1.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 1.2 irq 2
Timecounter "PIIX" frequency 3579545 Hz
chip0: <Intel 82371AB Power management controller> port 0x2180-0x218f at device 1.3 on pci0
sym0: <875> port 0xf800-0xf8ff mem 0xfebfe000-0xfebfefff,0xfebff800-0xfebff8ff irq 16 at device 17.0 on pci0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
sym0: SCAN AT BOOT disabled for targets 1 2 3 4 5 6 8 9 10 11 12 13 14 15.
sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15.
pci0: <Matrox MGA Millennium II 2164W graphics accelerator> at 18.0 irq 17
pcib2: <DEC 21152 PCI-PCI bridge> at device 19.0 on pci0
pci1: <PCI bus> on pcib2
dc0: <Intel 21143 10/100BaseTX> port 0xec00-0xec7f mem 0xfdfff800-0xfdfffbff irq 2 at device 4.0 on pci1
dc0: Ethernet address: 00:80:c8:f8:7b:50
miibus0: <MII bus> on dc0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc1: <Intel 21143 10/100BaseTX> port 0xe880-0xe8ff mem 0xfdfff400-0xfdfff7ff irq 18 at device 5.0 on pci1
dc1: Ethernet address: 00:80:c8:f8:7b:51
miibus1: <MII bus> on dc1
ukphy1: <Generic IEEE 802.3u media interface> on miibus1
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc2: <Intel 21143 10/100BaseTX> port 0xe800-0xe87f mem 0xfdfff000-0xfdfff3ff irq 17 at device 6.0 on pci1
dc2: Ethernet address: 00:80:c8:f8:7b:52
miibus2: <MII bus> on dc2
ukphy2: <Generic IEEE 802.3u media interface> on miibus2
ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc3: <Intel 21143 10/100BaseTX> port 0xe480-0xe4ff mem 0xfdffec00-0xfdffefff irq 16 at device 7.0 on pci1
dc3: Ethernet address: 00:80:c8:f8:7b:53
miibus3: <MII bus> on dc3
ukphy3: <Generic IEEE 802.3u media interface> on miibus3
ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
atapci1: <Generic PCI ATA controller> irq 0 at device 25.1 on pci0
atapci1: Busmastering DMA not supported
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.2
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.3
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.4
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.5
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.6
pci0: <unknown card> (vendor=0xffff, dev=0x0000) at 25.7
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xca7ff 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
fd1: <1200-KB 5.25" drive> on fdc0 drive 1
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
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
unknown: <PNP0501> can't assign resources
unknown: <PNP0501> can't assign resources
unknown: <PNP0401> can't assign resources
unknown: <PNP0700> can't assign resources
unknown: <PNP0303> can't assign resources
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
DUMMYNET initialized (010124)
IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging disabled
SMP: AP CPU #1 Launched!
ad0: 3079MB <Maxtor 90320D2> [6256/16/63] at ata0-master UDMA33
Waiting 5 seconds for SCSI devices to settle
sym0: suspicious SCSI data while resetting the BUS.
sym0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x7fc0100, expecting 0x100
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
Mounting root from ufs:/dev/ad0s1a
da0 at sym0 bus 0 target 0 lun 0
da0: <COMPAQPC FIREBALL1080S 1Q09> Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 8)
da0: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C)
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.20.0112081908500.5497-100000>