From: bluetail <a-development+asahi@posteo.de>
To: Marek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>, Bin Meng <bmeng.cn@gmail.com>,
Mark Kettenis <kettenis@openbsd.org>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de, Janne Grunau <j@jannau.net>
Subject: Re: u-boot crashes if mass-storage devices are connected via USB-C
Date: Wed, 01 Mar 2023 23:30:32 +0000 [thread overview]
Message-ID: <51317fdd620a146a7927cebf90f2e81c@posteo.net> (raw)
In-Reply-To: <79b7c4da-eae4-2e9c-585e-ae10f5bb0489@denx.de>
Sure. Please send some instructions my way on how to proceed. I know
there is a u-boot manual, but I don't wanna mess up my mac mini m1
system. So I'd stick with instructions on your end. Ideally, the action
is reversible. I always keep complete system backups, though. My current
version is asahi-v2022.10-1 as far as I can tell. I'm used to git, so
pulling and making would be the slightest issue.
All the best and thanks,
---
aka zDEFz
On 01.03.2023 23:51, Marek Vasut wrote:
> On 3/1/23 21:34, Simon Glass wrote:
>> +Marek Vasut +Bin Meng +Mark Kettenis +Tom Rini
>>
>> On Wed, 1 Mar 2023 at 08:12, bluetail <a-development+asahi@posteo.de>
>> wrote:
>>>
>>> Hello. user kettenis aka "Mark Kettenis" guided me write my bug
>>> report
>>> to this email. "bluetail: please report these usb bugs upstream;
>>> they're
>>> almost certainly not hardware-specific"
>>>
>>> But before, jannau aka Janne Grunau asked me to give the version
>>> output
>>> of `pacman -Qi uboot-asahi` to which I replied 2022.10.asahi1-1.
>>> Because I had the feeling that sometimes the reboot with a USB-C
>>> connected device succeeds, depending how many bays are populated. But
>>> I
>>> have no evidence for that.
>>> I did try other USB Type C Cables, but without success of fixing the
>>> underlying issue. The device works fine via USB Type A or C fine if
>>> plugged in AFTER u-boot.
>>> But, u-boot does not support USB Type A yet, which is why it wont
>>> break
>>> my boot sequence with USB Type A.
>>>
>>> Essentially, I connect a mass-storage device to the USB-C port of a
>>> Mac
>>> Mini 2020 (M1), and it leads to the issue in the attachment.
>>> I was able to reproduce it with Icy Box IB-3810 and ICY BOX IB-3805.
>>> Initially I thought this issue was only for some devices (also
>>> attached
>>> here) https://github.com/AsahiLinux/u-boot/issues/4 but it appears
>>> this
>>> might be a issue that is with many devices.
>>>
>>> If you need any more information, please feel free to ask. I am very
>>> eager to have this issue fixed because it seems to be a very broad
>>> issue
>>> with mass media storage in general.
>>> uname-r returns 6.1.0-asahi-2-2-edge-ARCH
> Would it be possible to check whether current u-boot/master works any
> better ?
next prev parent reply other threads:[~2023-03-02 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 13:38 u-boot crashes if mass-storage devices are connected via USB-C bluetail
2023-03-01 20:34 ` Simon Glass
2023-03-01 22:51 ` Marek Vasut
2023-03-01 23:30 ` bluetail [this message]
2023-03-02 9:14 ` Janne Grunau
2023-03-02 17:33 ` Marek Vasut
2023-03-02 18:51 ` Janne Grunau
2023-03-02 21:05 ` Marek Vasut
2023-03-02 23:47 ` Janne Grunau
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=51317fdd620a146a7927cebf90f2e81c@posteo.net \
--to=a-development+asahi@posteo.de \
--cc=bmeng.cn@gmail.com \
--cc=j@jannau.net \
--cc=kettenis@openbsd.org \
--cc=marex@denx.de \
--cc=sjg@chromium.org \
--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