[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #19 from Christophe Leroy (christophe.le...@csgroup.eu) --- Yes KASAN can bring some additional inputs. Maybe start with CONFIG_KFENCE, it is lighter than KASAN. For the above problem, maybe CONFIG_DEBUG_STACKOVERFLOW can help. --

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #18 from Erhard F. (erhar...@mailbox.org) --- Ok, and another problem during building via distcc on the G4, still LOWMEM_SIZE=0x2800 (kernel v5.17.6). [...] Oops: Kernel stack overflow, sig: 11 [#1] BE PAGE_SIZE=4K MMU=Hash SMP

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300775|0 |1 is obsolete|

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300774|0 |1 is obsolete|

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #15 from Erhard F. (erhar...@mailbox.org) --- It definitively still happens with the default values. Can test with the reduced CONFIG_LOWMEM_SIZE next week and report back. -- You may reply to this email to add a comment. You are

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #14 from Christophe Leroy (christophe.le...@csgroup.eu) --- Do you mean it still happens with the default values, or it also happens with the reduced CONFIG_LOWMEM_SIZE ? -- You may reply to this email to add a comment. You are

[Bug 215862] New: clang-14 fails 5.18-rc3 ppc64 BE kernel build - :0: error: expected relocatable expression

https://bugzilla.kernel.org/show_bug.cgi?id=215862 Bug ID: 215862 Summary: clang-14 fails 5.18-rc3 ppc64 BE kernel build - :0: error: expected relocatable expression Product: Platform Specific/Hardware Version: 2.5 Kernel

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #13 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300775 --> https://bugzilla.kernel.org/attachment.cgi?id=300775=edit kernel .config (5.18-rc3, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #12 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300774 --> https://bugzilla.kernel.org/attachment.cgi?id=300774=edit dmesg (5.18-rc3, PowerMac G4 DP) Another try with running glibc-2.34 testsuite on kernel

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300769 --> https://bugzilla.kernel.org/attachment.cgi?id=300769=edit dmesg (5.18-rc3, PowerMac G4 DP) Meanwhile the fixes landed in 5.16.x, 5.17.x and 5.18-rc3 is also

[Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 --- Comment #4 from Daniel Kolesa (li...@octaforge.org) --- Also, just to be clear, reverting the commit I linked above does fix the problem for me. Here is a patch you can quickly test:

[Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 --- Comment #3 from Daniel Kolesa (li...@octaforge.org) --- It does not panic in my case though; I merely get stuck with the offb framebuffer console instead of it switching modes to the right thing -- You may reply to this email to add a

[Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 Daniel Kolesa (li...@octaforge.org) changed: What|Removed |Added CC||li...@octaforge.org

[Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 --- Comment #1 from Zorro Lang (zl...@redhat.com) --- Created attachment 300697 --> https://bugzilla.kernel.org/attachment.cgi?id=300697=edit kernel .config file -- You may reply to this email to add a comment. You are receiving this mail

[Bug 215803] New: ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0

https://bugzilla.kernel.org/show_bug.cgi?id=215803 Bug ID: 215803 Summary: ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x0060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0 Product: Platform

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 --- Comment #4 from Christophe Leroy (christophe.le...@csgroup.eu) --- This problem was introduced in 5.15 by commit 602946ec2f90 ("powerpc: Set max_mapnr correctly") A similar issue has been opened at

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300667 --> https://bugzilla.kernel.org/attachment.cgi?id=300667=edit kernel .config (5.15.32, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300666 --> https://bugzilla.kernel.org/attachment.cgi?id=300666=edit kernel .config (5.16.18, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 215781] Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300665 --> https://bugzilla.kernel.org/attachment.cgi?id=300665=edit dmesg (5.15.32, PowerMac G4 DP) -- You may reply to this email to add a comment. You are

[Bug 215781] New: Highmem support broken on kernels greater 5.15.x on ppc32?

https://bugzilla.kernel.org/show_bug.cgi?id=215781 Bug ID: 215781 Summary: Highmem support broken on kernels greater 5.15.x on ppc32? Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.16.18 Hardware:

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #298919|0 |1 is obsolete|

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #19 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300562 --> https://bugzilla.kernel.org/attachment.cgi?id=300562=edit kernel .config (5.17-rc7, PowerMac G5 11,2) -- You may reply to this email to add a comment.

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #298933|0 |1 is obsolete|

[Bug 200055] [Bisected][Regression] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270

https://bugzilla.kernel.org/show_bug.cgi?id=200055 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEEDINFO|CLOSED

[Bug 200055] [Bisected][Regression] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270

https://bugzilla.kernel.org/show_bug.cgi?id=200055 --- Comment #25 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300559 --> https://bugzilla.kernel.org/attachment.cgi?id=300559=edit dmesg (kernel 5.17-rc7, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 200055] [Bisected][Regression] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270

https://bugzilla.kernel.org/show_bug.cgi?id=200055 --- Comment #24 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300558 --> https://bugzilla.kernel.org/attachment.cgi?id=300558=edit kernel .config (kernel 5.17-rc7, PowerMac G5 11,2) -- You may reply to this email to add a

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #9 from Alex Deucher (alexdeuc...@gmail.com) --- Only the person that filed the bug can close it. If it's fixed for you, please close it. Thanks! -- You may reply to this email to add a comment. You are receiving this mail

[Bug 215658] arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4)

https://bugzilla.kernel.org/show_bug.cgi?id=215658 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300550 --> https://bugzilla.kernel.org/attachment.cgi?id=300550=edit kernel dmesg (kernel 5.17-rc7, CONFIG_DRM_RADEON=m, Talos II) Seems this is issue already fixed in

[Bug 215658] arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4)

https://bugzilla.kernel.org/show_bug.cgi?id=215658 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 215658] New: arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4)

https://bugzilla.kernel.org/show_bug.cgi?id=215658 Bug ID: 215658 Summary: arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4) Product: Platform Specific/Hardware Version: 2.5

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- (In reply to Alex Deucher from comment #6) > You need to make sure the firmware is in your initrd. When the kernel > loads, it loads from the initrd. There is no filesystem mounted yet

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #6 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to Erhard F. from comment #5) > > With CONFIG_DRM_RADEON=m radeon does not load and I still get "modprobe: > ERROR: could not insert 'radeon': Unknown symbol in module, or

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Ok, changed my config to include the firmware via CONFIG_EXTRA_FIRMWARE="radeon/R520_cp.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" With CONFIG_DRM_RADEON=y the machine boots now as

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- No I don't use an initrd. The kernel to boot the Talos is on a boot partition, modules are loaded from root partition. Which worked in 5.16 and before. Now I am getting this "could not

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC|

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300522 --> https://bugzilla.kernel.org/attachment.cgi?id=300522=edit kernel .config (kernel 5.17-rc5, CONFIG_DRM_RADEON=m, Talos II) -- You may reply to this email to

[Bug 215652] kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300521 --> https://bugzilla.kernel.org/attachment.cgi?id=300521=edit kernel dmesg (kernel 5.17-rc5, CONFIG_DRM_RADEON=y, Talos II) -- You may reply to this email to

[Bug 215652] New: kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

https://bugzilla.kernel.org/show_bug.cgi?id=215652 Bug ID: 215652 Summary: kernel 5.17-rc fail to load radeon DRM "modprobe: ERROR: could not insert 'radeon': Unknown symbol in module, or unknown parameter (see dmesg)"

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Your 2nd patch solved the issue. Thanks Murilo! Build completes and the Talos boots fine into the patched 5.17-rc5. -- You may reply to this email to add a comment. You are receiving

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 --- Comment #4 from Murilo Opsfelder Araújo (mopsfel...@gmail.com) --- Erhard, would you mind trying the v2? https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-March/240715.html Christophe, thanks for the suggestion. That's exactly what I

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- I just tested your patch top of 5.17-rc5. It applies and build continues but fails later with: [...] CC lib/asn1_decoder.o GEN lib/oid_registry_data.c CC

[Bug 215567] build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 Murilo Opsfelder Araújo (mopsfel...@gmail.com) changed: What|Removed |Added CC|

[Bug 215621] Warning: Unable to mark rodata read only on this CPU. (PPC970MP)

https://bugzilla.kernel.org/show_bug.cgi?id=215621 --- Comment #4 from Christophe Leroy (christophe.le...@csgroup.eu) --- It is up to you to unselect CONFIG_STRICT_KERNEL_RWX. The kernel is usually built to boot on any PPC64 processors, so we can't forbid the selection of

[Bug 215621] Warning: Unable to mark rodata read only on this CPU. (PPC970MP)

https://bugzilla.kernel.org/show_bug.cgi?id=215621 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215621] Warning: Unable to mark rodata read only on this CPU. (PPC970MP)

https://bugzilla.kernel.org/show_bug.cgi?id=215621 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #298393|0 |1 is obsolete|

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #298019|0 |1 is obsolete|

[Bug 215622] WARNING: possible irq lock inversion dependency detected

https://bugzilla.kernel.org/show_bug.cgi?id=215622 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300485 --> https://bugzilla.kernel.org/attachment.cgi?id=300485=edit kernel .config (5.17-rc4, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 215622] New: WARNING: possible irq lock inversion dependency detected

https://bugzilla.kernel.org/show_bug.cgi?id=215622 Bug ID: 215622 Summary: WARNING: possible irq lock inversion dependency detected Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.17-rc4 Hardware:

[Bug 215621] Warning: Unable to mark rodata read only on this CPU. (PPC970MP)

https://bugzilla.kernel.org/show_bug.cgi?id=215621 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300483 --> https://bugzilla.kernel.org/attachment.cgi?id=300483=edit kernel .config (5.17-rc4, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 215621] New: Warning: Unable to mark rodata read only on this CPU. (PPC970MP)

https://bugzilla.kernel.org/show_bug.cgi?id=215621 Bug ID: 215621 Summary: Warning: Unable to mark rodata read only on this CPU. (PPC970MP) Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.17-rc4

[Bug 215169] UBSAN: shift-out-of-bounds in arch/powerpc/mm/kasan/book3s_32.c:22:23

https://bugzilla.kernel.org/show_bug.cgi?id=215169 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 214867] UBSAN: shift-out-of-bounds in drivers/of/unittest.c:1933:36

https://bugzilla.kernel.org/show_bug.cgi?id=214867 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215567] New: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config

https://bugzilla.kernel.org/show_bug.cgi?id=215567 Bug ID: 215567 Summary: build failure when PPC_64S_HASH_MMU=n is selected in kernel .config Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.17-rc2

[Bug 210749] sysfs: cannot create duplicate filename '/bus/nvmem/devices/module-vpd'

https://bugzilla.kernel.org/show_bug.cgi?id=210749 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- (In reply to Christophe Leroy from comment #10) > I'm wondering whether you could be running out of vmalloc space. I initially > thought you were using KASAN, but it seems not according to

[Bug 206669] Little-endian kernel crashing on POWER8 on heavy big-endian PowerKVM load

https://bugzilla.kernel.org/show_bug.cgi?id=206669 --- Comment #19 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) --- In case any runs into this issue, a workaround is disabling "dynamic_mt_modes": # echo 0 > /sys/module/kvm_hv/parameters/dynamic_mt_modes This fixes the crashes

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #10 from Christophe Leroy (christophe.le...@csgroup.eu) --- Thanks for the tests. I'm not surprised that the system doesn't poweroff or reboot without ADB_PMU because the PMU manages power. The "neverending build" is maybe because

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300354 --> https://bugzilla.kernel.org/attachment.cgi?id=300354=edit dmesg (5.10-rc2 with ADB_PMU disabled, PowerMac G4 DP) Took a little time but I double checked the

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #8 from Christophe Leroy (christophe.le...@csgroup.eu) --- Looking closer, in fact that might be a false positive. The huge difference with that bad commit is that: - Before the commit, the kernel is built _without_ CONFIG_VMAP_STACK

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #7 from Christophe Leroy (christophe.le...@csgroup.eu) --- Interesting ... Though confusing. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300318 --> https://bugzilla.kernel.org/attachment.cgi?id=300318=edit bisect.log Ok, finally got it. Interesting find: # git bisect bad

[Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Summary|"Kernel panic - not |[bisected] "Kernel

[Bug 213837] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300297 --> https://bugzilla.kernel.org/attachment.cgi?id=300297=edit bisect.log Finally did a bisect which revealed the following commit: # git bisect good

[Bug 215470] New: Unable to boot NXP P2020 processor (freeze before any print to stdout)

https://bugzilla.kernel.org/show_bug.cgi?id=215470 Bug ID: 215470 Summary: Unable to boot NXP P2020 processor (freeze before any print to stdout) Product: Platform Specific/Hardware Version: 2.5 Kernel Version: >=v5.15-rc1

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Ok, with zswap lzo/zbud I also get this memory corruption on 5.15.13. So most probably it's not lzo/z3pool but something else. I'll start a bisect then... -- You may reply to this email

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- I was able to easily reproduce this on 5.15.13, however not on 5.16-rc8. But on 5.16-rc8 I got this the 3rd time I ran the glibc testsuite: [...] watchdog: BUG: soft lockup - CPU#1 stuck

[Bug 215443] [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1]

https://bugzilla.kernel.org/show_bug.cgi?id=215443 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- (In reply to Alex Deucher from comment #2) > does appending amdgpu.runpm=0 on the kernel command line help? I doubt it as amdgpu is not even built (# CONFIG_DRM_AMDGPU is not set, see

[Bug 215443] [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1]

https://bugzilla.kernel.org/show_bug.cgi?id=215443 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC|

[Bug 215443] [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1]

https://bugzilla.kernel.org/show_bug.cgi?id=215443 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300197 --> https://bugzilla.kernel.org/attachment.cgi?id=300197=edit kernel .config (kernel 5.16-rc7, Talos II) -- You may reply to this email to add a comment. You

[Bug 215443] New: [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1]

https://bugzilla.kernel.org/show_bug.cgi?id=215443 Bug ID: 215443 Summary: [radeon] BUG: Unable to handle kernel data access on read at 0xc0079130, Oops: Kernel access of bad area, sig: 11 [#1] Product: Platform

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Bisecting will take some time. I'll report back as soon as I have any findings. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300115 --> https://bugzilla.kernel.org/attachment.cgi?id=300115=edit kernel .config (5.15.10, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 215389] New: pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

https://bugzilla.kernel.org/show_bug.cgi?id=215389 Bug ID: 215389 Summary: pagealloc: memory corruption at building glibc-2.33 and running its' testsuite Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.15.10

[Bug 215381] BUG: Unable to handle kernel data access on read at 0x6600cc00000004

https://bugzilla.kernel.org/show_bug.cgi?id=215381 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300107 --> https://bugzilla.kernel.org/attachment.cgi?id=300107=edit kernel .config (kernel 5.15.10, Talos II) -- You may reply to this email to add a comment. You

[Bug 215381] New: BUG: Unable to handle kernel data access on read at 0x6600cc00000004

https://bugzilla.kernel.org/show_bug.cgi?id=215381 Bug ID: 215381 Summary: BUG: Unable to handle kernel data access on read at 0x6600cc0004 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.15.10

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- (In reply to Christophe Leroy from comment #13) > arch/powerpc/lib/feature-fixups.o also need DISABLE_LATENT_ENTROPY_PLUGIN, > see extract from you vmlinux below I can confirm this works,

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #13 from Christophe Leroy (christophe.le...@csgroup.eu) --- arch/powerpc/lib/feature-fixups.o also need DISABLE_LATENT_ENTROPY_PLUGIN, see extract from you vmlinux below c0c0ad20 : c0c0ad20: 94 21 ff e0 stwur1,-32(r1)

[Bug 215285] power9 le: amdgpu: *ERROR* hw_init of IP block failed -22

https://bugzilla.kernel.org/show_bug.cgi?id=215285 --- Comment #1 from R0b0t1 (s...@aeam.us) --- Probable cause: missing dependencies (https://bugs.gentoo.org/736994). For PPC64, unsure of fix, see https://bugs.gentoo.org/829209 -- is there really a hard dependency on X86_64 and ACPI? -- You

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300015|0 |1 is obsolete|

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #11 from Christophe Leroy (christophe.le...@csgroup.eu) --- Ok, so that's not enough, must be something else. I guess you are right next step should be analysis of the image. zImage however can hardly be used for that. Could you

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #10 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300015 --> https://bugzilla.kernel.org/attachment.cgi?id=300015=edit kernel zImage (5.16-rc5 + CFLAGS_setup_32.o/early_32.o +=... , PowerMac G4 DP) Unfortunately

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #9 from Christophe Leroy (christophe.le...@csgroup.eu) --- Erhard, were you able to redo the test with DISABLE_LATENT_ENTROPY_PLUGIN also disabled for early_32.o ? If you can try with it disabled for both early_32.o and setup_32.o

[Bug 215285] New: power9 le: amdgpu: *ERROR* hw_init of IP block failed -22

https://bugzilla.kernel.org/show_bug.cgi?id=215285 Bug ID: 215285 Summary: power9 le: amdgpu: *ERROR* hw_init of IP block failed -22 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.15.6 Hardware:

[Bug 214913] [xfstests generic/051] BUG: Kernel NULL pointer dereference on read at 0x00000108 NIP [c0000000000372e4] tm_cgpr_active+0x14/0x40

https://bugzilla.kernel.org/show_bug.cgi?id=214913 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|ASSIGNED|NEEDINFO ---

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #8 from Christophe Leroy (christophe.le...@csgroup.eu) --- early_32.o should likely also have DISABLE_LATENT_ENTROPY_PLUGIN, maybe even more important that for setup_32.o -- You may reply to this email to add a comment. You are

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299967 --> https://bugzilla.kernel.org/attachment.cgi?id=299967=edit kernel .config (5.16-rc4 + CFLAGS_setup_32.o +=... , PowerMac G4 DP) -- You may reply to this

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- Ok I cheked that out. There are already some in the Makefile: CFLAGS_cputable.o += $(DISABLE_LATENT_ENTROPY_PLUGIN) CFLAGS_prom_init.o += $(DISABLE_LATENT_ENTROPY_PLUGIN) CFLAGS_btext.o +=

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299935 --> https://bugzilla.kernel.org/attachment.cgi?id=299935=edit kernel .config (4.18.20, PowerMac G4 DP) Hmm, strange... I tried to bisect but found out that

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #3 from Christophe Leroy (christophe.le...@csgroup.eu) --- I tried your config under QEMU and it works. So I don't know how I could help. >> = >> OpenBIOS 1.1 [Jul 22 2021

[Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)

https://bugzilla.kernel.org/show_bug.cgi?id=215217 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Just rebuilt the kernel without KASAN but I still hit this bug. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the

<    1   2   3   4   5   6   7   8   9   10   >