From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 20:13:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31F7A16A41F for ; Tue, 13 Dec 2005 20:13:03 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn.pobox.com (vds.fauxbox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B8AC43D60 for ; Tue, 13 Dec 2005 20:13:01 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id EF140149; Tue, 13 Dec 2005 15:13:22 -0500 (EST) Received: from pool-71-112-202-40.sttlwa.dsl-w.verizon.net (pool-71-112-202-40.sttlwa.dsl-w.verizon.net [71.112.202.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 3CC2527DA; Tue, 13 Dec 2005 15:13:20 -0500 (EST) Date: Tue, 13 Dec 2005 12:12:52 -0800 (PST) From: Luke Dean X-X-Sender: lukas@border.crystalsphere.multiverse To: Atanas In-Reply-To: <439E8103.7020106@asd.aplus.net> Message-ID: <20051213114921.Q72503@border.crystalsphere.multiverse> References: <439DE88B.1090407@asd.aplus.net> <20051212214003.GA77268@cirb503493.alcatel.com.au> <439E3894.6060901@asd.aplus.net> <439E8103.7020106@asd.aplus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 20:13:03 -0000 On Tue, 13 Dec 2005, Atanas wrote: > Atanas said the following on 12/12/05 18:57: >> Peter Jeremy said the following on 12/12/05 13:40: >>> >>> When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on >>> a serial console). >>> >> But if I have no keyboard response I won't be able to save it, right? >> > (replying to myself) > This is exactly what I was afraid would happen. The SATA based box just hung > up again, with all of the kernel debugging options in place: > > makeoptions DEBUG=-g > options KDB > options DDB > > But I wasn't able to do anything with the keyboard in order to save a > crashdump, so I got no other choices than hitting the reset button. > > Regards, > Atanas I posted this same problem recently. My latest attempt to troubleshoot the freezes was to snatch the SATA card out of the box. The machine has been running without any problems since. That was six days, 12 hours ago - the longest uptime I've had since I upgraded the machine to version 6. The only reason I added the SATA controller to the box was to set up a gmirror to make backups to, and since the machine kept freezing all the time I couldn't make decent backups anyway, so removing the SATA card didn't change the machine's duties at all. The reason I suspected the card might be the problem is that I installed it at the same time I upgraded to FreeBSD 6 (when the problems started), the card only cost $20, and the drives attached to the card were getting corrupted during crashes even though they weren't in use. The card was a SYBA SD-SATA-4P. I've also got an rl0 ethernet interface on the PCI bus also, and I wondered if it might be some kind of bus-mastering conflict or something. I still don't know if the problem was bad cheap hardware, bad interactions between cheap hardware, or a software problem. I suppose downgrading to 5.4 again might give some clues, but I don't really want to do that right now since the system finally seems to be stable again, albeit without my large disk array. This may easily have nothing to do with your problem, since we have so little information to go on, but the symptoms sound the same.