IRQ conflicts

IRQ conflicts

[Brian Gerst]

I'm having problems with 2.4.2-pre3 and IRQ conflicts.  Last kernel that
I tried and worked without conflict was 2.4.0-test11.  Here are the
relevant messages that I get:

Linux version 2.4.2-pre3 (root@neriak) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Sat Feb 10 11:13:59 EST 2001
PCI: PCI BIOS revision 2.10 entry at 0xfb4d0, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
Scanning bus 00
Found 00:00 [1106/0597] 000600 00
Found 00:08 [1106/8598] 000604 01
Found 00:38 [1106/0586] 000601 00
Found 00:39 [1106/0571] 000101 00
Found 00:3b [1106/3040] 000604 00
PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class.
Found 00:40 [102b/0519] 000300 00
Found 00:48 [1113/1211] 000200 00
Found 00:50 [10ec/8139] 000200 00
Fixups for bus 00
Scanning behind PCI bridge 00:01.0, config 010100, pass 0
Scanning bus 01
Fixups for bus 01
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Bus scan for 01 returning with max=01
Scanning behind PCI bridge 00:01.0, config 010100, pass 1
Bus scan for 00 returning with max=01
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
Activating ISA DMA hang workarounds.
isapnp: Scanning for Pnp cards...
isapnp: SB audio device quirk - increasing port range
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB32 PnP'
isapnp: Card 'Rockwell K56Flex Plug & Play Modem'
isapnp: 2 Plug & Play cards detected total
DMI 2.1 present.
25 structures occupying 843 bytes.
DMI table at 0x000F0800.
BIOS Vendor: Award Software International, Inc.
BIOS Version: 4.51 PG
BIOS Release: 02/26/99
System Vendor: System Manufacturer.
Product Name: Product Name.
Version SYS-xxxxxx.
Serial Number Serial Number xxxxxx.
Board Vendor: First International Computer, Inc..
Board Name: PA-2013.
Board Version: PCB 2.X.
Asset Tag: Asset Tag Number xxxxxx.
8139too Fast Ethernet driver 0.9.13 loaded
PCI: Found IRQ 11 for device 00:09.0
eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0xc4800000,
00:e0:29:6e:11:da, IRQ 11
PCI: Found IRQ 10 for device 00:0a.0
IRQ routing conflict in pirq table for device 00:0a.0
eth1: RealTek RTL8139 Fast Ethernet at 0xc4802000, 00:48:54:67:17:e9,
IRQ 5
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative SB32 PnP detected
sb: ISAPnP reports 'Creative SB32 PnP' at i/o 0x220, irq 9, dma 1, 5
sb: Interrupt test on IRQ9 failed - Probable IRQ conflict
sb: 1 Soundblaster PnP card(s) found.
ISAPnP reports AWE32 WaveTable at i/o 0x620
<SoundBlaster EMU8000 (RAM2048k)>
Sound: DMA (output) timed out - IRQ/DRQ config error?

00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev
04)
	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: 16 set
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [a0] AGP version 1.0
		Status: RQ=7 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 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 set
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA
[Apollo VP] (rev 47)
	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 set

