From: "Dave Airlie" <airlied@gmail.com>
To: "Cédric Godin" <cedric@belbone.be>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Xorg crash at first start
Date: Sun, 14 Dec 2008 09:14:23 +1000 [thread overview]
Message-ID: <21d7e9970812131514v328eff11o9a2fcaa0b2cce1db@mail.gmail.com> (raw)
In-Reply-To: <493CF58F.9080503@belbone.be>
On Mon, Dec 8, 2008 at 8:23 PM, Cédric Godin <cedric@belbone.be> wrote:
> Dave Airlie wrote:
>> On Fri, Dec 5, 2008 at 9:48 PM, Cédric Godin <cedric@belbone.be> wrote:
>>
>>> Dave Airlie wrote:
>>>
>>>> On Fri, Dec 5, 2008 at 12:26 AM, Cédric Godin <cedric@belbone.be> 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 <keithp@keithp.com>
>>>>> 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 <keithp@keithp.com>
>>>>> Signed-off-by: Dave Airlie <airlied@redhat.com>
>>>>>
>>>>> 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.
>>
>
> First sorry for late answer.
> Here is the dmesg asked in attach (modprobe + startx).
> Hope it helps.
>
Can you check out latest Linus git and retry this.
Dave.
next prev parent reply other threads:[~2008-12-13 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 14:26 Cédric Godin
2008-12-04 14:32 ` Cédric Godin
2008-12-05 4:27 ` Dave Airlie
2008-12-05 11:48 ` Cédric Godin
2008-12-08 4:29 ` Dave Airlie
2008-12-08 10:23 ` Cédric Godin
2008-12-13 23:14 ` Dave Airlie [this message]
2008-12-15 11:14 ` Cédric Godin
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=21d7e9970812131514v328eff11o9a2fcaa0b2cce1db@mail.gmail.com \
--to=airlied@gmail.com \
--cc=cedric@belbone.be \
--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®