September 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1176233] Unable to install nvidia driver 450.66
by bugzilla_noreply＠suse.com 07 Sep '20

07 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176233 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X11 3rd Party Driver 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 1176233] Unable to install nvidia driver 450.66
by bugzilla_noreply＠suse.com 07 Sep '20

07 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176233 https://bugzilla.suse.com/show_bug.cgi?id=1176233#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juergen-fuhrmann(a)web.de Flags| |needinfo?(juergen-fuhrmann@ | |web.de) --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- Weird. Can't reproduce this here on current kernel of Tumbleweed (also 5.8.4-1). Mabye the G05 package is outdated. Please check this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 07 Sep '20

07 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c58 --- Comment #58 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Martin Wilck from comment #57) Argh, I should proof-read my comments better. > I think I understand this now, at least partially. The explanation is > similar to what I wrote in comment 48. Can you confirm that the *version* of > the Nvidia driver was different, with only the *release* differing? I meant: "Can you confirm that the *version* of the Nvidia driver was *not* different (from before), with only the *release* differing?" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 07 Sep '20

07 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c57 --- Comment #57 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to John Shaw from comment #43) > This seemed to be working on my machine after the last round of grub2 > updates went through, then this morning a new nVidia driver update came > (along with about 20 other updates). On reboot with SecureBoot enabled, the > machine hung after post with a black screen. I rebooted with SecureBoot > disabled (ie, selected OtherOS in the ASUS bios), and it brought up the MOK > Manager. However, unlike before the options are now different. There is no > "enrole MOK", just: Continue, Reset MOK, Delete MOK, and enrole key and > enrole hash from disk. I think I understand this now, at least partially. The explanation is similar to what I wrote in comment 48. Can you confirm that the *version* of the Nvidia driver was different, with only the *release* differing? Because the driver package was using only the *version* (and not the release) in the certificate file name, the package update would create both an import and a deletion request for the same (new!) key at the same time, rather than a delete request for the old and an import request for the new one. Not sure how MokManager would deal with that, but your comment shows that it offered the key only for deletion. The latest Nvidia package fixes this by adding the release to the certificate file name. If it's only that, you should be able to recover from the problem by booting into a non-graphical environment, uninstalling the nvidia-gfx0$X package, and installing it again. I don't understand why any of this would cause your GRUB menu not to be shown. Normally these keys wouldn't be used until user space tries to load the nvidia driver. By that time, you should be past grub and past lots of boot messages from the kernel. The only explanation I have for that is that mokmanager might crash while trying to deal with the "contradictory" mok requests. (In reply to John Shaw from comment #37) > (In reply to Martin Wilck from comment #36) > > The question is if the BIOS fails to verify the shim, or shim fails to > > verify any of the follow-up binaries. Can you check this e.g. with the UEFI > > shell? > > I don't know how to check this in the UEFI shell. Can you explain? If you don't have an existing UEFI shell boot entry already, grab one. See e.g. > https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#… Next you need to copy this to your EFI boot partition, and find a way to make your BIOS boot it. Either the BIOS has a way to boot a specified EFI binary directly, or you could use efibootmgr to craft a suitable entry for it. Once in the shell, you can move around and run commands a bit like on good old DOS. You may have to enter a "drive" first, which would look like "fs0:". The "map" command can be used to see drives that the shell has recognized. The test would look roughly like this: > fs0: > cd \EFI\BOOT > bootx64.efi # or whatever else you want to boot The advantage is that you would see some error messages in this environment, e.g. if the binary's signature can't be verified by the BIOS. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1176233] New: Unable to install nvidia driver 450.66
by bugzilla_noreply＠suse.com 07 Sep '20

