[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #40 from Christophe Leroy (christophe.le...@csgroup.eu) --- Would also be great if you can activate CONFIG_PTDUMP_DEBUGFS and provide the content of /sys/kernel/debug/kernel_page_tables -- You may reply to this email to add a

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #39 from Christophe Leroy (christophe.le...@csgroup.eu) --- Can you retry with CONFIG_LOWMEM_SIZE=0x2800 or CONFIG_LOWMEM_SIZE=0x2000 ? -- You may reply to this email to add a comment. You are receiving this mail because:

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #38 from Christophe Leroy (christophe.le...@csgroup.eu) --- Looks like only x86 are arm implement this vmalloc= parameter: [chleroy@PO20335 linux-powerpc]$ git grep 'early_param("vmalloc"' arch/

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #37 from Christophe Leroy (christophe.le...@csgroup.eu) --- I see no obvious reason for a 32Mb allocation to fail while you have 588612kB free memory. And that happens early at boot, before user processes are started so the vmap

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #292347|0 |1 is obsolete|

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #35 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299713 --> https://bugzilla.kernel.org/attachment.cgi?id=299713=edit dmesg (5.15.5, INLINE KASAN, PowerMac G4 DP) -- You may reply to this email to add a comment.

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-11-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #34 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299711 --> https://bugzilla.kernel.org/attachment.cgi?id=299711=edit dmesg (5.15.5, OUTLINE KASAN, PowerMac G4 DP) Finally my G4 DP got its' fixed & overhauled PSU so

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

2021-11-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #4 from Zorro Lang (zl...@redhat.com) --- (In reply to Michal Suchanek from comment #3) > What CPU is this? > > Does it go away if you boot with ppc_tm=off (In reply to Michael Ellerman from comment #2) > Thanks for the report, I

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

2021-11-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 Michal Suchanek (hramr...@gmail.com) changed: What|Removed |Added CC||hramr...@gmail.com

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

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

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

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

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

2021-11-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 Bug ID: 214913 Summary: [xfstests generic/051] BUG: Kernel NULL pointer dereference on read at 0x0108 NIP [c00372e4] tm_cgpr_active+0x14/0x40 Product: Platform

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

2021-10-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214867 --- Comment #3 from Frank Rowand (bugzilla.kernel@frowand.com) --- I forwarded my email notification of this bug to the mail lists. I prefer discussion to occur there:

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

2021-10-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214867 Arnd Bergmann (a...@arndb.de) changed: What|Removed |Added CC||a...@arndb.de ---

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

2021-10-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214867 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299363 --> https://bugzilla.kernel.org/attachment.cgi?id=299363=edit kernel .config (kernel 5.15-rc7, Talos II) # lspci :00:00.0 PCI bridge: IBM POWER9 Host

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

2021-10-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214867 Bug ID: 214867 Summary: UBSAN: shift-out-of-bounds in drivers/of/unittest.c:1933:36 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.15-rc7 Hardware:

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

2021-10-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206669 --- Comment #18 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) --- There seems to be a related discussion: > https://yhbt.net/lore/all/20200831091523.gc29...@kitsune.suse.cz/T/ This suspects

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

2021-09-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206669 --- Comment #17 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) --- POWER server crashes with 100% reproducibility when building GCC in a powerpc chroot and GCC in a ppc64 chroot on the ppc64 KVM instance at the same time. And I

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

2021-09-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #12 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298963 --> https://bugzilla.kernel.org/attachment.cgi?id=298963=edit dmesg (5.15-rc2 + patch, PowerMac G5 11,2) #1 Last stack trace with CONFIG_THREAD_SHIFT=14

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

2021-09-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298961 --> https://bugzilla.kernel.org/attachment.cgi?id=298961=edit System.map (5.15-rc2 + patch + CONFIG_THREAD_SHIFT=15, PowerMac G5 11,2) -- You may reply to

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

2021-09-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #10 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298959 --> https://bugzilla.kernel.org/attachment.cgi?id=298959=edit kernel .config (5.15-rc2 + CONFIG_THREAD_SHIFT=15, PowerMac G5 11,2) (In reply to mpe from

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

2021-09-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298933 --> https://bugzilla.kernel.org/attachment.cgi?id=298933=edit System.map (5.15-rc2 + patch, PowerMac G5 11,2) (In reply to mpe from comment #8) > So it looks

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

2021-09-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #8 from m...@ellerman.id.au --- bugzilla-dae...@bugzilla.kernel.org writes: > https://bugzilla.kernel.org/show_bug.cgi?id=213837 > > --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- > Created attachment 298919 > -->

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

2021-09-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298919 --> https://bugzilla.kernel.org/attachment.cgi?id=298919=edit dmesg (5.15-rc2 + patch, PowerMac G5 11,2) (In reply to mpe from comment #6) > Can you try this

[Bug 213803] G5 kernel build (v5.14-rc2) fails at linking stage - ld: arch/powerpc/mm/pgtable.o: in function `.__ptep_set_access_flags': /usr/src/linux-stable/./arch/powerpc/include/asm/book3s/64/pgta

2021-09-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213803 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

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

2021-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206669 --- Comment #16 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) --- Hi Michael! Thanks a lot for looking into this! If you have installed a Debian unstable big-endian system, the easiest way to get such a setup by creating an

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

2021-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206669 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |NEEDINFO

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

2021-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |NEEDINFO --

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

2021-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

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

2021-09-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206669 --- Comment #14 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) --- Still reproduces with Linux 5.10.46 from Debian Bullseye. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching

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

2021-09-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #6 from m...@ellerman.id.au --- bugzilla-dae...@bugzilla.kernel.org writes: > https://bugzilla.kernel.org/show_bug.cgi?id=213837 > > Erhard F. (erhar...@mailbox.org) changed: > >What|Removed |Added

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

2021-09-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #298395|0 |1 is obsolete|

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

2021-09-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added See Also|https://bugzilla.kernel.org |

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-08-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #18 from Erhard F. (erhar...@mailbox.org) --- The 'hackfix for MSI init' patch also applies on top of v5.14-rc6. But unchanged the G5 runs later into bug #213837. -- You may reply to this email to add a comment. You are receiving

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

2021-08-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298395 --> https://bugzilla.kernel.org/attachment.cgi?id=298395=edit kernel .config (5.14-rc6, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

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

2021-08-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298393 --> https://bugzilla.kernel.org/attachment.cgi?id=298393=edit dmesg (5.14-rc6, PowerMac G5 11,2) Happens also on 5.14-rc6: [...] Kernel panic - not syncing:

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

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

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

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

[Bug 213961] Oops while loading radeon driver

2021-08-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 Elimar Riesebieter (riese...@lxtec.de) changed: What|Removed |Added Component|PPC-32 |Video(Other)

[Bug 213961] Oops while loading radeon driver

2021-08-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #10 from Christophe Leroy (christophe.le...@csgroup.eu) --- (In reply to Elimar Riesebieter from comment #9) > Well, 5.13.8 just runs fine, though. Yes, recent changes to Radeon appear for the first time in v5.14-rc1 -- You may

[Bug 213961] Oops while loading radeon driver

2021-08-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #9 from Elimar Riesebieter (riese...@lxtec.de) --- Well, 5.13.8 just runs fine, though. -- 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 213961] Oops while loading radeon driver

2021-08-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #8 from Christophe Leroy (christophe.le...@csgroup.eu) --- Great: [ 15.246367] NIP [bea42a80] radeon_agp_head_init+0x1c/0xf8 [radeon] [ 15.246969] LR [bea39860] radeon_driver_load_kms+0x1bc/0x1f4 [radeon] [ 15.247160] Call

[Bug 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #7 from Elimar Riesebieter (riese...@lxtec.de) --- Created attachment 298205 --> https://bugzilla.kernel.org/attachment.cgi?id=298205=edit dmesg dump with KALLSYMS enabled -- You may reply to this email to add a comment. You are

[Bug 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #6 from Elimar Riesebieter (riese...@lxtec.de) --- Created attachment 298203 --> https://bugzilla.kernel.org/attachment.cgi?id=298203=edit config with KALLSYMS enabled -- You may reply to this email to add a comment. You are

[Bug 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #5 from Elimar Riesebieter (riese...@lxtec.de) --- Configuring KALLSYMS doesn't give the function names -- 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 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #4 from Christophe Leroy (christophe.le...@csgroup.eu) --- Thanks, unfortunately the info is still not usable because we don't have function names in the dump: [ 15.810083] Call Trace: [ 15.810090] [f2b6dc30] [c1022318]

[Bug 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #3 from Elimar Riesebieter (riese...@lxtec.de) --- Created attachment 298197 --> https://bugzilla.kernel.org/attachment.cgi?id=298197=edit .config -- You may reply to this email to add a comment. You are receiving this mail

[Bug 213961] Oops while loading radeon driver

2021-08-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 --- Comment #2 from Elimar Riesebieter (riese...@lxtec.de) --- Created attachment 298195 --> https://bugzilla.kernel.org/attachment.cgi?id=298195=edit dmesg dump -- You may reply to this email to add a comment. You are receiving this mail

[Bug 213961] Oops while loading radeon driver

2021-08-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 213961] New: Oops while loading radeon driver

2021-08-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213961 Bug ID: 213961 Summary: Oops while loading radeon driver Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.14-rc4 Hardware: PPC-32 OS: Linux

[Bug 213803] G5 kernel build (v5.14-rc2) fails at linking stage - ld: arch/powerpc/mm/pgtable.o: in function `.__ptep_set_access_flags': /usr/src/linux-stable/./arch/powerpc/include/asm/book3s/64/pgta

2021-08-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213803 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Still a problem in v5.14-rc4. -- 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 213837] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5

