[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #26 from doru iorgulescu (doru.iorgules...@gmail.com) --- Today the patch was applied on https://github.com/torvalds/linux Pull ata fix from Niklas Cassel: - Fix a regression for the PATA MacIO driver were it would fail to probe

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #25 from doru iorgulescu (doru.iorgules...@gmail.com) --- I finalized to compile linux kernel 6.10.0-rc2 uith the patch aplied and is OK! Thank You I have atached dmesg-6100-rc2.txt Thank You Very mutch Regards -- You may reply to

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #24 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306427 --> https://bugzilla.kernel.org/attachment.cgi?id=306427=edit dmesg6100-rc2.txt -- You may reply to this email to add a comment. You are

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #23 from doru iorgulescu (doru.iorgules...@gmail.com) --- I am in compilation When is finished I send to You the results Thank You Very Mutch Regards -- You may reply to this email to add a comment. You are receiving this mail

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #22 from Michael Ellerman (mich...@ellerman.id.au) --- Can you please confirm that the patch fixes the issue for you. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #21 from doru iorgulescu (doru.iorgules...@gmail.com) --- Thank You Very much Please send to Linus for aproval Thank You Regards -- You may reply to this email to add a comment. You are receiving this mail because: You are watching

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #20 from Michael Ellerman (mich...@ellerman.id.au) --- Please try the patch here: https://lore.kernel.org/linuxppc-dev/87wmn3pntq.fsf@mail.lhotse/ -- You may reply to this email to add a comment. You are receiving this mail

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #19 from doru iorgulescu (doru.iorgules...@gmail.com) --- Please a pach for this warning Thank You Regards -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #18 from doru iorgulescu (doru.iorgules...@gmail.com) --- The patch responsable [04/23] scsi: initialize scsi midlayer limits before allocating the queue

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-06-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #17 from doru iorgulescu (doru.iorgules...@gmail.com) --- This problem is currently discussed and handled on the lists: https://lore.kernel.org/all/ce2bf6af-4382-4fe1-b392-cc6829f5c...@roeck-us.net/ A Patch for this ? Tank You Regards

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #16 from doru iorgulescu (doru.iorgules...@gmail.com) --- I have upload hdparam-I.txt For the cdrom Is ok with linux kernel 6.9.3 Thank You, Regards -- You may reply to this email to add a comment. You are receiving this mail

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #15 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306389 --> https://bugzilla.kernel.org/attachment.cgi?id=306389=edit hdparam-I.txt -- You may reply to this email to add a comment. You are receiving

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #14 from doru iorgulescu (doru.iorgules...@gmail.com) --- Yes is ok with linux-kernel 6.9.3 I can disconect for a test linux kernel 6.10.0-rc1 Thank You Regards -- You may reply to this email to add a comment. You are receiving

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #13 from Michael Ellerman (mich...@ellerman.id.au) --- root@mirela:~# lspci -tv ... -[0001:00]-+-00.0 Apple Inc. CPC945 HT Bridge ... +-05.0-[03]--+-0d.0 Apple Inc. K2 ATA/100 sr0 ->

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #12 from doru iorgulescu (doru.iorgules...@gmail.com) --- I have upload config-next.txt For Linux Kernel Linux mirela 6.11.0-next-20240529 #2 SMP Fri May 31 09:17:14 EEST 2024 ppc64 GNU/Linux The problems are the same! Thank You

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #11 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306388 --> https://bugzilla.kernel.org/attachment.cgi?id=306388=edit config-next.txt -- You may reply to this email to add a comment. You are receiving

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #10 from doru iorgulescu (doru.iorgules...@gmail.com) --- I have upload dmesg-next.txt Linux mirela 6.11.0-next-20240529 #2 SMP Fri May 31 09:17:14 EEST 2024 ppc64 GNU/Linux The problems are the same! Thank You Regards -- You may

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #9 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306385 --> https://bugzilla.kernel.org/attachment.cgi?id=306385=edit dmesg-next.txt -- You may reply to this email to add a comment. You are receiving

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #8 from doru iorgulescu (doru.iorgules...@gmail.com) --- I run linux kernel 6.9.3 root@mirela:~# ls -l /sys/class/block total 0 lrwxrwxrwx 1 root root 0 May 30 10:55 loop0 -> ../../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #7 from Michael Ellerman (mich...@ellerman.id.au) --- Can you boot a working kernel and post the output of: # ls -l /sys/class/block # ls -l /sys/class/scsi_host # lspci -tv -- You may reply to this email to add a comment. You are

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #6 from doru iorgulescu (doru.iorgules...@gmail.com) --- I have upload config-6.10.0-rc1.txt I compile 6.10.0-rc1 starting from 6.9.3 Thank You Regards -- You may reply to this email to add a comment. You are receiving this mail

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #5 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306380 --> https://bugzilla.kernel.org/attachment.cgi?id=306380=edit config-6.10.0-rc1.txt -- You may reply to this email to add a comment. You are

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #4 from doru iorgulescu (doru.iorgules...@gmail.com) --- Created attachment 306379 --> https://bugzilla.kernel.org/attachment.cgi?id=306379=edit config-6.9.3.txt -- You may reply to this email to add a comment. You are receiving

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 --- Comment #3 from doru iorgulescu (doru.iorgules...@gmail.com) --- For Linux Kernel 6.9.3 root@mirela:/boot# grep PAGE_SIZE config-6.9.3 CONFIG_MMU_GATHER_PAGE_SIZE=y CONFIG_HAVE_PAGE_SIZE_64KB=y CONFIG_PAGE_SIZE_64KB=y

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Bug 218905] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218905 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

