From owner-freebsd-current@FreeBSD.ORG Tue Jan 17 06:12:03 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABE4616A420 for ; Tue, 17 Jan 2006 06:12:03 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9729E43D46 for ; Tue, 17 Jan 2006 06:12:02 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by zproxy.gmail.com with SMTP id l1so1136335nzf for ; Mon, 16 Jan 2006 22:12:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=CaG+VmlWDX7BogTlp5bJu7v9AkupxWoeCxfwq/cw6eG98yNFGjOjukP4F+O6r6j/T2mDeJQOeIjg+VZKAIp+5fUZnVnIhmRecryWAfZ1gZRWIQ7cFeizZQDYejUARytVYkVMUIdll871vQq+SqgHoOZOeq+sgEm5h8SR6TQ5I/Y= Received: by 10.36.9.16 with SMTP id 16mr5649331nzi; Mon, 16 Jan 2006 22:12:02 -0800 (PST) Received: from michelle.rndsoft.co.kr ( [211.32.202.217]) by mx.gmail.com with ESMTP id 14sm884033nzp.2006.01.16.22.12.00; Mon, 16 Jan 2006 22:12:01 -0800 (PST) Received: from michelle.rndsoft.co.kr (localhost.rndsoft.co.kr [127.0.0.1]) by michelle.rndsoft.co.kr (8.13.5/8.13.5) with ESMTP id k0H6Ca1c036067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Jan 2006 15:12:36 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.rndsoft.co.kr (8.13.5/8.13.5/Submit) id k0H6CZbB036066; Tue, 17 Jan 2006 15:12:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 17 Jan 2006 15:12:35 +0900 From: Pyun YongHyeon To: Joshua Tinnin Message-ID: <20060117061235.GD35342@rndsoft.co.kr> References: <20060112113251.GB13481@rndsoft.co.kr> <20060115040206.GB27154@rndsoft.co.kr> <200601142143.14947.krinklyfig@comcast.net> <200601162258.43273.krinklyfig@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601162258.43273.krinklyfig@comcast.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: call for sk(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2006 06:12:03 -0000 On Mon, Jan 16, 2006 at 10:58:40PM -0700, Joshua Tinnin wrote: > On Sat 14 Jan 06 21:43, Joshua Tinnin wrote: > > On Sat 14 Jan 06 21:02, Pyun YongHyeon wrote: > > > On Sat, Jan 14, 2006 at 12:06:48AM -0700, Joshua Tinnin wrote: > > > > > # uname -a > > > > FreeBSD smogmonster.local 6.0-RELEASE-p2 FreeBSD 6.0-RELEASE-p2 > > > > #0: Fri Jan 13 23:13:57 MST 2006 > > > > krinklyfig@smogmonster.local:/usr/obj/usr/src/sys/MYKERNEL60 > > > > i386 > > > > > > > > # dmesg | grep sk > > > > skc0: port 0x9000-0x90ff mem > > > > 0xec000000-0xec003fff irq 17 at device 4.0 on pci1 > > > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) > > > > sk0: on skc0 > > > > sk0: Ethernet address: 00:0e:a6:70:56:75 > > > > > > > > As for dual port, I also have: > > > > > > > > miibus0: on sk0 > > > > e1000phy0: 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. Would you please give more information? Does stock sk(4) work on the NIC? is it YukonII? > > Still no watchdog timeouts on sk0, however. > I performed serveral hours of Rx/Tx tests and couldn't see watchdog timeout. So I think that particular issues was gone. > - jt Thank you. -- Regards, Pyun YongHyeon