Date: Mon, 2 Aug 1999 17:29:45 +0930 From: Greg Lehey <grog@lemis.com> To: Mike Smith <mike@smith.net.au> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>, FreeBSD Committers <cvs-committers@FreeBSD.ORG> Subject: Re: Recent -CURRENT doesn't show process times on some hardware Message-ID: <19990802172945.V64532@freebie.lemis.com> In-Reply-To: <199908020517.WAA01494@dingo.cdrom.com>; from Mike Smith on Sun, Aug 01, 1999 at 10:17:51PM -0700 References: <19990801132751.S64532@freebie.lemis.com> <199908020517.WAA01494@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 1 August 1999 at 22:17:51 -0700, Mike Smith wrote: >> What makes this all the more puzzling is that it happens only on one >> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal >> Pentium machine of no particular lineage. Does this ring a bell with >> anybody? > > Do you have APM enabled? Do you have the "broken statclock" option > enabled? I do now :-) > Have you tried permuting these two? Yes. I needed apm and broken statclock, and that did it. Thanks. (And why did it only happen in the past couple of weeks? Probably because I migrated from 3.2 to -CURRENT a little while before that, and didn't realise that there were problems until some time later). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key 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?19990802172945.V64532>