Re: [RFC PATCH v2 0/3] genirq, serial: 8250: Workaround to avoid irq=0 for console

[Thomas Gleixner]

On Wed, 29 Jul 2015, Peter Hurley wrote:
> On 07/29/2015 06:32 AM, Thomas Gleixner wrote:
> > On Wed, 29 Jul 2015, Taichi Kageyama wrote:
> >> - Keep interrupt disabled on the CPU which is used to detect 
> >>   an interrupt during the timeout of autoconfig_irq().
> >>      + Kick printk() on the CPU which detects interrupt 
> >>        from a console serial port.
> > 
> > This is wrong to begin with. How is that supposed to work on an UP
> > machine? Not at all.
> > 
> > So no, fix the code which has interrupts disabled accross autoprobing
> > and do not try to apply bandaids somewhere else.
> 
> Like printk() from some unrelated driver?

If that's the cause for the wreckage then yes, we need a way to tell
the printk code not to call into the driver until that initialization
step is done. It's that simple.

Thanks,

	tglx
--
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/