It seems to be appeared on 2.6.28 kernel. But not 2.6.26 kernel.
I got both as on my box as the gspca driver for my web camera seems only
worked on the 2.6.26 kernel.


On Thu, Jan 22, 2009 at 11:58 AM, Justin <jus...@j-schmitz.net> wrote:

> Willie Wong schrieb:
> > On Wed, Jan 21, 2009 at 12:22:17AM +0100, Penguin Lover Volker Armin
> Hemmann squawked:
> >
> >> On Mittwoch 21 Januar 2009, Willie Wong wrote:
> >>
> >>>   Recently when I quit the X server, the following can be seen in the
> >>>   sys log:
> >>>
> >>> Jan 20 18:06:34 e-nibbles mtrr: no MTRR for e8000000,2000000 found
> >>>
> >>>   and on the TTY where I issued X init, a similar message is shown,
> >>>   but the message is not echoed in /var/log/Xorg.0.log
> >>>
> >>>
> >> don't do it. Just don't do that. It should not be necessary. Instead
> look at
> >> the mtrr cleanup options in make menuconfig.
> >>
> >
> > Sorry, but this does not help. I have that after I terminate X, the
> > following line on the console:
> >
> > error setting MTRR (base = 0xe8000000, size = 0x02000000, type = 1)
> Invalid argument (22)
> >
> > and the following
> >
> > e-nibbles wwong # dmesg | tail -n 5
> > pci 0000:01:00.0: putting AGP V2 device into 4x mode
> > [drm] Setting GART location based on new memory map
> > [drm] Loading R200 Microcode
> > [drm] writeback test succeeded in 1 usecs
> > mtrr: no MTRR for e8000000,2000000 found
> > e-nibbles wwong # zgrep -i mtrr /proc/config.gz
> > CONFIG_MTRR=y
> > CONFIG_MTRR_SANITIZER=y
> > CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
> > CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
> > e-nibbles wwong # uname -a
> > Linux e-nibbles 2.6.28.1 #2 Thu Jan 22 14:28:04 EST 2009 i686 Intel(R)
> Pentium(R) M processor 1.60GHz GenuineIntel GNU/Linux
> >
> >
> > Is there anything I misconfigured?
> >
> > Any other ideas?
> >
> > Thanks,
> >
> > W
> >
> I read something about booting with "mtrr_cleanup_debug debug" in the
> command line. This will print you out what to set in mtrr_chunk_size in
> the commandline. Didn't test it but check that.
>
>

Reply via email to