From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Jenkins Subject: Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling Date: Mon, 27 Oct 2008 14:59:28 +0000 Message-ID: <4905D750.7000006@tuffmail.co.uk> References: <4905CFC3.1060907@tuffmail.co.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:sender; bh=qLFjbHhAxsl4szD+Sejz1gGEIout+xz3gEMvvVnNCSQ=; b=o4oOJQHWSS6k/hzPSpokdOhGjMjq+2SckhB7uXTrfUIPLTkU8drJQc07IIuvMurwWk r5LLBYLt8gCQwVLcsYLb7YHyALopoB2y2iOw0+TUqA/FfxC4YP/7qeU35rxgqvjumlaq W20sKoF0EQ+aW3vTpYLpiIzNSEQ+VqCZB6fu0= In-Reply-To: <4905CFC3.1060907-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Cc: Kernel Testers List , linux-kernel 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752475AbYJ0O6h (ORCPT ); Mon, 27 Oct 2008 10:58:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751327AbYJ0O61 (ORCPT ); Mon, 27 Oct 2008 10:58:27 -0400 Received: from ey-out-2122.google.com ([74.125.78.24]:4089 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751303AbYJ0O60 (ORCPT ); Mon, 27 Oct 2008 10:58:26 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :sender; b=Z41y4DLZqia+1RpOZpwIVjctJIQk3JAgiSNayMXWDbjDchovMjjclsqIZA0D9qA30E 4WugvdX3rt9G3qF/z3/IivukY82OqXY3pMw4zmWLOg1guIwh4eFKC/OODvtuh7A+HcPs pPDWnPXg41s7N41V/joqecHeWwwu/6f4WDpEo= Message-ID: <4905D750.7000006@tuffmail.co.uk> Date: Mon, 27 Oct 2008 14:59:28 +0000 From: Alan Jenkins User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: dri-devel@lists.sourceforge.net CC: Kernel Testers List , linux-kernel Subject: Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling References: <4905CFC3.1060907@tuffmail.co.uk> In-Reply-To: <4905CFC3.1060907@tuffmail.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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