From owner-freebsd-current Mon Nov 16 10:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09740 for freebsd-current-outgoing; Mon, 16 Nov 1998 10:07:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09735 for ; Mon, 16 Nov 1998 10:07:11 -0800 (PST) (envelope-from pal@PaLaDiN7.ml.org) Received: from localhost (localhost.my.domain [127.0.0.1]) by PaLaDiN7.ml.org (8.9.1/8.9.1) with ESMTP id MAA11655; Mon, 16 Nov 1998 12:33:25 -0500 (EST) (envelope-from pal@PaLaDiN7.ml.org) Date: Mon, 16 Nov 1998 12:33:23 -0500 (EST) From: pal To: Kyle Mestery cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: 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 Don't know about network traffic - but I was expiriencing several reboots too, however after cvsuping and recompiling kernel yesterday - its seems to be ok now On Mon, 16 Nov 1998, Kyle Mestery wrote: > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message