Re: [patch 1/2] tick/broadcast: Prevent deep idle states if no broadcast device available

[Thomas Gleixner]

On Mon, 6 Jul 2015, Sudeep Holla wrote:
> This triggered the below crash on boot, looks like it's accessing
> hrtimer->function which is null in periodic mode IIUC
> 
> Regards,
> Sudeep

Gah. I have no idea how that gets queued. /me goes off to tweak x86 to
emulate that crap.
 
> --->8
> 
> Bad mode in Synchronous Abort handler detected, code 0x86000005 -- IABT
> (current EL)
> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.2.0-rc1 #577
> Hardware name: ARM Juno development board (r0) (DT)
> task: ffffffc976900000 ti: ffffffc9768fc000 task.ti: ffffffc9768fc000
> PC is at 0x0
> LR is at bc_handler+0x20/0x58
> pc : [<0000000000000000>] lr : [<ffffffc00010f4a4>] pstate: a00001c5
> sp : ffffffc9768ffbd0
> 
> Call trace:
> [<          (null)>]           (null)
> [<ffffffc000101e88>] __hrtimer_run_queues+0xe0/0x150
> [<ffffffc0001028b4>] hrtimer_run_queues+0xb8/0xe8
> [<ffffffc000101714>] update_process_times+0x28/0x6c
> [<ffffffc00010d978>] tick_periodic+0x3c/0xb8
> [<ffffffc00010da1c>] tick_handle_periodic+0x28/0x94
> [<ffffffc0004d61d4>] arch_timer_handler_phys+0x28/0x38
> [<ffffffc0000f5964>] handle_percpu_devid_irq+0x74/0x9c
> [<ffffffc0000f1668>] generic_handle_irq+0x30/0x4c
> [<ffffffc0000f1984>] __handle_domain_irq+0x5c/0xac
> [<ffffffc0000824a8>] gic_handle_irq+0x30/0x80
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/