From owner-freebsd-current@FreeBSD.ORG  Mon Feb 23 12:14:58 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 CB3F916A4CE
	for <current@freebsd.org>; Mon, 23 Feb 2004 12:14:57 -0800 (PST)
Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ADEAC43D39
	for <current@freebsd.org>; Mon, 23 Feb 2004 12:14:57 -0800 (PST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 5666 invoked from network); 23 Feb 2004 20:14:57 -0000
Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx)
	([216.27.160.63])          (envelope-sender <jhb@FreeBSD.org>)
	encrypted SMTP
	for <current@freebsd.org>; 23 Feb 2004 20:14:57 -0000
Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1])
	by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i1NKEr28031958;
	Mon, 23 Feb 2004 15:14:53 -0500 (EST)
	(envelope-from jhb@FreeBSD.org)
From: John Baldwin <jhb@FreeBSD.org>
To: current@FreeBSD.org
Date: Mon, 23 Feb 2004 14:53:25 -0500
User-Agent: KMail/1.6
References: <FE045D4D9F7AED4CBFF1B3B813C85337045D81E0@mail.sandvine.com>
In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C85337045D81E0@mail.sandvine.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200402231453.25746.jhb@FreeBSD.org>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx
cc: "'current@freebsd.org'" <current@freebsd.org>
Subject: Re: 5.2.1-RC2: could not get PCI interrupt routing table for ...
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, 23 Feb 2004 20:14:58 -0000

On Sunday 22 February 2004 12:57 pm, Don Bowman wrote:
> On a supermicro 6033P-8R system
> (http://www.supermicro.com/PRODUCT/SUPERServer/SuperServer6033P-8R.htm)
>
> I'm getting an error on bootup as below:
>
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pci0: <unknown> at device 0.1 (no driver attached)
> pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
> pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ -
> AE_NOT_FOUND
>  ...
> pcib4: <ACPI PCI-PCI bridge> at device 3.0 on pci0
> pcib4: could not get PCI interrupt routing table for \\_SB_.PCI0.HLC_ -
> AE_NOT_FOUND
> pci4: <ACPI PCI bus> on pcib4
> pci4: <base peripheral, interrupt controller> at device 28.0 (no driver
> attached)
>
> First question: Do i need to worry? This is from the install CD, i have not
> yet built a kernel.
>
> System is using ASR 2010S zero-channel raid, 6 75GB U320 15KRM disc, 4GB
> memory, 2x 2.8GHz Xeon. In the bios, I set the 'OS Type' to 'Other', should
> i try 'win2k' or something else to make it route interrupts differently?

As long as there are no actual devices on pci1 and pci4 other than pci-pci 
bridges, you are ok.  Your mptable doesn't list any devices on busses 1 and 
4, so you are probably fine.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org