From owner-freebsd-current Wed Mar 22 22:18:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by hub.freebsd.org (Postfix) with ESMTP id 4E7B837BA06 for ; Wed, 22 Mar 2000 22:18:30 -0800 (PST) (envelope-from ilmar@ints.ru) Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id JAA02272; Thu, 23 Mar 2000 09:18:06 +0300 (MSK) Date: Thu, 23 Mar 2000 09:18:06 +0300 (MSK) From: "Ilmar S. Habibulin" To: Warner Losh Cc: Nikolai Saoukh , Yoshinobu Inoue , freebsd-current@FreeBSD.ORG Subject: Re: -current sudden panics :( In-Reply-To: <200003220658.XAA29305@harmony.village.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 On Tue, 21 Mar 2000, Warner Losh wrote: > : But why there is such a sudden change? Everything worked just fine a week > : before 5-current. > No it didn't. I've been seeing panics like this for about two weeks, Ok, it worked for me. > but it hadn't been a priority until this week for me. And I'm not > seeing it on lightly loaded networks, but am on heavily loaded ones. My pc is not on lightly loaded network. This networks' load is moving towards(?) zero. ;-) > Since our product's network port is just for debugging, it isn't a big > deal to me.... And i'm using freebsd as my desktop OS. So this became a VERY BIG problem for me. :( > It is definitely a load related problem for me. It usually works just > fine, but sometimes there's a packet that gets to arp that arp barfs > on. I can't track this situation. Everything seems to be fine, then - BBBOOOMMM - page fault. :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message