From owner-freebsd-current@FreeBSD.ORG  Wed Apr 14 10:11:49 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 06FF716A4CE
	for <current@FreeBSD.org>; Wed, 14 Apr 2004 10:11:49 -0700 (PDT)
Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at
	[213.225.30.218])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3110243D5A
	for <current@FreeBSD.org>; Wed, 14 Apr 2004 10:11:48 -0700 (PDT)
	(envelope-from tilman@arved.at)
Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1])
	i3EHBldK022113
	for <current@FreeBSD.org>; Wed, 14 Apr 2004 19:11:47 +0200 (CEST)
	(envelope-from tilman@arved.at)
Received: (from tilman@localhost)
	by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i3EHBlEH022112
	for current@FreeBSD.org; Wed, 14 Apr 2004 19:11:47 +0200 (CEST)
X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to
	tilman@arved.at using -f
Date: Wed, 14 Apr 2004 19:11:46 +0200
From: Tilman Linneweh <tilman@arved.at>
To: current@FreeBSD.org
Message-ID: <20040414171146.GF64506@arved.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: 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: Wed, 14 Apr 2004 17:11:49 -0000

Hi,

With todays CURRENT my ata controllers are a bit more verbose:

atapci1: <VIA 6420 SATA150 controller> port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 20 at device 15.0 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd400
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xe800
atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xe400
ata5: at 0xe800 on atapci1
atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe000
atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xd800
ata6: at 0xe000 on atapci1
atapci2: <VIA 8237 UDMA133 controller> port 0xfc00-0xfc0f at device 15.1 on pci0
atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfc00
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x8 bytes rid 0x10 type 4 at 0x1f0
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x4 bytes rid 0x14 type 4 at 0x3f4
ata0: at 0x1f0 irq 14 on atapci2
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x8 bytes rid 0x18 type 4 at 0x170
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x4 bytes rid 0x1c type 4 at 0x374
ata1: at 0x170 irq 15 on atapci2

Everything seems to work normal............