From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-wireless@vger.kernel.org, imx@lists.linux.dev
Subject: Re: Linux v6.6 sporadic reboot failures with ath9k on i.MX6Q
Date: Fri, 1 Dec 2023 16:26:28 +0100 [thread overview]
Message-ID: <20231201162628.715983d6@booty> (raw)
In-Reply-To: <016b48b0-2021-434f-88c7-deb1bf08d14a@gmail.com>
Hello Florian,
On Wed, 29 Nov 2023 21:10:44 -0800
Florian Fainelli <f.fainelli@gmail.com> wrote:
> Do you have a reboot log with "initcall_debug debug" set on the kernel
> command line and if so, does it always point to the PCI bus shutting
> down the device drivers, pcie ports and ultimately the root complex?
>
> We have seen something similar before with ath10k_pci and our
> pcie-brcmstb driver which eventually was a result of having made
> incorrect assumptions while implementing the platform_driver::shutdown
> routine. There was a hard hang in ath10k_remove(), I do not recall the
> details, but we were definitively doing something improper there.
>
> imx6_pcie_shutdown() seems to much simpler, but my first guess would be
> there.
I had attempted using initcall_debug but the hang was happening on a
different line across tests, so it did not reliably point to a specific
place. Perhaps the serial port just stopped working before being able
to flush the last few lines.
I will have the shutdown code, even though it did not seems to the
problematic.
Thank you for your hints.
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-12-01 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 9:22 Linux v6.6 sporadic reboot failures with ath9k on i.MX6Q Luca Ceresoli
2023-11-30 5:10 ` Florian Fainelli
2023-12-01 15:26 ` Luca Ceresoli [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=20231201162628.715983d6@booty \
--to=luca.ceresoli@bootlin.com \
--cc=f.fainelli@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.