November 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1178221] Latest image for openSUSE-Tumbleweed pine64 gets no IPv4 connection
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178221 https://bugzilla.suse.com/show_bug.cgi?id=1178221#c3 Freek de Kruijf <freek(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(freek(a)opensuse.or | |g) | --- Comment #3 from Freek de Kruijf <freek(a)opensuse.org> --- (In reply to Fabian Vogt from comment #2) > jeos-internal(a)suse.de is not for openSUSE ARM JeOS. In any case, this sounds > like either a kernel, firmware or maybe wicked issue. Currently my guess is > the former, so reassigning. > > Do you have packet traces? > Which packages changed between the images? You can narrow that down by > updating the older image to the latest packages in steps. I only did "zypper up kernel-default" and "shutdown -r now" and ended up with an eth0 device in UP state, without an IP address. I could select in GRUB the older kernel and also that one ended up in the same state, device UP, no IP address. I need to restore the whole system to continue with it. Hopefully just two hour work. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178221] Latest image for openSUSE-Tumbleweed pine64 gets no IPv4 connection
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178221 https://bugzilla.suse.com/show_bug.cgi?id=1178221#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freek(a)opensuse.org, | |fvogt(a)suse.com Component|Network |Kernel Assignee|jeos-internal(a)suse.de |kernel-bugs(a)opensuse.org Flags| |needinfo?(freek(a)opensuse.or | |g) --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- jeos-internal(a)suse.de is not for openSUSE ARM JeOS. In any case, this sounds like either a kernel, firmware or maybe wicked issue. Currently my guess is the former, so reassigning. Do you have packet traces? Which packages changed between the images? You can narrow that down by updating the older image to the latest packages in steps. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1149871] usb usb10-port1: Cannot enable. Maybe the USB cable is bad?
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1149871 http://bugzilla.opensuse.org/show_bug.cgi?id=1149871#c22 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Alan Hughes from comment #21) > Ubuntu has apparently had similar problems reported, and resolved them by > reverting the following kernel patch: > "https://patchwork.kernel.org/project/linux-usb/patch/1549025551-4306-1-git- > send-email-glogow(a)fbihome.de/". It might be worth while having a good hard > look at this. Interesting. I'm building a test kernel with the revert for Leap 15.2 in OBS home:tiwai:bsc1149871 repo. It'll appear later at http://download.opensuse.org/repositories/home:/tiwai:/bsc1149871/standard/ For Tumbleweed, it's being built in OBS home:tiwai:bsc1149871-tw repo, will be available at http://download.opensuse.org/repositories/home:/tiwai:/bsc1149871-tw/standa… Please give it a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1149871] usb usb10-port1: Cannot enable. Maybe the USB cable is bad?
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1149871 http://bugzilla.opensuse.org/show_bug.cgi?id=1149871#c21 Alan Hughes <alanhants(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alanhants(a)gmail.com --- Comment #21 from Alan Hughes <alanhants(a)gmail.com> --- I am also seeing this issue on OpenSUSE Leap 15.2 with kernel 5.3.18-lp152.47-default. The system has become highly unresponsive as a result of this bug; boot time has been extended by several minutes, KDE login now takes at least 2 minutes, Dolphin start-up takes at least 1 minute. The USB device in question is not being used - there is nothing plugged in to it. Not only that but I have tried to remove all USB devices plugged into the machine and the messages continue to appear. This problem did not appear on OpenSUSE Leap 15.1. Windows 10 installer does not report any faulty hardware. Ubuntu has apparently had similar problems reported, and resolved them by reverting the following kernel patch: "https://patchwork.kernel.org/project/linux-usb/patch/1549025551-4306-1-git-…". It might be worth while having a good hard look at this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178284] wifi doesn't work after machine boots up
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178284 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- 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

[kernel-bugs] [Bug 1178271] iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178271 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- 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

[kernel-bugs] [Bug 1178275] usb3 device generates lots of command errors
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178275 https://bugzilla.suse.com/show_bug.cgi?id=1178275#c1 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Chenzi Cao <chcao(a)suse.com> --- Assign to kernel team to take a look at this, please feel free to reassign, thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178401] errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default"
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178401 https://bugzilla.suse.com/show_bug.cgi?id=1178401#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- The fix was pushed to my packaging/for-next branch, and will be merged to other branches later. But this covers only about the modprobe "FATAL" error messages. What about the rest? Those look like the issue of other packages. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178401] errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default"
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178401 https://bugzilla.suse.com/show_bug.cgi?id=1178401#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Ah, that one, thanks. The fix should be just to add -q option to those explicit modprobe calls. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178401] errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default"
by bugzilla_noreply＠suse.com 04 Nov '20

04 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178401 https://bugzilla.suse.com/show_bug.cgi?id=1178401#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Component|Basesystem |Kernel Assignee|dracut-maintainers(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- The initrd is built as part of kernel-obs-build, and kernel-obs-build.spec.in has this: # a longer list to have them also available for qemu cross builds where x86_64 kernel runs in eg. arm env. # this list of modules where available on build workers of build.opensuse.org, so we stay compatible. export KERNEL_MODULES="loop dm-crypt dm-mod dm-snapshot binfmt-misc fuse kqemu squashfs ext2 ext3 ext4 reiserfs btrfs xfs nf_conntrack_ipv6 binfmt_misc virtio_pci virtio_mmio virtio_blk virtio_rng fat vfat nls_cp437 nls_iso8859-1 ibmvscsi sd_mod e1000 ibmveth overlay" # manually load all modules to make sure they're available for i in $KERNEL_MODULES; do ( echo "info ' $i'" echo "modprobe $i" ) >> /usr/lib/dracut/modules.d/80obs/setup_obs.sh done So reassigning back to kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0