From owner-freebsd-current@FreeBSD.ORG Wed Oct 21 09:22:48 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1F2910656AB; Wed, 21 Oct 2009 09:22:48 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 01C678FC0C; Wed, 21 Oct 2009 09:22:47 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA18451; Wed, 21 Oct 2009 12:22:45 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1N0XP3-0001hz-CD; Wed, 21 Oct 2009 12:22:45 +0300 Message-ID: <4ADED2D2.9050602@icyb.net.ua> Date: Wed, 21 Oct 2009 12:22:26 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090823) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: call for testing and review: new watchdog driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2009 09:22:49 -0000 Please test and/or review a new watchdog driver for watchdog timer found in SB600 and SB7xx south bridges, and also for watchdog hardware advertised/described via WDRT ACPI table. A tar file with the source file and module Makefile: http://people.freebsd.org/~avg/amdsbwd.tgz A full diff of the new driver against head source tree: http://people.freebsd.org/~avg/amdsbwd.diff If you have the mentioned hardware or if your ACPI provides WDRT table, please try this driver. WDRT presence can be checked with this command: acpidump -t | fgrep WDRT I am interested in what the driver prints to dmesg with debug.bootverbose=1, if it succesfully attaches and, obviously, if the driver does its job (i.e. resets system on timeout). That could be tested, for example, in single user mode with this command: watchdog -t 4 Thanks! -- Andriy Gapon