Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

Bug #571770 reported by Øyvind Stegard
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.32-22-generic

Sometimes during audio playback, a kernel thread named "[hd-audio0]" will consume excessive amounts of CPU and cause audio crackling. It seems to be more easily triggered when displaying video in fullscreen (or Rhythmbox visualizations) or dragging windows around while playing music, somehow relating it graphics operations (running default radeon driver with KMS and Compiz).

This all started after moving from Ubuntu Karmic to Lucid (never had this problem before).

Setting package to kernel, since it's probably alsa snd_hda_intel kernel module which is to blame.

Ubuntu 10.04 x86, Intel Core Duo 2GHz, 3GB RAM, ATI X1400 Radeon Mobility graphics.
Audio chip: Analog Devices AD1981 [HDA]

WORKAROUND: Disabling radeon KMS makes all the audio crackling go away.

Attaching:
* Screenshot of top running over Rhythmbox w/fullscreen visualizations, showing [hd-audio0] consuming more CPU than everything else at the time (audio crackles).
* Output of "lspci -vvnn"
* Output of "dmesg"
* Contents of /proc/interrupts
* ALSA info, as provided by the alsa-info.sh script.

Related to this: https://bugzilla.kernel.org/show_bug.cgi?id=14935 ???

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :
tags: added: kernel-sound
tags: added: kj-triage
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Currently testing if "position_fix=1" option to module snd-hda-intel will help.

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

So far it looks like the module option "bdl_pos_adj=0" is a work-around for this issue.

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

I'm currently running snd-hda-intel module with options "position_fix=1 bdl_pos_adj=0". This stops "[hd-audio0]" from showing up in top, but audio still crackles when scrolling in Firefox (for instance) after having used the desktop session for a while (more windows and apps open => more graphical resource usage). So in-kernel audio driver is badly affected by graphical operations, so much that it probably voids any effect of setting higher priority on pulseaudio user-space process...

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Tried snd-hda-intel option "enable_msi=1", since I figured it might be some IRQ issue. That didn't help.

So I noticed CPU0 was handling all interrupts occuring on my system (via /proc/interrupts) for radeon and hda-intel modules. I altered the IRQ affinity for hda-intel, so it would be handled on the other CPU, but that did not help on the audio crackling either.

So it seems I'm properly stuck for now, unless someone can come up with some other advice. Try newer kernel, perhaps ? Mainline PPA ?

summary: - Thread [hd-audio0] consuming excessive amounts of CPU during audio
- playback
+ Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Mainline 2.6.34-rc6 has audio problems as well. While the radeon KMS performance is a *lot* better than in Lucid 2.6.32-kernel, graphical operations still sometimes cause audio skipping or slight crackling (for instance, fullscreen Flash video playback has a tendency to provoke the crackling). In addition to that there are audio/video sync issues caused by some ALSA updates (https://bugzilla.kernel.org/show_bug.cgi?id=15796), which makes it more difficult to know if the problems are really the same as in standard Lucid kernel.

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

How to most easily reproducce and verify the audio crackling:
1) Start gstreamer-properties and do a sound test. This produces a sound which very easily reveals crackling.
2) Fire up a web browser and watch a Youtube video in fullscreen with Flash plugin (low volume).
3) Listen to the sound of pop corn popping.

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Running Compiz or not does not matter. However, disabling radeon KMS makes all the audio crackling go away.

description: updated
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Another confirmed case where disabling KMS also resolves issues with audio crackling: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/578342

Revision history for this message
In , JasonPorter (jasonporter) wrote :

Several Launchpad bug reports in process report radeon KMS conflicts with Intel wifi and audio output, causing wireless to hang/drop until power cycle and audio to crackle during any high GPU load. Disabling KMS as a workaround returns normal system operation.

Relevant Launchpad reports:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/564376
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/578342
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571770
And one on Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=15912

My own hardware is a Thinkpad T60 with Radeon X1400 and Intel wireless (iwl3945 driver) running vanilla Ubuntu 10.04. Users of Radeon X1250, X1300, and Xpress 200M chipsets have also reported the same behavior, on Lenovo, Dell and LG laptops. Using a mainline kernel does not change the behavior.

This may possibly be due to a difference in PCI configuration between KMS and UMS, they use different IRQs for "Pin A" as detailed in the Bugzilla report linked above.

Thanks for any assistance you can provide! And thanks for all your hard work!

Revision history for this message
JasonPorter (jasonporter) wrote :

Adding the radeon driver project to this, and linking to upstream bug report on freedesktop.org.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Confirming this one, Thinkpad Z61m, ATI X1400. However, the IRQ difference does not seem to matter for the audio problems (I've tested with radeon KMS both with and without MSI, which is the difference between the two PCI configs listed in bug at https://bugzilla.kernel.org/show_bug.cgi?id=15912).

Revision history for this message
In , agd5f (agd5f) wrote :

Is there an option in your bios to assign different irqs to different pci devices? Some systems set every device to the same irq.

Revision history for this message
In , Maarten Fonville (maarten-fonville) wrote :

I don't think it is directly an IRQ issue that can be solved in the BIOS.
Because on my girlfriend's laptop which is also hit by this problem the radeon takes IRQ 17 with IO-APIC-fasteoi and hda_intel takes IRQ 24 with PCI-MSI-edge

Revision history for this message
In , Maarten Fonville (maarten-fonville) wrote :

(In reply to comment #3)
> I don't think it is directly an IRQ issue that can be solved in the BIOS.
> Because on my girlfriend's laptop which is also hit by this problem the radeon
> takes IRQ 17 with IO-APIC-fasteoi and hda_intel takes IRQ 24 with PCI-MSI-edge

Actually, before booting the kernel itself (thus it can not be seen in DMESG) there is the message that starts with:
pci 0000:00:00.0: address space collision [..more stuff here..]
Just like in this mail I believe: http://lkml.org/lkml/2010/3/12/92

I don't know whether this could be relevant.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

I have no messages about address space collisions in kernel boot log. I'll add my hardware info to this bug tomorrow (interrupts, PCI, dmesg, Xorg, etc).

Revision history for this message
In , JasonPorter (jasonporter) wrote :

This appears to also be causing kernel crashes on some systems when wifi is powered off using the hardware switch. Disabling radeon KMS causes the crash behavior to disappear. I will inform devs in the upstream bug reports on that issue.

Reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/555286

Revision history for this message
In , JasonPorter (jasonporter) wrote :

(In reply to comment #6)

Oops, nevermind... I'm already upstream. Too many tabs open, sorry.

Revision history for this message
In , agd5f (agd5f) wrote :

Is there an option in your bios to assign different irqs to different pci
devices? Some systems set every device to the same irq. If so, please try changing the setting to auto, or select different irqs for each device and see if that helps. Also, please try both with and without msi enabled (boot with pci=nomsi).

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

(In reply to comment #8)
> Is there an option in your bios to assign different irqs to different pci
> devices? Some systems set every device to the same irq. If so, please try
> changing the setting to auto, or select different irqs for each device and see
> if that helps. Also, please try both with and without msi enabled (boot with
> pci=nomsi).

Yes. However, the list looks very uninformative. It's under PCI config, and basically contains just INTA-> 11, INTB -> 11, INTC -> 11, and so on. Tried setting to Auto-select on all entries (instead of 11). System booted OK, but it didn't help (on KMS+audio problems). Tried assigning sequentially from IRQ 3 and up, but then I got a really loud Thinkpad-style alarm beep, system didn't get past POST, and BIOS informing that network controller was missing IRQ. So obviously I switched back to default settings. The /proc/interrupts list didn't really look any different with BIOS-autoconfig for PCI IRQs (IIRC).

Booting with option pci=nomsi does not help at all, even though it definitely affects IRQ config, since /proc/interrupts contains no MSI-entries when booting with this option.

I will now be attaching some info for system running 2.6.34 kernel on Ubuntu Lucid x86 with ATIX1400 (KMS-mode). System has severe audio glitching with KMS, and no glitching at all in UMS mode.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Created an attachment (id=35734)
Kernel boot log

Audio glitching reproduced immediately after logging in to X session.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Created an attachment (id=35735)
Contents of /proc/interrupts

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Created an attachment (id=35736)
Contents of /proc/interrupts with MSI disabled

Does not resolve issue.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Created an attachment (id=35737)
PCI device config

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Created an attachment (id=35738)
Xorg startup log

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

The test setup I use to quickly reproduce and verify that the problem is there:

1) Play a pure sound which easily revelase playback glitches:
$ gst-launch-0.10 audiotestsrc ! pulsesink

2) Play some video (doesn't matter what) with MPlayer, using plain x11 output and no sound:
$ mplayer /path/to/some/movie.avi -vo x11 -zoom -nosound

3) Test audio starts glitching and the glitching becomes worse if I put the video in fullscreen.

And some observations about test:

1) There is not much load on system during test (MPlayer uses around 40% CPU, Xorg floats under 12% CPU, for a 1024x576 video with no sound).

2) There is a lot less audio glitching if I run things in a completely composited environment (e.g. Compiz with no unredirection for fullscreen windows). If I *do* unredirect fullscreen windows with Compiz the glitching becomes worse in fullscreen.

3) There is alomst no glitching at all if using XV for video playback in the test, instead of plain old x11. Obviously that's not going to help for apps that don't use XV, like fullscreen Flash video streaming or any affected non-video app.

4) The glitching is worse when video window is full screen.

5) HDA intel driver typically always reports that IRQ timing work-around has been activated. This doesn't happen in UMS-mode.

And some observations not just related to the specific test setup:
1) Flash fullscreen video playback causes more severe audio glitches if *not* running composited in fullscreen, for instance under Compiz with "Unredirect fullscreen windows" enabled. This is what typically also takes down wireless (just happened now with current setup, as I was testing Flash and writing this).

2) Flash fullscreen video causes glitches even when redirected in composited env.

3) Flash doesn't use XV, seems to correspond well with MPlayer -vo x11 being much worse than when using -vo xv.

4) There are no playback issues with video during any of these tests, the video is smooth, system not overloaded. And besides, the test sound generator requires almost no resources at all.

5) [ 1535.437114] CE: hpet increased min_delta_ns to 7500 nsec
Don't really know the meaning of this one, but it typically appears during problems with wireless and/or audio when running under KMS. Kernel compensating for what is seen as accuracy issues with system timing ?

6) It doesn't have to be MPlayer-vo-x11 or Flash that triggers problem, I just use them because they so easily reproduce it. I have heard audio popping when scrolling Firefox pages or moving windows around, and I've managed to take down wireless when launching Neverball (OpenGL-game).

7) No matter what IRQ config or snd-hda-intel options I test, the problems are always there with KMS and disappear with UMS.

Revision history for this message
In , JasonPorter (jasonporter) wrote :

To add my own results... booting with pci=nomsi doesn't seem to have an effect on my system (Thinkpad T60). I have the same PCI options in BIOS as Øyvind reports, all are set to "11" by default but changing to Auto seems to have very little effect on actual behavior after boot. I will test further to see if there are any other differences with MSI off, but so far it doesn't seem to have helped.

Revision history for this message
frankvielma (frankvielma) wrote :

I have a similar problem using a clean installation with Ubuntu 10.04 x86, Intel Pentium D 2.8 GHz, 4GB RAM, Intel 82945G/GZ Integrated Graphics Controller, Intel Corporation N10/ICH 7 Family High Definition Audio Control...

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
04:08.0 Ethernet controller: Intel Corporation N10/ICH 7 Family LAN Controller (rev 01)

I had used Debian 5.04 without any problems...

I used "powertop" it fixed partially the problem but after of a random time, the problem comes back.

Any suggestions ?

Thanks in advance,

Revision history for this message
In , agd5f (agd5f) wrote :

Does booting with radeon.disp_priority=1 help?

Revision history for this message
In , agd5f (agd5f) wrote :

Apply the settings with a cold boot.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