[Bug 218858] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured

2024-05-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=218858 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added CC|

[Bug 216723] BUG: spinlock wrong CPU on CPU#0, swapper/0/1 with CONFIG_NETCONSOLE=y (on a PowerMac G4 DP)

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

[Bug 216715] kernel 6.1-rc5 + KASAN_OUTLINE fails to boot at very early stage when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled (PowerMac G4 3,6)

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

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2024-04-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #17 from Erhard F. (erhar...@mailbox.org) --- Just noticed the issue is still there in v6.9-rc4. Does some side effects prevented the patch to get upstream or was it overlooked? ;) [..] Page orders: linear mapping = 12, virtual = 12,

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 --- Comment #10 from Christophe Leroy (christophe.le...@csgroup.eu) --- I built a kernel with your .config, the problem is a size problem. PPC32 kernels are not designed to be that big. Extract from generated System.map: c2394000 D _etext

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 --- Comment #9 from Erhard F. (erhar...@mailbox.org) --- Created attachment 305910 --> https://bugzilla.kernel.org/attachment.cgi?id=305910=edit kernel .config (6.8-rc6, KASAN_INLINE=y, PowerMac G4 DP) -- You may reply to this email to add a

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Status|CLOSED |REOPENED

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED --

[Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=207129 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

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

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=155231 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED --

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

2024-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=155231 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 216368] do_IRQ: stack overflow at boot during btrfs handling on a PowerMac G5 11,2

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

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

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

[Bug 215389] pagealloc: memory corruption with VMAP_STACK=y set and burdening the memory subsystem via "stress -c 2 --vm 2 --vm-bytes 896M"

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

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

2023-10-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #41 from Christophe Leroy (christophe.le...@csgroup.eu) --- I'm out of office until 06 Nov. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

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

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

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #16 from Erhard F. (erhar...@mailbox.org) --- Your newest patch fixes the issue. Thanks! -- 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 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #15 from Michael Ellerman (mich...@ellerman.id.au) --- Yeah, facepalm. Calling kmemleak_no_scan() later doesn't help, because it's the early allocation that is ignored, leading to the warning. So we can just drop the call to

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Thanks for having a look at the issue! Applied your patch on top of v6.5.6 but it didn't work out. Now I get: [...] drmem: No dynamic reconfiguration memory found ata5.00: ATAPI:

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #12 from Erhard F. (erhar...@mailbox.org) --- Created attachment 305198 --> https://bugzilla.kernel.org/attachment.cgi?id=305198=edit kernel .config (5.18, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- Created attachment 305197 --> https://bugzilla.kernel.org/attachment.cgi?id=305197=edit bisect.log -- You may reply to this email to add a comment. You are receiving this mail

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Summary|kmemleak: Not scanning |[bisected] kmemleak:

[Bug 216902] WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest

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

[Bug 216156] kmemleak: Not scanning unknown object at 0xc00000007f000000

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

