unable to boot with kernel 5.7

English Install/Boot/Login
1

Hi everybody,

this issue looks like some others posted yesterday, but not exactly so I open a new thread.

Since last update (yesterday night, previous one was ~2 days ago) booting time is very long, but it does’nt end up with a functional graphic interface. Login screen is displayed more than once. NumLock key indicator is not coherent, task bar won’t show up, etc…
I have no Nvidia card, nor WiFi, which seemed to create conflicts as reported in other threads.

When I boot with previous kernel (5.6.14-1) everything works fine as usually.

Here is the output of journalctl -b -p 0…4 (got from CLI after booting with kernel 5.7.1-1) :

https://pastebin.com/raw/Y0Qep4XS

My config :

  • Tumbleweed 20200615
  • KDE Plasma 5.19.0
  • Mesa DRI Intel HD Graphics
  • issue appears with kernel 5.7.1-1

I’d be glad to read your advice, thanks in advance.

Erik

2

Upgrade your kernel. 5.7.2 hit the mirrors on Friday (my local time). I suggest to boot the 5.6.14 kernel, remove the 5.7.1 kernel, then install the 5.7.2 kernel. That way you don’t need worry that your default zypper configuration would remove your working old kernel on installation of a newer one that also might not boot.

3

Thanks for your reply and OK, I’ll wait for 5.7.2 to appear on Friday at zypper dup and install it. I didn’t remove 5.7.1 because I’m not sure to do it correctly but I changed multiversion.kernels option in my /etc/zypper/zypp.conf that way :

multiversion.kernels = latest,latest-1,latest-2,running,5.6.14-1.6

which might provide a triple safety since 5.6 will be the running kernel, the latest-2 and is namely specified …:\ What would you say about it ?

(Besides that, it’s the first time I encounter such an issue with a new kernel - is it a bug, or does the problem come from my system / config / hardware ???)

4

It could be either. To find out would at least require some information about your hardware, but probably needs confirmation from others with similar hardware, or filing a new bug if a matching existing one could not be found. Output from the following (enclosed using code tags) should provide most of what we would need to know:

inxi -bxx

5.7.2 is already available on the mirrors via zypper dup. By Friday there could be an even newer version, since 5.7.3 has already been released upstream.

5

Here is the output from inxi -bxx :

System:    Host: linux-5n3o Kernel: 5.6.14-1-default x86_64 bits: 64 compiler: gcc v: 10.1.1 Console: tty 1 dm: SDDM 
           Distro: openSUSE Tumbleweed 20200615 
Machine:   Type: Desktop System: MSI product: MS-7817 v: 2.0 serial: N/A 
           Mobo: MSI model: B85M-E45 (MS-7817) v: 2.0 serial: N/A UEFI: American Megatrends v: 10.4 date: 02/20/2014 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: 4055-88-56-8f-de charge: 55% (should be ignored) 
           status: Discharging 
CPU:       Dual Core: Intel Pentium G3220 type: MCP arch: Haswell speed: 800 MHz min/max: 800/3000 MHz 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Micro-Star MSI driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0402 
           Display: server: X.org 1.20.8 compositor: kwin_x11 driver: modesetting unloaded: fbdev,vesa alternate: intel 
           tty: 137x35 
           Message: Advanced graphics data unavailable in console for root. 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
           port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 
Drives:    Local Storage: total: 2.11 TiB used: 636.71 GiB (29.5%) 
Info:      Processes: 265 Uptime: 8h 26m Memory: 7.63 GiB used: 4.39 GiB (57.6%) Init: systemd v: 245 runlevel: 5 
           target: graphical.target Compilers: gcc: 10.1.1 alt: 10/9 Shell: bash v: 5.0.17 running in: tty 1 inxi: 3.1.00

Thanks for your help.

6

For Tumbleweed, I use:

multiversion.kernels = oldest,latest,latest-1

That kept me a known working 5.5 kernel as a fall back. However, 5.7.1 booted without problems here. So I removed the older 5.5 kernel. And now the oldest is a 5.6 kernel. I’ll keep that around until there is a successful boot with a 5.8 kernel.

