Hi Colin, Yes, the bug is reproducible. (That's why i wrote this bug report in the first place :) ) The new 2.6.26-5-generic kernel oopses as well. The new oops message doesn't really differ from the original except for some different memory addresses. (Well, at least i think those are memory address.)
I managed to work around the error problem by blacklisting the rt2500usb driver. But why is this driver loaded in the fist place? I'm a little confused here. I rmmoded rt2500usb experimentally under 2.6.26-3 and didn't notice any difference. It seems this driver isn't used at all. (Is there any method to verify this?) Short: 2.6.26-3-generic rt2500usb and rt73usb are loaded --> works 2.6.26-4-generic and 2.6.26-5-generic rt2500usb is loaded --> oopses 2.6.26-4-generic and 2.6.26-5-generic with blacklisted rt2500usb --> works Regards, Christoph ** Attachment added: "oops 2.6.26-5.txt" http://launchpadlibrarian.net/16457009/oops%202.6.26-5.txt -- rt2x00 oopses in 2.6.26-4, regression against 2.6.24-3 https://bugs.launchpad.net/bugs/249242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
