From: Eric Anholt <eric@anholt.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
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, 27 Oct 2008 11:00:22 -0700 [thread overview]
Message-ID: <1225130422.4845.35.camel@gaiman.anholt.net> (raw)
In-Reply-To: <4905CFC3.1060907@tuffmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
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.36-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.
> [ 1.443353] [drm:i915_driver_load]o *ERROR* failed to enable MSI
Looks like we emit the error message even if your chipset doesn't
support MSI. That's a mistake, I'll get it cleaned up.
(MSI didn't actually get supported for integrated graphics until the
G965 for the desktop and GM45 for mobile, though it got supported for
ethernet and PEG earlier than that)
--
Eric Anholt
eric@anholt.net eric.anholt@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-27 18:00 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 [this message]
2009-03-23 9:50 ` Alan Jenkins
2009-03-23 9:52 ` Alan Jenkins
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=1225130422.4845.35.camel@gaiman.anholt.net \
--to=eric@anholt.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=dri-devel@lists.sourceforge.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®