To remove an older kernel, I use Yast, and search for “kernel”. Then I use the “Versions” tab to find the version that I wish to remove. There may also be a “kernel-default-devel”, “kernel-devel” of the same version to remove (if you install those. And I guess there’s a kernel source, but I have been installing kernel sources.

7

Not a whole lot of difference between OP’s MSI that doesn’t boot 5.7, and my Asus that does:

# inxi -SMCNxx
System:    Host: ab85m **Kernel: 5.7.1**-1-default x86_64 bits: 64 compiler: gcc v: 10.1.1 Desktop: Trinity R14.0.8 tk: Qt 3.5.0
           wm: Twin dm: TDM Distro: openSUSE **Tumbleweed 20200615**
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
           Mobo: ASUSTeK model: **B85M**-E v: Rev X.0x serial: MB-1234567890 UEFI: American Megatrends v: 3602 date: 04/04/2018
CPU:       Topology: Dual Core model: Intel **Pentium G3220** bits: 64 type: MCP arch: Haswell rev: 3 L1 cache: 128 KiB
           L2 cache: 3072 KiB L3 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 11972
           Speed: 898 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 898 2: 898
Network:   Device-1: **Realtek RTL8111/8168/8411** PCI Express Gigabit Ethernet vendor: ASUSTeK P8 series **driver: r8169** v: kernel
           port: e000 bus ID: 03:00.0 chip ID: 10ec:8168

I see 5.7.2 disappeared from the mirrors. :stuck_out_tongue:

8

I hadn’t noticed the ‘oldest’ options. That’s what I need.

Got it.
Thanks!

9

So harware is maybe not the key.
I’m still waiting for the new kernel, for now it does’nt appear in available updates, so I delayed them.

10

The update of tumbleweed of last week Friday, ruined my system (Dell Inspiron 15)
Tried to reinstall also failed booting.
Then I installed Leap 15.1. Worked until I updated to last state. And then also failed.
tried Ubuntu and fedora to see if my hardware failed. But they run well.
Seems a grub2 EFI problem, but I can not find the issue.

Co incident, my other computer (Desktop) had at the same tumbleweed update a file system reducing it self from 900+ G to 8G. Only this system runs well after a reinstall.

11

It seems unlikely that this would be a grub2 EFI problem. There’s been very little change in grub2 and EFI support throughout the life of Leap 15.1.

12

I have also been having issues with the 5.7.1 Kernel since the update on my Lenovo Legion Y730 laptop with Tumbleweed and now even when using wifi with the fallback 7.6.14. The problem seems to be with the iwlwifi kernel driver and my Intel AC 9560 wireless card. With wifi enabled in BIOS I cannot boot into 5.7.1, being blocked by an infinite workqueue error loop. If I disable wifi then everything works fine, except that I do not have internet connection which I need. I originally circumvented this problem by simply booting into 5.6.14, but after the latest update, which I believe updated iwlwifi, I get the following error from dmesg roughly every 10 seconds or whenever there is an attempt at establishing a connection.

  642.278830] iwlwifi 0000:00:14.3**: Collecting data: trigger 2 fired.**
  642.278833] ieee80211 phy0: Hardware restart was requested
  645.455955] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
  645.571206] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
  645.637023] iwlwifi 0000:00:14.3**: FW already configured (0) - re-configuring**
  823.268382] iwlwifi 0000:00:14.3: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [13, 27] HW [13, 27] FH TRB=0x0c010a01a
  823.268544] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
  823.268897] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
  823.268898] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
  823.268900] iwlwifi 0000:00:14.3: Loaded firmware version: 46.8902351f.0 9000-pu-b0-jf-b0-46.ucode
  823.268901] iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
  823.268902] iwlwifi 0000:00:14.3: 0x000028B7 | trm_hw_status0
  823.268903] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
  823.268904] iwlwifi 0000:00:14.3: 0x0048865E | branchlink2
  823.268905] iwlwifi 0000:00:14.3: 0x00478C5A | interruptlink1
  823.268906] iwlwifi 0000:00:14.3: 0x00006BD8 | interruptlink2
  823.268907] iwlwifi 0000:00:14.3: 0x0000CE22 | data1
  823.268907] iwlwifi 0000:00:14.3: 0xFF000000 | data2
  823.268908] iwlwifi 0000:00:14.3: 0xF0000008 | data3
  823.268909] iwlwifi 0000:00:14.3: 0xB1C01D92 | beacon time
  823.268910] iwlwifi 0000:00:14.3: 0xC414E23B | tsf low
  823.268911] iwlwifi 0000:00:14.3: 0x0000003C | tsf hi
  823.268912] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
  823.268913] iwlwifi 0000:00:14.3: 0x0A96DAA3 | time gp2
  823.268914] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
  823.268915] iwlwifi 0000:00:14.3: 0x0000002E | uCode version major
  823.268916] iwlwifi 0000:00:14.3: 0x8902351F | uCode version minor
  823.268917] iwlwifi 0000:00:14.3: 0x00000312 | hw version
  823.268917] iwlwifi 0000:00:14.3: 0x00C89008 | board version
  823.268918] iwlwifi 0000:00:14.3: 0x0A0D001C | hcmd
  823.268919] iwlwifi 0000:00:14.3: 0xA6F22002 | isr0
  823.268920] iwlwifi 0000:00:14.3: 0x01000000 | isr1
  823.268921] iwlwifi 0000:00:14.3: 0x08001802 | isr2
  823.268922] iwlwifi 0000:00:14.3: 0x40402088 | isr3
  823.268923] iwlwifi 0000:00:14.3: 0x00000000 | isr4
  823.268923] iwlwifi 0000:00:14.3: 0x004E019C | last cmd Id
  823.268924] iwlwifi 0000:00:14.3: 0x0000CE22 | wait_event
  823.268925] iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
  823.268926] iwlwifi 0000:00:14.3: 0x00450034 | l2p_duration
  823.268927] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
  823.268928] iwlwifi 0000:00:14.3: 0x00000080 | l2p_addr_match
  823.268929] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel
  823.268930] iwlwifi 0000:00:14.3: 0x02052033 | timestamp
  823.268931] iwlwifi 0000:00:14.3: 0x0000D860 | flow_handler
  823.269069] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
  823.269070] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
  823.269071] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
  823.269072] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
  823.269073] iwlwifi 0000:00:14.3: 0xC0088BAA | umac branchlink2
  823.269074] iwlwifi 0000:00:14.3: 0xC0084448 | umac interruptlink1
  823.269075] iwlwifi 0000:00:14.3: 0xC0084448 | umac interruptlink2
  823.269076] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
  823.269077] iwlwifi 0000:00:14.3: 0xC0084448 | umac data2
  823.269077] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
  823.269078] iwlwifi 0000:00:14.3: 0x0000002E | umac major
  823.269079] iwlwifi 0000:00:14.3: 0x8902351F | umac minor
  823.269080] iwlwifi 0000:00:14.3: 0x0A96DA91 | frame pointer
  823.269081] iwlwifi 0000:00:14.3: 0xC088627C | stack pointer
  823.269082] iwlwifi 0000:00:14.3: 0x004E019C | last host cmd
  823.269083] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
  823.269098] iwlwifi 0000:00:14.3: Fseq Registers:
  823.269107] iwlwifi 0000:00:14.3: 0xE9D905C9 | FSEQ_ERROR_CODE
  823.269115] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
  823.269123] iwlwifi 0000:00:14.3: 0x829DC2D7 | FSEQ_CNVIO_INIT_VERSION
  823.269132] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
  823.269140] iwlwifi 0000:00:14.3: 0x7134294E | FSEQ_TOP_CONTENT_VERSION
  823.269148] iwlwifi 0000:00:14.3: 0x86ADC286 | FSEQ_ALIVE_TOKEN
  823.269157] iwlwifi 0000:00:14.3: 0x95C2DBA0 | FSEQ_CNVI_ID
  823.269165] iwlwifi 0000:00:14.3: 0x08A8C403 | FSEQ_CNVR_ID
  823.269173] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  823.269184] iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  823.269195] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  823.269236] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR

