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

Re: [bluetooth-dev] Cannot run stack in kernal mode.



Here is btd command and log file messages. I run btd on slakware 8.1 on both
device. Everything seem OK until I inquire. It can't find another device on
both side.


root@xxxxxxx./btd -R -m -e on -u /dev/ttyS2
Bluetooth Control Application
-----------------------------
Please reset HW board within 5 seconds
Running as server
Physdev /dev/ttyS2, btdev /dev/ttyBT0, speed 115200 baud
Registered bluetooth line discipline on /dev/ttyS2
Init stack
Setting write_scan_enable in Ericsson module!
Setting event filter in Ericsson module!
Setting baudrate in Ericsson module!
Now entering cmd line mode

Menu
------------------------
  inq <Max number of responses> (inquiry scan)
  rf_conn <xx:xx:xx:xx:xx:xx> <srv ch> <line>
  rf_send <nbr bytes> <nbr repeats> <line>
  rf_disc <line>
  rf_wait <line>
  me <1/0>
  setbd <xx:xx:xx:xx:xx:xx>
  readbd
  reset
  role_switch <xx:xx:xx:xx:xx:xx> <role> (0=master, 1=slave)
  ppp
  quit
> inq 3 3
Inquiry: Timer expired
>

Jan 21 15:32:55 network15 btd: Initiating signal handler
Jan 21 15:32:58 network15 kernel: hub.c: USB new device connect on bus1/2,
assigned device number 2
Jan 21 15:33:00 network15 btd: Starting SDP server [sdp_server]
Jan 21 15:33:00 network15 btd: Opening dev /dev/ttyS2
Jan 21 15:33:00 network15 btd: Opening dev /dev/ttyBTC
Jan 21 15:33:00 network15 kernel: usb.c: USB disconnect on device 2
Jan 21 15:33:00 network15 sdp_server: SDP Server startingJ


root@xxxxxxx./btd -R -m -e on -r
client -u /dev/ttyS0
Bluetooth Control Application
-----------------------------
Please reset HW board within 5 seconds
Running as client
Physdev /dev/ttyS0, btdev /dev/ttyBT0, speed 115200 baud
Registered bluetooth line discipline on /dev/ttyS0
Init stack
Setting write_scan_enable in Ericsson module!
Setting event filter in Ericsson module!
Setting baudrate in Ericsson module!
Now entering cmd line mode

Menu
------------------------
 inq <Max number of responses> (inquiry scan)
 rf_conn <xx:xx:xx:xx:xx:xx> <srv ch> <line>
 rf_send <nbr bytes> <nbr repeats> <line>
 rf_disc <line>
 rf_wait <line>
 me <1/0>
 setbd <xx:xx:xx:xx:xx:xx>
 readbd
 reset
 role_switch <xx:xx:xx:xx:xx:xx> <role> (0=master, 1=slave)
 ppp
 quit

> inq 3 3
Inquiry: Timer expired
>

Jan 21 15:36:09 chubby btd: Initiating signal handler
Jan 21 15:36:14 chubby btd: Opening dev /dev/ttyS0
Jan 21 15:36:14 chubby btd: Opening dev /dev/ttyBTC



I done it again by run btd-server on slakware 8.1 and run btd-client on
mandrake 7.2 Here is command and log file messages


root@xxxxxxx./btd -R -m -e on -u /dev/ttyS2
Bluetooth Control Application
-----------------------------
Please reset HW board within 5 seconds
Running as server
Physdev /dev/ttyS2, btdev /dev/ttyBT0, speed 115200 baud
Registered bluetooth line discipline on /dev/ttyS2
Init stack
Setting write_scan_enable in Ericsson module!
Setting event filter in Ericsson module!
Setting baudrate in Ericsson module!
Now entering cmd line mode