00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (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: 64 set
	Region 4: I/O ports at e400 [size=16]

00:07.3 PCI bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
(prog-if 00 [Normal decode])
	!!! Header type 00 doesn't match class code 0604

00:08.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W
[Millennium] (rev 01) (prog-if 00 [VGA])
	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 A routed to IRQ 10
	Region 0: Memory at e4000000 (32-bit, non-prefetchable) [size=16K]
	Region 1: Memory at e5000000 (32-bit, prefetchable) [size=8M]
	Expansion ROM at e6000000 [disabled] [size=64K]

00:09.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
(rev 10)
	Subsystem: Accton Technology Corporation: Unknown device 1211
	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 min, 64 max, 64 set
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at e800 [size=256]
	Region 1: Memory at e7000000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME+
		Status: D0 PME-Enable- DSel=0 DScale=0 PME+
	Capabilities: [60] Vital Product Data

00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139
(rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	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 min, 64 max, 64 set
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at ec00 [size=256]
	Region 1: Memory at e7001000 (32-bit, non-prefetchable) [size=256]

           CPU0       
  0:     146319          XT-PIC  timer
  1:        184          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:       1889          XT-PIC  eth1
  9:          0          XT-PIC  soundblaster
 11:        356          XT-PIC  eth0
 12:          0          XT-PIC  PS/2 Mouse
 14:       2026          XT-PIC  ide0
 15:          5          XT-PIC  ide1
NMI:          0 
ERR:          0


PCI bus 01 is an AGP bus, but there is no AGP video card present.  eth1
does function, but the sound card does not.  More information available
on request.

-- 

						Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

IRQ conflicts

[Brian Gerst]

Brian Gerst wrote:
> 
> I'm having problems with 2.4.2-pre3 and IRQ conflicts.  Last kernel that
> I tried and worked without conflict was 2.4.0-test11.  Here are the
> relevant messages that I get:

I enabled more debug messages, so here is the updated messages.  I also
noticed that ACPI is trying to use IRQ 9, which the soundblaster is also
trying to use.

PCI: BIOS32 Service Directory structure at 0xc00fb020
PCI: BIOS32 Service Directory entry at 0xfb4a0
PCI: BIOS probe returned s=00 hw=11 ver=02.10 l=02
PCI: PCI BIOS revision 2.10 entry at 0xfb4d0, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
Scanning bus 00
Found 00:00 [1106/0597] 000600 00
Found 00:08 [1106/8598] 000604 01
Found 00:38 [1106/0586] 000601 00
Found 00:39 [1106/0571] 000101 00
PCI: IDE base address fixup for 00:07.1
Found 00:3b [1106/3040] 000604 00
PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class.
Found 00:40 [102b/0519] 000300 00
Found 00:48 [1113/1211] 000200 00
Found 00:50 [10ec/8139] 000200 00
Fixups for bus 00
PCI: Scanning for ghost devices on bus 0
Scanning behind PCI bridge 00:01.0, config 010100, pass 0
Scanning bus 01
Fixups for bus 01
PCI: Scanning for ghost devices on bus 1
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Bus scan for 01 returning with max=01
Scanning behind PCI bridge 00:01.0, config 010100, pass 1
Bus scan for 00 returning with max=01
PCI: IRQ init
PCI: Interrupt Routing Table found at 0xc00fdec0
00:07 slot=00 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8
00:08 slot=01 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8
00:09 slot=02 0:02/deb8 1:03/deb8 2:05/deb8 3:01/deb8
00:0a slot=03 0:03/deb8 1:05/deb8 2:01/deb8 3:02/deb8
00:0b slot=04 0:05/deb8 1:01/deb8 2:02/deb8 3:03/deb8
00:07 slot=00 0:00/deb8 1:00/deb8 2:00/deb8 3:00/deb8
00:01 slot=00 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
PCI: IRQ fixup
PCI: Allocating resources
PCI: Resource e0000000-e3ffffff (f=1208, d=0, p=0)
PCI: Resource 0000e400-0000e40f (f=101, d=0, p=0)
PCI: Resource e4000000-e4003fff (f=200, d=0, p=0)
PCI: Resource e5000000-e57fffff (f=1208, d=0, p=0)
PCI: Resource 0000e800-0000e8ff (f=101, d=0, p=0)
PCI: Resource e7000000-e70000ff (f=200, d=0, p=0)
PCI: Resource 0000ec00-0000ecff (f=101, d=0, p=0)
PCI: Resource e7001000-e70010ff (f=200, d=0, p=0)
PCI: Sorting device list...
Activating ISA DMA hang workarounds.
isapnp: Scanning for Pnp cards...
isapnp: SB audio device quirk - increasing port range
isapnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB32 PnP'
isapnp: Card 'Rockwell K56Flex Plug & Play Modem'
isapnp: 2 Plug & Play cards detected total
DMI 2.1 present.
25 structures occupying 843 bytes.
DMI table at 0x000F0800.
BIOS Vendor: Award Software International, Inc.
BIOS Version: 4.51 PG
BIOS Release: 02/26/99
System Vendor: System Manufacturer.
Product Name: Product Name.
Version SYS-xxxxxx.
Serial Number Serial Number xxxxxx.
Board Vendor: First International Computer, Inc..
Board Name: PA-2013.
Board Version: PCB 2.X.
Asset Tag: Asset Tag Number xxxxxx.
8139too Fast Ethernet driver 0.9.13 loaded
IRQ for 00:09.0:0 -> PIRQ 02, mask deb8, excl 0c20 -> newirq=11 -> got
IRQ 11
PCI: Found IRQ 11 for device 00:09.0
eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0xc4800000,
00:e0:29:6e:11:da, IRQ 11
IRQ for 00:0a.0:0 -> PIRQ 03, mask deb8, excl 0c20 -> newirq=5 -> got
IRQ 10
PCI: Found IRQ 10 for device 00:0a.0
IRQ routing conflict in pirq table for device 00:0a.0
eth1: RealTek RTL8139 Fast Ethernet at 0xc4802000, 00:48:54:67:17:e9,
IRQ 5
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative SB32 PnP detected
sb: ISAPnP reports 'Creative SB32 PnP' at i/o 0x220, irq 9, dma 1, 5
sb: Interrupt test on IRQ9 failed - Probable IRQ conflict
sb: 1 Soundblaster PnP card(s) found.
ISAPnP reports AWE32 WaveTable at i/o 0x620
<SoundBlaster EMU8000 (RAM2048k)>
ACPI: Core Subsystem version [20010208]
ACPI: SCI (IRQ9) allocation failed
ACPI: Subsystem enable failed
Trying to free free IRQ9

-- 

						Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: IRQ conflicts

[Alan Cox]

> <SoundBlaster EMU8000 (RAM2048k)>
> ACPI: Core Subsystem version [20010208]
> ACPI: SCI (IRQ9) allocation failed
> ACPI: Subsystem enable failed
> Trying to free free IRQ9

That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
good bet it will fix any random irq/driver problem right now


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: IRQ conflicts

[Brian Gerst]

Alan Cox wrote:
> 
> > <SoundBlaster EMU8000 (RAM2048k)>
> > ACPI: Core Subsystem version [20010208]
> > ACPI: SCI (IRQ9) allocation failed
> > ACPI: Subsystem enable failed
> > Trying to free free IRQ9
> 
> That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
> good bet it will fix any random irq/driver problem right now

Looking at this a bit further, I realised that when the sound driver was
compiled in the kernel, it is initialised before ACPI.  The BIOS has
assigned IRQ9 to ACPI, but the PCI code does not know this because of:

PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class. 

The ISAPnP code then assigns IRQ9 to the sound card, causing the ACPI
code to fail to allocate it.  If I compile sound as a module then the
ACPI driver grabs IRQ9 and the sound get IRQ7.

--
					Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: IRQ conflicts

[Andrey Panin]

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Sat, Feb 10, 2001 at 07:06:52PM -0500, Brian Gerst wrote:
> Alan Cox wrote:
> > 
> > > <SoundBlaster EMU8000 (RAM2048k)>
> > > ACPI: Core Subsystem version [20010208]
> > > ACPI: SCI (IRQ9) allocation failed
> > > ACPI: Subsystem enable failed
> > > Trying to free free IRQ9
> > 
> > That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
> > good bet it will fix any random irq/driver problem right now
> 
> Looking at this a bit further, I realised that when the sound driver was
> compiled in the kernel, it is initialised before ACPI.  The BIOS has
> assigned IRQ9 to ACPI, but the PCI code does not know this because of:
> 
> PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class. 
> 
> The ISAPnP code then assigns IRQ9 to the sound card, causing the ACPI
> code to fail to allocate it.  If I compile sound as a module then the
> ACPI driver grabs IRQ9 and the sound get IRQ7.
> 

Hi Brian,

please test this patch with ACPI enabled and sound driver compiled in kernel.
IMHO it should fix this problem.

Best regards.

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: IRQ conflicts

[Andrey Panin]

[-- Attachment #1.1: Type: text/plain, Size: 244 bytes --]


Hi Brian.

I'm sorry, patch itself was not attached in previous post :(

Best regards.

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc

[-- Attachment #1.2: patch-acpiirq --]
[-- Type: text/plain, Size: 1362 bytes --]

--- /linux/arch/i386/kernel/pci-pc.c.orig	Mon Feb 12 02:06:24 2001
+++ /linux/arch/i386/kernel/pci-pc.c	Mon Feb 12 02:08:51 2001
@@ -950,6 +950,26 @@
 	}
 }
 
+static void __init pci_fixup_via_acpi(struct pci_dev *d)
+{
+	/*
+	 * VIA ACPI device: IRQ line in PCI config byte 0x42
+	 */
+	u8 irq;
+	pci_read_config_byte(d, 0x42, &irq);
+	irq &= 0x0f;
+	if (irq && (irq != 2))
+		d->irq = irq;
+}
+
+static void __init pci_fixup_piix4_acpi(struct pci_dev *d)
+{
+	/*
+	 * PIIX4 ACPI device: hardwired IRQ9
+	 */
+	d->irq = 9;
+}
+
 struct pci_fixup pcibios_fixups[] = {
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82451NX,	pci_fixup_i450nx },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82454GX,	pci_fixup_i450gx },
@@ -963,6 +983,9 @@
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_SI,	PCI_DEVICE_ID_SI_5597,		pci_fixup_latency },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_SI,	PCI_DEVICE_ID_SI_5598,		pci_fixup_latency },
 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_VIA,	PCI_DEVICE_ID_VIA_8363_0,	pci_fixup_vt8363 },
