From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 16:26:17 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D28AC16A41F for ; Wed, 31 Aug 2005 16:26:17 +0000 (GMT) (envelope-from bsd@bathnetworks.com) Received: from lmail.bathnetworks.co.uk (mail.bathnetworks.com [84.92.24.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA8E43D53 for ; Wed, 31 Aug 2005 16:26:15 +0000 (GMT) (envelope-from bsd@bathnetworks.com) Received: (qmail 27666 invoked by uid 510); 31 Aug 2005 17:26:40 +0100 Received: from 84.92.24.252 by lmail.bathnetworks.co.uk (envelope-from , uid 508) with qmail-scanner-1.24-st-qms (clamdscan: 0.86.2/1032. spamassassin: 3.0.2. perlscan: 1.24-st-qms. Clear:RC:0(84.92.24.252):SA:0(-4.6/5.0):. Processed in 1.555832 secs); 31 Aug 2005 16:26:40 -0000 X-Spam-Status: No, hits=-4.6 required=5.0 X-Antivirus-MYDOMAIN-Mail-From: bsd@bathnetworks.com via lmail.bathnetworks.co.uk X-Antivirus-MYDOMAIN: 1.24-st-qms (Clear:RC:0(84.92.24.252):SA:0(-4.6/5.0):. Processed in 1.555832 secs Process 27659) Received: from mail.bathnetworks.com (HELO ?84.92.24.252?) (bsd@bathnetworks.com@84.92.24.252) by lmail.bathnetworks.co.uk with SMTP; 31 Aug 2005 17:26:38 +0100 From: Robert Slade To: "freebsd-questions@freebsd.org" In-Reply-To: <200508301621.20648.vizion@vizion.occoxmail.com> References: <1125428745.6664.37.camel@lmail.bathnetworks.co.uk> <200508301320.44459.vizion@vizion.occoxmail.com> <1125433886.14752.13.camel@lmail.bathnetworks.co.uk> <200508301621.20648.vizion@vizion.occoxmail.com> Content-Type: text/plain Message-Id: <1125505597.26164.19.camel@lmail.bathnetworks.co.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 31 Aug 2005 17:26:38 +0100 Content-Transfer-Encoding: 7bit Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem 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, 31 Aug 2005 16:26:18 -0000 On Wed, 2005-08-31 at 00:21, Vizion wrote: > On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the > dialogue on- > Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > > >On Tue, 2005-08-30 at 21:20, Vizion wrote: > >> On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to > >> the dialogue on- > >> > >> Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >On Tue, 2005-08-30 at 20:10, Vizion wrote: > >> >> On Tuesday 30 August 2005 12:05, the author Robert Slade contributed > >> >> to the dialogue on- > >> >> > >> >> Proliant 5000 sever Fbsd 5.4 (re)boot problem: > >> >> >Hiya, > >> >> > > >> >> >I've been working on this beasty on and off for some time. It's a Quad > >> >> >processor 1 Gbyte of memory and 5 scsi drives using the 2p raid > >> >> >controller setup as 2 raid arrays + 1 spare. > >> >> > > >> >> >The machine works fine with 5.4 release #0 with the supplied generic > >> >> >kernel. > >> >> > > >> >> >The problem(s) I have been having are: > >> >> > > >> >> >1. When I recompiled the Kernel with SMP support, I get random > >> >> > reboots. It also fails to boot sometimes failing at the point after > >> >> > waiting for the scsi drives to settle. I get some error codes and > >> >> > Fbsd fails to find the boot device. > >> >> > > >> >> >2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP > >> >> >support. This does to boot at all. It gets as far as the waiting 15s > >> >> > for scsi devices to settle, then (appears to) reset the scsi > >> >> > controller and immediately tries to access the drives (does not > >> >> > wait). I have tried recompiling with scsi_delay set to 30000 (30s) > >> >> > with no change. > >> >> > > >> >> >I have checked dmesg and message logs but there is nothing related to > >> >> >the problem(s) there. > >> >> > > >> >> >I have gone back to the 5.4 release #0 single processor kernel for now > >> >> >which is a shame as the machine is slow without the multi processor > >> >> >support. > >> >> > > >> >> >The only thing out of the ordinary I have noted is a tx underunn -- > >> >> >increasing threshold to 512 bytes message which appears related to > >> >> >running kde remotely via vncserver and tinync. > >> >> > > >> >> >Any ideas, I can send conf files etc if needed. > >> >> > > >> >> >Thanks > >> >> > > >> >> >Rob > >> >> > >> >> What are your bios setting? > >> >> My guess is that you have not made the right setting using the siftware > >> >> and configuration utilities > >> >> david > >> > > >> >David, > >> > > >> >Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk > >> >geometry) and the machine passes all the diagnostics. > >> > > >> >Rob > >> > >> I cannot remember - but I have sneaking notion that you need to set it as > >> linux > > > >Tried that too :-). I think that the problem is that with 5.4 release #2 > >it is trying to access that scsi drives immediately then inducing the > >kernel panic for 15s. Rather than inducing the panic 1st. > > > >Rob > > > > Did you follow my suggestion and search the HP resources with freebsd and your > model. I have had the same problem myself I am pretty certain it was fixed > by changes using the Proliant Essrntial Foundation Pack.. but my memory may > not be accurate. > david David, I did update the system and controller ROMs whne the machine was running windows. I have been on the HP site and as far as I can tell I have the latest. Rob