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. -----Original Message----- From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth-owner@xxxxxxxxxxxxxxx] On Behalf Of Andrei Emeltchenko Sent: Tuesday, May 15, 2012 4:13 PM To: Zhang, Jingke Cc: linux-bluetooth@xxxxxxxxxxxxxxx Subject: Re: Bluez/Obexd upstream test result_20120515 Hi Jingke, On Tue, May 15, 2012 at 08:05:00AM +0000, Zhang, Jingke wrote: > https://bugs.meego.com/show_bug.cgi?id=25107 [obexd-server] timer_softirq cause kernel panic after FTP file transfer. > Obexd-server-0.45 (server daemon) will cause old kernel (3.0.27) panic after one file transferred, while obexd-0.44 server could work smoothly with same environment. The bug does not have good log to analyze. Best regards Andrei Emeltchenko -- 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 -- 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
