http://bugs.meego.com/show_bug.cgi?id=1371 Summary: SAN fail when syncing with N900 phone Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: Netbook OS/Version: IA Status: ASSIGNED Severity: major Priority: High Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: jingke.zhang(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 This is from http://bugzilla.moblin.org/show_bug.cgi?id=10483 Description From ZhangJingke 2010-04-15 22:39:19 PST (-) [reply] Created an attachment (id=4684) --> (http://bugs.meego.com/attachment.cgi?id=4684) [details] N900 connection failure log syncevolution 0.9.99.20 Description: =============== This is a regression. Sync with N900 will meet "SANFormat 12 failed", please see the attachment. ------- Comment #1 From Chen Congwu 2010-04-15 22:57:08 PST (-) [reply] ------- It might be the phone is not responding for some reason, try reboot it.. ------- Comment #2 From ZhangJingke 2010-04-15 23:12:37 PST (-) [reply] ------- (In reply to comment #1) I reboot phone, re-pair N900. Then it still fail with the same reason. :( ------- Comment #3 From Chen Congwu 2010-04-16 00:53:30 PST (-) [reply] ------- (In reply to comment #2) That's strange, works on my environment.. > (In reply to comment #1) > > > I reboot phone, re-pair N900. Then it still fail with the same reason. :( ------- Comment #4 From Chen Congwu 2010-04-16 02:17:38 PST (-) [reply] ------- (In reply to comment #2) The connect system call will fail immediately with error code '104' (that is 'Connection reset by peer'), that's different when failed with pairing problem, error code '111' ('Connection refused') Any way, since it failed early enough before involving the Obex library, I suspect it might be: 1) Phone side mess 2) Bluez library or driver change in the image Jingke, could you 1) retest with another N900? 2) retest with an older image? > (In reply to comment #1) > > > I reboot phone, re-pair N900. Then it still fail with the same reason. :( ------- Comment #5 From ZhangJingke 2010-04-19 20:12:18 PST (-) [reply] ------- (In reply to comment #4) I tried another N900, still the same failure. So, is it the error of "Nokia N900" template? I am sure N900 could sync in some old image. ------- Comment #6 From Chen Congwu 2010-04-20 00:44:36 PST (-) [reply] ------- (In reply to comment #5) right, this is a real problem Actually the failing scenario is as following: Moblin: connect() OK write() OBEX_Connect cmd read() --104 (Connection reset by peer) My PC: connect() OK write() OBEX_Connect cmd read() OK ------ see the detailed strace log: ---Moblin--- bind(8, {sa_family=AF_BLUETOOTH, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 10) = 0 fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(8, F_SETFL, O_RDWR) = 0 fstat64(8, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0 fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR) connect(8, {sa_family=AF_BLUETOOTH, sa_data="KO\324:\275\0\31\0\37\0\0\0\0\0"}, 10) = 0 time(NULL) = 1271795229 write(8, "\200\0\25\20\0\177\377F\0\16SYNCML-SYNC", 21) = 21 gettimeofday({1271795229, 351568}, {240, 0}) = 0 open("/home/moblin/.cache/syncevolution/nokia n900-2010-04-20-16-27/syncevolution-log.html", O_WRONLY|O_CREAT|O_APPEND, 0666) = 9 fstat64(9, {st_mode=S_IFREG|0644, st_size=21384, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb745b000 fstat64(9, {st_mode=S_IFREG|0644, st_size=21384, ...}) = 0 _llseek(9, 21384, [21384], SEEK_SET) = 0 write(9, "<li><i>[2010-04-20 16:27:09.351]"..., 61) = 61 close(9) = 0 munmap(0xb745b000, 4096) = 0 recv(5, 0x88cf218, 1023, MSG_PEEK|MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN|POLLOUT}], 2, -1) = 1 ([{fd=8, revents=POLLOUT}]) time(NULL) = 1271795229 select(9, [8], NULL, NULL, {1, 0}) = 1 (in [8], left {0, 986552}) read(8, 0x88b2ce8, 3) = -1 ECONNRESET (Connection reset by peer) ----------- --PC-- bind(8, {sa_family=AF_BLUETOOTH, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 10) = 0 fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(8, F_SETFL, O_RDWR) = 0 fstat64(8, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0 fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR) connect(8, {sa_family=AF_BLUETOOTH, sa_data="KO\324:\275\0\31\0\37\0\0\0\0\0"}, 10) = 0 time(NULL) = 1271748604 write(8, "\200\0\25\20\0\177\377F\0\16SYNCML-SYNC", 21) = 21 gettimeofday({1271748604, 731927}, {4294966816, 0}) = 0 open("/home/cchen35/.cache/syncevolution/n900-2010-04-20-15-30/syncevolution-log.html", O_WRONLY|O_CREAT|O_APPEND, 0666) = 9 fstat64(9, {st_mode=S_IFREG|0644, st_size=21220, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7851000 fstat64(9, {st_mode=S_IFREG|0644, st_size=21220, ...}) = 0 _llseek(9, 21220, [21220], SEEK_SET) = 0 write(9, "<li><i>[2010-04-20 01:30:04.731]"..., 61) = 61 close(9) = 0 munmap(0xb7851000, 4096) = 0 recv(5, 0x9c61160, 1023, MSG_PEEK|MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN|POLLOUT}], 2, -1) = 1 ([{fd=8, revents=POLLOUT}]) time(NULL) = 1271748604 select(9, [8], NULL, NULL, {1, 0}) = 1 (in [8], left {0, 911726}) read(8, "\240\0\32", 3) = 3 read(8, "\20\0\4\0\313K\315Y\241J\0\16SYNCML-SYNC", 23) = 23 ---------- ------- Comment #7 From pohly 2010-04-26 06:43:34 PST (-) [reply] ------- Congwu, Jingke, what is the status regarding this issue? We agreed that this looks like a regression in the underlying Bluetooth transports (Bluez, kernel). To proof that, we need to find an old image where this kind of sync still works, then install the same SyncEvolution version on a recent image and show that it fails. If SyncEvolution is the same in this test but the OS is not, then it should be investigated by the OS maintainers. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.