new sk driver [was: nve timeout (and down) regression?]
Pyun YongHyeon
pyunyh at gmail.com
Mon May 8 04:56:42 UTC 2006
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
> Pyun,
>
> Pyun YongHyeon wrote:
> >On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
> > > On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
> > > > On Mar 28, Pyun YongHyeon wrote:
> > > > > and sparc64(SMP) and I never see above errors. The only issue
> > known to
> > > > > me is occasional watchdog timeout error which I really want to fix.
> > But
> > > > > the watchdog timeout error is hard to reproduce and I couldn't
> > reproduce
> > > > > the error on my system.
> > > >
> > > > I'm still seeing the watchdog timeout on 5.5-PRERELEASE
> > (uni-processor):
> > > >
> > > > Mar 22 14:47:04 belle kernel: sk0: watchdog timeout
> > > > Mar 24 08:37:19 belle kernel: sk0: watchdog timeout
> > > > Mar 27 04:09:15 belle kernel: sk0: watchdog timeout
> > > >
> > > > But at least the driver doesn't wedge the interface now.
> > >
> > > Yes, same here on 6.1-PRERELEASE:
> > >
> > > ch0: 10 slots, 1 drive, 1 picker, 0 portals
> > > sk0: watchdog timeout
> > > sk0: watchdog timeout
> > >
> >
> >Ok, here is a new patch that try to fix the watchdog timeout error.
> >I don't know it will eradicate the bug as I don't see the watchdog
> >error on my system.
> >The patch borrowed Yukon specific register definition from Linux
> >driver and adopted Yukon FIFO related operations from Linux. I don't
> >know exact meaning of the registers(it's just guessing) but it seems
> >it doesn't hurt on my system.
> >
> >You may have to download 4 files to build the driver.
> >http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
> >http://people.freebsd.org/~yongari/sk/sk_test2/if_skreg.h
> >http://people.freebsd.org/~yongari/sk/sk_test2/xmaciireg.h
> >http://people.freebsd.org/~yongari/sk/sk_test2/yukonreg.h
> >
> I compiled new sk driver on 6.1-RC, however I couldn't get it work.
> When I load module I get:
>
> May 8 12:04:56 proxy kernel: skc0: <Marvell Gigabit Ethernet> port
> 0xcc00-0xccff mem 0xfe3fc000-0xfe3fffff irq 20 at device 3.0 on pci6
> May 8 12:04:56 proxy kernel: skc0: unknown media type: 0x31
> May 8 12:04:56 proxy kernel: device_attach: skc0 attach returned 6
>
> Machine:
> FreeBSD 6.1-RC #1: Mon May 8 11:40:01 ULAST 2006
> tsgan at proxy.micom.mng.net:/usr/obj/usr/src/sys/PROXY
> ACPI APIC Table: <DELL PE1800 >
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.52-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0xf43 Stepping = 3
>
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> Features2=0x641d<SSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,<b14>>
> AMD Features=0x20100000<NX,LM>
> Logical CPUs per core: 2
> real memory = 1073479680 (1023 MB)
> avail memory = 1041559552 (993 MB)
> ...
>
> pciconf -lv
> ...
> skc0 at pci6:3:0: class=0x020000 card=0x432011ab chip=0x432011ab rev=0x14
> hdr=0x00
> vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> device = '88E8001/8003/8010 Gigabit Ethernet Controller with
> Integrated PHY (copper)'
> class = network
> subclass = ethernet
> ...
> Is this NIC supported by if_sk driver?
>
Hmm, It seems that the NIC is SysKonnect V2.0(SK98XX2) which is
supposed to work with sk(4). Did it ever work with sk(4)?
I see there is differences between sk(4) and Linux skge driver
in determining physical media type. It seems OpenBSD also
used Linux skge approach.
> thanks,
>
> Ganbold
>
--
Regards,
Pyun YongHyeon
More information about the freebsd-stable
mailing list