Re: 2.6.18-rc4-mm1 BUG, drm relatedy

From: Dave Airlie
Date: Mon Aug 21 2006 - 19:46:44 EST



I've been busy lately so having trouble following this stuff in a timely manner, I think this is an error path which the
userpsace code doesn't clean up properly, your patch is most definitely not correct..
I see. So this is most likely X's having trouble with the EFAULT on
unlock? I've gone through the 2.6.18-rc4-mm1 patches, and I couldn't
relate the updates and that new drm_unlock() error message. Any idea?

if I had to guess I'd say you have an AGP machine + card but no AGP support driver loaded...
I've got CONFIG_AGP=y and CONFIG_AGP_INTEL=y, do I need some more
options? What's strange is that this worked perfectly with
2.6.18-rc3-mm2...


Can you startup without X, do
echo 1 > /sys/modules/drm/parameters/debug

start X, and send me the dmesg output up to the oops?

Don't cc the list as I suspect it will be quite large..

Dave.
-
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/