All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [linux-linus test] 55255: regressions - FAIL
Date: Tue, 12 May 2015 13:35:46 +0100	[thread overview]
Message-ID: <5551F3A2.9050500@citrix.com> (raw)
In-Reply-To: <1431425244.8263.126.camel@citrix.com>

On 12/05/15 11:07, Ian Campbell wrote:
> On Mon, 2015-05-11 at 18:09 +0000, osstest service user wrote:
>> flight 55255 linux-linus real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/55255/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  test-armhf-armhf-xl-arndale   6 xen-boot                  fail REGR. vs. 50329
> 
> This is a real failure (and I suspect the others are just things which
> happened to run on arndale).
> 
> Tail of
> http://logs.test-lab.xenproject.org/osstest/logs/55255/test-armhf-armhf-xl-arndale/serial-arndale-metrocentre.log is below.
> 
> The "outdated DT detected, suspend/resume will NOT work" is due to the
> lack of an interrupt-controller property on the pmu device, which I fear
> we may be suppressing somewhere while making the dom0 dtb.

It seems that Osstest is using the device tree provided by the debian
installer.

I did try with the device tree provided by Linux and it boots without no
issue.

We may want to use the device tree attached to every Linux version in
order to avoid a such problem. Although, I don't much know


> The following null pointer exception I think is probably a bug arising
> from trying to continue on regardless.

I gave a quick look to see what happens. pmu_base_addr is NULL because
it's initialized only when the PMU is an interrupt controller (see
exynos_pmu_irq_init). So the first pmu_*read* will segfault.

I suspect it's an unwanted behavior because the warning only says
suspend/resume won't work. Not the kernel will crash.

Although, we know that DT is often tight to the kernel version. So I'm
not sure if we should care of it.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-05-12 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 18:09 [linux-linus test] 55255: regressions - FAIL osstest service user
2015-05-12 10:07 ` Ian Campbell
2015-05-12 10:28   ` Julien Grall
2015-05-12 12:35   ` Julien Grall [this message]
2015-05-12 12:53     ` Ian Campbell
2015-05-12 13:45       ` Julien Grall

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=5551F3A2.9050500@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.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.