From owner-freebsd-stable@FreeBSD.ORG Thu Apr 3 14:44:24 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 924C1FB3 for ; Thu, 3 Apr 2014 14:44:24 +0000 (UTC) Received: from forward6l.mail.yandex.net (forward6l.mail.yandex.net [IPv6:2a02:6b8:0:1819::6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9C76A0 for ; Thu, 3 Apr 2014 14:44:24 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward6l.mail.yandex.net (Yandex) with ESMTP id 02C8114E0E36 for ; Thu, 3 Apr 2014 18:44:13 +0400 (MSK) Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id B113A7E019A for ; Thu, 3 Apr 2014 18:44:13 +0400 (MSK) Received: from 46.38.38.120.tel.ru (46.38.38.120.tel.ru [46.38.38.120]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id vjgSIxqOCM-i5hquEmq; Thu, 3 Apr 2014 18:44:07 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: a2ffd79f-3da0-4d3a-b888-167a21ff296d Message-ID: <533D73B5.9020808@passap.ru> Date: Thu, 03 Apr 2014 18:44:05 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE? References: <533A8D3B.5040103@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 14:44:24 -0000 03.04.2014 15:21, jason-freebsd-stable@shalott.net пишет: > >>>> 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. Last idea from my side (since you run stable not current) -- do you load the driver by loader.conf? This is my message to freebsd-current@: ----- As of r261651 at CURRENT the driver works for me if: . disable multi-core at BIOS (so kern.smp.cpus: 1); . do not load driver at /boot/loader.conf (i.e. use the builtin kernel driver); . disable WITNESS* and INVARIANTS* (GENERIC does not work even with single CPU). ----- -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve