I can confirm this with 2.5.61 and my SB16AWE card. There seems to be a bug
when PCI interrupts are set by ACPI on a IBM 300PL 6892-N2U.
Also, the IBM BIOS's PnP for OS is enabled.
When the PnP BIOS is disabled and pci=noacpi is NOT used. There are no
conflicts. When PnP BIOS is enabled and we don't set pci=noacpi we get
conflicts with IRQs.
We might need a workaround or is this a bug in IBM's ACPI implimentation?
Shawn.
>List: linux-kernel
>Subject: 2.5.42 ACPI/Sb16 IRQ conflict
From: Simone Piunno <pioppo () ferrara ! linux ! it>
>Date: 2002-10-16 20:29:08
>Hi,
>I'm trying 2.5.42 compiled with ACPI and OSS ISA-Pnp Soundblaster 16.
>When playing audio, the sound is heavily chopped.
>dmesg says:
>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
>isapnp: Scanning for PnP cards...
>isapnp: SB audio device quirk - increasing port range
>isapnp: Card 'Creative SB16 PnP'
>isapnp: 1 Plug & Play card detected total
>ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
>ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
>[-cut-]
>Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
>sb: Creative SB16 PnP detected
>sb: ISAPnP reports 'Creative SB16 PnP' at i/o 0x220, irq 5, dma 1, 5
>SB 4.13 detected OK (220)
>sb: Interrupt test on IRQ5 failed - Probable IRQ conflict
>Sound Blaster 16 (4.13)> at 0x220 irq 5 dma 1,5
><Sound Blaster 16> at 0x330 irq 5 dma 0,0
>sb: 1 Soundblaster PnP card(s) found.
>Motherboard is Asus P5A.
>Audio is compiled as a module
>isapnp and ACPI are statically linked
>With ALSA was even worse (no output at all).
>After appending "pci=noapci" into lilo.conf, now OSS happily works
>again without problems. I haven't tried yet if ALSA too benefits
>from pci=noapci.
>Feel free to contact me if you need more info.
>Regards,
>Simone
-- Shawn Starr UNIX Systems Administrator, Operations Datawire Communication Networks Inc. 10 Carlson Court, Suite 300 Toronto, ON, M9W 6L2 T: 416-213-2001 ext 179 F: 416-213-2008 shawn.starr@datawire.net "The power to Transact" - http://www.datawire.net- 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/
This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:17 EST