From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 21 04:58:14 2004 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 BC1E716A4CE; Mon, 21 Jun 2004 04:58:14 +0000 (GMT) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 780AC43D5D; Mon, 21 Jun 2004 04:58:14 +0000 (GMT) (envelope-from pepper@reppep.com) Received: from [10.0.1.102] (airport.reppep.com [66.92.104.202]) by www.reppep.com (Postfix) with ESMTP id A84A6FDAF; Mon, 21 Jun 2004 00:58:12 -0400 (EDT) Mime-Version: 1.0 X-Sender: pepper@mail.reppep.com Message-Id: Date: Mon, 21 Jun 2004 00:57:56 -0400 To: freebsd-hardware@freebsd.org From: Chris Pepper Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Bill Paul Subject: re(4) hang at bootup under CURRENT 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, 21 Jun 2004 04:58:14 -0000 I've had a couple hangs bringing up re(4) at boot time. A reboot cleared both, but since it's happened twice in a couple weeks, here's a report. I'm not sure if this merits a PR. This all applies to an HP Pavilion 7915 w/ 3.04 BIOS and FreeBSD 5.2.1 (now running -CURRENT from a few days ago). I'm working on upgrading it to 3.07 BIOS to see if this lets me run with ACPI, but haven't gotten there yet. "pciconf -lv", dmesg, and my REPPEP5 kernel configuration are all at . The card itself is an 8169, sold by Asante as a FriendlyNet GigaNIX : >re0@pci1:10:0: class=0x020000 card=0x816910ec chip=0x816910ec >rev=0x10 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8169 Gigabit Ethernet Adapter' > class = network > subclass = ethernet After installing 5.2.1 from CD, the system hung during its first boot -- apparently while configuring the re driver. Since an immediate reboot cleared the problem, and it didn't recur within a week, I no longer have notes on that hang. I have a 6gb partition with Windows XP Pro SP1 on the disk. SP1 (which I installed after 5.2.1), does not come with a driver for the RealTek card; it does detect the 3Com 10/100 card, but I only got the RealTek driver from Windows Update a day or two ago, and Windows hadn't recognized for the 8169 before this evening. When I finished futzing with the (failed) HP UIUD BIOS update and booted back into FreeBSD, I got the second hang. I don't know if Windows configured the card problematically for FreeBSD, but mention it for completeness. If I have any further hangs, I'll report them here, and/or file a PR. For convenience, here's tonight's hang from : >xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x2080-0x20ff mem >0xf4104000-0xf410407f irq 9 at device 9.0 on pci1 >xl0: Ethernet address: 00:04:76:df:f2:82 >miibus0: on xl0 >xlphy0: <3c905C 10/100 internal PHY> on miibus0 >xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >re0: port 0x2400-0x24ff >mem 0xf4104400-0xf41044ff irq 10 at device 10.0 on pci1 >re0: Ethernet address: 00:0e:2e:06:ea:82 >miibus1: on re0 >rgephy0: on miibus1 >rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >1000baseTX, 1000baseTX-FDX, auto >re0: diagnostic failed, failed to receive packet in loopback mode >re0: attach aborted due to hardware diag failure > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x98 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xc05914c5 >stack pointer = 0x10:0xc0c21998 >frame pointer = 0x10:0xc0c219a8 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 0 (swapper) >trap number = 12 >panic: page fault >Uptime: 1s >Automatic reboot in 15 seconds - press a key on the console to abort >Rebooting... Regards, Chris Pepper -- Chris Pepper: Rockefeller University: From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 01:48:10 2004 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 3BCFB16A4D0 for ; Tue, 22 Jun 2004 01:48:10 +0000 (GMT) Received: from mail.corp.anonymizer.com (smtp.infonex.com [168.143.114.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05DA743D58 for ; Tue, 22 Jun 2004 01:48:10 +0000 (GMT) (envelope-from craig@anonymizer.com) Received: from [10.10.10.122] (enif.anonymizer.com [168.143.114.60]) by mail.corp.anonymizer.com (Postfix) with ESMTP id 18E8734801C for ; Mon, 21 Jun 2004 19:12:42 -0700 (PDT) From: Craig Calef To: freebsd-hardware@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4IJKhl4HxIG2p+KD+KXG" Message-Id: <1087868861.16099.112.camel@(null)> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 21 Jun 2004 18:47:41 -0700 Subject: Dell PowerEdge with Redundant Power Supplies 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, 22 Jun 2004 01:48:10 -0000 --=-4IJKhl4HxIG2p+KD+KXG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Everybody, I've recently bought a Dell PowerEdge 1750 server with redundant power supplies. This raises the question.. How do I detect when one of these power supplies fails? I've tried loading APM drivers, getting an SMBus driver to load, and played around with the old IPMI stuff to no avail.=20 Has anybody ever gotten this working or could atleast find a direction to point me in? If I can just get the status from some program I can take care of the rest of the "let me know about it" things myself. I am running FreeBSD 5.2-CURRENT on this machine and just CVSup'd yesterday. Thanks everybody, Craig Calef. --=-4IJKhl4HxIG2p+KD+KXG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA14+9S0rB05KjFuERAtG3AKCMjkNNHO0RTlB6hbm7DkimCYMWrgCeLEam t8bCTvxj8h7EfI9Hcp/rgOU= =lcUn -----END PGP SIGNATURE----- --=-4IJKhl4HxIG2p+KD+KXG-- From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 06:21:39 2004 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 5175616A4CE for ; Tue, 22 Jun 2004 06:21:39 +0000 (GMT) Received: from tom.chem.tue.nl (tom.chem.tue.nl [131.155.80.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF9B643D53 for ; Tue, 22 Jun 2004 06:21:38 +0000 (GMT) (envelope-from willy@tom.chem.tue.nl) Received: from tom.chem.tue.nl (localhost [127.0.0.1]) by tom.chem.tue.nl (8.12.10/8.12.10) with ESMTP id i5M6LbE3020727 for ; Tue, 22 Jun 2004 08:21:37 +0200 (CEST) (envelope-from willy@tom.chem.tue.nl) Received: (from willy@localhost) by tom.chem.tue.nl (8.12.10/8.12.10/Submit) id i5M6LahQ020726 for freebsd-hardware@freebsd.org; Tue, 22 Jun 2004 08:21:37 +0200 (CEST) (envelope-from willy) Date: Tue, 22 Jun 2004 08:21:36 +0200 From: Willy Offermans To: freebsd-hardware@freebsd.org Message-ID: <20040622062136.GA20700@tom.chem.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: NM9805 1284 Printer port Support in FreeBSD 5.2.1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: W.K.Offermans@TUe.nl List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 06:21:39 -0000 Dear FreeBSD friends, I have a new computer with an additional LPT port: puc0@pci3:13:0: class=0x078000 card=0x00101000 chip=0x98059710 rev=0x01 hdr=0x00 vendor = 'MosChip Semiconductors (Was: Netmos Technology)' device = 'Nm9805 PCI + 1284 Printer Port' class = simple comms I was able to get it work by adding the following to /usr/src/sys/dev/puc/pucdata.c /* Added by Willy@Rompen.nl 06/05/2004 */ /* recommended by john@feith.com */ /* NetMos 0S1P PCI : 0S, 1P */ { "NetMos NM9805 1284 Printer port", NULL, { 0x9710, 0x9805, 0, 0 }, { 0xffff, 0xffff, 0, 0 }, { { PUC_PORT_TYPE_LPT, 0x10, 0x00, 0x00 }, }, }, and to enable the puc driver in the kernel of course. Is it possible to add the data to /usr/src/sys/dev/puc/pucdata.c permanently? Thnx a lot, -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Eindhoven University of Technology Department of Chemical Engineering Laboratory of Catalysis (SKA) building ST-W 4.27, PO Box 513 5600 MB Eindhoven, Netherlands Tel: 0(031) 40 247 37 81 Fax: 0(031) 40 247 50 32 Home: 0(031) 45 544 49 44 Mobile: 0(031) 653 119 666 e-mail: w.k.offermans@tue.nl http://www.catalysis.nl The new slogan for windows 2003: Do more with less! The slogan for FreeBSD has always been: Do all for Free Have a look for free: www.FreeBSD.org (__) \\\'',) \/ \ ^ .\._/_) From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 07:57:56 2004 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 1BE7216A4CE; Tue, 22 Jun 2004 07:57:56 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0715843D54; Tue, 22 Jun 2004 07:57:56 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from dhcp-8.sql1.plosh.net (c-24-4-233-31.client.comcast.net [24.4.233.31]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id C7BEEA95B; Tue, 22 Jun 2004 07:57:30 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Date: Tue, 22 Jun 2004 00:57:23 -0700 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_pZ+1Atmdk51siaW"; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200406220057.29846.Peter_Losher@isc.org> Subject: Possible 3ware 8506-12 SATA Controller issues... 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, 22 Jun 2004 07:57:56 -0000 --Boundary-02=_pZ+1Atmdk51siaW Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline So I am tracking down a possible controller issue with a dual-Opteron=20 system (running the amd64 port - 5.2.1-REL branch) which has a 3ware=20 8506-12 SATA controller controlling 1.2TB of disk space.=20 While the system iself is nice, under sustained high disk I/O, the system=20 randomly locks up hard. (requires a hard reset) In trying to diagnose the problem I noticed the kernel recognises it as a=20 12 channel controller (albiet from the 7000 series): =2D=3D- % grep twe /var/run/dmesg.boot twe0: <3ware 7000 series Storage Controller. Driver version 1.50.00.000>=20 port 0x8c00-0x8c0f mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq=20 29 at device 1.0 on pci1 twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 =2D=3D- When we took delivery of the system late last year, the 12 channel=20 version of the 8506 card was so new you had to run 5.2-RC2 to get a=20 version of the twe driver to support it. Have there been changes to the=20 driver since then to better support this card? (Of course the problem may be elsewhere, the MB, CPU(s), memory... The=20 joys of HW debugging) Side note I have noticed that I can install 5.2.1=20 on the box and update to the latest patch level, but subequent 'make=20 buildworld's usually dies randomly on a signal 4 error. Best Wishes - Peter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow --Boundary-02=_pZ+1Atmdk51siaW Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA1+ZpPtVx9OgEjQgRAhLPAJ9s4dkgxdWBnG61q59ycetnrGnTVACgrw3a W3A/VtuhzrHrevm9bQDjKdQ= =F1Mp -----END PGP SIGNATURE----- --Boundary-02=_pZ+1Atmdk51siaW-- From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 08:39:25 2004 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 F0B1F16A4CE; Tue, 22 Jun 2004 08:39:25 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id E729B43D5D; Tue, 22 Jun 2004 08:39:23 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.12.10/8.12.10) with ESMTP id i5M8dHNf037320; Tue, 22 Jun 2004 10:39:17 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.12.10/8.12.10) with ESMTP id i5M8dOv9064518; Tue, 22 Jun 2004 10:39:24 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.12.10/8.12.10/Submit) id i5M8dOU0064517; Tue, 22 Jun 2004 10:39:24 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 22 Jun 2004 10:39:24 +0200 From: Francois Tigeot To: Peter Losher Message-ID: <20040622083924.GA60244@aoi.wolfpond.org> References: <200406220057.29846.Peter_Losher@isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406220057.29846.Peter_Losher@isc.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Possible 3ware 8506-12 SATA Controller issues... 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, 22 Jun 2004 08:39:26 -0000 On Tue, Jun 22, 2004 at 12:57:23AM -0700, Peter Losher wrote: > So I am tracking down a possible controller issue with a dual-Opteron > system (running the amd64 port - 5.2.1-REL branch) which has a 3ware > 8506-12 SATA controller controlling 1.2TB of disk space. > > While the system iself is nice, under sustained high disk I/O, the system > randomly locks up hard. (requires a hard reset) > > In trying to diagnose the problem I noticed the kernel recognises it as a > 12 channel controller (albiet from the 7000 series): > > -=- > % grep twe /var/run/dmesg.boot > twe0: <3ware 7000 series Storage Controller. Driver version 1.50.00.000> > port 0x8c00-0x8c0f mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq > 29 at device 1.0 on pci1 > twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > -=- > > (Of course the problem may be elsewhere, the MB, CPU(s), memory... The > joys of HW debugging) Side note I have noticed that I can install 5.2.1 > on the box and update to the latest patch level, but subequent 'make > buildworld's usually dies randomly on a signal 4 error. 3Ware 850x cards have PCI interaction issues with some Opteron mainboard Check if your mainboard is not in this list: https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf Alternatively you may try to plug the controller in a 32bit PCI slot. -- Francois Tigeot From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 09:03:30 2004 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 91FD416A4CE; Tue, 22 Jun 2004 09:03:30 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82F8043D1D; Tue, 22 Jun 2004 09:03:30 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from dhcp-8.sql1.plosh.net (c-24-4-233-31.client.comcast.net [24.4.233.31]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 9D06AA95B; Tue, 22 Jun 2004 09:03:12 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: Francois Tigeot Date: Tue, 22 Jun 2004 02:03:01 -0700 User-Agent: KMail/1.6.2 References: <200406220057.29846.Peter_Losher@isc.org> <20040622083924.GA60244@aoi.wolfpond.org> In-Reply-To: <20040622083924.GA60244@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_PX/1Arj41YeniXu"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406220203.11230.Peter_Losher@isc.org> cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Possible 3ware 8506-12 SATA Controller issues... 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, 22 Jun 2004 09:03:30 -0000 --Boundary-02=_PX/1Arj41YeniXu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 22 June 2004 01:39 am, Francois Tigeot wrote: > 3Ware 850x cards have PCI interaction issues with some Opteron > mainboard > > Check if your mainboard is not in this list: > > https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf Thanks, the system in question is using a Tyan Thunder S2882 MB (which=20 isn't on the list) However, the card was one of the first batch out, so=20 I can see about getting one of the "fixed" cards... > Alternatively you may try to plug the controller in a 32bit PCI slot. Yeah, that may be another option. Thanks for the pointer! - Peter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" --Boundary-02=_PX/1Arj41YeniXu Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA1/XPPtVx9OgEjQgRAkH3AKCCR+thajSlh9QnLM9FcsKlm9XVAgCgva25 FtKkC2lIkCjMeAnH0q6iggY= =RIla -----END PGP SIGNATURE----- --Boundary-02=_PX/1Arj41YeniXu-- From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 21 14:03:26 2004 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 6B13916A4CE for ; Mon, 21 Jun 2004 14:03:26 +0000 (GMT) Received: from marcie.netcarrier.net (marcie.netcarrier.net [216.178.72.21]) by mx1.FreeBSD.org (Postfix) with SMTP id ED5F943D2F for ; Mon, 21 Jun 2004 14:03:25 +0000 (GMT) (envelope-from nielm@edaonline.com) Received: (qmail 20788 invoked from network); 21 Jun 2004 14:03:24 -0000 Received: from user216-178-81-18.netcarrier.net (HELO edaonline.com) (216.178.81.18) by marcie.netcarrier.net with SMTP; 21 Jun 2004 14:03:24 -0000 Received: from niel2000 [216.178.81.20] by edaonline.com (FTGate 2, 2, 2, 1); Mon, 21 Jun 2004 09:53:51 -0400 From: "Niel Mazurek" To: Date: Mon, 21 Jun 2004 10:00:45 -0400 Message-ID: <000601c45798$25cffe10$1451b2d8@niel2000> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailman-Approved-At: Tue, 22 Jun 2004 12:16:20 +0000 Subject: RE: DTMF APPLICATION 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, 21 Jun 2004 14:03:26 -0000 I have an application that requires sending and receiving a large amount of DTMF characters via the HCF modem in my PC to a non modem device connected to a telephone line. I am looking for information on how to configure the modem for this type of application. From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 14:37:31 2004 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 5B6EC16A4CE; Tue, 22 Jun 2004 14:37:31 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id D495A43D2F; Tue, 22 Jun 2004 14:37:28 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id C8FDD1C186; Tue, 22 Jun 2004 07:36:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id C1D2F1C181; Tue, 22 Jun 2004 07:36:56 -0700 (PDT) Date: Tue, 22 Jun 2004 07:36:56 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Peter Losher In-Reply-To: <200406220057.29846.Peter_Losher@isc.org> Message-ID: References: <200406220057.29846.Peter_Losher@isc.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 22 Jun 2004 14:37:31 -0000 I had nearly the exact same card and setup - dual opteron, freebsd-amd64, 5.2.1-REL, 8506-8 card. When I called 3ware the guy told me AMD64 support for FreeBSD would be in their 9000 series of cards - so I sent back my 8506-8 and got a 9500S-8. BNesides for the hardware and BIOS improvements, they also did come out with a driver as well. I could not get it to work loaded in the kernel and kernel modules do not work for AMD64 yet. SO right now I have an email out to the guys there asking if they can help me out. Apparently they only tested it for FreeBSD 4.9 and 5.1. However, they did mention that support for the 8500 series and FreeBSD 5/amd64 would be much later in the summer or year. Further reason why I took the hassle to RMA the 8500 card and get the 9500S. My kernel also recognized the old card, even though the 3ware tech guy said "that is not supported properly, it might see it, but it won't work good" - the driver might work halfway, but you're also missing out on all the 3dm utils and whatnot, which are important to the maintenance of your array. The newest drivers for the 9500 series include all that - so they are providing properly supported stuff for our platform now, if only I can get it to work with a 5.2.x series kernel. I'd like to try it out as a kernel module, but kernel modules don't work yet in 5.2.x/AMD64. 3ware told me they need to get someone else involved to work on the kernel driver issue too... So I've been patient waiting for them to help. Email me back with any questions. I can give you my contact there so there can be an additional person bugging him for status on this. =) Hope this helps! - mike On Tue, 22 Jun 2004, Peter Losher wrote: > So I am tracking down a possible controller issue with a dual-Opteron > system (running the amd64 port - 5.2.1-REL branch) which has a 3ware > 8506-12 SATA controller controlling 1.2TB of disk space. > > While the system iself is nice, under sustained high disk I/O, the system > randomly locks up hard. (requires a hard reset) > > In trying to diagnose the problem I noticed the kernel recognises it as a > 12 channel controller (albiet from the 7000 series): > > -=- > % grep twe /var/run/dmesg.boot > twe0: <3ware 7000 series Storage Controller. Driver version 1.50.00.000> > port 0x8c00-0x8c0f mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq > 29 at device 1.0 on pci1 > twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > -=- > > When we took delivery of the system late last year, the 12 channel > version of the 8506 card was so new you had to run 5.2-RC2 to get a > version of the twe driver to support it. Have there been changes to the > driver since then to better support this card? > > (Of course the problem may be elsewhere, the MB, CPU(s), memory... The > joys of HW debugging) Side note I have noticed that I can install 5.2.1 > on the box and update to the latest patch level, but subequent 'make > buildworld's usually dies randomly on a signal 4 error. > > Best Wishes - Peter > -- > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow > From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 14:39:44 2004 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 9091C16A4CE; Tue, 22 Jun 2004 14:39:44 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FDC143D1F; Tue, 22 Jun 2004 14:39:44 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 8821F1C186; Tue, 22 Jun 2004 07:39:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 84B0E1C0E0; Tue, 22 Jun 2004 07:39:19 -0700 (PDT) Date: Tue, 22 Jun 2004 07:39:19 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Peter Losher In-Reply-To: <200406220203.11230.Peter_Losher@isc.org> Message-ID: References: <200406220057.29846.Peter_Losher@isc.org> <20040622083924.GA60244@aoi.wolfpond.org> <200406220203.11230.Peter_Losher@isc.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Francois Tigeot cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: Possible 3ware 8506-12 SATA Controller issues... 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, 22 Jun 2004 14:39:44 -0000 Just FYI - the 9500 series cards do not suffer from this problem. That was another thing they tried to mention. However, upgrading to the 9500S series they say has no flaky riser card issues anymore. My mainboard is the S2882 as well. I'd suggest swapping out with the 9500S. The price of it isn't much more than the 8506 series, surprisingly... On Tue, 22 Jun 2004, Peter Losher wrote: > On Tuesday 22 June 2004 01:39 am, Francois Tigeot wrote: > > > 3Ware 850x cards have PCI interaction issues with some Opteron > > mainboard > > > > Check if your mainboard is not in this list: > > > > https://www.3ware.com/kbadmin/attachments/TM900-0045-00%20Rev%20A_P.pdf > > Thanks, the system in question is using a Tyan Thunder S2882 MB (which > isn't on the list) However, the card was one of the first batch out, so > I can see about getting one of the "fixed" cards... > > > Alternatively you may try to plug the controller in a 32bit PCI slot. > > Yeah, that may be another option. > > Thanks for the pointer! - Peter > -- > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" > From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 15:13:40 2004 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 5F36F16A4CE for ; Tue, 22 Jun 2004 15:13:40 +0000 (GMT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0578243D1D for ; Tue, 22 Jun 2004 15:13:40 +0000 (GMT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 27407E86E0; Tue, 22 Jun 2004 12:13:08 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 23CD3E86DE for ; Tue, 22 Jun 2004 12:13:08 -0300 (ADT) Date: Tue, 22 Jun 2004 12:13:08 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-hardware@freebsd.org Message-ID: <20040622121156.O845@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: RFC: Chenbro Chassis (RM214) 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, 22 Jun 2004 15:13:40 -0000 Looking for thoughts/comments on the above rackchassis ... going to be putting a Tyan Thunder K7x into her, with 6xSeagate drives ... looking at the 460W PSU option, which seems to be the largest they have ... Stupid question ... they have a 460W+460W redundant option ... its still *max* 460W, right? If it needs a bit more, it won't pull from the second one at all, right? Anyone with good (or bad) experiences? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 21:29:43 2004 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 2CE2F16A4CE for ; Tue, 22 Jun 2004 21:29:43 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id A562443D46 for ; Tue, 22 Jun 2004 21:29:42 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from eiterra.error404.nls.net (eiterra.achedra.org [192.168.0.100]) by error404.nls.net (8.12.10/8.12.10) with ESMTP id i5MLTekp046720; Tue, 22 Jun 2004 17:29:41 -0400 (EDT) (envelope-from ketrien@error404.nls.net) Message-Id: <6.1.1.1.2.20040622171913.02b0b160@error404.nls.net> X-Sender: ketrien@error404.nls.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Tue, 22 Jun 2004 17:29:38 -0400 To: "Marc G. Fournier" From: "Ketrien I. Saihr-Kesenchedra" In-Reply-To: <20040622121156.O845@ganymede.hub.org> References: <20040622121156.O845@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: hardware@freebsd.org Subject: Re: RFC: Chenbro Chassis (RM214) 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, 22 Jun 2004 21:29:43 -0000 At 11:13 AM 6/22/2004, you wrote: >Looking for thoughts/comments on the above rackchassis ... going to be >putting a Tyan Thunder K7x into her, with 6xSeagate drives ... looking at >the 460W PSU option, which seems to be the largest they have ... >Stupid question ... they have a 460W+460W redundant option ... its still >*max* 460W, right? If it needs a bit more, it won't pull from the second >one at all, right? >Anyone with good (or bad) experiences? http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_869_965%5E3238,00.html Dual Athlon MP specifications require a typical minimum 460W PSU per the AMD SBG. Publication 25823, page 3. Amperage on the 12V must meet or exceed 16.5A + 13A combined CPU and I/O, +3.3V must have a minimum 27A, +5V must have a minimum 29A. http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25823.pdf Our old dual MP2000 was powered by a PC Power & Cooling 510XE. Rated for 640W peak, 510W at 50C. +5V 40A, +3.3V 30A, +12V 34A/38A Peak. Standard ATX layout. http://www.pcpowerandcooling.com/products/power_supplies/maxperformance/turbocools/index_hp_atx.htm As far as Chenbro, avoid at all costs. We had nothing but trouble with them. The backplane connections are non-standard (male to female,) and the backplanes frequently lost entire channels due to shoddy quality and failing to follow SCSI specifications. Heat was a constant problem due to a flawed layout, and the fans were pretty much worthless. I wouldn't take another one if someone paid me. -Ketrien I. Saihr-Kesenchedra # Maybe this world is another planet's hell. --Aldous Huxley Feanor smiles, "We, of course, are enlightened and s/Maybe t/T" From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 22:52:02 2004 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 3921816A4CE for ; Tue, 22 Jun 2004 22:52:02 +0000 (GMT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08F8943D68 for ; Tue, 22 Jun 2004 22:52:02 +0000 (GMT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id AB320EA4C4; Tue, 22 Jun 2004 19:51:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id AA1CAEA22B; Tue, 22 Jun 2004 19:51:40 -0300 (ADT) Date: Tue, 22 Jun 2004 19:51:40 -0300 (ADT) From: "Marc G. Fournier" To: "Ketrien I. Saihr-Kesenchedra" In-Reply-To: <6.1.1.1.2.20040622171913.02b0b160@error404.nls.net> Message-ID: <20040622194858.F845@ganymede.hub.org> References: <20040622121156.O845@ganymede.hub.org> <6.1.1.1.2.20040622171913.02b0b160@error404.nls.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: hardware@freebsd.org Subject: Re: RFC: Chenbro Chassis (RM214) 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, 22 Jun 2004 22:52:02 -0000 k, without breaking my bank, since I don't own one ... can you (or anyone else) recommend a suitable rack chassis? The one I liked was the RC0222 from CISS, but I can't find any prices on the web ... I'm not necessarily looking for the cheapest, don't get me wrong ... but its the only component that I just can't seem to find one I like ... note that I am restricted to a 2U space, so recommending me a 4U or 3U solution doesn't cut it ... On Tue, 22 Jun 2004, Ketrien I. Saihr-Kesenchedra wrote: > At 11:13 AM 6/22/2004, you wrote: >> Looking for thoughts/comments on the above rackchassis ... going to be >> putting a Tyan Thunder K7x into her, with 6xSeagate drives ... looking at >> the 460W PSU option, which seems to be the largest they have ... >> Stupid question ... they have a 460W+460W redundant option ... its still >> *max* 460W, right? If it needs a bit more, it won't pull from the second >> one at all, right? >> Anyone with good (or bad) experiences? > > http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_869_965%5E3238,00.html > > Dual Athlon MP specifications require a typical minimum 460W PSU per the AMD > SBG. Publication 25823, page 3. Amperage on the 12V must meet or exceed 16.5A > + 13A combined CPU and I/O, +3.3V must have a minimum 27A, +5V must have a > minimum 29A. > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25823.pdf > > Our old dual MP2000 was powered by a PC Power & Cooling 510XE. Rated for 640W > peak, 510W at 50C. +5V 40A, +3.3V 30A, +12V 34A/38A Peak. Standard ATX > layout. > http://www.pcpowerandcooling.com/products/power_supplies/maxperformance/turbocools/index_hp_atx.htm > > As far as Chenbro, avoid at all costs. We had nothing but trouble with them. > The backplane connections are non-standard (male to female,) and the > backplanes frequently lost entire channels due to shoddy quality and failing > to follow SCSI specifications. Heat was a constant problem due to a flawed > layout, and the fans were pretty much worthless. I wouldn't take another one > if someone paid me. > > > -Ketrien I. Saihr-Kesenchedra > # Maybe this world is another planet's hell. --Aldous Huxley > Feanor smiles, "We, of course, are enlightened and s/Maybe t/T" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 22 23:21:20 2004 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 9B55916A4CE; Tue, 22 Jun 2004 23:21:20 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70CB343D45; Tue, 22 Jun 2004 23:21:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i5MNKifN052463; Tue, 22 Jun 2004 16:20:44 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5MNKfM6052458; Tue, 22 Jun 2004 16:20:41 -0700 (PDT) (envelope-from obrien) Date: Tue, 22 Jun 2004 16:20:41 -0700 From: "David O'Brien" To: Vinod Kashyap Message-ID: <20040622232041.GC51951@dragon.nuxi.com> References: <200406220057.29846.Peter_Losher@isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: mike cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 23:21:20 -0000 Vinod, As the FreeBSD 3Ware driver maintainer can you address these driver concerns on AMD64 hardware [in 64-bit mode]? thanks, -- David On Tue, Jun 22, 2004 at 07:36:56AM -0700, mike wrote: > I had nearly the exact same card and setup - dual opteron, freebsd-amd64, > 5.2.1-REL, 8506-8 card. > > When I called 3ware the guy told me AMD64 support for FreeBSD would be in > their 9000 series of cards - so I sent back my 8506-8 and got a 9500S-8. > BNesides for the hardware and BIOS improvements, they also did come out > with a driver as well. I could not get it to work loaded in the kernel and > kernel modules do not work for AMD64 yet. SO right now I have an email out > to the guys there asking if they can help me out. > > Apparently they only tested it for FreeBSD 4.9 and 5.1. However, they did > mention that support for the 8500 series and FreeBSD 5/amd64 would be much > later in the summer or year. Further reason why I took the hassle to RMA > the 8500 card and get the 9500S. > > My kernel also recognized the old card, even though the 3ware tech guy > said "that is not supported properly, it might see it, but it won't work > good" - the driver might work halfway, but you're also missing out on all > the 3dm utils and whatnot, which are important to the maintenance of your > array. The newest drivers for the 9500 series include all that - so they > are providing properly supported stuff for our platform now, if only I can > get it to work with a 5.2.x series kernel. > > I'd like to try it out as a kernel module, but kernel modules don't > work yet in 5.2.x/AMD64. 3ware told me they need to get someone else > involved to work on the kernel driver issue too... > > So I've been patient waiting for them to help. > > Email me back with any questions. I can give you my contact there so there > can be an additional person bugging him for status on this. =) > > Hope this helps! > - mike > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > So I am tracking down a possible controller issue with a dual-Opteron > > system (running the amd64 port - 5.2.1-REL branch) which has a 3ware > > 8506-12 SATA controller controlling 1.2TB of disk space. > > > > While the system iself is nice, under sustained high disk I/O, the system > > randomly locks up hard. (requires a hard reset) > > > > In trying to diagnose the problem I noticed the kernel recognises it as a > > 12 channel controller (albiet from the 7000 series): > > > > -=- > > % grep twe /var/run/dmesg.boot > > twe0: <3ware 7000 series Storage Controller. Driver version 1.50.00.000> > > port 0x8c00-0x8c0f mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq > > 29 at device 1.0 on pci1 > > twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > > -=- > > > > When we took delivery of the system late last year, the 12 channel > > version of the 8506 card was so new you had to run 5.2-RC2 to get a > > version of the twe driver to support it. Have there been changes to the > > driver since then to better support this card? > > > > (Of course the problem may be elsewhere, the MB, CPU(s), memory... The > > joys of HW debugging) Side note I have noticed that I can install 5.2.1 > > on the box and update to the latest patch level, but subequent 'make > > buildworld's usually dies randomly on a signal 4 error. > > > > Best Wishes - Peter > > -- > > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" -- -- David (obrien@FreeBSD.org) From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 00:16:34 2004 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 EF5FE16A4CE; Wed, 23 Jun 2004 00:16:34 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA4F43D5F; Wed, 23 Jun 2004 00:16:34 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZQJFJ01.524; Tue, 22 Jun 2004 17:16:31 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062217163506647 ; Tue, 22 Jun 2004 17:16:35 -0700 From: "Vinod Kashyap" To: obrien@freebsd.org Date: Tue, 22 Jun 2004 17:16:30 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: mike cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 00:16:35 -0000 > -----Original Message----- > From: David O'Brien [mailto:obrien@freebsd.org] > Sent: Tuesday, June 22, 2004 4:21 PM > To: Vinod Kashyap > Cc: mike; Peter Losher; freebsd-amd64@freebsd.org; > freebsd-hardware@freebsd.org > Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller > issues... > = > = > Vinod, > = > As the FreeBSD 3Ware driver maintainer can you address these driver > concerns on AMD64 hardware [in 64-bit mode]? > = > thanks, > -- David > = > = > On Tue, Jun 22, 2004 at 07:36:56AM -0700, mike wrote: > > I had nearly the exact same card and setup - dual opteron, = > freebsd-amd64, > > 5.2.1-REL, 8506-8 card. > > = > > When I called 3ware the guy told me AMD64 support for = > FreeBSD would be in > > their 9000 series of cards - so I sent back my 8506-8 and = > got a 9500S-8. > > BNesides for the hardware and BIOS improvements, they also = > did come out > > with a driver as well. I could not get it to work loaded in = > the kernel and > > kernel modules do not work for AMD64 yet. SO right now I = > have an email out > > to the guys there asking if they can help me out. > > = > > Apparently they only tested it for FreeBSD 4.9 and 5.1. = > However, they did > > mention that support for the 8500 series and FreeBSD = > 5/amd64 would be much > > later in the summer or year. Further reason why I took the = > hassle to RMA > > the 8500 card and get the 9500S. > > = The official support on FreeBSD for 7xxx, 8xxx and 9xxx series controllers is only for i386. Although the driver might work on other platforms, it's never been tested. The FreeBSD management tools provided by 3ware are only for i386. > > My kernel also recognized the old card, even though the = > 3ware tech guy > > said "that is not supported properly, it might see it, but = > it won't work > > good" - the driver might work halfway, but you're also = > missing out on all > > the 3dm utils and whatnot, which are important to the = > maintenance of your > > array. The newest drivers for the 9500 series include all = > that - so they > > are providing properly supported stuff for our platform = > now, if only I can > > get it to work with a 5.2.x series kernel. > > = > > I'd like to try it out as a kernel module, but kernel modules don't > > work yet in 5.2.x/AMD64. 3ware told me they need to get someone else > > involved to work on the kernel driver issue too... > > = > > So I've been patient waiting for them to help. > > = > > Email me back with any questions. I can give you my contact = > there so there > > can be an additional person bugging him for status on this. =3D) > > = > > Hope this helps! > > - mike > > = > > = > > On Tue, 22 Jun 2004, Peter Losher wrote: > > = > > > So I am tracking down a possible controller issue with a = > dual-Opteron > > > system (running the amd64 port - 5.2.1-REL branch) which = > has a 3ware > > > 8506-12 SATA controller controlling 1.2TB of disk space. > > > > > > While the system iself is nice, under sustained high disk = > I/O, the system > > > randomly locks up hard. (requires a hard reset) > > > You might want to upgrade to twe in -CURRENT, and see if that makes a difference. > > > In trying to diagnose the problem I noticed the kernel = > recognises it as a > > > 12 channel controller (albiet from the 7000 series): > > > > > > -=3D- > > > % grep twe /var/run/dmesg.boot > > > twe0: <3ware 7000 series Storage Controller. Driver = > version 1.50.00.000> > > > port 0x8c00-0x8c0f mem = > 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq > > > 29 at device 1.0 on pci1 > > > twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > > > -=3D- > > > > > > When we took delivery of the system late last year, the 12 channel > > > version of the 8506 card was so new you had to run = > 5.2-RC2 to get a > > > version of the twe driver to support it. Have there been = > changes to the > > > driver since then to better support this card? > > > > > > (Of course the problem may be elsewhere, the MB, CPU(s), = > memory... The > > > joys of HW debugging) Side note I have noticed that I = > can install 5.2.1 > > > on the box and update to the latest patch level, but = > subequent 'make > > > buildworld's usually dies randomly on a signal 4 error. > > > > > > Best Wishes - Peter > > > -- > > > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The = > bits must flow > > > > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to = > "freebsd-amd64-unsubscribe@freebsd.org" > = > -- = > -- David (obrien@FreeBSD.org) > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 01:11:01 2004 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 2903016A4CE for ; Wed, 23 Jun 2004 01:11:01 +0000 (GMT) Received: from smtp2.linkline.com (smtp2.linkline.com [64.30.215.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09D9D43D5C for ; Wed, 23 Jun 2004 01:11:00 +0000 (GMT) (envelope-from sclements@linkline.com) Received: from samclementsde (host-66-59-225-129.lcinet.net [66.59.225.129]) by smtp2.linkline.com (Postfix) with ESMTP id 343DE1AA; Tue, 22 Jun 2004 18:10:57 -0700 (PDT) From: "Samuel Clements" To: "'Ketrien I. Saihr-Kesenchedra'" , "'Marc G. Fournier'" Date: Tue, 22 Jun 2004 18:11:00 -0700 Organization: linkLINE Communications, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcRYoBX7RmHaRP6fS0mSxdiKfVhzCQAHlAlw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2149 In-Reply-To: <6.1.1.1.2.20040622171913.02b0b160@error404.nls.net> Message-Id: <20040623011057.343DE1AA@smtp2.linkline.com> cc: hardware@freebsd.org Subject: RE: RFC: Chenbro Chassis (RM214) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: sclements@linkline.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 01:11:01 -0000 > As far as Chenbro, avoid at all costs. We had nothing but trouble with > them. The backplane connections are non-standard (male to female,) and the > backplanes frequently lost entire channels due to shoddy quality and > failing to follow SCSI specifications. Heat was a constant problem due to > a > flawed layout, and the fans were pretty much worthless. I wouldn't take > another one if someone paid me. We've had really good experiences with the RM225 chassis from chenbro, but they do not use backplanes and yes, we do replace the fans with ball-bearing ones. This particular chassis is excellent for use if you only need two fixed hard drives and/or multiple 3.5 or 5.25 devices. I don't know if it's qualified for this particular board or not, but you may want to ask your reseller about available PSU's, etc... -Sam From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 01:11:36 2004 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 C9EC416A4CE; Wed, 23 Jun 2004 01:11:36 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DB5543D2D; Wed, 23 Jun 2004 01:11:36 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from tardis.isc.org (tardis.isc.org [IPv6:2001:4f8:3:bb:230:1bff:fe31:a192]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 9D2AEA960; Wed, 23 Jun 2004 01:11:27 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: "Vinod Kashyap" Date: Tue, 22 Jun 2004 18:11:41 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_TjN2ACqlY58oCJo"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406221811.47868.Peter_Losher@isc.org> cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 01:11:36 -0000 --Boundary-02=_TjN2ACqlY58oCJo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 22 June 2004 05:16 pm, you wrote: > The official support on FreeBSD for 7xxx, 8xxx and 9xxx series > controllers is only for i386. Although the driver might work > on other platforms, it's never been tested. The FreeBSD management > tools provided by 3ware are only for i386. Any word on work on a amd64-compatible driver? (mike seemed to indicate tha= t a=20 amd64 driver for the 9xxx series might come later this summer?) > You might want to upgrade to twe in -CURRENT, and see if that > makes a difference. Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT=20 cvsup'ed 30 minutes ago, and it didn't go to well: =2D=3D- cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototype= s =20 =2DWmissing-prototypes -Wpointer-arith -Winline -Wcast-qual =20 =2Dfformat-extensions -std=3Dc99 -nostdinc -I- -I. -I/usr/src/sys=20 =2DI/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter=20 =2DI/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd=20 =2DI/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common= =20 =2Dfinline-limit=3D20000 -fno-strict-aliasing -fno-omit-frame-pointer=20 =2Dmcmodel=3Dkernel -mno-red-zone -mfpmath=3D387 -mno-sse -mno-sse2 -mno-m= mx=20 =2Dmno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding=20 =2DWerror /usr/src/sys/dev/twe/twe_freebsd.c /usr/src/sys/dev/twe/twe_freebsd.c:70: error: unknown field `d_version'=20 specified in initializer /usr/src/sys/dev/twe/twe_freebsd.c:70: error: `D_VERSION' undeclared here (= not=20 in a function) /usr/src/sys/dev/twe/twe_freebsd.c:70: error: initializer element is not=20 constant /usr/src/sys/dev/twe/twe_freebsd.c:70: error: (near initialization for=20 `twe_cdevsw.d_maj') /usr/src/sys/dev/twe/twe_freebsd.c:71: error: `D_NEEDGIANT' undeclared here= =20 (not in a function) /usr/src/sys/dev/twe/twe_freebsd.c:71: error: initializer element is not=20 constant /usr/src/sys/dev/twe/twe_freebsd.c:71: error: (near initialization for=20 `twe_cdevsw.d_flags') /usr/src/sys/dev/twe/twe_freebsd.c: In function `twe_attach': /usr/src/sys/dev/twe/twe_freebsd.c:219: warning: implicit declaration of=20 function `bus_alloc_resource_any' /usr/src/sys/dev/twe/twe_freebsd.c:220: warning: assignment makes pointer f= rom=20 integer without a cast /usr/src/sys/dev/twe/twe_freebsd.c:251: warning: redundant redeclaration of= =20 `bus_alloc_resource_any' in same scope /usr/src/sys/dev/twe/twe_freebsd.c:219: warning: previous declaration of=20 `bus_alloc_resource_any' /usr/src/sys/dev/twe/twe_freebsd.c:252: warning: assignment makes pointer f= rom=20 integer without a cast /usr/src/sys/dev/twe/twe_freebsd.c: In function `twed_attach': /usr/src/sys/dev/twe/twe_freebsd.c:813: warning: implicit declaration of=20 function `disk_alloc' /usr/src/sys/dev/twe/twe_freebsd.c:813: warning: assignment makes pointer f= rom=20 integer without a cast /usr/src/sys/dev/twe/twe_freebsd.c:825: error: `DISKFLAG_NEEDSGIANT'=20 undeclared (first use in this function) /usr/src/sys/dev/twe/twe_freebsd.c:825: error: (Each undeclared identifier = is=20 reported only once /usr/src/sys/dev/twe/twe_freebsd.c:825: error: for each function it appears= =20 in.) /usr/src/sys/dev/twe/twe_freebsd.c:827: error: `DISK_VERSION' undeclared=20 (first use in this function) /usr/src/sys/dev/twe/twe_freebsd.c:827: warning: passing arg 1 of=20 `disk_create' makes integer from pointer without a cast /usr/src/sys/dev/twe/twe_freebsd.c:827: error: too few arguments to functio= n=20 `disk_create' *** Error code 1 Stop in /usr/obj/usr/src/sys/AMD_64_WITNESS. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. =2D=3D- If there is something I can hack in to twe_freebsd.c to get it to compile=20 under 5.2.1, I am all ears. =2DPeter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --Boundary-02=_TjN2ACqlY58oCJo Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA2NjTPtVx9OgEjQgRAjo/AKCIwGqezyEsQQywE3kTqPw8+GKOWQCeJCIF rT9QcSKGeqBTzJ4UjRt2HkY= =/DM6 -----END PGP SIGNATURE----- --Boundary-02=_TjN2ACqlY58oCJo-- From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 01:25:46 2004 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 D82BC16A4CE for ; Wed, 23 Jun 2004 01:25:46 +0000 (GMT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4311843D39 for ; Wed, 23 Jun 2004 01:25:46 +0000 (GMT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 3872EEAA18; Tue, 22 Jun 2004 22:25:46 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 3714BEAA17; Tue, 22 Jun 2004 22:25:46 -0300 (ADT) Date: Tue, 22 Jun 2004 22:25:46 -0300 (ADT) From: "Marc G. Fournier" To: Samuel Clements In-Reply-To: <20040623011057.343DE1AA@smtp2.linkline.com> Message-ID: <20040622222032.Y845@ganymede.hub.org> References: <20040623011057.343DE1AA@smtp2.linkline.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: "'Ketrien I. Saihr-Kesenchedra'" cc: hardware@freebsd.org Subject: RE: RFC: Chenbro Chassis (RM214) 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, 23 Jun 2004 01:25:47 -0000 On Tue, 22 Jun 2004, Samuel Clements wrote: >> As far as Chenbro, avoid at all costs. We had nothing but trouble with >> them. The backplane connections are non-standard (male to female,) and the >> backplanes frequently lost entire channels due to shoddy quality and >> failing to follow SCSI specifications. Heat was a constant problem due to >> a >> flawed layout, and the fans were pretty much worthless. I wouldn't take >> another one if someone paid me. > > > We've had really good experiences with the RM225 chassis from chenbro, but > they do not use backplanes and yes, we do replace the fans with ball-bearing > ones. This particular chassis is excellent for use if you only need two > fixed hard drives and/or multiple 3.5 or 5.25 devices. I don't know if it's > qualified for this particular board or not, but you may want to ask your > reseller about available PSU's, etc... The one we are looking at is: http://www.chenbro.com.tw/product/product.jsp?p=3&s=302&pid=22 With Dual-460W power supply ... Looks good ... 3x80mm fans + 4cm fan on rear panel ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 01:48:08 2004 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 2FC5F16A4CE; Wed, 23 Jun 2004 01:48:08 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E631343D48; Wed, 23 Jun 2004 01:48:07 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id C81861C14E; Tue, 22 Jun 2004 18:25:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id C628C1C11E; Tue, 22 Jun 2004 18:25:12 -0700 (PDT) Date: Tue, 22 Jun 2004 18:25:12 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Vinod Kashyap In-Reply-To: Message-ID: References: mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: Peter Losher cc: obrien@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 01:48:08 -0000 actually according to Victor Paccheco (sp) at 3ware, they have tested an AMD64 compatible driver as of a couple weeks ago for the 9500S series at least. However it was only tested on freebsd 4.9 and 5.1. Obviously 4.9 has no AMD64 support, but he has said it's 64-bit compliant and shoul drun fine on freebsd 5.1 on amd64. I can give you his contact information, he's my point of contact but not on the development team. He's just passing word back and forth between myself and the developers. I can also send you the files he sent me including the driver - however I believe all that is up on their website now as well. On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > > > -----Original Message----- > > From: David O'Brien [mailto:obrien@freebsd.org] > > Sent: Tuesday, June 22, 2004 4:21 PM > > To: Vinod Kashyap > > Cc: mike; Peter Losher; freebsd-amd64@freebsd.org; > > freebsd-hardware@freebsd.org > > Subject: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller > > issues... > > > > > > Vinod, > > > > As the FreeBSD 3Ware driver maintainer can you address these driver > > concerns on AMD64 hardware [in 64-bit mode]? > > > > thanks, > > -- David > > > > > > On Tue, Jun 22, 2004 at 07:36:56AM -0700, mike wrote: > > > I had nearly the exact same card and setup - dual opteron, > > freebsd-amd64, > > > 5.2.1-REL, 8506-8 card. > > > > > > When I called 3ware the guy told me AMD64 support for > > FreeBSD would be in > > > their 9000 series of cards - so I sent back my 8506-8 and > > got a 9500S-8. > > > BNesides for the hardware and BIOS improvements, they also > > did come out > > > with a driver as well. I could not get it to work loaded in > > the kernel and > > > kernel modules do not work for AMD64 yet. SO right now I > > have an email out > > > to the guys there asking if they can help me out. > > > > > > Apparently they only tested it for FreeBSD 4.9 and 5.1. > > However, they did > > > mention that support for the 8500 series and FreeBSD > > 5/amd64 would be much > > > later in the summer or year. Further reason why I took the > > hassle to RMA > > > the 8500 card and get the 9500S. > > > > > The official support on FreeBSD for 7xxx, 8xxx and 9xxx series > controllers is only for i386. Although the driver might work > on other platforms, it's never been tested. The FreeBSD management > tools provided by 3ware are only for i386. > > > > > My kernel also recognized the old card, even though the > > 3ware tech guy > > > said "that is not supported properly, it might see it, but > > it won't work > > > good" - the driver might work halfway, but you're also > > missing out on all > > > the 3dm utils and whatnot, which are important to the > > maintenance of your > > > array. The newest drivers for the 9500 series include all > > that - so they > > > are providing properly supported stuff for our platform > > now, if only I can > > > get it to work with a 5.2.x series kernel. > > > > > > I'd like to try it out as a kernel module, but kernel modules don't > > > work yet in 5.2.x/AMD64. 3ware told me they need to get someone else > > > involved to work on the kernel driver issue too... > > > > > > So I've been patient waiting for them to help. > > > > > > Email me back with any questions. I can give you my contact > > there so there > > > can be an additional person bugging him for status on this. =) > > > > > > Hope this helps! > > > - mike > > > > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > > > > So I am tracking down a possible controller issue with a > > dual-Opteron > > > > system (running the amd64 port - 5.2.1-REL branch) which > > has a 3ware > > > > 8506-12 SATA controller controlling 1.2TB of disk space. > > > > > > > > While the system iself is nice, under sustained high disk > > I/O, the system > > > > randomly locks up hard. (requires a hard reset) > > > > > > You might want to upgrade to twe in -CURRENT, and see if that > makes a difference. > > > > > > In trying to diagnose the problem I noticed the kernel > > recognises it as a > > > > 12 channel controller (albiet from the 7000 series): > > > > > > > > -=- > > > > % grep twe /var/run/dmesg.boot > > > > twe0: <3ware 7000 series Storage Controller. Driver > > version 1.50.00.000> > > > > port 0x8c00-0x8c0f mem > > 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffc0f irq > > > > 29 at device 1.0 on pci1 > > > > twe0: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > > > > -=- > > > > > > > > When we took delivery of the system late last year, the 12 channel > > > > version of the 8506 card was so new you had to run > > 5.2-RC2 to get a > > > > version of the twe driver to support it. Have there been > > changes to the > > > > driver since then to better support this card? > > > > > > > > (Of course the problem may be elsewhere, the MB, CPU(s), > > memory... The > > > > joys of HW debugging) Side note I have noticed that I > > can install 5.2.1 > > > > on the box and update to the latest patch level, but > > subequent 'make > > > > buildworld's usually dies randomly on a signal 4 error. > > > > > > > > Best Wishes - Peter > > > > -- > > > > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The > > bits must flow > > > > > > > _______________________________________________ > > > freebsd-amd64@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > > To unsubscribe, send any mail to > > "freebsd-amd64-unsubscribe@freebsd.org" > > > > -- > > -- David (obrien@FreeBSD.org) > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 01:48:08 2004 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 B2A2816A4CE; Wed, 23 Jun 2004 01:48:08 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7233743D2D; Wed, 23 Jun 2004 01:48:08 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id B8EA91C207; Tue, 22 Jun 2004 18:28:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id B73201C11E; Tue, 22 Jun 2004 18:28:25 -0700 (PDT) Date: Tue, 22 Jun 2004 18:28:25 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Peter Losher In-Reply-To: <200406221811.47868.Peter_Losher@isc.org> Message-ID: References: <200406221811.47868.Peter_Losher@isc.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 01:48:09 -0000 No - The 8xxx series is what I meant - he said support for that on FreeBSD 5.x with AMD64 support (I believe he was including it in that statement) was due out later this summer at the earliest. I was told quote "if you want 64-bit support you need to buy the 9500S card. We will be having a driver and utilities out for it within 2-3 weeks it's in testing right now." It turned out to be more like a month, but it did come out. I believe the binaries "run" but obviously without the driver properly compiled, it can't find a card to attach to. If modules could be compiled under AMD64, I might have a chance at making it work. However, trying to compile it into the kernel fails. I will followup this email with the actual mail I sent them at 3ware. On Tue, 22 Jun 2004, Peter Losher wrote: > On Tuesday 22 June 2004 05:16 pm, you wrote: > > > The official support on FreeBSD for 7xxx, 8xxx and 9xxx series > > controllers is only for i386. Although the driver might work > > on other platforms, it's never been tested. The FreeBSD management > > tools provided by 3ware are only for i386. > > Any word on work on a amd64-compatible driver? (mike seemed to indicate that a > amd64 driver for the 9xxx series might come later this summer?) > > > You might want to upgrade to twe in -CURRENT, and see if that > > makes a difference. > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT > cvsup'ed 30 minutes ago, and it didn't go to well: > > -=- > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd > -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer > -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -Werror /usr/src/sys/dev/twe/twe_freebsd.c > /usr/src/sys/dev/twe/twe_freebsd.c:70: error: unknown field `d_version' > specified in initializer > /usr/src/sys/dev/twe/twe_freebsd.c:70: error: `D_VERSION' undeclared here (not > in a function) > /usr/src/sys/dev/twe/twe_freebsd.c:70: error: initializer element is not > constant > /usr/src/sys/dev/twe/twe_freebsd.c:70: error: (near initialization for > `twe_cdevsw.d_maj') > /usr/src/sys/dev/twe/twe_freebsd.c:71: error: `D_NEEDGIANT' undeclared here > (not in a function) > /usr/src/sys/dev/twe/twe_freebsd.c:71: error: initializer element is not > constant > /usr/src/sys/dev/twe/twe_freebsd.c:71: error: (near initialization for > `twe_cdevsw.d_flags') > /usr/src/sys/dev/twe/twe_freebsd.c: In function `twe_attach': > /usr/src/sys/dev/twe/twe_freebsd.c:219: warning: implicit declaration of > function `bus_alloc_resource_any' > /usr/src/sys/dev/twe/twe_freebsd.c:220: warning: assignment makes pointer from > integer without a cast > /usr/src/sys/dev/twe/twe_freebsd.c:251: warning: redundant redeclaration of > `bus_alloc_resource_any' in same scope > /usr/src/sys/dev/twe/twe_freebsd.c:219: warning: previous declaration of > `bus_alloc_resource_any' > /usr/src/sys/dev/twe/twe_freebsd.c:252: warning: assignment makes pointer from > integer without a cast > /usr/src/sys/dev/twe/twe_freebsd.c: In function `twed_attach': > /usr/src/sys/dev/twe/twe_freebsd.c:813: warning: implicit declaration of > function `disk_alloc' > /usr/src/sys/dev/twe/twe_freebsd.c:813: warning: assignment makes pointer from > integer without a cast > /usr/src/sys/dev/twe/twe_freebsd.c:825: error: `DISKFLAG_NEEDSGIANT' > undeclared (first use in this function) > /usr/src/sys/dev/twe/twe_freebsd.c:825: error: (Each undeclared identifier is > reported only once > /usr/src/sys/dev/twe/twe_freebsd.c:825: error: for each function it appears > in.) > /usr/src/sys/dev/twe/twe_freebsd.c:827: error: `DISK_VERSION' undeclared > (first use in this function) > /usr/src/sys/dev/twe/twe_freebsd.c:827: warning: passing arg 1 of > `disk_create' makes integer from pointer without a cast > /usr/src/sys/dev/twe/twe_freebsd.c:827: error: too few arguments to function > `disk_create' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/AMD_64_WITNESS. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > -=- > > If there is something I can hack in to twe_freebsd.c to get it to compile > under 5.2.1, I am all ears. > > -Peter > -- > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:00:09 2004 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 4472D16A4CE; Wed, 23 Jun 2004 02:00:09 +0000 (GMT) Received: from mail.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8D8243D5E; Wed, 23 Jun 2004 02:00:04 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.jrv.org [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id i5N1xfQN012317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2004 20:59:42 -0500 (CDT) (envelope-from james@jrv.org) Message-ID: <40D8E40D.5090805@jrv.org> Date: Tue, 22 Jun 2004 20:59:41 -0500 From: "James R. Van Artsalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Losher References: <200406221811.47868.Peter_Losher@isc.org> In-Reply-To: <200406221811.47868.Peter_Losher@isc.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 02:00:09 -0000 Peter Losher wrote: >>You might want to upgrade to twe in -CURRENT, and see if that >>makes a difference. >> >> > >Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT >cvsup'ed 30 minutes ago, and it didn't go to well: > > 5.2.1-release w/8506-8 seems to work for me on AMD64 with 8 GB of RAM in a Tyan S2885 with two Opteron 248 CPUs in a slot jumpered to 64/66 PCI rather than PCI-X. I'm not trying to use any twe-specific monitoring tools and haven't tested to see if the twe driver notices disk errors. I believe that the driver does not handle more than 4 GB of RAM and requires bounce-buffers. Testing consisted of running "make buildworld" in a loop with a kernel building in a loop at the same; see if it's still running after a week and fsck is clean. From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:06:20 2004 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 6028716A4CE; Wed, 23 Jun 2004 02:06:20 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21D3F43D2D; Wed, 23 Jun 2004 02:06:20 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZQOHZ02.64N; Tue, 22 Jun 2004 19:05:59 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062219060309502 ; Tue, 22 Jun 2004 19:06:03 -0700 From: "Vinod Kashyap" To: mike , Peter Losher Date: Tue, 22 Jun 2004 19:05:58 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:06:20 -0000 I can't speak for Victor, but I did talk to him this afternoon, and he (and other support people) couldn't recall telling anyone that 3ware supports FreeBSD amd64. There might have been some miscommunica= tion/misunderstandings since 3ware does support amd64 on Linux and Windows. Even in the thread below, I don't see him mention FreeBSD amd64. Of course, the problem you had was on amd64, and I don't know if he realized it. The "different OS versions" probably refers to 4.x and 5.x. Anyways, I am sorry about any miscommunications, but as far as my knowledge goes, there's not even been a FreeBSD amd64 version of the driver built here, let alone tested. As about future plans, it might happen if there's sufficient interest, but at this point, there's none. Also, I wonder why you ran into build problems! twa has been in /sys/amd64/conf/GENERIC for sometime now, and no build problems have been reported so far. > -----Original Message----- > From: mike [mailto:mike@mike2k.com] > Sent: Tuesday, June 22, 2004 6:35 PM > To: Peter Losher > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > freebsd-hardware@freebsd.org > Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] Possible = > 3ware 8506-12 > SATA Controller issues... > = > = > Here is the last response I received from Victor: > = > On Wed, 16 Jun 2004, Victor Pacheco wrote: > = > > Hi, Mike > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > recompiling against newer kernels. He wrote: > > "FreeBSD is unlike Linux in that you can't use driver = > source to compile > a driver for different OS versions. > Customers must have the compiled version of the driver for = > their except > FreeBSD version or it will not work. > > Also, it was my understanding that the 9500S series does = > not yet support > FreeBSD. The driver is not on the > shipping CD or the web." > > > > I have passed this on to my manager (this does not make = > sense) since we > have the released driver/source. > > I need to know if it should compile with 5.2.1. > > > > I just shot the email and wait to here back. > > > > Best Regards, > > > > Victor Pacheco > > Technical Support Engineer > = > And here is the error I emailed him. I followed the = > instructions from the > manual, which were slightly outdated. Like it says = > "twa_opt.h" instead of > "opt_twa.h" - but I did everything I could to compile this far. > = > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > Makefile > > twa.c > > twa.h > > twa_cam.c > > twa_externs.h > > twa_freebsd.c > > twa_fwimg.c > > twa_globals.c > > twa_includes.h > > twa_ioctl.h > > twa_reg.h > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > TWA_DEBUG opt_twa.h > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > dev/twa/twa.c optional twa > > dev/twa/twa_cam.c optional twa > > dev/twa/twa_freebsd.c optional twa > > dev/twa/twa_fwimg.c optional twa > > dev/twa/twa_globals.c optional twa > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > device twa # 3ware ATA RAID > > > > i get an error trying to compile it. if i keep the = > TWA_DEBUG out of the > > options file, when i try to "make depend" it says = > "opt_twa.h not found" > - > > even though i don't want debugging. so i have to put that in and it > shuts > > up. > > > > here's the error: > > > > [root@raid01 conf]# config RAID01 > > Kernel build directory is ../compile/RAID01 > > Don't forget to do a ``make depend'' > > [root@raid01 conf]# cd ../compile/RAID01 > > [root@raid01 RAID01]# make depend > > rm -f .olddep > > if [ -f .depend ]; then mv .depend .olddep; fi > > make _kernel-depend > > if [ -f .olddep ]; then mv .olddep .depend; fi > > rm -f .newdep > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > MKDEP_CPP=3D"cc -E" CC=3D"cc" xargs mkdep -a -f .newdep -O -pipe -Wall= > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -std=3Dc99 -nostdinc -I- -I. -I../../.. > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > -finline-limit=3D20000 -fno-strict-aliasing -mcmodel=3Dkernel = > -mno-red-zone > > -mfpmath=3D387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > -fno-asynchronous-unwind-tables -ffreestanding > > make -V SFILES | MKDEP_CPP=3D"cc -E" xargs mkdep -a -f .newdep -x > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith > > -Winline -Wcast-qual -fformat-extensions -std=3Dc99 = > -nostdinc -I- -I. > > -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > -finline-limit=3D20000 -fno-strict-aliasing -mcmodel=3Dkernel = > -mno-red-zone > > -mfpmath=3D387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > -fno-asynchronous-unwind-tables -ffreestanding > > rm -f .depend > > mv .newdep .depend > > [root@raid01 RAID01]# make > > linking kernel > > twa_cam.o: In function `twa_cam_setup': > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > twa_cam.o(.text+0xe8): undefined reference to `xpt_bus_deregister' > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > twa_cam.o: In function `twa_cam_detach': > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > twa_cam.o(.text+0x191): undefined reference to `xpt_bus_deregister' > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > twa_cam.o: In function `twa_execute_scsi': > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > twa_cam.o: In function `twa_action': > > twa_cam.o(.text+0x58f): undefined reference to `cam_calc_geometry' > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > twa_cam.o: In function `twa_request_bus_scan': > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > twa_cam.o: In function `twa_bus_scan_cb': > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > twa_cam.o: In function `twa_scsi_complete': > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > twa_cam.o: In function `twa_drain_busy_queue': > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > twa_cam.o: In function `twa_disallow_new_requests': > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > *** Error code 1 > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > = > = > = > = > = > On Tue, 22 Jun 2004, Peter Losher wrote: > = > > > > Any word on work on a amd64-compatible driver? (mike seemed = > to indicate that a > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped = > from -CURRENT > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > -=3D- > > > > If there is something I can hack in to twe_freebsd.c to get = > it to compile > > under 5.2.1, I am all ears. > > > = > I myself would love this. I'd pay $250 cash to expedite this = > fix. Someone > could work directly with someone at 3ware and get 9500 matured, at > least... I wonder if I tried -current if my 9500 would work = > better. Is it > still based off the 7xxx series driver though? > = > At this point I've got hardware and software can't handle it. = > It's sort of > discouraging, usually it's the opposite. I might pay up to $500 to get > this going. It's worth it that much to get this damn thing = > fixed so I can > send this box back east and get it into production =3D) > = > = > = > > -Peter > > -- > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits = > must flow" > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:19:25 2004 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 3991716A4CE; Wed, 23 Jun 2004 02:19:25 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CBD643D49; Wed, 23 Jun 2004 02:19:25 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZQP0X00.H1F; Tue, 22 Jun 2004 19:17:21 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062219172609776 ; Tue, 22 Jun 2004 19:17:26 -0700 From: "Vinod Kashyap" To: mike , "James R. Van Artsalen" Date: Tue, 22 Jun 2004 19:17:20 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:19:25 -0000 > = > = > According to 3ware this is a dangerous setup =3D) > = > I was able to get it to recognize the 8506 as a 7xxx, but he said it > wasn't guaranteed to work at all. Also I liked using the 3dm = > and cli tools > so I could schedule the integrity and media checks and such. > = It's NOT "dangerous"! :-) The driver doesn't make a distinction between 7xxx and 8xxx controllers, and sees them all as "7000 series" controllers. Since this was apparently cause of confusion, I have reverted the driver to only say "3ware Storage Controller" in the later versions. There's only one driver for 7xxx and 8xxx (also 6xxx for that matter). > However, I didn't spend $4500-5000 to have a half-ass compatible box. > = > There was the software compatibility issue as well as the > motherboard/riser card possibility as well. > = > Hoever, I was told going the 9500 route, they'd support it; = > and I wanted > to be doing the right thing here. > = > = > = > On Tue, 22 Jun 2004, James R. Van Artsalen wrote: > = > > Peter Losher wrote: > > > > >>You might want to upgrade to twe in -CURRENT, and see if that > > >>makes a difference. > > >> > > >> > > > > > >Tried compiling a 5.2.1 kernel w/ the twe driver plopped = > from -CURRENT > > >cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > > > > > 5.2.1-release w/8506-8 seems to work for me on AMD64 with 8 = > GB of RAM in > > a Tyan S2885 with two Opteron 248 CPUs in a slot jumpered = > to 64/66 PCI > > rather than PCI-X. > > > > I'm not trying to use any twe-specific monitoring tools and haven't > > tested to see if the twe driver notices disk errors. > > > > I believe that the driver does not handle more than 4 GB of RAM and > > requires bounce-buffers. > > > > Testing consisted of running "make buildworld" in a loop = > with a kernel > > building in a loop at the same; see if it's still running = > after a week > > and fsck is clean. > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to = > "freebsd-amd64-unsubscribe@freebsd.org" > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:39:22 2004 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 D02F316A4D3; Wed, 23 Jun 2004 02:39:22 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F1843D39; Wed, 23 Jun 2004 02:39:22 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 5110B1BBEA; Tue, 22 Jun 2004 19:09:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 481FC1BA72; Tue, 22 Jun 2004 19:09:38 -0700 (PDT) Date: Tue, 22 Jun 2004 19:09:38 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Vinod Kashyap In-Reply-To: Message-ID: References: mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:39:23 -0000 The AMD64/64 bit support I was told would work in FreeBSD; not in the email below but by two different techs over the phone and nobody has called that as the reason for my troubles. Are you telling me that the GENERIC twa should work fine for the 9500 series of 3ware controllers? Careful, apparently this controller is only a month old. On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > I can't speak for Victor, but I did talk to him this afternoon, > and he (and other support people) couldn't recall telling anyone > that 3ware supports FreeBSD amd64. There might have been some miscommunication/misunderstandings since 3ware does support amd64 > on Linux and Windows. Even in the thread below, I don't see > him mention FreeBSD amd64. Of course, the problem you had was > on amd64, and I don't know if he realized it. The "different OS > versions" probably refers to 4.x and 5.x. > > Anyways, I am sorry about any miscommunications, but as far as my > knowledge goes, there's not even been a FreeBSD amd64 version of the > driver built here, let alone tested. As about future plans, it > might happen if there's sufficient interest, but at this point, > there's none. > > Also, I wonder why you ran into build problems! twa has been > in /sys/amd64/conf/GENERIC for sometime now, and no build problems > have been reported so far. > > > > -----Original Message----- > > From: mike [mailto:mike@mike2k.com] > > Sent: Tuesday, June 22, 2004 6:35 PM > > To: Peter Losher > > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > > freebsd-hardware@freebsd.org > > Subject: [freebsd-amd64] Re: [freebsd-amd64] Re: [freebsd-amd64] Possible > > 3ware 8506-12 > > SATA Controller issues... > > > > > > Here is the last response I received from Victor: > > > > On Wed, 16 Jun 2004, Victor Pacheco wrote: > > > > > Hi, Mike > > > > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > > recompiling against newer kernels. He wrote: > > > "FreeBSD is unlike Linux in that you can't use driver > > source to compile > > a driver for different OS versions. > > Customers must have the compiled version of the driver for > > their except > > FreeBSD version or it will not work. > > > Also, it was my understanding that the 9500S series does > > not yet support > > FreeBSD. The driver is not on the > > shipping CD or the web." > > > > > > I have passed this on to my manager (this does not make > > sense) since we > > have the released driver/source. > > > I need to know if it should compile with 5.2.1. > > > > > > I just shot the email and wait to here back. > > > > > > Best Regards, > > > > > > Victor Pacheco > > > Technical Support Engineer > > > > And here is the error I emailed him. I followed the > > instructions from the > > manual, which were slightly outdated. Like it says > > "twa_opt.h" instead of > > "opt_twa.h" - but I did everything I could to compile this far. > > > > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > > Makefile > > > twa.c > > > twa.h > > > twa_cam.c > > > twa_externs.h > > > twa_freebsd.c > > > twa_fwimg.c > > > twa_globals.c > > > twa_includes.h > > > twa_ioctl.h > > > twa_reg.h > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > > TWA_DEBUG opt_twa.h > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > > dev/twa/twa.c optional twa > > > dev/twa/twa_cam.c optional twa > > > dev/twa/twa_freebsd.c optional twa > > > dev/twa/twa_fwimg.c optional twa > > > dev/twa/twa_globals.c optional twa > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > > device twa # 3ware ATA RAID > > > > > > i get an error trying to compile it. if i keep the > > TWA_DEBUG out of the > > > options file, when i try to "make depend" it says > > "opt_twa.h not found" > > - > > > even though i don't want debugging. so i have to put that in and it > > shuts > > > up. > > > > > > here's the error: > > > > > > [root@raid01 conf]# config RAID01 > > > Kernel build directory is ../compile/RAID01 > > > Don't forget to do a ``make depend'' > > > [root@raid01 conf]# cd ../compile/RAID01 > > > [root@raid01 RAID01]# make depend > > > rm -f .olddep > > > if [ -f .depend ]; then mv .depend .olddep; fi > > > make _kernel-depend > > > if [ -f .olddep ]; then mv .olddep .depend; fi > > > rm -f .newdep > > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > > MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -Wall > > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > > -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > -mno-red-zone > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > -fno-asynchronous-unwind-tables -ffreestanding > > > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x > > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > > -Winline -Wcast-qual -fformat-extensions -std=c99 > > -nostdinc -I- -I. > > > -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > -mno-red-zone > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > -fno-asynchronous-unwind-tables -ffreestanding > > > rm -f .depend > > > mv .newdep .depend > > > [root@raid01 RAID01]# make > > > linking kernel > > > twa_cam.o: In function `twa_cam_setup': > > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > > twa_cam.o(.text+0xe8): undefined reference to `xpt_bus_deregister' > > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > > twa_cam.o: In function `twa_cam_detach': > > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > > twa_cam.o(.text+0x191): undefined reference to `xpt_bus_deregister' > > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > > twa_cam.o: In function `twa_execute_scsi': > > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > > twa_cam.o: In function `twa_action': > > > twa_cam.o(.text+0x58f): undefined reference to `cam_calc_geometry' > > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > > twa_cam.o: In function `twa_request_bus_scan': > > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > > twa_cam.o: In function `twa_bus_scan_cb': > > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > > twa_cam.o: In function `twa_scsi_complete': > > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > > twa_cam.o: In function `twa_drain_busy_queue': > > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > > twa_cam.o: In function `twa_disallow_new_requests': > > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > > *** Error code 1 > > > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > > > > > > > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > > > > > Any word on work on a amd64-compatible driver? (mike seemed > > to indicate that a > > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped > > from -CURRENT > > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > -=- > > > > > > If there is something I can hack in to twe_freebsd.c to get > > it to compile > > > under 5.2.1, I am all ears. > > > > > > > I myself would love this. I'd pay $250 cash to expedite this > > fix. Someone > > could work directly with someone at 3ware and get 9500 matured, at > > least... I wonder if I tried -current if my 9500 would work > > better. Is it > > still based off the 7xxx series driver though? > > > > At this point I've got hardware and software can't handle it. > > It's sort of > > discouraging, usually it's the opposite. I might pay up to $500 to get > > this going. It's worth it that much to get this damn thing > > fixed so I can > > send this box back east and get it into production =) > > > > > > > > > -Peter > > > -- > > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits > > must flow" > > > > > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:39:24 2004 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 CAB7F16A4D1; Wed, 23 Jun 2004 02:39:24 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C2EA43D48; Wed, 23 Jun 2004 02:39:24 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 4C9311C24D; Tue, 22 Jun 2004 18:34:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 4A84A1C240; Tue, 22 Jun 2004 18:34:38 -0700 (PDT) Date: Tue, 22 Jun 2004 18:34:38 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Peter Losher In-Reply-To: <200406221811.47868.Peter_Losher@isc.org> Message-ID: References: <200406221811.47868.Peter_Losher@isc.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:39:25 -0000 Here is the last response I received from Victor: On Wed, 16 Jun 2004, Victor Pacheco wrote: > Hi, Mike > > > I am told by our engineer 5.2.1 is not supported nor we support recompiling against newer kernels. He wrote: > "FreeBSD is unlike Linux in that you can't use driver source to compile a driver for different OS versions. Customers must have the compiled version of the driver for their except FreeBSD version or it will not work. > Also, it was my understanding that the 9500S series does not yet support FreeBSD. The driver is not on the shipping CD or the web." > > I have passed this on to my manager (this does not make sense) since we have the released driver/source. > I need to know if it should compile with 5.2.1. > > I just shot the email and wait to here back. > > Best Regards, > > Victor Pacheco > Technical Support Engineer And here is the error I emailed him. I followed the instructions from the manual, which were slightly outdated. Like it says "twa_opt.h" instead of "opt_twa.h" - but I did everything I could to compile this far. > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > Makefile > twa.c > twa.h > twa_cam.c > twa_externs.h > twa_freebsd.c > twa_fwimg.c > twa_globals.c > twa_includes.h > twa_ioctl.h > twa_reg.h > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > TWA_DEBUG opt_twa.h > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > dev/twa/twa.c optional twa > dev/twa/twa_cam.c optional twa > dev/twa/twa_freebsd.c optional twa > dev/twa/twa_fwimg.c optional twa > dev/twa/twa_globals.c optional twa > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > device twa # 3ware ATA RAID > > i get an error trying to compile it. if i keep the TWA_DEBUG out of the > options file, when i try to "make depend" it says "opt_twa.h not found" - > even though i don't want debugging. so i have to put that in and it shuts > up. > > here's the error: > > [root@raid01 conf]# config RAID01 > Kernel build directory is ../compile/RAID01 > Don't forget to do a ``make depend'' > [root@raid01 conf]# cd ../compile/RAID01 > [root@raid01 RAID01]# make depend > rm -f .olddep > if [ -f .depend ]; then mv .depend .olddep; fi > make _kernel-depend > if [ -f .olddep ]; then mv .olddep .depend; fi > rm -f .newdep > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel -mno-red-zone > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. > -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel -mno-red-zone > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding > rm -f .depend > mv .newdep .depend > [root@raid01 RAID01]# make > linking kernel > twa_cam.o: In function `twa_cam_setup': > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > twa_cam.o(.text+0xe8): undefined reference to `xpt_bus_deregister' > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > twa_cam.o: In function `twa_cam_detach': > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > twa_cam.o(.text+0x191): undefined reference to `xpt_bus_deregister' > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > twa_cam.o: In function `twa_execute_scsi': > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > twa_cam.o: In function `twa_action': > twa_cam.o(.text+0x58f): undefined reference to `cam_calc_geometry' > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > twa_cam.o: In function `twa_request_bus_scan': > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > twa_cam.o: In function `twa_bus_scan_cb': > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > twa_cam.o: In function `twa_scsi_complete': > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > twa_cam.o: In function `twa_drain_busy_queue': > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > twa_cam.o: In function `twa_disallow_new_requests': > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > *** Error code 1 > > Stop in /usr/src/sys/amd64/compile/RAID01. On Tue, 22 Jun 2004, Peter Losher wrote: > > Any word on work on a amd64-compatible driver? (mike seemed to indicate that a > amd64 driver for the 9xxx series might come later this summer?) > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT > cvsup'ed 30 minutes ago, and it didn't go to well: > > -=- > > If there is something I can hack in to twe_freebsd.c to get it to compile > under 5.2.1, I am all ears. > I myself would love this. I'd pay $250 cash to expedite this fix. Someone could work directly with someone at 3ware and get 9500 matured, at least... I wonder if I tried -current if my 9500 would work better. Is it still based off the 7xxx series driver though? At this point I've got hardware and software can't handle it. It's sort of discouraging, usually it's the opposite. I might pay up to $500 to get this going. It's worth it that much to get this damn thing fixed so I can send this box back east and get it into production =) > -Peter > -- > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:39:25 2004 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 33DC916A4CE; Wed, 23 Jun 2004 02:39:25 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15A1D43D48; Wed, 23 Jun 2004 02:39:25 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id A264E1C14E; Tue, 22 Jun 2004 19:08:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id A000C1BBEA; Tue, 22 Jun 2004 19:08:07 -0700 (PDT) Date: Tue, 22 Jun 2004 19:08:07 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: "James R. Van Artsalen" In-Reply-To: <40D8E40D.5090805@jrv.org> Message-ID: References: <200406221811.47868.Peter_Losher@isc.org> <40D8E40D.5090805@jrv.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: Vinod Kashyap Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:39:25 -0000 According to 3ware this is a dangerous setup =) I was able to get it to recognize the 8506 as a 7xxx, but he said it wasn't guaranteed to work at all. Also I liked using the 3dm and cli tools so I could schedule the integrity and media checks and such. However, I didn't spend $4500-5000 to have a half-ass compatible box. There was the software compatibility issue as well as the motherboard/riser card possibility as well. Hoever, I was told going the 9500 route, they'd support it; and I wanted to be doing the right thing here. On Tue, 22 Jun 2004, James R. Van Artsalen wrote: > Peter Losher wrote: > > >>You might want to upgrade to twe in -CURRENT, and see if that > >>makes a difference. > >> > >> > > > >Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT > >cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > 5.2.1-release w/8506-8 seems to work for me on AMD64 with 8 GB of RAM in > a Tyan S2885 with two Opteron 248 CPUs in a slot jumpered to 64/66 PCI > rather than PCI-X. > > I'm not trying to use any twe-specific monitoring tools and haven't > tested to see if the twe driver notices disk errors. > > I believe that the driver does not handle more than 4 GB of RAM and > requires bounce-buffers. > > Testing consisted of running "make buildworld" in a loop with a kernel > building in a loop at the same; see if it's still running after a week > and fsck is clean. > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:41:38 2004 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 8ED0F16A4CF; Wed, 23 Jun 2004 02:41:38 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F90943D41; Wed, 23 Jun 2004 02:41:38 +0000 (GMT) (envelope-from ps@mu.org) Received: from [216.145.52.43] (butter.corp.yahoo.com [216.145.52.43]) by elvis.mu.org (Postfix) with ESMTP id E42B05C80C; Tue, 22 Jun 2004 19:41:00 -0700 (PDT) From: Paul Saab To: freebsd-hardware@freebsd.org Date: Tue, 22 Jun 2004 19:41:00 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406221941.00765.ps@mu.org> cc: mike cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: Peter Losher Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:41:38 -0000 If you dont have CAM in your kernel, then twa will not work. On Tuesday 22 June 2004 07:09 pm, mike wrote: > The AMD64/64 bit support I was told would work in FreeBSD; not in the > email below but by two different techs over the phone and nobody has > called that as the reason for my troubles. > > Are you telling me that the GENERIC twa should work fine for the 9500 > series of 3ware controllers? Careful, apparently this controller is only a > month old. > > On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > I can't speak for Victor, but I did talk to him this afternoon, > > and he (and other support people) couldn't recall telling anyone > > that 3ware supports FreeBSD amd64. There might have been some > > miscommunication/misunderstandings since 3ware does support amd64 on > > Linux and Windows. Even in the thread below, I don't see > > him mention FreeBSD amd64. Of course, the problem you had was > > on amd64, and I don't know if he realized it. The "different OS > > versions" probably refers to 4.x and 5.x. > > > > Anyways, I am sorry about any miscommunications, but as far as my > > knowledge goes, there's not even been a FreeBSD amd64 version of the > > driver built here, let alone tested. As about future plans, it > > might happen if there's sufficient interest, but at this point, > > there's none. > > > > Also, I wonder why you ran into build problems! twa has been > > in /sys/amd64/conf/GENERIC for sometime now, and no build problems > > have been reported so far. > > > > > -----Original Message----- > > > From: mike [mailto:mike@mike2k.com] > > > Sent: Tuesday, June 22, 2004 6:35 PM > > > To: Peter Losher > > > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > > > freebsd-hardware@freebsd.org > > > Subject: [freebsd-amd64] Re: [freebsd-amd64] Re: [freebsd-amd64] > > > Possible 3ware 8506-12 > > > SATA Controller issues... > > > > > > > > > Here is the last response I received from Victor: > > > > > > On Wed, 16 Jun 2004, Victor Pacheco wrote: > > > > Hi, Mike > > > > > > > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > > > > > > recompiling against newer kernels. He wrote: > > > > "FreeBSD is unlike Linux in that you can't use driver > > > > > > source to compile > > > a driver for different OS versions. > > > Customers must have the compiled version of the driver for > > > their except > > > FreeBSD version or it will not work. > > > > > > > Also, it was my understanding that the 9500S series does > > > > > > not yet support > > > FreeBSD. The driver is not on the > > > shipping CD or the web." > > > > > > > I have passed this on to my manager (this does not make > > > > > > sense) since we > > > have the released driver/source. > > > > > > > I need to know if it should compile with 5.2.1. > > > > > > > > I just shot the email and wait to here back. > > > > > > > > Best Regards, > > > > > > > > Victor Pacheco > > > > Technical Support Engineer > > > > > > And here is the error I emailed him. I followed the > > > instructions from the > > > manual, which were slightly outdated. Like it says > > > "twa_opt.h" instead of > > > "opt_twa.h" - but I did everything I could to compile this far. > > > > > > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > > > Makefile > > > > twa.c > > > > twa.h > > > > twa_cam.c > > > > twa_externs.h > > > > twa_freebsd.c > > > > twa_fwimg.c > > > > twa_globals.c > > > > twa_includes.h > > > > twa_ioctl.h > > > > twa_reg.h > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > > > TWA_DEBUG opt_twa.h > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > > > dev/twa/twa.c optional twa > > > > dev/twa/twa_cam.c optional twa > > > > dev/twa/twa_freebsd.c optional twa > > > > dev/twa/twa_fwimg.c optional twa > > > > dev/twa/twa_globals.c optional twa > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > > > device twa # 3ware ATA RAID > > > > > > > > i get an error trying to compile it. if i keep the > > > > > > TWA_DEBUG out of the > > > > > > > options file, when i try to "make depend" it says > > > > > > "opt_twa.h not found" > > > - > > > > > > > even though i don't want debugging. so i have to put that in and it > > > > > > shuts > > > > > > > up. > > > > > > > > here's the error: > > > > > > > > [root@raid01 conf]# config RAID01 > > > > Kernel build directory is ../compile/RAID01 > > > > Don't forget to do a ``make depend'' > > > > [root@raid01 conf]# cd ../compile/RAID01 > > > > [root@raid01 RAID01]# make depend > > > > rm -f .olddep > > > > if [ -f .depend ]; then mv .depend .olddep; fi > > > > make _kernel-depend > > > > if [ -f .olddep ]; then mv .olddep .depend; fi > > > > rm -f .newdep > > > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > > > MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -Wall > > > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > > > -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > > > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > > > -mno-red-zone > > > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x > > > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > > > > > -Wpointer-arith > > > > > > > -Winline -Wcast-qual -fformat-extensions -std=c99 > > > > > > -nostdinc -I- -I. > > > > > > > -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > > > -mno-red-zone > > > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > rm -f .depend > > > > mv .newdep .depend > > > > [root@raid01 RAID01]# make > > > > linking kernel > > > > twa_cam.o: In function `twa_cam_setup': > > > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > > > twa_cam.o(.text+0xe8): undefined reference to `xpt_bus_deregister' > > > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > > > twa_cam.o: In function `twa_cam_detach': > > > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > > > twa_cam.o(.text+0x191): undefined reference to `xpt_bus_deregister' > > > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > > > twa_cam.o: In function `twa_execute_scsi': > > > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_action': > > > > twa_cam.o(.text+0x58f): undefined reference to `cam_calc_geometry' > > > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_request_bus_scan': > > > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > > > twa_cam.o: In function `twa_bus_scan_cb': > > > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > > > twa_cam.o: In function `twa_scsi_complete': > > > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_drain_busy_queue': > > > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_disallow_new_requests': > > > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > > > *** Error code 1 > > > > > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > Any word on work on a amd64-compatible driver? (mike seemed > > > > > > to indicate that a > > > > > > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped > > > > > > from -CURRENT > > > > > > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > > > -=- > > > > > > > > If there is something I can hack in to twe_freebsd.c to get > > > > > > it to compile > > > > > > > under 5.2.1, I am all ears. > > > > > > I myself would love this. I'd pay $250 cash to expedite this > > > fix. Someone > > > could work directly with someone at 3ware and get 9500 matured, at > > > least... I wonder if I tried -current if my 9500 would work > > > better. Is it > > > still based off the 7xxx series driver though? > > > > > > At this point I've got hardware and software can't handle it. > > > It's sort of > > > discouraging, usually it's the opposite. I might pay up to $500 to get > > > this going. It's worth it that much to get this damn thing > > > fixed so I can > > > send this box back east and get it into production =) > > > > > > > -Peter > > > > -- > > > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits > > > > > > must flow" > > > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > _______________________________________________ > 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 Wed Jun 23 02:46:26 2004 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 24C9616A4CE; Wed, 23 Jun 2004 02:46:26 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 089EF43D31; Wed, 23 Jun 2004 02:46:26 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from tardis.isc.org (tardis.isc.org [IPv6:2001:4f8:3:bb:230:1bff:fe31:a192]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id C556BA951; Wed, 23 Jun 2004 02:46:02 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: "Vinod Kashyap" Date: Tue, 22 Jun 2004 19:46:22 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_/7O2AVnurvodbeE"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406221946.23458.Peter_Losher@isc.org> cc: mike cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:46:26 -0000 --Boundary-02=_/7O2AVnurvodbeE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 22 June 2004 07:19 pm, Vinod Kashyap wrote: > > Are you telling me that the GENERIC twa should work fine for the 9500 > > series of 3ware controllers? Careful, apparently this > > controller is only a > > month old. > > I am telling you it should "build" fine since I haven't heard of build > problems during the nightly builds of the FreeBSD cvs repository. To clear up some (percieved) confusion here: What I am trying to do is take the twe driver that is in -CURRENT and compi= le=20 it inside of a 5.2.1 kernel. The twe driver as it stands now in -CURRENT m= ay=20 require other bits that are -CURRENT specific and may not be easily=20 back-portable to 5.2.1-RELEASE (which is what this amd64 system runs), whic= h=20 is what I was asking when I posted my errors to the list. Best Wishes - Peter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --Boundary-02=_/7O2AVnurvodbeE Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA2O7/PtVx9OgEjQgRAsImAKCBYGdEphAH69v4GoZsng0OpCkKTQCcD0Df 87pbyZOVIlpl0P9sL0wfyww= =pLrV -----END PGP SIGNATURE----- --Boundary-02=_/7O2AVnurvodbeE-- From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:48:23 2004 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 AD43916A4CE for ; Wed, 23 Jun 2004 02:48:23 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CECF43D39 for ; Wed, 23 Jun 2004 02:48:23 +0000 (GMT) (envelope-from ps@mu.org) Received: from [216.145.52.43] (butter.corp.yahoo.com [216.145.52.43]) by elvis.mu.org (Postfix) with ESMTP id A4C605C750 for ; Tue, 22 Jun 2004 19:47:58 -0700 (PDT) From: Paul Saab To: freebsd-hardware@freebsd.org Date: Tue, 22 Jun 2004 19:47:58 -0700 User-Agent: KMail/1.6.2 References: <200406221946.23458.Peter_Losher@isc.org> In-Reply-To: <200406221946.23458.Peter_Losher@isc.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406221947.58422.ps@mu.org> Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:48:23 -0000 Can you make a box available.. I can do this pretty easily. On Tuesday 22 June 2004 07:46 pm, Peter Losher wrote: > On Tuesday 22 June 2004 07:19 pm, Vinod Kashyap wrote: > > > Are you telling me that the GENERIC twa should work fine for the 9500 > > > series of 3ware controllers? Careful, apparently this > > > controller is only a > > > month old. > > > > I am telling you it should "build" fine since I haven't heard of build > > problems during the nightly builds of the FreeBSD cvs repository. > > To clear up some (percieved) confusion here: > > What I am trying to do is take the twe driver that is in -CURRENT and > compile it inside of a 5.2.1 kernel. The twe driver as it stands now in > -CURRENT may require other bits that are -CURRENT specific and may not be > easily back-portable to 5.2.1-RELEASE (which is what this amd64 system > runs), which is what I was asking when I posted my errors to the list. > > Best Wishes - Peter From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 02:57:30 2004 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 AC57716A4CE; Wed, 23 Jun 2004 02:57:30 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7732743D46; Wed, 23 Jun 2004 02:57:30 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZQQUK00.U2Q; Tue, 22 Jun 2004 19:56:44 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062219564810673 ; Tue, 22 Jun 2004 19:56:49 -0700 From: "Vinod Kashyap" To: Peter Losher Date: Tue, 22 Jun 2004 19:56:43 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: cc: mike cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 02:57:30 -0000 > -----Original Message----- > From: Peter Losher [mailto:Peter_Losher@isc.org] > Sent: Tuesday, June 22, 2004 7:46 PM > To: Vinod Kashyap > Cc: mike; freebsd-amd64@freebsd.org; freebsd-hardware@freebsd.org > Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64] > Possible 3ware 8506-12SATA Controller issues... > = > = > On Tuesday 22 June 2004 07:19 pm, Vinod Kashyap wrote: > = > > > Are you telling me that the GENERIC twa should work fine = > for the 9500 > > > series of 3ware controllers? Careful, apparently this > > > controller is only a > > > month old. > > > > I am telling you it should "build" fine since I haven't = > heard of build > > problems during the nightly builds of the FreeBSD cvs repository. > = > To clear up some (percieved) confusion here: > = > What I am trying to do is take the twe driver that is in = > -CURRENT and compile = > it inside of a 5.2.1 kernel. The twe driver as it stands now = > in -CURRENT may = > require other bits that are -CURRENT specific and may not be easily = > back-portable to 5.2.1-RELEASE (which is what this amd64 = > system runs), which = > is what I was asking when I posted my errors to the list. I'm sorry I forgot to answer that. There are some recent changes in -CURRENT's twe, which I wanted you to try. To get over the build problems, on those lines that the compiler reports errors, you will have to revert to twe of 5.2.1. You should be able to see twe change history here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twe/ = > Best Wishes - Peter > -- = > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 06:53:25 2004 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 5526316A4CE; Wed, 23 Jun 2004 06:53:25 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3589D43D2F; Wed, 23 Jun 2004 06:53:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i5N6r8tZ079697; Tue, 22 Jun 2004 23:53:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5N6r796079696; Tue, 22 Jun 2004 23:53:07 -0700 (PDT) (envelope-from obrien) Date: Tue, 22 Jun 2004 23:53:07 -0700 From: "David O'Brien" To: Vinod Kashyap Message-ID: <20040623065307.GC79131@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: mike cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 06:53:25 -0000 On Tue, Jun 22, 2004 at 05:16:30PM -0700, Vinod Kashyap wrote: > > From: David O'Brien [mailto:obrien@freebsd.org] > > Vinod, > > As the FreeBSD 3Ware driver maintainer can you address these driver > > concerns on AMD64 hardware [in 64-bit mode]? ... > The official support on FreeBSD for 7xxx, 8xxx and 9xxx series > controllers is only for i386. Although the driver might work > on other platforms, it's never been tested. The FreeBSD management > tools provided by 3ware are only for i386. As twe(4) maintainer, what would it take for you to test the drivers on FreeBSD/AMD64 (in 64-bit mode)? -- -- David (obrien@FreeBSD.org) From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 07:20:34 2004 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 607B116A4CE; Wed, 23 Jun 2004 07:20:34 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F67243D62; Wed, 23 Jun 2004 07:20:34 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 9C93E1C267; Tue, 22 Jun 2004 20:57:31 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 9A7221C265; Tue, 22 Jun 2004 20:57:31 -0700 (PDT) Date: Tue, 22 Jun 2004 20:57:31 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Paul Saab In-Reply-To: <200406221941.00765.ps@mu.org> Message-ID: References: <200406221941.00765.ps@mu.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Peter Losher cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 07:20:34 -0000 i'd like to take a moment to thank paul. adding in these 3 lines to enable "CAM" apparently allowed the kernel to compile, and it has recognized it: device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) 3ware device driver for 9000 series storage controllers, version: 2.50.01.001 twa0: <3ware 9000 series Storage Controller> port 0x9800-0x98ff mem 0xfb800000-0xfbffffff,0xfc7ffc00-0xfc7ffcff irq 30 at device 5.0 on pci1 twa0: 8 ports, Firmware FE9X 2.02.00.008, BIOS BE9X 2.02.01.037 da0 at twa0 bus 0 target 0 lun 0 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 1430448MB (2929557504 512 byte sectors: 255H 63S/T 182356C) now we'll see if i can format it and such and then try to put a load on it. what do people suggest to ensure i put a load that could freeze it up if there are any driver issues? what program(s)/port(s) could i use to benchmark/stress test? On Tue, 22 Jun 2004, Paul Saab wrote: > If you dont have CAM in your kernel, then twa will not work. > > On Tuesday 22 June 2004 07:09 pm, mike wrote: > > The AMD64/64 bit support I was told would work in FreeBSD; not in the > > email below but by two different techs over the phone and nobody has > > called that as the reason for my troubles. > > > > Are you telling me that the GENERIC twa should work fine for the 9500 > > series of 3ware controllers? Careful, apparently this controller is only a > > month old. > > > > On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > > I can't speak for Victor, but I did talk to him this afternoon, > > > and he (and other support people) couldn't recall telling anyone > > > that 3ware supports FreeBSD amd64. There might have been some > > > miscommunication/misunderstandings since 3ware does support amd64 on > > > Linux and Windows. Even in the thread below, I don't see > > > him mention FreeBSD amd64. Of course, the problem you had was > > > on amd64, and I don't know if he realized it. The "different OS > > > versions" probably refers to 4.x and 5.x. > > > > > > Anyways, I am sorry about any miscommunications, but as far as my > > > knowledge goes, there's not even been a FreeBSD amd64 version of the > > > driver built here, let alone tested. As about future plans, it > > > might happen if there's sufficient interest, but at this point, > > > there's none. > > > > > > Also, I wonder why you ran into build problems! twa has been > > > in /sys/amd64/conf/GENERIC for sometime now, and no build problems > > > have been reported so far. > > > > > > > -----Original Message----- > > > > From: mike [mailto:mike@mike2k.com] > > > > Sent: Tuesday, June 22, 2004 6:35 PM > > > > To: Peter Losher > > > > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > > > > freebsd-hardware@freebsd.org > > > > Subject: [freebsd-amd64] [freebsd-amd64] Re: [freebsd-amd64] Re: [freebsd-amd64] > > > > Possible 3ware 8506-12 > > > > SATA Controller issues... > > > > > > > > > > > > Here is the last response I received from Victor: > > > > > > > > On Wed, 16 Jun 2004, Victor Pacheco wrote: > > > > > Hi, Mike > > > > > > > > > > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > > > > > > > > recompiling against newer kernels. He wrote: > > > > > "FreeBSD is unlike Linux in that you can't use driver > > > > > > > > source to compile > > > > a driver for different OS versions. > > > > Customers must have the compiled version of the driver for > > > > their except > > > > FreeBSD version or it will not work. > > > > > > > > > Also, it was my understanding that the 9500S series does > > > > > > > > not yet support > > > > FreeBSD. The driver is not on the > > > > shipping CD or the web." > > > > > > > > > I have passed this on to my manager (this does not make > > > > > > > > sense) since we > > > > have the released driver/source. > > > > > > > > > I need to know if it should compile with 5.2.1. > > > > > > > > > > I just shot the email and wait to here back. > > > > > > > > > > Best Regards, > > > > > > > > > > Victor Pacheco > > > > > Technical Support Engineer > > > > > > > > And here is the error I emailed him. I followed the > > > > instructions from the > > > > manual, which were slightly outdated. Like it says > > > > "twa_opt.h" instead of > > > > "opt_twa.h" - but I did everything I could to compile this far. > > > > > > > > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > > > > Makefile > > > > > twa.c > > > > > twa.h > > > > > twa_cam.c > > > > > twa_externs.h > > > > > twa_freebsd.c > > > > > twa_fwimg.c > > > > > twa_globals.c > > > > > twa_includes.h > > > > > twa_ioctl.h > > > > > twa_reg.h > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > > > > TWA_DEBUG opt_twa.h > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > > > > dev/twa/twa.c optional twa > > > > > dev/twa/twa_cam.c optional twa > > > > > dev/twa/twa_freebsd.c optional twa > > > > > dev/twa/twa_fwimg.c optional twa > > > > > dev/twa/twa_globals.c optional twa > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > > > > device twa # 3ware ATA RAID > > > > > > > > > > i get an error trying to compile it. if i keep the > > > > > > > > TWA_DEBUG out of the > > > > > > > > > options file, when i try to "make depend" it says > > > > > > > > "opt_twa.h not found" > > > > - > > > > > > > > > even though i don't want debugging. so i have to put that in and it > > > > > > > > shuts > > > > > > > > > up. > > > > > > > > > > here's the error: > > > > > > > > > > [root@raid01 conf]# config RAID01 > > > > > Kernel build directory is ../compile/RAID01 > > > > > Don't forget to do a ``make depend'' > > > > > [root@raid01 conf]# cd ../compile/RAID01 > > > > > [root@raid01 RAID01]# make depend > > > > > rm -f .olddep > > > > > if [ -f .depend ]; then mv .depend .olddep; fi > > > > > make _kernel-depend > > > > > if [ -f .olddep ]; then mv .olddep .depend; fi > > > > > rm -f .newdep > > > > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > > > > MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -Wall > > > > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > > > > -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > > > > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > > > > > -mno-red-zone > > > > > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x > > > > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > > > > > > > -Wpointer-arith > > > > > > > > > -Winline -Wcast-qual -fformat-extensions -std=c99 > > > > > > > > -nostdinc -I- -I. > > > > > > > > > -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common > > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > > > > > -mno-red-zone > > > > > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > > rm -f .depend > > > > > mv .newdep .depend > > > > > [root@raid01 RAID01]# make > > > > > linking kernel > > > > > twa_cam.o: In function `twa_cam_setup': > > > > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > > > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > > > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > > > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > > > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > > > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > > > > twa_cam.o(.text+0xe8): undefined reference to `xpt_bus_deregister' > > > > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > > > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > > > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > > > > twa_cam.o: In function `twa_cam_detach': > > > > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > > > > twa_cam.o(.text+0x191): undefined reference to `xpt_bus_deregister' > > > > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > > > > twa_cam.o: In function `twa_execute_scsi': > > > > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_action': > > > > > twa_cam.o(.text+0x58f): undefined reference to `cam_calc_geometry' > > > > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_request_bus_scan': > > > > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > > > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > > > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > > > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > > > > twa_cam.o: In function `twa_bus_scan_cb': > > > > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > > > > twa_cam.o: In function `twa_scsi_complete': > > > > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_drain_busy_queue': > > > > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_disallow_new_requests': > > > > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > > > > *** Error code 1 > > > > > > > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > > > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > > Any word on work on a amd64-compatible driver? (mike seemed > > > > > > > > to indicate that a > > > > > > > > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > > > > > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped > > > > > > > > from -CURRENT > > > > > > > > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > > > > > -=- > > > > > > > > > > If there is something I can hack in to twe_freebsd.c to get > > > > > > > > it to compile > > > > > > > > > under 5.2.1, I am all ears. > > > > > > > > I myself would love this. I'd pay $250 cash to expedite this > > > > fix. Someone > > > > could work directly with someone at 3ware and get 9500 matured, at > > > > least... I wonder if I tried -current if my 9500 would work > > > > better. Is it > > > > still based off the 7xxx series driver though? > > > > > > > > At this point I've got hardware and software can't handle it. > > > > It's sort of > > > > discouraging, usually it's the opposite. I might pay up to $500 to get > > > > this going. It's worth it that much to get this damn thing > > > > fixed so I can > > > > send this box back east and get it into production =) > > > > > > > > > -Peter > > > > > -- > > > > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits > > > > > > > > must flow" > > > > > > _______________________________________________ > > > freebsd-amd64@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > > _______________________________________________ > > 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 Wed Jun 23 11:54:32 2004 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 7A8C216A4CE; Wed, 23 Jun 2004 11:54:32 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47C2043D2F; Wed, 23 Jun 2004 11:54:32 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZQP3R02.G3B; Tue, 22 Jun 2004 19:19:03 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062219190709818 ; Tue, 22 Jun 2004 19:19:07 -0700 From: "Vinod Kashyap" To: mike Date: Tue, 22 Jun 2004 19:19:02 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 11:54:32 -0000 > = > The AMD64/64 bit support I was told would work in FreeBSD; not in the > email below but by two different techs over the phone and nobody has > called that as the reason for my troubles. > = > Are you telling me that the GENERIC twa should work fine for the 9500 > series of 3ware controllers? Careful, apparently this = > controller is only a > month old. > = I am telling you it should "build" fine since I haven't heard of build problems during the nightly builds of the FreeBSD cvs repository. > = > On Tue, 22 Jun 2004, Vinod Kashyap wrote: > = > > > > I can't speak for Victor, but I did talk to him this afternoon, > > and he (and other support people) couldn't recall telling anyone > > that 3ware supports FreeBSD amd64. There might have been = > some miscommunication/misunderstandings since 3ware does support amd64 > > on Linux and Windows. Even in the thread below, I don't see > > him mention FreeBSD amd64. Of course, the problem you had was > > on amd64, and I don't know if he realized it. The "different OS > > versions" probably refers to 4.x and 5.x. > > > > Anyways, I am sorry about any miscommunications, but as far as my > > knowledge goes, there's not even been a FreeBSD amd64 version of the > > driver built here, let alone tested. As about future plans, it > > might happen if there's sufficient interest, but at this point, > > there's none. > > > > Also, I wonder why you ran into build problems! twa has been > > in /sys/amd64/conf/GENERIC for sometime now, and no build problems > > have been reported so far. > > > > > > > -----Original Message----- > > > From: mike [mailto:mike@mike2k.com] > > > Sent: Tuesday, June 22, 2004 6:35 PM > > > To: Peter Losher > > > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > > > freebsd-hardware@freebsd.org > > > Subject: [freebsd-amd64] Re: [freebsd-amd64] Re: = > [freebsd-amd64] Possible > > > 3ware 8506-12 > > > SATA Controller issues... > > > > > > > > > Here is the last response I received from Victor: > > > > > > On Wed, 16 Jun 2004, Victor Pacheco wrote: > > > > > > > Hi, Mike > > > > > > > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > > > recompiling against newer kernels. He wrote: > > > > "FreeBSD is unlike Linux in that you can't use driver > > > source to compile > > > a driver for different OS versions. > > > Customers must have the compiled version of the driver for > > > their except > > > FreeBSD version or it will not work. > > > > Also, it was my understanding that the 9500S series does > > > not yet support > > > FreeBSD. The driver is not on the > > > shipping CD or the web." > > > > > > > > I have passed this on to my manager (this does not make > > > sense) since we > > > have the released driver/source. > > > > I need to know if it should compile with 5.2.1. > > > > > > > > I just shot the email and wait to here back. > > > > > > > > Best Regards, > > > > > > > > Victor Pacheco > > > > Technical Support Engineer > > > > > > And here is the error I emailed him. I followed the > > > instructions from the > > > manual, which were slightly outdated. Like it says > > > "twa_opt.h" instead of > > > "opt_twa.h" - but I did everything I could to compile this far. > > > > > > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > > > Makefile > > > > twa.c > > > > twa.h > > > > twa_cam.c > > > > twa_externs.h > > > > twa_freebsd.c > > > > twa_fwimg.c > > > > twa_globals.c > > > > twa_includes.h > > > > twa_ioctl.h > > > > twa_reg.h > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > > > TWA_DEBUG opt_twa.h > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > > > dev/twa/twa.c optional twa > > > > dev/twa/twa_cam.c optional twa > > > > dev/twa/twa_freebsd.c optional twa > > > > dev/twa/twa_fwimg.c optional twa > > > > dev/twa/twa_globals.c optional twa > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > > > device twa # 3ware ATA RAID > > > > > > > > i get an error trying to compile it. if i keep the > > > TWA_DEBUG out of the > > > > options file, when i try to "make depend" it says > > > "opt_twa.h not found" > > > - > > > > even though i don't want debugging. so i have to put = > that in and it > > > shuts > > > > up. > > > > > > > > here's the error: > > > > > > > > [root@raid01 conf]# config RAID01 > > > > Kernel build directory is ../compile/RAID01 > > > > Don't forget to do a ``make depend'' > > > > [root@raid01 conf]# cd ../compile/RAID01 > > > > [root@raid01 RAID01]# make depend > > > > rm -f .olddep > > > > if [ -f .depend ]; then mv .depend .olddep; fi > > > > make _kernel-depend > > > > if [ -f .olddep ]; then mv .olddep .depend; fi > > > > rm -f .newdep > > > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > > > MKDEP_CPP=3D"cc -E" CC=3D"cc" xargs mkdep -a -f .newdep -O = > -pipe -Wall > > > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > > > -fformat-extensions -std=3Dc99 -nostdinc -I- -I. -I../../.. > > > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > -I../../../contrib/ngatm -D_KERNEL -include = > opt_global.h -fno-common > > > > -finline-limit=3D20000 -fno-strict-aliasing -mcmodel=3Dkernel > > > -mno-red-zone > > > > -mfpmath=3D387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow = > -msoft-float > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > make -V SFILES | MKDEP_CPP=3D"cc -E" xargs mkdep -a -f .newdep -x > > > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > > -Wpointer-arith > > > > -Winline -Wcast-qual -fformat-extensions -std=3Dc99 > > > -nostdinc -I- -I. > > > > -I../../.. -I../../../contrib/dev/acpica = > -I../../../contrib/ipfilter > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > -I../../../contrib/ngatm -D_KERNEL -include = > opt_global.h -fno-common > > > > -finline-limit=3D20000 -fno-strict-aliasing -mcmodel=3Dkernel > > > -mno-red-zone > > > > -mfpmath=3D387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow = > -msoft-float > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > rm -f .depend > > > > mv .newdep .depend > > > > [root@raid01 RAID01]# make > > > > linking kernel > > > > twa_cam.o: In function `twa_cam_setup': > > > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > > > twa_cam.o(.text+0xe8): undefined reference to = > `xpt_bus_deregister' > > > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > > > twa_cam.o: In function `twa_cam_detach': > > > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > > > twa_cam.o(.text+0x191): undefined reference to = > `xpt_bus_deregister' > > > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > > > twa_cam.o: In function `twa_execute_scsi': > > > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_action': > > > > twa_cam.o(.text+0x58f): undefined reference to = > `cam_calc_geometry' > > > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_request_bus_scan': > > > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > > > twa_cam.o: In function `twa_bus_scan_cb': > > > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > > > twa_cam.o: In function `twa_scsi_complete': > > > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_drain_busy_queue': > > > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > > > twa_cam.o: In function `twa_disallow_new_requests': > > > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > > > *** Error code 1 > > > > > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > > > > > > > > > > > > > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > > > > > > > > Any word on work on a amd64-compatible driver? (mike seemed > > > to indicate that a > > > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped > > > from -CURRENT > > > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > > > -=3D- > > > > > > > > If there is something I can hack in to twe_freebsd.c to get > > > it to compile > > > > under 5.2.1, I am all ears. > > > > > > > > > > I myself would love this. I'd pay $250 cash to expedite this > > > fix. Someone > > > could work directly with someone at 3ware and get 9500 matured, at > > > least... I wonder if I tried -current if my 9500 would work > > > better. Is it > > > still based off the 7xxx series driver though? > > > > > > At this point I've got hardware and software can't handle it. > > > It's sort of > > > discouraging, usually it's the opposite. I might pay up = > to $500 to get > > > this going. It's worth it that much to get this damn thing > > > fixed so I can > > > send this box back east and get it into production =3D) > > > > > > > > > > > > > -Peter > > > > -- > > > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits > > > must flow" > > > > > > > > > > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to = > "freebsd-amd64-unsubscribe@freebsd.org" > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 14:14:55 2004 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 2284F16A4CE for ; Wed, 23 Jun 2004 14:14:55 +0000 (GMT) Received: from main.dca.nnov.ru (altex-nevsk.mts-nn.ru [213.177.120.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF6DD43D2D for ; Wed, 23 Jun 2004 14:14:53 +0000 (GMT) (envelope-from olegn@main.dca.nnov.ru) Received: from main.dca.nnov.ru (localhost.dca.local [127.0.0.1]) by main.dca.nnov.ru (8.12.10/8.12.10) with ESMTP id i5NEEL0H039637 for ; Wed, 23 Jun 2004 18:14:21 +0400 (MSD) (envelope-from olegn@main.dca.nnov.ru) Received: (from olegn@localhost) by main.dca.nnov.ru (8.12.10/8.12.10/Submit) id i5NEELsF039636 for freebsd-hardware@freebsd.org; Wed, 23 Jun 2004 18:14:21 +0400 (MSD) (envelope-from olegn) Date: Wed, 23 Jun 2004 18:14:21 +0400 (MSD) From: Oleg Nezvanov Message-Id: <200406231414.i5NEELsF039636@main.dca.nnov.ru> To: freebsd-hardware@freebsd.org Subject: FreeBSD-4.9-RELEASE dont work network card 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, 23 Jun 2004 14:14:55 -0000 Hello, I am trying to setup FreeBSD 4.9-RELEASE on a PC, which is equipped with * ASUS P4S533-MX/LAN Socket 478 SIS651 mATX - matherboard * COMPEX RE 100TX/WOL (RealTek RTL8139) - network card Booting from CDROM and kernel says something like ---- skip --- sis0: at device 4.0 on pci0 sis0: couldn`t map ports/memory device_probe_and_atach: sis0 attach returned 6 ---- skip --- rl0: at device 15.0 on pci0 rl0: couldn`t map ports/memory device_probe_and_atach: rl0 attach returned 6 ---- skip --- How can I solve this one? Oleg Nezvanov From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 14:23:23 2004 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 2C9BA16A4CE for ; Wed, 23 Jun 2004 14:23:23 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93CB043D64 for ; Wed, 23 Jun 2004 14:23:22 +0000 (GMT) (envelope-from david.gurvich@verizon.net) Received: from verizon.net ([68.160.241.159]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040623142317.CEWZ1464.out001.verizon.net@verizon.net>; Wed, 23 Jun 2004 09:23:17 -0500 Date: Wed, 23 Jun 2004 10:23:16 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) To: Oleg Nezvanov From: David Gurvich In-Reply-To: <200406231414.i5NEELsF039636@main.dca.nnov.ru> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.553) X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.160.241.159] at Wed, 23 Jun 2004 09:23:16 -0500 cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD-4.9-RELEASE dont work network card 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, 23 Jun 2004 14:23:23 -0000 Adjust settings in bios, change to OS PnP ->disabled. On Wednesday, June 23, 2004, at 10:14 AM, Oleg Nezvanov wrote: > > Hello, > > I am trying to setup FreeBSD 4.9-RELEASE on a PC, which is equipped > with > > * ASUS P4S533-MX/LAN Socket 478 SIS651 mATX - matherboard > * COMPEX RE 100TX/WOL (RealTek RTL8139) - network card > > Booting from CDROM and kernel says something like > > ---- skip --- > sis0: at device 4.0 on pci0 > sis0: couldn`t map ports/memory > device_probe_and_atach: sis0 attach returned 6 > ---- skip --- > rl0: at device 15.0 on pci0 > rl0: couldn`t map ports/memory > device_probe_and_atach: rl0 attach returned 6 > ---- skip --- > > How can I solve this one? > > Oleg Nezvanov > > _______________________________________________ > 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 Wed Jun 23 15:32:32 2004 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 5DB6D16A4CF; Wed, 23 Jun 2004 15:32:32 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF33A43D48; Wed, 23 Jun 2004 15:32:31 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id EA3FA1C1AE; Wed, 23 Jun 2004 08:32:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id E78311C0F6; Wed, 23 Jun 2004 08:32:30 -0700 (PDT) Date: Wed, 23 Jun 2004 08:32:30 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Vinod Kashyap In-Reply-To: Message-ID: References: mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... 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, 23 Jun 2004 15:32:32 -0000 Well it did "build" fine - now the problem is that anytime I try to mount any of the partitions I've made it freezes the process up. Can't even control-C or control-Z or kill -9 it. It never goes away until I reboot. (not to mention trying to partition > 1tb is messed up using standinstall, so I tried making smaller partitions just to see if I could use the array without things like this happening) On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > > > The AMD64/64 bit support I was told would work in FreeBSD; not in the > > email below but by two different techs over the phone and nobody has > > called that as the reason for my troubles. > > > > Are you telling me that the GENERIC twa should work fine for the 9500 > > series of 3ware controllers? Careful, apparently this > > controller is only a > > month old. > > > I am telling you it should "build" fine since I haven't heard of build > problems during the nightly builds of the FreeBSD cvs repository. > > > > > On Tue, 22 Jun 2004, Vinod Kashyap wrote: > > > > > > > > I can't speak for Victor, but I did talk to him this afternoon, > > > and he (and other support people) couldn't recall telling anyone > > > that 3ware supports FreeBSD amd64. There might have been > > some miscommunication/misunderstandings since 3ware does support amd64 > > > on Linux and Windows. Even in the thread below, I don't see > > > him mention FreeBSD amd64. Of course, the problem you had was > > > on amd64, and I don't know if he realized it. The "different OS > > > versions" probably refers to 4.x and 5.x. > > > > > > Anyways, I am sorry about any miscommunications, but as far as my > > > knowledge goes, there's not even been a FreeBSD amd64 version of the > > > driver built here, let alone tested. As about future plans, it > > > might happen if there's sufficient interest, but at this point, > > > there's none. > > > > > > Also, I wonder why you ran into build problems! twa has been > > > in /sys/amd64/conf/GENERIC for sometime now, and no build problems > > > have been reported so far. > > > > > > > > > > -----Original Message----- > > > > From: mike [mailto:mike@mike2k.com] > > > > Sent: Tuesday, June 22, 2004 6:35 PM > > > > To: Peter Losher > > > > Cc: Vinod Kashyap; freebsd-amd64@freebsd.org; > > > > freebsd-hardware@freebsd.org > > > > Subject: [freebsd-amd64] [freebsd-amd64] Re: [freebsd-amd64] Re: > > [freebsd-amd64] Possible > > > > 3ware 8506-12 > > > > SATA Controller issues... > > > > > > > > > > > > Here is the last response I received from Victor: > > > > > > > > On Wed, 16 Jun 2004, Victor Pacheco wrote: > > > > > > > > > Hi, Mike > > > > > > > > > > > > > > > I am told by our engineer 5.2.1 is not supported nor we support > > > > recompiling against newer kernels. He wrote: > > > > > "FreeBSD is unlike Linux in that you can't use driver > > > > source to compile > > > > a driver for different OS versions. > > > > Customers must have the compiled version of the driver for > > > > their except > > > > FreeBSD version or it will not work. > > > > > Also, it was my understanding that the 9500S series does > > > > not yet support > > > > FreeBSD. The driver is not on the > > > > shipping CD or the web." > > > > > > > > > > I have passed this on to my manager (this does not make > > > > sense) since we > > > > have the released driver/source. > > > > > I need to know if it should compile with 5.2.1. > > > > > > > > > > I just shot the email and wait to here back. > > > > > > > > > > Best Regards, > > > > > > > > > > Victor Pacheco > > > > > Technical Support Engineer > > > > > > > > And here is the error I emailed him. I followed the > > > > instructions from the > > > > manual, which were slightly outdated. Like it says > > > > "twa_opt.h" instead of > > > > "opt_twa.h" - but I did everything I could to compile this far. > > > > > > > > > [root@raid01 twa]# ls -1 /usr/src/sys/dev/twa > > > > > Makefile > > > > > twa.c > > > > > twa.h > > > > > twa_cam.c > > > > > twa_externs.h > > > > > twa_freebsd.c > > > > > twa_fwimg.c > > > > > twa_globals.c > > > > > twa_includes.h > > > > > twa_ioctl.h > > > > > twa_reg.h > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/options > > > > > TWA_DEBUG opt_twa.h > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/conf/files.amd64 > > > > > dev/twa/twa.c optional twa > > > > > dev/twa/twa_cam.c optional twa > > > > > dev/twa/twa_freebsd.c optional twa > > > > > dev/twa/twa_fwimg.c optional twa > > > > > dev/twa/twa_globals.c optional twa > > > > > > > > > > [root@raid01 twa]# grep twa /usr/src/sys/amd64/conf/RAID01 > > > > > device twa # 3ware ATA RAID > > > > > > > > > > i get an error trying to compile it. if i keep the > > > > TWA_DEBUG out of the > > > > > options file, when i try to "make depend" it says > > > > "opt_twa.h not found" > > > > - > > > > > even though i don't want debugging. so i have to put > > that in and it > > > > shuts > > > > > up. > > > > > > > > > > here's the error: > > > > > > > > > > [root@raid01 conf]# config RAID01 > > > > > Kernel build directory is ../compile/RAID01 > > > > > Don't forget to do a ``make depend'' > > > > > [root@raid01 conf]# cd ../compile/RAID01 > > > > > [root@raid01 RAID01]# make depend > > > > > rm -f .olddep > > > > > if [ -f .depend ]; then mv .depend .olddep; fi > > > > > make _kernel-depend > > > > > if [ -f .olddep ]; then mv .olddep .depend; fi > > > > > rm -f .newdep > > > > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | > > > > > MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O > > -pipe -Wall > > > > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > > > > -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > > > > > -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > > -I../../../contrib/ngatm -D_KERNEL -include > > opt_global.h -fno-common > > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > -mno-red-zone > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow > > -msoft-float > > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x > > > > > assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls > > > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > > > -Wpointer-arith > > > > > -Winline -Wcast-qual -fformat-extensions -std=c99 > > > > -nostdinc -I- -I. > > > > > -I../../.. -I../../../contrib/dev/acpica > > -I../../../contrib/ipfilter > > > > > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > > > > > -I../../../contrib/ngatm -D_KERNEL -include > > opt_global.h -fno-common > > > > > -finline-limit=20000 -fno-strict-aliasing -mcmodel=kernel > > > > -mno-red-zone > > > > > -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow > > -msoft-float > > > > > -fno-asynchronous-unwind-tables -ffreestanding > > > > > rm -f .depend > > > > > mv .newdep .depend > > > > > [root@raid01 RAID01]# make > > > > > linking kernel > > > > > twa_cam.o: In function `twa_cam_setup': > > > > > twa_cam.o(.text+0x12): undefined reference to `cam_simq_alloc' > > > > > twa_cam.o(.text+0x58): undefined reference to `cam_sim_alloc' > > > > > twa_cam.o(.text+0x70): undefined reference to `cam_simq_free' > > > > > twa_cam.o(.text+0x8d): undefined reference to `xpt_bus_register' > > > > > twa_cam.o(.text+0xa2): undefined reference to `cam_sim_free' > > > > > twa_cam.o(.text+0xd4): undefined reference to `xpt_create_path' > > > > > twa_cam.o(.text+0xe8): undefined reference to > > `xpt_bus_deregister' > > > > > twa_cam.o(.text+0xf9): undefined reference to `cam_sim_free' > > > > > twa_cam.o(.text+0x114): undefined reference to `xpt_setup_ccb' > > > > > twa_cam.o(.text+0x143): undefined reference to `xpt_action' > > > > > twa_cam.o: In function `twa_cam_detach': > > > > > twa_cam.o(.text+0x176): undefined reference to `xpt_free_path' > > > > > twa_cam.o(.text+0x191): undefined reference to > > `xpt_bus_deregister' > > > > > twa_cam.o(.text+0x1a2): undefined reference to `cam_sim_free' > > > > > twa_cam.o: In function `twa_execute_scsi': > > > > > twa_cam.o(.text+0x408): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_action': > > > > > twa_cam.o(.text+0x58f): undefined reference to > > `cam_calc_geometry' > > > > > twa_cam.o(.text+0x650): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_request_bus_scan': > > > > > twa_cam.o(.text+0x6b9): undefined reference to `xpt_periph' > > > > > twa_cam.o(.text+0x6ca): undefined reference to `xpt_create_path' > > > > > twa_cam.o(.text+0x6e0): undefined reference to `xpt_setup_ccb' > > > > > twa_cam.o(.text+0x701): undefined reference to `xpt_action' > > > > > twa_cam.o: In function `twa_bus_scan_cb': > > > > > twa_cam.o(.text+0x730): undefined reference to `xpt_free_path' > > > > > twa_cam.o: In function `twa_scsi_complete': > > > > > twa_cam.o(.text+0x87b): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_drain_busy_queue': > > > > > twa_cam.o(.text+0x8d9): undefined reference to `xpt_done' > > > > > twa_cam.o: In function `twa_disallow_new_requests': > > > > > twa_cam.o(.text+0x951): undefined reference to `xpt_freeze_simq' > > > > > *** Error code 1 > > > > > > > > > > Stop in /usr/src/sys/amd64/compile/RAID01. > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 22 Jun 2004, Peter Losher wrote: > > > > > > > > > > > > > > Any word on work on a amd64-compatible driver? (mike seemed > > > > to indicate that a > > > > > amd64 driver for the 9xxx series might come later this summer?) > > > > > > > > > > > > > > > Tried compiling a 5.2.1 kernel w/ the twe driver plopped > > > > from -CURRENT > > > > > cvsup'ed 30 minutes ago, and it didn't go to well: > > > > > > > > > > -=- > > > > > > > > > > If there is something I can hack in to twe_freebsd.c to get > > > > it to compile > > > > > under 5.2.1, I am all ears. > > > > > > > > > > > > > I myself would love this. I'd pay $250 cash to expedite this > > > > fix. Someone > > > > could work directly with someone at 3ware and get 9500 matured, at > > > > least... I wonder if I tried -current if my 9500 would work > > > > better. Is it > > > > still based off the 7xxx series driver though? > > > > > > > > At this point I've got hardware and software can't handle it. > > > > It's sort of > > > > discouraging, usually it's the opposite. I might pay up > > to $500 to get > > > > this going. It's worth it that much to get this damn thing > > > > fixed so I can > > > > send this box back east and get it into production =) > > > > > > > > > > > > > > > > > -Peter > > > > > -- > > > > > Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits > > > > must flow" > > > > > > > > > > > > > > > _______________________________________________ > > > freebsd-amd64@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > > To unsubscribe, send any mail to > > "freebsd-amd64-unsubscribe@freebsd.org" > > > > > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 15:38:43 2004 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 A141D16A4CE for ; Wed, 23 Jun 2004 15:38:43 +0000 (GMT) Received: from typhoon.he.net (typhoon.he.net [64.62.229.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 751F043D1D for ; Wed, 23 Jun 2004 15:38:43 +0000 (GMT) (envelope-from bill@wiliweld.com) Received: from bsd.billschoolcraft.com ([63.204.157.14]) by typhoon.he.net for ; Wed, 23 Jun 2004 08:38:39 -0700 Date: Wed, 23 Jun 2004 08:38:40 -0700 (PDT) From: Bill Schoolcraft X-X-Sender: bill@bsd.billschoolcraft.com To: FreeBSD Message-ID: <20040623081354.D13804@bsd.billschoolcraft.com> System-ID: [en] (I; FreeBSD 5.2.1-RELEASE #0 x86) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: (5.2.1) No mouse on Dell Inspiron 5150, XP and Linux ok. 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, 23 Jun 2004 15:38:43 -0000 Hello Family, I have a new Dell Inspiron 5150 and it's a company issue and I immediately took it and triple booted it with Linux and FreeBSD-5.2.1 and the default XP. I had to download the Nvidia drivers for both Linux and FreeBSD and the X displays are GREAT except for one thing. Linux has a mouse in X FreeBSD has no mouse PERIOD. It is not detected in "sysinstall" and when I fire up X the mouse cursor stays frozen in the middle of the screen. I did notice that there was NO /dev/psm* and was wondering if there is any way of fixing this. The ridicule from the Linux folks at work is getting a bit old. :( Thanks for any consideration in helping me with this. -- Bill Schoolcraft PO Box 210076 San Francisco CA 94121 http://billschoolcraft.com From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 17:25:43 2004 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 0475116A4CE; Wed, 23 Jun 2004 17:25:43 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9624443D39; Wed, 23 Jun 2004 17:25:41 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZRV2S01.Y7V; Wed, 23 Jun 2004 10:25:40 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062310254402545 ; Wed, 23 Jun 2004 10:25:44 -0700 From: "Vinod Kashyap" To: obrien@freebsd.org Date: Wed, 23 Jun 2004 10:25:39 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: mike cc: Peter Losher cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 17:25:43 -0000 > = > On Tue, Jun 22, 2004 at 05:16:30PM -0700, Vinod Kashyap wrote: > > > From: David O'Brien [mailto:obrien@freebsd.org] > > > Vinod, > > > As the FreeBSD 3Ware driver maintainer can you address = > these driver > > > concerns on AMD64 hardware [in 64-bit mode]? > ... > > The official support on FreeBSD for 7xxx, 8xxx and 9xxx series > > controllers is only for i386. Although the driver might work > > on other platforms, it's never been tested. The FreeBSD management > > tools provided by 3ware are only for i386. > = > As twe(4) maintainer, what would it take for you to test the = > drivers on > FreeBSD/AMD64 (in 64-bit mode)? > = Officially supporting a platform will need the driver to go through a thorough QA process, and therefore need QA resources (not me). Also, there has to be this... ROI... :-) All in all, it's not my call! > -- = > -- David (obrien@FreeBSD.org) > From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 18:32:19 2004 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 84D5716A4CE; Wed, 23 Jun 2004 18:32:19 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB9543D48; Wed, 23 Jun 2004 18:32:19 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id C46405C7F8; Wed, 23 Jun 2004 11:31:46 -0700 (PDT) Date: Wed, 23 Jun 2004 11:31:46 -0700 From: Paul Saab To: Vinod Kashyap Message-ID: <20040623183146.GA8624@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org cc: mike cc: Peter Losher cc: obrien@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 18:32:19 -0000 Vinod Kashyap (vkashyap@amcc.com) wrote: > Officially supporting a platform will need the driver to go through > a thorough QA process, and therefore need QA resources (not me). Also, > there has to be this... ROI... :-) All in all, it's not my call! Then you wont complain when I make it work and commit the changes because we're a multi-platform environment and want the drivers to work on as much of the hardware as possible. People are not asking for official support of all the architectures, but they want to know that the driver will atleast work for them. 3ware just doesn't seem to understand the project at all. From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 18:45:55 2004 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 EC6DF16A4CE; Wed, 23 Jun 2004 18:45:55 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C3C643D2F; Wed, 23 Jun 2004 18:45:55 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id HZRYR000.J7Y; Wed, 23 Jun 2004 11:45:00 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004062311450405148 ; Wed, 23 Jun 2004 11:45:04 -0700 From: "Vinod Kashyap" To: Paul Saab Date: Wed, 23 Jun 2004 11:44:59 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-amd64@freebsd.org cc: mike cc: Peter Losher cc: obrien@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 18:45:56 -0000 > = > Vinod Kashyap (vkashyap@amcc.com) wrote: > > Officially supporting a platform will need the driver to go through > > a thorough QA process, and therefore need QA resources (not = > me). Also, > > there has to be this... ROI... :-) All in all, it's not my call! > = > Then you wont complain when I make it work and commit the = > changes because > we're a multi-platform environment and want the drivers to work on as > much of the hardware as possible. People are not asking for official > support of all the architectures, but they want to know that = > the driver > will atleast work for them. 3ware just doesn't seem to understand the > project at all. > = How do you make sure that it will at least work? By testing it, right? And you cannot do a half-a** testing since people can run into problems and you can be inundated with calls. So, thorough testing will need to be done, and it will take resources. A company will be ready to allocate resources only if there's ROI. That's reality! If you want to make it work on amd64, by all means, go ahead! From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 23 20:42:15 2004 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 78CBF16A4CE; Wed, 23 Jun 2004 20:42:15 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B1FF43D2D; Wed, 23 Jun 2004 20:42:15 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id 2B05B5C7DE; Wed, 23 Jun 2004 13:42:04 -0700 (PDT) Date: Wed, 23 Jun 2004 13:42:04 -0700 From: Paul Saab To: Vinod Kashyap Message-ID: <20040623204204.GA17825@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... 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, 23 Jun 2004 20:42:15 -0000 Vinod Kashyap (vkashyap@amcc.com) wrote: > How do you make sure that it will at least work? By testing it, right? > And you cannot do a half-a** testing since people can run into problems > and you can be inundated with calls. So, thorough testing will need to > be done, and it will take resources. A company will be ready to allocate > resources only if there's ROI. That's reality! > > If you want to make it work on amd64, by all means, go ahead! And then there are companies who work with the community to make the drivers and cards work well on all platforms regardless of ROI because there's a commitment to the project as a whole. I'm sure all the amd64 issues are very minor and will only require a small amount of changes, because that's the way things work. Sometimes you need to make a little investment in things to make the ROI actually happen. From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 24 04:59:00 2004 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 5140516A4CE; Thu, 24 Jun 2004 04:59:00 +0000 (GMT) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D46743D1D; Thu, 24 Jun 2004 04:59:00 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from dhcp-7.sql1.plosh.net (c-24-4-233-31.client.comcast.net [24.4.233.31]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 09F75A82B; Thu, 24 Jun 2004 04:58:43 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: "Vinod Kashyap" Date: Wed, 23 Jun 2004 21:58:41 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_C+l2A/+mNYXHp4d"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406232158.42167.Peter_Losher@isc.org> cc: mike cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Possible 3ware 8506-12 SATA Controller issues... 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, 24 Jun 2004 04:59:00 -0000 --Boundary-02=_C+l2A/+mNYXHp4d Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 22 June 2004 07:56 pm, Vinod Kashyap wrote: > I'm sorry I forgot to answer that. There are some recent changes > in -CURRENT's twe, which I wanted you to try. =20 An update: Thanks to Paul Saab, I have a -CURRENT twe driver that=20 compiles under 5.2.1. It compiled, and runs fine. However, like=20 before, the system still locks up hard under heavy I/O load. In this=20 case, copying a deep directory tree using thousands of inodes, and=20 removing a similar tree at the same time. Any ideas? Mike - have you had any success in stressing your 9000 series=20 card? =2DPeter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" --Boundary-02=_C+l2A/+mNYXHp4d Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA2l+CPtVx9OgEjQgRAohwAJ0cw0ENIZK+ycrcEG0szMAJBg8pNQCgiqJA u0mlfyko8ywuKwgwLxe1F5o= =AfTw -----END PGP SIGNATURE----- --Boundary-02=_C+l2A/+mNYXHp4d-- From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 24 09:27:29 2004 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 2255716A4CE; Thu, 24 Jun 2004 09:27:29 +0000 (GMT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7E0A43D53; Thu, 24 Jun 2004 09:27:28 +0000 (GMT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 4C0EC1C2A0; Wed, 23 Jun 2004 23:04:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 4AB5E1C1BA; Wed, 23 Jun 2004 23:04:14 -0700 (PDT) Date: Wed, 23 Jun 2004 23:04:14 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: Peter Losher In-Reply-To: <200406232158.42167.Peter_Losher@isc.org> Message-ID: References: <200406232158.42167.Peter_Losher@isc.org> mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: Possible 3ware 8506-12 SATA Controller issues... 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, 24 Jun 2004 09:27:29 -0000 I switched to debian-amd64 today. Better utils compatibility and poor faith this will be resolved ASAP was the main decision. It sounds like Paul will help out get the 8xxx series rolling, but I wasn't sure if he'd have time or ability to make sure the 9xxx series ran. I had a minor kernel tweak in linux 2.6.7 (newest kernel) but the 2.6 kernel driver sources worked fine. Much easier than trying to get the FreeBSD ones to work under 5.2.1-RELEASE AMD64. Even when I did get it to "compile" into the fbsd kernel, it seemed like any time I wanted to do anything with it - newfs, try mounting, etc, it would lock up. On Wed, 23 Jun 2004, Peter Losher wrote: > On Tuesday 22 June 2004 07:56 pm, Vinod Kashyap wrote: > > > I'm sorry I forgot to answer that. There are some recent changes > > in -CURRENT's twe, which I wanted you to try. > > An update: Thanks to Paul Saab, I have a -CURRENT twe driver that > compiles under 5.2.1. It compiled, and runs fine. However, like > before, the system still locks up hard under heavy I/O load. In this > case, copying a deep directory tree using thousands of inodes, and > removing a similar tree at the same time. > > Any ideas? Mike - have you had any success in stressing your 9000 series > card? > > -Peter > -- > Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" > From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 24 14:02:50 2004 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 9FA4816A4CE for ; Thu, 24 Jun 2004 14:02:50 +0000 (GMT) Received: from fulcrum.mig-29.net (dsl-200-78-45-190.prod-infinitum.com.mx [200.78.45.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF9A143D1F for ; Thu, 24 Jun 2004 14:02:47 +0000 (GMT) (envelope-from mig@mig-29.net) Received: by fulcrum.mig-29.net (Postfix, from userid 1000) id 6ED3633C48; Thu, 24 Jun 2004 09:01:52 -0500 (CDT) Date: Thu, 24 Jun 2004 09:01:52 -0500 From: Manuel Rabade Garcia To: hardware@freebsd.org Message-ID: <20040624140152.GA894@mig-29.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.6i Subject: Sony DSC P73 and umass failed (CBI reset failed, STALLED) 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, 24 Jun 2004 14:02:50 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi everyone, i buy a Sony DSC P73 Digital Camera wich supports USB Normal mode (as a 'standard' storage device), PTP mode and Picture Bridge (for other Sony devices i think). I use FreeBSD 5.2.1 (see dmesg above) and when i connect it the umass fails to detect the storage device and kernel says: umass0: Sony Sony DSC, rev 2.00/5.00, addr 2 umass0: CBI reset failed, STALLED umass0: CBI reset failed, STALLED umass0: CBI reset failed, STALLED umass0: CBI reset failed, STALLED umass0: CBI reset failed, STALLED The output of 'usbdevs -v' is: mig@fulcrum:~$ usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: low speed, power 100 mA, config 1, Microsoft Trackball Explorer®(0x0024), Microsoft(0x045e), rev 1.21 port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, self powered, config 1, Sony DSC(0x0010), Sony(0x054c), rev 5.00 port 2 powered I wan to send a pr but i don't know what other information could be useful (the dmesg and usbdevs i think are not enough), i am very interested in coperating to get it working :). Thanks to everyone and keep up the good work :) -- Manuel Rabade Garcia WWW - http://mig-29.net GPG - 1024D/AA3325C0 2002-09-30 Fingerprint - D2E5 76E1 CE2D 8783 545D 1F41 399B 5765 AA33 25C0 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename="dmesg.txt" Content-Transfer-Encoding: 8bit Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE-p5 #0: Tue Apr 20 13:36:34 CDT 2004 root@:/usr/obj/usr/src/sys/FULCRUM Preloaded elf kernel "/boot/kernel/kernel" at 0xc0b4e000. Preloaded elf module "/boot/modules/linux.ko" at 0xc0b4e1cc. Preloaded acpi_dsdt "/boot/acpi_dsdt.aml" at 0xc0b4e278. Preloaded elf module "/boot/modules/nvidia.ko" at 0xc0b4e2c0. Preloaded elf module "/boot/modules/acpi.ko" at 0xc0b4e36c. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz (1993.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebf9ff real memory = 536748032 (511 MB) avail memory = 511143936 (487 MB) netsmb_dev: loaded Pentium Pro MTRR support enabled VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc0877782 (1000022) VESA: NVidia ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00fbb90 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_tz0: port 0x530-0x537 on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTC is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 nvidia0: mem 0xdff80000-0xdfffffff,0xe0000000-0xe7ffffff,0xfc000000-0xfcffffff irq 11 at device 0.0 on pci1 uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft Trackball Explorer®, rev 1.10/1.21, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. uhci1: port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 pcib2: slot 0 INTA is routed to irq 11 pcib2: slot 1 INTA is routed to irq 11 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2 xl0: Ethernet address: 00:08:74:e5:9e:ba miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cbb0: at device 1.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib2: slot 1 INTA is routed to irq 11 cbb0: [MPSAFE] cbb1: at device 1.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib2: slot 1 INTA is routed to irq 11 cbb1: [MPSAFE] fwohci0: mem 0xf8ff8000-0xf8ffbfff,0xf8fff000-0xf8fff7ff irq 11 at device 1.2 on pci2 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 32:4f:c0:00:08:40:d8:41 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 32:4f:c0:40:d8:41 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xbfa0-0xbfaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 speaker0 port 0x67,0x65,0x63,0x61 on acpi0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x280-0x287,0x2f8-0x2ff irq 3 drq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: