June 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[kernel-bugs] [Bug 1173294] New: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1173294 Bug ID: 1173294 Summary: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This looks similar to: https://bugzilla.kernel.org/show_bug.cgi?id=204643 I hit the following WARNING while playing with network manager's new activate hotspot UI functionality and then disabling all radio (nmcli radio wifi off): [ 1157.323257] wlan1: deauthenticating from 34:31:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) [ 1157.323301] ------------[ cut here ]------------ [ 1157.323302] TX on unused queue 5 [ 1157.323343] WARNING: CPU: 3 PID: 6784 at ../drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323344] Modules linked in: tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptablet [ 1157.323376] snd_hda_core dell_smm_hwmon fat kvm snd_hwdep dell_wmi dell_smbios irqbypass iwlwifi dcdbas joydev snd_pcm snd_timer sparse_keymap mei_me cfg80211 dell_wmi_d] [ 1157.323412] CPU: 3 PID: 6784 Comm: kworker/3:1 Not tainted 5.3.18-lp152.19-default #1 openSUSE Leap 15.2 (unreleased) [ 1157.323413] Hardware name: Dell Inc. Latitude E7450/0YGN55, BIOS A21 05/16/2019 [ 1157.323434] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 1157.323444] RIP: 0010:iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323447] Code: 80 3d 2b 65 03 00 00 b8 ea ff ff ff 0f 85 25 f8 ff ff 89 ce 48 c7 c7 49 6e d8 c0 89 04 24 c6 05 0d 65 03 00 01 e8 42 94 33 e1 <0f> 0b 8b 04 24 e9 03 f8 c [ 1157.323448] RSP: 0018:ffff9f66404bf7f0 EFLAGS: 00010282 [ 1157.323449] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000006 [ 1157.323450] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93915e399a10 [ 1157.323451] RBP: ffff939155e59e28 R08: 000000000000065e R09: 0000000000000001 [ 1157.323452] R10: 0000000000000005 R11: 0000000000000001 R12: ffff9390f1cc4b00 [ 1157.323453] R13: 0000000000000005 R14: 0000000000000037 R15: ffff9391566683e8 [ 1157.323454] FS: 0000000000000000(0000) GS:ffff93915e380000(0000) knlGS:0000000000000000 [ 1157.323455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1157.323456] CR2: 00007f8e2af0a000 CR3: 00000002ba00a005 CR4: 00000000003606e0 [ 1157.323457] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1157.323458] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1157.323459] Call Trace: [ 1157.323473] ? iwl_mvm_set_tx_cmd+0x1a2/0x480 [iwlmvm] [ 1157.323483] ? iwl_mvm_get_tx_rate.isra.21+0x44/0xe0 [iwlmvm] [ 1157.323491] ? iwl_mvm_get_tx_ant+0x43/0x80 [iwlmvm] [ 1157.323499] ? iwl_mvm_set_tx_params+0x11f/0x4e0 [iwlmvm] [ 1157.323507] iwl_mvm_tx_mpdu+0x207/0x600 [iwlmvm] [ 1157.323516] iwl_mvm_tx_skb_sta+0x1ed/0x480 [iwlmvm] [ 1157.323524] iwl_mvm_tx_skb+0x17/0x40 [iwlmvm] [ 1157.323532] iwl_mvm_mac_itxq_xmit+0x7a/0xf0 [iwlmvm] [ 1157.323559] ieee80211_queue_skb+0x2da/0x420 [mac80211] [ 1157.323582] ieee80211_tx+0xd9/0x130 [mac80211] [ 1157.323604] __ieee80211_tx_skb_tid_band+0x58/0x70 [mac80211] [ 1157.323627] ieee80211_send_deauth_disassoc+0xfd/0x130 [mac80211] [ 1157.323649] ieee80211_set_disassoc+0x3a0/0x5e0 [mac80211] [ 1157.323679] ieee80211_mgd_deauth+0x113/0x230 [mac80211] [ 1157.323701] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211] [ 1157.323720] cfg80211_mlme_down+0x7b/0x90 [cfg80211] [ 1157.323739] cfg80211_disconnect+0x11f/0x1d0 [cfg80211] [ 1157.323754] cfg80211_leave+0x26/0x40 [cfg80211] [ 1157.323767] cfg80211_netdev_notifier_call+0x258/0x5b0 [cfg80211] [ 1157.323774] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323794] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323800] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323817] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323831] ? ieee80211_iterate_active_interfaces_atomic+0xd/0x10 [mac80211] [ 1157.323838] ? iwl_mvm_recalc_multicast+0x45/0x70 [iwlmvm] [ 1157.323841] ? rtnl_is_locked+0x11/0x20 [ 1157.323843] ? inetdev_event+0x46/0x5c0 [ 1157.323850] ? iwl_mvm_configure_filter+0x61/0x80 [iwlmvm] [ 1157.323853] notifier_call_chain+0x47/0x70 [ 1157.323855] __dev_close_many+0x5f/0x110 [ 1157.323857] dev_close_many+0x7c/0x120 [ 1157.323859] dev_close.part.104+0x3e/0x70 [ 1157.323874] cfg80211_shutdown_all_interfaces+0x6d/0xc0 [cfg80211] [ 1157.323886] cfg80211_rfkill_sync_work+0x29/0x30 [cfg80211] [ 1157.323889] process_one_work+0x1f4/0x3e0 [ 1157.323892] worker_thread+0x2d/0x3e0 [ 1157.323894] ? process_one_work+0x3e0/0x3e0 [ 1157.323895] kthread+0x10d/0x130 [ 1157.323897] ? kthread_park+0xa0/0xa0 [ 1157.323899] ret_from_fork+0x35/0x40 [ 1157.323902] ---[ end trace 3217541a75ee82c3 ]--- I've not been able to reproduce it so far, but will update when/if I get a clear procedure. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[kernel-bugs] [Bug 1172541] New: Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 22 Oct '20

22 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172541 Bug ID: 1172541 Summary: Mysterious crashes with kernel 5.6.14 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jimc(a)jfcarter.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Version: kernel-default-5.6.14-1.1.x86_64 and aarch64 for Tumbleweed I did a dist-upgrade on 2020-06-02. After I waited for download.opensuse.org to recover from its illness, the upgrade went smoothly. But after I rebooted all the machines, 5 to 10 minutes later two of them went catatonic, and a third (my laptop) froze up a few minutes after being booted up two days later. After I power cycled the gateway machine, it again froze about five minutes after booting. On those hosts I reverted (by the grub menu) to kernel-default-5.6.12-1.3.x86_64 and aarch64. There were no further catatonic incidents. The other hosts continued (on 5.6.14) for up to 36 hours and did not go catatonic (but I eventually reverted them also). Here are the symptoms: On two machines I was working on the console (XFCE) when it happened. It seemed perfectly normal, but suddenly keystrokes had no effect and continuously updating apps (load meter etc.) ceased updating. On the gateway, network thru traffic was no longer forwarded. After I rebooted it I checked syslog (debug level). After the last normal message (e.g. DHCP lease renewed) there was a burst of \0's, and the dmesg dump appeared immediately after, starting with "microcode updated early to revision..." and "Jun 4 08:47:03 jacinth kernel: [ 0.000000] Linux version 5.6.12-1-default (geeko@buildhost) (gcc version 9.3.1 20200406 [revision 6db837a5288ee3ca5ec504fbd5a765817e556ac2] (SUSE Linux)) #1 SMP Tue May 12 17:44:12 UTC 2020 (9bff61b)", i.e. the very first expected messages from dmesg. (I carefully booted it into 5.6.12 not 5.6.14.) I have not been able to find any useful symptoms that might shed light on what is killing the machines. Machines running 5.6.12 did not crash, both before the dist-upgrade and after I reverted. For what it's worth, here is some data about the various machines. These went catatonic: jacinth Gateway, directory server, never sleeps. Intel NUC6CAYH, Celeron(R) CPU J3455 @ 1.50GHz, Intel HD Graphics 500 (i915). It runs hostapd as a wireless access point, driver 8812au from rtl8812au-kmp-default-5.6.4.2+git20200318.49e98ff_k5.6.12_1-1.7.x86_64 xena Laptop, wireless, powered off when the human is sleeping. Acer Aspire A515-54-51D1, Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz, Intel UHD Graphics 620 (Whiskey Lake) (i915) diamond Normal desktop. When it crashed nobody was using it. At night it hibernates. Intel NUC7i5BNH, Core(TM) i5-7260U CPU @ 2.20GHz, Intel Iris Plus Graphics 640 (i915) These survived up to 36 hours on 5.6.14 (called "non-catatonic" below): claude Webserver (1.5 hits/min). VM (KVM) on Jacinth, x86_64, video=cirrus holly Desktop replacement. Raspberry Pi-3B, Broadcom BCM2837 @1.2GHz and VideoCore IV (vc4). aarch64. RPi's can't sleep. iris Audio-video player (17kbyte/sec), hibernates when unused. Intel NUC6CAYH, Celeron(R) CPU J3455 @ 1.50GHz (like Jacinth), Intel HD Graphics 500 (i915) oso Development VM (KVM) on Diamond, x86_64, video=cirrus petra Development VM (KVM) on Xena, x86_64, video=cirrus surya Cloud server, VM (KVM) at Linode, never sleeps :-), Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, no GPU at all. Thinking that X-Windows activity might be correlated with catatonia, for about 6 hours I set the non-catatonic machines (except Surya, has no console) to show screensaver eye candy continuously. I was wrong; none of them crashed. Iris hardware is identical to Jacinth, yet it did not go catatonic while Jacinth failed more times than any other host. I don't really know what effective action could be taken, beyond trying to guess which kernel patch may have been the culprit. Anyway, thank you for whatever you can do with this info. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1173402] New: Kernel delays boot by 12s if ip= option given
by bugzilla_noreply＠suse.com 19 Aug '20

19 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173402 Bug ID: 1173402 Summary: Kernel delays boot by 12s if ip= option given 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dracut-maintainers(a)suse.de, iforster(a)suse.com Found By: --- Blocker: --- For networking in the initrd, the "ip=dhcp" (or similiar) option can be set in the kernel cmdline. This is parsed by dracut and used to configure wicked. However, this option is also parsed by the kernel in its ip autoconfig code, which then ends up trying to bring up the network itself. This bringup includes a 12s delay to wait for interfaces to appear: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net… At this point the initrd isn't even mounted, so there are no kernel modules available and no interfaces appear. @kernel maintainers: Is it maybe possible to not do autoconfig in this circumstance? It might be possible to check whether there are any network drivers at all (the default kernel seems to have those as modules only) or whether it's booting an initrd. Though in the latter case I guess it's possible that some initrd out there relies on the kernel's successful autoconfig? @dracut maintainers: It seems like "rd.neednet=1" is enough to get dracut to acquire an address over DHCP, so a workaround is to just drop "ip=dhcp". I'd like to have confirmation that this is intended behaviour and won't break without notice in the future. This doesn't help for cases without DHCP though. If it's not possible to avoid the "ip=foo" induced kernel delay, it might be a good idea to provide "rd.ip=foo" or similar as alias, which is ignored by the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1173158] New: CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 14 Aug '20

14 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173158 Bug ID: 1173158 Summary: CONFIG_MODULE_SIG=y Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: opensuse-releaseteam(a)suse.de Found By: --- Blocker: --- The 15.2 kernel has CONFIG_MODULE_SIG=y enabled. Correct me if I'm wrong but that means the NVidia driver won't work with secure boot enabled, right? Users would have to go to the BIOS and disable secure boot. A step that was not required in any openSUSE before, right? Do we really want that? If so, requires explicit documentation IMO. -- You are receiving this mail because: You are the assignee for the bug.

1 66

[kernel-bugs] [Bug 1173449] New: WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman.
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 Bug ID: 1173449 Summary: WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avaish92(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Not getting an option to turn wifi on in openSuse 15.2 Steps to reproduce : 1. Install opensuse leap 15.2. 2. add packman repo. 3. install broadcom-wl and reboot. lspci output : 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1) 07:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01) 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[kernel-bugs] [Bug 1173546] New: Provide some way to circumvent "Disabling f2fs" though it's unsupported
by bugzilla_noreply＠suse.com 30 Jun '20

30 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173546 Bug ID: 1173546 Summary: Provide some way to circumvent "Disabling f2fs" though it's unsupported Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bertocheraphael(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, bugs(a)tmarques.com, dleuenberger(a)suse.com, jeffm(a)suse.com, lnussel(a)suse.com, nborisov(a)suse.com, rbrown(a)suse.com Depends on: 1109665 Found By: --- Blocker: --- In the discussions about this as the thread linked below it was mentioned that enabling f2fs would be one line commentary away. But after removing the commentary I found out I have no kernel module able to mount f2fs. https://lists.opensuse.org/opensuse-kernel/2018-10/msg00001.html It's worth mentioning f2fs is currently actively used - especially on mobile platforms and other SoCs. Is it possible to provide a better way to mount an f2fs disk, even though you have dropped it's support, that doesn't involve recompiling the whole kernel every once in a while? -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1109665] Disabling f2fs
by bugzilla_noreply＠suse.com 30 Jun '20

30 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1109665 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c33 --- Comment #33 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1173085) was mentioned in https://build.opensuse.org/request/show/817782 15.2 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1165790] System hung - nouveau 0000:01:00.0: plasmashell[2512]: channel 7 killed!
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1165790 https://bugzilla.suse.com/show_bug.cgi?id=1165790#c10 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | --- Comment #10 from Miroslav Beneš <mbenes(a)suse.com> --- If the issue still happens with the latest kernel in Kernel:stable (that is 5.7.x), it is time to report it upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1107525] Raise default file descriptor limits to meet Valve Proton requirements
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1107525 https://bugzilla.suse.com/show_bug.cgi?id=1107525#c7 --- Comment #7 from Daniel Noga <noga.dany(a)gmail.com> --- I am not an expert, but according to Valve documentation and Phoronix blog site it looks like it can be changed both on kernel and on systemd. Systemd change can be maybe better, because it is only backport from upstream systemd 240 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1107525] Raise default file descriptor limits to meet Valve Proton requirements
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1107525 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1140573] Intel/Kabylake: External monitor stops working when coming back from screen save mode (with docking station)
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1140573 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1161843] Screen flickering on latest Dell XPS 7390 with kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1161843 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c32 --- Comment #32 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1173085) was mentioned in https://build.opensuse.org/request/show/817641 15.2 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173448] Webcam(earlier working) doesn't work now. Sony Vaio
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173448 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None Severity|Critical |Major -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173448] Webcam(earlier working) doesn't work now. Sony Vaio
by bugzilla_noreply＠suse.com 29 Jun '20

29 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173448 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |Kernel Assignee|gnome-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 28 Jun '20

28 Jun '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2 -> http://bugzilla.suse.com/show_bug.cgi?id=1166342 test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 Support for 64-bot processors on motherboards with 32-bit UEFI -> http://bugzilla.suse.com/show_bug.cgi?id=1172292 usb message shown on console even with "quiet splash=silent" -> http://bugzilla.suse.com/show_bug.cgi?id=1172322 kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode -> http://bugzilla.suse.com/show_bug.cgi?id=1172670 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

1 0

[kernel-bugs] [Bug 1173382] openat2: location of header file
by bugzilla_noreply＠suse.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173382 http://bugzilla.opensuse.org/show_bug.cgi?id=1173382#c1 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm(a)suse.com Assignee|kernel-bugs(a)opensuse.org |pgajdos(a)suse.com --- Comment #1 from Jeff Mahoney <jeffm(a)suse.com> --- I'm not sure how this is a kernel bug other than all system calls happening in the kernel. This is an issue in the man pages. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173382] openat2: location of header file
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173382 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173116] zypper dup from 15.1 doesn't boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173116 https://bugzilla.suse.com/show_bug.cgi?id=1173116#c8 --- Comment #8 from Ludwig Nussel <lnussel(a)suse.com> --- I grabbed ucode-intel-20200616-3.3.1.x86_64 from IBS. Seems to work fine, thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173071] Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173071 https://bugzilla.suse.com/show_bug.cgi?id=1173071#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- OK, then it's time to report to upstream. The upstream bug tracker is on gitlab.freedesktop.org https://gitlab.freedesktop.org/drm/intel Open an issue ticket there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173116] zypper dup from 15.1 doesn't boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173116 https://bugzilla.suse.com/show_bug.cgi?id=1173116#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Ludwig Nussel from comment #4) > CPU family: 6 > Model: 78 > Model name: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz > Stepping: 3 This is indeed the CPU model hitting a buggy firmware. Try to downgrade the ucode-intel to 20191115 of Leap 15.1 until the fixed (reverted) package is released for Leap 15.2 If you still see the same problem even after the ucode revert, please reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173116] zypper dup from 15.1 doesn't boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173116 https://bugzilla.suse.com/show_bug.cgi?id=1173116#c4 --- Comment #4 from Ludwig Nussel <lnussel(a)suse.com> --- # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 78 Model name: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz Stepping: 3 CPU MHz: 771.700 CPU max MHz: 3400.0000 CPU min MHz: 400.0000 BogoMIPS: 5599.85 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 4096K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173116] zypper dup from 15.1 doesn't boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173116 https://bugzilla.suse.com/show_bug.cgi?id=1173116#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Is your machine a Skylake CPU? It might be some side effect of the buggy Intel ucode. The update for certain CPU models brought such problems. The correction (revert of ucode updates for those CPUs) seem still on its way. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173116] zypper dup from 15.1 doesn't boot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173116 https://bugzilla.suse.com/show_bug.cgi?id=1173116#c2 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Upgrade Problems |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #2 from Lubos Kocman <lubos.kocman(a)suse.com> --- Any proposal for the assignee Ludwig? Seems like issue in between kernel/bootloader. Let's start with kernel since complete freeze is involved. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172475] Random screen flashing after suspend on KDE
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172475 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lubos.kocman(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lubos.kocman(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173138] Kernel 5.7.1 stuck at booting on HP Elitebook 840G6
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173138 https://bugzilla.suse.com/show_bug.cgi?id=1173138#c7 Huy Phung <huy.phung1292(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(huy.phung1292@gma | |il.com) | --- Comment #7 from Huy Phung <huy.phung1292(a)gmail.com> --- Fixed in Kernel 5.7.2 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c32 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1082905 --- Comment #32 from Jiri Slaby <jslaby(a)suse.com> --- FTR, the bug 1082905 was opened to turn MODULE_SIG in master+stable on. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c31 --- Comment #31 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Ludwig Nussel from comment #1) > (see bug 1173115) for another side effect It's not about signed modules, AFAICT -- mokutil loads to MOK a key the kernel is signed by. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 25 Jun '20

25 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c30 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #30 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Martin Wilck from comment #26) > sold. But that's just a single, once-in-a-system-lifetime MOK operation away. The upstream kernel does not verify module signatures against MOK keys. You need a non-upstream patch: patches.suse/KEYS-Make-use-of-platform-keyring-for-module-signatu.patch for that. Leap indeed inherits it from SLE, TW doesn't have it... So TW should keep MODULE_SIG as I don't want to lose the ability to check if modules are genuine. If you ask me, I would not set SIG_FORCE to allow loading of other modules (like nvidia, but there are many others, like those built by myself). Loading such a module properly taints the kernel which is good. For Leap, I have no opinion. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173138] Kernel 5.7.1 stuck at booting on HP Elitebook 840G6
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173138 https://bugzilla.suse.com/show_bug.cgi?id=1173138#c6 --- Comment #6 from Huy Phung <huy.phung1292(a)gmail.com> --- Hi, I forgot to comment back. The kernel 5.7.2 works perfectly. Kernel boots normally, Wifi and bluetooth works. I will close this bug. Thanks all. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173138] Kernel 5.7.1 stuck at booting on HP Elitebook 840G6
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173138 https://bugzilla.suse.com/show_bug.cgi?id=1173138#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huy.phung1292(a)gmail.com Flags| |needinfo?(huy.phung1292@gma | |il.com) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Any chance to test 5.7.2 and later? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c23 --- Comment #23 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Martin Wilck from comment #17) > It's indeed not easy. We could use a key stored in a standard location on > the user's system. However, at the very least the build procedure should > allow to enter the pass phrase for the key in a secure manner. Otherwise the > secret key would need to be stored unencrypted on the target system, which > would forfeit the use of secure boot, or a locked-down kernel, almost > entirely. Right now we are loading unsigned modules so there is not much of a difference to that. In the worst case if storing the private key really is a concern, a new one could be created for each rebuild of the ko and the private key deleted afterwards. Sure, that means enrolling the key on reboot then. If one really decides to play that secure boot game it's a matter of picking your poison basically :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c20 --- Comment #20 from Michal Kubeček <mkubecek(a)suse.com> --- (In reply to Martin Wilck from comment #19) > I didn't make myself clear. That "real KMP" I talked about would not trigger > the rebuild. It would rather rely on KABI, like real KMPs do. If the KABI > changes, the "real KMP" would need to be rebuilt. I'd hope that wouldn't > happen too often, at least not on Leap. We do not check kABI in Leap kernel branches like we do in SLE but as openSUSE-15.2 shares the codebase (same tarball and patches) with SLE15-SP2, the risk of breaking kABI in a way that would cause trouble is relatively low. It would have to be a kABI breakage that would only manifest in parts of the code which are built in openSUSE-15.2 but not SLE15-SP2. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173248] Kernel 5.7.2 - nvidia Installer hangs with high system load
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173248 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X11 3rd Party Driver Assignee|kernel-bugs(a)opensuse.org |gfx-bugs(a)suse.de QA Contact|qa-bugs(a)suse.de |sndirsch(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173239] command 'losetup -P' does not work in 15.2
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173239 https://bugzilla.suse.com/show_bug.cgi?id=1173239#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Assignee|kernel-bugs(a)opensuse.org |daniel.wagner(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- It looks like the commit was blacklisted. Daniel, could you check it again? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 24 Jun '20

24 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173115 http://bugzilla.opensuse.org/show_bug.cgi?id=1173115#c11 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com --- Comment #11 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Ludwig Nussel from comment #10) > > So similar checks could be done in the kernel spec file and skip mokutil > when built with the openSUSE keys. Or mokutil itself should have a list of keys that don't need to be added to the MoK db. We could have a list of fingerprints of built-in keys somewhere under /etc/uefi, and could check the cert to be imported against this list before importing. And if we don't, we should at least improve the message of the mokutil screen at boot, explaining why it's popping up. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173071] New: Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173071 Bug ID: 1173071 Summary: Kernel 5.7.1 does not boot 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: bdonauba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838888 --> http://bugzilla.opensuse.org/attachment.cgi?id=838888&action=edit last words of Kernel 5.7.1 With the last tumbleweed update came Kernel 5.7.1. Unfortunately it does not boot on my system. I attached a photo of the "last words" at boot because journalctl --boot=-1 gives me the log of the last successful boot. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[kernel-bugs] [Bug 1173085] New: Realtek RTL8117 NIC not recognized by Leap 15.2 RC
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173085 Bug ID: 1173085 Summary: Realtek RTL8117 NIC not recognized by Leap 15.2 RC Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838907 --> http://bugzilla.opensuse.org/attachment.cgi?id=838907&action=edit Hardware info On my motherboard (Asus Pro WS X570-ACE) there are two NICs present: * Realtek RTL8117 * Intel I211-AT Gigabit LAN Leap 15.1 recognizes both, but on a fresh install of Leap 15.2 RC only the Intel NIC is recognized. That is, the command "ip a" lists only one Ethernet adapter on 15.2 RC, whereas it lists two on 15.1. In dmesg I find the following error which I think is relevant: [ 6.650810] r8169 0000:06:00.1: unknown chip XID 54a Please add support for the Realtek RTL8117 NIC in the 15.2 kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c11 --- Comment #11 from S. B. <sb56637(a)gmail.com> --- Created attachment 839044 --> https://bugzilla.suse.com/attachment.cgi?id=839044&action=edit openSUSE TW with Mate desktop and Clear kernel, long Zoom meeting -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c10 --- Comment #10 from S. B. <sb56637(a)gmail.com> --- Created attachment 839043 --> https://bugzilla.suse.com/attachment.cgi?id=839043&action=edit openSUSE TW with Mate desktop and stock kernel, long Zoom meeting -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c9 --- Comment #9 from S. B. <sb56637(a)gmail.com> --- So, a few updates: I did a fresh install of Tumbleweed, now using the Mate desktop. Needed something more lightweight on this machine, and that alone has helped a lot with the thermal problems and excess CPU load. Then I had an ~2 hour Zoom meeting with ~25 participants using the stock openSUSE 5.7.1 kernel, and then I had another similar Zoom meeting with the Clear kernel. There are indeed major differences in CPU load, although they don't seem to translate directly to a cooler system. However, I wonder if it's because Clear has set different temp thresholds for the fan speeds, because the fan seems to generally spin slower with the Clear kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173248] New: Kernel 5.7.2 - nvidia Installer hangs with high system load
by bugzilla_noreply＠suse.com 23 Jun '20

23 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173248 Bug ID: 1173248 Summary: Kernel 5.7.2 - nvidia Installer hangs with high system load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 839025 --> http://bugzilla.opensuse.org/attachment.cgi?id=839025&action=edit Installation log Installation of current TW image causes issue if Nvidia-driver is installed: At installation of nvidia-glG05-440.82-30.1.x86_64 , system hangs under high system load. Previous compilation of driver fails, see attachment -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1173239] New: command 'losetup -P' does not work in 15.2
by bugzilla_noreply＠suse.com 22 Jun '20

22 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173239 Bug ID: 1173239 Summary: command 'losetup -P' does not work in 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a usb disk image on file with several partitions on it. Normally I would run: losetup -P -f --show usb.img and such command would attach the file usb.img to a loop device (/dev/loop0) and it would create also the devices /dev/loop0p1, /dev/loop0p<n> for each partition in the image file. Such command works in 15.1 but fails in 15.2. dmesg shows: loop_reread_partitions: partition scan of loop0 (usb.img) failed (rc=-16) Instead with the latest kernelstable installed losetup -P works as expected. I have found this 5.6.11 commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=… I have applied such modification to the kernel 5.3.18-lp152.19 of 15.2 and I can confirm that such commit fixes the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172997] New: kernel panic about "SError Interrupt on CPU…" on aarch64, 4.12.14-lp151.28.48-default
by bugzilla_noreply＠suse.com 22 Jun '20

