From: Marek Vasut <marex@denx.de>
To: Zixun LI <admin@hifiphile.com>, Lukasz Majewski <lukma@denx.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: usb:composite: data abort on second ums launch
Date: Mon, 24 Mar 2025 15:03:44 +0100 [thread overview]
Message-ID: <72987a42-4e5b-4b53-a5de-2c654e129c43@denx.de> (raw)
In-Reply-To: <CA+GyqebHib_N7szGKkR0Ejac1rmoDQp+0a8t7ROng=PE3g9pGA@mail.gmail.com>
On 3/24/25 11:42 AM, Zixun LI wrote:
> Hi,
>
> I encountered a data abort on the 2nd "ums 0 mmc 0" command on
> u-boot-at91 2024.07 with sam9x60-curiosity board.
>
> U-Boot> ums 0 mmc 0
> UMS: LUN 0, dev mmc 0, hwpart 0, sector 0x0, count 0x1d29000
> CTRL+C - Operation aborted
> U-Boot> ums 0 mmc 0
> UMS: LUN 0, dev mmc 0, hwpart 0, sector 0x0, count 0x1d29000
> data abort
> pc : [<27f93428>] lr : [<27ef7e80>]
> reloc pc : [<23f16428>] lr : [<23e7ae80>]
> sp : 27ef4cf0 ip : a5200000 fp : 23f6915c
> r10: deadbeef r9 : 27ef7e80 r8 : 27f7d2a0
> r7 : a5200000 r6 : 00000000 r5 : 00000000 r4 : 27f01668
> r3 : 00000000 r2 : 00000000 r1 : 27fe1d88 r0 : 27f01668
> Flags: nzCV IRQs off FIQs off Mode SVC_32 (T)
> Code: 45ac d017 68c5 4667 (60fd) 60af
>
> From backtrace the abort happened in fREe_impl(), with some debugging
> I've localized the abort in fact happened in fsg buffer allocation in
> fsg_common_init() [1]
>
> It looks like the buffer is not freed on driver unregister since
> fsg_common_release() is only called if fsg_common_init() met an error.
Can you reproduce this on u-boot/master too ?
next prev parent reply other threads:[~2025-03-24 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 10:42 usb:composite: data abort on second ums launch Zixun LI
2025-03-24 14:03 ` Marek Vasut [this message]
2025-03-24 15:18 ` Zixun LI
2025-03-24 17:21 ` Mattijs Korpershoek
2025-03-24 17:33 ` Zixun LI
2025-03-24 17:40 ` Mattijs Korpershoek
2025-03-27 13:46 ` Mattijs Korpershoek
2025-03-28 8:20 ` Mattijs Korpershoek
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=72987a42-4e5b-4b53-a5de-2c654e129c43@denx.de \
--to=marex@denx.de \
--cc=admin@hifiphile.com \
--cc=lukma@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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