From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 28 16:03:02 2003 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 45B6D16A4B3 for ; Sun, 28 Sep 2003 16:03:02 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C79F844015 for ; Sun, 28 Sep 2003 16:03:01 -0700 (PDT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id C15CD2ED436; Sun, 28 Sep 2003 16:03:01 -0700 (PDT) Date: Sun, 28 Sep 2003 16:03:01 -0700 From: Paul Saab To: David Hill Message-ID: <20030928230301.GA4610@elvis.mu.org> References: <20030919112802.338678e3.david@wmol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030919112802.338678e3.david@wmol.com> User-Agent: Mutt/1.4.1i cc: hardware@freebsd.org Subject: Re: 3ware escalade 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: Sun, 28 Sep 2003 23:03:02 -0000 they work just fine. David Hill (david@wmol.com) wrote: > Hello - > Has anyone successfully used a 3ware escalade 8506 Serial ATA raid controller with FreeBSD 4.x? > > twe(4) on -CURRENT lists it as supported. I am wondering if 4.x supports it? > http://www.3ware.com/products/serial_ata.asp > > Thanks > - David > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > -- -ps From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 28 16:45:45 2003 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 2AD2E16A4B3 for ; Sun, 28 Sep 2003 16:45:45 -0700 (PDT) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FEDD44011 for ; Sun, 28 Sep 2003 16:45:43 -0700 (PDT) (envelope-from anthony@carmoda.com) Received: from carmoda3 (c211-28-220-147.kelvn1.qld.optusnet.com.au [211.28.220.147])h8SNjf714490 for ; Mon, 29 Sep 2003 09:45:42 +1000 From: "Anthony Carmody" To: Date: Mon, 29 Sep 2003 09:50:03 +1000 Message-ID: <004c01c3861b$3d302430$6600a8c0@carmoda3> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: Ethernet Drivers with 5.1 not happening X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: anthony@carmoda.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2003 23:45:45 -0000 Hiya, I posted a question about this last week. I have done a little homework and I am resubmitting my question with more information and i hope someone can help this time around. I am building a FreeBSD 5.1 box for a client using a fairly new ASUS Mainboard, that SHOULD according to the HARDWARE.TXT file on my installer CDROM, work with all the hardware chip-sets concerned. precisely, an "Intel 82562EZ LAN PHY". These are the relevant lines i get from "pciconf -lv" : none3@pci1:8:0: class=0x2020000 card=0x80f81043 chip=0x10508086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet AND this is what i get from "dmesg | more" : pci1: on pcib1 pci1: at device 8.0 (no driver attached) is there a way i might just install some drivers without reinstalling the whole system? I think someone has made some recently, although i am not familiar with the procedure of obtaining and installing them. I have experience installing from ISO images and adding the odd port but not much beyond that. Here is the link to the mailing.freebsd.cvs-current thread im not sure about: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&th=c2cc18e7fd2e3621&rnum= 1 any info is greatly appreciated always. Regards, Carmoda iamcarmoda[remove-spam]@hotmail.com ==================================== From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 11:21:14 2003 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 8C37116A4B3; Mon, 29 Sep 2003 11:21:14 -0700 (PDT) Received: from excdmz5.cinfin.com (excdmz5.cinfin.com [216.196.231.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3410D43FF5; Mon, 29 Sep 2003 11:21:13 -0700 (PDT) (envelope-from ANTIGEN_EXCDMZ5@CINFIN.com) Received: by excdmz5.cinfin.com with Internet Mail Service (5.5.2650.21) id ; Mon, 29 Sep 2003 14:21:12 -0400 Message-ID: <7BE4D57FB272D4118D1400508BD9525802BB4C54@excdmz5.cinfin.com> From: ANTIGEN_EXCDMZ5 To: "'freebsd-questions@freebsd.org'" , "'freebsd-hardware@freebsd.org'" Date: Mon, 29 Sep 2003 14:21:11 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C386B6.75C10FE4" Subject: Antigen forwarded attachment 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: Mon, 29 Sep 2003 18:21:14 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C386B6.75C10FE4 Content-Type: text/plain The entire message "Sil680 RAID Support while installing 5.1-Release", originally sent to you by owner-freebsd-hardware@freebsd.org (owner-freebsd-hardware@freebsd.org), has been forwarded to you from the Antigen Quarantine area. This message may have been re-scanned by Antigen and handled according to the appropriate scan job's settings. ------_=_NextPart_000_01C386B6.75C10FE4 Content-Type: message/rfc822 From: "owner-freebsd-hardware@freebsd.org" To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Sil680 RAID Support while installing 5.1-Release Date: Mon, 29 Sep 2003 14:21:11 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain I just purchased a Sil680 IDE RAID controller, and have setup a striped RAID array. When I boot from the 5.1 installation CD-ROM, FreeBSD does not recognize them as one disk. I checked the hardware notes, and "Sil680 UDMA6" is listed. Seeing Sil680 listed, I assumed that the RAID capabilities would also be supported. I read something posted awhile back referring to the Sil680 controller, saying it was supported, but dangerous unless using 5.1-Current. Does anybody know anything about the current status of this? Is there anyway to get the FreeBSD installation to recognize my RAID array, or should I just buy another controller? Thanks, Travis Troyer _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------_=_NextPart_000_01C386B6.75C10FE4-- From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 11:21:17 2003 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 F16FC16A4B3 for ; Mon, 29 Sep 2003 11:21:16 -0700 (PDT) Received: from excdmz5.cinfin.com (excdmz5.cinfin.com [216.196.231.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 257E94401A for ; Mon, 29 Sep 2003 11:21:16 -0700 (PDT) (envelope-from ANTIGEN_EXCDMZ5@CINFIN.com) Received: by excdmz5.cinfin.com with Internet Mail Service (5.5.2650.21) id ; Mon, 29 Sep 2003 14:21:16 -0400 Message-ID: <7BE4D57FB272D4118D1400508BD9525802BB4C55@excdmz5.cinfin.com> From: ANTIGEN_EXCDMZ5 To: "'troyertm@email.uc.edu'" Date: Mon, 29 Sep 2003 14:21:15 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C386B6.781EA530" cc: "'freebsd-hardware@freebsd.org'" Subject: Antigen forwarded attachment 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: Mon, 29 Sep 2003 18:21:17 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C386B6.781EA530 Content-Type: text/plain The entire message "Re: Sil680 RAID Support while installing 5.1-Release", originally sent to you by owner-freebsd-hardware@freebsd.org (owner-freebsd-hardware@freebsd.org), has been forwarded to you from the Antigen Quarantine area. This message may have been re-scanned by Antigen and handled according to the appropriate scan job's settings. ------_=_NextPart_000_01C386B6.781EA530 Content-Type: message/rfc822 From: "owner-freebsd-hardware@freebsd.org" To: troyertm@email.uc.edu Cc: freebsd-hardware@freebsd.org Subject: Re: Sil680 RAID Support while installing 5.1-Release Date: Mon, 29 Sep 2003 14:21:15 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain I don't know about 5.1-Current, but if you look at the ata-raid.* code in the 5.1-Release kernel source tree, you will find that only Promise and Highpoint chips are supported. This is a pity because the Sil0680 chip is the cheapest and most widely available around. It is selling for less than US$20 here in Hong Kong with ATA133 and full "RAID" capabilities. While it may not be super fast, it does work alright under Windows environment. If it is indeed supported under 5.1-Current, that is great news. Andrew ----- Original Message ----- From: "Travis Troyer" To: ; Sent: Saturday, September 27, 2003 10:56 PM Subject: Sil680 RAID Support while installing 5.1-Release > I just purchased a Sil680 IDE RAID controller, and have setup > a striped RAID array. When I boot from the 5.1 installation > CD-ROM, FreeBSD does not recognize them as one disk. I > checked the hardware notes, and "Sil680 UDMA6" is listed. > Seeing Sil680 listed, I assumed that the RAID capabilities > would also be supported. I read something posted awhile back > referring to the Sil680 controller, saying it was supported, > but dangerous unless using 5.1-Current. Does anybody know > anything about the current status of this? Is there anyway to > get the FreeBSD installation to recognize my RAID array, or > should I just buy another controller? _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------_=_NextPart_000_01C386B6.781EA530-- From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 11:21:21 2003 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 E7DEF16A4B3 for ; Mon, 29 Sep 2003 11:21:21 -0700 (PDT) Received: from excdmz5.cinfin.com (excdmz5.cinfin.com [216.196.231.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E5DE43FBF for ; Mon, 29 Sep 2003 11:21:21 -0700 (PDT) (envelope-from ANTIGEN_EXCDMZ5@CINFIN.com) Received: by excdmz5.cinfin.com with Internet Mail Service (5.5.2650.21) id ; Mon, 29 Sep 2003 14:21:21 -0400 Message-ID: <7BE4D57FB272D4118D1400508BD9525802BB4C56@excdmz5.cinfin.com> From: ANTIGEN_EXCDMZ5 To: "'troyertm@email.uc.edu'" Date: Mon, 29 Sep 2003 14:21:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C386B6.7B2F0ADA" cc: "'freebsd-hardware@freebsd.org'" Subject: Antigen forwarded attachment 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: Mon, 29 Sep 2003 18:21:22 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C386B6.7B2F0ADA Content-Type: text/plain The entire message "Re: Sil680 RAID Support while installing 5.1-Release", originally sent to you by owner-freebsd-hardware@freebsd.org (owner-freebsd-hardware@freebsd.org), has been forwarded to you from the Antigen Quarantine area. This message may have been re-scanned by Antigen and handled according to the appropriate scan job's settings. ------_=_NextPart_000_01C386B6.7B2F0ADA Content-Type: message/rfc822 From: "owner-freebsd-hardware@freebsd.org" To: troyertm@email.uc.edu Cc: freebsd-hardware@freebsd.org Subject: Re: Sil680 RAID Support while installing 5.1-Release Date: Mon, 29 Sep 2003 14:21:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Hi Travis Troyer, you wrote. TT> I just purchased a Sil680 IDE RAID controller, and have setup TT> a striped RAID array. When I boot from the 5.1 installation TT> CD-ROM, FreeBSD does not recognize them as one disk. I TT> checked the hardware notes, and "Sil680 UDMA6" is listed. TT> Seeing Sil680 listed, I assumed that the RAID capabilities TT> would also be supported. I read something posted awhile back TT> referring to the Sil680 controller, saying it was supported, TT> but dangerous unless using 5.1-Current. Does anybody know TT> anything about the current status of this? Is there anyway to TT> get the FreeBSD installation to recognize my RAID array, or TT> should I just buy another controller? I was wondering about the online Sil 3112 SATA RAID controller on my Gigabyte 7VAXP board. The 5.1 RELEASE boot CD crashes saying it couldn't write to root (which is weird, considering it usually should be able to write to memfs??). Regards, Gabriel _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------_=_NextPart_000_01C386B6.7B2F0ADA-- From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 11:22:19 2003 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 96A2F16A4E0 for ; Mon, 29 Sep 2003 11:22:19 -0700 (PDT) Received: from excdmz5.cinfin.com (excdmz5.cinfin.com [216.196.231.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D00CD44025 for ; Mon, 29 Sep 2003 11:22:18 -0700 (PDT) (envelope-from ANTIGEN_EXCDMZ5@CINFIN.com) Received: by excdmz5.cinfin.com with Internet Mail Service (5.5.2650.21) id ; Mon, 29 Sep 2003 14:22:18 -0400 Message-ID: <7BE4D57FB272D4118D1400508BD9525802BB4C5D@excdmz5.cinfin.com> From: ANTIGEN_EXCDMZ5 To: "'freebsd-hardware@freebsd.org'" Date: Mon, 29 Sep 2003 14:22:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C386B6.9C7A81B0" cc: "'gaml@buz.ch'" Subject: Antigen forwarded attachment 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: Mon, 29 Sep 2003 18:22:19 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C386B6.9C7A81B0 Content-Type: text/plain The entire message "Re: Sil680 RAID Support while installing 5.1-Release", originally sent to you by owner-freebsd-hardware@freebsd.org (owner-freebsd-hardware@freebsd.org), has been forwarded to you from the Antigen Quarantine area. This message may have been re-scanned by Antigen and handled according to the appropriate scan job's settings. ------_=_NextPart_000_01C386B6.9C7A81B0 Content-Type: message/rfc822 From: "owner-freebsd-hardware@freebsd.org" To: freebsd-hardware@freebsd.org Cc: gaml@buz.ch Subject: Re: Sil680 RAID Support while installing 5.1-Release Date: Mon, 29 Sep 2003 14:22:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain on Sat, 27 Sep 2003, gaml@buz.ch wrote: > I was wondering about the online Sil 3112 SATA RAID controller on my > Gigabyte 7VAXP board. The 5.1 RELEASE boot CD crashes saying it > couldn't write to root (which is weird, considering it usually should > be able to write to memfs??). That also seems odd to me. My Gigabyte 8KNXP motherboard also has a Sil 3112 SATA RAID controller. I can configure it in BIOS to operate in either "base" (i.e. SATA) mode or in "raid" mode. My 5.1-RELEASE system just ignores the PCI device in either case because there is no 5.1-RELEASE driver for either personality. (The controller identifies itself slightly differently in its PCI configuration space header depending on the mode.) I recall booting the 5.1-RELEASE CD with the Sil 3112 controller in base mode to see if 5.1-RELEASE had a driver for it and had no problem (and no luck either). Someone recently wrote in one of the freebsd-mailing-lists that they had recently committed a Sil 3112 driver (personality unstated) in the 5.1-current branch. Dan Strick _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------_=_NextPart_000_01C386B6.9C7A81B0-- From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 13:04:22 2003 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 0317D16A4BF for ; Mon, 29 Sep 2003 13:04:22 -0700 (PDT) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 883624402A for ; Mon, 29 Sep 2003 13:04:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 7916 invoked from network); 29 Sep 2003 20:04:17 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 29 Sep 2003 20:04:17 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h8TK4D6Y053839; Mon, 29 Sep 2003 16:04:14 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200309270624.h8R6OBjS000841@ice.nodomain> Date: Mon, 29 Sep 2003 16:04:19 -0400 (EDT) From: John Baldwin To: Dan Strick X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: dan@ice.nodomain cc: freebsd-hardware@freebsd.org Subject: RE: bad BIOS confuses boot0 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: Mon, 29 Sep 2003 20:04:22 -0000 On 27-Sep-2003 Dan Strick wrote: > The AWARD BIOS on my Gigabyte 8KNXP motherboard has been giving me > a hard time for several weeks. Tonight I got around to instrumenting > a copy of /usr/src/sys/boot/i386/boot0/boot0.s and verified my > suspicion. > > The AWARD BIOS loads the MBR from the first drive in the BIOS drive > list, drive code 0x80, but passes the value 0x81 to the bootstrap > program through the %dl register. > > This has a couple of consequences: > > 1) The boot0 program lists the partition on the first drive but > boots the selected partition from the second drive, and > > 2) The boot0 program may overwrite the MBR on the second drive > with a copy of the MBR from the first drive. > > My workaround was to do: > > boot0cfg -Bv -d 0x80 -o setdrv,noupdate ad0 > > The noupdate option is intended to prevent a major disaster if > this drive should ever be assigned a different number by the BIOS. > > I don't like this workaround. It is clumsy and restrictive. > The drive configuration on my PC is in a state of flux. > > Has anyone noticed such antisocial BIOS behavior in the past? > > Is there actually a standard for passing the BIOS drive number through > the %dl register? Do I have grounds for *demanding* that the motherboard > manufacturer get the BIOS fixed? I don't think there is an actual standard for BIOS booting off a hard disk. The defacto standard is to indeed pass in the BIOS device number in %dl, so you likely can complain to your BIOS vendor. It's amazing Windows boots off the thing. Windows may hardcode 0x80 though as a workaround. The boot0cfg -d option exists to workaround this type of bug, so you are using the best workaround available. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 14:06:44 2003 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 6C23F16A4B3 for ; Mon, 29 Sep 2003 14:06:44 -0700 (PDT) Received: from smtp.covadmail.net (mx05.covadmail.net [63.65.120.65]) by mx1.FreeBSD.org (Postfix) with SMTP id 105C24402F for ; Mon, 29 Sep 2003 14:06:42 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 4581 invoked from network); 29 Sep 2003 21:06:37 -0000 Received: from unknown (HELO ice.nodomain) (68.164.196.108) by sun-qmail04 with SMTP; 29 Sep 2003 21:06:36 -0000 Received: from ice.nodomain (localhost [127.0.0.1]) by ice.nodomain (8.12.8p1/8.12.8) with ESMTP id h8TL6mwo000698; Mon, 29 Sep 2003 14:06:48 -0700 (PDT) (envelope-from dan@ice.nodomain) Received: (from dan@localhost) by ice.nodomain (8.12.8p1/8.12.8/Submit) id h8TL6leo000697; Mon, 29 Sep 2003 14:06:47 -0700 (PDT) Date: Mon, 29 Sep 2003 14:06:47 -0700 (PDT) From: Dan Strick Message-Id: <200309292106.h8TL6leo000697@ice.nodomain> To: freebsd-hardware@FreeBSD.org cc: dan@ice.nodomain cc: jhb@FreeBSD.org Subject: RE: bad BIOS confuses boot0 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: Mon, 29 Sep 2003 21:06:44 -0000 On 29-Sep-2003 John Baldwin wrote: > I don't think there is an actual standard for BIOS booting off a hard > disk. The defacto standard is to indeed pass in the BIOS device number > in %dl, so you likely can complain to your BIOS vendor. It's amazing > Windows boots off the thing. Windows may hardcode 0x80 though as a > workaround. The boot0cfg -d option exists to workaround this type of > bug, so you are using the best workaround available. I did some intensive Web searching over the weekend. I could not find an absolutely authoritative BIOS bootstrap standard, however I did find the following: http://www.phoenix.com/resources/specs-bbs101.pdf In 1996 Compaq, Phoenix Technologies, and Intel published a "BIOS Boot Specification, Version 1.01". Appendix D begins, "If O/S's responded to the mechanism of passing the INT 13h drive number to the boot sector as defined by the Plug and Play BIOS Specification, the BIOS could boot from any INT 13h drive." The "Plug and Play BIOS Specification" can be found at: http://www.microsoft.com/whdc/hwdev/tech/PnP/default.mspx under "Industry Standards" as a self extracting pkzipped rich text file. (ugh...) In section 2.4 it says: "The very last function of the system BIOS POST after loading and validating the operating system boot sector is to transfer control. In an ISA system, control is transferred without any parameters. In a Plug and Play system BIOS, parameters will be passed to the operating system. The parameters are: Entry: ES:DI Pointer to System BIOS Plug and Play Installation Check Structure (See section 4.4) DL Physical device number the OS is being loaded from (e.g. 80h, assuming the device supports INT 13H interface.) My Gigabyte 8KNXP motherboard has an Award BIOS. The Award BIOS (see www.award.com) is apparently a product of Phoenix Technologies. I guess I can make the claim that the BIOS behavior is inconsistent with its own manufacturer's specifications. Will Gigabyte care? I don't know. I will ask... Dan Strick strick@covad.net From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 19:18:14 2003 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 A048B16A4B3 for ; Mon, 29 Sep 2003 19:18:14 -0700 (PDT) Received: from smtp.covadmail.net (mx05.covadmail.net [63.65.120.65]) by mx1.FreeBSD.org (Postfix) with SMTP id A532F43FFD for ; Mon, 29 Sep 2003 19:18:13 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 14201 invoked from network); 30 Sep 2003 02:18:08 -0000 Received: from unknown (HELO ice.nodomain) (68.164.196.197) by sun-qmail01 with SMTP; 30 Sep 2003 02:18:08 -0000 Received: from ice.nodomain (localhost [127.0.0.1]) by ice.nodomain (8.12.8p1/8.12.8) with ESMTP id h8U2GwHY001270 for ; Mon, 29 Sep 2003 19:17:19 -0700 (PDT) (envelope-from dan@ice.nodomain) Received: (from dan@localhost) by ice.nodomain (8.12.8p1/8.12.8/Submit) id h8U2BkCZ001224; Mon, 29 Sep 2003 19:11:46 -0700 (PDT) Date: Mon, 29 Sep 2003 19:11:46 -0700 (PDT) From: Dan Strick Message-Id: <200309300211.h8U2BkCZ001224@ice.nodomain> To: freebsd-hardware@FreeBSD.org cc: dan@ice.nodomain Subject: ATA controller cards supported by FreeBSD 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: Tue, 30 Sep 2003 02:18:14 -0000 Does FreeBSD support any PCI ATA controller cards other than those made by HighPoint and Promise? Everything else that I can identify in the ATA section of the HARDWARE.TXT file seems to be a CPU support chipset. I am confused by the HighPoint model numbers listed. HPT370, HPT372, and HPT374 are RAID controller ICs. The Rocket133 ATA controller card made by HighPoint uses the HPT302 IC, which is not listed in the HARDWARE.TXT file. (Is it too new? Is it not supported?) Given that HighPoint sports a FreeBSD logo on its web site, I would expect broader hardware support. I am also a little confused by the Promise products listed in the HARDWARE.TXT file. Every single FastTrak or TX2000 product listed on the Promise web site is a RAID controller. The only ATA controller from the HARDWARE.TXT file described on the Promise web site is the Ultra-133 TX2. The other Ultra-xxx products are presumably old and discontinued. Summary: with the *single* exception of the Promise Ultra-133 TX2, every single supported ATA controller listed in the HARDWARE.TXT file is either old/discontinued, a chipset, or actually a RAID controller and not an ATA controller. This can't be right. Surely FreeBSD supports a bunch of PCI ATA controller cards. What/Where are they? If I took the HARDWARE.TXT file literally, I would also have to conclude that FreeBSD did not support a single ISA ATA controller card. I must have missed something really obvious and important. Can someone point me in the right direction. Dan Strick strick@covad.net From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 20:14:24 2003 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 7C66416A4B3 for ; Mon, 29 Sep 2003 20:14:24 -0700 (PDT) Received: from smtp012.mail.yahoo.com (smtp012.mail.yahoo.com [216.136.173.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 55D1943F85 for ; Mon, 29 Sep 2003 20:14:23 -0700 (PDT) (envelope-from q_dolan@yahoo.com.au) Received: from vdub.onthenet.net (HELO ?172.22.1.10?) (q?dolan@203.10.89.16 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 Sep 2003 03:14:22 -0000 From: Q To: Dan Strick In-Reply-To: <200309300211.h8U2BkCZ001224@ice.nodomain> References: <200309300211.h8U2BkCZ001224@ice.nodomain> Message-Id: <1064891658.35687.57.camel@boxster> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 30 Sep 2003 13:14:18 +1000 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-hardware@FreeBSD.org Subject: Re: ATA controller cards supported by FreeBSD 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: Tue, 30 Sep 2003 03:14:24 -0000 I think you will find that the only distinction between most of these "ATA Raid Controllers" and a regular "ATA Controller", is the BIOS code used to manage the array and boot from the set. The RAID itself is most often done in software by the driver and not in hardware. These cards are NOT true "Hardware RAID", but rather hardware assisted software raid. For example, the earlier Promise Ultra66 (non-raid) cards can be upgraded to be a "FastTrack66" (raid) by simply grounding pin 23 on the bios chip with a 100ohm resistor and reflashing the onboard BIOS with the FastTrack66 bios. They are that similar. In short, these "ATA Raid controllers" are usually just a regular ATA Controller with a fancy BIOS, and will function perfectly well as a regular ATA controller if that's what you are after. Seeya...Q On Tue, 2003-09-30 at 12:11, Dan Strick wrote: > Does FreeBSD support any PCI ATA controller cards other than those > made by HighPoint and Promise? Everything else that I can identify > in the ATA section of the HARDWARE.TXT file seems to be a CPU support > chipset. > > I am confused by the HighPoint model numbers listed. HPT370, HPT372, > and HPT374 are RAID controller ICs. The Rocket133 ATA controller card > made by HighPoint uses the HPT302 IC, which is not listed in the > HARDWARE.TXT file. (Is it too new? Is it not supported?) > Given that HighPoint sports a FreeBSD logo on its web site, I would > expect broader hardware support. > > I am also a little confused by the Promise products listed in the > HARDWARE.TXT file. Every single FastTrak or TX2000 product listed > on the Promise web site is a RAID controller. The only ATA controller > from the HARDWARE.TXT file described on the Promise web site is the > Ultra-133 TX2. The other Ultra-xxx products are presumably old and > discontinued. > > Summary: with the *single* exception of the Promise Ultra-133 TX2, > every single supported ATA controller listed in the HARDWARE.TXT file > is either old/discontinued, a chipset, or actually a RAID controller > and not an ATA controller. > > This can't be right. Surely FreeBSD supports a bunch of PCI ATA > controller cards. What/Where are they? > > If I took the HARDWARE.TXT file literally, I would also have to > conclude that FreeBSD did not support a single ISA ATA controller > card. > > I must have missed something really obvious and important. > Can someone point me in the right direction. > > Dan Strick > strick@covad.net > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 29 21:36:30 2003 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 4B3B816A4BF for ; Mon, 29 Sep 2003 21:36:30 -0700 (PDT) Received: from smtp102.mail.sc5.yahoo.com (smtp102.mail.sc5.yahoo.com [216.136.174.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 232DF4400F for ; Mon, 29 Sep 2003 21:36:29 -0700 (PDT) (envelope-from q_dolan@yahoo.com.au) Received: from vdub.onthenet.net (HELO ?172.22.1.10?) (q?dolan@203.10.89.16 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 Sep 2003 04:36:28 -0000 From: Q To: freebsd-hackers@freebsd.org Message-Id: <1064896584.35687.63.camel@boxster> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 30 Sep 2003 14:36:25 +1000 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-hardware@freebsd.org Subject: nForce MCP network driver - working 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: Tue, 30 Sep 2003 04:36:30 -0000 Hi, I am in the final stages of porting the NVidia Linux nForce MCP network driver to FreeBSD-5.1 and am after some experienced users/developers with access to this hardware to do some testing to find out what breaks, and what doesn't work. My driver makes use of the Linux nvnetlib.o API library, and should therefore be compliant with the NVidia Linux distribution license. The driver currently appears to be stable on my hardware (an MSI K7N420 Pro), although I haven't done much stress testing, nor do I have access to an nForce2 based motherboard to test. This is still very much a work in progress, but it has been stable enough for me to actually use productively so I thought I would share the wealth, so to speak, with the rest of the community. If you are interested in testing this, email me offline. I am also interested in how many people would like to see a FreeBSD-4.x version. PS: I am still waiting for NVidia to reply to any of my emails. :( -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan q_dolan@yahoo.com.au __ __/ / / __/ / / / __ / _/ / / Gold Coast, QLD, Australia __/ __/ __/ ____/ / - / Ph: +61 419 729 806 _______ / _\ From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 30 06:15:16 2003 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 D718216A4B3 for ; Tue, 30 Sep 2003 06:15:16 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5064E43FE9 for ; Tue, 30 Sep 2003 06:15:14 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-2.aaa.net.au [203.14.230.67]) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h8UDF9is000760 for ; Tue, 30 Sep 2003 23:15:10 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h8UDHWfx074945 for ; Tue, 30 Sep 2003 23:17:34 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h8UC7GgA074874 for ; Tue, 30 Sep 2003 22:07:16 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Tue, 30 Sep 2003 22:07:16 +1000 (EST) From: Andrew MacIntyre To: freebsd-hardware@freebsd.org In-Reply-To: <200309300211.h8U2BkCZ001224@ice.nodomain> Message-ID: <20030930220008.B74851@bullseye.apana.org.au> References: <200309300211.h8U2BkCZ001224@ice.nodomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) Subject: Re: ATA controller cards supported by FreeBSD 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: Tue, 30 Sep 2003 13:15:17 -0000 On Mon, 29 Sep 2003, Dan Strick wrote: > Does FreeBSD support any PCI ATA controller cards other than those > made by HighPoint and Promise? Everything else that I can identify > in the ATA section of the HARDWARE.TXT file seems to be a CPU support > chipset. > > I am confused by the HighPoint model numbers listed. HPT370, HPT372, > and HPT374 are RAID controller ICs. The Rocket133 ATA controller card > made by HighPoint uses the HPT302 IC, which is not listed in the > HARDWARE.TXT file. (Is it too new? Is it not supported?) > Given that HighPoint sports a FreeBSD logo on its web site, I would > expect broader hardware support. > > I am also a little confused by the Promise products listed in the > HARDWARE.TXT file. Every single FastTrak or TX2000 product listed > on the Promise web site is a RAID controller. The only ATA controller > from the HARDWARE.TXT file described on the Promise web site is the > Ultra-133 TX2. The other Ultra-xxx products are presumably old and > discontinued. > > Summary: with the *single* exception of the Promise Ultra-133 TX2, > every single supported ATA controller listed in the HARDWARE.TXT file > is either old/discontinued, a chipset, or actually a RAID controller > and not an ATA controller. > > This can't be right. Surely FreeBSD supports a bunch of PCI ATA > controller cards. What/Where are they? > > If I took the HARDWARE.TXT file literally, I would also have to > conclude that FreeBSD did not support a single ISA ATA controller > card. > > I must have missed something really obvious and important. > Can someone point me in the right direction. I believe that CMD 64[789] based PCI controllers are supported (I had one running on a 4.7 system anyway). AFAIK, the Highpoint controllers can be used for JBOD - you just don't define an array. Ditto for many Promise controllers, though driver support is more patchy. FreeBSD 5's ATA code also supports Intersil (I think; may have the mfr name wrong) based controllers. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 30 10:55:04 2003 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 4BB3D16A4B3 for ; Tue, 30 Sep 2003 10:55:04 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9BA9443FE5 for ; Tue, 30 Sep 2003 10:55:03 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 21910 invoked by uid 1068); 30 Sep 2003 17:55:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Sep 2003 17:55:03 -0000 Date: Tue, 30 Sep 2003 10:55:03 -0700 (PDT) From: David Raistrick To: hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: SMP and Supermicro, problems! 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: Tue, 30 Sep 2003 17:55:04 -0000 Folks, My Supermicro 6023P-8R arrived and I've started working with it. 2 2.4Ghz 533FSB Xeons and 512 megs of ram. This has the X5DP8 motherboard. (e7501 chipset) Installed FreeBSD 4.8-RELEASE (development constraints currently restrict this to 4.8-R.) and everything is fine w/o SMP. Hyperthreading /disabled/ in the Bios and NOT enabled in the kernel. Added options SMP and APIC_IO to a generic kernel and rebuilt it. Rebooted to serious problems. I removed my PCI devices just to be sure, and still have the same problems. If anyone has suggestions please let me know. I'm also sending a copy of this message to Supermicro support. Details below: PhoenixBIOS 4.0 Release 6.0 Copyright 1985-2001 Phoenix Technologies Ltd. All Rights Reserved Supermicro X5DP8-G2/X5DPE-G2 BIOS Rev 1.4c The most common error message is: ahd0: Timedout SCB already complete. Interrupts may not be functioning. ahd0: Timedout SCB already complete. Interrupts may not be functioning. em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting The machine usually freezes sometime during the boot, or just after boot, outputing these messages every few minutes. On some boots, I get this message before boot. It eventually repeats, boot never continuing (LONG error message): Waiting 15 seconds for SCSI devices to settle (probe3:ahd0:0:3:0): SCB 0xc - timed out >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x10f Mode 0x33 Card was paused HS_MAILBOX[0x0] INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) SCSISIGI[0xb6]:(P_MESGOUT|REQI|BSYI|ATNI) SCSIPHASE[0x0] SCSIBUS[0xc0] LASTPHASE[0xa0]:(P_MESGOUT) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x40]:(NO_CDB_SENT) SEQ_FLAGS2[0x0] SSTAT0[0x2]:(SPIORDY) SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xc NEXTSCB 0x0 qinstart = 38 qinfifonext = 39 QINFIFO: 0xf WAITING_TID_QUEUES: Pending list: 15 FIFO_USE[0x0] SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x7] 12 FIFO_USE[0x0] SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x37] Total 2 Kernel Free SCB list: 9 1 2 3 4 5 6 7 8 10 11 13 14 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0 SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVE SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xc SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVE SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x52 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 SIMODE0[0xc]:(ENOVERRUN|ENIOERR) CCSCBCTL[0x4]:(CCSCBDIR) ahd0: REG0 == 0xc, SINDEX = 0x107, DINDEX = 0xe1 ahd0: SCBPTR == 0xc, SCB_NEXT == 0xff00, SCB_NEXT2 == 0xff12 CDB 0 0 0 0 0 0 STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> I have complete boot messages available if anyone needs them, and will be happy to supply any other information you folks need. FWIW, I tried a ~Aug 8 2003 -STABLE kernel with SMP enabled with identical results. --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 30 13:45:13 2003 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 DA43116A4B3; Tue, 30 Sep 2003 13:45:13 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D019344005; Tue, 30 Sep 2003 13:45:12 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id BD2CC2A7EA; Tue, 30 Sep 2003 13:45:12 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Q In-Reply-To: <1064896584.35687.63.camel@boxster> Date: Tue, 30 Sep 2003 13:45:12 -0700 From: Peter Wemm Message-Id: <20030930204512.BD2CC2A7EA@canning.wemm.org> cc: freebsd-hackers@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: nForce MCP network driver - working 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: Tue, 30 Sep 2003 20:45:14 -0000 Q wrote: > Hi, > > I am in the final stages of porting the NVidia Linux nForce MCP network > driver to FreeBSD-5.1 and am after some experienced users/developers > with access to this hardware to do some testing to find out what breaks, > and what doesn't work. My driver makes use of the Linux nvnetlib.o API > library, and should therefore be compliant with the NVidia Linux > distribution license. > > The driver currently appears to be stable on my hardware (an MSI K7N420 Pro), > although I haven't done much stress testing, nor do I have access to an > nForce2 based motherboard to test. I have a set of nForce2 and nForce3 based boards, but they all run 5.x and the nForce3 is an athlon64 system. > This is still very much a work in progress, but it has been stable > enough for me to actually use productively so I thought I would share > the wealth, so to speak, with the rest of the community. > > If you are interested in testing this, email me offline. I am also > interested in how many people would like to see a FreeBSD-4.x version. > > PS: I am still waiting for NVidia to reply to any of my emails. :( Fun fun. :-( Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 30 13:59:20 2003 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 3DA5516A4B3 for ; Tue, 30 Sep 2003 13:59:20 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3BE7A43FFB for ; Tue, 30 Sep 2003 13:59:17 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 42021 invoked by uid 1068); 30 Sep 2003 20:59:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Sep 2003 20:59:16 -0000 Date: Tue, 30 Sep 2003 13:59:16 -0700 (PDT) From: David Raistrick To: freebsd-scsi@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: support@supermicro.com cc: freebsd-hardware@freebsd.org Subject: Re: SCSI, SMP, and Supermicro, problems! 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: Tue, 30 Sep 2003 20:59:20 -0000 > maybe posting your 'mptable' output to the list > will help things. Thanks. Here goes. fred:/root%# mptable =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f6810 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xfe mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x0009f9a0 signature: 'PCMP' base table length: 388 version: 1.4 checksum: 0x29 OEM ID: ' ' Product ID: 'Kings Canyon' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 40 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x14 BSP, usable 15 2 5 0xbfebf 6 0x14 AP, usable 15 2 5 0xbfebf -- Bus: Bus ID Type 0 PCI 1 PCI 2 PCI 3 PCI 4 PCI 5 PCI 6 PCI 7 PCI 8 ISA -- I/O APICs: APIC ID Version State Address 2 0x20 usable 0xfec00000 3 0x20 usable 0xfec80000 4 0x20 usable 0xfec80400 5 0x20 usable 0xfec81000 8 0x20 usable 0xfec81400 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 8 0 2 0 INT active-hi edge 8 1 2 1 INT active-hi edge 8 0 2 2 INT active-hi edge 8 3 2 3 INT active-hi edge 8 4 2 4 INT active-hi edge 8 5 2 5 INT active-hi edge 8 6 2 6 INT active-hi edge 8 7 2 7 INT active-hi edge 8 8 2 8 INT active-hi edge 8 9 2 9 INT active-lo level 0 29:B 2 19 INT active-lo level 0 29:A 2 16 INT active-hi edge 8 12 2 12 INT active-hi edge 8 13 2 13 INT active-hi edge 8 14 2 14 INT active-hi edge 8 15 2 15 INT active-lo level 0 29:C 2 18 INT active-lo level 3 2:A 3 4 INT active-lo level 3 2:B 3 5 INT active-lo level 6 2:A 5 4 INT active-lo level 6 2:B 5 5 INT active-lo level 7 1:A 2 16 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 8 0 255 0 NMI active-hi edge 8 0 255 1 =============================================================================== --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 07:07:25 2003 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 0A70316A4C1 for ; Wed, 1 Oct 2003 07:07:25 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id C590943FF5 for ; Wed, 1 Oct 2003 07:07:23 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 44827 invoked by uid 1068); 1 Oct 2003 14:07:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Oct 2003 14:07:23 -0000 Date: Wed, 1 Oct 2003 07:07:23 -0700 (PDT) From: David Raistrick To: freebsd-scsi@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: support@supermicro.com cc: freebsd-hardware@freebsd.org Subject: Re: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 14:07:25 -0000 It was recommended by supermicro support, as well as a list member, to update the Seagate 15k disks to firmware 0006. I've done this: da0: Fixed Direct Access SCSI-3 device da1: Fixed Direct Access SCSI-3 device The results are that the system still has the same problems: Works fine with a UP kernel, hangs/errors with a SMP kernel. " Starting final network daemons: mountd NFS on reserved port only=YES nfsd rpc.s. ELF ldconfig path: /usr/lib /usr/lib/compat /usr/local/lib a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Starting standard daemons: inetd cron sshd usbd sendmail sendmail-clientmqueueeg ahd0: Timedout SCB already complete. Interrupts may not be functioning. ahd0: Timedout SCB already complete. Interrupts may not be functioning. " The other issues I'm seeing, with the em0 watchdog timeouts, are mentioned as a bug in 4.8-R here: http://lists.freebsd.org/pipermail/freebsd-stable/2003-April/000551.html I'll try this workaround shortly. Further update: Since the above, I rebooted the system again...and for the first time I have a running SMP system. Still seeing the em0 timeouts, I'm going to try the workaround. ...david --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 07:09:55 2003 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 DD1D016A4BF for ; Wed, 1 Oct 2003 07:09:55 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A4FED43F93 for ; Wed, 1 Oct 2003 07:09:54 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 45244 invoked by uid 1068); 1 Oct 2003 14:09:54 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Oct 2003 14:09:54 -0000 Date: Wed, 1 Oct 2003 07:09:54 -0700 (PDT) From: David Raistrick To: freebsd-scsi@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: support@supermicro.com cc: freebsd-hardware@freebsd.org Subject: Re: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 14:09:56 -0000 > Since the above, I rebooted the system again...and for the first time I > have a running SMP system. ...which degraded into being hung right after I sent the last email: ahd0: Timedout SCB already complete. Interrupts may not be functioning. ahd0: Timedout SCB already complete. Interrupts may not be functioning. Anyone have futher suggestions? --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 11:41:44 2003 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 2484B16A4B3; Wed, 1 Oct 2003 11:41:44 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 047B743FE3; Wed, 1 Oct 2003 11:41:43 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 1 Oct 2003 14:41:42 -0400 Message-ID: From: Don Bowman To: 'David Raistrick' , Richy Kim , freebsd-scsi@freebsd.org Date: Wed, 1 Oct 2003 14:41:32 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-hardware@freebsd.org Subject: RE: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 18:41:44 -0000 From: David Raistrick [mailto:drais@wow.atlasta.net] > > Since the above, I rebooted the system again...and for the > first time I > > have a running SMP system. > > ...which degraded into being hung right after I sent the last email: > > ahd0: Timedout SCB already complete. Interrupts may not be > functioning. > > ahd0: Timedout SCB already complete. Interrupts may not be > functioning. > Well, another suggestion has to do with the use of the APIC and interrupt rotation. I can't recall the exact details of this, we ended up adding a 'options UNSWIZZLE' to the kernel. This was specifically for stuff behind a bridge. The problem was that BSD only allowed 24 interrupts, and we had run out. --don From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 11:57:57 2003 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 9626A16A4B3; Wed, 1 Oct 2003 11:57:57 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4367343FF7; Wed, 1 Oct 2003 11:57:54 -0700 (PDT) (envelope-from rkim@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 1 Oct 2003 14:57:53 -0400 Message-ID: From: Richy Kim To: "'freebsd-scsi@freebsd.org'" Date: Wed, 1 Oct 2003 14:57:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-hardware@freebsd.org'" Subject: RE: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 18:57:57 -0000 David, patch below basically compacts or unswizzles the pin-pin to 1:1 mapping when the mptable is parsed, thus saving a few interrupts... This is more so a workaround than a solution to FreeBSD's (4.x and older) historical interrupt limits. -r. Index: mp_machdep.c =================================================================== RCS file: /cvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.115.2.12 retrieving revision 1.115.2.12.1000.1 diff -u -r1.115.2.12 -r1.115.2.12.1000.1 --- mp_machdep.c 28 Apr 2002 18:18:17 -0000 1.115.2.12 +++ mp_machdep.c 14 Aug 2003 15:33:01 -0000 1.115.2.12.1000.1 @@ -27,6 +27,7 @@ #include "opt_cpu.h" #include "opt_user_ldt.h" +#include "opt_unswizzle.h" #ifdef SMP #include @@ -1404,6 +1405,30 @@ int_entry(int_entry_ptr entry, int intr) { int apic; +#ifdef UNSWIZZLE + int src_pin = entry->src_bus_irq & 3; + int dst_pin = entry->dst_apic_int & 3; + int slot = (entry->src_bus_irq >> 2) & 0x1f; + + if (src_pin != dst_pin) { + /* not 1:1 mapping, possibly a swizzled (pci) device behind a bridge */ + + /* swizzle src pin based pci 1.1 spec */ + int pin = (src_pin + slot) % 4; + + if (pin == dst_pin) { + /* BIOS has properly swizzled/rotated pins for this device + * However, we will un-swizzle the pin to get 1:1 mapping. + * This will save us some interrupts in cases where all + * slots behind the bridge use only first two pins anyways. + */ + + printf("IOAPIC: unswizzle intpin %d", entry->dst_apic_int); + entry->dst_apic_int = (entry->dst_apic_int & ~3) + src_pin; + printf(" --> %d\n", entry->dst_apic_int); + } + } +#endif io_apic_ints[intr].int_type = entry->int_type; io_apic_ints[intr].int_flags = entry->int_flags; -----Original Message----- From: Don Bowman Sent: Wednesday, October 01, 2003 2:42 PM To: 'David Raistrick'; Richy Kim; freebsd-scsi@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: RE: SCSI, SMP, and Supermicro, problems! From: David Raistrick [mailto:drais@wow.atlasta.net] > > Since the above, I rebooted the system again...and for the > first time I > > have a running SMP system. > > ...which degraded into being hung right after I sent the last email: > > ahd0: Timedout SCB already complete. Interrupts may not be > functioning. > > ahd0: Timedout SCB already complete. Interrupts may not be > functioning. > Well, another suggestion has to do with the use of the APIC and interrupt rotation. I can't recall the exact details of this, we ended up adding a 'options UNSWIZZLE' to the kernel. This was specifically for stuff behind a bridge. The problem was that BSD only allowed 24 interrupts, and we had run out. --don From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 12:59:08 2003 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 062BD16A4B3 for ; Wed, 1 Oct 2003 12:59:08 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DF35C43FFD for ; Wed, 1 Oct 2003 12:59:06 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 83944 invoked by uid 1068); 1 Oct 2003 19:59:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Oct 2003 19:59:06 -0000 Date: Wed, 1 Oct 2003 12:59:06 -0700 (PDT) From: David Raistrick To: Don Bowman In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org cc: Richy Kim Subject: RE: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 19:59:08 -0000 Thanks everyone for all of the suggestions and help. Between Supermicro Support and myself we've decided to RMA the motherboard...it seems to have various issues: Doesn't boot with tested-good recommended memory (Kingston KVR266X72RC25/25) SCSI related crashes with a UP 4.7-R GENERIC kernel ATA related crashes with a SMP 4.7-R kernel when SCSI disabled (jumper J22) SCSI & ATA crashes with SMP 4.8-R kernel, with or without SCSI disks installed. Hopefully a replacement board will clear most of this up. I do know I'll need to tweak the 4.8-R em driver to fix the watchdog timeouts, and I may need to apply Richy's UNSWIZZLE patch down the road. The board is /very/ recent, dated 08/03...it's possible that it's just a bad one. Fingers crossed! ...david (awaiting the advance replacement) --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 13:36:25 2003 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 772C316A4B3 for ; Wed, 1 Oct 2003 13:36:25 -0700 (PDT) Received: from atlasta.net (wow.atlasta.net [12.129.13.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B31D843FF3 for ; Wed, 1 Oct 2003 13:36:19 -0700 (PDT) (envelope-from drais@wow.atlasta.net) Received: (qmail 87906 invoked by uid 1068); 1 Oct 2003 20:36:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Oct 2003 20:36:19 -0000 Date: Wed, 1 Oct 2003 13:36:19 -0700 (PDT) From: David Raistrick To: freebsd-scsi@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org Subject: RE: SCSI, SMP, and Supermicro, problems! 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: Wed, 01 Oct 2003 20:36:25 -0000 [top posting another detail for the archives] Supermicro SuperServer 6023P-8R with the X5DP8-G2 motherboard. On Wed, 1 Oct 2003, David Raistrick wrote: > > Thanks everyone for all of the suggestions and help. > > Between Supermicro Support and myself we've decided to RMA the > motherboard...it seems to have various issues: > > Doesn't boot with tested-good recommended memory (Kingston > KVR266X72RC25/25) > SCSI related crashes with a UP 4.7-R GENERIC kernel > ATA related crashes with a SMP 4.7-R kernel when SCSI disabled (jumper > J22) > SCSI & ATA crashes with SMP 4.8-R kernel, with or without SCSI disks > installed. > > > Hopefully a replacement board will clear most of this up. I do know I'll > need to tweak the 4.8-R em driver to fix the watchdog timeouts, and I may > need to apply Richy's UNSWIZZLE patch down the road. > > The board is /very/ recent, dated 08/03...it's possible that it's just a > bad one. > > Fingers crossed! > > ...david (awaiting the advance replacement) > > > > > --- > david raistrick > drais@atlasta.net http://www.expita.com/nomime.html > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > --- david raistrick drais@atlasta.net http://www.expita.com/nomime.html From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 14:06:35 2003 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 472DF16A4B3 for ; Wed, 1 Oct 2003 14:06:35 -0700 (PDT) Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB3343FBD for ; Wed, 1 Oct 2003 14:06:29 -0700 (PDT) (envelope-from butch@infowest.com) Received: from [216.190.25.234] (unknown [216.190.25.234]) by delivery.infowest.com (Postfix) with ESMTP id E0B53EA8BC7 for ; Wed, 1 Oct 2003 15:06:28 -0600 (MDT) User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Wed, 01 Oct 2003 15:06:13 -0600 From: "Cassidy B. Larson" To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: 3ware escalade 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: Wed, 01 Oct 2003 21:06:35 -0000 I'm actually having a bit of a problem with the 3ware 8506 running 5.1, or -CURRENT from a week ago. I can use the machine just fine with all 8, 160GB Seagate (ST3160023AS) drives working happily in their RAID5 configuration. I've been trying to simulate a drive failure, and pull one of the hot swap drives out while the machine is live. I get a message warning me the array is running in degraded mode, plug the drive back in, go to my 3dmd web manager and try rebuilding the array (or from the 3ware bios to rebuild). Rebuilding starts just fine. However, when I reboot (during rebuilding phase) the kernel loads and the device drivers proceed to load and go through normal bootup phase. However, about the point that the machine verifies the slices are clean, I get a core-dump and error out. From there, the only option is to reboot the machine, which results in the same, unable to mount the drives stage (inoperable). I'm going to try another testing method and create a 2 drive mirror array and a 6 drive RAID5. Hopefully, if I pull one of the drives of the RAID5, I can boot successfully during Rebuilding stage. Then the next test is to pull one of the mirrored array. Anybody have similar experiences with the 8506 and rebooting in a Rebuilding stage, but unable to use the OS? I'd be interested to hear. If more information is needed, please let me know as I can record the errors appropriately after this next Array gets built and the OS installed. Thanks, Cassidy From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 1 14:23:02 2003 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 841DC16A4B3 for ; Wed, 1 Oct 2003 14:23:02 -0700 (PDT) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 104D643FA3 for ; Wed, 1 Oct 2003 14:23:00 -0700 (PDT) (envelope-from simon@optinet.com) Received: (qmail 18488 invoked by uid 110); 1 Oct 2003 21:23:01 -0000 Received: from ool-18baaf5c.dyn.optonline.net (HELO win2kpc1) (24.186.175.92) by cobra.acceleratedweb.net with SMTP; 1 Oct 2003 21:23:01 -0000 From: "Simon" To: "Cassidy B. Larson" , "freebsd-hardware@freebsd.org" Date: Wed, 01 Oct 2003 17:22:48 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: MIME-Version: 1.0 Message-Id: <20031001212300.104D643FA3@mx1.FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: 3ware escalade 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: Wed, 01 Oct 2003 21:23:02 -0000 Why are you rebooting in a middle of a rebuild? I didn't know this is acceptable. I thought about it, but didn't actually try it. Rebuilds without interruption work fine with my 7500-8 controller with 8 IBM drives in RAID5 running 5.1-R -Simon On Wed, 01 Oct 2003 15:06:13 -0600, Cassidy B. Larson wrote: > > >I'm actually having a bit of a problem with the 3ware 8506 running 5.1, or >-CURRENT from a week ago. > >I can use the machine just fine with all 8, 160GB Seagate (ST3160023AS) >drives working happily in their RAID5 configuration. I've been trying to >simulate a drive failure, and pull one of the hot swap drives out while the >machine is live. I get a message warning me the array is running in >degraded mode, plug the drive back in, go to my 3dmd web manager and try >rebuilding the array (or from the 3ware bios to rebuild). Rebuilding starts >just fine. > >However, when I reboot (during rebuilding phase) the kernel loads and the >device drivers proceed to load and go through normal bootup phase. However, >about the point that the machine verifies the slices are clean, I get a >core-dump and error out. From there, the only option is to reboot the >machine, which results in the same, unable to mount the drives stage >(inoperable). > >I'm going to try another testing method and create a 2 drive mirror array >and a 6 drive RAID5. Hopefully, if I pull one of the drives of the RAID5, I >can boot successfully during Rebuilding stage. Then the next test is to >pull one of the mirrored array. > >Anybody have similar experiences with the 8506 and rebooting in a Rebuilding >stage, but unable to use the OS? I'd be interested to hear. > >If more information is needed, please let me know as I can record the errors >appropriately after this next Array gets built and the OS installed. > >Thanks, > >Cassidy > >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 02:38:05 2003 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 C038C16A4BF for ; Thu, 2 Oct 2003 02:38:05 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id AD48543FBD for ; Thu, 2 Oct 2003 02:38:02 -0700 (PDT) (envelope-from pilkis@gmx.net) Received: (qmail 6886 invoked by uid 65534); 2 Oct 2003 09:38:01 -0000 Received: from unknown (EHLO pilkishome) (62.68.63.42) by mail.gmx.net (mp023) with SMTP; 02 Oct 2003 11:38:01 +0200 X-Authenticated: #6832473 Message-ID: <051501c388c8$dfe0bc30$1e64a8c0@spotripoli.local> From: "Putinas" To: Date: Thu, 2 Oct 2003 11:38:01 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: fasttrack 100 raid0 and low write speed 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: Thu, 02 Oct 2003 09:38:05 -0000 Hi all, I have in my 4-STABLE system 2 drives in RAID 0 configuration: ATA channel 2: Master: ad4 ATA/ATAPI rev 5 Slave: no device present ATA channel 3: Master: ad6 ATA/ATAPI rev 5 Slave: no device present and following controller atapci0: port 0x9800-0x983f,0xa000-0xa003,0xa400-0xa407,0xa800-0xa803,0xb000-0xb007 mem 0xf0800000-0xf081ffff irq 9 at device 11.0 on pci2 ( only this controller is sitting on irq 9 ) and I have noticed very low write speed with samba , transfer speeds are lower then 1 mb/s, here is output from iostat tty ad2 ad4 ad6 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 9813 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 16 0 5 3 76 0 77 0.00 0 0.00 128.00 7 0.87 128.00 7 0.87 0 0 2 9 88 0 78 128.00 1 0.12 128.00 7 0.87 128.00 7 0.87 1 0 4 9 87 0 80 0.00 0 0.00 128.00 7 0.87 128.00 8 1.00 0 0 5 14 81 0 79 0.00 0 0.00 128.00 6 0.75 128.00 6 0.75 0 0 2 3 95 0 78 0.00 0 0.00 87.00 27 2.29 75.69 26 1.92 2 0 8 22 68 when read speed goes more then 8mb/s transfer via wire already, after playing with samba settings I found out what writing to ad2 drive which is not RAID0 part goes up to 7-8Mb/s without problem. So all my guessing about wrong samba or network tuning was wrong and I come to the point: why writes to array are so slow ? Is it "normal" or there is a way to fix this somehow ? Please reply me directly to e-mail ( if there will be any ;-) Thank you, Putinas From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 08:29:08 2003 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 8003016A4BF for ; Thu, 2 Oct 2003 08:29:08 -0700 (PDT) Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D61843FE3 for ; Thu, 2 Oct 2003 08:29:06 -0700 (PDT) (envelope-from butch@infowest.com) Received: from [216.190.25.234] (unknown [216.190.25.234]) by delivery.infowest.com (Postfix) with ESMTP id 0444FEA870A; Thu, 2 Oct 2003 09:29:06 -0600 (MDT) User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 02 Oct 2003 09:28:50 -0600 From: "Cassidy B. Larson" To: Simon , "freebsd-hardware@freebsd.org" Message-ID: In-Reply-To: <20031001212303.A59E4EA791C@mailbox.infowest.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Re: 3ware escalade 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: Thu, 02 Oct 2003 15:29:08 -0000 I would think for Redundancy in a RAID array a hardware controller should be allowed to have the machine reboot during a rebuild process and not loose track of where it is, and still run in degraded mode. Last test was a RAID10 rebuild, to see if a reboot would load the OS fine. It appears it successfully reboots during a rebuild phase. Strange how a RAID5 wouldn't boot and a RAID10 would. I'll try RAID5 once more to see if I got something amiss. However, I do like the speed of a RAID10.. Maybe I'll just keep it. Cassidy On 10/1/03 3:22 PM, "Simon" wrote: > > Why are you rebooting in a middle of a rebuild? I didn't know this is > acceptable. > I thought about it, but didn't actually try it. Rebuilds without interruption > work fine > with my 7500-8 controller with 8 IBM drives in RAID5 running 5.1-R > > -Simon From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 10:05:14 2003 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 941D516A4B3 for ; Thu, 2 Oct 2003 10:05:14 -0700 (PDT) Received: from mail.johnrshannon.com (mail.johnrshannon.com [69.20.155.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF76143FBF for ; Thu, 2 Oct 2003 10:05:12 -0700 (PDT) (envelope-from john@johnrshannon.com) Received: by mail.johnrshannon.com (Postfix, from userid 1003) id 3D779124B9; Thu, 2 Oct 2003 11:05:12 -0600 (MDT) Received: from pablo.internal.johnrshannon.com (pablo.internal.johnrshannon.com [192.168.1.34]) by mail.johnrshannon.com (Postfix) with ESMTP id 92E11124B4 for ; Thu, 2 Oct 2003 11:05:11 -0600 (MDT) Received: by pablo.internal.johnrshannon.com (Postfix, from userid 1001) id 0B97DBA; Thu, 2 Oct 2003 11:05:11 -0600 (MDT) From: "John R. Shannon" To: freebsd-hardware@freebsd.org Date: Thu, 2 Oct 2003 11:05:01 -0600 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200310021105.10872.john@johnrshannon.com> Subject: Hyperthreading Kernel Configuration - 5.1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: john@johnrshannon.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2003 17:05:14 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On a new computer, dmesg shows: CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf29 Stepping =3D 9 Features=3D0xbfebfbff Hyperthreading: 2 logical CPUs acpi_cpu0: port 0x530-0x537 on acpi0 acpi_cpu1: port 0x530-0x537 on acpi0 Should options SMP and APIC_IO be enabled in kernel? =2D --=20 John R. Shannon john@johnrshannon.com =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iEYEARECAAYFAj98WsQACgkQOKbCxya4HYthOQCff6xp1f1QsK88mPcv/bNBn6Mn NzMAn0DJRYm12ZW7Bst2w52OCmlpjcmn =3DURzX =2D----END PGP SIGNATURE----- From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 10:10:16 2003 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 C6C2F16A4B3 for ; Thu, 2 Oct 2003 10:10:16 -0700 (PDT) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E883243F93 for ; Thu, 2 Oct 2003 10:10:14 -0700 (PDT) (envelope-from damian@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h92HAEl7018347 for ; Thu, 2 Oct 2003 13:10:14 -0400 (EDT) (envelope-from damian@sentex.net) Received: from pegmatite.sentex.ca (pegmatite.sentex.ca [192.168.42.92]) by lava.sentex.ca (8.12.9p1/8.12.9) with ESMTP id h92HAEdJ092650 for ; Thu, 2 Oct 2003 13:10:14 -0400 (EDT) (envelope-from damian@sentex.net) Received: by pegmatite.sentex.ca (Postfix, from userid 1001) id E8715170F3; Thu, 2 Oct 2003 13:09:52 -0400 (EDT) Date: Thu, 2 Oct 2003 13:09:52 -0400 From: Damian Gerow To: hardware@freebsd.org Message-ID: <20031002170952.GF15256@sentex.net> References: <200310021105.10872.john@johnrshannon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200310021105.10872.john@johnrshannon.com> X-GPG-Key-Id: 0xB841F142 X-GPG-Fingerprint: C7C1 E1D1 EC06 7C86 AF7C 57E6 173D 9CF6 B841 F142 X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i X-Virus-Scanned: by Sentex Communications (avscan1/20021227) Subject: Re: Hyperthreading Kernel Configuration - 5.1 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: Thu, 02 Oct 2003 17:10:16 -0000 Thus spake John R. Shannon (john@johnrshannon.com) [02/10/03 13:05]: > On a new computer, dmesg shows: > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > acpi_cpu0: port 0x530-0x537 on acpi0 > acpi_cpu1: port 0x530-0x537 on acpi0 > > Should options SMP and APIC_IO be enabled in kernel? In short: yes. And then you need to look at the machdep.* sysctl nobs, there's one you need to enable in there (I've forgotten which one). But that leads me to a secondary question: is enabling HTT really worth the time? I know that people have said that using HTT can actually make your system slower -- is this an implementation issue, or did Intel really release something that degrades performance? From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 10:21:45 2003 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 4AEEA16A4B3 for ; Thu, 2 Oct 2003 10:21:45 -0700 (PDT) Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0468643FBF for ; Thu, 2 Oct 2003 10:21:41 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id B75163443F; Thu, 2 Oct 2003 14:20:48 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id B5A6E3442F; Thu, 2 Oct 2003 14:20:48 -0300 (ADT) Date: Thu, 2 Oct 2003 14:20:48 -0300 (ADT) From: "Marc G. Fournier" To: Damian Gerow In-Reply-To: <20031002170952.GF15256@sentex.net> Message-ID: <20031002141921.K25730@ganymede.hub.org> References: <200310021105.10872.john@johnrshannon.com> <20031002170952.GF15256@sentex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hardware@freebsd.org Subject: Re: Hyperthreading Kernel Configuration - 5.1 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: Thu, 02 Oct 2003 17:21:45 -0000 On Thu, 2 Oct 2003, Damian Gerow wrote: > Thus spake John R. Shannon (john@johnrshannon.com) [02/10/03 13:05]: > > On a new computer, dmesg shows: > > > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbff > > Hyperthreading: 2 logical CPUs > > acpi_cpu0: port 0x530-0x537 on acpi0 > > acpi_cpu1: port 0x530-0x537 on acpi0 > > > > Should options SMP and APIC_IO be enabled in kernel? > > In short: yes. And then you need to look at the machdep.* sysctl nobs, > there's one you need to enable in there (I've forgotten which one). > > But that leads me to a secondary question: is enabling HTT really worth the > time? I know that people have said that using HTT can actually make your > system slower -- is this an implementation issue, or did Intel really > release something that degrades performance? My understanding is that the speed improvements (or degradation) depend on the use of the machine ... for instance, I've heard that a high I/O server will be slower with HTT enabled, and, from my experience with one such, it is so ... I'm not sure what circumstances would show improvements though ... From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 11:15:06 2003 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 7CBE316A4B3 for ; Thu, 2 Oct 2003 11:15:06 -0700 (PDT) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DD4443FE3 for ; Thu, 2 Oct 2003 11:15:04 -0700 (PDT) (envelope-from simon@optinet.com) Received: (qmail 50727 invoked by uid 110); 2 Oct 2003 18:15:07 -0000 Received: from ool-18baaf5c.dyn.optonline.net (HELO win2kpc1) (24.186.175.92) by cobra.acceleratedweb.net with SMTP; 2 Oct 2003 18:15:07 -0000 From: "Simon" To: "Cassidy B. Larson" , "freebsd-hardware@freebsd.org" Date: Thu, 02 Oct 2003 14:14:49 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: MIME-Version: 1.0 Message-Id: <20031002181504.6DD4443FE3@mx1.FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: 3ware escalade 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: Thu, 02 Oct 2003 18:15:06 -0000 If I'm not mistaken and from what I recall, in theory, you should be able to reboot in the middle of a rebuild, however, once it comes back, you would have to start rebuilding it from scratch. It should not prevent your machine from booting, though, why? because the array is still functional as only 1 drive failed, maybe something else happened to your system. To see if if this is the case, I'm gonna try it right now with my 7500-8 controller. Perhaps someone on the list can confirm this. I believe I tried this once with Mylex Accelerated serries and it worked as I describe above. -Simon On Thu, 02 Oct 2003 09:28:50 -0600, Cassidy B. Larson wrote: >I would think for Redundancy in a RAID array a hardware controller should be >allowed to have the machine reboot during a rebuild process and not loose >track of where it is, and still run in degraded mode. > >Last test was a RAID10 rebuild, to see if a reboot would load the OS fine. >It appears it successfully reboots during a rebuild phase. Strange how a >RAID5 wouldn't boot and a RAID10 would. I'll try RAID5 once more to see if >I got something amiss. However, I do like the speed of a RAID10.. Maybe >I'll just keep it. > > >Cassidy > >On 10/1/03 3:22 PM, "Simon" wrote: > >> >> Why are you rebooting in a middle of a rebuild? I didn't know this is >> acceptable. >> I thought about it, but didn't actually try it. Rebuilds without interruption >> work fine >> with my 7500-8 controller with 8 IBM drives in RAID5 running 5.1-R >> >> -Simon > > From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 12:36:22 2003 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 4BF8316A4BF for ; Thu, 2 Oct 2003 12:36:22 -0700 (PDT) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id D811743FCB for ; Thu, 2 Oct 2003 12:36:18 -0700 (PDT) (envelope-from simon@optinet.com) Received: (qmail 66705 invoked by uid 110); 2 Oct 2003 19:36:23 -0000 Received: from ool-18baaf5c.dyn.optonline.net (HELO win2kpc1) (24.186.175.92) by cobra.acceleratedweb.net with SMTP; 2 Oct 2003 19:36:23 -0000 From: "Simon" To: "Cassidy B. Larson" , "freebsd-hardware@freebsd.org" Date: Thu, 02 Oct 2003 15:36:06 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: <20031002181504.6DD4443FE3@mx1.FreeBSD.org> MIME-Version: 1.0 Message-Id: <20031002193618.D811743FCB@mx1.FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: 3ware escalade 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: Thu, 02 Oct 2003 19:36:22 -0000 I just want to confirm that rebooting a server with 3ware 7500-8 while in rebuilding mode, reboots the machine just fine. The controller comes back in rebuilding mode and starts to rebuild in few minutes. However, I'm not sure if it starts from scratch or continues where it had left off. I guess I could verify this, but it doesn't really matter to me as I don't expect to reboot in the middle of a rebuild. Having said the above, there might be something wrong with your 8506 controller if it does not reboot after rebooting while in rebuilding mode. Maybe you need firmware upgrade, I would contact 3ware. -Simon On Thu, 02 Oct 2003 14:14:49 -0400, Simon wrote: > >If I'm not mistaken and from what I recall, in theory, you should be able to >reboot in the middle of a rebuild, however, once it comes back, you would >have to start rebuilding it from scratch. It should not prevent your machine >from booting, though, why? because the array is still functional as only 1 >drive failed, maybe something else happened to your system. To see if if >this is the case, I'm gonna try it right now with my 7500-8 controller. Perhaps >someone on the list can confirm this. I believe I tried this once with Mylex >Accelerated serries and it worked as I describe above. > >-Simon > > >On Thu, 02 Oct 2003 09:28:50 -0600, Cassidy B. Larson wrote: > >>I would think for Redundancy in a RAID array a hardware controller should be >>allowed to have the machine reboot during a rebuild process and not loose >>track of where it is, and still run in degraded mode. >> >>Last test was a RAID10 rebuild, to see if a reboot would load the OS fine. >>It appears it successfully reboots during a rebuild phase. Strange how a >>RAID5 wouldn't boot and a RAID10 would. I'll try RAID5 once more to see if >>I got something amiss. However, I do like the speed of a RAID10.. Maybe >>I'll just keep it. >> >> >>Cassidy >> >>On 10/1/03 3:22 PM, "Simon" wrote: >> >>> >>> Why are you rebooting in a middle of a rebuild? I didn't know this is >>> acceptable. >>> I thought about it, but didn't actually try it. Rebuilds without interruption >>> work fine >>> with my 7500-8 controller with 8 IBM drives in RAID5 running 5.1-R >>> >>> -Simon >> >> > > >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 13:28:21 2003 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 BBD6716A4BF for ; Thu, 2 Oct 2003 13:28:21 -0700 (PDT) Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2C2A43FD7 for ; Thu, 2 Oct 2003 13:28:20 -0700 (PDT) (envelope-from butch@infowest.com) Received: from [216.190.25.234] (unknown [216.190.25.234]) by delivery.infowest.com (Postfix) with ESMTP id 0E919EA9B8F; Thu, 2 Oct 2003 14:28:20 -0600 (MDT) User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 02 Oct 2003 14:28:04 -0600 From: "Cassidy B. Larson" To: Simon , "freebsd-hardware@freebsd.org" Message-ID: In-Reply-To: <20031002193618.E2A6CEA989F@mailbox.infowest.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Re: 3ware escalade 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: Thu, 02 Oct 2003 20:28:21 -0000 Very strange indeed. I don't think there is a problem with my 8506 card, as it is a different model than the 7500, it's SATA not parallel ATA. RAID10 works just like a charm, however, RAID5 does not. I'm running the latest firmware on the BIOS, card, etc. I've read in the past with those that contact 3ware, detailing that they use FreeBSD are given the shaft as FreeBSD isn't supported at all by 3ware (IIRC). Any other useful hints, suggestions, ideas would be appreciated from anyone. Thanks! Cassidy On 10/2/03 1:36 PM, "Simon" wrote: > > I just want to confirm that rebooting a server with 3ware 7500-8 while > in rebuilding mode, reboots the machine just fine. The controller comes > back in rebuilding mode and starts to rebuild in few minutes. However, I'm > not sure if it starts from scratch or continues where it had left off. I guess > I could verify this, but it doesn't really matter to me as I don't expect to > reboot in the middle of a rebuild. > > Having said the above, there might be something wrong with your 8506 > controller if it does not reboot after rebooting while in rebuilding mode. > Maybe you need firmware upgrade, I would contact 3ware. > > -Simon From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 15:36:33 2003 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 0D3BD16A4B3 for ; Thu, 2 Oct 2003 15:36:33 -0700 (PDT) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B27143FE0 for ; Thu, 2 Oct 2003 15:36:28 -0700 (PDT) (envelope-from simon@optinet.com) Received: (qmail 458 invoked by uid 110); 2 Oct 2003 22:36:34 -0000 Received: from ool-18baaf5c.dyn.optonline.net (HELO win2kpc1) (24.186.175.92) by cobra.acceleratedweb.net with SMTP; 2 Oct 2003 22:36:34 -0000 From: "Simon" To: "Cassidy B. Larson" , "freebsd-hardware@freebsd.org" Date: Thu, 02 Oct 2003 18:36:16 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: MIME-Version: 1.0 Message-Id: <20031002223628.2B27143FE0@mx1.FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: 3ware escalade 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: Thu, 02 Oct 2003 22:36:33 -0000 Indeed they are not the same controllers, however, I don't believe they are a complete redesign, so, yes they support serial over parallel drives, but the idea and the design should be the same, so they should function the same, maybe the firmware is broken on those controller, I'm not sure. -Simon On Thu, 02 Oct 2003 14:28:04 -0600, Cassidy B. Larson wrote: >Very strange indeed. I don't think there is a problem with my 8506 card, as >it is a different model than the 7500, it's SATA not parallel ATA. RAID10 >works just like a charm, however, RAID5 does not. > >I'm running the latest firmware on the BIOS, card, etc. > >I've read in the past with those that contact 3ware, detailing that they use >FreeBSD are given the shaft as FreeBSD isn't supported at all by 3ware >(IIRC). > >Any other useful hints, suggestions, ideas would be appreciated from anyone. > >Thanks! > >Cassidy > >On 10/2/03 1:36 PM, "Simon" wrote: > >> >> I just want to confirm that rebooting a server with 3ware 7500-8 while >> in rebuilding mode, reboots the machine just fine. The controller comes >> back in rebuilding mode and starts to rebuild in few minutes. However, I'm >> not sure if it starts from scratch or continues where it had left off. I guess >> I could verify this, but it doesn't really matter to me as I don't expect to >> reboot in the middle of a rebuild. >> >> Having said the above, there might be something wrong with your 8506 >> controller if it does not reboot after rebooting while in rebuilding mode. >> Maybe you need firmware upgrade, I would contact 3ware. >> >> -Simon > > > From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 17:00:35 2003 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 BAF8E16A4BF for ; Thu, 2 Oct 2003 17:00:35 -0700 (PDT) Received: from curee3.eerc.berkeley.edu (curee3.EERC.Berkeley.EDU [128.32.145.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B40143FE5 for ; Thu, 2 Oct 2003 17:00:35 -0700 (PDT) (envelope-from jmwong@curee.org) Received: from curee3.eerc.berkeley.edu (localhost [127.0.0.1]) h9300Ys7002244 for ; Thu, 2 Oct 2003 17:00:34 -0700 (PDT) (envelope-from jmwong@curee.org) Received: from localhost (jmwong@localhost)h9300Yl4002241 for ; Thu, 2 Oct 2003 17:00:34 -0700 (PDT) X-Authentication-Warning: curee3.eerc.berkeley.edu: jmwong owned process doing -bs Date: Thu, 2 Oct 2003 17:00:34 -0700 (PDT) From: John-Michael Wong X-X-Sender: jmwong@curee3.eerc.berkeley.edu To: freebsd-hardware@freebsd.org Message-ID: <20031002165005.U79192@curee3.eerc.berkeley.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: UltraTrak 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, 03 Oct 2003 00:00:35 -0000 Hi, I'm thinking of getting a Promise UltraTrak SX4000 and setting up a RAID-5 on it. Does anyone have experience with this product, or suggestions for something similar? The UltraTrak is an external enclosure with a built-in IDE RAID controller and it interfaces with the host computer using SCSI. I'm running a 4.8-REL system on an SMP Tyan S2510 motherboard using the on-board SCSI controller. Thanks for any suggestions. -- John-Michael Wong From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 2 17:16:32 2003 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 053FA16A4B3 for ; Thu, 2 Oct 2003 17:16:32 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 471DD43FE0 for ; Thu, 2 Oct 2003 17:16:27 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id h930EoDH025497; Thu, 2 Oct 2003 17:14:50 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h930EoU6025496; Thu, 2 Oct 2003 17:14:50 -0700 Date: Thu, 2 Oct 2003 17:14:50 -0700 From: Brooks Davis To: John-Michael Wong Message-ID: <20031003001444.GB20964@Odin.AC.HMC.Edu> References: <20031002165005.U79192@curee3.eerc.berkeley.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline In-Reply-To: <20031002165005.U79192@curee3.eerc.berkeley.edu> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-hardware@freebsd.org Subject: Re: UltraTrak 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, 03 Oct 2003 00:16:32 -0000 --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 02, 2003 at 05:00:34PM -0700, John-Michael Wong wrote: >=20 > I'm thinking of getting a Promise UltraTrak SX4000 and setting up a RAID-5 > on it. Does anyone have experience with this product, or suggestions for > something similar? The UltraTrak is an external enclosure with a built-in > IDE RAID controller and it interfaces with the host computer using SCSI. > I'm running a 4.8-REL system on an SMP Tyan S2510 motherboard using the > on-board SCSI controller. We've got an RM8000. Performance is unremarkable at around 25MBps. At some point our system developed a problem where the box panics at boot if the array is attached. Shutting of the array during boot is a workaround and we're about out of space on it so I'm not wasting much time trying to find the problem. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --hHWLQfXTYDoKhP50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/fL90XY6L6fI4GtQRApheAJ9/W2u2NZCG3voWcZtZj+WBb5ZG4wCfYZmV V3eeK7sJOR2LWSu2IUcwdXg= =W+GW -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50-- From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 4 17:05:44 2003 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 D119216A4B3 for ; Sat, 4 Oct 2003 17:05:44 -0700 (PDT) Received: from maelstrom.waterspout.com (rrcs-ma-24-56-74-54.biz.rr.com [24.56.74.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC0244003 for ; Sat, 4 Oct 2003 17:05:43 -0700 (PDT) (envelope-from csg@waterspout.com) Received: from maelstrom.waterspout.com (localhost [127.0.0.1]) h9505aPH043687; Sat, 4 Oct 2003 19:05:36 -0500 (CDT) (envelope-from csg@waterspout.com) Received: (from csg@localhost)h9505ZNI043686; Sat, 4 Oct 2003 19:05:35 -0500 (CDT) X-Authentication-Warning: maelstrom.waterspout.com: csg set sender to csg@waterspout.com using -f Date: Sat, 4 Oct 2003 19:05:35 -0500 From: "C. Stephen Gunn" To: "Marc G. Fournier" Message-ID: <20031005000535.GA40750@waterspout.com> References: <200310021105.10872.john@johnrshannon.com> <20031002170952.GF15256@sentex.net> <20031002141921.K25730@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031002141921.K25730@ganymede.hub.org> User-Agent: Mutt/1.4.1i cc: Damian Gerow cc: hardware@freebsd.org Subject: Re: Hyperthreading Kernel Configuration - 5.1 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: Sun, 05 Oct 2003 00:05:44 -0000 Marc G. Fournier (scrappy@hub.org) likely uttered: > My understanding is that the speed improvements (or degradation) depend on > the use of the machine ... for instance, I've heard that a high I/O server > will be slower with HTT enabled, and, from my experience with one such, it > is so ... I'm not sure what circumstances would show improvements though Most likly the other end of the spectrum. I've seem some transactional loads that require modest compute (say .2 seconds) that seem to do quite well on a Hyperthread box. - Steve