Date: Sun, 20 May 2007 21:39:54 -0500 From: "Li-Lun \"Leland\" Wang" <llwang@infor.org> To: pyunyh@gmail.com Cc: freebsd-current@freebsd.org Subject: Re: msk watchdog timeout Message-ID: <b680ed60705201939i4f54e332t731dd5e3b466a7ce@mail.gmail.com> In-Reply-To: <20070521010944.GB36838@cdnetworks.co.kr> References: <20070520174124.GA14987@Athena.infor.org> <20070521010944.GB36838@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/20/07, Pyun YongHyeon <pyunyh@gmail.com> 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 possible? -- llwang
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b680ed60705201939i4f54e332t731dd5e3b466a7ce>