From owner-freebsd-current@FreeBSD.ORG  Mon Sep 29 13:21:22 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1A04B16A4B3; Mon, 29 Sep 2003 13:21:22 -0700 (PDT)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1740A43F93; Mon, 29 Sep 2003 13:21:19 -0700 (PDT)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP (SSL) id MUA74016;
        Mon, 29 Sep 2003 13:21:17 -0700
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id C3ED35D08; Mon, 29 Sep 2003 13:21:16 -0700 (PDT)
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: Message from John Baldwin <jhb@FreeBSD.org> 
	<XFMail.20030929160425.jhb@FreeBSD.org> 
Date: Mon, 29 Sep 2003 13:21:16 -0700
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20030929202116.C3ED35D08@ptavv.es.net>
cc: acpi-jp@jp.freebsd.org
cc: current@freebsd.org
Subject: Re: Odd ACPI behavior 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2003 20:21:22 -0000

> Date: Mon, 29 Sep 2003 16:04:25 -0400 (EDT)
> From: John Baldwin <jhb@FreeBSD.org>
> 
> 
> On 29-Sep-2003 Kevin Oberman wrote:
> > I recently noticed that, when I boot with ACPI on my IBM T30, I get
> > errors trying to probe the BIOS disabled sio1. This does not happen
> > under apm and happens twice(?) when booting with ACPI and happens even
> > though I have the line 'hint.sio.1.disabled="1"' in /boot/device.hints.
> >>From my dmesg:
> > sio0: type 16550A
> > sio1: configured irq 3 not in bitmap of probed irqs 0
> > sio1: port may not be enabled
> > acpi_cmbat0: <Control method Battery> on acpi0
> > acpi_cmbat1: <Control method Battery> on acpi0
> > acpi_acad0: <AC adapter> on acpi0
> > sio1: configured irq 3 not in bitmap of probed irqs 0
> > sio1: port may not be enabled
> > 
> > Any idea why this is happening? It does not seem to be a serious
> > issue, but it is very odd.
> > 
> > acpidump output, full dmesg, config and whatever available on request.
> 
> Do you kldload a module at some point during your boot?  If so, that
> would explain the double probe.

Yes, it would, but I am not loading any kernel modules except the
slightly automatic loads of ACPI, itself and a few others which should
not cause a probe: ntfs, linux, linprocfs, and daemon_saver.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634