From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Don Slutz <dslutz@verizon.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [TESTDAY] Test report
Date: Thu, 23 Jan 2014 10:51:12 +0000 [thread overview]
Message-ID: <1390474272.24595.37.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <c6880ec1-95a8-4c1d-8b10-75534b33f170@email.android.com>
On Mon, 2014-01-20 at 18:35 -0500, Konrad Rzeszutek Wilk wrote:
> >[root@dcs-xen-54 ~]# xl save -p 6 /big/xl-save/centos-6.4-x86_64.0.save
> >Saving to /big/xl-save/centos-6.4-x86_64.0.save new xl format (info
> >0x0/0x0/560)
> >xc: Saving memory: iter 0 (last sent 0 skipped 0): 1044481/1044481
> >100%
> >[root@dcs-xen-54 ~]# xl unpause 6
> >
> >has left domain #6 in a bad disk state (on VGA):
> >
> >INFO: task jbd2/dm-0-8:386 blocked for more then 120 seconds.
> >INFO: task sadc:22139 blocked for more then 120 seconds.
> >
> >
> >However "xl restore -V /big/xl-save/centos-6.4-x86_64.0.save" looks to
> >work fine.
> >
> >2nd time the unpause failed with:
> >[root@dcs-xen-54 ~]# xl unpause 17
> >
> >WARNING: g.e. still in use!
> >WARNING: g.e. still in use!
> >WARNING: g.e. still in use!
> >pm_op(): platform_pm_resume+0x0/0x50 returns -19
> >PM: Device i8042 failed to resume: error -19
> >INFO: task sadc:22164 blocked for more then 120 seconds.
> >"echo 0 >..."
> >INFO: task sadc:22164 blocked for more then 120 seconds.
> >
> >
> >[root@dcs-xen-54 ~]# xl des 17
> >[root@dcs-xen-54 ~]# xl restore -V
> >/big/xl-save/centos-6.4-x86_64.0.save
> >
> >
> >Not sure if this is expected or not.
>
> I think Ian saw this with the 'fast-cancel' something resume but I might be incorrect.
It seems to me that it would be the same issue, but I can't recall if
the fix from Ian J was in rc2 or not.
Ian.
next prev parent reply other threads:[~2014-01-23 10:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 22:49 [TESTDAY] Test report Don Slutz
2014-01-20 23:35 ` Konrad Rzeszutek Wilk
2014-01-23 10:51 ` Ian Campbell [this message]
2014-01-23 22:03 ` Don Slutz
2014-01-24 14:58 ` Konrad Rzeszutek Wilk
2014-01-24 16:43 ` Don Slutz
2014-01-24 19:06 ` Don Slutz
2014-01-24 19:20 ` Konrad Rzeszutek Wilk
2014-01-27 1:15 ` herbert cland
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 17:03 Andrii Anisov
2017-05-23 20:14 ` Stefano Stabellini
2017-05-25 10:17 ` Julien Grall
2017-05-25 18:41 ` Stefano Stabellini
2016-05-13 20:34 Edgar E. Iglesias
2016-05-14 18:15 ` Julien Grall
2016-05-14 19:04 ` Edgar E. Iglesias
2016-05-16 9:58 ` Wei Liu
2016-05-16 13:20 ` Julien Grall
2016-05-16 13:41 ` Edgar E. Iglesias
2016-05-16 13:43 ` Julien Grall
2016-05-13 15:14 Tamas K Lengyel
2015-10-01 16:59 Tamas K Lengyel
2015-10-01 17:04 ` Wei Liu
2014-10-30 10:54 Jan Vejvalka
2014-10-30 14:39 ` Ian Campbell
2014-10-31 6:35 ` Jan Vejvalka
2014-10-30 14:58 ` Roger Pau Monné
2012-09-19 7:04 Dariusz Krempa
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=1390474272.24595.37.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=dslutz@verizon.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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).