Summary: | PulseAudio is interrupted for 380 milliseconds exactly every 20 minutes | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Bert Aerts <bert.ram.aerts> |
Component: | modules | Assignee: | pulseaudio-bugs |
Status: | RESOLVED INVALID | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | doktor5000, lennart |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Bert Aerts
2014-12-11 07:37:51 UTC
The second part is not relevant. I have no exact correlation between sound interruption and occurance of irq/46-iwlwifi as there is no time-stamp available in top. When there is no sound interrupt, irq/46-iwlwifi also reaches the top in the command top. Question remains: how can I find the root-cause of the 380 millisecond interrupt in sound on bluetooth headphones that happens every 20 minutes? The fact that the iwlwifi irq doesn't always cause audio interruptions doesn't mean that it never causes them. Could you try unloading the iwlwifi module? Tried to unload iwlwifi and succeeded in it. Bluetooth is handled by another module, as it kept on working. [root@Dell7720Mageia4 bert]# rmmod iwlwifi rmmod: ERROR: Module iwlwifi is in use by: iwldvm [root@Dell7720Mageia4 bert]# rmmod iwldvm [root@Dell7720Mageia4 bert]# rmmod iwlwifi But still interrupt in sound via Bluetooth headphones as shown here: [root@Dell7720Mageia4 bert]# journalctl --lines=20 -- Logs begin at Fri 2014-02-21 19:17:02 CET, end at Mon 2014-12-15 12:39:03 CET. -- Dec 15 12:36:54 Dell7720Mageia4 chronyd[966]: Can't synchronise: no reachable sources Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Chip: i8k-virtual-0 Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Adapter: Virtual device Dec 15 12:39:03 Dell7720Mageia4 pulseaudio[5259]: [bluetooth] module-bluez5-device.c: Skipping 400501 us (= 70648 bytes) in audio stream Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Right Fan: 0 RPM Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: CPU: 68.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: temp2: 37.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: temp3: 51.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: temp4: 55.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Chip: acpitz-virtual-0 Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Adapter: Virtual device Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: temp1: 70.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: temp2: 70.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Chip: coretemp-isa-0000 Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Adapter: ISA adapter Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Physical id 0: 69.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Core 0: 62.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Core 1: 60.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Core 2: 61.0 C Dec 15 12:39:03 Dell7720Mageia4 sensord[1135]: Core 3: 68.0 C But exactly at the moment of interrupt in sound, sensord was active. So what is the priority of sensord? [root@Dell7720Mageia4 bert]# ps -ef | grep sensord UID PID PPID C STIME TTY TIME CMD root 1135 1 0 12:19 ? 00:00:01 /usr/sbin/sensord -i 1m -l 20m -f daemon What do we see: logging every 20 minutes... twenty minutes... the sound interrupt interval !!! So I disabled sensord in Mageia Control Center / System / Manage System Services And the 20 minutes interval passed without sound interruption !!! Marked as FIXED and INVALID. As it is not a PulseAudio bug but an i8k bug. After unloading kernel module i8k, the command sensors works OK. No interrupt in sound anymore. i8k is intended for accessing data from the SMM BIOS and the DMI table on Dell laptops, but is not up to date for my Dell Inspiron 17R SE 7720. I'm happy to hear you got the problem resolved! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.