22 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172997 Bug ID: 1172997 Summary: kernel panic about "SError Interrupt on CPU…" on aarch64, 4.12.14-lp151.28.48-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, mbrugger(a)suse.com, ptesarik(a)suse.com, tiwai(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1162612 +++ ## Observation The SUSE internal machine "openqaworker-arm-3" is an aarch64 Machine model: Cavium ThunderX CN88XX running openSUSE Leap 15.1 with kernel 4.12.14-lp151.28.48-default showed multiple times system crashes with kernel panic and error reports about "SError Interrupt on CPU…", e.g. like: ``` Apr 28 15:17:30 [256898.042772] SError Interrupt on CPU81, code 0xbe000000 -- SError Apr 28 15:17:30 [256898.042775] CPU: 81 PID: 24143 Comm: worker Tainted: G W 4.12.14-lp151.28.44-default #1 openSUSE Leap 15.1 Apr 28 15:17:30 [256898.042777] Hardware name: GIGABYTE R270-T64-00/MT60-SC4-00, BIOS T32 03/03/2017 Apr 28 15:17:30 [256898.042778] task: ffff810cc501c080 task.stack: ffff810cc829c000 Apr 28 15:17:30 [256898.042779] pstate: 60000005 (nZCv daif -PAN -UAO) Apr 28 15:17:30 [256898.042780] pc : ptep_set_access_flags+0xc0/0x100 Apr 28 15:17:30 [256898.042781] lr : 0xe0010bbfeb9bd3 Apr 28 15:17:30 [256898.042782] sp : ffff810cc829fca0 Apr 28 15:17:30 [256898.042784] x29: ffff810cc829fca0 x28: ffff810cc501c080 Apr 28 15:17:30 [256898.042787] x27: ffff810cc2443468 x26: 0000000000000007 Apr 28 15:17:30 [256898.042789] x25: ffff810f6f63d0c8 x24: 0000000000000054 Apr 28 15:17:30 [256898.042792] x23: ffff810cc2443400 x22: ffff810f6f63d0c8 Apr 28 15:17:30 [256898.042794] x21: 62c6000aaab37e3b x20: 00e0010bbfeb9fd3 Apr 28 15:17:30 [256898.042796] x19: ffff810cce57b1d8 x18: 0000000000000000 Apr 28 15:17:30 [256898.042799] x17: 0000ffffa9823238 x16: 0000aaaaeabfd350 Apr 28 15:17:30 [256898.042801] x15: 000040c4034d32e5 x14: 0000000000000000 Apr 28 15:17:30 [256898.042803] x13: 8080c08013012026 x12: 0000000000000000 Apr 28 15:17:30 [256898.042806] x11: 0000000000000040 x10: 000000000000000e Apr 28 15:17:30 [256898.042808] x9 : 000000000000ff00 x8 : 0000ffffa937bac8 Apr 28 15:17:30 [256898.042810] x7 : 0000aaab1bb72d48 x6 : 0000000000000024 Apr 28 15:17:30 [256898.042813] x5 : 00e0010bbfeb9b53 x4 : 00e0010bbfeb9b53 Apr 28 15:17:30 [256898.042815] x3 : 0080000000000400 x2 : 00e0010bbfeb9fd3 Apr 28 15:17:30 [256898.042817] x1 : 00e0010bbfeb9bd3 x0 : 00000000001262c6 Apr 28 15:17:30 [256898.042820] Kernel panic - not syncing: Asynchronous SError Interrupt Apr 28 15:17:30 [256898.042822] CPU: 81 PID: 24143 Comm: worker Tainted: G W 4.12.14-lp151.28.44-default #1 openSUSE Leap 15.1 Apr 28 15:17:30 [256898.042823] Hardware name: GIGABYTE R270-T64-00/MT60-SC4-00, BIOS T32 03/03/2017 Apr 28 15:17:30 [256898.042824] Call trace: Apr 28 15:17:30 [256898.042825] dump_backtrace+0x0/0x188 Apr 28 15:17:30 [256898.042826] show_stack+0x24/0x30 Apr 28 15:17:30 [256898.042827] dump_stack+0x90/0xb0 Apr 28 15:17:30 [256898.042828] panic+0x114/0x28c Apr 28 15:17:30 [256898.042828] nmi_panic+0x7c/0x80 Apr 28 15:17:30 [256898.042829] arm64_serror_panic+0x80/0x90 Apr 28 15:17:30 [256898.042830] __pte_error+0x0/0x50 Apr 28 15:17:30 [256898.042831] el1_error+0x7c/0xdc Apr 28 15:17:30 [256898.042832] ptep_set_access_flags+0xc0/0x100 Apr 28 15:17:30 [256898.042833] __handle_mm_fault+0x204/0x500 Apr 28 15:17:30 [256898.042834] handle_mm_fault+0xd4/0x178 Apr 28 15:17:30 [256898.042835] do_page_fault+0x1a0/0x448 Apr 28 15:17:30 [256898.042836] do_mem_abort+0x54/0xb0 Apr 28 15:17:30 [256898.042837] el0_da+0x24/0x28 Apr 28 15:17:30 [256899.126203] SError Interrupt on CPU6, code 0xbe000000 -- SError Apr 28 15:17:30 [256899.126205] CPU: 6 PID: 19627 Comm: /usr/bin/isotov Tainted: G W 4.12.14-lp151.28.44-default #1 openSUSE Leap 15.1 Apr 28 15:17:30 [256899.126207] Hardware name: GIGABYTE R270-T64-00/MT60-SC4-00, BIOS T32 03/03/2017 Apr 28 15:17:30 [256899.126208] task: ffff810cbfc24080 task.stack: ffff810cc9564000 Apr 28 15:17:30 [256899.126209] pstate: 60000005 (nZCv daif -PAN -UAO) Apr 28 15:17:30 [256899.126210] pc : ptep_clear_flush+0x88/0xd8 Apr 28 15:17:30 [256899.126211] lr : wp_page_copy+0x298/0x6c0 Apr 28 15:17:30 [256899.126212] sp : ffff810cc9567be0 Apr 28 15:17:30 [256899.126213] x29: ffff810cc9567be0 x28: 0000aaaafc866000 Apr 28 15:17:30 [256899.126216] x27: ffff810cb93f8330 x26: ffff810cc1142c00 Apr 28 15:17:30 [256899.126218] x25: 0000aaaafc866000 x24: ffff810cc1142c00 Apr 28 15:17:30 [256899.126220] x23: 00e801048f9ccf53 x22: ffff810f56d2a708 Apr 28 15:17:30 [256899.126223] x21: ffff810f56d2a708 x20: 0000000aaaafc866 Apr 28 15:17:30 [256899.126225] x19: ffff810cb93f8330 x18: 0000000000000000 Apr 28 15:17:30 [256899.126228] x17: 0000aaaafc85f420 x16: 0000aaaafc8693c0 Apr 28 15:17:30 [256899.126230] x15: 4000000b00000001 x14: 0000aaaafc863880 Apr 28 15:17:30 [256899.126232] x13: 0000000000000032 x12: 0000110100000001 Apr 28 15:17:30 [256899.126235] x11: 0000aaaafc866fb8 x10: 0000aaaafc867fd0 Apr 28 15:17:30 [256899.126237] x9 : 1000440300000001 x8 : 0000aaaafc85f440 Apr 28 15:17:30 [256899.126239] x7 : 0000000000000029 x6 : 0000110100000001 Apr 28 15:17:30 [256899.126242] x5 : 0088000000000000 x4 : 00e0000e8ed2ff53 Apr 28 15:17:30 [256899.126244] x3 : 00e001048f9ccfd3 x2 : 0000000000000000 Apr 28 15:17:30 [256899.126247] x1 : 3804000aaaafc866 x0 : 00e0000e8ed2ffd3 Apr 28 15:17:30 [256899.126271] SMP: stopping secondary CPUs Apr 28 15:17:30 [256899.126272] SMP: failed to stop secondary CPUs 1,6,48,81,84-85 Apr 28 15:17:30 [256899.126273] Kernel Offset: disabled Apr 28 15:17:30 [256899.126274] CPU features: 0x01,04101128 Apr 28 15:17:30 [256899.126275] Memory Limit: none Apr 28 15:17:30 [256899.126277] SError Interrupt on CPU85, code 0xbe000000 -- SError Apr 28 15:17:30 [256899.126279] CPU: 85 PID: 23855 Comm: worker Tainted: G W 4.12.14-lp151.28.44-default #1 openSUSE Leap 15.1 Apr 28 15:17:30 [256899.126280] Hardware name: GIGABYTE R270-T64-00/MT60-SC4-00, BIOS T32 03/03/2017 Apr 28 15:17:30 [256899.126281] task: ffff810cc9f0a180 task.stack: ffff810cc99b4000 Apr 28 15:17:30 [256899.126282] pstate: 60000005 (nZCv daif -PAN -UAO) Apr 28 15:17:30 [256899.126283] pc : ptep_set_access_flags+0xc0/0x100 Apr 28 15:17:30 [256899.126284] lr : 0xe0000a0c000fd1 Apr 28 15:17:30 [256899.126285] sp : ffff810cc99b7c30 Apr 28 15:17:30 [256899.126286] x29: ffff810cc99b7c30 x28: ffff810cc9f0a180 Apr 28 15:17:30 [256899.126288] x27: ffff000008d32000 x26: 0000000000000008 Apr 28 15:17:30 [256899.126291] x25: ffff7e0000000000 x24: ffff810f6b56ced8 Apr 28 15:17:30 [256899.126293] x23: ffff00000933a000 x22: ffff810f6b56ced8 Apr 28 15:17:30 [256899.126295] x21: 5f3e000aaab2f400 x20: 00e8000a0c000f51 Apr 28 15:17:30 [256899.126298] x19: ffff810cdab62bd0 x18: 0000000000000000 Apr 28 15:17:30 [256899.126300] x17: 0000ffffafddac80 x16: 0000aaaae4c21020 Apr 28 15:17:30 [256899.126302] x15: 000089a652d558cc x14: 0000000000000000 Apr 28 15:17:30 [256899.126305] x13: 0d4b4f2030303220 x12: 312e312f50545448 Apr 28 15:17:30 [256899.126307] x11: 0000aaab233d1eb0 x10: 00000000c6cf1b21 Apr 28 15:17:30 [256899.126309] x9 : 0000000000000009 x8 : 0000aaab24a44d00 Apr 28 15:17:31 [256899.126311] x7 : 41203832202c6575 x6 : 54203a657461440a Apr 28 15:17:31 [256899.126314] x5 : 0000000000100073 x4 : 00e0000a0c000f51 Apr 28 15:17:31 [256899.126316] x3 : 0088000000000480 x2 : 00e8000a0c000f51 Apr 28 15:17:31 [256899.126318] x1 : 00e0000a0c000fd1 x0 : 0000000000125f3e Apr 28 15:17:31 [256899.725248] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt Apr 28 16:18:35 � ``` ## Reproducible Happened multiple times but sporadic, every couple of days or weeks. On two other, very similar machines running 5.6.0 there are also random crashes but the same error report was never seen. ## Further details Internal issue: https://progress.opensuse.org/issues/41882 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1173186] Intel Centrino 6205 iwlwifi crashed during heavy load k5.7.1
by bugzilla_noreply＠suse.com 22 Jun '20

22 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173186 https://bugzilla.suse.com/show_bug.cgi?id=1173186#c6 S. B. <sb56637(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from S. B. <sb56637(a)gmail.com> --- Thanks Takashi. I doubt it's reproducible consistently, so I'll just wait for the standard Tumbleweed kernel updates. I'll close this bug for now, and I'll re-open it if the same bug hits again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173186] Intel Centrino 6205 iwlwifi crashed during heavy load k5.7.1
by bugzilla_noreply＠suse.com 22 Jun '20

22 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173186 https://bugzilla.suse.com/show_bug.cgi?id=1173186#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(sb56637(a)gmail.com | |) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- The bug in 5.7.1 was rather crashing at boot, so it's possibly a different issue. In anyway, try a later version of 5.7.x kernel in OBS Kernel:stable repo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173115 http://bugzilla.opensuse.org/show_bug.cgi?id=1173115#c10 --- Comment #10 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Michal Suchanek from comment #9) > Does that work for kernels built in random home project? Those are signed with a key different from the one signed by the openSUSE Secure boot CA. So for those of course one has to import the sign key into Mok. That doesn't mean that a) the kernel %post script has to do that automatically (well it doesn't anyways, just prepares for it once) and b) the kernel built in official projects have to do the import. Check for example shim, it behaves differently when built in the official project (ie with openSUSE/SLE keys) vs built in home or devel projects. So similar checks could be done in the kernel spec file and skip mokutil when built with the openSUSE keys. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c9 --- Comment #9 from Michal Suchanek <msuchanek(a)suse.com> --- Does that work for kernels built in random home project? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c8 --- Comment #8 from Ludwig Nussel <lnussel(a)suse.com> --- Well in case of our kernel it's guaranteed as the CA cert is built into shim. The whole setup in obs is made so shim, grub and kernel match and work out of the box. So the case where the sign key chains back to our our CA cert can be optimized. So far we never imported the sign key itself either after all and relied on the CA only. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- It's not necessarily the case. The kernel (and modules) is signed with some key and if not imported it breaks secure boot. As in you won't be able to boot kernel signed with the key. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173115 http://bugzilla.opensuse.org/show_bug.cgi?id=1173115#c6 --- Comment #6 from Ludwig Nussel <lnussel(a)suse.com> --- ok, got it. It's caused by CONFIG_MODULE_SIG=y. With that enabled, the %post snippet wants to import the extra cert. It's not imported directly but rather added to some "to be imported queue" for next reboot. On reboot, a dialog with a 10s timeout is shown before grub. It asks to press a key to enter Mok key management. To actually import the key, one has to perform several steps in that wizard, including entering the root password. Not pressing a key will just continue boot, not import the key and don't bother anymore (until the next kernel update?). In other words, the whole stunt seems pointless and just confusing. Since kernel module signatures chain back to the secure boot CA built into shim we don't need that extra cert anyways, right? So can we just skip importing it? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c5 --- Comment #5 from Michal Suchanek <msuchanek(a)suse.com> --- If there is significant difference in scripts between 15.1 and 15.2 that's a bug. The scripts in the kernel-source repo are identical and changed only cosmetically since 15.1 beta. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173115] zypper dup from 15.1 shows mok screen on reboot
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173115 http://bugzilla.opensuse.org/show_bug.cgi?id=1173115#c4 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |Kernel Hardware|IA64 |x86-64 Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #4 from Ludwig Nussel <lnussel(a)suse.com> --- Moving to kernel then. If that behavior is intentional we should document it in the release notes. It feels a bit like a layering violation to mess with the certs in the kernel %post also. Shouldn't update-bootloader take care of the certs instead? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1171677] USB-C external hub randomly stops working
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

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

1 0

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- FYI, I created another test kernel in OBS home:tiwai:bsc1173085-2 repo containing more backports. If 5.7 kernel worked, please give this a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c12 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(seroton10(a)gmail.c | |om) --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Also, could you confirm that 5.7.x kernel in OBS Kernel:stable works? If that's confirmed, I can try to backport up to 5.7. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173138] New: Kernel 5.7.1 stuck at booting on HP Elitebook 840G6
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173138 Bug ID: 1173138 Summary: Kernel 5.7.1 stuck at booting on HP Elitebook 840G6 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: huy.phung1292(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838956 --> http://bugzilla.opensuse.org/attachment.cgi?id=838956&action=edit Last kernel debug line before hanging. Opensuse Tumbleweed freshly installed, kernel 5.7.1-1. Booting process stuck at 'workqueue lockup'. I uploaded 2 screenshot 1. Last line showed up on boot process before OS stucks in workqueue lockup 2. and 3. The screen when the booting hangs. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 19 Jun '20

19 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- You might need to unload realtek kernel module (it's phy driver) beforehand. But, could you upload the full dmesg output with the new kernel? The first probe should have succeeded if everything is right. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173085] Realtek RTL8117 NIC not recognized by Leap 15.2 RC (regression from 15.1)
by bugzilla_noreply＠suse.com 18 Jun '20

18 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1173085 https://bugzilla.suse.com/show_bug.cgi?id=1173085#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(seroton10(a)gmail.c | |om) --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Unfortunately there are quite lots of prerequisite commits the fix commit depends on, so in the end I had to apply almost 50 patches to reach there. The test kernel is built in OBS home:tiwai:bsc1173085 repo. It'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1173085/standard/ Please give it a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c8 --- Comment #8 from S. B. <sb56637(a)gmail.com> --- Created attachment 838896 --> https://bugzilla.suse.com/attachment.cgi?id=838896&action=edit Clear kernel on openSUSE vs default from same repo Thanks a lot Takashi for helping me to test this. So I tried the default kernel you compiled, and it behaves the same as the current Tumbleweed kernel and all the other major distros I've tested. I also was wondering how much of a difference the kernel boot parameters make. >From the AUR instructions I was using this with the Clear kernel: > quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs,f2fs tsc=reliable rw So I tested the with just `quiet splash mitigations=off` with the Clear kernel, but apart from some boot warnings it performed about as well. Then I tried the recommended Clear parameter with your kernel-default, and it also threw some boot warnings and performed the same as before with the same kernel. So the performance differences don't seem to be due to the boot parameters. I also realized that my thermal readings are probably being affected by the "ksgrd_network_helper" process that seems to be going a bit crazy, generating almost as much CPU load as Firefox itself. So I'll try to run some more tests later tonight with a lighter GUI system monitor. Please let me know if you need any more info. Cheers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172911] Raspi 3 kernel crash
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

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

1 0

[kernel-bugs] [Bug 1172911] Raspi 3 kernel crash
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172911 https://bugzilla.suse.com/show_bug.cgi?id=1172911#c1 --- Comment #1 from Matthias Brugger <mbrugger(a)suse.com> --- (In reply to Christian Goll from comment #0) > On my Rapspi 3 running a Nextcloud instance I experience stability problems > (no reachable via network any more after approx 1 day) for the actual > kernel. I could not find any hint in the system journal > The kernel version 5.3.18-lp152.10-default runs stable, so using kernel > 5.3.18-lp152.10-default solves the problem for me. Do you mean that you are experiencing problems with kernel-default-5.3.18-lp152.18.1.aarch64.rpm but not with the older lp152.10? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173014] New: TW 2020-06-15 fails to boot on Intel NUC10i7FNK2
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173014 Bug ID: 1173014 Summary: TW 2020-06-15 fails to boot on Intel NUC10i7FNK2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dostermann912(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838877 --> http://bugzilla.opensuse.org/attachment.cgi?id=838877&action=edit Error message on tty5 A fresh Tumbleweed installation (here: 20200615, but 20200614 and 0611 are also faulty) fails to boot after GRUB2 on an Intel NUC10i7FNK2. I get to see the TW EFI boot screen, but the system doesn't switch into graphical user mode. The virtual console on tty5 shows a "BUG: work queue lockup[...]" repeating roughly every minute until the computer freezes completely at some point. See the attachment for the full error message. The error persists after upgrading to the newest EFI firmware and turning off CPU mitigations in the kernel boot parameters. System specifications: - Intel Core i7-10710U - 32GB DDR4-2666 - Samsung EVO Pro 970 512GB - BIOS/EFI Version FN0042 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1172905] New: Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172905 Bug ID: 1172905 Summary: Kernel 5.7.1 does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: p.stolz77(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After update to Tumbleweed snapshot 20200612 the new kernel 5.7.1 does not boot. Booting with old kernel 5.6.14 works. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Thanks, I'll wait for your feedback. Meanwhile, I built kernel-default from the same source again. It'll be published soon in the same URL above. If the significant improvement is confirmed with kernel-clear, please try kernel-default from that repo and test whether you see the similar improvement. If kernel-default in that repo gets improvements, it implies that it's due to some Clear Linux downstream patches. OTOH, if kernel-default doesn't show the difference, it means that the key point is the kernel config, not the patches. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173023] New: Unexpected change from kernel-firmware to kernel-firmware-all package by 'zypper dup'
by bugzilla_noreply＠suse.com 17 Jun '20

17 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173023 Bug ID: 1173023 Summary: Unexpected change from kernel-firmware to kernel-firmware-all package by 'zypper dup' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse+build(a)de-korte.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Due to boo#1172905 I recently switched from 'kernel-firmware-all' to 'kernel-firmware' package to work around this bug. This didn't quite work as I expected. Removing 'kernel-firmware-all' would leave the remainder of the 'kernel-firmware-*' packages installed and I had to zypper lock the 'kernel-firmware-all' package after deinstallation. Otherwise 'zypper dup' would insist on reverting back to 'kernel-firmware-all' and removing 'kernel-firmware'. As I understand 'kernel-firmware-all' and 'kernel-firmware' are mutually exclusive and although the first may be preferred over the latter upon first installation, once a choice is made (for whatever reason), zypper should not change to the other. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c6 S. B. <sb56637(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sb56637(a)gmail.com | |) | --- Comment #6 from S. B. <sb56637(a)gmail.com> --- Created attachment 838878 --> https://bugzilla.suse.com/attachment.cgi?id=838878&action=edit openSUSE with Clear kernel vs stock openSUSE kernel Thanks very much Takashi, you saved a ton of time with that. It does look like the Clear kernel also makes a significant difference on openSUSE. I did the tests on my installed daily driver system, but with Openbox to eliminate some of the variables and to prevent my normal Plasma autostart apps from running. The only weird thing is that there doesn't seem to be a clear (pun not intended) advantage in terms of thermal performance, but that might just be a function of which kernel I tested first and how long the machine was running. Or it might be Clear being more aggressive with the processor. At any rate, I'll use this kernel in a "real" Zoom meeting that I have scheduled for this weekend, and I'll see how it feels, literally, in terms of heat and smell. Please let me know if you'd like any more information. Thanks again! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sb56637(a)gmail.com | |) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks, that's an interesting finding. Now I tried to build a kernel that contains Clear Linux downstream patches and the config aligned with it but slightly adjusted to be usable on TW. It's being built in OBS home:tiwai:test:kernel-clear repo. The new kernel package is "kernel-clear", not "kernel-default", and it'll be available at http://download.opensuse.org/repositories/home:/tiwai:/test:/kernel-clear/s… Download kernel-clear-5.7.*.rpm from there and install it via zypper in kernel-clear-5.7.*.rpm later. And let me know if this brings anything better than kernel-default. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173008] New: Kernel 5.7.1-1 upgrade breaks boot
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173008 Bug ID: 1173008 Summary: Kernel 5.7.1-1 upgrade breaks boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pointedstick(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838862 --> http://bugzilla.opensuse.org/attachment.cgi?id=838862&action=edit Console output when using the 7.1.1 recovery kernel I just got a Tumbleweed snapshot that includes Kernel 5.7.1-1. After installing this update (using `zypper dup`) and rebooting, my system (Lenovo ThinkPad X1 Yoga gen 4) did not progress past the boot splash screen. When using grub to select the 5.7.1-1 recovery kernel, I got a bunch of console spew and the cursor became visible and could be moved, but the system was otherwise frozen and the boot process did not progress, as before. reverting to Kernel 5.6.14 allowed the system to boot normally. Definitely seems like a regression in the 5.7.1-1 kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c4 S. B. <sb56637(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sb56637(a)gmail.com | |) | --- Comment #4 from S. B. <sb56637(a)gmail.com> --- Created attachment 838855 --> https://bugzilla.suse.com/attachment.cgi?id=838855&action=edit Arch with Clear Linux kernel Hi again, I found the Clear Linux kernel and kernel boot options available for Arch Linux: https://software.opensuse.org/package/linux-clear https://aur.archlinux.org/packages/linux-clear/#pinned-630000 This made it much easier for me to test it. I created an Arch installation on a live USB and installed the above linux-clear package and compared it with the stock Arch kernel. In summary, it does indeed appear that the Clear Linux kernel usually drastically reduces CPU load, whereas the stock Arch kernel behaves approximately the same as the stock openSUSE kernel. I found that Jitsi CPU loads were highly variable, so started testing with a similar service at http://appr.tc, which seems to produce more consistent results. Please let me know if you need any more information. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel regression 5.7.1 with iwlwifi 9260 model
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c35 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #35 from Jiri Slaby <jslaby(a)suse.com> --- . -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel regression 5.7.1 with iwlwifi 9260 model
by bugzilla_noreply＠suse.com 16 Jun '20

16 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c34 --- Comment #34 from Jiri Slaby <jslaby(a)suse.com> --- SR#814606 pending. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Use whatever the config you can build the upstream vanilla kernel :) The point is to build such a kernel on TW, and test whether you get the performance gain. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c2 --- Comment #2 from S. B. <sb56637(a)gmail.com> --- Hi Takashi, thanks for the reply, would this be any easier? https://github.com/clearlinux-pkgs/linux -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c22 --- Comment #22 from Peter Stolz <p.stolz77(a)googlemail.com> --- Created attachment 838791 --> https://bugzilla.suse.com/attachment.cgi?id=838791&action=edit Output of dmesg After boot with kernel 5.6.14 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c21 --- Comment #21 from Peter Stolz <p.stolz77(a)googlemail.com> --- Created attachment 838790 --> https://bugzilla.suse.com/attachment.cgi?id=838790&action=edit Output of hwinfo After boot with kernel 5.6.14 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c12 --- Comment #12 from Roger Whittaker <roger.whittaker(a)suse.com> --- I see the same messages attached by Dan in comment#10, on the same hardware Precision 5530. I tested with dis_ucode_ldr and it made no difference. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172911] New: Raspi 3 kernel crash
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172911 Bug ID: 1172911 Summary: Raspi 3 kernel crash Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Rapspi 3 running a Nextcloud instance I experience stability problems (no reachable via network any more after approx 1 day) for the actual kernel. I could not find any hint in the system journal The kernel version 5.3.18-lp152.10-default runs stable, so using kernel 5.3.18-lp152.10-default solves the problem for me. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172900] Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172900 https://bugzilla.suse.com/show_bug.cgi?id=1172900#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(sb56637(a)gmail.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- You can try to build the kernel based on the config of Clear Linux manually on TW and see whether you get the given performance boost. If not, it's a user-space problem. Install linux git repo on the running Clear Linux system, set up the compiler and other tool chains, and run "make localmodconfig". You might need to catch up more via "make oldconfig". Change the CONFIG_LOCAL_VERSION string not to conflict with the existing one, make, and install the kernel, and confirm that the system works. Then you can copy the .config file from there to TW, and build again there in a similar step. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172901] Kernel - AMD-Vi: Unable to read/write to IOMMU perf counter.
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172901 https://bugzilla.suse.com/show_bug.cgi?id=1172901#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Assignee|kernel-bugs(a)opensuse.org |jroedel(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Joerg, could you take a look? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172905] Kernel 5.7.1 does not boot
by bugzilla_noreply＠suse.com 15 Jun '20

15 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172905 https://bugzilla.suse.com/show_bug.cgi?id=1172905#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |p.stolz77(a)googlemail.com, | |tiwai(a)suse.com Flags| |needinfo?(p.stolz77@googlem | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Do you get any crash trace or such if you boot without quiet option? Also try to remove splash=silent, too. And, please boot with the old working kernel, and get hwinfo output from there, and attach to Bugzilla. Give the dmesg output from the working kernel, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172901] New: Kernel
by bugzilla_noreply＠suse.com 14 Jun '20

14 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172901 Bug ID: 1172901 Summary: Kernel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rahmspinat(a)gmx.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0 Build Identifier: On Lenovo Laptop with Ryzen APU I get the message during boot: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. (dmsg | grep IOMMU) Reproducible: Always Steps to Reproduce: Hardware for reproducing is needed. Actual Results: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. Expected Results: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40 perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). The expected result I got when booting Ubuntu 20.04. Seems to be that a certain parameter in kernel config needs to be set. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172900] New: Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux
by bugzilla_noreply＠suse.com 14 Jun '20

14 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172900 Bug ID: 1172900 Summary: Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838777 --> http://bugzilla.opensuse.org/attachment.cgi?id=838777&action=edit lots of screenshots and terminal outputs Hi there, the pandemic has forced a lot of users to spend much more time in videoconferencing apps, which in turn has given more exposure to some of the inefficiencies in the Linux graphics stack. I've been fighting with Jitsi Meet via Firefox and Zoom making my laptop so hot that the fans go full speed, and it smells and feels hot. It's an all-Intel components Thinkpad T530. I also observe even higher CPU loads but slightly less palpable heat on my secondary Thinkpad T440s, also with all-Intel components. And of course, with the addtional CPU load comes much shorter battery life. I've also extensively tested other mainstream distros like the most recent Ubuntu, Fedora, and Manjaro releases with similar results, but since Tumbleweed is the one I actually want to use on this laptop I'm reporting this bug here. As a last resort, I tried Clear Linux on the Thinkpad T530, since I heard Clear was optimized for Intel hardware. Surprisingly, it reported drastically lower CPU load and generally lower heat readings. And to the touch/smell the machine was obviously cooler and less stressed. The Firefox CPU load with Jitsi under Clear Linux was similar to what I have observed under Windows 8 on my Thinkpad T440s laptop. I retested several times in Clear under Gnome (Xorg session), and then several times more on my daily driver installed openSUSE Tumbleweed system with KDE Plasma (Xorg) and Openbox, and then I confirmed the excess CPU usage with a Tumbleweed live USB running Gnome on Xorg and Wayland. I'm attaching a tarball of all my findings, since there are a lot of files. The filenames describe what OS and what applications are running. The Zoom test was with a simple 2 user meeting with first video and then screensharing. The Jitsi test was performed with just 2 users with video enabled on a fresh Firefox profile. I'm attaching Firefox's support output and Zoom's terminal output, as well as the loaded kernel modules. I'm also attaching the hwinfo for my Thinkpad T530, but I don't think it's particularly relevant because I have observed the same CPU loads with the same apps on all the other laptops I own running Linux. Please let me know if you need any other information, I'd be glad to help troubleshoot. I'm not really an expert on the graphics stack in Linux, but I have tried to follow the Arch Wiki guidelines for enabling VA-API, and I've tried tons of options in about:config for Firefox on my installed openSUSE TW system. I'm sure it has packages installed that aren't present on the TW live Gnome system I booted, which is probably the reason for the differences in CPU load and temperature between the two systems. But both are drastically worse than Clear Linux straight out-of-the-box. Any ideas on what Clear Linux is doing differently? Is it just the result of thousands of little tweaks and optimizations, or is there some major configuration or compile flag in the graphics stack that Clear is using that could be applied to Tumbleweed? Thanks a lot for the help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 14 Jun '20

14 Jun '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2 -> http://bugzilla.suse.com/show_bug.cgi?id=1166342 test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 Support for 64-bot processors on motherboards with 32-bit UEFI -> http://bugzilla.suse.com/show_bug.cgi?id=1172292 usb message shown on console even with "quiet splash=silent" -> http://bugzilla.suse.com/show_bug.cgi?id=1172322 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

1 0

[kernel-bugs] [Bug 1172886] New: Kernel 4.12.14-lp151.28.52-default is unable to start on some hardware
by bugzilla_noreply＠suse.com 14 Jun '20

14 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172886 Bug ID: 1172886 Summary: Kernel 4.12.14-lp151.28.52-default is unable to start on some hardware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ae(a)ae-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838763 --> http://bugzilla.opensuse.org/attachment.cgi?id=838763&action=edit Screenshot of Kernelpanic Kernelpanic with Linux mail 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020 (464fb5f) x86_64 x86_64 x86_64 GNU/Linux Kernel Linux mail 4.12.14-lp151.28.48-default #1 SMP Fri Apr 17 05:38:36 UTC 2020 (18849d1) x86_64 x86_64 x86_64 GNU/Linux works fine. I can only add a picture from the root server. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6
by bugzilla_noreply＠suse.com 12 Jun '20

12 Jun '20

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

1 0

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6
by bugzilla_noreply＠suse.com 12 Jun '20

12 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172741 https://bugzilla.suse.com/show_bug.cgi?id=1172741#c3 --- Comment #3 from Tony Jones <tonyj(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > Pushed the fix to master/for-next branch. Wrong. We don't collect perf patches in the kernel tree. Please revert and leave perf stuff to me. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6
by bugzilla_noreply＠suse.com 12 Jun '20

12 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172741 https://bugzilla.suse.com/show_bug.cgi?id=1172741#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Pushed the fix to master/for-next branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172856] New: ucode-intel 20200602 hangs on 06-4e-03
by bugzilla_noreply＠suse.com 12 Jun '20

12 Jun '20

https://bugzilla.suse.com/show_bug.cgi?id=1172856 Bug ID: 1172856 Summary: ucode-intel 20200602 hangs on 06-4e-03 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 URL: https://github.com/intel/Intel-Linux-Processor-Microco de-Data-Files/issues/31 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- New microcode ucode-intel 20200602-lp151.2.24.1 hangs hard on 06-4e-03. workaround: zypper in --oldpackage ucode-intel-20191115-lp151.2.21.1 DMI: Dell Inc. Latitude E7470/0T6HHJ, BIOS 1.22.8 10/08/2019 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172475] New: Random screen flashing after suspend on KDE
by bugzilla_noreply＠suse.com 11 Jun '20

11 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172475 Bug ID: 1172475 Summary: Random screen flashing after suspend on KDE Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: piotr.kusnierz(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have serious problem with my laptop after suspend. Screen is randomly blinking when opening new window or scrolling in KDE with default kernel. Problem not persist in GNOME. It happens only on one of my machines and only after wakeup from suspend. Maybe there os something wrong with refresh rate after wake up? Problem is gone when i update kernel to 5.6, so I think this is a kernel 5.3 bug. My hardware is: Huawei MateBook 13 (i7-8565U, GeForce MX150) -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1172812] New: Thinkpad X1 Yoga gen 4: Kernel upgrade made microphone disappear
by bugzilla_noreply＠suse.com 11 Jun '20

11 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172812 Bug ID: 1172812 Summary: Thinkpad X1 Yoga gen 4: Kernel upgrade made microphone disappear Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pointedstick(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new Lenovo ThinkPad X1 Yoga recently and installed TW on it. As of yesterday, with the latest available Kernel, sof-firmware, and PulseAudio 14 (built from source and installed to /usr/local), I had the audio in the following condition: - Working microphone - Working 4-channel audio, albeit without any bass - Unplugged HDMI and DisplayPort audio devices pointlessly showed up in PulseAudio volume control and plasma-pa System Tray applet/KCM After today's Tumbleweed update, The following things improved: - The audio profile in PulseAudio changed to "Analog Surround 4.0 Output" - The unplugged HDMI and DisplayPort audio devices disappeared from PulseAudio volume control and plasma-pa System Tray applet/KCM However the following things regressed: - Microphone no longer appears in PulseAudio volume control and plasma-pa System Tray applet/KCM This is kind of sucky as the device has a nice quad microphone arrangement and now it's just not visible at all. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1172741] perf fails to build on aarch64 and armv7/6
by bugzilla_noreply＠suse.com 10 Jun '20

10 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172741 http://bugzilla.suse.com/show_bug.cgi?id=1172741#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> --- Landed in Linus tree, the commit 168200b6d6ea0cb5765943ec5da5b8149701f36a perf cs-etm: Move definition of 'traceid_list' global variable from header file -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172741] New: perf fails to build on aarch64 and armv7/6
by bugzilla_noreply＠suse.com 09 Jun '20

09 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172741 Bug ID: 1172741 Summary: perf fails to build on aarch64 and armv7/6 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 Found By: --- Blocker: --- perf fails to build on aarch64 and armv7/6 due to: ********** [ 652s] ld: arch/perf-in.o:/home/abuild/rpmbuild/BUILD/tools/perf/util/include/../../util/cs-etm.h:118: multiple definition of `traceid_list'; util/perf-in.o:/home/abuild/rpmbuild/BUILD/tools/perf/util/cs-etm.h:118: first defined here ********** Likely fixed by: https://lkml.org/lkml/2020/5/5/497 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172699] [Staging] Kernel 5.7 breaks test suite of tar and libarchive
by bugzilla_noreply＠suse.com 09 Jun '20

09 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172699 http://bugzilla.suse.com/show_bug.cgi?id=1172699#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Hardware|x86-64 |i686 Assignee|kernel-bugs(a)opensuse.org |jslaby(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #1) > Happens on x86_64 too. Switching to that as it's more common. I am wrong here. osc build takes the last arch used, so I repeated an i586 build, x86_64 looks to be unaffected. And it explains the irreproducibility above. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172699] [Staging] Kernel 5.7 breaks test suite of tar and libarchive
by bugzilla_noreply＠suse.com 09 Jun '20

09 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172699 http://bugzilla.suse.com/show_bug.cgi?id=1172699#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|i586 |x86-64 --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Hm, it's some setup thing. While it reproduces in osc shell environment, I cannot reproduce in a VM with that kernel installed, nor with a compiled kernel. Happens on x86_64 too. Switching to that as it's more common. I really love these issues. To be continued. What happens is that tar'ing of a sparse 8G file (512B at the end) creates a proper archive. Untar'ing (using xvf) creates a zeroed 512B file with the bad kernel (5.7). Good kernel untars to a proper 8G file, indeed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172699] New: [Staging] Kernel 5.7 breaks test suite of tar and libarchive
by bugzilla_noreply＠suse.com 09 Jun '20

09 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172699 Bug ID: 1172699 Summary: [Staging] Kernel 5.7 breaks test suite of tar and libarchive Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i586 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Staging:B contains kernel 5.7 If the obs worker VM is built up using kernel-obs-build 5.7, then I see build failures in at least * apr * libarchive * tar failing their test suites. from libarchive: >[ 305s] 445/692 Test #448: libarchive_test_sparse_basic .............................................***Failed 0.02 sec >[ 305s] >[ 305s] If tests fail or crash, details will be in: >[ 305s] /tmp/libarchive_test.2020-06-08T22.51.32-000 >[ 305s] >[ 305s] Reference files will be read from: /home/abuild/rpmbuild/BUILD/libarchive-3.4.3/libarchive/test >[ 305s] Exercising: libarchive 3.4.3 zlib/1.2.11 liblzma/5.2.5 bz2lib/1.0.8 liblz4/1.9.2 libzstd/1.4.5 >[ 305s] 447: test_sparse_basic >[ 305s] ../libarchive/test/test_sparse_basic.c:431: expected_offset != archive_entry_size(ae) >[ 305s] expected_offset=4563410944 (0x110002000, 042000020000) >[ 305s] archive_entry_size(ae)=3221233664 (0xc0002000, 030000020000) >[ 305s] ../libarchive/test/test_sparse_basic.c:434: holes_seen != expected_holes >[ 305s] Description: file4 >[ 305s] holes_seen=1 (0x1, 01) >[ 305s] expected_holes=2 (0x2, 02) Tar also fails in context of sparse files > 8GB apr lists something like this: >[ 345s] Headers (3): >[ 345s] 15 bytes (1) >[ 345s] 5 bytes (E) >[ 345s] 80000 bytes (^) >[ 345s] File: 200000 bytes from offset 0 >[ 345s] Trailers (3): >[ 345s] 19 bytes >[ 345s] 10 bytes >[ 345s] 90000 bytes >[ 345s] apr_socket_sendfile()->0, sent 370049 bytes >[ 345s] After apr_socket_sendfile(), the kernel file pointer is at offset 0. >[ 345s] client: apr_socket_sendfile() worked as expected! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] New: kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172670 Bug ID: 1172670 Summary: kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode 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: shung-hsi.yu(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838585 --> http://bugzilla.opensuse.org/attachment.cgi?id=838585&action=edit journalctl output (colored) The system is configured to capture core dump on crash with `yast2 kdump`. This is confirmed by looking at /proc/cmdline (contains ' crashkernel=256M,high crashkernel=72M,low'), output of `dmesg`, and the status of kdump.service. Triggering a crash dump manually with `echo c >/proc/sysrq-trigger` shows the stacktrace, but fails to correctly boot up the dump-capturing kernel. Below is an excerpt of the output of `journalctl` before the emergency shell was started. Jun 08 14:13:35 localhost systemd[1]: Starting Switch Root... Jun 08 14:13:35 localhost systemctl[377]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. Jun 08 14:13:35 localhost systemd[1]: Failed to start Switch Root. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= d ependencies. Jun 08 14:13:35 localhost systemd[1]: Starting Setup Virtual Console... Jun 08 14:13:35 localhost systemd[1]: Finished Setup Virtual Console. Jun 08 14:13:35 localhost systemd[1]: Started Emergency Shell. Jun 08 14:13:35 localhost systemd[1]: Reached target Emergency Mode. This issue looks a bit similar to https://bugzilla.redhat.com/show_bug.cgi?id=1812393 but I'm not too sure. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1172541] Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172541 http://bugzilla.suse.com/show_bug.cgi?id=1172541#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's wait until 5.7 kernel gets merged to TW snapshot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1171677] USB-C external hub randomly stops working
by bugzilla_noreply＠suse.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1171677 http://bugzilla.suse.com/show_bug.cgi?id=1171677#c7 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |lubos.kocman(a)suse.com Component|GNOME |Kernel Assignee|gnome-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #7 from Lubos Kocman <lubos.kocman(a)suse.com> --- Switching from GNOME desktop to kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 07 Jun '20

07 Jun '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

1 0

[kernel-bugs] [Bug 1172541] Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 05 Jun '20

05 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172541 http://bugzilla.suse.com/show_bug.cgi?id=1172541#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> --- Unfortunately it's very hard to guess what's going on there only from that. We already moved to 5.7 kernel now, and the update is on its way to TW. Could you try 5.7 kernel from OBS Kernel:stable repo and see whether the issue persists? If a crash happens, it'd be great if you can get a trace of Oops or whatever. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172322] usb message shown on console even with "quiet splash=silent"
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172322 http://bugzilla.suse.com/show_bug.cgi?id=1172322#c3 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #3 from Frank Krüger <fkrueger(a)mailbox.org> --- Using current TW and Kernel:stable, my webcam does not work from time to time (using uvcvideo driver), and in this case I am also seeing the above-mentioned messages. Does your webcam work? What is the output of 'lsusb -t' and 'lsusb -v | grep -i port1'? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172292] Support for 64-bot processors on motherboards with 32-bit UEFI
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172292 http://bugzilla.suse.com/show_bug.cgi?id=1172292#c2 --- Comment #2 from Gary Ching-Pang Lin <glin(a)suse.com> --- It's so called UEFI Mixed mode, and it would need support both from bootloader and kernel. CONFIG_EFI_MIXED is already enabled in kernel, so the question would be how to detect mixed mode and install the proper UEFI bootloader. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172322] usb message shown on console even with "quiet splash=silent"
by bugzilla_noreply＠suse.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172322 http://bugzilla.suse.com/show_bug.cgi?id=1172322#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert(a)suse.com Flags| |needinfo?(mrueckert(a)suse.co | |m) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The changes between v5.6.12..v5.6.14 wrt drivers/usb are mostly for gadget and other device-specific fixes, so it's not obvious what may break. In anyway, please give the detailed hardware information as well as hwinfo output, and the whole dmesg outputs on both working and non-working cases. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1166342] Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2
by bugzilla_noreply＠suse.com 03 Jun '20

03 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1166342 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172366] btrfs balance in endless loop and couldn't be canceled
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172366 Goldwyn Rodrigues <rgoldwyn(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |wqu(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172378] New: oopsing in dm_mirror during pvmove
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172378 Bug ID: 1172378 Summary: oopsing in dm_mirror during pvmove Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've seen a few of these now trying to migrate pontifex (download.opensuse.org) away from an old storage. It is probably triggered by a read error on the underlying device. kernel: 4.12.14-lp151.28.48-default, x86_64 most recent: -- 100:pontifex2 -- time-stamp -- Jun/02/20 2:49:09 -- [68935.390120] invalid opcode: 0000 [#1] SMP NOPTI [68935.404194] CPU: 2 PID: 26557 Comm: kworker/2:0 Not tainted 4.12.14-lp151.28.48-default #1 openSUSE Leap 15.1 [68935.406277] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.0-0-g63451fc-prebuilt.qemu-project.org 04/01/2014 [68935.408703] Workqueue: kmirrord do_mirror [dm_mirror] [68935.409680] task: ffff8801ea3d0080 task.stack: ffffc900148c4000 [68935.410863] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [68935.411948] RSP: 0018:ffffc900148c7d48 EFLAGS: 00010296 [68935.412957] RAX: 0000000000000040 RBX: ffff88005a28c0b0 RCX: 0000000000000006 [68935.414326] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fc97a60 [68935.415690] RBP: ffffffffa02ea280 R08: 0000000000000241 R09: 0000000000000001 [68935.417088] R10: ffffc90014c5fc20 R11: 0000000000000001 R12: ffff88005a28c040 [68935.418463] R13: ffffffffa02ea410 R14: ffff880333ea2128 R15: 0000000000000000 [68935.419968] FS: 0000000000000000(0000) GS:ffff88183fc80000(0000) knlGS:0000000000000000 [68935.421504] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [68935.422608] CR2: 000055e713b82e58 CR3: 000000028f0e0000 CR4: 00000000000406e0 [68935.424047] Call Trace: [68935.424541] do_reads+0x17a/0x1c0 [dm_mirror] [68935.425385] ? dm_rh_update_states+0x2f9/0x310 [dm_region_hash] [68935.426527] ? down_trylock+0x25/0x30 [68935.427262] ? dm_rh_recovery_prepare+0x9d/0x120 [dm_region_hash] [68935.428483] do_mirror+0x102/0x66e [dm_mirror] [68935.429360] ? __switch_to_asm+0x34/0x70 [68935.430134] ? __switch_to_asm+0x40/0x70 [68935.430905] ? __switch_to_asm+0x34/0x70 [68935.431774] ? __switch_to_asm+0x34/0x70 [68935.432608] ? finish_task_switch+0x76/0x230 [68935.433509] process_one_work+0x1da/0x400 [68935.434320] worker_thread+0x2b/0x3f0 [68935.435091] ? process_one_work+0x400/0x400 [68935.435921] kthread+0x10d/0x130 [68935.436562] ? kthread_create_worker_on_cpu+0x50/0x50 [68935.437623] ret_from_fork+0x22/0x40 [68935.438372] Code: 7b e0 48 8d 54 24 07 48 89 de e8 2e 41 5a e1 83 f8 01 74 39 83 f8 02 74 14 85 c0 74 15 89 c6 48 c7 c7 30 df 46 a0 e8 f2 16 d6 e0 <0f> 0b c6 44 24 07 0b 80 7b f8 00 75 08 48 89 df e8 fd 9e f7 e0 [68935.442895] Modules linked in: ip6table_raw xt_comment iptable_raw xt_CT nfnetlink_cthelper nfnetlink af_packet iscsi_ibft iscsi_boot_sysfs ip6 t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broa dcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables edac_mce_amd kvm_amd ccp xfs kvm ir qbypass libcrc32c dm_mirror crc32_pclmul cirrus dm_region_hash crc32c_intel dm_log ghash_clmulni_intel ttm pcbc drm_kms_helper dm_mod aesni_intel drm virtio_net aes_x86_64 crypto_simd glue_helper net_failover drm_panel_orientation_quirks cryptd failover virtio_balloon fb_sys_fops syscopyarea sysfillrect sysimgblt i2c_piix4 pcspkr qemu_fw_cfg button ata_generic ata_piix [68935.459497] ahci uhci_hcd libahci ehci_hcd serio_raw usbcore virtio_blk floppy sg [68935.461356] ---[ end trace 2f37a9f791364259 ]--- [68935.462345] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [68935.462347] RSP: 0018:ffffc900148c7d48 EFLAGS: 00010296 [68935.462349] RAX: 0000000000000040 RBX: ffff88005a28c0b0 RCX: 0000000000000006 [68935.462350] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fc97a60 [68935.462351] RBP: ffffffffa02ea280 R08: 0000000000000241 R09: 0000000000000001 [68935.462357] R10: ffffc90014c5fc20 R11: 0000000000000001 R12: ffff88005a28c040 [68935.471992] R13: ffffffffa02ea410 R14: ffff880333ea2128 R15: 0000000000000000 [68935.471995] FS: 0000000000000000(0000) GS:ffff88183fc80000(0000) knlGS:0000000000000000 [68935.471996] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [68935.471997] CR2: 000055e713b82e58 CR3: 000000028f0e0000 CR4: 00000000000406e0 -- 100:pontifex2 -- time-stamp -- Jun/02/20 2:51:02 -- one before: -- 100:pontifex2 -- time-stamp -- Jun/01/20 6:05:10 -- [60441.972610] invalid opcode: 0000 [#1] SMP NOPTI [60441.973885] CPU: 5 PID: 30125 Comm: kworker/5:1 Not tainted 4.12.14-lp151.28.48-default #1 openSUSE Leap 15.1 [60441.975765] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.0-0-g63451fc-prebuilt.qemu-project.org 04/01/2014 [60441.977969] Workqueue: kmirrord do_mirror [dm_mirror] [60441.979186] task: ffff88029f9d8180 task.stack: ffffc9000e5d4000 [60441.981195] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [60441.982803] RSP: 0018:ffffc9000e5d7d48 EFLAGS: 00010296 [60441.984530] RAX: 0000000000000040 RBX: ffff88012c518870 RCX: 0000000000000006 [60441.986931] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fd57a60 [60441.988503] RBP: ffffffffa0153280 R08: 000000000000024a R09: 0000000000000001 [60441.989878] R10: ffffc9000752f7f8 R11: 0000000000000001 R12: ffff88012c518800 [60441.991239] R13: ffffffffa0153410 R14: ffff8817db49f928 R15: 0000000000000000 [60441.992661] FS: 0000000000000000(0000) GS:ffff88183fd40000(0000) knlGS:0000000000000000 [60441.995364] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [60441.996482] CR2: 00007f20a09d3000 CR3: 0000000308c96000 CR4: 00000000000406e0 [60441.997927] Call Trace: [60441.998417] do_reads+0x17a/0x1c0 [dm_mirror] [60441.999249] ? dm_rh_update_states+0x2f9/0x310 [dm_region_hash] [60442.000352] ? down_trylock+0x25/0x30 [60442.001033] ? dm_rh_recovery_prepare+0x9d/0x120 [dm_region_hash] [60442.002188] do_mirror+0x102/0x66e [dm_mirror] [60442.003036] ? __switch_to_asm+0x34/0x70 [60442.003724] ? __switch_to_asm+0x40/0x70 [60442.004385] ? __switch_to_asm+0x34/0x70 [60442.005301] ? __switch_to_asm+0x34/0x70 [60442.006079] ? finish_task_switch+0x76/0x230 [60442.007175] process_one_work+0x1da/0x400 [60442.007959] worker_thread+0x2b/0x3f0 [60442.008664] ? process_one_work+0x400/0x400 [60442.009497] kthread+0x10d/0x130 [60442.010111] ? kthread_create_worker_on_cpu+0x50/0x50 [60442.011171] ret_from_fork+0x22/0x40 [60442.011867] Code: 7b e0 48 8d 54 24 07 48 89 de e8 2e e1 7a e1 83 f8 01 74 39 83 f8 02 74 14 85 c0 74 15 89 c6 48 c7 c7 30 3f 26 a0 e8 f2 b6 f6 e0 <0f> 0b c6 44 24 07 0b 80 7b f8 00 75 08 48 89 df e8 fd 3e 18 e1 [60442.015764] Modules linked in: ip6table_raw xt_comment iptable_raw xt_CT nfnetlink_cthelper nfnetlink af_packet iscsi_ibft iscsi_boot_sysfs ip6 t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broa dcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables edac_mce_amd kvm_amd xfs ccp dm_mir ror kvm cirrus libcrc32c dm_region_hash ttm irqbypass drm_kms_helper crc32_pclmul dm_log crc32c_intel dm_mod ghash_clmulni_intel drm pcbc drm_pane l_orientation_quirks virtio_net fb_sys_fops aesni_intel syscopyarea sysfillrect net_failover aes_x86_64 sysimgblt failover crypto_simd glue_helper virtio_balloon pcspkr cryptd i2c_piix4 qemu_fw_cfg button ata_generic ata_piix [60442.029932] ahci libahci uhci_hcd ehci_hcd serio_raw virtio_blk usbcore floppy sg [60442.031558] ---[ end trace aead3917ec7f1b83 ]--- [60442.032626] RIP: 0010:clone_endio+0x5e/0x150 [dm_mod] [60442.032627] RSP: 0018:ffffc9000e5d7d48 EFLAGS: 00010296 [60442.032628] RAX: 0000000000000040 RBX: ffff88012c518870 RCX: 0000000000000006 [60442.032629] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88183fd57a60 [60442.032630] RBP: ffffffffa0153280 R08: 000000000000024a R09: 0000000000000001 [60442.032631] R10: ffffc9000752f7f8 R11: 0000000000000001 R12: ffff88012c518800 [60442.032631] R13: ffffffffa0153410 R14: ffff8817db49f928 R15: 0000000000000000 [60442.032634] FS: 0000000000000000(0000) GS:ffff88183fd40000(0000) knlGS:0000000000000000 [60442.032635] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [60442.032636] CR2: 00007f20a09d3000 CR3: 0000000308c96000 CR4: 00000000000406e0 -- 100:pontifex2 -- time-stamp -- Jun/01/20 6:07:09 -- -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1172366] New: btrfs balance in endless loop and couldn't be canceled
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172366 Bug ID: 1172366 Summary: btrfs balance in endless loop and couldn't be canceled Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have had a endless running btrfs balance with the kernel 4.12.14-lp151.28.48-default. The balance was triggered from the btrfsmaintenance balance timer. I have no kernel stack trace, only the same following trace during 15h: "kernel: [.......] BTRFS info (device dm-0): found 2087 extents" The btrfs filesystem was in the following situation: " Total devices 1 FS bytes used 30.81GiB devid 1 size 45.00GiB used 45.00GiB path /dev/mapper/system-root2 " I've tried to free some space through deletion of old snaphots during this situation, but the btrfs balance was running without change. Also canceling of the btrfs balance had no effect. After these tries i have rebooted the system with skip_balance option in the fstab. Manually started btrfs balance in several steps (with argument -musage beginning from 10 to 80, then with argument -dusage from 10 to 80) were running without problem, but the used size (second line) was a little smaller than 45.00 GiB at the start of the balance runs. A scrub of this filesystem shows no errors. There are some other bug reports describing the same or a similar problem (e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=1160947) but for me it is not clear, if this kernel, which has quite a lot btrfs related changes, should have a bugfix for this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172292] Support for 64-bot processors on motherboards with 32-bit UEFI
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172292 http://bugzilla.suse.com/show_bug.cgi?id=1172292#c1 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Michal Filka <mfilka(a)suse.com> --- Nothing for yast. Kernel team might help with that (?) -- You are receiving this mail because: You are the assignee for the bug.

1 0