From owner-freebsd-hackers  Thu Jan 18 14:17: 1 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from etinc.com (et-gw.etinc.com [207.252.1.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8215837B401; Thu, 18 Jan 2001 14:16:44 -0800 (PST)
Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18])
	by etinc.com (8.9.3/8.9.3) with ESMTP id RAA41645;
	Thu, 18 Jan 2001 17:17:43 GMT
	(envelope-from dennis@etinc.com)
Message-Id: <5.0.0.25.0.20010118165305.02eb76a0@mail.etinc.com>
X-Sender: dennis@mail.etinc.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Thu, 18 Jan 2001 17:25:12 -0500
To: Mike Smith <msmith@freebsd.org>
From: Dennis <dennis@etinc.com>
Subject: Re: stray irq 7 
Cc: hackers@freebsd.org
In-Reply-To: <200101181953.f0IJrmQ00749@mass.osd.bsdi.com>
References: <Your message of "Thu, 18 Jan 2001 13:04:10 EST." <5.0.0.25.0.20010118122059.01fb0b00@mail.etinc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>
>
> > 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 majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message