From: Rufus & Azrael <rufus-azrael@numericable.fr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem error
Date: Thu, 08 May 2008 09:08:39 +0200 [thread overview]
Message-ID: <4822A6F7.7010704@numericable.fr> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE010057B4@orsmsx423.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Pallipadi, Venkatesh a écrit :
>
>
>
>> -----Original Message-----
>> From: Rufus & Azrael [mailto:rufus-azrael@numericable.fr]
>> Sent: Wednesday, May 07, 2008 1:58 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 :
>>
>>>
>>>
>>> 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
>>>
>>>
>>>
>> Hi all,
>>
>> Yes, the error's message is in my Xorg.log file :-)
>>
>>
>
> One more piece of data I need. Can you please send the output of `cat /proc/mtrr` from this system (after the X failure has happened)
>
> Thanks,
> Venki
>
>
Hi Venki,
See my /proc/mtrr file attached.
Regards.
[-- Attachment #2: mtrr --]
[-- Type: text/plain, Size: 137 bytes --]
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0xf0000000 (3840MB), size= 16MB: write-combining, count=1
next prev parent reply other threads:[~2008-05-08 7:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 8:24 [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem error Rufus & Azrael
2008-05-04 8:52 ` Ingo Molnar
2008-05-04 9:03 ` Rufus & Azrael
2008-05-05 17:26 ` Suresh Siddha
2008-05-05 22:19 ` Rufus & Azrael
2008-05-05 23:25 ` Venki Pallipadi
2008-05-05 23:49 ` Ingo Molnar
2008-05-06 2:09 ` Venki Pallipadi
2008-05-06 11:55 ` Ingo Molnar
[not found] ` <4820962B.6050702@numericable.fr>
2008-05-06 20:34 ` Pallipadi, Venkatesh
2008-05-06 21:56 ` Rufus & Azrael
2008-05-06 22:05 ` Pallipadi, Venkatesh
2008-05-07 20:58 ` Rufus & Azrael
2008-05-07 22:12 ` Pallipadi, Venkatesh
2008-05-08 7:08 ` Rufus & Azrael [this message]
2008-05-08 13:18 ` Pallipadi, Venkatesh
[not found] ` <B5B0CFF685D7DF46A05CF1678CFB42ED20E04609@orsmsx423.amr.corp.intel.com>
2008-05-08 19:25 ` Venki Pallipadi
2008-05-08 20:08 ` Rufus & Azrael
2008-05-08 21:37 ` Venki Pallipadi
2008-05-08 21:42 ` H. Peter Anvin
[not found] ` <20080508215931.GA5035@jamoon.sc.intel.com>
2008-05-08 23:40 ` Venki Pallipadi
2008-05-08 23:54 ` H. Peter Anvin
2008-05-09 0:34 ` Venki Pallipadi
2008-05-09 0:49 ` H. Peter Anvin
2008-05-09 0:52 ` H. Peter Anvin
2008-05-09 13:46 ` Pallipadi, Venkatesh
2008-05-29 19:01 ` Venki Pallipadi
2008-05-29 21:51 ` Rufus & Azrael
2008-05-31 8:10 ` Ingo Molnar
2008-05-06 22:51 ` Venki Pallipadi
2008-05-07 7:06 ` Ingo Molnar
2008-05-07 21:42 ` Yinghai Lu
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=4822A6F7.7010704@numericable.fr \
--to=rufus-azrael@numericable.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@intel.com \
/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