From owner-acpi-jp@jp.FreeBSD.org Thu Nov 21 02:19:40 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gAKHJe172255;
	Thu, 21 Nov 2002 02:19:40 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gAKHJe272250
	for <acpi-jp@jp.FreeBSD.org>; Thu, 21 Nov 2002 02:19:40 +0900 (JST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 14847 invoked from network); 20 Nov 2002 17:19:42 -0000
Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63])
          (envelope-sender <jhb@FreeBSD.org>)
          by mail14.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP
          for <acpi-jp@jp.FreeBSD.org>; 20 Nov 2002 17:19:42 -0000
Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1])
	by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gAKHJa2D035078;
	Wed, 20 Nov 2002 12:19:37 -0500 (EST)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.20021120121941.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: <20021121.014539.34605434.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 12:19:41 -0500
X-Sequence: acpi-jp 1946
Subject: [acpi-jp 1946] 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:
> John Baldwin <jhb@freebsd.org> wrote
>   in <XFMail.20021120094142.jhb@FreeBSD.org>:
> 
> jhb> Note that for some reason the request to allocate 0xb800-0xb80f,
> jhb> 0xb400-0xb403, and 0xac00-0xac03 all failed claiming that they
> jhb> are not valid.  They also claimed to only be 0x0-0xfff.  I'm
> jhb> kind of wondering if those error messages are incorrect and
> jhb> printing the wrong things to begin with.  Have you tried setting
> jhb> the loader tunable hw.pci_allow_unsupported_io_range to 1?
> 
>  Thanks for the clarification.  I tried hw.pci.allow_unsupported_io_range=1,
>  so pst(4) was finally recognized!  The result of dmesg at that time is
>  attached.
> 
>   # Sometimes "panic: ffs_valloc: dup alloc" occurs when pst0s1*
>   # is accessed, however...  But this is not ACPI-related, isn't it?

That is not ACPI related.  I believe it may be due to softupdates or
possibly other filesystem issues.

>  Just my curiosity, is this the problem caused by FreeBSD
>  or the badly-designed hardware?  And, are there any points to notice that
>  I should consider when using hw.pci.allow_unsupported_io_range tunable?

It is more FreeBSD's fault, specifically in its PCI code.

-- 

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