From owner-freebsd-proliant@FreeBSD.ORG Mon Feb 27 13:39:33 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D778716A420 for ; Mon, 27 Feb 2006 13:39:33 +0000 (GMT) (envelope-from karl@futurefiber.dk) Received: from cicero2.cybercity.dk (cicero2.cybercity.dk [212.242.40.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6993443D48 for ; Mon, 27 Feb 2006 13:39:33 +0000 (GMT) (envelope-from karl@futurefiber.dk) Received: from user1.cybercity.dk (user1.cybercity.dk [212.242.41.34]) by cicero2.cybercity.dk (Postfix) with ESMTP id 7B79A244CA5 for ; Mon, 27 Feb 2006 14:39:30 +0100 (CET) Received: from main (port22.ds1-od.adsl.cybercity.dk [212.242.51.23]) by user1.cybercity.dk (Postfix) with ESMTP id 9735574F84B for ; Mon, 27 Feb 2006 14:39:29 +0100 (CET) From: "Karl Andersen" To: Date: Mon, 27 Feb 2006 14:37:27 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcY7ovLO1NZsc+THRaSHd8h4Bj1ANA== Message-Id: <20060227133929.9735574F84B@user1.cybercity.dk> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: proliant dl320 and freebsd 6.x power control X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 13:39:34 -0000 Can any one tell me if there is an alternative to http://people.freebsd.org/~jcagle/ for controlling fans etc.on proliant servers I haven't tried the linux things, is that possible ? Karl Andersen From owner-freebsd-proliant@FreeBSD.ORG Tue Feb 28 20:52:06 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 523AA16A420 for ; Tue, 28 Feb 2006 20:52:06 +0000 (GMT) (envelope-from kama@pvp.se) Received: from ms1.as.pvp.se (dns.pvp.se [213.64.187.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E86DF43D46 for ; Tue, 28 Feb 2006 20:52:05 +0000 (GMT) (envelope-from kama@pvp.se) Received: by ms1.as.pvp.se (Postfix, from userid 1001) id 642FAA9; Tue, 28 Feb 2006 21:55:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ms1.as.pvp.se (Postfix) with ESMTP id 62CF7A7; Tue, 28 Feb 2006 21:55:00 +0100 (CET) Date: Tue, 28 Feb 2006 21:55:00 +0100 (CET) From: kama X-X-Sender: kama@ns1.as.pvp.se To: nocturnal In-Reply-To: <43F5CC7F.7010304@swehack.se> Message-ID: <20060228212842.R33180@ns1.as.pvp.se> References: <43F5CC7F.7010304@swehack.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-proliant@freebsd.org Subject: Re: HP Proliant SATA RAID Cards for FreeBSD? X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 20:52:06 -0000 On Fri, 17 Feb 2006, nocturnal wrote: > Hi > > I need to buy a server from a HP partner for a customer and we don't > need hardware RAID but we would prefer it. We do need SATA because of > budget restrictions. I'm new to hardware and i don't know much at all > about SATA or SATA RAID. I've had only bad experience with SATA RAID > cards using FreeBSD where disk writes timed out and made the system hang > repeatedly. > > They offer mainly Proliant machines and i'm wondering which cards you > guys have experience with working well on FreeBSD. We will be using > 6.0-RELEASE for the operatingsystem. We could also accept software RAID > if it comes to that, all we need to know is that it will work without > problems and be stable for a production environment. > > If any of you feel kind enough to recommend a machine for me then the > required specs are at least two cpu slots with one Intel Xeon processor > of at least 2.0GHz. At least 512MB ram and at least 40GB disks in > hardware raid of course. SCSI disks would be great if the price is right > but SATA disks are recommended because of limited ammounts of resources. > -- If your specifications of the machines are so low and disk io is not critical. You probably just need to buy yourself a moderate DL380. And fill it with disks. It have a decent integrated smart array card (SA6i) and you can choose between 36GB to 300GB disks... You will probably get 2*146GB for the price of one extra array controller. I've been using the DL380 with FreeBSD for aprox 5 years and are more than pleased with the stability and performance. The integrated SA6i is faster than the former cards. If you still want SATA have a look at these: http://h18004.www1.hp.com/products/servers/proliantstorage/sharedstorage/sacluster/msa20/ http://h18004.www1.hp.com/products/servers/proliantstorage/arraycontrollers/index.html If you go with a msa20 and a 6402 card, you are good to go... I dont know if the smart array sata controllers uses the ciss driver as the 6402 do. But this setup will cost you more than just buying scsi disks. /Bjorn From owner-freebsd-proliant@FreeBSD.ORG Tue Feb 28 22:38:36 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1D9A16A420 for ; Tue, 28 Feb 2006 22:38:36 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5B043D45 for ; Tue, 28 Feb 2006 22:38:36 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 28 Feb 2006 14:38:36 -0800 Received: from beasley.cisco.com (beasley.cisco.com [171.71.180.166]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1SMcaHf011893 for ; Tue, 28 Feb 2006 14:38:36 -0800 (PST) Received: from [64.101.130.146] ([64.101.130.146] (may be forged)) by beasley.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA16217 for ; Tue, 28 Feb 2006 14:38:36 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-proliant@freebsd.org From: Mike Holloway Date: Tue, 28 Feb 2006 16:38:03 -0600 X-Mailer: Apple Mail (2.746.2) Subject: hpasmcli locks up a DL380G3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 22:38:36 -0000 >> Hi! >> >> Sorry for being late on this one, found this browsing around. >> >> Yes, I have had ONE machine lock up on me once. >> And older HP Proliant DL380G1 UP. Just as you describe, it had been >> working great for >> a couple of weeks, then suddenly when starting hpasmcli it froze. >> Couldn't even ping the machine. >> >> This particualar machine really is not doing anything, and as I belive >> it still is running (Moved/changed job) and I could probably >> recreate the lockup. >> I still have access to this machine, so if anyone want me to try >> something, I can do it. >> The machine is 600km away from me now, so if lockup occurs it can >> take some time to get it >> powercycled though. >> >> Oh, 5.3 or 5.4 as I recall. >> >> Have you seen any other lockup Greg? > >I haven't tempted fate that way yet. I always restart the hpasmd >before using the client on a machine. This seems to avoid the problem. > >Thanks for responding to my mail, you're the third person to confirm >the problem, which given that it locks the machine up hard, is a very >serious one. > >best. >greg. Besides the hpasmcli tool hanging just after the banner message, I've also experienced reboots caused by hpasmd, and have had to remove it completely from my test lab servers. I was able to find a scenario which would invariably cause the servers to reboot, I had hpasmd running on approximately 20 HP DL380 G4 servers all running the same customized FreeBSD 6.0 release kernel on x86 (intel xeon). All machines were configured to run hpasmcli -s "show temps;" every 5 minutes, within a perl wrapper around hpasmcli (included below) which would kill the perl wrapper process (and so hpasmcli) via an ALARM signal if hpasmcli didn't exit within 45 seconds. Within a few hours, a few machines would show the hpasmcli tool hanging and only displaying the banner message. Cron was continuing to run-and-kill the hung hpasmcli tool every 5 minutes for some period of hours before I would notice. After commenting out the cron job and verifying that no hpasmcli processes existed, I could then stop hpasmd via the init script, which sends a TERM signal to the process followed by a KILL signal a couple of seconds later. Without exception those servers would spontaneously reboot a few minutes (2-5) later. On servers that the hpasmcli tool hadn't yet hung, I could stop hpasmd with no ill effects to the system. John, are you still working on this very useful tool? I can provide access to a DL380 G4 if you need a platform to test on. -mike #!/usr/bin/perl eval { local $SIG{ALRM} = sub { local $SIG{HUP} = 'IGNORE'; kill 1,(-$$); }; alarm 45; system ("/usr/sbin/hpasmcli -s \"show temps;\""); alarm 0; }; $SIG{HUP} = 'DEFAULT'; exit 0; From owner-freebsd-proliant@FreeBSD.ORG Tue Feb 28 22:56:40 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA21616A420 for ; Tue, 28 Feb 2006 22:56:40 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC91043D48 for ; Tue, 28 Feb 2006 22:56:39 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 28 Feb 2006 14:56:40 -0800 X-IronPort-AV: i="4.02,154,1139212800"; d="scan'208"; a="1780663545:sNHT32705042" Received: from beasley.cisco.com (beasley.cisco.com [171.71.180.166]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k1SMudVb029575 for ; Tue, 28 Feb 2006 14:56:39 -0800 (PST) Received: from [64.101.130.146] ([64.101.130.146] (may be forged)) by beasley.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA15568; Tue, 28 Feb 2006 14:56:40 -0800 (PST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <55636C59-3ED3-4448-AB91-80ACCBC8CFB1@cisco.com> Content-Transfer-Encoding: 7bit From: Mike Holloway Date: Tue, 28 Feb 2006 16:56:07 -0600 To: Mike Holloway X-Mailer: Apple Mail (2.746.2) Cc: freebsd-proliant@freebsd.org Subject: Re: hpasmcli locks up a DL380G3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 22:56:40 -0000 These are probably of no use for debugging, but here are a couple of presumably non-maskable-interrupts that were logged just as 2 servers rebooted (guess which one of these machines is in Australia): Feb 28 13:28:36 host3 kernel: <<2<<>22>2>NN>NMNMIMMII I II SISIASA SA A 33330000,,, E, EI EISEIAISS AA S fAf ffff Feb 28 13:28:36 host3 kernel: Feb 28 13:28:36 host3 kernel: f Feb 28 13:28:36 host3 kernel: f Mar 1 06:30:51 host14 kernel: NMI INSMAI NINMSMAII 3II0SS3,AA0 ,E IESIAS A 3ff3f00f, Mar 1 06:30:51 host14 kernel: Mar 1 06:30:51 host14 kernel: Mar 1 06:30:51 host14 kernel: < Mar 1 06:30:51 host14 kernel: 2>< Mar 1 06:30:51 host14 kernel: 2,> EEIISSAA ffff Mar 1 06:30:51 host14 kernel: -mike On Feb 28, 2006, at 4:38 PM, Mike Holloway wrote: > >> Hi! > >> > >> Sorry for being late on this one, found this browsing around. > >> > >> Yes, I have had ONE machine lock up on me once. > >> And older HP Proliant DL380G1 UP. Just as you describe, it had been > >> working great for > >> a couple of weeks, then suddenly when starting hpasmcli it froze. > >> Couldn't even ping the machine. > >> > >> This particualar machine really is not doing anything, and as I > belive > >> it still is running (Moved/changed job) and I could probably > >> recreate the lockup. > >> I still have access to this machine, so if anyone want me to try > >> something, I can do it. > >> The machine is 600km away from me now, so if lockup occurs it can > >> take some time to get it > >> powercycled though. > >> > >> Oh, 5.3 or 5.4 as I recall. > >> > >> Have you seen any other lockup Greg? > > > >I haven't tempted fate that way yet. I always restart the hpasmd > >before using the client on a machine. This seems to avoid the > problem. > > > >Thanks for responding to my mail, you're the third person to confirm > >the problem, which given that it locks the machine up hard, is a very > >serious one. > > > >best. > >greg. > > > Besides the hpasmcli tool hanging just after the banner message, > I've also experienced reboots caused by hpasmd, and have had to > remove it completely from my test lab servers. I was able to find > a scenario which would invariably cause the servers to reboot, I > had hpasmd running on approximately 20 HP DL380 G4 servers all > running the same customized FreeBSD 6.0 release kernel on x86 > (intel xeon). > > All machines were configured to run hpasmcli -s "show temps;" every > 5 minutes, within a perl wrapper around hpasmcli (included below) > which would kill the perl wrapper process (and so hpasmcli) via an > ALARM signal if hpasmcli didn't exit within 45 seconds. Within a > few hours, a few machines would show the hpasmcli tool hanging and > only displaying the banner message. Cron was continuing to run-and- > kill the hung hpasmcli tool every 5 minutes for some period of > hours before I would notice. After commenting out the cron job and > verifying that no hpasmcli processes existed, I could then stop > hpasmd via the init script, which sends a TERM signal to the > process followed by a KILL signal a couple of seconds later. > Without exception those servers would spontaneously reboot a few > minutes (2-5) later. On servers that the hpasmcli tool hadn't yet > hung, I could stop hpasmd with no ill effects to the system. > > > John, are you still working on this very useful tool? I can > provide access to a DL380 G4 if you need a platform to test on. > > > -mike > > > #!/usr/bin/perl > > eval { > local $SIG{ALRM} = > sub { > local $SIG{HUP} = 'IGNORE'; > kill 1,(-$$); > }; > alarm 45; > system ("/usr/sbin/hpasmcli -s \"show temps;\""); > alarm 0; > }; > > $SIG{HUP} = 'DEFAULT'; > > exit 0; > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant- > unsubscribe@freebsd.org" > From owner-freebsd-proliant@FreeBSD.ORG Wed Mar 1 00:52:45 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CEA916A420 for ; Wed, 1 Mar 2006 00:52:45 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09C8F43D45 for ; Wed, 1 Mar 2006 00:52:44 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by xproxy.gmail.com with SMTP id h27so6436wxd for ; Tue, 28 Feb 2006 16:52:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GLHZYmX2WZoerL7kKLjN4ZXUDTY2c/hMCRXbkaBD3Hih5vEF3vctikHwpzw3PW6svLcbjestRwCEJC3d6myfjp2Nz6mnBZoK37Wf2fIsmqJ56msBTtIVc45fI3WuNwS6TCPH6xJ5ailBlI7Sh4BVfmvpoojZSGy45c61ppCKbxI= Received: by 10.70.38.8 with SMTP id l8mr1211581wxl; Tue, 28 Feb 2006 16:52:44 -0800 (PST) Received: by 10.70.16.12 with HTTP; Tue, 28 Feb 2006 16:52:44 -0800 (PST) Message-ID: <6863f0c90602281652gb9207d4rb36189cfa5de4693@mail.gmail.com> Date: Tue, 28 Feb 2006 18:52:44 -0600 From: jmc To: "Mike Holloway" In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org Subject: Re: hpasmcli locks up a DL380G3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 00:52:45 -0000 Mike, Did you try to disable ASR (automatic server recovery) in the BIOS settings? You might also try running hpasmd with the -i option to force it to ignore all shutdown conditions. I would be interested to know if that keeps your servers from rebooting 2-5 minutes after killing the errant hpasmd process. At the current time, I don't have the bandwidth to build it for 6.0... Sorry. John From owner-freebsd-proliant@FreeBSD.ORG Wed Mar 1 16:38:00 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE2C416A420 for ; Wed, 1 Mar 2006 16:38:00 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0F6E43D6A for ; Wed, 1 Mar 2006 16:38:00 +0000 (GMT) (envelope-from mikhollo@cisco.com) Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 01 Mar 2006 08:38:01 -0800 X-IronPort-AV: i="4.02,157,1139212800"; d="scan'208"; a="310789686:sNHT29392572" Received: from beasley.cisco.com (beasley.cisco.com [171.71.180.166]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k21Gc0Hf000068 for ; Wed, 1 Mar 2006 08:38:00 -0800 (PST) Received: from [64.101.130.146] ([64.101.130.146] (may be forged)) by beasley.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA23440 for ; Wed, 1 Mar 2006 08:38:00 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <6863f0c90602281652gb9207d4rb36189cfa5de4693@mail.gmail.com> References: <6863f0c90602281652gb9207d4rb36189cfa5de4693@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mike Holloway Date: Wed, 1 Mar 2006 10:37:27 -0600 To: freebsd-proliant@freebsd.org X-Mailer: Apple Mail (2.746.2) Subject: Re: hpasmcli locks up a DL380G3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 16:38:01 -0000 Thanks, I'll give your recommendations a go and report back to the list in a couple of days. -mike On Feb 28, 2006, at 6:52 PM, jmc wrote: > Mike, > > Did you try to disable ASR (automatic server recovery) in the BIOS > settings? You might also try running hpasmd with the -i option to > force it to ignore all shutdown conditions. > > I would be interested to know if that keeps your servers from > rebooting 2-5 minutes after killing the errant hpasmd process. > > At the current time, I don't have the bandwidth to build it for > 6.0... Sorry. > > John From owner-freebsd-proliant@FreeBSD.ORG Fri Mar 3 09:25:41 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 244C616A420 for ; Fri, 3 Mar 2006 09:25:41 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5F5643D48 for ; Fri, 3 Mar 2006 09:25:40 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from localhost (terrapin.inter-sonic.com [172.16.1.12]) by neonpark.inter-sonic.com (Postfix) with ESMTP id 89879818E53 for ; Fri, 3 Mar 2006 10:25:38 +0100 (CET) Message-ID: <44080B8F.7060806@intersonic.se> Date: Fri, 03 Mar 2006 10:25:35 +0100 From: Per olof Ljungmark User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-proliant@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Two questions on DL380Gx X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2006 09:25:41 -0000 Hi, We have a few DL380's here of different generations and so far they are running FreeBSD 4 and 5. Now it seems to me be a good time to start with version 6 and a couple of questions surfaced: 1. Can hpasm run with COMPAT5x installed? 2. Is there a way to control fan speed via acpi in 6.x? Thanks, Per olof