From owner-freebsd-mobile Mon Apr 3 3:13:46 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by hub.freebsd.org (Postfix) with ESMTP id F25A537B634 for ; Mon, 3 Apr 2000 03:13:35 -0700 (PDT) (envelope-from bc-freebsd@vicious.dropbear.id.au) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id UAA28096 for ; Mon, 3 Apr 2000 20:13:26 +1000 (EST) Received: from julubu.staff.apnic.net(192.168.1.37) by int-gw.staff.apnic.net via smap (V2.1) id xma028087; Mon, 3 Apr 00 20:13:08 +1000 Date: Mon, 3 Apr 2000 20:13:06 +1000 (EST) From: Bruce Campbell X-Sender: bc@julubu.staff.apnic.net To: freebsd-mobile@freebsd.org Subject: obscure panics under 4.0-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Unrelated to my previous message, I've been experiencing odd panics on a 4.0-STABLE system whenever particular network processes (using promiscious mode) are specifically killed, specifically 'arpwatch' and 'tcpdump'. I'm not sure whether its a few suspend/resume cycles, a busy network, or changing IP address which is the initial trigger for the problem (which I cannot duplicate right now, in accordance with Murphy's Law). Is this a 'oh, that was fixed in kern/{376,3329}' problem or something specific to 4.0-stable? [1] Mailing lists do not seem to have anything matching. --==-- Bruce. [1] Yes, I realise this is inadequate information at the current time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message