lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 18:26:21 -0700 (PDT)
From:	Christian Kujau <>
To:	Jeremy Fitzhardinge <>
cc:	LKML <>,,, Thomas Gleixner <>
Subject: Re: 2.6.32-rc not booting with Xen-3.2 (bisected)

On Mon, 26 Oct 2009 at 18:14, Christian Kujau wrote:
> Oh, I totally forgot about "xm dmesg", it's on the URL above too. I don't 
> see any timestamps in "xm dmesg", so I guess I'll have to try again with 
> "xm dmesg --clear" inbetween boots.

Did that - when I boot a working kernel (2.6.31), "xm dmesg" prints 
nothing but a newline. When I boot 2.6.31-rc1, this happens:

$ xm create sid.cfg -c
Using config file "/etc/xen/sid.cfg".
Started domain sid

$ xm dmesg
(XEN) mm.c:665:d889 Error getting mfn 127f (pfn 7403) from L1 entry 801000000127f065 for dom889
(XEN) traps.c:413:d889 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 889 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.2.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e033:[<ffffffff812c50ad>]
(XEN) RFLAGS: 0000000000000282   CONTEXT: guest
(XEN) rax: 00000000ffffffea   rbx: 800000000127f061   rcx: 000000000008885a
(XEN) rdx: 0000000000000000   rsi: 800000000127f061   rdi: ffffffff8127f000
(XEN) rbp: ffffffff81279fb8   rsp: ffffffff81279f18   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffffffff8127f000   r13: 0000000000000000   r14: 0000000000000080
(XEN) r15: ffffffff81279fc8   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 00000000aa991000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff81279f18:
(XEN)    000000000008885a 0000000000000000 ffffffff812c50ad 000000010000e030
(XEN)    0000000000010082 ffffffff81279f58 000000000000e02b ffffffff812c504c
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff81279f60 0000008000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff810197bd ffff8127f000007f 000000000000ffff
(XEN)    0000000000000000 ffffffff812c4d19 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffffffff81385000 ffffffff81386000 ffffffff81387000
(XEN)    ffffffff81388000 ffffffff81389000 ffffffff8138a000 ffffffff8138b000
(XEN)    ffffffff8138c000 ffffffff8138d000 ffffffff8138e000 ffffffff8138f000
(XEN)    ffffffff81390000 ffffffff81391000 ffffffff81392000 ffffffff81393000
(XEN)    ffffffff81394000 ffffffff81395000 ffffffff81396000 ffffffff81397000
(XEN)    ffffffff81398000 ffffffff81399000 ffffffff8139a000 ffffffff8139b000
(XEN)    ffffffff8139c000 ffffffff8139d000 ffffffff8139e000 ffffffff8139f000
(XEN)    ffffffff813a0000 ffffffff813a1000 ffffffff813a2000 ffffffff813a3000
(XEN)    ffffffff813a4000 ffffffff813a5000 ffffffff813a6000 ffffffff813a7000
(XEN)    ffffffff813a8000 ffffffff813a9000 ffffffff813aa000 ffffffff813ab000
(XEN)    ffffffff813ac000 ffffffff813ad000 ffffffff813ae000 ffffffff813af000
(XEN)    ffffffff813b0000 ffffffff813b1000 ffffffff813b2000 ffffffff813b3000
(XEN)    ffffffff813b4000 ffffffff813b5000 ffffffff813b6000 ffffffff813b7000

Also, "xm list" takes very long to complete now:

$ time xm list sid
Name                  ID   Mem VCPUs      State   Time(s)
sid                  906   512     1     --p---     0.0
real    0m10.677s user    0m0.108s sys     0m0.028s

BOFH excuse #43:

boss forgot system password
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists