From owner-freebsd-bugs@freebsd.org  Mon Sep 21 20:29:29 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 30415A0588C
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 21 Sep 2015 20:29:29 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 148841150
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Sep 2015 20:29:29 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8LKTSsc084784
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Sep 2015 20:29:28 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203166] [wbwd][patch] Stop watchdog timer in attach routine if
 it is already started
Date: Mon, 21 Sep 2015 20:29:29 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-203166-8-mAHOEj8rID@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203166-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203166-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2015 20:29:29 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203166

--- Comment #1 from Ed Maste <emaste@freebsd.org> ---
We definitely need something like this change.

I'm a little worried that this introduces a window in normal operation though
where the watchdog is ineffective, between wbwd attach and watchdogd starting
up. For example we may have a driver which intermittently hangs in attach, and
we'd want the watchdog to reset the system in that case.

A few ideas from IRC discussion:
- we could pat the watchdog once at attach time so that we don't reboot in
cases where multiuser system startup takes a while after wbwd attaching
- watchdog disabling could happen when the system enters single user mode
- we ought to have a tunable or other configuration to control this, as some
system vendors etc. may not want the watchdog disabled

In any case I think it's probably better to have this change than not.

-- 
You are receiving this mail because:
You are the assignee for the bug.