From owner-freebsd-current@FreeBSD.ORG Thu May 17 03:58:37 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 60F4E16A402 for ; Thu, 17 May 2007 03:58:37 +0000 (UTC) (envelope-from llwang@infor.ck.tp.edu.tw) Received: from infor.ck.tp.edu.tw (infor.ck.tp.edu.tw [203.64.26.200]) by mx1.freebsd.org (Postfix) with ESMTP id 328F413C44B for ; Thu, 17 May 2007 03:58:37 +0000 (UTC) (envelope-from llwang@infor.ck.tp.edu.tw) Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001) id DCCA91708E; Thu, 17 May 2007 11:38:56 +0800 (CST) From: "Li-Lun Wang (Leland Wang)" To: freebsd-current@FreeBSD.org Message-ID: <20070517033856.GA52039@Athena.infor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) Cc: Subject: 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: , Date: Thu, 17 May 2007 03:58:37 -0000 X-Original-Date: Thu, 17 May 2007 11:38:56 +0800 X-List-Received-Date: Thu, 17 May 2007 03:58:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, 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. 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. 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 several Mbytes throughput without a problem. - -- llwang -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGS85PCQM7t5B2mhARArxmAJ9Iv6vG6I8h6OH2aclBxfs287KgQACfdq0V NqBqQiryN25esGNmdnZ3440= =FR6d -----END PGP SIGNATURE-----