From: Malte Starostik <malte@starostik.de>
To: bagasdotme@gmail.com
Cc: basavaraj.natikar@amd.com, linux-input@vger.kernel.org,
linux@hexchain.org, regressions@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: amd_sfh driver causes kernel oops during boot
Date: Mon, 05 Jun 2023 13:24:25 +0200 [thread overview]
Message-ID: <3250319.ancTxkQ2z5@zen> (raw)
In-Reply-To: <ZG3ipauL9FTnQJiC@debian.me>
Hello,
chiming in here as I'm experiencing what looks like the exact same issue, also
on a Lenovo Z13 notebook, also on Arch:
Oops during startup in task udev-worker followed by udev-worker blocking all
attempts to suspend or cleanly shutdown/reboot the machine - in fact I first
noticed because the machine surprised with repeatedly running out of battery
after it had supposedly been in standby but couldn't. Only then I noticed the
error on boot.
bisect result:
904e28c6de083fa4834cdbd0026470ddc30676fc is the first bad commit
commit 904e28c6de083fa4834cdbd0026470ddc30676fc
Merge: a738688177dc 2f7f4efb9411
Author: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Date: Wed Feb 22 10:44:31 2023 +0100
Merge branch 'for-6.3/hid-bpf' into for-linus
Initial support of HID-BPF (Benjamin Tissoires)
The history is a little long for this series, as it was intended to be
sent for v6.2. However some last minute issues forced us to postpone it
to v6.3.
Conflicts:
* drivers/hid/i2c-hid/Kconfig:
commit bf7660dab30d ("HID: stop drivers from selecting CONFIG_HID")
conflicts with commit 2afac81dd165 ("HID: fix I2C_HID not selected
when I2C_HID_OF_ELAN is")
the resolution is simple enough: just drop the "default" and "select"
lines as the new commit from Arnd is doing
BR Malte
> On Wed, May 24, 2023 at 02:10:31PM +0800, Haochen Tong wrote:
> > > What last kernel version before this regression occurs? Do you mean
> > > v6.2?
> > >
> >
> > I was using 6.2.12 (Arch Linux distro kernel) before seeing this
regression.
>
> Can you perform bisection to find the culprit that introduces the
> regression? Since you're on Arch Linux, see its wiki article [1] for
> instructions.
>
> Thanks.
>
> [1]: https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
next prev parent reply other threads:[~2023-06-05 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 17:27 amd_sfh driver causes kernel oops during boot Haochen Tong
2023-05-24 3:58 ` Bagas Sanjaya
2023-05-24 6:10 ` Haochen Tong
2023-05-24 10:10 ` Bagas Sanjaya
2023-06-05 11:24 ` Malte Starostik [this message]
2023-06-06 2:36 ` Bagas Sanjaya
2023-06-06 6:56 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-06 8:08 ` Benjamin Tissoires
2023-06-06 15:25 ` Limonciello, Mario
2023-06-06 22:57 ` Malte Starostik
2023-06-20 13:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 18:50 ` Limonciello, Mario
2023-06-20 20:03 ` Limonciello, Mario
2023-06-21 23:41 ` Malte Starostik
2023-06-21 2:46 ` Haochen Tong
2023-07-10 12:16 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-06-06 9:53 ` Malte Starostik
2023-06-06 2:39 ` Bagas Sanjaya
2023-06-06 3:41 ` Haochen Tong
2023-05-24 10:08 ` Bagas Sanjaya
2023-07-07 9:37 ` Linux regression tracking #update (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=3250319.ancTxkQ2z5@zen \
--to=malte@starostik.de \
--cc=bagasdotme@gmail.com \
--cc=basavaraj.natikar@amd.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@hexchain.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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