[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

USB Module Hangs



Hi,

I am currently working on a routing project for Bluetooth which relies 
on BlueZ for and an Axis Devboard 82 to do the trick. I realize that 
this is not the mailing list for bluetooth, but I don't think my problem 
is a bluetooth problem. Even though several developers have Axis/BlueZ 
Problems, the topic doesn't seem to get much attention on any list (be 
it dev-axis or bluez-devel), so this list is as good as any...

I have 2 types of Bluetooth modules, one USB and one serial. In short, 
the axis board hangs, if attached to a USB-Bluetooth dongle, as soon as 
certain commands are executed. With the serial one, everything is just 
fine. Both are CSR BC02 rev. HCI 16.4.

Some commands do not cause a problem at all (hcitool inq). Others will 
crash immediately (hciconfig hci0 revision). The funny thing is, that 
certain commands can be executed once (!) and cause the crash during the 
second call:

[root@AxisProduct /]247# hciconfig hci0 up
[root@AxisProduct /]247# hcitool scan               <--- first call
Scanning ...
         00:02:FE:A4:70:1B       Eric's 6310i
[root@AxisProduct /]247# hcitool scan               <--- second call
Scanning ...                                        <--- that's it


The system outputs the following:

# Apr  7 03:20:09 AxisProduct login: ROOT LOGIN ON 0
00:40:8C:63:A5:<1>Unable to handle kernel access at virtual address 10000000
Oops: 0000
IRP: 9ffffb8e SRP: c001af74 DCCR: 000004a0 USP: 9ffff954 MOF: 00000000
  r0: c02301a8  r1: 00013d4b   r2: b0000003  r3: b0000003
  r4: c0063e44  r5: c0063e44   r6: 00000000  r7: b0000207
  r8: 00002000  r9: 00000006  r10: c03ec240 r11: c01204e8
r12: c02301a8 r13: 00000006 oR10: c03ec240
R_MMU_CAUSE: 10001000
Process hcitool (pid: 255, stackpage=c0ba8000)

Stack from 9ffff954:
        35556b96 355567e8 00000003 35567790 9ffffa0c 000803c8 0007762c 
0008059a
        3555c05a 35567238 00000000 355677c0 00000000 00000000 00000001 
00000009
        9ffffa20 000804d8 0000000b 000889b8 000807ac 35567292 35566b14 
9ffffa0c
Call Trace: [<c0063e44>] [<c0063e44>]
Stack from c0ba9de8:
        c0008a14 c0ba9f34 c0061d16 c0061e74 c01204e8 00000000 c0ba8000 
b0000003
        c0108da0 00000000 c0ba9ef0 c0061f46 10000000 c0ba9ef0 c0008a14 
c006481e
        00002000 b0000207 00000000 c0063e44 c0063e44 b0000003 c0b9a040 
10000000
Call Trace: [<c0008a14>] [<c0061d16>] [<c0061e74>] [<c0061f46>] 
[<c0008a14>] [<c006481e>] [<c0063e44>]
        [<c0063e44>] [<c0063e44>] [<c0093f92>] [<c0094204>] [<c00645ea>] 
[<c0061b2e>] [<c0063e44>] [<c0063e44>]
        [<c001af74>] [<c0092672>] [<c0063e44>] [<c00629fe>] [<c00628b6>]
Code:  Bad IP value.
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing


It seems to be some interrupt or maybe buffer problem. Speed could also 
be a problem since the serial cannot go faster than 115200. Anybody got 
any ideas on where to start looking?



-- 
Eric Chapman

-----------------
Lehrstuhl für Nachrichtentechnik
Universität des Saarlandes
Postfach 15 11 50
D-66041 Saarbrücken
Tel: +49 681 302 3975
Fax: +49 681 302 3972
Web: www.lnt.uni-saarland.de