From owner-freebsd-stable@FreeBSD.ORG Thu Mar 27 11:47:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB320106566C for ; Thu, 27 Mar 2008 11:47:21 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 89C8D8FC24 for ; Thu, 27 Mar 2008 11:47:21 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by el-out-1112.google.com with SMTP id n30so2549767elf.7 for ; Thu, 27 Mar 2008 04:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=372i1cBdlYutuLVV/OVToAHpFOnu+gy2jfIhwdyQb18=; b=AhQ2BFq0IeDskwf5n3uDCySELv+uTxLtNLsFep9S0GcBIXBXCo1YjVY35qctrbajtuAwLYMVS1Dgu9TuJpLpvXfjXsLFwTm3duXJQi6v8yhFcilePzzVZu51weBE952Q8qKdzUpBk70sl2pEyQKfkyTLbm/Fp+huYZZxX+ALfpg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=amE8HKSAviJhtAagWqf62er6aEqOQ5VBYwvkhjE1PCSWFiV/DgR/3wHvS9q9lQ8S6Atlvj3bWuN/bvRu2t29vHWFXkze+WfquFMxBsMki8yIYm0WxIfa8dzrrtMmpw2k8nLFtExk2WpEZUcq23m9SD/aMPCYFfeXqJ/1z2GnsmI= Received: by 10.142.162.5 with SMTP id k5mr962070wfe.171.1206618439533; Thu, 27 Mar 2008 04:47:19 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 30sm247576wfd.19.2008.03.27.04.47.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Mar 2008 04:47:17 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m2RBlDTT096003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Mar 2008 20:47:13 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2RBlCF8096002; Thu, 27 Mar 2008 20:47:12 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 27 Mar 2008 20:47:12 +0900 From: Pyun YongHyeon To: Danny Braniss Message-ID: <20080327114712.GB95274@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Marvell Technology Group Ltd. Yukon EC Ultra X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2008 11:47:22 -0000 On Thu, Mar 27, 2008 at 01:32:46PM +0200, Danny Braniss wrote: > > On Thu, Mar 27, 2008 at 12:57:31PM +0200, Danny Braniss wrote: > > > Hi, > > > Under load, the msk has problems, with hw.msk.legacy_intr=1 and 0. > > > with = 1, i get > > > TCP segementation error > > > watchdog timeout > > > with = 0, > > > Tx MAC parity error > > > watchdog timeout > > > > > > > Would you show me verbosed boot messages related with msk(4)/e1000phy(4)? > > > mskc0: port 0xc800-0xc8ff mem > 0xfeafc000-0xfeafffff irq 17 at device 0.0 on pci1 > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfeafc000 > mskc0: MSI count : 1 > mskc0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to vector 52 > mskc0: using IRQ 256 for MSI > mskc0: RAM buffer size : 128KB > mskc0: Port 0 : Rx Queue 85KB(0x00000000:0x000153ff) > mskc0: Port 0 : Tx Queue 43KB(0x00015400:0x0001ffff) > msk0: on mskc0 > msk0: bpf attached > msk0: Ethernet address: 00:1e:8c:6d:5c:fe > miibus0: on msk0 > e1000phy0: PHY 0 on miibus0 > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, > auto > mskc0: [MPSAFE] > mskc0: [FILTER] > > is this enough? Yes, it seems that 88E8056/88E1149 PHY has several issues. I recall that there had been several reports for this issue. Since nfe(4) with 88E1149 also have some stability issues, e1000phy(4) has lack of required code for 88E1149 PHY. Up to date, I couldn't find a clue, sorry. I'll let you know if I have a code to give it spin. > danny > > > > the board is a Asus P5K-VM > > > > > > Cheers, > > > danny > > > > > > > > > > -- > > Regards, > > Pyun YongHyeon > > -- Regards, Pyun YongHyeon