On Mon, May 05, 2008 at 03:19:30PM -0700, Rufus & Azrael wrote:
quoted text
>    Suresh Siddha a ecrit :
>    > On Sun, May 04, 2008 at 11:03:52AM +0200, Rufus & Azrael wrote:
>    >  
>    >> Ingo Molnar a ecrit :
>    >>    
>    >>> * 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
>    >>>> [1]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
>    >
>    >  
>    Hi,
> 
>    Here is my dmesg with 2.6.26-rc1-git3 and CONFIG_X86_PAT=y
> 
>    Hope it can help you to fixe the crash.
> 

Did you capture dmesg after X failed to start? Only relevent msg I see is

quoted text
> [    0.333352] [drm] Initialized radeon 1.28.0 20060524 on minor 0
> [    0.334110] uvesafb: (C) 1988-2005, ATI Technologies Inc. RS69001.00, RS69001.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. RS69001.00, VBE v3.0
> [    0.351570] uvesafb: VBIOS/hardware supports DDC2 transfers
> [    0.410125] uvesafb: monitor limits: vf = 75 Hz, hf = 83 kHz, clk = 140 MHz
> [    0.410313] uvesafb: scrolling: redraw
> [    0.412579] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
> [    0.657370] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
> [    0.894472] Console: switching to colour frame buffer device 160x64
> [    0.894532] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
> [    1.128483] uvesafb: framebuffer at 0xf0000000, mapped to 0xffffc20010a80000, using 16384k, total 16384k
> [    1.128518] fb0: VESA VGA frame buffer device

Which seems to be mapping framebuffer successfully. 

Can you please try the patch below and capture the dmesg after you get the
above xf86MapVidMem error and send it. That should give us more information
on the failure.

Thanks,
Venki

Index: linux-2.6/arch/x86/mm/pat.c
===================================================================
--- linux-2.6.orig/arch/x86/mm/pat.c	2008-05-05 14:13:16.000000000 -0700
+++ linux-2.6/arch/x86/mm/pat.c	2008-05-05 15:54:21.000000000 -0700
@@ -7,6 +7,8 @@
  * Loosely based on earlier PAT patchset from Eric Biederman and Andi Kleen.
  */
 
+#define	DEBUG
+
 #include <linux/mm.h>
 #include <linux/kernel.h>
 #include <linux/gfp.h>
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/