So your complete system hangs? This is different here. Unloading the rfcomm Module also does not change the situtation here. Having a closer look to the dmesg output I discovered, that the backtrace is different here to the bug message: [4389040.659000] Call Trace: [4389040.659000] [<c022008e>] tty_ioctl+0xbe/0x490 [4389040.659000] [<c0172ea7>] do_ioctl+0x67/0x80 [4389040.659000] [<c0173041>] vfs_ioctl+0x51/0x1f0 [4389040.659000] [<c015f19e>] do_sys_open+0x7e/0xd0 [4389040.659000] [<c017323d>] sys_ioctl+0x5d/0x90 [4389040.659000] [<c010302b>] sysenter_past_esp+0x54/0x79
complete dmesg output at: http://www.frahi.de/pub/dmesg-kpilotDaemonBug01.txt -- kpilot stops responding https://launchpad.net/bugs/43686 -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
