NetBSD Problem Report #42773

From gcw@primenet.com.au  Tue Feb  9 05:21:17 2010
Return-Path: <gcw@primenet.com.au>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 23BBA63BBAC
	for <gnats-bugs@gnats.NetBSD.org>; Tue,  9 Feb 2010 05:21:17 +0000 (UTC)
Message-Id: <20100209052112.2027.qmail@g.primenet.com.au>
Date: 9 Feb 2010 16:21:12 +1100
From: gcw@primenet.com.au
Reply-To: gcw@primenet.com.au
To: gnats-bugs@gnats.NetBSD.org
Subject: ichlpcib(4) and source code give wrong watchdog time limits
X-Send-Pr-Version: 3.95

>Number:         42773
>Category:       kern
>Synopsis:       The time boundaries for ichlpcib are give incorrectly in source and manual
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jruoho
>State:          closed
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 09 05:25:00 +0000 2010
>Closed-Date:    Sat Sep 24 23:41:25 +0000 2016
>Last-Modified:  Sat Sep 24 23:41:25 +0000 2016
>Originator:     Geoff C. Wing
>Release:        NetBSD 5.99.24
>Organization:
>Environment:
System: NetBSD g.primenet.com.au 5.99.24 NetBSD 5.99.24 (G) #0: Tue Feb 9 14:51:41 EST 2010 gcw@g.primenet.com.au:/usr/netbsd/src/sys/arch/i386/compile/G i386
Architecture: i386
Machine: i386
>Description:
	ichlpcib(4) reads:
		"The watchdog timer may be configured for ... 4 seconds (on
		ICH5 or older) min period and for a 39 seconds (on ICH5 or
		older) ... max period"
	My machines of that type allow 3 seconds to 38 seconds.  Outside that
	it provides a "wdogctl: WDOGIOC_SMODE: Invalid argument" error.

	src/sys/arch/x86/pci/ichlpcib.c:tcotimer_setmode() agrees with the
	manual page.  Maybe it was source of the manual information?

	The 82801AA/82801AB specification:
		http://download.intel.com/design/chipsets/datashts/29065503.pdf
	says section 8.9.3 (page 8-70): "The timer is clocked at approximately
	0.6 seconds, and this allows timeouts ranging from 2.4 to 38 seconds."

	Given we only use integers for wdogctl, this gives 3 to 38 seconds
	which matches my experience.

	I haven't found ICH6 (and onwards) reference yet to confirm times
	for those.

	My "ICH9" (82801IR) gives 2 seconds to 368 seconds, which doesn't
	match the manual/source either - it gives a maximum of 613 seconds
	which, I'm guessing, was calculated from the number of bits
	available, even though no such devices may exist.

>How-To-Repeat:
	Read
>Fix:
	Correct limits for ICH5 and below.
	Mention real limits for ICH6 and above.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->jruoho
Responsible-Changed-By: jruoho@NetBSD.org
Responsible-Changed-When: Tue, 22 Mar 2011 10:42:38 +0000
Responsible-Changed-Why:

I will try to deal with this.



State-Changed-From-To: open->closed
State-Changed-By: mrg@NetBSD.org
State-Changed-When: Sat, 24 Sep 2016 23:41:25 +0000
State-Changed-Why:
pgoyette fixed these a while back.


>Unformatted:

Home	PR Database Search