All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-next test] 36692: regressions - FAIL
Date: Wed, 25 Mar 2015 09:22:29 +0000	[thread overview]
Message-ID: <1427275349.10784.17.camel@citrix.com> (raw)
In-Reply-To: <osstest-36692-mainreport@xen.org>

On Wed, 2015-03-25 at 04:54 +0000, xen.org wrote:
> flight 36692 linux-next real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/36692/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-xl            5 xen-boot                  fail REGR. vs. 36569

I replied separately to all the test-amd64-i386-* ones.

>  test-amd64-amd64-xl-multivcpu  9 guest-start              fail REGR. vs. 36569

Guest log ends
http://www.chiark.greenend.org.uk/~xensrcts/logs/36692/test-amd64-amd64-xl-multivcpu/guest-debian.guest.osstest-console

[    0.280449] BUG: unable to handle kernel NULL pointer dereference at 00000000000000f8
[    0.280483] IP: [<ffffffff81425473>] free_cache_attributes+0xa3/0x110
[    0.281024] PGD 0 
[    0.281024] Oops: 0002 [#1] SMP 
[    0.281024] Modules linked in:
[    0.281024] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W       4.0.0-rc4-next-20150323 #1
[    0.281024] task: ffff88001e8c0000 ti: ffff88001e8c8000 task.ti: ffff88001e8c8000
[    0.281024] RIP: e030:[<ffffffff81425473>]  [<ffffffff81425473>] free_cache_attributes+0xa3/0x110
[    0.281024] RSP: e02b:ffff88001e8cbe08  EFLAGS: 00010206
[    0.281024] RAX: 0000000000000001 RBX: ffff88001eb0acf8 RCX: 00000000000000d8
[    0.281024] RDX: 0000000000000001 RSI: fffffffffffffffe RDI: ffff88001eb0acf8
[    0.281024] RBP: ffff88001e8cbe58 R08: 000000000000000f R09: 0000000000000000
[    0.281024] R10: ffff88001f6cedc0 R11: ffffffff813258a0 R12: 0000000000000000
[    0.281024] R13: 00000000000000d8 R14: 0000000000000000 R15: 0000000000010670
[    0.281024] FS:  0000000000000000(0000) GS:ffff88001fa80000(0000) knlGS:0000000000000000
[    0.281024] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    0.281024] CR2: 00000000000000f8 CR3: 0000000001e0e000 CR4: 0000000000000660
[    0.281024] Stack:
[    0.281024]  ffff8800ffffffea 0000000000010670 ffff88001fa10670 0000000300010680
[    0.281024]  ffff88001e8cbe88 0000000000000000 00000000ffffffea 0000000000000000
[    0.281024]  ffffffff81ec49e8 0000000000000000 ffff88001e8cbe88 ffffffff81f28079
[    0.281024] Call Trace:
[    0.281024]  [<ffffffff81f28079>] cacheinfo_sysfs_init+0x40/0x93
[    0.281024]  [<ffffffff81f28039>] ? container_dev_init+0x2f/0x2f
[    0.281024]  [<ffffffff81002124>] do_one_initcall+0x84/0x1e0
[    0.281024]  [<ffffffff810f126e>] ? __wake_up+0x4e/0x70
[    0.281024]  [<ffffffff81ee8310>] kernel_init_freeable+0x15e/0x1f8
[    0.281024]  [<ffffffff81ee79b5>] ? do_early_param+0x8c/0x8c
[    0.281024]  [<ffffffff817f1b50>] ? rest_init+0x70/0x70
[    0.281024]  [<ffffffff817f1b59>] kernel_init+0x9/0xf0
[    0.281024]  [<ffffffff81808853>] ret_from_fork+0x53/0x80
[    0.281024]  [<ffffffff817f1b50>] ? rest_init+0x70/0x70
[    0.281024] Code: 48 89 df 48 63 d2 e8 2d 2c f1 ff 39 05 d7 06 aa 00 89 c2 76 2b 41 39 d4 74 de 89 d1 48 8b 0c cd 40 45 ec 81 49 8b 0c 0f 4c 01 e9 <f0> 4c 0f b3 71 20 89 c0 f0 48 0f b3 03 eb be 66 0f 1f 44 00 00 
[    0.281024] RIP  [<ffffffff81425473>] free_cache_attributes+0xa3/0x110
[    0.281024]  RSP <ffff88001e8cbe08>
[    0.281024] CR2: 00000000000000f8
[    0.281024] ---[ end trace ff2aa05e6cc4a726 ]---
[    0.399540] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009

with a prior WARNING which looks related. Looks most likely to be a
generic issue?

>  test-amd64-amd64-xl-credit2   9 guest-start               fail REGR. vs. 36569

Similar trace to above.

>  build-armhf-pvops             5 kernel-build              fail REGR. vs. 36569

ld:./arch/arm/kernel/vmlinux.lds:544: syntax error

=> Likely a generic issue.

>  test-amd64-amd64-xl-qemut-winxpsp3  7 windows-install     fail REGR. vs. 36569

http://www.chiark.greenend.org.uk/~xensrcts/logs/36692/test-amd64-amd64-xl-qemut-winxpsp3/win.guest.osstest--vnc.jpeg

"Before starting OpenSSH service you must..." Is this a problem with the
test image perhaps?

Ian.

      parent reply	other threads:[~2015-03-25  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  4:54 [linux-next test] 36692: regressions - FAIL xen.org
2015-03-25  9:16 ` Ian Campbell
2015-03-25 13:33   ` Boris Ostrovsky
2015-03-25  9:22 ` Ian Campbell [this message]

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=1427275349.10784.17.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.