From owner-freebsd-current Sun Sep 10 6:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 153B637B423 for ; Sun, 10 Sep 2000 06:30:01 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13Y6kd-000PZi-00; Sun, 10 Sep 2000 14:02:27 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id OAA59155; Sun, 10 Sep 2000 14:02:26 +0100 (BST) (envelope-from ben) Date: Sun, 10 Sep 2000 14:02:26 +0100 From: Ben Smithurst To: Bosko Milekic Cc: current@freebsd.org Subject: Re: page fault in sched_ithd Message-ID: <20000910140226.H77593@strontium.scientia.demon.co.uk> References: <14779.6851.88867.359611@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > 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). ifconfig(8) is what does it for me too. It's ifconfig(8) at boot time though, so I'm not sure exactly what arguments it has or what it's doing at the time. Mike wrote: >> 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. If people think so then I'll improve my patch a bit to do this. I agree, unless there's a better way to fix the problem. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message