It seems to be restarting the network card repeatedly. When this occurs the computer freezes for a couple seconds, though despite this I do somehow have a connection that works for the split second after this reset, before seemingly failing again until the next reset. Strangely, during some reboots into 7.6.14 this error does not occur once and the computer functions perfectly as before with uninterrupted internet connection.

Can anyone tell me when the next kernel or iwlwifi update will be released or where I can find the schedule of updates for Tumbleweed?

13

That’s pretty much what others are reporting with the 5.7.1 kernel.

As far as I know, the Tumbleweed “release schedule” depends on what passes openQA testing. They are possibly holding back kernel updates until they are sure this problem is solved.

I do have a laptop with iwlwifi, but it is usually running Leap 15.2. I have not yet upgraded Tumbleweed on that system to kernel 5.7.1. I expect to update Tumbleweed there on Saturday (June 27th), and I guess I will find out whether there are kernel problems at that time.

14

My system would boot, but X wouldn’t run at all. I deleted that kernel and returned to 5.6.14-1-default Here is my inix output:


System:    Host: localhost.localdomain Kernel: 5.6.14-1-default x86_64 bits: 64 compiler: gcc v: 10.1.1 Console: tty 1 
           dm: SDDM Distro: openSUSE Tumbleweed 20200620 
Machine:   Type: Laptop System: LENOVO product: 80XV v: Lenovo ideapad 320-15AST serial: PF0VMDZA Chassis: type: 10 
           v: Lenovo ideapad 320-15AST serial: PF0VMDZA 
           Mobo: LENOVO model: LNVNB161216 v: SDK0J40700WIN serial: PF0VMDZA UEFI: LENOVO v: 5PCN24WW date: 10/29/2018 
Battery:   ID-1: BAT0 charge: 18.8 Wh condition: 18.8/30.0 Wh (63%) volts: 8.5/7.5 model: SMP L16M2PB1 serial: 25940 
           status: Full 
CPU:       Dual Core: AMD A6-9220 RADEON R4 5 COMPUTE CORES 2C+3G type: MCP arch: Excavator speed: 1458 MHz 
           min/max: 1300/2500 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] vendor: Lenovo driver: amdgpu 
           v: kernel bus ID: 00:01.0 chip ID: 1002:98e4 
           Device-2: Acer type: USB driver: uvcvideo bus ID: 1-1.3:4 chip ID: 5986:1127 
           Display: server: X.org 1.20.8 compositor: kwin_x11 driver: amdgpu FAILED: ati unloaded: fbdev,modesetting,vesa 
           tty: 191x44 
           Message: Advanced graphics data unavailable in console for root. 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo driver: ath10k_pci v: kernel 
           port: 2100 bus ID: 01:00.0 chip ID: 168c:0042 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Lenovo driver: r8169 v: kernel port: 1000 
           bus ID: 02:00.0 chip ID: 10ec:8136 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-1.2:3 chip ID: 0cf3:e500 
Drives:    Local Storage: total: 931.51 GiB used: 40.80 GiB (4.4%) 
Info:      Processes: 190 Uptime: 2h 54m Memory: 7.17 GiB used: 1.98 GiB (27.6%) Init: systemd v: 245 runlevel: 5 
           target: graphical.target Compilers: gcc: 10.1.1 alt: 10 Shell: bash v: 5.0.17 running in: tty 1 inxi: 3.1.00
15

Checking back in to report that after updating to kernel 5.7.2-1-default (along with the iwlwifi update) everything seems to be working smoothly again on my Lenovo.

16

I take it back I am still receiving a very similar if not identical error with my wifi, resulting awful connectivity. At least it boots.

 4750.575335] iwlwifi 0000:00:14.3**: WRT: Collecting data: ini trigger 4 fired.**
 4750.575338] ieee80211 phy0: Hardware restart was requested
 4798.706013] iwlwifi 0000:00:14.3: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [106, 143] HW [106, 143] FH TRB=0x0c010a079
 4798.706146] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
 4798.706500] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
 4798.706501] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
 4798.706502] iwlwifi 0000:00:14.3: Loaded firmware version: 46.8902351f.0 9000-pu-b0-jf-b0-46.ucode
 4798.706503] iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN        
 4798.706504] iwlwifi 0000:00:14.3: 0x00002AF0 | trm_hw_status0
 4798.706504] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
 4798.706505] iwlwifi 0000:00:14.3: 0x0048865E | branchlink2
 4798.706506] iwlwifi 0000:00:14.3: 0x00478C5A | interruptlink1
 4798.706506] iwlwifi 0000:00:14.3: 0x00006BD8 | interruptlink2
 4798.706507] iwlwifi 0000:00:14.3: 0x0001ADA2 | data1
 4798.706508] iwlwifi 0000:00:14.3: 0xFF000000 | data2
 4798.706508] iwlwifi 0000:00:14.3: 0xF0000008 | data3
 4798.706509] iwlwifi 0000:00:14.3: 0x70C03070 | beacon time
 4798.706510] iwlwifi 0000:00:14.3: 0xE8B55F5E | tsf low
 4798.706510] iwlwifi 0000:00:14.3: 0x0000006D | tsf hi
 4798.706511] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
 4798.706511] iwlwifi 0000:00:14.3: 0x02BFAC93 | time gp2
 4798.706512] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
 4798.706513] iwlwifi 0000:00:14.3: 0x0000002E | uCode version major
 4798.706514] iwlwifi 0000:00:14.3: 0x8902351F | uCode version minor
 4798.706514] iwlwifi 0000:00:14.3: 0x00000312 | hw version
 4798.706515] iwlwifi 0000:00:14.3: 0x00C89008 | board version
 4798.706515] iwlwifi 0000:00:14.3: 0x0A6A001C | hcmd
 4798.706516] iwlwifi 0000:00:14.3: 0x8002200A | isr0
 4798.706517] iwlwifi 0000:00:14.3: 0x00000000 | isr1
 4798.706517] iwlwifi 0000:00:14.3: 0x08001802 | isr2
 4798.706518] iwlwifi 0000:00:14.3: 0x004179C8 | isr3
 4798.706519] iwlwifi 0000:00:14.3: 0x00000000 | isr4
 4798.706519] iwlwifi 0000:00:14.3: 0x809DFB03 | last cmd Id
 4798.706520] iwlwifi 0000:00:14.3: 0x0001ADA2 | wait_event
 4798.706521] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
 4798.706521] iwlwifi 0000:00:14.3: 0x00000020 | l2p_duration
 4798.706522] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
 4798.706523] iwlwifi 0000:00:14.3: 0x00000081 | l2p_addr_match
 4798.706523] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel
 4798.706524] iwlwifi 0000:00:14.3: 0x02052033 | timestamp
 4798.706525] iwlwifi 0000:00:14.3: 0x0000C080 | flow_handler
 4798.706664] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
 4798.706666] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
 4798.706667] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
 4798.706667] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
 4798.706668] iwlwifi 0000:00:14.3: 0xC0088BAA | umac branchlink2
 4798.706669] iwlwifi 0000:00:14.3: 0xC0084448 | umac interruptlink1
 4798.706670] iwlwifi 0000:00:14.3: 0xC0084448 | umac interruptlink2
 4798.706670] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
 4798.706671] iwlwifi 0000:00:14.3: 0xC0084448 | umac data2
 4798.706671] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
 4798.706672] iwlwifi 0000:00:14.3: 0x0000002E | umac major
 4798.706673] iwlwifi 0000:00:14.3: 0x8902351F | umac minor
 4798.706673] iwlwifi 0000:00:14.3: 0x02BFAC81 | frame pointer
 4798.706674] iwlwifi 0000:00:14.3: 0xC088627C | stack pointer
 4798.706675] iwlwifi 0000:00:14.3: 0x0088010D | last host cmd
 4798.706675] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
 4798.706691] iwlwifi 0000:00:14.3: Fseq Registers:
 4798.706700] iwlwifi 0000:00:14.3: 0xE9D985C9 | FSEQ_ERROR_CODE
 4798.706708] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
 4798.706717] iwlwifi 0000:00:14.3: 0x829FC2D7 | FSEQ_CNVIO_INIT_VERSION
 4798.706725] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
 4798.706733] iwlwifi 0000:00:14.3: 0x7134214E | FSEQ_TOP_CONTENT_VERSION
 4798.706742] iwlwifi 0000:00:14.3: 0x86AD8206 | FSEQ_ALIVE_TOKEN
 4798.706750] iwlwifi 0000:00:14.3: 0x93C3DB20 | FSEQ_CNVI_ID
 4798.706758] iwlwifi 0000:00:14.3: 0x08A8C503 | FSEQ_CNVR_ID
 4798.706767] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
 4798.706777] iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
 4798.706788] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
 4798.706829] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
