From owner-freebsd-stable@freebsd.org Sun Jul 26 10:40:49 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 3D3399A79B5 for ; Sun, 26 Jul 2015 10:40:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (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 0C91C22E for ; Sun, 26 Jul 2015 10:40:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by pachj5 with SMTP id hj5so36073077pac.3 for ; Sun, 26 Jul 2015 03:40:48 -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=XBsJ5woMYLsEoRQ1QMBvpq8sWIc+kzgOv+/jPICFDLg=; b=uKaQkeTlFAJN7lWCZIrfzPYXSzACuyO5zmo5NsjySRYleMPYatsIngbT8kyvgBS2yz LZEWhm0Lzok2f2OQjrOROQEtfKo/eEGG+XUq6CMY1pPoAnnP9Hxu7P3BaXeciX0m7ou8 Azz4vlRXxgmbaAQlCnnY7eL+NxnFKlcnidJMDop5gNA0UdjduWhDZnO9LppSj1lhywQu FBYubT6VFY8V6pFtDq7uQfmkGYagZgoITfqYjSRInWn0RYLlNW6O8AJd8+67VD+oqRNg 6BcqzOMJJli3NxzQSL12JzZnKQHHRlQ3RLwGjBFrl4wPTEy0t5uGTD7TRqlfxwTD+d8t +Lrg== X-Received: by 10.66.55.41 with SMTP id o9mr54186941pap.148.1437907248515; Sun, 26 Jul 2015 03:40:48 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id o7sm23731923pdi.16.2015.07.26.03.40.44 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 26 Jul 2015 03:40:46 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 26 Jul 2015 19:40:39 +0900 Date: Sun, 26 Jul 2015 19:40:39 +0900 To: Alnis Morics Cc: freebsd-stable@freebsd.org Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem Message-ID: <20150726104039.GA1034@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <20150413081348.GA965@michelle.fasterthan.com> <55B36E1A.3040806@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <55B36E1A.3040806@gmail.com> 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: Sun, 26 Jul 2015 10:40:49 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jul 25, 2015 at 02:08:10PM +0300, Alnis Morics wrote: > Just tried 10.2-RC1 amd64 GENERIC, and the problem seems to be gone. I > was even able to scp a 500 MB file. Could it be related to this fix in > BETA2, as mentioned in the announcement, "The watchdog(4) device has > been fixed to print to the correct buffer."? > msk(4) will show watchdog timeouts when it detects driver TX path is in stuck condition but I believe this has nothing to do with watchdog(4). There was no msk(4) code change in 10.2-RC1. If you happen to see the watchdog timeouts again, please try attached patch and let me know whether it makes any difference for you. I didn't get much feedbacks on the patch so I'm not sure whether it really fixes the root cause. > pciconf -lv > [..] > mskc0@pci0:9:0:0: class=0x020000 card=0xc072144d chip=0x435411ab > rev=0x00 hdr=0x00 > vendor = 'Marvell Technology Group Ltd.' > device = '88E8040 PCI-E Fast Ethernet Controller' > class = network > subclass = ethernet > > --1yeeQ81UyVL57Vl7 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="msk.align.diff" Index: sys/dev/msk/if_mskreg.h =================================================================== --- sys/dev/msk/if_mskreg.h (revision 281587) +++ sys/dev/msk/if_mskreg.h (working copy) @@ -2175,13 +2175,8 @@ #define MSK_ADDR_LO(x) ((uint64_t) (x) & 0xffffffffUL) #define MSK_ADDR_HI(x) ((uint64_t) (x) >> 32) -/* - * At first I guessed 8 bytes, the size of a single descriptor, would be - * required alignment constraints. But, it seems that Yukon II have 4096 - * bytes boundary alignment constraints. - */ -#define MSK_RING_ALIGN 4096 -#define MSK_STAT_ALIGN 4096 +#define MSK_RING_ALIGN 32768 +#define MSK_STAT_ALIGN 32768 /* Rx descriptor data structure */ struct msk_rx_desc { --1yeeQ81UyVL57Vl7--