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

2023-10-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #41 from Christophe Leroy (christophe.le...@csgroup.eu) --- I'm out of office until 06 Nov. -- 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

2023-10-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300354|0 |1 is obsolete|

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

2023-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #39 from Erhard F. (erhar...@mailbox.org) --- No change with 6.4-rc4, only additional data "page_type: 0x()" is shown: [...] pagealloc: memory corruption 06fe3258: 00 00 00 00 CPU: 1

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

2023-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #38 from Erhard F. (erhar...@mailbox.org) --- Created attachment 304309 --> https://bugzilla.kernel.org/attachment.cgi?id=304309=edit kernel .config (6.3.3, PowerMac G4 DP) -- 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

2023-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #37 from Erhard F. (erhar...@mailbox.org) --- Created attachment 304308 --> https://bugzilla.kernel.org/attachment.cgi?id=304308=edit dmesg (6.3.3, KCSAN, PowerMac G4 DP) Thanks for taking another look into this Christophe!

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

2023-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #36 from Christophe Leroy (christophe.le...@csgroup.eu) --- Would be nice to give it a new try with KCSAN enabled. To get KCSAN on powerpc/32, apply following series:

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

2022-08-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #35 from Erhard F. (erhar...@mailbox.org) --- Created attachment 301640 --> https://bugzilla.kernel.org/attachment.cgi?id=301640=edit kernel .config (6.0-rc2, 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

2022-08-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #301302|0 |1 is obsolete|

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

2022-07-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #33 from Erhard F. (erhar...@mailbox.org) --- Created attachment 301337 --> https://bugzilla.kernel.org/attachment.cgi?id=301337=edit dmesg (5.19-rc5, outline KASAN, PowerMac G4 DP) Re-tested on 5.19-rc5 +

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

2022-06-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #32 from Erhard F. (erhar...@mailbox.org) --- (In reply to Michael Ellerman from comment #30) > It's a bit of a stab in the dark, but can you try turning preempt off? > > ie. CONFIG_PREEMPT_NONE=y Looks like your intuition was not

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

2022-06-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #31 from Erhard F. (erhar...@mailbox.org) --- (In reply to Michael Ellerman from comment #30) > It's a bit of a stab in the dark, but can you try turning preempt off? > > ie. CONFIG_PREEMPT_NONE=y Just tested that. Backtrace looks a

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

2022-06-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #30 from Michael Ellerman (mich...@ellerman.id.au) --- It's a bit of a stab in the dark, but can you try turning preempt off? ie. CONFIG_PREEMPT_NONE=y -- You may reply to this email to add a comment. You are receiving this mail

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

2022-06-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300115|0 |1 is obsolete|

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

2022-06-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #300113|0 |1 is obsolete|

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

2022-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #27 from Erhard F. (erhar...@mailbox.org) --- I opened a new bug for the stack issue which contains a bit more data. Hopefully the output is of some help (see bug #216041). -- 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

2022-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #26 from Christophe Leroy (christophe.le...@csgroup.eu) --- Note that THREAD_SHIFT is set to 14 when using KASAN: config THREAD_SHIFT int "Thread shift" if EXPERT range 13 15 default "15" if PPC_256K_PAGES

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

2022-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #25 from Christophe Leroy (christophe.le...@csgroup.eu) --- The Kernel stack overflow looks odd. Value of R1 is wrong and LR is NULL. Don't know how we ended up here, but probably not by a real stack overflow. -- You may reply to

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

2022-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #24 from Christophe Leroy (christophe.le...@csgroup.eu) --- Seems like with Inline KASAN your kernel is far too big compared to what we support at the time being: c2468000 T __end_rodata c280 T __init_begin c280 T _sinittext

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

2022-05-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #23 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300978 --> https://bugzilla.kernel.org/attachment.cgi?id=300978=edit kernel .config (5.18-rc6, CONFIG_LOWMEM_SIZE=0x2800, outline KASAN, PowerMac G4 DP) -- You

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

2022-05-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #22 from Erhard F. (erhar...@mailbox.org) --- Created attachment 300977 --> https://bugzilla.kernel.org/attachment.cgi?id=300977=edit dmesg (5.18-rc6, CONFIG_LOWMEM_SIZE=0x2800, outline KASAN, PowerMac G4 DP) I increased

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

2022-05-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |ASSIGNED

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

2022-05-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #20 from Erhard F. (erhar...@mailbox.org) --- DEBUG_STACKOVERFLOW and KFENCE have been enabled already in the builds I did here (see kernel attached kernel .config here). However if I enable (inline) KASAN the kernel won't boot at

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

2022-05-12 Thread bugzilla-daemon
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

2022-05-11 Thread bugzilla-daemon
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

2022-05-11 Thread bugzilla-daemon
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

2022-05-11 Thread bugzilla-daemon
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

2022-05-02 Thread bugzilla-daemon
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

2022-05-02 Thread bugzilla-daemon
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 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

2022-04-18 Thread bugzilla-daemon
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

2022-04-18 Thread bugzilla-daemon
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 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

2022-01-31 Thread bugzilla-daemon
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 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

2022-01-30 Thread bugzilla-daemon
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

2022-01-30 Thread bugzilla-daemon
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

2022-01-25 Thread bugzilla-daemon
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

2022-01-25 Thread bugzilla-daemon
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

2022-01-25 Thread bugzilla-daemon
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 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

2022-01-08 Thread bugzilla-daemon
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

2022-01-07 Thread bugzilla-daemon
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 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite

2021-12-26 Thread bugzilla-daemon
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

2021-12-24 Thread bugzilla-daemon
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

2021-12-22 Thread bugzilla-daemon
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