From owner-freebsd-current Tue Mar 21 22:59:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 82F3737C0E9 for ; Tue, 21 Mar 2000 22:59:08 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA26307; Tue, 21 Mar 2000 23:59:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA29305; Tue, 21 Mar 2000 23:58:49 -0700 (MST) Message-Id: <200003220658.XAA29305@harmony.village.org> To: "Ilmar S. Habibulin" Subject: Re: -current sudden panics :( Cc: Nikolai Saoukh , Yoshinobu Inoue , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 08:59:45 +0300." References: Date: Tue, 21 Mar 2000 23:58:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Ilmar S. Habibulin" writes: : 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, 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. Since our product's network port is just for debugging, it isn't a big deal to 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. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message