From owner-freebsd-sparc64@FreeBSD.ORG Sun Jun 23 16:18:38 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0D8E190E for ; Sun, 23 Jun 2013 16:18:38 +0000 (UTC) (envelope-from riccardo.veraldi@gmail.com) Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 95178131B for ; Sun, 23 Jun 2013 16:18:37 +0000 (UTC) Received: by mail-ea0-f170.google.com with SMTP id h10so5552861eaj.15 for ; Sun, 23 Jun 2013 09:18:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HqGlSGnqcfFBCWNCbv0g/Ce8G4SVMT6+O/W5ebzg8nw=; b=cd/ZHIcGtO0qekjdrqC2/NyMWS3OreMloG+qF6cPHqfwIIBtg611dwClynIfg9Wdmx Ho66SxlMTRwl9CxRqTSokyfcI0QnbCFZgR/VKqwtWWA/QnwACCOChhzojrC+16XDostf 6i44SpEmRqt0rp7Ht7LVzFKJEKofAH/D2uLKj2+oY0kPnP+bqIx/g3S8k3TDX2mQEzqR Nr9D5EzFjQR+yCqwLfZLeR2vEEWa13zm6753coeBhfoUq22iFwK7SABwsfFpzA4IxXSi siEfYrIaueK+zrsVrlq/Hfx1nT6J7jYzbhov+8rgaK1blDuK0J3gF8WCAJZnXNwd7iVb XbjA== X-Received: by 10.15.22.199 with SMTP id f47mr21109314eeu.47.1372004316782; Sun, 23 Jun 2013 09:18:36 -0700 (PDT) Received: from knuth.default.domain.invalid ([31.177.41.8]) by mx.google.com with ESMTPSA id y1sm17412500eew.3.2013.06.23.09.18.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Jun 2013 09:18:36 -0700 (PDT) Message-ID: <51C71FDA.5070208@gmail.com> Date: Sun, 23 Jun 2013 18:18:34 +0200 From: Riccardo Veraldi User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Marius Strobl Subject: Re: watchdog timeout References: <51C60DAA.5020300@gmx.it> <20130622233911.GA81789@alchemy.franken.de> <51C6DAE3.6050602@gmail.com> <20130623153003.GC940@alchemy.franken.de> In-Reply-To: <20130623153003.GC940@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: fddi , freebsd-sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 16:18:38 -0000 yes I am running 9.1-RELEASE because it is a production system and I needed to recompile the less possible... On 6/23/13 5:30 PM, Marius Strobl wrote: > On Sun, Jun 23, 2013 at 01:24:19PM +0200, Riccardo Veraldi wrote: >> it is 9.1-RELEASE >> >> I have no way to reproduce it, because it appeared suddently without any >> specific cause. >> The system was not under heavy load, I Was not compiling anything... >> >> But I had other errors recently which are really not related I think, >> mainly parity SCSI errors on isp0 >> >> Jun 12 04:48:38 blade kernel: (da3:isp0:0:1:0): CAM status: SCSI Status >> Error >> Jun 12 04:48:38 blade kernel: (da3:isp0:0:1:0): SCSI sense: ABORTED >> COMMAND asc:47,0 (SCSI parity error) > In fact, there's one open issue with isp(4) causing timeouts of the > kind you have seen but which never got quite resolved. Investigating > that as a potential culprit for the case you have encountered would > require updating to stable/9 and possibly giving a patch a try, > though. Besides, we'd need a way to reliably detect whether the > problem is gone. > On the other hand, the parity errors indicate that this system is > suffering from hardware problems, including the possibility that a > disk is defective or has broken firmware and the combination of some > components not getting along for some reason. > > Marius >