August 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 26 Aug '21

26 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189773 http://bugzilla.opensuse.org/show_bug.cgi?id=1189773#c4 --- Comment #4 from Thomas Vatter <thomas_vatter(a)web.de> --- (In reply to Andreas Stieger from comment #3) > Provide output of the following commands for both direct connection and > connection via KVM switch > > lsusb > hwinfo --mouse > hwinfo --keyboard That is not possible because there is no keyboard via KVM switch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189762] Kernel 5.3.18-57/59 stuck in early boot on AMD hardware, iommu=soft helps
by bugzilla_noreply＠suse.com 26 Aug '21

26 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189762 https://bugzilla.suse.com/show_bug.cgi?id=1189762#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Possibly it's a hang at AMDGPU, which will of course make things invisible. You can try to pass nomodeset boot option to disable the native graphics. -- 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 26 Aug '21

26 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c108 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #108 from Ludwig Nussel <lnussel(a)suse.com> --- closing. Thanks everyone for your patience! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188729] kernel: socfpga_setup_ocram_self_refresh: Unable to find mmio-sram in dtb
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188729 https://bugzilla.suse.com/show_bug.cgi?id=1188729#c3 --- Comment #3 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra@aarch32-HD24G https://openqa.opensuse.org/tests/1883854 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189773 http://bugzilla.opensuse.org/show_bug.cgi?id=1189773#c3 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger(a)gmx.de, | |thomas_vatter(a)web.de Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|Mouse problem |Keyboard / Mouse do not | |work when connected through | |MT VIKI Auto USB KVM Switch Flags| |needinfo?(thomas_vatter@web | |.de) --- Comment #3 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Provide output of the following commands for both direct connection and connection via KVM switch lsusb hwinfo --mouse hwinfo --keyboard -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189762] Kernel 5.3.18-57/59 stuck in early boot on AMD hardware, iommu=soft helps
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189762 https://bugzilla.suse.com/show_bug.cgi?id=1189762#c3 Joerg Roedel <jroedel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pastas4(a)gmail.com Flags| |needinfo?(pastas4(a)gmail.com | |) --- Comment #3 from Joerg Roedel <jroedel(a)suse.com> --- (In reply to Dainius Masiliunas from comment #1) > After doing a bunch of trial and error with kernel parameters, it turns out > that the culprit is indeed iommu. Obviously the intel_iommu option doesn't > work because this is AMD, but the regular iommu option makes a difference. > It boots to graphical interface with iommu=off (but then the mouse doesn't > work), and it boots correctly (including the mouse) with iommu=soft. No > other iommu options (e.g. iommu=calgary) make any difference. Do you see where it hangs when removing the quiet and splash parameters from the kernel command line? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189733] New: Screen fickers and netwok disconnect when on battrey power on Samsung Chromebook3
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189733 Bug ID: 1189733 Summary: Screen fickers and netwok disconnect when on battrey power on Samsung Chromebook3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: yitzhakbargeva(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Screen fickers and netwok disconnecst when on battrey power on Samsung Chromebook 3 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c20 --- Comment #20 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Javier Llorente from comment #19) > In my case, the whole screen flickers. It could be a different bug. Then it must be a different bug. Can you submit a separate bug report? Please provide "inxi -SGa" again and also dmesg output after some flickering has happened. We might have to file this bug upstream later on, but lets start with an opensuse bug report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189733] Screen fickers and netwok disconnect when on battrey power on Samsung Chromebook3
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189733 https://bugzilla.suse.com/show_bug.cgi?id=1189733#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |yitzhakbargeva(a)gmail.com Flags| |needinfo?(yitzhakbargeva@gm | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Both issues are completely individual, so I'd track only the graphics issue here. As usual, please give either hwinfo output or a reference to that information. Then try to enable the DRM debug via drm.debug=0x1e boot option, boot with the power cable, plug off the power (where flickering starts), then give the kernel log. Please tell us at which timing the power got off in the log. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189762] Kernel 5.3.18-57/59 stuck in early boot on AMD hardware, iommu=soft helps
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189762 https://bugzilla.suse.com/show_bug.cgi?id=1189762#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jroedel(a)suse.com, | |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether the recent upstream works as is? Try the kernel package in OBS Kernel:stable:Backport repo. http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ As the issue seems relevant with AMD IOMMU, adding Joerg to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185744] System hangs at reboot and shutdown, waiting for network
by bugzilla_noreply＠suse.com 25 Aug '21

25 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1185744 https://bugzilla.suse.com/show_bug.cgi?id=1185744#c7 --- Comment #7 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to David Kerkhof from comment #6) > I hoped that after some recent updates the problem would be solved but it's > still there. I could be wrong, but could it not just be a systemd service > wrongly configured or something? It looks to me that while stopping the > system, networkmanager received a start signal and tries to load the wilwifi > again, which has become impossible so far into the shutdown process. > When the whole shutdown process is paused to wait for networkmanager to > finish, it waits endlessly. Ctrl-alt-delete doesn't help, and pressing the > power button to force a poweroff shows a 'waiting for wpasupplicant and > networkmanager to finish'. > On my system that doesn't have a problem I still see the same thing in the > logs about trying to activate the wifi during shutdown, but maybe it doesn't > hang because the processor is faster and just jumps this step? Or because of > a newer wifi chip (also from intel) > Can you upload the output of "journalctl -b" with verbose NetworkManager logs enabled? -- 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 24 Aug '21

24 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c106 --- Comment #106 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #105) > Now resubmitted UsrMerged kernel in sr#913265. ACcepted. Can we close this now? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189207] Webcam not detected in Lenovo Thinkpad T14 gen 1
by bugzilla_noreply＠suse.com 24 Aug '21

24 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189207 https://bugzilla.suse.com/show_bug.cgi?id=1189207#c43 --- Comment #43 from Bonacini <paolabonacini(a)virgilio.it> --- Ok. Thank you for your work -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c19 --- Comment #19 from Javier Llorente <javier(a)opensuse.org> --- (In reply to Patrik Jakobsson from comment #18) > (In reply to Javier Llorente from comment #17) > > Aug 23 17:53:07 lapbook kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A > > FIFO underrun > > FIFO underruns normally cause flickering of the entire screen, and not just > certain windows. Are you sure you're experiencing the same issue as Patrick > Keys are describing? (see the video he attached). In my case, the whole screen flickers. It could be a different bug. > > I don�t know why I have no issues with the KDE Live image since it's the > > same Tumbleweed version (20210820) as the one I have installed and both are > > using the i915 driver. > > That is odd. The only difference is that I have an encrypted /home partition on my laptop's SSD. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] New: iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189596 Bug ID: 1189596 Summary: iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vicente.bolea(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: I am having daily system crashes due to NULL pointer dereference in the iwlwifi module. The system renders unusable afterwards and a hard reboot is needed. My wifi card is: 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Kernel: 5.3.18-59.16-default Reproducible: Sometimes Steps to Reproduce: 1. systemctl restart NetworkManager multiple times seems to trigger this 2. 3. Actual Results: kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Aug 09 20:07:28 linux-oov9 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: #PF: supervisor instruction fetch in kernel mode Aug 09 20:07:28 linux-oov9 kernel: #PF: error_code(0x0010) - not-present page Aug 09 20:07:28 linux-oov9 kernel: PGD 0 P4D 0 Aug 09 20:07:28 linux-oov9 kernel: Oops: 0010 [#2] SMP PTI Aug 09 20:07:28 linux-oov9 kernel: CPU: 6 PID: 1142 Comm: irq/163-iwlwifi Tainted: G D X N 5.3.18-59.16-default #1 SLE15-SP3 Aug 09 20:07:28 linux-oov9 kernel: Hardware name: Dell Inc. Precision 5530/0NFGCT, BIOS 1.20.0 06/07/2021 Aug 09 20:07:28 linux-oov9 kernel: RIP: 0010:0x0 Aug 09 20:07:28 linux-oov9 kernel: Code: Bad RIP value. Aug 09 20:07:28 linux-oov9 kernel: RSP: 0018:ffffa30400defea8 EFLAGS: 00010282 Aug 09 20:07:28 linux-oov9 kernel: RAX: 0000000000000000 RBX: ffff8dff3b6d0000 RCX: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: RDX: ffffa30400defec8 RSI: 0000000000000000 RDI: ffffa30400defec8 Aug 09 20:07:28 linux-oov9 kernel: RBP: ffff8dff3b6d0b84 R08: 0000000000000000 R09: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: R10: 0000000000000000 R11: ffffa30400defb40 R12: ffffffff8ece56e0 Aug 09 20:07:28 linux-oov9 kernel: R13: 0000000000000000 R14: ffff8dff3b6d0001 R15: ffff8dff3b6d0b50 Aug 09 20:07:28 linux-oov9 kernel: FS: 0000000000000000(0000) GS:ffff8dff5c380000(0000) knlGS:0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 09 20:07:28 linux-oov9 kernel: CR2: ffffffffffffffd6 CR3: 000000082fa0a002 CR4: 00000000003706e0 Aug 09 20:07:28 linux-oov9 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Aug 09 20:07:28 linux-oov9 kernel: Call Trace: Aug 09 20:07:28 linux-oov9 kernel: task_work_run+0x87/0xb0 Aug 09 20:07:28 linux-oov9 kernel: do_exit+0x397/0xb80 Aug 09 20:07:28 linux-oov9 kernel: ? irq_thread_check_affinity+0xe0/0xe0 Aug 09 20:07:28 linux-oov9 kernel: ? kthread+0x10d/0x130 Aug 09 20:07:28 linux-oov9 kernel: rewind_stack_do_exit+0x17/0x20 Aug 09 20:07:28 linux-oov9 kernel: RIP: 0000:0x0 Aug 09 20:07:28 linux-oov9 kernel: Code: Bad RIP value. Aug 09 20:07:28 linux-oov9 kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: Modules linked in: veth tun binfmt_misc rfcomm ccm xt_CHECKSUM ipt_REJECT xt_tcpudp nf_nat_tftp nf_conntrack_tftp xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_> Aug 09 20:07:28 linux-oov9 kernel: i2c_designware_platform mei_hdcp(NN) mei_wdt iTCO_vendor_support i2c_designware_core intel_rapl_msr dell_laptop dell_smm_hwmon(NN) cdc_ether usbnet r8152 mii ses enclosure scsi> Aug 09 20:07:28 linux-oov9 kernel: dell_wmi_descriptor wmi_bmof intel_wmi_thunderbolt(NN) snd_compress snd_pcm_dmaengine i2c_i801 rtsx_pci_ms(NN) memstick rfkill idma64 mei_me ucsi_acpi processor_thermal_device(> Aug 09 20:07:28 linux-oov9 kernel: msr snd_aloop snd_pcm snd_timer snd soundcore videodev mc efivarfs Aug 09 20:07:28 linux-oov9 kernel: Supported: No, Unsupported modules are loaded Aug 09 20:07:28 linux-oov9 kernel: CR2: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: ---[ end trace 4ddb4bc4dc05d796 ]--- Aug 09 20:07:28 linux-oov9 kernel: RIP: 0010:iwl_pcie_irq_msix_handler+0x219/0x510 [iwlwifi] Aug 09 20:07:28 linux-oov9 kernel: Code: 8b 7b 38 49 c7 c0 08 62 1f c1 48 c7 c1 40 94 1e c1 31 d2 be 00 00 00 02 e8 84 8a ff ff e9 e9 fe ff ff 48 8b 45 78 48 8b 7b 38 <44> 8b 48 08 41 81 f9 d3 00 00 00 0f 84 3c 0> Aug 09 20:07:28 linux-oov9 kernel: RSP: 0018:ffffa30400defe68 EFLAGS: 00010202 Aug 09 20:07:28 linux-oov9 kernel: RAX: 0000000000000000 RBX: ffff8dff3baf8018 RCX: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff8dff5898d0c0 Aug 09 20:07:28 linux-oov9 kernel: RBP: ffff8dff3baf9af8 R08: 0000000000000000 R09: ffffa30400defe00 Aug 09 20:07:28 linux-oov9 kernel: R10: 0000000000000001 R11: 0000000000000001 R12: 0000000024000182 Aug 09 20:07:28 linux-oov9 kernel: R13: ffff8dff3bafa6e8 R14: 00000000a5a5a5a2 R15: ffff8dff3bafa544 Aug 09 20:07:28 linux-oov9 kernel: FS: 0000000000000000(0000) GS:ffff8dff5c380000(0000) knlGS:0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 09 20:07:28 linux-oov9 kernel: CR2: ffffffffffffffd6 CR3: 000000082fa0a002 CR4: 00000000003706e0 Aug 09 20:07:28 linux-oov9 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 09 20:07:28 linux-oov9 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Aug 09 20:07:28 linux-oov9 kernel: Fixing recursive fault but reboot is needed! Aug 09 20:07:28 linux-oov9 kernel: iwlwifi 0000:3b:00.0: Start IWL Error Log Dump: Aug 09 20:07:28 linux-oov9 kernel: iwlwifi 0000:3b:00.0: Status: 0x00000040, count: -1751076845 Aug 09 20:07:28 linux-oov9 kernel: iwlwifi 0000:3b:00.0: Loaded firmware version: 46.4d093a30.0 9260-th-b0-jf-b0-46.ucode -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c18 --- Comment #18 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Javier Llorente from comment #17) > Aug 23 17:53:07 lapbook kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A > FIFO underrun FIFO underruns normally cause flickering of the entire screen, and not just certain windows. Are you sure you're experiencing the same issue as Patrick Keys are describing? (see the video he attached). > I don�t know why I have no issues with the KDE Live image since it's the > same Tumbleweed version (20210820) as the one I have installed and both are > using the i915 driver. That is odd. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c7 --- Comment #7 from Vicente Adolfo Bolea Sanchez <vicente.bolea(a)gmail.com> --- Yes, it is a regression, it did not occur in previous kernels in 15.3, 15.2 and 15.1. I have also noticed that after updating the kernel from 5.3.18-59.16-default to 5.3.18-59.19-default I have not experience this issue anymore for about two weeks. Perhaps something was included in the last rpm release. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c17 --- Comment #17 from Javier Llorente <javier(a)opensuse.org> --- (In reply to Patrik Jakobsson from comment #14) > How easy is it to reproduce the error? > > As a quick test I ran the KDE Live Tumbleweed image for a while on my Dell > Skylake laptop. I couldn't see any issues. > > Are you able to reproduce the error on a KDE Live image? > > Anything else I can try to reproduce this? Booting up from the KDE Live image works fine. However, if I boot up from the installed OS, I always end up with severe flickering on tty and KDE Desktop. Some logs from the installed OS: Aug 23 17:52:55 lapbook kernel: fb0: switching to inteldrmfb from EFI VGA Aug 23 17:52:55 lapbook kernel: Console: switching to colour dummy device 80x25 Aug 23 17:52:55 lapbook kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Aug 23 17:52:55 lapbook kernel: i915 0000:00:02.0: [drm] couldn't get memory information Aug 23 17:52:55 lapbook kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Aug 23 17:52:55 lapbook kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [...] Aug 23 17:53:07 lapbook kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun I don�t know why I have no issues with the KDE Live image since it's the same Tumbleweed version (20210820) as the one I have installed and both are using the i915 driver. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189183] Kernel-default 5.13 causes default screen to blink after login
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189183 https://bugzilla.suse.com/show_bug.cgi?id=1189183#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- As 5.14 kernel seems working, I close as UPSTREAM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189207] Webcam not detected in Lenovo Thinkpad T14 gen 1
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189207 https://bugzilla.suse.com/show_bug.cgi?id=1189207#c42 --- Comment #42 from Takashi Iwai <tiwai(a)suse.com> --- FYI, I pushed my patch into stable branch for the TW kernels now. I'll update the patch once when any correction is suggested by upstream. Let's see. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Well, the question was whether you've seen the similar bug in the earlier releases of Leap 15.3 kernels. If it happens only with the latest kernel, it's a new regression. Or if you haven't used the older kernels, you can try to downgrade from the already released packages. e.g. zypper se -s kernel-default will show the all kernel-default package, and you can forcibly install the old version with --oldpackage and the explicit version-release numbers like zypper in --oldpackage kernel-default-5.3.18-57.3 But before testing older kernels, I'd recommend you to increase the number of installable kernels by editing /etc/zypp/zypp.conf. Modify the line containing "multiversion.kernels = ..." to add more entries, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c5 --- Comment #5 from Vicente Adolfo Bolea Sanchez <vicente.bolea(a)gmail.com> --- > Thanks. And is this a regression from the previous kernels? No problem. How can I check this? I am using the default kernel in 15.3. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Fusion Future from comment #15) > Processors: 8 � AMD Ryzen 7 4700U with Radeon Graphics > Memory: 15.0 GiB of RAM > Graphics Processor: AMD RENOIR Well, this bug entry is about i915 Intel graphics problem, so yours is likely a different problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c15 --- Comment #15 from Fusion Future <qydwhotmail(a)gmail.com> --- I am using KDE git build. The bug is very likely to be triggered after minimizing a Firefox window. Operating System: openSUSE Tumbleweed 20210820 KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-1-default (64-bit) Graphics Platform: X11 Processors: 8 � AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182556] i915 [DRM] Random window/background flickering
by bugzilla_noreply＠suse.com 23 Aug '21

23 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182556 http://bugzilla.opensuse.org/show_bug.cgi?id=1182556#c14 --- Comment #14 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- How easy is it to reproduce the error? As a quick test I ran the KDE Live Tumbleweed image for a while on my Dell Skylake laptop. I couldn't see any issues. Are you able to reproduce the error on a KDE Live image? Anything else I can try to reproduce this? -- You are receiving this mail because: You are the assignee for the bug.

1 0