public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
	Lee Jones <lee@kernel.org>
Subject: Re: [PATCH V2 4/7] clocksource: bcm2835: Migrate to new 'set-state' interface
Date: Mon, 15 Jun 2015 20:57:16 -0600	[thread overview]
Message-ID: <557F908C.3010600@wwwdotorg.org> (raw)
In-Reply-To: <ca4714d7b04c0c8b99194ccb8504610e67ba7d95.1434095303.git.viresh.kumar@linaro.org>

On 06/12/2015 02:00 AM, Viresh Kumar wrote:
> Migrate bcm2835 driver to the new 'set-state' interface provided by
> the clockevents core, the earlier 'set-mode' interface is marked
> obsolete now.
> 
> This also enables us to implement callbacks for new states of clockevent
> devices, for example: ONESHOT_STOPPED.
> 
> We weren't doing anything in the ->set_mode() callback. So, this patch
> doesn't provide any set-state callbacks.

This generates a panic at boot (on top of 4.1.0-rc8+, which certainly at
least booted fine):

> [    0.008586] clocksource timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
> [    0.018080] ------------[ cut here ]------------
> [    0.022843] kernel BUG at kernel/time/clockevents.c:480!
> [    0.028299] Internal error: Oops - BUG: 0 [#1] ARM
> [    0.033237] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0-rc8+ #46
> [    0.039567] Hardware name: BCM2835
> [    0.043092] task: c06fb648 ti: c06f6000 task.ti: c06f6000
> [    0.048668] PC is at clockevents_register_device+0x15c/0x174
> [    0.054481] LR is at clockevents_config_and_register+0x2c/0x30
> [    0.060467] pc : [<c00665e0>]    lr : [<c00666b4>]    psr: 600001d3
> [    0.060467] sp : c06f7f18  ip : c0066498  fp : c06f7f34
> [    0.072243] r10: cdffc660  r9 : 410fb767  r8 : c06db128
> [    0.077611] r7 : 0000001b  r6 : f0003018  r5 : cde38ed4  r4 : cd422020
> [    0.084294] r3 : 00000002  r2 : 00000000  r1 : 000003e7  r0 : cd422020
> [    0.090979] Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
> [    0.098627] Control: 00c5387d  Table: 00004008  DAC: 00000015
> [    0.104521] Process swapper (pid: 0, stack limit = 0xc06f6188)
> [    0.110502] Stack: (0xc06f7f18 to 0xc06f8000)
> [    0.114993] 7f00:                                                       000003e7 cd422020
> [    0.123354] 7f20: cde38ed4 f0003018 c06f7f4c c06f7f38 c00666b4 c0066490 ffffffff cd422000
> [    0.131715] 7f40: c06f7f7c c06f7f50 c06c3358 c0066694 00000020 c03429ac c06f7f7c 000f4240
> [    0.140076] 7f60: cde38ed4 00000001 c06f7f84 ffffffff c06f7fa4 c06f7f80 c06c3124 c06c321c
> [    0.148436] 7f80: 00000001 c06f4ea0 ffffffff 00000000 00000001 c075aea0 c06f7fb4 c06f7fa8
> [    0.156798] 7fa0: c06988e4 c06c30dc c06f7ff4 c06f7fb8 c0695b90 c06988c0 ffffffff ffffffff
> [    0.165159] 7fc0: c06956e4 00000000 00000000 c06db128 c075b014 c06f8024 c06db124 c06fc910
> [    0.173518] 7fe0: 00004008 006d9fcc 00000000 c06f7ff8 00008074 c069597c 00000000 00000000
> [    0.181910] [<c00665e0>] (clockevents_register_device) from [<c00666b4>] (clockevents_config_and_register+0x2c/0x30)
> [    0.192661] [<c00666b4>] (clockevents_config_and_register) from [<c06c3358>] (bcm2835_timer_init+0x148/0x19c)
> [    0.202785] [<c06c3358>] (bcm2835_timer_init) from [<c06c3124>] (clocksource_of_init+0x54/0x98)
> [    0.211693] [<c06c3124>] (clocksource_of_init) from [<c06988e4>] (time_init+0x30/0x38)
> [    0.219798] [<c06988e4>] (time_init) from [<c0695b90>] (start_kernel+0x220/0x3a4)
> [    0.227459] [<c0695b90>] (start_kernel) from [<00008074>] (0x8074)
> [    0.233803] Code: e5943078 e3530000 1affffd5 eaffffd2 (e7f001f2) 
> [    0.240103] ---[ end trace cb88537fdc8fa200 ]---
> [    0.244866] Kernel panic - not syncing: Attempted to kill the idle task!
> [    0.251730] ---[ end Kernel panic - not syncing: Attempted to kill the idle task!


  reply	other threads:[~2015-06-16  2:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  8:00 [PATCH V2 0/7] clockevent: Migrate to new 'set-state' interface Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 1/7] clockevents: Allow set-state callbacks to be optional Viresh Kumar
2015-06-29  8:47   ` Daniel Lezcano
2015-06-29  9:15     ` Thomas Gleixner
2015-06-12  8:00 ` [PATCH V2 2/7] clocksource: arm_arch_timer: Migrate to new 'set-state' interface Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 3/7] clocksource: arm_global_timer: " Viresh Kumar
2015-06-12  8:22   ` Maxime Coquelin
2015-06-12  8:28     ` Viresh Kumar
2015-06-12  9:10   ` srini
2015-06-12  9:11     ` Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 4/7] clocksource: bcm2835: " Viresh Kumar
2015-06-16  2:57   ` Stephen Warren [this message]
2015-06-16  3:17     ` Viresh Kumar
2015-06-16  4:16       ` Stephen Warren
2015-06-16  4:19         ` Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 5/7] clocksource: bcm_kona: " Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 6/7] clocksource: cs5535: " Viresh Kumar
2015-06-12  8:00 ` [PATCH V2 7/7] clocksource: em_sti: " Viresh Kumar
2015-06-18  9:10 ` [PATCH V2 0/7] clockevent: " Daniel Lezcano
2015-06-18  9:14   ` Daniel Lezcano

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=557F908C.3010600@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=lee@kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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