public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Erich Focht <focht@ess.nec.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] hanging process cannot be killed
Date: Wed, 16 May 2001 16:55:20 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005594@msgid-missing> (raw)

Hello,

how can it happen that a process isn't killable with kill -9 any more? I
have encountered this a few times and from within kdb two processes seem
to be in "run" state on the same CPU! The one marked as "current" shows
the following traceback:
   __ia64_save_fpu+0x20
   schedule+0xa40
   invoke_schedule+0x20
   ia64_leave_kernel+0x30

This process sits on the CPU, eats up cycles and the scheduler doesn't
seem to touch it any more. I only can get rid of it by rebooting.

Another traceback of a similar situation (with the same executable) was:
   __ia64_save_fpu+0x280
   schedule+0xa40
   ia64_do_signal+0x670
   handle_signal_delivery+0x30
   ia64_leave_kernel+0x30

I've seen this with 2.4.0 and 2.4.4 kernels, with B1 stepping CPUs. With
2.4.4 in single dispersal mode the problem doesn't seem to occur...

Thanks in advance for any help, ideas, comments...

Best regards,
Erich

---
Erich Focht                                    <efocht@ess.nec.de>
NEC European Supercomputer Systems, European HPC Technology Center
Hessbruehlstr. 21B, 70565 Stuttgart, Germany
phone: +49-711-78055-15                    fax  : +49-711-78055-25




             reply	other threads:[~2001-05-16 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 16:55 Erich Focht [this message]
2001-05-16 18:49 ` [Linux-ia64] hanging process cannot be killed David Mosberger

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=marc-linux-ia64-105590693005594@msgid-missing \
    --to=focht@ess.nec.de \
    --cc=linux-ia64@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