Re: Problems with CF bluetooth (fwd) (fwd)

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > Thanks, Russell. Marcel, this is probably solution to that oops.
> 
> cool that you worked something out. Do you have a patch for me?

Well, I have that ugly workaround that helps me, but is wrong (as rmk
confirmed). His comment was:

|> Sep 29 15:42:34 amd kernel: Call Trace:
|> Sep 29 15:42:34 amd kernel:  [<c03f9df6>] hci_uart_flush+0x66/0x80
|> Sep 29 15:42:34 amd kernel:  [<c03f9e27>] hci_uart_close+0x17/0x20
|> Sep 29 15:42:34 amd kernel:  [<c03f9f86>]
|> hci_uart_tty_close+0x26/0x60
|> Sep 29 15:42:34 amd kernel:  [<c02a5ed7>] release_dev+0x587/0x670
|
|Looking at release_dev(), it does things in the following order:
|
|1. various sanity checks
|2. close the driver
|3. more sanity checks and other housekeeping
|4. close the ldisc
|5. reset the ldisc for the tty to N_TTY
|
|This means that bluetooth is calling into a TTY driver with a tty
|for which the driver has already shut down.  No surprise it oopses.
|Bluetooth should not call the driver during it's closedown.
|
|(There also appears to be an interesting race condition between the
|driver shutting down and the ldisc write functions getting to know
|about it... Alan?)

But no, I do not have patch for that.
								Pavel

-- 
if you have sharp zaurus hardware you don't need... you know my address
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/