mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: Guenter Roeck <linux@roeck-us.net>,
	Matthew Bettencourt <matthew.bettencourt@gmail.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [BUG] SPD5118 Intermittent MR11 Corruption During Suspend/Resume
Date: Fri, 4 Sep 2026 00:47:01 +0200	[thread overview]
Message-ID: <02dc7eb6-6d0d-4c0c-af10-b831d3f8ba06@gmx.de> (raw)
In-Reply-To: <5480c69c-8e98-443e-96d7-30e64e886373@roeck-us.net>

Am 03.09.26 um 23:05 schrieb Guenter Roeck:

> Hi Matthew,
>
> On 9/3/26 11:25, Matthew Bettencourt wrote:
>> Hello Guenter,
>>
>>  > This system [MSI PRO B850M-A WIF/7600x3d] does _not_ have a 
>> problem, or did I misunderstand the above ?
>>
>> That is correct. I was unable to replicate the issue with the MSI PRO 
>> B850M-A WIF and 7600x3d. The MR11 registered never got corrupted 
>> during sleep/resume and I never saw any piix4 errors logged when 
>> using my piix4 driver with the additional logging enabled.
>>
>> I never swapped the CPUs as that was more hassle than I was willing 
>> to do right now, but if it something that might be useful I can 
>> probably try that at some point.
>>
> I don't think that would help. From all the reports I browsed through
> so far, the common denominator seems to be that the affected systems use
> a X870 or X870E chipset.
>
> Anyway, couple of ideas:
>
> - Do you have the latest BIOS installed on your system ?
>   Some statements online seem to suggest that the problem
>   _may_ be fixed with the latest BIOS on at least some
>   of the affected systems.
>
> - Please boot the affected system with "usbcore.autosuspend=-1"
>   kernel command line parameter.
>   There are some claims online that this might resolve the problem.
>   I have no idea why that would be the case, but I guess it does
>   not hurt trying. Of course, if that _does_ work, we have yet another
>   mystery to solve.
>
> - Do you have memory with RGB-anything in the affected system ? If so,
>   is it controlled by the BIOS ? If yes, please disable the functionality
>   if that is possible.
>
> Thanks,
> Guenter 

According to the output of /proc/ioports, the root issue seems to be that the ACPI firmware
drives the SMBus controller and marks the affected IO ports as reserved, but acpi_check_region()
still tells the driver that the IO ports are available.

I already CCed the ACPI people to take a look at this.

Thanks,
Armin Wolf


  reply	other threads:[~2026-09-03 22:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 23:21 Matthew Bettencourt
2026-08-31 15:12 ` Guenter Roeck
2026-08-31 17:28   ` Guenter Roeck
2026-08-31 23:36     ` Matthew Bettencourt
     [not found]     ` <37132c40-aa82-4df1-b5ce-337601f3c085@gmail.com>
     [not found]       ` <3c4e9f59-5272-48cf-a4a0-eeefcba955a9@roeck-us.net>
2026-09-01  0:16         ` Matthew Bettencourt
2026-09-01  3:10           ` Guenter Roeck
2026-09-01 16:31             ` Matthew Bettencourt
2026-09-01 17:04               ` Guenter Roeck
2026-09-01 20:53                 ` Matthew Bettencourt
2026-09-01 22:36                   ` Guenter Roeck
2026-09-02  0:57                     ` Matthew Bettencourt
2026-09-02  1:32                       ` Guenter Roeck
2026-09-02  2:14                         ` Matthew Bettencourt
2026-09-02  3:19                           ` Guenter Roeck
2026-09-02 14:00                             ` Matthew Bettencourt
2026-09-02 14:52                               ` Guenter Roeck
2026-09-02 15:26                                 ` Matthew Bettencourt
2026-09-02 17:21                                   ` Guenter Roeck
2026-09-02 17:37                                     ` Matthew Bettencourt
2026-09-02 16:57                               ` Armin Wolf
2026-09-02 17:08                                 ` Matthew Bettencourt
2026-09-02 17:22                                   ` Armin Wolf
2026-09-02 17:28                                     ` Matthew Bettencourt
2026-09-02 19:19                                       ` Armin Wolf
2026-09-02 19:25                                         ` Matthew Bettencourt
2026-09-02 19:31                                           ` Armin Wolf
2026-09-02 19:40                                             ` Matthew Bettencourt
2026-09-02 19:51                                               ` Armin Wolf
2026-09-03 18:01                                                 ` Matthew Bettencourt
2026-09-03 18:16                                                   ` Guenter Roeck
2026-09-03 18:25                                                     ` Matthew Bettencourt
2026-09-03 21:05                                                       ` Guenter Roeck
2026-09-03 22:47                                                         ` Armin Wolf [this message]
2026-09-04  0:24                                                           ` Matthew Bettencourt
2026-09-04 17:58                                                             ` 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=02dc7eb6-6d0d-4c0c-af10-b831d3f8ba06@gmx.de \
    --to=w_armin@gmx.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthew.bettencourt@gmail.com \
    --cc=rafael@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

all inboxes | Powered by JetHome®