Date: Thu, 2 May 2002 17:57:59 -0500 From: Will Andrews <will@csociety.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Doug Rabson <dfr@nlsystems.com>, Kris Kennaway <kris@FreeBSD.ORG>, Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_tc.c src/sys/sys timepps.h timetc.h Message-ID: <20020502225759.GS53809@squall.waterspout.com> In-Reply-To: <20020502153040.B4030@Odin.AC.HMC.Edu> References: <200204262151.g3QLp8m26766@freefall.freebsd.org> <20020426205129.A34126@citusc17.usc.edu> <200205020918.17192.dfr@nlsystems.com> <20020502153040.B4030@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 02, 2002 at 03:30:40PM -0700, Brooks Davis wrote: > I haven't tryed backing the commits out yet, but I'm seeing similar behavior > on my HP Omnibook 500. In my case, it's actually not quite hung. What > appears to be happening is that nothing is causing the console buffer to > actually flush. The system is up (sort of), but the only way to see the > console output is to cause a kernel printf, say be breaking in to the > debugger. The system is basicaly useless at that point and you can't > shutdown cleanly. Similar behavior manifests itself on my -current laptop dated before April 27. I.O.W. it appears to freeze but will flush the console if you break to the debugger then hit 'c'. I believe this was caused by an earlier change to the timecounter code. Unfortunately I didn't have time to investigate further. Regards, -- wca 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?20020502225759.GS53809>