From owner-freebsd-current@FreeBSD.ORG Mon May 21 04:45:41 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 8DB0E16A46F for ; Mon, 21 May 2007 04:45:41 +0000 (UTC) (envelope-from llwang@llwang.org) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 2E95713C4BB for ; Mon, 21 May 2007 04:45:40 +0000 (UTC) (envelope-from llwang@llwang.org) Received: by ug-out-1314.google.com with SMTP id 71so826211ugh for ; Sun, 20 May 2007 21:45:40 -0700 (PDT) Received: by 10.78.97.7 with SMTP id u7mr984970hub.1179722739718; Sun, 20 May 2007 21:45:39 -0700 (PDT) Received: by 10.78.121.6 with HTTP; Sun, 20 May 2007 21:45:39 -0700 (PDT) Message-ID: Date: Sun, 20 May 2007 23:45:39 -0500 From: "Li-Lun \"Leland\" Wang" Sender: llwang@llwang.org To: pyunyh@gmail.com In-Reply-To: <20070521040808.GD36838@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070520174124.GA14987@Athena.infor.org> <20070521010944.GB36838@cdnetworks.co.kr> <20070521040808.GD36838@cdnetworks.co.kr> X-Google-Sender-Auth: 4fb3be38e79fc977 Cc: freebsd-current@freebsd.org Subject: Re: msk watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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:45:41 -0000 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? > > 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. -- llwang P.S. I do greatly appreciate your efforts on msk(4).