All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shirley Ma <mashirle@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	mcao@us.ibm.com
Subject: Re: INFO: task kjournal:337 blocked for more than 120 seconds
Date: Thu, 01 Oct 2009 14:00:20 -0700	[thread overview]
Message-ID: <1254430820.5033.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1254416336.6787.6.camel@localhost.localdomain>

I talked to Mingming, she suggested to use different IO scheduler. The
default scheduler is cfg, after I switch to noop, the problem is gone. 

So there seems a bug in cfg scheduler. It's easily reproduced it when
running the guest kernel, so far I haven't hit this problem on the host
side.

If I need to file a bug for some one to look at, please let me know.

Thanks
Shirley


  parent reply	other threads:[~2009-10-01 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 21:11 INFO: task journal:337 blocked for more than 120 seconds Shirley Ma
2009-10-01 13:20 ` Marcelo Tosatti
2009-10-01 16:58   ` Shirley Ma
2009-10-01 21:00     ` INFO: task kjournal:337 " Shirley Ma
2009-10-01 21:00     ` Shirley Ma [this message]
2009-10-01 21:03       ` Javier Guerra
2009-10-01 21:03       ` Javier Guerra
2009-10-01 21:17         ` Shirley Ma
2009-10-01 21:17         ` Shirley Ma
2009-10-01 22:09           ` Shirley Ma
2009-10-01 22:09           ` Shirley Ma
2009-10-01 16:58   ` INFO: task journal:337 " Shirley Ma
2009-10-01 13:20 ` Marcelo Tosatti
2009-10-02 18:30 ` Jeremy Fitzhardinge
2009-10-02 19:06   ` Shirley Ma
2009-10-02 19:13     ` Jeremy Fitzhardinge
2009-10-02 19:13     ` Jeremy Fitzhardinge
2009-10-02 19:06   ` Shirley Ma
2009-10-04  4:12   ` Kevin Bowling
2009-10-04  4:12   ` Kevin Bowling
2009-10-02 18:30 ` Jeremy Fitzhardinge

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=1254430820.5033.4.camel@localhost.localdomain \
    --to=mashirle@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcao@us.ibm.com \
    --cc=mtosatti@redhat.com \
    --cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.