From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 14:54:39 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 20A4216A400 for ; Fri, 13 Jul 2007 14:54:39 +0000 (UTC) (envelope-from llwang@llwang.org) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 9E04B13C4A8 for ; Fri, 13 Jul 2007 14:54:38 +0000 (UTC) (envelope-from llwang@llwang.org) Received: by ug-out-1314.google.com with SMTP id o4so651726uge for ; Fri, 13 Jul 2007 07:54:37 -0700 (PDT) Received: by 10.78.201.10 with SMTP id y10mr494991huf.1184336995314; Fri, 13 Jul 2007 07:29:55 -0700 (PDT) Received: by 10.78.121.3 with HTTP; Fri, 13 Jul 2007 07:29:55 -0700 (PDT) Message-ID: Date: Fri, 13 Jul 2007 09:29:55 -0500 From: "Li-Lun \"Leland\" Wang" Sender: llwang@llwang.org To: "John Baldwin" In-Reply-To: <200707130836.58062.jhb@freebsd.org> 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> <20070521040808.GD36838@cdnetworks.co.kr> <200707130836.58062.jhb@freebsd.org> X-Google-Sender-Auth: 183da2d2658d3eb1 Cc: pyunyh@gmail.com, 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: Fri, 13 Jul 2007 14:54:39 -0000 On 7/13/07, John Baldwin wrote: > 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. Here is the output of pciconf -lc: hostb0@pci0:0:0: class=0x060000 card=0x50001458 chip=0x29a08086 rev=0x02 hdr=0x00 cap 09[e0] = vendor (length 9) Intel cap 0 version 1 pcib1@pci0:1:0: class=0x060400 card=0x50001458 chip=0x29a18086 rev=0x02 hdr=0x01 cap 0d[88] = PCI Bridge card=0x50001458 cap 01[80] = powerspec 3 supports D0 D3 current D0 cap 05[90] = MSI supports 1 message cap 10[a0] = PCI-Express 1 root port none0@pci0:3:0: class=0x078000 card=0x29a41458 chip=0x29a48086 rev=0x02 hdr=0x00 cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[8c] = MSI supports 1 message, 64 bit uhci0@pci0:26:0: class=0x0c0300 card=0x50041458 chip=0x28348086 rev=0x02 hdr=0x00 uhci1@pci0:26:1: class=0x0c0300 card=0x50041458 chip=0x28358086 rev=0x02 hdr=0x00 ehci0@pci0:26:7: class=0x0c0320 card=0x50061458 chip=0x283a8086 rev=0x02 hdr=0x00 cap 01[50] = powerspec 2 supports D0 D3 current D0 pcm0@pci0:27:0: class=0x040300 card=0xa0021458 chip=0x284b8086 rev=0x02 hdr=0x00 cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 05[60] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 1 type 0 pcib2@pci0:28:0: class=0x060400 card=0x50011458 chip=0x283f8086 rev=0x02 hdr=0x01 cap 10[40] = PCI-Express 1 root port cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x50011458 cap 01[a0] = powerspec 2 supports D0 D3 current D0 pcib3@pci0:28:3: class=0x060400 card=0x50011458 chip=0x28458086 rev=0x02 hdr=0x01 cap 10[40] = PCI-Express 1 root port cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x50011458 cap 01[a0] = powerspec 2 supports D0 D3 current D0 pcib4@pci0:28:4: class=0x060400 card=0x50011458 chip=0x28478086 rev=0x02 hdr=0x01 cap 10[40] = PCI-Express 1 root port cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x50011458 cap 01[a0] = powerspec 2 supports D0 D3 current D0 uhci2@pci0:29:0: class=0x0c0300 card=0x50041458 chip=0x28308086 rev=0x02 hdr=0x00 uhci3@pci0:29:1: class=0x0c0300 card=0x50041458 chip=0x28318086 rev=0x02 hdr=0x00 uhci4@pci0:29:2: class=0x0c0300 card=0x50041458 chip=0x28328086 rev=0x02 hdr=0x00 ehci1@pci0:29:7: class=0x0c0320 card=0x50061458 chip=0x28368086 rev=0x02 hdr=0x00 cap 01[50] = powerspec 2 supports D0 D3 current D0 pcib5@pci0:30:0: class=0x060401 card=0x50001458 chip=0x244e8086 rev=0xf2 hdr=0x01 cap 0d[50] = PCI Bridge card=0x50001458 isab0@pci0:31:0: class=0x060100 card=0x50011458 chip=0x28108086 rev=0x02 hdr=0x00 cap 09[e0] = vendor (length 12) Intel cap 1 version 0 features: SATA RAID-5, 4 PCI-e x1 slots, SATA RAID-0/1/10 atapci1@pci0:31:2: class=0x010601 card=0xb0051458 chip=0x28248086 rev=0x02 hdr=0x00 cap 05[80] = MSI supports 16 messages cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = unknown ichsmb0@pci0:31:3: class=0x0c0500 card=0x50011458 chip=0x283e8086 rev=0x02 hdr=0x00 vgapci0@pci1:0:0: class=0x030000 card=0x34451458 chip=0x042110de rev=0xa1 hdr=0x00 cap 01[60] = powerspec 2 supports D0 D3 current D0 cap 05[68] = MSI supports 1 message, 64 bit cap 10[78] = PCI-Express 1 endpoint atapci0@pci3:0:0: class=0x010185 card=0xb0001458 chip=0x2363197b rev=0x02 hdr=0x00 cap 01[68] = powerspec 2 supports D0 D3 current D0 cap 10[50] = PCI-Express 1 legacy endpoint IRQ 0 mskc0@pci4:0:0: class=0x020000 card=0xe0001458 chip=0x436211ab rev=0x22 hdr=0x00 cap 01[48] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 03[50] = VPD cap 05[5c] = MSI supports 2 messages, 64 bit cap 10[e0] = PCI-Express 1 legacy endpoint Thanks. -- llwang