LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Stefan Priebe - allied internet ag <s.priebe@allied-internet.ag>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Christian Kujau <lists@nerdbynature.de>,
	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: Thu, 21 Feb 2008 14:15:04 +0100	[thread overview]
Message-ID: <47BD7958.5080203@gmail.com> (raw)
In-Reply-To: <47BD5B30.103@allied-internet.ag>

Stefan Priebe - allied internet ag napsal(a):
> Hello!
> 
> I've done the (echo t > /proc/sysrq-trigger) now but i'm not able to get
> the whole output via dmesg.
> 
> Here is what i get:
> # dmesg
> 3.432124]  [<c0165a11>] do_select+0x390/0x46e
> [272363.432226]  [<c0166107>] __pollwait+0x0/0xcf
> [272363.432319]  [<c0115d90>] default_wake_function+0x0/0x8

dmesg ring buffer is too small to fit this in. Please repeat it once again
with bigger ringbuffer (dmesg -s if you have this chosen in your kernel) or
post /var/log/meassages output of all processes. I see only waiters in
readdir, not seeing who could block them.

Which filesystem did you run du on?

  reply	other threads:[~2008-02-21 13:14 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
2008-02-21 11:06       ` Stefan Priebe - allied internet ag
2008-02-21 13:15         ` Jiri Slaby [this message]
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=47BD7958.5080203@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=arjan@infradead.org \
    --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).