From owner-freebsd-stable Tue Jun 6 10:50:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 29EF237B567 for ; Tue, 6 Jun 2000 10:50:54 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id KAA11211; Tue, 6 Jun 2000 10:50:47 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200006061750.KAA11211@freeway.dcfinc.com> Subject: Re: using shared irq%d In-Reply-To: <200006061236.IAA70234@misha.privatelabs.com> from Mikhail Teterin at "Jun 6, 0 08:36:52 am" To: mi@privatelabs.com (Mikhail Teterin) Date: Tue, 6 Jun 2000 10:50:46 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Mikhail Teterin wrote: > Why am I seeing this every once in a while: > using shared irq7 > ? > > The only driver using irq7 seems to be the ppc... Here is the machine's > dmesg : I believe it was stated earlier on this list that any interrupt vectors not initialized in the hardware will be sent to the interrupt 7 handler. There was a recommendation from Intel quoted about how the int7 handler was supposed to be prepared for that. So, stray or spurrious interrupts could be the cause of your messages. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message