linux-kernel - Re: Xorg crash at first start

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <49463C05.7000501@belbone.be>
Date:	Mon, 15 Dec 2008 12:14:13 +0100
From:	Cédric Godin <cedric@...bone.be>
To:	Dave Airlie <airlied@...il.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Xorg crash at first start

Dave Airlie wrote:
> On Mon, Dec 8, 2008 at 8:23 PM, Cédric Godin <cedric@...bone.be> wrote:
>   
>> Dave Airlie wrote:
>>     
>>> On Fri, Dec 5, 2008 at 9:48 PM, Cédric Godin <cedric@...bone.be> wrote:
>>>
>>>       
>>>> Dave Airlie wrote:
>>>>
>>>>         
>>>>> On Fri, Dec 5, 2008 at 12:26 AM, Cédric Godin <cedric@...bone.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@...thp.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@...thp.com>
>>>>>>    Signed-off-by: Dave Airlie <airlied@...hat.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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   
Hello,

here is the result. The X server started this time (with the irq 10
nobody cared).
But if I use kdm, i still have the problem.
I think that X is starting more slowly than before and that kdm gives up.
It seems i'm not the only one :
http://forums.gentoo.org/viewtopic-t-677324-highlight-kdm.html.

Cedric

View attachment "noX-drm-debug2.txt" of type "text/plain" (51094 bytes)