Let me know where to pull the patch(es) and I will see if it fixes the oops on the 2.6.34-xxx kernel. > I believe I've found the source of this oops. > It's also the source of the garbage string characters > reported in other messages when the driver is removed.