Re: msk watchdog timeout

8 msg	zfs refuses to load pool on boot, zpool denies ...
2 msg	FreeBSD uses the year 1936 in qemu
1 msg	net/boinc-client pograms only run half the time...
12 msg	kqemu crash (page fault) with -current
3 msg	Spurious RSTs, syncache, and pf weirdness
3 msg	Promise SATA300 TX4 problems in CURRENT
5 msg	Can't build RELENG_6 from HEAD?
4 msg	Re: fun fun fun. no networking
1 msg	Re: Multiple IRQs for PCI interrupt
4 msg	Re: em0 hijacking traffic to port 623

Re: msk watchdog timeout
\ John Baldwin (13 Jul 2007)
. \ Li-Lun \Leland\ Wang (13 Jul 2007)
. . \ John Baldwin (13 Jul 2007)

5 msg	Re: Quick hardware survey - disk INT13 'EDD' se...
1 msg	Wireless (bg)scan and ARP
6 msg	threadlock and msk watchdog timeout
4 msg	immediate reboot with ipnat/ipmon on amd64
1 msg	request for approval: G965 AGP support
25 msg	crash in tty code in 6.1.. fixed since?
1 msg	uma_zalloc_arg: zone 'mbuf' with the following ...
3 msg	patch to catch non-working hpet
4 msg	Removing an accidentally incorrect vdev from a ...

Subject:	Re: msk watchdog timeout
Group:	Freebsd-current
From:	John Baldwin
Date:	13 Jul 2007

On Monday 21 May 2007 12:45:39 am Li-Lun "Leland" Wang wrote:
> On 5/20/07, Pyun YongHyeon <pyunyh> wrote:
> > On Sun, May 20, 2007 at 09:39:54PM -0500, Li-Lun Leland Wang wrote:
> > > On 5/20/07, Pyun YongHyeon <pyunyh> 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
_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"