>Number:         12985
>Category:       port-i386
>Synopsis:       1.5V i386: serial ports freeze
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 19 18:21:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jim Bernard
>Release:        May 19, 2001
>Organization:
>Environment:
System: NetBSD zoo 1.5V NetBSD 1.5V (ZOO-$Revision: 1.63 $) #0: Sat May 19 12:50:45 MDT 2001 jim@zoo:/home/tmp/compile/sys/arch/i386/compile/ZOO i386
Architecture: i386
Machine: i386
>Description:
	I'm using ppp over a dialup link, with an internal 56K modem.
	I start up netscape, the link comes up (or bring the link up
	first), I load a couple of pages, and then the (serial) mouse
	freezes and the ppp connection becomes inoperable.  There's no
	further communation possible over the link (ping fails, dns fails,
	netscape doesn't successfully load the page, etc.).  Otherwise,
	the system seems fine.  If the mouse cursor is in a window, I
	can execute commands in that window.  I can log in on another
	virtual terminal and do things.  If I try to hang up the connection
	(after killing netscape) via "kill -HUP" to pppd, I get:

	  tcsetattr: interrupted system call

	but a "kill -9" will kill it.  I can then open the port with
	kermit:

	  kermit -l /dev/dty02 -b 57600

	and it will appear to connect, but I can't communicate with the
	modem (no characters appear on screen when I type commands).
	When I try to quit from kermit, I get:

	  Closing /dev/dty02...ttclos() timeout: hangup
	  ttclos() timeout: reset
	  OK

	The local ethernet is still working through all this, BTW.
	The only way to get the serial devices back is to reboot.  (Killing
	and restarting X doesn't fix the mouse.)

	The kernel was built from -current sources updated via cvs early
	this morning (MDT).  But I first observed the problem this morning
	with a kernel built one week ago (May 12), which had been running
	without incident all week (evidently I had never tried to use
	netscape during the week).

	The kernel I was using up until May 12 (1.5S, built March 15)
	doesn't have this problem.

	The modem is com2 (dty02) and the mouse is on com0 (tty00).
	Netscape is: communicator-4.77 from pkgsrc.

	Here are some probe messages:
NetBSD 1.5V #0: Sat May 19 12:50:45 MDT 2001
cpu0: Intel Pentium (P54C) (586-class), 99.48 MHz
cpu0: features 1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
total memory = 32380 KB
avail memory = 26780 KB
using 430 buffers containing 1720 KB of memory
BIOS32 rev. 0 found at 0xf0380
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82437FX System Controller (TSC) (rev. 0x01)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371FB PCI-to-ISA Bridge (PIIX) (rev. 0x02)
pciide0 at pci0 dev 7 function 1: Intel 82371FB IDE controller (PIIX) (rev. 0x02)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
wd0 at pciide0 channel 0 drive 0: <WDC AC310200R>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 9787 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 20044080 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel ignored (disabled)
de0 at pci0 dev 9 function 0
de0: interrupting at irq 15
de0: DEC 21040 [10Mb/s] pass 2.3
de0: address 08:00:2b:e5:60:70
vga1 at pci0 dev 10 function 0: ATI Technologies Mach64 GX (rev. 0x01)
wsdisplay0 at vga1: console (80x25, vt100 emulation)
siop0 at pci0 dev 11 function 0: Symbios Logic 53c810 (fast scsi)
siop0: interrupting at irq 9
scsibus0 at siop0: 8 targets, 8 luns per target
tlp0 at pci0 dev 12 function 0: Macronix MX98715AEC-x Ethernet, pass 2.5
tlp0: interrupting at irq 10
tlp0: Ethernet address 00:80:c6:f9:c9:54
tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
lpt0 at isa0 port 0x378-0x37b irq 7
lpt1 at isa0 port 0x278-0x27b: polled
pcppi0 at isa0 port 0x61
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0: read port 0x203
com2 at isapnp0 port 0x3e8/8 irq 5: ns16550a, working fifo
biomask 7b45 netmask ff45 ttymask ffc7


>How-To-Repeat:
	See above.

>Fix:
	Unknown, but I seem to recall seeing some recent fiddling with
	the com driver.
>Release-Note:
>Audit-Trail:
>Unformatted: