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

unexpected hard reset on devboard_lx



I'm working with the OpenBT stack on a pair of devboard_lx's and have run
into a problem. I have a script that periodically initiates a connection
between the systems, exchanges some data then disconnects. The connection
lasts around 30 seconds. After quite a few connect/disconnect cycles, one
of the devboards suddenly repeats some Bluetooth debug lines to the system
log, followed by a bunch of hex values, then hard resets. I've
intentionaly reproduced it a few times since it first happened. It doesn't
seem to matter which of the devboards initiates the connections, and both
the connecting and the receiving system have (in different trials)
exhibited the problem.

I'm running the latest devboard_lx software (2.1) and the most recently
released OpenBT (0.8), both built with the latest compiler tools
(cris-dist-1.16). The relevant lines from the system log are included
below, starting with the initial crash and running through the hard reset.

thanks in advance for any help,
	-patrick


============================================================
System Log
============================================================

<4>BT SYS: rfcomm_config_cfm: l2cap is now open
<4>BT (driver) bt_connect_ind: RFCOMM dlci : 0
<4>BT (driver) bt_connect_ind: RFCOMM dlci : 2
<4>BT SYS: bt_register_rfcomm: dlci 2 on line 0
<4>BT (driver) bt_connect_cfm: Line 0 [RCOMM]
<4>BT (driver) __bt_ioctl: BTREADREMOTEBDADDR
<4>BT SYS: get_remote_bd: 00:03:7a:00:08:26
<4>BT (driver) bt_open: Line 0
<4>BT (driver) Registering tty on line 0 (pppd)
<4>BT (driver) bt_set_termios: Forwarding to serial driver
<4>BT (driver) bt_chars_in_buffer: 0
<4>BT (driver) bt_chars_in_buffer: 0
<4>BT (driver) bt_disconnect_ind: RFCOMM dlci: 2
<4>BT (driver) bt_unregister_rfcomm: Line 0
<4>BT (driver) Upper tty still open...
<4>BT (driver) bt_hangupline: Hanging up line 0
<4>BT (driver) bt_flush_buffer: Ignored
<4>BT (driver) bt_hangup: Line 0 (nothing done) pid 2 (keventd)
<4>BT SYS: RFCOMM control ch disconnected (remotely) [line:0]
<4>BT (driver) bt_close: Line 0
<4>BT (driver) Unregistering tty on line 0
<4>BT SYS: rfcomm_disconnect_ind: remote cid 159
<4>BT SYS: l2cap channel (143,159) [RFCOMM] disconnected
<4>BT SYS: process_event: DISCONNECTION_COMPLETE Other End Terminated
Connection: User Ended Connection
<4>BT SYS: lp06b00>] [<60051e00>] [<60051fc4>] [<60051d34>] [<60006912>]
[<6005399e>] [<60006916>]
<4>       [<60006a88>] [<600068d6>] [<6000696a>] [<60006a62>] [<60006cf0>]
[<60006c3c>] [<60066532>] [<60063ce4>]
<4>       [<60063344>] [<60060b18>] [<6005fa2a>] [<6005dcf2>] [<6005d9ee>]
[<60056d66>] [<60008e54>] [<6000b46c>]
<4>       [<60008da0>] [<60008cc6>] [<60008a7c>] [<60052aee>] [<6005210c>]
[<60051b68>] [<60051ca2>]
<4>Code: d8 01 00 b0 41 d2 c9 db 69 d6 4d 9a (82) 93 fb 20 6a a6 0c 30 42
d2 6f 9e
<4>*** HARD RESET ***
gister_rfcomm: dlci 2 on line 0
<4>BT (driver) bt_connect_cfm: Line 0 [RCOMM]
<4>BT (driver) __bt_ioctl: BTREADREMOTEBDADDR
<4>BT SYS: get_remote_bd: 00:03:7a:00:08:26
<4>BT (driver) bt_open: Line 0
<4>BT (driver) Registering tty on line 0 (pppd)
<4>BT (driver) bt_set_termios: Forwarding to serial driver
<4>BT (driver) bt_chars_in_buffer: 0
<4>BT (driver) bt_chars_in_buffer: 0
<4>BT (driver) bt_disconnect_ind: RFCOMM dlci: 2
<4>BT (driver) bt_unregister_rfcomm: Line 0
<4>BT (driver) Upper tty still open...
<4>BT (driver) bt_hangupline: Hanging up line 0
<4>BT (driver) bt_flush_buffeUncompressing Linux...
Done. Now booting the kernel.