|
Bugzilla – Full Text Bug Listing |
|
Description
Vadim Krevs
2017-12-18 20:23:40 UTC
Created attachment 753553 [details]
/var/log/messages for first boot with 4.14.6-1.5
Booting into previous 4.14.4-1.6 kernel resolves the issue (until the next kernel update?). By some reason the HD-audio driver got unloaded and the ASoC HD-audio driver got loaded after that. As there is no change in the relevant drivers between two kernel versions, it must be a problem brought from a different place. Could you give the dmesg output from the working kernel (4.14.4)? I guess putting the blacklist to snd-soc-skl should work around it. After getting the good kernel messages above, try to add the file /etc/modprobe.d/50-hda-blacklist.conf containing the following line: blacklist snd-soc-skl and retest 4.14.6 kernel again. Created attachment 753611 [details]
dmesg output after boot with 4.14.4
dmesg output after boot with 4.14.4 attached
Blacklisting snd-soc-skl works around the issue in 4.14.6 kernel. Thank you Takashi. Good to hear. But it doesn't mean that the issue is really fixed. The fact that another driver gets loaded implies that something went wrong beforehand. Now looking at your original log, there are a few AMDGPU messages around 136, 143, 187 and 192 seconds: [ 136.769175] [drm] PCIE GART of 256M enabled (table at 0x000000F400040000). [ 136.777404] amdgpu: [powerplay] can't get the mac of 5 ..... [ 143.844475] amdgpu: [powerplay] VI should always have 2 performance levels [ 143.886723] amdgpu 0000:01:00.0: GPU pci config reset [ 187.627361] [drm] PCIE GART of 256M enabled (table at 0x000000F400040000). [ 187.630772] amdgpu: [powerplay] can't get the mac of 5 ..... [ 192.993036] amdgpu: [powerplay] VI should always have 2 performance levels [ 193.039854] amdgpu 0000:01:00.0: GPU pci config reset Then USB-audio is deregistered and the kernel WARNING appears from snd-soc-skl: [ 195.275515] usbcore: deregistering interface driver snd-usb-audio [ 196.073281] memremap attempted on mixed range 0x0000000000000000 size: 0x0 [ 196.073287] ------------[ cut here ]------------ [ 196.073292] WARNING: CPU: 3 PID: 4834 at ../kernel/memremap.c:98 memremap+0x122/0x170 Do you know what happened on your machine? Did you unplug something, or any special action at these events at all? Also, could you try to uninstall virtual box modules? It's out-of-tree modules, hence one of suspects in such a secret breakage. Nothing I am aware of. Did an "init 3", then ran a "zypper dup" to install latest TW snapshot which included the new kernel, then "reboot" to reboot, and then, once booted with the new kernel, there was no sound. I'll try uninstalling virtualbox driver and removing the module blacklist entry to see if that makes any difference once I get home this evening. Hmm, this is strange. Came home, commented out the module blacklist entry, rebooted without uninstalling vbox drivers. And after reboot, sound works in 4.14.6 ... dmesg attached. Feel free to close the bug. Created attachment 753714 [details]
dmesg output after boot with 4.14.6 and working sound
OK, then could you try to re-install / re-enable virtualbox stuff again? If this triggers the bug again, it's a breakage due to that. I did not unininstall vbox drivers. That's the thing - just rebooting again resulted in working sound - without the need for the module blacklist entry. Hrm, the bug already appears unusual, and it indicates some weird memory corruption or unbalanced refcount or such, i.e. the behavior isn't deterministic. Please update the bug once when you can reproduce the issue reliably. Thanks. (In reply to Takashi Iwai from comment #13) > Hrm, the bug already appears unusual, and it indicates some weird memory > corruption or unbalanced refcount or such, i.e. the behavior isn't > deterministic. > Please update the bug once when you can reproduce the issue reliably. > Thanks. Will do. Closing as invalid for the time being. You still can reopen if you have something new. Several days ago I had upgraded the same laptop to the latest TW snapshot which includes kernel 5.1.7-1.2. Just updated to latest Tumbleweed snapshot that includes 4.14.6-1.5. After reboot, there is no sound, the KDE sound icon in the task bar has a red minus in it. Takashi's workaround from comment #3 does not seem to have any effect. If I go into Yast->Sound, select the unconfigured "Sunrise Point-LP HD Audio" device, click Edit to perform Quick default configuration, then configuration fails, but the the KDE sound icon in the task bar changes to normal (red minus is gone), and I now have sound - until next reboot. $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.1.7-1-default root=UUID=d58e8e85-bfdd-4a74-a694-5149ccd85110 quiet resume=/dev/sda3 splash=silent quiet showopts $ rpm -qa | grep kernel | sort kernel-default-5.1.4-1.1.x86_64 kernel-default-5.1.7-1.2.x86_64 kernel-default-devel-5.1.4-1.1.x86_64 kernel-default-devel-5.1.7-1.2.x86_64 kernel-devel-5.1.4-1.1.noarch kernel-devel-5.1.7-1.2.noarch kernel-docs-5.1.7-1.2.noarch kernel-firmware-20190514-1.3.noarch kernel-macros-5.1.7-1.2.noarch kernel-source-5.1.4-1.1.noarch kernel-source-5.1.7-1.2.noarch kernel-syms-5.1.4-1.1.x86_64 kernel-syms-5.1.7-1.2.x86_64 Attaching /var/log/messages, dmesg and alsa-config logs after boot when there is no sound, and after doing Yast->Sound->Edit after which there is sound. Created attachment 808174 [details]
/var/log/messages for boot with 5.1.7-1.2
Created attachment 808175 [details]
dmesg for boot with 5.1.7-1.2
Created attachment 808176 [details]
alsa-info.txt for boot with 5.1.7-1.2 (no sound)
Created attachment 808177 [details]
/var/log/messages for boot with 5.1.7-1.2 after running Yast sound module
Created attachment 808178 [details]
dmesg for boot with 5.1.7-1.2 after running Yast sound module
Created attachment 808179 [details]
alsa-info.txt for for boot with 5.1.7-1.2 after running Yast sound module (sound works)
Pls ignore the second sentence in comment 16 (cut and paste error). $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] (rev c1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07) 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Was browsing TW bug list filtered by "sound" and stumbled on "Bug 1116849 - yast2-sound: do not add sound modules to initrd". My laptop also had an /etc/modules-load.d/yast.conf containing "snd-hda-intel". Removed the file, and re-ran "dracut -f", rebooted - and sound works. So looks like /etc/modules-load.d/yast.conf with "snd-hda-intel" can result in more than one "quirk". *** This bug has been marked as a duplicate of bug 1116849 *** |