From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: mhi resume failure on reboot with 6.13-rc2
Date: Wed, 11 Dec 2024 20:23:15 +0530 [thread overview]
Message-ID: <20241211145315.vaf7gbapieywcvau@thinkpad> (raw)
In-Reply-To: <Z1me8iaK7cwgjL92@hovoldconsulting.com>
Hi,
On Wed, Dec 11, 2024 at 03:17:22PM +0100, Johan Hovold wrote:
> Hi Mani,
>
> I just hit the following modem related error on reboot of the x1e80100
> CRD for the second time with 6.13-rc2:
>
> [ 138.348724] shutdown[1]: Rebooting.
> [ 138.545683] arm-smmu 3da0000.iommu: disabling translation
> [ 138.582505] mhi mhi0: Resuming from non M3 state (SYS ERROR)
> [ 138.588516] mhi-pci-generic 0005:01:00.0: failed to resume device: -22
> [ 138.595375] mhi-pci-generic 0005:01:00.0: device recovery started
> [ 138.603841] wwan wwan0: port wwan0qcdm0 disconnected
> [ 138.609508] wwan wwan0: port wwan0mbim0 disconnected
> [ 138.615137] wwan wwan0: port wwan0qmi0 disconnected
> [ 138.702604] mhi mhi0: Requested to power ON
> [ 139.027494] mhi mhi0: Power on setup success
> [ 139.027640] mhi mhi0: Wait for device to enter SBL or Mission mode
>
> and then the machine hangs.
>
> Do you know if there are any changes since 6.12 that could cause this?
>
Only 3 changes went in for 6.13-rc1 and they shouldn't cause any issues. One
caused the regression with pcim_iomap_region(), but you submitted a fix for
that and other two were trivial.
From the log, 'mhi mhi0: Resuming from non M3 state (SYS ERROR)' indicates that
the firmware got crashed while resuming. So maybe you should check with ath12k
folks.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-12-11 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 14:17 Johan Hovold
2024-12-11 14:53 ` Manivannan Sadhasivam [this message]
2024-12-11 15:03 ` Johan Hovold
2024-12-16 7:40 ` Manivannan Sadhasivam
2024-12-16 7:43 ` Manivannan Sadhasivam
2024-12-16 13:20 ` Johan Hovold
2024-12-16 14:13 ` Manivannan Sadhasivam
2024-12-16 16:25 ` Loic Poulain
2024-12-17 9:57 ` Johan Hovold
2024-12-18 8:48 ` Johan Hovold
2024-12-18 8:40 ` Johan Hovold
2024-12-18 11:38 ` Manivannan Sadhasivam
2024-12-18 12:02 ` Johan Hovold
2024-12-18 12:30 ` Manivannan Sadhasivam
2024-12-18 13:55 ` Johan Hovold
2024-12-18 14:09 ` Manivannan Sadhasivam
2024-12-18 14:26 ` Johan Hovold
2024-12-18 18:35 ` Manivannan Sadhasivam
2024-12-19 8:36 ` Johan Hovold
2025-01-08 12:49 ` Manivannan Sadhasivam
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=20241211145315.vaf7gbapieywcvau@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhi@lists.linux.dev \
/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®