From owner-freebsd-questions@FreeBSD.ORG Fri Apr 20 00:25:37 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6460F16A407; Fri, 20 Apr 2007 00:25:37 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from bcmelmx.bytecraft.au.com (bcmelmx.bytecraft.au.com [203.39.118.2]) by mx1.freebsd.org (Postfix) with ESMTP id AFF8913C45A; Fri, 20 Apr 2007 00:25:36 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from svmarshal2.bytecraft.internal (svmarshal2.bytecraft.internal [10.0.0.3]) by bcmelmx.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id l3K0PXX8020500; Fri, 20 Apr 2007 10:25:33 +1000 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal2.bytecraft.internal with MailMarshal (v6, 1, 4, 441) id ; Fri, 20 Apr 2007 10:25:32 +1000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 20 Apr 2007 10:25:32 +1000 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F12DF1C6@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IBM / FreeBSD Install problem Thread-Index: AceC2VfHArr8RUijQtqjHMjQzFhwgwAB/Plg From: "Murray Taylor" To: "Jerry McAllister" Cc: freebsd-hackers@freebsd.org, FreeBSD Mailing List Subject: RE: IBM / FreeBSD Install 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: Fri, 20 Apr 2007 00:25:37 -0000 Thanks Jerry, We have determined that our problem is related to the god-awful mess known as ACPI. With a single processor installed, it all boots fine, including finding PCI busses 1 and 2 .... and the raid on the aac driver is peachy! With 2 or more processors installed, and ACPI enabled, it panics with a madt error about id 38 is greater than the allowed max And with ACPI disabled, it boots, but doesnt find PCI busses 1 and 2, which is unfortunate as the RAID controller sits in PCI bus 1 .... and the bge inet interface seems to be on PCI bus 2 ....=20 So at present we are on the FC6 path, which is obviously much softer on the vagaries of ACPI and is ignoring the crap data returns. mjt > -----Original Message----- > From: Jerry McAllister [mailto:jerrymc@msu.edu]=20 > Sent: Friday, 20 April 2007 12:40 AM > To: Murray Taylor > Cc: FreeBSD Mailing List; freebsd-hackers@freebsd.org > Subject: Re: IBM / FreeBSD Install problem >=20 > On Thu, Apr 19, 2007 at 10:14:13AM +1000, Murray Taylor wrote: >=20 > > Server: IBM X3850 (88633SM) > > CPU X 4: 40K2522 > > HDD X 6: 40K1051 > > IBM ServeRAID 8i: 39R8729 > >=20 > > We are attempting to install FreeBSD 6.2-RELEASE onto this=20 > machine and > > are running into a problem getting the operating system to=20 > recognise the > > RAID controller. As a result not finding any disks when it comes to > > installing the O/S. > >=20 > > We have attempted various modifications to the boot=20 > process, including > > the loading of an "aac" module, which according to the BSD website, > > should provide support for this type of controller. >=20 > I have only installed on a couple of raids and so don't know about > them all or even this one. So, this might not apply to your=20 > situation. > But, I found that I had to study DMESG very carefully to find=20 > out what=20 > device to use for them. The system seemed to put out a lot=20 > of messages=20 > that looked like other device names but in the end there was just one=20 > little line that pointed to the correct one. The most=20 > recent one was=20 > a Dell Perc 3i or something like that and I had to run the fixit and=20 > study the boot messages to figure it out. I don't have that one=20 > available to look at what it turned out to be, but it was more simple=20 > than I first thought from all the stuff it wrote out. After mucking > with fixit a bit, then sysinstall seemed to figure it out OK. I don't > remember actually changing anything - just fishing around a while. > I may have run fdisk under fixit to look at things and maybe delete > some slices. >=20 > So, rather than trying to change things right off, I would suggest > looking carefully at stuff and trying to determine what it is already > doing. >=20 > Anyway, good luck, >=20 > ////jerry >=20 > >=20 > > When we attempt to boot to OS to install after making these above > > modifications, the boot loader advises that this module=20 > already appears > > to be loaded, which contradicts what I believe. In any respect, it > > doesn't work either way (with or without the module=20 > manually loaded). > >=20 > > One side note (which i don't think is contributing) is that when I > > attempt to start the boot loader with ACPI enabled, it=20 > freezes with the > > message "cpu id 38 too high". However if I boot the boot loader with > > ACPI disabled, this message dissapears. It _may_ be a=20 > possibility that a > > bi-product of disabling the ACPI is causing the RAID=20 > controller to have > > issues. This appears to be an issue because of the X4 CPU count ?? > >=20 > > That's a quick summary of the problem we have, and the=20 > path(s) we have > > been down to date to attempt to fix it. Any help you can=20 > provide would > > be very much appreciated. We are at the position now where we are > > prepared to pay for consulting services to get it going. > >=20 > > Dave Faulkner / Murray Taylor > >=20 > > Bytecraft Systems > >=20 > >=20 > > -- > >=20 > > "Any intelligent fool can make things bigger and more complex... It > > takes a > > touch of genius - and a lot of courage to move in the opposite > > direction." > > --Albert Einstein=20 > > --------------------------------------------------------------- > > The information transmitted in this e-mail is for the exclusive > > use of the intended addressee and may contain confidential > > and/or privileged material. Any review, re-transmission, > > dissemination or other use of it, or the taking of any action > > in reliance upon this information by persons and/or entities > > other than the intended recipient is prohibited. If you > > received this in error, please inform the sender and/or > > addressee immediately and delete the material.=20 > >=20 > > E-mails may not be secure, may contain computer viruses and > > may be corrupted in transmission. Please carefully check this > > e-mail (and any attachment) accordingly. No warranties are > > given and no liability is accepted for any loss or damage > > caused by such matters. > > --------------------------------------------------------------- > >=20 > > ### This e-mail message has been scanned for Viruses by=20 > Bytecraft ### > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to=20 > "freebsd-questions-unsubscribe@freebsd.org" > >=20 >=20 --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ### This e-mail message has been scanned for Viruses by Bytecraft ###