From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 5 03:32:57 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 617B716A4CE; Sun, 5 Sep 2004 03:32:57 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 147C943D31; Sun, 5 Sep 2004 03:32:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id i853WuB4068675; Sat, 4 Sep 2004 23:32:56 -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 i853WuP4065293; Sat, 4 Sep 2004 23:32:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4DE867303F; Sat, 4 Sep 2004 23:32:56 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040905033256.4DE867303F@freebsd-current.sentex.ca> Date: Sat, 4 Sep 2004 23:32:56 -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, 05 Sep 2004 03:32:57 -0000 TB --- 2004-09-05 02:25:13 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-09-05 02:25:13 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-09-05 02:25:13 - checking out the source tree TB --- 2004-09-05 02:25:13 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-09-05 02:25:13 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-09-05 02:30:23 - building world (CFLAGS=-O2 -pipe) TB --- 2004-09-05 02:30:23 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-09-05 02:30:23 - /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 [...] cc -O2 -pipe -DNOI4B -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadHeader': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:447: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:451: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadName': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:462: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 4) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin. *** 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-09-05 03:32:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-09-05 03:32:56 - ERROR: failed to build world TB --- 2004-09-05 03:32:56 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 5 13:32:05 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 B75FF16A4CE; Sun, 5 Sep 2004 13:32:05 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5371443D1D; Sun, 5 Sep 2004 13:32:05 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id i85DW448029101; Sun, 5 Sep 2004 09:32:04 -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 i85DW4U3015284; Sun, 5 Sep 2004 09:32:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B59EE7303F; Sun, 5 Sep 2004 09:32:04 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040905133204.B59EE7303F@freebsd-current.sentex.ca> Date: Sun, 5 Sep 2004 09:32:04 -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, 05 Sep 2004 13:32:05 -0000 TB --- 2004-09-05 12:22:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-09-05 12:22:06 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-09-05 12:22:06 - checking out the source tree TB --- 2004-09-05 12:22:06 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-09-05 12:22:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-09-05 12:28:18 - building world (CFLAGS=-O2 -pipe) TB --- 2004-09-05 12:28:18 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-09-05 12:28:18 - /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 [...] cc -O2 -pipe -DNOI4B -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadHeader': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:447: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:451: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadName': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:462: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 4) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin. *** 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-09-05 13:32:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-09-05 13:32:04 - ERROR: failed to build world TB --- 2004-09-05 13:32:04 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 5 16:39:09 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C93C916A4CE for ; Sun, 5 Sep 2004 16:39:09 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD48943D58 for ; Sun, 5 Sep 2004 16:39:09 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 0AF4155433 for ; Sun, 5 Sep 2004 16:39:04 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A34F16A4CE for ; Sun, 5 Sep 2004 16:39:04 +0000 (GMT) Received: from lorax.ldc.upenn.edu (lorax.LDC.upenn.edu [158.130.16.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D35743D2D for ; Sun, 5 Sep 2004 16:39:03 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: by lorax.ldc.upenn.edu (Postfix, from userid 32822) id D2B64228C9; Sun, 5 Sep 2004 12:39:02 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by lorax.ldc.upenn.edu (Postfix) with ESMTP id CB762228C4 for ; Sun, 5 Sep 2004 12:39:02 -0400 (EDT) Date: Sun, 5 Sep 2004 12:39:02 -0400 (EDT) From: "Jason M. Leonard" To: freebsd-amd64@lists.freebsd.org Message-ID: <20040905123829.D51907@lorax.ldc.upenn.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 3ware (twe, twa) support for AMD64 in 5.3? 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: Sun, 05 Sep 2004 16:39:09 -0000 I found a couple of threads related to this: http://lists.freebsd.org/pipermail/freebsd-amd64/2004-June/001583.html http://lists.freebsd.org/pipermail/freebsd-amd64/2004-July/001663.html Neither seems conclusive enough to make a purchasing decision. But this file, /usr/src/release/doc/share/misc/dev.archlist.txt dated today, tells me this: twa i386,amd64 twe i386,amd64 I have two questions: 1. Are the 3ware drivers ready for production on AMD64? 2. Will the CLI utilities run on AMD64? :Fuzz From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 5 23:14: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 DDEC416A4CE; Sun, 5 Sep 2004 23:14:29 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CD2D43D49; Sun, 5 Sep 2004 23:14:29 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id i85NESEB078769; Sun, 5 Sep 2004 19:14:28 -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 i85NESK8020528; Sun, 5 Sep 2004 19:14:28 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9ECFF7303F; Sun, 5 Sep 2004 19:14:28 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040905231428.9ECFF7303F@freebsd-current.sentex.ca> Date: Sun, 5 Sep 2004 19:14:28 -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, 05 Sep 2004 23:14:30 -0000 TB --- 2004-09-05 22:06:55 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-09-05 22:06:55 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-09-05 22:06:55 - checking out the source tree TB --- 2004-09-05 22:06:55 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-09-05 22:06:55 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-09-05 22:12:08 - building world (CFLAGS=-O2 -pipe) TB --- 2004-09-05 22:12:08 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-09-05 22:12:08 - /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 [...] cc -O2 -pipe -DNOI4B -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadHeader': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:447: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:451: warning: unsigned int format, different type arg (arg 4) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c: In function `auth_ReadName': /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:462: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp/auth.c:468: warning: unsigned int format, different type arg (arg 4) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin/ppp. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/usr.sbin. *** 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-09-05 23:14:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-09-05 23:14:28 - ERROR: failed to build world TB --- 2004-09-05 23:14:28 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 02:13: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 2E16D16A4CE for ; Mon, 6 Sep 2004 02:13:26 +0000 (GMT) Received: from lakermmtao05.cox.net (lakermmtao05.cox.net [68.230.240.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id B261A43D48 for ; Mon, 6 Sep 2004 02:13:25 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao05.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040906021326.IQLG25497.lakermmtao05.cox.net@dolphin.local.net> for ; Sun, 5 Sep 2004 22:13:26 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id i862DOrH012845 for ; Sun, 5 Sep 2004 21:13:24 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sun, 5 Sep 2004 21:13:19 -0500 From: "Conrad J. Sabatier" To: freebsd-amd64@freebsd.org Message-Id: <20040905211319.234725bc@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; amd64-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: linux base for amd64 must be Slackware? 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, 06 Sep 2004 02:13:26 -0000 Is there any particular reason why the website describing setting up Linux emulation for amd64 recommends using Slackware as the base? Will any of the linux_base* ports work instead? -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 02:33: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 0D16716A4CE for ; Mon, 6 Sep 2004 02:33:38 +0000 (GMT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0A9443D39 for ; Mon, 6 Sep 2004 02:33:37 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.40.26) by smtp01.syd.iprimus.net.au (7.0.028) id 412F6C1400315C70; Mon, 6 Sep 2004 12:33:29 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 4FE75420E; Mon, 6 Sep 2004 12:33:32 +1000 (EST) Date: Mon, 6 Sep 2004 12:33:32 +1000 From: Tim Robbins To: "Conrad J. Sabatier" Message-ID: <20040906023332.GA99335@cat.robbins.dropbear.id.au> References: <20040905211319.234725bc@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040905211319.234725bc@dolphin.local.net> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: linux base for amd64 must be Slackware? 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, 06 Sep 2004 02:33:38 -0000 On Sun, Sep 05, 2004 at 09:13:19PM -0500, Conrad J. Sabatier wrote: > Is there any particular reason why the website describing setting up > Linux emulation for amd64 recommends using Slackware as the base? Will > any of the linux_base* ports work instead? At the time it was written, the ports collection had not been updated to deal with 32-bit Linux emulation on amd64, and Slackware was the easiest to get started with. I assume the linux_base port works on amd64 after David O'Brien's recent change, but I haven't gotten around to testing it yet -- if it works, I'll update the web page suggesting that people use it instead of tediously installing Slackware by hand. Tim From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 04:59:49 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 8E17016A4CE; Mon, 6 Sep 2004 04:59:49 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 651DC43D1D; Mon, 6 Sep 2004 04:59:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.13.1/8.12.11) with ESMTP id i864wNXM021999; Sun, 5 Sep 2004 21:58:24 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i864wNgN021998; Sun, 5 Sep 2004 21:58:23 -0700 (PDT) (envelope-from obrien) Date: Sun, 5 Sep 2004 21:58:23 -0700 From: "David O'Brien" To: Tim Robbins Message-ID: <20040906045823.GA21935@dragon.nuxi.com> References: <20040905211319.234725bc@dolphin.local.net> <20040906023332.GA99335@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040906023332.GA99335@cat.robbins.dropbear.id.au> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-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: linux base for amd64 must be Slackware? 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: Mon, 06 Sep 2004 04:59:49 -0000 On Mon, Sep 06, 2004 at 12:33:32PM +1000, Tim Robbins wrote: > I assume the linux_base port works on amd64 after David O'Brien's > recent change, but I haven't gotten around to testing it yet -- if it > works, It probably doesn't work yet. It would be great if someone could give it a try and polish it off. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 06:07:45 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 9C83E16A4D0 for ; Mon, 6 Sep 2004 06:07:45 +0000 (GMT) Received: from astra.telenet-ops.be (astra.telenet-ops.be [195.130.132.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1DE043D49 for ; Mon, 6 Sep 2004 06:07:44 +0000 (GMT) (envelope-from brampie@no-wackos.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by astra.telenet-ops.be (Postfix) with SMTP id AB8E132805A for ; Mon, 6 Sep 2004 08:07:41 +0200 (MEST) Received: from [192.168.1.102] (d51A5479A.kabel.telenet.be [81.165.71.154]) by astra.telenet-ops.be (Postfix) with ESMTP id 9A6B6328025 for ; Mon, 6 Sep 2004 08:07:41 +0200 (MEST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <0FC266BD-FFCB-11D8-8D56-000D93B0200E@no-wackos.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@FreeBSD.org From: bram Date: Mon, 6 Sep 2004 08:07:41 +0200 X-Mailer: Apple Mail (2.619) Subject: Newbie question 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, 06 Sep 2004 06:07:45 -0000 Hi all I've just installed freebsd AMD64 and have come to the (maybe wrong) conclusion that you cannot run 32 bit software on it. whenever I try to compile for i386 freebsd something it says I do not have i386 and therefor cannot he cannot compile. A programmer that I know says that c code is not processor specific and also that the amd64 support 32 bit applications. So I ask you, what is the problem here and how can I solve it. programs wich are a problem here are MySQL and hotline for unix. can't I just say something like: compile 32 bit ? sorry for my english and my maybe stupid question bram From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 07:13:06 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 4ACC116A4CE; Mon, 6 Sep 2004 07:13:06 +0000 (GMT) Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73C843D58; Mon, 6 Sep 2004 07:13:05 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [194.97.55.192] (helo=mx8.freenet.de) by mout0.freenet.de with asmtp (Exim 4.41) id 1C4DgW-0005Bd-RV; Mon, 06 Sep 2004 09:13:04 +0200 Received: from pd9ead067.dip0.t-ipconnect.de ([217.234.208.103] helo=amd64.bsdnet.)4.42 #2) id 1C4DgW-0007j1-It; Mon, 06 Sep 2004 09:13:04 +0200 Date: Mon, 6 Sep 2004 09:13:12 +0200 From: Manuel =?ISO-8859-1?Q?St=FChn?= To: obrien@freebsd.org Message-Id: <20040906091312.42eb6164.freebsdnewbie@freenet.de> In-Reply-To: <20040906045823.GA21935@dragon.nuxi.com> References: <20040905211319.234725bc@dolphin.local.net> <20040906023332.GA99335@cat.robbins.dropbear.id.au> <20040906045823.GA21935@dragon.nuxi.com> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; amd64-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: linux base for amd64 must be Slackware? 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, 06 Sep 2004 07:13:06 -0000 Am Sun, 5 Sep 2004 21:58:23 -0700 schrieb "David O'Brien" : > On Mon, Sep 06, 2004 at 12:33:32PM +1000, Tim Robbins wrote: > > I assume the linux_base port works on amd64 after David O'Brien's > > recent change, but I haven't gotten around to testing it yet -- if > > it works, > > It probably doesn't work yet. It would be great if someone could give > it a try and polish it off. I've installed the linux_base by adding "-noscripts" at the RPMFLAGS-Section of the Makefile. I don't know whether it's a hack or not, but until now it works for me. The following ports are installed and functional: linux-sun-jdk-1.4.2.05 Sun Java Development Kit 1.4 for Linux linux_base-7.1_7 The base set of packages needed in Linux mode de-staroffice-7.0_3 Wordprocessor/dbase/spreadheet/drawing/chart acroread-5.09 View, distribute and print PDF documents And linux-eagle-4.13 is installed without ports and works also. #uname -a FreeBSD AMD64.BSDNet 5.3-BETA3 FreeBSD 5.3-BETA3 #0: Sat Sep 4 10:13:55 CEST 2004 manuel@AMD64.BSDNet:/usr/obj/usr/src/sys/SCHED_ULE amd64 FreeBSD 5.3-BETA3 amd64 Manuel -- If you can't learn to do it well, learn to enjoy doing it badly. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 08:54: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 808B416A4CE for ; Mon, 6 Sep 2004 08:54:15 +0000 (GMT) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id 51CFB43D41 for ; Mon, 6 Sep 2004 08:54:14 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 32662 invoked from network); 6 Sep 2004 08:54:12 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by salvador with SMTP; 6 Sep 2004 08:54:12 -0000 Received: from [192.168.0.107] ([210.24.202.141]) by maxwell2.pacific.net.sg with ESMTP <20040906085412.VRWX1154.maxwell2.pacific.net.sg@[192.168.0.107]>; Mon, 6 Sep 2004 16:54:12 +0800 Message-ID: <413C25AE.8060400@pacific.net.sg> Date: Mon, 06 Sep 2004 16:54:06 +0800 From: Erich Dollansky User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040714) X-Accept-Language: en-us, en MIME-Version: 1.0 To: bram References: <0FC266BD-FFCB-11D8-8D56-000D93B0200E@no-wackos.com> In-Reply-To: <0FC266BD-FFCB-11D8-8D56-000D93B0200E@no-wackos.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: Newbie question 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, 06 Sep 2004 08:54:15 -0000 Hi, bram wrote: > Hi all > > I've just installed freebsd AMD64 and have come to the (maybe wrong) > conclusion that you cannot run 32 bit software on it. I think that you are right for the moment if you talk about the mix of 32 and 64 bit applications. > whenever I try to compile for i386 freebsd something it says I do not > have i386 and therefor cannot he cannot compile. > A programmer that I know says that c code is not processor specific and > also that the amd64 support 32 bit applications. It would be so nice of this would be true. > So I ask you, what is the problem here and how can I solve it. > programs wich are a problem here are MySQL and hotline for unix. > can't I just say something like: compile 32 bit ? > You have two options. One is that there is a 64 bit port available, the other one is that you install the 32 bit version of FreeBSD on your machine. Erich From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 11:01:20 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 224F816A4CE for ; Mon, 6 Sep 2004 11:01:20 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14F0143D1D for ; Mon, 6 Sep 2004 11:01:20 +0000 (GMT) (envelope-from tomaz.borstnar@over.net) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 0652855830 for ; Mon, 6 Sep 2004 11:01:20 +0000 (GMT) (envelope-from tomaz.borstnar@over.net) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3E2016A4CF for ; Mon, 6 Sep 2004 11:01:19 +0000 (GMT) Received: from game.over.net (game.over.net [193.189.169.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6787043D2D for ; Mon, 6 Sep 2004 11:01:17 +0000 (GMT) (envelope-from tomaz.borstnar@over.net) Received: from cable13-82.ljk.voljatel.net ([217.72.82.13]:11650 "EHLO masina.over.net") by game.over.net with ESMTP id ; Mon, 6 Sep 2004 13:00:58 +0200 Message-Id: <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> X-Sender: tmail@193.189.169.9 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sun, 05 Sep 2004 23:20:44 +0200 To: "Jason M. Leonard" From: Tomaz Borstnar In-Reply-To: <20040905123829.D51907@lorax.ldc.upenn.edu> References: <20040905123829.D51907@lorax.ldc.upenn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-OverNet-MailScanner-Information: Contact mailscanner@over.net for more information X-OverNet-MailScanner: Found to be clean X-OverNet-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.354, required 5, BAYES_00 -4.90, DATE_IN_PAST_12_24 0.75, RCVD_IN_NJABL_DUL 1.71, RCVD_IN_SORBS_DUL 0.09) X-MailScanner-From: tomaz.borstnar@over.net cc: freebsd-amd64@lists.freebsd.org Subject: Re: 3ware (twe, twa) support for AMD64 in 5.3? 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, 06 Sep 2004 11:01:20 -0000 At 18:39 5.9.2004, Jason M. Leonard wrote: >1. Are the 3ware drivers ready for production on AMD64? so far twa seem to work OK on 5.3beta. Will test it more extensively in future. >2. Will the CLI utilities run on AMD64? Hmm, i can check that one of these days. Tomaz From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 11:02:49 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 DE43216A4CF for ; Mon, 6 Sep 2004 11:02:49 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26DE43D1D for ; Mon, 6 Sep 2004 11:02:49 +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 i86B2np2094348 for ; Mon, 6 Sep 2004 11:02:49 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i86B2mTj094342 for freebsd-amd64@freebsd.org; Mon, 6 Sep 2004 11:02:48 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Sep 2004 11:02:48 GMT Message-Id: <200409061102.i86B2mTj094342@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, 06 Sep 2004 11:02:50 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/08/31] amd64/71173 amd64 nfs writing problems on exported msdosfs 4 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve 6 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 11:45: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 7763716A4CE; Mon, 6 Sep 2004 11:45:51 +0000 (GMT) Received: from mailhost.m5p.com (209-162-215-52.dq1sn.easystreet.com [209.162.215.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECBC543D1F; Mon, 6 Sep 2004 11:45:50 +0000 (GMT) (envelope-from george@m5p.com) Received: from m5p.com (ssh.m5p.com [IPv6:2001:418:3fd::fb]) by mailhost.m5p.com (8.12.11/8.12.11) with ESMTP id i86Bjndq004580 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=OK); Mon, 6 Sep 2004 04:45:50 -0700 (PDT) Received: (from george@localhost) by m5p.com (8.12.11/8.12.11/Submit) id i86BjnID008866; Mon, 6 Sep 2004 04:45:49 -0700 (PDT) Date: Mon, 6 Sep 2004 04:45:49 -0700 (PDT) From: George Mitchell Message-Id: <200409061145.i86BjnID008866@m5p.com> To: bugmaster@freebsd.org, freebsd-amd64@freebsd.org In-Reply-To: <200409061102.i86B2mTj094342@freefall.freebsd.org> X-Scanned-By: MIMEDefang 2.43 Subject: Re: 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, 06 Sep 2004 11:45:51 -0000 Re: amd64/67745: To the best of my knowledge, the Presario R3000Z has an 32-bit Athlon processor, not a 64-bit. -- George From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 12:21: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 852B316A4CE for ; Mon, 6 Sep 2004 12:21:17 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 410D843D39 for ; Mon, 6 Sep 2004 12:21:15 +0000 (GMT) (envelope-from zparta@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so179143rnk for ; Mon, 06 Sep 2004 05:21:13 -0700 (PDT) Received: by 10.38.125.73 with SMTP id x73mr1401467rnc; Mon, 06 Sep 2004 05:21:12 -0700 (PDT) Received: by 10.38.9.56 with HTTP; Mon, 6 Sep 2004 05:21:12 -0700 (PDT) Message-ID: <3b41db8504090605217fc0a352@mail.gmail.com> Date: Mon, 6 Sep 2004 14:21:12 +0200 From: Jens Holmqvist To: George Mitchell In-Reply-To: <200409061145.i86BjnID008866@m5p.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200409061102.i86B2mTj094342@freefall.freebsd.org> <200409061145.i86BjnID008866@m5p.com> cc: bugmaster@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jens Holmqvist List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 12:21:17 -0000 the R3000Z do have a 64-bit CPU heres a (long)link http://www.shopping.hp.com/webapp/shopping/computer_series.do?series_name=R3000Z_series&brandName=compaq&category=%2Fnotebooks%2Fcompaq_presario%2F&catLevel=2&storeName=computer_store On Mon, 6 Sep 2004 04:45:49 -0700 (PDT), George Mitchell wrote: > Re: amd64/67745: To the best of my knowledge, the Presario R3000Z has an > 32-bit Athlon processor, not a 64-bit. -- George > > > _______________________________________________ > 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 Mon Sep 6 12:52: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 13D6916A4CE for ; Mon, 6 Sep 2004 12:52:01 +0000 (GMT) Received: from kelmis.telenet-ops.be (kelmis.telenet-ops.be [195.130.132.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id D34B943D31 for ; Mon, 6 Sep 2004 12:52:00 +0000 (GMT) (envelope-from brampie@no-wackos.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by kelmis.telenet-ops.be (Postfix) with SMTP id 4B65537EC9 for ; Mon, 6 Sep 2004 14:51:57 +0200 (MEST) Received: from [192.168.1.102] (d51A5479A.kabel.telenet.be [81.165.71.154]) by kelmis.telenet-ops.be (Postfix) with ESMTP id 2A93537F04 for ; Mon, 6 Sep 2004 14:51:57 +0200 (MEST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <8933C971-0003-11D9-A1F3-000D93B0200E@no-wackos.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@FreeBSD.org From: bram Date: Mon, 6 Sep 2004 14:51:57 +0200 X-Mailer: Apple Mail (2.619) Subject: RE : Newbie question 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, 06 Sep 2004 12:52:01 -0000 Hi Thank you very much for yur clear advice but: Isn't there a workaround for this, I am a experienced mac user and have two G5 machines these work on the PPC950 wich is 64bit, on this machine you can mix 32bit with 64 bit indicating that this would be possible. I would still prefer to use the 64bit version, so maybe you know wether MySQL is a good option (on AMD64) I've also read that POSTGRESQL is 64 runable but I am new to all this so I am open for suggestions. Also I would like to install a filesharing protocol on it. Since netatalk doesn't seems to work on AMD64 (I think) What would be another good option for both inter- and intranet preferably not nfs or Samba. I would appreciate if you could answer these questions and give me some advice. bram Op 6-sep-04 om 10:54 heeft Erich Dollansky het volgende geschreven: > Hi, > > bram wrote: >> Hi all >> I've just installed freebsd AMD64 and have come to the (maybe wrong) >> conclusion that you cannot run 32 bit software on it. > > I think that you are right for the moment if you talk about the mix of > 32 and 64 bit applications. > >> whenever I try to compile for i386 freebsd something it says I do not >> have i386 and therefor cannot he cannot compile. >> A programmer that I know says that c code is not processor specific >> and also that the amd64 support 32 bit applications. > > It would be so nice of this would be true. > >> So I ask you, what is the problem here and how can I solve it. >> programs wich are a problem here are MySQL and hotline for unix. >> can't I just say something like: compile 32 bit ? > You have two options. One is that there is a 64 bit port available, > the other one is that you install the 32 bit version of FreeBSD on > your machine. > > Erich > From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 14:00:52 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 445B616A4CE for ; Mon, 6 Sep 2004 14:00:52 +0000 (GMT) Received: from beer.ux6.net (beer.ux6.net [64.62.253.29]) by mx1.FreeBSD.org (Postfix) with SMTP id 2D4C043D41 for ; Mon, 6 Sep 2004 14:00:52 +0000 (GMT) (envelope-from miha@ghuug.org) Received: (qmail 64799 invoked by uid 113); 6 Sep 2004 07:00:50 -0700 Received: from miha@ghuug.org by beer.ux6.net by uid 112 with qmail-scanner-1.22 Clear:RC:0(205.177.65.128):SA:0(0.0/6.0):. Processed in 0.918683 secs); 06 Sep 2004 14:00:50 -0000 X-Spam-Status: No, hits=0.0 required=6.0 Received: from unknown (HELO ?192.168.0.3?) (miha@beer.ux6.net@205.177.65.128) by localhost with SMTP; 6 Sep 2004 07:00:49 -0700 From: "Mikhail P." Organization: Ghana Unix Users Group To: freebsd-amd64@freebsd.org Date: Mon, 6 Sep 2004 14:00:46 +0000 User-Agent: KMail/1.6.2 References: <8933C971-0003-11D9-A1F3-000D93B0200E@no-wackos.com> In-Reply-To: <8933C971-0003-11D9-A1F3-000D93B0200E@no-wackos.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <200409061400.46786.miha@ghuug.org> cc: bram Subject: Re: Newbie question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: miha@ghuug.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 14:00:52 -0000 I have played a bit with AMD64 in 64bit mode and binaries from x86 system - I think you may run these buy putting corresponding libraries into /compat/ia32/ (which is *I think* serves as a root for x86 compat files, similar to linux emulation). I'm unsure about this thought - perhaps someone more knowledgeable should make a comment here. regards, M. On Monday 06 September 2004 12:51, bram wrote: > Hi > > Thank you very much for yur clear advice but: > > Isn't there a workaround for this, I am a experienced mac user and have > two G5 machines > these work on the PPC950 wich is 64bit, on this machine you can mix > 32bit with 64 bit indicating that this would be possible. > > I would still prefer to use the 64bit version, so maybe you know wether > MySQL is a good option (on AMD64) > I've also read that POSTGRESQL is 64 runable but I am new to all this > so I am open for suggestions. > > Also I would like to install a filesharing protocol on it. Since > netatalk doesn't seems to work on AMD64 (I think) > What would be another good option for both inter- and intranet > preferably not nfs or Samba. > > I would appreciate if you could answer these questions and give me some > advice. > > bram > > Op 6-sep-04 om 10:54 heeft Erich Dollansky het volgende geschreven: > > Hi, > > > > bram wrote: > >> Hi all > >> I've just installed freebsd AMD64 and have come to the (maybe wrong) > >> conclusion that you cannot run 32 bit software on it. > > > > I think that you are right for the moment if you talk about the mix of > > 32 and 64 bit applications. > > > >> whenever I try to compile for i386 freebsd something it says I do not > >> have i386 and therefor cannot he cannot compile. > >> A programmer that I know says that c code is not processor specific > >> and also that the amd64 support 32 bit applications. > > > > It would be so nice of this would be true. > > > >> So I ask you, what is the problem here and how can I solve it. > >> programs wich are a problem here are MySQL and hotline for unix. > >> can't I just say something like: compile 32 bit ? > > > > You have two options. One is that there is a 64 bit port available, > > the other one is that you install the 32 bit version of FreeBSD on > > your machine. > > > > Erich > > _______________________________________________ > 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 Mon Sep 6 16:51:41 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 E622216A4CE for ; Mon, 6 Sep 2004 16:51:41 +0000 (GMT) Received: from smtp1.mc.surewest.net (smtp1.mc.surewest.net [66.60.130.50]) by mx1.FreeBSD.org (Postfix) with SMTP id A574843D5A for ; Mon, 6 Sep 2004 16:51:41 +0000 (GMT) (envelope-from avoozl@surewest.net) Received: (s3-8460); Mon, 06 Sep 2004 09:48:35 -0700 Received: from unknown (HELO avoozl) (66.60.134.178) by smtp1.mc.surewest.net (s3-smtpd/0.90-beta3) with SMTP; Mon, 06 Sep 2004 09:48:34 -0700 Message-ID: <003101c49431$ca5b35a0$0400a8c0@avoozl> From: "Chris F. Willoughby" To: "George Mitchell" , , References: <200409061145.i86BjnID008866@m5p.com> Date: Mon, 6 Sep 2004 09:51:43 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-TST: smtp1 SNWK3 0.31-80 ip=66.60.134.178 Subject: Re: 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, 06 Sep 2004 16:51:42 -0000 I double checked on the Compaq website. It appears that that particular system can be loaded with either the Athlon 64 or the Athlon XP-M. The A64 is the default. --Chris ----- Original Message ----- From: "George Mitchell" To: ; Sent: Monday, September 06, 2004 4:45 AM Subject: Re: Current problem reports assigned to you > Re: amd64/67745: To the best of my knowledge, the Presario R3000Z has an > 32-bit Athlon processor, not a 64-bit. -- George > From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 18:27:04 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 E0EAB16A4CE for ; Mon, 6 Sep 2004 18:27:04 +0000 (GMT) Received: from lakermmtao05.cox.net (lakermmtao05.cox.net [68.230.240.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6848F43D2F for ; Mon, 6 Sep 2004 18:27:04 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao05.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040906182704.PKMC25497.lakermmtao05.cox.net@dolphin.local.net> for ; Mon, 6 Sep 2004 14:27:04 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id i86IR3Tm026242 for ; Mon, 6 Sep 2004 13:27:03 -0500 (CDT) (envelope-from conrads@cox.net) Date: Mon, 6 Sep 2004 13:26:58 -0500 From: "Conrad J. Sabatier" To: freebsd-amd64@freebsd.org Message-ID: <20040906132658.447c574f@dolphin.local.net> In-Reply-To: <20040906091312.42eb6164.freebsdnewbie@freenet.de> References: <20040905211319.234725bc@dolphin.local.net> <20040906023332.GA99335@cat.robbins.dropbear.id.au> <20040906045823.GA21935@dragon.nuxi.com> <20040906091312.42eb6164.freebsdnewbie@freenet.de> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: linux base for amd64 must be Slackware? 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, 06 Sep 2004 18:27:05 -0000 On Mon, 6 Sep 2004 09:13:12 +0200 Manuel St=FChn wrote: > Am Sun, 5 Sep 2004 21:58:23 -0700 > schrieb "David O'Brien" : >=20 > > On Mon, Sep 06, 2004 at 12:33:32PM +1000, Tim Robbins wrote: > > > I assume the linux_base port works on amd64 after David O'Brien's > > > recent change, but I haven't gotten around to testing it yet -- if > > > it works, > >=20 > > It probably doesn't work yet. It would be great if someone could > > give it a try and polish it off. >=20 > I've installed the linux_base by adding "-noscripts" at the > RPMFLAGS-Section of the Makefile. I don't know whether it's a hack > or not, but until now it works for me. Cool! It worked! (By the way, that's "--noscripts", with two hyphens). :-) I just did a "chroot /compat/linux /bin/bash" and it appears to be working fine. Thanks! --=20 Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 19:08: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 B6DAD16A4CE; Mon, 6 Sep 2004 19:08:00 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40EF243D5D; Mon, 6 Sep 2004 19:08:00 +0000 (GMT) (envelope-from andrew.lankford@verizon.net) Received: from outgoing.verizon.net ([192.168.1.2]) by out001.verizon.net ESMTP <20040906190759.OZYK24594.out001.verizon.net@outgoing.verizon.net>; Mon, 6 Sep 2004 14:07:59 -0500 X-Mailer: Openwave WebEngine, version 2.8.12 (webedge20-101-197-20030912) From: Andrew Lankford To: , Date: Mon, 6 Sep 2004 14:07:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [192.168.1.2] at Mon, 6 Sep 2004 14:07:59 -0500 Message-Id: <20040906190759.OZYK24594.out001.verizon.net@outgoing.verizon.net> cc: Scott Long Subject: Re: Latest MFSs break boot on amd64 notebook. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andrew.lankford@verizon.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 19:08:00 -0000 >I just tested the BETA3 shapshot that will be released >in the morning and everything works fine. The best >guess that I have is that you updated before all of the >work was committed to the tree. You should >be able to use the BETA3 disks to recover your system. > >Scott I burned BETA3-amd64-disc2 and tried booting from it. Again, regardless of what I tried, the computer locked up and then powered down before it got to the kernel copyright message. Unlike my last fateful build of the kernel however, the spinner got to "|" instead of just "-" or "/". I'm fighting the temptation to try BETA3-i386-disc2 to see if it does the same thing. Andrew Lankford From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 6 19:10: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 81FD116A4CE for ; Mon, 6 Sep 2004 19:10:43 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id F39CF43D54 for ; Mon, 6 Sep 2004 19:10:42 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040906191042.CWVM28752.lakermmtao08.cox.net@dolphin.local.net> for ; Mon, 6 Sep 2004 15:10:42 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id i86JAfRl026915 for ; Mon, 6 Sep 2004 14:10:41 -0500 (CDT) (envelope-from conrads@cox.net) Date: Mon, 6 Sep 2004 14:10:36 -0500 From: "Conrad J. Sabatier" To: freebsd-amd64@freebsd.org Message-ID: <20040906141036.475f0f96@dolphin.local.net> In-Reply-To: <20040906132658.447c574f@dolphin.local.net> References: <20040905211319.234725bc@dolphin.local.net> <20040906023332.GA99335@cat.robbins.dropbear.id.au> <20040906045823.GA21935@dragon.nuxi.com> <20040906091312.42eb6164.freebsdnewbie@freenet.de> <20040906132658.447c574f@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: linux base for amd64 must be Slackware? 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, 06 Sep 2004 19:10:43 -0000 On Mon, 6 Sep 2004 13:26:58 -0500 "Conrad J. Sabatier" wrote: > On Mon, 6 Sep 2004 09:13:12 +0200 > Manuel St=FChn wrote: >=20 > > Am Sun, 5 Sep 2004 21:58:23 -0700 > > schrieb "David O'Brien" : > >=20 > > > On Mon, Sep 06, 2004 at 12:33:32PM +1000, Tim Robbins wrote: > > > > I assume the linux_base port works on amd64 after David > > > > O'Brien's recent change, but I haven't gotten around to testing > > > > it yet -- if it works, > > >=20 > > > It probably doesn't work yet. It would be great if someone could > > > give it a try and polish it off. > >=20 > > I've installed the linux_base by adding "-noscripts" at the > > RPMFLAGS-Section of the Makefile. I don't know whether it's a hack > > or not, but until now it works for me. >=20 > Cool! It worked! (By the way, that's "--noscripts", with two > hyphens).:-) >=20 > I just did a "chroot /compat/linux /bin/bash" and it appears to be > working fine. >=20 > Thanks! One footnote: to get acroread to run, I first had to edit /compat/linux/etc/ld.so.conf and add: /lib /usr/lib /usr/X11R6/lib Then chroot as above and run "ldconfig". Otherwise, acroread complained that it couldn't find libXt.so.6. Once I had done the above procedure, it worked fine. Very nice! Great work, folks! --=20 Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 7 02: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 9C72616A4CF for ; Tue, 7 Sep 2004 02:55:37 +0000 (GMT) Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D1EF43D39 for ; Tue, 7 Sep 2004 02:55:37 +0000 (GMT) (envelope-from murrayp@rm-rstar.sfu.ca) Received: from cultus.sfu.ca (cultus.sfu.ca [142.58.101.5]) i872tZO2016512 for ; Mon, 6 Sep 2004 19:55:36 -0700 (PDT) Message-Id: <200409070255.i872tZO2016512@rm-rstar.sfu.ca> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: SFUwebmail 2.70 X-Sender: murrayp@popserver.sfu.ca To: freebsd-amd64@freebsd.org MIME-Version: 1.0 From: murrayp@sfu.ca Date: Mon, 06 Sep 2004 19:55:35 -0700 X-Virus-Scanned: by antibody.sfu.ca running antivirus scanner Subject: getting an amd64 system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: murrayp@sfu.ca List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 02:55:37 -0000 Hi, I'm thinking of purchasing a new amd64 system. I have used freeBSD on an amd64 for about 4-5 months now, so I am somewhat familiar with it, but I only know a bit. I am going to put freeBSD5.2.1 on the new system and I have a few concerns about some of the hardware on this new system: 1) This system comes with a DVDRW drive, I assume that burning DVD's is well defined (possible) by now is it? 2) I'm getting an Asus Radeon 9600XT 128MB AGP w/DVI for my video card. Is this supported, or is this a big mistake? If so, is there a comparable video card that is supported? 3) I am connecting to a wireless network. Is WiFi supported in 5.2.1? for any of the cards out there? If not, is WiFi supported in FreeBSD, period (ie: for any systems, including an i386, etc?) thanks very much, Murray From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 7 17:40:29 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 DC23A16A4D2 for ; Tue, 7 Sep 2004 17:40:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC8A743D60 for ; Tue, 7 Sep 2004 17:40:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i87HeSHg039328 for ; Tue, 7 Sep 2004 17:40:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i87HeS1R039327; Tue, 7 Sep 2004 17:40:28 GMT (envelope-from gnats) Resent-Date: Tue, 7 Sep 2004 17:40:28 GMT Resent-Message-Id: <200409071740.i87HeS1R039327@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Tomaz Borstnar Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A9BC16A4CF for ; Tue, 7 Sep 2004 17:33:00 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF9543D55 for ; Tue, 7 Sep 2004 17:33:00 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i87HWxW4097204 for ; Tue, 7 Sep 2004 17:32:59 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i87HWxjD097203; Tue, 7 Sep 2004 17:32:59 GMT (envelope-from nobody) Message-Id: <200409071732.i87HWxjD097203@www.freebsd.org> Date: Tue, 7 Sep 2004 17:32:59 GMT From: Tomaz Borstnar To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M 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, 07 Sep 2004 17:40:29 -0000 >Number: 71471 >Category: amd64 >Synopsis: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 07 17:40:28 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Tomaz Borstnar >Release: 5.3beta3-amd64 >Organization: >Environment: >Description: Trying to install official (miniinst) ISO of 5.3beta3-amd64 which ALWAYS fails during copyingfiles on mirror volume on ServeRAID-6m. Here are two attempts: ------- panic: ffs_valloc: dup alloc cpuid = 1 KDB: enter: panic [thread 100108] Stopped at kdb_enter+0x2f: nop db> where kdb_enter() at kdb_enter+0x2f panic() at panic+0x249 ffs_valloc() at ffs_valloc+0x684 ufs_mkdir() at ufs_mkdir+0x243 kern_mkdir() at kern_mkdir+0x243 syscall() at syscall+0x1fb Xfast_syscall() at XFast_syscall+0xa8 --- syscall (136, FreeBSD ELF64, mkdir), rip = 0x520ecc, rsp = 0x7fffffffe588, rbp = 0x803120 ----- Another attempt. Same volume, same settings except for soft-updates being off... Installation stopped by not being able to read from CD. After retrying to read the distribution again I got: panic: ufsdirhash_findslot: 'atacontrol' not found cpuid = 1 KDB enter: panic [thread 100076] Stopped at kdb_enter+0x2f: nop db> where kdb_enter() at kdb_enter+0x2f panic() at panic+0x249 ufsdirhash_findslot() at ufsdirhash_findslot+0xd3 ufsdirhash_remove() at ufsdirhash_remove+0x82 ufs_dirremove() at ufs_dirremove+0x1da ufs_remove() at ufs_remove+0x7d kern_unlink() at kern_unlink+0x1e5 unlink() at unlink+0x3e syscall() at syscall+0x4ab Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (10, FreeBSD ELF64, unlink)), rip = 0x521354, rsp = 0x7fffffffe588, rbp = 0x802070 --- db> >How-To-Repeat: Boot official mini inst ISO of 5.3beta3-amd64. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 7 22:15:28 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 02B3316A4CE for ; Tue, 7 Sep 2004 22:15:28 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id D471643D55 for ; Tue, 7 Sep 2004 22:15:27 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i87MH2aZ009035; Tue, 7 Sep 2004 15:17:02 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i87MH1hv009034; Tue, 7 Sep 2004 15:17:01 -0700 Date: Tue, 7 Sep 2004 15:17:01 -0700 From: Brooks Davis To: murrayp@sfu.ca Message-ID: <20040907221701.GB2826@odin.ac.hmc.edu> References: <200409070255.i872tZO2016512@rm-rstar.sfu.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes" Content-Disposition: inline In-Reply-To: <200409070255.i872tZO2016512@rm-rstar.sfu.ca> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: getting an amd64 system 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, 07 Sep 2004 22:15:28 -0000 --jq0ap7NbKX2Kqbes Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 06, 2004 at 07:55:35PM -0700, murrayp@sfu.ca wrote: > Hi, >=20 > I'm thinking of purchasing a new amd64 system. I have used freeBSD on an > amd64 for about 4-5 months now, so I am somewhat familiar with it, but I > only know a bit. I am going to put freeBSD5.2.1 on the new system and I > have a few concerns about some of the hardware on this new system: >=20 > 1) This system comes with a DVDRW drive, I assume that burning DVD's is w= ell > defined (possible) by now is it? burncd(8) should work for the actual burning. We don't currently have support for DVD+-RW optimized file systems. > 2) I'm getting an Asus Radeon 9600XT 128MB AGP w/DVI for my video card. = Is > this supported, or is this a big mistake? If so, is there a comparable > video card that is supported? I'm not really up on video hardware support, but just about everything will work with X. Accelleration may be another story. > 3) I am connecting to a wireless network. Is WiFi supported in 5.2.1? for > any of the cards out there? If not, is WiFi supported in FreeBSD, period > (ie: for any systems, including an i386, etc?) Many wireless devices are supported natively. The rest are generally supported in i386 mode using ndis(4) (aka project evil). Once 64-bit Windows support becomes common, amd64 ndis support will probably happen. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jq0ap7NbKX2Kqbes Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBPjNdXY6L6fI4GtQRAoudAKDVnK9giNuOcJpp2O63GQZe81ZwHwCfZjF5 TcgAdndqU9l2P7rYZktbCoI= =plQl -----END PGP SIGNATURE----- --jq0ap7NbKX2Kqbes-- From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 09:33:05 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 54DB316A4CE for ; Wed, 8 Sep 2004 09:33:05 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C780043D53 for ; Wed, 8 Sep 2004 09:33:04 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=[127.0.0.1]) by pandora.cs.kun.nl (8.12.10/4.13) with ESMTP id i889X3AV021217 for ; Wed, 8 Sep 2004 11:33:03 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 8 Sep 2004 11:33:02 +0200 User-Agent: KMail/1.6.2 References: <200409070255.i872tZO2016512@rm-rstar.sfu.ca> <20040907221701.GB2826@odin.ac.hmc.edu> In-Reply-To: <20040907221701.GB2826@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409081133.02935.groot@kde.org> Subject: Re: getting an amd64 system 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, 08 Sep 2004 09:33:05 -0000 On Wednesday 08 September 2004 00:17, Brooks Davis wrote: > On Mon, Sep 06, 2004 at 07:55:35PM -0700, murrayp@sfu.ca wrote: > > 2) I'm getting an Asus Radeon 9600XT 128MB AGP w/DVI for my video card. > > Is this supported, or is this a big mistake? If so, is there a > > comparable video card that is supported? > > I'm not really up on video hardware support, but just about everything > will work with X. Accelleration may be another story. Take a good look at xfree86.org or x.org and their hardware-support lists before picking anything particular. I've heard varying reports about support for newer Radeons (post 7000), in particular that acceleration is not supported. (However, this was some time ago, who knows what has changed since then). > > 3) I am connecting to a wireless network. Is WiFi supported in 5.2.1? > > for any of the cards out there? If not, is WiFi supported in FreeBSD, > > period (ie: for any systems, including an i386, etc?) > > Many wireless devices are supported natively. The rest are generally "Many" is a relative word. If you consider the wifi stuff you can just buy at computer stores in Europe, just about all the 802.11g stuff is ralink based (PCI cards) or usb based, and neither of those are supported in 64-bit mode at all. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 13:07:28 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 9A99816A4CE; Wed, 8 Sep 2004 13:07:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C7543D4C; Wed, 8 Sep 2004 13:07:28 +0000 (GMT) (envelope-from tjr@FreeBSD.org) Received: from freefall.freebsd.org (tjr@localhost [127.0.0.1]) i88D7SGt090406; Wed, 8 Sep 2004 13:07:28 GMT (envelope-from tjr@freefall.freebsd.org) Received: (from tjr@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i88D7SUJ090402; Wed, 8 Sep 2004 13:07:28 GMT (envelope-from tjr) Date: Wed, 8 Sep 2004 13:07:28 GMT From: "Tim J. Robbins" Message-Id: <200409081307.i88D7SUJ090402@freefall.freebsd.org> To: loox@e-shell.net, tjr@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/71173: nfs writing problems on exported msdosfs 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, 08 Sep 2004 13:07:28 -0000 Synopsis: nfs writing problems on exported msdosfs State-Changed-From-To: open->patched State-Changed-By: tjr State-Changed-When: Wed Sep 8 13:07:08 GMT 2004 State-Changed-Why: Should be fixed in -CURRENT now. http://www.freebsd.org/cgi/query-pr.cgi?pr=71173 From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 13:51:52 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AE8016A4CE for ; Wed, 8 Sep 2004 13:51:52 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A0F743D39 for ; Wed, 8 Sep 2004 13:51:52 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id C1DAF55EB4 for ; Wed, 8 Sep 2004 13:51:10 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C207416A4CE for ; Wed, 8 Sep 2004 13:51:10 +0000 (GMT) Received: from lorax.ldc.upenn.edu (lorax.LDC.upenn.edu [158.130.16.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B98A43D46 for ; Wed, 8 Sep 2004 13:51:10 +0000 (GMT) (envelope-from fuzz@ldc.upenn.edu) Received: by lorax.ldc.upenn.edu (Postfix, from userid 32822) id 9AB24228A2; Wed, 8 Sep 2004 09:51:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by lorax.ldc.upenn.edu (Postfix) with ESMTP id 920A8228A0; Wed, 8 Sep 2004 09:51:09 -0400 (EDT) Date: Wed, 8 Sep 2004 09:51:09 -0400 (EDT) From: "Jason M. Leonard" To: Tomaz Borstnar In-Reply-To: <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> Message-ID: <20040908092352.T26965@lorax.ldc.upenn.edu> References: <20040905123829.D51907@lorax.ldc.upenn.edu> <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@lists.freebsd.org Subject: Re: 3ware (twe, twa) support for AMD64 in 5.3? 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, 08 Sep 2004 13:51:52 -0000 On Sun, 5 Sep 2004, Tomaz Borstnar wrote: > At 18:39 5.9.2004, Jason M. Leonard wrote: >> 1. Are the 3ware drivers ready for production on AMD64? > > so far twa seem to work OK on 5.3beta. Will test it more extensively in > future. Thanks. I do have several AMD64 boxes with 3ware 9500 cards. They're all running i386 right now, though, because I bought them based on the fact that twa was in the AMD64 GENERIC in -CURRENT at the time. Silly me not to do my research; twa built fine in -CURRENT, newfs seemed OK, mounting the volume seemed OK, but anything after that resulted in a panic. So I read the threads cited in my previous email, smacked myself on the head and installed FreeBSD/i386 on those machines. But I still wanted a box running FreeBSD/AMD64, so I ordered an all-SCSI box with an asr(4)-based SCSI card. Because this time I checked the hardware release notes for AMD64 and asr(4) was listed. Cool. Except, of course, when I tried to install FreeBSD/AMD64 on my new SCSI machine I found that asr(4) didn't really work after all. Now I need to purchase new hardware again, so this time I thought I would ask first instead of making another mistake. Since twa(4) seems to be working for you I'll take down one of the boxes currently running FreeBSD/i386, install 5.3/AMD64 on it and begin extenstive testing today. :Fuzz > > >> 2. Will the CLI utilities run on AMD64? > > Hmm, i can check that one of these days. > > > Tomaz > > From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 14:39:11 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2B1F16A4CE for ; Wed, 8 Sep 2004 14:39:11 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AF1643D39 for ; Wed, 8 Sep 2004 14:39:10 +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 i88Ed0Nf034713; Wed, 8 Sep 2004 16:39:00 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id i88Ed9Lt085852; Wed, 8 Sep 2004 16:39:09 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i88Ed9OT085851; Wed, 8 Sep 2004 16:39:09 +0200 (CEST) (envelope-from ftigeot) Date: Wed, 8 Sep 2004 16:39:09 +0200 From: Francois Tigeot To: "Jason M. Leonard" Message-ID: <20040908143909.GA42620@aoi.wolfpond.org> References: <20040905123829.D51907@lorax.ldc.upenn.edu> <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> <20040908092352.T26965@lorax.ldc.upenn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040908092352.T26965@lorax.ldc.upenn.edu> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@www.freebsd.org Subject: Re: 3ware (twe, twa) support for AMD64 in 5.3? 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, 08 Sep 2004 14:39:11 -0000 On Wed, Sep 08, 2004 at 09:51:09AM -0400, Jason M. Leonard wrote: > > On Sun, 5 Sep 2004, Tomaz Borstnar wrote: > > >At 18:39 5.9.2004, Jason M. Leonard wrote: > >>1. Are the 3ware drivers ready for production on AMD64? > > > >so far twa seem to work OK on 5.3beta. Will test it more extensively in > >future. > > Thanks. I do have several AMD64 boxes with 3ware 9500 cards. They're all > running i386 right now, though, because I bought them based on the fact > that twa was in the AMD64 GENERIC in -CURRENT at the time. Silly me > not to do my research; twa built fine in -CURRENT, newfs seemed OK, > mounting the volume seemed OK, but anything after that resulted in a > panic. So I read the threads cited in my previous email, smacked myself > on the head and installed FreeBSD/i386 on those machines. It has also been my experience that 9500s didn't work on 5.2-CURRENT from july but were ok with 4.10 (obviously i386). > Now I need to purchase new hardware again, so this time I thought I would > ask first instead of making another mistake. Since twa(4) seems to be > working for you I'll take down one of the boxes currently running > FreeBSD/i386, install 5.3/AMD64 on it and begin extenstive testing today. I just put 5.3-BETA3 on the same type of machine (bi-opteron, 6x Gb Ethernet) and the RAID system now seems to work reliably. Additionally FreeBSD was the only OS I could install and use in 64-bit mode, but this is another story... -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 18:16:13 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB96016A4CE for ; Wed, 8 Sep 2004 18:16:13 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D1043D31 for ; Wed, 8 Sep 2004 18:16:13 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i88IHqnk026407; Wed, 8 Sep 2004 11:17:52 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i88IHp02026406; Wed, 8 Sep 2004 11:17:51 -0700 Date: Wed, 8 Sep 2004 11:17:51 -0700 From: Brooks Davis To: "Jason M. Leonard" Message-ID: <20040908181751.GB32204@odin.ac.hmc.edu> References: <20040905123829.D51907@lorax.ldc.upenn.edu> <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> <20040908092352.T26965@lorax.ldc.upenn.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline In-Reply-To: <20040908092352.T26965@lorax.ldc.upenn.edu> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@www.freebsd.org Subject: Re: 3ware (twe, twa) support for AMD64 in 5.3? 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, 08 Sep 2004 18:16:14 -0000 --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 08, 2004 at 09:51:09AM -0400, Jason M. Leonard wrote: >=20 >=20 > On Sun, 5 Sep 2004, Tomaz Borstnar wrote: >=20 > >At 18:39 5.9.2004, Jason M. Leonard wrote: > >>1. Are the 3ware drivers ready for production on AMD64? > > > >so far twa seem to work OK on 5.3beta. Will test it more extensively in= =20 > >future. >=20 > Thanks. I do have several AMD64 boxes with 3ware 9500 cards. They're al= l=20 > running i386 right now, though, because I bought them based on the fact= =20 > that twa was in the AMD64 GENERIC in -CURRENT at the time. Silly me=20 > not to do my research; twa built fine in -CURRENT, newfs seemed OK,=20 > mounting the volume seemed OK, but anything after that resulted in a=20 > panic. So I read the threads cited in my previous email, smacked myself= =20 > on the head and installed FreeBSD/i386 on those machines. >=20 > But I still wanted a box running FreeBSD/AMD64, so I ordered an all-SCSI= =20 > box with an asr(4)-based SCSI card. Because this time I checked the=20 > hardware release notes for AMD64 and asr(4) was listed. Cool. > > Except, of course, when I tried to install FreeBSD/AMD64 on my new SCSI= =20 > machine I found that asr(4) didn't really work after all. asr(4) is not 64-bit ready. :( I believe aac is. > Now I need to purchase new hardware again, so this time I thought I would= =20 > ask first instead of making another mistake. Since twa(4) seems to be=20 > working for you I'll take down one of the boxes currently running=20 > FreeBSD/i386, install 5.3/AMD64 on it and begin extenstive testing today. twa(4) is supposed to work. I think it's even been tested by 3ware. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBP0zPXY6L6fI4GtQRAoteAJ9KpeD4wyhG0+2RHlK+EJR5N8IeugCdGCOL zhU2kSQG1caNJILtEnM7DBs= =wXo1 -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 8 18:46:48 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 5B07E16A4CF for ; Wed, 8 Sep 2004 18:46:48 +0000 (GMT) Received: from web12822.mail.yahoo.com (web12822.mail.yahoo.com [216.136.174.203]) by mx1.FreeBSD.org (Postfix) with SMTP id 2F8C443D48 for ; Wed, 8 Sep 2004 18:46:48 +0000 (GMT) (envelope-from neshort@yahoo.com) Message-ID: <20040908184648.23415.qmail@web12822.mail.yahoo.com> Received: from [208.240.243.170] by web12822.mail.yahoo.com via HTTP; Wed, 08 Sep 2004 11:46:48 PDT Date: Wed, 8 Sep 2004 11:46:48 -0700 (PDT) From: Neil Short To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Current problem reports assigned to you - Re: boot fails on AMD Compaqs and HPs 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, 08 Sep 2004 18:46:48 -0000 re: compaq presario r3000z and HP Pavillion zv5000 boot failure. This is an issue that bounced around both this list and the mobile list several months ago. A user came up with a patch which is complicated to install because you have to compile it on a different machine and make your own installable media. He suggested we focus our efforts on the AMD64 list. The problem seems really to be with the nforce3 chipset that runs both AMD64 and Athlon-M processors. The patch he suggests is well presented in the mailing list: http://lists.freebsd.org/pipermail/freebsd-amd64/2004-July/001684.html Much gratitude to Jung-uk Kim for coming up with this fix. There may be a better solution somewhere else in the OS. It sure would be cool if this were fixed. _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 9 05:08: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 AA00316A4CE; Thu, 9 Sep 2004 05:08:44 +0000 (GMT) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AF6043D1F; Thu, 9 Sep 2004 05:08:44 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from dsl-201-135-241-226.prod-infinitum.com.mx (unknown [201.135.241.226]) by sophia3.e-shell.net (Postfix) with ESMTP id 58B72656804; Thu, 9 Sep 2004 00:09:00 -0500 (CDT) From: Axel Gonzalez Organization: e-shell.net Inc To: "Tim J. Robbins" Date: Thu, 9 Sep 2004 00:08:34 -0500 User-Agent: KMail/1.7 References: <200409081307.i88D7SUJ090402@freefall.freebsd.org> In-Reply-To: <200409081307.i88D7SUJ090402@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409090008.34756.loox@e-shell.net> cc: freebsd-amd64@freebsd.org Subject: amd64/71173: nfs writing problems on exported msdosfs 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, 09 Sep 2004 05:08:44 -0000 Just cvsuped and installed, it works like a charm! Thanks for the fix ;) On Wednesday 08 September 2004 08:07, Tim J. Robbins wrote: > Synopsis: nfs writing problems on exported msdosfs > > State-Changed-From-To: open->patched > State-Changed-By: tjr > State-Changed-When: Wed Sep 8 13:07:08 GMT 2004 > State-Changed-Why: > Should be fixed in -CURRENT now. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=71173 From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 9 14:49:06 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 364C416A4CF for ; Thu, 9 Sep 2004 14:49:06 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA4F543D53 for ; Thu, 9 Sep 2004 14:49:05 +0000 (GMT) (envelope-from bob@immure.com) Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1])i89En1vd224858; Thu, 9 Sep 2004 10:49:01 -0400 Received: from luke.immure.com (luke.immure.com [10.1.132.3]) by maul.immure.com (8.12.11/8.12.11) with ESMTP id i89EmwIn088965; Thu, 9 Sep 2004 09:48:58 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (localhost [127.0.0.1]) by luke.immure.com (8.12.11/8.12.11) with ESMTP id i89Emwvu004057; Thu, 9 Sep 2004 09:48:58 -0500 (CDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.12.11/8.12.11/Submit) id i89Emwff004056; Thu, 9 Sep 2004 09:48:58 -0500 (CDT) (envelope-from bob) Date: Thu, 9 Sep 2004 09:48:58 -0500 From: Bob Willcox To: Brooks Davis Message-ID: <20040909144858.GA3512@luke.immure.com> References: <20040905123829.D51907@lorax.ldc.upenn.edu> <6.1.2.0.0.20040905214720.05a7d5b0@193.189.169.9> <20040908092352.T26965@lorax.ldc.upenn.edu> <20040908181751.GB32204@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040908181751.GB32204@odin.ac.hmc.edu> User-Agent: Mutt/1.5.6i X-immure-MailScanner-Information: Please contact the ISP for more information X-immure-MailScanner: Found to be clean X-MailScanner-From: bob@immure.com cc: freebsd-amd64@www.freebsd.org Subject: Re: 3ware (twe, twa) support for AMD64 in 5.3? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bob Willcox List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2004 14:49:06 -0000 On Wed, Sep 08, 2004 at 11:17:51AM -0700, Brooks Davis wrote: > On Wed, Sep 08, 2004 at 09:51:09AM -0400, Jason M. Leonard wrote: > > > > But I still wanted a box running FreeBSD/AMD64, so I ordered an all-SCSI > > box with an asr(4)-based SCSI card. Because this time I checked the > > hardware release notes for AMD64 and asr(4) was listed. Cool. > > > > Except, of course, when I tried to install FreeBSD/AMD64 on my new SCSI > > machine I found that asr(4) didn't really work after all. > > asr(4) is not 64-bit ready. :( I believe aac is. FWIW, the amr driver (w/ an LSI 320-2 RAID ctlr) works fine on my AMD64 system running 5-current (from the May '04 time frame). Bob -- Bob Willcox Acquaintance, n.: bob@immure.com A person whom we know well enough to borrow from, Austin, TX but not well enough to lend to. -- Ambrose Bierce, "The Devil's Dictionary" From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 10 18:14:06 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 92CBC16A4CE for ; Fri, 10 Sep 2004 18:14:06 +0000 (GMT) Received: from mail.mcneil.com (rrcs-24-199-45-54.west.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17F2C43D4C for ; Fri, 10 Sep 2004 18:14:06 +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 33462F190D for ; Thu, 9 Sep 2004 11:56:50 -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 00766-01 for ; Thu, 9 Sep 2004 11:56:49 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 44745F1872 for ; Thu, 9 Sep 2004 11:56:49 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: multipart/mixed; boundary="=-Hb/SSVWRnwBzoQqtif/J" Message-Id: <1094756209.1061.8.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 09 Sep 2004 11:56:49 -0700 X-Virus-Scanned: by amavisd-new at mcneil.com Subject: [Fwd: setrunqueue(): corrupt kq_runq] 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, 10 Sep 2004 18:14:06 -0000 --=-Hb/SSVWRnwBzoQqtif/J Content-Type: text/plain Content-Transfer-Encoding: 7bit --=-Hb/SSVWRnwBzoQqtif/J Content-Disposition: inline Content-Description: Forwarded message - setrunqueue(): corrupt kq_runq Content-Type: message/rfc822 Subject: setrunqueue(): corrupt kq_runq From: Sean McNeil To: freebsd-current@freebsd.org Content-Type: text/plain Message-Id: <1094756152.1061.6.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 09 Sep 2004 11:55:52 -0700 Content-Transfer-Encoding: 7bit amd64 -CURRENT system has crashed now several times in the last 2 days. Ever since the change to SCHED_4BSD and PREEMPTION. I certainly hope this is fixed before 5.3-RELEASE. Sep 9 11:43:46 server syslogd: kernel boot file is /boot/kernel/kernel Sep 9 11:43:46 server kernel: setrunqueue(): corrupt kq_runq, td= 0xffffff004be8e520 Sep 9 11:43:46 server kernel: panic: deadlock in setrunqueue Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c21a90 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c21aa0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c21810 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c21820 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c21590 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c215a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c21310 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c21320 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c21090 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c210a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20e10 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c20e20 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20b90 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c20ba0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20910 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c20920 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20690 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c206a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20410 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c20420 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c20190 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c201a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1ff10 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1ff20 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1fc90 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1fca0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1fa10 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1fa20 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1f790 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1f7a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1f510 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1f520 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1f290 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1f2a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1f010 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1f020 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1ed90 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1eda0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1eb10 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1eb20 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1e890 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1e8a0 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Sep 9 11:43:46 server kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode Sep 9 11:43:46 server kernel: instruction pointer = 0x8:0xffffffff8031a71fSep 9 11:43:46 server kernel: stack pointer = 0x10:0xffffffffb1c1e610 Sep 9 11:43:46 server kernel: frame pointer = 0x10:0xffffffffb1c1e620 Sep 9 11:43:46 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 9 11:43:46 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 9 11:43:46 server kernel: processor eflags = IOPL = 0 Sep 9 11:43:46 server kernel: current process = 61 (schedcpu) Sep 9 11:43:46 server kernel: trap number = 3 Sep 9 11:43:46 server kernel: panic: breakpoint instruction fault Sep 9 11:43:46 server kernel: KDB: enter: panic Then a reboot. Sean --=-Hb/SSVWRnwBzoQqtif/J-- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 10 18:50: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 A9A8816A4CE for ; Fri, 10 Sep 2004 18:50:29 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A7CD43D46 for ; Fri, 10 Sep 2004 18:50:29 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=odin.cs.kun.nl) by pandora.cs.kun.nl (8.12.10/4.16) with ESMTP id i8AIoRmR017334; Fri, 10 Sep 2004 20:50:27 +0200 (MEST) Date: Fri, 10 Sep 2004 20:50:27 +0200 (MEST) From: groot@kde.org X-X-Sender: adridg@odin.cs.kun.nl To: Sean McNeil In-Reply-To: <1094756209.1061.8.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: [Fwd: setrunqueue(): corrupt kq_runq] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: groot@kde.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2004 18:50:29 -0000 On Thu, 9 Sep 2004, Sean McNeil wrote: > amd64 -CURRENT system has crashed now several times in the last 2 days. > Ever since the change to SCHED_4BSD and PREEMPTION. I certainly hope > this is fixed before 5.3-RELEASE. Um, 4BSD? I have # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.421.2.1 2004/09/07 23:49:57 oh, wait, that's RELENG_5 again, and it has _ULE by default. This machine has been portupgrading non-stop for two days (hadn't made the xorg switch yet) and is stable like a rock. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 10 19:06: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 95F8416A4CE for ; Fri, 10 Sep 2004 19:06:03 +0000 (GMT) Received: from mail.mcneil.com (rrcs-24-199-45-54.west.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B2FF43D48 for ; Fri, 10 Sep 2004 19:06:03 +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 32C6DF18F1; Fri, 10 Sep 2004 12:06:03 -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 09205-02; Fri, 10 Sep 2004 12:06:02 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 465FCF1802; Fri, 10 Sep 2004 12:06:02 -0700 (PDT) From: Sean McNeil To: groot@kde.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1094843162.9501.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 10 Sep 2004 12:06:02 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: [Fwd: setrunqueue(): corrupt kq_runq] 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, 10 Sep 2004 19:06:03 -0000 On Fri, 2004-09-10 at 11:50, groot@kde.org wrote: > On Thu, 9 Sep 2004, Sean McNeil wrote: > > > amd64 -CURRENT system has crashed now several times in the last 2 days. > > Ever since the change to SCHED_4BSD and PREEMPTION. I certainly hope > > this is fixed before 5.3-RELEASE. > > Um, 4BSD? I have > > # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.421.2.1 2004/09/07 23:49:57 > > > oh, wait, that's RELENG_5 again, and it has _ULE by default. This machine > has been portupgrading non-stop for two days (hadn't made the xorg switch > yet) and is stable like a rock. This was RELENG_6 (-CURRENT) and the default is now 4BSD and PREEMPTION. RELENG_5 was suppose to get these defaults too from what I saw in the list. I have since disabled PREEMPTION and have no longer had a crash. So this is still an issue with PREEMPTION and I believe is being looked into. Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 11 03:24:01 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 E67E016A4CE; Sat, 11 Sep 2004 03:24:01 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB22843D2F; Sat, 11 Sep 2004 03:24:01 +0000 (GMT) (envelope-from tjr@FreeBSD.org) Received: from freefall.freebsd.org (tjr@localhost [127.0.0.1]) i8B3O15a071640; Sat, 11 Sep 2004 03:24:01 GMT (envelope-from tjr@freefall.freebsd.org) Received: (from tjr@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8B3O19D071636; Sat, 11 Sep 2004 03:24:01 GMT (envelope-from tjr) Date: Sat, 11 Sep 2004 03:24:01 GMT From: "Tim J. Robbins" Message-Id: <200409110324.i8B3O19D071636@freefall.freebsd.org> To: loox@e-shell.net, tjr@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/71173: nfs writing problems on exported msdosfs 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, 11 Sep 2004 03:24:02 -0000 Synopsis: nfs writing problems on exported msdosfs State-Changed-From-To: patched->closed State-Changed-By: tjr State-Changed-When: Sat Sep 11 03:23:13 GMT 2004 State-Changed-Why: Now fixed in RELENG_5. http://www.freebsd.org/cgi/query-pr.cgi?pr=71173 From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 11 21:50: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 6E30616A4CE for ; Sat, 11 Sep 2004 21:50:08 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2942443D2F for ; Sat, 11 Sep 2004 21:50:08 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5C2241FF9A8 for ; Sat, 11 Sep 2004 23:50:07 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 4F00E1FF9A7; Sat, 11 Sep 2004 23:50:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 0D61F15389; Sat, 11 Sep 2004 21:49:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 026F815329 for ; Sat, 11 Sep 2004 21:49:42 +0000 (UTC) Date: Sat, 11 Sep 2004 21:49:42 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-amd64@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: ACPI and serial console problem 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, 11 Sep 2004 21:50:08 -0000 Hi, when booting default (1) in beastie menu I can see kernel messages on serial console (-h in boot.config) up to Mounting root from ufs:/dev/ad10s1a Afterwards I can only see device_printf messages like: capidev: CAPI device created fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 ppc0: cannot reserve I/O port range avmaic0: port 0xa800-0xa87f mem 0xf7c00000-0xf7c0007f irq 18 at device 13.0 on pci0 ... when I happen to boot w/o ACPI (2 in beastie menu) I also get the "normal" rc output to serial console in addition to device_printf: Mounting root from ufs:/dev/ad10s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ad10s1b as swap device Starting file system checks: /dev/ad10s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad10s1a: clean, 88904 free (744 frags, 11020 blocks, 0.6% fragmentation) ... Is this a bug or a feature or what am I doing wrong ? I suspect this is a /dev/console problem ? Just to further confuse you: with ACPI I get my login prompt on ttyd1 but w/o ACPI it simply seems to hang after the FreeBSD/amd64 (one.of.my.machines) (ttyd1) And yes it's ttyd1 and not 0 which has confused me from the very first day I got that machine. board is an asus K8V SE Deluxe btw and it says following upon boot: sio0 port 0x2f8-0x2ff irq 3 on acpi0 sio0: type 16550A, console sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A .me is totaly confused :( PS: I have got more problems with that machine like reboot or halt -p not working (should they?) -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT