Date: Fri, 2 Feb 1996 21:17:17 +1100 From: Bruce Evans <bde@zeta.org.au> To: jgreco@solaria.sol.net, stevep@orion.ods.net Cc: hackers@FreeBSD.org Subject: Re: WYE Message-ID: <199602021017.VAA09314@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>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<CR> (nothing) <CR> (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! Last-closing all the devices should disconnect the physical devices from the IRQ, but won't help unjam the devices. Probing might unjam them or fail to detect the jammed ones so that the others work. -current has better probing code that went into -stable a couple of days ago. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602021017.VAA09314>