Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Dec 2006 09:39:14 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Pascal Hofstee <caelian@gmail.com>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: D-Link DGE-350T and if_sk (no go)
Message-ID:  <20061214003914.GB20386@cdnetworks.co.kr>
In-Reply-To: <d8a0b7620612131359h1a533b2cib48399c1f08a8a1b@mail.gmail.com>
References:  <d8a0b7620612131359h1a533b2cib48399c1f08a8a1b@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 13, 2006 at 10:59:53PM +0100, Pascal Hofstee wrote:
 > I just acquired a new shiny D-Link DGE-350T (which according to sk(4)
 > is supported by FreeBSD) but unfortunately had to come to the
 > conclusion that i cannot get this card to actually send/receive any
 > actual packets.
 > 
 > The device probes, attached and comes up perfectly, auto-negotiation
 > (properly) chooses 1000baseTX full-duplex and after that the device is
 > basically dead .. i can't get it to produce any actual traffic.
 > 
 > Below is verbose dmesg output with ACPI disabled .. as i was unable to
 > get the desired info with ACPI enabled (because of a ACPI bad write
 > output storm)
 > 
 > If anybody has any ideas on how to resolve this problem i am open for
 > suggestions and willing to test patches.
 > 
 > ----[dmesg output]--------
 > Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation.
 > FreeBSD 7.0-CURRENT #9: Tue Dec 12 13:42:43 CET 2006
 >    pascal@chekov.ufp.fli4l:/usr/obj/usr/src/sys/CHEKOV
 > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0cde000.
 > Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc0cde158.
 > Preloaded elf module "/boot/kernel/sound.ko" at 0xc0cde208.
 > Preloaded elf module "/boot/kernel/cpufreq.ko" at 0xc0cde2b4.
 > Calibrating clock(s) ... i8254 clock: 1193224 Hz
 > CLK_USE_I8254_CALIBRATION not specified - using default frequency
 > Timecounter "i8254" frequency 1193182 Hz quality 0
 > Calibrating TSC clock ... TSC clock: 902052593 Hz
 > CPU: Intel Pentium III (902.05-MHz 686-class CPU)
 >  Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
 >  Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>

[...]

 > found->	vendor=0x1186, dev=0x4b01, revid=0x11

It looks like second generation DGE-530T.

 > 	bus=0, slot=9, func=0
 > 	class=02-00-00, hdrtype=0x00, mfdev=0
 > 	cmdreg=0x0017, statreg=0x02b0, cachelnsz=8 (dwords)
 > 	lattimer=0x20 (960 ns), mingnt=0x17 (5750 ns), maxlat=0x1f (7750 ns)
 > 	intpin=a, irq=5
 > 	powerspec 2  supports D0 D1 D2 D3  current D0
 > 	VPD Ident: DGE-530T Gigabit Ethernet Adapter
 > 	PN: DGE-530T
 > 	EC: Rev. 1.1
 > 	MN: D-Link
 > 	SN: DGE530TBCD870
 > 	CP: id 1, BAR16, off 0x3cc
 > 	RV: 0x99
 > 	map[10]: type 1, range 32, base 0xde000000, size 14, enabled
 > 	map[14]: type 4, range 32, base 0xa800, size  8, enabled

[...]

 > skc0: <D-Link DGE-530T Gigabit Ethernet> port 0xa800-0xa8ff mem
 > 0xde000000-0xde003fff irq 5 at device 9.0 on pci0
 > skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xde000000
 > skc0: interrupt moderation is 100 us
 > skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9)
 > skc0: chip ver  = 0xb1
 > skc0: chip rev  = 0x09
 > skc0: SK_EPROM0 = 0x10
 > skc0: SRAM size = 0x010000
 > sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
 > sk0: using obsoleted if_watchdog interface
 > sk0: bpf attached
 > sk0: Ethernet address: 00:17:9a:bc:d8:70
 > miibus0: <MII bus> on sk0
 > e1000phy0: <Marvell 88E1011 Gigabit PHY> on miibus0
 > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, 
 > auto
 > skc0: [MPSAFE]

If Tx side doesn't work at all it would show watchdog timeout message.
Did you see that? If Rx doesn't work you wouldn't see interrupts on
your NIC. Running a ping(8) on the other host to a system with sk(4)
and watch interrupts section in "systat -vmstat 1" output.

-- 
Regards,
Pyun YongHyeon



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