BT worked fine without any OOPs or soft lockups over 24 hours with 3.5.0 rc 5. So the bug did not appear in 3.5.0 rc 5.
As I said in my previous post, since testing the rc kernel Bluetooth has stopped working in all kernels, including the one from which I originally reported the bug (now Bluetooth always shows up as "disabled"). It is enabled in BIOS. I don't see how I can test anything until this is resolved, please see the forum post (link in previous message) for details. Help would be appreciated so I can continue to test and maybe one day take the Bluetooth keyboard out of the box. On 12-08-01 12:23 PM, Christopher M. Penalver wrote: > b: > > + So just to clarify, when you said in comment > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1023723/comments/3 : >> "I've had a chance to test 3.5.0 rc 5 for 24 hours or so with bluetooth on >> and the keyboard remained active and there were no Oops or soft lockups in >> the logs." > > is this still true or did it manifest itself again in that kernel as > well? > > + For regression testing purposes, could you please test for this > problem in Lucid using http://cdimage.ubuntu.com/lucid/daily- > live/current/ ? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023723 Title: WARNING: at /build/buildd/linux-3.2.0/fs/sysfs/dir.c:481 sysfs_add_one+0x9b/0xd0() To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1023723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
