From owner-freebsd-current Sat Sep 9 22:50:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 155CC37B424 for ; Sat, 9 Sep 2000 22:50:23 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.net ([24.201.203.136]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G0N00G8ZPJSPD@falla.videotron.net> for current@freebsd.org; Sun, 10 Sep 2000 01:50:16 -0400 (EDT) Date: Sun, 10 Sep 2000 01:53:40 -0400 (EDT) From: Bosko Milekic Subject: Re: page fault in sched_ithd In-reply-to: <14779.6851.88867.359611@guru.mired.org> X-Sender: bmilekic@jehovah.technokratis.com To: current@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I catch this page fault (described in topic) following an: `ifconfig de0 down' Unfortunately, I don't have much more information to provide for now. I'm in the middle of debugging something else. More info can be provided on request (let me know if you want to look at it and cannot reproduce it). Sources of last friday (evening). On Sun, 10 Sep 2000, Mike Meyer wrote: > Ben Smithurst writes: > > After poking around a bit with remote GDB, this seems to be caused by a > > stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. > > > > The attached rather crude patch has "fixed" the problem for now, but > > does anyone have any suggestions for a real fix? > > Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it > and then ignoring it would be the right thing. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message