linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
	Rhyland Klein <rklein@nvidia.com>, Rob Herring <robh@kernel.org>
Cc: Tero Kristo <t-kristo@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Regression: next-20160518: Clk? on BeagleBoard-X15
Date: Thu, 19 May 2016 20:35:29 +0300	[thread overview]
Message-ID: <573DF961.4070705@ti.com> (raw)
In-Reply-To: <20160519165719.GW5995@atomide.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1741 bytes --]

On 19/05/16 19:57, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [160519 08:48]:
>> I have'nt bisected yet, but the platform seems to have booted on
>> next-20160517
>> https://github.com/nmenon/kernel-test-logs/blob/next-20160517/omap2plus_defconfig/am57xx-evm.txt
>>
>> https://github.com/nmenon/kernel-test-logs/blob/next-20160518/omap2plus_defconfig/am57xx-evm.txt
> 
> Seems to be commit ac78f9bdcf38 ("drivers/of: Fix depth when
> unflattening devicetree").
> 
> Rob, you need to start playing golf or something between -rc6 and
> the end of the merge window or something :)

I'm not sure if it's related, but I'm seeing this on omap4 panda, next-20160519:

[    0.000000] Unable to handle kernel paging request at virtual address af6ec820
...
[    0.000000] [<c071ced4>] (unflatten_dt_nodes) from [<c071d5a4>] (__unflatten_device_tree+0xe8/0x254)
[    0.000000]  r10:c0de3140 r9:ef6b44a4 r8:c15b77c0 r7:00000000 r6:cffee000 r5:00038358
[    0.000000]  r4:c0de00c0
[    0.000000] [<c071d4bc>] (__unflatten_device_tree) from [<c0c4a050>] (unflatten_device_tree+0x28/0x40)
[    0.000000]  r9:0000000c r8:c0d07ca8 r7:c159f4f4 r6:c0d520f8 r5:c0c5984c r4:c0c491a0
[    0.000000] [<c0c4a028>] (unflatten_device_tree) from [<c0c04754>] (setup_arch+0x770/0xbb4)
[    0.000000]  r5:c0c5984c r4:c0d02908
[    0.000000] [<c0c03fe4>] (setup_arch) from [<c0c009c8>] (start_kernel+0x50/0x3c4)
[    0.000000]  r10:00000000 r9:412fc09a r8:8000406a r7:c0d02900 r6:c0c5ba44 r5:c0d029ac
[    0.000000]  r4:c0de3214
[    0.000000] [<c0c00978>] (start_kernel) from [<8000807c>] (0x8000807c)
[    0.000000]  r10:00000000 r9:412fc09a r8:8000406a r7:c0d07de8 r6:c0c5ba44 r5:c0d029ac
[    0.000000]  r4:c0de3214

 Tomi


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2016-05-19 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <573DDFE6.8010209@ti.com>
2016-05-19 16:57 ` Regression: next-20160518: Clk? on BeagleBoard-X15 Tony Lindgren
2016-05-19 17:35   ` Rob Herring
2016-05-20 19:43     ` Nishanth Menon
2016-05-19 17:35   ` Tomi Valkeinen [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=573DF961.4070705@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rklein@nvidia.com \
    --cc=robh@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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).