From owner-freebsd-stable@FreeBSD.ORG Mon Nov 5 10:17:56 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CDF516A41B for ; Mon, 5 Nov 2007 10:17:56 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 7B27713C4A7; Mon, 5 Nov 2007 10:17:55 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <472EEDD2.1010203@FreeBSD.org> Date: Mon, 05 Nov 2007 11:17:54 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Oleg Derevenetz References: <47278B33.6040904@FreeBSD.org> <008401c81ca8$65861a70$eec55358@OODAMDXP> <472DDF50.80505@FreeBSD.org> <01c801c81f1f$6366ae20$eec55358@OODAMDXP> <472E470C.9030607@FreeBSD.org> <20071105093640.GN37471@deviant.kiev.zoral.com.ua> <006401c81f91$88325ca0$eec55358@OODAMDXP> In-Reply-To: <006401c81f91$88325ca0$eec55358@OODAMDXP> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: kern/104406: [ufs] Processes get stuck in "ufs" stateunderpersistent CPU load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2007 10:17:56 -0000 Oleg Derevenetz wrote: >> Anyway, I looked at the ddb output already, said that it looks as either >> driver or hw problem with very high confidence. >> >> I think the time of the project could be spent more productive elsewere, >> while submitter checks his hardware, for instance, by changing >> controller, >> disks, or controller type. > > I already said that: > > 1. This controller and disks succesfully works earlier with FreeBSD > 4.6.2 without any problems; Yes, as Kostik says it may be a driver problem. Or it could be a hardware problem because the driver is quite different than in 4.x, and may be exercising the hardware in a different way that provokes a hardware bug. > 2. I tried to replace a disk with another one (the same model), but it > doesn't help. Unfortunately, I have no another free SCSI controller (but > see #1); > 3. I have another AMD64 machine with different hardware (including disks > and SCSI controller) that periodically suffers from the same problem. > Unfortunately, that machine is in production and heavily loaded, so I > can't overload it even more with INVARIANTS, WITNESS, and DIAGNOSTIC - > my clients will not forgive me for that. Many different problems can have similar symptoms when you do not look closely. Indeed, the PR you are replying to is itself a completely different issue that has nothing to do with your own bug report, and someone else also replied to it with what looks like yet another completely different issue. There is no evidence so far pointing anywhere apart from the mylex controller, so that argues against the hypothesis that your second problem is the same. Kris