2021-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 298019 --> https://bugzilla.kernel.org/attachment.cgi?id=298019=edit kernel .config (5.13.4, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

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

2021-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213837 Bug ID: 213837 Summary: "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5 Product: Memory Management

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #15 from Erhard F. (erhar...@mailbox.org) --- (In reply to Oliver O'Halloran from comment #13) > In the meanwhile, can you try the patch above? That seems to fix bug which > is causing MSIs to be unusable. I'm not 100% sure why that

[Bug 205303] Compilation for PPC64 fails on warning in watchdog.o

2021-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205303 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 213803] New: G5 kernel build (v5.14-rc2) fails at linking stage - ld: arch/powerpc/mm/pgtable.o: in function `.__ptep_set_access_flags': /usr/src/linux-stable/./arch/powerpc/include/asm/book3s/64

2021-07-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213803 Bug ID: 213803 Summary: G5 kernel build (v5.14-rc2) fails at linking stage - ld: arch/powerpc/mm/pgtable.o: in function `.__ptep_set_access_flags':

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

2021-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #295621|0 |1 is obsolete|

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

2021-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297867 --> https://bugzilla.kernel.org/attachment.cgi?id=297867=edit dmesg (kernel 5.14-rc1 w. 61f764c307f6, 4e302c3b568e reverted, Talos II) Yes, I can confirm

