From: Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
To: dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling
Date: Mon, 27 Oct 2008 15:12:08 +0000 [thread overview]
Message-ID: <4905DA48.2070409@tuffmail.co.uk> (raw)
In-Reply-To: <4905D750.7000006-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Alan Jenkins wrote:
> 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.
There's no obvious difference in Xorg.log (compared to 2.6.27). In fact
it claims to have successfuly enabled tiling.
(**) intel(0): Tiling enabled
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Success.
So these new kernel error messages seem a bit random.
Thanks
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: dri-devel@lists.sourceforge.net
Cc: 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 15:12:08 +0000 [thread overview]
Message-ID: <4905DA48.2070409@tuffmail.co.uk> (raw)
In-Reply-To: <4905D750.7000006@tuffmail.co.uk>
Alan Jenkins wrote:
> 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.
There's no obvious difference in Xorg.log (compared to 2.6.27). In fact
it claims to have successfuly enabled tiling.
(**) intel(0): Tiling enabled
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Success.
So these new kernel error messages seem a bit random.
Thanks
Alan
next prev parent reply other threads:[~2008-10-27 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:27 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling Alan Jenkins
2008-10-27 14:27 ` Alan Jenkins
[not found] ` <4905CFC3.1060907-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2008-10-27 14:59 ` Alan Jenkins
2008-10-27 14:59 ` Alan Jenkins
[not found] ` <4905D750.7000006-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2008-10-27 15:12 ` Alan Jenkins [this message]
2008-10-27 15:12 ` Alan Jenkins
2008-10-27 18:00 ` Eric Anholt
[not found] ` <1225130422.4845.35.camel-yC3FP0L0upstnJUoGz2Qal6hYfS7NtTn@public.gmane.org>
2009-03-23 9:50 ` Alan Jenkins
2009-03-23 9:50 ` Alan Jenkins
[not found] ` <9b2b86520903230250q15ffd726k8f20bb13f8321f22-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-23 9:52 ` 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=4905DA48.2070409@tuffmail.co.uk \
--to=alan-jenkins-ccz0lq7mmjm9fhfhhbbuya@public.gmane.org \
--cc=dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.