April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184514] kernel-default-devel-5.11.11-1.2.x86_64 does not depend on kernel-default-5.11.11-1.2.x86_64

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184514 https://bugzilla.suse.com/show_bug.cgi?id=1184514#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrueckert(a)suse.co | |m) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Marcus R�ckert from comment #2) > I guess it needs to be a Requires(post/postun) as you need the > kernel-default in when the scriptlet is running that rebuilds the packages > like nvidia Hrm, I'm not sure about that. If you can verify the exact condition, let us know. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184514] kernel-default-devel-5.11.11-1.2.x86_64 does not depend on kernel-default-5.11.11-1.2.x86_64

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184514 https://bugzilla.suse.com/show_bug.cgi?id=1184514#c2 Marcus R�ckert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mrueckert(a)suse.co | |m) | --- Comment #2 from Marcus R�ckert <mrueckert(a)suse.com> --- I guess it needs to be a Requires(post/postun) as you need the kernel-default in when the scriptlet is running that rebuilds the packages like nvidia -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c16 --- Comment #16 from Diedrich Ehlerding <diedrich.ehlerding(a)t-online.de> --- (Reply to Takashi Iwai, comment # 15) Nothing changes if I add these options, neither if I apply single options nor if I add all three options together. Nothing is displayed except "Loading initial ramdisk ..." , no activity on the disk (according to activity led). -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #13) > Hm, do all people have the same problem, i.e. you don't get any output at > all even if you remove "quiet" and "splash=silent", and add "nomodeset" and > "earlyprintk=efi" boot options? > > If so, it means that the problem is triggered in a quite early boot stage. > Some blind shots are: > * Add dis_ucode_ldr boot option > * Try to disable IOMMU via intel_iommu=off Also * acpi=off boot option -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c14 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek(a)suse.com --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- Adding branch maintainer to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Hm, do all people have the same problem, i.e. you don't get any output at all even if you remove "quiet" and "splash=silent", and add "nomodeset" and "earlyprintk=efi" boot options? If so, it means that the problem is triggered in a quite early boot stage. Some blind shots are: * Add dis_ucode_ldr boot option * Try to disable IOMMU via intel_iommu=off -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184585] 5.3.18-lp152.69-default causes SEGV in intel-iommu

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184585 https://bugzilla.suse.com/show_bug.cgi?id=1184585#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jroedel(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- It's assert_spin_locked(&device_domain_lock) in domain_update_iotlb(). Joerg? -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184578] kernel-syms package pulls in kernel-preempt-devel to satisfy dependencies

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1184578 https://bugzilla.suse.com/show_bug.cgi?id=1184578#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FEATURE --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- This is the correct and expected behavior. kernel-syms is a meta package to allow build of KMPs for various flavors. If you need to build a module for the running kernel, you just need the corresponding kernel-$flavor-devel instead. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1184585] New: 5.3.18-lp152.69-default causes SEGV in intel-iommu

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184585 Bug ID: 1184585 Summary: 5.3.18-lp152.69-default causes SEGV in intel-iommu Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mischa.salle(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848228 --> http://bugzilla.opensuse.org/attachment.cgi?id=848228&action=edit SEGV stacktrace from syslog On my Dell XPS 15 9560, when running with kernel cmdline options acpi_rev_override=1 intel_iommu=on,igfx_off mitigations=auto the new 5.3.18-lp152.69-default causes a SEGV in intel-iommu: kernel BUG at ../drivers/iommu/intel-iommu.c:1389 This prevents (among other things) my wifi from working (Qualcomm Atheros QCA6174 802.11ac). I've attached the relevant part of the syslog. Disabling intel_iommu, by running with acpi_rev_override=1 intel_iommu=off,igfx_off mitigations=auto prevents the SEGV (as expected since it disables the iommu). The previous kernel, 5.3.18-lp152.66-default, still works fine with the now-broken intel_iommu=on setting. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
0
0 0

[Bug 1183838] New: Full resolution of the monitor no longer available in 5.11 kernels with i9-9900K and Intel display driver

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1183838 Bug ID: 1183838 Summary: Full resolution of the monitor no longer available in 5.11 kernels with i9-9900K and Intel display 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: mciobanu(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0 Build Identifier: I use TumbleWeed as my main OS, and also have a separate TumbleWeed partition to test the updates first. So my main system is still on 5.10.16-1-default, while the test system is on 5.11.6-1, after trying 5.11.2-1. There is no graphic card besides the one embedded in the CPU, with the built-in drivers, which so far has been good enough for me. On the test system, my 3440x1440 monitor is now seen as 2560x1080 (or sometimes 1024x768 or 1600x900), in the sense that you cannot set a higher resolution. The reason I'm saying this has to do with the kernel rather than with X, is what happens at boot: I use "nosplash", to see the boot messages. On the old/main system, there is some text with a large font for less than 1 second, and then it enters a text mode with around 90 lines, and then the X graphics mode of 3440x1440. On the updated system, the first boot goes the same in the text modes, but at reboots the text mode is really some 77 visible lines (or sometimes fewer), but it still thinks there are 90, so what happens is the bottom lines and right columns aren't shown. (Well, the bottom visible line is truncated, only the top of the characters are seen.) I think these text modes are configured before X had a chance to do anything, so it looks more like some "garbage" left in some memory from a previous run that decides the resolution. It didn't occur to me to try the older kernel (5.10.16-1) when I saw that things no longer worked as expected with 5.11.6-1, which would have made it clearer if the issue is with the kernel or not. Now I'm not sure how to go about installing an older kernel, as I don't see it in YaST. However, there is a workaround of sorts: Disconnect the DP cable and reconnect it. Then I can set the resolution to 3440x1440@60. This seems to make the text mode (e.g. Ctrl+Alt+F1) unavailable, though. Reproducible: Always Steps to Reproduce: 1. Start TumbleWeed with "nosplash" on a 3440x1440 monitor (Samsung CF791) and TW as of 2021.03.21 2. Reboot, once it started Actual Results: 1. In text mode during boot, bottom lines are not visible. 2. In graphics mode the resolution is something smaller (usually 2560x1080) and cannot be made 3440x1440 Expected Results: 1. All text lines should be visible during boot (except maybe the first boot). 2. It should be possible to set the resolution to 3440x1440@60 3. The resolution should be kept between reboots. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 3 months

1
3
0 0

2022

2021

2020

openSUSE Kernel Bugs April 2021