From owner-freebsd-current Fri Oct 23 18:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00933 for freebsd-current-outgoing; Fri, 23 Oct 1998 18:17:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00927 for ; Fri, 23 Oct 1998 18:17:44 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA01142; Fri, 23 Oct 1998 18:17:11 -0700 (PDT) (envelope-from jdp) Message-Id: <199810240117.SAA01142@austin.polstra.com> To: jeff-ml@mountin.net Subject: Re: 3.0 missing some docs? In-Reply-To: <3.0.3.32.19981023154926.007002b0@207.227.119.2> References: <3.0.3.32.19981023032536.0075034c@207.227.119.2> <3.0.3.32.19981023154926.007002b0@207.227.119.2> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 23 Oct 1998 18:17:11 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3.0.3.32.19981023154926.007002b0@207.227.119.2>, Jeffrey J. Mountin wrote: > >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. I wonder if the difference could be caused by the new bootloader. Have you tried booting an a.out kernel using the new boot code? It would be interesting to find out whether the IRQ 7s came back again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message