From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 11 21:49:22 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAFC416A4CE for ; Fri, 11 Feb 2005 21:49:22 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F5643D45 for ; Fri, 11 Feb 2005 21:49:22 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IBROMF00.K8S; Fri, 11 Feb 2005 13:49:27 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005021113530630903 ; Fri, 11 Feb 2005 13:53:07 -0800 From: "Vinod Kashyap" To: Jeff Soule Date: Fri, 11 Feb 2005 13:49:05 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-hardware@freebsd.org Subject: RE: Problems with 4.10 Release and "supported" hardware X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 21:49:22 -0000 > -----Original Message----- > From: Jeff Soule [mailto:jsoule@webcrossing.com] > Sent: Friday, February 11, 2005 1:22 PM > To: Vinod Kashyap > Cc: freebsd-hardware@freebsd.org > Subject: Re: Problems with 4.10 Release and "supported" hardware > = > = > No other controllers. > The built in SATA controller is turned off in the bios. > The bios sees the controller, and I am able to access and = > configure the = > controller at boot. > No errors are reported and I am able to delete/create the RAID Array = > with no problems. > I waited more then a few minutes (Went to get coffee when the 'Kernel = > Configuration Menu' appeared.) > Heck, I even back revved the motherboard bios to the same = > version as a = > server that is working. > = > The only difference is some changes 3ware made to the latest 9000 = > series card (BBU added and firmware changed to support BBU Battery = > Backup Unit) I suspect that their changes broke the twa = > driver but am = > not slick enough to get any further with this :-( > = I don't think the twa driver is even in the picture here. Do you see any message printed by twa at boot time? It looks to me like the FreeBSD PCI subsystem does not even detect any PCI controllers for twa to claim. When this happened, we attached a PCI analyzer and saw that there was almost on activity on any of the PCI busses. Can you plug-in any other PCI controller and see if gets detected? > My vender is building another box with a different Supermicro = > Motherboard that does work, (Already verified), but the bus speed is = > slower so it is not the best solution by a long shot... > = > On Feb 11, 2005, at 12:56 PM, Vinod Kashyap wrote: > = > > Do you see PCI controllers other than 3ware? Do you > > see them (other PCI controllers) if the 3ware controller > > is not plugged in? Does the motherboard BIOS detect > > the 3ware controller? i.e., do you see messages from > > the 3ware BIOS at startup? For how much time did you > > wait at the 'Kernel Configuration Menu'? You might want > > to try waiting longer... > > > > One other thing I have observed is that, if there are > > any degraded units attached to 3ware, the 3ware BIOS > > waits for 30 seconds rather than the usual 5 seconds, > > and when this happens, _all_ PCI controllers are seen! > = >