Hi Peter On Tue, Aug 23, 2011 at 5:47 PM, Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> wrote: > David, > I know you already posted a patch for this (which looks ok for fixing > the oops specifically), but it'd still be helpful to see a debug kernel > log that led up to that. There's only a couple of reasons -- all bad -- > why the hci connection could not be found in the connection list while > the ctrl & intr sockets are connected (which are tested just prior to > hidp_add_connection). Sorry for the delay. I currently have no other machine to run a debug kernel and I really don't like provoking oopses on my working machine. However, the next days I will setup a machine and try to send a full trace. Are there any useful config symbols for bluetooth debug? Despite the standard kernel-wide debug symbols. What are possible reasons why an l2cap connection can be available without an underlying ACL connection? My fix eliminates the oops but I still think that it is not fixing the real problem (anyway, I'd really like to see it upstream). I will try to send a debug log if I can reproduce it. > Regards, > Peter Hurley Cheers David -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
