linux-kernel - Re: [REGRESSION] spi: omap2-mcspi: not working with kernel v6.10

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1b9852d1-4454-4f62-bd8a-fb6167dc0576@leemhuis.info>
Date: Mon, 17 Jun 2024 11:29:05 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: João Paulo Gonçalves
 <jpaulo.silvagoncalves@...il.com>, Mark Brown <broonie@...nel.org>,
 Vaishnav Achath <vaishnav.a@...com>,
 Louis Chauvet <louis.chauvet@...tlin.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
 joao.goncalves@...adex.com,
 Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [REGRESSION] spi: omap2-mcspi: not working with kernel v6.10

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

On 12.06.24 19:00, João Paulo Gonçalves wrote:
> 
> It appears that omap2-mcspi broke on kernel v6.10. I was testing an EEPROM like
> SPI FRAM using this DT:
> 
> &main_spi1 {
> 	pinctrl-0 = <&pinctrl_spi1>,
> 		    <&pinctrl_gpio_4>;
> 	cs-gpios =  <&mcu_gpio0 4 GPIO_ACTIVE_LOW>;
> 	status = "okay";
> 
> 	fram@0 {
> 		compatible = "fujitsu,mb85rs256", "atmel,at25";
> 		reg = <0>;
> 		address-width = <16>;
> 		size = <32768>;
> 		spi-max-frequency = <33000000>;
> 		pagesize = <1>;
> 	};
> };
> 
> On kernel v6.9, spi works fine and is possible to read/write the FRAM. However,
> on kernel v6.10-rc3 it gives me an Oops after a timeout:
> [...]

Thx for the report. Hmm, no developer replied yet. I suspect that means
they have no idea what causes this. In that case the thing that really
helps would be if you could use a git bisection to find the change that
causes this.

Anyway, to ensure that does not fall though the cracks, let me add this
to the tracking:

#regzbot report ^
#regzbot introduced: v6.9..v6.10-rc3
#regzbot summary: spi: omap2-mcspi: omap2-mcspi broke, Oops after a timeout

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.