From: "Artem S. Tashkinov" <aros@gmx.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
iommu <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 17:21:18 +0000 [thread overview]
Message-ID: <e97de44a-39b0-c4fa-488c-d9fa76eb1eae@gmx.com> (raw)
In-Reply-To: <CAHk-=wj0E9vCO_VTiK6xuXAW13ZeeLsW=G3v+yNsCaUm1+H61A@mail.gmail.com>
On 3/11/20 4:21 PM, Linus Torvalds wrote:
> On Wed, Mar 11, 2020 at 9:02 AM Artem S. Tashkinov <aros@gmx.com> wrote:
>>
>> With this patch the system works (I haven't created an initrd, so it
>> doesn't completely boot and panics on not being able to mount root fs
>> but that's expected).
>
> Perfect.
>
> I ended up applying my earlier cleanup patch with just the added
> removal of the kfree(), which was the actual trigger of the bug.
>
> It's commit e423fb6929d4 ("driver code: clarify and fix platform
> device DMA mask allocation") in my tree. I've not pushed it out yet (I
> have a few pending pull requests), but it should be out shortly.
I've been able to compile and run
e3a36eb6dfaeea8175c05d5915dcf0b939be6dab successfully. I won't claim
this patch doesn't break something for other people :-)
Best regards,
Artem
WARNING: multiple messages have this Message-ID (diff)
From: "Artem S. Tashkinov" <aros@gmx.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
iommu <iommu@lists.linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 206175] Fedora >= 5.4 kernels instantly freeze on boot without producing any display output
Date: Wed, 11 Mar 2020 17:21:18 +0000 [thread overview]
Message-ID: <e97de44a-39b0-c4fa-488c-d9fa76eb1eae@gmx.com> (raw)
In-Reply-To: <CAHk-=wj0E9vCO_VTiK6xuXAW13ZeeLsW=G3v+yNsCaUm1+H61A@mail.gmail.com>
On 3/11/20 4:21 PM, Linus Torvalds wrote:
> On Wed, Mar 11, 2020 at 9:02 AM Artem S. Tashkinov <aros@gmx.com> wrote:
>>
>> With this patch the system works (I haven't created an initrd, so it
>> doesn't completely boot and panics on not being able to mount root fs
>> but that's expected).
>
> Perfect.
>
> I ended up applying my earlier cleanup patch with just the added
> removal of the kfree(), which was the actual trigger of the bug.
>
> It's commit e423fb6929d4 ("driver code: clarify and fix platform
> device DMA mask allocation") in my tree. I've not pushed it out yet (I
> have a few pending pull requests), but it should be out shortly.
I've been able to compile and run
e3a36eb6dfaeea8175c05d5915dcf0b939be6dab successfully. I won't claim
this patch doesn't break something for other people :-)
Best regards,
Artem
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-03-11 17:21 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
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 [this message]
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=e97de44a-39b0-c4fa-488c-d9fa76eb1eae@gmx.com \
--to=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--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.