From: Guenter Roeck <linux@roeck-us.net>
To: Nishanth Menon <nm@ti.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Runtime warning due to commit 'ARM: OMAP: Catch callers of revision information prior to it being populated' in -next
Date: Mon, 18 Apr 2016 21:37:00 -0700 [thread overview]
Message-ID: <5715B5EC.2040000@roeck-us.net> (raw)
Hi,
commit 'ARM: OMAP: Catch callers of revision information prior to it
being populated' results in a runtime warning on various non-OMAP
architectures. I have seen it with the following qemu tests.
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:midway:multi_v7_defconfig:ecx-2000
arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
It is also reported by kernelci.org in at least one boot test for imx6q-cm-fx6.
The warning is as follows.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/id.c:49 omap_rev+0x3c/0x50
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc2-next-20160411 #1
Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[<c030f970>] (unwind_backtrace) from [<c030b094>] (show_stack+0x10/0x14)
[<c030b094>] (show_stack) from [<c0585424>] (dump_stack+0x84/0xa4)
[<c0585424>] (dump_stack) from [<c0341774>] (__warn+0xd4/0x100)
[<c0341774>] (__warn) from [<c03417c0>] (warn_slowpath_null+0x20/0x28)
[<c03417c0>] (warn_slowpath_null) from [<c0324024>] (omap_rev+0x3c/0x50)
[<c0324024>] (omap_rev) from [<c1114a18>] (__omap4_sar_ram_init+0x8/0x88)
[<c1114a18>] (__omap4_sar_ram_init) from [<c0301e5c>] (do_one_initcall+0x3c/0x16c)
[<c0301e5c>] (do_one_initcall) from [<c1100ccc>] (kernel_init_freeable+0x70/0x1ec)
[<c1100ccc>] (kernel_init_freeable) from [<c0b495e4>] (kernel_init+0x8/0x110)
[<c0b495e4>] (kernel_init) from [<c0307f78>] (ret_from_fork+0x14/0x3c)
---[ end trace cb88537fdc8fa200 ]---
Please have a look.
Thanks,
Guenter
next reply other threads:[~2016-04-19 4:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 4:37 Guenter Roeck [this message]
2016-04-19 12:19 ` Runtime warning due to commit 'ARM: OMAP: Catch callers of revision information prior to it being populated' in -next Nishanth Menon
2016-04-19 12:19 ` Nishanth Menon
2016-04-19 12:19 ` Nishanth Menon
2016-04-19 14:13 ` Tony Lindgren
2016-04-19 14:13 ` Tony Lindgren
2016-04-19 14:21 ` Nishanth Menon
2016-04-19 14:21 ` Nishanth Menon
2016-04-19 14:21 ` Nishanth Menon
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=5715B5EC.2040000@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nm@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 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.