November 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178275 https://bugzilla.suse.com/show_bug.cgi?id=1178275#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimoe(a)sohnen-moe.com Flags| |needinfo?(jimoe@sohnen-moe. | |com) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- That's possible, but it's difficult to judge remotely... Just as a blind shot: could you try the kernel at http://download.opensuse.org/repositories/home:/tiwai:/bsc1149871-tw/standa… ? It's a test kernel containing a revert of a USB commit that apparently caused problems for some people. I don't think this is the same problem as yours, but just to be sure. -- 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 16 Nov '20

16 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178221 http://bugzilla.opensuse.org/show_bug.cgi?id=1178221#c5 --- Comment #5 from Freek de Kruijf <freek(a)opensuse.org> --- Nov 16 15:20:21.989577 bpim64tumhon wickedd-dhcp4[625]: eth0: Reinitiating DHCPv4 discovery (ifindex 2) Nov 16 15:20:21.989622 bpim64tumhon wickedd-dhcp4[625]: valid lease: 0; have prefs: 0 Nov 16 15:20:21.989657 bpim64tumhon wickedd-dhcp4[625]: eth0: setting fsm timeout to 64000 msec Nov 16 15:20:21.989704 bpim64tumhon wickedd-dhcp4[625]: eth0: sending DHCP4_DISCOVER with xid 0xa1b66a5 in state SELECTING Nov 16 15:20:21.989838 bpim64tumhon wickedd-dhcp4[625]: timeout 4000 adjusted by -571 to 3429 (jr 2000) Nov 16 15:20:21.989871 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer (3429 msec) Nov 16 15:20:22.660834 bpim64tumhon wickedd-dhcp6[635]: timeout 360000 adjusted by -22381 to 337619 (jr 72000) Nov 16 15:20:22.660897 bpim64tumhon wickedd-dhcp6[635]: arming retransmit timer (337619 msec) Nov 16 15:20:22.660939 bpim64tumhon wickedd-dhcp6[635]: eth0: advanced xid 0xd68463 retransmission timeout from 360000 to 337619 [-36000 .. 36000] Nov 16 15:20:22.660975 bpim64tumhon wickedd-dhcp6[635]: eth0: Retransmitting DHCPv6 Info Request Nov 16 15:20:22.661036 bpim64tumhon wickedd-dhcp6[635]: elapsed-time: 655.35 Nov 16 15:20:22.661091 bpim64tumhon wickedd-dhcp6[635]: client-id: 00:01:00:01:26:d9:b4:31:02:ba:f7:39:24:a4 Nov 16 15:20:22.661166 bpim64tumhon wickedd-dhcp6[635]: oro: info-refresh-time, preference, inf-max-rt, dns-servers, dns-domains, sntp-servers, posix-tz-string, posix-tz-dbname, bootfile-url, bootfile-param Nov 16 15:20:22.661374 bpim64tumhon wickedd-dhcp6[635]: eth0: INFO-REQUEST message #14, xid 0xd68463 sent with 52 of 52 byte to ff02::1:2 Nov 16 15:20:22.661414 bpim64tumhon wickedd-dhcp6[635]: eth0: xid 0xd68463 retransmitted, next deadline in 57m36.029s I enabled debugging for wicked in /etc/sysconfig/network/config while using the newest kernel-default-5.9.1-2. Did not see anything strange in the journalctl log. Finally did "journalctl -b -o short-precise -f" and got a repeated patern of messages (see below): Nov 16 15:20:25.421522 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit request Nov 16 15:20:25.421687 bpim64tumhon wickedd-dhcp4[625]: timeout 8000 adjusted by -253 to 7747 (jr 2000) Nov 16 15:20:25.421721 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer (7747 msec) Nov 16 15:20:33.175722 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit request Nov 16 15:20:33.175897 bpim64tumhon wickedd-dhcp4[625]: timeout 16000 adjusted by 918 to 16918 (jr 2000) Nov 16 15:20:33.175933 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer (16918 msec) Nov 16 15:20:50.110064 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit request Nov 16 15:20:50.110237 bpim64tumhon wickedd-dhcp4[625]: timeout 32000 adjusted by 976 to 32976 (jr 2000) Nov 16 15:20:50.110273 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer (32976 msec) Nov 16 15:21:23.118478 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit request Nov 16 15:21:23.118652 bpim64tumhon wickedd-dhcp4[625]: timeout 64000 adjusted by 707 to 64707 (jr 2000) Nov 16 15:21:23.118692 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer (64707 msec) Nov 16 15:21:25.991793 bpim64tumhon wickedd-dhcp4[625]: eth0: timeout in state SELECTING Nov 16 15:21:25.991857 bpim64tumhon wickedd-dhcp4[625]: eth0: discovery got no (valid) reply, retrying. Nov 16 15:21:25.991897 bpim64tumhon wickedd-dhcp4[625]: eth0: Reinitiating DHCPv4 discovery (ifindex 2) I got two global IPv6 addresses, but they do not seem to be alive on the network when I try to ping these addresses on the same network/switch. Also a ping6 from the system gets nothing back. These two addresses are derived from the MAC address and a random number. This would mean the system received data from SLAAC. Is there anything else I can do? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1170696] Dell Latitude 7490 freezes with 15.2
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c22 --- Comment #22 from Adrian Schr�ter <adrian.schroeter(a)suse.com> --- removing i915/kbl_dmc_ver1_04.bin and recreating the firmware is indeed solving the issue. At least I was able to reach even this web browser window. Let's see if anything else breaks over time. (/me is punishing himself for not trying that before ... thought the screen will stay black without firmware) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1170696] Dell Latitude 7490 freezes with 15.2
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1170696 https://bugzilla.suse.com/show_bug.cgi?id=1170696#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- Honestly speaking, it's hard to judge because of the lack of the crash information. But this looks indeed like the same problem. Did you try to exclude the firmware as pointed there? You'd need to rebuild initrd after the removal. It's unfortunate that our team (hardware-enablement) hasn't received the recent company-standard laptop for verification at all. The last one we received was some Skylake models in a few years ago. An employee may receive something for the workstation or the laptop for daily works, but not for the evaluation and the debugging purpose for the team. (And of course we're not involved with the decision which model to choose, either.) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1169099 http://bugzilla.opensuse.org/show_bug.cgi?id=1169099#c9 --- Comment #9 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- This still happens: https://openqa.opensuse.org/tests/1475498#step/kdump_and_crash/59 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178822] all Factory packages fail to build in kvm
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178822 https://bugzilla.suse.com/show_bug.cgi?id=1178822#c18 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |adrian.schroeter(a)suse.com --- Comment #18 from Dominique Leuenberger <dimstar(a)opensuse.org> --- Let's assign to Adrian; I was informed that a fix was already deployed on OBS; a kernel-default (5.9.8) is currently being built in openSUSE:Factory and once ready, I will check its signatures of the modules. If OK, we will let this produce the kernel-obs-build again and hopefully be done with it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178822] all Factory packages fail to build in kvm
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178822 https://bugzilla.suse.com/show_bug.cgi?id=1178822#c17 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jslaby(a)suse.com |kernel-bugs(a)opensuse.org --- Comment #17 from Jiri Slaby <jslaby(a)suse.com> --- So who is the right assignee now? I am certainly not :). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1178793] nvidia graphic module won't load with kernel 5.3.18-lp152.50.1
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178793 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|kernel-bugs(a)opensuse.org | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1178793] nvidia graphic module won't load with kernel 5.3.18-lp152.50.1
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178793 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lgt(a)aber.ac.uk), | |needinfo?(kernel-bugs@opens | |use.org), | |needinfo?(alan@downinglewis | |.plus.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1178639] The plasma login screen freezes on kernel 5.9.1-1
by bugzilla_noreply＠suse.com 16 Nov '20

16 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178639 http://bugzilla.opensuse.org/show_bug.cgi?id=1178639#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Could you try to boot those (broken) upstream kernels with "nomodeset" boot option? This disables the native graphics, and we can see whether it's GPU driver that locks up or not. -- You are receiving this mail because: You are the assignee for the bug.

1 0