Possibly related. I'm seeing a bluetooth drop out problem on a NC10 also. I'm writing software which does lots of discovery and obex pushing. After some time. Boom! - Kernel 2.6.31-16-generic. - Bluetooth fails to detect or send without obvious error. For example hcitool scan returns no results. Using the send file option from the bluetooth applet just results in nothing but an orange triangle, but no error message. - Power off/on fixes issue. Reboot does not. - Tried /etc/init.d/bluetooth restart, problem still occurs. - Tried rmmod, and modprobe on btusb, problem still occurs. - Booted into windows XP, and same fault (although i've not used bluetooth under windows before so can't be 100% it ever worked). Conclusion: hardware?, or somehow chipset getting into bad state??
Nothing interesting in dmesg apart from lines like this: [ 5101.707126] bluetoothd[1152]: segfault at 1e00000 ip 003d1779 sp bfd20a58 error 4 in libc-2.10.1.so[362000+13e000] Bluetooth device in question is the onboard one. lsusb: Bus 003 Device 002: ID 0a5c:2151 Broadcom Corp. Let me know what other info you need. Adam -- Samsung NC10 - bluetooth dies under load, needs restarting https://bugs.launchpad.net/bugs/480787 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
