From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/26] ARM: OMAP2+: PRCM cleanups for 3.18 merge window
Date: Tue, 23 Sep 2014 09:14:41 -0700 [thread overview]
Message-ID: <20140923161440.GE2451@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409191726050.22526@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [140919 10:28]:
> On Fri, 19 Sep 2014, Paul Walmsley wrote:
>
> > However, I saw the following crash at boot on 37xxevm during one of
> > the boot test. Ran thirty more boot tests afterwards on that board
> > and it did not recur. It seems unlikely that the problem is related
> > to this series, but looks like we may have some intermittent boot
> > failure or race on 37xx :-(
>
> ...
>
> > [ 4.892211] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa318034
> > [ 4.900299] Internal error: : 1028 [#1] SMP ARM
> > [ 4.905090] Modules linked in:
> > [ 4.908325] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.17.0-rc5-12866-g0164b2d #1
> > [ 4.916320] task: c0835db0 ti: c082a000 task.ti: c082a000
> > [ 4.922027] PC is at omap2_gp_timer_set_next_event+0x24/0x78
> > [ 4.928009] LR is at clockevents_program_event+0xc0/0x148
> > [ 4.933715] pc : [<c002622c>] lr : [<c00a2800>] psr: 00000193
> > [ 4.933715] sp : c082bed8 ip : 00000000 fp : 00000000
> > [ 4.945800] r10: 00000000 r9 : 24101100 r8 : c0839080
> > [ 4.951324] r7 : 00000001 r6 : 237bc339 r5 : 0000009f r4 : 3d9759e7
> > [ 4.958190] r3 : fa318034 r2 : c08cb920 r1 : 00000003 r0 : fffffec1
> > [ 4.965087] Flags: nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel
> > [ 4.972900] Control: 10c5387d Table: 80004019 DAC: 00000015
> > [ 4.978942] Process swapper/0 (pid: 0, stack limit = 0xc082a248)
> > [ 4.985290] Stack: (0xc082bed8 to 0xc082c000)
> > [ 4.989868] bec0: 237bc339 00000001
> > [ 4.998504] bee0: 00000001 24101100 00000001 cfc7d6c8 00000001 cfc7da50 cfc7d720 c00a4780
> > [ 5.007141] bf00: 00000000 c00962b0 cfc7d720 c0096180 00000001 00000000 00000001 c08256c8
> > [ 5.015777] bf20: c082a000 c08256c8 00000000 c00962b0 237b4c04 00000001 00000002 a0000193
> > [ 5.024414] bf40: 00989680 00000000 00000000 24101100 00000001 cfc7da50 00000000 c108cc78
> > [ 5.033020] bf60: 00000000 c00962b0 00000000 00000002 00000001 00000000 c108cc78 c00a56f0
> > [ 5.041656] bf80: 00000000 00000002 237b4c04 00000001 c08c8ce8 c082a000 00000000 c08c8ce8
> > [ 5.050292] bfa0: c08329dc c0832978 cfc7f0f8 c0072808 c0559928 c08270f0 c08caf40 c080fdc0
> > [ 5.058929] bfc0: 00000000 c07c3b74 ffffffff ffffffff c07c35f0 00000000 00000000 c080fdc0
> > [ 5.067535] bfe0: c08cb154 c0832968 c080fdbc c083763c 80004059 80008074 00000000 00000000
> > [ 5.076171] [<c002622c>] (omap2_gp_timer_set_next_event) from [<c00a2800>] (clockevents_program_event+0xc0/0x148)
> > [ 5.087005] [<c00a2800>] (clockevents_program_event) from [<c00a4780>] (tick_program_event+0x44/0x54)
> > [ 5.096771] [<c00a4780>] (tick_program_event) from [<c0096180>] (__hrtimer_start_range_ns+0x3c0/0x4a0)
> > [ 5.106597] [<c0096180>] (__hrtimer_start_range_ns) from [<c00962b0>] (hrtimer_start_range_ns+0x24/0x2c)
> > [ 5.116577] [<c00962b0>] (hrtimer_start_range_ns) from [<c00a56f0>] (tick_nohz_idle_exit+0x140/0x1ec)
> > [ 5.126342] [<c00a56f0>] (tick_nohz_idle_exit) from [<c0072808>] (cpu_startup_entry+0xf4/0x2d0)
> > [ 5.135528] [<c0072808>] (cpu_startup_entry) from [<c07c3b74>] (start_kernel+0x340/0x3a8)
> > [ 5.144165] [<c07c3b74>] (start_kernel) from [<80008074>] (0x80008074)
> > [ 5.151031] Code: 13a0c000 0a000004 ee07cfba e592301c (e5931000)
> > [ 5.157470] ---[ end trace f92de024d996d904 ]---
> > [ 5.162353] Kernel panic - not syncing: Attempted to kill the idle task!
> > [ 5.169433] ---[ end Kernel panic - not syncing: Attempted to kill the idle task!
>
> Actually it just occurred to me that if something broke
> *wait_target_ready(), we'd expect to see intermittent failures like this,
> and this series touches *wait_target_ready(). So it might be worth taking
> a look at that with a magnifying glass to make sure that it's working.
Yes errors like this should not happen. Let's make sure things are
working reliably before merging this.
Regards,
Tony
next prev parent reply other threads:[~2014-09-23 16:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 18:08 [PATCH 00/26] ARM: OMAP2+: PRCM cleanups for 3.18 merge window Tero Kristo
2014-09-01 18:08 ` [PATCH 01/26] ARM: DRA7: PRM: add voltage processor check behind a prm_feature flag Tero Kristo
2014-09-01 18:08 ` [PATCH 02/26] ARM: AM43XX: PRM: use OMAP4 PRM driver Tero Kristo
2014-09-01 18:08 ` [PATCH 03/26] ARM: OMAP2/3: hwmod: merge wait_target_ready functions for omap2/3 Tero Kristo
2014-09-01 18:08 ` [PATCH 04/26] ARM: AM33xx/OMAP4+: CM: remove cdoffs parameter from wait_module_idle/ready Tero Kristo
2014-09-01 18:08 ` [PATCH 05/26] ARM: OMAP4/AM33xx: add cm_init / cm_exit calls for AM33xx and OMAP4+ Tero Kristo
2014-09-01 18:08 ` [PATCH 06/26] ARM: OMAP2+: CM: add common API for cm_wait_module_ready Tero Kristo
2014-09-01 18:08 ` [PATCH 07/26] ARM: OMAP4+/AM33xx: CM: add common API for cm_wait_module_idle Tero Kristo
2014-09-01 18:08 ` [PATCH 08/26] ARM: OMAP2+: CM: make clkdm_hwsup operations static Tero Kristo
2014-09-01 18:08 ` [PATCH 09/26] ARM: OMAP2+: CM: add common APIs for cm_module_enable/disable Tero Kristo
2014-09-01 18:08 ` [PATCH 10/26] ARM: OMAP2/3: CM: make cm_split_idlest_reg SoC calls static Tero Kristo
2014-09-01 18:09 ` [PATCH 11/26] ARM: AM33xx: hwmod: remove am33xx specific module SoC opts Tero Kristo
2014-09-01 18:09 ` [PATCH 12/26] ARM: AM43xx: hwmod: use OMAP4 hardreset ops instead of the AM33xx version Tero Kristo
2014-09-01 18:09 ` [PATCH 13/26] ARM: AM33xx: PRM: add support for prm_init Tero Kristo
2014-09-01 18:09 ` [PATCH 14/26] ARM: OMAP2+: PRM: add generic API for asserting hardware reset Tero Kristo
2014-09-01 18:09 ` [PATCH 15/26] ARM: OMAP2+: PRM: add generic API for deasserting " Tero Kristo
2014-09-01 18:09 ` [PATCH 16/26] ARM: OMAP2+: PRM: add generic API for checking hardreset status Tero Kristo
2014-09-01 18:09 ` [PATCH 17/26] ARM: OMAP4: CM: move public definitions from cminst44xx.h to cm44xx.h Tero Kristo
2014-09-01 18:09 ` [PATCH 18/26] ARM: OMAP4: CM: make cminst direct register access functions static Tero Kristo
2014-09-01 18:09 ` [PATCH 19/26] ARM: OMAP4+: CM: remove omap4_cm1/cm2_* functions Tero Kristo
2014-09-01 18:09 ` [PATCH 20/26] ARM: AM33xx: PRM: move global warm reset implementation to driver Tero Kristo
2014-09-01 18:09 ` [PATCH 21/26] ARM: AM33xx: PRM: make direct register access functions static Tero Kristo
2014-09-01 18:09 ` [PATCH 22/26] ARM: OMAP4: PRM: make omap4_prm_read/write_inst_reg calls static Tero Kristo
2014-09-01 18:09 ` [PATCH 23/26] ARM: OMAP3: PRM: make PRCM interrupt handler related functions static Tero Kristo
2014-09-01 18:09 ` [PATCH 24/26] ARM: OMAP4: " Tero Kristo
2014-09-01 18:09 ` [PATCH 25/26] ARM: OMAP3+: PRM: add generic API for reconfiguring I/O chain Tero Kristo
2014-09-01 18:09 ` [PATCH 26/26] ARM: OMAP2+: PRM: provide generic API for system reset Tero Kristo
2014-09-18 17:16 ` [PATCH 00/26] ARM: OMAP2+: PRCM cleanups for 3.18 merge window Tony Lindgren
2014-09-18 19:16 ` Tony Lindgren
2014-09-19 16:38 ` Paul Walmsley
2014-09-19 17:27 ` Paul Walmsley
2014-09-23 16:14 ` Tony Lindgren [this message]
2014-09-24 9:04 ` Tero Kristo
2014-10-02 16:32 ` Tony Lindgren
2014-10-02 19:52 ` Tony Lindgren
2014-10-02 20:17 ` Felipe Balbi
2014-10-02 21:19 ` Tony Lindgren
2014-10-02 21:59 ` Felipe Balbi
2014-10-03 14:49 ` Felipe Balbi
2014-10-03 15:46 ` Tony Lindgren
2014-09-19 20:12 ` Nishanth Menon
2014-09-19 15:47 ` Paul Walmsley
2014-09-19 16:30 ` Paul Walmsley
2014-09-22 13:19 ` Tero Kristo
2014-09-23 16:08 ` Tony Lindgren
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=20140923161440.GE2451@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).