+	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_VIA,	PCI_DEVICE_ID_VIA_82C586_3,	pci_fixup_via_acpi },
+	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_VIA,	PCI_DEVICE_ID_VIA_82C686_4,	pci_fixup_via_acpi },
+	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_INTEL,	PCI_DEVICE_ID_INTEL_82371AB_3,	pci_fixup_piix4_acpi },
 	{ 0 }
 };
 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: IRQ conflicts

[Brian Gerst]

Andrey Panin wrote:
> 
> Hi Brian.
> 
> I'm sorry, patch itself was not attached in previous post :(
> 

Yes, this does fix that part of the problem.  There is still the matter
of the class code being wrong but I have ideas on how to fix that.

-- 

						Brian Gerst

IRQ conflicts

[753 user]

I would like to know may I use the same IRQs for more
than one component with 2.4.x?

My first network card use the same IRQ as paralell
port,
and my second card use the same as my USB have.

BX chipset, ne2k-pci driver.

With 2.4.5 I *often* get kernel Oopses with IRQ
routing error messages. This never happend before
and the only one change was a a second network
card inserted into the mobo and changed kernel
from 2.4.3 to 2.4.5.

  0:     389014          XT-PIC  timer
  1:          2          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:         50          XT-PIC  
  5:      27065          XT-PIC  eth0
 10:      75114          XT-PIC  ide2
 11:      24916          XT-PIC  eth1
 12:          0          XT-PIC  EMU10K1
 14:         12          XT-PIC  ide0
