From owner-freebsd-current Thu Mar 4 1: 6:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A915C14E20 for ; Thu, 4 Mar 1999 01:06:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89031; Thu, 4 Mar 1999 10:05:17 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040905.KAA89031@freebsd.dk> Subject: Re: ata1: unwanted interrupt In-Reply-To: from Alex Zepeda at "Mar 3, 1999 2:57:50 pm" To: garbanzo@hooked.net (Alex Zepeda) Date: Thu, 4 Mar 1999 10:05:17 +0100 (CET) Cc: osa@etrust.ru, chris@calldei.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Thu, 4 Mar 1999, oZZ!!! wrote: > > > What exactly is 'unwanted interrupt' supposed to mean, and is it > > > likely to be a problem in my kernel configuration? (I can send a copy > > > of it on request...) > > i think it tell you about not used 2nd IDE controller... > > Nope. I've got three IDE/ATAPI devices, primary master, secondary > master+slave, and I still get it. I've got a PIIX4 controller. Its an artifact from the probes, it will go away as soon as I get the last bits of that running when interrupts are enabled. No need to worry about it though. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message