segun / bluecove

Automatically exported from code.google.com/p/bluecove
0 stars 0 forks source link

kernel failure #121

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,
i wonder if anyone ever had the same problem or maybe kwnow the solution. I'm 
using bluecove to send images to mobiles. My program is more complicated by 
what is running slowly. It is also multithread on one donle. The problem is: 
when I had managed to accelerate the appliacation I received a kernel failure. 
By accelerating I understand that images were sent more frequently. But also I 
reduced number of thread on dongle to four. After a while I get the following 
error :

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868238] Oops: 0000 [#1] SMP

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868241] last sysfs file: /sys/devices/pci0000:00/0000:00:03.3/usb1/1-1/1-1.1/1-1.1:1.0/bluetooth/hci0/hci0:47/type

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868339] Process java (pid: 21303, ti=c8df4000 task=f5bb3300 task.ti=c8df4000)

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868341] Stack:

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868362] Call Trace:

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868486] Code: fa 83 ec 04 89 04 24 8b 6c 24 18 8b 40 50 89 48 1c 89 e9 89 70 10 c7 40 18 00 00 00 00 89 68 0c 89 f0 e8 8f 64 f3 ff 85 c0 75 10 <8b> 5e 24 89 f9 89 f2 55 8b 44 24 04 ff 53 44 5d 5f 5b 5e 5f 5d

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868520] EIP: [<c11cbf3a>] __sock_sendmsg+0x34/0x4a SS:ESP 0068:c8df5de8

Message from syslogd@kolorowy at Dec  2 17:22:44 ...
 kernel:[33533.868525] CR2: 0000000000000b5e

There is no java exception - program is running, but no file is sent.
I'm using Debian, but it was also tested on Ubuntu. Different kernels (32 and 
64 bit) were also checked. Java is 32-bit.
Bluecove version :2.1.0.

Regards,
Agnieszka

Original issue reported on code.google.com by agnieszk...@gmail.com on 21 Dec 2010 at 11:00