From owner-freebsd-questions Wed Nov 29 17:33:55 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA11339 for questions-outgoing; Wed, 29 Nov 1995 17:33:55 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA11334 for ; Wed, 29 Nov 1995 17:33:52 -0800 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id RAA10989 for ; Wed, 29 Nov 1995 17:33:42 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA13448; Thu, 30 Nov 1995 11:58:20 GMT From: Michael Smith Message-Id: <199511301158.LAA13448@genesis.atrad.adelaide.edu.au> Subject: Re: Strange Multi-port SIO behaviour To: awebster@dataradio.com (Andrew Webster) Date: Thu, 30 Nov 1995 11:58:19 +0000 () Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <199511291539.KAA05360@vhf.dataradio.com> from "Andrew Webster" at Nov 29, 95 10:40:27 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1957 Sender: owner-questions@FreeBSD.ORG Precedence: bulk Andrew Webster stands accused of saying: > > I've noticed on systems with AST/4 port and Digi PC/4/8 cards that > when a soft-reboot occurs (i.e. after crash/panic), the SIO ports are > not all initialized properly, whereas after a shutdown -r or reboot, > or cold boot the ports all init properly. Can you please note the state of the ports when their probes fail? In particular, DCD and rx status info are vital. Also, enable verbose probing (flags & 0x80) on all the ports, and let us know which tests fail. > I've looked at the sioprobe function in the sio.c module and there > appears to be lots of instances where the programmer added > EXTRA_DELAY? Has anyone else seen this problem? The EXTRA DELAY comments appear to be mostly pertinent to emulated serial ports on cheapo internal modems, but NOBODY HAS GOTTEN BACK TO ME ON THIS ONE 8( **GRR** > Appart from forcing the machine to reboot if all the sio ports are > not detected, is there a clean way to make sioprobe find all the > ports after a crash? At the moment, the problem _seems_ to be due to UARTs that are already initialised either receiving or still sending data, or possibly having DCD state change interrupts pending. It's probably worth adding code to the probe to try to hang modems up, and so forth, but it's not easy to guarantee a successful probe if the device is receiving data. It may simply be easier to add another flag bit that says "assume the port is there, regardless of the probe results" Comments, Bruce? > Andrew Webster Network Manager / Special Projects -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[