[Bug 216156] kmemleak: Not scanning unknown object at 0xc00000007f000000

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

[Bug 215862] clang-15 fails ppc64 BE kernel build - ld.lld: error: undefined symbol: .early_setup

2023-07-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215862 --- Comment #6 from Christophe Leroy (christophe.le...@csgroup.eu) --- I'm out of office until August 1st. -- 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 215862] clang-15 fails ppc64 BE kernel build - ld.lld: error: undefined symbol: .early_setup

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

[Bug 217702] makedumpfile can not open /proc/vmcore

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

[Bug 217702] New: makedumpfile can not open /proc/vmcore

2023-07-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217702 Bug ID: 217702 Summary: makedumpfile can not open /proc/vmcore Product: Platform Specific/Hardware Version: 2.5 Hardware: All OS: Linux Status: NEW

[Bug 216715] kernel 6.1-rc5 + KASAN_OUTLINE fails to boot at very early stage when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled (PowerMac G4 3,6)

2023-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216715 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 304311 --> https://bugzilla.kernel.org/attachment.cgi?id=304311=edit kernel .config (6.4-rc3, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 216715] kernel 6.1-rc5 + KASAN_OUTLINE fails to boot at very early stage when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled (PowerMac G4 3,6)

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

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

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

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

2023-05-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215389 --- Comment #38 from Erhard F. (erhar...@mailbox.org) --- Created attachment 304309 --> https://bugzilla.kernel.org/attachment.cgi?id=304309=edit kernel .config (6.3.3, PowerMac G4 DP) -- You may reply to this email to add a comment. You are

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

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

[Bug 216715] kernel 6.1-rc5 + KASAN_OUTLINE fails to boot at very early stage when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled (PowerMac G4 3,6)

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

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

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

[Bug 217427] Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217427 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 217427] Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217427 --- Comment #3 from darkbasic (darkba...@linuxsystems.it) --- Gitlab issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2553 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the

[Bug 217427] Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217427 --- Comment #2 from Artem S. Tashkinov (a...@gmx.com) --- Please also report to https://gitlab.freedesktop.org/drm/amd/-/issues Performing git bisect would be nice: https://docs.kernel.org/admin-guide/bug-bisect.html -- You may reply to this

[Bug 217350] kdump kernel hangs in powerkvm guest

2023-05-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217350 --- Comment #2 from Cédric Le Goater (c...@kaod.org) --- Hello Pingfan, This was a large series. Did you identify the exact patch ? It should be related to the powerpc/pseries/pci or powerpc/xive subsystem. -- You may reply to this email to

[Bug 217427] Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217427 --- Comment #1 from darkbasic (darkba...@linuxsystems.it) --- Created attachment 304241 --> https://bugzilla.kernel.org/attachment.cgi?id=304241=edit journalctl_6.3.1.log -- You may reply to this email to add a comment. You are receiving

[Bug 217427] New: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217427 Bug ID: 217427 Summary: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0) Product: Platform Specific/Hardware

[Bug 217350] kdump kernel hangs in powerkvm guest

2023-05-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217350 Coiby (coiby...@gmail.com) changed: What|Removed |Added CC||c...@kaod.org,

[Bug 217390] use after free in spufs_switch_log_poll

2023-05-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217390 James Kim (james010...@gmail.com) changed: What|Removed |Added Severity|high|normal -- You may

[Bug 217390] New: use after free in spufs_switch_log_poll

2023-05-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217390 Bug ID: 217390 Summary: use after free in spufs_switch_log_poll Product: Platform Specific/Hardware Version: 2.5 Hardware: PPC-32 OS: Linux Status: NEW

[Bug 217350] New: kdump kernel hangs in powerkvm guest

2023-04-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217350 Bug ID: 217350 Summary: kdump kernel hangs in powerkvm guest Product: Platform Specific/Hardware Version: 2.5 Hardware: PPC-64 OS: Linux Status: NEW

[Bug 216041] Stack overflow at boot (do_IRQ: stack overflow: 1984) on a PowerMac G4 DP, KASAN debug build

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216041 --- Comment #10 from Christophe Leroy (christophe.le...@csgroup.eu) --- I'm away from the office until April 24th -- 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 216041] Stack overflow at boot (do_IRQ: stack overflow: 1984) on a PowerMac G4 DP, KASAN debug build

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216041 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED --

