From owner-freebsd-hackers Thu Feb 1 06:18:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA29016 for hackers-outgoing; Thu, 1 Feb 1996 06:18:37 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA29011 for ; Thu, 1 Feb 1996 06:18:35 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id IAA09387; Thu, 1 Feb 1996 08:18:35 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id IAA04160; Thu, 1 Feb 1996 08:19:49 -0600 From: Joe Greco Message-Id: <199602011419.IAA04160@solaria.sol.net> Subject: Re: WYE To: stevep@orion.ods.net (Steve Palm) Date: Thu, 1 Feb 96 8:19:45 CST Cc: hackers@freebsd.org In-Reply-To: <199601312221.QAA11581@orion.ods.net> from "Steve Palm" at Jan 31, 96 04:23:12 pm X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-hackers@freebsd.org Precedence: bulk Good morning SIO hackers, In my continuing struggles with the BocaBoard 2016-and-jammed-IRQ problem, I've set up a continuous port monitor system that alerts me when something bad happens. The condition, as previously described, is quite detectable - see the first two lines below. Steve Palm has redeemed himself by making the following possibly important observation which I have somehow missed: > I determined that wye's IRQ was jammed again.... The light was on > red, as well as the AT (nothing) (OK) behaviour. > > I downed wye and did a physical reset. One thing to note: When I > did a halt, and wye was waiting for a reboot, the IRQ light did go > out. Not sure if that would indicate anything meaningful or not, > since I don't know what the software drivers do during a halt request > to make changes to the IRQ status, but thought I would share it with > you in case you hadn't noticed. Okay, this suggests that there is some way to clear this condition in software! I had been meaning to write a little more about this anyways, so here goes. The time before this, when this happened, I made the trek down to the office and manually unplugged each port, and ran "cu" against it and typed "AT" in the hopes that I would "shake a bit" someplace that had been missed. Each time I got the message "sio: IRQ pending (2) in poll" which was a message that Bruce (I think?) had sent me a minor patch to put in to help debug this.. However I got through all 16 ports and the IRQ was still jammed low. Any ideas or next-step suggestions would be appreciated. Steve's observation suggests that the condition can be corrected via software.. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847