xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <dunlapg@umich.edu>
To: Marek Marczykowski <marmarek@invisiblethingslab.com>
Cc: Simon Gaiser <simon@invisiblethingslab.com>,
	Ian Jackson <ian.jackson@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test for osstest, features used in Qubes OS
Date: Mon, 21 May 2018 16:48:38 +0100	[thread overview]
Message-ID: <CAFLBxZagWwUe-wJ-f7B9KZSTYWfqta71w3GWcz=djbLZiODKHQ@mail.gmail.com> (raw)
In-Reply-To: <20180518161925.GE11683@mail-itl>

On Fri, May 18, 2018 at 5:19 PM, Marek Marczykowski
<marmarek@invisiblethingslab.com> wrote:
> On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
>> >>> On 18.05.18 at 17:33, <marmarek@invisiblethingslab.com> wrote:
>> > Yes, I'm happy to help with that. As I've said, the basic test is very
>> > simple (rtcwake command) and already very useful. The fact that it is(?)
>> > broken on staging doesn't make it easier,
>>
>> Details on the breakage would be appreciated (on a separate thread),
>> unless you plan to address it yourself. I recall Simon(?) mentioning this as
>> well, but also not providing sufficient data to consider looking into it
>> (perhaps simply because it wasn't easy to obtain useful data, as
>> frequently is the case with S3 resume). I think it would be nice if we could
>> release 4.11 without a regression here.
>
> I only know that Simon have tested it and it fails. Cc'ing him.

Well I tried it with a post-RC 4.11 and got the below.  I haven't done
any investigation.

 -George

(XEN) CPU0 CMCI LVT vector (0xf2) already installed
(XEN) CPU0: Thermal monitoring enabled (TM1)
(XEN) Finishing wakeup from ACPI S3 state.
(XEN) Preparing system for ACPI S3 state.
(XEN) Disabling non-boot CPUs ...
(XEN) Broke affinity for irq 16
(XEN) Broke affinity for irq 49
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) Enabling non-boot CPUs  ...
(XEN) Booting processor 1/2 eip 8e000
(XEN) Initializing CPU#1
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU1: Intel(R) Xeon(R) CPU           E5630  @ 2.53GHz stepping 02
(XEN) Booting processor 2/18 eip 8e000
(XEN) Initializing CPU#2
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 9
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU2: Intel(R) Xeon(R) CPU           E5630  @ 2.53GHz stepping 02
(XEN) Booting processor 3/20 eip 8e000
(XEN) Initializing CPU#3
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 10
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 12288K
(XEN) CPU3: Intel(R) Xeon(R) CPU           E5630  @ 2.53GHz stepping 02
(XEN) *** DOUBLE FAULT ***
(XEN) ----[ Xen-4.11-rc  x86_64  debug=y   Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82d080377944>] handle_exception+0x9c/0xf7
(XEN) RFLAGS: 0000000000010006   CONTEXT: hypervisor
(XEN) rax: ffffc900422480b8   rbx: 0000000000000000   rcx: 0000000000000005
(XEN) rdx: 0000000000000000   rsi: 0000000000000000   rdi: 0000000000000000
(XEN) rbp: 000036ffbddb7f27   rsp: ffffc90042248000   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: ffffc9004224ffff
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026e0
(XEN) cr3: 000000018a100000   cr2: ffffc90042247ff8
(XEN) fsb: 00007f6242d95700   gsb: ffff88003dc00000   gss: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Current stack base ffffc90042248000 differs from expected ffff8300dfa80000
(XEN) Valid stack range: ffffc9004224e000-ffffc90042250000,
sp=ffffc90042248000, tss.rsp0=ffff8300dfa87fa0
(XEN) No stack overflow detected. Skipping stack trace.
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) DOUBLE FAULT -- system shutdown
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-21 15:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 21:54 Test for osstest, features used in Qubes OS Marek Marczykowski-Górecki
2018-05-17 12:26 ` Ian Jackson
2018-05-17 14:59   ` Marek Marczykowski-Górecki
2018-05-17 15:12     ` Ian Jackson
2018-05-17 18:00       ` Sander Eikelenboom
2018-05-18 15:44         ` Marek Marczykowski-Górecki
2018-05-18 15:33       ` Marek Marczykowski-Górecki
2018-05-18 15:54         ` Jan Beulich
2018-05-18 16:19           ` Marek Marczykowski
2018-05-21 15:48             ` George Dunlap [this message]
2018-05-21 16:17               ` Andrew Cooper
2018-05-21 16:28                 ` George Dunlap
2018-05-21 17:18                   ` George Dunlap
2018-05-22 22:21               ` Simon Gaiser
2018-05-24 13:15                 ` Jan Beulich
2018-05-24 13:39                   ` Simon Gaiser
2018-05-21 11:04       ` George Dunlap
2018-05-21 11:52         ` Dario Faggioli
2018-05-21 13:57           ` Ian Jackson
2018-05-21 14:11             ` George Dunlap
2018-05-22  7:51             ` Dario Faggioli
2018-05-21 11:49       ` Dario Faggioli

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='CAFLBxZagWwUe-wJ-f7B9KZSTYWfqta71w3GWcz=djbLZiODKHQ@mail.gmail.com' \
    --to=dunlapg@umich.edu \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@citrix.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=simon@invisiblethingslab.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).