From: Knut Petersen <Knut_Petersen@t-online.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: i915_stolen_to_physical() broken in 3.11+
Date: Mon, 09 Sep 2013 14:06:33 +0200 [thread overview]
Message-ID: <522DB9C9.90502@t-online.de> (raw)
In-Reply-To: <CAKMK7uESP0wk-8OL9xembirDoBEh-K3Pwa=eK9Hy98L7R62S9w@mail.gmail.com>
On 09.09.2013 11:53, Daniel Vetter wrote:
> On Mon, Sep 9, 2013 at 11:39 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> On Mon, Sep 09, 2013 at 11:34:19AM +0200, Knut Petersen wrote:
>>> Problem:
>>> =======
>>>
>>> Your changes to i915_stolen_to_physical() (commit: eaba1b8f3379b5d100bd146b9a41d28348bdfd09) expose the following problem
>>>
>>> [ 2.272218] [drm:i915_stolen_to_physical] *ERROR* conflict detected with stolen region: [0x7f800000 - 0x80000000]
>> The fix, to reserve the stolen region in early x86 init, should be
>> upstream already.
> Atm it's stuck in drm-intel-fixes, but the pull request is already
> sent to Dave. So hopefully it'll land in upstream in a few days ...
> Poking Dave to speed stuff up ;-)
> -Daniel
>
Well, at least those two patches do fix the problem:
00100000-7f7effff : System RAM
00100000-005492f1 : Kernel code
005492f2-007d2fbf : Kernel data
0084e000-00dacfff : Kernel bss
7f7f0000-7f7f2fff : ACPI Non-volatile Storage
7f7f3000-7f7fffff : ACPI Tables
7f800000-7fffffff : reserved
7f800000-7fffffff : Graphics Stolen Memory
cu,
Knut
prev parent reply other threads:[~2013-09-09 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 9:34 i915_stolen_to_physical() broken in 3.11+ Knut Petersen
2013-09-09 9:39 ` Chris Wilson
2013-09-09 9:53 ` Daniel Vetter
2013-09-09 12:06 ` Knut Petersen [this message]
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=522DB9C9.90502@t-online.de \
--to=knut_petersen@t-online.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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