Screaming Interrupt [Was: Post-logoff sound problems]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-------- Original Message --------
Subject: 	Post-logoff sound problems
Date: 	Sun, 26 Sep 2004 16:27:34 -0400
From: 	Paul Kopacz <pkopacz@xxxxxxxxxxxx>
Reply-To: 	For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
To: 	fedora-list@xxxxxxxxxx



Hi Everybody,

Been trying to find a solution to this for a while. Using FC2 with a KDE desktop. My sound works fine the first time I log in. Upon subsequent logins, aRTs is running but does not accept sound to play (i.e. the play button is pressed but nothing is happening). If using ALSA to play sound directly (e.g. using XMMS and the ALSA plugin), it is trivial to make the sound skip, where on the first login it was difficult. When I logout, I get this from syslog:

Sep 26 15:39:22 Berdoo kernel: irq 11: nobody cared! (screaming interrupt?)
Sep 26 15:39:22 Berdoo kernel: irq 11: Please try booting with acpi=off and report a bug
Sep 26 15:39:22 Berdoo kernel: Stack pointer is garbage, not printing trace
Sep 26 15:39:22 Berdoo kernel: handlers:
Sep 26 15:39:22 Berdoo kernel: [<42db33e1>] (snd_audiopci_interrupt+0x0/0x16a [snd_ens1371])
Sep 26 15:39:22 Berdoo kernel: Disabling IRQ #11


I would be infinitely surprised if this was not related :)

I did boot with acpi=off (or at least I attempted to. I put acpi=off at the end of the kernel command line in GRUB. That should do it, right?) but the same message came up.

I saw a similar bug at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126322 that was apparantly fixed with a new kernel. I am running kernel-2.6.8-1.521 updated via yum. The original kernel had the same problem.

Any help would be appreciated.  Thanks.

Paul Kopacz


-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list



I have attempted booting with acpi=off and pci=noacpi as well as changing just about everything in the BIOS that seems in any way related. There does not seem to be a way to turn off ACPI in the BIOS (No explicit ACPI = OFF setting, though I have turned off all power management options). Should I try building a non ACPI enabled kernel?

I have also noticed that this problem happens when I _logoff_ KDE. If I just go and kill the X process (which has the effect of logging out the user, just not as 'cleanly'), then everything is fine. Something that KDE is doing upon logoff is causing this problem. (I'm not saying it's a KDE bug, since KDE does not have the power to unmap an interrupt, as that is what seems to be happening).

Here is some /proc/interrupts output for those interested.

After the computer is booted up but before the sound stuff is loaded:
         CPU0
 0:     133910          XT-PIC  timer
 1:        187          XT-PIC  i8042
 2:          0          XT-PIC  cascade
 8:          1          XT-PIC  rtc
 9:          0          XT-PIC  acpi
10:         41          XT-PIC  eth0
11:       3181          XT-PIC  r128@PCI:1:0:0
12:         82          XT-PIC  uhci_hcd, uhci_hcd, uhci_hcd
14:       8766          XT-PIC  ide0
15:        957          XT-PIC  ide1
NMI:          0
ERR:          0

After the first login (sound stuff is loaded):

         CPU0
 0:     176109          XT-PIC  timer
 1:        312          XT-PIC  i8042
 2:          0          XT-PIC  cascade
 8:          1          XT-PIC  rtc
 9:          0          XT-PIC  acpi
10:         41          XT-PIC  eth0
11:       3771          XT-PIC  r128@PCI:1:0:0, Ensoniq AudioPCI
12:         82          XT-PIC  uhci_hcd, uhci_hcd, uhci_hcd
14:      10755          XT-PIC  ide0
15:       1066          XT-PIC  ide1
NMI:          0
ERR:          0

The soundcard and vid card are sharing Interrupt 11, no problem, right?

After logout:
         CPU0
 0:     305703          XT-PIC  timer
 1:        399          XT-PIC  i8042
 2:          0          XT-PIC  cascade
 8:          1          XT-PIC  rtc
 9:          0          XT-PIC  acpi
10:       2099          XT-PIC  eth0
11:     200000          XT-PIC  Ensoniq AudioPCI, r128@PCI:1:0:0
12:       6313          XT-PIC  uhci_hcd, uhci_hcd, uhci_hcd
14:      11547          XT-PIC  ide0
15:       8051          XT-PIC  ide1
NMI:          0
ERR:          0

Now the soundcard and vid card have switched places under Int 11, and the interrupt count has gone up 'significantly'

I don't know enough to interpret a very verbose lspci dump, but if you do:

00:00.0 Host bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266] (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 8064
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-
Latency: 0
Region 0: Memory at f8000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
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-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: f3000000-f3dfffff
Prefetchable memory behind bridge: f3f00000-f7ffffff
Expansion ROM at 0000d000 [disabled] [size=4K]
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:0d.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08)
Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (3000ns min, 32000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at b800
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-


00:0e.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
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-
Latency: 32 (2500ns min, 2500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at b400
Region 1: Memory at f2800000 (32-bit, non-prefetchable) [size=128]
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-


00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
Subsystem: Asustek Computer, Inc. VT8233A
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-
Latency: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
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-
Latency: 32
Region 4: I/O ports at b000 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 18) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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-
Latency: 32, Cache Line Size 08
Interrupt: pin D routed to IRQ 12
Region 4: I/O ports at a800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 18) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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-
Latency: 32, Cache Line Size 08
Interrupt: pin D routed to IRQ 12
Region 4: I/O ports at a400 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 18) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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-
Latency: 32, Cache Line Size 08
Interrupt: pin D routed to IRQ 12
Region 4: I/O ports at a000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
Subsystem: PC Partner Limited: Unknown device 7106
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-
Latency: 64 (2000ns min), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f4000000 (32-bit, prefetchable) [size=f3fe0000]
Region 1: I/O ports at d800 [size=256]
Region 2: Memory at f3000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at 00020000 [disabled]
Capabilities: [50] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1
Capabilities: [5c] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-



This is before the problem happens. After, the output is the same, except that the sound card (at 00:0d.0), the line


Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-

Now reads:

Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort+ >SERR- <PERR-

(The MAbort has switched from - to +)

Again, the relevant portion of /var/log/messages:

Sep 29 07:25:30 Berdoo gdm(pam_unix)[2692]: session closed for user paul
Sep 29 07:25:32 Berdoo kernel: irq 11: nobody cared! (screaming interrupt?)
Sep 29 07:25:32 Berdoo kernel: irq 11: Please try booting with acpi=off and report a bug
Sep 29 07:25:32 Berdoo kernel: Stack pointer is garbage, not printing trace
Sep 29 07:25:32 Berdoo kernel: handlers:
Sep 29 07:25:32 Berdoo kernel: [<42db63e1>] (snd_audiopci_interrupt+0x0/0x16a [snd_ens1371])
Sep 29 07:25:32 Berdoo kernel: Disabling IRQ #11
Sep 29 07:25:32 Berdoo kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Sep 29 07:25:32 Berdoo kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Sep 29 07:25:32 Berdoo kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode



I don't know what to make of all this, and I don't know what else to try. The Screaming Interrupt problems I have seen discussed online are very short on solutions. Should I maybe try the kernel list?


Thanks for your time.

Sincerely,

Paul Kopacz

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux