On Monday 09 April 2007 17:15, Levend Sayar wrote:
> Denis,
> 
> Here is the tail of the log :
> 
> KLOG: readtoken called
> KLOG: xxreadtoken called
> KLOG: pgetc called
> KLOG: preadbuffer called
> KLOG: preadfd called
> KLOG: safe_read(0,..) calling
> rs_interrupt_single(4)... /d
> rs_interrupt_single(4)... e
> rs_interrupt_single(4)... v
> rs_interrupt_single(4)... /
> rs_interrupt_single(4)... tt
> rs_interrupt_single(4)... y
> rs_interrupt_single(4)... S
> rs_interrupt_single(4)... 0
> rs_interrupt_single(4)...
> 
> rs_interrupt_single(4)...
> rs_interrupt_single(4)... re
> rs_interrupt_single(4)... ad
> rs_interrupt_single(4)... ..
> rs_interrupt_single(4)... .
> rs_interrupt_single(4)...
> 
> readlink(/proc/self/fd/0) -> /dev/ttyS0 as you see.
> And what we see is just "read..." from safe_read.

Seems that input data doesn't make it to the userspace.
There were changes in tty handling which similarly bit me too:

http://lkml.org/lkml/2005/6/2/91
http://lkml.org/lkml/2005/6/3/70

Hope this helps.
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox

Reply via email to