From owner-freebsd-stable@FreeBSD.ORG Sat Jan 25 19:51:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35F52E6B for ; Sat, 25 Jan 2014 19:51:26 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 01B931E31 for ; Sat, 25 Jan 2014 19:51:25 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id e14so4333777iej.3 for ; Sat, 25 Jan 2014 11:51:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9e3qDLZtm1xgwcdwKLRvU+R+W1PUa/Xg3doXFEra+F0=; b=Nv2CBh6wRgwoqxvA2sl3c+YhU1YPKDCqjHSUnWLY+vhYHSnW08aiY6dajBGFBffuTf XeZvei4zJumGQAxO8oWXLbYkrpE+RvSbkRmtjV/5arbjeMz+YL///6Y5h4mZsD94E1KK T3u4QIQPKMsEuTeRzZjwcodYiSGO9c/J2dcw3wuhjQ21MK8twITCe+iqN9FZxJZDHOTh iMwtyVo5DJQVlm8saTiij/qUIHKcbOxukDEIlAqEO9OJCpLRmugAS35p52zaJ829O5e8 0Pc5QD8qoHIoxEwCCWmIw8JWvSLo2MdaQ2Xn8ob/6eJRfS+FGtLoKEzhx5RPbkC8P+sl 3J/A== X-Received: by 10.50.3.101 with SMTP id b5mr10583814igb.6.1390679485468; Sat, 25 Jan 2014 11:51:25 -0800 (PST) Received: from [172.16.0.2] (tx97.net. [85.198.160.156]) by mx.google.com with ESMTPSA id kt2sm33154675igb.1.2014.01.25.11.51.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 11:51:24 -0800 (PST) Message-ID: <52E4159A.4020007@gmail.com> Date: Sat, 25 Jan 2014 21:50:50 +0200 From: Vitaly Magerya User-Agent: Thunderbird MIME-Version: 1.0 To: curtis@ipv6.occnc.com Subject: Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE? References: <201401251935.s0PJZAwH048013@maildrop2.v6ds.occnc.com> In-Reply-To: <201401251935.s0PJZAwH048013@maildrop2.v6ds.occnc.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Yonghyeon PYUN , freebsd-stable@freebsd.org 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: Sat, 25 Jan 2014 19:51:26 -0000 On 01/25/14 21:35, Curtis Villamizar wrote: > When I'm no longer quite so swamped I'll look at this again. It seems > we are the only two reporting this problem. To everyone reading this list: if you have an msk(4) NIC that doesn't work on 10-RELEASE, now is the time to speak up. > Please send lines of these form from dmesg: > > mskc0: port 0xe800-0xe8ff > mem 0xfebfc000-0xfebfffff irq 19 at deviceD 0.0 on pci2 > > msk0: > on mskc0 > > That may indicate we have very similar chips. If not, this msk > problem may be more widespread. Mine goes like this: mskc0: port 0x2000-0x20ff mem 0xf0200000-0xf0203fff irq 18 at device 0.0 on pci9 msk0: on mskc0 Pretty different chips it seems.