Messages in this thread | | | Date | Fri, 4 May 2007 20:46:27 +0200 | From | "Antonino Ingargiola" <> | Subject | Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug] |
| |
On 5/4/07, Paul Fulghum <paulkf@microgate.com> wrote: > On Fri, 2007-05-04 at 19:25 +0200, Antonino Ingargiola wrote: > > > No. Ehmm ... I've an usb keybord and vga monitor on a standard desktop pc. > > OK, I'm stumped. > > I don't see how my patch could cause the machine to not boot > and I'm not seeing that behavior here.
I can boot it hitting SysReq+K, but only in text mode. X start but I can't do login (the mouse moves but I cant enter username and password). Furthermore if I hit some key in GDM I can't switch to text console anymore. If I switch to text-mode after boot all seems to work. Maybe this is related to some important process I kill with the SysReq key.
I'm quite confident the system blocks on "Setting consoles fonts and modes.", and thus during the boot script console-screen.h. I'll try to see which commands blocks...
BTW, I've tried the serial port in text mode. With the patch, flushing the input results effectively in a complete flush. However after doing the flush I can't read any char anymore without closing and reopening the port. I've verified this behavior both communicating between two serial port and both communicating with an usb-serial device (driver cdc-acm).
Regards,
~ Antonio - 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/
| |