| View previous topic :: View next topic |
| Author |
Message |
XenoTerraCide
Veteran
Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA
|
 Posted: Thu Feb 09, 2006 5:28 pm Post subject: Very High IRQ numbers on devices |
 |
|
I was following a thread on how to speed up the system via the kernel, and I inserted the option's that it suggested. unfortunately I haven't figured out which thread this is yet today. I noticed now that I have several IRQs that are really High and I don't understand why or if this is really a good thing.
| Code: | lspci -v
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog -if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Unknown device 5700
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 177
Memory at ec000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog -if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd. Unknown device 5700
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 193
Memory at ec001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog -if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Unknown device 5700
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
Memory at ec004000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port
Capabilities: [80] Power Management version 2
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
Subsystem: Micro-Star International Co., Ltd. Unknown device 570c
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 177
Memory at ec005000 (32-bit, non-prefetchable) [size=4K]
I/O ports at e000 [size=8]
Capabilities: [44] Power Management version 2
|
this is just some of it. I just notice a USB and the ethernet are sharing an IRQ. I think this is do to the | Code: | | [*] Message Signaled Interrupts (MSI and MSI-X) |
module in the kernel as it was one of the few things I added. It may not be though, if it isn't does anyone have an Idea what it is? Is this a good thing? how can it be? why did they get so high?
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help. |
|
| Back to top |
|
 |
Blood Fluke
Apprentice
Joined: 15 Sep 2005
Posts: 224
|
| Posted: Thu Feb 09, 2006 8:05 pm Post subject: |
|
|
I'm not sure, but I think those really high IRQs are just an ACPI issue.
ACPI hijacks I/O at the hardware level, sooo... |
|
| Back to top |
|
|
XenoTerraCide
Veteran
Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA
|
| Posted: Thu Feb 09, 2006 8:08 pm Post subject: |
|
|
they weren't high until I changed stuff, they were normal. could it have anything to do with stack size or pci IDE I/O sharing (or something like that.
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help. |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Thu Feb 09, 2006 8:32 pm Post subject: Re: Very High IRQ numbers on devices |
|
|
| XenoTerraCide wrote: | | I noticed now that I have several IRQs that are really High and I don't understand why or if this is really a good thing. |
It's not a problem, interrupts routed through an I/O APIC can have high numbers, while interrupts routed through legacy PIC have numbers less than 16. If the devices work, then the interrupts are routed properly, no need to worry about that.
| XenoTerraCide wrote: | I think this is do to the | Code: | | [*] Message Signaled Interrupts (MSI and MSI-X) |
module in the kernel as it was one of the few things I added. |
No, it's just that you enabled the APIC, and XT-PIC and I/O APIC interrupt numbers are different. The devices you're showing can't use message signaled interrupts anyways. If they could, they would have the MSI capability, like this one:
| Code: | 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 08
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [40] 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-
Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable+
Address: 00000000fee00000 Data: 40b9
Capabilities: [58] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot+) IRQ 0
... |
|
|
| Back to top |
|
|
XenoTerraCide
Veteran
Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA
|
| Posted: Thu Feb 09, 2006 8:38 pm Post subject: |
|
|
hmm I'm not showing any devices on lspci that can use them then. should I keep it in the kernel?
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
