Subject: Recent problems with UUCP
To: None <port-i386@NetBSD.ORG>
From: Gerald C. Simmons <simmons@darykon.cet.com>
List: port-i386
Date: 10/09/1997 09:38:50
Recent update:

Changed to US Robotics Internal Modem. Still getting ERROR: Timed out waiting for packet", but
no lock-ups so far. I think the lock-up problem is related to the HAYES-ESP Board.

Gerry

--------------------------------------------------------------------------------------------------

Oct 7, 1997

I have had UUCP up and running on my machine for several years now, starting with ver 0.9a.
I just upgraded to 1.2.1, and am running into a interesting snag. 

I have a 66Mhz 486 System 32M RAM with an External Supra 28.8 modem interfaced to a
Hayes ESP serial port.

-Oct  7 08:17:48 dakkon /netbsd: com1 at isa0 port 0x2f8-0x2ff irq 3: ESP, 1024 byte fifo
-Oct  7 08:17:48 dakkon /netbsd: lpt0 at isa0 port 0x378-0x37f irq 7
-Oct  7 08:17:48 dakkon /netbsd: wdc0 at isa0 port 0x1f0-0x1f7 irq 14
-Oct  7 08:17:48 dakkon /netbsd: wd0 at wdc0 drive 0: 1549MB, 3148 cyl, 16 head, 63 sec, 512 by
tes/sec <WDC AC31600H>

The system works fine most of the time, save for getting "ERROR: Timed out waiting for packet"
occasionally on large news downloads. But, every once in a while uucico locks up so tight, I need
to reboot the system. Here are the messages:

-uucico legends news (1997-10-02 01:20:46.77 9830) ERROR: Got hangup signal 
-uucico legends news (1997-10-02 01:20:46.77 9830) ERROR: Can't set MIN for terminal: Interrupted
 system call
-uucico legends - (1997-10-02 01:20:46.77 9830) Call complete (918 seconds 2632986 bytes 2868 bps)
-uucico legends - (1997-10-02 02:05:01.56 10446) ERROR: System already locked
-uucico legends - (1997-10-02 03:05:00.84 12198) ERROR: System already locked
   .
   .
   .
-uucico legends - (1997-10-02 22:05:00.50 13087) ERROR: System already locked

Re-Boot initiated "shutdown -r now"

-uucico legends - (1997-10-07 08:09:51.45 9830) ERROR: Got termination signal
-uucico legends - (1997-10-07 08:09:51.46 9830) ERROR: Can't disable hardware flow control: Interrup
ted system call 
-uucico legends - (1997-10-07 08:09:53.46 9830) ERROR: write: Input/output error
-uucico legends - (1997-10-07 08:09:53.46 9830) ERROR: write: Input/output error

Now if I don't Power-down and Cold boot the system, uucico can't talk to the modem! I have to
initiate a Cold-boot. Then everything's fine.

-uucico legends - (1997-10-07 08:15:28.77 182) Calling system legends (port tty01)
-uucico legends - (1997-10-07 08:15:52.01 182) ERROR: Got termination signal 
alling system legends (port tty01)
uucico legends - (1997-10-07 08:19:33.60 182) Login successful
uucico legends - (1997-10-07 08:19:34.00 182) Handshake successful (protocol 'i' sending packet/wind
ow 1024/16 receiving 1024/16)
uucico legends mail (1997-10-07 08:19:39.95 182) Receiving rmail simmons@darykon.cet.com (2738 bytes
)
uucico legends mail (1997-10-07 08:19:40.40 182) Receiving rmail simmons@darykon.cet.com (2315 bytes
)
uucico legends mail (1997-10-07 08:19:43.17 182) Receiving rmail simmons@darykon.cet.com (2007 bytes
)

This stuff never happened when I was running 1.2. Any Ideas!

Gerry Simmons
simmons@darykon.cet.com