From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
Kevin Bowling <kevinb@analograils.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: INFO: task journal:337 blocked for more than 120 seconds
Date: Fri, 02 Oct 2009 12:13:26 -0700 [thread overview]
Message-ID: <4AC650D6.5040800@goop.org> (raw)
In-Reply-To: <1254510407.7999.3.camel@localhost.localdomain>
On 10/02/09 12:06, Shirley Ma wrote:
> On Fri, 2009-10-02 at 11:30 -0700, Jeremy Fitzhardinge wrote:
>
>> I'm assuming from the lists you've posted to that this is under KVM?
>> What disk drivers are you using (virtio or emulated)?
>>
>> Can you get a full stack backtrace of kjournald?
>>
> Yes, it's under KVM, disk driver is virtio. Since the io has issue, the
> stack can't be saved on the disk. I have the image file attached here.
>
Ah, thank you. The backtrace does indeed look very similar.
(BTW, you could get a serial console with "qemu-kvm -nographic -append
console=ttyS0 ...")
J
next prev parent reply other threads:[~2009-10-02 19:13 UTC|newest]
Thread overview: 11+ 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:03 ` Javier Guerra
2009-10-01 21:17 ` Shirley Ma
2009-10-01 22:09 ` Shirley Ma
2009-10-02 18:30 ` INFO: task journal:337 " Jeremy Fitzhardinge
2009-10-02 19:06 ` Shirley Ma
2009-10-02 19:13 ` Jeremy Fitzhardinge [this message]
2009-10-04 4:12 ` Kevin Bowling
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=4AC650D6.5040800@goop.org \
--to=jeremy@goop.org \
--cc=drjones@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=kevinb@analograils.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.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 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).