From owner-freebsd-questions@FreeBSD.ORG Wed Nov 28 10:40:19 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AF3916A421 for ; Wed, 28 Nov 2007 10:40:19 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id EB7EC13C467 for ; Wed, 28 Nov 2007 10:40:18 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so1822933uge for ; Wed, 28 Nov 2007 02:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=5W2SZosgB8WfskByFbY4Cto7D9nVL40RWUpR0g93ZxQ=; b=WYJICJdUB0baU30SeReNHI01LtMianwEltplsmEb0e9lIJjaDfSVgYSVjTxzMt9hYemY9zgom6XAAVAIuiYuu3t//FUSvPv1KT93G4SNXMrayRIJnTjNiYuQi8CnVU6ZZHK/ZrJYj24y6BgKZaDVoWs4T8R0Sdc1fuMJEBZFgKw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nPHxy8/m5dAuedLCTWx+Z8tEFb8MEm0EdpjpvwwZGbP5icYDcWqQU5qL+9R15pyiS65rDUo+mPBEPSTQ+X1iO74Nchfc7Q5j0rlE2LRICQwGpqYRBrBt41aTpmT+SnUJS31fV3P3Ti/waLLz9GHtTHKeVeygXfo8II+0UQQsYRA= Received: by 10.67.30.6 with SMTP id h6mr208180ugj.1196246417420; Wed, 28 Nov 2007 02:40:17 -0800 (PST) Received: by 10.66.220.16 with HTTP; Wed, 28 Nov 2007 02:40:16 -0800 (PST) Message-ID: <3aaaa3a0711280240y56ec99c7qb4130a93f942a9a5@mail.gmail.com> Date: Wed, 28 Nov 2007 10:40:16 +0000 From: Chris To: "Kris Kennaway" In-Reply-To: <474D40F4.3090409@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <000701c82f89$fb9b40a0$0200a8c0@satellite> <4749FDE0.9030902@netscape.net> <474A9DCD.6020500@FreeBSD.org> <3aaaa3a0711260734tb0a46a3kac3b423bfd89582b@mail.gmail.com> <474B4610.5020702@FreeBSD.org> <3aaaa3a0711280211g1a44172bi117ea3ee95f729bb@mail.gmail.com> <474D40F4.3090409@FreeBSD.org> Cc: Tore Lund , freebsd-questions@freebsd.org Subject: Re: stability of FreeBSD 7 Beta 3? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2007 10:40:19 -0000 On 28/11/2007, Kris Kennaway wrote: > Chris wrote: > > On 26/11/2007, Kris Kennaway wrote: > > > >> Of course not :P What are the PR references? > >> > >>> Try this. > >>> > >>> Login to twice on ssh. > >>> If not root su both to root. > >>> using the 2nd tty do a watch -W on the first tty. > >>> on the first tty type 'killall watch' > >>> you have now crashed freebsd 7 and most probably a auto reboot timer > >>> is counting down. > >> I can confirm this. > >> > >>> Even typing reboot to reboot the server causes page faults. > >> But not this. > >> > >> Kris > >> > >> > > Hi Kris > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=116719 is the watch report > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=116720 for the reboot > > > > The reboot stopped crashing when I recompiled world using -O I have > > however seen it on other servers crashing on -O binaries its not > > consistent like the watch problem but its on numerous servers I seen > > the problem on. > > Unfortunately both of these are not high quality PR submissions, which > is probably why no action has been taken yet. At least in the first one > you give a "how to repeat" that I was able to follow, but in general > when you encounter a panic you should be providing the backtrace and/or > other debugging information requested here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > > The second PR is basically null as written since it cannot be reproduced > and no debugging information was submitted. If you are interested in > proceeding with it, please reproduce and obtain the necessary kernel > debugging. Otherwise we should close it. > > Does the patch I sent you solve the first problem? > > Kris > > Ok first an apology there was feedback to 116720 which I didnt know until now. I did another crash on the watch but had foreground fsck set in rc.conf and did another immediate reboot afterwards and as expected because no bg fsck running it didnt crash. Patching it now and will also enable full debugging on the kernel. Chris