[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4820D415.5090900@numericable.fr>
Date: Tue, 06 May 2008 23:56:37 +0200
From: Rufus & Azrael <rufus-azrael@...ericable.fr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
CC: Ingo Molnar <mingo@...e.hu>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Linux-kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem
error
Pallipadi, Venkatesh a écrit :
>
>
>
>> -----Original Message-----
>> From: Rufus & Azrael [mailto:rufus-azrael@...ericable.fr]
>> Sent: Tuesday, May 06, 2008 10:32 AM
>> To: Ingo Molnar
>> Cc: Pallipadi, Venkatesh; Siddha, Suresh B; Linux-kernel Mailing List
>> Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with
>> xf86MapVidMem error
>>
>> Ingo Molnar a écrit :
>>
>>> * Venki Pallipadi <venkatesh.pallipadi@...el.com> wrote:
>>>
>>>
>>>
>>>> Below is the patch to enable debug messages by a boot option
>>>> "debugpat".
>>>>
>>>>
>> Hi all,
>>
>> 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.
>>
>>
>
> Did you use "debugpat" kernel boot option after applying Ingo's patch?
> 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 and will give bigger dmesg output.
>
> Thanks,
> Venki
>
>
Hi,
Here is my dmesg.log file with CONFIG_X86_PAT=y and debugpat kernel boot
option.
Is it helpfull ? :-).
Regards.
View attachment "dmesg.log" of type "text/plain" (31419 bytes)
Powered by blists - more mailing lists