NetBSD Problem Report #13875

Received: (qmail 15066 invoked from network); 5 Sep 2001 21:25:31 -0000
Message-Id: <20010905223038.A12681@nmrc.ie>
Date: Wed, 5 Sep 2001 22:30:38 +0100
From: Lars Hecking <lhecking@nmrc.ie>
Reply-To: Lars Hecking <lhecking@nmrc.ie>
To: gnats-bugs@gnats.netbsd.org
Subject: WARNING: bad date in battery clock
X-Send-Pr-Version: 3.95

>Number:         13875
>Category:       port-amiga
>Synopsis:       WARNING: bad date in battery clock
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amiga-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 05 21:26:00 +0000 2001
>Closed-Date:    Sun Sep 23 15:08:12 +0000 2001
>Last-Modified:  Sun Sep 23 15:08:12 +0000 2001
>Originator:     Lars Hecking
>Release:        NetBSD 1.5.1
>Organization:
AAAAA - All-Irish Association Against Acronym Abuse
>Environment:
	Amiga 3000 desktop w/ _int2 hack, CyberStorm MkIII 060/50, 2 HD's on
	the CyberSCSI controller, none on the A3k internal SCSI (doesn't work
	w/ CS installed); 64+16+2MB RAM.
System: NetBSD dusty 1.5.1 NetBSD 1.5.1 (DUSTY) #4: Tue Sep 4 00:29:33 IST 2001 root@dusty:/usr/src/sys/arch/amiga/compile/DUSTY amiga


>Description:
	"WARNING: bad date in battery clock" message upon boot. Analysis under
	AmigaOS shows that battery backed-up clock has suffered 'Amnesia' in
	both shared UNIX/AmigaDOS and AmigaDOS portion.
>How-To-Repeat:
	Boot into AmigaOS, fix 'Amnesia' with SCSIPrefs tool from Aminet, set
	clock.  Boot into NetBSD - clock setting is fine. Shutdown, boot into
	NetBSD again, and then the battery clock date is bad. This is what
	makes me think why NetBSDis at fault! The time is reset to the time of
	last logout.  This problem appeared only after upgrading from a G-Force
	040 board to the CS MkIII; the clock battery was replaced about a year
	ago, it should be fine.  dmesg is available on request.
>Fix:
	No idea. Could this be some sort of race?

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: is 
State-Changed-When: Sat Sep 22 14:23:37 PDT 2001 
State-Changed-Why:  
I can't confirm this behaviour with a 68040 CSPPC system on an A3000, using 
NetBSD-1.5.2 GENERIC. 

- what kernel are you using? 
- if it is a custom kernel, what is the configuration file? 
- yes, I'd like to see the dmesg. 

If possible, reply to this message so that your reply will be archived in 
the bug database. 
-is 
State-Changed-From-To: feedback->closed 
State-Changed-By: is 
State-Changed-When: Sun Sep 23 08:06:28 PDT 2001 
State-Changed-Why:  
Submitter writes that it turned out to be a hardware (battery?) problem. 
>Unformatted:

Home	PR Database Search