07 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176233 Bug ID: 1176233 Summary: Unable to install nvidia driver 450.66 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: juergen-fuhrmann(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi on a fresh install of tumbleweed (kernel 5.8) (and btw also on Leap 15.2 with Kernel 5.3) the nvidia driver 450.66 installation fails. The culprit seems to be that the make system complains about missing scripts/Makefile.kcsan Trying to report this to nvidia as well... -- You are receiving this mail because: You are the assignee for the bug.

1 1

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

06 Sep '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! Noveau driver dumps many of these and the laptop freezes for 10 seconds -> http://bugzilla.suse.com/show_bug.cgi?id=1105974 Raise default file descriptor limits to meet Valve Proton requirements -> http://bugzilla.suse.com/show_bug.cgi?id=1107525 suspend to RAM no longer working after upgrade to Leap 15.1 -> http://bugzilla.suse.com/show_bug.cgi?id=1137748 Untested laptop multimedia keys, please report success or failure to eric.piel(a)tremplin-utc.net -> http://bugzilla.suse.com/show_bug.cgi?id=1142370 Go To Meeting kills ethernet network connection intermittendly (r8152 4-1.2:1.0 eth2: Tx status -71) -> http://bugzilla.suse.com/show_bug.cgi?id=1146782 Bad USB cable causes eternal kernel messages, even after unplug: "tag#0 sense submit err -19 uas-tag 1 inflight: s-st a-in s-in a-cmd s-cmd" -> http://bugzilla.suse.com/show_bug.cgi?id=1155840 System crash caused by i915 driver -> http://bugzilla.suse.com/show_bug.cgi?id=1155938 missing keyboard & mouse events ... -> http://bugzilla.suse.com/show_bug.cgi?id=1158190 Bluetooth device sometimes vanishes after booting Tumbleweed - needs BIOS on/off cycle to come back -> http://bugzilla.suse.com/show_bug.cgi?id=1159767 Excessive swapping when buffers / cache expand beyond free physical RAM -> http://bugzilla.suse.com/show_bug.cgi?id=1159882 Screen flickering on latest Dell XPS 7390 with kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -> http://bugzilla.suse.com/show_bug.cgi?id=1161843 kernel 5.3.18-lp152.1 : Interrupts enabled after mce_syscore_resume -> http://bugzilla.suse.com/show_bug.cgi?id=1161867 kernel packaging problem: RPM group = %group -> http://bugzilla.suse.com/show_bug.cgi?id=1163592 Kernel oops in s390x tumbleweed -> http://bugzilla.suse.com/show_bug.cgi?id=1163684 Kernel crash (likely because of Intel graphics card) -> http://bugzilla.suse.com/show_bug.cgi?id=1164698 CD tray closed immediately after ejecting media -> http://bugzilla.suse.com/show_bug.cgi?id=1165047 System hung - nouveau 0000:01:00.0: plasmashell[2512]: channel 7 killed! -> http://bugzilla.suse.com/show_bug.cgi?id=1165790 Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2 -> http://bugzilla.suse.com/show_bug.cgi?id=1166342 shorewall traffic shaping locks/crashes kernel hard -> http://bugzilla.suse.com/show_bug.cgi?id=1166688 ACPI BIOS Error (bug) -> http://bugzilla.suse.com/show_bug.cgi?id=1167305 Mounting of SMB share through fstab fails on boot -> http://bugzilla.suse.com/show_bug.cgi?id=1168873 ACPI error on boot -> http://bugzilla.suse.com/show_bug.cgi?id=1169837 HW exception while booting on Rockchip Excavation board (aarch64) -> http://bugzilla.suse.com/show_bug.cgi?id=1170088 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 Random screen flashing after suspend on KDE -> http://bugzilla.suse.com/show_bug.cgi?id=1172475 Mysterious crashes with kernel 5.6.14, suspect KVM -> http://bugzilla.suse.com/show_bug.cgi?id=1172541 Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux -> http://bugzilla.suse.com/show_bug.cgi?id=1172900 Kernel 5.7.1 does not boot -> http://bugzilla.suse.com/show_bug.cgi?id=1173071 iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 -> http://bugzilla.suse.com/show_bug.cgi?id=1173294 Kernel delays boot by 12s if ip= option given -> http://bugzilla.suse.com/show_bug.cgi?id=1173402 Webcam(earlier working) doesn't work now. Sony Vaio -> http://bugzilla.suse.com/show_bug.cgi?id=1173448 WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman. -> http://bugzilla.suse.com/show_bug.cgi?id=1173449 Build of VMware access to kernel gives issues at interface build time. -> http://bugzilla.suse.com/show_bug.cgi?id=1173591 journal is flooded with "upowerd: treating change event as add on" when Dell WD15 Dock is connected -> http://bugzilla.suse.com/show_bug.cgi?id=1173728 System hangups in dual monitor use, likely Plasma/Xorg related -> http://bugzilla.suse.com/show_bug.cgi?id=1173748 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS -> http://bugzilla.suse.com/show_bug.cgi?id=1173819 Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX) -> http://bugzilla.suse.com/show_bug.cgi?id=1173870 BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook -> http://bugzilla.suse.com/show_bug.cgi?id=1173891 Laptop: one of two usb3 hubs gone with 5.7 - works with 5.3.6 (linux live system) -> http://bugzilla.suse.com/show_bug.cgi?id=1174017 kernel-firmware-amdgpu 20200702 breaks video on Picasso -> http://bugzilla.suse.com/show_bug.cgi?id=1174278 rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0 -> http://bugzilla.suse.com/show_bug.cgi?id=1174505 Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed -> http://bugzilla.suse.com/show_bug.cgi?id=1174868 Kernel v5.7.9 panic when resuming from hibernation with usb dock plugged-in -> http://bugzilla.suse.com/show_bug.cgi?id=1174886 Black screen with cursor upon login to plasma -> http://bugzilla.suse.com/show_bug.cgi?id=1175033 mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table -> http://bugzilla.suse.com/show_bug.cgi?id=1175105 WiFi breaks for Intel duel band AC 8265 -> http://bugzilla.suse.com/show_bug.cgi?id=1175125 AMDGPU Driver Brightness Issue -> http://bugzilla.suse.com/show_bug.cgi?id=1175300 NFSv4.1: timeout and endless unsuccessful retries -> http://bugzilla.suse.com/show_bug.cgi?id=1175305 Laptop BuildIn keyboard is not working with kernel-default-5.8.0-1.1 -> http://bugzilla.suse.com/show_bug.cgi?id=1175581 latest kernel update gives backtrace on boot on Huawei TaiShan 2280 -> http://bugzilla.suse.com/show_bug.cgi?id=1175589 After bios update, some keyboard function keys not recognized. -> http://bugzilla.suse.com/show_bug.cgi?id=1175646-- 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 1170232] Kernel spec self obsoletes
by bugzilla_noreply＠suse.com 04 Sep '20

04 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1170232 https://bugzilla.suse.com/show_bug.cgi?id=1170232#c18 --- Comment #18 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2540-1: An update that solves 7 vulnerabilities and has 129 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1074701,1083548,1085030,1085235,1085308,1087078,1087082,1094912,1100394,1102640,1105412,1111666,1112178,1113956,1120163,1133021,1144333,1152148,1163524,1165629,1166965,1169790,1170232,1171688,1172073,1172108,1172247,1172418,1172428,1172781,1172782,1172783,1172871,1172872,1172873,1172963,1173485,1173798,1173954,1174003,1174026,1174070,1174161,1174205,1174247,1174387,1174484,1174547,1174550,1174625,1174658,1174685,1174689,1174699,1174734,1174757,1174771,1174840,1174841,1174843,1174844,1174845,1174852,1174873,1174887,1174904,1174926,1174968,1175062,1175063,1175064,1175065,1175066,1175067,1175112,1175127,1175128,1175149,1175199,1175213,1175228,1175232,1175284,1175393,1175394,1175396,1175397,1175398,1175399,1175400,1175401,1175402,1175403,1175404,1175405,1175406,1175407,1175408,1175409,1175410,1175411,1175412,1175413,1175414,1175415,1175416,1175417,1175418,1175419,1175420,1175421,1175422,1175423,1175440,1175493,1175515,1175518,1175526,1175550,1175654,1175666,117566 7,1175668,1175669,1175670,1175767,1175768,1175769,1175770,1175771,1175772,1175786,1175873 CVE References: CVE-2018-3639,CVE-2020-14314,CVE-2020-14331,CVE-2020-14356,CVE-2020-16166,CVE-2020-1749,CVE-2020-24394 JIRA References: Sources used: SUSE Linux Enterprise Server 12-SP5 (src): kernel-azure-4.12.14-16.25.1, kernel-source-azure-4.12.14-16.25.1, kernel-syms-azure-4.12.14-16.25.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1170232] Kernel spec self obsoletes
by bugzilla_noreply＠suse.com 04 Sep '20

04 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1170232 https://bugzilla.suse.com/show_bug.cgi?id=1170232#c17 --- Comment #17 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2541-1: An update that solves 7 vulnerabilities and has 130 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1074701,1083548,1085030,1085235,1085308,1087078,1087082,1094912,1100394,1102640,1105412,1111666,1112178,1113956,1120163,1133021,1144333,1152148,1163524,1165629,1166965,1169790,1170232,1171688,1171988,1172073,1172108,1172247,1172418,1172428,1172781,1172782,1172783,1172871,1172872,1172873,1172963,1173485,1173798,1173954,1174003,1174026,1174070,1174161,1174205,1174387,1174484,1174547,1174549,1174550,1174625,1174658,1174685,1174689,1174699,1174734,1174757,1174771,1174840,1174841,1174843,1174844,1174845,1174852,1174873,1174887,1174904,1174926,1174968,1175062,1175063,1175064,1175065,1175066,1175067,1175112,1175127,1175128,1175149,1175199,1175213,1175228,1175232,1175284,1175393,1175394,1175396,1175397,1175398,1175399,1175400,1175401,1175402,1175403,1175404,1175405,1175406,1175407,1175408,1175409,1175410,1175411,1175412,1175413,1175414,1175415,1175416,1175417,1175418,1175419,1175420,1175421,1175422,1175423,1175440,1175493,1175515,1175518,1175526,1175550,1175654,117566 6,1175667,1175668,1175669,1175670,1175767,1175768,1175769,1175770,1175771,1175772,1175786,1175873 CVE References: CVE-2020-10135,CVE-2020-14314,CVE-2020-14331,CVE-2020-14356,CVE-2020-16166,CVE-2020-1749,CVE-2020-24394 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP1 (src): kernel-azure-4.12.14-8.41.1, kernel-source-azure-4.12.14-8.41.1, kernel-syms-azure-4.12.14-8.41.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 04 Sep '20

04 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c56 --- Comment #56 from John Shaw <johngshaw(a)twc.com> --- (In reply to Gary Ching-Pang Lin from comment #54) > (In reply to Gary Ching-Pang Lin from comment #53) > > John, > > > > Have you seen the MokManager screen with Secure Boot enabled before? I > > wonder if it's a drawing problem. > (I mean the MokManager from the older shim.) Yes, if I remember correctly it worked after I upgraded 15.1 to 15.2 and installed the nVidia drivers. This caught me by surprise and I was not sure what to do, so I just selected to continue to boot. The drivers did not load, but I was able to at least figure out what was happening. I imported the key again with mokutil and rebooted and selected "enroll MOK". FYI: I also see via "efibootmgr" that the system seems to be booting ".\efi\opensuse\shim.efi",even though I have SecureBoot disabled (verified by "mokutil --sb-state"). Note that the firmware bios still says its "enabled", but this allows the system to boot now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 04 Sep '20

04 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c55 --- Comment #55 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Neil Rickert from comment #52) > That cannot actually work. I might have more than one openSUSE system > installed on my computer, and those systems all share the same list of > enrolled keys. The rpm scripts can only check what is needed for the > particular system where it is running. Good point. But solving this correctly is tough. See comment 49, there are cases where we *want* to be sure to purge keys from the MokList. We can't ensure that, and at the same time keep all keys that other installations would want to have around. I guess the only way to solve it would be to have per-installation MokList variables, which would be a major implementation effort. Meanwhile Gary explained to me that for booting the *kernel*, having the keys in the MokList is actually not necessary, because shim has these sign keys built-in anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 0