From owner-freebsd-current@FreeBSD.ORG Mon May 21 01:09:53 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 0ED9216A400 for ; Mon, 21 May 2007 01:09:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id AA87513C468 for ; Mon, 21 May 2007 01:09:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so1713120pyh for ; Sun, 20 May 2007 18:09:52 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=meQn/V6u625oFbSOpkfdhpSyFgQ4wrl4Mupi6pvZpkSyf1Oyp+2uZqypLAIneZYx6acUkeVPmDp5CpCxX0o5rPD9l70jtUzP8jPW8MFyfWPzhsVizAhV+CKsbXRPUhzsBzZSlR7qDvTmjfFuG8jL0A+IoL7Jb2QHMzl8TDOoyPo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=aGfq776X+l8H6SA6xqodaD34H7MW6eQJ4BEUNRdpVDWqBIC7+L6ahQyLByhXIQiK23UCy3BJFIpcxe8IBif9mOXfFZAdc9LRtZBlA1IrVNXusEmzgPQpW4nZCsYC33E3/dZL8zwOmpPBPjCeUIyoILwjq+3ANO7kkpl8Ux+ClAU= Received: by 10.35.106.1 with SMTP id i1mr7762049pym.1179709791853; Sun, 20 May 2007 18:09:51 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id m2sm4635348nzf.2007.05.20.18.09.48; Sun, 20 May 2007 18:09:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l4L19jMc037266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 10:09:45 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l4L19ivW037265; Mon, 21 May 2007 10:09:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 21 May 2007 10:09:44 +0900 From: Pyun YongHyeon To: "Li-Lun Wang (Leland Wang)" Message-ID: <20070521010944.GB36838@cdnetworks.co.kr> References: <20070520174124.GA14987@Athena.infor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070520174124.GA14987@Athena.infor.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.org Subject: Re: msk watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com 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 01:09:53 -0000 On Mon, May 21, 2007 at 01:41:24AM +0800, Li-Lun Wang (Leland Wang) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I am resending this the third time since my previous messages didn't seem > to go through. > > I was persuaded to report this on freebsd-current. > 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. > Sometimes doing a kldunload / kldload if_msk can bring the interface > back, but sometimes it is helpless with the following message when I > reload the kernel module: > > kernel: mskc0: port 0xb000-0xb0ff > mem 0xf9000000-0xf9003fff irq 16 at device 0.0 on pci4 > kernel: msk0: on > mskc0 > kernel: msk0: failed to allocate DMA'able memory for jumbo buf > kernel: device_attach: msk0 attach returned 1 > > I would have to reboot to solve this situation. > Supporting jumbo frame requires a big contiguous kernel memory which may not be available at the time of driver loading. If you unload the driver the contiguous kernel memory would be used by other parts of kernel. Unfortunately, there is no easy way to recover from this and the only known way to fix is reboot. > Google found me not much information, but someone did mention something > about MSI. I set hw.pci.enable_msix=0 and hw.pci.enable_msi=0 in my > loader.conf, and I was able to reach megas of bytes throughput without > a problem. > > - -- llwang -- Regards, Pyun YongHyeon