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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #15 from Erhard F. (erhar...@mailbox.org) --- On Fri, 09 Aug 2019 12:31:26 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 # cat ~/bisect01.log binäre Suche: danach noch 37903

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

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

[Bug 204479] KASAN hit at modprobe zram

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

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 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #13 from Erhard F. (erhar...@mailbox.org) --- On Fri, 09 Aug 2019 12:31:26 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > [...] [ 22.809365]

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #12 from Erhard F. (erhar...@mailbox.org) --- On Fri, 09 Aug 2019 12:31:26 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > Tried a few LTS kernels on the G4 DP. Looks like

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #16 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284309 --> https://bugzilla.kernel.org/attachment.cgi?id=284309=edit dmesg (kernel 5.3-rc3 + debug patch + shadow patch + parallel patch, PowerMac G4 DP) Also tested

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #15 from Christophe Leroy (christophe.le...@c-s.fr) --- As far as I can see in the latest dmesg, the Oops occurs in raid6 pq module. An this time it is not anymore in kasan register global. -- You are receiving this mail because:

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284303 --> https://bugzilla.kernel.org/attachment.cgi?id=284303=edit dmesg (kernel 5.3-rc3 + patch + 2nd patch, without CONFIG_SMP, v2, PowerMac G4 DP) However the

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #13 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284301 --> https://bugzilla.kernel.org/attachment.cgi?id=284301=edit dmesg (kernel 5.3-rc3 + patch + 2nd patch, without CONFIG_SMP, PowerMac G4 DP) Definitely an

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #12 from Christophe Leroy (christophe.le...@c-s.fr) --- Patch at https://patchwork.ozlabs.org/patch/1144756/ -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #11 from Christophe Leroy (christophe.le...@c-s.fr) --- Thanks. Then it is not about SMP allthough there's anyway a theoritical problem with SMP that's I'll address in another patch. I think I finally spotted the issue. Let's take

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #11 from m...@ellerman.id.au --- bugzilla-dae...@bugzilla.kernel.org writes: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #10 from David Sterba (dste...@suse.com) --- > In my case it happened on 5.3-rc3, with a

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

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

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #10 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284297 --> https://bugzilla.kernel.org/attachment.cgi?id=284297=edit dmesg (kernel 5.3-rc3 + patch, without CONFIG_SMP, PowerMac G4 DP) Here's the dmesg with the

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #9 from Christophe Leroy (christophe.le...@c-s.fr) --- The module loads seems to be nested. It might then be an SMP issue, kasan_init_region() is most likely not SMP safe. Could you test without CONFIG_SMP or with only one CPU ? --

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #8 from Christophe Leroy (christophe.le...@c-s.fr) --- List of allocated areas with associated kasan shadow area in [ ], together with the addresses when shadow initialisation fails: Aug 08 23:39:58 T600 kernel: ##

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

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

