Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1462561 > unrolled thread
| Started by | Chen-Yu Tsai <wens@csie.org> |
|---|---|
| First post | 2016-08-15 08:00 +0200 |
| Last post | 2016-08-16 12:30 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function Chen-Yu Tsai <wens@csie.org> - 2016-08-15 08:00 +0200
Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function Rask Ingemann Lambertsen <ccc94453@vip.cybercity.dk> - 2016-08-15 23:00 +0200
Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function Daniel Lezcano <daniel.lezcano@linaro.org> - 2016-08-16 12:30 +0200
| From | Chen-Yu Tsai <wens@csie.org> |
|---|---|
| Date | 2016-08-15 08:00 +0200 |
| Subject | [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function |
| Message-ID | <s6j6h-1AG-3@gated-at.bofh.it> |
The bootloader (U-boot) sometimes uses this timer for various delays. It uses it as a ongoing counter, and does comparisons on the current counter value. The timer counter is never stopped. In some cases when the user interacts with the bootloader, or lets it idle for some time before loading Linux, the timer may expire, and an interrupt will be pending. This results in an unexpected interrupt when the timer interrupt is enabled by the kernel, at which point the event_handler isn't set yet. This results in a NULL pointer dereference exception, panic, and no way to reboot. Clear any pending interrupts after we stop the timer in the probe function to avoid this. Cc: stable@vger.kernel.org Signed-off-by: Chen-Yu Tsai <wens@csie.org> --- Changes since v1: - Add stable kernel to Cc. --- drivers/clocksource/sun4i_timer.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/clocksource/sun4i_timer.c b/drivers/clocksource/sun4i_timer.c index 97669ee4df2a..7ab69b36f744 100644 --- a/drivers/clocksource/sun4i_timer.c +++ b/drivers/clocksource/sun4i_timer.c @@ -208,6 +208,9 @@ static int __init sun4i_timer_init(struct device_node *node) /* Make sure timer is stopped before playing with interrupts */ sun4i_clkevt_time_stop(0); + /* clear timer0 interrupt */ + writel(0x1, timer_base + TIMER_IRQ_ST_REG); + sun4i_clockevent.cpumask = cpu_possible_mask; sun4i_clockevent.irq = irq; -- 2.8.1
[toc] | [next] | [standalone]
| From | Rask Ingemann Lambertsen <ccc94453@vip.cybercity.dk> |
|---|---|
| Date | 2016-08-15 23:00 +0200 |
| Subject | Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function |
| Message-ID | <s6x9f-1ZP-3@gated-at.bofh.it> |
| In reply to | #1462561 |
On Mon, Aug 15, 2016 at 12:57:04PM +0800, Chen-Yu Tsai wrote: > The bootloader (U-boot) sometimes uses this timer for various delays. > It uses it as a ongoing counter, and does comparisons on the current > counter value. The timer counter is never stopped. > > In some cases when the user interacts with the bootloader, or lets > it idle for some time before loading Linux, the timer may expire, > and an interrupt will be pending. This results in an unexpected > interrupt when the timer interrupt is enabled by the kernel, at > which point the event_handler isn't set yet. This results in a NULL > pointer dereference exception, panic, and no way to reboot. Thanks for tracking down this bug. It bit me too once. Now I won't wonder if it was my fault. I do wonder if there are more interrupts which need their pending status cleared in the probe function. -- Rask Ingemann Lambertsen
[toc] | [prev] | [next] | [standalone]
| From | Daniel Lezcano <daniel.lezcano@linaro.org> |
|---|---|
| Date | 2016-08-16 12:30 +0200 |
| Subject | Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function |
| Message-ID | <s6JN8-1Ri-23@gated-at.bofh.it> |
| In reply to | #1462561 |
On 08/15/2016 06:57 AM, Chen-Yu Tsai wrote: > The bootloader (U-boot) sometimes uses this timer for various delays. > It uses it as a ongoing counter, and does comparisons on the current > counter value. The timer counter is never stopped. > > In some cases when the user interacts with the bootloader, or lets > it idle for some time before loading Linux, the timer may expire, > and an interrupt will be pending. This results in an unexpected > interrupt when the timer interrupt is enabled by the kernel, at > which point the event_handler isn't set yet. This results in a NULL > pointer dereference exception, panic, and no way to reboot. > > Clear any pending interrupts after we stop the timer in the probe > function to avoid this. > > Cc: stable@vger.kernel.org > Signed-off-by: Chen-Yu Tsai <wens@csie.org> > --- > Changes since v1: > > - Add stable kernel to Cc. > --- > drivers/clocksource/sun4i_timer.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/clocksource/sun4i_timer.c b/drivers/clocksource/sun4i_timer.c > index 97669ee4df2a..7ab69b36f744 100644 > --- a/drivers/clocksource/sun4i_timer.c > +++ b/drivers/clocksource/sun4i_timer.c > @@ -208,6 +208,9 @@ static int __init sun4i_timer_init(struct device_node *node) > /* Make sure timer is stopped before playing with interrupts */ > sun4i_clkevt_time_stop(0); > > + /* clear timer0 interrupt */ > + writel(0x1, timer_base + TIMER_IRQ_ST_REG); Can you replace this call with a static inline function and reuse it also in 'sun4i_timer_interrupt' ? Thanks. -- Daniel -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web