From: Christoph Hellwig <hch@lst.de>
To: "Artem S. Tashkinov" <aros@gmx.com>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
iommu@lists.linux-foundation.org
Subject: Re: [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output
Date: Wed, 11 Mar 2020 16:43:28 +0100 [thread overview]
Message-ID: <20200311154328.GA24044@lst.de> (raw)
In-Reply-To: <e70dd793-e8b8-ab0c-6027-6c22b5a99bfc@gmx.com>
On Wed, Mar 11, 2020 at 03:34:38PM +0000, Artem S. Tashkinov wrote:
> On 3/11/20 3:24 PM, Christoph Hellwig wrote:
>> pdev->dma_mask = parent->dma_mask ? *parent->dma_mask : 0;
>
> This patch makes no difference.
>
> The kernel panics with the same call trace which starts with:
This looks really strange and not dma mask related, but there must be
some odd interactions somewhere.
Can you call gdb on the vmlinux file for the 5.5.8-200.fc31 kernel
in the jpg and then do
l *(kmem_cache_alloc_trace+0x7e)
l *(acpi_processor_add+0x3a)
and send the output?
next prev parent reply other threads:[~2020-03-11 15:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-206175-5873@https.bugzilla.kernel.org/>
[not found] ` <bug-206175-5873-dSmrOaqbiZ@https.bugzilla.kernel.org/>
2020-01-14 21:40 ` [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output Linus Torvalds
2020-01-14 22:22 ` Alex Deucher
[not found] ` <bug-206175-5873-S6PaNNClEr@https.bugzilla.kernel.org/>
[not found] ` <CAHk-=wi4GS05j67V0D_cRXRQ=_Jh-NT0OuNpF-JFsDFj7jZK9A@mail.gmail.com>
[not found] ` <20200310162342.GA4483@lst.de>
[not found] ` <CAHk-=wgB2YMM6kw8W0wq=7efxsRERL14OHMOLU=Nd1OaR+sXvw@mail.gmail.com>
2020-03-10 18:25 ` Christoph Hellwig
2020-03-10 18:25 ` Christoph Hellwig
2020-03-11 15:24 ` Christoph Hellwig
2020-03-11 15:34 ` Artem S. Tashkinov
2020-03-11 15:43 ` Christoph Hellwig [this message]
2020-03-11 15:47 ` Christoph Hellwig
2020-03-11 16:02 ` Artem S. Tashkinov
2020-03-11 16:15 ` Robin Murphy
2020-03-11 16:21 ` Linus Torvalds
2020-03-11 16:24 ` Linus Torvalds
2020-03-11 16:48 ` Linus Torvalds
2020-03-11 16:48 ` Linus Torvalds
2020-03-11 17:05 ` Artem S. Tashkinov
2020-03-11 17:05 ` Artem S. Tashkinov
2020-03-11 17:21 ` Artem S. Tashkinov
2020-03-11 17:21 ` Artem S. Tashkinov
2020-03-11 17:27 ` Linus Torvalds
2020-03-11 17:27 ` Linus Torvalds
2020-03-11 15:48 ` Artem S. Tashkinov
2020-03-11 15:57 ` Linus Torvalds
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=20200311154328.GA24044@lst.de \
--to=hch@lst.de \
--cc=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.