lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 6 May 2022 11:44:43 +0300
From:   Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Samuel Clark <slc2015@...il.com>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: regression: Null pointer exception on resume from S3 with i2c
 DesignWare driver

Hi

On 5/5/22 12:52, Thorsten Leemhuis wrote:
>> Running Manjaro on a Gigabyte B660M DS3H DDR4 with custom 5.17 kernel. Confirmed on other distributions and kernels back to 5.12; issue is not present on most recent 5.11 kernel. dmesg traceback points to i2c DesignWare driver, specifically drivers/i2c/busses/i2c-designware-master.c:369. It seems the msgs struct passed in to i2c_dw_xfer_msg is null.
>>
>> Similar issue seems to be reported here:  https://lore.kernel.org/lkml/YY5BRrE8bLyvd3PB@smile.fi.intel.com/t/
>>
>> lspci output: https://pastebin.com/MwFM2VBJ
>> dmesg from crashed kernel: https://pastebin.com/t6GsHjkq
>> kernel config: https://pastebin.com/awrSve5u
> 
> Could somebody take a look into this? Or was this discussed somewhere
> else already? Or even fixed?
> 
> Anyway, to get this tracked:
> 
> #regzbot introduced: v5.11..v5.12
> #regzbot from: Samuel Clark <slc2015@...il.com>
> #regzbot title: i2c: designware: Null pointer exception on resume from S3
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215907
> 
Thanks for sharing the bug. The reason why it occurs after v5.11 is that 
the i2c-designware support for Alder Lake -S came to v5.12 and issue is 
hiding before it.

Looks like there are suspend/resume issues with i2c-designware on some 
Gigabyte motherboards. I commented in the bugzilla if Samuel can attach 
the ACPI dump there.

Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