Bug#408635: slattach only works every other time
On Sat, Jan 27, 2007 at 03:06:13PM +0100, Martin Fuzzey wrote:
> debian-qemu:~# slattach -L -vd -p slip -s 115200 /dev/ttyS0
> slattach: tty_open: looking for lock
> slattach: tty_open: trying to open /dev/ttyS0
> slattach: tty_open: /dev/ttyS0 (fd=3) slattach: tty_set_speed: 115200
> slattach: tty_set_databits: 8
> slattach: tty_set_stopbits: 1
> slattach: tty_set_parity: N
> slip started on /dev/ttyS0 interface sl0
>
> Above is OK, now kill process with CTRL-C
>
> slattach: tty_set_speed: 0
> debian-qemu:~#
> debian-qemu:~# slattach -L -vd -p slip -s 115200 /dev/ttyS0
> slattach: tty_open: looking for lock
> slattach: tty_open: trying to open /dev/ttyS0
> slattach: tty_open: /dev/ttyS0 (fd=3) slattach: tty_set_speed: 115200
> slattach: tty_set_databits: 8
> slattach: tty_set_stopbits: 1
> slattach: tty_set_parity: N
> SLIP_set_disc(1): File exists
> debian-qemu:~#
> debian-qemu:~# dmesg
> Gives trace shown above
>
> Note that the same problem occurs on real hardware not just qemu (I'm submitting this from home and my etch system doesn't have a serial port)
hey Martin,
Thanks for your detailed investigation.
Can you reproduce with the latest trunk builds? I didn't see any
changesets upstream that obviously fix this issue, but just in case...
Trunk builds can be installed from here:
deb http://kernel-archive.buildserver.net/debian-kernel trunk main
If you can still reproduce, we should file it upstream
(http://bugzilla.kernel.org).
--
dann frazier
Reply to: