Well, it didn't break anything, but it didn't fix my no-sound after suspend
problem.
Without your patch, sound on my dell inspiron 3500 laptop works fine until
the first APM suspend and resume cycle, after which noatun under KDE will
block indefinitely trying to write sound and trying sound from the command
line (no X/KDE running) can get a little sound out sometimes, but it loops
endlessly with warnings printing to the console about an IRQ problem. To get
sound working again, I have to power the laptop off and back on.
I just applied the patch against 2.5.0 (with the
don't-eat-your-filesystem-on-shutdown patch as well: hey, it's 2.5, it's
supposed to do that, isn't it?) and it made no noticeable difference.
lspci produces the same output before and after APM suspend. It's a strange
chipset, but it's using the ad1848 sound driver:
lspci -s 01:00.1 -v -v
01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV
Audio] (rev 12)
Subsystem: Dell Computer Corporation MagicMedia 256AV Audio Device on
Colorado Inspiron
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B+
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 11
Region 0: Memory at fe000000 (32-bit, prefetchable) [size=4M]
Region 1: Memory at fe700000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Any clues?
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/