Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: George Hilliard <thirtythreeforty@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"linux1394-devel@lists.sourceforge.net"
	<linux1394-devel@lists.sourceforge.net>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: 5.19.9 regression: DMAR error on i7-8650U
Date: Tue, 20 Sep 2022 16:16:33 +0800	[thread overview]
Message-ID: <b003e86c-1cec-e6b1-1717-7c63372040ac@linux.intel.com> (raw)
In-Reply-To: <CACmrr9joJi5v2DOu4AAX3tyWDxM5LV+bviRZHeesdp37b+8gRQ@mail.gmail.com>

On 2022/9/20 3:05, George Hilliard wrote:
> On Mon, Sep 19, 2022 at 9:43 AM Mika Westerberg
> <mika.westerberg@linux.intel.com>  wrote:
>> Hi Baolu,
>>
>> On Mon, Sep 19, 2022 at 11:09:02AM +0300, Mika Westerberg wrote:
>>> Here's bugzilla report that looks to have similar symptoms:
>>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216497
>> The reporters of the above bugzilla bisected this down to:
>>
>>    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.19.y&id=9516acba29e322202674d18f4dc383879f7813a5
> I can confirm that reverting 9516acba29e322202674d18f4dc383879f7813a5
> fixes the problem for me as well.

Thanks for doing this. I will post a patch to revert this commit.

Best regards,
baolu

  reply	other threads:[~2022-09-20  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  0:00 5.19.9 regression: DMAR error on i7-8650U George Hilliard
2022-09-19  0:53 ` Baolu Lu
2022-09-19  5:27   ` Mika Westerberg
2022-09-19  8:09     ` Mika Westerberg
2022-09-19 14:44       ` Mika Westerberg
2022-09-19 19:05         ` George Hilliard
2022-09-20  8:16           ` Baolu Lu [this message]
2022-09-19  8:31 ` 5.19.9 regression: DMAR error on i7-8650U #forregzbot Thorsten Leemhuis

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=b003e86c-1cec-e6b1-1717-7c63372040ac@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mika.westerberg@linux.intel.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=thirtythreeforty@gmail.com \
    --cc=will@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