17

It goes far beyond the scope of user-to-user forum. You may try posting it in Wireless subforum in case some guru happens to notice it, but as 203277 – iwlwifi 8265 Microcode SW error detected (queue stuck) demonstrates, it can be caused by environmental conditions and you need actual firmware dump and firmware developer to investigate it. And no, I do not claim you have the same issue, just that we have no chance to determine it.

18

So far, 5.7.2-1-default and X are running fine. Thanks for kernel fix.

19

Thanks for the tip. I’m sorry to derail this thread with my firmware issue. I managed to mitigate the problem for now by disabling 802.11n in /etc/modprobe.d/iwlwifi.conf per this article. It is a good enough solution for now. I hope this may help anyone else with an Intel wifi card having similar issues.

20

Hi everybody,
seems like except special hardware issues, 5.7 kernels (at least >= 5.2) are working fine. Unfortunately this is not my case. :X

5.7.2 still leaves me with a messed up GUI, where I only have 1 desktop window with all the windows on it, and trying to switch to another one simply displays another window on top ; trying to close it has no effect, there is no task bar, it is replaced with a duplicated bar from firefox, etc…

I tried to boot from a live dvd (20200626) : black screen. When I boot in failsafe option, I end up with a CLI screen which displays :

kernel 5.7.5-1 default
localhost login:    123.931364] snd_hda_intel 000:00:03:0 : HSW/BDW HD-audio HDMI/DP requires binding with gfx driver

Any idea about it anybody ?

Système d’exploitation : openSUSE Tumbleweed 20200622
Version de KDE Plasma : 5.19.1
Version de KDE Frameworks : 5.71.0
Version de Qt : 5.15.0
Version de noyau : 5.6.14-1-default
Type de système d’exploitation : 64-bit
Processeurs : 2 × Intel® Pentium® CPU G3220 @ 3.00GHz
Mémoire : 7,6 Gio de mémoire vive
Processeur graphique : Mesa DRI Intel® HD Graphics