August 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1214428] NVMe regression between kernel 6.4.9 and 6.4.11
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214428 https://bugzilla.suse.com/show_bug.cgi?id=1214428#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Martin Wilck from comment #19) > Perhaps we should just revert this in openSUSE stable (and master) until > upstream has figured it out? Yes, the patch was already reverted on our stable/master branches (as well as SLE15-SP6/ALP-current). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214428] NVMe regression between kernel 6.4.9 and 6.4.11
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214428 https://bugzilla.suse.com/show_bug.cgi?id=1214428#c20 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brent.j.franklin(a)gmail.com --- Comment #20 from Martin Wilck <martin.wilck(a)suse.com> --- *** Bug 1214397 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 1214397] Installation cannot find my NVMe drive when it comes time to format and install.
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214397 https://bugzilla.suse.com/show_bug.cgi?id=1214397#c24 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC| |martin.wilck(a)suse.com --- Comment #24 from Martin Wilck <martin.wilck(a)suse.com> --- Marking as dup of 1214428. *** This bug has been marked as a duplicate of bug 1214428 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214428] NVMe regression between kernel 6.4.9 and 6.4.11
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214428 https://bugzilla.suse.com/show_bug.cgi?id=1214428#c19 --- Comment #19 from Martin Wilck <martin.wilck(a)suse.com> --- All evidence points to 69304c8d285b / 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg"). The commit author hypothesizes something about a generic power saving issue [1], but that makes little sense to me, given that the issue seems to occur only on systems that feature the rtsx hardware. I rather think that this commit makes the rtsx hardware misbehave in some way, with the side effect that the NVMe device appears dead. I second the recommendation that this should be reverted [2]. Perhaps we should just revert this in openSUSE stable (and master) until upstream has figured it out? [1] https://lore.kernel.org/lkml/570d465a-7500-4b58-98f0-fd781c8740cc@sapience.… [2] https://lore.kernel.org/lkml/570d465a-7500-4b58-98f0-fd781c8740cc@sapience.… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214428] NVMe regression between kernel 6.4.9 and 6.4.11
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214428 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com URL| |https://bugzilla.kernel.org | |/show_bug.cgi?id=217802 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214445] increase vm.max_map_count
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214445 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Component|Basesystem |Kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214208] Bluetooth headphone audio inconsistent/connection unstable
by bugzilla_noreply＠suse.com 29 Aug '23

29 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214208 https://bugzilla.suse.com/show_bug.cgi?id=1214208#c25 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |DUPLICATE --- Comment #25 from Takashi Iwai <tiwai(a)suse.com> --- Yes, the pipewire fix is already on its way to TW (or already included). Make this as dup to be more obvious. *** This bug has been marked as a duplicate of bug 1214374 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207728] BTRFS info (device sda2): qgroup scan paused each time i startup or reboot computer
by bugzilla_noreply＠suse.com 29 Aug '23

29 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1207728 https://bugzilla.suse.com/show_bug.cgi?id=1207728#c16 John Shand <jshand2013(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #16 from John Shand <jshand2013(a)gmail.com> --- this seems to being dealt with upstream. i will now close -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214259] Unable to use 4k resolution using the DisplayPort on ryzen 9 7900
by bugzilla_noreply＠suse.com 28 Aug '23

28 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214259 https://bugzilla.suse.com/show_bug.cgi?id=1214259#c16 --- Comment #16 from Alex <alex(a)polverini.org> --- does anybody know if the fix made it in kernel 6.5? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214432] Kernel 5.14.21-150500.55.19 causes qlogic driver to fail
by bugzilla_noreply＠suse.com 28 Aug '23

28 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214432 https://bugzilla.suse.com/show_bug.cgi?id=1214432#c2 --- Comment #2 from Frank Gießler <frank.giessler(a)yahoo.de> --- The only difference betwen the two controllers was the number of the FC it was using. The apparently 'good' one was using channel 1 while the apparentely 'faulty' one was using channel 0. I now reconfigured the 'faulty' one to use also channel 1 and although I don't see why this should make a difference the previously 'faulty' one is now also working. If it weren't for the fact that the previous kernel had no problem with either controller I'd vote for a hardware issue. Go figure. Nevertheless, as far as I'm concerned the bug can be closed now. Thanks, Frank -- You are receiving this mail because: You are the assignee for the bug.

1 0