NMI:          0 
ERR:          0

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

IRQ conflicts

[753 user]

>With 2.4.5 I *often* get kernel Oopses with IRQ
>routing error messages. This never happend before
>and the only one change was a a second network
>card inserted into the mobo and changed kernel
>from 2.4.3 to 2.4.5.

As as wrote... Here is one of them, getting every 3
hours...

CPU: 0
EIP: 0010:[<c018a302>]
EFLAGS: 00010202
eax: c233cae0   ebx: 00001025   ecx: 00000000   edx:
00001025
esi: c21334a0   edi: c233c380   ebp: 00000060   esp:
c01fdddc
ds: 0018        es: 0018        ss: 0018
Process swapper (pid: 0, stackpage=c01fd000)
Stack: ...
Call Trace: ...
Code: 8b 1b 8b 42 70 83 f8 01 74 0a ff 4a 70 0f 94 c0 84 c0
74 09
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Re: IRQ conflicts

[Alan Cox]

> >With 2.4.5 I *often* get kernel Oopses with IRQ
> >routing error messages. This never happend before
> >and the only one change was a a second network
> >card inserted into the mobo and changed kernel
> >from 2.4.3 to 2.4.5.
> 
> As as wrote... Here is one of them, getting every 3
> hours...

See REPORTING-BUGS and include the call trace details and ksymoops data