From: Shawn Starr <shawn.starr@datawire.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Simone Piunno <pioppo@ferrara.linux.it>,
Grover@unaropia, Andrew <andrew.grover@intel.com>,
Adam Belay <ambx1@neo.rr.com>
Subject: Re: 2.5.xx ACPI/Sb16 IRQ conflict
Date: Mon, 17 Feb 2003 09:06:33 -0500 [thread overview]
Message-ID: <200302170906.33198.shawn.starr@datawire.net> (raw)
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
next reply other threads:[~2003-02-17 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 14:06 Shawn Starr [this message]
2003-02-18 17:42 Grover, Andrew
2003-02-18 22:42 ` Adam Belay
2003-02-19 11:41 ` Simone Piunno
2003-04-08 8:10 Yu, Luming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200302170906.33198.shawn.starr@datawire.net \
--to=shawn.starr@datawire.net \
--cc=Grover@unaropia \
--cc=ambx1@neo.rr.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pioppo@ferrara.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®