Hi Luiz, I attached the sdp browse info into bug. Please check again, thanks! -----Original Message----- From: Luiz Augusto von Dentz [mailto:luiz.dentz@xxxxxxxxx] Sent: Tuesday, May 15, 2012 4:34 PM To: Zhang, Jingke Cc: Andrei Emeltchenko; linux-bluetooth@xxxxxxxxxxxxxxx Subject: Re: Bluez/Obexd upstream test result_20120515 Hi, On Tue, May 15, 2012 at 11:17 AM, Zhang, Jingke <jingke.zhang@xxxxxxxxx> wrote: > Well, I can understand only the kernel panic picture is not enough, > however, it is also hard to get call trace from my testing machine > because there is no serial port. :( > > But it is interesting that, same environment has no same panic if I used obexd-0.44. So, I have to notify 0.45 potential issue. I saw something related to timer.c, but I am not sure where bug is. Regarding bug 25109, this seems to be causing the problem: obex-client[969]: client/bluetooth.c:transport_connect() port 65535 Apparently this is a problem parsing the record, can you attach the output of sdptool browse to the bug. -- Luiz Augusto von Dentz -- 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
