January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1181609] New: Laptop keyboard not working
by bugzilla_noreply＠suse.com 30 Jan '21

30 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181609 Bug ID: 1181609 Summary: Laptop keyboard not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jcarricksmith(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845660 --> http://bugzilla.opensuse.org/attachment.cgi?id=845660&action=edit Diagnostic filers The laptop is a Novatech N1819, which is based on the Clevo PB71F1-G chassis, and this is a new installation of openSUSE 15.2. The keyboard works in Bios control and in grub, after the kernel has loaded it is totally dead in graphical desktop or cli session run using Ctrl+Alt+F1. A plugged in USB keyboard works and this is what I used to get the laptop up and running on openSUSE. I tried to load latest Tumbleweed (at 30/01/2021) and same problem in the install. I have created a compressed file (diags0.tar.gz) with diagnostic files in it:- dm = output from dmesg hw = output from hwinfo journalk = the output from journalctl -k pci = output from lspci -t -vv -k -nn usb = outputs from lsusb, lsusb -t, lsusb -v conccatenated into the same file separated by lines of "=" x11_00-keyboard = content of 00-keyboard.conf in /etc/X11/xorg.conf.d/ In KDE Systems Settings the keyboard is detected as a 105 key keyboard which is consistent with the manufacturer's documentation. Help please! John -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181605] New: Kernel BTRFS assertion failed when creating a docker container
by bugzilla_noreply＠suse.com 30 Jan '21

30 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181605 Bug ID: 1181605 Summary: Kernel BTRFS assertion failed when creating a docker container 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: thdiaman(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845658 --> http://bugzilla.opensuse.org/attachment.cgi?id=845658&action=edit kernel log greetings everyone, not sure if this is docker related, btrfs/kernel related or DB2 related (or all of them) but here we go :) when trying to start a (specific) container (namely https://hub.docker.com/r/ibmcom/db2) with a BTRFS attached volume (either named volume or an external mount point) i get a kernel error about a failed assertion in system log and the container hangs. i can kill the container but then i have to reboot otherwise any operation on that folder will fail miserably (process is zomb-ied, reset button is the only way to restart). the same docker run command if executed with an ext4 volume, is just fine. Reproducible: always. also reproducible since at least a couple of kernel (minor) versions back. - openSUSE Tumbleweed / 5.10.9-1-default kernel - btrfs-progs v5.9 - docker version: Client: Version: 19.03.14 API version: 1.40 Go version: go1.13.15 Git commit: 5eb3275d4006 Built: Wed Dec 23 00:00:00 2020 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 19.03.14 API version: 1.40 (minimum version 1.12) Go version: go1.13.15 Git commit: 5eb3275d4006 Built: Wed Dec 23 00:00:00 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.3.9 GitCommit: ea765aba0d05254012b0b9e595e995c09186427f runc: Version: 1.0.0-rc10 GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd docker-init: Version: 0.1.5_catatonit GitCommit: Docker command: docker run --name db2luw-with-luv --privileged=true -v data-db2luw:/database -p 50000:50000 -e LICENSE=accept -e DB2INST1_PASSWORD=12345678 -e DBNAME=testdb ibmcom/db2 Kernel log attached. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181478] ptrace_singlestep breaks hardware watchpoints
by bugzilla_noreply＠suse.com 28 Jan '21

28 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181478 https://bugzilla.suse.com/show_bug.cgi?id=1181478#c2 --- Comment #2 from Borislav Petkov <bpetkov(a)suse.com> --- https://lkml.kernel.org/r/YBMAbQGACujjfz%2Bi@hirez.programming.kicks-ass.net -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180917] kernel BUG at mm/huge_memory.c:2144!
by bugzilla_noreply＠suse.com 28 Jan '21

28 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180917 https://bugzilla.suse.com/show_bug.cgi?id=1180917#c14 --- Comment #14 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2021-01-28 12:56 EDT------- (In reply to comment #17) > all buildservice workers are LPARs running KVM to run the individual worker > instances. the LPARS are (in case of OBS) usually running a current > Tumbleweed > kernel and the KVM VMs on top usually run the kernel of the target > distribution > of the package the worker is building for. the bug displayed above is > happening > on the worker level so as a KVM VM running in an LPAR. > > Thank you for the information, R?diger. Thanks, one more thing, out of curiosity what could be the reason why this apparently only is reproducible in the Tumbleweed build service: Do you use "real" large pages for the KVM guests, i.e. have qemu (in the host) back the KVM guest with hugetlbfs mapping (see "hpage=1" parameter in https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181018] New: floppy broken in 5.3.18-lp152.57.1 under KVM
by bugzilla_noreply＠suse.com 28 Jan '21

28 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181018 Bug ID: 1181018 Summary: floppy broken in 5.3.18-lp152.57.1 under KVM Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)garloff.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running a Leap-15.2 VM under KVM on Leap-15.2 on x86-64: [ 3.721557] floppy0: disk absent or changed during operation^M [ 3.723621] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0^M [ 3.727385] floppy0: disk absent or changed during operation^M [ 3.729420] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0^M [ 3.733782] Buffer I/O error on dev fd0, logical block 0, async page read^M An older image with 5.3.18-lp152.50.1 still worked. This one is tricky: * I don't see any changes from 50 to 57 in the floppy.c sources. * After many more of these I/O errors (till second 136), floppy starts to work. I can dd /dev/fd0 to /dev/null without any further errors -- very strange. For completeness: qemu accesses the disk with -drive file=/tmp/ci-disk.17138.3Jf2/seed-17138.img,format=raw,if=floppy,id=cidata (In case you wonder -- it's a cloud image where the cloud-init data is passed in via a floppy image -- I can probably work around with using an emulated CD-Rom rather than floppy, but it's still a somewhat strange regression that might point to something fishy in the kernel. The -60 kernel does not help, BTW.) -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1181478] ptrace_singlestep breaks hardware watchpoints
by bugzilla_noreply＠suse.com 27 Jan '21

27 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181478 Tom de Vries <tdevries(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ptrace_singlestep breaks |ptrace_singlestep breaks |hardware breakpoints |hardware watchpoints -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181478] ptrace_singlestep breaks hardware breakpoints
by bugzilla_noreply＠suse.com 27 Jan '21

27 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181478 https://bugzilla.suse.com/show_bug.cgi?id=1181478#c1 Tom de Vries <tdevries(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Development |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Tom de Vries <tdevries(a)suse.com> --- Boris, I suspect this is a kernel PR. Reproduces on HW. I got both tw and leap 15.2 installed on the same laptop, and problem only reproduces on tw. Could you take a look? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181339] RTL8723BS Bluetooth not working , but wifi works !
by bugzilla_noreply＠suse.com 27 Jan '21

27 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181339 https://bugzilla.suse.com/show_bug.cgi?id=1181339#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Also, could you give "lsusb -v" output on both Ubuntu and TW kernels? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181339] RTL8723BS Bluetooth not working , but wifi works !
by bugzilla_noreply＠suse.com 27 Jan '21

27 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181339 https://bugzilla.suse.com/show_bug.cgi?id=1181339#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Afsal Mc from comment #16) > (In reply to Takashi Iwai from comment #15) > > OK, so it might be no regression on TW. That makes sense. > > > > If Ubuntu still works with their old kernel and not the generic one, there > > can be some downstream patch there. Let's see whether it's confirmed. > > I'm confirming that Bluetooth works Out-of-the-box with Ubuntu 20.04's > Default kernel 5.4.0.53-generic . Interesting. Please give dmesg output after the BT connection with that kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181330] New: Sound partially broken with kernel 5.10.x
by bugzilla_noreply＠suse.com 26 Jan '21

26 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181330 Bug ID: 1181330 Summary: Sound partially broken with kernel 5.10.x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845458 --> http://bugzilla.opensuse.org/attachment.cgi?id=845458&action=edit hwinfo output (hwinfo run under kernel 5.9.14) With kernel 5.10.x, only sound output over headphones (3.5mm plug) works on my laptop. The following things do NOT work: - internal microphone - microphone input (3.5mm plug) - internal speaker This happens with all 5.10.x kernels Tumbleweed got so far (starting at 5.10.1, and still in 5.10.7). kernel-default-5.9.14-1.2.x86_64 (and older) have working sound, therefore I boot with 5.9.14 as a workaround. Hardware: a laptop with Intel CPU, graphics and sound chip. The output of hwinfo is attached. If you need more information or want me to test something, just ask ;-) -- You are receiving this mail because: You are the assignee for the bug.

1 8