public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Coiby Xu <coxu@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	kexec@lists.infradead.org, Marc Zyngier <maz@kernel.org>
Subject: Re: [Regression] kdump fails to get DHCP address unless booting with pci=nomsi or without nr_cpus=1
Date: Mon, 11 Aug 2025 15:03:21 +0200	[thread overview]
Message-ID: <878qjq80yu.ffs@tglx> (raw)
In-Reply-To: <87bjom8106.ffs@tglx>

On Mon, Aug 11 2025 at 15:02, Thomas Gleixner wrote:

CC+ Marc

> On Mon, Aug 11 2025 at 11:23, Coiby Xu wrote:
>> Recently I met an issue that on certain virtual machines, the kdump
>> kernel fails to get DHCP IP address most of times starting from
>> 6.11-rc2. git bisection shows commit b5712bf89b4b ("irqchip/gic-v3-its:
>> Provide MSI parent for PCI/MSI[-X]") is the 1st bad commit,
>>
>>      # good: [7d189c77106ed6df09829f7a419e35ada67b2bd0] PCI/MSI: Provide
>>      # MSI_FLAG_PCI_MSI_MASK_PARENT
>>      git bisect good 7d189c77106ed6df09829f7a419e35ada67b2bd0
>>      # good: [48f71d56e2b87839052d2a2ec32fc97a79c3e264] irqchip/gic-v3-its:
>>      # Provide MSI parent infrastructure
>>      git bisect good 48f71d56e2b87839052d2a2ec32fc97a79c3e264
>>      # good: [8c41ccec839c622b2d1be769a95405e4e9a4cb20] irqchip/irq-msi-lib:
>>      # Prepare for PCI MSI/MSIX
>>      git bisect good 8c41ccec839c622b2d1be769a95405e4e9a4cb20
>>      # first bad commit: [b5712bf89b4bbc5bcc9ebde8753ad222f1f68296]
>>      # irqchip/gic-v3-its: Provide MSI parent for PCI/MSI[-X]
>
> There were follow up fixes on this, so isolating this one is not really
> conclusive.
>
> Is the problem still there on v6.16 and v6.17-rc1?
>
> Thanks,
>
>         tglx


  reply	other threads:[~2025-08-11 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11  3:23 [Regression] kdump fails to get DHCP address unless booting with pci=nomsi or without nr_cpus=1 Coiby Xu
2025-08-11 13:02 ` Thomas Gleixner
2025-08-11 13:03   ` Thomas Gleixner [this message]
2025-08-11 14:52     ` Marc Zyngier
2025-08-12 10:09       ` Coiby Xu
2025-08-12 10:17         ` Marc Zyngier
2025-08-12 11:07           ` Coiby Xu
2025-08-12 13:14             ` Marc Zyngier
     [not found]               ` <yweverlt7onyse3rbm7phxzwrwfk4pq2dipzdjenrx4onrak6r@dsm4ra3x3gv6>
2025-08-19 23:30                 ` Coiby Xu
2025-08-20  8:56                   ` Marc Zyngier
     [not found]                     ` <p7aa2fcm3g32ydulq3nqrvsg57tyvt5ro5cs3oqrdahxesoroj@tqpulky4drlo>
2025-08-27  8:17                       ` Coiby Xu
2025-08-12  3:29   ` Coiby Xu

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=878qjq80yu.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=coxu@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox