Re: Interrupts disabled for too long in printk

["Jon Smirl" <jonsmirl@gmail.com>]

On 6/7/06, Mathieu Desnoyers <compudj@krystal.dyndns.org> wrote:
> * Jon Smirl (jonsmirl@gmail.com) wrote:
> > You can look at this problem from the other direction too. Why is it
> > taking 15ms to get between the two points? If IRQs are off how is the
> > serial driver getting interrupts to be able to display the message? It
> > is probably worthwhile to take a look and see what the serial console
> > driver is doing.
>
> Hi John,
>
> The serial port is configured at 38000 bauds. It can therefore transmit 4800
> bytes per seconds, for 72 characters in 15 ms. So the console driver would be
> simply busy sending characters to the serial port during that interrupt
> disabling period.

Why can't the serial console driver record the message in a buffer at
the point where it is being called with interrupts off, and then let
the serial port slowly print it via interupts? It sounds to me like
the serial port is being driven in polling mode.

> Mathieu
>
> OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
> Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68


--
Jon Smirl
jonsmirl@gmail.com
-
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/