From: "Andrew B. Cramer" <andrew.cramer@cramer-ts.com>
To: linux-admin@vger.kernel.org,
thomas.steinbrecher@physchem.uni-freiburg.de
Subject: RE: killing a stuborn process
Date: Fri, 10 Jan 2003 01:05:05 -0600 [thread overview]
Message-ID: <3E1E1C41.24507.1DD1FD@localhost> (raw)
In-Reply-To: <C65F89D1AC0BB54B865127151A24DA780E4902FD@nbexchm2.aliant.icn>
Thomas,
If you think it may be a hardware problem, compile the kernel
without SMP support, and remove the second processor. After a
restart, check /proc/cpuinfo to see that one processor is shown.
Test. If it still fails or not, swap the processors. Test again. That
will eliminate the CPU's as an issue. DO NOT use your working system
for parts! Just check configuration files and module versions.
Best - Andrew
> From: Thomas Steinbrecher [mailto:thomas.steinbrecher@physchem.uni-freiburg.de]
> Sent: Tuesday, January 07, 2003 3:34 PM
> To: linux-admin@vger.kernel.org
> Subject: killing a stuborn process
>
>
> Greetings,
>
> please excuse if this is a newbie question, I'm no computer expert.
>
> I have several dual ATHLON PC's with Suse 8.0 in a Beowulf cluster on which I run molecular dynamics calculations.
>
> On one of my machines the calculations stop sometimes
> without apparent reason and I can't end the processes
> anymore (kill -9 has no effect). The processes are shown as running by ps, but they produce no cpu load with top.
>
> Is there another way to kill such a process?
>
> I suppose one of the CPUs might be damaged, but how do I
> test if that is true and what causes the processes to
> hangup?
> (The same calculation runs fine on another PC with
> identical software and hardware setup)
>
> Regards,
>
> Thomas
next prev parent reply other threads:[~2003-01-10 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 14:48 killing a stuborn process Shaw, Marco
2003-01-10 7:05 ` Andrew B. Cramer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 19:34 Thomas Steinbrecher
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=3E1E1C41.24507.1DD1FD@localhost \
--to=andrew.cramer@cramer-ts.com \
--cc=linux-admin@vger.kernel.org \
--cc=thomas.steinbrecher@physchem.uni-freiburg.de \
/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;
as well as URLs for NNTP newsgroup(s).