From: Haochen Tong <linux@hexchain.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
stable@vger.kernel.org,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: regressions@lists.linux.dev, linux-input@vger.kernel.org,
Basavaraj Natikar <basavaraj.natikar@amd.com>
Subject: Re: amd_sfh driver causes kernel oops during boot
Date: Tue, 6 Jun 2023 11:41:39 +0800 [thread overview]
Message-ID: <d354c90c-03cb-1919-e587-a2cfd0511add@hexchain.org> (raw)
In-Reply-To: <ZH6cd6_8EUrRY0W0@debian.me>
On 6/6/23 10:39, Bagas Sanjaya wrote:
> On Wed, May 24, 2023 at 05:10:45PM +0700, Bagas Sanjaya wrote:
>> 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.
>>
>
> Haochen, any news on this? Has the bisection been done and any result?
> Another reporter had concluded possibly bad bisect [1].
>
> Thanks.
>
> [1]: https://lore.kernel.org/regressions/3250319.ancTxkQ2z5@zen/
>
Hi,
Sorry for the late reply. I haven't gotten enough time for it yet.
I took a look at the git logs, and it doesn't look like the modules
involved in the original stack trace (amd_sfh, hid_sensor_hub,
hid_sensor_iio_common, hid_sensor_gyro_3d) has received any significant
changes between v6.2 and v6.3. IMHO, the bisect done by Malte might
indicate that the issue could be a problem outside of these modules.
Also, I've upgrade from 6.3.3 to 6.3.5 a week ago and this issue hasn't
happened so far in 4 reboots. However, there still doesn't seem to be
any changes regarding these modules, so I'm not sure if it's fixed
elsewhere or I'm just being lucky. It would be nice if someone can
confirm or disprove this.
Thanks,
next prev parent reply other threads:[~2023-06-06 3:46 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
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 [this message]
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=d354c90c-03cb-1919-e587-a2cfd0511add@hexchain.org \
--to=linux@hexchain.org \
--cc=bagasdotme@gmail.com \
--cc=basavaraj.natikar@amd.com \
--cc=linux-input@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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;
as well as URLs for NNTP newsgroup(s).