Date: Sun, 4 Feb 2007 19:40:25 GMT From: Miles Nordin <carton@Ivy.NET> To: freebsd-sparc64@FreeBSD.org Subject: Re: sparc64/108757: cant boot if rtc stuffed, no means of recovery Message-ID: <200702041940.l14JePBH049763@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR sparc64/108757; it has been noted by GNATS.
From: Miles Nordin <carton@Ivy.NET>
To: freebsd-sparc64@freebsd.org
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: sparc64/108757: cant boot if rtc stuffed, no means of recovery
Date: Sun, 04 Feb 2007 14:18:57 -0500
--pgp-sign-Multipart_Sun_Feb__4_14:18:42_2007-1
Content-Type: text/plain; charset=US-ASCII
>>>>> "ag" == Andrew Grillet <Andrew> writes:
ag> The boot process fails because the rtc is invalid, and then
ag> reboots endlessly.(no dump device)
ag> This needs to be changed so that the user is offered the
ag> choice of having the rtc zapped to a sane state for subsequent
ag> resetting after reboot.
possibly there is a way to do this in OpenFirmware. I don't know
what's wrong with your RTC in particular. How do you know it's
corrupt? Did you see an error message?
This is for older Suns, but you could try parts of it:
http://www.squirrel.com/sun-nvram-hostid.faq.html
I don't think it's a good idea to add architecture-specific user
dialog to the bootup process. Whatever you want the kernel to
do---ignore the problem, work around the problem, fix the problem, do
nothing differently but print a better error message---it should
always do that thing, not ask questions.
--pgp-sign-Multipart_Sun_Feb__4_14:18:42_2007-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
iQCVAwUARcYxoYnCBbTaW/4dAQI0mgP9HF+T3AjWJ1ArjJ80ZO+wSegBndbj0vYQ
mJMff+RBFV0hq/+Ur8wNYnd3MPM59X0FKPmJ7Skj52c1e2uvyxwrsLLuBNSOBbhW
+v+PgwhvMV4JDTqcw4q8W7flu5yAA/yCHUlWFNLbkmHMzfukM07+jFNyI98rF+xu
Bb+4LsKqUp8=
=DqpK
-----END PGP SIGNATURE-----
--pgp-sign-Multipart_Sun_Feb__4_14:18:42_2007-1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702041940.l14JePBH049763>