From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.sourceforge.net,
Kernel Testers List <kernel-testers@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling
Date: Mon, 23 Mar 2009 09:52:15 +0000 [thread overview]
Message-ID: <9b2b86520903230252m4d95351ejcd0742c9d271a2b5@mail.gmail.com> (raw)
In-Reply-To: <9b2b86520903230250q15ffd726k8f20bb13f8321f22@mail.gmail.com>
On 3/23/09, Alan Jenkins <sourcejedi.lkml@googlemail.com> wrote:
> On 10/27/08, Eric Anholt <eric@anholt.net> wrote:
>> On Mon, 2008-10-27 at 14:27 +0000, Alan Jenkins wrote:
>>> What does this mean, should I do anything about it? Is tiling nice to
>>> have?
>>>
>>> It sounds like GEM broke something - though maybe it just added a more
>>> verbose error report.
>>>
>>> System: EeePC 701
>>> Kernel: v2.6.28-rc1-5-g23cf24c
>>> Chipset: Intel mobile 915G-something
>>> Regretably necessary kernel boot option: noapic
>>>
>>>
>>> [ 1.438441] Linux agpgart interface v0.103
>>> [ 1.438441] agpgart-intel 0000:00:00.0: Intel 915GM Chipset
>>> [ 1.438441] agpgart-intel 0000:00:00.0: detected 7932K stolen memory
>>> [ 1.443353] agpgart-intel 0000:00:00.0: AGP aperture is 256M @
>>> 0xd0000000
>>> [ 1.443353] [drm] Initialized drm 1.1.0 20060810
>>> [ 1.443353] pci 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 5
>>> (level, low) -> IRQ 5
>>> [ 1.443353] pci 0000:00:02.0: setting latency timer to 64
>>> [ 1.443353] [drm:i915_gem_detect_bit_6_swizzle] *ERROR* Couldn't read
>>> from MCHBAR. Disabling
>>> tiling.
>>
>> This means that something went wrong with our detection of the
>> CPU-versus-GPU tiling swizzling mode, and object tiling under GEM will
>> be disabled as a result. I should get access to an eee 7xx on Thursday
>> to see what's up with it -- it's supposed to be just a normal 915gm as
>> far as I know.
>
> Any news about this tiling error?
>
> It's already been reported as a bug in Ubuntu Jaunty, in the belief
> that it "reduces video performance" [1], and is also mentioned on a
> similar bug in Fedora [2].
>
> [1] <https://bugzilla.redhat.com/show_bug.cgi?id=444328#c37>
> [2]
> <https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/329266>
Ah, I should also mention that I still see the error on the latest RC,
2.6.29-rc8.
Alan
prev parent reply other threads:[~2009-03-23 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:27 Alan Jenkins
2008-10-27 14:59 ` Alan Jenkins
2008-10-27 15:12 ` Alan Jenkins
2008-10-27 18:00 ` Eric Anholt
2009-03-23 9:50 ` Alan Jenkins
2009-03-23 9:52 ` Alan Jenkins [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=9b2b86520903230252m4d95351ejcd0742c9d271a2b5@mail.gmail.com \
--to=sourcejedi.lkml@googlemail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®