Re: [patch] Re: Serial Oopsen caused by global IRQ chanes

William Lee Irwin III (wli@holomorphy.com)
Sat, 27 Jul 2002 16:01:50 -0700


On Sat, Jul 27, 2002 at 08:43:04PM +0200, Ingo Molnar wrote:
>> the attached patch fixes a synchronize_irq() bug: if the interrupt is
>> freed while an IRQ handler is running (irq state is IRQ_INPROGRESS) then

On Sat, Jul 27, 2002 at 03:36:17PM -0700, William Lee Irwin III wrote:
> I'm having trouble with this one, I seem to get lots of these messages:
> pu: 12, clocks: 99983, slice: 3029
> CPU12<T0:99968,T1:60576,D:15,S:3029,C:99983>
> CPU 12 IS NOW UP!

Sorry, this is the hotplug stuff which surprised me, but is unrelated
to any deadlock (unless it's printk'ing at a bad time, which I doubt).
Thought it was an arch complaint about trying to wake already-woken cpus.

On Sat, Jul 27, 2002 at 03:36:17PM -0700, William Lee Irwin III wrote:
> ... and then the kernel deadlocks after free_initmem()'s printk().

Seems to be timing related, printk's in init/main.c made it go away.
ISTR hearing something about hotplug merge troubles, I'll investigate
that thread and report results with the fixes posted there.

Cheers,
Bill
-
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/