From: Changhui Zhong <czhong@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [bug report] WARNING: CPU: 0 PID: 226 at drivers/pci/pci.c:2236 pci_disable_device+0xf4/0x100
Date: Thu, 21 Mar 2024 18:11:46 +0800 [thread overview]
Message-ID: <CAGVVp+WPJZO50=-egr+67x9uePf3y4LS-85iCT_aEtSf=LASZw@mail.gmail.com> (raw)
In-Reply-To: <20240320024647.GA1254126@bhelgaas>
On Wed, Mar 20, 2024 at 10:46 AM Bjorn Helgaas <helgaas@kernel.org> 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@kernel.org> 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
next prev parent reply other threads:[~2024-03-21 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 7:34 [bug report] WARNING: CPU: 0 PID: 226 at drivers/pci/pci.c:2236 pci_disable_device+0xf4/0x100 Changhui Zhong
2024-03-19 16:23 ` Bjorn Helgaas
2024-03-20 2:16 ` Changhui Zhong
2024-03-20 2:46 ` Bjorn Helgaas
2024-03-20 3:13 ` Changhui Zhong
2024-03-21 10:11 ` Changhui Zhong [this message]
2024-03-21 12:44 ` Bjorn Helgaas
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='CAGVVp+WPJZO50=-egr+67x9uePf3y4LS-85iCT_aEtSf=LASZw@mail.gmail.com' \
--to=czhong@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.