From: "Jeremy Linton" <jeremy.linton@arm.com>
To: Rebecca Cran <rebecca@bsdio.com>, devel@edk2.groups.io, ardb@kernel.org
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Abdul Lateef Attar <AbdulLateef.Attar@amd.com>,
Abner Chang <abner.chang@amd.com>,
Chuong Tran <chuong@os.amperecomputing.com>,
Graeme Gregory <graeme@xora.org.uk>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Marcin Wojtas <marcin.s.wojtas@gmail.com>,
Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>,
Narinder Dhillon <ndhillon@marvell.com>,
Nhi Pham <nhi@os.amperecomputing.com>,
Paul Grimes <paul.grimes@amd.com>,
Rebecca Cran <rebecca@os.amperecomputing.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Thomas Abraham <thomas.abraham@arm.com>,
Wenyi Xie <xiewenyi2@huawei.com>,
Ling Jia <jialing@phytium.com.cn>,
Peng Xie <xiepeng@phytium.com.cn>,
Yiqi Shu <shuyiqi@phytium.com.cn>
Subject: Re: [edk2-devel] [PATCH edk2-platforms 0/2] Switch all platforms to [Peiless]Sec
Date: Thu, 1 Aug 2024 13:50:05 -0500 [thread overview]
Message-ID: <77fe8412-114c-4089-89ec-20e8507a626c@arm.com> (raw)
In-Reply-To: <74d6cf49-d046-49c6-8480-7809d632c04e@bsdio.com>
On 8/1/24 10:50, Rebecca Cran wrote:
> On 8/1/24 9:43 AM, Ard Biesheuvel wrote:
>
>> Haven't noticed this one myself. The only issue I hit once in a while
>> (but only with DEBUG builds as far as I am aware) is an ASSERT() on
>> some XhciDxe control register read (or perhaps a timeout?)
>
> This might be the XHCI bug where there's missing error handling around a
> controller reset failure. I have a patch to send to fix it.
>
>
I would second the please send the patch request. I've got a USB raid
enclosure I carried a patch for a few years similar to the one in this
discussion: https://edk2.groups.io/g/devel/message/58193
Plugging a jmicron based yottamaster JBOD into an edk2/xhci setup is
still a 100% guaranteed crash, and with the recent rework in
UsbIoPortReset()/etc now fails like:
https://paste.centos.org/view/fbff41dc
UsbIoPortReset: Failed to set configuration - Out of Resources
Synchronous Exception at 0x0000000036A5635C
PC 0x000036A5635C (0x000036A55000+0x0000135C) [ 0] UsbBusDxe.dll
PC 0x000036A576D0 (0x000036A55000+0x000026D0) [ 0] UsbBusDxe.dll
PC 0x000036A44E00 (0x000036A42000+0x00002E00) [ 1] UsbMassStorageDxe.dll
PC 0x000036A45888 (0x000036A42000+0x00003888) [ 1] UsbMassStorageDxe.dll
PC 0x000036A46D74 (0x000036A42000+0x00004D74) [ 1] UsbMassStorageDxe.dll
PC 0x000036A46F00 (0x000036A42000+0x00004F00) [ 1] UsbMassStorageDxe.dll
PC 0x000036CC0EBC (0x000036CBD000+0x00003EBC) [ 2] DiskIoDxe.dll
PC 0x000036CB82CC (0x000036CB3000+0x000052CC) [ 3] PartitionDxe.dll
PC 0x000036CB590C (0x000036CB3000+0x0000290C) [ 3] PartitionDxe.dll
PC 0x000039F37FAC (0x000039F33000+0x00004FAC) [ 4] DxeCore.dll
PC 0x000039F38250 (0x000039F33000+0x00005250) [ 4] DxeCore.dll
PC 0x000036A5A748 (0x000036A55000+0x00005748) [ 5] UsbBusDxe.dll
PC 0x000036A5B1D0 (0x000036A55000+0x000061D0) [ 5] UsbBusDxe.dll
PC 0x000036A5CBA4 (0x000036A55000+0x00007BA4) [ 5] UsbBusDxe.dll
PC 0x000036A5CDF0 (0x000036A55000+0x00007DF0) [ 5] UsbBusDxe.dll
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120193): https://edk2.groups.io/g/devel/message/120193
Mute This Topic: https://groups.io/mt/107649429/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-08-01 18:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 16:33 [edk2-devel] [PATCH edk2-platforms 0/2] Switch all platforms to [Peiless]Sec Ard Biesheuvel
2024-07-31 16:33 ` [edk2-devel] [PATCH edk2-platforms 1/2] Platform AARCH64: Move PrePeiCore users to Sec.inf Ard Biesheuvel
2024-08-01 15:25 ` Nhi Pham via groups.io
2024-08-05 19:14 ` Marcin Juszkiewicz
2024-08-06 14:08 ` Leif Lindholm
2024-07-31 16:33 ` [edk2-devel] [PATCH edk2-platforms 2/2] Platform AARCH64: Move PrePi users to PeilessSec.inf Ard Biesheuvel
2024-08-01 9:21 ` [edk2-devel] [PATCH edk2-platforms 0/2] Switch all platforms to [Peiless]Sec Sami Mujawar
2024-08-01 13:49 ` Jeremy Linton
2024-08-01 14:11 ` Ard Biesheuvel
2024-08-01 14:44 ` Ard Biesheuvel
2024-08-01 15:19 ` Jeremy Linton
2024-08-01 15:43 ` Ard Biesheuvel
2024-08-01 15:50 ` Rebecca Cran
2024-08-01 15:54 ` Ard Biesheuvel
2024-08-01 18:50 ` Jeremy Linton [this message]
2024-08-02 11:44 ` Rebecca Cran
2024-08-05 16:17 ` Jeremy Linton
2024-08-06 14:10 ` Leif Lindholm
2024-08-27 16:37 ` Ard Biesheuvel via groups.io
2024-08-28 3:54 ` Jeremy Linton
2024-08-28 7:54 ` Ard Biesheuvel via groups.io
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-list 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=77fe8412-114c-4089-89ec-20e8507a626c@arm.com \
--to=devel@edk2.groups.io \
/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