From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Rufus & Azrael <rufus-azrael@numericable.fr>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
venkatesh.pallipadi@intel.com
Subject: Re: [2.6.25-git18 => 2.6.26-rc1-git1] Xorg crash with xf86MapVidMem error
Date: Mon, 5 May 2008 10:26:19 -0700 [thread overview]
Message-ID: <20080505172619.GD28173@linux-os.sc.intel.com> (raw)
In-Reply-To: <481D7BF8.4080405@numericable.fr>
On Sun, May 04, 2008 at 11:03:52AM +0200, Rufus & Azrael wrote:
> Ingo Molnar a écrit :
> >* Rufus & Azrael <rufus-azrael@numericable.fr> wrote:
> >>When upgrading to 2.6.25-git18 and above kernel this Xorg error occurs :
> >>
> >>xf86MapVidMem: Could not mmap framebuffer (0xf0000000,0x8000000) (Invalid
> >>argument)
> >>
> >>The latest working kernel was 25-git17 and perhaps is it related to
> >>http://lkml.org/lkml/2008/4/28/52
> >>
> >
> >does this X-does-not-start-up problem go away if you disable this
> >option:
> >
> >>CONFIG_X86_PAT=y
> >>
> >
> >?
> >
> Thanks for your help Ingo, all work fine when CONFIG_PAT=n :-)
hi, Can you please send us the "dmesg" output in the failing scenario
with PAT enabled, after the X crash?
thanks,
suresh
next prev parent reply other threads:[~2008-05-05 17:26 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 [this message]
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
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=20080505172619.GD28173@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rufus-azrael@numericable.fr \
--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