Phil Elwell
Phil Elwell
> This suggests the pcie-32bit-dma-pi5 overlay has compatibility issues with kernel 6.12 on the Pi 5 To me it suggests that there are problems with the mt7915e on Pi 5...
Looking at the increasing mess that is the downstream bcm2711 DTS files, I think we need to split out our common modifications into files that get included by each platform,...
The bug report at the link says that reading hwrng provokes the problem. Does running `sudo dd if=/dev/hwrng of=/dev/null bs=64 count=1` trigger a glitch in your system?
Can you point to any software which requires it?
That's not a compelling argument in favour of enabling the feature. It's telling that only one architecture (and 2 defconfigs) enable it: ``` arch/s390/configs/debug_defconfig:110:CONFIG_ANON_VMA_NAME=y arch/s390/configs/defconfig:101:CONFIG_ANON_VMA_NAME=y ```
I'm not seeing that on Bookworm with either 6.6 or 6.7, when testing using Pi 5 and its built-in RTC., but on a CM4+CM4IO running Bullseye with the onboard PCF85073a...
From the comments on the issue on the sdtool maintainer's site (https://github.com/BertoldVdb/sdtool/issues/10), it isn't understood and also doesn't appear to be specific to Raspberry Pi.
#7029 is a reversion to the downstream driver until we understand this issue more.
It would help me to understand the symptoms a bit more. Simply pulling the plug on a running system is asking for trouble, but its not clear whether you are...
Thanks for all of the additional details. >> BTW, I don't see the linked forum thread as being the same issue at all - that was about a mismatched set...