Re: 2.5.45 odd deref in serial_in

From: Zwane Mwaikambo (zwane@holomorphy.com)
Date: Tue Nov 05 2002 - 04:20:00 EST


On Tue, 5 Nov 2002, Russell King wrote:

> a) have to rely on interrupts running

Not really ;) If i'm successful i may get this working albeit only for
specific boxes. Although we'd need an IDT at least, but interrupts may
remain masked...

> b) have to buffer the data somewhere, which may possibly fill up and
> then what do we do with the printk message
>
> Bear in mind that dropping random printk messages because we've filled
> a buffer isn't acceptable. Also note that the behaviour in this area
> hasn't changed since 2.4 times.
>
> Obviously, the way to reduce the time spent writing console messages to
> the serial port is to increase the baud rate. 8)

I'm runnning 115200 :P It looks like a race however because i don't always
trigger it, but when i do the trace is always the same. However i'm not
going to make you run circles for my potentially dodgy code.

Cheers,
        Zwane

-- 
function.linuxpower.ca

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



This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:37 EST