LIBQMI APIs Response "Transaction timed out"

[Sai Chaitanya]

Hi,

We are seeing timeouts with different LIBQMI APIs on Sierra modems.
I have attached a sample test app and am waiting for your kind inputs.
I have been able to reproduce the issue very frequently with this test app
run on Linux host with Sierra modem connected via RED mangOH board.

Regards,
Sai.


On Mon, Aug 14, 2023 at 3:18 PM Aleksander Morgado <
aleksandermj at chromium.org> wrote:

> Hey,
>
> On Mon, Aug 14, 2023 at 3:05 PM Sai Chaitanya <msaichaitanya at gmail.com>
> wrote:
> >
> > Thank you for your response.
> > I have used four different clients DMS, WDS, NAS and UIM.
> > When I allocate clients, I notice that same client ID is allocated for
> WDS and NAS
> >
> > DMS client allocated successfully with ID: 1
> > WDS client allocated successfully with ID: 3
> > NAS client allocated successfully with ID: 3
> > UIM client allocated successfully with ID: 2
> >
> > I am not sure if this is an issue. It is hard to say, since it works
> fine most of the time, though the same ID is assigned to two different
> services.
>
> That is not a problem. The client id is unique per service.
>
> > But sometimes, the program either timesout or gets stuck for a long time
> in
> qmi-endpoint-qmux.c->input_ready_cb()->g_unix_input_stream_read()->g_poll(),
> as show by my gdb trace.
> >
> > That is why I have shared a sample code, to understand if I am missing
> something fundamental regarding usage of the QMI APIs.
>
> Ah, just saw the test app you shared. Will try to look at it at some point.
>
> --
> Aleksander
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20231115/00dffd4c/attachment.htm>