From owner-freebsd-amd64@FreeBSD.ORG Sun Jun 20 10:01:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5C5A16A4CE; Sun, 20 Jun 2004 10:01:07 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A73743D5A; Sun, 20 Jun 2004 10:01:07 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i5KA10ck009892; Sun, 20 Jun 2004 06:01:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id i5KA106H012434; Sun, 20 Jun 2004 06:01:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id AC8747306D; Sun, 20 Jun 2004 06:00:59 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040620100059.AC8747306D@freebsd-current.sentex.ca> Date: Sun, 20 Jun 2004 06:00:59 -0400 (EDT) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 10:01:08 -0000 TB --- 2004-06-20 09:41:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-06-20 09:41:25 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-06-20 09:41:25 - checking out the source tree TB --- 2004-06-20 09:41:25 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- 2004-06-20 09:41:25 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-06-20 09:46:06 - building world (CFLAGS=-O2 -pipe) TB --- 2004-06-20 09:46:06 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- 2004-06-20 09:46:06 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_finite.c -o s_finite.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_finitef.c -o s_finitef.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_floor.c -o s_floor.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_floorf.c -o s_floorf.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_frexp.c -o s_frexp.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_frexpf.c -o s_frexpf.So cc -fpic -DPIC -O2 -pipe -D_IEEE_LIBM -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/msun/../libc/amd64 -c /tinderbox/CURRENT/amd64/amd64/src/lib/msun/src/s_ilogb.c -o s_ilogb.So cccc: in free(): error: junk pointer, too high to make sense *** Signal 6 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/msun. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-06-20 10:00:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-06-20 10:00:59 - ERROR: failed to build world TB --- 2004-06-20 10:00:59 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 11:02:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9039116A4CF for ; Mon, 21 Jun 2004 11:02:02 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A95D43D31 for ; Mon, 21 Jun 2004 11:02:02 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i5LB1sh1064602 for ; Mon, 21 Jun 2004 11:01:54 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5LB1rVZ064596 for freebsd-amd64@freebsd.org; Mon, 21 Jun 2004 11:01:53 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 21 Jun 2004 11:01:53 GMT Message-Id: <200406211101.i5LB1rVZ064596@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 11:02:02 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64 Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9057916A4CE; Mon, 21 Jun 2004 11:03:50 +0000 (GMT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 311F743D41; Mon, 21 Jun 2004 11:03:50 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smtp3.sentex.ca (8.12.11/8.12.11) with ESMTP id i5LB3VRb045928; Mon, 21 Jun 2004 07:03:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id i5LB3WKA024187; Mon, 21 Jun 2004 07:03:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 73BDB7306D; Mon, 21 Jun 2004 07:03:32 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040621110332.73BDB7306D@freebsd-current.sentex.ca> Date: Mon, 21 Jun 2004 07:03:32 -0400 (EDT) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 11:03:51 -0000 TB --- 2004-06-21 09:35:33 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-06-21 09:35:33 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-06-21 09:35:33 - checking out the source tree TB --- 2004-06-21 09:35:33 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- 2004-06-21 09:35:33 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-06-21 09:40:22 - building world (CFLAGS=-O2 -pipe) TB --- 2004-06-21 09:40:22 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- 2004-06-21 09:40:22 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ln -sf /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/gen-doc.texi configdoc.texi makeinfo --no-validate -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/mi -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc --no-split -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo -o ld.info gzip -cn ld.info > ld.info.gz makeinfo --no-validate -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/mi -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc --no-split -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc -I /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/gasp.texi -o gasp.i nfo gzip -cn gasp.info > gasp.info.gz ln -sf /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/all-cfg.texi gdb-cfg.texi echo "@set GDBVN `sed q /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/version.in`" > GDBvn.texi make: don't know how to make annotate.texi. Stop *** Error code 2 Stop in /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/gnu/usr.bin. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/gnu. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-06-21 11:03:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-06-21 11:03:32 - ERROR: failed to build world TB --- 2004-06-21 11:03:32 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:19:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10FF116A4D2 for ; Mon, 21 Jun 2004 15:19:15 +0000 (GMT) Received: from lyris2.strategicprayer.net (lyris2.strategicprayer.net [65.206.160.125]) by mx1.FreeBSD.org (Postfix) with SMTP id B69B143D1F for ; Mon, 21 Jun 2004 15:19:14 +0000 (GMT) (envelope-from lyris-admin@lyris2.strategicprayer.net) Message-Id: X-lyris-type: action-phrase From: "Lyris ListManager" To: freebsd-amd64@freebsd.org Date: Mon, 21 Jun 2004 09:27:43 -0600 Subject: Your message was rejected! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Lyris ListManager List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 15:19:15 -0000 Due to several viruses being sent to lists, this list server is configured to reject messages with attachments. Your message has been rejected because it contains such an attachment. Please resubmit your message without the attachment. Thank you. From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 07:57:56 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Tue Jun 22 08:39:25 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Tue Jun 22 09:03:30 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Tue Jun 22 10:09:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3651516A4CE for ; Tue, 22 Jun 2004 10:09:56 +0000 (GMT) Received: from qeylIS.klingons.de (snake.de [212.102.166.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E0D243D58 for ; Tue, 22 Jun 2004 10:09:55 +0000 (GMT) (envelope-from jekat@qeylIS.klingons.de) Received: from qeylIS.klingons.de (jekat@localhost [127.0.0.1]) i5MA9q0r058480; Tue, 22 Jun 2004 12:09:52 +0200 (CEST) (envelope-from jekat@qeylIS.klingons.de) Received: (from jekat@localhost) by qeylIS.klingons.de (8.12.10/8.12.10/Submit) id i5MA9pQd058479; Tue, 22 Jun 2004 12:09:51 +0200 (CEST) (envelope-from jekat) Date: Tue, 22 Jun 2004 12:09:51 +0200 From: Astrid To: freebsd-amd64@freebsd.org Message-ID: <20040622100951.GV83028@snake.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.41 Subject: loading kernel modules under amd64 fbsd? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 10:09:56 -0000 Greetings, ye amd64 developer gurus! This humble admin hath a question: I searched the ml archives and read that at long last the amd64 fbsd kernel module loader is starting to work... even if there still were dragons as of May 17th. What is the present staus, please? I really need to get the vinum volume manager up and running, especially as raidframe under fbsd more or less is dead... ... could not statically compile vinum support (yes, I know that is not recommended) into an amd64 5.2.1 kernel... Vinum as a kernel module would of course be preferable - is there any prerelease I could try out? Pointers and input would be greatly appreciated. A.Jekat ISP Service AG Munich, Germany From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 14:37:31 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Tue Jun 22 14:39:44 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Re: Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Tue Jun 22 16:13:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A131616A4D0; Tue, 22 Jun 2004 16:13:16 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0DD643D53; Tue, 22 Jun 2004 16:13:15 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id EAFD41F001; Tue, 22 Jun 2004 18:13:01 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id CF3D461DA; Tue, 22 Jun 2004 18:13:01 +0200 (CEST) Date: Tue, 22 Jun 2004 18:13:01 +0200 From: Marc Olzheim To: sos@freebsd.org Message-ID: <20040622161301.GA780@stack.nl> References: <20040504194803.GA94861@stack.nl> <4097F65A.3000709@DeepCore.dk> <20040511165044.GA52478@stack.nl> <20040511190859.GA80652@dragon.nuxi.com> <20040511193404.GA56219@stack.nl> <20040511194308.GB14683@dragon.nuxi.com> <20040511201156.GA57223@stack.nl> <20040511205725.GA57636@stack.nl> <20040512022938.GA23426@dragon.nuxi.com> <20040526190653.GA1508@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040526190653.GA1508@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.2-CURRENT FreeBSD 5.2-CURRENT X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: ATA driver cannot detect the Serial ATA disk in FreeBSD/AMD64-Current X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 16:13:16 -0000 On Wed, May 26, 2004 at 09:06:53PM +0200, Marc Olzheim wrote: > On Tue, May 11, 2004 at 07:29:38PM -0700, David O'Brien wrote: > > On Tue, May 11, 2004 at 10:57:25PM +0200, Marc Olzheim wrote: > > > Alas, to no avail... > > > http://www.stack.nl/~marcolz/FreeBSD/hammer.bootlog.broken.20040511.newbios.txt > > > > :-( > > Anyone with any new ideas to try ? Tried today's kernel to no avail > again... Upgraded my Tyan 2885 to Bios 2.02 but still no SATA in a new kernel... Marc From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 21:38:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC04816A4CE for ; Tue, 22 Jun 2004 21:38:03 +0000 (GMT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7394E43D46 for ; Tue, 22 Jun 2004 21:38:01 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C255BFD03A for ; Tue, 22 Jun 2004 14:38:00 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00704-01 for ; Tue, 22 Jun 2004 14:38:00 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 4F0DCFD006 for ; Tue, 22 Jun 2004 14:38:00 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1087940280.6833.37.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 22 Jun 2004 14:38:00 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: crash in ata_completed with atapicam cd X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 21:38:03 -0000 I'm trying to track down my crash when I try to write a CD, but I'm not familiar with amd64 assembly. It is obviously an attempt to indirectly jump to a routine: ata_completed+0xcc: call *%eax where eax is 0xffffffff801a0fa8 Looking at ata-queue.c and an objdump of ata-queue.o, I see the call but cannot tell where it corresponds to the C code. It looks like there is a return immediately following the indirect call, but I cannot see how it aligns with the source. Returns follow calls to ata_queue_request() and ata_start(). Neither of which I should think would be indirect calls. The only place that looks right is at the end of the function where it calls request->callback(). Can someone give me a hand in trying to interpret the assembly? TIA, Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 23:16:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EA0C16A4CE for ; Tue, 22 Jun 2004 23:16:09 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 204FF43D4C for ; Tue, 22 Jun 2004 23:16:09 +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 i5MNFq3M052267; Tue, 22 Jun 2004 16:15:52 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5MNFp4J052264; Tue, 22 Jun 2004 16:15:51 -0700 (PDT) (envelope-from obrien) Date: Tue, 22 Jun 2004 16:15:51 -0700 From: "David O'Brien" To: Astrid Message-ID: <20040622231551.GB51951@dragon.nuxi.com> References: <20040622100951.GV83028@snake.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040622100951.GV83028@snake.de> 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: freebsd-amd64@freebsd.org Subject: Re: loading kernel modules under amd64 fbsd? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 23:16:09 -0000 On Tue, Jun 22, 2004 at 12:09:51PM +0200, Astrid wrote: > Greetings, ye amd64 developer gurus! > I really need to get the vinum volume manager up and running, > especially as raidframe under fbsd more or less is dead... I went into /sys/modules/vinum and was able to make 'vinum' fine. I've just committed a change building vinum by default on AMD64. Please let me know what your experiences are with it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 23:21:20 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 00:16:34 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 01:11:36 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 01:48:08 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 01:48:08 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 01:48:08 -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-amd64@FreeBSD.ORG Wed Jun 23 02:00:09 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:06:20 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:19:25 2004 Return-Path: Delivered-To: freebsd-amd64@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: 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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:39:22 2004 Return-Path: Delivered-To: freebsd-amd64@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: 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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:39:24 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:39:25 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: Vinod Kashyap Subject: Re: [freebsd-amd64] Re: [freebsd-amd64] Possible 3ware 8506-12SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:41:38 2004 Return-Path: Delivered-To: freebsd-amd64@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 Subject: Re: [freebsd-amd64] RE: [freebsd-amd64] Re: [freebsd-amd64]Possible 3ware 8506-12SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:46:26 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 02:57:30 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 05:15:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 066EA16A4CE for ; Wed, 23 Jun 2004 05:15:18 +0000 (GMT) Received: from bsdhosting.net (bsdhosting.net [65.39.221.113]) by mx1.FreeBSD.org (Postfix) with SMTP id B7E2043D54 for ; Wed, 23 Jun 2004 05:15:17 +0000 (GMT) (envelope-from jhopper@bsdhosting.net) Received: (qmail 83830 invoked from network); 23 Jun 2004 05:14:14 -0000 Received: from unknown (HELO ?192.168.1.6?) (jhopper@bsdhosting.net@65.39.221.113) by bsdhosting.net with SMTP; 23 Jun 2004 05:14:14 -0000 From: Justin Hopper To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1087967700.18067.403.camel@work.gusalmighty.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 22 Jun 2004 22:15:00 -0700 Content-Transfer-Encoding: 7bit Subject: freebsd-amd64 threading issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 05:15:18 -0000 Hello, I haven't seen any further talk about the threading problem running MySQL on freebsd-amd64. Has anyone made any more progress on this? We are due to receive our first Dual or Quad Opteron box here shortly, and I'm concerned I will not be able to run freebsd-amd64, as the box will need all the DB horsepower it can get. Is it an option to run freebsd-i386 on the Opteron hardware? It would be a shame to run i386 on it, but I can't have the MySQL daemon using only 1 CPU. Has anyone tracked down where exactly the problem lies, either in the threading library or perhaps in the way that MySQL is using the library? Is there any other multi-threading applications that somebody could run on freebsd-amd64 to see if it's the threading library that is the problem? I'll be able to run my own tests when the box arrives, but I'll have little time to test before I have to push the box into production, running some OS that can give good performance on MySQL (really hoping it will be freebsd...) -- Justin Hopper UNIX Systems Engineer BSDHosting.net Hosting Division of Digital Oasys Inc. http://www.bsdhosting.net From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 06:53:25 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 07:20:34 2004 Return-Path: Delivered-To: freebsd-amd64@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: 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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 11:54:32 2004 Return-Path: Delivered-To: freebsd-amd64@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: 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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 15:32:32 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 16:54:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5968816A4CE for ; Wed, 23 Jun 2004 16:54:55 +0000 (GMT) Received: from carebears.mine.nu (ti400720a080-0547.bb.online.no [83.108.194.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A65FF43D5C for ; Wed, 23 Jun 2004 16:54:54 +0000 (GMT) (envelope-from solskogen@carebears.mine.nu) Received: from localhost (localhost.carebears.net [127.0.0.1]) by carebears.mine.nu (Postfix) with ESMTP id 2F72127F85A for ; Wed, 23 Jun 2004 18:54:37 +0200 (CEST) Received: from carebears.mine.nu ([127.0.0.1])port 10024) with ESMTP id 82141-08 for ; Wed, 23 Jun 2004 18:54:34 +0200 (CEST) Received: by carebears.mine.nu (Postfix, from userid 1001) id 085B927F279; Wed, 23 Jun 2004 18:54:34 +0200 (CEST) Date: Wed, 23 Jun 2004 18:54:34 +0200 From: Christer Solskogen To: freebsd-amd64@freebsd.org Message-ID: <20040623165434.GA82815@tenderheart.carebears.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavis at wish.carebears.net Subject: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 16:54:55 -0000 Hi! I`m having a bit problem with my keysettings with FreeBSD AMD64. Its seems like FreeBSD dont care about my settings in rc.conf. I also have a machine running FreeBSD i386, with the same settings in rc.conf, and it works on that arch. Just to be sure, I have included my rc.conf. (which is just like the rc.conf on the i386) # This is really done in rc.conf --->>>>> defaultrouter="192.168.0.1" hostname="funshine.carebears.net" ifconfig_rl0="inet 192.168.0.9 mtu 1492 netmask 255.255.255.0" nfs_client_enable="YES" sshd_enable="YES" usbd_enable="YES" sendmail_enable="NONE" keymap="norwegian.iso" keyrate="fast" rpcbind_enable="YES" # This is /not/ beeing done. font8x8="iso-8x8" font8x14="iso-8x14" font8x16="iso-8x16" allscreens_flags="80x50" --- Even the "allscreens_flag" is not taken care of. But here come the bug question! If I run /stand/sysinstall, and selects my options; my keyboard works with norwegian options and all. But it wont hold after a reboot. Tips, anyone? (Running FreeBSD 5.2.1-RELEASE-p8 on amd64) -- cso From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 17:12:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9CBF16A4CE; Wed, 23 Jun 2004 17:12:31 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA5D43D2D; Wed, 23 Jun 2004 17:12:30 +0000 (GMT) (envelope-from tilman@arved.at) Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1]) i5NHCKqk052921; Wed, 23 Jun 2004 19:12:21 +0200 (CEST) (envelope-from tilman@arved.at) Received: (from tilman@localhost) by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i5NHCKic052920; Wed, 23 Jun 2004 19:12:20 +0200 (CEST) X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to tilman@arved.at using -f Date: Wed, 23 Jun 2004 19:12:20 +0200 From: Tilman Linneweh To: kde@FreeBSD.org Message-ID: <20040623171220.GX65887@arved.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org Subject: Konqueror krashing on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 17:12:31 -0000 Hi, Anybody running KDE on amd64-CURRENT? Somewhere in the last three months something broke. Today I finally recompiled kdelibs with DEBUG support. Several applications start to crash on startup, like konqueror, kmix, kate and others still run fine, like konsole or kicker. The BT looks like this: Program received signal SIGSEGV, Segmentation fault. 0x0000000202883b39 in QString::fromUtf8 () from /usr/X11R6/lib/libqt-mt.so.3 (gdb) bt #0 0x0000000202883b39 in QString::fromUtf8 () from /usr/X11R6/lib/libqt-mt.so.3 #1 0x00000002018ea580 in KXMLGUIFactory::readConfigFile (filename=@0xacf0b0, never_null=false, _instance=0xffffffffffff9fff) at kxmlguifactory.cpp:127 #2 0x00000002018ea30d in KXMLGUIFactory::readConfigFile (filename=@0xad0000, instance=0xffffffffffff9fff) at kxmlguifactory.cpp:99 #3 0x00000002018e7748 in KXMLGUIClient::findMostRecentXMLFile ( files=@0x7fffffffdd20, doc=@0x7fffffffdd60) at kxmlguiclient.cpp:630 #4 0x00000002018e5dfb in KXMLGUIClient::setXMLFile (this=0x8d97a0, _file=@0x7fffffffde10, merge=false, setXMLDoc=16) at kxmlguiclient.cpp:183 [...] Any ideas? regards tilman From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 17:25:43 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 18:32:19 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 18:45:55 2004 Return-Path: Delivered-To: freebsd-amd64@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: freebsd-hardware@freebsd.org Subject: RE: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 19:00:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A07E816A52A; Wed, 23 Jun 2004 18:59:59 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A1A43D60; Wed, 23 Jun 2004 18:59:58 +0000 (GMT) (envelope-from tilman@arved.at) Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1]) i5NIvjRe053704; Wed, 23 Jun 2004 20:57:46 +0200 (CEST) (envelope-from tilman@arved.at) Received: (from tilman@localhost) by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i5NIvj57053703; Wed, 23 Jun 2004 20:57:45 +0200 (CEST) X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to tilman@arved.at using -f Date: Wed, 23 Jun 2004 20:57:45 +0200 From: Tilman Linneweh To: kde@FreeBSD.org Message-ID: <20040623185745.GA53673@arved.at> References: <20040623171220.GX65887@arved.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040623171220.GX65887@arved.at> User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org Subject: Re: Konqueror krashing on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 19:00:00 -0000 * Tilman Linneweh [2004-06-23 19:12]: > Several applications start to crash on startup, like konqueror, kmix, kate > and others still run fine, like konsole or kicker. > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000202883b39 in QString::fromUtf8 () from /usr/X11R6/lib/libqt-mt.so.3 Okay, this should be fixed with my last commit to kdelibs3. Thanks to Frerich for providing me with a fix. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 19:01:15 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F119B16A4CE for ; Wed, 23 Jun 2004 19:01:15 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D34DF43D64 for ; Wed, 23 Jun 2004 19:01:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i5NIoLKH081155 for ; Wed, 23 Jun 2004 18:50:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5NIoLCd081154; Wed, 23 Jun 2004 18:50:21 GMT (envelope-from gnats) Date: Wed, 23 Jun 2004 18:50:21 GMT Message-Id: <200406231850.i5NIoLCd081154@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Joe Talbott Subject: Re: amd64/67947: AMD64 Current 20040324 snapshot iso panics on install X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joe Talbott List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 19:01:16 -0000 The following reply was made to PR amd64/67947; it has been noted by GNATS. From: Joe Talbott To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: amd64/67947: AMD64 Current 20040324 snapshot iso panics on install Date: Wed, 23 Jun 2004 14:48:31 -0400 fix: update to 05/12/2004 BIOS Joe Talbott From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 19:01:31 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04F6216A4CE for ; Wed, 23 Jun 2004 19:01:31 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB3F043D69 for ; Wed, 23 Jun 2004 19:01:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i5NJ0glc081892 for ; Wed, 23 Jun 2004 19:00:42 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5NJ0gBG081891; Wed, 23 Jun 2004 19:00:42 GMT (envelope-from gnats) Date: Wed, 23 Jun 2004 19:00:42 GMT Message-Id: <200406231900.i5NJ0gBG081891@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Joe Talbott Subject: Re: amd64/68083: AMD64 Current 20040324 snapshot iso panics on install X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joe Talbott List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 19:01:31 -0000 The following reply was made to PR amd64/68083; it has been noted by GNATS. From: Joe Talbott To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: amd64/68083: AMD64 Current 20040324 snapshot iso panics on install Date: Wed, 23 Jun 2004 14:49:49 -0400 this pr is a duplicate of amd64/67947 and can be closed Joe Talbott From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 19:47:37 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D49AB16A4CE; Wed, 23 Jun 2004 19:47:37 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8467D43D3F; Wed, 23 Jun 2004 19:47:37 +0000 (GMT) (envelope-from simon@FreeBSD.org) Received: from freefall.freebsd.org (simon@localhost [127.0.0.1]) i5NJks3Z087525; Wed, 23 Jun 2004 19:46:54 GMT (envelope-from simon@freefall.freebsd.org) Received: (from simon@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5NJksWd087521; Wed, 23 Jun 2004 19:46:54 GMT (envelope-from simon) Date: Wed, 23 Jun 2004 19:46:54 GMT From: "Simon L. Nielsen" Message-Id: <200406231946.i5NJksWd087521@freefall.freebsd.org> To: josepht@xenno.com, simon@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/67947: AMD64 Current 20040324 snapshot iso panics on install X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 19:47:38 -0000 Synopsis: AMD64 Current 20040324 snapshot iso panics on install State-Changed-From-To: open->closed State-Changed-By: simon State-Changed-When: Wed Jun 23 19:46:36 GMT 2004 State-Changed-Why: Close at submitters request. http://www.freebsd.org/cgi/query-pr.cgi?pr=67947 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 20:42:15 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Wed Jun 23 20:45:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9794916A4CE for ; Wed, 23 Jun 2004 20:45:01 +0000 (GMT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21C3043D55 for ; Wed, 23 Jun 2004 20:45:01 +0000 (GMT) (envelope-from henrik.w.lund@broadpark.no) Received: from [10.0.0.3] (52.80-202-129.nextgentel.com [80.202.129.52]) by mail.broadpark.no (Postfix) with ESMTP id EF22A1AF8; Wed, 23 Jun 2004 22:45:13 +0200 (MEST) Message-ID: <40DA6A95.2070906@broadpark.no> Date: Wed, 23 Jun 2004 22:45:57 -0700 From: Henrik W Lund User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: nb, en-us, en MIME-Version: 1.0 To: Christer Solskogen References: <20040623165434.GA82815@tenderheart.carebears.net> In-Reply-To: <20040623165434.GA82815@tenderheart.carebears.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 20:45:01 -0000 Christer Solskogen wrote: >Hi! > >I`m having a bit problem with my keysettings with FreeBSD AMD64. >Its seems like FreeBSD dont care about my settings in rc.conf. >I also have a machine running FreeBSD i386, with the same settings >in rc.conf, and it works on that arch. > >Just to be sure, I have included my rc.conf. (which is just like >the rc.conf on the i386) > ># This is really done in rc.conf --->>>>> >defaultrouter="192.168.0.1" >hostname="funshine.carebears.net" >ifconfig_rl0="inet 192.168.0.9 mtu 1492 netmask 255.255.255.0" >nfs_client_enable="YES" >sshd_enable="YES" >usbd_enable="YES" >sendmail_enable="NONE" >keymap="norwegian.iso" >keyrate="fast" >rpcbind_enable="YES" ># This is /not/ beeing done. >font8x8="iso-8x8" >font8x14="iso-8x14" >font8x16="iso-8x16" >allscreens_flags="80x50" >--- > >Even the "allscreens_flag" is not taken care of. >But here come the bug question! >If I run /stand/sysinstall, and selects my options; my keyboard >works with norwegian options and all. But it wont hold after >a reboot. > >Tips, anyone? > >(Running FreeBSD 5.2.1-RELEASE-p8 on amd64) > > > Greetings, fellow norwegian!! Er du på NOBUG-lista? Den er jammen stille, må jeg si. ;-) I'm having the exact same problem as you. I have the keymap setting in rc.conf, but the bootup process doesn't honor it at all. It does, in fact, not honor any setting that has to do with syscons, as keyrate, screenmap and such does not work either. I dug around, and it seems the /etc/rc.d/syscons script is skipped during startup, for some obscure reason. Running 5.2.1-RELEASE-p0 I am, and I have just cvsupped hoping that it'd be fixed. No such luck, I see. :-/ I wonder if this is an issue with other scripts in /etc/rc.d as well? Haven't tried too much, I admit. Anyways, on a per session basis, I find that kbdmap is ideal to use for setting the keymap. It's a lot faster that /stand/sysinstall, and doesn't add a line to /etc/rc.conf every time. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 21:23:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34B4916A4CE for ; Wed, 23 Jun 2004 21:23:38 +0000 (GMT) Received: from carebears.mine.nu (ti400720a080-0547.bb.online.no [83.108.194.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 912FB43D5D for ; Wed, 23 Jun 2004 21:23:37 +0000 (GMT) (envelope-from solskogen@carebears.mine.nu) Received: from localhost (localhost.carebears.net [127.0.0.1]) by carebears.mine.nu (Postfix) with ESMTP id EA3E527FE10 for ; Wed, 23 Jun 2004 23:22:37 +0200 (CEST) Received: from carebears.mine.nu ([127.0.0.1])port 10024) with ESMTP id 83685-07 for ; Wed, 23 Jun 2004 23:22:36 +0200 (CEST) Received: from [192.168.0.9] (funshine.carebears.net [192.168.0.9]) by carebears.mine.nu (Postfix) with ESMTP id 7F2E227FE0E for ; Wed, 23 Jun 2004 23:22:36 +0200 (CEST) From: Christer Solskogen To: freebsd-amd64@freebsd.org In-Reply-To: <40DA6A95.2070906@broadpark.no> References: <20040623165434.GA82815@tenderheart.carebears.net> <40DA6A95.2070906@broadpark.no> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1088025770.45689.1.camel@funshine.carebears.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 23 Jun 2004 23:22:50 +0200 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavis at wish.carebears.net Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 21:23:38 -0000 On Thu, 2004-06-24 at 07:45, Henrik W Lund wrote: > > > Greetings, fellow norwegian!! Er du på NOBUG-lista? Den er jammen > stille, må jeg si. ;-) Jada, er der. > > I'm having the exact same problem as you. I have the keymap setting in > rc.conf, but the bootup process doesn't honor it at all. It does, in > fact, not honor any setting that has to do with syscons, as keyrate, > screenmap and such does not work either. I dug around, and it seems the > /etc/rc.d/syscons script is skipped during startup, for some obscure > reason. Running 5.2.1-RELEASE-p0 I am, and I have just cvsupped hoping > that it'd be fixed. No such luck, I see. :-/ One "nice" thing is that the norwegian keys works in X. even if it dont in console. I`m compiling CURRENT as we speak. maybe it will get rid of the problem. -- Med Vennlig Hilsen / Best regards Christer Solskogen http://carebears.mine.nu/~solskogen One's life tends to be like a beaver's, one dam thing after another. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 21:42:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B39B816A4CF for ; Wed, 23 Jun 2004 21:42:51 +0000 (GMT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AAAF43D2D for ; Wed, 23 Jun 2004 21:42:49 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 42953FD04C; Wed, 23 Jun 2004 14:42:28 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91004-10; Wed, 23 Jun 2004 14:42:28 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id CA1E5FD03B; Wed, 23 Jun 2004 14:42:27 -0700 (PDT) From: Sean McNeil To: Christer Solskogen In-Reply-To: <1088025770.45689.1.camel@funshine.carebears.net> References: <20040623165434.GA82815@tenderheart.carebears.net> <40DA6A95.2070906@broadpark.no> <1088025770.45689.1.camel@funshine.carebears.net> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1088026947.43260.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 23 Jun 2004 14:42:27 -0700 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 21:42:51 -0000 On Wed, 2004-06-23 at 14:22, Christer Solskogen wrote: > On Thu, 2004-06-24 at 07:45, Henrik W Lund wrote: > > > > > > > Greetings, fellow norwegian!! Er du på NOBUG-lista? Den er jammen > > stille, må jeg si. ;-) > > Jada, er der. > > > > > I'm having the exact same problem as you. I have the keymap setting in > > rc.conf, but the bootup process doesn't honor it at all. It does, in > > fact, not honor any setting that has to do with syscons, as keyrate, > > screenmap and such does not work either. I dug around, and it seems the > > /etc/rc.d/syscons script is skipped during startup, for some obscure > > reason. Running 5.2.1-RELEASE-p0 I am, and I have just cvsupped hoping > > that it'd be fixed. No such luck, I see. :-/ > > One "nice" thing is that the norwegian keys works in X. even if it dont > in console. > I`m compiling CURRENT as we speak. maybe it will get rid of the problem. You have enable_syscons="YES" in your /etc/rc.conf? From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 21:55:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B566416A4CF for ; Wed, 23 Jun 2004 21:55:37 +0000 (GMT) Received: from carebears.mine.nu (ti400720a080-0547.bb.online.no [83.108.194.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 276DA43D2F for ; Wed, 23 Jun 2004 21:55:35 +0000 (GMT) (envelope-from solskogen@carebears.mine.nu) Received: from localhost (localhost.carebears.net [127.0.0.1]) by carebears.mine.nu (Postfix) with ESMTP id C0D0027FE26; Wed, 23 Jun 2004 23:53:45 +0200 (CEST) Received: from carebears.mine.nu ([127.0.0.1])port 10024) with ESMTP id 17006-01; Wed, 23 Jun 2004 23:53:44 +0200 (CEST) Received: from [192.168.0.9] (funshine.carebears.net [192.168.0.9]) by carebears.mine.nu (Postfix) with ESMTP id 785A527FE10; Wed, 23 Jun 2004 23:53:44 +0200 (CEST) From: Christer Solskogen To: Sean McNeil In-Reply-To: <1088026947.43260.0.camel@server.mcneil.com> References: <20040623165434.GA82815@tenderheart.carebears.net> <40DA6A95.2070906@broadpark.no> <1088025770.45689.1.camel@funshine.carebears.net> <1088026947.43260.0.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1088027638.45689.3.camel@funshine.carebears.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 23 Jun 2004 23:53:58 +0200 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis at wish.carebears.net cc: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 21:55:37 -0000 On Wed, 2004-06-23 at 23:42, Sean McNeil wrote: > You have > > enable_syscons="YES" > > in your /etc/rc.conf? Eh, no? I never needed it. Will try. -- Med Vennlig Hilsen / Best regards Christer Solskogen http://carebears.mine.nu/~solskogen All probabilities are 50%: either a thing will happen or it won't. This is especially true when dealing with women. Likelihoods, however, are 90% against you. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 22:14:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5691C16A4CE for ; Wed, 23 Jun 2004 22:14:53 +0000 (GMT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4039643D2D for ; Wed, 23 Jun 2004 22:14:53 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id A5C5CFD04C; Wed, 23 Jun 2004 15:14:42 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43396-01; Wed, 23 Jun 2004 15:14:42 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 3D0F3FD03B; Wed, 23 Jun 2004 15:14:42 -0700 (PDT) From: Sean McNeil To: Christer Solskogen In-Reply-To: <1088027638.45689.3.camel@funshine.carebears.net> References: <20040623165434.GA82815@tenderheart.carebears.net> <40DA6A95.2070906@broadpark.no> <1088025770.45689.1.camel@funshine.carebears.net> <1088026947.43260.0.camel@server.mcneil.com> <1088027638.45689.3.camel@funshine.carebears.net> Content-Type: text/plain Message-Id: <1088028881.43484.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 23 Jun 2004 15:14:42 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 22:14:53 -0000 On Wed, 2004-06-23 at 14:53, Christer Solskogen wrote: > On Wed, 2004-06-23 at 23:42, Sean McNeil wrote: > > > You have > > > > enable_syscons="YES" > > > > in your /etc/rc.conf? > > Eh, no? > I never needed it. > Will try. Sorry, it would be the other way around: syscons_enable="YES" I don't know if it is required either, but most things in RCng require an enable in rc.conf. Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 22:20:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C83116A4CE for ; Wed, 23 Jun 2004 22:20:40 +0000 (GMT) Received: from carebears.mine.nu (ti400720a080-0547.bb.online.no [83.108.194.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B4EC43D64 for ; Wed, 23 Jun 2004 22:20:39 +0000 (GMT) (envelope-from solskogen@carebears.mine.nu) Received: from localhost (localhost.carebears.net [127.0.0.1]) by carebears.mine.nu (Postfix) with ESMTP id BBBC527F06F; Thu, 24 Jun 2004 00:20:01 +0200 (CEST) Received: from carebears.mine.nu ([127.0.0.1])port 10024) with ESMTP id 84047-09; Thu, 24 Jun 2004 00:20:00 +0200 (CEST) Received: from [192.168.0.9] (funshine.carebears.net [192.168.0.9]) by carebears.mine.nu (Postfix) with ESMTP id 4F3FE27F068; Thu, 24 Jun 2004 00:20:00 +0200 (CEST) From: Christer Solskogen To: Sean McNeil In-Reply-To: <1088028881.43484.2.camel@server.mcneil.com> References: <20040623165434.GA82815@tenderheart.carebears.net> <40DA6A95.2070906@broadpark.no> <1088025770.45689.1.camel@funshine.carebears.net> <1088026947.43260.0.camel@server.mcneil.com> <1088027638.45689.3.camel@funshine.carebears.net> <1088028881.43484.2.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1088029210.25697.0.camel@funshine.carebears.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 24 Jun 2004 00:20:10 +0200 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis at wish.carebears.net cc: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 22:20:40 -0000 On Thu, 2004-06-24 at 00:14, Sean McNeil wrote: > On Wed, 2004-06-23 at 14:53, Christer Solskogen wrote: > > On Wed, 2004-06-23 at 23:42, Sean McNeil wrote: > > > > > You have > > > > > > enable_syscons="YES" > > > > > > in your /etc/rc.conf? > > > > Eh, no? > > I never needed it. > > Will try. > > Sorry, it would be the other way around: > > syscons_enable="YES" > > I don't know if it is required either, but most things in RCng require > an enable in rc.conf. > Neverless. It works with CURRENT :) -- Med Vennlig Hilsen / Best regards Christer Solskogen http://carebears.mine.nu/~solskogen Sow your wild oats on Saturday night - then on Sunday pray for crop failure. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 24 04:59:00 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Thu Jun 24 09:27:29 2004 Return-Path: Delivered-To: freebsd-amd64@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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform 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-amd64@FreeBSD.ORG Thu Jun 24 14:42:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E840A16A4CE for ; Thu, 24 Jun 2004 14:42:24 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A074943D48 for ; Thu, 24 Jun 2004 14:42:22 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with spam-scanned (Exim 4.34; FreeBSD) id 1BdVQJ-0007Sx-3l for freebsd-amd64@freebsd.org; Thu, 24 Jun 2004 16:42:05 +0200 Received: from eirik.unicore.no ([213.225.74.166] helo=anduin.net) by anduin.net with esmtp (Exim 4.34; FreeBSD) id 1BdVQ8-0007Sn-AY; Thu, 24 Jun 2004 16:41:44 +0200 Message-ID: <40DAE7EB.7070800@anduin.net> Date: Thu, 24 Jun 2004 16:40:43 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.5 (X11/20040308) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <023d01c45161$8f486360$471b3dd4@dual><40CCA3CB.6090808@anduin.net><02b001c4517d$46da25c0$471b3dd4@dual><033301c45198$ddd10b40$471b3dd4@dual> <058901c4525a$105cfbc0$471b3dd4@dual> <010e01c45304$ed1c5c90$471b3dd4@dual> In-Reply-To: <010e01c45304$ed1c5c90$471b3dd4@dual> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on anduin.net X-Spam-Status: No, hits=0.0 required=7.5 tests=none autolearn=no version=2.63 X-Spam-Level: cc: freebsd-ports@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: anybody using net-snmp on AMD64 or other 64bit platforms?? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 14:42:25 -0000 Willem Jan Withagen wrote: > For those really desperate to run snmpd on 64bit, there are some very crude > patches. Most likely not for the faint of hart, but everything compiles and runs > at my end. I can confirm that for the limited use I have of it, it seems to work. Been running for a week now, no hickups. /Eirik > They need more work to be integrated into the port, since I have not worked out > the int <> long <> pointer stuff. Which really creates issues here. > > None the less, if you want: > withagen.dyndns.org:/FreeBSD/net-snmp.64bit.diff > Tell me if it breaks. > > --WjW > > > ----- Original Message ----- > From: "Willem Jan Withagen" > To: "Willem Jan Withagen" > Cc: ; > Sent: Monday, June 14, 2004 11:53 PM > Subject: Re: anybody using net-snmp on AMD64 or other 64bit platforms?? > > > >>>I've got it more or less running, and snmpd is no longer crashing on me > > "yet". > >>>But I'm now getting wrong answers for the tcp/udp connections. But for >>>established connections as well as open server ports.... >>> >>>Both netstat and snmpd do this by retreiving data with sysctl from the > > kernel. > >>>And where netstat has got its things right, snmpd seems to be really off. >>>The most likely reason is that snmpd defines some structures by itself, but >> >>now >> >>>the question is which part is that??? >> >>It is now running to the part where I can do the things with it I'd like to > > use > >>it for.... >>Just figure out a way of putting the changes back in in such a way that it'll >>still work on 32bit. And get the maintainer to accept my fixes... >> >>But as far as I could tell, certain features (udp/tcptables) did not work on >>i386 either. >> >>--WjW >> >>_______________________________________________ >>freebsd-ports@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>To unsubscribe, send any mail to "freebsd-ports-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-amd64@FreeBSD.ORG Fri Jun 25 06:03:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 035B416A4CE for ; Fri, 25 Jun 2004 06:03:17 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8C443D66 for ; Fri, 25 Jun 2004 06:03:16 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [212.227.126.179] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bdjmf-0000Iw-00 for freebsd-amd64@freebsd.org; Fri, 25 Jun 2004 08:01:57 +0200 Received: from [213.7.228.111] (helo=freenet.de) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1Bdjme-0001BA-00 for freebsd-amd64@freebsd.org; Fri, 25 Jun 2004 08:01:57 +0200 Message-ID: <40DBBFC9.4080404@freenet.de> Date: Fri, 25 Jun 2004 08:01:45 +0200 From: Manuel Stuehn User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-AT; rv:1.6) Gecko/20040615 X-Accept-Language: de-de, de MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:599aa05e1f3f8231fce0632e961004a8 Subject: core-dumping gdb6 on amd64-CURRENT X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 06:03:17 -0000 Hi. Im running an amd64-FreeBSD 5.2-CURRENT (from Jun 22). I tried to install the /usr/ports/devel/gdb6-20040615. Everything (configure,build and install of the gdb) goes fine, but when I start the gdb, this happens: manuel@AMD64:~> gdb GNU gdb 20040615 [GDB v6.x for FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd5.2". Segmentation fault (core dumped) Output of xconsole: Jun 25 07:45:42 AMD64 kernel: pid 21608 (gdb6), uid 1001: exited on signal 11 (core dumped) #uname -v FreeBSD 5.2-CURRENT #0: Tue Jun 22 19:46:30 CEST 2004 manuel@AMD64.BSDNet:/usr/obj/usr/src/sys/SCHED_ULE If I forgot any usefull information, please give me a hint. Thanks in advance Manuel Stuehn From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 07:14:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6411F16A4CE for ; Fri, 25 Jun 2004 07:14:30 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA9F143D31 for ; Fri, 25 Jun 2004 07:14:29 +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 i5P7D2i6034757; Fri, 25 Jun 2004 00:13:02 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5P7D2to034756; Fri, 25 Jun 2004 00:13:02 -0700 (PDT) (envelope-from obrien) Date: Fri, 25 Jun 2004 00:13:02 -0700 From: "David O'Brien" To: Christer Solskogen Message-ID: <20040625071302.GA34362@dragon.nuxi.com> References: <20040623165434.GA82815@tenderheart.carebears.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040623165434.GA82815@tenderheart.carebears.net> 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: freebsd-amd64@freebsd.org Subject: Re: keymap and rc.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 07:14:30 -0000 On Wed, Jun 23, 2004 at 06:54:34PM +0200, Christer Solskogen wrote: > I`m having a bit problem with my keysettings with FreeBSD AMD64. You didn't state if this is 5.2.1 or 5-CURRENT. If 5.2.1, a bug was fixed in /etc/rc.d/syscons that I think would behave as you are seeing. > allscreens_flags="80x50" > Even the "allscreens_flag" is not taken care of. Your 'allscreens_flags' flag won't work. This is because AMD64 doesn't support VESA modes. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 08:19:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C9216A4CE; Fri, 25 Jun 2004 08:19:08 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2C5043D2F; Fri, 25 Jun 2004 08:19:08 +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 i5P8IBTf038770; Fri, 25 Jun 2004 01:18:11 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5P8IB5x038745; Fri, 25 Jun 2004 01:18:11 -0700 (PDT) (envelope-from obrien) Date: Fri, 25 Jun 2004 01:18:11 -0700 From: "David O'Brien" To: mike Message-ID: <20040625081811.GA49426@dragon.nuxi.com> References: <200406221811.47868.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: 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-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 08:19:09 -0000 On Tue, Jun 22, 2004 at 06:34:38PM -0700, mike wrote: > > 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 =) *So* much has been fixed from 5.2.1, which was branched last Fall, in 5-CURRENT (ie, HEAD) WRT AMD64, I don't know why anyone is running 5.2.1 and not 5-CURRENT. I would definitely put AMD64 5-CURRENT into production vs. 5.2.1. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 08:50:45 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FC1216A4CE for ; Fri, 25 Jun 2004 08:50:45 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5300443D54 for ; Fri, 25 Jun 2004 08:50:45 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i5P8oO9Z025888 for ; Fri, 25 Jun 2004 08:50:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5P8oOhn025887; Fri, 25 Jun 2004 08:50:24 GMT (envelope-from gnats) Date: Fri, 25 Jun 2004 08:50:24 GMT Message-Id: <200406250850.i5P8oOhn025887@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Jeff Connelly Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jeff Connelly List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 08:50:45 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Jeff Connelly To: freebsd-gnats-submit@FreeBSD.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Fri, 25 Jun 2004 01:41:08 -0700 (PDT) --0-1052444370-1088152868=:51949 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline >Loader succeeds, boot fails. All boot options (safe >mode, disable acpi) fail. Fails immediately, with nary a >turn of the boot spinner (/-\|). Fails with default >modules loaded or unloaded. Same problem occurs on Compaq Presario R3140US (which is almost the same laptop), with FreeBSD amd64 5.2.1, FreeBSD i386 5.2.1, and FreeBSD i386 4.10. Verbose logging doesn't reveal any information. Debian amd64 sid and NetBSD 2.0-beta amd64 boot fine. Any help greatly appreciated. Wish I could provide more information, I'm open to suggestions on what to try. Attached is the dmesg of a successful boot of NetBSD 2.0 on the R3140US, I hope its helpful to FreeBSD amd64 developers. __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail --0-1052444370-1088152868=:51949 Content-Type: application/octet-stream; name=dmesg-netbsd-amd64-compaq_presario_r3140us Content-Transfer-Encoding: base64 Content-Description: dmesg-netbsd-amd64-compaq_presario_r3140us Content-Disposition: attachment; filename=dmesg-netbsd-amd64-compaq_presario_r3140us TmV0QlNEIDIuMF9CRVRBIChHRU5FUklDKSAjMDogVGh1IEFwciAyMiAxNjo0 NzowOCBQRFQgMjAwNAoJbXRob21hc0BjZXJlYWxib3guZW5nbGFiLmJyb2Nh ZGUuY29tOi91Mi9uZXRic2QtMi0wL2FtZDY0L29iai9zeXMvYXJjaC9hbWQ2 NC9jb21waWxlL0dFTkVSSUMKdG90YWwgbWVtb3J5ID0gNTExIE1CCmF2YWls IG1lbW9yeSA9IDQ4NCBNQgptYWluYnVzMCAocm9vdCkKY3B1MCBhdCBtYWlu YnVzMDogKHVuaXByb2Nlc3NvcikKY3B1MDogQU1EIEF0aGxvbih0bSkgNjQg UHJvY2Vzc29yIDMwMDArLCAxNzk1LjQ4IE1IegpjcHUwOiBmZWF0dXJlczog ZTdkYmZiZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxB UElDLFNFUCxNVFJSPgpjcHUwOiBmZWF0dXJlczogZTdkYmZiZmY8UEdFLE1D QSxDTU9WLFBBVCxQU0UzNixNUEMsTk9YLE1NWFgsTU1YPgpjcHUwOiBmZWF0 dXJlczogZTdkYmZiZmY8RlhTUixTU0UsU1NFMixMT05HLDNETk9XMiwzRE5P Vz4KY3B1MDogSS1jYWNoZSA2NCBLQiA2NGIvbGluZSAyLXdheSwgRC1jYWNo ZSA2NCBLQiA2NGIvbGluZSAyLXdheQpjcHUwOiBMMiBjYWNoZSAxIE1CIDY0 Yi9saW5lIDE2LXdheQpjcHUwOiBJVExCIDMyIDQgS0IgZW50cmllcyBmdWxs eSBhc3NvY2lhdGl2ZSwgOCA0IE1CIGVudHJpZXMgZnVsbHkgYXNzb2NpYXRp dmUKY3B1MDogRFRMQiAzMiA0IEtCIGVudHJpZXMgZnVsbHkgYXNzb2NpYXRp dmUsIDggNCBNQiBlbnRyaWVzIGZ1bGx5IGFzc29jaWF0aXZlCmNwdTA6IDE2 IHBhZ2UgY29sb3JzCnBjaTAgYXQgbWFpbmJ1czAgYnVzIDA6IGNvbmZpZ3Vy YXRpb24gbW9kZSAxCnBjaTA6IGkvbyBzcGFjZSwgbWVtb3J5IHNwYWNlIGVu YWJsZWQsIHJkL2xpbmUsIHJkL211bHQsIHdyL2ludiBvawpwY2hiMCBhdCBw Y2kwIGRldiAwIGZ1bmN0aW9uIDAKcGNoYjA6IE52aWRpYSBDb3Jwb3JhdGlv biBuRm9yY2UzIEhvc3QtUENJIGJyaWRnZSAocmV2LiAweGE0KQpwY2liMCBh dCBwY2kwIGRldiAxIGZ1bmN0aW9uIDAKcGNpYjA6IE52aWRpYSBDb3Jwb3Jh dGlvbiBuRm9yY2UzIFBDSS1JU0EgYnJpZGdlIChyZXYuIDB4YTYpCk52aWRp YSBDb3Jwb3JhdGlvbiBuRm9yY2UzIFNNQnVzIGNvbnRyb2xsZXIgKFNNQnVz IHNlcmlhbCBidXMsIHJldmlzaW9uIDB4YTQpIGF0IHBjaTAgZGV2IDEgZnVu Y3Rpb24gMSBub3QgY29uZmlndXJlZApvaGNpMCBhdCBwY2kwIGRldiAyIGZ1 bmN0aW9uIDA6IE52aWRpYSBDb3Jwb3JhdGlvbiBuRm9yY2UzIFVTQiBIb3N0 IENvbnRyb2xsZXIgKHJldi4gMHhhNSkKb2hjaTA6IGludGVycnVwdGluZyBh dCBpcnEgMTEKb2hjaTA6IE9IQ0kgdmVyc2lvbiAxLjAsIGxlZ2FjeSBzdXBw b3J0CnVzYjAgYXQgb2hjaTA6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjAgYXQg dXNiMAp1aHViMDogTnZpZGlhIENvcnBvcmF0IE9IQ0kgcm9vdCBodWIsIGNs YXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxCnVodWIwOiAzIHBvcnRz IHdpdGggMyByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApvaGNpMSBhdCBwY2kw IGRldiAyIGZ1bmN0aW9uIDE6IE52aWRpYSBDb3Jwb3JhdGlvbiBuRm9yY2Uz IFVTQiBIb3N0IENvbnRyb2xsZXIgKHJldi4gMHhhNSkKb2hjaTE6IGludGVy cnVwdGluZyBhdCBpcnEgMTAKb2hjaTE6IE9IQ0kgdmVyc2lvbiAxLjAsIGxl Z2FjeSBzdXBwb3J0CnVzYjEgYXQgb2hjaTE6IFVTQiByZXZpc2lvbiAxLjAK dWh1YjEgYXQgdXNiMQp1aHViMTogTnZpZGlhIENvcnBvcmF0IE9IQ0kgcm9v dCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxCnVodWIx OiAzIHBvcnRzIHdpdGggMyByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApOdmlk aWEgQ29ycG9yYXRpb24gbkZvcmNlMyBVU0IyIEhvc3QgQ29udHJvbGxlciAo VVNCIHNlcmlhbCBidXMsIGludGVyZmFjZSAweDIwLCByZXZpc2lvbiAweGEy KSBhdCBwY2kwIGRldiAyIGZ1bmN0aW9uIDIgbm90IGNvbmZpZ3VyZWQKYXVp Y2gwIGF0IHBjaTAgZGV2IDYgZnVuY3Rpb24gMDogbkZvcmNlMyBNQ1AtVCBB Qy05NyBBdWRpbwphdWljaDA6IGludGVycnVwdGluZyBhdCBpcnEgMTEKYXVp Y2gwOiBhYzk3OiBBbmFsb2cgRGV2aWNlcyBBRDE5ODFCIGNvZGVjOyBoZWFk cGhvbmUsIDIwIGJpdCBEQUMsIG5vIDNEIHN0ZXJlbwphdWljaDA6IGFjOTc6 IGV4dCBpZCA2MDU8QUM5N18yMixBTUFQLFNQRElGLFZSQT4KTnZpZGlhIENv cnBvcmF0aW9uIHByb2R1Y3QgMHgwMGQ5IChtb2RlbSBjb21tdW5pY2F0aW9u cywgcmV2aXNpb24gMHhhMikgYXQgcGNpMCBkZXYgNiBmdW5jdGlvbiAxIG5v dCBjb25maWd1cmVkCnZpYWlkZTAgYXQgcGNpMCBkZXYgOCBmdW5jdGlvbiAw CnZpYWlkZTA6IE5WSURJQSBuRm9yY2UzIElERSBDb250cm9sbGVyIChyZXYu IDB4YTUpCnZpYWlkZTA6IGJ1cy1tYXN0ZXIgRE1BIHN1cHBvcnQgcHJlc2Vu dAp2aWFpZGUwOiBwcmltYXJ5IGNoYW5uZWwgY29uZmlndXJlZCB0byBjb21w YXRpYmlsaXR5IG1vZGUKdmlhaWRlMDogcHJpbWFyeSBjaGFubmVsIGludGVy cnVwdGluZyBhdCBpcnEgMTQKYXRhYnVzMCBhdCB2aWFpZGUwIGNoYW5uZWwg MAp2aWFpZGUwOiBzZWNvbmRhcnkgY2hhbm5lbCBjb25maWd1cmVkIHRvIGNv bXBhdGliaWxpdHkgbW9kZQp2aWFpZGUwOiBzZWNvbmRhcnkgY2hhbm5lbCBp bnRlcnJ1cHRpbmcgYXQgaXJxIDE1CmF0YWJ1czEgYXQgdmlhaWRlMCBjaGFu bmVsIDEKcHBiMCBhdCBwY2kwIGRldiAxMCBmdW5jdGlvbiAwOiBOdmlkaWEg Q29ycG9yYXRpb24gbkZvcmNlMyBQQ0ktUENJIGJyaWRnZSAocmV2LiAweGEy KQpwY2kxIGF0IHBwYjAgYnVzIDIKcGNpMTogaS9vIHNwYWNlLCBtZW1vcnkg c3BhY2UgZW5hYmxlZApydGswIGF0IHBjaTEgZGV2IDEgZnVuY3Rpb24gMDog UmVhbHRlayA4MTM5IDEwLzEwMEJhc2VUWApydGswOiBpbnRlcnJ1cHRpbmcg YXQgaXJxIDExCnJ0azA6IEV0aGVybmV0IGFkZHJlc3MgMDA6MDI6M2Y6MjU6 MTM6NDQKdWtwaHkwIGF0IHJ0azAgcGh5IDc6IEdlbmVyaWMgSUVFRSA4MDIu M3UgbWVkaWEgaW50ZXJmYWNlCnVrcGh5MDogT1VJIDB4MDAwMDAwLCBtb2Rl bCAweDAwMDAsIHJldi4gMAp1a3BoeTA6IDEwYmFzZVQsIDEwYmFzZVQtRkRY LCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1dG8KQnJvYWRjb20gQ29y cG9yYXRpb24gcHJvZHVjdCAweDQzMjAgKG1pc2NlbGxhbmVvdXMgbmV0d29y aywgcmV2aXNpb24gMHgwMykgYXQgcGNpMSBkZXYgMiBmdW5jdGlvbiAwIG5v dCBjb25maWd1cmVkClRleGFzIEluc3RydW1lbnRzIFBDSTE2MjAgUENJLUNh cmRCdXMgQnJpZGdlIChDYXJkQnVzIGJyaWRnZSwgcmV2aXNpb24gMHgwMSkg YXQgcGNpMSBkZXYgNCBmdW5jdGlvbiAwIG5vdCBjb25maWd1cmVkClRleGFz IEluc3RydW1lbnRzIFBDSTE2MjAgUENJLUNhcmRCdXMgQnJpZGdlIChDYXJk QnVzIGJyaWRnZSwgcmV2aXNpb24gMHgwMSkgYXQgcGNpMSBkZXYgNCBmdW5j dGlvbiAxIG5vdCBjb25maWd1cmVkClRleGFzIEluc3RydW1lbnRzIHByb2R1 Y3QgMHg4MjAxIChtaXNjZWxsYW5lb3VzIHN5c3RlbSwgcmV2aXNpb24gMHgw MSkgYXQgcGNpMSBkZXYgNCBmdW5jdGlvbiAyIG5vdCBjb25maWd1cmVkCnBw YjEgYXQgcGNpMCBkZXYgMTEgZnVuY3Rpb24gMDogTnZpZGlhIENvcnBvcmF0 aW9uIHByb2R1Y3QgMHgwMGQyIChyZXYuIDB4YTQpCnBjaTIgYXQgcHBiMSBi dXMgMQpwY2kyOiBpL28gc3BhY2UsIG1lbW9yeSBzcGFjZSBlbmFibGVkCnZn YTAgYXQgcGNpMiBkZXYgMCBmdW5jdGlvbiAwOiBOdmlkaWEgQ29ycG9yYXRp b24gcHJvZHVjdCAweDAxNzYgKHJldi4gMHhhMykKd3NkaXNwbGF5MCBhdCB2 Z2EwIGtiZG11eCAxOiBjb25zb2xlICg4MHgyNSwgdnQxMDAgZW11bGF0aW9u KQp3c211eDE6IGNvbm5lY3RpbmcgdG8gd3NkaXNwbGF5MApwY2hiMSBhdCBw Y2kwIGRldiAyNCBmdW5jdGlvbiAwCnBjaGIxOiBBZHZhbmNlZCBNaWNybyBE ZXZpY2VzIEFNRDY0IEh5cGVyVHJhbnNwb3J0IGNvbmZpZ3VyYXRpb24gKHJl di4gMHgwMCkKcGNoYjIgYXQgcGNpMCBkZXYgMjQgZnVuY3Rpb24gMQpwY2hi MjogQWR2YW5jZWQgTWljcm8gRGV2aWNlcyBBTUQ2NCBBZGRyZXNzIE1hcCBj b25maWd1cmF0aW9uIChyZXYuIDB4MDApCnBjaGIzIGF0IHBjaTAgZGV2IDI0 IGZ1bmN0aW9uIDIKcGNoYjM6IEFkdmFuY2VkIE1pY3JvIERldmljZXMgQU1E NjQgRFJBTSBjb25maWd1cmF0aW9uIChyZXYuIDB4MDApCnBjaGI0IGF0IHBj aTAgZGV2IDI0IGZ1bmN0aW9uIDMKcGNoYjQ6IEFkdmFuY2VkIE1pY3JvIERl dmljZXMgQU1ENjQgTWlzY2VsbGFuZW91cyBjb25maWd1cmF0aW9uIChyZXYu IDB4MDApCmlzYTAgYXQgcGNpYjAKbHB0MCBhdCBpc2EwIHBvcnQgMHgzNzgt MHgzN2IgaXJxIDcKcGNrYmMwIGF0IGlzYTAgcG9ydCAweDYwLTB4NjQKcGNr YmQwIGF0IHBja2JjMCAoa2JkIHNsb3QpCnBja2JjMDogdXNpbmcgaXJxIDEg Zm9yIGtiZCBzbG90Cndza2JkMCBhdCBwY2tiZDA6IGNvbnNvbGUga2V5Ym9h cmQsIHVzaW5nIHdzZGlzcGxheTAKcG1zMCBhdCBwY2tiYzAgKGF1eCBzbG90 KQpwY2tiYzA6IHVzaW5nIGlycSAxMiBmb3IgYXV4IHNsb3QKd3Ntb3VzZTAg YXQgcG1zMCBtdXggMApwY3BwaTAgYXQgaXNhMCBwb3J0IDB4NjEKbWlkaTAg YXQgcGNwcGkwOiBQQyBzcGVha2VyCnN5c2JlZXAwIGF0IHBjcHBpMAphdWlj aDA6IG1lYXN1cmVkIGFjOTcgbGluayByYXRlIGF0IDE2MDc3IEh6LCB3aWxs IHVzZSA0ODAwMCBIegphdWRpbzAgYXQgYXVpY2gwOiBmdWxsIGR1cGxleCwg bW1hcCwgaW5kZXBlbmRlbnQKS2VybmVsaXplZCBSQUlEZnJhbWUgYWN0aXZh dGVkCndkMCBhdCBhdGFidXMwIGRyaXZlIDA6IDxGVUpJVFNVIE1IVDIwNjBB VCBQTD4Kd2QwOiBkcml2ZSBzdXBwb3J0cyAxNi1zZWN0b3IgUElPIHRyYW5z ZmVycywgTEJBIGFkZHJlc3NpbmcKd2QwOiA1NzIzMSBNQiwgMTE2MjgwIGN5 bCwgMTYgaGVhZCwgNjMgc2VjLCA1MTIgYnl0ZXMvc2VjdCB4IDExNzIxMDI0 MCBzZWN0b3JzCndkMDogMzItYml0IGRhdGEgcG9ydAp3ZDA6IGRyaXZlIHN1 cHBvcnRzIFBJTyBtb2RlIDQsIERNQSBtb2RlIDIsIFVsdHJhLURNQSBtb2Rl IDUgKFVsdHJhLzEwMCkKd2QwKHZpYWlkZTA6MDowKTogdXNpbmcgUElPIG1v ZGUgNCwgVWx0cmEtRE1BIG1vZGUgNSAoVWx0cmEvMTAwKSAodXNpbmcgRE1B IGRhdGEgdHJhbnNmZXJzKQphdGFwaWJ1czAgYXQgYXRhYnVzMTogMiB0YXJn ZXRzCmNkMCBhdCBhdGFwaWJ1czAgZHJpdmUgMDogPEhMLURULVNUIERWRCtS VyBHQ0EtNDA0ME4sICwgMS4xNz4gY2Ryb20gcmVtb3ZhYmxlCmNkMDogMzIt Yml0IGRhdGEgcG9ydApjZDA6IGRyaXZlIHN1cHBvcnRzIFBJTyBtb2RlIDQs IERNQSBtb2RlIDIKY2QwKHZpYWlkZTA6MTowKTogdXNpbmcgUElPIG1vZGUg NCwgRE1BIG1vZGUgMiAodXNpbmcgRE1BIGRhdGEgdHJhbnNmZXJzKQpib290 IGRldmljZTogd2QwCnJvb3Qgb24gd2QwYSBkdW1wcyBvbiB3ZDBiCnJvb3Qg ZmlsZSBzeXN0ZW0gdHlwZTogZmZzCndzZGlzcGxheTA6IHNjcmVlbiAxIGFk ZGVkICg4MHgyNSwgdnQxMDAgZW11bGF0aW9uKQp3c2Rpc3BsYXkwOiBzY3Jl ZW4gMiBhZGRlZCAoODB4MjUsIHZ0MTAwIGVtdWxhdGlvbikKd3NkaXNwbGF5 MDogc2NyZWVuIDMgYWRkZWQgKDgweDI1LCB2dDEwMCBlbXVsYXRpb24pCndz ZGlzcGxheTA6IHNjcmVlbiA0IGFkZGVkICg4MHgyNSwgdnQxMDAgZW11bGF0 aW9uKQo= --0-1052444370-1088152868=:51949-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 09:21:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70F1A16A4CE; Fri, 25 Jun 2004 09:21:32 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 190AA43D55; Fri, 25 Jun 2004 09:21:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i5P9LVrs068656; Fri, 25 Jun 2004 05:21:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.12.11/8.12.11) with ESMTP id i5P9LUTm095859; Fri, 25 Jun 2004 05:21:30 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E39717303F; Fri, 25 Jun 2004 05:21:30 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040625092130.E39717303F@freebsd-current.sentex.ca> Date: Fri, 25 Jun 2004 05:21:30 -0400 (EDT) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 09:21:32 -0000 TB --- 2004-06-25 08:15:34 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-06-25 08:15:34 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-06-25 08:15:34 - checking out the source tree TB --- 2004-06-25 08:15:34 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- 2004-06-25 08:15:34 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-06-25 08:19:19 - building world (CFLAGS=-O2 -pipe) TB --- 2004-06-25 08:19:19 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- 2004-06-25 08:19:19 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-06-25 09:16:42 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-06-25 09:16:42 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- 2004-06-25 09:16:42 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Jun 25 09:16:43 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/fake.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/feeder.c awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/feeder_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchron ous-unwind-tables -ffreestanding -Werror feeder_if.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/feeder_fmt.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/feeder_rate.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/mixer.c /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/mixer.c: In function `mixer_init': /tinderbox/CURRENT/amd64/amd64/src/sys/dev/sound/pcm/mixer.c:192: warning: `v' might be used uninitialized in this function *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-06-25 09:21:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-06-25 09:21:30 - ERROR: failed to build generic kernel TB --- 2004-06-25 09:21:30 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 09:55:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3671516A4CE; Fri, 25 Jun 2004 09:55:14 +0000 (GMT) Received: from daemon.li (daemon.li [213.203.244.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4DC243D1D; Fri, 25 Jun 2004 09:55:13 +0000 (GMT) (envelope-from josef@daemon.li) Received: from localhost (localhost [127.0.0.1]) (uid 1000) by daemon.li with local; Fri, 25 Jun 2004 09:53:25 +0000 Date: Fri, 25 Jun 2004 09:53:25 +0000 From: Josef El-Rayes To: FreeBSD Tinderbox Message-ID: <20040625095324.GD17587@daemon.li> References: <20040625092130.E39717303F@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_daemon.li-18392-1088157205-0001-2" Content-Disposition: inline In-Reply-To: <20040625092130.E39717303F@freebsd-current.sentex.ca> User-Agent: Mutt/1.3.28i cc: amd64@freebsd.org cc: current@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 09:55:14 -0000 This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_daemon.li-18392-1088157205-0001-2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable FreeBSD Tinderbox : > TB --- 2004-06-25 08:15:34 - tinderbox 2.3 running on freebsd-current.sen= tex.ca > TB --- 2004-06-25 08:15:34 - starting CURRENT tinderbox run for amd64/amd= 64 > TB --- 2004-06-25 08:15:34 - checking out the source tree > TB --- 2004-06-25 08:15:34 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd= 64 > TB --- 2004-06-25 08:15:34 - /usr/bin/cvs -f -R -q -d/home/ncvs update -P= d -A src > TB --- 2004-06-25 08:19:19 - building world (CFLAGS=3D-O2 -pipe) > TB --- 2004-06-25 08:19:19 - cd /home/tinderbox/sandbox/CURRENT/amd64/amd= 64/src > TB --- 2004-06-25 08:19:19 - /usr/bin/make -B buildworld > [...] sorry, my fault, ill fix this asap. -josef --=20 Josef El-Rayes (__) Email: josef@daemon.li \\\'',)=20 Web: http://daemon.li/ \/ \ ^ FreeBSD: josef@FreeBSD.org .\._/_) --=_daemon.li-18392-1088157205-0001-2 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iQEVAwUBQNv2FFnFItmnnbU8AQJ2OAgAmGL+TzdNUl/qmBwpXE89D3rDOHKMHjz/ qGCNjX7nX5ct29JmJhDRePWuRrXLk+yF5qDVabFRkWdhmVimfKzib66XYCl+Nvbs xg9bYNJlDQkqsxN4CDWDghMjkquN1lOLUogridgi0lghbANAVEZh6PEo7QvlHvU3 yZD3qdag0AD0okJwLCQerhjm5M0+UC8Vu3rWd8D4Je4e3aDop4XR2gA6EkzMHxi2 IZVheHKPq01ca0XGNFPjQMqTJ5egvFoxeyH5c4xe626tjbJIaEAjWJllr42cPCbp 7uHiVX6dL1S9y48hL1f92yFX1f0ZYvnOvSv6n/UCb/bzxpOUcvBHJA== =7EgG -----END PGP SIGNATURE----- --=_daemon.li-18392-1088157205-0001-2-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 00:17:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B984416A4CE for ; Sat, 26 Jun 2004 00:17:38 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D61043D2D for ; Sat, 26 Jun 2004 00:17:38 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) i5Q0G6Rl033685; Fri, 25 Jun 2004 20:16:06 -0400 (EDT) (envelope-from jkim@niksun.com) X-RAV-AntiVirus: This e-mail has been scanned for viruses. From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, Jeff Connelly Date: Fri, 25 Jun 2004 20:16:04 -0400 User-Agent: KMail/1.6.1 References: <200406250850.i5P8oOhn025887@freefall.freebsd.org> In-Reply-To: <200406250850.i5P8oOhn025887@freefall.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200406252016.04775.jkim@niksun.com> cc: dillon@apollo.backplane.com Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2004 00:17:38 -0000 On Friday 25 June 2004 04:50 am, Jeff Connelly wrote: > The following reply was made to PR amd64/67745; it has been noted > by GNATS. > > From: Jeff Connelly > To: freebsd-gnats-submit@FreeBSD.org, newntrbr@ucla.edu > Cc: > Subject: Re: amd64/67745: boot fails on compaq presario r3000z > Date: Fri, 25 Jun 2004 01:41:08 -0700 (PDT) > > --0-1052444370-1088152868=:51949 > Content-Type: text/plain; charset=us-ascii > Content-Id: > Content-Disposition: inline > > >Loader succeeds, boot fails. All boot options (safe > >mode, disable acpi) fail. Fails immediately, with > > nary a > > >turn of the boot spinner (/-\|). Fails with default > >modules loaded or unloaded. > > Same problem occurs on Compaq Presario R3140US (which > is almost the same laptop), with FreeBSD amd64 5.2.1, > FreeBSD i386 5.2.1, and FreeBSD i386 4.10. Verbose > logging doesn't reveal any information. Debian amd64 > sid and NetBSD 2.0-beta amd64 boot fine. > > Any help greatly appreciated. Wish I could provide > more information, I'm open to suggestions on what to > try. > > Attached is the dmesg of a successful boot of NetBSD > 2.0 on the R3140US, I hope its helpful to FreeBSD > amd64 developers. ----- SNIP!!! ----- The last known bootable kernel is from FreeBSD 2.2.2-RELEASE(!). With obvious reason, this is a bad choice. 2.2.5 panics with a different reason. 2.2.6, 2.2.7, and 2.2.8 boot kernels but shut down at the same place, i. e., probing sc0 -> kdbio test. From FreeBSD-3, the symptom is basically the same as reported here. DragonFlyBSD suffers the same problem because of the similarities in kernel init process. Initially I thought loader is culprit but it doesn't seem so. In -STABLE and -CURRENT, I traced it down to cninit() call from hammer_time() and init386() in src/sys/amd64/amd64/machdep.c and src/sys/i386/i386/machdep.c. It seems one of hard-wired ISA hacks for vidconsole is responsible, probably keyboard hacks. I am stuck at this point because of the tangled web of kludges. :-( FYI, there is no serial port on the laptop, so comconsole is not an option. I hope it helps, Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 18:50:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F12E16A4CE for ; Sat, 26 Jun 2004 18:50:35 +0000 (GMT) Received: from wizkid.homeip.net (wizkid.homeip.net [213.238.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C85EE43D39 for ; Sat, 26 Jun 2004 18:50:34 +0000 (GMT) (envelope-from me@wizkid.homeip.net) Received: from amavis by wizkid.homeip.net with scanned-ok (Exim 3.36 #1 (Debian)) id 1BeIEa-0006RE-00; Sat, 26 Jun 2004 20:49:04 +0200 Received: from wizkid.homeip.net ([127.0.0.1]) by localhost (darkstar [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24367-09; Sat, 26 Jun 2004 20:48:54 +0200 (CEST) Received: from thakisis ([192.168.1.25] helo=wizkid.homeip.net) by wizkid.homeip.net with esmtp (Exim 3.36 #1 (Debian)) id 1BeIEQ-0006R4-00; Sat, 26 Jun 2004 20:48:54 +0200 Message-ID: <40DDC516.5000309@wizkid.homeip.net> Date: Sat, 26 Jun 2004 20:48:54 +0200 From: me User-Agent: Mozilla Thunderbird 0.5 (X11/20040306) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim References: <20040504194803.GA94861@stack.nl> <4097F65A.3000709@DeepCore.dk> <20040511165044.GA52478@stack.nl> <20040511190859.GA80652@dragon.nuxi.com> <20040511193404.GA56219@stack.nl> <20040511194308.GB14683@dragon.nuxi.com> <20040511201156.GA57223@stack.nl> <20040511205725.GA57636@stack.nl> <20040512022938.GA23426@dragon.nuxi.com> <20040526190653.GA1508@stack.nl> <20040622161301.GA780@stack.nl> In-Reply-To: <20040622161301.GA780@stack.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at wizkid.homeip.net cc: freebsd-amd64@freebsd.org Subject: Re: ATA driver cannot detect the Serial ATA disk in FreeBSD/AMD64-Current X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2004 18:50:35 -0000 Hi, running a generic Kernel with onboard Sata in non-Raid mode and all drives are found and usable on a Tyan Thunder K8S Pro S2882UG3NR. Maybe you have enabled Raid-mode in Bios, try to disable it. \ruediger Marc Olzheim wrote: > On Wed, May 26, 2004 at 09:06:53PM +0200, Marc Olzheim wrote: > >>On Tue, May 11, 2004 at 07:29:38PM -0700, David O'Brien wrote: >> >>>On Tue, May 11, 2004 at 10:57:25PM +0200, Marc Olzheim wrote: >>> >>>>Alas, to no avail... >>>>http://www.stack.nl/~marcolz/FreeBSD/hammer.bootlog.broken.20040511.newbios.txt >>> >>>:-( >> >>Anyone with any new ideas to try ? Tried today's kernel to no avail >>again... > > > Upgraded my Tyan 2885 to Bios 2.02 but still no SATA in a new kernel... > > Marc > _______________________________________________ > 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-amd64@FreeBSD.ORG Sat Jun 26 22:58:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDFC016A4CE for ; Sat, 26 Jun 2004 22:58:09 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49C4543D41 for ; Sat, 26 Jun 2004 22:58:09 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mailhost.stack.nl (Postfix) with ESMTP id 218651F101; Sun, 27 Jun 2004 00:57:48 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 333) id 035171CD92; Sun, 27 Jun 2004 00:57:47 +0200 (CEST) Date: Sun, 27 Jun 2004 00:57:47 +0200 From: Marc Olzheim To: me Message-ID: <20040626225747.GA52328@stack.nl> References: <20040511165044.GA52478@stack.nl> <20040511190859.GA80652@dragon.nuxi.com> <20040511193404.GA56219@stack.nl> <20040511194308.GB14683@dragon.nuxi.com> <20040511201156.GA57223@stack.nl> <20040511205725.GA57636@stack.nl> <20040512022938.GA23426@dragon.nuxi.com> <20040526190653.GA1508@stack.nl> <20040622161301.GA780@stack.nl> <40DDC516.5000309@wizkid.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40DDC516.5000309@wizkid.homeip.net> X-Operating-System: FreeBSD turtle.stack.nl 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: ATA driver cannot detect the Serial ATA disk in FreeBSD/AMD64-Current X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2004 22:58:10 -0000 On Sat, Jun 26, 2004 at 08:48:54PM +0200, me wrote: > Hi, > > running a generic Kernel with onboard Sata in non-Raid mode and all > drives are found and usable on a Tyan Thunder K8S Pro S2882UG3NR. > Maybe you have enabled Raid-mode in Bios, try to disable it. Nope... As said, a -current of april third works ok. Something broke halfway april with the driver rewrite... Marc From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 23:25:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BD7A16A4CE for ; Sat, 26 Jun 2004 23:25:25 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5010243D1D for ; Sat, 26 Jun 2004 23:25: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 i5QNOUTP012512; Sat, 26 Jun 2004 16:24:30 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i5QNOTAQ012511; Sat, 26 Jun 2004 16:24:29 -0700 (PDT) (envelope-from obrien) Date: Sat, 26 Jun 2004 16:24:29 -0700 From: "David O'Brien" To: Justin Hopper Message-ID: <20040626232429.GD11573@dragon.nuxi.com> References: <1087967700.18067.403.camel@work.gusalmighty.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1087967700.18067.403.camel@work.gusalmighty.com> 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: freebsd-amd64@freebsd.org Subject: Re: freebsd-amd64 threading issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2004 23:25:25 -0000 On Tue, Jun 22, 2004 at 10:15:00PM -0700, Justin Hopper wrote: > I haven't seen any further talk about the threading problem running > MySQL on freebsd-amd64. Has anyone made any more progress on this? We > are due to receive our first Dual or Quad Opteron box here shortly, and > I'm concerned I will not be able to run freebsd-amd64, as the box will > need all the DB horsepower it can get. I thought the threading problem was resolved. You need to run 5-CURRENT though, 5.2.1-RELEASE has threading problems. I'll see about building a new AMD64 snapshot this coming week, but with USENIX going on it might take 2 weeks to get it out. -- -- David (obrien@FreeBSD.org)