From owner-freebsd-stable@freebsd.org Fri Aug 28 01:37:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3FA79C472C for ; Fri, 28 Aug 2015 01:37:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1646AB6 for ; Fri, 28 Aug 2015 01:37:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by pacgr6 with SMTP id gr6so7268401pac.3 for ; Thu, 27 Aug 2015 18:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=0M0D9+AfDOC2eVH/YKBfxnjFhnpdYzzVawFQmcoqOuc=; b=rswwbcNMDb4qIA5uEvJT2DI+m/AIFjTZtcQAv/iyQTG7JiNbkBVRyNLe7ePcsNgIZO lgAcyWw+ZVdvwHz8PMOjY5kEjrD6m15CDY0EE1vWWTRvAsUGKQ+48aYyyaHXHp4nRa0G CAnXW3b87+qc9F9rX1zlcr57t8OjP1UL1wqR3yaIa4Ue5WnpE/804UwSh8x+G3P8eix2 dCayYQPFZkUd1MqOwcSEHwYfia0w4OTTQNrJNovHeKLgNz51xZn2afH5YSAqckr2+YQG Bjq83IeV9hYBiyxbh8mju0lg5PhD9HhRf7wkQhqLhNIioKh9ApkVzgqVDJ9wSUpc03OF QTjQ== X-Received: by 10.67.8.106 with SMTP id dj10mr10977219pad.123.1440725822195; Thu, 27 Aug 2015 18:37:02 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id xo14sm3792920pac.24.2015.08.27.18.36.58 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 27 Aug 2015 18:37:01 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 28 Aug 2015 10:36:48 +0900 Date: Fri, 28 Aug 2015 10:36:48 +0900 To: Johann Hugo Cc: Roosevelt Littleton , freebsd-stable@freebsd.org Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem Message-ID: <20150828013648.GA989@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <20150816120831.GB1288@michelle.fasterthan.com> <20150826082850.GC971@michelle.fasterthan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2015 01:37:03 -0000 On Thu, Aug 27, 2015 at 11:29:28AM +0200, Johann Hugo wrote: > It's working for me so far and I haven't seen any watchdog timeouts. > With 10.2-RELEASE I got timeouts and lost connectivity in less that a > minute. > Ok, great. Committed in r287238. Thanks again. > Johann > > On Wed, Aug 26, 2015 at 10:28 AM, Yonghyeon PYUN wrote: > > On Wed, Aug 26, 2015 at 10:06:29AM +0200, Johann Hugo wrote: > >> 10.2-RELEASE does not work for me. It works for a very short while and > >> then it stops with "msk0 watchdog timeout" errors > >> > > > > Thanks a lot for your report. This is the first report for > > msk(4) watchdog timeouts on 10.2-RELEASE. > > > >> I'm not sure what patch Roosevelt was talking about, but the patch in > >> this thread works for me: > >> https://lists.freebsd.org/pipermail/freebsd-stable/2015-April/082226.html > >> > >> I've changed MSK_STAT_ALIGN from 4096 to 8192 in if_mskreg.h and it's > >> been running stable for the last week. > >> > > > > I see. I'm under the impression that RX/TX descriptor ring > > alignment shall trigger the same issue so it would be better to > > know how attached patch works on your box. > > > > Thanks. > > > >> Johann > >> > >> On Sun, Aug 16, 2015 at 2:08 PM, Yonghyeon PYUN wrote: > >> > On Wed, Aug 12, 2015 at 09:44:06AM -0400, Roosevelt Littleton wrote: > >> >> Hi, > >> >> So, I can confirm with the attached patch. I have a working msk0 that > >> >> hasn't failed for the past month. I considered this problem fix for me. > >> >> Since, I have went a long time without any problems. Thanks! > >> > > >> > I'm not sure which patch you used. Given that users reported > >> > 10.2-RELEASE works, it would be great if you revert local patch > >> > and try it again on 10.2-RELEASE.