Bug 16487 - Thinkpad r51e sound no longer working in 2.6.34
Thinkpad r51e sound no longer working in 2.6.34
Status: RESOLVED OBSOLETE
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA)
All Linux
: P1 normal
Assigned To: Jaroslav Kysela
:
Depends on:
Blocks: 15310
  Show dependency treegraph
 
Reported: 2010-08-01 07:24 UTC by Tom Stellard
Modified: 2012-08-09 15:13 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.34
Tree: Mainline
Regression: Yes


Attachments
dmesg log booting 2.6.34 without pci=noacpi (39.28 KB, text/plain)
2010-08-01 07:24 UTC, Tom Stellard
Details
dmesg log booting 2.6.34 with pci=noacpi after sound stops working (26.21 KB, text/plain)
2010-08-01 07:27 UTC, Tom Stellard
Details
lspci -v (6.53 KB, text/plain)
2010-08-01 07:28 UTC, Tom Stellard
Details

Description Tom Stellard 2010-08-01 07:24:54 UTC
Created attachment 27309 [details]
dmesg log booting 2.6.34 without pci=noacpi

I have a Thinkpad r51e and starting with this commit (which is necessary for my gpu to work see bug 15626), my audio no longer works unless I boot with pci=noacpi:  

commit c414a117c6094c3f86b533f97beaf45ef9075f03
Author: Alex Deucher <alexdeucher@gmail.com>
Date:   Tue Mar 30 17:22:32 2010 -0400

    drm/radeon/kms: disable MSI on IGP chips
    
    Doesn't seem to work reliably and the pci quirks don't
    always work.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

If I boot with pci=noacpi, the audio works at first, but it usually stops working after running a few programs that use sound.  When the audio stops working, this message appears in my dmesg log:

ALSA sound/pci/atiixp.c:690: atiixp: XRUN detected (DMA 0)
Comment 1 Tom Stellard 2010-08-01 07:27:15 UTC
Created attachment 27310 [details]
dmesg log booting 2.6.34 with pci=noacpi after sound stops working
Comment 2 Tom Stellard 2010-08-01 07:28:22 UTC
Created attachment 27311 [details]
lspci -v
Comment 3 Rafael J. Wysocki 2010-08-03 09:15:28 UTC
Did you try 2.6.35?
Comment 4 Tom Stellard 2010-09-14 07:04:14 UTC
This is still an issue in 2.6.35.
Comment 5 Alan 2012-06-14 17:26:32 UTC
Is this still present in  modern kernels ?

Note You need to log in before you can comment on or make changes to this bug.