Re: bad SK NICs ??
Hi, I have also had quite some issues with this sk driver. We are also using the D-LINK DGE-530T cards, and every now and then, we get a watchdog timeout. I can be 99% sure that it is not a cabling or switching problem because the problem stops when I switch to another card (even a xl). If necessary, I can provide more information or even send one NIC over for testing purposes. Best regards, ebl
Re: bad SK NICs ??
I hate to add to the "Me Too" crowd about this issue, but I myself
have been experiencing this also. I was running a snapshot of 3.7
where the machine would crash pretty hard from it after the watchdog
timeout appeared a few times over the period of a few days. Now,
though, with 3.9 snapshot I see the timeouts but it hasn't crashed yet
from it:
As you can see from the dmesg, my network card is the lesser expensive
Linksys EG1032 marvel based card.
OpenBSD 3.9-current (GENERIC) #702: Thu Apr 20 00:36:31 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 2.40GHz ("GenuineIntel" 686-class) 2.43 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM
real mem = 1073217536 (1048064K)
avail mem = 811261952 (792248K)
using 4278 buffers containing 215060480 bytes (210020K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(ed) BIOS, date 11/10/03, BIOS32 rev. 0 @ 0xf1e30
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
apm0: flags b0102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x24b2
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf23d0/224 (12 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xc800 0xd/0x7c00!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82845G/GL" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82845G/GL/GV/GE/PE AGP" rev 0x02
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce2 MX" rev 0xb2
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x02: irq 12
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x02: irq 3
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x02: irq 14
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x02: irq 11
usb3 at ehci0: USB revision 2.0
uhub3 at usb3
uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
ppb1 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0x82
pci2 at ppb1 bus 2
"VIA VT6306 FireWire" rev 0x80 at pci2 dev 3 function 0 not configured
pciide0 at pci2 dev 4 function 0 "Promise PDC20376" rev 0x02: DMA
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6
pciide0: using irq 11 for native-PCI interrupt
bge0 at pci2 dev 5 function 0 "Broadcom BCM5702X" rev 0x02, BCM5703 A2
(0x1002): irq 10, address 00:e0:18:bf:77:eb
brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
skc0 at pci2 dev 10 function 0 "Linksys EG1032" rev 0x12, Marvell
Yukon (0x1): irq 5
sk0 at skc0 port A, address 00:0c:41:eb:c4:35
eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x02
pciide1 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x02: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
pciide1: no compatibility interrupt for use by channel 0
atapiscsi0 at pciide1 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask fb4d netmask ff6d ttymask ffef
pctr: user-level cycle counter enabled
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: bad SK NICs ??
Ive also had those watchdog problems with sk(4) on 3.9. They did appear on 3.8 but not as often. It doesnt seem to matter what i do to get those, they are not coming when i use much traffic but they seem to just appear at random. My card is; skc0 at pci0 dev 15 function 0 "3Com 3c940" rev 0x10, Marvell Yukon (0x1): irq 10 sk0 at skc0 port A, address 00:0a:5e:5c:58:ec
Re: bad SK NICs ??
Hi Reyk, Thank you so much for your help and interest. The machine in question is working as a anti-spam bridge. It was passing traffic normally until the problem occur. After that the conectivity was lost between the internal LAN and the external world. It went operational last friday at 21:12 (GMT-3). The problem occured this monday at 7:09am (GMT-3), as shown in the log entries below. So, it took about 2 days and half. May 26 21:12:55 wall savecore: no core dump ... May 29 07:09:08 wall /bsd: sk0: watchdog timeout I have had similar problems with other machines running OpenBSD 3.6, 3.7 and 3.8. I do not know if it helps, but what is common in all these cases is Intel/Pentium IV and D-LINK DGE-530T. I only used brand new NICs and machines. On the 3.7 machine, it did happen so often that I decided not to use the NIC and switched to a on-board fxp NIC. The problem simply disappeard. This is just a small extract from the log files. Sep 5 18:45:31 euler /bsd: sk0: watchdog timeout Sep 6 13:00:45 euler /bsd: sk0: watchdog timeout Sep 7 02:23:34 euler /bsd: sk0: watchdog timeout Sep 7 03:10:10 euler /bsd: sk0: watchdog timeout Sep 7 15:42:48 euler /bsd: sk0: watchdog timeout Sep 7 15:43:46 euler /bsd: sk0: watchdog timeout Sep 7 20:01:27 euler /bsd: sk0: watchdog timeout Sep 9 01:43:26 euler /bsd: sk0: watchdog timeout Sep 11 19:10:22 euler /bsd: sk0: watchdog timeout Sep 12 11:28:39 euler /bsd: sk0: watchdog timeout Sep 12 15:38:22 euler /bsd: sk0: watchdog timeout Sep 12 16:13:17 euler /bsd: sk0: watchdog timeout Sep 14 09:24:31 euler /bsd: sk0: watchdog timeout Sep 14 10:57:58 euler /bsd: sk0: watchdog timeout Sep 15 01:17:10 euler /bsd: sk0: watchdog timeout Sep 15 02:45:10 euler /bsd: sk0: watchdog timeout Sep 15 11:21:36 euler /bsd: sk0: watchdog timeout Sep 15 18:42:28 euler /bsd: sk0: watchdog timeout Sep 16 00:35:03 euler /bsd: sk0: watchdog timeout Sep 16 08:52:16 euler /bsd: sk0: watchdog timeout Sep 17 15:35:08 euler /bsd: sk0: watchdog timeout Sep 17 17:36:36 euler /bsd: sk0: watchdog timeout Sep 17 19:02:43 euler /bsd: sk0: watchdog timeout Sep 18 17:45:01 euler /bsd: sk0: watchdog timeout Sep 18 23:35:27 euler /bsd: sk0: watchdog timeout Sep 19 15:26:31 euler /bsd: sk0: watchdog timeout Sep 19 19:01:58 euler /bsd: sk0: watchdog timeout On the 3.8 machine, it did happen less often. But the machine in question is not traffic intensive at all. So, I can not tell much: Dec 7 16:13:13 dantzig /bsd: sk0: watchdog timeout Feb 3 16:23:56 dantzig /bsd: sk0: watchdog timeout Mar 28 19:59:01 dantzig /bsd: sk0: watchdog timeout In fact, the machine where this problem is less often is the one running 3.6: May 6 12:54:31 wall /bsd: sk0: watchdog timeout Jul 26 16:35:51 wall /bsd: sk1: watchdog timeout Aug 5 00:58:44 wall /bsd: sk1: watchdog timeout Aug 22 09:57:02 wall /bsd: sk0: watchdog timeout Nov 24 12:38:17 wall /bsd: sk0: watchdog timeout Feb 5 00:08:07 wall /bsd: sk0: watchdog timeout May 29 15:48:10 wall /bsd: sk0: watchdog timeout Please, let me know if you need any additional information. Best regards, Josi - Original Message - From: "Reyk Floeter" To: "Jose Fragoso" Subject: Re: bad SK NICs ?? Date: Mon, 29 May 2006 23:28:54 +0200 hi, On Mon, May 29, 2006 at 09:58:44AM -0500, Jose Fragoso wrote: > A while ago, a message was posted in this list stating the sk > based NICs were supposed to be good in performance and stability. > Now, I have already had quite a few problems with D-LINK DGE-530T > when used on Intel motherboards. On several ocasions, these NICs > ended up causing WATCHDOG TIMEOUT. So, I would like to know if > there is any known bad revision of one of this cards, or if there > is any kind of test a can perform to see if there is a real > problem with the NIC. Apparently, it is not a problem with the > NIC itself, since I have used the same NIC that behaved badly on > one board, and it behaved all right on another. The NICs show as could you try this with openbsd 3.8? (there have been some changes in the sk driver for the 3.9 release) how long did the sk work before you got the watchdog timeouts? could you pass any traffic? reyk -- ___ Play 100s of games for FREE! http://games.mail.com/
Re: bad SK NICs ??
hi,
On Mon, May 29, 2006 at 09:58:44AM -0500, Jose Fragoso wrote:
> A while ago, a message was posted in this list stating the sk based NICs were
> supposed to be good in performance and stability.
> Now, I have already had quite a few problems with D-LINK DGE-530T when used
> on Intel motherboards. On several ocasions,
> these NICs ended up causing WATCHDOG TIMEOUT. So, I would like to know if
> there is any known bad revision of one of this
> cards, or if there is any kind of test a can perform to see if there is a
> real problem with the NIC. Apparently,
> it is not a problem with the NIC itself, since I have used the same NIC that
> behaved badly on one board, and it behaved
> all right on another. The NICs show as
>
could you try this with openbsd 3.8? (there have been some changes in
the sk driver for the 3.9 release)
how long did the sk work before you got the watchdog timeouts?
could you pass any traffic?
reyk
> skc0 at pci2 dev 2 function 0 "D-Link Systems DGE-530T" rev 0x11, Marvell
> Yukon (0x1): irq 3
> sk0 at skc0 port A, address 00:13:46:72:00:24
> eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
>
> in the dmesg (which is attached below). I am asking because I read another
> message with complaints about this sk
> driver. Only it was:
>
> skc0 at pci0 dev 14 function 0 "Schneider & Koch SK-9821 v2.0" rev 0x12:
> irq 10
> skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3 (0x7)
> sk0 at skc0 port A: address 00:0c:46:46:50:ec
> eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5
>
> Any help will be appreciated.
>
> Thanks in advance.
>
> Regards,
>
> Josi
>
>
>
>
> OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) 4 CPU 1.80GHz ("GenuineIntel" 686-class) 1.80 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SB
> F,CNXT-ID
> real mem = 1072410624 (1047276K)
> avail mem = 971837440 (949060K)
> using 4278 buffers containing 53723136 bytes (52464K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(00) BIOS, date 04/02/04, BIOS32 rev. 0 @ 0xf0010
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 30102 dobusy 0 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf3d30/224 (12 entries)
> pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82801EB/ER LPC" rev 0x00)
> pcibios0: PCI bus #2 is the last bus
> bios0: ROM list: 0xc/0x1
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82865G/PE/P CPU-I/0-1" rev 0x02
> ppb0 at pci0 dev 1 function 0 "Intel 82865G/PE/P CPU-AGP" rev 0x02
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 vendor "SiS", unknown product 0x0325 rev 0x00:
> aperture at 0xe000, size 0x40
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: irq 11
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: irq 5
> usb1 at uhci1: USB revision 1.0
> uhub1 at usb1
> uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
> uhub1: 2 ports with 2 removable, self powered
> uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: irq 10
> usb2 at uhci2: USB revision 1.0
> uhub2 at usb2
> uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
> uhub2: 2 ports with 2 removable, self powered
> uhci3 at pci0 dev 29 function 3 "Intel 82801EB/ER USB" rev 0x02: irq 11
> usb3 at uhci3: USB revision 1.0
> uhub3 at usb3
> uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
> uhub3: 2 ports with 2 removable, self powered
> ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: irq 9
> usb4 at ehci0: USB revision 2.0
> uhub4 at usb4
> uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
> uhub4: 8 ports with 8 removable, self powered
> ppb1 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0xc2
> pci2 at ppb1 bus 2
> skc0 at pci2 dev 2 function 0 "D-Link Systems DGE-530T" rev 0x11, Marvell
> Yukon (0x1): irq 3
> sk0 at skc0 port A, address 00:13:46:72:00:24
> eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
> skc1 at pci2 dev 3 function 0 "D-Link Systems DGE-530T" rev 0x11, Marvell
> Yukon (0x1): irq 5
> sk1 at skc1 port A, address 00:13:46:71:f8:0e
> eephy1 at sk1 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
> skc2 at pci2 dev 4 function 0 "D-Link Systems DGE-530T" rev 0x11, Marvell
> Yukon (0x1): irq 10
> sk2 at skc2 port A, address 00:13:46:71:f7:cf
> eephy2 at sk2 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02
> pciide0 at pci0 dev 31 functi
