From owner-freebsd-current Mon Nov 16 09:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03634 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:22:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03625 for ; Mon, 16 Nov 1998 09:22:51 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id LAA00972; Mon, 16 Nov 1998 11:22:15 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma000954; Mon, 16 Nov 98 11:22:06 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id LAA03389; Mon, 16 Nov 1998 11:22:04 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Mon, 16 Nov 1998 11:22:03 -0600 (CST) From: Kyle Mestery To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <4.1.19981116111511.00b92100@206.25.93.69> 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 > 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 noticed this over the weekend also. I am running a current kernel from Saturday night around 5PM CST, on a dual PPro machine. On both Sunday morning and this morning I awoke to find the machine in a hung state, no video output, nohting. Required a hard reset. I havent had time to investivate, but will tonite. Very strange. Mine appears to be caused by a lot of network traffic also, asa CVSup this morning caused the same thing to happen. -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message