July 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173870 https://bugzilla.suse.com/show_bug.cgi?id=1173870#c8 --- Comment #8 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Dirk Mueller from comment #5) > do you have the exact timestamp? No, I don't. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173870 https://bugzilla.suse.com/show_bug.cgi?id=1173870#c7 --- Comment #7 from Dirk Mueller <dmueller(a)suse.com> --- (I am somehow assuming that ECC errors would not only be reported in the guest but also in the host. maybe that assumption isn't correct?) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173870 https://bugzilla.suse.com/show_bug.cgi?id=1173870#c6 --- Comment #6 from Dirk Mueller <dmueller(a)suse.com> --- obs-arm-2 has been updated (host was leap 15.1, now is tw 20200721). lets see if it reappears. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

1 0

[kernel-bugs] [Bug 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173870 https://bugzilla.suse.com/show_bug.cgi?id=1173870#c5 --- Comment #5 from Dirk Mueller <dmueller(a)suse.com> --- do you have the exact timestamp? on the host things look normal, albeit the nvme timeouts are weird: [So Jul 26 14:15:59 2020] nvme nvme0: I/O 407 QID 7 timeout, completion polled [So Jul 26 14:51:58 2020] nvme nvme0: I/O 726 QID 14 timeout, completion polled [So Jul 26 20:11:21 2020] nvme nvme0: I/O 115 QID 18 timeout, completion polled [So Jul 26 20:12:01 2020] nvme nvme0: I/O 798 QID 4 timeout, completion polled [So Jul 26 20:21:10 2020] nvme nvme0: I/O 673 QID 25 timeout, completion polled [So Jul 26 20:26:30 2020] nvme nvme0: I/O 365 QID 11 timeout, completion polled [So Jul 26 20:56:37 2020] nvme nvme0: I/O 738 QID 16 timeout, completion polled [So Jul 26 20:59:03 2020] nvme nvme0: I/O 90 QID 20 timeout, completion polled [So Jul 26 20:59:53 2020] nvme nvme0: I/O 315 QID 19 timeout, completion polled [So Jul 26 21:01:35 2020] nvme nvme0: I/O 897 QID 29 timeout, completion polled [So Jul 26 21:02:29 2020] nvme nvme0: I/O 745 QID 17 timeout, completion polled [So Jul 26 21:03:11 2020] nvme nvme0: I/O 489 QID 18 timeout, completion polled [So Jul 26 21:03:16 2020] nvme nvme0: I/O 826 QID 20 timeout, completion polled [So Jul 26 21:14:30 2020] nvme nvme0: I/O 901 QID 25 timeout, completion polled [So Jul 26 21:16:43 2020] nvme nvme0: I/O 932 QID 26 timeout, completion polled [So Jul 26 21:17:22 2020] nvme nvme0: I/O 153 QID 26 timeout, completion polled [So Jul 26 21:18:19 2020] nvme nvme0: I/O 341 QID 31 timeout, completion polled [So Jul 26 21:23:53 2020] nvme nvme0: I/O 476 QID 21 timeout, completion polled [So Jul 26 21:43:30 2020] nvme nvme0: I/O 264 QID 8 timeout, completion polled [So Jul 26 21:45:17 2020] nvme nvme0: I/O 731 QID 31 timeout, completion polled [So Jul 26 21:58:37 2020] nvme nvme0: I/O 393 QID 3 timeout, completion polled [So Jul 26 21:59:12 2020] nvme nvme0: I/O 537 QID 2 timeout, completion polled [So Jul 26 22:04:07 2020] nvme nvme0: I/O 281 QID 15 timeout, completion polled [So Jul 26 22:06:56 2020] nvme nvme0: I/O 414 QID 23 timeout, completion polled [So Jul 26 22:37:24 2020] nvme nvme0: I/O 176 QID 13 timeout, completion polled -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174505] New: rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174505 Bug ID: 1174505 Summary: rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0 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: ianmepham(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I have two folders shared on an old Windows retro gaming PC. In Tumbleweed I have those shares mounted via /etc/fstab using cifs and the SMB protocol option vers=1.0. With kernel versions up to 5.7.7-1.2 rsync and mv would rename files correctly. Since upgrading to kernel 5.7.9 rsync and mv are failing to rename files. If I downgrade to kernel 5.7.7-1.2 rsync and mv can rename files again. I've read that this only affects kernels >=5.7.8 in combination with cifs SMB protocol 1.0. I found this discussion on the samba mailing list where someone else has already reported the problem and it specifically mentions the kernel patch which introduced the regression: https://lists.samba.org/archive/samba-technical/2020-July/135581.html Reproducible: Always Steps to Reproduce: 1.touch foo bar 2.mv -f foo bar Actual Results: touch foo bar mv -f foo bar mv: cannot move 'foo' to 'bar': File exists Expected Results: renamed 'foo' -> 'bar' While I don't use an LTS kernel, I've noticed other users report the same problem: https://www.raspberrypi.org/forums/viewtopic.php?t=280530 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174391] New: /lib/firmware update causes Dell 7300 to hang on boot after loading initrd ramdisk
by bugzilla_noreply＠suse.com 26 Jul '20

26 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174391 Bug ID: 1174391 Summary: /lib/firmware update causes Dell 7300 to hang on boot after loading initrd ramdisk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: janm2(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: Hi, last Saturday 16.07. I did "zypper dup" on my Tumbleweed Dell Latitude 7300 laptop and rebooted. The laptop froze directly after the messages "Loading kernel 5.7.7, Loading Ramdisk". Booting from the earlier kernel version 5.7.5 worked once in recovery mode but on a second attempt (and running mkinitrd) not either anymore. Booting from any older read-only snapshot did not help either (could my snapshotting set-up be broken/incomplete here??). I was pretty desperate. Then I realized that it could be something with UEFI secure boot and disabled secure boot. Then I chrooted into my broken Tumbleweed installation with a life cd. Next restored /lib/firmware directly directly from an older snapshot (the older fire versions were there). Rebooted. Works again - without secureboot with older firmware. So for now I can work again. But I want to inform to spare others from this desperation ... and eventually to get a fix to the firmware packages. Best regards, Jan Reproducible: Always Steps to Reproduce: 1.update to latest firmware packages 2.reboot Actual Results: Grub2 bootloader starts normally Computer freezes after message "Loading Ramdisk" Newly installed and not working firmware versions: kernel-firmware-intel-20200702-1.1.noarch kernel-firmware-nvidia-20200702-1.1.noarch kernel-firmware-realtek-20200702-1.1.noarch ... all further firmwares have same rpm version for standard tumbleweed kernel 5.7.7-1-default 64bit Some general information on my Dell Latitude 7300 Laptop Intel Coffee Lake is the Chipset, I believe >>:~ # lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:15.3 Serial bus controller [0c80]: Intel Corporation Device 9deb (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:19.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Host Controller (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device 9db3 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 02:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 02:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 02:02.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 03:00.0 System peripheral: Intel Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 05:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 05:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 06:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06) 39:00.0 USB controller: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] (rev 02) 3a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3b:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 >>:~ # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 006 Device 004: ID 05e3:0612 Genesys Logic, Inc. Hub Bus 006 Device 003: ID 0bda:0413 Realtek Semiconductor Corp. Bus 006 Device 002: ID 0bda:0487 Realtek Semiconductor Corp. Dell dock Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 004: ID 413c:b06e Dell Computer Corp. Bus 005 Device 011: ID 413c:b06f Dell Computer Corp. Bus 005 Device 010: ID 0bda:402e Realtek Semiconductor Corp. Bus 005 Device 008: ID 0b0e:0300 GN Netcom Dell dock Bus 005 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 005 Device 003: ID 0bda:5413 Realtek Semiconductor Corp. Bus 005 Device 002: ID 0bda:5487 Realtek Semiconductor Corp. Dell dock Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 413c:81d7 Dell Computer Corp. DW5821e Snapdragon X20 LTE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0a5c:5843 Broadcom Corp. 58200 Bus 001 Device 002: ID 1bcf:28c4 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You are receiving this mail because: You are the assignee for the bug.

1 2

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

26 Jul '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! Raise default file descriptor limits to meet Valve Proton requirements -> http://bugzilla.suse.com/show_bug.cgi?id=1107525 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 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 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 Many usb errors while booting: device descriptor read/8, error -71 -> http://bugzilla.suse.com/show_bug.cgi?id=1165173 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 ACPI BIOS Error (bug) -> http://bugzilla.suse.com/show_bug.cgi?id=1167305 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 kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode -> http://bugzilla.suse.com/show_bug.cgi?id=1172670 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 zypper dup from 15.1 shows mok screen on reboot -> http://bugzilla.suse.com/show_bug.cgi?id=1173115 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 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 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS -> http://bugzilla.suse.com/show_bug.cgi?id=1173819 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 -- 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 1174492] oracle Virtualbox 6.1 : I can install on 15.1 but not on 15.2
by bugzilla_noreply＠suse.com 26 Jul '20

26 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1174492 https://bugzilla.suse.com/show_bug.cgi?id=1174492#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcdole(a)free.fr, | |tiwai(a)suse.com Flags| |needinfo?(jcdole(a)free.fr) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Are you using Secure Boot? If yes, that's the likely problem. If yes, try to turn it off in BIOS, or you'd have to sign your module by yourself. -- You are receiving this mail because: You are the assignee for the bug.

1 0