Re: call for sk(4) testers

On Sat 14 Jan 06 21:43, Joshua Tinnin <krinklyfig_at_comcast.net> wrote:
> On Sat 14 Jan 06 21:02, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
> > On Sat, Jan 14, 2006 at 12:06:48AM -0700, Joshua Tinnin wrote:
<snip>
> >  > # uname -a
> >  > FreeBSD smogmonster.local 6.0-RELEASE-p2 FreeBSD 6.0-RELEASE-p2
> >  > #0: Fri Jan 13 23:13:57 MST 2006
> >  > krinklyfig_at_smogmonster.local:/usr/obj/usr/src/sys/MYKERNEL60 
> >  > i386
> >  >
> >  > # dmesg | grep sk
> >  > skc0: <Marvell Gigabit Ethernet> port 0x9000-0x90ff mem
> >  > 0xec000000-0xec003fff irq 17 at device 4.0 on pci1
> >  > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7)
> >  > sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
> >  > sk0: Ethernet address: 00:0e:a6:70:56:75
> >  >
> >  > As for dual port, I also have:
> >  >
> >  > miibus0: <MII bus> on sk0
> >  > e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
> >  > e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
> >  > 1000baseTX-FDX, auto
> >  >
> >  > ... although I haven't used that one, yet. I can try it if you
> >  > like.
> >
> > Yes. I'd like to know it has locking bugs on dual port handling.
> > I'd also like to know sk(4) works on second generation chips from
> > Marvell.(e.g. Yukon-II XL/EC/FE)
>
> OK, I'll give it a shot ...

Sorry to say, unfortunately, it didn't work. I couldn't even bring up 
the e1000phy interface.

Still no watchdog timeouts on sk0, however.

- jt