From: "H. Peter Anvin" <hpa@zytor.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andy Isaacson <adi@hexapodia.org>,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Chris Wright <chrisw@sous-sol.org>,
Matthew Wilcox <willy@linux.intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Date: Mon, 12 Apr 2010 18:51:45 -0700 [thread overview]
Message-ID: <4BC3CE31.2000100@zytor.com> (raw)
In-Reply-To: <201004121156.41716.bjorn.helgaas@hp.com>
On 04/12/2010 10:56 AM, Bjorn Helgaas wrote:
>
> Linux thinks the windows are:
> pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
> pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000effff]
> pci_root PNP0A03:00: host bridge window [mem 0x000f0000-0x000fffff]
>
> The 0xa0000-0xbffff one makes good sense. That's normally MMIO that's
> routed via PCI to the VGA device frame buffer, and we should be able
> to figure out how to avoid that area, e.g., by using BIOS info, PCI
> class codes, etc.
>
> Now we need to figure how to avoid the 0xc0000-0xeffff and 0xf0000-0xfffff
> windows. Maybe there's something special about how ACPI describes them.
>
> Or maybe we're just unlucky because these are the first windows in the
> _CRS list, and Linux tries them in order, while Windows uses a different
> strategy.
>
I strongly suspects that Windows knows that < 1 MB is special, and only
ever assigns it upon explicit allocation.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-04-13 1:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:54 [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff) Andy Isaacson
2010-04-07 1:08 ` Yinghai
2010-04-07 1:28 ` Andy Isaacson
2010-04-07 2:19 ` Yinghai Lu
2010-04-07 3:59 ` Bjorn Helgaas
2010-04-07 4:13 ` Andy Isaacson
2010-04-07 4:21 ` Bjorn Helgaas
2010-04-07 17:16 ` Andy Isaacson
2010-04-07 18:08 ` Bjorn Helgaas
2010-04-07 18:42 ` Andy Isaacson
2010-04-12 17:56 ` Bjorn Helgaas
2010-04-12 19:33 ` Andy Isaacson
2010-04-12 21:56 ` Matthew Wilcox
2010-04-13 2:14 ` H. Peter Anvin
2010-04-13 1:51 ` H. Peter Anvin [this message]
2010-04-09 19:10 ` Maciej Rutecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC3CE31.2000100@zytor.com \
--to=hpa@zytor.com \
--cc=adi@hexapodia.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=chrisw@sous-sol.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@linux.intel.com \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox