January 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 17 May '24

17 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1219180] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219180 Bug ID: 1219180 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tzimmermann(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218184] New: Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug ID: 1218184 Summary: Eliminate the need for 'OBS source links': convert to _multibuild Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: Dolomite Version: Milestone 5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fcrozat(a)suse.com CC: dimstar(a)opensuse.org, dleuenberger(a)suse.com, fcrozat(a)suse.com, jslaby(a)suse.com, kernel-bugs(a)opensuse.org, mls(a)suse.com, msuchanek(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com Depends on: 1211226 Target Milestone: --- Group: SUSE Enterprise Partner Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1211226 +++ In order to prepare for 'git based source management', we need to fix up a few technical issues. One such issue is 'source links' not being supported in git (i.e in OBS we have openSUSE:Factory/kernel-source as the main package plus a bunch of 'linked packages', each with the name of the additional spec files) The solution is, technically seem, rather simple: using _multibuild multibuild support on OBS is known in two variants, one using a single spec file and conditionals inside the spec file based on @BUILD_FLAVOR@ (probably the more known way) but OBS also supports 'just' listing the additional spec files as 'flavors' the _multibuild to be added to the kernel-source (main package) can be generated like this:  #!/bin/sh echo "<multibuild>" > _multibuild for pkg in *.spec; do test "{$pkg}" == "kernel-source.spec" && continue echo " <package>${pkg/.spec/}</package>" >> _multibuild; done echo "</multibuild>" >> _multibuild  the spec files do not need to be changed in anyway with this method -- You are receiving this mail because: You are on the CC list for the bug.

1 59

[Bug 1219188] New: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219188 Bug ID: 1219188 Summary: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jack(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Starting from build 20240123, which brought kernel 6.7 splice fail: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded Jan, could you please have look whether it's a test bug or mainline kernel bug? I can reproduce the problem also on mainline 6.8.0-rc1 (testing with rapido). -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1211975] New: freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 26 Mar '24

26 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1211975 Bug ID: 1211975 Summary: freeze with flip_done time out when external monitor attached Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mattm3a(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Only when external monitor is attached, display freezes for a Lenovo T14. External monitor is connected via HDMI. Mean time between freeze ~1 hour. Output from terminal (CTRL+ALT+F1) looks something like this (from image, not copied in text form): [374.123930][ T1729] i915 0000:00:02.0: [drm] *ERROR* flip_done timed out [374.123938][ T1729] i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) lsb-release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230531 Codename: n/a uname -srvp Linux 6.3.4-1-default #1 SMP PREEMPT_DYNAMIC Mon May 29 06:22:29 UTC 2023 (2c66b1f) x86_64 I think this issue first appeared for me in mid-May, but I'm unsure of exactly what Tumbleweed update that was. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1218552] New: [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 - Steam Deck
by bugzilla_noreply＠suse.com 13 Mar '24

13 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218552 Bug ID: 1218552 Summary: [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 - Steam Deck Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871668 --> https://bugzilla.suse.com/attachment.cgi?id=871668&action=edit dmesg-pci-eror Hi everyone, Every once in awhile, this Steam Deck print out this error and the system drops me to tty. I do not know why. I did change the SSD to a WD Black as listed below. I do not know how to reproduce the error. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20231228 Codename: n/a Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Valve Version: F7A0120 Release Date: 12/01/2023 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 16 MB Information for package kernel-default: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : kernel-default Version : 6.6.7-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 238.1 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.6.7-1.1.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2023-12-14 17:36:48 +0000 GIT Revision: 6869d093e8485475463bc171d23d7c4142fb6fa4 GIT Branch: stable === START OF INFORMATION SECTION === Model Number: WD_BLACK SN770M 1TB Serial Number: 233101400993 Firmware Version: 731100WD PCI Vendor/Subsystem ID: 0x15b7 IEEE OUI Identifier: 0x001b44 Total NVM Capacity: 1,000,204,886,016 [1.00 TB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 001b44 4a48dc08dc Local Time is: Thu Jan 4 17:36:48 2024 PST Firmware Updates (0x14): 2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x00df): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify Log Page Attributes (0x7e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Log0_FISE_MI Telmtry_Ar_4 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 36 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 3,267,997 [1.67 TB] Data Units Written: 3,844,737 [1.96 TB] Host Read Commands: 22,073,106 Host Write Commands: 62,512,660 Controller Busy Time: 79 Power Cycles: 576 Power On Hours: 46 Unsafe Shutdowns: 123 [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 [ 402.012342] nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 402.012346] nvme 0000:01:00.0: device [15b7:5042] error status/mask=00000001/0000e000 [ 402.012351] nvme 0000:01:00.0: [ 0] RxErr [ 421.302005] usb 3-1.1: new full-speed USB device -- You are receiving this mail because: You are the assignee for the bug.

1 6

Leap 15.6 Alpha uses kernel 6.4.x which is buggy with Adaptec RAID controllers.
by Maxim 08 Mar '24

08 Mar '24

https://bugzilla.kernel.org/show_bug.cgi?id=217599 [ 7427.739081] aacraid: Host bus reset request. SCSI hang ? [ 7427.739101] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7427.739105] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7427.739107] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7427.739109] aacraid 0000:08:00.0: outstanding cmd: firmware-48 [ 7427.739111] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7427.765640] aacraid 0000:08:00.0: Controller reset type is 3 [ 7427.765652] aacraid 0000:08:00.0: Issuing IOP reset [ 7469.875692] aacraid 0000:08:00.0: IOP reset succeeded [ 7469.936116] aacraid: Comm Interface type2 enabled [ 7483.472661] aacraid 0000:08:00.0: Scheduling bus rescan [ 7496.491585] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7496.491764] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7553.768632] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768644] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768650] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768655] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768660] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768664] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768669] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.818630] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835306] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835312] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835317] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835331] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835335] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835340] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835344] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835348] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835353] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835357] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355616] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355631] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355637] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355642] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355647] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355652] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355657] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355661] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355666] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.382419] aacraid: Host bus reset request. SCSI hang ? [ 7598.382439] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7598.382443] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7598.382445] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7598.382447] aacraid 0000:08:00.0: outstanding cmd: firmware-30 [ 7598.382449] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7598.402360] aacraid 0000:08:00.0: Controller reset type is 3 [ 7598.402371] aacraid 0000:08:00.0: Issuing IOP reset [ 7640.363459] aacraid 0000:08:00.0: IOP reset succeeded [ 7640.422724] aacraid: Comm Interface type2 enabled [ 7653.650105] aacraid 0000:08:00.0: Scheduling bus rescan [ 7666.688374] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7666.688467] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7814.462297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462308] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462313] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462318] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462330] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462334] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462338] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.478923] aacraid: Host bus reset request. SCSI hang ? [ 7814.478936] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7814.478938] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7814.478940] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7814.478942] aacraid 0000:08:00.0: outstanding cmd: firmware-9 [ 7814.478943] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7814.495578] aacraid 0000:08:00.0: Controller reset type is 3 [ 7814.495587] aacraid 0000:08:00.0: Issuing IOP reset [ 7856.730598] aacraid 0000:08:00.0: IOP reset succeeded [ 7856.779371] aacraid: Comm Interface type2 enabled [ 7869.946607] aacraid 0000:08:00.0: Scheduling bus rescan [ 7882.985564] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7882.985661] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). P.S. I was not able to login to SUSE bugzillla. Login to SUSE portal does not work.

2 1

[Bug 1219406] New: [BUG] kernel NULL pointer dereference with Linux 6.7.1-2-default
by bugzilla_noreply＠suse.com 06 Mar '24

06 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219406 Bug ID: 1219406 Summary: [BUG] kernel NULL pointer dereference with Linux 6.7.1-2-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kostas.peletidis(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just saw this bug on my work laptop. The desktop froze and only the mouse pointer was responsive. I connected to the laptop from another machine and noticed that Xorg was a zombie process. I also saw the following kernel messages: [ 8550.326847] pcieport 0000:00:08.1: PME: Spurious native interrupt! [13172.962208] BUG: kernel NULL pointer dereference, address: 0000000000000000 [13172.962228] #PF: supervisor read access in kernel mode [13172.962235] #PF: error_code(0x0000) - not-present page [13172.962243] PGD 0 P4D 0 [13172.962255] Oops: 0000 [#1] PREEMPT SMP NOPTI [13172.962266] CPU: 11 PID: 2019 Comm: Xorg.bin Not tainted 6.7.1-2-default #1 openSUSE Tumbleweed d50116cfdb1b14a701e904c894d8f1c040bf1146 [13172.962281] Hardware name: LENOVO 20XGS0V508/20XGS0V508, BIOS R1NET47W (1.17) 12/21/2021 [13172.962289] RIP: 0010:drm_mode_rmfb+0xb6/0x1c0 [13172.962308] Code: 00 00 4c 89 ef e8 7a 0e 3e 00 48 8b 83 98 00 00 00 48 2d 98 00 00 00 48 39 c3 0f 84 eb 00 00 00 31 d2 b9 01 00 00 00 4c 39 e0 <48> 8b 80 98 00 00 00 0f 44 d1 48 2d 98 00 00 00 48 39 c3 75 e8 85 [13172.962317] RSP: 0018:ffffa86fc2bbfc80 EFLAGS: 00010202 [13172.962327] RAX: ffffffffffffff68 RBX: ffff941bc60f1800 RCX: 0000000000000001 [13172.962334] RDX: 0000000000000001 RSI: ffff941bc2004920 RDI: ffff941bc60f18a8 [13172.962341] RBP: ffff941e7352b318 R08: ffff941bc2004b18 R09: ffff941c88c80200 [13172.962347] R10: 0000000000000000 R11: 0000000000000000 R12: ffff941e7352b300 [13172.962354] R13: ffff941bc60f18a8 R14: ffffa86fc2bbfd68 R15: 0000000000000004 [13172.962361] FS: 00007faa06805980(0000) GS:ffff941e9ef80000(0000) knlGS:0000000000000000 [13172.962368] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13172.962374] CR2: 0000000000000000 CR3: 00000001045ce000 CR4: 0000000000750ef0 [13172.962379] PKRU: 55555554 [13172.962384] Call Trace: [13172.962390] <TASK> [13172.962403] ? __die+0x23/0x70 [13172.962423] ? page_fault_oops+0x14d/0x490 [13172.962434] ? ttwu_queue_wakelist+0xef/0x110 [13172.962446] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.962468] ? exc_page_fault+0x71/0x160 [13172.962480] ? asm_exc_page_fault+0x26/0x30 [13172.962495] ? drm_mode_rmfb+0xb6/0x1c0 [13172.962508] ? __pfx_drm_mode_rmfb_ioctl+0x10/0x10 [13172.962516] drm_ioctl_kernel+0xce/0x170 [13172.962525] ? __pfx_drm_mode_page_flip_ioctl+0x10/0x10 [13172.962543] drm_ioctl+0x256/0x490 [13172.962552] ? __pfx_drm_mode_rmfb_ioctl+0x10/0x10 [13172.962561] ? __pfx_drm_mode_page_flip_ioctl+0x10/0x10 [13172.962580] amdgpu_drm_ioctl+0x4e/0x90 [amdgpu c19de16ba0fd72478b307639f09a9c13c52c8d28] [13172.963085] __x64_sys_ioctl+0x97/0xd0 [13172.963098] do_syscall_64+0x64/0xe0 [13172.963108] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963116] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963122] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963129] ? do_syscall_64+0x70/0xe0 [13172.963137] ? switch_fpu_return+0x50/0xe0 [13172.963147] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963154] ? exit_to_user_mode_prepare+0x142/0x1f0 [13172.963165] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963172] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963178] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963185] ? do_syscall_64+0x70/0xe0 [13172.963192] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963199] ? do_syscall_64+0x70/0xe0 [13172.963206] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963212] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963219] ? do_syscall_64+0x70/0xe0 [13172.963227] ? __irq_exit_rcu+0x3b/0xb0 [13172.963242] entry_SYSCALL_64_after_hwframe+0x6e/0x76 [13172.963254] RIP: 0033:0x7faa067139ef [13172.963332] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [13172.963338] RSP: 002b:00007fff5e104280 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [13172.963346] RAX: ffffffffffffffda RBX: 00005608e31df550 RCX: 00007faa067139ef [13172.963351] RDX: 00007fff5e10431c RSI: 00000000c00464af RDI: 000000000000000e [13172.963355] RBP: 00007fff5e10431c R08: 00000005608e3575 R09: 0000000000000007 [13172.963360] R10: 00005608e35751a0 R11: 0000000000000246 R12: 00000000c00464af [13172.963364] R13: 000000000000000e R14: 00005608e12f3ff0 R15: 0000000000000040 [13172.963377] </TASK> [13172.963381] Modules linked in: tun rfcomm nf_conntrack_netbios_ns nf_conntrack_broadcast ccm af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink qrtr cmac algif_hash algif_skcipher af_alg bnep msr binfmt_misc snd_acp_legacy_mach snd_acp_mach snd_soc_nau8821 nls_iso8859_1 snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_sof_amd_acp63 nls_cp437 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir vfat snd_sof_amd_acp fat snd_ctl_led snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_realtek mt7921e snd_sof mt7921_common snd_hda_codec_generic btusb mt792x_lib snd_sof_utils btrtl mt76_connac_lib snd_hda_codec_hdmi btintel uvcvideo snd_soc_core intel_rapl_msr btbcm intel_rapl_common mt76 videobuf2_vmalloc btmtk snd_compress uvc snd_pcm_dmaengine snd_hda_intel videobuf2_memops edac_mce_amd bluetooth videobuf2_v4l2 snd_pci_ps snd_intel_dspcfg snd_intel_sdw_acpi [13172.963548] snd_rpl_pci_acp6x mac80211 videodev r8169 snd_acp_pci libarc4 thinkpad_acpi kvm_amd snd_acp_legacy_common snd_hda_codec snd_pci_acp6x videobuf2_common snd_pci_acp5x snd_hda_core realtek ecdh_generic mc ledtrig_audio snd_hwdep kvm mdio_devres cfg80211 snd_rn_pci_acp3x snd_pcm think_lmi platform_profile snd_acp_config irqbypass firmware_attributes_class snd_timer snd_soc_acpi wmi_bmof tiny_power_button efi_pstore libphy rfkill k10temp snd_pci_acp3x i2c_piix4 snd thermal soundcore ac joydev button nvme_fabrics fuse configfs dmi_sysfs ip_tables x_tables usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched nvme drm_suballoc_helper xhci_pci drm_buddy xhci_pci_renesas ucsi_acpi hid_multitouch drm_display_helper nvme_core xhci_hcd aesni_intel cec typec_ucsi video hid_generic nvme_auth crypto_simd cryptd usbcore ccp roles rc_core t10_pi typec sp5100_tco battery [13172.963741] i2c_hid_acpi wmi i2c_hid serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq br_netfilter bridge stp llc efivarfs [13172.963781] CR2: 0000000000000000 [13172.963787] ---[ end trace 0000000000000000 ]--- [13172.963792] RIP: 0010:drm_mode_rmfb+0xb6/0x1c0 [13172.963801] Code: 00 00 4c 89 ef e8 7a 0e 3e 00 48 8b 83 98 00 00 00 48 2d 98 00 00 00 48 39 c3 0f 84 eb 00 00 00 31 d2 b9 01 00 00 00 4c 39 e0 <48> 8b 80 98 00 00 00 0f 44 d1 48 2d 98 00 00 00 48 39 c3 75 e8 85 [13172.963807] RSP: 0018:ffffa86fc2bbfc80 EFLAGS: 00010202 [13172.963813] RAX: ffffffffffffff68 RBX: ffff941bc60f1800 RCX: 0000000000000001 [13172.963818] RDX: 0000000000000001 RSI: ffff941bc2004920 RDI: ffff941bc60f18a8 [13172.963822] RBP: ffff941e7352b318 R08: ffff941bc2004b18 R09: ffff941c88c80200 [13172.963827] R10: 0000000000000000 R11: 0000000000000000 R12: ffff941e7352b300 [13172.963831] R13: ffff941bc60f18a8 R14: ffffa86fc2bbfd68 R15: 0000000000000004 [13172.963836] FS: 00007faa06805980(0000) GS:ffff941e9ef80000(0000) knlGS:0000000000000000 [13172.963841] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13172.963846] CR2: 0000000000000000 CR3: 00000001045ce000 CR4: 0000000000750ef0 [13172.963851] PKRU: 55555554 [13172.963856] note: Xorg.bin[2019] exited with irqs disabled -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1217748] New: Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 04 Mar '24

04 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217748 Bug ID: 1217748 Summary: Display corruption with spesific applications in Gnome-wayland session Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871111 --> https://bugzilla.suse.com/attachment.cgi?id=871111&action=edit sudo hwinfo >hwinfo.txt (macbook 5.1 with nvidia 9400/ core2 duo. 2008 old and rare) current build: 20231129 yast-snapper gui says my oldest snapshot is 2023-11-23 After a KDE/SDDM issue I installed a base gnome with gnome-wayland session and GDM. While most of the warnings on kernel log disappeared, couple of applications are causing massive display corruption in their work windows. gnome-terminal current and kde system monitor. They even corrupt the areas of desktop when they are moved. This is a kernel/nouveau hardware issue for sure as when I use gnome screen recording/snapshot all looks fine. Gnome developers suggested me to compile a new gnome git version which includes gtk4-terminal as opposed to current one which is a gtk3 version. I found a binary ( https://build.opensuse.org/package/show/home:mantarimay:GNOME:apps/gnome-te… ) and it is fine. I launched kde system monitor. I don't think it has anything to do with gtk3 and yet behaves same way. I am used to nouveau warnings but never seen this one: nouveau 0000:02:00.0: imem: OOM: 00100000 00001000 -2 I decided to post this bug report here as gnome-terminal from Fedora current official live USB works all fine. I have dmesg etc from it if needed. I can live without these applications however as this is a particularly rare configuration I thought I better report. I am OK with testing things. -- You are receiving this mail because: You are the assignee for the bug.

1 8