[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4eefdae3-125e-4c80-9968-8d20648f33bd@zohomail.com>
Date: Tue, 10 Feb 2026 19:56:20 +0800
From: Li Ming <ming.li@...omail.com>
To: Alison Schofield <alison.schofield@...el.com>
Cc: dave@...olabs.net, jonathan.cameron@...wei.com, dave.jiang@...el.com,
vishal.l.verma@...el.com, ira.weiny@...el.com, dan.j.williams@...el.com,
linux-cxl@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Fix port enumeration failure
在 2026/2/10 11:04, Alison Schofield 写道:
> On Sat, Feb 07, 2026 at 09:35:10PM +0800, Li Ming wrote:
>> I ran CXL mock testing with next branch, I usually hit the following
>> call trace.
> Hi Ming,
> I started hitting this after you first posted, however it takes me a
> long time to hit it. Do you have a method to reproduce that is better
> than running on repeat as I do? Thanks!
> -- Alison
>
> snip
Hi Alison,
My environment is a VM with 2 CPUs, maybe you can try it.
I use a script to run "meson test --suite=cxl" again and again in the VM.
I can typically reproduce it within 30 minutes, I have also encountered
cases where it fails to reproduce even after one or two hours.
Ming
Powered by blists - more mailing lists