On Mon, Dec 13, 2010 at 7:12 PM, Jean Delvare <khali@xxxxxxxxxxxx> wrote: > Hi Alex, > > On Sun, 12 Dec 2010 23:33:42 -0500, Alex Deucher wrote: >> On Sun, Dec 12, 2010 at 7:31 PM, Alex Deucher <alexdeucher@xxxxxxxxx> wrote: >> > On Fri, Dec 10, 2010 at 7:01 AM, Jean Delvare <khali@xxxxxxxxxxxx> wrote: >> >> Any progress on this? Linus' latest kernel (2.6.37-rc5-git3) still has >> >> the problem. And this is a regression, so I don't think you can just >> >> ignore it. >> >> >> >> Is there a bug opened to track this bug already? I couldn't find one on >> >> bugzilla.kernel.org, but maybe I missed it. If there is none, I'll >> >> create one. >> > >> > Was it not fixed by this commit? >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a235e4c9302509ac5956bbbffa22eb5ed9fcdc54 > > Not, it wasn't. > >> > If not, open a bug and attach the dmesg with the error messages. >> >> Does the attached patch fix it? > > Yes it does, thanks! > > If you consider that user-space applications failing these tests are > broken, maybe you could use printk_once() to let them know? Otherwise I > suspect they will never get fixed. I think there's a way to get the > name of the faulty process and include it in the message. No its a problem with developing GPU drivers, you write some code in userspace that seems correct, it gets rolled out, you later add a new feature like tiling, find a bug in the kernel checker code, realise the userspace code is wrong, and give up and become a farmer. Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
