April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot
by bugzilla_noreply＠suse.com 15 Apr '21

15 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c42 --- Comment #42 from Philippe Andersson <pan(a)iba-group.com> --- I can confirm that my laptop boots fine on the .69 kernel with the "intel_iommu=off" parameter. Unfortunately, I can't use the test kernel with the faulty patch removed as I need Secure Boot support (corporate laptop, I don't have access to the BIOS). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184763] New: Dell WD15 Dock is detected as Dell TB16 Dock
by bugzilla_noreply＠suse.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184763 Bug ID: 1184763 Summary: Dell WD15 Dock is detected as Dell TB16 Dock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: srinidhi.bs(a)microfocus.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Whenever I connect my Dell WD15 Dock to my Dell 7480 laptop running openSUSE Leap 15.2, it detects the dock as a Dell TB16 Dock: 2021-04-14T21:00:34.549707+05:30 srinidhi kernel: [150317.485963] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd 2021-04-14T21:00:34.567002+05:30 srinidhi kernel: [150317.506275] usb 4-1: New USB device found, idVendor=0424, idProduct=5807, bcdDevice= 2.04 2021-04-14T21:00:34.567075+05:30 srinidhi kernel: [150317.506287] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2021-04-14T21:00:34.567090+05:30 srinidhi kernel: [150317.506295] usb 4-1: Product: USB5807 Hub 2021-04-14T21:00:34.567102+05:30 srinidhi kernel: [150317.506301] usb 4-1: Manufacturer: Microchip ... 2021-04-14T21:00:34.860835+05:30 srinidhi kernel: [150317.797934] usb 4-1.2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd 2021-04-14T21:00:34.880911+05:30 srinidhi kernel: [150317.818629] usb 4-1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.11 2021-04-14T21:00:34.880971+05:30 srinidhi kernel: [150317.818642] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 2021-04-14T21:00:34.880986+05:30 srinidhi kernel: [150317.818651] usb 4-1.2: Product: USB 10/100/1000 LAN 2021-04-14T21:00:34.880996+05:30 srinidhi kernel: [150317.818659] usb 4-1.2: Manufacturer: Realtek 2021-04-14T21:00:34.881008+05:30 srinidhi kernel: [150317.818667] usb 4-1.2: SerialNumber: 000002000000 ... 2021-04-14T21:00:37.985062+05:30 srinidhi kernel: [150320.922325] usb 4-1.2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd 2021-04-14T21:00:38.008787+05:30 srinidhi kernel: [150320.947061] usb 4-1.2: Dell TB16 Dock, disable RX aggregation ... I've observed the same in the openSUSE Leap 15.3 Public Beta build as well as the Build9.10 GNOME Live image as well. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot
by bugzilla_noreply＠suse.com 15 Apr '21

15 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c41 --- Comment #41 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for confirmation, and it's a good news! Does anyone else still see the boot problem even with intel_iommu=off boot option? I thought Philippe hitting such a problem, but maybe worth to retest. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 15 Apr '21

15 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c32 --- Comment #32 from Jeffrey Cheung <jcheung(a)suse.com> --- (In reply to Michal Suchanek from comment #26) > Then this is upstream problem and we don't have a fix. Well, it seems the fix is here -> https://github.com/crash-utility/crash/commit/d379b47f04dc77ea1989609aca9bf… Introduce a new ARM64 "--machdep vabits_actual=<value>" command -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot
by bugzilla_noreply＠suse.com 15 Apr '21

