From: Manivannan Sadhasivam <mani@kernel.org>
To: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Pranav Mahesh Phansalkar <pranav.phansalkar@oss.qualcomm.com>,
Chris Lew <christopher.lew@oss.qualcomm.com>,
Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] net: qrtr: don't lose name server packets behind the HELLO gate
Date: Mon, 26 Oct 2026 20:20:06 +0530 [thread overview]
Message-ID: <at9n5CR6de3echo_@debian> (raw)
In-Reply-To: <20261019-upstream-qrtr-hello-gate-fix_b4-v1-0-bd420aec171b@oss.qualcomm.com>
Hi Igor,
On Mon, Oct 19, 2026 at 01:12:00PM +0200, Igor Opaniuk wrote:
> Since commit 544d85de4dc2 ("net: qrtr: Send HELLO message on endpoint
> register") the core refuses every non-HELLO packet to a node until the
> HELLO to it has been sent, and retries a HELLO that cannot be sent yet
> 100 ms later. A freshly booted remoteproc has no glink rx intents, so
> the first HELLO fails, and the name server's announcements in that
> window (the replies to the remote's HELLO and the NEW_SERVER broadcasts
> of local servers) are dropped for good. The name server then also skips
> the lookup notifications for a server whose broadcast failed.
>
> On QCM2290 (Arduino UNO Q) this stalls the modem in about one boot in
> five: it waits for the RMTFS service, which rmtfs registers in the same
> instant the modem starts, until its watchdog fires 40 s later; WiFi,
> whose firmware runs on the modem, comes up a minute late.
>
> Patch 1 makes the name server carry on after a failed send (announce
> the remaining servers, notify the pending lookups). Patch 2 holds
> control packets for a node behind its HELLO and sends them right after
> it, instead of dropping them; data packets are still refused before the
> HELLO, so flow control is unchanged.
>
> Initially tested on the Arduino UNO Q (QRB2210) with v7.3-rc6 plus the board
> support it needs: 10 fresh boots and 10 modem stop/start cycles, no
> "failed to announce new service", no modem watchdog, WLAN firmware up
> 6.4-8.2 s after boot every time; unpatched, 2/10 boots and 1/18 restarts
> stalled. Built with W=1 on net/main; applies to next-20261016.
>
> I'm not deeply familiar with QRTR; an alternative would be to have the
> core trigger announce_servers() for the node once its HELLO is sent.
> Happy to rework it that way if preferred.
>
Thanks for the series. There is already a patch floating [1] to fix the issue
you are trying to fix and it looks simple compared to this series.
But still, this series is useful, atleast patch 1. So you can resend this series
on top of v3 of [1] after fixing Sashiko's comments.
- Mani
[1] https://lore.kernel.org/netdev/20261022163116.1042-1-26rote@gmail.com
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2026-10-26 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 11:12 Igor Opaniuk
2026-10-19 11:12 ` [PATCH 1/2] net: qrtr: ns: keep going when an announcement cannot be sent Igor Opaniuk
2026-10-23 5:14 ` netdev-bot+sashiko
2026-10-19 11:12 ` [PATCH 2/2] net: qrtr: hold control packets behind the HELLO gate instead of dropping them Igor Opaniuk
2026-10-23 5:14 ` netdev-bot+sashiko
2026-10-26 14:50 ` Manivannan Sadhasivam [this message]
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=at9n5CR6de3echo_@debian \
--to=mani@kernel.org \
--cc=christopher.lew@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=deepak.singh@oss.qualcomm.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=igor.opaniuk@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pranav.phansalkar@oss.qualcomm.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®