From: Malte Starostik <malte@starostik.de>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
basavaraj.natikar@amd.com, linux-input@vger.kernel.org,
linux@hexchain.org, stable@vger.kernel.org
Subject: Re: amd_sfh driver causes kernel oops during boot
Date: Thu, 22 Jun 2023 01:41:41 +0200 [thread overview]
Message-ID: <2426092.W91McpcXCD@zen> (raw)
In-Reply-To: <602504a5-334d-92e8-2fd3-f7e8662b714e@amd.com>
Am Dienstag, 20. Juni 2023, 22:03:00 CEST schrieb Limonciello, Mario:
> On 6/20/2023 1:50 PM, Limonciello, Mario wrote:
> > Anyways; I just double checked the Z13 I have on my hand. I don't
> > have the PCI device for SFH (1022:164a) present on the system.
> >
> > Can you please double check you are on the latest BIOS?
> >
> > I'm on the latest release from LVFS, 0.1.57 according to fwupdmgr.
I was on 0.1.27 while running the tests.
At least when I saw the errors first, there was no update offered. Haven't re-
checked until now.
> Hopefully the newer BIOS fixes it for you, but if it doesn't I did come
> up with another patch I've sent out that I guess could be another
> solution.
After updating to 0.1.57, it looks like I cannot reproduce the error anymore
either.
> https://lore.kernel.org/linux-input/20230620200117.22261-1-mario.limonciello
> @amd.com/T/#u
I tested your patch before performing the firmware update. Still got the Oops
just like before.
BR Malte
next prev parent reply other threads:[~2023-06-21 23:41 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 [this message]
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=2426092.W91McpcXCD@zen \
--to=malte@starostik.de \
--cc=bagasdotme@gmail.com \
--cc=basavaraj.natikar@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@hexchain.org \
--cc=mario.limonciello@amd.com \
--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).