Distribution: Debian Unstable Hardware Environment: IBM Thinkpad r50p Software Environment: Problem Description: Sound & Network run fine after fresh boot. After suspending & resuming, sound runs for a short while (~30 secs) and then stops. IRQ 5 no longer increments when sound has stopped. Steps to reproduce: Boot system. Suspend. resume. Play sounds... (using Juk, Xine, whatever).
Created attachment 3257 [details] .config running .config
Created attachment 3258 [details] dmesg output
Created attachment 3259 [details] /proc/interrupts 10 secs apart with sound running With juk playing, IRQ5 doesn't increment (Intel sound chip on IRQ5)
Created attachment 3260 [details] lspci -vv after resuming lspci -vv output from after resuming.
Created attachment 3261 [details] lspci -vv after resume
Have patched kernel 2.6.7 with suggested patch from bug #2643. This apears to have fixed the problem with the ethernet stopping, but has done nothing for the sound.
Seeing as sound was on IRQ5 and the patch for 2643 fixed the ethernet, I added a (big hack here :) call to acpi_pic_sci_set_trigger(5, acpi_sci_flags.trigger); in acpi_pm_finish(u32 state); just after the call to set the IRQ trigger for the acpi irq... Results in (kern.log) Jun 27 21:15:28 ballbreaker kernel: ACPI: IRQ9 SCI: Edge set to Level Trigger. Jun 27 21:15:28 ballbreaker kernel: ACPI: IRQ5 SCI: Edge set to Level Trigger. and then sound works after resume... Obviously not a very good fix as it won't fix anything that uses somethign other than IRQ5. So. What should the correct fix be? Obviously some IRQ's triggers aren't surviving the resume... But why... The timer (IRQ 0) obviously does...
*** This bug has been marked as a duplicate of 2643 ***