From: "JaniD++" <djani22@dynamicweb.hu>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
Date: Thu, 1 Dec 2005 00:25:42 +0100 [thread overview]
Message-ID: <042101c5f605$6c6e6250$0400a8c0@dcccs> (raw)
In-Reply-To: Pine.LNX.4.61.0511301835270.26040@yvahk01.tjqt.qr
Hi,
----- Original Message -----
From: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
To: "Carlos Martín" <carlosmn@gmail.com>
Cc: "JaniD++" <djani22@dynamicweb.hu>; <linux-kernel@vger.kernel.org>;
"Denis Vlasenko" <vda@ilport.com.ua>
Sent: Wednesday, November 30, 2005 6:35 PM
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
> >> > *7)
> >> > Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKD]
(IRQs
> >> > *7)
> >> > Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKE]
(IRQs 3
> >> > 4 5 6 7 10 11 12 14 15) *0, disabled.
> >> > Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKF]
(IRQs 3
> >> > 4 5 6 7 10 11 12 14 15) *0, disabled.
> >> > Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKG]
(IRQs 3
> >> > 4 5 6 7 10 11 12 14 15) *0, disabled.
> >> > Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKH]
(IRQs 3
> >> > 4 5 6 7 *10 11 12 14 15)
> >> >
> >> > This is normal? :-)
> >>
> >> I do not understand your question
> >
> >To answer the question, yes, it is perfectly normal to see that.
> >That's just the kernel describing how the PCI IRQs are set up. You
> >have nothing to worry about.
>
> I think it's the "disabled" that worries.
No, i worried about the " (IRQs *7)" format.
I never seen this before....
I searching the bottleneck of my system, and simply found these lines.
I have another question:
CPU0 CPU1 CPU2 CPU3
0: 112 0 0 12095059 IO-APIC-edge timer
8: 0 0 0 2005 IO-APIC-edge rtc
9: 0 0 0 0 IO-APIC-level acpi
14: 0 0 0 1922693 IO-APIC-edge ide0
169: 0 0 0 0 IO-APIC-level
uhci_hcd:usb2
177: 0 0 0 0 IO-APIC-level
uhci_hcd:usb3
185: 0 0 0 0 IO-APIC-level
uhci_hcd:usb4
193: 0 0 0 0 IO-APIC-level
ehci_hcd:usb1
209: 0 0 0 204795144 IO-APIC-level eth0
217: 0 0 0 424538586 IO-APIC-level eth1
NMI: 0 0 0 0
LOC: 12095010 12095009 12094905 12094904
ERR: 0
MIS: 0
How can i avoid this?
(all irq on CPU 3)
The echo /proc/irq/#smp_affinity # >smp_affinity
Has no effect. :-(
I tried it with kernel irq load balancing is on and off.
But nothing is changed. :(
Thanks
Janos
>
>
>
> Jan Engelhardt
> --
> | Alphagate Systems, http://alphagate.hopto.org/
> | jengelh's site, http://jengelh.hopto.org/
> -
> 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/
next prev parent reply other threads:[~2005-11-30 23:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 3:23 PC speaker beeping on high CPU loads on an nForce2 Martin Drab
2005-11-27 3:31 ` Petr Vandrovec
2005-11-27 13:39 ` Martin Drab
2005-11-28 15:50 ` Jan Engelhardt
2005-11-28 16:05 ` ACPI: PCI Interrupt Link [LNKA] (IRQs *7) JaniD++
2005-11-29 8:15 ` Denis Vlasenko
2005-11-29 15:36 ` Carlos Martín
2005-11-30 17:35 ` Jan Engelhardt
2005-11-30 23:25 ` JaniD++ [this message]
2005-11-30 23:18 ` JaniD++
2005-11-30 23:14 ` JaniD++
2005-11-27 6:11 ` PC speaker beeping on high CPU loads on an nForce2 Gene Heskett
2005-11-27 14:34 ` Ivan Yosifov
2005-11-27 17:56 ` Martin Drab
2005-11-27 18:33 ` Willy Tarreau
2005-11-27 21:38 ` Martin Drab
2005-11-27 19:10 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 8:22 ACPI: PCI Interrupt Link [LNKA] (IRQs *7) Brown, Len
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='042101c5f605$6c6e6250$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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