From owner-freebsd-current@FreeBSD.ORG Mon May 21 04:08:17 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 7337316A421 for ; Mon, 21 May 2007 04:08:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2C86413C457 for ; Mon, 21 May 2007 04:08:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so1742365pyh for ; Sun, 20 May 2007 21:08:16 -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=QbdyCfvjSHB6H4W/Z0bEwWjUml7iwQiokWGJ/wgpAOMzp/EjM6wz6vWruX3T1SUzdjBczKZkiOjxktvNfzdz621dXDo/AvMGITa/rm1X2O0SPKqsLx8kROqBaYHM+Gis6ujcmNPvsGCC5TG0ARDo9pdi2+FEcj+jkDwtAkPyEME= 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=Pr+Uia9TxbwR598xETu+TkmOsFORKAsi5nCJNmZJJONR/N8FrpwxiGF09N8VJ5QWPFPjm6uCQ5rMH9ZdbNHb0NNOxAhiJD+IgktnjYKPSSKKLjdeWqB2G9zScFYbwuNTFXDwLFkvfiZYxmw70THmUKDNIcgtmoRxen6UHaFUqjg= Received: by 10.35.19.6 with SMTP id w6mr7981073pyi.1179720496325; Sun, 20 May 2007 21:08:16 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 38sm17490607nza.2007.05.20.21.08.13; Sun, 20 May 2007 21:08:15 -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 l4L489an037801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 13:08:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l4L489Ht037800; Mon, 21 May 2007 13:08:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 21 May 2007 13:08:08 +0900 From: Pyun YongHyeon To: Li-Lun Leland Wang Message-ID: <20070521040808.GD36838@cdnetworks.co.kr> References: <20070520174124.GA14987@Athena.infor.org> <20070521010944.GB36838@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 04:08:17 -0000 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. > possible? > Yes. But I couldn't find possible issue on msk(4) yet. > -- llwang -- Regards, Pyun YongHyeon