Menu
------------------------
  inq <Max number of responses> (inquiry scan)
  rf_conn <xx:xx:xx:xx:xx:xx> <srv ch> <line>
  rf_send <nbr bytes> <nbr repeats> <line>
  rf_disc <line>
  rf_wait <line>
  me <1/0>
  setbd <xx:xx:xx:xx:xx:xx>
  readbd
  reset
  role_switch <xx:xx:xx:xx:xx:xx> <role> (0=master, 1=slave)
  ppp
  quit
> inq 3 3
Inquiry: Timer expired
>

Jan 21 17:14:47 network15 btd: Initiating signal handler
Jan 21 17:14:49 network15 kernel: hub.c: USB new device connect on bus1/2,
assigned device number 8
Jan 21 17:14:52 network15 btd: Starting SDP server [sdp_server]
Jan 21 17:14:52 network15 sdp_server: SDP Server starting
Jan 21 17:14:52 network15 btd: Opening dev /dev/ttyS2
Jan 21 17:14:52 network15 btd: Opening dev /dev/ttyBTC
Jan 21 17:14:52 network15 kernel: usb.c: USB disconnect on device 8


[root@xxxxxxx./btd -m -u /dev/ttyS0 -R -r client -e on
Bluetooth Control Application
-----------------------------
Please reset HW board within 5 seconds
Running as client
Physdev /dev/ttyS0, btdev /dev/ttyBT0, speed 115200 baud
Registered bluetooth line discipline on /dev/ttyS0
Init stack
Setting write_scan_enable in Ericsson module!
Setting event filter in Ericsson module!
Setting baudrate in Ericsson module!
Now entering cmd line mode

Menu
------------------------
  inq <Max number of responses> (inquiry scan)
  rf_conn <xx:xx:xx:xx:xx:xx> <srv ch> <line>
  rf_send <nbr bytes> <nbr repeats> <line>
  rf_disc <line>
  rf_wait <line>
  me <1/0>
  role_switch <xx:xx:xx:xx:xx:xx> <role> (0=master,1=slave)
  ppp
  quit

> inq 3 3
Inquiry: Timer expired
>

Jan 21 16:55:47 kainui btd: Initiating signal handler
Jan 21 16:55:51 kainui kernel: usb.c: USB new device connect, assigned
device number 2
Jan 21 16:55:51 kainui kernel: usb.c: This device is not recognized by any
installed USB driver.
Jan 21 16:55:52 kainui btd: Opening dev /dev/ttyS0
Jan 21 16:55:52 kainui kernel: BT (driver) bt_open: Line 7
Jan 21 16:55:52 kainui kernel: BT (driver) Registeringtty on line 7 (btd)
Jan 21 16:55:52 kainui kernel: BT (driver) Now 1 open fd:s for ttyBTC [btd]
Jan 21 16:55:52 kainui kernel: BT (driver) bt_close: Line 7
Jan 21 16:55:52 kainui kernel: BT (driver) Unregistering tty on line 7
Jan 21 16:55:52 kainui kernel: BT (ldisc) bt_tty_open
Jan 21 16:55:52 kainui kernel: BT SYS: Setting BT driver to use serial tty
Jan 21 16:55:52 kainui btd: Opening dev /dev/ttyBTC
Jan 21 16:55:52 kainui kernel: BT (driver) bt_open: Line 7
Jan 21 16:55:52 kainui kernel: BT (driver) Registering tty on line 7 (btd)
Jan 21 16:55:52 kainui kernel: BT (driver) Now 1 open fd:s for ttyBTC [btd]
Jan 21 16:55:52 kainui kernel: BT (driver) bt_flush_buffer: Ignored
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising Bluetooth Stack
Jan 21 16:55:52 kainui kernel: BT SYS: Current HW: Ericsson
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising BTMEM [2500 bytes]
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising HCI
Jan 21 16:55:52 kainui kernel: BT SYS: HCI emulator off
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising HCI inbuffers [800]
Jan 21 16:55:52 kainui kernel: BT SYS: Reading buffer sizes in HW module
Jan 21 16:55:52 kainui kernel:
Jan 21 16:55:52 kainui kernel: HW module contains...
Jan 21 16:55:52 kainui kernel: 10 ACL buffers at 800 bytes
Jan 21 16:55:52 kainui kernel: 0 SCO buffers at 0 bytes
Jan 21 16:55:52 kainui kernel:
Jan 21 16:55:52 kainui kernel: BT SYS: Reading firmware info in HW module
Jan 21 16:55:52 kainui kernel: Ericsson HW revision info: ^M
Jan 21 16:55:52 kainui kernel:  Generated: 2000-04-28 15:54^M
Jan 21 16:55:52 kainui kernel:  Comment: CXC 125 244 P9A
Jan 21 16:55:52 kainui kernel:
Jan 21 16:55:52 kainui kernel: BT SYS: Host flow control not enabled
Jan 21 16:55:52 kainui kernel: BT SYS: M/S switch disabled
Jan 21 16:55:52 kainui kernel: BT SYS: Force M/S switch set to 0
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising L2CAP
Jan 21 16:55:52 kainui kernel: BT SYS: Local bd [44:44:44:44:44:44]
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising RFCOMM
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising SDP
Jan 21 16:55:52 kainui kernel: BT SYS: Init SDP as server
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising TCS
Jan 21 16:55:52 kainui kernel: BT SYS: Initialising TEST
Jan 21 16:55:52 kainui kernel: BT (driver) __bt_ioctl: HCIWRITECLASSOFDEVICE
Jan 21 16:55:52 kainui kernel: BT (driver) __bt_ioctl: HCISETLOCALNAME
Jan 21 16:55:52 kainui kernel: usb.c: USB disconnect on device 2
Jan 21 16:55:53 kainui kernel: BT (driver) Setting write scan enable: [0x3]
Jan 21 16:55:54 kainui kernel: BT (driver) __bt_ioctl: HCISET_EVENT_FILTER
Jan 21 16:55:55 kainui kernel: BT (driver) __bt_ioctl: Setting baudrate in
host controller to 115200
Jan 21 16:55:55 kainui kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl
0x5401 to n_tty line disc
Jan 21 16:55:55 kainui kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl
0x5402 to n_tty line disc
Jan 21 16:55:55 kainui kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl
0x5401 to n_tty line disc
Jan 21 16:55:55 kainui kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl
0x540b to n_tty line disc
Jan 21 16:56:41 kainui kernel: BT (driver) __bt_ioctl: HCINQUIRY
Jan 21 16:56:41 kainui kernel:
Jan 21 16:56:41 kainui kernel: hci_inquiry (9):
Jan 21 16:56:41 kainui kernel: 0x01 0x01 0x04 0x05 0x33 0x8b 0x9e 0x03 0x03
Jan 21 16:56:47 kainui kernel: inq_timeout: Timeout when waiting for inquiry
response



I have no idea why it cannot see another bluetooth device. Can you suggest
what should I do?
Thanks
Best regard.


----- Original Message -----
From: "Peter Kjellerstedt" <peter.kjellerstedt@xxxxxxx.com>
To: "'Tummaru'" <Tummaru@xxxxxxx.com>
Sent: Monday, January 21, 2002 4:39 PM
Subject: RE: [bluetooth-dev] Cannot run stack in kernal mode.


> On normal linux systems they are retrieved by klogd, and forwarded to
> syslogd, which means they should have appeared in your /var/log/messages
> (from which I guess you have extracted the log below). You could also try
> reading them directly from /proc/kmsg.
>
> //Peter
>
> > -----Original Message-----
> > From: Tummaru [mailto:Tummaru@xxxxxxx.com]
> > Sent: 21 January 2002 08:42
> > To: Peter Kjellerstedt
> > Subject: Re: [bluetooth-dev] Cannot run stack in kernal mode.
> >
> > Could you tell me how can I get the log messages from the kernal? I am
> > newbie about linux.
> >
> > ----- Original Message -----
> > From: "Peter Kjellerstedt" <peter.kjellerstedt@xxxxxxx.com>
> > To: "'Tummaru .com'" <tummaru@xxxxxxx.com>; "Bluetooth-dev"
> > <bluetooth-dev@xxxxxxx.com>
> > Sent: Monday, January 21, 2002 1:55 PM
> > Subject: RE: [bluetooth-dev] Cannot run stack in kernal mode.
> >
> > > If you provided the log messages from the kernel we might
> > > be able to see what is going on...
> > >
> > > //Peter
> > >
> > > > -----Original Message-----
> > > > From: Tummaru .com [mailto:tummaru@xxxxxxx.com]
> > > > Sent: Sunday, January 20, 2002 22:23
> > > > To: bluetooth-dev@xxxxxxx.com
> > > > Subject: [bluetooth-dev] Cannot run stack in kernal mode.
> > > >
> > > > I use openbt 0.0.8 on slakware 8.1 with ericsson bluetooth
> > > > application & training tool kit. I try to run btdm. But it
> > > > will hang and show the message
> > > >
> > > > root@xxxxxxx./btdm
> > > > -u /dev/ttyS2 -R
> > > > Please reset HW board within 5 seconds
> > > > Shutting down Bluetooth stack
> > > > Bluetooth stack shut down
> > > > Please reset HW board within 5 seconds
> > > > Shutting down Bluetooth stack
> > > > Bluetooth stack shut down
> > > >
> > > > Jan 21 03:52:02 network15 kernel: hub.c: USB new device connect on
> > > > bus1/2,assigned device number 2
> > > > Jan 21 03:52:04 network15 btduser: Starting SDP server [sdp_user]
> > > > Jan 21 03:52:04 network15 btduser: Opening dev /dev/ttyS2
> > > > Jan 21 03:52:05 network15 kernel: usb.c: USB disconnect on
> > > > device 2 Jan 21
> > > > 03:56:28 network15 btduser: Killing SDP server
> > > > Jan 21 03:56:28 network15 btduser: Shutting down bluetooth stack
> > > > Jan 21 03:56:28 network15 btduser: close_device
> > > > Jan 21 03:56:28 network15 btduser: close_device
> > > > Jan 21 03:57:17 network15 btdm: Bluetooth daemon starting
> > > > Jan 21 03:57:17 network15 sdp_server: SDP Server starting
> > > > Jan 21 03:57:32 network15 btdm: Registered bluetooth line
> > discipline
> > > > on/dev/ttyS2
> > > > Jan 21 03:57:37 network15 btdm: Init stack
> > > > Jan 21 03:57:41 network15 btdm: Init stack
> > > > Jan 21 03:57:46 network15 btdm: Init failed, lets try
> > restarting btd
> > > > Jan 21 03:57:46 network15 btdm: Shutting down bluetooth stack
> > > > Jan 21 03:57:46 network15 btdm: Restart...
> > > > Jan 21 03:57:47 network15 sdp_server: SDP Server starting
> > > > Jan 21 03:58:02 network15 btdm: Registered bluetooth line
> > > > discipline on /dev/ttyS2
> > > > Jan 21 03:58:07 network15 btdm: Init stack
> > > > Jan 21 03:58:11 network15 btdm: Init stack
> > > > Jan 21 03:58:15 network15 btdm: Init failed after second try,
> > > > giving up...
> > > > Jan 21 03:58:15 network15 btdm: Shutting down bluetooth stack
> > > >
> > > > So I change to run "btd" instead. I run it on 2 linux PC.
> > > > ./btd -R -u /dev/ttyS2 -m and
> > > > ./btd -R -u /dev/ttyS1 -m -r client
> > > > Everything seem no error. But when I try to use command "inq
> > > > <Max number of responses> (inquiry scan)" it cannot find another
> > > > bluetooth device like this.
> > > >
> > > > >inq 3 3
> > > > Inquiry: Timer expired
> > > >
> > > > I don't know what i am wrong. Can anyone tell me what should I do?
> > > > Thank everybody
> > > > Best regard.
> > >
> >
>
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com