Messages in this thread | | | Subject | Re: bug seen with dynticks from CONFIG_HARDIRQS_SW_RESEND | From | Thomas Gleixner <> | Date | Thu, 17 May 2007 12:10:59 +0200 |
| |
On Wed, 2007-05-16 at 18:20 -0500, Woodruff, Richard wrote: > The crashes were because the frame pointer per_cpu____irq_regs value was > 0. That code does a user_mode(get_irq_regs()). Currently regs is set > only upon real hardware entry on an irq. > > The crash path shows resend_irqs() could be called with in a context > where set_irq_regs() was not executed. In one specific case this was > from > softirq->tasklet_action(resend_tasklet)->resend_irqs->handle_level_irq-> > handle_IRQ_event->...->profile_tick. > > It seems anyone calling kernel/irq/manage.c:enable_irq() at the wrong > time can trigger this crash.
which code is disabling / enabling the timer interrupt ?
tglx
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |