virtual serial port infinite loop problem

virtual serial port infinite loop problem

[Jeff Backus]

Hey folks, I've got a bit of an issue.  I am trying to use the virtual 
serial port feature in order to use an old DOS bbs door under linux. 
Looking at the out put log, it seems to boot up fine to a point, but then 
once you hit a key, the log goes crazy, dumping the same four lines over 
and over.  That is with debug "+s" in the log.  With out the +s, the log 
doesn't go crazy.  This is even when I'm not running anything that 
accesses the serial port under dos(i.e. normal start up with 
com_1="virtual").  The whole time, the screen remains blank.

I am using dosemu 1.2.2(obtained and compiled from 
dosemu-1.2.2-1.src.rpm).  The problem persists, whether I use 
FreeDos(packaged in the rpm) or DR DOS 7.02.  At the bottom is the 
output log just before hitting a key(i.e. before it goes nuts), as well as 
the configuration file I'm using(sans comments), but here are some entries 
that I thought deserved highlighting:

The last line in the log before receiving "serial input" is:
SER0: INT14 0x0: Return with AL=0xb0 AH=0x6

and it would appear that here is where dosemu detects the input:
SERIAL: Async notification received
SER0: Got 1 bytes, 1 in buffer

and then this:
SER0: Func uart_fill requesting RX_INTR
SER0: tmp=0 int_cond=1 int_req=0 int=1
SER0: Interrupt 12 (1) cannot be requested: enable=0 IER=0x0
SER0: Got -1 bytes, 1 in buffer
(lather, rinse, repeat)

Lastly, earlier in the log is this line:
SER0: Interrupt 12 (8) cannot be requested: enable=0 IER=0x0

Dosemu is running on a K6/2 with fedora-core-3 with either of the 
following command lines:
dosemu.bin -fdosemu.conf -odosemu_out.txt -D+s
dosemu -fdosemu.conf -odosemu_out.txt -D+s

Lastly, even though there is an issue in the logs with the tty lock, I ran 
it again with $_ttylocks = "/tmp/locks/" (where /tmp/locks was an actual 
directory), and the log entry went away, but everything else remained the 
same, as far as I could tell.

Any ideas?

jeff
jsbackus@ncsu.edu

(<< Begin DOSEMU.CONF >>)

$_mouse_internal=(off)
$_com1="virtual"

(<< End DOSEMU.CONF >>)

