From: Greg KH <gregkh@linuxfoundation.org>
To: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: SMMU Fault after setting RUN_STOP during gadget_pullup
Date: Fri, 23 Dec 2022 16:12:45 +0100 [thread overview]
Message-ID: <Y6XFbc4aSOh7KnsO@kroah.com> (raw)
In-Reply-To: <b116d857-572c-8fd5-d6d8-04ef3af7920c@quicinc.com>
On Fri, Dec 23, 2022 at 08:34:08PM +0530, Krishna Kurapati PSSNV wrote:
>
>
> On 12/23/2022 7:56 PM, Greg KH wrote:
> > On Fri, Dec 23, 2022 at 07:26:49PM +0530, Krishna Kurapati PSSNV wrote:
> > > Hi all,
> > >
> > > I am facing one SMMU fault with FAR=0x00 on current targets running on 5.10
> > > and 5.15 with following signature:
> >
> > What about 6.1?
> >
> > thanks,
> >
> > greg k-h
>
> Hi Greg,
>
> Current mobile targets are running on 5.10 and 5.15 only till now. No
> target on 6.1 hasn't come up completely yet. So not sure if this issue is
> there on 6.1.
>
> I can try putting 6.1 on a minimal busybox ramdisk image on the mobile
> target and see if the issue comes up but seeing that the issue is random and
> seen only after long duration, I might take some time to get back with the
> results.
>
> In the meantime, I would be happy to try out any ideas coming up from
> community in the meantime on current 5.15 build.
We can't do much about older kernels, as you know, sorry. If you can
reproduce the issue on a modern kernel (i.e. 6.1), then we can look into
it. If you can't, then 'git bisect' is your friend :)
good luck!
greg k-h
prev parent reply other threads:[~2022-12-23 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 13:56 SMMU Fault after setting RUN_STOP during gadget_pullup Krishna Kurapati PSSNV
2022-12-23 14:26 ` Greg KH
2022-12-23 15:04 ` Krishna Kurapati PSSNV
2022-12-23 15:12 ` Greg KH [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=Y6XFbc4aSOh7KnsO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_kriskura@quicinc.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 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.