October 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for quick testing. Then could you load alsa-info.sh output from the patched kernel after suspend/resume? Run the script with --no-upload, and use Bugzilla attachment. Also, for verifying whether it's a driver PM problem, try the following: - Before and after suspend/resume, try to play without PA, PW or JACK but via ALSA native API, e.g. % aplay -Dplughw:XXX foo.wav where XXX is the card number like 0, 1, 2, corresponding to the device index appearing in /proc/asound/cards. I suppose this also results in the mono output? - Get alsa-info.sh outputs before and after the suspend/resume. - Check whether the problem persists with suspend-to-RAM and suspend-to-disk (hibernate). I assume you're dealing with the former, right? - Last but not least, check whether re-loading the driver fixes the problem without re-plugging. You might need to go out of desktop session once, unload snd-usb-audio module and re-load snd-usb-audio module on Linux console. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c2 --- Comment #2 from Andrea P <pandre.x(a)gmail.com> --- Hi! Thank you for your quick response. I just tried your kernel but unfortunately it doesn't fix the audio issue. Is there something I can log for you? Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190326] Update to kernel 5.14 makes disks disapear/system unbootable
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190326 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |dracut-maintainers(a)suse.de -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190326] Update to kernel 5.14 makes disks disapear/system unbootable
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190326 https://bugzilla.suse.com/show_bug.cgi?id=1190326#c20 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #20 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Thomas Blume from comment #19) > (In reply to Olaf Hering from comment #18) > > (In reply to Thomas Blume from comment #17) > > > Does that contain the right dependency for xen_netfront/blkfront? > > > > See comment#15 (and comment#13) for three live systems that show the issue. > > Ok thanks, I can see this: > > --> > dracut-install: Handling > /lib/modules/5.14.5-7.g24dfde2-default//kernel/drivers/block/xen-blkfront.ko. > xz > dracut-install: No symbol or path match for > '/lib/modules/5.14.5-7.g24dfde2-default//kernel/drivers/block/xen-blkfront. > ko.xz' > --< > > which comes from dracut-install.c > > --> > if (!check_module_path(path) || !check_module_symbols(mod)) { > log_debug("No symbol or path match for '%s'", path); > return 1; > } > --< > > For kernel 5.3.18-59.19-default this is different: > > --> > dracut-install: Handling > /lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen-blkfront.ko.xz > dracut-install: Module xen_blkfront: symbol blk_cleanup_queue matched > inclusion filter > dracut-install: dracut_install > '/lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen-blkfront.ko.xz' > '/lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen-blkfront.ko.xz' > dracut-install: > dracut_install('/lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen- > blkfront.ko.xz', > '/lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen-blkfront.ko.xz') > dracut-install: dracut_install ret = 0 > dracut-install: cp > '/lib/modules/5.3.18-59.19-default//kernel/drivers/block/xen-blkfront.ko.xz' > '/var/tmp/dracut.dTMGuu/initramfs/lib/modules/5.3.18-59.19-default//kernel/ > drivers/block/xen-blkfront.ko.xz' > dracut-install: cp ret = 0 > dracut-install: dracut_install ret = 0 > dracut-install: dracut_install 'xen_blkfront' OK > --< > > Not really sure whether dracut is to blame therefore. FWICT, the relevant lines are: local _blockfuncs='ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|... ... dracut_instmods -o -s "${_blockfuncs}" "=drivers" It goes through all driver modules and installs those which have symbols in the given list. xen-blkfront was ported away from blk_cleanup_queue to blk_cleanup_disk in 3b62c140e93d32, so it no longer matches. Adding blk_cleanup_disk to the list might be the right fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190797] nls_utf8.ko is missing in Leap 15.3, although CONFIG_NLS_UTF8=m is set
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190797 https://bugzilla.suse.com/show_bug.cgi?id=1190797#c4 Akihiro Suda <suda.kyoto(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suda.kyoto@gmail. | |com) | --- Comment #4 from Akihiro Suda <suda.kyoto(a)gmail.com> --- (In reply to Fabian Vogt from comment #3) > According to > https://lore.kernel.org/lkml/20210808162453.1653-1-pali@kernel.org/, > nls_utf8 will probably be dropped in the future. It seems to be necessary > only for specific filesystems. Yes, I know, but the patch isn't merged into the upstream yet. > What's your use case which needs this module? Mounting SMB with non-ASCII file names. > I'll prepare SRs for TW and Leap. Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190797] nls_utf8.ko is missing in Leap 15.3, although CONFIG_NLS_UTF8=m is set
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190797 https://bugzilla.suse.com/show_bug.cgi?id=1190797#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suda.kyoto(a)gmail.com Flags| |needinfo?(suda.kyoto@gmail. | |com) --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- According to https://lore.kernel.org/lkml/20210808162453.1653-1-pali@kernel.org/, nls_utf8 will probably be dropped in the future. It seems to be necessary only for specific filesystems. What's your use case which needs this module? I'll prepare SRs for TW and Leap. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191190] New: Honeycomb LX2K: restool not working with Kernel 5.14.6-default
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191190 Bug ID: 1191190 Summary: Honeycomb LX2K: restool not working with Kernel 5.14.6-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmayer(a)windinternethaus.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This regards the SolidRun Honeycomb LX2K [https://en.opensuse.org/HCL:HoneyComb_LX2K] running OpenSUSE Tumbleweed with Kernel 5.14.6-1-default. When trying to bring up dpmac network interfaces with the userspace tool 'restool', this error occurs: > # ls-addni dpmac.9 > error: Did not find a device file > Restool wrapper scripts only support the latest major MC version > that currently is MC10.x. Use with caution. > error: Did not find a device file Jon Nettleton of SolidRun has pointed out to me, that restool requires the kernel to be compiled with 'CONFIG_FSL_MC_UAPI_SUPPORT=y' [https://community.solid-run.com/t/restool-with-kernel-5-14-did-not-find-a-d…] You will find more detailed version information and full dmesg output in my post in the SolidRun forum [https://community.solid-run.com/t/restool-with-kernel-5-14-did-not-find-a-d…] Most significant are these messages: > [ 14.732750] fsl_mc_dpio dpio.14: probed > [ 14.737781] fsl_mc_dpio dpio.13: Adding to iommu group 0 > [ 14.745525] fsl_mc_dpio dpio.13: unknown SoC version > [ 14.775314] fsl_mc_dpio dpio.13: probed > [...] > [ 15.138743] fsl_mc_dpio dpio.1: Adding to iommu group 0 > [ 15.146263] fsl_mc_dpio dpio.1: unknown SoC version > [ 15.170320] fsl_mc_dpio dpio.1: probed > [ 15.173450] fsl_mc_dpio dpio.0: Adding to iommu group 0 > [ 15.181233] fsl_mc_dpio dpio.0: unknown SoC version > [ 15.187358] fsl_mc_dpio dpio.0: probed You can currently find a restool package here: https://build.opensuse.org/package/show/home:wind.gmbh/restool (I have submitted it to Network:Utilities as well: [https://build.opensuse.org/request/show/922384] -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1190646] Touchpad stopped working after recent update
by bugzilla_noreply＠suse.com 01 Oct '21

01 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190646 http://bugzilla.opensuse.org/show_bug.cgi?id=1190646#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |KDE Workspace (Plasma) Assignee|kernel-bugs(a)opensuse.org |opensuse-kde-bugs@opensuse. | |org --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- It indicates that the problem isn't in the kernel, but rather user-space stack that interprets it. Might it be some activation of a tablet mode or such? Reassigned to KDE. -- You are receiving this mail because: You are the assignee for the bug.

1 0