From owner-freebsd-questions Wed Nov 29 07:40:59 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA24739 for questions-outgoing; Wed, 29 Nov 1995 07:40:59 -0800 Received: from vhf.dataradio.com (G496.InterLink.NET [198.168.61.62]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA24713 for ; Wed, 29 Nov 1995 07:40:36 -0800 Received: from dri.UUCP (uucp@localhost) by vhf.dataradio.com (8.6.12/8.6.12) with UUCP id KAA05360 for freebsd-questions@freebsd.org; Wed, 29 Nov 1995 10:39:32 -0500 Message-Id: <199511291539.KAA05360@vhf.dataradio.com> Received: by dri (UUXFER v1.4d); Wed 29 Nov 1995 10:40:36 EST From: "Andrew Webster" To: freebsd-questions@freebsd.org Date: Wed, 29 Nov 1995 10:40:27 +0000 Subject: Strange Multi-port SIO behaviour X-Confirm-Reading-To: "Andrew Webster" X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: owner-questions@freebsd.org Precedence: bulk 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. 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? 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? ----------------------------------------------------------------------- Andrew Webster Network Manager / Special Projects Dataradio Inc. 200-5500 Royalmount Ave. TEL: +1 514 737 0020 Town of Mount Royal, QC, CANADA H4P 1H7 FAX: +1 514 737 7883 http://www.dataradio.com Email: awebster@dataradio.com