Hi all,
-----Original Message-----
From: Rufus & Azrael [mailto:rufus-azrael@xxxxxxxxxxxxxx] Sent: Tuesday, May 06, 2008 2:57 PM
To: Pallipadi, Venkatesh
Cc: Ingo Molnar; Siddha, Suresh B; Linux-kernel Mailing List
Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem error
Pallipadi, Venkatesh a écrit :
Mailing List
-----Original Message-----
From: Rufus & Azrael [mailto:rufus-azrael@xxxxxxxxxxxxxx] Sent: Tuesday, May 06, 2008 10:32 AM
To: Ingo Molnar
Cc: Pallipadi, Venkatesh; Siddha, Suresh B; Linux-kernel
Ingo's patch?Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem errorDid you use "debugpat" kernel boot option after applying
Ingo Molnar a écrit :
* Venki Pallipadi <venkatesh.pallipadi@xxxxxxxxx> wrote:Hi all,
Below is the patch to enable debug messages by a boot option "debugpat".
I have applied the patch from Ingo and I put my
dmesg/syslog/messages/Xorg.log files in attached to help you to identify
the problem (two mails).
Hope it can help you.
With Ingo's patch, that option is needed to print more info(Not needed with one line change I sent you yday).
Also, 'dmesg -s 256000' will not truncate the msg at 32K andwill give bigger dmesg output.
Thanks,Hi,
Venki
Here is my dmesg.log file with CONFIG_X86_PAT=y and debugpat kernel boot option.
Is it helpfull ? :-).
Yes. This has some debug information in there. Did you see xf86MapVidMem error (I mean did you try to start X) before you captured this dmesg?
Thanks,
Venki