Date: Wed, 16 Apr 1997 10:07:07 -0400 From: Chris Shenton <cshenton@it.hq.nasa.gov> To: hackers@freebsd.org Subject: 2.2.1-R crash with looped serial gettys Message-ID: <199704161407.OAA02408@wirehead.it.hq.nasa.gov> In-Reply-To: Your message of "Wed, 16 Apr 1997 05:36:25 -0700 (PDT)" References: <199704161236.FAA24481@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I've built a little box for pppd/mpd and routing out of a 486sx33 and a whopping 8MB RAM; seems to mostly run fine with 2.2.1-RELEASE. It's a fairly minimal install (Kernel User option I think) and I rebuilt the kernel to fit the hardware. I've added a dual 16550A serial port card to which I'll connect a pair of modems. I have getty running on the ports, cuaa1 and cuaa2. PROBLEM: If I connect a null-modem cable between the ports, the system crashes within a couple seconds. It's repeatable. It leaves no message in /var/log/messages, or dmesg, and there's no core file. I presume looping the serial gettys is causing them to scream at each other "Login:"; "Invalid Login:"; no *you* login; dammit, `login' is not a valid login... and consumes too many resources. Not sure if there's an intelligent way to detect this and prevent it, but it did seem surprising that simply connecting a cable crashed the machine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704161407.OAA02408>