15 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c40 --- Comment #40 from Bill Wayson <bill_wayson(a)yahoo.com> --- (In reply to Takashi Iwai from comment #38) > (In reply to Bill Wayson from comment #37) > > (In reply to Takashi Iwai from comment #35) > > > For the people who can boot with intel_iommu=off boot option, please go to > > > bug 1184585. The culprit was identified and the test fix kernel is being > > > built there. > > > > > > If your machine doesn't boot with intel_iommu=off boot option, this must be > > > a different bug, and we'd like to see whether other options make boot > > > forward (even if not fully functional). If that's the case, please speak up. > > > > I'm with this bug. The intel_iommu=off boot option does not help me. > > IIUC, it's your laptop (while the desktop is working), and the boot hangs at > some while after some boot process, right? Then it must be the influence by > acpi=off option. Try to drop this and retest. In that way, check which one > makes booting at best by removing one by one. > > The options quiet and splash=silent can be dropped for the whole testing. > It's about the boot splash, hence likely irrelevant. Check whether > intel_iommu=off really doesn't give any difference on the laptop, too. Takashi, I apologize for wasting your time here. First, you do understand correctly about my desktop and laptop. But I missed it somehow -- I _can_ successfully boot the 5.3.18-lp152.69-default kernel on my laptop by adding only (of all of your suggestions) the intel_iommu=off parameter. So I do belong over at bug 1184585. Thank you for your help and work. I'll bring myself up to speed over there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183839] kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183839 https://bugzilla.suse.com/show_bug.cgi?id=1183839#c22 --- Comment #22 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Created attachment 848382 --> https://bugzilla.suse.com/attachment.cgi?id=848382&action=edit lsinitrd kernel-default 5.11.11 without sound drivers Finally a normal initrd -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183839] kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183839 https://bugzilla.suse.com/show_bug.cgi?id=1183839#c21 --- Comment #21 from Bruno Friedmann <bruno(a)ioda-net.ch> --- (In reply to Takashi Iwai from comment #20) > Try to fix your set up not to include sound drivers in the initrd. That can > bring just headaches, even if it worked somehow casually in the past. Hi Takashi. I never intended to have sound drivers in initrd, except the conf I sended before I've nothing else that normally a stock TW configuration, so I don't understand from where and the why the mkinitrd command think they are mandatory. So to follow your advise to not have them in initrd, I've actually created a /etc/dracut.conf.d/80-no-sound-drivers.conf with the following exclusion omit_drivers+=" snd_hda_intel snd_seq_device snd_hwdep snd_hda_intel snd_usb_audio snd_usbmidi_lib snd_hda_codec snd_timer snd_compress snd_soc_core snd_pcm snd_rawmidi snd_intel_dspcfg sou ndwire_intel soundwire_intel snd_compress snd_soc_core snd_hda_core snd_pcm_dmaengine snd_soc_core snd_compress snd_seq_device snd_hwdep snd_timer snd_pcm snd_timer snd soundcore_bus soundc ore soundwire_generic_allocation soundwire_bus soundwire_cadence " I've recreated a new initrd (content in next attachement) and rebooted the computer. As expected, I didn't suffer from any rip, nor I did to boot first single etc. So we have now understood that mkinitrd is adding those sound drivers in initrd. But still the root cause is unknown... I've check on another computer (cpu AMD + nvidia) and the drivers are not in the initrd ? Honestly I've no clue about why this is happening. If you have any idead I would be really glad to help debugging this mis-behaviour. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183839] kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183839 https://bugzilla.suse.com/show_bug.cgi?id=1183839#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- Try to fix your set up not to include sound drivers in the initrd. That can bring just headaches, even if it worked somehow casually in the past. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183839] kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183839 https://bugzilla.suse.com/show_bug.cgi?id=1183839#c19 --- Comment #19 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Created attachment 848370 --> https://bugzilla.suse.com/attachment.cgi?id=848370&action=edit lsinitrd 5.10.3 kernel-default The content shown here, clearly proove that snd-hda-intel was there also in previous kernel, and was not causing the crash I found actually. Is there anything else we can investigate ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183839] kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183839 https://bugzilla.suse.com/show_bug.cgi?id=1183839#c18 Bruno Friedmann <bruno(a)ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bruno(a)ioda-net.ch | |) | --- Comment #18 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Created attachment 848369 --> https://bugzilla.suse.com/attachment.cgi?id=848369&action=edit lsinitrd 5.11.11 kernel-default It contains snd related drivers. but nothing I would have made in a concensius way. So I'm really interested by understanding what would have changed here. I will restore older 5.10.3 vmlinuz and initrd dating from January and report the content in next attachement. -- You are receiving this mail because: You are the assignee for the bug.

1 0