Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Jan 2006 10:55:15 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Ganbold <ganbold@micom.mng.net>
Cc:        freebsd-stable@FreeBSD.org
Subject:   Re: fxp0: device timeout and sk0: watchdog timeout problems
Message-ID:  <20060118015515.GB39792@rndsoft.co.kr>
In-Reply-To: <7.0.0.16.2.20060118090616.04209af8@micom.mng.net>
References:  <7.0.0.16.2.20060118090616.04209af8@micom.mng.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 18, 2006 at 09:27:09AM +0800, Ganbold wrote:
 > Hi,
 > 
 > I'm having problem with sk and fxp NIC. I get fxp0: device timeout 
 > and sk0: watchdog timeout problems and network stops responding.
 > 
 > gw# uname -an
 > FreeBSD xx.xx.xx 6.0-STABLE FreeBSD 6.0-STABLE #2: Mon Jan 16 
 > 12:09:59 UTC 2006     otgonpurev@xx.xx.xx:/usr/obj/usr/src/sys/GATEWAY  i386
 > 
 > Message log:
 > Jan 17 18:15:22 gw kernel: fxp0: device timeout
 > Jan 17 18:15:25 gw kernel: sk0: watchdog timeout
 > Jan 17 18:15:25 gw kernel: sk0: link state changed to DOWN
 > Jan 17 18:15:41 gw kernel: sk0: watchdog timeout
 > Jan 17 18:15:53 gw kernel: fxp0: device timeout
 > Jan 17 18:16:29 gw kernel: fxp0: device timeout
 > Jan 17 18:17:07 gw kernel: fxp0: device timeout
 > Jan 17 18:17:19 gw kernel: sk0: watchdog timeout
 > Jan 17 18:17:42 gw kernel: fxp0: device timeout
 > Jan 17 18:17:59 gw kernel: sk0: watchdog timeout
 > Jan 17 18:18:19 gw kernel: sk0: watchdog timeout
 > Jan 17 18:18:53 gw kernel: sk0: watchdog timeout
 > 
 > pciconf -lv output:
 > 
 > skc0@pci0:1:0:  class=0x020000 card=0x4c001186 chip=0x4c001186 
 > rev=0x11 hdr=0x00
 >     vendor   = 'D-Link System Inc'
 >     device   = 'DGE-530T Gigabit Ethernet Adapter'
 >     class    = network
 >     subclass = ethernet
 > fxp0@pci1:2:0:  class=0x020000 card=0x01f11014 chip=0x12298086 
 > rev=0x0c hdr=0x00
 >     vendor   = 'Intel Corporation'
 >     device   = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
 >     class    = network
 >     subclass = ethernet
 > 
 > dmesg.boot:
 > 
 > Copyright (c) 1992-2005 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 6.0-STABLE #2: Mon Jan 16 12:09:59 UTC 2006
 >     otgonpurev@xx.xx.xx:/usr/obj/usr/src/sys/GATEWAY
 > ACPI APIC Table: <IBM    SERMOHIC>
 > Timecounter "i8254" frequency 1193182 Hz quality 0
 > CPU: Pentium III/Pentium III Xeon/Celeron (548.54-MHz 686-class CPU)
 >   Origin = "GenuineIntel"  Id = 0x673  Stepping = 3
 >   Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
 > real memory  = 536854528 (511 MB)
 > avail memory = 515850240 (491 MB)
 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 >  cpu0 (BSP): APIC ID:  1
 >  cpu1 (AP): APIC ID:  0
 > MADT: Forcing active-low polarity and level trigger for SCI
 > ioapic0 <Version 1.1> irqs 0-23 on motherboard
 > npx0: [FAST]
 > npx0: <math processor> on motherboard
 > npx0: INT 16 interface
 > acpi0: <IBM SERMOHIC> on motherboard
 > acpi0: Power Button (fixed)
 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xfe88-0xfe8b on acpi0
 > cpu0: <ACPI CPU> on acpi0
 > cpu1: <ACPI CPU> on acpi0
 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
 > pci0: <ACPI PCI bus> on pcib0
 > skc0: <D-Link DGE-530T Gigabit Ethernet> port 0x2000-0x20ff mem 
 > 0xfebfc000-0xfebfffff irq 18 at device 1.0 on pci0
 > skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x1)
 > sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
 > sk0: Ethernet address: 00:11:95:e1:7d:16
 > miibus0: <MII bus> on sk0
 > e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
 > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 
 > 1000baseTX-FDX, auto
 > ahc0: <Adaptec aic7895 Ultra SCSI adapter> port 0x2200-0x22ff mem 
 > 0xfebfb000-0xfebfbfff irq 16 at device 6.0 on pci0
 > ahc1: [GIANT-LOCKED]
 > aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
 > pci0: <display, VGA> at device 10.0 (no driver attached)
 > isab0: <PCI-ISA bridge> port 0xfe00-0xfe0f at device 15.0 on pci0
 > isa0: <ISA bus> on isab0
 > atapci0: <GENERIC ATA controller> port 
 > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 18 at device 15.1 on 
 > pci0
 > ata0: <ATA channel 0> on atapci0
 > ata1: <ATA channel 1> on atapci0
 > ohci0: <OHCI (generic) USB controller> mem 0xff700000-0xff700fff irq 
 > 18 at device 15.2 on pci0
 > ohci0: [GIANT-LOCKED]
 > usb0: OHCI version 1.0, legacy support
 > usb0: <OHCI (generic) USB controller> on ohci0
 > usb0: USB revision 1.0
 > uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 > uhub0: 2 ports with 2 removable, self powered
 > pcib1: <ACPI Host-PCI bridge> on acpi0
 > pci1: <ACPI PCI bus> on pcib1
 > fxp0: <Intel 82550 Pro/100 Ethernet> port 0x4b00-0x4b3f mem 
 > 0xc0fdf000-0xc0fdffff,0xc0fa0000-0xc0fbffff irq 19 at device 2.0 o
 > n pci1
 > miibus1: <MII bus> on fxp0
 > inphy0: <i82555 10/100 media interface> on miibus1
 > inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 > fxp0: Ethernet address: 00:03:47:e0:64:3c
 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
 > atkbd0: <AT Keyboard> irq 1 on atkbdc0
 > kbd0 at atkbd0
 > atkbd0: [GIANT-LOCKED]
 > psm0: <PS/2 Mouse> irq 12 on atkbdc0
 > psm0: [GIANT-LOCKED]
 > psm0: model Generic PS/2 mouse, device ID 0
 > fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
 > fdc0: [FAST]
 > fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 > ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0
 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
 > ppbus0: <Parallel port bus> on ppc0
 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on 
 > acpi0
 > sio0: type 16550A
 > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
 > sio1: type 16550A
 > pmtimer0 on isa0
 > orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xcd000-0xce7ff on isa0
 > sc0: <System console> at flags 0x100 on isa0
 > sc0: VGA <16 virtual consoles, flags=0x300>
 > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 > Timecounters tick every 1.000 msec
 > IP Filter: v4.1.8 initialized.  Default = pass all, Logging = enabled
 > ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding 
 > disabled, default to accept, logging limited to 100 packets/
 > entry by default
 > Waiting 5 seconds for SCSI devices to settle
 > ses0 at ahc1 bus 0 target 14 lun 0
 > ses0: <SDR GEM200 2> Fixed Processor SCSI-2 device
 > ses0: 3.300MB/s transfers
 > ses0: SAF-TE Compliant Device
 > da0 at ahc1 bus 0 target 0 lun 0
 > da0: <IBM DPSS-318350M S96H> Fixed Direct Access SCSI-3 device
 > da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing 
 > Enabled
 > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
 > SMP: AP CPU #1 Launched!
 > Trying to mount root from ufs:/dev/da0s1a
 > 
 > ifconfig output:
 > 
 > sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >         options=b<RXCSUM,TXCSUM,VLAN_MTU>
 >         inet 175.176.1.11 netmask 0xffff0000 broadcast 175.176.255.255
 >         ether 00:11:95:e1:7d:16
 >         media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
 >         status: active
 > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >         options=b<RXCSUM,TXCSUM,VLAN_MTU>
 >         inet 202.72.245.xxx netmask 0xfffffff0 broadcast 202.72.245.xxx
 >         ether 00:03:47:e0:64:3c
 >         media: Ethernet autoselect (100baseTX <full-duplex>)
 >         status: active
 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
 >         inet 127.0.0.1 netmask 0xff000000
 > 
 > I used new if_sk codes from Pyun YongHyeon but after 2 days I got 
 > same problem device timeout.
 > fxp is also timing out and I don't know why.
 > Any idea?
 > 

If sk(4) is the cause of problem fxp wouldn't be affected.
Of course it's possible for sk(4) to corrupt kernel memory structure
but the possibility is low. While fixing sk(4) I pushed sk(4) to the
limit on sparc64. I never met such timeouts.

atm I have no clue. How about updated sk(4)?
http://people.freebsd.org/~yongari/sk/if_sk.c
http://people.freebsd.org/~yongari/sk/if_skreg.h

Disabling sk(4) remedy your issue?
-- 
Regards,
Pyun YongHyeon



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