From: rob koendering <susegebr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernels 2.6.29.rc3 2.1 3.1 4.1 5.1 6.1 7.1 and rc4 8.1 Is ACPI broken ???????
Date: Wed, 11 Feb 2009 18:25:34 -0400 [thread overview]
Message-ID: <e63fe7530902111425i68e8d139v8cc90289cd73331f@mail.gmail.com> (raw)
hi all
the second posting went wrong due tot gmail problem (network)
this is /proc/interrupts
did the following run with full acpi
CPU0 CPU1 CPU2 CPU3
0: 97 0 0 0 IO-APIC-edge timer
1: 7310 0 0 0 IO-APIC-edge i8042
7: 1 0 0 0 IO-APIC-edge
8: 1 0 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-fasteoi acpi
12: 115 36083 0 0 IO-APIC-edge i8042
14: 8029 0 0 0 IO-APIC-edge pata_amd
15: 0 0 0 0 IO-APIC-edge pata_amd
16: 94270 0 0 0 IO-APIC-fasteoi
sym53c8xx, nvidia
17: 13352 0 0 0 IO-APIC-fasteoi
0000:02:07.0
19: 2 0 0 0 IO-APIC-fasteoi ohci1394
20: 108 0 15721 0 IO-APIC-fasteoi
ohci_hcd:usb1
21: 190 0 0 4807 IO-APIC-fasteoi sata_nv
22: 76802 0 0 0 IO-APIC-fasteoi
sata_nv, HDA Intel
23: 306 3394 0 0 IO-APIC-fasteoi
sata_nv, ehci_hcd:usb2
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 386083 362373 201504 188108 Local timer interrupts
RES: 5424 3506 2743 2027 Rescheduling interrupts
CAL: 2916 3637 5086 5499 Function call interrupts
TLB: 1013 2101 1904 2128 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
SPU: 0 0 0 0 Spurious interrupts
ERR: 1
MIS: 0
then run with no acpi
CPU0 CPU1 CPU2 CPU3
0: 88 0 0 0 IO-APIC-edge timer
1: 16 0 0 0 IO-APIC-edge i8042
2: 0 0 0 0 XT-PIC-XT cascade
5: 56805 0 0 0 IO-APIC-fasteoi
sata_nv, HDA Intel
7: 3 0 0 0 IO-APIC-fasteoi
sata_nv, ohci1394
8: 1 0 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-edge acpi
10: 299 5730 0 0 IO-APIC-fasteoi
sata_nv, ohci_hcd:usb1, nvidia
11: 588 0 0 1174 IO-APIC-fasteoi
sym53c8xx, ehci_hcd:usb2, 0000:02:07.0
12: 115 0 3843 0 IO-APIC-edge i8042
14: 684 0 0 0 IO-APIC-edge pata_amd
15: 0 0 0 0 IO-APIC-edge pata_amd
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 30438 23491 22784 25051 Local timer interrupts
RES: 1618 802 664 743 Rescheduling interrupts
CAL: 3828 1716 5318 5331 Function call interrupts
TLB: 598 737 659 927 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
SPU: 0 0 0 0 Spurious interrupts
ERR: 1
MIS: 0
in both cases irq-balancer is running
see the difference in IO-APIC-edge i8042
This is a raid 0 system
in the acpi run irq 22 23 is the raid array
and in the no acpi run irq 5 7 is the raid array
all togethher the no acpi run gives a more equal load on the 4 cpu's
as the acpi run gives 0 60 to 90 % load on cpu 0 the other cpu's not
more then 4 to 10 percent with intervals
hope this gives you more info in what i mean
2.6.27 kernels acted more like the no acpi setting.
and no warning on the acpi tables in the bios
--
Robert Koendering
Willemstad
Curacao
next reply other threads:[~2009-02-11 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 22:25 rob koendering [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 20:02 rob koendering
2009-02-11 20:47 ` Len Brown
2009-02-11 21:42 ` Rafael J. Wysocki
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=e63fe7530902111425i68e8d139v8cc90289cd73331f@mail.gmail.com \
--to=susegebr@gmail.com \
--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
all inboxes | Powered by JetHome®