From owner-freebsd-hackers@freebsd.org Fri Jan 8 15:02:40 2016 Return-Path: Delivered-To: freebsd-hackers@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 8C8A2A689F4 for ; Fri, 8 Jan 2016 15:02:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4706D1BAD for ; Fri, 8 Jan 2016 15:02:39 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from e-bsd.cs.huji.ac.il ([132.65.80.241] helo=outmail.cs.huji.ac.il) by kabab.cs.huji.ac.il with esmtp id 1aHYYn-000JJE-MN; Fri, 08 Jan 2016 17:02:37 +0200 Received: from [132.65.179.20] (helo=mbpro2.bs.cs.huji.ac.il) by outmail.cs.huji.ac.il with esmtpsa id 1aHYYn-000GQs-Is; Fri, 08 Jan 2016 17:02:37 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: watchdog not rebooting From: Daniel Braniss In-Reply-To: <568F99E0.5080008@grosbein.net> Date: Fri, 8 Jan 2016 17:02:36 +0200 Cc: Freebsd hackers list Content-Transfer-Encoding: quoted-printable Message-Id: References: <95D6F157-70B1-48F3-B512-9A4B7D6F9EA4@cs.huji.ac.il> <568F9916.2000802@grosbein.net> <568F99E0.5080008@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 15:02:40 -0000 > On 8 Jan 2016, at 1:13 PM, Eugene Grosbein wrote: >=20 >>> on real hardware, with hardware watchdog, it does the right thing, = panics and reboots, >>> but on vmware, it enters the debugger, and =E2=80=98cont=E2=80=99 = will resume. >>> the kernel in both cases(it=E2=80=99s the same) has option KDB and = ALT_BREAK_TO_DEBUGGER >>>=20 >>> so how can I get the vm to reboot? >>=20 >> debug.debugger_on_panic=3D0 in the /boot/loader.conf and/or options = KDB_UNATTENDED in the kernel config. >=20 > Hmm, no - in case of watchdog, only kernel options KDB_UNATTENDED will = help, > debug.debugger_on_panic will not. >=20 I just tried an older kernel, 10.1, and it works as expected, with = debugger_on_panic =3D 0, it reboots. so something changed. I actually tried this on different hardware, and = so far it fails on 10.2 and works ok on 10.1=