linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unable to transfer big files to Nokia N9
Date: Mon, 20 Dec 2021 22:31:45 +0100	[thread overview]
Message-ID: <a93c0fa7-7b84-6aea-265b-c913e0c84678@molgen.mpg.de> (raw)
In-Reply-To: <cf71bdea-ec22-e4c9-016c-69e94a130607@molgen.mpg.de>

Dear Luiz,


Am 01.12.21 um 23:07 schrieb Paul Menzel:

> Am 01.12.21 um 19:29 schrieb Luiz Augusto von Dentz:
> 
>> On Wed, Dec 1, 2021 at 9:39 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> 
>>> For the first time, I wanted to transfer a 2 MB PDF file from a Dell
>>> Latitude E7250 with Debian sid/unstable with Linux 5.16-rc1 to a Nokia
>>> N9 (MeeGo/Harmattan). Using the package *bluez-obexd* 5.61-1 and GNOME
>>> 41, the device was found, and paired fine. Then I selected to transfer
>>> the 2 MB file, and after starting for a second, it timed out after the
>>> progress bar moves forward ones and failed.
>>>
>>> The systemd journal contains:
>>>
>>>       obexd[21139]: Transfer(0x56243fe4f790) Error: Timed out waiting 
>>> for response
>>>
>>> Testing with a a 5 byte test text file, worked fine. Also testing with a
>>> Galaly M32, both files were transferred without problems (though slowly
>>> with 32 KB/s.)
>>>
>>> Trying to connect to the device with bluetoothctl failed for me, and the
>>> journal contained, it failed.
>>>
>>>       $ bluetoothctl
>>>       Agent registered
>>>       [bluetooth]# connect 40:98:4E:5B:CE:XX
>>>       Attempting to connect to 40:98:4E:5B:CE:XX
>>>       Failed to connect: org.bluez.Error.Failed
>>>
>>>       bluetoothd[21104]: src/service.c:btd_service_connect() 
>>> a2dp-source profile connect failed for 40:98:4E:5B:CE:B3: Protocol 
>>> not available
>>>
>>> As the Nokia N9 was once pretty popular in the Linux community, I am
>>> pretty sure, it used to work fine in the past, and there is some
>>> regression. It’d be great, if you could give me some hints how to
>>> further debug the issue.
>>
>> We will need some logs, obexd and btmon, if possible.
> 
> I only managed to get the btmon trace [1]. I did `sudo modprobe -r 
> btusb` and `sudo btmon -w /dev/shm/trace.log`.
> 
> Linux messages:
> 
>      [29880.100381] calling  btusb_driver_init+0x0/0x1000 [btusb] @ 28716
>      [29880.239603] usbcore: registered new interface driver btusb
>      [29880.239608] initcall btusb_driver_init+0x0/0x1000 [btusb] returned 0 after 135952 usecs
>      [29880.240706] Bluetooth: hci0: unexpected event for opcode 0x0500
>      [29880.241598] Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014
>      [29880.241605] Bluetooth: hci0: Intel device is already patched. patch num: 32
> 
>  From the system journal:
> 
>      Dez 01 22:52:19 ersatz obexd[21139]: Transfer(0x56243fe53dd0) Error: Timed out waiting for response

Were you able to see anything in the attached logs? If the obexd logs 
are missing, can you please tell how I should capture them?

I also tested with Ubuntu 20.04 (*linux-image-5.11.0-27-generic*) and 
21.10 (*linux-image-5.13.0-19-generic*) live systems booted from a USB 
storage device, and transferring `/usr/bin/systemctl` 
(`/lib/systemd/systemd`) with size of 1.8 MB worked fine.

Could there be a regression in that area? Unfortunately, it’s not easy 
for me to do a bisection on the device at hand.

(Would it be possible to do with QEMU and USB controller and Bluetooth 
device passthrough? How can I transfer the file on the command line so I 
wouldn’t need to install a desktop environment?)


Kind regards,

Paul


> [1]: https://owww.molgen.mpg.de/~pmenzel/trace.log.7z

  reply	other threads:[~2021-12-20 21:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 17:39 Paul Menzel
2021-12-01 18:29 ` Luiz Augusto von Dentz
2021-12-01 22:07   ` Paul Menzel
2021-12-20 21:31     ` Paul Menzel [this message]
2022-01-16 13:27       ` Paul Menzel
2022-01-28 10:36         ` Thorsten Leemhuis
2022-02-07 13:14           ` Paul Menzel
2022-02-08  7:49             ` Paul Menzel
2022-02-10 10:36               ` Thorsten Leemhuis
2022-02-11  8:29                 ` Paul Menzel
2022-02-11  8:59                   ` Thorsten Leemhuis
2022-02-11 16:10         ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a93c0fa7-7b84-6aea-265b-c913e0c84678@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --subject='Re: Unable to transfer big files to Nokia N9' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).