Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Message-ID: <e6eacb51-bd9f-e014-5735-a624186458a8@linux.intel.com>
Date:   Fri, 6 May 2022 11:44:43 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Firefox/91.0 Thunderbird/91.8.1
Subject: Re: regression: Null pointer exception on resume from S3 with i2c
 DesignWare driver
Content-Language: en-US
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     Samuel Clark <slc2015@gmail.com>,
        "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
        "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        LKML <linux-kernel@vger.kernel.org>
References: <941f292d-2ce2-d7aa-3d70-01a11ba171cf@leemhuis.info>
From:   Jarkko Nikula <jarkko.nikula@linux.intel.com>
In-Reply-To: <941f292d-2ce2-d7aa-3d70-01a11ba171cf@leemhuis.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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@gmail.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