[Bug 1197434] New: kernel call trace when setting up sound card
https://bugzilla.suse.com/show_bug.cgi?id=1197434 Bug ID: 1197434 Summary: kernel call trace when setting up sound card Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: pablo@blueoakdb.com QA Contact: qa-bugs@suse.de CC: pablo@blueoakdb.com Depends on: 1197315 Found By: --- Blocker: --- Created attachment 857299 --> https://bugzilla.suse.com/attachment.cgi?id=857299&action=edit Unit test Hi, The onboard mic while recognized, does not capture audio. The jack works. The DE is KDE. ::: Steps to reproduce ::: o /Set up/ devices per below. o Use /alsaucm/ and /arecord/ to create file - see unit test attachment. ::: Expected output ::: Capture audio in the .wav file. ::: Observed Output ::: No audio is captured in the .wav file. ::: Set up ::: Volume icon > Show inactive devices Playback devices ---------------- Fedoara: Check: Speaker (sof-soundwire Speaker) TW: Check: Speaker (Comet Lake PCH cAVS Speaker) Set to 100% Recording Devices ----------------- Fedora: Check: SoundWire microphone (sof-soundwire SoundWire microphones) TW: Check: SoundWire microphone (Comet Lake PCH cAVS SoundWire microphones) Set to 100% -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c1 --- Comment #1 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857300 --> https://bugzilla.suse.com/attachment.cgi?id=857300&action=edit alsa-info.txt from TW -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c2 Pablo Sanchez <pablo@blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/thesofpr | |oject/linux/issues/3532 --- Comment #2 from Pablo Sanchez <pablo@blueoakdb.com> --- This issue may be an upstream bug and is being tracked there - see the /See Also/ 3532 issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 Pablo Sanchez <pablo@blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|kernel call trace when |Onboard mic does not |setting up sound card |capture audio -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c3 --- Comment #3 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857301 --> https://bugzilla.suse.com/attachment.cgi?id=857301&action=edit alsa-info.txt from Fedora -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c4 --- Comment #4 from Pablo Sanchez <pablo@blueoakdb.com> --- In the upstream issue, a test proved that on Fedora 35, the mic works (albeit extremely low capture volume - noted upstream). For completion, I've attached the alsa-info.txt from that environment to allow comparison between /non-working/ and /working/. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- You can save alsactl contents on Fedora (right after alsaucm invocation) like alsactl -f /some/file store 1 where "1" is the card number for the SOF driver. Check /proc/asound/cards beforehand. Then copy this file to TW, and restore it via alsactl -f /some/file restore 0 here "0" is specified as TW had this device as primary. See /proc/asound/cards beforehand just to be sure. Then try arecord. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c6 --- Comment #6 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857307 --> https://bugzilla.suse.com/attachment.cgi?id=857307&action=edit TW - alsa.cfg Thank you so much (again) Takashi for the direction on how to continue to get to the root-cause. I thought it might be useful to capture a baseline. This is my computer's current alsa.cfg -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c7 --- Comment #7 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857308 --> https://bugzilla.suse.com/attachment.cgi?id=857308&action=edit Fed alsa.cfg This is the as-is Fedora alsa.cfg When I attempted to load it, I received the following errors: alsactl: set_controls:1499: device='hw:0', doit=0 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' No state is present for card sofsoundwire alsactl: set_controls:1587: result code: -2 alsactl: sysfs_init:45: sysfs_path='/sys' alsactl: set_controls:1499: device='hw:0', doit=1 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' No state is present for card sofsoundwire alsactl: set_controls:1587: result code: -2 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c8 --- Comment #8 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857309 --> https://bugzilla.suse.com/attachment.cgi?id=857309&action=edit Fed alsa.cfg, tweaked I diff'd the TW vs Fedora .cfg files and thought perhaps the error with applying the vanilla, Fedora .cfg was due to line 1. I changed it to match the TW 'alsa.cfg' That didn't work ... :) :) :) ... see the errors below: alsactl: set_controls:1499: device='hw:0', doit=0 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' alsactl: set_control:1339: failed to obtain info for control #1 (No such file or directory) alsactl: set_controls:1587: result code: -2 alsactl: sysfs_init:45: sysfs_path='/sys' alsactl: set_controls:1499: device='hw:0', doit=1 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' alsactl: set_control:1339: failed to obtain info for control #1 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #6 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #13 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #18 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #19 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #20 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #21 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #22 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #23 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #24 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #25 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #26 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #27 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #28 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #29 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #30 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #31 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #32 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #33 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #34 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #35 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #36 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #37 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #38 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #39 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #40 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #41 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #42 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #43 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #45 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #46 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #47 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #48 (No such file or directory) alsactl: set_control:1339: failed to obtain info for control #49 (No such file or directory) alsactl: set_controls:1587: result code: -2 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- The content in comment 7 is for Nvidia HDMI, you can see "state.NVidia" at the beginning, that's why it can't be loaded on to SOF soundwire driver. The card order may change depending on the boot condition, so you'd need to check which card index (0 or 1) to save by checking /proc/asound/cards beforehand. If you get the right sound state, it should be loaded properly on TW. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c10 --- Comment #10 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, I'm wondering if what you mentioned in Comment #9 about selecting both cards is the issue. Only one card is presented:
��������� $ ls /proc/asound/ card0/ cards devices hwdep modules oss/ pcm seq/ sofsoundwire@ timers version ��������� $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF
-- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- No, no, it's the *content* of alsactl file you've tried to restore on TW. You saved the content from Nvidia device, not from soundwire, and yet tried to store those values onto TW's soundwire. That's the reason of the failure. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c12 --- Comment #12 from Pablo Sanchez <pablo@blueoakdb.com> --- Must ... learn ... to ... read. Ijiot! Sorry about that. Be back. :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c13 --- Comment #13 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857336 --> https://bugzilla.suse.com/attachment.cgi?id=857336&action=edit Fed alsa.cfg - for sof sound wire card O ... M ... G ... the mic is working using the Fedora alsa.cfg file. \o/ Thank you so much! I conducted an end-to-end unit test using Zoom. Worked. How do we proceed from here? Do not hesitate to ask for anything on my end. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c14 --- Comment #14 from Takashi Iwai <tiwai@suse.com> --- OK, that's a good step forward. It implies it being a configuration problem. Now, please try to unload the modules on TW system. Then remove (better to backup) /var/lib/alsa/asound.state file. Then reboot and retest the mic as-is. Does it still bring to a broken mic state? Take alsa-info.sh output again before testing the mic. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- (In reply to Takashi Iwai from comment #14)
Now, please try to unload the modules on TW system.
I meant to unload modules in a way in bug 1197315 (but in a right order not to trigger Oops), something like fuser -k /dev/snd/* modprobe -r snd_soc_sof_sdw Then /proc/asound/cards must be gone or empty. After that state, remove /var/lib/alsa/asound.state, reboot and retest. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c16 --- Comment #16 from Pablo Sanchez <pablo@blueoakdb.com> --- I did both tests because I wasn't sure whether it was necessary to test the unload code snippet or not. As expected, without removing the parent PCI device, an oops. Once I manually removed it, followed by the unload code snippet, all unloaded well. I've mv'd away asound.state. Quick question before I reboot, should I reload with the Fedora alsa.cfg before the reboot? (Obviously I am unclear on how the sound stuff works ... :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- No, the purpose of this test is to see the clean state on TW without adjustment. It might be that something got corrupted accidentally or mistakenly, and it's been kept due to alsactl-saved state. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c18 --- Comment #18 from Pablo Sanchez <pablo@blueoakdb.com> --- Of course, it makes sense (I thought that that might be the case during my outing but doesn't hurt to ask). I confirmed after the reboot, that the `asound.state' file was recreated. Unfortunately, the mic didn't work. Immediately after, I tested loading the Fedora .cfg file and the mic works. Thx! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c19 --- Comment #19 from Pablo Sanchez <pablo@blueoakdb.com> --- Oh and the md5sum result is the same between the previous and re-gen'd `asound.state'
��������� # md5sum asound.state /var/lib/alsa/asound.state 7b0d7049115f8fbab4413302d8a1da37 asound.state 7b0d7049115f8fbab4413302d8a1da37 /var/lib/alsa/asound.state
Probably not important given the previous test results but I thought I'd mention it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c20 --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- (In reply to Pablo Sanchez from comment #18)
Of course, it makes sense (I thought that that might be the case during my outing but doesn't hurt to ask).
I confirmed after the reboot, that the `asound.state' file was recreated.
Wait, when was this created? At a fresh boot, it should remain without asound.state until you shutdown/reboot again. Maybe the modules weren't properly unloaded before the previous reboot? Could you retry the step again? - Forcibly unload modules - Confirm that /proc/asound/cards empty - Remove /var/lib/alsa/* - Reboot -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c21 --- Comment #21 from Pablo Sanchez <pablo@blueoakdb.com> --- Voila ! It's working! It's unclear how `asound.state' got into an unsound state but meh, it's working! Thank you so so much for your patience. I very much appreciate it. Let's close this issue. I'll update the upstream issue with the findings. I'm not sure how to set the status. I don't know whether metrics are run off of the status so either you can make it resolved with the proper resolution or please let me know and I'll mark it as such. Have a great day! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c22 --- Comment #22 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi, Unfortunately, the mic has stopped working. It turns out that it works only after the first boot when the previous recipe[1] is applied. After the second boot, it stops working. Shortly I'll attached some preliminary forensics: alsa-info.txt and output from 'alsactl store'. One key observation is after the first boot (when the mic works), /var/lib/alsa/asound.state is empty (zero-length). After the second boot, the file has content. ::: Recipe ::: cd /var/lib/alsa mv asound.state ~ fuser -k /dev/snd/* # Remove parent device /sbin/modprobe -r snd_sof_pci_intel_cnl mod=$(grep -m1 -E '^(snd[^ ]*|ac97_bus) [0-9]+ 0' /proc/modules) while [ -n "$mod" ]; do mod=${mod%% *} /sbin/modprobe -r $mod mod=$(grep -m1 -E '^(snd[^ ]*|ac97_bus) [0-9]+ 0' /proc/modules) done rmdir card0.conf.d # Should be empty ls /var/lib/alsa # confirm no cards listed cat /proc/asound/cards reboot -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c23 --- Comment #23 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 857609 --> https://bugzilla.suse.com/attachment.cgi?id=857609&action=edit tar-ball of boot 1 vs boot 2 forensics ��������� $ tar -zcvf boot.cmp.tar.gz boot.* boot.1st/ boot.1st/alsa-info.boot.1st.txt boot.1st/alsa.boot.1st.cfg boot.2nd/ boot.2nd/alsa-info.boot.2nd.txt boot.2nd/alsa.boot.2nd.cfg boot.cmp.tar.gz -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c24 --- Comment #24 from Takashi Iwai <tiwai@suse.com> --- Hm, the alsactl contents look identical in both cases. Do I understand correctly that, if you remove /var/lib/alsa/* before the reboot, the mic works always? OTOH, if /var/lib/alsa/* is present, the mic is always broken? Let's check whether they are really related. If they are related, at the 1st boot, run "alsactl store", and "alsactl restore". Does it break the mic recording? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c25 --- Comment #25 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, I'm sorry for the late response. Too many fires today.
Do I understand correctly that, if you remove /var/lib/alsa/* before the reboot, the mic works always?
I have to remove the devices *and* clear out the directory. Under the above conditions, after the first boot, the mic works.
OTOH, if /var/lib/alsa/* is present, the mic is always broken?
That does seem to be the case.
If they are related, at the 1st boot, run "alsactl store", and "alsactl restore". Does it break the mic recording?
The above was an interesting test. You obviously know your domain well because it did break the mic. I tried to anticipate what you may need so I captured some additional data. I also compared "alsactl store" .cfg file after boot 1 vs boot 2: they're identical. ::: /var/lib/alsa - before restore ::: # ls asound.state card0.conf.d/ # ls -la * -rw-r--r-- 1 root root 0 2022-04-01 22:26 asound.state card0.conf.d: total 0 drwxr-xr-x 1 root root 0 2022-04-01 22:27 ./ drwxr-xr-x 1 root root 48 2022-04-01 22:27 ../ root@zoom:/var/lib/alsa ::: /var/lib/alsa - after restore ::: # ls asound.state card0.conf.d/ # ls -la * -rw-r--r-- 1 root root 0 2022-04-01 22:26 asound.state card0.conf.d: total 0 drwxr-xr-x 1 root root 0 2022-04-01 22:31 ./ drwxr-xr-x 1 root root 48 2022-04-01 22:31 ../ ::: Restore w/-d ::: alsactl: set_controls:1499: device='hw:0', doit=0 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' alsactl: set_controls:1546: list count: 67 alsactl: set_controls:1574: maxnumid=67 maxnumid2=65 alsactl: set_controls:1579: more controls than maxnumid? alsactl: set_controls:1587: result code: -11 alsactl: sysfs_init:45: sysfs_path='/sys' alsactl: set_controls:1499: device='hw:0', doit=1 alsactl: set_controls:1511: card-info-id: 'sofsoundwire' alsactl: set_controls:1587: result code: 0 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c26 --- Comment #26 from Takashi Iwai <tiwai@suse.com> --- OK, then please reopen the upstream bug entry for the mic issue, and inform this new finding: the simple restore of the current working content of alsactl breaks the mic recording. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c27 --- Comment #27 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, I've reopened the upstream issue. In conjunction with your code, I created a prettified, reproducible test case. Thank you again for your help! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c28 --- Comment #28 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, As it's been nine days since the update to the upstream issue with no activity, I thought I'd ask how things were going there ... It's a fine balance between being a pest and not letting an issue fall through the crack. I hope I struck a proper balance. :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c29 --- Comment #29 from Takashi Iwai <tiwai@suse.com> --- Feel free to ping the upstream bug tracker. It's likely that they are too busy for other tasks. One thing you can test more would be, though, restoring the mixer element one by one, and check which one breaks the mic. For example, if "alsactl store" output contains the entry like state.sofsoundwire { control.1 { iface MIXER name 'rt711 DAC Surr Playback Volume' value.0 87 value.1 87 comment { ...... Then the element 1 can be restored manually via amixer like: % amixer -Dhw:sofsoundwire cset iface=MIXER,name='rt711 DAC Surr Playback Volume' 87,87 If restoring each element in that way, does it also break mic? If yes, which entry triggers it? That can be investigated. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c30 --- Comment #30 from Pablo Sanchez <pablo@blueoakdb.com> --- Hi Takashi, I finally wiggled free some time today to resume chasing this issue. The good news is that it seems the issue has been resolved. \o/ I confirmed that the mic was not working before I started. Next, I used the recipe that you provided to unload the modules and rebooted. After which, the mic was working. I did an `alsactl ... store' followed by a `alsactl ... restore' and the mic still was working. To be 'for sure, for sure', I rebooted four times. *grin* Using the mic web site, I was able to test switching between my onboard mic and my wireless earbuds. Everything is working well! In case there's interest, I'm now on TW drop 20220415. Clearly some fix came in between when I reported the bug and now. Good stuff! I'll attach the current `alsa.cfg' in case there's any interest. I'll close the bug too. Once again, thank you /so/ much for your help with this issue. I'll close the upstream issue too. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c31 --- Comment #31 from Pablo Sanchez <pablo@blueoakdb.com> --- Created attachment 858327 --> https://bugzilla.suse.com/attachment.cgi?id=858327&action=edit working alsa.cfg It was interesting to diff the /old/ vs /new/ `alsa.cfg' files. Not that it made much sense to my untrained eye. :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c32 Pablo Sanchez <pablo@blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://github.com/thesofpr | |oject/linux/issues/3532 | --- Comment #32 from Pablo Sanchez <pablo@blueoakdb.com> --- Hmmm, I'm not sure how to handle closing this bug. It has a dependency on the https://bugzilla.suse.com/show_bug.cgi?id=1197315 - the kernel stack trace. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 Bug 1197434 depends on bug 1197315, which changed state. Bug 1197315 Summary: kernel call trace when setting up sound card https://bugzilla.suse.com/show_bug.cgi?id=1197315 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1197434 https://bugzilla.suse.com/show_bug.cgi?id=1197434#c33 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #33 from Takashi Iwai <tiwai@suse.com> --- Let's close. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com