From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Joshua Scott <Joshua.Scott@alliedtelesis.co.nz>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Subject: Re: Unhandled prefetch abort when probing USB flash drive
Date: Tue, 14 Dec 2021 11:20:54 +0000 [thread overview]
Message-ID: <Ybh+FhDYN1CSzXi+@shell.armlinux.org.uk> (raw)
In-Reply-To: <d23175b8312e4b4093943b38c2ed59d2@svr-chch-ex1.atlnz.lc>
On Tue, Dec 14, 2021 at 05:13:20AM +0000, Joshua Scott wrote:
> Hi,
>
> I have been running into a kernel panic when probing a USB flash drive, and was after some advice or suggestions on what might be going wrong.
>
> First up, the details of my setup:
> * Initially seen on Linux 5.7.19, but I've tested on a vanilla copy of Linux 5.15.0 without any extra modules, and the panic still occurs.
> * Flash drive (lsusb): Bus 001 Device 002: ID 1005:b113 Apacer Technology, Inc. Handy Steno 2.0/HT203
> * Our system is based on the Marvell 98DX323x SoC (Arm v7, based on the Armada 370/XP)
Does it work with any kernel? If it doesn't, then I would suspect a
hardware bug, power supply glitch, or a SDRAM timing issue.
Why? These seem somewhat random and spurious. In the example prefetch
abort, it's weird on two accounts:
1) "external abort on non-linefetch" means that we weren't accessing
cached memory, but the kernel is always in cached memory.
2) prefetch abort means the instruction stream failed to read from
this location, but we later see in the Code: line that we have been
able to read the instructions into the data cache.
If the system runs fine without the flash drive attached, I would
suggest it's a power issue. I would suggest trying with an externally
powered USB hub, so the hub sources the power for the flash drive and
see whether that makes a difference.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-12-14 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 5:13 Unhandled prefetch abort when probing USB flash drive Joshua Scott
2021-12-14 11:20 ` Russell King (Oracle) [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=Ybh+FhDYN1CSzXi+@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Joshua.Scott@alliedtelesis.co.nz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 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).