xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Marek Marczykowski <marmarek@mimuw.edu.pl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Joanna Rutkowska <joanna@invisiblethingslab.com>
Subject: Re: xen-4.1: PV domain hanging at startup, jiffies stopped
Date: Mon, 29 Aug 2011 22:21:23 +0200	[thread overview]
Message-ID: <4E5BF4C3.2050108@mimuw.edu.pl> (raw)
In-Reply-To: <20110829200749.GA17265@dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 2138 bytes --]

On 29.08.2011 22:07, Konrad Rzeszutek Wilk wrote:
> On Sun, Aug 28, 2011 at 03:13:46PM +0200, Marek Marczykowski wrote:
>> Hey,
>>
>> I'm experiencing strange problem: non-deterministic PV domain hang, only
>> on some machines (with fast SSD drive). I've tried xen-4.1.0 and
>> xen-4.1.1 with many kernels different kernels:
>> VM:
>>  - 2.6.38.3 xenlinux based on SUSE package
>>  - vanilla 3.0.3
>>  - vanilla 3.1 rc2
>> dom0:
>>  - 2.6.38.3 xenlinux based on SUSE package
>>  - vanilla 3.1 rc2
>>
>> Result always the same: sometimes VM hang at startup, SysRq-T shows
>> modprobe waiting in "wait_for_devices" (concretely schedule_timeout) and
>> jiffies counter not increasing between task-states dumps.
>>
>> The only found thing (probably) connected with this problem are domU
>> kernel messages:
>> CE: xen increased min_delta_ns to 150000 nsec
>> (...)
>> CE: xen increased min_delta_ns to 4000000 nsec
>> CE: Reprogramming failure. Giving up
>>
>> This messages doesn't exists in successful boot.
>>
>> I've also tried some options to xen and domU kernel, but without success
>> (all combinations):
> 
> BTW, your 'xencons=..' and 'swiotlb=force' are obsolete. Use
> 'console=hvc0' and 'iommu=soft'. The 'swiotlb=force' kills performance.
> 
>> xen: tsc=unstable, cpufreq=none
>> domU: nohz=off, clocksource=tsc
>>
>> Some combination of above options lowered frequency of problem (ex
>> tsc=unstable + nohz=off), but it happens quite often - like 1 of 15
>> boots fails.
>>
>> Have you idea what is the cause and what can help?
> 
> The problem looks to be xenwatch stuck. So the problem is in Dom0 right?

This "R" state of xenwatch looks like result of SysRq, which dumps data...

[  118.679707]  [<ffffffff812a8081>] handle_sysrq+0x21/0x30
[  118.679707]  [<ffffffff8128db49>] sysrq_handler+0xb9/0xe0
[  118.679707]  [<ffffffff8128ff50>] xenwatch_thread+0xb0/0x170

And the problem is at DomU boot, Dom0 works without any problems.

-- 
Pozdrawiam / Best Regards,
Marek Marczykowski         | RLU #390519
marmarek at mimuw edu pl   | xmpp:marmarek at staszic waw pl


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-08-29 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28 13:13 xen-4.1: PV domain hanging at startup, jiffies stopped Marek Marczykowski
2011-08-29 20:07 ` Konrad Rzeszutek Wilk
2011-08-29 20:21   ` Marek Marczykowski [this message]
2011-08-29 20:59     ` Konrad Rzeszutek Wilk
2011-08-29 21:28       ` Pasi Kärkkäinen
2011-08-30 17:18       ` Marek Marczykowski
2011-08-31 16:27         ` Marek Marczykowski
2011-08-31 20:00           ` Dan Magenheimer
2011-08-31 20:49             ` Marek Marczykowski
2011-08-31 21:01               ` Keir Fraser
2011-08-31 21:13                 ` Marek Marczykowski
2011-08-31 22:07                   ` Keir Fraser

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=4E5BF4C3.2050108@mimuw.edu.pl \
    --to=marmarek@mimuw.edu.pl \
    --cc=joanna@invisiblethingslab.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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).