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