| 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
| ||
|
Message-ID: <20251230172427.4f22ac7c@windsurf> Date: Tue, 30 Dec 2025 17:24:27 +0100 From: Thomas Petazzoni <thomas.petazzoni@...tlin.com> To: Fabian Pflug <f.pflug@...gutronix.de> Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org, Haidong Zheng <haidong.zheng@....com>, Danwei Luo <danwei.luo@....com>, Lei Xu <lei.xu@....com> Subject: Re: [PATCH v4 2/2] arm64: dts: freescale: add support for NXP i.MX93 FRDM Hello (again), On Tue, 30 Dec 2025 17:15:48 +0100 Thomas Petazzoni <thomas.petazzoni@...tlin.com> wrote: > I see the PMIC interrupt and the RTC interrupts are routed to the I2C > GPIO expander at 1-0022, so I imagine either the PMIC or the RTC are > triggering an interrupt (left enabled by U-Boot), and the kernel isn't > compiled with the driver for either the PMIC or the RTC, and therefore > there's no IRQ handler? > > (I confess I didn't investigate more than that at this point.) Upon closer inspection, I in fact get thousands over IRQ #100 per seconds right after boot, until the point where it reaches 100000 IRQ events, and the splat appears, with the IRQ being subsequently disabled. So it's not just one interrupt, but a storm of it. Thomas -- Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com
Powered by blists - more mailing lists