From owner-freebsd-current@FreeBSD.ORG Mon May 21 05:43:30 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5890D16A421 for ; Mon, 21 May 2007 05:43:30 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0BFB913C457 for ; Mon, 21 May 2007 05:43:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so1758261pyh for ; Sun, 20 May 2007 22:43:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=i99dBLhWxwW2RHFvhGpXfc0FiG2AA2uOSfVIj4CCFgklX1ik8mTpf5cjg/LcGUtZ+AtQX8KO3bTD1YTVVYw/ciMZOR9MrCjcRyGBDo7RZ145XNVkSU1YbMTxwWsff1zE4bJQTjxzApQs0nh71v+AjUKE5oohu7whhBKM2SsD74w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=sq0KDvDFjMShoX3w3mFFcBf+ErJtG7qhbVnt1MiVc8xg14395hg8Wq9bT9jrXmeuI+qyb187C7dSO0tEdllhrCq9zq0mcjKn0tjgMyRTZxRsX2K8/pkla9hklWZO2zykGr57pnFXKEzxDMjLfElnS4zDtz2d9xIsz2plVnC2uYs= Received: by 10.35.43.10 with SMTP id v10mr8098951pyj.1179726208914; Sun, 20 May 2007 22:43:28 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 7sm17721405nzn.2007.05.20.22.43.26; Sun, 20 May 2007 22:43:27 -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 l4L5hMcn038120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 14:43:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l4L5hMF2038119; Mon, 21 May 2007 14:43:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 21 May 2007 14:43:22 +0900 From: Pyun YongHyeon To: Li-Lun Leland Wang Message-ID: <20070521054322.GE36838@cdnetworks.co.kr> References: <20070520174124.GA14987@Athena.infor.org> <20070521010944.GB36838@cdnetworks.co.kr> <20070521040808.GD36838@cdnetworks.co.kr> 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-current@freebsd.org Subject: Re: msk watchdog timeout 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: Mon, 21 May 2007 05:43:30 -0000 On Sun, May 20, 2007 at 11:45:39PM -0500, Li-Lun Leland Wang wrote: > On 5/20/07, Pyun YongHyeon wrote: > >On Sun, May 20, 2007 at 09:39:54PM -0500, Li-Lun Leland Wang wrote: > > > On 5/20/07, Pyun YongHyeon wrote: > > > >On Mon, May 21, 2007 at 01:41:24AM +0800, Li-Lun Wang (Leland Wang) > > wrote: > > > > > I just installed 7.0-current as of May 3 on my new computer that > > comes > > > > > with an on-board Marvell Yukon Gigabit Ethernet. Every now and then > > > > > if the network throughput comes near several hundred kbytes, I get > > the > > > > > msk0 watchdog timeout messages: > > > > > > > > > > kernel: msk0: watchdog timeout > > > > > msk0: watchdog timeout (missed Tx interrupts) -- recovering > > > > > > > > > > Although it says recovering, the interface never comes back alive. > > > > > > > >The above message indicates the driver sent all pending transmission > > > >requests but the driver didn't receive corresponding Tx completion > > > >interrupts. Not recovering from the watchdog timeout means there are > > > >another issues on the driver. However as disabling MSI fixed the > > > >issue, I guess it's not fault of msk(4) and it comes from bad/broken > > > >MSI implementation of your system. I guess it's time to add your > > > >chipset to a PCI quirk table in order to blacklist it. > > > > > > I do reckon that MSI doesn't work on earlier Intel chipsets. Mine is > > > P965 (on a gigabyte GA-965P-DS3 rev 1.3), which I suppose is recent > > > enough to support MSI, isn't it? Or could there be other problems > > > >Using latest chipsets does not necessarily guarantee working MSI. > > I see. I think we should maybe add P965 to the PCI quirk list for > broken MSI, then? > I don't have systems that use P965 so I'm not sure whether MSI support is broken or not on the chipset. If other drivers that supports MSI does not work too it would be strong indication of broken MSI implementation. > > > possible? > > > > > > >Yes. But I couldn't find possible issue on msk(4) yet. > > Maybe I was not clear enough. Could there be something else that > causes MSI to not working correctly other than the chipset? I was > just wondering why I didn't see too many broken MSI reports if most > Intel chipsets are broken. > Since msk(4) with MSI is working without issues on my box I guess there is not much to do in msk(4). > -- llwang > > P.S. I do greatly appreciate your efforts on msk(4). You're welcome. -- Regards, Pyun YongHyeon