March 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 19 Mar '21

19 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 https://bugzilla.suse.com/show_bug.cgi?id=1183716#c6 --- Comment #6 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- @dirk, could you also include CONFIG_KASAN_HW_TAGS=y in the debug config, please? -# CONFIG_KASAN is not set +CONFIG_KASAN=y +# CONFIG_KASAN_GENERIC is not set +CONFIG_KASAN_HW_TAGS=y +CONFIG_KASAN_STACK=1 +# CONFIG_TEST_KASAN_MODULE is not set -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183727] Shutdown hangs frequently in various places.
by bugzilla_noreply＠suse.com 19 Mar '21

19 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183727 https://bugzilla.suse.com/show_bug.cgi?id=1183727#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- This rather sounds like a user-space issue than the kernel. Does "/sbin/reboot -f" also show the problem? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182929] kernel fuse crash in heavy use with cvmfs
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182929 https://bugzilla.suse.com/show_bug.cgi?id=1182929#c24 Stefan Kluth <skluth(a)mpp.mpg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(skluth(a)mpp.mpg.de | |) | --- Comment #24 from Stefan Kluth <skluth(a)mpp.mpg.de> --- skluth@thserv04:~$ uname -a Linux thserv04 5.12.0-rc3-1.g8d911cd-default #1 SMP Thu Mar 18 12:08:15 UTC 2021 (8d911cd) x86_64 x86_64 x86_64 GNU/Linux The full build of the ATLAS software now ran to completion w/o problems. Looks like a fix for us. Thanks for the efforts of everybody! Does this fix have a chance of backporting to LTS kernel 5.4.x? Our application is opensuse tumbleweed, but others would be affected too if they use linux >= 5.4.x -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183739] New: Kernel update with a release minor number bump causes old kernel removal
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183739 Bug ID: 1183739 Summary: Kernel update with a release minor number bump causes old kernel removal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kerossin(a)pm.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a kernel update is released that only bumps up the last number of the release the older kernel is removed and the new one installed instead of just installing the new. >rpm -qi kernel-default-5.11.4 > >Version : 5.11.4 >Release : 1.3 <- this is the number I'm talking about Perhaps a real example will makes this clearer. Recently Tumbleweed was on kernel 5.11.4-1.2, snapshot 20210315 had an update - 5.11.4-1.3. Zypper handles this update by removing -1.2 first and then installing -1.3. With the current configuration of kernel packages it's not possible to install both of these packages side by side because they use the exact same file and directory names, the minor release number is omitted, e.g. /boot/initrd-5.11.4-1-default, /lib/modules/5.11.4-1-default/. What problems does this cause: Well a fundamental one would be that it doesn't follow the convention and what everyone expects - a kernel update shouldn't touch the previous kernel and should be installed separately. Another one and how we noticed this issue is that it can mess with out of tree kernel modules during updates. We specifically noticed this with Nvidia driver kernel modules and it depends on how lucky you are. For example when 'zypper dup' installs kernel-default before kernel-default-devel you're in luck, no problem happens. But if you get unlucky and zypper installs kernel-default-devel before kernel-default that's when the problem occurs. Nvidia kernel module installation is triggered by kernel-default-devel installation and those modules are put into /lib/modules/$kernelversion/updates/. The removal of those modules is triggered by removal of kernel-default. So here's what happens with the 20210315 unlucky example: 1) kernel-default-devel-5.11.4-1.3 is installed 2) Nvidia modules are installed at /lib/modules/5.11.4-1-default/updates/ 3) kernel-default-5.11.4-1.2 is removed 4) Nvidia modules are deleted from /lib/modules/5.11.4-1-default/updates/ 5) kernel-default-5.11.4-1.3 is installed now your new kernel is left without Nvidia drivers and it will boot to the terminal. If it would use file and directory names with the full release number (/lib/modules/5.11.4-1.2-default/, /lib/modules/5.11.4-1.3-default/) this wouldn't happen and also the removal of the kernel wouldn't be nescessary. The way I see it this potentially affects not only Nvidia drivers, if other kernel modules are managed in a similar fashion they could be affected. *Note: this same thing occured with snapshot 20210222 when kernel went from 5.10.16-1.2 to 5.10.16-1.3. Solutions: Is it possible to use the full release number in file and directory names so that these kernels would be installed alongside old kernels? Or perhaps an easier solution is to not increment the minor release number and just the major e.g. 5.11.4-1, 5.11.4-2, 5.11.4-3, etc. ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c10 --- Comment #10 from Peer FRANK <peer.frank(a)web.de> --- today I installed TW 20210316 with Kernel 5.11.6-1-default and the problem is gone. i915 with renderer Mesa DRI INtel HD Graphics 4400 on X11 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 https://bugzilla.suse.com/show_bug.cgi?id=1183716#c5 --- Comment #5 from Michal Kube��ek <mkubecek(a)suse.com> --- Please submit the new config also to master once arm64 configs are updated for 5.12 so that it doesn't get lost on next master->stable merge (when 5.12 final is released). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 https://bugzilla.suse.com/show_bug.cgi?id=1183716#c3 --- Comment #3 from Dirk Mueller <dmueller(a)suse.com> --- Lets give it a try for aarch64/debug on stable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182929] kernel fuse crash in heavy use with cvmfs
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182929 https://bugzilla.suse.com/show_bug.cgi?id=1182929#c23 --- Comment #23 from Luis Henriques <lhenriques(a)suse.com> --- (In reply to Luis Henriques from comment #22) > Created attachment 847415 [details] > mm/truncate: Make invalidate_inode_pages2_range work with THPs > > I've built another kernel with the attached patch. I forgot to mention that the patch was provided by Matthew Wilcox here: https://lore.kernel.org/linux-fsdevel/20210318115543.GM3420@casper.infradea… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182929] kernel fuse crash in heavy use with cvmfs
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182929 https://bugzilla.suse.com/show_bug.cgi?id=1182929#c22 Luis Henriques <lhenriques(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(skluth(a)mpp.mpg.de | |) --- Comment #22 from Luis Henriques <lhenriques(a)suse.com> --- Created attachment 847415 --> https://bugzilla.suse.com/attachment.cgi?id=847415&action=edit mm/truncate: Make invalidate_inode_pages2_range work with THPs I've built another kernel with the attached patch. It should (hopefully) fix this issue. This patch is added on top of the previous one, so the VM_BUG_ON_PAGE() is still there. Stefan, could you please give it a try? It's in OBS home:henrix:bsc1182929-fix-v01 (https://download.opensuse.org/repositories/home:/henrix:/bsc1182929-fix-v01…) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183671] New: All 5.11 kernels present mouse cursor as vertical dashed lines
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183671 Bug ID: 1183671 Summary: All 5.11 kernels present mouse cursor as vertical dashed lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: David.Boyd49(a)twc.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0 Build Identifier: After upgrading Tumbleweed from 5.10.16 to 5.11.2 or 5.11.4 or 5.11.6 kernel, the mouse cursor is presented as a series of dashed lines abound .75 inches tall on 24-inch monitor at 1440 x 900 resolution. Falling back to 5.10.16 kernel displays the mouse cursor as expected. With a little practice, it is possible to identify the part to this strange cursor that is actually the pointer. But users are unable to negotiate this. Reproducible: Always Steps to Reproduce: 1.Update system from 5.10.16 to 5.11.x kernel 2. 3. This problem is reproducible on production and test machines, so it is easy to try any type of change that might mitigate or help to identify this issue. I don't have a screen shot of this strange cursor, but I have been provided with a rough approxmation: ---- ---- ---- - -- - -- -- -- - - - - - - - - - - - - - - - - --- That is a terrible drawing, I know. Thanks for your patience and understanding. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 https://bugzilla.suse.com/show_bug.cgi?id=1183716#c2 --- Comment #2 from Michal Kube��ek <mkubecek(a)suse.com> --- Checked the history. We in fact never had an arm64/debug config. - arm64/default was added in 2013 (kernel-source commit b1aa50ee0ed2) - arm64/vanilla was added in 2014 (kernel-source commit cd0d0f39a416) - arm64/64kb was added in 2016 (kernel-source commit 9900bf5693ff) but noone ever created arm64/debug. As arm configs are maintained by arm team, I would leave the decision to them. While debug is a relatively small diff config, maintaining it should not be too complicated but kernel-debug packages are IIRC more resource hungry to build and I don't know if we are already out of the problem with arm builders in both IBS and OBS. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183132] Kernel wont boot after grub initialization 5.11.2
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183132 Joerg Roedel <jroedel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |jroedel(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183060] suse-prime-bbswitch package dependencies missing
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183060 https://bugzilla.suse.com/show_bug.cgi?id=1183060#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183716] No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183716 https://bugzilla.suse.com/show_bug.cgi?id=1183716#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |mkubecek(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- I don't remember why kernel-debug isn't built for arm, maybe just for saving the build power / time. I believe it's a bit too late for changing Leap 15.3, but we can certainly fix this for TW. It's a matter of editing config.conf. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183727] New: Shutdown hangs frequently in various places.
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183727 Bug ID: 1183727 Summary: Shutdown hangs frequently in various places. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jcarricksmith(a)gmail.com 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: When I shutdown my laptop (Novatech N1819 which is a re-badged Clevo PB71DF1-G) the process will hang > 50% of the time. Reproducible: Sometimes Steps to Reproduce: Execute a normal shutdown. opensuse 15.2 and KDE. Patched. Actual Results: The shutdown process hangs. If I press the <Esc> key the last message is usually:- <code>Stopped Name Service Cache Daemon</code> but has been:- <code>Stopped Authorisation Manager</code> (no time-out) or <code>A stop job is running for Modem Manager</code> (time-out of 90s keeps getting extended) or <code>shutdown.target reached</code> but the system does not power off. Sometimes pressing and holding <Ctrl><Alt><Del> will cause a forced reboot, otherwise it is necessary to press and hold the power button until the laptop switches off. It always (so far) has restarted OK. Even when it does shut down it pauses for 90s with the message:- <code>A stop job is running for /mnt/srv/xxxxxx</code> (where xxxxx is on of the NFS shares mounted). This times out after 90s and shutdown proceeds normally for the rest of the shutdown. Incidentally the mount units report in /var/lob/messages that they have failed with:- <Code>2021-03-17T15:26:56.120622+00:00 jlinn systemd[1]: mnt-srv-shared.mount: Mount process exited, code=exited status=32 2021-03-17T15:26:56.120788+00:00 jlinn systemd[1]: Failed to mount /mnt/srv/shared. 2021-03-17T15:26:56.120874+00:00 jlinn systemd[1]: Dependency failed for Remote File Systems. 2021-03-17T15:26:56.120952+00:00 jlinn systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'. 2021-03-17T15:26:56.121025+00:00 jlinn systemd[1]: mnt-srv-shared.mount: Unit entered failed state.</code> BUT when the desktop session starts the NFS shares ARE mounted. Expected Results: Normal shutdown. The OS is installed on an NVMe m.2 drive. It has an i7 octacore processor. 16GB RAM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183479] Graphic glitch and freeze at wake from sleep
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183479 http://bugzilla.opensuse.org/show_bug.cgi?id=1183479#c3 Pierre Bonamy <flyos(a)mailoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Pierre Bonamy <flyos(a)mailoo.org> --- The problem seems to be fixed using new kernel 5.11.6-1-default. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183716] New: No kernel-debug for aarch64
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183716 Bug ID: 1183716 Summary: No kernel-debug for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- Currently on Tumbleweed, there is no kernel-debug for aarch64 (same for armv7 and armv6). Could we add a kernel-debug flavor, at least for aarch64? This is the same for Leap/SLE. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181862] GCC 11: kernel-default package failures
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1181862 https://bugzilla.suse.com/show_bug.cgi?id=1181862#c23 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #23 from Martin Li��ka <martin.liska(a)suse.com> --- It's fixed now. Thanks guys for the help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183517] New: xslab: v-raptor: network bring-up fails
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183517 Bug ID: 1183517 Summary: xslab: v-raptor: network bring-up fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: yousaf.kaukab(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, ddavis(a)suse.com, mbrugger(a)suse.com Found By: --- Blocker: --- It is not possible to bring up network after the kernel has booted. Network works fine in firmware and PXE booting works. When using device-tree, Ethernet driver probe fails: [ 18.987362] netsec 522d0000.ethernet: Invalid size 0x1 for dma-range(s) [ 18.987658] netsec 522d0000.ethernet: hardware revision 5.65 [ 18.988226] libphy: SNI NETSEC MDIO: probed [ 19.033280] netsec 522d0000.ethernet eth0 (uninitialized): register_netdev() failed [ 19.266061] netsec 522d0000.ethernet: init failed [ 19.272200] netsec: probe of 522d0000.ethernet failed with error -12 When using ACPI, Ethernet driver is successfully probed however it's not possible to bring-up the network. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1183617] Module e1000e appears to be unsigned
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183617 https://bugzilla.suse.com/show_bug.cgi?id=1183617#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(millermj4(a)gmail.c | |om) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- So this doesn't look like a regression in the kernel side. Maybe it's the update of grub2, instead? You can downgrade the grub2 package from TW history repo, just for testing. http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183675] Getting into console (instead of GDM) when booting with the Leap 15.3 kernel
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183675 https://bugzilla.suse.com/show_bug.cgi?id=1183675#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxkamarada(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(linuxkamarada@gma | |il.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Hm, the suspicious line is: [ 5.942066] btrfs: autodefrag is not supported, load module with allow_unsupported=1 Could you try to boot with btrfs.allow_unsupported=1 boot option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183671] All 5.11 kernels present mouse cursor as vertical dashed lines
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183671 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |David.Boyd49(a)twc.com, | |tiwai(a)suse.com Flags| |needinfo?(David.Boyd49@twc. | |com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182929] kernel fuse crash in heavy use with cvmfs
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182929 https://bugzilla.suse.com/show_bug.cgi?id=1182929#c21 Stefan Kluth <skluth(a)mpp.mpg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(skluth(a)mpp.mpg.de | |) | --- Comment #21 from Stefan Kluth <skluth(a)mpp.mpg.de> --- 2021-03-15T21:05:43.484788+01:00 thserv04 kernel: [16247.536348] page:00000000dfe36ab1 refcount:673 mapcount:0 mapping:00000000f982a 7f8 index:0x1400 pfn:0x4c65e00 2021-03-15T21:05:43.484810+01:00 thserv04 kernel: [16247.536359] head:00000000dfe36ab1 order:9 compound_mapcount:0 compound_pincount :0 2021-03-15T21:05:43.484812+01:00 thserv04 kernel: [16247.536361] memcg:ffff8e730012b000 2021-03-15T21:05:43.484814+01:00 thserv04 kernel: [16247.536364] aops:fuse_file_aops [fuse] ino:8b8 dentry name:"cc1plus" 2021-03-15T21:05:43.484815+01:00 thserv04 kernel: [16247.536379] flags: 0xaffff800010037(locked|referenced|uptodate|lru|active|head) 2021-03-15T21:05:43.484820+01:00 thserv04 kernel: [16247.536385] raw: 00affff800010037 ffffd6519ed9c448 ffffd651abea5b08 ffff8eb2f9a 02ef8 2021-03-15T21:05:43.484823+01:00 thserv04 kernel: [16247.536388] raw: 0000000000001400 0000000000000000 000002a1ffffffff ffff8e73001 2b000 2021-03-15T21:05:43.484825+01:00 thserv04 kernel: [16247.536389] page dumped because: VM_BUG_ON_PAGE(page_mapped(page)) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183138] New: Reboot and Shutdown no longer function after update to latest kernel
by bugzilla_noreply＠suse.com 18 Mar '21

18 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183138 Bug ID: 1183138 Summary: Reboot and Shutdown no longer function after update to latest kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martijnklerks123(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846863 --> http://bugzilla.opensuse.org/attachment.cgi?id=846863&action=edit JournalCTL output. Steps to reproduce: 1. Update to the latest "Stable" version of the kernel. (I have done this manually before using the stable branch and now also on a fresh install through the regular DUP method, both gave the same result) 2. Reboot after updating completed. 3. Try to shut-down or reboot. Results: The result is that the machine appears to shut down as expected. Hitting escape shows everything is OK or DONE in green until "power off target" has been reached. After which the screen will turn off but the laptop remains on. This is indicated by the power button remaining lit and the fan still spinning. Expected result: The expected result is for the machine to actually power down after the OS has stopped/shutdown which it currently does not. The previous kernel 5.10 worked but the 5.11.2 kernel doesn't. Temporary workaround: It seems that the OS actually does shutdown so holding the powerbutton does not seem to cause data loss or corruption. HOWEVER! i have not been able to confirm this fully. Hardware: This was tested on a HP Envy x360. Kernel 5.11.2-1-default KDE Plasma 5.21.1 KWIN WM HP: Model13-ar0250nd (This laptop uses an AMD Mobile APU, and the bios uses S2IDLE which is a major aspect of kernel 5.11 since it added full support, atleast that's what was listed) It seems to me that the power target isn actually reached properly thus not shutting down the machine. However the logs don seem to confirm this. They do show alot of X11 issues and some KWIN issues. I have added the Journalctl logs of the day of updating and rebooting. The logs include the update, reboot and then 2 or 3 attempts at shutting down. This reveals alot of "Errors" and issues. -- You are receiving this mail because: You are the assignee for the bug.

1 3