From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 12:49:19 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 2C4BE16A408 for ; Fri, 13 Jul 2007 12:49:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 99A1013C4C2 for ; Fri, 13 Jul 2007 12:49:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l6DCnB4c003447; Fri, 13 Jul 2007 08:49:15 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 13 Jul 2007 08:36:56 -0400 User-Agent: KMail/1.9.6 References: <20070520174124.GA14987@Athena.infor.org> <20070521040808.GD36838@cdnetworks.co.kr> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200707130836.58062.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 13 Jul 2007 08:49:15 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3656/Fri Jul 13 07:24:51 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: pyunyh@gmail.com, "Li-Lun \"Leland\" Wang" 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: Fri, 13 Jul 2007 12:49:19 -0000 On Monday 21 May 2007 12:45:39 am 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? Possibly. > > > 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. If it's not the driver it would be the chipset. We already don't use MSI on systems that don't support either PCI-X or PCI-express, so that implicitly blacklists most older Intel chipsets. Do you have any other devices in your system that support MSI? pciconf -lc output would be useful to look at. -- John Baldwin