[Bug 204479] KASAN hit at modprobe zram

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

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- (In reply to Christophe Leroy from comment #4) > We need to identify if the allocation of KASAN shadow area at module > allocation fails, or if kasan accesses outside of the allocated area.

[Bug 204479] KASAN hit at modprobe zram

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

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #4 from Christophe Leroy (christophe.le...@c-s.fr) --- We need to identify if the allocation of KASAN shadow area at module allocation fails, or if kasan accesses outside of the allocated area. Could you please run again with the

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #10 from David Sterba (dste...@suse.com) --- In my case it happened on 5.3-rc3, with a strestest. The same machine has been running fstests periodically, with slab debug on, but there are no slab reports like that. [ 8516.870046] BUG

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 David Sterba (dste...@suse.com) changed: What|Removed |Added CC||dste...@suse.com ---

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284243 --> https://bugzilla.kernel.org/attachment.cgi?id=284243=edit kernel .config (PowerMac G5 11,2, kernel 5.3-rc3) -- You are receiving this mail because: You are

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284241 --> https://bugzilla.kernel.org/attachment.cgi?id=284241=edit dmesg (PowerMac G5 11,2, kernel 5.3-rc3) -- You are receiving this mail because: You are on the

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #6 from Erhard F. (erhar...@mailbox.org) --- On Wed, 31 Jul 2019 12:09:54 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #4 from m...@ellerman.id.au --- >

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- Yes, at least one usb driver is also affected. Also radeon.ko sometimes loads ok, sometimes it stalls: # modprobe -v radeon insmod

[Bug 204479] KASAN hit at modprobe zram

https://bugzilla.kernel.org/show_bug.cgi?id=204479 Christophe Leroy (christophe.le...@c-s.fr) 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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- With radeon.ko module removed the G4 DP continues and finishes booting with KASAN. So this one seems fixed. Thanks! -- You are receiving this mail because: You are watching the assignee

[Bug 204479] KASAN hit at modprobe zram

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

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- On Wed, 31 Jul 2019 12:09:54 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204371 > > --- Comment #4 from m...@ellerman.id.au --- > > > I

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #13 from Erhard F. (erhar...@mailbox.org) --- Thanks for the hint! But adding KASAN_SANITIZE := n to lib/mpi/Makefile did not make a change in this case. However I had the idea to disable btrfs (at all) and boot from my other ext4

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #12 from Christophe Leroy (christophe.le...@c-s.fr) --- On my side under QEMU, deactivating KASAN on lib/mpi significantly reduces boot time. For that, just add the following on top of lib/mpi/Makefile: KASAN_SANITIZE := n -- You

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

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

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

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 204375] kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Hmm, nice.. I'll try to get the G4 booting further by prolonging HUNG_TASK_TIMEOUT and PANIC_TIMEOUT to 10min. Probably the btrfs guys also want to know about this btrfs deadlock. I try to

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #8 from Christophe Leroy (christophe.le...@c-s.fr) --- Created attachment 284061 --> https://bugzilla.kernel.org/attachment.cgi?id=284061=edit Screenshot2 Then it reverts to text mode and continue booting -- You are receiving

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #7 from Christophe Leroy (christophe.le...@c-s.fr) --- Created attachment 284059 --> https://bugzilla.kernel.org/attachment.cgi?id=284059=edit Screenshot1 When booting QEMU in graphic mode, it first hangs for some time here. --

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #6 from Christophe Leroy (christophe.le...@c-s.fr) --- >> = >> OpenBIOS 1.1 [Oct 19 2017 07:00] >> Configuration device id QEMU version 1 machine id 1 >> CPUs: 1 >> Memory:

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #5 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284057 --> https://bugzilla.kernel.org/attachment.cgi?id=284057=edit early boot picture (PowerMac G4 DP, kernel 5.2.5) Thanks! Your patch cleanly applied against

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #3 from Erhard F. (erhar...@mailbox.org) --- On Tue, 30 Jul 2019 11:52:44 -0700 Andrew Morton wrote: > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > > On Mon, 29 Jul 2019

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #4 from Christophe Leroy (christophe.le...@c-s.fr) --- Proposed fix at https://patchwork.ozlabs.org/patch/1139515/ -- You are receiving this mail because: You are watching the assignee of the bug.

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

https://bugzilla.kernel.org/show_bug.cgi?id=204375 --- Comment #3 from Christophe Leroy (christophe.le...@c-s.fr) --- Looks like that's due to 4a6d8cf90017 ("powerpc/mm: don't use pte_alloc_kernel() until slab is available on PPC32"), committed just before the KASAN series -- You are receiving

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

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

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

https://bugzilla.kernel.org/show_bug.cgi?id=204371 --- Comment #2 from Andrew Morton (a...@linux-foundation.org) --- (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Mon, 29 Jul 2019 22:35:48 + bugzilla-dae...@bugzilla.kernel.org wrote:

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

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

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

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 200055] 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 Attachment #280503|0 |1 is obsolete|

[Bug 200055] 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 Attachment #283679|0 |1 is obsolete|

[Bug 200055] 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 #19 from Erhard F. (erhar...@mailbox.org) --- Created attachment 284001 --> https://bugzilla.kernel.org/attachment.cgi?id=284001=edit bisect.log At last... I got the offending commit. Funnily enough it is about silencing lockdep

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

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

[Bug 200055] 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 Attachment #281901|0 |1 is obsolete|

[Bug 200055] 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 #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 200055] 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 #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

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 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

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 204125] FTBFS on ppc64 big endian and gcc9 because of -mcall-aixdesc and missing __linux__

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__

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__

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__

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__

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__

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__

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

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

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 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

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

[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

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

[Bug 203837] Booting kernel under KVM immediately freezes host

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 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

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 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

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

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

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 203837] Booting kernel under KVM immediately freezes host

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 155231] powerpc : native aslr vdso randomization is not working in powerpc platform

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

https://bugzilla.kernel.org/show_bug.cgi?id=203839 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

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 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

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] Booting kernel under KVM immediately freezes host

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

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

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] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument

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] 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

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] New: Booting kernel under KVM immediately freezes host

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 203515] [crypto] alg: skcipher: p8_aes_ctr encryption test failed (wrong result) on test vector 3, cfg="uneven misaligned splits, may sleep"

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.

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

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

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 203725] New: Build error: 'init_module' specifies less restrictive attribute than its target 'rtas_flash_init': 'cold'

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

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 203699] Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000

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 203699] New: Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000

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 203125] Kernel 5.1-rc1 fails to boot on a PowerMac G4 3,6: Caused by (from SRR1=141020): Transfer error ack signal

https://bugzilla.kernel.org/show_bug.cgi?id=203125 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.

https://bugzilla.kernel.org/show_bug.cgi?id=203517 David Sterba (dste...@suse.com) 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

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

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

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

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

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

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

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

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

<    4   5   6   7   8   9   10   >