LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: allied internet ag- Stefan Priebe <s.priebe@allied-internet.ag>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: getting uninterruptible sleep processes after upgrade from 2.6.20.20 to 2.6.24.2
Date: Sun, 17 Feb 2008 21:36:25 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0802172133470.6469@sheep.housecafe.de> (raw)
In-Reply-To: <47B892B9.7060205@allied-internet.ag>

On Sun, 17 Feb 2008, allied internet ag- Stefan Priebe wrote:
> One week ago we upgraded about 300 servers from 2.6.20.20 to 2.6.24.2.

Did you test with *one* server before upgrading all 300? If not, please do 
and try to upgrade in smaller steps, e.g. 2.6.20->2.6.21 and see when it 
breaks. Add a few *DEBUG .config options, they may help narrowing 
down the problem...

C.
-- 
BOFH excuse #405:

Sysadmins unavailable because they are in a meeting talking about why they are unavailable so much.

  reply	other threads:[~2008-02-17 20:36 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 [this message]
2008-02-17 20:49   ` allied internet ag- Stefan Priebe
2008-02-17 20:54     ` Arjan van de Ven
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=alpine.DEB.1.00.0802172133470.6469@sheep.housecafe.de \
    --to=lists@nerdbynature.de \
    --cc=linux-kernel@vger.kernel.org \
    --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).