Re: Serial related oops
- From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
- Date: Mon, 19 Feb 2007 20:51:53 +0000
On Mon, Feb 19, 2007 at 12:37:00PM -0800, Michael K. Edwards wrote:
What we've seen on our embedded ARM is that enabling an interrupt that
is shared between multiple UARTs, at a stage when you have not set up
all the data structures touched by the ISR and softirq, can have
horrible consequences, including soft lockups and fandangos on core.
Incorrect. We have:
1. registered an interrupt handler at this point.
2. disabled interrupts (we're under the spin lock)
So, no interrupt will be seen by the CPU since the interrupt is masked.
The test is intentionally designed to be safe from the interrupt
generation point of view.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
-
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/
- Follow-Ups:
- Re: Serial related oops
- From: Michael K. Edwards
- Re: Serial related oops
- References:
- Serial related oops
- From: Frederik Deweerdt
- Re: Serial related oops
- From: Russell King
- Re: Serial related oops
- From: Frederik Deweerdt
- Re: Serial related oops
- From: Russell King
- Re: Serial related oops
- From: Frederik Deweerdt
- Re: Serial related oops
- From: Russell King
- Re: Serial related oops
- From: Jose Goncalves
- Re: Serial related oops
- From: Russell King
- Re: Serial related oops
- From: Jose Goncalves
- Re: Serial related oops
- From: Michael K. Edwards
- Serial related oops
- Prev by Date: Re: GPL vs non-GPL device drivers
- Next by Date: Re: GPL vs non-GPL device drivers
- Previous by thread: Re: Serial related oops
- Next by thread: Re: Serial related oops
- Index(es):
Relevant Pages
|