public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-kernel@vger.kernel.org
Subject: "Unkillable processes" and INFO: task ... blocked for more than 120 seconds
Date: Fri, 20 Feb 2015 18:13:36 +0100	[thread overview]
Message-ID: <mc7q02$i7v$1@ger.gmane.org> (raw)

Hello,

today, I had the following problem:

I was editing a few photos in GIMP and after I finished with that, I 
tried to close GIMP which failed. KDE offered me to terminate the 
application which also didn't work.

So I opened a terminal and tried "killall -9 gimp" --> No success

Next I tried "pgrep gimp" to get the PID of the hanging process. With 
the result that pgrep now also got stuck with hangup of my whole shell.

A "strace pgrep gimp" told me that pgrep actually hung up on a read on 
"/proc/18294/cmdline" so I guessed that this could be my hanging GIMP 
process. But even "kill -9 18294" was not able to kill the process.

So I switched over to a VT shell and logged in as root which at first 
hung up the login shell, but was fixable by pressing "Ctrl + C". Even as 
root I was unable to kill GIMP.

The kernel didn't actually crash. My music player continued to play 
nicely and my mail client was fully usable.

I saved some log output to pastebin: http://pastebin.com/FPDvyePJ

What has been happening here? Why is it possible that I actually get 
non-killable processes?

If you need additional information, please ask.

Thank you very much in advance.

Manuel


             reply	other threads:[~2015-02-20 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 17:13 Manuel Reimer [this message]
2015-02-20 17:30 ` "Unkillable processes" and INFO: task ... blocked for more than 120 seconds Manuel Reimer
2015-02-20 19:27   ` Martin Steigerwald

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='mc7q02$i7v$1@ger.gmane.org' \
    --to=manuel.spam@nurfuerspam.de \
    --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