From owner-freebsd-current Fri Oct 23 13:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09131 for freebsd-current-outgoing; Fri, 23 Oct 1998 13:54:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09123 for ; Fri, 23 Oct 1998 13:54:30 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id PAA01513; Fri, 23 Oct 1998 15:54:03 -0500 (CDT) Received: from klinzhai-109.isdn.mke.execpc.com(169.207.65.237) by peak.mountin.net via smap (V1.3) id sma001511; Fri Oct 23 15:53:39 1998 Message-Id: <3.0.3.32.19981023154926.007002b0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 23 Oct 1998 15:49:26 -0500 To: Doug White From: "Jeffrey J. Mountin" Subject: Re: 3.0 missing some docs? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19981023032536.0075034c@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:13 AM 10/23/98 -0700, Doug White wrote: >You'll see it if your lpt port is in polled mode, like mine is. I >discovered this tidbit the hard way with the qcam driver; every time I >logged out of X the system would panic. I finally got a VT320 and ran a >serial console and figured out what was going on. At first I thoguht the >motherboard was bad and hd it replaced, and it did the same thing. Er, why did I say com port. Must have been really tired. Sleep is a GoodThing. ;) The lpt is disabled and no support is compiled in. Before it's disabling, it is changed to "normal" mode, no ECP or EPP. Now that I'm awake, the problem I had was related to installing a new Adaptec 2940UW (1.5 years ago). Once installed, the system started generating stray IRQ7's and would panic. Swapped _everything_ out and disabling unused devices did in visual userconfig did nothing to help. Finally a BIOS update fixed the problem. >It's a hardware-ism. IRQ 7 is the generic junk IRQ. Why would changing to an elf kernel "fix" the strays? Nothing else has changed since the kernel went from aout -> elf. If it were a hardware-ism, as you say, this change should do nothing to eliminate the strays. Unless the new elf kernel ignores stray IRQ7's, because there are no drivers using that interrupt. The board is an older Asus TP4N using the FX chipset. Must be a common issue. I'll try a BIOS update and see if the old kernel still does this. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message