From owner-freebsd-current Sun Mar 23 12:41:33 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06AD737B401; Sun, 23 Mar 2003 12:41:32 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29D1943F85; Sun, 23 Mar 2003 12:41:30 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id HAA19593; Mon, 24 Mar 2003 07:41:27 +1100 Date: Mon, 24 Mar 2003 07:41:26 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: ACPI problem: sio ports improperly attached with ACPI on Intel L440GX+ In-Reply-To: Message-ID: <20030324073217.O12413@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 23 Mar 2003, Robert Watson wrote: > When I boot with ACPI, the following appears in dmesg: > > Mar 23 14:14:31 none kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 > Mar 23 14:14:31 none kernel: sio0: port may not be enabled > Mar 23 14:14:31 none kernel: sio0 port 0x3f8-0x3ff irq 4 on acpi0 > Mar 23 14:14:31 none kernel: sio0: type 16550A > ... > > And sure enough, when using ACPI, interrupts don't work properly with the > serial ports, resulting in them essentially being unusable (stuff goes > out, but not in, except once in a while when the silo overflows). I > notice that, unlike my other 5.x boxes, sio0 and sio1 seem to attach to > acpi0, rather than isa0 as one would expect, so I guess it's not entirely > surprising that the interrupts aren't working right. > > Any suggestions about how I might go about diagnosing and remedying this > problem? Maybe something else steals their interrupts (it could be unconfigured ports sio[2-3]). I think the ports get probed again later with isa hints (ISTR seeing this for isa-pnp) but their "successful" attachment to acpi prevents this doing anything. The "configured irq N not in bitmap" warning used to be an error and this would have prevented attachment. You could try making it an error again. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message