Return to BSD News archive
Xref: sserve comp.unix.bsd.netbsd.misc:560 comp.os.386bsd.bugs:3082 Newsgroups: comp.unix.bsd.netbsd.misc,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nexus.coast.net!news.kei.com!news.mathworks.com!news.ultranet.com!news.sprintlink.net!noc.netcom.net!netcom.com!devtrix From: devtrix@netcom.com (Matthew B. Wood) Subject: MODEM trouble, process hangs... Message-ID: <devtrixDAMwF4.2xA@netcom.com> Organization: NETCOM (home of the NetCruiser! :^P ack!) X-Newsreader: TIN [version 1.2 PL1] Date: Fri, 23 Jun 1995 16:28:16 GMT Lines: 35 Sender: devtrix@netcom15.netcom.com WARNING: message is cross-posted to 'comp.unix.bsd.netbsd.misc' and 'comp.os.386bsd.bugs'! Please reply carefully. Here's the trouble: A friend and I recently installed NetBSD1.0 on a 486DX. After wrangling a disklabel process and the 1.3 Gig drive, things seem to be on track. The modem seems to be having trouble, though. We have started kermit, ignored DTR on modem, and quit out of kermit. Ran the 'slattach' process and things were cool, CSLIP running seemingly OK. (By the way, we wanted PPP, but it doesn't come with the default kernel! grumble...) Things seem OK until we start seeing 'silo overflow' errors. Which I assume is my old serial card (I just bought a 16550 UART, but I haven't installed it yet). And then, after getting back to the prompt (which isn't easy), we cannot kill the 'slattach' process! Running as root and kill -9, the damn process won't die. To me, that's scary. Thus, I think I should put in my new serial card for the 16byte buffering ability. Hopefully that will help the overflow errors. But not being able to kill a process in the background? What's up with that?! Does anyone know of bugs in the i386-port of the 1.0 kernel that cause trouble on tty's or cause tty processes to hang indefinitely? I read the patch list but none of them seem to describe this problem. Does anyone think the "current" release would fix this problem? Any and all info/help appreciated! +Matt