From owner-freebsd-current Mon Nov 16 09:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03143 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:17:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03136 for ; Mon, 16 Nov 1998 09:17:46 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id MAA00288 for ; Mon, 16 Nov 1998 12:17:22 -0500 (EST) Message-Id: <4.1.19981116111511.00b92100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 11:18:27 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Nasty rebooting in 3.0 current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of this weekend's CVS update (current to the timestamp of this message) there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. I first noticed something awry last night. Essentially, during any significant network traffic (like CVSup) the system will suddenly hang... and then reboot. There don't appear to be any revealing messages in the logs, either. The system is running ipfw also, and I noted that this and some of the tcp_* files had been updated this weekend. Anyone else having this problem? Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message