>Number:         13875
>Category:       port-amiga
>Synopsis:       WARNING: bad date in battery clock
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amiga-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 05 14:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>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:
>Unformatted: