Hi all, > Am 03.09.2024 um 16:00 schrieb H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: > > > >> Am 03.09.2024 um 15:09 schrieb H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: >> >> I can roll back and try to build&run letux-6.10-rc1 as well. > > Ok, I can confirm this issue in 6.10-rc1: > > [ 0.000000] Linux version 6.10.0-rc1-letux+ (hns@iMac.local) (arm-linux-gnueabihf-gcc (GCC) 6.3.0, GNU ld (GNU Binutils) 2.27) #18983 SMP PREEMPT Tue Sep 3 15:18:59 CEST 2024 > [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > [ 0.000000] OF: fdt: Machine model: TI OMAP4 PandaBoard-ES > ... > [ 2.315277] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz > [ 2.325073] ocp:target-module@48210000:mpu:fck: device ID is greater than 24 > [ 2.332580] ti-sysc ocp:target-module@48210000: could not add child clock fck: -12 > [ 2.356781] omap_wdt: OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec > > Boot process is stuck with > SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.33: No such file or directory > > Both effects are gone with 6.11-rc6. I had made a mistake in updating the kernels and drawn a false conclusion. The new result is: all kernels I have tested between v6.10-rc1 and v6.11-rc6 report these messages. But after 6.10-rc1 they appear to be harmless (I did not miss any functions so far) and it is not clear if my 6.10-rc1 being stuck is related to this at all. E.g. from 6.11-rc6: root@letux:~# dmesg | fgrep 'device ID is greater than' [ 2.340148] ocp:target-module@48210000:mpu:fck: device ID is greater than 24 [ 2.414978] ocp:target-module@54000000:pmu:fck: device ID is greater than 24 [ 2.491973] 5a05a400.target-module:iva:fck: device ID is greater than 24 root@letux:~# BR, Nikolaus
