June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 15 Jun '21

15 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c9 --- Comment #9 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- I can give you one additional business reason for fixing the bug: I know from the Development Ecosystem Team that Developers want to develop directly on the mainframe. Therefore, there is a goal to support several programming languages and frameworks. NodeJS is a JavaScript runtime environment required by multiple applications and event-driven servers. Therefore, supporting NodeJS is a business goal of IBM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187329] New: Kernel Panic loading initial ramdisk with kernel version 5.3.18-57.3 and pm80xx module
by bugzilla_noreply＠suse.com 15 Jun '21

15 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187329 Bug ID: 1187329 Summary: Kernel Panic loading initial ramdisk with kernel version 5.3.18-57.3 and pm80xx module Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dave(a)redmoor.org.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: After upgrading to Leap 15.3, the system fails to boot with a a kernel panic while processing the initial ramdisk. The error message reports that a fatal exception occurred while processing an interrupt in the pm80xx module. The system will boot if the option pci=nomsi is added to the command line but there is an error reported in the boot log saying that the interrupts could not be intialised and the disks on the PM8001 SAS controller are inaccessible. The following kernel command options have no effect acpi=off, pci=noacpi, acpi=noirq With module_blacklist=pm80xx, the system boot successfully to a rescue prompt as systemd times out waiting for the disks on the controller to become available The system boots successfully with kernel version 5.3.18-lp152.75 Output from an lspci -s 01:00.0 -vv command is included in additional information The motherboard is an ASUS P8H61-M-LE-USB3 The BIOS is updated to the latest version available. Reproducible: Always Steps to Reproduce: 1. boot with default menu option 2. 3. Actual Results: kernel panic when processing initial RAM disk Expected Results: boot to command line 01:00.0 Serial Attached SCSI controller: Adaptec PMC-Sierra PM8001 SAS HBA [Series 6H] (rev 05) Subsystem: Adaptec Device 0800 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f7960000 (64-bit, non-prefetchable) [size=64K] Region 2: Memory at f7950000 (64-bit, non-prefetchable) [size=64K] Region 4: Memory at f7940000 (32-bit, non-prefetchable) [size=64K] Region 5: Memory at f7900000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at f7800000 [disabled] [size=1M] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <1us, L1 <8us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [ac] MSI-X: Enable+ Count=16 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00004000 Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Kernel driver in use: pm80xx Kernel modules: pm80xx -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1185513] ACPI BIOS Error after upgrade to 5.12.0-1-default
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1185513 https://bugzilla.suse.com/show_bug.cgi?id=1185513#c66 --- Comment #66 from Frank Kr�ger <fkrueger(a)mailbox.org> --- The patch is part of kernel 5.13-rc6 (https://lore.kernel.org/linux-acpi/CAJZ5v0gyZhwcODnLhOfNc=Lxkr9kqt4UrsYsQUg…). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187252] Pluggable SATA disk not detected in newer kernels
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187252 http://bugzilla.opensuse.org/show_bug.cgi?id=1187252#c5 --- Comment #5 from Manfred Hollstein <manfred.h(a)gmx.net> --- Just found the culprit: somehow the "Hot Plug" bit for the SATA port connected to the tray box got disabled in the BIOS. Really don't know how this could have happened, but I guess it must have been during a BIOS update as the misbehaviour could be reproduced on two otherwise identical systems. Strange! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184403] New: iwlwifi driver failing to load in current MicroOS Desktop image
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1184403 Bug ID: 1184403 Summary: iwlwifi driver failing to load in current MicroOS Desktop image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin.rohde(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Right upon installation I get the following errors during boot and connection via WiFi and LAN cable fail: iwlwifi: not suitable firmware found iwlwifi: minimum version required: iwlwifi-6000g2a-5 iwlwifi: maximum version supported: iwlwifi-6000g2a-6 -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 1187132] New: Bad page map in process cc1 during building process of Midnight Commander (problem with mapping files into memory)
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187132 Bug ID: 1187132 Summary: Bad page map in process cc1 during building process of Midnight Commander (problem with mapping files into memory) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 850106 --> http://bugzilla.opensuse.org/attachment.cgi?id=850106&action=edit mc kernel bug log The Midnight Commander can not be built because of a kernel bug: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems… [ 71s] === configuring in src/vfs/smbfs/helpers (/home/abuild/rpmbuild/BUILD/mc-4.8.26/src/vfs/smbfs/helpers) [ 71s] configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr' '--host=s390x-suse-linux-gnu' '--build=s390x-suse-linux-gnu' '--program-prefix=' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--localstatedir=/var' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--disable-dependency-tracking' '--localstatedir=/var/lib' '--enable-charset' '--enable-vfs-smb' '--with-smb-configdir=/etc/samba' '--disable-vfs-fish' 'build_alias=s390x-suse-linux-gnu' 'host_alias=s390x-suse-linux-gnu' 'CFLAGS=-O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -W -Wall -Wstrict-prototypes -Wpointer-arith -Wformat-security -Wno-unused-parameter' 'LDFLAGS=-flto=auto' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig' --cache-file=/dev/null --srcdir=. [ 71s] checking for s390x-suse-linux-gnu-gcc... no [ 71s] checking for gcc... gcc [ 71s] checking whether the C compiler works... [ 63.161178] BUG: Bad page map in process cc1 pte:89790215 pmd:820df000 [ 71s] [ 63.161339] addr:0000000001d90000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d90 [ 71s] [ 63.161485] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.161631] BUG: Bad page map in process cc1 pte:89791215 pmd:820df000 [ 71s] [ 63.161715] addr:0000000001d91000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d91 [ 71s] [ 63.161810] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.161929] BUG: Bad page map in process cc1 pte:89792215 pmd:820df000 [ 71s] [ 63.162010] addr:0000000001d92000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d92 [ 71s] [ 63.162104] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.162220] BUG: Bad page map in process cc1 pte:89793215 pmd:820df000 [ 71s] [ 63.162301] addr:0000000001d93000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d93 [ 71s] [ 63.162397] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.162511] BUG: Bad page map in process cc1 pte:89794215 pmd:820df000 [ 71s] [ 63.162593] addr:0000000001d94000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d94 [ 71s] [ 63.162686] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.162801] BUG: Bad page map in process cc1 pte:89795215 pmd:820df000 [ 71s] [ 63.162883] addr:0000000001d95000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d95 [ 71s] [ 63.162976] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.163090] BUG: Bad page map in process cc1 pte:89796215 pmd:820df000 [ 71s] [ 63.163171] addr:0000000001d96000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d96 [ 71s] [ 63.163264] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.163380] BUG: Bad page map in process cc1 pte:89797215 pmd:820df000 [ 71s] [ 63.163462] addr:0000000001d97000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d97 [ 71s] [ 63.163554] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.163669] BUG: Bad page map in process cc1 pte:89798215 pmd:820df000 [ 71s] [ 63.163749] addr:0000000001d98000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d98 [ 71s] [ 63.163842] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.163958] BUG: Bad page map in process cc1 pte:89799215 pmd:820df000 [ 71s] [ 63.164039] addr:0000000001d99000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d99 [ 71s] [ 63.164133] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.164247] BUG: Bad page map in process cc1 pte:8979a215 pmd:820df000 [ 71s] [ 63.166507] addr:0000000001d9a000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9a [ 71s] [ 63.166658] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.166791] BUG: Bad page map in process cc1 pte:8979b215 pmd:820df000 [ 71s] [ 63.166885] addr:0000000001d9b000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9b [ 71s] [ 63.166979] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.167152] BUG: Bad page map in process cc1 pte:8979c215 pmd:820df000 [ 71s] [ 63.167301] addr:0000000001d9c000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9c [ 71s] [ 63.167418] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.167545] BUG: Bad page map in process cc1 pte:8979d215 pmd:820df000 [ 71s] [ 63.167631] addr:0000000001d9d000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9d [ 71s] [ 63.167724] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.167839] BUG: Bad page map in process cc1 pte:8979e215 pmd:820df000 [ 71s] [ 63.167923] addr:0000000001d9e000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9e [ 71s] [ 63.168016] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] [ 63.168133] BUG: Bad page map in process cc1 pte:8979f215 pmd:820df000 [ 71s] [ 63.168215] addr:0000000001d9f000 vm_flags:08000875 anon_vma:0000000000000000 mapping:0000000091ea42b8 index:d9f [ 71s] [ 63.168311] file:cc1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage [ 71s] no The whole log is attached. It seems that there is a problem with mapping files into memory. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1187264] [Build 20210611] [s390x] "Bad page state in process cc1plus pfn:fe401" during build of nodejs16
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1187264 https://bugzilla.suse.com/show_bug.cgi?id=1187264#c2 --- Comment #2 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-06-14 08:33 EDT------- We have a known (apparently) s390-specific issue in Tumbleweed with THP enabled, see LTC bug#190818 / SUSE bug#1180917. This bug report here does not show any s390-specific issues at first sight. Does this also show on other architectures? Is THP enabled on this system, and if yes, can you reproduce the problem also w/o THP? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186729] Hibernation stopped working after update 04 May 2020
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186729 https://bugzilla.suse.com/show_bug.cgi?id=1186729#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Last but not least, try the kernel in OBS Kernel:stable repo, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186729] Hibernation stopped working after update 04 May 2020
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186729 https://bugzilla.suse.com/show_bug.cgi?id=1186729#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rtsvetkov(a)suse.co | |m) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, then could you tell us exactly which old kernel kernel did work and which one started showing the breakage? And please give the dmesg outputs on both working and non-working cases (after trying hibernation). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186903] Reboot after zypper dup does not boot to desktop environment
by bugzilla_noreply＠suse.com 14 Jun '21

14 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186903 https://bugzilla.suse.com/show_bug.cgi?id=1186903#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |DUPLICATE --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Likely a dup of the recent UsrMerge fallout, breaking Nvidia driver installation. *** This bug has been marked as a duplicate of bug 1186710 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0