(In reply to comment #17)
> Does booting with radeon.disp_priority=1 help?

Does not help on my hardware. Tested with kernel 2.6.34, cold boot.

Revision history for this message
In , JasonPorter (jasonporter) wrote :

(In reply to comment #17)
> Does booting with radeon.disp_priority=1 help?

For some reason, passing that option at boot seems to disable KMS on my system. I've tried it both without a radeon.modeset declaration, and with radeon.modeset=1, and in both cases Xorg.0.log shows KMS to be disabled when radeon.disp_priority=1 is on.

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #20)
> (In reply to comment #17)
> > Does booting with radeon.disp_priority=1 help?
>
> For some reason, passing that option at boot seems to disable KMS on my system.
> I've tried it both without a radeon.modeset declaration, and with
> radeon.modeset=1, and in both cases Xorg.0.log shows KMS to be disabled when
> radeon.disp_priority=1 is on.

If your kernel is too old, the option is not valid and the module won't load. See modinfo radeon to verify.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

I've noticed that the audio glitches become a lot worse when many windows are open and running Compiz (I did an artificial test). I can open lots of windows on one desktop, switch back to an empty desktop, open a single window there and trigger audio drop-outs (simple test sound) just by toggling maximization state of that single window, even though all the other windows are not in view and system load is close to nil. Basically, most Compiz-operations besides simple window movement will cause glitches.

Interestingly, I might have pushed things too far, since Compiz crashed with this message:
drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.

Kernel log contained this:
[ 543.577306] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
[ 574.532539] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
[ 742.437808] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

* This was all with radeon.disp_priority=1, cannot say whether that mattered or not.
* Don't know the consequences of using the Ubuntu default Xorg-driver/libdrm/DRI-stuff together with 2.6.34 mainline kernel DRM. I haven't noticed any bad things in particular during normal usage (quite the contrary, KMS performance with 2.6.34 seems better), except for the issues at hand of course.
* The version of the radeon module in the default Ubuntu kernel does not have disp_priority option.

Revision history for this message
In , JasonPorter (jasonporter) wrote :

(In reply to comment #21)
> If your kernel is too old, the option is not valid and the module won't load.
> See modinfo radeon to verify.

I'm running the standard 2.6.32-22-generic that is current in Ubuntu Lucid.

Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

Has it been considered that this might be due to interrupt latency caused by radeon KMS? E.g. spending too much time in the IRQ handler or unnecessarily running it with other IRQs disabled.

Changed in xserver-xorg-driver-ati:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in xserver-xorg-driver-ati:
importance: Medium → Unknown
Changed in xserver-xorg-driver-ati:
importance: Unknown → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
24 comments hidden view all 104 comments
Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

Created attachment 48007
dmesg from Ubuntu 11.04 - unaffected

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

Created attachment 48008
dmesg from Fedora 15 - affected

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

I've added dmesg output from Ubuntu 11.04 which is not affected with the bug (at least on my laptop - Thinkpad T60, 2623P2U, X1300) and Fedora 15 which does have the problem. Unless I missed something, the only relevant difference is DRM version reported, which is 2.8 for Ubuntu and 2.10 for Fedora (how come that's possible is another question).
So far, the following does not help:
- disp_priority=1
- agpmode=1
- gartsize=64
- dynclks=0

Revision history for this message
In , Jantaegert (jantaegert) wrote :

(In reply to comment #45)

Dynamic Powermanagement is disabled here (powermanagement profile is fixed to "default", what means, that all pcie lines stay allways enabled).

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

I played a bit with power_profile settings and it turns our that whenever profile is set to high, mid, sound stuttering is pronounced. Yet, once set to low, stuttering is gone (or unnoticeable).
If anyone wants to try (adjust path to suit your hardware):
echo low > /sys/class/drm/card0/device/power_profile
Then the actual frequency can be verified by:
cat /sys/kernel/debug/dri/0/radeon_pm_info

Also dynpm power_method does not really work, there was another bug report recenty that the frequency is never lowered if dynpm is used.

Additionally, given the recent fuss about pcie_aspm=force (and possible effect on PCIe), sound stuttering is present regardless of the setting.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

(In reply to comment #50)
> I played a bit with power_profile settings and it turns our that whenever
> profile is set to high, mid, sound stuttering is pronounced. Yet, once set to
> low, stuttering is gone (or unnoticeable).
> If anyone wants to try (adjust path to suit your hardware):
> echo low > /sys/class/drm/card0/device/power_profile
> Then the actual frequency can be verified by:
> cat /sys/kernel/debug/dri/0/radeon_pm_info

Confirming this on ATI X1400 mobile, Ubuntu 11.04 x86. When using the "low" power profile, audio stuttering/crackling is much less prevalent (or maybe not even noticable) in Youtube fullscreen vids. Using the "high" setting results in definite audio crackling when switching to fullscreen. This is with the very latest Flashplayer 11 beta for Linux released today.

On my card, low setting results in:
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 392000 kHz
current engine clock: 128250 kHz
default memory clock: 350000 kHz
current memory clock: 135000 kHz
PCIE lanes: 1

High setting gives:
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 392000 kHz
current engine clock: 391500 kHz
default memory clock: 350000 kHz
current memory clock: 342000 kHz
PCIE lanes: 0

There's a difference not only in board frequencies, but also the PCIE lanes number (0 means full throttle, or is "more performant" than 1 I guess ??).

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

(In reply to comment #51)
> There's a difference not only in board frequencies, but also the PCIE lanes
> number (0 means full throttle, or is "more performant" than 1 I guess ??).

The PCIe lanes information seems to be read from the card itself (at least that's for RV515), look here:
http://lxr.linux.no/#linux+v2.6.39/drivers/gpu/drm/radeon/r300.c#L553
While 1 is understandable (PCIe x1), 0 value is confusing and I can't tell if that'x x16 or not. Maybe one of the driver authorsa can provide some input.

I've failed to locate any docs that contain information on the registers exposed on the PCI.

Revision history for this message
In , agd5f (agd5f) wrote :

Does adding noapic to the kernel commandline in grub help? See the last few comments in bug 37679.

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

(In reply to comment #53)
> Does adding noapic to the kernel commandline in grub help? See the last few
> comments in bug 37679.
No, it seems to have no effect on the problem, at least on my setup.

Revision history for this message
In , Richtigfalsch (richtigfalsch) wrote :

I'd like the importance of this bug being corrected to 'major' because disabling KMS in fact means a major loss of functionality. I'm now on kernel 2.6.40 and sadly this heavy bug still is there.

I skipped form Windows to Linux, mainly because the ATI Driver for the x1400 in my Thinkpad T60 (with iwl3945 od course) is crap.Now having tried many different distributions and kernels, i can confirm the bug still is there, and is making the notebook unusable. There's no 3D acceleration available at all on this GPU with KMS disabled. When playing a flash video it needs about 30 seconds fpr reaction if I clock some control with the mouse. Compiz or DirectX in Wine aren't working at all, and make the display crash. The GPU is wasting much energy and the notebook is running very hot, and overall just sluggish and not enjoyable in any fashion, I'd rather use my old Pentium M notebook, if it wasn't defective.

Please consider creating a solution fot this problem, as there's no single alternative for many Notebook owners, of expecially good notebooks (Thinkpad, Dell and more).

Problems with KMS enabled remain as before:
-iwl3945 WLAN gets slower and slower, until disconnect.
-heavy video (especially fullscreen) make the sound stutter in a fashion that makes it impossible to understand spoken word

Thanks,

Changed in xserver-xorg-driver-ati:
importance: Medium → High
Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Seems worse than ever on Ubuntu 11.10 just released (kernel 3.0, libdrm 2.4.26, xserver 1.10.4, using the new Unity-interface-thing). Just moving the mouse pointer is enough to disturb audio now, apparently. And moving windows around turns audio into bubbling porridge.

Revision history for this message
In , Øyvind Stegard (oyvindstegard) wrote :

Unity is sluggish on the X1400. Guess it's too old to cope now, with the latest desktop tech. Anyways, audio interruption is more or less constant after a while. Don't even need to move anything. Got these:

[ 931.698537] CE: hpet increased min_delta_ns to 515452 nsec
[ 1019.733804] CE: hpet increased min_delta_ns to 773178 nsec
[ 1023.203405] hrtimer: interrupt took 7398146 ns
[ 1171.028962] CE: hpet increased min_delta_ns to 1159767 nsec

Revision history for this message
In , Maciej Borzecki (maciek-borzecki) wrote :

(In reply to comment #57)
> Unity is sluggish on the X1400. Guess it's too old to cope now, with the latest
> desktop tech.
Not really. Worked great with UMS. Compiz with way more advanced effects than fade in/out was smooth, same for ioquake running at decent framerate.

Revision history for this message
In , Tom Morton (tomm) wrote :

I get this on my Thinkpad T60, Radeon X1300 running debian sid.

As well as crackle on the internal intel audio, I get even worse crackle and popping when using my Logitech V20 USB speakers.

The only thing that resolves the problem for me is:

echo mid > /sys/class/drm/card0/device/power_profile

But then gnome-shell and all 3d apps are really slow.

Revision history for this message
In , Steffen-schloenvoigt (steffen-schloenvoigt) wrote :

Same problem on openSUSE 12.1 with lenovo T60, Radeon Mobility X1400

Revision history for this message
In , stevenb (stevenb) wrote :

Hi

Jan Kouba put me on track to this bug-page. I don't know if "official" developers use this channel as a information or judgment source of bugs. As far as I know Ubuntu works on launchpad to administrate bugs.

For this problem I created https://bugs.launchpad.net/ubuntu/+bug/879790 in order to make Ubuntu know that problem. It may be an idea to "make some noise" there in form of clicking on the button "This bug affects...". And - if you feel like - to reproduce some of your statements from this bug-report-page. Hopefully they will take notice finally.

keep fingers crossed
Quesst

Revision history for this message
In , Neven Klacar (nklacar) wrote :

Looks like this will never get solved ;(

If anyone has ideas on how to debug this issue, I have a t60 that I can use.

Revision history for this message
In , Neven Klacar (nklacar) wrote :

(In reply to comment #62)
> Looks like this will never get solved ;(
>
> If anyone has ideas on how to debug this issue, I have a t60 that I can use.

I tried enabling msi on alsa and its alot better. Still fulscreen is not good, but much sounds like 11.04

Add: options snd-hda-intel enable_msi=1" to the bottom of your /etc/modprobe.d/alsa-base file.

I think radeon is somehow not playing nice with msi. If we could disable it it might fix the problem...I tried doing it with echo 0 > msi_bus in the radeon bridge but it wasnt working

Revision history for this message
In , agd5f (agd5f) wrote :

With a new enough kernel, you can disable MSIs on radeon by setting radeon.msi=0 on the kernel command line in grub or when you load the module. You can disable MSIs globally by setting pci=nomsi on the kernel command line in grub.

Revision history for this message
In , agd5f (agd5f) wrote :
Revision history for this message
In , Neven Klacar (nklacar) wrote :

(In reply to comment #65)
> You might also try this patch:
> http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-fixes&id=b7f5b7dec3d539a84734f2bcb7e53fbb1532a40b

I tried to git the 11.10 package from ubuntu and recompile with the change you mentioned in rs600.c file and r100.c . It didnt seem to help. I noticed someone tried disabling MSI so this might not be related to MSI at all...

I was thinking of trying the latest radeon src?

Revision history for this message
In , agd5f (agd5f) wrote :

Has anyone tried messing with the audio or wifi drivers? It's possible the issue is on that side. How about messing with the cpufreq governors? Is it still an issue if you force the cpu power state to performance, etc.?

5 comments hidden view all 104 comments
Revision history for this message
In , Neven Klacar (nklacar) wrote :

The wifi I tried disabling the sound quaility is still bad when doing anything display intensive. I havent tried disabling alsa altogether to see if the wifi is still dropping..

I wanna say when I first come up with MSI fixed version it sounds fine, youtube also sounds normal, but if I make the unity taskbar show up, then it goes into some sort of bad state where sound is bad again..maybe the clock switch in the gpu clock or cpu? Not sure....

I need to do some more experiments, haven't had the time.

4 comments hidden view all 104 comments
Revision history for this message
penalvch (penalvch) wrote :

Øyvind Stegard, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 571770

As well, since you noted this started moving from Karmic to Lucid, a bisect needs to be conducted to find the offending commit. Could you please perform this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: i386 lucid
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

This has been an issue ever since Radeon KMS was introduced, and it is still very much an issue in the most recent Ubuntu versions. I marked is as duplicate of https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/879790

4 comments hidden view all 104 comments
Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

According to bug 38694 there can be problems when changing the number of PCIe lanes. Does disabling that as described there help for this problem?

Revision history for this message
In , Kolin S. Murray (kolinab) wrote :

Hi,

Apologies if this is not strictly on topic regarding fixing this bug - what I'm curious to know is what the 'best case' workaround all of you are using to avoid this problem? I'm open to absolutely any distribution, desktop environment, etc. Just wondering what the best alternative many of you have found to avoid the conflict and maintain the most functionality.

My best case options so far: Ubuntu 10.04 LTS where I don't remember noticing this problem, or even 12.04 in 2D if I could get my volume control buttons to work on my Thinkpad t60.

I'm also playing with arch to see if I can build something usable I like.

Regards,

K

Revision history for this message
In , Jan Kouba (kouba-honza) wrote :

Hi,

I have been able to get around this bug on IBM T60/x1400 running Kubuntu 12.04, by using kwin_gles desktop manager instead of the default one (kwin).

I had problems with sound slowing down and being very choppy when desktop effects were enabled, or when playing full-screen flash videos. I did not notice any problems with wifi. With kwin_gles I have absolutely no sound issues with desktop effects enabled.

How to change the window manager see:
http://weits.blogspot.cz/2012/02/kwin-gles-as-default-window-manager-in.html

I'm not X expert, so please take the following lines as my humble opinion. I belive, that the workaround is caused by the fact, that kwin_gles uses EGL for rendering, while kwin uses GLX. So maybe this bug can be avoided on other distros and window managers by setting them to use EGL instead of GLX.

Revision history for this message
In , Andrey Shamakhov (shamakhov-a) wrote :

Using kwin_gles doesn't make sense on my Asus A8Jr. Sound is crackling still during fullscreen flash video playing and when kwin desktop effects enabled.

Revision history for this message
In , Steffen-schloenvoigt (steffen-schloenvoigt) wrote :

Man, I love you! :)
I was fighting with this bug since - I don't know - and now, finally my laptop is usable again.

I know, using GLES is just a workarround - but at least there is one, now :)

Revision history for this message
In , Vassil Panayotov (vd-panayotov) wrote :

Just for the record I've tried Kubuntu 12.04.02 and the kwin_gles workaround does _not_ work for me unfortunately(T60 w/ X1400) . There are still messages like "CE: hpet increased min_delta_ns to 20113 nsec", and the wireless is very slow. This issue is very frustrating and is the first time when the open source model fails to work for me. I mean this report was filed 3 years ago, affects thousands of people, there is no good workaround and yet no one from the "radeon" developers seems to care.
I wonder if we can raise money and put together a bounty or something...

(posted this on https://bugs.launchpad.net/bugs/879790 24 hours ago but for some reason it's not synchronized yet, so posting it here "manually" too)

Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

This could just as easily be a chipset or sound or wifi issue tiggered by the additional bus activity of KMS.

Revision history for this message
In , Vassil Panayotov (vd-panayotov) wrote :

@Alex Deucher: Yes, the modern operating systems and hardware are complex beasts and I surely understand that some bugs may be hard to track down. The point is however that there wasn't a systematic effort to resolve this particular issue except for some "there is a random problem X described in ticket Y, which may be the reason for your troubles too, so why don't you try the solution proposed there". By the way I tried the change proposed by Michel Dänzer in https://bugs.freedesktop.org/show_bug.cgi?id=38694 , but unfortunately it doesn't seem to help either.
I am clueless about the kernel internals, but the manifestations of this bug seem to be consistent with the hypothesis that there is something wrong with the "radeon" driver. It seems like something locks the system for long periods of time and the other time sensitive modules "freak out". On my laptop the problem became even more pronounced when I swapped the "1440x900" LCD panel with a "1600x1200" one.

Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

(In reply to comment #76)
> @Alex Deucher: Yes, the modern operating systems and hardware are complex
> beasts and I surely understand that some bugs may be hard to track down. The
> point is however that there wasn't a systematic effort to resolve this
> particular issue except for some "there is a random problem X described in
> ticket Y, which may be the reason for your troubles too, so why don't you
> try the solution proposed there". By the way I tried the change proposed by
> Michel Dänzer in https://bugs.freedesktop.org/show_bug.cgi?id=38694 , but
> unfortunately it doesn't seem to help either.

There were several suggestions on this bug, but apparently none of them helped.

> I am clueless about the kernel internals, but the manifestations of this bug
> seem to be consistent with the hypothesis that there is something wrong with
> the "radeon" driver. It seems like something locks the system for long
> periods of time and the other time sensitive modules "freak out". On my
> laptop the problem became even more pronounced when I swapped the "1440x900"
> LCD panel with a "1600x1200" one.

A bigger display means more data is being moved around. It sounds to me like a chipset issue when large amounts of data are being transferred across the bus. KMS uses system memory more readily than UMS did which is likely why the issues shows up with KMS. I don't know of any other options to try in the driver. We don't have these problems with the same radeon chips is other systems. Unfortunately, I'm not a chipset expert so I'm not sure what sort of pci quirks, etc. to try.

It could also be that the there is an issue in the sound or wifi driver which didn't show up as readily when there was less traffic on the bug. As far as I know no one has investigated these avenues very much.

Revision history for this message
In , Tomwallroth (tomwallroth) wrote :

I had all the problems as described by Øyvind Stegard and I have the feeling that it got slightly better after installing the latest available BIOS for my Thinkpad T60 2007-CTO (ATI X1400, iwl3945, snd-hda-intel).

I'm running 32bit Arch with the 3.11.4-1-ARCH Kernel and xf86-video-ati 1:7.2.0-1

I've tried all other options mentioned here, without any sign of improvement. What can I do to further help investigating this problem? Would it be of any help to e.g. study the IRQ settings used in windows?

penalvch (penalvch)
tags: added: regression-release
description: updated
12 comments hidden view all 104 comments
Revision history for this message
penalvch (penalvch) wrote :

Øyvind Stegard, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a terminal, as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux 571770

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.14-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Low
tags: added: needs-kernel-logs needs-upstream-testing
Revision history for this message
Øyvind Stegard (oyvindstegard) wrote : Re: [Bug 571770] Re: Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

This bug is really just bug 879790, set status to duplicate or close.
Either way I will not be able to test, as I gave up on using Linux on
the machine due this problem. And now it is obsolete and dusty.

Revision history for this message
penalvch (penalvch) wrote :

Øyvind Stegard, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571770/comments/90 regarding you are not using Ubuntu with the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

no longer affects: linux (Ubuntu)
affects: xserver-xorg-driver-ati → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: High → Undecided
status: Confirmed → Invalid
Changed in linux (Ubuntu):
importance: Undecided → High
status: Invalid → Confirmed
11 comments hidden view all 104 comments
Revision history for this message
In , mirh (mirh) wrote :

Many of the linked issues report the problem fixed (broadly, by the time of ubuntu 14.04).

Is this still a thing?

penalvch (penalvch)
Changed in linux (Ubuntu):
importance: High → Undecided
status: Confirmed → Invalid
Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

(In reply to mirh from comment #79)
> Is this still a thing?

Let's assume not, thanks for the follow-up.

Changed in linux (Ubuntu):
importance: Undecided → High
status: Invalid → Fix Released
penalvch (penalvch)
no longer affects: linux (Ubuntu)
Changed in linux:
status: New → Invalid
Displaying first 40 and last 40 comments. View all 104 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.