LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: allied internet ag- Stefan Priebe <s.priebe@allied-internet.ag>
Cc: Christian Kujau <lists@nerdbynature.de>,
	LKML <linux-kernel@vger.kernel.org>,
	jirislaby@gmail.com
Subject: Re: getting uninterruptible sleep processes after upgrade from 2.6.20.20 to 2.6.24.2
Date: Sun, 17 Feb 2008 12:54:07 -0800	[thread overview]
Message-ID: <20080217125407.5b76a052@laptopd505.fenrus.org> (raw)
In-Reply-To: <47B89DC6.4070906@allied-internet.ag>

On Sun, 17 Feb 2008 21:49:10 +0100
allied internet ag- Stefan Priebe <s.priebe@allied-internet.ag> wrote:

>  >> One week ago we upgraded about 300 servers from 2.6.20.20 to
>  >> 2.6.24.2.
>  >
>  > Painfull.
> 
> OK not really - i've tested the new kernel on all models. And it
> works fine... the DN state only comes sometimes - absolutely not
> reproducable. So my tests went OK and then we've done the update.
> I've now seen 5 servers in 7 days having this problem.
> 
>  >> Now we get sometimes dozent of processes in state DN. The system
>  >> is completely idle - but the load is 20 or 90 or whatever. And it
>  >> can only be "repaired" by rebooting the system.
>  >
>  > please post sysrq-t (echo t > /proc/sysrq-trigger) output.
> Sorry what key is sysrq? Can i also do this via SSH Console?

just do the echo above and it'll have the same effect as the key, and yes
you can do this via ssh just fine (I do that all the time)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-02-17 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 20:02 getting uninterruptible sleep processes after upgrade from 2.6.20.20 to 2.6.24.2 allied internet ag- Stefan Priebe
2008-02-17 20:36 ` Christian Kujau
2008-02-17 20:49   ` allied internet ag- Stefan Priebe
2008-02-17 20:54     ` Arjan van de Ven [this message]
2008-02-21 11:06       ` Stefan Priebe - allied internet ag
2008-02-21 13:15         ` Jiri Slaby
2008-02-21 13:37           ` Stefan Priebe - allied internet ag
2008-02-24 10:06             ` Jiri Slaby
2008-03-31 23:21               ` David Chinner
2008-02-17 20:37 ` Jiri Slaby

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=20080217125407.5b76a052@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=s.priebe@allied-internet.ag \
    /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).