Date: Sun, 27 Jan 2002 11:34:26 +1030 From: Greg Lehey <grog@FreeBSD.org> To: Gabriel Ambuehl <gabriel_ambuehl@buz.ch> Cc: current@freebsd.org Subject: Re: microuptime went backwards Message-ID: <20020127113426.A94334@wantadilla.lemis.com> In-Reply-To: <76296244797.20020126162804@buz.ch> References: <76296244797.20020126162804@buz.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 26 January 2002 at 16:28:04 +0100, Gabriel Ambuehl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hello, > I just installed 5 CURRENT (20.1. snapshot) on a K6-2 500 whic was > previously running 4.4 STABLE without any problems but since CURRENT > is running, it keeps printing error messages about microuptime went > backwards which doesn't seem to hurt the system itself but is very > annoying to work with as it jams the whole screen in a matter of > seconds with error messages, thus making it impossible to really work > with the system. Now in some mailinglist archive it was suggested to > turn of the APM of the board (some Elitegroup Super Socket 7 board > based on a SiS chipset, can dig out the specs if that helps) but > that didn't help at all... Funny, it always does for me. Note that you have to build a kernel without APM support; just disabling it doesn't work. If that doesn't help, you're probably on your own. > Oh and please reply to me privately as well as I'm not reading this > list (too much traffic)! If you're running -CURRENT, you should be reading this list. If you don't have time, don't run -CURRENT. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020127113426.A94334>