From owner-freebsd-stable@FreeBSD.ORG Thu Apr 3 11:21:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CA426F3 for ; Thu, 3 Apr 2014 11:21:31 +0000 (UTC) Received: from new.shalott.net (new.shalott.net [66.180.195.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.shalott.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 30479EAF for ; Thu, 3 Apr 2014 11:21:30 +0000 (UTC) Received: (qmail 4510 invoked by uid 1000); 3 Apr 2014 11:21:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Apr 2014 11:21:22 -0000 Date: Thu, 3 Apr 2014 04:21:22 -0700 (PDT) From: jason-freebsd-stable@shalott.net X-X-Sender: jason@new.shalott.net To: freebsd-stable@freebsd.org Subject: Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE? In-Reply-To: <533A8D3B.5040103@gmail.com> Message-ID: References: <533A8D3B.5040103@gmail.com> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 11:21:31 -0000 >>> A solution was committed and some reports of both success and failure >>> where submitted [1,2]. (I myself switched to another network card and >>> did not test the fix as of yet). >> I did try upgrading sys/dev/msk to r261577; it didn't help. >> >> I also tried downgrading sys/dev/msk back to the version >> from9.0-RELEASE; also didn't help. I looked at trying to downgrade the >> relevant portions of sys/dev/mii back to that same version as well, but >> clang choked on it, and I didn't have time to dig in any further. > I managed to use msk at CURRENT by disabling multi-core at BIOS (and get > kern.smp.cpus: 1). I tried this. The first time I rebooted after changing the BIOS, the machine booted okay, but after the msk card had passed about 200k, the entire machine locked up hard, and I had to power-cycle to get it back. After that, it behaved as previously -- after passing about 200k total, the card hangs and there's an interrupt storm. -Jason