From owner-acpi-jp@jp.FreeBSD.org Wed Nov 20 23:41:40 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gAKEfeg56604;
	Wed, 20 Nov 2002 23:41:40 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gAKEfd256598
	for <acpi-jp@jp.FreeBSD.org>; Wed, 20 Nov 2002 23:41:39 +0900 (JST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 23560 invoked from network); 20 Nov 2002 14:41:40 -0000
Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63])
          (envelope-sender <jhb@FreeBSD.org>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP
          for <acpi-jp@jp.FreeBSD.org>; 20 Nov 2002 14:41:40 -0000
Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4])
	by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gAKEfb2D034481;
	Wed, 20 Nov 2002 09:41:38 -0500 (EST)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.20021120094142.jhb@FreeBSD.org>
X-Mailer: XFMail 1.5.2 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20021120.225617.112624784.hrs@eos.ocn.ne.jp>
From: John Baldwin <jhb@freebsd.org>
To: Hiroki Sato <hrs@eos.ocn.ne.jp>
Cc: acpi-jp@jp.FreeBSD.org
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 20 Nov 2002 09:41:42 -0500
X-Sequence: acpi-jp 1944
Subject: [acpi-jp 1944] RE: supermicro's P4DPE motherboard
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: jhb@FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021111


On 20-Nov-2002 Hiroki Sato wrote:
> Hiroki Sato <hrs@eos.ocn.ne.jp> wrote
>   in <20021119.232756.35050056.hrs@eos.ocn.ne.jp>:
> 
> hrs>  The result of dmesg and acpidump are attached.  I do not know if this
> hrs>  is an ACPI-related issue or not, but if anyone knows what I should do,
> hrs>  please let me know.
> 
>  I tried the attached patch that Iwasaki-san suggested to me.  Although
>  some errors disappeared, pst driver could not be attached :-(

That patch isn't correct.  The acpi pci link driver should not be trying
to attach when it isn't used.  In an SMP kernel, we use I/O APICs to
route PCI interrupts, not the programmable interrupt routers hooked up
to the 8259A master/slave PICs.  Right now we don't properly route PCI
interrupts when using an APIC (something I am still working on) both
with and without ACPI, but that isn't your problem as far as I can tell.

The problem you are seeing is that for some reason the atapci(4) and
pst(4) drivers are asking PCI to give it resources that they don't have.
For example:

atapci2: <Promise TX2 ATA133 controller> port 0xb800-0xb80f,0xb400-0xb403,0xb000
-0xb007,0xac00-0xac03,0xa800-0xa807 mem 0xdb008000-0xdb00bfff irq 14 at device 2
.0 on pci4
pcib4: device atapci2 requested unsupported I/O range 0x0-0xfff (decoding 0xf000
-0xfff)
atapci2: Busmastering DMA not configured
pcib4: device atapci2 requested unsupported I/O range 0x0-0xfff (decoding 0xf000
-0xfff)
ata6: probe allocation failed
pcib4: device atapci2 requested decoded I/O range 0xb000-0xb007
pcib3: device atapci2 requested decoded I/O range 0xb000-0xb007
pcib1: device atapci2 requested decoded I/O range 0xb000-0xb007
pcib4: device atapci2 requested unsupported I/O range 0x0-0xfff (decoding 0xf000
-0xfff)
ata7: probe allocation failed

Note that for some reason the request to allocate 0xb800-0xb80f,
0xb400-0xb403, and 0xac00-0xac03 all failed claiming that they
are not valid.  They also claimed to only be 0x0-0xfff.  I'm
kind of wondering if those error messages are incorrect and
printing the wrong things to begin with.  Have you tried setting
the loader tunable hw.pci_allow_unsupported_io_range to 1?

-- 

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