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.
[ 1.443353] [drm:i915_driver_load] *ERROR* failed to enable MSI
I expect noapic explains the MSI failure. I can boot without noapic if
necessary for testing, but I can't run with it because I get nasty hangs
& reboots. I don't see why that merits an *ERROR*... anyway, what I'm
interested in is the "Disabling tiling".
Actually... MSI does seem to be working for my ethernet.
$ grep eth /proc/interrupts
44: 2446 PCI-MSI-edge eth1
DRM wasn't using MSI in 2.6.27 though. So I'm still doubtful that the
MSI issue is really an "*ERROR*".
Thanks
Alan
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
