From: Michael Renner <michael.renner@geizhals.at>
To: linux-kernel@vger.kernel.org
Subject: Re: faulty oom-killer on amd64?
Date: Thu, 24 Nov 2005 17:27:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20051124T182006-575@post.gmane.org> (raw)
In-Reply-To: loom.20051124T013917-518@post.gmane.org
Michael Renner <michael.renner <at> geizhals.at> writes:
> On the 16 processor machine I get CPU lockups with identical traces which can
> be seen at http://666kb.com/i/10yov42ydfdog.jpg and
> http://666kb.com/i/10yom358azw8w.jpg (this was tested with 2.6.14 and
> 2.6.15-rc2 respectively).
Ok, retried this with burnMMX on the "large" box, apparently the killer works in
some cases. (It killed the offending burnMMX processes after stalling for a
minute or two, but I guess I can't blame the scheduler when it hast to handle
more than 1000 running processes).
Still, the situation isn't favorable with the other workloads which lead to
lockups.
best regards,
Michael Renner
prev parent reply other threads:[~2005-11-24 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 1:26 faulty oom-killer on amd64? Michael Renner
2005-11-24 17:27 ` Michael Renner [this message]
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=loom.20051124T182006-575@post.gmane.org \
--to=michael.renner@geizhals.at \
--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