RE: 2.5.xx ACPI/Sb16 IRQ conflict

RE: 2.5.xx ACPI/Sb16 IRQ conflict

[Grover, Andrew]

> From: Shawn Starr [mailto:shawn.starr@datawire.net] 
> 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. 

Hmmm, yes.

> >ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5

There should have been a previous line about LNKD, listing possible
interrupts for it -- what did that line say?

Clearly, either we need another IRQ for LNKD or we PnPISA needs to
assign a different IRQ - some coordination is needed here.

Regards -- Andy

Re: 2.5.xx ACPI/Sb16 IRQ conflict

[Adam Belay]

On Tue, Feb 18, 2003 at 09:42:10AM -0800, Grover, Andrew wrote:
> > From: Shawn Starr [mailto:shawn.starr@datawire.net] 
> > 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.
>
> Hmmm, yes.
>
> > >ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
>
> There should have been a previous line about LNKD, listing possible
> interrupts for it -- what did that line say?

On my copy of Shawn's dmesg I see the following:

ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [PIN1] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PIN2] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIN3] (IRQs 3 4 5 6 7 9 10 11 12 14 15, disabled)
ACPI: PCI Interrupt Link [PIN4] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)

ACPI: PCI Interrupt Link [PIN3] enabled at IRQ 5


> 
> Clearly, either we need another IRQ for LNKD or we PnPISA needs to
> assign a different IRQ - some coordination is needed here.

Agreed, in this particular case there are no available irqs for PnPISA to
assign because it isn't able to share irqs.  Here is some aditional
information about the ISAPnP device that is using irq 5.

7 is used by the parport
10 and 11 are used by pci devices
5 is clear but only with pci=noacpi

ISAPnP Based Sound Blaster Card

sh-2.05a$ cat possible
Dependent: 01 - Priority preferred
   port 0x220-0x220, align 0x0, size 0x10, 16-bit address decoding
   port 0x330-0x330, align 0x0, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5 High-Edge
   dma 1 8-bit byte-count compatible
   dma 5 16-bit word-count compatible
Dependent: 02 - Priority acceptable
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 03 - Priority acceptable
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 04 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 05 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
Dependent: 06 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
Dependent: 07 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   irq 5,7,10,11 High-Edge
   dma 0,1,3 8-bit byte-count compatible

How would you suggest PnP and PCI coordinate this?

Thanks,

Adam

Re: 2.5.xx ACPI/Sb16 IRQ conflict

[Simone Piunno]

On Tue, Feb 18, 2003 at 10:42:54PM +0000, Adam Belay wrote:

> > > From: Shawn Starr [mailto:shawn.starr@datawire.net] 
> > > I can confirm this with 2.5.61 and my SB16AWE card. There

> > There should have been a previous line about LNKD, listing possible
> > interrupts for it -- what did that line say?
> 
> On my copy of Shawn's dmesg I see the following:

I'd like to help with my sb16, bu neither OSS nor ALSA do compile on
2.5.62 :(

sound/oss/sb_card.c: In function `activate_dev':
sound/oss/sb_card.c:744: structure has no member named `active'
sound/oss/sb_card.c:747: structure has no member named `activate'
sound/oss/sb_card.c:750: structure has no member named `deactivate'
[...]

sound/isa/sb/sb16.c: In function `snd_sb16_isapnp':
sound/isa/sb/sb16.c:279: warning: implicit declaration of function
`isapnp_find_dev'
sound/isa/sb/sb16.c:279: warning: assignment makes pointer from integer
without a cast
sound/isa/sb/sb16.c:280: structure has no member named `active'
sound/isa/sb/sb16.c:293: structure has no member named `prepare'
[...]

Regards,
Simone

-- 
 Simone Piunno -- http://members.ferrara.linux.it/pioppo 
.-------  Adde parvum parvo magnus acervus erit  -------.
 Ferrara Linux Users Group - http://www.ferrara.linux.it 
 Deep Space 6, IPv6 on Linux - http://www.deepspace6.net 
 GNU Mailman, Mailing List Manager - http://www.list.org 
`-------------------------------------------------------'

RE: 2.5.xx ACPI/Sb16 IRQ conflict

[Yu, Luming]

Did you try disabling Pnp BIOS and enabling ACPI in kernel?
If yes, please do cat  /proc/acpi/dsdt  > dsdt.dat and send it to me. 
And I need the outputs of  "lspci -vv" and "cat /proc/interrupts".
(Dmesg of problematic kernel is also needed)

Thanks,
Luming

-----Original Message-----
From: Adam Belay [mailto:ambx1@neo.rr.com]
Sent: 2003?2?19? 6:43
To: Grover, Andrew; Shawn Starr; LinuxKernelMailingList
Cc: Simone Piunno; Grover@unaropia
Subject: Re: 2.5.xx ACPI/Sb16 IRQ conflict
Importance: High


On Tue, Feb 18, 2003 at 09:42:10AM -0800, Grover, Andrew wrote:
> > From: Shawn Starr [mailto:shawn.starr@datawire.net] 
> > 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.
>
> Hmmm, yes.
>
> > >ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
>
> There should have been a previous line about LNKD, listing possible
> interrupts for it -- what did that line say?

On my copy of Shawn's dmesg I see the following:

ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [PIN1] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PIN2] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PIN3] (IRQs 3 4 5 6 7 9 10 11 12 14 15, disabled)
ACPI: PCI Interrupt Link [PIN4] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)

ACPI: PCI Interrupt Link [PIN3] enabled at IRQ 5


> 
> Clearly, either we need another IRQ for LNKD or we PnPISA needs to
> assign a different IRQ - some coordination is needed here.

Agreed, in this particular case there are no available irqs for PnPISA to
assign because it isn't able to share irqs.  Here is some aditional
information about the ISAPnP device that is using irq 5.

7 is used by the parport
10 and 11 are used by pci devices
5 is clear but only with pci=noacpi

ISAPnP Based Sound Blaster Card

sh-2.05a$ cat possible
Dependent: 01 - Priority preferred
   port 0x220-0x220, align 0x0, size 0x10, 16-bit address decoding
   port 0x330-0x330, align 0x0, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5 High-Edge
   dma 1 8-bit byte-count compatible
   dma 5 16-bit word-count compatible
Dependent: 02 - Priority acceptable
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 03 - Priority acceptable
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 04 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
   dma 5,6,7 16-bit word-count compatible
Dependent: 05 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
Dependent: 06 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   port 0x300-0x330, align 0x2f, size 0x2, 16-bit address decoding
   irq 5,7,10 High-Edge
   dma 0,1,3 8-bit byte-count compatible
Dependent: 07 - Priority functional
   port 0x220-0x280, align 0x1f, size 0x10, 16-bit address decoding
   irq 5,7,10,11 High-Edge
   dma 0,1,3 8-bit byte-count compatible

How would you suggest PnP and PCI coordinate this?

Thanks,

Adam

Re: 2.5.xx ACPI/Sb16 IRQ conflict

[Shawn Starr]

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