From: Zi Yan <ziy@nvidia.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Wei Liu <wei.liu@kernel.org>, Joerg Roedel <jroedel@suse.de>,
<x86@kernel.org>, <iommu@lists.linux-foundation.org>,
<linux-hyperv@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<xen-devel@lists.xenproject.org>
Subject: Re: Boot crash due to "x86/msi: Consolidate MSI allocation"
Date: Thu, 1 Oct 2020 09:39:42 -0400 [thread overview]
Message-ID: <2F4EC354-C0BB-44BD-86A5-07F321590C31@nvidia.com> (raw)
In-Reply-To: <874knegxtg.fsf@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On 1 Oct 2020, at 4:22, Thomas Gleixner wrote:
> Yan,
>
> On Wed, Sep 30 2020 at 21:29, Zi Yan wrote:
>> I am running linux-next on my Dell R630 and the system crashed at boot
>> time. I bisected linux-next and got to your commit:
>>
>> x86/msi: Consolidate MSI allocation
>>
>> The crash log is below and my .config is attached.
>>
>> [ 11.840905] intel_get_irq_domain+0x24/0xb0
>> [ 11.840905] native_setup_msi_irqs+0x3b/0x90
>
> This is not really helpful because that's in the middle of the queue and
> that code is gone at the very end. Yes, it's unfortunate that this
> breaks bisection.
>
> Can you please test:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/irq
>
> which contains fixes and if it still crashes provide the dmesg of it.
>
My system boots without any problem using this tree. Thanks.
—
Best Regards,
Yan Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2020-10-01 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A838FF2B-11FC-42B9-87D7-A76CF46E0575@nvidia.com>
2020-10-01 8:22 ` Boot crash due to "x86/msi: Consolidate MSI allocation" Thomas Gleixner
2020-10-01 13:39 ` Zi Yan [this message]
2020-10-01 13:53 ` Thomas Gleixner
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=2F4EC354-C0BB-44BD-86A5-07F321590C31@nvidia.com \
--to=ziy@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).