linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Hans de Goede <hdegoede@redhat.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
Date: Sat, 21 May 2022 13:30:51 +0200	[thread overview]
Message-ID: <6b12a0b4-2f6d-1c35-f2e2-a28022583c47@leemhuis.info> (raw)
In-Reply-To: <CAHk-=wjKtV3mT3S=vxgqe__MUzxRrZ7=fopKQtTKOeQJAVyoUQ@mail.gmail.com>

On 21.05.22 07:01, Linus Torvalds wrote:
> On Thu, May 19, 2022 at 6:10 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Note this is not part of any pending drm-fixes* pull-reqs yet though.
> 
> It has now hit my tree as part of Dave's drm pull today.

Great, just like Hans I have been watching the progress of that patch
closely. A fix for a regression on the Raspi CM4 also landed in the past
24 hours.

I assume you'll also get the patch "objtool: Fix objtool regression on
x32 systems"
(https://lore.kernel.org/all/165304401319.4207.18392602354110557584.tip-bot2@tip-bot2/

) today or tomorrow.

That leaves the following post-5.17 regressions on my list where no fix
is in sight yet:

* Laptop with Ryzen 4600H fails to resume video
https://lore.kernel.org/stable/2584945.lGaqSPkdTl@geek500.localdomain/
(doesn't look like it first, but this apparently is a post-5.17
regression, as the commit causing it was backported; note, the Laptop
has some other problems with suspend that make the first suspend fail;
Mario is working hard with the reporter to find a fix)

* dpaa2: TSO offload on lx2160a causes fatal exception in interrupt
https://bugzilla.kernel.org/show_bug.cgi?id=215886
Debugging is ongoing, there is a patch now, but it's not clear yet if it
helps.

* the netperf.Throughput_Mbps -18.0% regression that made it into mainline:
https://lore.kernel.org/lkml/20220420013526.GB14333@xsang-OptiPlex-9020/
Didn't follow that one closely, as you were active in the discussion
yourself.

HTH, Ciao, Thorsten

  reply	other threads:[~2022-05-21 11:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09  8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09  9:13   ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20   ` Linus Torvalds
2022-05-09 19:04     ` Hans de Goede
2022-05-10 14:41       ` Maarten Lankhorst
2022-05-17 15:50       ` Hans de Goede
2022-05-19 16:09         ` Hans de Goede
2022-05-21  5:01           ` Linus Torvalds
2022-05-21 11:30             ` Thorsten Leemhuis [this message]
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck

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=6b12a0b4-2f6d-1c35-f2e2-a28022583c47@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=hdegoede@redhat.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=regressions@lists.linux.dev \
    --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 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).