From owner-freebsd-stable@FreeBSD.ORG Sat Jan 25 12:24: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 B6377483 for ; Sat, 25 Jan 2014 12:24:24 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 81BF11D36 for ; Sat, 25 Jan 2014 12:24:24 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id x13so3874439ief.23 for ; Sat, 25 Jan 2014 04:24:24 -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=N1KjFg2VAR2qvLmfjVGIy/WgBZpKETLDFVqUYWUsshw=; b=ka90QcSdvthr7kVp45mJT0tHVdZYmilC07N0pTT7Nm+SLFeLI9CPbQzrj2k70RKBbG CffKLTTI+Jia6BIJcDdS3BazMWVJprQzeBmIN8ZA/bJrAZMIWqpbzDliuFi5RSaFsXAo yPcvQNLiytUOyT3fgKrvWpASlZE96jXZrmMu7aU9dxIdttEjI8GAH8aEiIC6CBeTCqEj mNAaCEbgJ7AJQQuFS8nNIp0rwPEWnE8S4DNyMMMwiqTh0mZocHukXLV+VMqFqQxlIDCS Y21W+RfT8pEfVuvAZPaW5I0QOTjrWVncDd+efj9gFjI+YX57ZmMCDJosbW+5UCuZ3dph x6oQ== X-Received: by 10.50.176.137 with SMTP id ci9mr9194266igc.31.1390652663997; Sat, 25 Jan 2014 04:24:23 -0800 (PST) Received: from [172.16.0.2] (tx97.net. [85.198.160.156]) by mx.google.com with ESMTPSA id f15sm19675403igd.3.2014.01.25.04.24.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 04:24:23 -0800 (PST) Message-ID: <52E3ACCC.1080707@gmail.com> Date: Sat, 25 Jan 2014 14:23:40 +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: <201401211956.s0LJuHiS065218@maildrop2.v6ds.occnc.com> In-Reply-To: <201401211956.s0LJuHiS065218@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 12:24:24 -0000 On 01/21/14 21:56, Curtis Villamizar wrote: > I have mine working but I haven't done a lot of reboots to see if it > is a "fix" or luck. > > There is a lot of junk that you won't need in the code that is running > well for me. But here it is, as-is warts and all. > > I've been swamped lately and haven't had time to look at this further. I've tried the patch, and the testing went like this: 1) Reboot into fixed kernel => msk0 shows watchdog timeouts. 2) Reboot again => no timeouts, but the interrupt storm is still there. 3) Disable the machine completely for 15 minutes (take out the battery too; it's a laptop), boot fixed kernel => msk works fine. 4) Reboot one more time => msk still works fine. 5) Reboot into 10-RELEASE kernel => watchdog timeouts. 6) Disable the machine completely for 15 minutes, boot fixed kernel => still watchdog timeouts. 7) Disable the machine for 30 minutes, boot fixed kernel => nope, still doesn't work. So, there was a success once (step 3), but I was not able to reproduce it after that. Seems to be random.