Speakers produce static noise when I move the mouse or the cpu is working

Hello, now I'm noticing again a problem with the speakers, those are producing static noise if I move the mouse or if the CPU is working with some process. It's like if I had HDD... but I have SSD... LMAO

I said again because I knew about this problem since kernel 5.0, so I always install 4.19 or 4.14 LTS. But know I have the problem with 4.19..., so probably because this kernel now received some patch from kernel 5.X?

Inxi info
System:    Host: aaron-e5-573 Kernel: 4.19.69-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 Desktop: Gnome 3.32.2 
           wm: gnome-shell dm: GDM 3.32.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Acer product: Aspire E5-573 v: V3.72 serial: <root required> 
           Mobo: Acer model: ZORO_BH v: Type2 - A01 Board Version serial: <root required> UEFI: Insyde v: 1.37 
           date: 02/16/2016 
Battery:   ID-1: BAT1 charge: 32.1 Wh condition: 32.1/37.0 Wh (87%) volts: 17.1/14.8 model: SANYO AL15A32 type: Li-ion 
           serial: 56616 status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell rev: 4 
           L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17604 
           Speed: 800 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:1616 
           Display: x11 server: X.org 1.20.5 driver: i915 compositor: gnome-shell resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 19.1.5 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel Broadwell-U Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel 
           bus ID: 00:03.0 chip ID: 8086:160c 
           Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0 
           Sound Server: ALSA v: k4.19.69-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI 
           driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: down mac: ff:ff:ff:ff:ff:ff
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Foxconn driver: ath10k_pci 
           v: kernel port: 3000 bus ID: 03:00.0 chip ID: 168c:0042 
           IF: wlp3s0 state: up mac: ff:ff:ff:ff:ff:ff 
Drives:    Local Storage: total: 704.24 GiB used: 609.83 GiB (86.6%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDP256G size: 238.47 GiB speed: 6.0 Gb/s serial: 124729400509 
           scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Toshiba model: MQ01ABD050 size: 465.76 GiB rotation: 5400 rpm 
           serial: 1437SMD4S scheme: GPT 
Partition: ID-1: / size: 60.00 GiB used: 11.77 GiB (19.6%) fs: f2fs dev: /dev/sda2 
           ID-2: /home size: 167.97 GiB used: 144.90 GiB (86.3%) fs: f2fs dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 214 Uptime: 1h 59m Memory: 15.58 GiB used: 2.00 GiB (12.8%) Init: systemd v: 242 Compilers: 
           gcc: N/A Shell: bash v: 5.0.9 running in: gnome-terminal inxi: 3.0.36 

Journalctl -p 3 -xb
-- Logs begin at Sat 2019-09-14 08:19:02 WEST, end at Sun 2019-09-15 15:31:06 WEST. --
sep 15 13:29:05 aaron-e5-573 kernel: dw_dmac INTL9C60:00: Missing DT data
sep 15 13:29:19 aaron-e5-573 gdm-password][1241]: gkr-pam: unable to locate daemon control file
dmesg | grep dw_dmac
[    0.617656] dw_dmac INTL9C60:00: Missing DT data
[    0.634425] dw_dmac INTL9C60:00: DesignWare DMA Controller, 8 channels

I need to know what exactly is dw_dmac, I didn't find anything relevant about that yet...

I saw this issue with both kernels 5.X and 4.19: kernel: dw_dmac INTL9C60:00: Missing DT data. And I found this thread about this problem and related also with sound problems, but no solution.

My sound card is working fine, but I have the static noise with headphones and without headphones. The static noise is only the speakers, the headphones are fine. But I have no idea what is going on... Thanks :slight_smile:

Looks like it's a DMA controller.
DesignWare DMA Controller

I have no idea how to diagnose random electronic noise bleeding through to other components, which is what this seems like.

However, your BIOS is pretty old. Have you checked to see if there's a newer one available?
A new BIOS doesn't sound like it would be useful but you'd be surprised.

Hello SinisterBrain, yes I have the latest version of BIOS. Thanks for the info, so if it's the DMA controller sounds pretty serious problem. For the moment I can use the kernel 4.14 LTS, with this kernel is working fine. But if in the future I can use the newest kernel I will have the same problem, let me try to find more information about that.

Maybe with the RT Kernel or LowLatency if I want the newest?

Yes, I'd try as many kernels as you can other than the EOL one of course.
I'm just a bit mystified why a DMA controller would do such a wonky thing.
You're not having crashes or corrupted programs or anything, correct?

I also found this:
https://bbs.archlinux.org/viewtopic.php?id=236757

No, I don't have corrupted programs or something weird, this is a fresh install. I have the problem with the kernel 5.0 or superior, and know 4.19. I had the same problem when I installed OpenSUSE TW with the kernel 5.0 a year ago, and Ubuntu 18.04.2 or something.

Do you use bluetooth?

If not, with a kernel that's causing the issue. Turn bluetooth off and see if it still happens.

At least let's eliminate that.

Ok, I tried to turn off the Bluetooth but the noise is still there. I read that thread https://bbs.archlinux.org/viewtopic.php?id=236757 and it looks like a bug and some report in Bugzilla, but that report was rejected...

The best way for the moment is to stay in 4.14 or tray the RT kernel. Thanks for the help SinisterBrain :slight_smile:

1 Like

Not much help. :smirk:

Bluetooth can do that weird bleed through so at least it's tested and removed from the list of "maybes".

It was rejected because it's not an Arch bug. That package is apparently maintained by Intel. As far as I can see, there are a scattering of reports back to 2016 about issues with that package.
Not sure what to tell you about future kernels.
Keep trying? Test the RTs for sure.

Good luck.

Sorry, I forgot something when I turn off the Bluetooth I have these issues:

Journalctl -p 3 -xb
-- Logs begin at Sat 2019-09-14 08:19:02 WEST, end at Sun 2019-09-15 17:16:50 W>
sep 15 17:14:00 aaron-e5-573 kernel: dw_dmac INTL9C60:00: Missing DT data
sep 15 17:15:30 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked thro>
sep 15 17:16:04 aaron-e5-573 gdm-password][4027]: gkr-pam: unable to locate dae>
sep 15 17:16:09 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked thro>
lines 1-5/5 (END)...skipping...
-- Logs begin at Sat 2019-09-14 08:19:02 WEST, end at Sun 2019-09-15 17:16:50 WEST. --
sep 15 17:14:00 aaron-e5-573 kernel: dw_dmac INTL9C60:00: Missing DT data
sep 15 17:15:30 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked through rfkill (0x12)
sep 15 17:16:04 aaron-e5-573 gdm-password][4027]: gkr-pam: unable to locate daemon control file
sep 15 17:16:09 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked through rfkill (0x12)
lines 1-5/5 (END)
-- Logs begin at Sat 2019-09-14 08:19:02 WEST, end at Sun 2019-09-15 17:16:50 WEST. --
sep 15 17:14:00 aaron-e5-573 kernel: dw_dmac INTL9C60:00: Missing DT data
sep 15 17:15:30 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked through rfkill (0x12)
sep 15 17:16:04 aaron-e5-573 gdm-password][4027]: gkr-pam: unable to locate daemon control file
sep 15 17:16:09 aaron-e5-573 bluetoothd[2761]: Failed to set mode: Blocked through rfkill (0x12)

bluetoothd[2761]: Failed to set mode: Blocked through rfkill (0x12)

Yeah, it's just complaining about the systemd bluetooth service.
When you turn it back on it'll stop.

1 Like

Try running alsamixer in a terminal and checking if all gains are at 0 dB or less.

Forum kindly sponsored by Bytemark