Hi
This message popped up infrequently on my FreeBSD 3.x as well. It is not
specific to 4.x. Now that I run 4.2, I still get the message once in a
while.
The fact that other OSs don't report the condition does not mean it does
not occur. I had a NT box that was slow as hell. I eventually put FreeBSD
on it and my logs were full of hardware errors. After correcting the
hardware the box ran like a dream. Under NT I had no idea what was wrong
as it didn't bother reporting the condition.
Michael
On Thu, 18 Jan 2001, Dennis wrote:
>
> >
> >
> > > What exactly is the hardware problem..and if you've identified it why is
> > > there no simple workaround after all this time (or is there)?
> >
> >You should read the i8259 datasheet, or the datasheet for any device
> >embedding a macrocell which emulates it, and once you read the section on
> >spurious interrupts all should become clear.
>
> 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?
>
> Or did someone just decide it was a neat idea to spit information onto the
> screen about a condition that you cant do anything about? Previous versions
> of freebsd dont complain with the same hardware, nor do other OS's.
>
> Dennis
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
