From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756020AbYLHE3c (ORCPT ); Sun, 7 Dec 2008 23:29:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754838AbYLHE3W (ORCPT ); Sun, 7 Dec 2008 23:29:22 -0500 Received: from rn-out-0910.google.com ([64.233.170.184]:13746 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754875AbYLHE3V convert rfc822-to-8bit (ORCPT ); Sun, 7 Dec 2008 23:29:21 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=acHujL+PfJY4pJwFf8FWsZ260zy6TUyBjSd4KcT6m4hcp7FpGCB2+zxIbbizqWyGHs 7phxcIyxGllENAWE2nOuZKZ0rbAOnmwABxCkNU9vFaSrsWgwnL9XzGrKlTAjJj+k+aVi uvE0eRVbFZzeb80N8/X4Gxikc4JHkPQF9+sdo= Message-ID: <21d7e9970812072029w2b5f47ecoeb1d042880e4bff1@mail.gmail.com> Date: Mon, 8 Dec 2008 14:29:20 +1000 From: "Dave Airlie" To: "=?ISO-8859-1?Q?C=E9dric_Godin?=" Subject: Re: Xorg crash at first start Cc: "Linux Kernel" In-Reply-To: <49391512.4000604@belbone.be> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-Disposition: inline References: <4937E87C.6030106@belbone.be> <21d7e9970812042027w13271ceas91ecab87aa60562e@mail.gmail.com> <49391512.4000604@belbone.be> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 5, 2008 at 9:48 PM, Cédric Godin wrote: > Dave Airlie wrote: >> On Fri, Dec 5, 2008 at 12:26 AM, Cédric Godin wrote: >> >>> Hello, >>> >>> With the v2.6.28-rc7-105-gfeaf384 kernel, when booting my compaq with >>> attached config, the screen switches in graphical mode but then switches >>> back in textual mode with an 'irq10 nobody cared' error in dmesg (attached). >>> >>> If I restart kdm by hand, all is ok (i have my kdm) but the error yet >>> appears in dmesg (at each X start in fact). >>> >>> I bisected the problem (git bisect log attached) and found the following >>> commit as "culprit" : >>> >>> commit 52440211dcdc52c0b757f8b34d122e11b12cdd50 >>> Author: Keith Packard >>> Date: Tue Nov 18 09:30:25 2008 -0800 >>> >>> drm: move drm vblank initialization/cleanup to driver load/unload >>> >>> drm vblank initialization keeps track of the changes in driver-supplied >>> frame counts across vt switch and mode setting, but only if you let >>> it by >>> not tearing down the drm vblank structure. >>> >>> Signed-off-by: Keith Packard >>> Signed-off-by: Dave Airlie >>> >>> Reverting it brings back my X screen at first start. >>> >> >> Just for testing, can you try without using vesafb.... >> >> so remove the vga= line from the commandline or build the kernel >> without vesafb support. >> > I can confirm the problem without vesafb Can you boot to a runlevel with no X running do modprobe drm debug=1 or if drm is loaded echo 1 > /sys/module/drm/parameters/debug and then start X and attach the dmesg here. I've some ideas but no concrete reason for what might be going wrong. Dave.