From owner-freebsd-hackers Thu Jan 18 14:31:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 5403E37B401 for ; Thu, 18 Jan 2001 14:30:54 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IMjYQ01614; Thu, 18 Jan 2001 14:45:34 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101182245.f0IMjYQ01614@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: stray irq 7 In-reply-to: Your message of "Thu, 18 Jan 2001 17:25:12 EST." <5.0.0.25.0.20010118165305.02eb76a0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 14:45:34 -0800 From: Mike Smith 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? 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. > 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. Actually, you can often do something about it. What's more curious here is that you're saying that the same problem doesn't manifest with other versions of FreeBSD. Since the code in question hasn't changed, I think you're looking at a symptom rather than a cause. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message