November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- So the network worked even with r8153_ecm blacklisted, and the suspend/resume problem persists even after the blacklist? If so, another test would be to pass usbcore.autosuspend=-1 boot option while keeping the blacklist. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205740] New: btrfs fails to act on fs if the fs is read-only
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205740 Bug ID: 1205740 Summary: btrfs fails to act on fs if the fs is read-only 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: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Transactional server mounts in read only mode on /. This causes all btrfs management commands to fail. # btrfs balance start -f -sconvert=dup -mconvert=dup -dconvert=single / ERROR: error during balancing '/': Read-only file system There may be more info in syslog - try dmesg | tail However if you (on the same filesystem/pool) do this to /home, it works since that's mounted rw. This is an extremely surprising and unintuitive behaviour. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c5 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Ivan Ivanov from comment #4) > I would say duplicate of bsc#1205259. Indeed! *** This bug has been marked as a duplicate of bug 1205259 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c10 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.schroeter(a)suse.com --- Comment #10 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- *** Bug 1205751 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c4 --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I would say duplicate of bsc#1205259. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c3 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #3 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Ivan Ivanov from comment #2) > Exact kernel version, please? It fails with 6.0.8-1-default. According to the user report on the mailing list it worked with 6.0.3 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c2 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guillaume.gardet@ | |arm.com) --- Comment #2 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Exact kernel version, please? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c1 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- This has been reported on the mailing list as well: https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/X526… I can reproduce locally with latest JeOS image for Raspberry Pi: HDMI output goes down once drm/vc4 driver takes over. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c54 --- Comment #54 from Takashi Iwai <tiwai(a)suse.com> --- I meant not the "section" but just the all output from dmesg. That is, simply run dmesg > dmesg.out and attach the dmesg.out file to Bugzilla. For debugging such hardware issues, you need to see the full picture, not only the focused on. Especially a case like this is involved with different layers (the input device is enabled via ACPI, then transport via designware i2c bus over kernel i2c layer, kernel HID layer, kernel HID touchpad driver, then kernel input driver, finally comes to user-space, then interpreted by libinput, and reaches to the desktop environment at last -- maybe there are something middle I forgot, too). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c53 --- Comment #53 from Paul Soto <pst73de(a)yahoo.com> --- how full is full? I pasted you the section that gets logged after resume from STR. there is nothing else related to the touchpad driver -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205741] New: btrfs splitting a raid1 mirror is "not a trivial process".
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205741 Bug ID: 1205741 Summary: btrfs splitting a raid1 mirror is "not a trivial process". 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: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In zfs if I have a pool of two disks in a raid 1 mirror and want to "split" that to remove a single device (say I'm replacing it, and can't add all three at once)., all I have to do is: zpool remove pool device. In btrfs you can't simply break a raid1 mirror and you have to go through a very confusing and tedious process. First, you need to find which devid you need to remove: # btrfs filesystem show Label: none uuid: cfa4961a-bb45-4941-ae70-948bb27fdd9b Total devices 2 FS bytes used 101.68GiB devid 1 size 256.00GiB used 103.03GiB path /dev/nvme0n1p2 devid 2 size 256.00GiB used 103.03GiB path /dev/nvme1n1p2 Then you have to rebalance to raid0 (jbod?). It's unclear where stripes of data are moved and rebalanced here. The rebalance command is not trivial either, required a bit of knowledge about what is a data,system and metadata chunk. # btrfs balance start -f -sconvert=dup -mconvert=dup -dconvert=single / So at this point I can only assume my raid 1 is now a raid 0 and data is striped over two devices (reducing redundancy). Then I can finally split this with: # btrfs device remove 2 /home Beside being very confusing, this process does open up the possibility of surprise dataloss due to the raid 1 -> raid 0 conversion in the middle, as well as generally being very time consuming. Breaking mirrors to remove a drive and replace a new one in should be a routine and easy task but it's not so here. I think the user experience here should be improved so that I can "break" a raid 1 mirror, keep it as "raid 1" in the btrfs metadata and just remove a single device into a degraded mode before replacing in the new one. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203748] New: Laptop very slow in battery mode (Lenovo Thinkpad T470)
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203748 Bug ID: 1203748 Summary: Laptop very slow in battery mode (Lenovo Thinkpad T470) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For some reason my laptop gets very slow in battery only mode. I notice this when watching videos. It makes it rather unusable when not connecting it to power. It looks like it goes into some deep powersave mode. I would like to avoid this even if this would half the running time in battery mode. Which information do you need? -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137748 http://bugzilla.opensuse.org/show_bug.cgi?id=1137748#c140 --- Comment #140 from Takashi Iwai <tiwai(a)suse.com> --- Mainly because the problem happens only on certain (likely old) machines under some situations. And partly because debugging the suspend/resume problem is *VERY* difficult to do remotely; the suspend/resume can't leave much logs unless you set up specially. At least you can try the latest upstream kernel from OBS Kernel:stable:Backport, and check whether the problem persists. If yes, the issue should be reported rather to the upstream and handled there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c52 --- Comment #52 from Takashi Iwai <tiwai(a)suse.com> --- Again: * Please don't paste too long texts on the form but use attachments * Please give the full dmesg output instead of snippet -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c51 --- Comment #51 from Paul Soto <pst73de(a)yahoo.com> --- 2022-10-26T00:40:43.770672-04:00 t16 kernel: [ 8234.507064][ T5334] PM: hibernation: hibernation entry 2022-10-26T00:40:57.849014-04:00 t16 kernel: [ 8234.586000][ T5334] Filesystems sync: 0.011 seconds 2022-10-26T00:40:57.849145-04:00 t16 kernel: [ 8234.586006][ T5334] Freezing user space processes ... (elapsed 12.299 seconds) done. 2022-10-26T00:40:57.849150-04:00 t16 kernel: [ 8246.885774][ T5334] OOM killer disabled. 2022-10-26T00:40:57.849152-04:00 t16 kernel: [ 8246.886134][ T5334] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff] 2022-10-26T00:40:57.849153-04:00 t16 kernel: [ 8246.886144][ T5334] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff] 2022-10-26T00:40:57.849155-04:00 t16 kernel: [ 8246.886152][ T5334] PM: hibernation: Marking nosave pages: [mem 0x88906000-0x8894dfff] 2022-10-26T00:40:57.849160-04:00 t16 kernel: [ 8246.886158][ T5334] PM: hibernation: Marking nosave pages: [mem 0x89252000-0x89252fff] 2022-10-26T00:40:57.849162-04:00 t16 kernel: [ 8246.886181][ T5334] PM: hibernation: Marking nosave pages: [mem 0x8db6f000-0x937fefff] 2022-10-26T00:40:57.849199-04:00 t16 kernel: [ 8246.887174][ T5334] PM: hibernation: Marking nosave pages: [mem 0x93800000-0xffffffff] 2022-10-26T00:40:57.849200-04:00 t16 kernel: [ 8246.891016][ T5334] PM: hibernation: Basic memory bitmaps created 2022-10-26T00:40:57.849201-04:00 t16 kernel: [ 8246.891754][ T5334] PM: hibernation: Preallocating image memory 2022-10-26T00:40:57.849202-04:00 t16 kernel: [ 8247.113079][ T5334] PM: hibernation: Allocated 881810 pages for snapshot 2022-10-26T00:40:57.849203-04:00 t16 kernel: [ 8247.113080][ T5334] PM: hibernation: Allocated 3527240 kbytes in 0.22 seconds (16032.90 MB/s) 2022-10-26T00:40:57.849204-04:00 t16 kernel: [ 8247.113082][ T5334] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2022-10-26T00:40:57.849206-04:00 t16 kernel: [ 8247.114516][ T5334] printk: Suspending console(s) (use no_console_suspend to debug) 2022-10-26T00:40:57.849207-04:00 t16 kernel: [ 8247.121125][ T1043] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/259) 2022-10-26T00:40:57.849208-04:00 t16 kernel: [ 8247.123101][ T1043] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/1) 2022-10-26T00:40:57.849209-04:00 t16 kernel: [ 8247.393948][ T4740] xhci_hcd 0000:00:14.0: PM: pci_pm_freeze(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 2022-10-26T00:40:57.849211-04:00 t16 kernel: [ 8247.394025][ T4740] xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xd0 returns -16 2022-10-26T00:40:57.849212-04:00 t16 kernel: [ 8247.394041][ T4740] xhci_hcd 0000:00:14.0: PM: failed to freeze async: error -16 2022-10-26T00:40:57.849213-04:00 t16 kernel: [ 8247.850542][ T5705] nvme nvme0: 7/0/0 default/read/poll queues 2022-10-26T00:40:57.849214-04:00 t16 kernel: [ 8247.852188][ T4761] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 2022-10-26T00:40:57.849215-04:00 t16 kernel: [ 8247.852190][ T4761] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 2022-10-26T00:40:57.849216-04:00 t16 kernel: [ 8247.867776][ T4761] i915 0000:00:02.0: [drm] HuC authenticated 2022-10-26T00:40:57.849218-04:00 t16 kernel: [ 8247.867976][ T4761] i915 0000:00:02.0: [drm] GuC submission enabled 2022-10-26T00:40:57.849219-04:00 t16 kernel: [ 8247.867976][ T4761] i915 0000:00:02.0: [drm] GuC SLPC enabled 2022-10-26T00:40:57.849220-04:00 t16 kernel: [ 8247.868565][ T4761] i915 0000:00:02.0: [drm] GuC RC: enabled 2022-10-26T00:40:57.849221-04:00 t16 kernel: [ 8248.587458][ T5334] PM: hibernation: Basic memory bitmaps freed 2022-10-26T00:40:57.849222-04:00 t16 kernel: [ 8248.587465][ T5334] OOM killer enabled. 2022-10-26T00:40:57.849223-04:00 t16 kernel: [ 8248.587467][ T5334] Restarting tasks ... 2022-10-26T00:40:57.849225-04:00 t16 kernel: [ 8248.587767][ T5692] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) 2022-10-26T00:40:57.850670-04:00 t16 kernel: [ 8248.589439][ T5334] done. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137748 http://bugzilla.opensuse.org/show_bug.cgi?id=1137748#c139 christian mathieu <cma63(a)free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #139 from christian mathieu <cma63(a)free.fr> --- Hello. Why is this old bug not fixed ? OpenSUSE is the only distribution affected ! I prefer OpenSUSE, but I can't install it! Kind regards -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205649] New: SEGV when mounting / during boot
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205649 Bug ID: 1205649 Summary: SEGV when mounting / during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: thomas.leroy(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863042 --> https://bugzilla.suse.com/attachment.cgi?id=863042&action=edit Kernel BUG I receive a kernel BUG during boot when trying to mount the root partition. Unfortunately I can't copy/paste the journalctl output because it's the laptop's host kernel, but I linked a picture of the kernel BUG information. I'm running Tumbleweed with a 6.0.8-1-vanilla kernel on x86_64. Additionally, I tried to mount the decrypted disk in a live usb, and mount also segfaulted. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c50 --- Comment #50 from Takashi Iwai <tiwai(a)suse.com> --- Please give the full dmesg output instead of snippet. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c49 --- Comment #49 from Paul Soto <pst73de(a)yahoo.com> --- what appeared in kernel log after the touchpad switched into crazy mode after wake up from STR: 2022-11-10T16:48:25.834049-05:00 t16 kernel: [ 8262.080731][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/255) 2022-11-10T16:48:25.834050-05:00 t16 kernel: [ 8262.082980][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/65280) 2022-11-11T14:45:25.960183-05:00 t16 kernel: [ 8391.816413][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/255) 2022-11-11T14:45:25.960184-05:00 t16 kernel: [ 8391.817710][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/259) 2022-11-11T14:45:25.960207-05:00 t16 kernel: [ 8391.818875][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/65281) apparently from drivers/hid/i2c-hid/i2c-hid-core.c -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c48 --- Comment #48 from Takashi Iwai <tiwai(a)suse.com> --- Also give the dmesg output, too. The hwinfo and dmesg outputs are required to figure out exactly which device is on your machine and what are probed, also whether any relevant info / error is seen from the kernel. To deal with a hardware issue like this, you always need to know the detailed hardware information as much as possible before going further. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c47 --- Comment #47 from Paul Soto <pst73de(a)yahoo.com> --- Created attachment 863047 --> http://bugzilla.opensuse.org/attachment.cgi?id=863047&action=edit hwinfo doubt hwinfo will help you -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Ah right, I forgot one more step. I thought it were done automatically, but apparently not. Run as root: make modules_install *before* running "make install". This will install modules. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c9 --- Comment #9 from Philippe Cond� <conde.philippe(a)skynet.be> --- hello, I followed your instructions but the build kernel gives a infinite loop start -> reboot. I see this remark with sudo make install "philippe@hpprol2:~/kernel_clone/linux> sudo make install [sudo] Mot de passe de philippe�: INSTALL /boot renamed '/boot/config-6.0.7-test07' -> '/boot/config-6.0.7-test07.old' Certificate must have Code Signing extended key usage defined for Secure Boot. You may need to create an initial ramdisk now. " but mkinitrd doesn't take kernel 6.0.7-test07 in account I see in /boot that the config-6.0.7.test07 is not linked to a lib/module directory lrwxrwxrwx 1 root root 41 Nov 7 14:07 config-6.0.7-1-default -> ../usr/lib/modules/6.0.7-1-default/config -rw-r--r-- 1 philippe users 171587 Nov 22 12:33 config-6.0.7-test07 -rw-r--r-- 1 philippe users 171587 Nov 22 12:33 config-6.0.7-test07.old lrwxrwxrwx 1 root root 41 Nov 14 14:07 config-6.0.8-1-default -> ../usr/lib/modules/6.0.8-1-default/config lrwxrwxrwx 1 root root 50 Nov 22 08:30 config-6.0.9-2.g699b9c2-default -> ../usr/lib/modules/6.0.9-2.g699b9c2-default/config drwxr-xr-x 6 root root 4096 Nov 22 14:12 grub2 lrwxrwxrwx 1 root root 31 Nov 22 08:30 initrd -> initrd-6.0.9-2.g699b9c2-default -rw------- 1 root root 20359727 Nov 22 13:50 initrd-6.0.7-1-default -rw------- 1 root root 20361111 Nov 22 13:50 initrd-6.0.8-1-default -rw------- 1 root root 20343116 Nov 22 13:50 initrd-6.0.9-2.g699b9c2-default any advice? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- In this case, it might be better to run git bisect on linux-stable git tree, supposing it's an upstream problem. Clone the linux-stable.git from either github.com or git.kernel.org. https://github.com/gregkh/linux or git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Then checkout v6.0.7, copy the kernel config from the running kernel: % git checkout v6.0.7 % zcat /proc/config.gz > .config Edit .config file to change CONFIG_LOCALVERSION, set it to a unique prefix (e.g. "-test"). The next step is to reduce the needed config to match with the currently used modules (which will reduce the compile time a lot): % make localmodconfig You'll need a few more packages like kernel-install-tools, etc. Then make, and install it % make -j8 % sudo make install Confirm that it's working. Then checkout v6.0.8, build, install, and retest. Confirm that the problem appears. Once after confirming the bug reproduction, go for bisection. % git bisect start % git bisect good v6.0.7 % git bisect bad v6.0.8 Again, build, install and retest. If the kernel is good, give "git bisect good". If it's buggy, "git bisect bad". Then git will lead to another commit to test. It's repeated until you find the first buggy commit. As a hint: it might be better to change the kernel suffix at each time not to conflict with the previous kernels (e.g. name it "bisect1" or such). And, be careful to choose the kernel to boot at GRUB. It's crucial to know exactly which kernel / commit you're testing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c7 --- Comment #7 from Philippe Cond� <conde.philippe(a)skynet.be> --- Hello, I have the kernel sources installed and I think all development tools needed. Can I follow this guide? https://github.com/openSUSE/kernel-source/blob/master/doc/README.SUSE I never did a run git bisect so I need some instructions about this Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205359] Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*".
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205359 https://bugzilla.suse.com/show_bug.cgi?id=1205359#c4 --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Given that documentation explicitly says how spidev is supposed to work I am planing to close this as WONTFIX. Objections? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Then the best would be to perform git bisect to identify the buggy commit, I guess. Would you try to build a kernel and run git bisect? If yes, and if you want, I can give you a brief instruction, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c5 --- Comment #5 from Philippe Cond� <conde.philippe(a)skynet.be> --- Hello, I installed kernel 6.0.9 from obs and PysolFC had a lock very rapidly. I have no problem with kernel 6.0.7 I attach the journalctl output with kernel 6.0.9 Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c4 --- Comment #4 from Philippe Cond� <conde.philippe(a)skynet.be> --- Created attachment 863029 --> https://bugzilla.suse.com/attachment.cgi?id=863029&action=edit lock with kernel 6.0.9 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c46 --- Comment #46 from Takashi Iwai <tiwai(a)suse.com> --- Please don't paste too long texts on the form but use attachments. Moreover, the requested information still isn't given... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c45 --- Comment #45 from Paul Soto <pst73de(a)yahoo.com> --- example trace when I do the following: put one finger close to left touchpad boundary, then quickly put another finger close to the right touchpad boundary (so max distance between fingers), then quickly move the finger on the right side down, the other finger stationary: Testing ... (interrupt to exit) Event: time 1669061803.977276, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 20462 Event: time 1669061803.977276, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 262 Event: time 1669061803.977276, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 673 Event: time 1669061803.977276, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 ===> here Event: time 1669061803.977276, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1669061803.977276, type 3 (EV_ABS), code 0 (ABS_X), value 262 Event: time 1669061803.977276, type 3 (EV_ABS), code 1 (ABS_Y), value 673 Event: time 1669061803.977276, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0 Event: time 1669061803.977276, -------------- SYN_REPORT ------------ Event: time 1669061803.978655, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 14000 Event: time 1669061803.978655, -------------- SYN_REPORT ------------ Event: time 1669061803.985448, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 21000 Event: time 1669061803.985448, -------------- SYN_REPORT ------------ Event: time 1669061803.992383, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 28000 Event: time 1669061803.992383, -------------- SYN_REPORT ------------ Event: time 1669061803.999188, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 35000 Event: time 1669061803.999188, -------------- SYN_REPORT ------------ Event: time 1669061804.006099, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 671 Event: time 1669061804.006099, type 3 (EV_ABS), code 1 (ABS_Y), value 671 Event: time 1669061804.006099, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42000 Event: time 1669061804.006099, -------------- SYN_REPORT ------------ Event: time 1669061804.013264, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 669 Event: time 1669061804.013264, type 3 (EV_ABS), code 1 (ABS_Y), value 669 Event: time 1669061804.013264, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 49000 Event: time 1669061804.013264, -------------- SYN_REPORT ------------ Event: time 1669061804.020173, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 668 Event: time 1669061804.020173, type 3 (EV_ABS), code 1 (ABS_Y), value 668 Event: time 1669061804.020173, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 56000 Event: time 1669061804.020173, -------------- SYN_REPORT ------------ Event: time 1669061804.027186, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 667 Event: time 1669061804.027186, type 3 (EV_ABS), code 1 (ABS_Y), value 667 Event: time 1669061804.027186, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 63000 Event: time 1669061804.027186, -------------- SYN_REPORT ------------ Event: time 1669061804.034055, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 666 Event: time 1669061804.034055, type 3 (EV_ABS), code 1 (ABS_Y), value 666 Event: time 1669061804.034055, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 70000 Event: time 1669061804.034055, -------------- SYN_REPORT ------------ Event: time 1669061804.040941, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 665 Event: time 1669061804.040941, type 3 (EV_ABS), code 1 (ABS_Y), value 665 Event: time 1669061804.040941, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 77000 Event: time 1669061804.040941, -------------- SYN_REPORT ------------ Event: time 1669061804.047660, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 663 Event: time 1669061804.047660, type 3 (EV_ABS), code 1 (ABS_Y), value 663 Event: time 1669061804.047660, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 84000 Event: time 1669061804.047660, -------------- SYN_REPORT ------------ Event: time 1669061804.054702, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 662 Event: time 1669061804.054702, type 3 (EV_ABS), code 1 (ABS_Y), value 662 Event: time 1669061804.054702, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 91000 Event: time 1669061804.054702, -------------- SYN_REPORT ------------ Event: time 1669061804.061661, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 661 Event: time 1669061804.061661, type 3 (EV_ABS), code 1 (ABS_Y), value 661 Event: time 1669061804.061661, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 98000 Event: time 1669061804.061661, -------------- SYN_REPORT ------------ Event: time 1669061804.068471, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 660 Event: time 1669061804.068471, type 3 (EV_ABS), code 1 (ABS_Y), value 660 Event: time 1669061804.068471, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 105000 Event: time 1669061804.068471, -------------- SYN_REPORT ------------ Event: time 1669061804.075437, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 659 Event: time 1669061804.075437, type 3 (EV_ABS), code 1 (ABS_Y), value 659 Event: time 1669061804.075437, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 112000 Event: time 1669061804.075437, -------------- SYN_REPORT ------------ Event: time 1669061804.082345, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 658 Event: time 1669061804.082345, type 3 (EV_ABS), code 1 (ABS_Y), value 658 Event: time 1669061804.082345, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 119000 Event: time 1669061804.082345, -------------- SYN_REPORT ------------ Event: time 1669061804.089101, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 657 Event: time 1669061804.089101, type 3 (EV_ABS), code 1 (ABS_Y), value 657 Event: time 1669061804.089101, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 126000 Event: time 1669061804.089101, -------------- SYN_REPORT ------------ Event: time 1669061804.096128, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 656 Event: time 1669061804.096128, type 3 (EV_ABS), code 1 (ABS_Y), value 656 Event: time 1669061804.096128, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 133000 Event: time 1669061804.096128, -------------- SYN_REPORT ------------ Event: time 1669061804.103113, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 655 Event: time 1669061804.103113, type 3 (EV_ABS), code 1 (ABS_Y), value 655 Event: time 1669061804.103113, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 140000 Event: time 1669061804.103113, -------------- SYN_REPORT ------------ Event: time 1669061804.110091, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 654 Event: time 1669061804.110091, type 3 (EV_ABS), code 1 (ABS_Y), value 654 Event: time 1669061804.110091, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 147000 Event: time 1669061804.110091, -------------- SYN_REPORT ------------ Event: time 1669061804.117026, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 261 Event: time 1669061804.117026, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 653 Event: time 1669061804.117026, type 3 (EV_ABS), code 0 (ABS_X), value 261 Event: time 1669061804.117026, type 3 (EV_ABS), code 1 (ABS_Y), value 653 Event: time 1669061804.117026, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 154000 Event: time 1669061804.117026, -------------- SYN_REPORT ------------ Event: time 1669061804.123812, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 260 Event: time 1669061804.123812, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 652 Event: time 1669061804.123812, type 3 (EV_ABS), code 0 (ABS_X), value 260 Event: time 1669061804.123812, type 3 (EV_ABS), code 1 (ABS_Y), value 652 Event: time 1669061804.123812, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 161000 Event: time 1669061804.123812, -------------- SYN_REPORT ------------ Event: time 1669061804.130848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 259 Event: time 1669061804.130848, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 651 Event: time 1669061804.130848, type 3 (EV_ABS), code 0 (ABS_X), value 259 Event: time 1669061804.130848, type 3 (EV_ABS), code 1 (ABS_Y), value 651 Event: time 1669061804.130848, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 168000 Event: time 1669061804.130848, -------------- SYN_REPORT ------------ Event: time 1669061804.137579, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 258 Event: time 1669061804.137579, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650 Event: time 1669061804.137579, type 3 (EV_ABS), code 0 (ABS_X), value 258 Event: time 1669061804.137579, type 3 (EV_ABS), code 1 (ABS_Y), value 650 Event: time 1669061804.137579, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 175000 Event: time 1669061804.137579, -------------- SYN_REPORT ------------ Event: time 1669061804.144650, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 257 Event: time 1669061804.144650, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649 Event: time 1669061804.144650, type 3 (EV_ABS), code 0 (ABS_X), value 257 Event: time 1669061804.144650, type 3 (EV_ABS), code 1 (ABS_Y), value 649 Event: time 1669061804.144650, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 182000 Event: time 1669061804.144650, -------------- SYN_REPORT ------------ Event: time 1669061804.151555, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 256 Event: time 1669061804.151555, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648 Event: time 1669061804.151555, type 3 (EV_ABS), code 0 (ABS_X), value 256 Event: time 1669061804.151555, type 3 (EV_ABS), code 1 (ABS_Y), value 648 Event: time 1669061804.151555, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 189000 Event: time 1669061804.151555, -------------- SYN_REPORT ------------ Event: time 1669061804.158543, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 255 Event: time 1669061804.158543, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647 Event: time 1669061804.158543, type 3 (EV_ABS), code 0 (ABS_X), value 255 Event: time 1669061804.158543, type 3 (EV_ABS), code 1 (ABS_Y), value 647 Event: time 1669061804.158543, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 196000 Event: time 1669061804.158543, -------------- SYN_REPORT ------------ Event: time 1669061804.165390, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 254 Event: time 1669061804.165390, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646 Event: time 1669061804.165390, type 3 (EV_ABS), code 0 (ABS_X), value 254 Event: time 1669061804.165390, type 3 (EV_ABS), code 1 (ABS_Y), value 646 Event: time 1669061804.165390, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 203000 Event: time 1669061804.165390, -------------- SYN_REPORT ------------ Event: time 1669061804.172268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 253 Event: time 1669061804.172268, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645 Event: time 1669061804.172268, type 3 (EV_ABS), code 0 (ABS_X), value 253 Event: time 1669061804.172268, type 3 (EV_ABS), code 1 (ABS_Y), value 645 Event: time 1669061804.172268, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 210000 Event: time 1669061804.172268, -------------- SYN_REPORT ------------ Event: time 1669061804.179248, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 644 Event: time 1669061804.179248, type 3 (EV_ABS), code 1 (ABS_Y), value 644 Event: time 1669061804.179248, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 217000 Event: time 1669061804.179248, -------------- SYN_REPORT ------------ Event: time 1669061804.186213, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 252 Event: time 1669061804.186213, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 643 Event: time 1669061804.186213, type 3 (EV_ABS), code 0 (ABS_X), value 252 Event: time 1669061804.186213, type 3 (EV_ABS), code 1 (ABS_Y), value 643 Event: time 1669061804.186213, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 224000 Event: time 1669061804.186213, -------------- SYN_REPORT ------------ Event: time 1669061804.193220, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 642 Event: time 1669061804.193220, type 3 (EV_ABS), code 1 (ABS_Y), value 642 Event: time 1669061804.193220, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 231000 Event: time 1669061804.193220, -------------- SYN_REPORT ------------ Event: time 1669061804.201089, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.201089, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 20463 Event: time 1669061804.201089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2845 Event: time 1669061804.201089, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 266 Event: time 1669061804.201089, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 ===> here Event: time 1669061804.201089, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1 Event: time 1669061804.201089, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 238000 Event: time 1669061804.201089, -------------- SYN_REPORT ------------ Event: time 1669061804.207933, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 245000 Event: time 1669061804.207933, -------------- SYN_REPORT ------------ Event: time 1669061804.214592, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 252000 Event: time 1669061804.214592, -------------- SYN_REPORT ------------ Event: time 1669061804.221776, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 259000 Event: time 1669061804.221776, -------------- SYN_REPORT ------------ Event: time 1669061804.228593, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 266000 Event: time 1669061804.228593, -------------- SYN_REPORT ------------ Event: time 1669061804.235456, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.235456, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 251 Event: time 1669061804.235456, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 639 Event: time 1669061804.235456, type 3 (EV_ABS), code 0 (ABS_X), value 251 Event: time 1669061804.235456, type 3 (EV_ABS), code 1 (ABS_Y), value 639 Event: time 1669061804.235456, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 273000 Event: time 1669061804.235456, -------------- SYN_REPORT ------------ Event: time 1669061804.242306, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 280000 Event: time 1669061804.242306, -------------- SYN_REPORT ------------ Event: time 1669061804.249213, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 287000 Event: time 1669061804.249213, -------------- SYN_REPORT ------------ Event: time 1669061804.256028, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 294000 Event: time 1669061804.256028, -------------- SYN_REPORT ------------ Event: time 1669061804.263239, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 301000 Event: time 1669061804.263239, -------------- SYN_REPORT ------------ Event: time 1669061804.270080, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 308000 Event: time 1669061804.270080, -------------- SYN_REPORT ------------ Event: time 1669061804.277252, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 315000 Event: time 1669061804.277252, -------------- SYN_REPORT ------------ Event: time 1669061804.283932, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 322000 Event: time 1669061804.283932, -------------- SYN_REPORT ------------ Event: time 1669061804.290915, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 329000 Event: time 1669061804.290915, -------------- SYN_REPORT ------------ Event: time 1669061804.297836, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 336000 Event: time 1669061804.297836, -------------- SYN_REPORT ------------ Event: time 1669061804.304438, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 343000 Event: time 1669061804.304438, -------------- SYN_REPORT ------------ Event: time 1669061804.311537, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.311537, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2841 Event: time 1669061804.311537, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 267 Event: time 1669061804.311537, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 350000 Event: time 1669061804.311537, -------------- SYN_REPORT ------------ Event: time 1669061804.318509, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 357000 Event: time 1669061804.318509, -------------- SYN_REPORT ------------ Event: time 1669061804.325590, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2837 Event: time 1669061804.325590, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 272 Event: time 1669061804.325590, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 364000 Event: time 1669061804.325590, -------------- SYN_REPORT ------------ Event: time 1669061804.332258, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2835 Event: time 1669061804.332258, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 278 Event: time 1669061804.332258, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 371000 Event: time 1669061804.332258, -------------- SYN_REPORT ------------ Event: time 1669061804.339335, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2833 Event: time 1669061804.339335, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 286 Event: time 1669061804.339335, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 378000 Event: time 1669061804.339335, -------------- SYN_REPORT ------------ Event: time 1669061804.346229, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2831 Event: time 1669061804.346229, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 297 Event: time 1669061804.346229, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 385000 Event: time 1669061804.346229, -------------- SYN_REPORT ------------ Event: time 1669061804.353107, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2828 Event: time 1669061804.353107, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 312 Event: time 1669061804.353107, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 392000 Event: time 1669061804.353107, -------------- SYN_REPORT ------------ Event: time 1669061804.360041, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2825 Event: time 1669061804.360041, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 328 Event: time 1669061804.360041, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 399000 Event: time 1669061804.360041, -------------- SYN_REPORT ------------ Event: time 1669061804.366884, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.366884, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 250 Event: time 1669061804.366884, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 642 Event: time 1669061804.366884, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.366884, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2821 Event: time 1669061804.366884, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 345 Event: time 1669061804.366884, type 3 (EV_ABS), code 0 (ABS_X), value 250 Event: time 1669061804.366884, type 3 (EV_ABS), code 1 (ABS_Y), value 642 Event: time 1669061804.366884, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 406000 Event: time 1669061804.366884, -------------- SYN_REPORT ------------ Event: time 1669061804.373682, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2816 Event: time 1669061804.373682, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 363 Event: time 1669061804.373682, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 413000 Event: time 1669061804.373682, -------------- SYN_REPORT ------------ Event: time 1669061804.380722, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2811 Event: time 1669061804.380722, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 381 Event: time 1669061804.380722, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 420000 Event: time 1669061804.380722, -------------- SYN_REPORT ------------ Event: time 1669061804.387320, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.387320, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645 Event: time 1669061804.387320, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.387320, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2806 Event: time 1669061804.387320, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 399 Event: time 1669061804.387320, type 3 (EV_ABS), code 1 (ABS_Y), value 645 Event: time 1669061804.387320, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 427000 Event: time 1669061804.387320, -------------- SYN_REPORT ------------ Event: time 1669061804.394883, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2800 Event: time 1669061804.394883, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419 Event: time 1669061804.394883, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 434000 Event: time 1669061804.394883, -------------- SYN_REPORT ------------ Event: time 1669061804.401212, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2795 Event: time 1669061804.401212, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 438 Event: time 1669061804.401212, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 441000 Event: time 1669061804.401212, -------------- SYN_REPORT ------------ Event: time 1669061804.408302, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.408302, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648 Event: time 1669061804.408302, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.408302, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2790 Event: time 1669061804.408302, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 457 Event: time 1669061804.408302, type 3 (EV_ABS), code 1 (ABS_Y), value 648 Event: time 1669061804.408302, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 448000 Event: time 1669061804.408302, -------------- SYN_REPORT ------------ Event: time 1669061804.415029, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2786 Event: time 1669061804.415029, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 476 Event: time 1669061804.415029, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 455000 Event: time 1669061804.415029, -------------- SYN_REPORT ------------ Event: time 1669061804.421937, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2782 Event: time 1669061804.421937, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 495 Event: time 1669061804.421937, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 462000 Event: time 1669061804.421937, -------------- SYN_REPORT ------------ Event: time 1669061804.429222, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2778 Event: time 1669061804.429222, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 514 Event: time 1669061804.429222, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 469000 Event: time 1669061804.429222, -------------- SYN_REPORT ------------ Event: time 1669061804.436179, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2774 Event: time 1669061804.436179, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 538 Event: time 1669061804.436179, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 476000 Event: time 1669061804.436179, -------------- SYN_REPORT ------------ Event: time 1669061804.443063, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2769 Event: time 1669061804.443063, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 564 Event: time 1669061804.443063, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 483000 Event: time 1669061804.443063, -------------- SYN_REPORT ------------ Event: time 1669061804.450016, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2763 Event: time 1669061804.450016, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 594 Event: time 1669061804.450016, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 490000 Event: time 1669061804.450016, -------------- SYN_REPORT ------------ Event: time 1669061804.456630, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.456630, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 251 Event: time 1669061804.456630, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645 Event: time 1669061804.456630, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.456630, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2757 Event: time 1669061804.456630, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 623 Event: time 1669061804.456630, type 3 (EV_ABS), code 0 (ABS_X), value 251 Event: time 1669061804.456630, type 3 (EV_ABS), code 1 (ABS_Y), value 645 Event: time 1669061804.456630, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 497000 Event: time 1669061804.456630, -------------- SYN_REPORT ------------ Event: time 1669061804.463820, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2751 Event: time 1669061804.463820, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649 Event: time 1669061804.463820, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 504000 Event: time 1669061804.463820, -------------- SYN_REPORT ------------ Event: time 1669061804.470430, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.470430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 641 Event: time 1669061804.470430, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.470430, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2746 Event: time 1669061804.470430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 674 Event: time 1669061804.470430, type 3 (EV_ABS), code 1 (ABS_Y), value 641 Event: time 1669061804.470430, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 511000 Event: time 1669061804.470430, -------------- SYN_REPORT ------------ Event: time 1669061804.477263, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2741 Event: time 1669061804.477263, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 699 Event: time 1669061804.477263, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 518000 Event: time 1669061804.477263, -------------- SYN_REPORT ------------ Event: time 1669061804.484492, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.484492, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 252 Event: time 1669061804.484492, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 637 Event: time 1669061804.484492, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.484492, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2736 Event: time 1669061804.484492, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 721 Event: time 1669061804.484492, type 3 (EV_ABS), code 0 (ABS_X), value 252 Event: time 1669061804.484492, type 3 (EV_ABS), code 1 (ABS_Y), value 637 Event: time 1669061804.484492, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 525000 Event: time 1669061804.484492, -------------- SYN_REPORT ------------ Event: time 1669061804.491348, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2732 Event: time 1669061804.491348, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 741 Event: time 1669061804.491348, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 532000 Event: time 1669061804.491348, -------------- SYN_REPORT ------------ Event: time 1669061804.498412, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2729 Event: time 1669061804.498412, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 757 Event: time 1669061804.498412, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 539000 Event: time 1669061804.498412, -------------- SYN_REPORT ------------ Event: time 1669061804.505262, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.505262, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 634 Event: time 1669061804.505262, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.505262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2726 Event: time 1669061804.505262, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 770 Event: time 1669061804.505262, type 3 (EV_ABS), code 1 (ABS_Y), value 634 Event: time 1669061804.505262, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 546000 Event: time 1669061804.505262, -------------- SYN_REPORT ------------ Event: time 1669061804.512405, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2724 Event: time 1669061804.512405, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 781 Event: time 1669061804.512405, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 553000 Event: time 1669061804.512405, -------------- SYN_REPORT ------------ Event: time 1669061804.519123, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2722 Event: time 1669061804.519123, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 790 Event: time 1669061804.519123, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 560000 Event: time 1669061804.519123, -------------- SYN_REPORT ------------ Event: time 1669061804.525736, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.525736, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 631 Event: time 1669061804.525736, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.525736, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2720 Event: time 1669061804.525736, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 798 Event: time 1669061804.525736, type 3 (EV_ABS), code 1 (ABS_Y), value 631 Event: time 1669061804.525736, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 567000 Event: time 1669061804.525736, -------------- SYN_REPORT ------------ Event: time 1669061804.532583, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2718 Event: time 1669061804.532583, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 805 Event: time 1669061804.532583, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 574000 Event: time 1669061804.532583, -------------- SYN_REPORT ------------ Event: time 1669061804.539595, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2716 Event: time 1669061804.539595, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 811 Event: time 1669061804.539595, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 581000 Event: time 1669061804.539595, -------------- SYN_REPORT ------------ Event: time 1669061804.547173, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2714 Event: time 1669061804.547173, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 816 Event: time 1669061804.547173, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 588000 Event: time 1669061804.547173, -------------- SYN_REPORT ------------ Event: time 1669061804.554086, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2713 Event: time 1669061804.554086, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 821 Event: time 1669061804.554086, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 595000 Event: time 1669061804.554086, -------------- SYN_REPORT ------------ Event: time 1669061804.560651, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2712 Event: time 1669061804.560651, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 825 Event: time 1669061804.560651, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 602000 Event: time 1669061804.560651, -------------- SYN_REPORT ------------ Event: time 1669061804.567444, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2711 Event: time 1669061804.567444, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 829 Event: time 1669061804.567444, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 609000 Event: time 1669061804.567444, -------------- SYN_REPORT ------------ Event: time 1669061804.574375, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2710 Event: time 1669061804.574375, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 832 Event: time 1669061804.574375, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 616000 Event: time 1669061804.574375, -------------- SYN_REPORT ------------ Event: time 1669061804.581320, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2709 Event: time 1669061804.581320, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 835 Event: time 1669061804.581320, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 623000 Event: time 1669061804.581320, -------------- SYN_REPORT ------------ Event: time 1669061804.587969, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2708 Event: time 1669061804.587969, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 838 Event: time 1669061804.587969, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 630000 Event: time 1669061804.587969, -------------- SYN_REPORT ------------ Event: time 1669061804.595311, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2707 Event: time 1669061804.595311, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 841 Event: time 1669061804.595311, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 637000 Event: time 1669061804.595311, -------------- SYN_REPORT ------------ Event: time 1669061804.602276, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2706 Event: time 1669061804.602276, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 844 Event: time 1669061804.602276, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 644000 Event: time 1669061804.602276, -------------- SYN_REPORT ------------ Event: time 1669061804.609090, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2705 Event: time 1669061804.609090, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 847 Event: time 1669061804.609090, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 651000 Event: time 1669061804.609090, -------------- SYN_REPORT ------------ Event: time 1669061804.615631, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2704 Event: time 1669061804.615631, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 850 Event: time 1669061804.615631, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 658000 Event: time 1669061804.615631, -------------- SYN_REPORT ------------ Event: time 1669061804.622587, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2703 Event: time 1669061804.622587, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 853 Event: time 1669061804.622587, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 665000 Event: time 1669061804.622587, -------------- SYN_REPORT ------------ Event: time 1669061804.629559, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2702 Event: time 1669061804.629559, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 856 Event: time 1669061804.629559, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 672000 Event: time 1669061804.629559, -------------- SYN_REPORT ------------ Event: time 1669061804.636472, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2701 Event: time 1669061804.636472, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 860 Event: time 1669061804.636472, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 679000 Event: time 1669061804.636472, -------------- SYN_REPORT ------------ Event: time 1669061804.643342, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2700 Event: time 1669061804.643342, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 864 Event: time 1669061804.643342, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 686000 Event: time 1669061804.643342, -------------- SYN_REPORT ------------ Event: time 1669061804.650323, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2698 Event: time 1669061804.650323, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 869 Event: time 1669061804.650323, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 693000 Event: time 1669061804.650323, -------------- SYN_REPORT ------------ Event: time 1669061804.657380, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2696 Event: time 1669061804.657380, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 874 Event: time 1669061804.657380, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 700000 Event: time 1669061804.657380, -------------- SYN_REPORT ------------ Event: time 1669061804.664089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2695 Event: time 1669061804.664089, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 878 Event: time 1669061804.664089, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 707000 Event: time 1669061804.664089, -------------- SYN_REPORT ------------ Event: time 1669061804.671094, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 714000 Event: time 1669061804.671094, -------------- SYN_REPORT ------------ Event: time 1669061804.678310, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 721000 Event: time 1669061804.678310, -------------- SYN_REPORT ------------ Event: time 1669061804.685000, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.685000, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 254 Event: time 1669061804.685000, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 632 Event: time 1669061804.685000, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1 Event: time 1669061804.685000, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1669061804.685000, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1669061804.685000, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0 Event: time 1669061804.685000, type 3 (EV_ABS), code 0 (ABS_X), value 254 Event: time 1669061804.685000, type 3 (EV_ABS), code 1 (ABS_Y), value 632 Event: time 1669061804.685000, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 728000 Event: time 1669061804.685000, -------------- SYN_REPORT ------------ Event: time 1669061804.691286, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0 Event: time 1669061804.691286, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 633 Event: time 1669061804.691286, type 3 (EV_ABS), code 1 (ABS_Y), value 633 Event: time 1669061804.691286, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 735000 Event: time 1669061804.691286, -------------- SYN_REPORT ------------ Event: time 1669061804.698170, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 634 Event: time 1669061804.698170, type 3 (EV_ABS), code 1 (ABS_Y), value 634 Event: time 1669061804.698170, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 742000 Event: time 1669061804.698170, -------------- SYN_REPORT ------------ Event: time 1669061804.705004, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 635 Event: time 1669061804.705004, type 3 (EV_ABS), code 1 (ABS_Y), value 635 Event: time 1669061804.705004, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 749000 Event: time 1669061804.705004, -------------- SYN_REPORT ------------ Event: time 1669061804.712189, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 636 Event: time 1669061804.712189, type 3 (EV_ABS), code 1 (ABS_Y), value 636 Event: time 1669061804.712189, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 756000 Event: time 1669061804.712189, -------------- SYN_REPORT ------------ Event: time 1669061804.718921, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 637 Event: time 1669061804.718921, type 3 (EV_ABS), code 1 (ABS_Y), value 637 Event: time 1669061804.718921, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 763000 Event: time 1669061804.718921, -------------- SYN_REPORT ------------ Event: time 1669061804.725887, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 638 Event: time 1669061804.725887, type 3 (EV_ABS), code 1 (ABS_Y), value 638 Event: time 1669061804.725887, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 770000 Event: time 1669061804.725887, -------------- SYN_REPORT ------------ Event: time 1669061804.732603, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 639 Event: time 1669061804.732603, type 3 (EV_ABS), code 1 (ABS_Y), value 639 Event: time 1669061804.732603, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 777000 Event: time 1669061804.732603, -------------- SYN_REPORT ------------ Event: time 1669061804.739505, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 784000 Event: time 1669061804.739505, -------------- SYN_REPORT ------------ Event: time 1669061804.746595, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 791000 Event: time 1669061804.746595, -------------- SYN_REPORT ------------ Event: time 1669061804.753552, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 798000 Event: time 1669061804.753552, -------------- SYN_REPORT ------------ Event: time 1669061804.760641, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 805000 Event: time 1669061804.760641, -------------- SYN_REPORT ------------ Event: time 1669061804.767491, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 812000 Event: time 1669061804.767491, -------------- SYN_REPORT ------------ Event: time 1669061804.774367, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 819000 Event: time 1669061804.774367, -------------- SYN_REPORT ------------ Event: time 1669061804.781064, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 253 Event: time 1669061804.781064, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 640 Event: time 1669061804.781064, type 3 (EV_ABS), code 0 (ABS_X), value 253 Event: time 1669061804.781064, type 3 (EV_ABS), code 1 (ABS_Y), value 640 Event: time 1669061804.781064, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 826000 Event: time 1669061804.781064, -------------- SYN_REPORT ------------ Event: time 1669061804.788263, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 252 Event: time 1669061804.788263, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 641 Event: time 1669061804.788263, type 3 (EV_ABS), code 0 (ABS_X), value 252 Event: time 1669061804.788263, type 3 (EV_ABS), code 1 (ABS_Y), value 641 Event: time 1669061804.788263, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 833000 Event: time 1669061804.788263, -------------- SYN_REPORT ------------ Event: time 1669061804.795041, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 251 Event: time 1669061804.795041, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 642 Event: time 1669061804.795041, type 3 (EV_ABS), code 0 (ABS_X), value 251 Event: time 1669061804.795041, type 3 (EV_ABS), code 1 (ABS_Y), value 642 Event: time 1669061804.795041, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 840000 Event: time 1669061804.795041, -------------- SYN_REPORT ------------ Event: time 1669061804.801971, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 250 Event: time 1669061804.801971, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 643 Event: time 1669061804.801971, type 3 (EV_ABS), code 0 (ABS_X), value 250 Event: time 1669061804.801971, type 3 (EV_ABS), code 1 (ABS_Y), value 643 Event: time 1669061804.801971, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 847000 Event: time 1669061804.801971, -------------- SYN_REPORT ------------ Event: time 1669061804.808879, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 249 Event: time 1669061804.808879, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 644 Event: time 1669061804.808879, type 3 (EV_ABS), code 0 (ABS_X), value 249 Event: time 1669061804.808879, type 3 (EV_ABS), code 1 (ABS_Y), value 644 Event: time 1669061804.808879, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 854000 Event: time 1669061804.808879, -------------- SYN_REPORT ------------ Event: time 1669061804.815745, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 247 Event: time 1669061804.815745, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645 Event: time 1669061804.815745, type 3 (EV_ABS), code 0 (ABS_X), value 247 Event: time 1669061804.815745, type 3 (EV_ABS), code 1 (ABS_Y), value 645 Event: time 1669061804.815745, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 861000 Event: time 1669061804.815745, -------------- SYN_REPORT ------------ Event: time 1669061804.822648, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 245 Event: time 1669061804.822648, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646 Event: time 1669061804.822648, type 3 (EV_ABS), code 0 (ABS_X), value 245 Event: time 1669061804.822648, type 3 (EV_ABS), code 1 (ABS_Y), value 646 Event: time 1669061804.822648, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 868000 Event: time 1669061804.822648, -------------- SYN_REPORT ------------ Event: time 1669061804.829615, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 243 Event: time 1669061804.829615, type 3 (EV_ABS), code 0 (ABS_X), value 243 Event: time 1669061804.829615, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 875000 Event: time 1669061804.829615, -------------- SYN_REPORT ------------ Event: time 1669061804.836479, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 241 Event: time 1669061804.836479, type 3 (EV_ABS), code 0 (ABS_X), value 241 Event: time 1669061804.836479, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 882000 Event: time 1669061804.836479, -------------- SYN_REPORT ------------ Event: time 1669061804.843657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 239 Event: time 1669061804.843657, type 3 (EV_ABS), code 0 (ABS_X), value 239 Event: time 1669061804.843657, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 889000 Event: time 1669061804.843657, -------------- SYN_REPORT ------------ Event: time 1669061804.850528, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 896000 Event: time 1669061804.850528, -------------- SYN_REPORT ------------ Event: time 1669061804.857484, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 903000 Event: time 1669061804.857484, -------------- SYN_REPORT ------------ Event: time 1669061804.864055, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1669061804.864055, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1669061804.864055, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 Event: time 1669061804.864055, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 910000 Event: time 1669061804.864055, -------------- SYN_REPORT ------------ ^Ct16:~ # seems to me it generates a double tap event, even if fingers at max distance between each other. The question is, is this a driver generated event or is that sent that way already by the hardware? If I understand that correctly then the stream contains ABS_MT_SLOT 0 or 1 event and then a sequence of updates regarding finger0 or finger1 slot . So clearly visible that one finger virtually doesnt move (only some jitter there) but the other finger moves down (Y value increases quickly). Still this is recognized as a two finger scrolling. Im not working on these drivers however if the above stream is just HW stream then this is obviously not correctly converted in the driver into a two finger scrolling event. Should not be a scroll if only one finger moves (and the other finger nearly doesn't). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] New: PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202138 Bug ID: 1202138 Summary: PowerPC machine crashes frequently after upgrading to Leap 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: marius.kittler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading a PowerPC machine (the openQA worker qa-power8-4-kvm.qa.suse.de) from Leap 15.3 to Leap 15.4 that machine crashes frequently. It usually does not stay on for more than a few hours. Downgrading the machine (by rolling back to the last BTRFS snapshot with Leap 15.3) allows the machine to run stable again. Note that there's actually a second machine (the openQA worker qa-power8-5-kvm.qa.suse.de) that we managed to operate without crashes on Leap 15.4. Both machines seems very similar to me so I'm not sure whether one is crashing and the other one not. Note that in the first place both machines did not boot on Leap 15.4. It seemed to be stuck at some point and the kernel logged messages like ``` [ 197.877239][ C62] watchdog: BUG: soft lockup - CPU#62 stuck for 25s! [swapper/62:0]` quite frequently ``` quite frequently. So I added the kernel parameter `nmi_watchdog=0`. With this parameter both machines could boot on Leap 15.4 (but as mentioned only qa-power8-5 runs stable without crashing). So the kernel command line used is: ``` root=UUID=89ca2dff-86af-478b-8d4c-2a45ca689fd5 nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M nmi_watchdog=0 ``` Not sure what other details could be relevant. Unfortunately the journal does not have any interesting message right before the crash. Via SOL I could once see a kernel panic being logged: ``` QA-Power8-4-kvm login: [ 365.807470][ T3923] EXT4-fs error (device sdb1) in ext4_free_inode:362: Corrupt filesystem [ 438.050890][ T94] Kernel panic - not syncing: corrupted stack end detected inside scheduler [ 438.051046][ T94] CPU: 16 PID: 94 Comm: ksof ``` (The filesystem error is likely just a symptom of the crashes.) Any advice what I could try? Maybe another kernel parameter? Maybe booting Leap 15.4 but with the kernel version from 15.3 (not sure how I'd do that, though - so any advice would be welcome if that idea sounds helpful)? By the way, that's `/proc/cpuinfo` on the problematic machine: ``` root=UUID=eebe647f-e867-416e-a0fa-7a6732bfcf9d nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M martchus@QA-Power8-4-kvm:~> cat /proc/cpuinfo processor : 0 cpu : POWER8, altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 7 more times with processor 8, 16, 24, 32, 40, 48 and 56] timebase : 512000000 platform : PowerNV model : 8348-21C machine : PowerNV 8348-21C firmware : OPAL MMU : Hash ``` On the stable machine it looks very similar but it is actually a model with more processors: ``` processor : 0 cpu : POWER8 (raw), altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 13 more times with processor 8, 16, 24, ��] timebase : 512000000 platform : PowerNV model : 8335-GCA machine : PowerNV 8335-GCA firmware : OPAL MMU : Hash ``` That's the relevant ticket on the openQA infrastructure tracker (for additional context): https://progress.opensuse.org/issues/114565 -- You are receiving this mail because: You are the assignee for the bug.

1 32

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c44 --- Comment #44 from Paul Soto <pst73de(a)yahoo.com> --- Input device ID: bus 0x18 vendor 0x4f3 product 0x320b version 0x100 Input device name: "ELAN0683:00 04F3:320B Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 328 (BTN_TOOL_QUINTTAP) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event code 335 (BTN_TOOL_QUADTAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 508 Min 0 Max 3528 Resolution 31 Event code 1 (ABS_Y) Value 1754 Min 0 Max 2002 Resolution 31 Event code 47 (ABS_MT_SLOT) Value 0 Min 0 Max 4 Event code 53 (ABS_MT_POSITION_X) Value 0 Min 0 Max 3528 Resolution 31 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min 0 Max 2002 Resolution 31 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min 0 Max 2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min 0 Max 65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) so does it mean it does not support two finger scrolling event? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Just to be sure, could you check the latest 6.0.9 kernel in OBS Kernel:stable repo? Through a quick glance, there has been no changes for nouveau between 6.0.7 and 6.0.9, so if any, it might be something in a lower layer... Also, please double-check that 6.0.8 is really working. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205359] New: Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*".
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205359 Bug ID: 1205359 Summary: Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*". Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: expeehaa(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Raspberry Pi with MicroOS I want to use a library that requires "/dev/spidev*.*" devices, but when following the guide at https://en.opensuse.org/openSUSE:SPI, none show up, even though the spidev Kernel module is successfully loaded. I��ve obtained the same result with a regular Tumbleweed image, as well as Leap 15.3 and 15.4. On Raspbian on the other hand, it works as expect, but apparently only due to a patch for the spidev source in its kernel: https://github.com/raspberrypi/linux/commit/ea85fb22e836d6457bf69665e65fe60… Using the patch I compiled spidev out-of-tree and got the expected "/dev/spidev0.0" and "/dev/spidev0.1" devices upon modprobing. I have no clue if this is acceptable or if there is a better (easier?) solution, but it would be nice if the patch could be included in kernel-default (at least in Tumbleweed, maybe even in Leap). -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1205597] New: ltp:pyt03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205597 Bug ID: 1205597 Summary: ltp:pyt03:slcan: null-ptr-deref in process_one_work 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: richard.palethorpe(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The LTP test pty03 is causing a null pointer dereference on Tumbleweed in OpenQA: https://openqa.opensuse.org/tests/2891345#step/pty03/9 https://openqa.opensuse.org/tests/2891345/logfile?filename=serial0.txt This has been happening for a month or more: https://openqa.opensuse.org/tests/2891345#next_previous I can't reproduce this on the upstream kernel (v6.0.9). Plus I can't see the connection to SLCAN although I guess it could have submitted faulty data to the workqueue. Or else this is actually a use-after-free of some sort. AFAIK enabling the SLCAN ldisc requires privs. I'd be in favour of moving the module to a separate package or blacklisting it. Below is the decoded stack trace. [ 173.520584][ T348] BUG: kernel NULL pointer dereference, address: 0000000000000008 [ 173.521211][ T348] #PF: supervisor read access in kernel mode [ 173.521711][ T348] #PF: error_code(0x0000) - not-present page [ 173.522197][ T348] PGD 0 P4D 0 [ 173.522641][ T348] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 173.523287][ T348] CPU: 0 PID: 348 Comm: kworker/0:3 Not tainted 6.0.8-1-default #1 openSUSE Tumbleweed 9d20364b934f5aab0a9bdf84e8f45cfdfae39dab [ 173.524682][ T348] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 173.525978][ T348] Workqueue: 0x0 (events) [ 173.526562][ T348] RIP: 0010:process_one_work (/home/rich/kernel/linux/kernel/workqueue.c:706 /home/rich/kernel/linux/kernel/workqueue.c:2185) [ 173.527114][ T348] Code: 49 89 ff 41 56 41 55 41 54 55 53 48 89 f3 48 83 ec 10 48 8b 06 48 8b 6f 48 49 89 c4 45 30 e4 a8 04 b8 00 00 00 00 4c 0f 44 e0 <49> 8b 44 24 08 44 8b a8 00 01 00 00 41 83 e5 20 f6 45 10 04 75 0e All code ======== 0: 49 89 ff mov %rdi,%r15 3: 41 56 push %r14 5: 41 55 push %r13 7: 41 54 push %r12 9: 55 push %rbp a: 53 push %rbx b: 48 89 f3 mov %rsi,%rbx e: 48 83 ec 10 sub $0x10,%rsp 12: 48 8b 06 mov (%rsi),%rax 15: 48 8b 6f 48 mov 0x48(%rdi),%rbp 19: 49 89 c4 mov %rax,%r12 1c: 45 30 e4 xor %r12b,%r12b 1f: a8 04 test $0x4,%al 21: b8 00 00 00 00 mov $0x0,%eax 26: 4c 0f 44 e0 cmove %rax,%r12 2a:* 49 8b 44 24 08 mov 0x8(%r12),%rax <-- trapping instruction 2f: 44 8b a8 00 01 00 00 mov 0x100(%rax),%r13d 36: 41 83 e5 20 and $0x20,%r13d 3a: f6 45 10 04 testb $0x4,0x10(%rbp) 3e: 75 0e jne 0x4e Code starting with the faulting instruction =========================================== 0: 49 8b 44 24 08 mov 0x8(%r12),%rax 5: 44 8b a8 00 01 00 00 mov 0x100(%rax),%r13d c: 41 83 e5 20 and $0x20,%r13d 10: f6 45 10 04 testb $0x4,0x10(%rbp) 14: 75 0e jne 0x24 [ 173.528748][ T348] RSP: 0018:ffffaf7b40f47e98 EFLAGS: 00010046 [ 173.529401][ T348] RAX: 0000000000000000 RBX: ffff9d644e1b8b48 RCX: ffff9d649e439968 [ 173.530031][ T348] RDX: 00000000ffff8455 RSI: ffff9d644e1b8b48 RDI: ffff9d64764aa6c0 [ 173.530660][ T348] RBP: ffff9d649e4335c0 R08: 0000000000000c00 R09: ffff9d64764aa734 [ 173.531300][ T348] R10: 0000000000000007 R11: 0000000000000001 R12: 0000000000000000 [ 173.531959][ T348] R13: ffff9d649e4335e8 R14: ffff9d64490da780 R15: ffff9d64764aa6c0 [ 173.532620][ T348] FS: 0000000000000000(0000) GS:ffff9d649e400000(0000) knlGS:0000000000000000 [ 173.533412][ T348] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 173.534064][ T348] CR2: 0000000000000008 CR3: 0000000036424000 CR4: 00000000000006f0 [ 173.534827][ T348] Call Trace: [ 173.535315][ T348] <TASK> [ 173.535753][ T348] worker_thread (/home/rich/kernel/linux/kernel/workqueue.c:2436) [ 173.536379][ T348] ? process_one_work (/home/rich/kernel/linux/./include/trace/events/workqueue.h:82 /home/rich/kernel/linux/kernel/workqueue.c:2288) [ 173.536947][ T348] kthread (/home/rich/kernel/linux/kernel/kthread.c:376) [ 173.537396][ T348] ? kthread_complete_and_exit (/home/rich/kernel/linux/kernel/kthread.c:331) [ 173.537912][ T348] ret_from_fork (/home/rich/kernel/linux/arch/x86/entry/entry_64.S:312) [ 173.538370][ T348] </TASK> [ 173.538754][ T348] Modules linked in: slcan can_dev ppp_synctty n_hdlc mkiss ax25 ppp_async ppp_generic slip slhc serport af_packet rfkill qrtr snd_hda_codec_generic ledtrig_audio tiny_power_button snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec ppdev snd_hda_core snd_hwdep snd_pcm snd_timer pcspkr virtio_net net_failover snd soundcore failover i2c_piix4 parport_pc button parport joydev nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs dmi_sysfs ip_tables x_tables hid_generic usbhid xhci_pci xhci_pci_renesas xhci_hcd sr_mod cdrom ata_generic usbcore bochs virtio_blk virtio_scsi drm_vram_helper drm_ttm_helper ttm ata_piix floppy serio_raw btrfs blake2b_generic libcrc32c xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua qemu_fw_cfg virtio_rng [ 173.544273][ T348] CR2: 0000000000000008 [ 173.544764][ T348] ---[ end trace 0000000000000000 ]--- [ 173.545331][ T348] RIP: 0010:process_one_work (/home/rich/kernel/linux/kernel/workqueue.c:706 /home/rich/kernel/linux/kernel/workqueue.c:2185) [ 173.545891][ T348] Code: 49 89 ff 41 56 41 55 41 54 55 53 48 89 f3 48 83 ec 10 48 8b 06 48 8b 6f 48 49 89 c4 45 30 e4 a8 04 b8 00 00 00 00 4c 0f 44 e0 <49> 8b 44 24 08 44 8b a8 00 01 00 00 41 83 e5 20 f6 45 10 04 75 0e All code ======== 0: 49 89 ff mov %rdi,%r15 3: 41 56 push %r14 5: 41 55 push %r13 7: 41 54 push %r12 9: 55 push %rbp a: 53 push %rbx b: 48 89 f3 mov %rsi,%rbx e: 48 83 ec 10 sub $0x10,%rsp 12: 48 8b 06 mov (%rsi),%rax 15: 48 8b 6f 48 mov 0x48(%rdi),%rbp 19: 49 89 c4 mov %rax,%r12 1c: 45 30 e4 xor %r12b,%r12b 1f: a8 04 test $0x4,%al 21: b8 00 00 00 00 mov $0x0,%eax 26: 4c 0f 44 e0 cmove %rax,%r12 2a:* 49 8b 44 24 08 mov 0x8(%r12),%rax <-- trapping instruction 2f: 44 8b a8 00 01 00 00 mov 0x100(%rax),%r13d 36: 41 83 e5 20 and $0x20,%r13d 3a: f6 45 10 04 testb $0x4,0x10(%rbp) 3e: 75 0e jne 0x4e Code starting with the faulting instruction =========================================== 0: 49 8b 44 24 08 mov 0x8(%r12),%rax 5: 44 8b a8 00 01 00 00 mov 0x100(%rax),%r13d c: 41 83 e5 20 and $0x20,%r13d 10: f6 45 10 04 testb $0x4,0x10(%rbp) 14: 75 0e jne 0x24 [ 173.547458][ T348] RSP: 0018:ffffaf7b40f47e98 EFLAGS: 00010046 [ 173.548063][ T348] RAX: 0000000000000000 RBX: ffff9d644e1b8b48 RCX: ffff9d649e439968 [ 173.548766][ T348] RDX: 00000000ffff8455 RSI: ffff9d644e1b8b48 RDI: ffff9d64764aa6c0 [ 173.549488][ T348] RBP: ffff9d649e4335c0 R08: 0000000000000c00 R09: ffff9d64764aa734 [ 173.550193][ T348] R10: 0000000000000007 R11: 0000000000000001 R12: 0000000000000000 [ 173.550898][ T348] R13: ffff9d649e4335e8 R14: ffff9d64490da780 R15: ffff9d64764aa6c0 [ 173.551604][ T348] FS: 0000000000000000(0000) GS:ffff9d649e400000(0000) knlGS:0000000000000000 [ 173.552358][ T348] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 173.552998][ T348] CR2: 0000000000000008 CR3: 0000000036424000 CR4: 00000000000006f0 [ 173.553729][ T348] note: kworker/0:3[348] exited with preempt_count 1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205410 https://bugzilla.suse.com/show_bug.cgi?id=1205410#c43 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(pst73de(a)yahoo.com | |) --- Comment #43 from Takashi Iwai <tiwai(a)suse.com> --- That's the full of text, but there is no hardware detail information given yet. So, let's start with that. Could you upload the output of hwinfo from various kernels? e.g. on Leap 15.4 and on 6.1-rcx. Also, please give the dmesg outputs from both cases. Then, try to check the touchpad device with evtest (included in the package evtest). Run it as root on a terminal, and you'll choose the device there. Check the input device capabilities and whether the multi-finger tracking works properly. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204952] New: System crashes when booting first time after kernel update
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204952 Bug ID: 1204952 Summary: System crashes when booting first time after kernel update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I think I had observed this for the last three (or so) kernel updates: When the system boots the new kernel after a kernel update, the system reboots unexpectedly about at the moment when the filesystems were all mounted. Unfortunately there is no trace in journal or messages of that failed boot. However "last" seems to record those. I have: reboot system boot 5.14.21-150400.2 Wed Nov 2 09:21 still running reboot system boot 5.14.21-150400.2 Wed Nov 2 09:20 - 09:20 (00:00) reboot system boot 5.14.21-150400.2 Tue Oct 18 07:59 - 09:19 (15+02:19) reboot system boot 5.14.21-150400.2 Tue Oct 18 07:56 - 07:57 (00:00) reboot system boot 5.14.21-150400.2 Fri Sep 23 12:07 - 13:00 (7+00:53) reboot system boot 5.14.21-150400.2 Fri Sep 23 12:05 - 12:05 (00:00) reboot system boot 5.14.21-150400.2 Thu Sep 15 12:08 - 12:04 (7+23:55) reboot system boot 5.14.21-150400.2 Thu Sep 15 12:07 - 12:07 (00:00) reboot system boot 5.14.21-150400.2 Tue Aug 16 08:55 - 11:57 (30+03:01) reboot system boot 5.14.21-150400.2 Tue Aug 16 08:46 - 08:54 (00:07) reboot system boot 5.14.21-150400.2 Thu Jul 28 07:43 - 08:22 (19+00:38) reboot system boot 5.14.21-150400.2 Sun Jul 24 16:31 - 23:07 (3+06:36) reboot system boot 5.14.21-150400.2 Sun Jul 24 16:20 - 16:30 (00:09) reboot system boot 5.14.21-150400.2 Fri Jul 22 23:39 - 16:19 (1+16:39) reboot system boot 5.14.21-150400.2 Mon Jul 18 14:38 - 14:58 (4+00:19) reboot system boot 5.14.21-150400.2 Thu Jul 14 12:07 - 10:09 (3+22:02) You see that starting around August 16th, there are two boots within rather short time (a boot here takes some time as I have to enter passwords for encrypted filesystems three times, and GRUB's decryption is rather slow, too). You also see that the new kernel version strings are not quite compatible with "last" (they are too long). -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205576 Philippe Cond� <conde.philippe(a)skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(conde.philippe@sk | |ynet.be) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c42 --- Comment #42 from Paul Soto <pst73de(a)yahoo.com> --- only part of the issues would be a resume problem. E.g. the bad two finger detection happens all the time, also without STR -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205576 http://bugzilla.opensuse.org/show_bug.cgi?id=1205576#c2 --- Comment #2 from Philippe Cond� <conde.philippe(a)skynet.be> --- Hello, I tested with kernel 6.0.8-xen today and after 15-30mn the system locked when playing pysolFC I rebooted in kernel 6.0.7-default and I had no lock when playing PysolFC for more than 2 hours. So seems related to kernel 6.0.8. Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Thinkpad T16 touchpad does |Thinkpad T16 touchpad does |not work correctly |not work correctly after | |resume -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c41 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum(a)suse.com, | |sndirsch(a)suse.com Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de Flags|needinfo? | --- Comment #41 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So looks like a kernel (driver) resume issue. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205576 http://bugzilla.opensuse.org/show_bug.cgi?id=1205576#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |conde.philippe(a)skynet.be, | |tiwai(a)suse.com Flags| |needinfo?(conde.philippe@sk | |ynet.be) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Looks more like a bug in nouveau. Is it a regression from earlier kernels? If it's a regression and can be reproduced, could you identify which kernel started showing the problem? You can find some old 6.0.x kernel packages in OBS history repo, http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 19 Nov '22

19 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205576 Christophe Giboudeaux <christophe(a)krop.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Applications |Kernel Assignee|opensuse-kde-bugs@opensuse. |kernel-bugs(a)opensuse.org |org | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 https://bugzilla.suse.com/show_bug.cgi?id=1204705#c34 --- Comment #34 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:4072-1: An update that solves 32 vulnerabilities, contains 25 features and has 36 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1152472,1152489,1188238,1194869,1196018,1196632,1199904,1200567,1200692,1200788,1202187,1202686,1202700,1202914,1203098,1203229,1203290,1203435,1203514,1203699,1203767,1203802,1203922,1204017,1204142,1204166,1204168,1204171,1204241,1204353,1204354,1204355,1204402,1204413,1204415,1204417,1204428,1204431,1204439,1204470,1204479,1204498,1204533,1204569,1204574,1204575,1204619,1204635,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204753,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970 CVE References: CVE-2022-1882,CVE-2022-2153,CVE-2022-28748,CVE-2022-2964,CVE-2022-2978,CVE-2022-3169,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3640,CVE-2022-3646,CVE-2022-3649,CVE-2022-40476,CVE-2022-40768,CVE-2022-42703,CVE-2022-43750 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1649,PED-634,PED-676,PED-678,PED-679,PED-707,PED-732,PED-813,PED-817,PED-822,PED-825,PED-833,PED-842,PED-846,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-9246 Sources used: openSUSE Leap 15.4 (src): dtb-aarch64-5.14.21-150400.24.33.1, kernel-64kb-5.14.21-150400.24.33.2, kernel-debug-5.14.21-150400.24.33.2, kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4, kernel-docs-5.14.21-150400.24.33.2, kernel-kvmsmall-5.14.21-150400.24.33.2, kernel-obs-build-5.14.21-150400.24.33.1, kernel-obs-qa-5.14.21-150400.24.33.1, kernel-source-5.14.21-150400.24.33.1, kernel-syms-5.14.21-150400.24.33.1, kernel-zfcpdump-5.14.21-150400.24.33.2 SUSE Linux Enterprise Workstation Extension 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 SUSE Linux Enterprise Module for Live Patching 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2, kernel-livepatch-SLE15-SP4_Update_5-1-150400.9.3.4 SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 SUSE Linux Enterprise Module for Development Tools 15-SP4 (src): kernel-docs-5.14.21-150400.24.33.2, kernel-obs-build-5.14.21-150400.24.33.1, kernel-source-5.14.21-150400.24.33.1, kernel-syms-5.14.21-150400.24.33.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): kernel-64kb-5.14.21-150400.24.33.2, kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4, kernel-source-5.14.21-150400.24.33.1, kernel-zfcpdump-5.14.21-150400.24.33.2 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4 SUSE Linux Enterprise High Availability 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 H�ctor Or�n Mart�nez <hector.oron(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Hardware|LittleEndian |PowerPC-64 Assignee|kernel-bugs(a)opensuse.org |bugproxy(a)us.ibm.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205552] New: xfstests btrfs/021 fails
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205552 Bug ID: 1205552 Summary: xfstests btrfs/021 fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://openqa.opensuse.org/tests/2883505#step/btrfs-021/2 [version] kernel-default-6.0.8-1.1.x86_64 btrfsprogs-6.0-1.1.x86_64 xfsdump-3.1.11-1.1.x86_64 xfsprogs-5.19.0-1.2.x86_64 xfstests-1.1.1+git.20220820-1.1.x86_64 6.0.8-1-default Name : kernel-default Version : 6.0.8 Release : 1.1 Architecture: x86_64 Install Date: Thu Nov 17 09:52:54 2022 Group : System/Kernel Size : 286823886 License : GPL-2.0-only Signature : RSA/SHA256, Sat Nov 12 13:45:49 2022, Key ID b88b2fd43dbdc284 Source RPM : kernel-default-6.0.8-1.1.nosrc.rpm Build Date : Sat Nov 12 13:40:32 2022 Build Host : stones Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2022-11-11 08:02:50 +0000 GIT Revision: 1579d93a204dab0da2ae1ae638af853b9b6ca66e GIT Branch: stable Distribution: openSUSE Tumbleweed [environment] 1 config file for xfstests export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_MNT=/mnt/scratch export SCRATCH_DEV_POOL="/dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5" export KEEP_DMESG=yes 2. device size /dev/loop0 3840M /dev/loop1 3840M /dev/loop2 3840M /dev/loop3 3840M /dev/loop4 3840M /dev/loop5 3840M [output] FSTYP -- btrfs PLATFORM -- Linux/x86_64 susetest 6.0.8-1-default #1 SMP PREEMPT_DYNAMIC Fri Nov 11 08:02:50 UTC 2022 (1579d93) MKFS_OPTIONS -- /dev/loop1 MOUNT_OPTIONS -- /dev/loop1 /mnt/scratch btrfs/021 QA output created by 021 /mnt/scratch/padding-0 /mnt/scratch/padding-1 /mnt/scratch/padding-2 /mnt/scratch/padding-3 /mnt/scratch/padding-4 /mnt/scratch/padding-5 /mnt/scratch/padding-6 /mnt/scratch/padding-7 /mnt/scratch/padding-8 /mnt/scratch/padding-9 /mnt/scratch/padding-10 /mnt/scratch/padding-11 /mnt/scratch/padding-12 /mnt/scratch/padding-13 /mnt/scratch/padding-14 /mnt/scratch/padding-15 /mnt/scratch/padding-16 /mnt/scratch/padding-17 /mnt/scratch/padding-18 /mnt/scratch/padding-19 /mnt/scratch/padding-20 /mnt/scratch/padding-21 /mnt/scratch/padding-22 /mnt/scratch/padding-23 /mnt/scratch/padding-24 /mnt/scratch/padding-25 /mnt/scratch/padding-26 /mnt/scratch/padding-27 /mnt/scratch/padding-28 /mnt/scratch/padding-29 /mnt/scratch/padding-30 /mnt/scratch/padding-31 /mnt/scratch/padding-32 /mnt/scratch/padding-33 /mnt/scratch/padding-34 /mnt/scratch/padding-35 /mnt/scratch/padding-36 /mnt/scratch/padding-37 /mnt/scratch/padding-38 /mnt/scratch/padding-39 /mnt/scratch/padding-40 /mnt/scratch/padding-41 /mnt/scratch/padding-42 /mnt/scratch/padding-43 /mnt/scratch/padding-44 /mnt/scratch/padding-45 /mnt/scratch/padding-46 /mnt/scratch/padding-47 /mnt/scratch/padding-48 /mnt/scratch/padding-49 /mnt/scratch/padding-50 /mnt/scratch/padding-51 /mnt/scratch/padding-52 /mnt/scratch/padding-53 /mnt/scratch/padding-54 /mnt/scratch/padding-55 /mnt/scratch/padding-56 /mnt/scratch/padding-57 /mnt/scratch/padding-58 /mnt/scratch/padding-59 /mnt/scratch/padding-60 /mnt/scratch/padding-61 /mnt/scratch/padding-62 /mnt/scratch/padding-63 /mnt/scratch/padding-64 /mnt/scratch/padding-65 /mnt/scratch/padding-66 /mnt/scratch/padding-67 /mnt/scratch/padding-68 /mnt/scratch/padding-69 /mnt/scratch/padding-70 /mnt/scratch/padding-71 /mnt/scratch/padding-72 /mnt/scratch/padding-73 /mnt/scratch/padding-74 /mnt/scratch/padding-75 /mnt/scratch/padding-76 /mnt/scratch/padding-77 /mnt/scratch/padding-78 /mnt/scratch/padding-79 /mnt/scratch/padding-80 /mnt/scratch/padding-81 /mnt/scratch/padding-82 /mnt/scratch/padding-83 /mnt/scratch/padding-84 /mnt/scratch/padding-85 /mnt/scratch/padding-86 /mnt/scratch/padding-87 /mnt/scratch/padding-88 /mnt/scratch/padding-89 /mnt/scratch/padding-90 /mnt/scratch/padding-91 /mnt/scratch/padding-92 /mnt/scratch/padding-93 /mnt/scratch/padding-94 /mnt/scratch/padding-95 /mnt/scratch/padding-96 /mnt/scratch/padding-97 /mnt/scratch/padding-98 /mnt/scratch/padding-99 /mnt/scratch/padding-100 /mnt/scratch/foo-0 /mnt/scratch/foo-1 /mnt/scratch/foo-2 /mnt/scratch/foo-3 /mnt/scratch/foo-4 /mnt/scratch/foo-5 /mnt/scratch/foo-6 /mnt/scratch/foo-7 /mnt/scratch/foo-8 /mnt/scratch/foo-9 /mnt/scratch/foo-10 /mnt/scratch/foo-11 /mnt/scratch/foo-12 /mnt/scratch/foo-13 /mnt/scratch/foo-14 /mnt/scratch/foo-15 /mnt/scratch/foo-16 /mnt/scratch/foo-17 /mnt/scratch/foo-18 /mnt/scratch/foo-19 /mnt/scratch/foo-20 /mnt/scratch/foo-21 /mnt/scratch/foo-22 /mnt/scratch/foo-23 /mnt/scratch/foo-24 /mnt/scratch/foo-25 /mnt/scratch/foo-26 /mnt/scratch/foo-27 /mnt/scratch/foo-28 /mnt/scratch/foo-29 /mnt/scratch/foo-30 /mnt/scratch/foo-31 /mnt/scratch/foo-32 /mnt/scratch/foo-33 /mnt/scratch/foo-34 /mnt/scratch/foo-35 /mnt/scratch/foo-36 /mnt/scratch/foo-37 /mnt/scratch/foo-38 /mnt/scratch/foo-39 /mnt/scratch/foo-40 /mnt/scratch/foo-41 /mnt/scratch/foo-42 /mnt/scratch/foo-43 /mnt/scratch/foo-44 /mnt/scratch/foo-45 /mnt/scratch/foo-46 /mnt/scratch/foo-47 /mnt/scratch/foo-48 /mnt/scratch/foo-49 /mnt/scratch/foo-50 Silence is golden - output mismatch (see /opt/xfstests/results//btrfs/021.out.bad) --- tests/btrfs/021.out 2022-09-05 15:25:14.000000000 -0400 +++ /opt/xfstests/results//btrfs/021.out.bad 2022-11-17 15:15:17.331712251 -0500 @@ -1,2 +1,154 @@ QA output created by 021 +/mnt/scratch/padding-0 +/mnt/scratch/padding-1 +/mnt/scratch/padding-2 +/mnt/scratch/padding-3 +/mnt/scratch/padding-4 +/mnt/scratch/padding-5 ... (Run diff -u /opt/xfstests/tests/btrfs/021.out /opt/xfstests/results//btrfs/021.out.bad to see the entire diff) Ran: btrfs/021 Failures: btrfs/021 Failed 1 of 1 tests out.bad full dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203800] Recent Kernel Updates (likely) broke backintime
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203800 http://bugzilla.opensuse.org/show_bug.cgi?id=1203800#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |c.buhtz(a)posteo.jp --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the information! I reassign this bug to you for handling further, then. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203800] Recent Kernel Updates (likely) broke backintime
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203800 http://bugzilla.opensuse.org/show_bug.cgi?id=1203800#c2 buhtz buhtz <c.buhtz(a)posteo.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |c.buhtz(a)posteo.jp --- Comment #2 from buhtz buhtz <c.buhtz(a)posteo.jp> --- Hello, I'm one of the upstream maintainers of "Back In Time" (BIT). I assume it is not related to the kernel. The bug is known at upstream: https://github.com/bit-team/backintime/issues/921 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205506] New: [Leap][15.4][transactional server] kdump service fails to start
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205506 Bug ID: 1205506 Summary: [Leap][15.4][transactional server] kdump service fails to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The system role is transactional server, so root file system is readonly. === susetest:~ # cat /etc/*release NAME="openSUSE Leap" VERSION="15.4" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.4" PRETTY_NAME="openSUSE Leap 15.4" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.4" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" susetest:~ # rpm -qa|grep kdump yast2-kdump-4.4.4-150400.3.3.1.x86_64 kdump-1.0.2+git14.gb49d4a3-150400.3.5.1.x86_64 susetest:~ # uname -r 5.14.21-150400.24.28-default === susetest:~ # systemctl restart kdump Job for kdump.service failed because the control process exited with error code. See "systemctl status kdump.service" and "journalctl -xeu kdump.service" for details. susetest:~ # journalctl -xeu kdump.service �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit kdump.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Nov 17 01:54:16 susetest systemd[1]: kdump.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit kdump.service has entered the 'failed' state with result 'exit-code'. Nov 17 01:54:16 susetest systemd[1]: Failed to start Load kdump kernel and initrd. �� Subject: A start job for unit kdump.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has finished with a failure. �� The job identifier is 880 and the job result is failed. Nov 17 01:56:58 susetest systemd[1]: Starting Load kdump kernel and initrd... �� Subject: A start job for unit kdump.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has begun execution. �� The job identifier is 1068. Nov 17 01:56:59 susetest load.sh[15275]: Regenerating kdump initrd ... Nov 17 01:56:59 susetest load.sh[15275]: dracut: Executing: /usr/bin/dracut --force --hostonly --no-hostonly-default-device --omit "plymouth resume usrmount" --compress "xz -0 --check=crc32" --add kdump /boot/initrd-5.14.21-150400.24.28-> Nov 17 01:56:59 susetest load.sh[15275]: dracut: No permission to write to /boot. Nov 17 01:56:59 susetest systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit kdump.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Nov 17 01:56:59 susetest systemd[1]: kdump.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit kdump.service has entered the 'failed' state with result 'exit-code'. Nov 17 01:56:59 susetest systemd[1]: Failed to start Load kdump kernel and initrd. �� Subject: A start job for unit kdump.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has finished with a failure. �� The job identifier is 1068 and the job result is failed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1204382] New: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204382 Bug ID: 1204382 Summary: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrian.schroeter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We noticed that the kernel-obs-build is not loading in KVM for armv7l anymore. This was noticed in openSUSE:Step:15.3 project, but we used this kernel also so far as default kernel for any distributions which do not bring their own kernel. Switching to SP4 has solved the issues, but SP3 kernel used to work also. It might be caused by switching to SP4 as host OS (qemu 5.3 to 6.2), not verified yet. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1205447] New: machine keyring is not enabled
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205447 Bug ID: 1205447 Summary: machine keyring is not enabled 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- machine keyring is the upstream solution for making MOK available to the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 LTC BugProxy <bugproxy(a)us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=200524 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 https://bugzilla.suse.com/show_bug.cgi?id=1204277#c5 --- Comment #5 from G�ry Schneider <gery.schneider(a)fr.ibm.com> --- Hello SUSE, I have mirrored this bug to IBM LTC Bug 200524. The IBM team update about it will show up here. Thank you for your support. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c9 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Yep, tested on RPi4 with upcoming TW kernel 6.0.9 which has above patch, system boot to graphical login screen. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 Mark Cowley <mcowley(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hector.oron(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c8 Stefan Wahren <stefan.wahren(a)i2se.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.wahren(a)i2se.com --- Comment #8 from Stefan Wahren <stefan.wahren(a)i2se.com> --- There is already a fix (mainline and in 6.0.9) which should address this issue: drm/vc4: hdmi: Fix HSM clock too low on Pi4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov(a)suse.com, | |mbrugger(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like the known issue we've hit. Adding more people to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ray.jantz(a)gmail.c | |om) | --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The thread can be seen at: https://lore.kernel.org/all/ba072331-b7db-edc3-de77-4496d402f497@gmail.com/ The problem seems to be known. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c67 --- Comment #67 from Phi <comphi(a)protonmail.com> --- (In reply to Takashi Iwai from comment #66) > (In reply to Phi from comment #65) > > Hello, > > my Zenbook has the same issue. > > cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA > > cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. > > It would be nice if you could add them to the patch as well. > > Does the problem happen with the latest TW kernel, too? Luckily, it somehow works now, at least in TW. I found out that there is a bios update so I applied it. I also disabled secure boot and did a fresh install of TW (6.0.8). Not sure which part fixed it, but the problem is gone now. I also installed arch 6.0.8, and the problem still happens there, but I guess that is a different story. Maybe 6.1 will fix it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 https://bugzilla.suse.com/show_bug.cgi?id=1204705#c33 --- Comment #33 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3998-1: An update that solves 37 vulnerabilities, contains 25 features and has 38 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1152472,1152489,1188238,1194869,1196018,1196632,1199904,1200567,1200692,1200788,1202187,1202686,1202700,1202914,1203098,1203229,1203290,1203435,1203514,1203699,1203701,1203767,1203770,1203802,1203922,1203979,1204017,1204051,1204059,1204060,1204125,1204142,1204166,1204168,1204171,1204241,1204353,1204354,1204355,1204402,1204413,1204415,1204417,1204428,1204431,1204439,1204470,1204479,1204498,1204533,1204569,1204574,1204575,1204619,1204635,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204753,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970 CVE References: CVE-2022-1882,CVE-2022-2153,CVE-2022-28748,CVE-2022-2964,CVE-2022-2978,CVE-2022-3169,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3640,CVE-2022-3646,CVE-2022-3649,CVE-2022-40476,CVE-2022-40768,CVE-2022-41674,CVE-2022-42703,CVE-2022-42719,CVE-2022-42720,CVE-2022-42721,CVE-2022-42722,CVE-2022-43750 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1649,PED-634,PED-676,PED-678,PED-679,PED-707,PED-732,PED-813,PED-817,PED-822,PED-825,PED-833,PED-842,PED-846,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-9246 Sources used: openSUSE Leap 15.4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c3 Pablo Alonso <tau0(a)tutanota.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Pablo Alonso <tau0(a)tutanota.com> --- I've installed it successfully today. It was because of Ventoy -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c4 --- Comment #4 from Ray Jantz <ray.jantz(a)gmail.com> --- The message ID for my bug submission to linux-wireless is: <ba072331-b7db-edc3-de77-4496d402f497(a)gmail.com> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] New: WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205259 Bug ID: 1205259 Summary: WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862768 --> http://bugzilla.opensuse.org/attachment.cgi?id=862768&action=edit Dmesg ouput On my raspberry pi400 when I boot with kernel 6.0.7-1 I can select the boot but after display "loading initial ramdisk" the screen goes black and nothing is displayed. I can login via ssh.So the system is started correctly but nothing is displayed. If at boot I select kernel 6.0.3 the login screen is correzctly displayed n the hdmi screen and I can login. I attach the dmesg output and the Xorg.0.log logfile when booting kernel 6.0.7-1 Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c2 --- Comment #2 from Pablo Alonso <tau0(a)tutanota.com> --- The history doesn't go far enough to test it. Also, I could only boot in recovery mode. I can try to install Leap and then transform it to Thumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] New: KDE Plasma fails to start with Kernel 6.0.3
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204705 Bug ID: 1204705 Summary: KDE Plasma fails to start with Kernel 6.0.3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: postix(a)posteo.eu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since updating from kernel 6.0.2 to 6.0.3 on openSUSE TW, KDE Plasma 5.26.1 running X11 or Wayland fails to start, after logging in from SDDM: * The cursor works, but no panel shows up, the desktop starts to freeze, i.e. turns gray after a while * Pressing CTRL+ALT+DEL opens the power-management overlay, where logging out works * Shutting down the system does not work after having logged in once, but takes infinitely long and requires a forced shut down Going back to kernel 6.0.2 fixes the issue. An interesting part of the journalctl is likely the following: ``` 09:56:43 kernel: BUG: kernel NULL pointer dereference, address: 00000000000001c8 09:56:43 kernel: #PF: supervisor write access in kernel mode 09:56:43 kernel: #PF: error_code(0x0002) - not-present page 09:56:43 kernel: PGD 0 P4D 0 09:56:43 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI 09:56:43 kernel: CPU: 16 PID: 1419 Comm: rasdaemon Tainted: G O 6.0.3-1-default #1 openSUSE Tumbleweed 50a6ebc5cb1873d6b9c639843cdd1ed0089a1281 09:56:43 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 4204 02/24/2022 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 09:56:43 kernel: Call Trace: 09:56:43 kernel: <TASK> 09:56:43 kernel: tracing_buffers_release+0x49/0x90 09:56:43 kernel: __fput+0x91/0x250 09:56:43 kernel: task_work_run+0x5c/0x90 09:56:43 kernel: exit_to_user_mode_prepare+0x1cb/0x1f0 09:56:43 kernel: syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd 09:56:43 kernel: RIP: 0033:0x7fd74658e014 09:56:43 kernel: Code: 00 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 80 3d 8d 09 0f 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 51 09:56:43 kernel: RSP: 002b:00007ffce5e64348 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 09:56:43 kernel: RAX: 0000000000000000 RBX: 00007ffce5e64490 RCX: 00007fd74658e014 09:56:43 kernel: RDX: 0000000000000000 RSI: 00007ffce5e64540 RDI: 000000000000001d 09:56:43 kernel: RBP: 00007ffce5e65a10 R08: 000055939344e6c0 R09: 0000000000000000 09:56:43 kernel: R10: 0000000000000008 R11: 0000000000000202 R12: 0000000000000001 09:56:43 kernel: R13: 00007ffce5e644d8 R14: 000055939344e6c0 R15: 000055939344e6c0 09:56:43 kernel: </TASK> 09:56:43 kernel: Modules linked in: amd64_edac(-) cmac algif_hash algif_skcipher af_alg vboxdrv(O) qrtr bnep dmi_sysfs wacom nls_iso8859_1 nls_cp437 vfat fat intel_rapl_msr iwlmvm intel_rapl_common asus_ec_sensors mac80211 libarc4 snd_hda_codec_realtek snd_hda_codec_generic btusb edac_mce_amd snd_hda_codec_hdmi btrtl snd_usb_audio btbcm snd_hda_intel btintel snd_intel_dspcfg btmtk snd_intel_sdw_acpi kvm_amd snd_hda_codec snd_usbmidi_lib iwlwifi bluetooth snd_rawmidi snd_hda_core joydev snd_seq_device kvm ecdh_generic eeepc_wmi snd_hwdep asus_wmi cfg80211 battery snd_pcm irqbypass ledtrig_audio sparse_keymap r8169 platform_profile snd_timer video pcspkr wmi_bmof efi_pstore mxm_wmi realtek snd igb k10temp i2c_piix4 mdio_devres soundcore libphy rfkill dca tiny_power_button button acpi_cpufreq fuse configfs ip_tables x_tables hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul xhci_pci xhci_pci_renesas drm_ttm_helper ttm xhci_hcd 09:56:43 kernel: iommu_v2 gpu_sched ghash_clmulni_intel drm_buddy aesni_intel drm_display_helper nvme usbcore crypto_simd cryptd cec ccp nvme_core sp5100_tco rc_core wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq v4l2loopback(O) videodev mc sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 09:56:43 kernel: CR2: 00000000000001c8 09:56:43 kernel: ---[ end trace 0000000000000000 ]--- 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 ``` SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221023 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-1-default (64-bit) / 6.0.3-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c66 --- Comment #66 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Phi from comment #65) > Hello, > my Zenbook has the same issue. > cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA > cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. > It would be nice if you could add them to the patch as well. Does the problem happen with the latest TW kernel, too? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Great, could you point the URL (or Message-Id of your post) for tracking? It should be visible on lore.kernel.org. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205277] Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205277 Goldwyn Rodrigues <rgoldwyn(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |fdmanana(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205277] Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 13 Nov '22

13 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205277 https://bugzilla.suse.com/show_bug.cgi?id=1205277#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgoldwyn(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Something for filesystem team? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c2 --- Comment #2 from Ray Jantz <ray.jantz(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > Unless it's a regression, it's rather a thing to be reported to the upstream. > Could you try to report it the upstream, e.g. linux-wireless ML? I submitted it to linux-wireless. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205365] New: soft lockup - CPU Stuck
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205365 Bug ID: 1205365 Summary: soft lockup - CPU Stuck 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: j(a)ganomi.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to kernel 6.x I am getting CPU Stuck errors which crash my Thinkpad laptop. This is happening intermittently. My current kernel is 6.0.6-1-default, but this has been happening with all 6.x kernels. Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [swapper/4:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G O 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0x8/0x20 Nov 12 15:58:18 superman kernel: Code: 01 c3 cc cc cc cc 48 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 <48> 89 c2 48 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b100250de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f567e38d400 RBX: ffff9f57e9ea5780 RCX: ffff9f567e38d400 Nov 12 15:58:18 superman kernel: RDX: ffff9f567e38d400 RSI: ffff9f57e9ea58e0 RDI: ffff9f57e9ea58e0 Nov 12 15:58:18 superman kernel: RBP: 0000000000000036 R08: ffff9f57e9ea58e0 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000003 Nov 12 15:58:18 superman kernel: R13: 00000000000005a0 R14: 000000000000025e R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f500000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2ca90c2000 CR3: 0000000348d06001 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: tcp_send_loss_probe+0x170/0x1d0 Nov 12 15:58:18 superman kernel: tcp_write_timer+0x99/0xd0 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: call_timer_fn+0x24/0x130 Nov 12 15:58:18 superman kernel: __run_timers.part.0+0x1d7/0x260 Nov 12 15:58:18 superman kernel: ? __hrtimer_run_queues+0x159/0x2c0 Nov 12 15:58:18 superman kernel: ? ktime_get+0x35/0xa0 Nov 12 15:58:18 superman kernel: run_timer_softirq+0x26/0x50 Nov 12 15:58:18 superman kernel: __do_softirq+0xc2/0x2a3 Nov 12 15:58:18 superman kernel: __irq_exit_rcu+0xaa/0xe0 Nov 12 15:58:18 superman kernel: sysvec_apic_timer_interrupt+0x6e/0x90 Nov 12 15:58:18 superman kernel: </IRQ> Nov 12 15:58:18 superman kernel: <TASK> Nov 12 15:58:18 superman kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Nov 12 15:58:18 superman kernel: RIP: 0010:cpuidle_enter_state+0xde/0x420 Nov 12 15:58:18 superman kernel: Code: 00 00 31 ff e8 13 cf 85 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 c8 c4 8c ff fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b10013fe90 EFLAGS: 00000246 Nov 12 15:58:18 superman kernel: RAX: ffff9f5d1f533bc0 RBX: ffffd9b0ffb01200 RCX: 0000000000000000 Nov 12 15:58:18 superman kernel: RDX: 0000000000000004 RSI: 000064e982a14ffa RDI: 0000000000000000 Nov 12 15:58:18 superman kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 000000003161f86e Nov 12 15:58:18 superman kernel: R10: 0000000000000018 R11: 00000000000001e5 R12: ffffffff918246a0 Nov 12 15:58:18 superman kernel: R13: 000068081530de4c R14: 0000000000000002 R15: 0000000000000000 Nov 12 15:58:18 superman kernel: cpuidle_enter+0x29/0x40 Nov 12 15:58:18 superman kernel: do_idle+0x202/0x2a0 Nov 12 15:58:18 superman kernel: cpu_startup_entry+0x19/0x20 Nov 12 15:58:18 superman kernel: start_secondary+0x114/0x140 Nov 12 15:58:18 superman kernel: secondary_startup_64_no_verify+0xe5/0xeb Nov 12 15:58:18 superman kernel: </TASK> Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [swapper/6:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 6 PID: 0 Comm: swapper/6 Tainted: G O L 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0xf/0x20 Nov 12 15:58:18 superman kernel: Code: 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 48 89 c2 48 8b 40 10 <48> 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 eb f4 48 8b 07 48 85 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b1002b8de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f5656e41200 RBX: ffff9f57e9ea6900 RCX: ffff9f5656e41200 Nov 12 15:58:18 superman kernel: RDX: ffff9f5656e41200 RSI: ffff9f57e9ea6a60 RDI: ffff9f57e9ea6a60 Nov 12 15:58:18 superman kernel: RBP: 000000000000003d R08: ffff9f57e9ea6a60 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000002 Nov 12 15:58:18 superman kernel: R13: 00000000000005a8 R14: 000000000000001f R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f580000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2c15673000 CR3: 0000000525210006 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: Collecting data: trigger 2 fired. Nov 12 15:57:52 superman rtkit-daemon[2184]: Supervising 1 threads of 1 processes of 1 users. Nov 12 15:57:52 superman rtkit-daemon[2184]: Supervising 1 threads of 1 processes of 1 users. Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [swapper/4:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G O 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0x8/0x20 Nov 12 15:58:18 superman kernel: Code: 01 c3 cc cc cc cc 48 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 <48> 89 c2 48 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b100250de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f567e38d400 RBX: ffff9f57e9ea5780 RCX: ffff9f567e38d400 Nov 12 15:58:18 superman kernel: RDX: ffff9f567e38d400 RSI: ffff9f57e9ea58e0 RDI: ffff9f57e9ea58e0 Nov 12 15:58:18 superman kernel: RBP: 0000000000000036 R08: ffff9f57e9ea58e0 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000003 Nov 12 15:58:18 superman kernel: R13: 00000000000005a0 R14: 000000000000025e R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f500000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2ca90c2000 CR3: 0000000348d06001 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: tcp_send_loss_probe+0x170/0x1d0 Nov 12 15:58:18 superman kernel: tcp_write_timer+0x99/0xd0 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: call_timer_fn+0x24/0x130 Nov 12 15:58:18 superman kernel: __run_timers.part.0+0x1d7/0x260 Nov 12 15:58:18 superman kernel: ? __hrtimer_run_queues+0x159/0x2c0 Nov 12 15:58:18 superman kernel: ? ktime_get+0x35/0xa0 Nov 12 15:58:18 superman kernel: run_timer_softirq+0x26/0x50 Nov 12 15:58:18 superman kernel: __do_softirq+0xc2/0x2a3 Nov 12 15:58:18 superman kernel: __irq_exit_rcu+0xaa/0xe0 Nov 12 15:58:18 superman kernel: sysvec_apic_timer_interrupt+0x6e/0x90 Nov 12 15:58:18 superman kernel: </IRQ> Nov 12 15:58:18 superman kernel: <TASK> Nov 12 15:58:18 superman kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Nov 12 15:58:18 superman kernel: RIP: 0010:cpuidle_enter_state+0xde/0x420 Nov 12 15:58:18 superman kernel: Code: 00 00 31 ff e8 13 cf 85 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 c8 c4 8c ff fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b10013fe90 EFLAGS: 00000246 Nov 12 15:58:18 superman kernel: RAX: ffff9f5d1f533bc0 RBX: ffffd9b0ffb01200 RCX: 0000000000000000 Nov 12 15:58:18 superman kernel: RDX: 0000000000000004 RSI: 000064e982a14ffa RDI: 0000000000000000 Nov 12 15:58:18 superman kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 000000003161f86e Nov 12 15:58:18 superman kernel: R10: 0000000000000018 R11: 00000000000001e5 R12: ffffffff918246a0 Nov 12 15:58:18 superman kernel: R13: 000068081530de4c R14: 0000000000000002 R15: 0000000000000000 Nov 12 15:58:18 superman kernel: cpuidle_enter+0x29/0x40 Nov 12 15:58:18 superman kernel: do_idle+0x202/0x2a0 Nov 12 15:58:18 superman kernel: cpu_startup_entry+0x19/0x20 Nov 12 15:58:18 superman kernel: start_secondary+0x114/0x140 Nov 12 15:58:18 superman kernel: secondary_startup_64_no_verify+0xe5/0xeb Nov 12 15:58:18 superman kernel: </TASK> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205288] New: kernel-default-6.0.7-1.1 breaks wifi on Opensuse Tumbleweed
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205288 Bug ID: 1205288 Summary: kernel-default-6.0.7-1.1 breaks wifi on Opensuse Tumbleweed 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: chingmichaellee2016(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862786 --> http://bugzilla.opensuse.org/attachment.cgi?id=862786&action=edit this is the result after updating to kernel-default-6.0.7-1.1.x86_64 Wifi not working on kernel-default-6.0.7-1.1 opensuse tumbleweed KDE plasma WiFi card: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) Drivers and firmware are install. But no wifi adapter is shown on kde networkmanager -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205277] New: Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205277 Bug ID: 1205277 Summary: Kernel crash at full btrfs balance Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862780 --> http://bugzilla.opensuse.org/attachment.cgi?id=862780&action=edit kernel crash and detail infos of the filesystem a full btrfs balance leads reproducably to a kernel crash (on kernel 5.14.21-150400.24.28-default, 5.14.21-150400.24.18-default) and afterwards to a readonly filesystem. A reboot is necessary to get a writable filesystem again. Interesting is, that balances are running, if executed with steps (with musage or dusage) scrubs doesn't show any errors on the filesystem. The only problem could be that internal space is almost full, if i interpret the output correctly: Label: 'boot1' uuid: 42e9a4d7-878e-457a-ab99-98106b1b556c Total devices 1 FS bytes used 724.80MiB devid 1 size 1.00GiB used 927.00MiB path /dev/mapper/system-boot1 But i can't reduce the space with the incremental balances. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c65 Phi <comphi(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comphi(a)protonmail.com --- Comment #65 from Phi <comphi(a)protonmail.com> --- Hello, my Zenbook has the same issue. cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. It would be nice if you could add them to the patch as well. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c31 --- Comment #31 from Michal Suchanek <msuchanek(a)suse.com> --- What kind of hardware is powerqaworker-qam-1.qa.suse.de? So far the problematic workers were POWER8 which use the old KVM code which gets very little testing upstream. Further, the problematic workers use 'openpower' firmware. That's some specific firmware different from what most machines use, and the little testing that is done by upstream on POWER8 likely happens on different firmware that also supports PowerVM. Finally the virtualization team does not provide any support for KVM on Power at all. Any support we have is best-effort. I don't have any POWER8 hardware capable of running KVM available. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tzimmermann(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193064] New: Touchpad doesn't work on Lenovo Yoga Slim7
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1193064 Bug ID: 1193064 Summary: Touchpad doesn't work on Lenovo Yoga Slim7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Touchpad doesn't work on Lenovo Yoga Slim7 That problem on Leap 15.3 and Tumbleweed (also in RHEL 9 beta) And some bugs on Fedora (it failed to start after sleep, but at all is working), so probably problem more on kernel side -- You are receiving this mail because: You are the assignee for the bug.

1 43

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ray.jantz(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(ray.jantz(a)gmail.c | |om) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Unless it's a regression, it's rather a thing to be reported to the upstream. Could you try to report it the upstream, e.g. linux-wireless ML? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c50 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |joan.torres(a)suse.com Resolution|--- |FIXED --- Comment #50 from Takashi Iwai <tiwai(a)suse.com> --- Joan kindly tested the latest status with his laptop, and 6.0.x kernel worked without the patch. So the workaround seems superfluous nowadays. Let's drop the patch now. Once when the problem reappears, we can rethink. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] New: LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205198 Bug ID: 1205198 Summary: LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver 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: ray.jantz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0 Build Identifier: The activity LED on my ASUS AC51 wireless USB adapter does not flash when there is link activity. Everything else works - the adapter connects to wireless networks, but the LED never flashes. The LED works fine in Windows 10. Reproducible: Always Steps to Reproduce: 1. Plug ASUS AC51 adapter into a USB port. 2. No need to install a driver (driver is in-kernel) 3.(Optional) reboot 4. Connect to wireless network. 5. Open a browser and bring up a web page. Actual Results: The activity LED on the AC51 never flashes even though there is network activity. Expected Results: The activity LED on the AC51 should flash when there is network activity. The OS is Opensuse Tumbleweed 6.0.5-1-default. The info from lsusb is: ASUSTek Computer, Inc. AC51 802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610U] Bus 001 Device 003: ID 0b05:17d1 ASUSTek Computer, Inc. AC51 802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610U] I have checked the kernel config file and CONFIG_MT76_LEDS=y is set. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c9 --- Comment #9 from Marc Balmer <marc(a)msys.ch> --- It seem somehow to be related to the USB controller in use. On an IBM SurePOS 300 with UHCI, I have not issues. On EHCI and XHCI controllers it seems not to work. Also there are two hardware versions of the 1472g base station that use different CPUs. So there is quite some variations to check... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c8 --- Comment #8 from Marc Balmer <marc(a)msys.ch> --- The scanner is operation as long as the machine is in the grub bootloader. As soon as the kernel boots, the scanner goes into a non-operational mode. There must be a bug in the cdc_acm driver/subsystem, that was introduced with openSUSE Leap 15.3 that that persists till today. atm, the machine is running the 5.14.21-150400.24.28-default kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c7 --- Comment #7 from Marc Balmer <marc(a)msys.ch> --- Setting the ID_MM_DEVICE_IGNORE flag does not change anything. In fact, I even deinstalled ModemManager, no change either. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 Marc Balmer <marc(a)msys.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.3 |Leap 15.4 OS|openSUSE Leap 15.3 |openSUSE Leap 15.4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199661] New: amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199661 Bug ID: 1199661 Summary: amd-pstate CPU Performance Scaling Driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, is there an easy way to activate the new amd-pstate driver on Tumbleweed? I've tried: kernel-parameters: amd_pstate.replace=1 and amd_pstate.shared_mem=1 additionally I created a file named /etc/modules-load.d/amd-pstate.conf inside: # Load amd pstate at boot amd_pstate However it still defaults to: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq Anything I'm missing here? Thanks for your help -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1203539] New: Boot hangs with update to kernel 5.14.21-15040.24.21-default
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203539 Bug ID: 1203539 Summary: Boot hangs with update to kernel 5.14.21-15040.24.21-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jcarricksmith(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861545 --> https://bugzilla.suse.com/attachment.cgi?id=861545&action=edit Outputs from journalctl -b -? After the latest kernel update, when booting the system the load stalls after the message "Apparmor profiles loaded" is shown on the boot screen. After a pause both the CAPS Lock and NUM Lock lights flash together. The only way to recover from the situation is to hold the power button down. Booting 5.14.21-150400.24.18-default works fine. In the attachment there is the output from a boot on ...24.21-... (badjournal) and the output from good session on ...24.18-... (goodjournal) Many thanks John -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1199661] Autoload amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1199661 https://bugzilla.suse.com/show_bug.cgi?id=1199661#c18 Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(reiokorn@tutanota | |.com) | --- Comment #18 from Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> --- Closing as per comment 17. Thanks Takashi and Boris for helping the user out. The commit fixing this problem is fbd74d16890b9f5d08ea69b5282b123c894f8860 (" ACPI: CPPC: Fix enabling CPPC on AMD systems with shared memory") from Linux v5.19, which has now been available on Tumbleweed for a while. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c12 --- Comment #12 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862688 --> https://bugzilla.suse.com/attachment.cgi?id=862688&action=edit ethernet_nic_hang_issue_sysrq_logs Hello please find attached the requested logs. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c11 --- Comment #11 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862659 --> https://bugzilla.suse.com/attachment.cgi?id=862659&action=edit Boot logs with 15sp5 kernel Boot logs with 15sp4 kernel Linux version 5.14.21-150500.33.gc8fa035-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c10 --- Comment #10 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- (In reply to Takashi Iwai from comment #9) > Thanks. The kernel log doesn't show anything doubtful through a quick > glance. > > Then can you try to get the stack traces of the tasks via alt-sysrq-t? > Try to enable the all sysrq beforehand (e.g. pass "sysrq_always_enabled" > boot option). I talked with Thomas Bogendoerfer about the issue and he advised me to test with the kernel from SLES15sp5 as it has a closer igc driver sources to upstream. Even with that kernel the issue is reproduced, log are attached, but does not have anything relevant on it as well. The only thing is that with the kernel from SLES15SP5 the problem is less frequent to happen. I am trying to reproduce and as soon as I reproduce the issue I will collect the stack traces from the different tasks with sysrq -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205046] New: kernel panic Hard lockup
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205046 Bug ID: 1205046 Summary: kernel panic Hard lockup Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: strangerover2002(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862654 --> http://bugzilla.opensuse.org/attachment.cgi?id=862654&action=edit screenshot1 Using a dell 2 in 1 laptop 12 gen intel i7-1255U Using vmlinux-5.14.21-150400.24.21-default.gz linux boots as normal Using vmlinux-5.14.21-150400.24.28-default.gz linux stops at bootup and shows the message ---[ end Kernel panic - not syncing: Hard LOCKUP ] --- The screenshot show the debug on the laptop Both kernels work on another computer, so I suspect this is specific to my brand new laptop -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The kernel log doesn't show anything doubtful through a quick glance. Then can you try to get the stack traces of the tasks via alt-sysrq-t? Try to enable the all sysrq beforehand (e.g. pass "sysrq_always_enabled" boot option). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(tau0(a)tutanota.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Can you figure out which kernel version started showing the problem? You can find older packages (up to one month ago or so) in TW history repo, http://download.opensuse.org/history/ If you need older kernels, there are my kernel builds found in OBS home:tiwai:kernel:5.19, home:tiwai:kernel:5.18, home:tiwai:kernel:5.17, ... Note that my kernel packages are unofficial builds, hence you'd need to turn off Secure Boot if it's enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c8 --- Comment #8 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862653 --> https://bugzilla.suse.com/attachment.cgi?id=862653&action=edit Boot logs with 15sp4 kernel Boot logs for the test done with latest kernel from OBS Kernel:SLE15-SP4 repo : Linux version 5.14.21-150400.271.gfcd75f5-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c7 --- Comment #7 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- (In reply to Takashi Iwai from comment #6) > Could you check whether it's a regression in the update kernel? That is, > install the old Leap 15.4 GA kernel and confirm the behavior. > > Also, please check with the latest kernel in OBS Kernel:SLE15-SP4 repo, too. > http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ Tested with the latest kernel in OBS Kernel:SLE15-SP4 repo and the issue is reproduced. Boot log attached -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205032] New: [Build 20221103] LTP: test fails in setitimer01
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205032 Bug ID: 1205032 Summary: [Build 20221103] LTP: test fails in setitimer01 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2853408/modules/seti timer01/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation setitimer01.c:73: TPASS: sys_setitimer(tc->which, value, ovalue) passed setitimer01.c:80: TFAIL: Ending counters are out of range setitimer01.c:89: TPASS: Child received signal: SIGPROF Failed. Test took approximately 0.169252419000259 seconds Some test output could not be parsed: 8 lines were ignored. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [setitimer01](https://openqa.opensuse.org/tests/2853408/modules/setitimer01/… ## Test suite description ## Reproducible Fails since (at least) Build [20221021](https://openqa.opensuse.org/tests/2826982) ## Expected result Last good: [20221020](https://openqa.opensuse.org/tests/2825305) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1204342] MATE CPU Frequency Monitoring stuck at lowest CPU speed
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204342 http://bugzilla.opensuse.org/show_bug.cgi?id=1204342#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X11 Applications Assignee|kernel-bugs(a)opensuse.org |sor.alexei(a)meowr.ru Flags|needinfo?(llrainey15@gmail. | |com) | --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's try to reassign to MATE OBS project maintainer. If it turned out to be a kernel issue, please reassign back. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0