From owner-freebsd-current@FreeBSD.ORG  Thu Apr 15 19:56:36 2004
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 68F5716A4D1
	for <freebsd-current@freebsd.org>;
	Thu, 15 Apr 2004 19:56:36 -0700 (PDT)
Received: from fep01-mail.bloor.is.net.cable.rogers.com
	(fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B616543D3F
	for <freebsd-current@freebsd.org>;
	Thu, 15 Apr 2004 19:56:33 -0700 (PDT)
	(envelope-from mikej@rogers.com)
Received: from [192.168.0.1] ([69.193.41.53])
	by fep01-mail.bloor.is.net.cable.rogers.comESMTP
	<20040416025512.QTGQ360069.fep01-mail.bloor.is.net.cable.rogers.com@[192.168.0.1]>;
	Thu, 15 Apr 2004 22:55:12 -0400
Received: from 192.168.0.200
        (SquirrelMail authenticated user mikej)
        by 192.168.0.1 with HTTP;
        Thu, 15 Apr 2004 22:56:29 -0400 (EDT)
Message-ID: <1073.192.168.0.200.1082084189.squirrel@192.168.0.1>
In-Reply-To: <20040415.141333.67561583.imp@bsdimp.com>
References: 
	<20040415.092434.22229494.imp@bsdimp.com><63887.66.11.183.182.1082059063.squirrel@69.193.41.47><20040415.140738.42906545.imp@bsdimp.com>
	<20040415.141333.67561583.imp@bsdimp.com>
Date: Thu, 15 Apr 2004 22:56:29 -0400 (EDT)
From: "Mike Jakubik" <mikej@rogers.com>
To: "M. Warner Losh" <imp@bsdimp.com>
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
X-Authentication-Info: Submitted using SMTP AUTH LOGIN at
	fep01-mail.bloor.is.net.cable.rogers.com from [69.193.41.53] using ID
	<mikej@rogers.com> at Thu, 15 Apr 2004 22:55:12 -0400
cc: freebsd-current@freebsd.org
Subject: Re: Is a BAD BAR something to worry about?
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: Fri, 16 Apr 2004 02:56:36 -0000

M. Warner Losh said:

> : : > In message: <20040414171146.GF64506@arved.at>
> : : >             Tilman Linneweh <tilman@arved.at> writes:
> : : > : atapci2: BAD BAR: skipping checks
> : : >
> : : > These are fine.
> : : >
> : : > Warner
> : :
> : : Well, they are kind of annoying. Is this temporary debugging stuff, or
> : : will this be permanent?
> :
> : Read the code:
> :
> : 		/* if (bootverbose) */
> : 		device_printf(child, "BAD BAR: skipping checks\n");
>
> eg, I plan on making it bootverbose fodder.

I see. Any ideas why my fdc stopped working and acpi reports a number of
errors? It used to work fine before.

What is all of this?

---
pci0: <serial bus, USB> at device 4.2 (no driver attached)
pci0:4:2: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
pci0: <serial bus, USB> at device 4.3 (no driver attached)
pci0:4:3: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
pci0: <bridge, PCI-unknown> at device 4.4 (no driver attached)
pci0:4:4: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
...
fdc0: cannot reserve I/O port range (1 ports)
---