(<< Begin LOG OUTPUT >>)
CONF: config variable parser_version_3 set
CONF: config variable c_system set
CONF: Parsing built-in dosemu.conf file.
CONF: config variable version_3_style_used set
CONF: Parsing built-in global.conf file.
CONF: config variable version_3_style_used unset
CONF: config variable version_3_style_used set
CONF: opened include file /etc/dosemu/dosemu.conf
CONF: closed include file /etc/dosemu/dosemu.conf
CONF: opened include file dosemu.conf
CONF: closed include file dosemu.conf
CONF: config variable skip_dosrc set
debug flags: -a+cw
CONF: Disabling use of pentium timer
CONF: dosbanner on
CONF: timer freq=18, update=54925
CONF: CPU set to 386
CONF: 8192k bytes XMS memory
CONF: 2048k bytes EMS memory
CONF: EMS-frame = 0xe000
CONF: DPMI-Server on
CONF: dosemu running on _xterm
SER: directory /var/lock namestub LCK.. binary No
SER: /dev/pts/3 port 0 int 0
CONF: Keyboard-layout keyb-user
ERROR: Unable to open console to evaluate the keyboard map.
Please specify your keyboard map explicitly via the $_layout option
CONF: Keyboard-layout us
CONF: **** Warning: floppy /dev/fd0 not accessable, disabled
CONF: fastfloppy = 1
CONF: IPX support off
CONF(LPT0) f: (null)   c: lpr  o: -Plp  t: 20  port: 0
CONF: not allowing speaker port access
CONF: Packet Driver disabled.
device: /home/jeff/.dosemu/drives/a type 4 h: -1  s: -1   t: -1 drive C:
device: /home/jeff/.dosemu/drives/c type 4 h: -1  s: -1   t: -1 drive D:
device: /home/jeff/.dosemu/drives/d type 0 header_size: 128 h: -1  s: -1 
t: -1 drive E:
CONF: config variable c_system unset
debug flags: +s
CONF: mostly running as USER: uid=500 (cached 500) gid=500 (cached 500)
DBG_FD already set
DOSEMU-1.2.2.0 is coming up on Linux version 2.6.9-1.667
CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K))
CONF: reserving 64Kb at 0xF0000 for 'r' (Dosemu reserved area)
CPU: Stack bottom 0xbfffb000, top 0xc0000000, esp=0xbffff800
major = 136 minor = 3
CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory)
SERIAL $Header: /cvsroot/dosemu/dosemu/src/base/serial/ser_init.c,v 
1.1.2.5 2004/02/10 00:36:26 bartoldeman Exp $
SER: Running serial_init, 1 serial ports
registering /dev/pts/3 for serial
SER0: enabling interrupt 12
SER0: COM1, intlevel=12, base=0x3f8, device=/dev/pts/3
SER0: BIOS memory location 0x400 has value of 0x3f8
CONF: reserving 64Kb at 0xE0000 for 'E' (EMS page frame)
TIME: using 9154 usec for updating ALRM timer
SER0: INT14 0x0: Initialize port 0, AL=0xa3
SER0: Running ser_open, fd=-1
DOSEMU: tty_lock: can't reopen to delete: Permission denied
SER0: Clear FIFO.
SER0: tmp=0 int_cond=0 int_req=0 int=0
SER0: do_ser_init: running ser_termios
SER0: LCR = 0x3, 8N1, bps = 2400, divisor 0x30 -> 0x30
SER0: Modem Status Change: MSR -> 0xb0
SER0: Func modstat_engine requesting MS_INTR
SER0: tmp=0 int_cond=8 int_req=0 int=8
SER0: Interrupt 12 (8) cannot be requested: enable=0 IER=0x0
SER0: Read LCR = 0x3
SER0: MCR = 0x3
SER0: MCR: DTR -> 1
SER0: MCR: RTS -> 2
SER0: LCR = 0x83, DLAB high.
SER0: Divisor LSB = 0x30
SER0: Divisor MSB = 0x0
SER0: LCR = 0x3, DLAB low.
SER0: LCR = 0x3, 8N1, bps = 2400, divisor 0x30 -> 0x30
SER0: Read LSR = 0x60
SER0: tmp=0 int_cond=0 int_req=0 int=0
SER0: Read MSR = 0xbb
SER0: INT14 0x0: Return with AL=0xbb AH=0x60
SER0: INT14 0x0: Initialize port 0, AL=0xa3
SER0: Read LCR = 0x3
SER0: MCR = 0x3
SER0: MCR: DTR -> 1
SER0: MCR: RTS -> 2
SER0: LCR = 0x83, DLAB high.
SER0: Divisor LSB = 0x30
SER0: Divisor MSB = 0x0
SER0: LCR = 0x3, DLAB low.
SER0: LCR = 0x3, 8N1, bps = 2400, divisor 0x30 -> 0x30
SER0: Read LSR = 0x60
SER0: tmp=0 int_cond=0 int_req=0 int=0
SER0: Read MSR = 0xb0
SER0: INT14 0x0: Return with AL=0xb0 AH=0x60
(<< End LOG OUTPUT >>)

Re: virtual serial port infinite loop problem

[Stas Sergeev]

Hello.

Jeff Backus wrote:
> I am using dosemu 1.2.2(obtained and compiled from
> dosemu-1.2.2-1.src.rpm).  The problem persists, whether I use
> DOSEMU: tty_lock: can't reopen to delete: Permission denied
Try the CVS code before anything else.
At least your problem with lockfiles
is no longer there, so you should set
$_ttylocks back to its initial state.
If the problem is still there, open a
bug-report at BTS and attach the full
-D9+sc log to it.