On Thu, Jan 18, 2001 at 02:45:34PM -0800, Mike Smith wrote:
> > Ok, so why is this only a problem in FreeBSD 4.x, or better yet, since its
> > a well known problem, why arent they handled more eloquently?
>
> I have no idea why it only happens to you with 4.x; the code that does
> that has been in place since the 2.x days. There's no real way to be
> more "eloquent" about it; you could just ignore them like everyone else
> does, but that doesn't alert you to misbehaving hardware, which is
> sometimes desirable.
At the risk of being dragged into this, I've see this kind of behaviour
on RELENG_3 also in the past.
Joe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
