From owner-freebsd-current Thu Nov 16 9:19: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2A4FA37B479 for ; Thu, 16 Nov 2000 09:19:00 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA30813; Thu, 16 Nov 2000 18:17:46 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011161717.SAA30813@freebsd.dk> Subject: Re: CURRENT is freezing again ... In-Reply-To: from Boris Popov at "Nov 16, 2000 10:54:47 pm" To: bp@butya.kz (Boris Popov) Date: Thu, 16 Nov 2000 18:17:46 +0100 (CET) Cc: valentin@valcho.net (Valentin Chopov), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Boris Popov wrote: > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > 10 min after boot... > > > > You mean "is still freezing" right ? > > > > Current has been like this for longer than I care to think about, it > > seems those in charge doesn't take these problems seriously (enough)... > > I think info about where/how it freezing would be more helpful. No idea, the system just freezes, no drob to DDB no remote gdb no nothing, so its really hard to tell where... As to how, just boot current on a fairly fast machine, make a kernel and it'll hang in minutes if not less, or just leave it alone and it will hang in 10-30 mins... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message