From: Wei Liu <wei.liu2@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xensource.com, wei.liu2@citrix.com
Subject: Re: [xen-unstable test] 64494: regressions - FAIL
Date: Wed, 18 Nov 2015 14:49:45 +0000 [thread overview]
Message-ID: <20151118144945.GA16306@citrix.com> (raw)
In-Reply-To: <osstest-64494-mainreport@xen.org>
Hi Juergen
Looks like there is something we missed after all.
On Wed, Nov 18, 2015 at 02:31:57PM +0000, osstest service owner wrote:
> flight 64494 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64494/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-i386-pvgrub 10 guest-start fail REGR. vs. 64035
Nov 18 05:11:19.753014 (d2) Bootstrapping...
Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
Nov 18 05:11:19.769134 (d2) start_info: 0xa13000(VA)
Nov 18 05:11:19.769158 (d2) nr_pages: 0x20000
Nov 18 05:11:19.777046 (d2) shared_inf: 0xca1fc000(MA)
Nov 18 05:11:19.777072 (d2) pt_base: 0xa16000(VA)
Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
Nov 18 05:11:19.785108 (d2) mod_start: 0x0(VA)
Nov 18 05:11:19.785135 (d2) mod_len: 0
Nov 18 05:11:19.793047 (d2) flags: 0x0
Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
Nov 18 05:11:19.793108 (d2) stack: 0x972580-0x992580
Nov 18 05:11:19.801150 (d2) MM: Init
Nov 18 05:11:19.801181 (d2) _text: 0x0(VA)
Nov 18 05:11:19.801197 (d2) _etext: 0x7b22d(VA)
Nov 18 05:11:19.809104 (d2) _erodata: 0xa4000(VA)
Nov 18 05:11:19.809123 (d2) _edata: 0xa81a8(VA)
Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
Nov 18 05:11:19.817062 (d2) _end: 0x992b30(VA)
Nov 18 05:11:19.817099 (d2) start_pfn: a24
Nov 18 05:11:19.817125 (d2) max_pfn: 20000
Nov 18 05:11:19.825037 (d2) Mapping memory range 0x1000000 - 0x20000000
Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
Nov 18 05:11:19.825100 (d2) skipped 1000
Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for b1c000(b1c000)-20000000(20000000)
Nov 18 05:11:19.833089 (d2) Page fault at linear address c00008, eip 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid memory?).
The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
be working fine.
Wei.
next prev parent reply other threads:[~2015-11-18 14:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:31 [xen-unstable test] 64494: regressions - FAIL osstest service owner
2015-11-18 14:49 ` Wei Liu [this message]
2015-11-18 15:54 ` Juergen Gross
2015-11-18 15:59 ` Wei Liu
2015-11-18 16:03 ` Juergen Gross
2015-11-19 10:24 ` Juergen Gross
2015-11-19 10:30 ` Ian Campbell
2015-11-19 10:50 ` Wei Liu
2015-11-19 10:55 ` Ian Campbell
2015-11-19 10:56 ` Wei Liu
2015-11-19 10:57 ` Juergen Gross
2015-11-19 11:47 ` Juergen Gross
2015-11-19 12:19 ` Wei Liu
2015-11-19 12:29 ` Juergen Gross
2015-11-19 12:38 ` Wei Liu
2015-11-20 15:14 ` Jan Beulich
2015-11-20 15:23 ` Wei Liu
[not found] ` <564F46C802000078000B73E9@suse.com>
2015-11-20 15:29 ` Juergen Gross
2015-11-20 15:34 ` Wei Liu
2015-11-20 15:41 ` Andrew Cooper
2015-11-20 15:42 ` Andrew Cooper
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=20151118144945.GA16306@citrix.com \
--to=wei.liu2@citrix.com \
--cc=jgross@suse.com \
--cc=osstest-admin@xenproject.org \
--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).