From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: Kernel 2.4.17-32-smp problem
Date: Sun, 24 Mar 2002 20:58:48 -0700 [thread overview]
Message-ID: <20020325035848.477324855@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jeremy Drake <jeremyd@apptechsys.com> of "Sun, 24 Mar 2002 09:33:16 PST." <Pine.LNX.4.33L2.0203240928550.13376-100000@eiger.apptechsys.com>
Jeremy Drake wrote:
> I was running 2.4.17-32-smp before. It just updated a debian package of
> the same kernel version. I had no problems with the old one, other than
> the fact that it seems to ignore cpu0. All processor time goes to cpu1
> and cpu0 gets a ton of idle.
hmm..that fits with the "top" report of 50% idle that I've seen.
We've already got a bug report on this, iirc.
Your observation suggest something wrong with either process scheduling
or process accounting.
And I hope CPU0 isn't completely idle, look at /proc/interrupts.
I know interrupt distribution works.
> When the box crashed both times, I was checking out the cvs tree :)
network/IO intensive load - lots of interrupts...hmm.
grant
next prev parent reply other threads:[~2002-03-25 3:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 4:03 [parisc-linux] Kernel 2.4.17-32-smp problem Jeremy Drake
2002-03-24 8:14 ` [parisc-linux] " Grant Grundler
2002-03-24 17:33 ` Jeremy Drake
2002-03-24 17:33 ` Jeremy Drake
2002-03-25 3:58 ` Grant Grundler [this message]
2002-03-25 7:33 ` Jeremy Drake
2002-03-25 10:42 ` Thibaut VARENE
2002-03-25 17:00 ` Jeremy Drake
2002-03-24 8:14 ` Grant Grundler
2002-03-25 0:33 ` [parisc-linux] " Randolph Chung
2002-03-25 3:01 ` Jeremy Drake
2002-03-25 4:10 ` Grant Grundler
2002-03-25 17:44 ` Jeremy Drake
2002-03-25 18:00 ` Jeremy Drake
2002-03-26 5:26 ` Jeremy Drake
2002-03-25 17:44 ` Jeremy Drake
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=20020325035848.477324855@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=jeremyd@apptechsys.com \
--cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.