public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: David Airlie <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	abelay@mit.edu, Chris Wilson <chris@chris-wilson.co.uk>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: resource map sanity check conflict
Date: Mon, 13 Dec 2010 11:02:46 +0100	[thread overview]
Message-ID: <4D05EF46.6010306@gmail.com> (raw)
In-Reply-To: <201012081256.06513.bjorn.helgaas@hp.com>

On 12/08/2010 08:56 PM, Bjorn Helgaas wrote:
> On Monday, December 06, 2010 01:34:56 pm Bjorn Helgaas wrote:
>> On Monday, December 06, 2010 01:17:33 pm Jiri Slaby wrote:
>>> On 11/24/2010 08:22 PM, Bjorn Helgaas wrote:
>>>> On Wednesday, November 24, 2010 06:36:01 am Jiri Slaby wrote:
> ...
>>>>> pnp 00:0a: [mem 0xfed40000-0xfed44fff]
>>>>> pnp 00:0a: Plug and Play ACPI device, IDs ATM1200 PNP0c31 (active)
>>>>> ...
>>>>> resource map sanity check conflict: 0xfed40000 0xfed44fff 0xfed44000
> ...
>>>> Yes, this is related to the PCI resource changes I made recently.
>>>> We used to allocate PCI resources from low addresses first and work
>>>> upwards, and now we do the reverse.  So in 2.6.36, the "Intel Flush
>>>> Page" was probably allocated low in the [mem 0x7e000000-0xfebfffff]
>>>> window, but now we put it in the [mem 0xfed40000-0xfed4bfff] window:
>>>>
>>>>   pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
>>>>   pci_root PNP0A08:00: host bridge window [mem 0xfed40000-0xfed4bfff]
>>>>
>>>> I think the problem is that we ignore most of what ACPI tells us
>>>> about motherboard device resource usage.  We do have the "system"
>>>> driver, which reserves resources used by PNP0c01 and PNP0c02 devices,
>>>> but we don't do anything about other devices like the ATM1200/PNP0c31
>>>> device which, in your case, is using some of the space in that
>>>> [mem 0xfed40000-0xfed4bfff] host bridge window.
> 
>>> I created the bko entry some time ago:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=23802
> 
> I have a patch here for testing:
> 
>   https://bugzilla.kernel.org/attachment.cgi?id=39262

Yes, it works:
https://bugzillafiles.novell.org/attachment.cgi?id=404327

thanks,
-- 
js

  reply	other threads:[~2010-12-13 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 13:36 resource map sanity check conflict Jiri Slaby
2010-11-24 19:22 ` Bjorn Helgaas
2010-12-06 20:17   ` Jiri Slaby
2010-12-06 20:34     ` Bjorn Helgaas
2010-12-08 19:56       ` Bjorn Helgaas
2010-12-13 10:02         ` Jiri Slaby [this message]
     [not found] <fSnJM-6IJ-11@gated-at.bofh.it>
     [not found] ` <fSrkl-4sU-11@gated-at.bofh.it>
2010-11-25 13:20   ` Andreas Hartmann

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=4D05EF46.6010306@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=abelay@mit.edu \
    --cc=airlied@linux.ie \
    --cc=bjorn.helgaas@hp.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    /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