[Bug 213733] Kernel NULL pointer dereference on read (Oops: Kernel access of bad area, sig: 7 [#1]) at systemctl poweroff

2021-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213733 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297859 --> https://bugzilla.kernel.org/attachment.cgi?id=297859=edit kernel .config (kernel 5.14-rc1, Talos II) -- You may reply to this email to add a comment. You

[Bug 213733] New: Kernel NULL pointer dereference on read (Oops: Kernel access of bad area, sig: 7 [#1]) at systemctl poweroff

2021-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213733 Bug ID: 213733 Summary: Kernel NULL pointer dereference on read (Oops: Kernel access of bad area, sig: 7 [#1]) at systemctl poweroff Product: Platform Specific/Hardware Version: 2.5

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-07-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Thanks for the patch! I will try it as soon as I get to this G5 again. Don't know whether write access is necessary to trigger the bug. The past weekend I've seen it only by doing an

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-07-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #13 from Oliver O'Halloran (ooh...@gmail.com) --- Hi, I got a loaner G5 with an NVMe drive, but I haven't been able to replicate the crash you're seeing. However, I think that's probably because I'm only reading from the NVMe since

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-07-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #12 from Oliver O'Halloran (ooh...@gmail.com) --- Created attachment 297755 --> https://bugzilla.kernel.org/attachment.cgi?id=297755=edit hackfix for MSI init -- You may reply to this email to add a comment. You are receiving

[Bug 195755] rcu_sched detected stalls on CPUs/tasks: (detected by 0, t=6302 jiffies, g=11405, c=11404, q=1880), ppc64, G5

2021-06-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=195755 r...@heitbaum.com changed: What|Removed |Added CC||r...@heitbaum.com --- Comment #31

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #33 from Erhard F. (erhar...@mailbox.org) --- I can tell you in the next few weeks, as soon as my G4 MDD gets its' overhaul with the serviced PSU. -- You may reply to this email to add a comment. You are receiving this mail

[Bug 11143] [PATCH]unconditional linker option arch/powerpc/lib/crtsavres.o causes external module buildfailure

2021-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=11143 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 209277] powerpc: obsolete driver: Marvell MV64X60 MPSC

2021-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=209277 --- Comment #4 from Christophe Leroy (christophe.le...@csgroup.eu) --- The watchdog patch is flagged 'accepted' in patchwork, should go into 5.14 -- You may reply to this email to add a comment. You are receiving this mail because: You are

[Bug 209277] powerpc: obsolete driver: Marvell MV64X60 MPSC

2021-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=209277 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d

2021-06-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205099 --- Comment #32 from Christophe Leroy (christophe.le...@csgroup.eu) --- Is this problem still there with 5.13 ? -- 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 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297473 --> https://bugzilla.kernel.org/attachment.cgi?id=297473=edit dmesg (5.13-rc6 + DEBUG_VM_PGTABLE, PowerMac G5 11,2) The trace got some additional data with

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-06-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

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

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297437 --> https://bugzilla.kernel.org/attachment.cgi?id=297437=edit dmesg (5.13-rc6 w. patch fbbefb3 reverted + debug, PowerMac G5 11,2) -- You may reply to this

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297435 --> https://bugzilla.kernel.org/attachment.cgi?id=297435=edit dmesg (5.13-rc6 + debug, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- (In reply to Oliver O'Halloran from comment #5) > Could you add "debug" to the kernel command line and post the dmesg output > for a boot with the patch applied and reverted? Ok, on top of

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- This is already a custom built kernel with lots of debugging options turned on (see bugzilla attached kernel .config). But of course I can add "debug" to the other kernel command line

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #5 from Oliver O'Halloran (ooh...@gmail.com) --- Hmm, it's pretty weird to see an NVMe drive using LSIs. Not too sure what to make of that. I figure there's something screwy going on with interrupt routing, but I don't have any g5

[Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 297191 --> https://bugzilla.kernel.org/attachment.cgi?id=297191=edit bisect.log Turns out the problem was introduced between v5.11 and v5.12 by following commit: #

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-06-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 213221] New: Lockdep self tests failing on e6500 system

2021-05-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213221 Bug ID: 213221 Summary: Lockdep self tests failing on e6500 system Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.12.6 Hardware: All OS: Linux

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-05-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 --- Comment #3 from Christophe Leroy (christophe.le...@csgroup.eu) --- Patch proposed by Anshuman, to be tested: https://lore.kernel.org/linuxppc-dev/bug-213069-206...@https.bugzilla.kernel.org%2F/T/#m82f2974b813c4d3a085b0cd2ac3d5b732a362e68 --

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

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

[Bug 206733] i2c i2c-3: i2c-powermac: modalias failure on /uni-n@f8000000/i2c@f8001000/cereal@1c0

2021-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206733 Paul Osmialowski (newch...@king.net.pl) changed: What|Removed |Added CC|

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 Christophe Leroy (christophe.le...@csgroup.eu) changed: What|Removed |Added CC|

[Bug 213079] IRQ problems and crashes on a PowerMac G5 with 5.12.3

2021-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Kernel Version|5.13-rc1|5.12.3

[Bug 213079] IRQ problems and crashes on a PowerMac G5 with 5.13-rc1

2021-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Hmm... Just also happened on 5.12.3. But without the Kernel panic (yet). [...] irq 63: nobody cared (try booting with the "irqpoll" option) Call Trace: CPU: 1 PID: 43491 Comm: emerge

[Bug 213079] IRQ problems and crashes on a PowerMac G5 with 5.13-rc1

2021-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 296761 --> https://bugzilla.kernel.org/attachment.cgi?id=296761=edit kernel .config (5.13-rc1, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 213079] New: IRQ problems and crashes on a PowerMac G5 with 5.13-rc1

2021-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213079 Bug ID: 213079 Summary: IRQ problems and crashes on a PowerMac G5 with 5.13-rc1 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.13-rc1 Hardware:

[Bug 213069] kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- The bug occurs with DEBUG_VM_PGTABLE=y. When DEBUG_VM_PGTABLE is not set the kernel boots fine. -- You may reply to this email to add a comment. You are receiving this mail because: You

[Bug 213069] New: kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1]

2021-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=213069 Bug ID: 213069 Summary: kernel BUG at arch/powerpc/include/asm/book3s/64/hash-4k.h:147! Oops: Exception in kernel mode, sig: 5 [#1] Product: Platform Specific/Hardware

[Bug 212631] Misaligned floating point loads and store occasionally fail

2021-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=212631 --- Comment #2 from Trevor Davenport (trevor_davenp...@selinc.com) --- A git bisect found this has existed for quite a while. git bisect start # bad: [0cc244011f40280b78fc344d5c2aac5a0c659f77] Linux 4.14.229 git bisect bad

[Bug 212631] Misaligned floating point loads and store occasionally fail

2021-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=212631 --- Comment #1 from Trevor Davenport (trevor_davenp...@selinc.com) --- I can also reproduce this with kernel version 5.11.12. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee

[Bug 212631] New: Misaligned floating point loads and store occasionally fail

2021-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=212631 Bug ID: 212631 Summary: Misaligned floating point loads and store occasionally fail Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 5.4.110 Hardware:

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

2021-03-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 --- Comment #8 from Michael Ellerman (mich...@ellerman.id.au) --- Actually I also reverted 4e302c3b568e ("misc: eeprom: at24: fix NVMEM name with custom AT24 device name"). -- You may reply to this email to add a comment. You are receiving

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

2021-03-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |ASSIGNED ---

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

2021-03-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

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

2021-03-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #294195|0 |1 is obsolete|

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

2021-03-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210749 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Attachment #294193|0 |1 is obsolete|

[Bug 206203] kmemleak reports various leaks in drivers/of/unittest.c

2021-03-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206203 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|NEW |RESOLVED

  1   2   3   4   5   6   7   >