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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 05 Dec 2008 12:48:34 +0100
From:	Cédric Godin <cedric@...bone.be>
To:	Dave Airlie <airlied@...il.com>
CC:	Keith Packard <keithp@...thp.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Xorg crash at first start

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
> 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/
>   

Cedric
--
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/