[Bug 216041] Stack overflow at boot (do_IRQ: stack overflow: 1984) on a PowerMac G4 DP, KASAN debug build

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216041 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

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

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215470 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED --

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

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215470 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-04-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

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

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #15 from Michal Suchánek (msucha...@suse.de) --- You do have two outputs defined in the device tree: /pci@f000/ATY,AlteracParent@10/ATY,Alterac_A@0 /pci@f000/ATY,AlteracParent@10/ATY,Alterac_B@1 If they correspond to a

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303601 --> https://bugzilla.kernel.org/attachment.cgi?id=303601=edit kernel .config (6.2-rc3, PowerMac G4 DP) -- You may reply to this email to add a comment. You

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

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

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #12 from Michal Suchánek (msucha...@suse.de) --- Thanks for the DT dumps. So you really do have two outputs but the problem is likely different: The hardware-specific driver gets initialized earlier, and then the offb/ofdrm driver

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303554 --> https://bugzilla.kernel.org/attachment.cgi?id=303554=edit device tree - PowerMac G5 11,2 Here's also the device tree of my G5, having the same issue. It

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #10 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303553 --> https://bugzilla.kernel.org/attachment.cgi?id=303553=edit device tree - PowerMac G4 3,6 DP (In reply to Michal Suchánek from comment #9) > Could you also

[Bug 216902] WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest

2023-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216902 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303552 --> https://bugzilla.kernel.org/attachment.cgi?id=303552=edit kernel .config (6.2-rc2, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 216902] New: WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest

2023-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216902 Bug ID: 216902 Summary: WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest Product: Platform Specific/Hardware Version: 2.5 Kernel Version:

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2023-01-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 Michal Suchánek (msucha...@suse.de) changed: What|Removed |Added CC||msucha...@suse.de

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

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

[Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'

2022-12-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216095 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303509 --> https://bugzilla.kernel.org/attachment.cgi?id=303509=edit dmesg (6.2-rc1, PowerMac G4 DP) Now as the new ofdrm driver is in 6.2-rc1 the G4 fails to pick it

[Bug 216368] do_IRQ: stack overflow at boot during btrfs handling on a PowerMac G5 11,2

2022-12-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216368 --- Comment #8 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303425 --> https://bugzilla.kernel.org/attachment.cgi?id=303425=edit kernel .config (6.1.0, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 216368] do_IRQ: stack overflow at boot during btrfs handling on a PowerMac G5 11,2

2022-12-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216368 --- Comment #7 from Erhard F. (erhar...@mailbox.org) --- Created attachment 303424 --> https://bugzilla.kernel.org/attachment.cgi?id=303424=edit dmesg (6.1.0, PowerMac G5 11,2) Still in v6.1.0. Happens sometimes at boot on my G5: [...] Stack

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

2022-12-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #11 from Christophe Leroy (christophe.le...@csgroup.eu) --- Le 12/12/2022 à 04:52, Nicholas Piggin a écrit : > On Sun Dec 11, 2022 at 11:19 PM AEST, wrote: >> https://bugzilla.kernel.org/show_bug.cgi?id=214913 >> >> --- Comment #7

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

2022-12-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #10 from npig...@gmail.com --- On Mon Dec 12, 2022 at 3:57 PM AEST, wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=214913 > > --- Comment #9 from Michael Ellerman (mich...@ellerman.id.au) --- > I assume it's an io_uring IO

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

2022-12-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #9 from Michael Ellerman (mich...@ellerman.id.au) --- I assume it's an io_uring IO worker. They're created via create_io_worker() -> create_io_thread(). They pass a non-NULL `args->fn` to copy_process() -> copy_thread(), so we end

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

2022-12-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #8 from npig...@gmail.com --- On Sun Dec 11, 2022 at 11:19 PM AEST, wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=214913 > > --- Comment #7 from Zorro Lang (zl...@redhat.com) --- > (In reply to Michael Ellerman from comment

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

2022-12-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214913 --- Comment #7 from Zorro Lang (zl...@redhat.com) --- (In reply to Michael Ellerman from comment #5) > Sorry I don't have any idea which commit could have fixed this. > > The process that crashed was "fsstress", do you know if it uses io_uring?

  1   2   3   4   5   6   7   8   9   10   >