From owner-freebsd-isp Thu May 16 16:49:22 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA17339 for isp-outgoing; Thu, 16 May 1996 16:49:22 -0700 (PDT) Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA17326 for ; Thu, 16 May 1996 16:49:17 -0700 (PDT) Received: (from boot@localhost) by itchy.mosquito.com (8.6.11/8.6.12) id TAA20817; Thu, 16 May 1996 19:50:49 -0400 From: Bruce Bauman Message-Id: <199605162350.TAA20817@itchy.mosquito.com> Subject: locked-up modem To: portmaster-users@livingston.com Date: Thu, 16 May 1996 19:50:49 -0400 (EDT) Cc: freebsd-isp@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We are using Livingston Portmaster 2E-30s with ComOS 3.3.1. We have 30 USR Sportsters attached, some 28.8 and some 33.6. Once in a while, we see a modem "lock up". The symptoms are that all of the lights on the modem are lit up solidly, and rlogind on our FreeBSD box eats up a fair amount of CPU. This only happens to shell account users. Is this a problem anyone has seen before? It only appears to happen to one specific customer, which seems weird. Any hints on how to figure this out? -- Bruce