Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Suresh Siddha]

On Sun, Jun 15, 2008 at 04:02:10PM -0700, Frans Pop wrote:
> I've done 4 successive boots with the boot parameters as shown below.
> Each boot was basically: set correct parameters in grub -> login to KDE
>                          -> reboot and check for artifacts.
> 
> 1) (none)                      --> clean
> 2) vga=791                     --> artifacts
> 3) vga=791 nopat               --> clean
> 4) vga=791 video=vesafb:mtrr:3 --> artifacts
> 
> So the mtrr option did not help (if I passed it correctly; the double ":"
> is somewhat non-intuitive). The kernel log also does not show any
> difference I can see in the last boot, but I don't know if the mtrr option
> is supposed to show up in any way.

If the initlevel is '3', then the mtrr option will show up in /proc/mtrr
otheriwse not. In init level '5', X server will add the mtrr (irrespective
of boot option, if it's not already there) and will remove it when the X process
completes its execution.

Can you also please try if "mtrr:1" makes any difference. This will setup the
mapping as UC during boot. Apart from PAT WC mapping(which we shouldn't be using
in your current setup), UC MTRR should override all the other PAT mappings and
should be consistent across X and VT console mappings. As such, if the
problem is because of improper aliasing, then with this UC MTRR,
my understanding is that we shouldn't see any artifacts with the "mtrr:1".

with this mtrr:1, we should now see a UC mtrr setting in /proc/mtrr.

thanks,
suresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/