July 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188238] [RPi 3 B+] bluetooth command tx timeout and reset failure
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

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

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c28 --- Comment #28 from Mathew McBride <matt(a)traverse.com.au> --- Created attachment 850952 --> https://bugzilla.suse.com/attachment.cgi?id=850952&action=edit Full console bootlog (incl. dmesg), nvme driver enabled and crashes This is the full serial console boot log, including dmesg and the nvme related panic. The system was booted from USB but still 'stalls' in initramfs due to the nvme panic. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188238] New: [RPi 3 B+] bluetooth command tx timeout and reset failure
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188238 Bug ID: 1188238 Summary: [RPi 3 B+] bluetooth command tx timeout and reset failure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://openqa.opensuse.org/tests/1833322/modules/jour nal_check/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, guillaume.gardet(a)arm.com Found By: openQA Blocker: No Created attachment 850945 --> http://bugzilla.opensuse.org/attachment.cgi?id=850945&action=edit journal While booting Leap15.3 on RPi (generalhw openQA backend), journal_check test case has found following bluetooth issues. The system continues without boot other issues. ``` Apr 29 12:01:16.090128 localhost kernel: Bluetooth: Core ver 2.22 Apr 29 12:01:16.090643 localhost kernel: NET: Registered protocol family 31 Apr 29 12:01:16.090878 localhost kernel: Bluetooth: HCI device and connection manager initialized Apr 29 12:01:16.091083 localhost kernel: Bluetooth: HCI socket layer initialized Apr 29 12:01:16.091296 localhost kernel: Bluetooth: L2CAP socket layer initialized Apr 29 12:01:16.091492 localhost kernel: Bluetooth: SCO socket layer initialized Apr 29 12:01:16.230101 localhost kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Apr 29 12:01:16.230678 localhost kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Apr 29 12:01:16.350088 localhost kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Apr 29 12:01:16.351692 localhost kernel: cfg80211: failed to load regulatory.db Apr 29 12:01:16.559444 localhost kernel: Bluetooth: HCI UART driver ver 2.3 Apr 29 12:01:16.560201 localhost kernel: Bluetooth: HCI UART protocol H4 registered Apr 29 12:01:16.560497 localhost kernel: Bluetooth: HCI UART protocol BCSP registered Apr 29 12:01:16.560724 localhost kernel: Bluetooth: HCI UART protocol LL registered Apr 29 12:01:16.560934 localhost kernel: Bluetooth: HCI UART protocol ATH3K registered Apr 29 12:01:16.561193 localhost kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered Apr 29 12:01:16.561414 localhost kernel: Bluetooth: HCI UART protocol Intel registered Apr 29 12:01:16.810140 localhost kernel: Bluetooth: HCI UART protocol Broadcom registered Apr 29 12:01:16.810777 localhost kernel: Bluetooth: HCI UART protocol QCA registered Apr 29 12:01:16.811053 localhost kernel: Bluetooth: HCI UART protocol AG6XX registered Apr 29 12:01:16.811272 localhost kernel: Bluetooth: HCI UART protocol Marvell registered Apr 29 12:01:18.880097 localhost kernel: Bluetooth: hci0: command 0x0c03 tx timeout Apr 29 12:01:26.970221 localhost kernel: Bluetooth: hci0: BCM: Reset failed (-110) ``` Tested image: openSUSE-Leap-15.3-ARM-JeOS-raspberrypi.aarch64-2021.05.31-Build9.126.raw.xz kernel: Linux version 5.3.18-59.10-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Fri Jun 25 12:36:56 UTC 2021 (6856d31) Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 efi: EFI v2.80 by Das U-Boot Kernel command line: BOOT_IMAGE=/boot/Image-5.3.18-59.10-default root=UUID=e26a6cb2-0e27-453f-b1cc-17a7efd495ba rw loglevel=3 splash=silent plymouth.enable=0 console=ttyS0,115200n8 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188237] New: [RPi 3 B+] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188237 Bug ID: 1188237 Summary: [RPi 3 B+] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://openqa.opensuse.org/tests/1833322/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, guillaume.gardet(a)arm.com Found By: openQA Blocker: No Created attachment 850943 --> http://bugzilla.opensuse.org/attachment.cgi?id=850943&action=edit journal While booting Leap15.3 on RPi (generalhw openQA backend), journal_check test case has found following LAN78XX issue. The system boots successfully with network working. ``` Apr 29 12:01:16.561627 localhost kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed Apr 29 12:01:16.561627 localhost kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed. Apr 29 12:01:16.911933 localhost kernel: usbcore: registered new interface driver lan78xx Apr 29 12:01:19.870072 localhost kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped ``` Seems like the issue has been reported and closed in upstream already https://github.com/raspberrypi/linux/issues/2447, but the problem still persists Tested image: openSUSE-Leap-15.3-ARM-JeOS-raspberrypi.aarch64-2021.05.31-Build9.126.raw.xz kernel: Linux version 5.3.18-59.10-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Fri Jun 25 12:36:56 UTC 2021 (6856d31) Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 efi: EFI v2.80 by Das U-Boot Kernel command line: BOOT_IMAGE=/boot/Image-5.3.18-59.10-default root=UUID=e26a6cb2-0e27-453f-b1cc-17a7efd495ba rw loglevel=3 splash=silent plymouth.enable=0 console=ttyS0,115200n8 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c27 --- Comment #27 from Joerg Roedel <jroedel(a)suse.com> --- Thanks for providing the lspci output files. Unfortunately they don't explain the errors happening, the only differences in the PCI configuration are because the name driver is not loaded on the broken kernel. The full boot log of the broken kernel might be helpful. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188187] Running any type of web-content clocks the CPU
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188187 https://bugzilla.suse.com/show_bug.cgi?id=1188187#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |latinovicne(a)gmail.com Flags| |needinfo?(latinovicne@gmail | |.com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Yes, please retest without nomodeset. The nomodeset flag means that the system is without the native graphics, i.e. with UEFI frame buffer, which is VERY slow. And we need more details about your system. Please boot without nomodeset, run hwinfo, and upload the output to Bugzilla. Also, please give the output of dmesg, too. And, please specify which desktop you're using: is it with X11 or Wayland? Last but not least, if it's X11, it might be worth to try to uninstall xf86-video-amdgpu once. Then it'll switch to modesetting driver. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188106] kernel 5.13.0 no audio - snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x200f0000
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188106 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gitlab.freedesktop. | |org/drm/intel/-/issues/3762 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c13 --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- FWIW works for me: > [ 0.000000] Linux version 5.13.1-21.g72aabc2-default (geeko@buildhost) (gcc (SUSE Linux) 11.1.1 20210625 [revision 62bbb113ae68a7e724255e17143520735bcb9ec9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Mon Jul 12 06:35:58 UTC 2021 (72aabc2) > [ 0.018709] Secure boot enabled -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 13 Jul '21

13 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Frank Kr�ger from comment #11) > (In reply to Jiri Slaby from comment #10) > > (In reply to Yan Huang from comment #9) > > > I re-checked the system logs on my laptop and can confirm that > > > - 5.13.0-4.gaa40472 was the last Kernel:stable kernel that could > > > successfully boot with Secure Boot enabled > > > - the issue indeed started with 5.13.0-5.1.g9140415 > > > > This range contains exactly the commit I reverted. But 5.13.1-3.1.gbebf622 > > contains the revert already and still causes the trouble... I am lost. > > Unfortunately, kernel-default-5.13.1-3.1.gbebf622.x86_64 does not boot > either, as alreday confirmed by comment #8. Sorry, my fault: gbebf622 does not contain the revert yet! g72aabc28 or gb6ab3de do. Look for 'Revert "UsrMerge the kernel (boo#1184804)"' in the changelog. But it's currently building yet, so you have to wait until it is finished. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 Frank Kr�ger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fkrueger@mailbox. | |org) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c11 --- Comment #11 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Jiri Slaby from comment #10) > (In reply to Yan Huang from comment #9) > > I re-checked the system logs on my laptop and can confirm that > > - 5.13.0-4.gaa40472 was the last Kernel:stable kernel that could > > successfully boot with Secure Boot enabled > > - the issue indeed started with 5.13.0-5.1.g9140415 > > This range contains exactly the commit I reverted. But 5.13.1-3.1.gbebf622 > contains the revert already and still causes the trouble... I am lost. Unfortunately, kernel-default-5.13.1-3.1.gbebf622.x86_64 does not boot either, as alreday confirmed by comment #8. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c34 --- Comment #34 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Jiri Slaby from comment #33) > (In reply to Michal Suchanek from comment #32) > > Sorry, there is no way to detect usrmerge. It has been asked for in the > > usrmerge thread and it was rejected. > > Maybe it's time to reconsider? (I don't know the details, nor I know what > msg/thread this was.) I also support for having some usable and reasonable rpm condition to check UsrMerge. e.g. we'd want to have a check in kernel-firmware package. Already it has bitten lots of people and reported as bugs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c33 --- Comment #33 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Suchanek from comment #32) > Sorry, there is no way to detect usrmerge. It has been asked for in the > usrmerge thread and it was rejected. Maybe it's time to reconsider? (I don't know the details, nor I know what msg/thread this was.) > On Leap I see > > suse-release = 15.3-lp153.146.1 > > which is arguably > 15 > > On TW there is > > suse-release = 20210606-1005.1 > > so if you wanted a hack > > %if %usrmerged > Requires: suse-release > 16 > %endif > > might work Yeah, that's weird. I'd assumed to do it the same thing we are doing for cross-distribution ifs where TW check is: %if 0%{?suse_version} > 1500 All this is mess :/. *-product could provide /usr/merged for usrmerged releases. And Kernel would just do the %if above and "Requires: /usr/merged" in it. BTW, it looks like (maybe) pesign-obs-integration is broken by this change too (bug 1188142). All this has to be resolved before I revert the revert I did in the morning... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187589] No sound device detected on Pinebook Pro, stock TW install
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187589 http://bugzilla.opensuse.org/show_bug.cgi?id=1187589#c6 --- Comment #6 from Jonas del Campo <jonasdcdm(a)mailbox.org> --- Created attachment 850935 --> http://bugzilla.opensuse.org/attachment.cgi?id=850935&action=edit Dmesg's output with debug flag and test kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187589] No sound device detected on Pinebook Pro, stock TW install
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187589 http://bugzilla.opensuse.org/show_bug.cgi?id=1187589#c5 --- Comment #5 from Jonas del Campo <jonasdcdm(a)mailbox.org> --- First of all sorry for not mentioning that I'm using Tow-Boot, flashed to the SPI of my PBP. I think this has some implications for the tests I could do. With your test kernel I could no longer get graphics past GRUB. I remembered that Tow-Boot uses a different devicetree, I believe this one: https://source.denx.de/u-boot/u-boot/-/blob/v2021.04/arch/arm/dts/rk3399-pi… Once I used openSUSE's dtb in GRUB, I could boot with your kernel. I no longer have graphics (I'll have to open another issue for that later), but I can see devices with alsamixer, which wasn't possible before. I couldn't try if sound worked because of no graphical desktop, but this is progress. There is still the same IRQ error however. I'm attaching the dmesg after booting with your kernel and the debug flag. I also used the flag fbcon=map:1 to try to get graphics, but it didn't have any effect, the rest is default. Thanks for your time and help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c10 --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Yan Huang from comment #9) > I re-checked the system logs on my laptop and can confirm that > - 5.13.0-4.gaa40472 was the last Kernel:stable kernel that could > successfully boot with Secure Boot enabled > - the issue indeed started with 5.13.0-5.1.g9140415 This range contains exactly the commit I reverted. But 5.13.1-3.1.gbebf622 contains the revert already and still causes the trouble... I am lost. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c9 --- Comment #9 from Yan Huang <yan.huang(a)suse.com> --- I re-checked the system logs on my laptop and can confirm that - 5.13.0-4.gaa40472 was the last Kernel:stable kernel that could successfully boot with Secure Boot enabled - the issue indeed started with 5.13.0-5.1.g9140415 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c8 --- Comment #8 from Yan Huang <yan.huang(a)suse.com> --- (In reply to Jiri Slaby from comment #7) > Is this another usrmerge fallout? Does current (when it builds) work for > you? I've reverted the change this morning. Thanks, Jiri. But the newest Kernel:stable kernel 5.13.1-3.1.gbebf622 (if this one already has the change reverted) still has the issue - at least on my laptop. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c32 --- Comment #32 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Takashi Iwai from comment #31) > (In reply to Jiri Slaby from comment #30) > > So, we should add some sort of dependence to > > Kernel:stable kernels. For example (untested): > > %if UsrMerge > > Requires: suse-release > 15 > > %endif > > A good idea, let's take something like this for avoiding the pitfalls. Sorry, there is no way to detect usrmerge. It has been asked for in the usrmerge thread and it was rejected. On Leap I see suse-release = 15.3-lp153.146.1 which is arguably > 15 On TW there is suse-release = 20210606-1005.1 so if you wanted a hack %if %usrmerged Requires: suse-release > 16 %endif might work -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188142] Kernel 5.13.1 does not boot due to bad shim signature
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188142 https://bugzilla.suse.com/show_bug.cgi?id=1188142#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org Flags| |needinfo?(fkrueger@mailbox. | |org) --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- Is this another usrmerge fallout? Does current (when it builds) work for you? I've reverted the change this morning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188187] Running any type of web-content clocks the CPU
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188187 https://bugzilla.suse.com/show_bug.cgi?id=1188187#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> --- Please try to boot with nomodeset boot option for checking whether it's an issue of the native graphics driver or not. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c26 --- Comment #26 from Mathew McBride <matt(a)traverse.com.au> --- Created attachment 850922 --> https://bugzilla.suse.com/attachment.cgi?id=850922&action=edit "Working" kernel lspci information -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c25 Mathew McBride <matt(a)traverse.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jroedel(a)suse.com) | --- Comment #25 from Mathew McBride <matt(a)traverse.com.au> --- Created attachment 850921 --> https://bugzilla.suse.com/attachment.cgi?id=850921&action=edit "Broken" kernel lspci information -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c31 --- Comment #31 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Jiri Slaby from comment #30) > So, we should add some sort of dependence to > Kernel:stable kernels. For example (untested): > %if UsrMerge > Requires: suse-release > 15 > %endif A good idea, let's take something like this for avoiding the pitfalls. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 12 Jul '21

12 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c30 --- Comment #30 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Takashi Iwai from comment #29) > Just to be sure: are you testing the kernel in OBS Kernel:stable, or in > Kernel:stable:Backport? The repo for installable stable kernels on Leap > systems is the latter one, and the former is only for TW systems. I installed the one from Kernel:stable as usual (following a report in Kernel:stable project comment). So, we should add some sort of dependence to Kernel:stable kernels. For example (untested): %if UsrMerge Requires: suse-release > 15 %endif Kernel:stable:Backport indeed works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0