[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282807 --> https://bugzilla.kernel.org/attachment.cgi?id=282807=edit kernel .config (5.1.3, Talos II) -- You are receiving this mail because: You are watching the

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

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

[Bug 203725] New: Build error: 'init_module' specifies less restrictive attribute than its target 'rtas_flash_init': 'cold'

2019-05-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203725 Bug ID: 203725 Summary: Build error: 'init_module' specifies less restrictive attribute than its target 'rtas_flash_init': 'cold' Product: Platform Specific/Hardware Version: 2.5

[Bug 203723] New: Build error: taking address of packed member of 'struct ftrace_graph_ent' may result in an unaligned pointer value

2019-05-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203723 Bug ID: 203723 Summary: Build error: taking address of packed member of 'struct ftrace_graph_ent' may result in an unaligned pointer value Product: Platform

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

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

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Has it already landed in 5.1 stable? Have not seen it yet. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283137 --> https://bugzilla.kernel.org/attachment.cgi?id=283137=edit failed boot, screenshot 5.2-rc1 -- You are receiving this mail because: You are watching the

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283139 --> https://bugzilla.kernel.org/attachment.cgi?id=283139=edit kernel .config (5.2-rc3, G4 MDD) -- You are receiving this mail because: You are watching the

[Bug 203839] New: Kernel 5.2-rc3 fails to boot on a PowerMac G4 3, 6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 Bug ID: 203839 Summary: Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument Product: Platform

[Bug 203837] Booting kernel under KVM immediately freezes host

2019-06-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203837 --- Comment #2 from Paul Mackerras (pau...@ozlabs.org) --- Just tried 5.1.7 in the host and got the guest locking up during boot. In xmon I see one cpu in pmdp_invalidate and another in handle_mm_fault. It seems very possible this is the bug that

[Bug 203837] Booting kernel under KVM immediately freezes host

2019-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203837 Paul Mackerras (pau...@ozlabs.org) changed: What|Removed |Added CC||pau...@ozlabs.org

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #3 from Christophe Leroy (christophe.le...@c-s.fr) --- Could you try and revert the following commits ? 38b4564cf042 powerpc/32: don't do syscall stuff in transfer_to_handler 1a4b739bbb4f powerpc/32: implement fast entry for syscalls

[Bug 203837] New: Booting kernel under KVM immediately freezes host

2019-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203837 Bug ID: 203837 Summary: Booting kernel under KVM immediately freezes host Product: Platform Specific/Hardware Version: 2.5 Kernel Version: v5.2-rc2 Hardware: PPC-64 OS:

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283163 --> https://bugzilla.kernel.org/attachment.cgi?id=283163=edit failed boot, screenshot 5.2-rc3+ After reverting the 3 commits on top of v5.2-rc3 the kernel

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-06-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #8 from Christophe Leroy (christophe.le...@c-s.fr) --- Argh ! CONFIG_SMP must (again) be the reason we missed it. Can you please try the change below ? diff --git a/arch/powerpc/kernel/head_32.S b/arch/powerpc/kernel/head_32.S

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

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

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283183 --> https://bugzilla.kernel.org/attachment.cgi?id=283183=edit bisect.log bisect took me a while due to quite some skips. Cherry-picking

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC|

[Bug 155231] powerpc : native aslr vdso randomization is not working in powerpc platform

2019-06-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=155231 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC|

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-06-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- (In reply to Christophe Leroy from comment #8) > Argh ! > > CONFIG_SMP must (again) be the reason we missed it. > > Can you please try the change below ? Applied your change on top of

[Bug 203837] Booting kernel under KVM immediately freezes host

2019-06-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203837 --- Comment #4 from Shawn Anastasio (sh...@anastas.io) --- I have applied Nick's patchset to 5.1.7 but the issue still occurs. As for using pdbg, I'm aware of the tool's existence but I'm not sure how I would effectively use it to diagnose this

[Bug 203837] Booting kernel under KVM immediately freezes host

2019-06-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203837 --- Comment #3 from npig...@gmail.com --- bugzilla-dae...@bugzilla.kernel.org's on June 7, 2019 4:29 pm: > https://bugzilla.kernel.org/show_bug.cgi?id=203837 > > --- Comment #2 from Paul Mackerras (pau...@ozlabs.org) --- > Just tried 5.1.7 in

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- I tried to apply the patch on top of 5.1.0 but it did not work out 'cause there is no arch/powerpc/mm/book3s32/hash_low.S. The correct file on my system seemed

[Bug 203571] may_use_simd() returns false in soft irq context

2019-05-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203571 --- Comment #1 from Shawn Landden (sland...@gmail.com) --- ▒ - 11.41% 0.01% kworker/1:2-mm_ [kernel.vmlinux][k] process_one_work

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #6 from Christophe Leroy (christophe.le...@c-s.fr) --- Try followin change: diff --git a/arch/powerpc/mm/book3s32/hash_low.S b/arch/powerpc/mm/book3s32/hash_low.S index e27792d0b744..8366c2abeafc 100644 ---

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- @Christophe: Oops, accidentally I trashed your last comment. Sorry! This patch didn't apply either. There is no book3s32 directory in my linux-stable tree, the hash_*.S files are directly

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC|

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #7 from Christophe Leroy (christophe.le...@c-s.fr) --- On 05/09/2019 10:05 AM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=203125 > > Christophe Leroy (christophe.le...@c-s.fr) changed: >

[Bug 203571] New: may_use_simd() returns false in kworkers

2019-05-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203571 Bug ID: 203571 Summary: may_use_simd() returns false in kworkers Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 4.19 Hardware: All OS: Linux

[Bug 203571] Allow use of SIMD in interrupts on PowerPC

2019-05-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203571 --- Comment #2 from Shawn Landden (sland...@gmail.com) --- X86 manages to allow SIMD in interrupts through some very careful code in arch/x86/kernel/fpu/core.c (starting with irq_fpu_usable()) PowerPC can do the same. -- You are receiving this

[Bug 203597] New: kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage

2019-05-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203597 Bug ID: 203597 Summary: kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 4.9.175

[Bug 203597] kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage

2019-05-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203597 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282745 --> https://bugzilla.kernel.org/attachment.cgi?id=282745=edit bisect.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 203597] kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage

2019-05-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203597 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC|

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

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

[Bug 203699] New: Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000

2019-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203699 Bug ID: 203699 Summary: Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: Kernel 5.2

[Bug 203699] Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000

2019-05-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203699 --- Comment #1 from Mathieu Malaterre (mathieu.malate...@gmail.com) --- Created attachment 282929 --> https://bugzilla.kernel.org/attachment.cgi?id=282929=edit Fix symptoms -- You are receiving this mail because: You are watching the assignee

[Bug 203597] kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage

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

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 --- Comment #2 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282835 --> https://bugzilla.kernel.org/attachment.cgi?id=282835=edit dmesg (4.19.44, G5 11,2) -- You are receiving this mail because: You are watching the assignee of

[Bug 203647] New: Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 Bug ID: 203647 Summary: Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x Product: Platform Specific/Hardware Version: 2.5 Kernel Version:

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282839 --> https://bugzilla.kernel.org/attachment.cgi?id=282839=edit dmesg (4.9.177, G5 11,2) -- You are receiving this mail because: You are watching the assignee of

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282841 --> https://bugzilla.kernel.org/attachment.cgi?id=282841=edit kernel .config (5.1.3, G5 11,2) -- You are receiving this mail because: You are watching the

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282833 --> https://bugzilla.kernel.org/attachment.cgi?id=282833=edit dmesg (5.0.17, G5 11,2) -- You are receiving this mail because: You are watching the assignee of

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282837 --> https://bugzilla.kernel.org/attachment.cgi?id=282837=edit dmesg (4.14.120, G5 11,2) -- You are receiving this mail because: You are watching the assignee

[Bug 203597] kernel 4.9.175 fails to boot on a PowerMac G4 3,6 at early stage

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203597 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #10 from Christophe Leroy (christophe.le...@c-s.fr) --- Thanks for testing. Proposed patch at https://patchwork.ozlabs.org/patch/1097492/ Note that the backport to stable should be straight forward as the directory and file name

[Bug 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

2019-05-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203125 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282679 --> https://bugzilla.kernel.org/attachment.cgi?id=282679=edit bisect.log Finally, the results of the bisect... f7354ccac844da7b1af8cc4f09da330fa3e960e4 is the

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 David Sterba (dste...@suse.com) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 203609] Build error: implicit declaration of function 'cpu_mitigations_off'

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

[Bug 203609] Build error: implicit declaration of function 'cpu_mitigations_off'

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

[Bug 203609] New: Build error: implicit declaration of function 'cpu_mitigations_off'

2019-05-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203609 Bug ID: 203609 Summary: Build error: implicit declaration of function 'cpu_mitigations_off' Product: Platform Specific/Hardware Version: 2.5 Kernel Version: 4.19.43 and 4.14.119

[Bug 203161] ppc64 started failing to build: error: 'MAX_PHYSMEM_BITS' undeclared

2019-05-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203161 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- (In reply to Eric Biggers from comment #5) > [...] That was almost a month ago though; I'm not sure whether anyone has > actually done anything yet. I'll send a reminder. Thanks!

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Kernel Version|5.1.0-rc7 |5.1.0-rc1 --- Comment

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282669 --> https://bugzilla.kernel.org/attachment.cgi?id=282669=edit bisect.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added CC|

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Some more info about the system: Talos II running Gentoo Linux ppc64, Big Endian. btrfs root filesystem (zstd compressed, standard compression level). swap: /sbin/zram-init -d0 -s32 -azstd

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 Eric Biggers (ebigge...@gmail.com) changed: What|Removed |Added CC||ebigge...@gmail.com

[Bug 203515] New: [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 Bug ID: 203515 Summary: [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep" Product:

[Bug 203517] New: WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 Bug ID: 203517 Summary: WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage. Product: Platform Specific/Hardware Version: 2.5 Kernel Version:

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282611 --> https://bugzilla.kernel.org/attachment.cgi?id=282611=edit kernel .config (5.1.0-rc7, Talos II) -- You are receiving this mail because: You are watching the

[Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.

2019-05-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203517 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282615 --> https://bugzilla.kernel.org/attachment.cgi?id=282615=edit kernel .config (5.1.0-rc7, Talos II -- You are receiving this mail because: You are watching the

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Kernel Version|5.1.0-rc7 |5.1.0-rc1 --- Comment

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282623 --> https://bugzilla.kernel.org/attachment.cgi?id=282623=edit bisect.log git-bisect found 4e7babba30d820c4195b1d58cf51dce3c22ecf2b as the 1st bad commit: # git

[Bug 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

2019-05-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203515 --- Comment #4 from Erhard F. (erhar...@mailbox.org) --- Created attachment 282625 --> https://bugzilla.kernel.org/attachment.cgi?id=282625=edit kernel .config of the final bisect (5.0.0-rc1+, Talos II) -- You are receiving this mail because:

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

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

[Bug 204125] New: FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 Bug ID: 204125 Summary: FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__ Product: Platform Specific/Hardware Version: 2.5 Kernel Version: any

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 Segher Boessenkool (seg...@kernel.crashing.org) changed: What|Removed |Added CC|

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #4 from Segher Boessenkool (seg...@kernel.crashing.org) --- I meant GNU userland. I don't know any project that officially support BE ELFv2. No BE ELFv2 Linux ABI is defined, either, as far as I know. It's great to hear that a lot

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #5 from Daniel Kolesa (li...@octaforge.org) --- I have an entire distro built with it. A small number of things require minor patches. Some of these have been upstreamed, some of these are pending (for example, to make OpenSSL

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #3 from Daniel Kolesa (li...@octaforge.org) --- Also, reported in gcc: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91135 Let's see what the compiler people have to say... -- You are receiving this mail because: You are watching

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #2 from Daniel Kolesa (li...@octaforge.org) --- ELFv2 works perfectly fine in BE userland, the musl libc *requires* ELFv2 on both endians and glibc works okay using either. ELFv2 was defined for both endians and there are distros that

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #6 from Daniel Kolesa (li...@octaforge.org) --- This appears to be the actual reason why the kernel fails to link without -mcall-aixdesc: specifically it's the -mcall-aixdesc that's problematic. but removing it breaks

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #7 from Daniel Kolesa (li...@octaforge.org) --- Btw, turns out an ELFv2 BE kernel requires little to no changes, these two commits produce a working kernel:

[Bug 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

2019-07-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204125 --- Comment #8 from Daniel Kolesa (li...@octaforge.org) --- Using this patch on my machines now: https://gist.github.com/q66/625cbec5d7317829a302773f89533b51 seems to work well -- You are receiving this mail because: You are watching the

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

2019-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=200055 --- Comment #16 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283677 --> https://bugzilla.kernel.org/attachment.cgi?id=283677=edit dmesg.txt (G5 11,2 + kernel 4.14.132) -- You are receiving this mail because: You are watching

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

2019-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=200055 --- Comment #15 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283675 --> https://bugzilla.kernel.org/attachment.cgi?id=283675=edit dmesg.txt (G5 11,2 + kernel 4.9.184) By running some older kernels from the stable series I

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

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

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

2019-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=200055 --- Comment #17 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283679 --> https://bugzilla.kernel.org/attachment.cgi?id=283679=edit 4.9.184 kernel .config (G5 11,2) -- You are receiving this mail because: You are watching the

[Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203839 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647 Anatoly Pugachev (mator...@gmail.com) changed: What|Removed |Added CC|

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC|

[Bug 204479] KASAN hit at modprobe zram

2019-08-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #18 from Christophe Leroy (christophe.le...@c-s.fr) --- The Oops occurs at 0x3c8: 3b0: 81 21 00 88 lwz r9,136(r1) 3b4: 13 67 dc c4 vxorv27,v7,v27 3b8: 7d 11 a8 ce lvx v8,r17,r21 3bc: 11 5f 5b 06

[Bug 204479] KASAN hit at modprobe zram

2019-08-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #17 from Christophe Leroy (christophe.le...@c-s.fr) --- Created attachment 284343 --> https://bugzilla.kernel.org/attachment.cgi?id=284343=edit Disassembly of lib/raid6/altivec8.o -- You are receiving this mail because: You are on

[Bug 204375] kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage

2019-07-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- I opened bug #204397 with your output. The G4 DP won't boot to a stage where I can get a dmesg, even if waiting for 10 minutes. -- You are receiving this mail because: You are watching

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-07-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #4 from m...@ellerman.id.au --- bugzilla-dae...@bugzilla.kernel.org writes: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #2 from Andrew Morton (a...@linux-foundation.org) --- > (switched to email. Please

[Bug 204375] kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage

2019-07-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #10 from Christophe Leroy (christophe.le...@c-s.fr) --- Yes feel free to take anything I have attached here. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added CC|

[Bug 204375] kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284039 --> https://bugzilla.kernel.org/attachment.cgi?id=284039=edit kernel .config (PowerMac G4 DP, kernel 5.2.4) With this .config the G4 DP boots fine. With this

[Bug 204375] New: kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204375 Bug ID: 204375 Summary: kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage Product: Platform Specific/Hardware Version: 2.5 Kernel Version:

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #33 from Erhard F. (erhar...@mailbox.org) --- On Fri, 16 Aug 2019 08:22:31 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #32 from Christophe Leroy

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #35 from Christophe Leroy (christophe.le...@c-s.fr) --- Le 16/08/2019 à 16:38, bugzilla-dae...@bugzilla.kernel.org a écrit : > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #34 from Erhard F.

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #34 from Erhard F. (erhar...@mailbox.org) --- On Fri, 16 Aug 2019 08:22:31 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #32 from Christophe Leroy

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #25 from Christophe Leroy (christophe.le...@c-s.fr) --- You can use get_zeroed_page(GFP_NOFS) instead of __get_free_page(GFP_NOFS | __GFP_ZERO) -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #36 from Erhard F. (erhar...@mailbox.org) --- On Fri, 16 Aug 2019 15:20:47 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #35 from Christophe Leroy

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #38 from Christophe Leroy (christophe.le...@c-s.fr) --- Le 30/07/2019 à 20:52, bugzilla-dae...@bugzilla.kernel.org a écrit : > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #2 from Andrew Morton

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #26 from Erhard F. (erhar...@mailbox.org) --- On Wed, 14 Aug 2019 20:33:51 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > >--- Comment #24 from Christophe Leroy

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #29 from Christophe Leroy (christophe.le...@c-s.fr) --- Looks good. Does it work better ? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

2019-08-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #30 from Erhard F. (erhar...@mailbox.org) --- On Thu, 15 Aug 2019 17:11:36 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #29 from Christophe Leroy

  1   2   3   4   5   6   >