rfcomm / Bluetooth oops when disconnecting rfcomm session

[Ian Howson]

Binary package hint: linux-source-2.6.22

I've been using rfcomm + ppp to connect my laptop (running Ubuntu Gutsy) to my mobile phone for Internet access.

At some point, the connection will drop unexpectedly (more on this below). I verify that pppd is shut down and close the rfcomm connection with 'rfcomm release 1'. At some point after this, I'll usually get a kernel error of some sort - the exact message varies. It's always related to freeing kobjects.

I've attached a few different logs showing the issue - the one in the image caused the machine to hard lock.

The standard Ubuntu kernel logs will be attached in a minute.

---

Connection dropping unexpectedly: I'm not sure whether this is because the Bluetooth signal is getting out of range or the cell network is dropping the connection or what. The cell network (Three Australia) seems to silently 'hang up' the connection if I leave it idle for too long - constantly pinging a host definitely helps the connection stay alive and stave off the kernel bug.

[Leann Ogasawara (leannogasawara)]

The Hardy Heron Alpha2 release will be coming out soon (around Dec 20). It will have an updated version of the kernel. It would be great if you could test with this new release and verify if this issue still exists. I'll be sure to update this report when Alpha2 is available. Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[Leann Ogasawara (leannogasawara)]

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!