In message <[EMAIL PROTECTED]>, Will Andrews writes
>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.

Do you see this with up to date -current ?

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to