linux-kernel - Re: top displaying 50% si time and 50% idle on idle machine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1b270aae0609110449m2f71495cna78a6cb17e7ca649@mail.gmail.com>
Date:	Mon, 11 Sep 2006 13:49:57 +0200
From:	"Metathronius Galabant" <m.galabant@...glemail.com>
To:	"Pavel Machek" <pavel@...e.cz>
Cc:	"Andrew Morton" <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: top displaying 50% si time and 50% idle on idle machine

> >>>>Cpu(s):  0.0% us,  0.0% sy,  0.0% ni, 50.0% id,  0.0%
> >>>>wa,  0.0% hi, 50.0%si
>
> >> BTW what means si? (interrupt service time? google
> >> didn't find anything)
>
> > 'soft interrupt' probably. try disconnecting network.
>
> The cause has been found. The timer of that machine is seriously
> broken, 1 second is approximately 500ms long.
> It is a HP DL360 G4 and I configured the kernel without ACPI or
> similar. Maybe there are some strange BIOS power management schemes
> active. I will look deeper into the problem and report back.
> A broken timer is _very_ strange to me (I didn't encounter that in the
> last 12 years w/ custom kernels).

Power management was completely switched off, so that was not the cause.
Instead, please have a look the this dmesg outputs:

not working (no ACPI):

ENABLING IO-APIC IRQs
unknown bus type 32. (repeated MULTIPLE TIMES!)
..TIMER: vector=0x31 apic1=-1 pin1=-1 apic2=-1 pin2=-1
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... works.

working (ACPI + processor support):

ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1

Can this be considered as a kernel-bug?

Thanks for the help,
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/