linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Amit Pundir <amit.pundir@linaro.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Sibi Sankar <quic_sibis@quicinc.com>,
	Will Deacon <will@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [GIT PULL] arm64 updates for 6.1-rc1
Date: Fri, 11 Nov 2022 23:09:52 +0530	[thread overview]
Message-ID: <20221111173952.GB5393@thinkpad> (raw)
In-Reply-To: <Y24uvyDJU3CL1jOi@arm.com>

On Fri, Nov 11, 2022 at 11:15:11AM +0000, Catalin Marinas wrote:
> On Tue, Nov 08, 2022 at 10:58:16PM +0530, Amit Pundir wrote:
> > On Tue, 25 Oct 2022 at 18:08, Amit Pundir <amit.pundir@linaro.org> wrote:
> > > On Wed, 12 Oct 2022 at 17:24, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > On Sat, Oct 08, 2022 at 08:28:26PM +0530, Amit Pundir wrote:
> > > > > On Wed, 5 Oct 2022 at 20:11, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > > > Will Deacon (2):
> > > > > >       arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()
> > > > >
> > > > > This patch broke AOSP on Dragonboard 845c (SDM845). I don't see any
> > > > > relevant crash in the attached log and device silently reboots into
> > > > > USB crash dump mode. The crash is fairly reproducible on db845c. I
> > > > > could trigger it twice in 5 reboots and it always crash at the same
> > > > > point during the boot process. Reverting this patch fixes the crash.
> > > > >
> > > > > I'm happy to test run any debug patche(s), that would help narrow
> > > > > down this breakage.
> [...]
> > > Further narrowed down the breakage to the userspace daemon rmtfs
> > > https://github.com/andersson/rmtfs. Is there anything specific in the
> > > userspace code that I should be paying attention to?
> 
> Since you don't see anything in the logs like a crash and the system
> restarts, I suspect it's some deadlock and that's triggering the
> watchdog. We have an erratum (826319) but that's for Cortex-A53. IIUC
> SDM845 has Kryo 3xx series which based on some random google searches is
> derived from A75/A55. Unfortunately the MIDR_EL1 register doesn't match
> the Arm Ltd numbering, so I have no idea what CPUs these are by looking
> at the boot log.
> 
> I wouldn't be surprised if you hit a similar bug, though I couldn't find
> anything close in the A55 errata notice.
> 
> While we could revert commit c44094eee32f ("arm64: dma: Drop cache
> invalidation from arch_dma_prep_coherent()"), if you hit a real hardware
> issue it may trigger in other scenario where we only do cache cleaning
> (without invalidate), like arch_sync_dma_for_device(). So I'd rather get
> to the bottom of this and potentially enable the workaround for this
> chipset.
> 
> You could give it a quick try to by adding the MIDR ranges for SDM845 to
> struct midr_range workaround_clean_cache[].
> 

I gave it a shot and indeed it fixes the crash on DB845.

> After that I suggest you raise it with Qualcomm to investigate. Normally
> we ask for an erratum number to enable a workaround and it's only
> Qualcomm that can provide one here.
> 

I will check with Qualcomm folks and update.

Thanks,
Mani

> -- 
> Catalin

-- 
மணிவண்ணன் சதாசிவம்

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-11-11 17:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 14:41 [GIT PULL] arm64 updates for 6.1-rc1 Catalin Marinas
2022-10-06 19:00 ` pr-tracker-bot
     [not found] ` <CAMi1Hd38YB2m_r=m0wuDz+wErii37fUq1BJnvN9=y6opDzo_Fw@mail.gmail.com>
     [not found]   ` <Y0aq8y5mEZi14lJ/@arm.com>
2022-10-18 16:05     ` Amit Pundir
2022-10-25 12:38     ` Amit Pundir
2022-11-08 17:28       ` Amit Pundir
2022-11-11 11:15         ` Catalin Marinas
2022-11-11 11:54           ` Robin Murphy
2022-11-11 17:39           ` Manivannan Sadhasivam [this message]
2022-11-11 19:18             ` Manivannan Sadhasivam
2022-11-14 14:09               ` Will Deacon
2022-11-14 14:54                 ` Catalin Marinas
2022-11-14 18:59         ` [GIT PULL] arm64 updates for 6.1-rc1 #forregzbot Thorsten Leemhuis
2022-12-07  5:36           ` Thorsten Leemhuis

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=20221111173952.GB5393@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_sibis@quicinc.com \
    --cc=robin.murphy@arm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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 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).