Bug#422231: xserver-xorg-core: Found out the bug is only visible when running a 2.6.20 or 2.6.21 kernel.
Brice Goglin <Brice.Goglin@ens-lyon.org> kirjoitti:
Mika Rastas wrote:
> So about 5 boots later I'am firmly confident that the problem shows
> itself only on kernel 2.6.20. On this computer I have compiled my kernel from debian
> sources with the vesa-tng patch. On the other computer the kernel is the
> official debian kernel 2.6.20-1-k7. On 2.6.18 self compiled it's all
> good.
>
Do you see the problem with any kernel *without* this patch?
Yes in the other computer which has official debian kernel 2.6.20-1-k7.
What's your kernel command line?
Command line is root=/dev/sdb1 video=1280x1024@60 splash=silent
Does the problem go away if you remove all parameters on the command line?
Can't test right now as I'am at work. I'll try when I'am at home.
If framebuffer console is enabled, could you try without it?
Yes I'll try with the debian kernel. With atifb disabled on kernel command line.
The problem could be related to a conflict between X and the framebuffer
console.
Ok
> Also The black rectangles are only shown when in X. Not when I'am in a
> console with framebuffer.
>
> Might the kernel be the source of the bug after all? Or is the kernel
> doing something different and xorg is not upto it yet?
>
The kernel has to initialize some stuff and provide some mappings for X.
However, I would expect big X breakage in case of a bug in the kernel,
not such a "tiny" rendering artefact.
If the bug occurs with 2.6.20 and 2.6.21 but not in 2.6.18, it would be
very good to locate where it exactly appeared. I mean, try with 2.6.19,
and then try 2.6.18-rcX or 2.6.19-rcY, and then find the exactly git commit.
Yes it occurs on 2.6.20 and 2.6.21 but not 2.6.18 so I'll go for the 2.6.19 versions.
I'll compile a few tonight :)
Reply to: