On Thu, Mar 21, 2024 at 06:11:46PM +0800, Changhui Zhong wrote: > On Wed, Mar 20, 2024 at 10:46 AM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > On Wed, Mar 20, 2024 at 10:16:06AM +0800, Changhui Zhong wrote: > > > On Wed, Mar 20, 2024 at 12:30 AM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > > > On Tue, Mar 19, 2024 at 03:34:56PM +0800, Changhui Zhong wrote: > > > > > repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > > > > branch: master > > > > > commit HEAD:b3603fcb79b1036acae10602bffc4855a4b9af80 > > > > > > > > Where's the rest of this? I don't see "WARNING: CPU: 0 PID: 226 at > > > > drivers/pci/pci.c:2236" in the snippet below. Please include or post > > > > the complete dmesg log. > > > > > > > > Is this reproducible? If so, how? And is it a regression? > > > > > > it reproduceible，I can trigger it every time on my server，but I'm not > > > sure if it is a regression， > > > > Great, it's always easier if it's easily reproducible. Can you please > > try an older kernel, e.g., v6.8? > > I tested v6.8 and v6.7 both triggered this issue, > and not trigger this issue on v6.6 Bisecting between v6.6 and v6.7 might be the quickest way to find it, but it's a fair bit of work on your end. How do you trigger the problem? It looks like you're capturing console output, and most of the kernel messages don't appear on the console. The kernel messages (dmesg) I'm interested in should be captured somewhere like /var/log/dmesg or similar (I don't know the exact filename for Red Hat). Bjorn
