From owner-freebsd-current@FreeBSD.ORG Sun May 20 17:41:26 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 0ED1E16A46C for ; Sun, 20 May 2007 17:41:26 +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 D386313C48C for ; Sun, 20 May 2007 17:41:25 +0000 (UTC) (envelope-from llwang@infor.ck.tp.edu.tw) Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001) id D39EF170BB; Mon, 21 May 2007 01:41:24 +0800 (CST) Date: Mon, 21 May 2007 01:41:24 +0800 From: "Li-Lun Wang (Leland Wang)" To: freebsd-current@FreeBSD.org Message-ID: <20070520174124.GA14987@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: , X-List-Received-Date: Sun, 20 May 2007 17:41:26 -0000 -----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. 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 megas of bytes throughput without a problem. - -- llwang -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGUIhDCQM7t5B2mhARAjRiAJ9sUZY2r1Js/ZUc+hV0cq9zrtAyJACfbihs vgaKBUNWLC4Y8LSZ39vxBI8= =4bxd -----END PGP SIGNATURE-----