Re: HCI Remote Name Request error "Page Timeout"

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

 



On Wed, Jul 18, 2012 at 3:04 PM, Andrei Emeltchenko
<andrei.emeltchenko.news@xxxxxxxxx> wrote:
> Hi Victor,
>
> On Wed, Jul 18, 2012 at 02:26:47PM +0800, victor yeo wrote:
>> > Hi Victor,
>> >
>> > * victor yeo <victoryeo1974@xxxxxxxxx> [2012-07-17 17:34:32 +0800]:
>> >
>> >> Hi,
>> >>
>> >> The hcidump program shows a remote name request "Page Timeout" error.
>> >> I do not understand the reason. The Bluez stack requests for remote
>> >> name, the device replied with 'Nonin_Medical_Inc._359443' twice, Then
>> >> Bluez stack requests again, got "Page Timeout" error, and connection
>> >> stops. What is the reason of this behavior?
>> >>
>> >> Thanks,
>> >> Victor
>> >>
>> >> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>> >>     bdaddr 00:1C:05:00:70:44 mode 2 clkoffset 0x0000
>> >> > HCI Event: Command Status (0x0f) plen 4
>> >>     Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
>> >> > HCI Event: Remote Name Req Complete (0x07) plen 255
>> >>     status 0x00 bdaddr 00:1C:05:00:70:44 name 'Nonin_Medical_Inc._359443'
>> >> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>> >>     bdaddr 00:1C:05:00:70:44 mode 2 clkoffset 0x0000
>> >> > HCI Event: Command Status (0x0f) plen 4
>> >>     Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
>> >> > HCI Event: Remote Name Req Complete (0x07) plen 255
>> >>     status 0x00 bdaddr 00:1C:05:00:70:44 name 'Nonin_Medical_Inc._359443'
>> >> < HCI Command: Remote Name Request (0x01|0x0019) plen 10
>> >>     bdaddr 00:1C:05:00:70:44 mode 2 clkoffset 0x0000
>> >> > HCI Event: Command Status (0x0f) plen 4
>> >>     Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
>> >> > HCI Event: Remote Name Req Complete (0x07) plen 255
>> >>     status 0x04 bdaddr 00:1C:05:00:70:44 name ''
>> >>     Error: Page Timeout
>
> BTW: What about adding timestamp, just wondering are those requests sent
> immediately one after one.
>
>> > Can you enable dynamic_debug on your kernel for the bluetooth module and post
>> > those logs to us? I wanna see what HCI is doing here.
>> >
>> >         Gustavo
>>
>> So i re-build the kernel with CONFIG_DYNAMIC_DEBUG, use the newly
>> built kernel, then run?
>>
>> echo -n 'module bluetoothd +p' >    <debugfs>/dynamic_debug/control
>
> something like this is enough:
>
>         echo 'file l2cap_core.c +fpt' > /debugfs/dynamic_debug/control; \
>         echo 'file hci_conn.c +fpt' > /debugfs/dynamic_debug/control; \
>         echo 'file hci_event.c +fpt' > /debugfs/dynamic_debug/control; \
>         echo 'file hci_core.c +fpt' > /debugfs/dynamic_debug/control"
>
> Best regards
> Andrei Emeltchenko
>

Hi,


I found out the root cause of the "Page Timeout" error. I swap in
another bluetooth module. The device data is received by Bluez.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux