From owner-freebsd-hackers  Thu Jan 18 10:48:26 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73])
	by hub.freebsd.org (Postfix) with ESMTP id 7DB0B37B404
	for <hackers@FreeBSD.ORG>; Thu, 18 Jan 2001 10:48:09 -0800 (PST)
Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1])
	by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id f0IIm3h29818;
	Thu, 18 Jan 2001 11:48:03 -0700
Message-Id: <200101181848.f0IIm3h29818@chopper.Poohsticks.ORG>
To: Dennis <dennis@etinc.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: stray irq 7 
In-reply-to: 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"
Content-ID: <29814.979843682.1@chopper.Poohsticks.ORG>
Date: Thu, 18 Jan 2001 11:48:03 -0700
From: Drew Eckhardt <drew@PoohSticks.ORG>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <5.0.0.25.0.20010118122059.01fb0b00@mail.etinc.com>, dennis@etinc.co
m writes:
>
>I know we've discussed this before. But I cant believe its a "hardware 
>problem".

Standard PIC behavior is to assert IRQ7 when an IRQ line is deasserted before 
it can be properly latched in.

>and if you've identified it why is there no simple workaround after all this 
>time (or is there)?

You can replace the device not keeping its interrupt line active long 
enough, or ignore the spurious int7 messages.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message