From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 30 03:52:03 2005 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 1235216A4D0; Sun, 30 Jan 2005 03:52:03 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C38143D39; Sun, 30 Jan 2005 03:52:02 +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 j0U3pmrw067667; Sat, 29 Jan 2005 22:51:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0U3poZf081839; Sat, 29 Jan 2005 22:51:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id CEA027306E; Sat, 29 Jan 2005 22:51:48 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050130035148.CEA027306E@freebsd-current.sentex.ca> Date: Sat, 29 Jan 2005 22:51:48 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Scanned: ClamAV 0.80/690/Fri Jan 28 07:09:45 2005 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean X-Virus-Status: Clean 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, 30 Jan 2005 03:52:03 -0000 TB --- 2005-01-30 02:32:26 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-30 02:32:26 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-01-30 02:32:26 - checking out the source tree TB --- 2005-01-30 02:32:26 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-01-30 02:32:26 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-30 02:38:06 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-30 02:38:06 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-01-30 02:38:06 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-30 03:45:44 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-30 03:45:44 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-01-30 03:45:44 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 30 03:45:45 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/isofs/cd9660/cd9660_vnops.c awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/amd64/amd64/src/sys/kern/bus_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno -sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror bus_if.c awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/amd64/amd64/src/sys/kern/device_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse - mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror device_if.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/kern/imgact_elf.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/kern/imgact_shell.c /tinderbox/CURRENT/amd64/amd64/src/sys/kern/imgact_shell.c: In function `exec_shell_imgact': /tinderbox/CURRENT/amd64/amd64/src/sys/kern/imgact_shell.c:166: warning: passing arg 4 of `copystr' from incompatible pointer type /tinderbox/CURRENT/amd64/amd64/src/sys/kern/imgact_shell.c:170: warning: passing arg 4 of `copystr' from incompatible pointer type *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-01-30 03:51:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-30 03:51:48 - ERROR: failed to build generic kernel TB --- 2005-01-30 03:51:48 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 30 07:46:49 2005 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 2A16E16A4CE for ; Sun, 30 Jan 2005 07:46:49 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id C46F043D41 for ; Sun, 30 Jan 2005 07:46:48 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.11] (tardiss.ne.client2.attbi.com[66.30.82.93]) by comcast.net (sccrmhc13) with ESMTP id <2005013007464701600hb7eje>; Sun, 30 Jan 2005 07:46:47 +0000 Message-ID: <41FC90D4.9050306@comcast.net> Date: Sun, 30 Jan 2005 02:46:28 -0500 From: Sean User-Agent: Mozilla Thunderbird 1.0 (X11/20050121) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Support for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 07:46:49 -0000 So many ports, and some Linux games I bought long ago, I try to install pop up with something about only supporting i386. Is there some way to make a port, perhaps pass some sort of switch, or compile something else into the kernel to get i386 support? Thanks Sean From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 11:01:54 2005 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 7E6F716A4CE for ; Mon, 31 Jan 2005 11:01:54 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C86043D39 for ; Mon, 31 Jan 2005 11:01:54 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0VB1s7S048066 for ; Mon, 31 Jan 2005 11:01:54 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0VB1r6W048060 for freebsd-amd64@freebsd.org; Mon, 31 Jan 2005 11:01:53 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 31 Jan 2005 11:01:53 GMT Message-Id: <200501311101.j0VB1r6W048060@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, 31 Jan 2005 11:01:54 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 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/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra 15 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/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 18:30:14 2005 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 A111616A4D9 for ; Mon, 31 Jan 2005 18:30:14 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4132F43D2F for ; Mon, 31 Jan 2005 18:30:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0VIUE2G007051 for ; Mon, 31 Jan 2005 18:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0VIUEDs007050; Mon, 31 Jan 2005 18:30:14 GMT (envelope-from gnats) Resent-Date: Mon, 31 Jan 2005 18:30:14 GMT Resent-Message-Id: <200501311830.j0VIUEDs007050@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, gert cuykens Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DE3C16A4CE for ; Mon, 31 Jan 2005 18:20:36 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 275F743D2F for ; Mon, 31 Jan 2005 18:20:36 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j0VIKaDd015146 for ; Mon, 31 Jan 2005 18:20:36 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j0VIKZKC015145; Mon, 31 Jan 2005 18:20:35 GMT (envelope-from nobody) Message-Id: <200501311820.j0VIKZKC015145@www.freebsd.org> Date: Mon, 31 Jan 2005 18:20:35 GMT From: gert cuykens To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/76914: /usr/ports/audio/xmms-osssurround (build error amd64) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 18:30:14 -0000 >Number: 76914 >Category: amd64 >Synopsis: /usr/ports/audio/xmms-osssurround (build error amd64) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 31 18:30:13 GMT 2005 >Closed-Date: >Last-Modified: >Originator: gert cuykens >Release: 5.3 >Organization: >Environment: FreeBSD 7rxI 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat Jan 29 22:25:40 CET 2005 root@7rxI:/usr/obj/usr/src/sys/gert amd64 >Description: /usr/ports/audio/xmms-osssurround (build error amd64) CFLAGS+= -fPIC in make file not working > 7rxI# make > ===> Building for xmms-osssurround-0.1_1 > cc -shared -olibOSSSurround.so about.o audio.o configure.o convert.o > init.o mixer.o OSS.o > /usr/bin/ld: about.o: relocation R_X86_64_32 can not be used when > making a shared object; recompile with -fPIC > about.o: could not read symbols: Bad value > *** Error code 1 > > Stop in /usr/ports/audio/xmms-osssurround/work/xmms-a52dec-1.0/OSSSurround-0.1. > *** Error code 1 > > Stop in /usr/ports/audio/xmms-osssurround. > 7rxI# >How-To-Repeat: cd /usr/ports/audio/xmms-osssurround make >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 20:13:21 2005 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 DC9AA16A4CE; Mon, 31 Jan 2005 20:13:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B70FB43D41; Mon, 31 Jan 2005 20:13:21 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from freefall.freebsd.org (pav@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0VKDLYT020088; Mon, 31 Jan 2005 20:13:21 GMT (envelope-from pav@freefall.freebsd.org) Received: (from pav@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0VKDLk2020084; Mon, 31 Jan 2005 20:13:21 GMT (envelope-from pav) Date: Mon, 31 Jan 2005 20:13:21 GMT From: Pav Lucistnik Message-Id: <200501312013.j0VKDLk2020084@freefall.freebsd.org> To: pav@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/76914: /usr/ports/audio/xmms-osssurround (build error amd64) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 20:13:22 -0000 Synopsis: /usr/ports/audio/xmms-osssurround (build error amd64) Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: pav Responsible-Changed-When: Mon Jan 31 20:13:00 GMT 2005 Responsible-Changed-Why: Refile under ports where it belongs. http://www.freebsd.org/cgi/query-pr.cgi?pr=76914 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 22:54:42 2005 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 15C5416A4D2 for ; Mon, 31 Jan 2005 22:54:42 +0000 (GMT) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB8B643D31 for ; Mon, 31 Jan 2005 22:54:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2743 invoked from network); 31 Jan 2005 22:54:41 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Jan 2005 22:54:41 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0VMsX3u033005; Mon, 31 Jan 2005 17:54:33 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 31 Jan 2005 17:32:04 -0500 User-Agent: KMail/1.6.2 References: <200501192214.27401.jkim@niksun.com> In-Reply-To: <200501192214.27401.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501311732.04609.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: Compaq R3000z ACPI fix 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, 31 Jan 2005 22:54:42 -0000 On Wednesday 19 January 2005 10:14 pm, Jung-uk Kim wrote: > Hi, > > I finally found some time and made ACPI working on Compaq R3000z. You > need to fix kernel and DSDT. The kernel hack is for FreeBSD/amd64. > Similar hack should work with FreeBSD/i386 but I haven't tested. > > To enable the hack, you need to set 'hw.acpi.skip_timer_override=1' > from loader or loader.conf. > > Yes, I stole the idea from Linux. ;-) > > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.5/ >20040422223905-nforce2_timer.patch > > I only tested with the following options: > > options SMP > device atpic > > The DSDT fix is against BIOS version F.33. To override DSDT, please > read: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html > > Enjoy, > > Jung-uk Kim The kernel patch can be somewhat simplified (no need for getenv_int() if you just use TUNABLE_INT() I think), but I'll work on getting it into the tree. It means that this is a truly screwed up motherboard though, as every other x86 MP system in existence has routed IRQ 0 via intpin 2 and used intpin 0 as ExtINT. Actually, this also forces us to use the ATPIC for IRQ 0 via intpin 0, except that if intpin 0 is really wired up to the clock, that is wrong as well. Can you find out what the real deal is on this motherboard? Is intpin 0 ExtINT to the ATPIC or is it wired up to ISA IRQ 0 directly? Also, if it is ExtINT, then you should be able to work around this w/o a kernel patch by just forcing mixed mode. That is, set 'hw.apic.mixed_mode=1' from the loader on a stock kernel. Then we ignore the APIC for IRQ0 and use the 8259A to deliver it anyway. It seems that adding 'device atpic' should do this for you automatically as it is actually so long as you remove 'options NO_MIXED_MODE' from your kernel config. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 22:54:45 2005 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 1D5B316A4D0 for ; Mon, 31 Jan 2005 22:54:45 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC20143D2D for ; Mon, 31 Jan 2005 22:54:44 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 8180 invoked from network); 31 Jan 2005 22:54:44 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Jan 2005 22:54:44 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0VMsX3v033005; Mon, 31 Jan 2005 17:54:38 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 31 Jan 2005 17:38:04 -0500 User-Agent: KMail/1.6.2 References: <200501261149.11530.jkim@niksun.com> In-Reply-To: <200501261149.11530.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501311738.04377.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: nForce3 (Compaq R3000) timer fix 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, 31 Jan 2005 22:54:45 -0000 On Wednesday 26 January 2005 11:49 am, Jung-uk Kim wrote: > This is (hopefully) the last patch of the series, which fixes infamous > '8254 timer not connected to IO-APIC' problem for nForce2+. Linux > people had a hack here: > > http://lkml.org/lkml/2003/12/21/7 > > (Note: 2.6.10 has more refined version.) > > The attached patch requires the previous 'skip_timer_override' hack > posted here: > > http://docs.freebsd.org/cgi/mid.cgi?200501192214.27401.jkim > > After the patch, you need to set 'hw.apic.skip_set_extint=1' from > loader or loader.conf. Be careful with spelling; this is 'apic', not > 'acpi' this time. ;-) > > With verbose boot logging, we should see: > > ioapic0: intpin 0 -> ISA IRQ 0 (edge, high) > > instead of: > > ioapic0: Routing external 8259A's -> intpin 0 > ioapic0: intpin 0 -> ExtINT (edge, high) > > I was able to run this laptop overnight without 'device atpic'. ;-) I > think somebody (jhb and peter, I guess) should double check if this > is okay. I tried many combinations including 'options SMP' and all > seemed to be fine so far. > > Finally I can run this laptop at full speed (2 GHz) under heavy load > with 'acpi_ppc' driver! > > http://www.spa.is.uec.ac.jp/~nfukuda/software/ Ok,. this answers my earlier question, pin 0 is really ISA IRQ 0 and not ExtINT. Unfortunately, there's no good way to know this from MADT or MPTable except using some sort of BIOS blacklist. I want to tinker with this slightly so we can require just one hint in the MADT code to handle this though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 31 22:54:47 2005 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 BC87F16A4E7 for ; Mon, 31 Jan 2005 22:54:47 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8248243D5E for ; Mon, 31 Jan 2005 22:54:47 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 31875 invoked from network); 31 Jan 2005 22:54:47 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Jan 2005 22:54:46 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0VMsX3w033005; Mon, 31 Jan 2005 17:54:43 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org, Joseph Koshy Date: Mon, 31 Jan 2005 17:55:00 -0500 User-Agent: KMail/1.6.2 References: <20050127100818.M46092@daemon.mistermishap.net> <20050128105930.V54223@daemon.mistermishap.net> <84dead72050128204479414c88@mail.gmail.com> In-Reply-To: <84dead72050128204479414c88@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501311755.00391.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Rob Watt Subject: Re: 32-bit binary compatibility on 5.3-amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 22:54:47 -0000 On Friday 28 January 2005 11:44 pm, Joseph Koshy wrote: > rw> a ktrace is attached for this sample code: > > Here is the culprit: > > src/lib/libc/i386/gen/_set_tp.c: > > sel = i386_set_ldt(LDT_AUTO_ALLOC, &ldt, 1); > __asm __volatile("movl %0,%%gs" : : "rm" ((sel << 3) | 7)); > > i386_set_ldt() will return -1 on the AMD64 since this > function is not supported there. The lack of error checking > means that -1 will be attempted to be loaded into %gs by the > movl instruction, leading to a processor protection fault and > a process SIGSEGV. > > Compiling your sample program with '-static' under a 4.X > environment yields an executable that runs on the AMD64. > > On 5.X both statically linked and dynamically linked > executables appear to call _init_tls() and _set_tp() > and are consequently not usable in IA32 emulation > mode. > > Clearly our IA32 emulation needs work. I've no idea > why we don't support a sysarch(I386_{GET,SET}_LDT) operation > for IA32 executables. Because amd64 doesn't have LDTs. Peter has hacks in place in the dynamic 32-bit libraries that amd64 uses to use the different backing methods for implementing TLS on amd64, but that stuff wasn't in 5.3. It might be in 5.3-STABLE. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 00:10:24 2005 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 5B03916A4D8 for ; Tue, 1 Feb 2005 00:10:24 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 245A543D41 for ; Tue, 1 Feb 2005 00:10:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j110AOXj047000 for ; Tue, 1 Feb 2005 00:10:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j110ANH5046999; Tue, 1 Feb 2005 00:10:23 GMT (envelope-from gnats) Date: Tue, 1 Feb 2005 00:10:23 GMT Message-Id: <200502010010.j110ANH5046999@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Dave Myron" Subject: Re: amd64/73775: Kernel panic (trap 12) when booting with (not from!) Promise 378 controller enabled X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dave Myron List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 00:10:24 -0000 The following reply was made to PR amd64/73775; it has been noted by GNATS. From: "Dave Myron" To: , Cc: Subject: Re: amd64/73775: Kernel panic (trap 12) when booting with (not from!) Promise 378 controller enabled Date: Mon, 31 Jan 2005 15:58:21 -0800 This is a multi-part message in MIME format. ------=_NextPart_000_0F23_01C507AD.B2795580 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit This happens on my P4 system too on an ASUS P4C800 with the PDC20378 controller. More info: - If I enable the controller in the BIOS but have no drives attached (either S-ATA or P-ATA - I'm using P-ATA only because that's what I've got) the system boots fine - If I add just one disk, the system still boots fine (ad8 on ata4-master) - The problem happens when I add the slave drive ------=_NextPart_000_0F23_01C507AD.B2795580 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Re: amd64/73775: Kernel panic (trap 12) when booting with (not = from!) Promise 378 controller enabled

This happens = on my P4 system too on an ASUS P4C800 with the PDC20378 = controller.

More = info:
- If I = enable the controller in the BIOS but have no drives attached (either = S-ATA or P-ATA - I'm using P-ATA only because that's what I've got) the = system boots fine

- If I add = just one disk, the system still boots fine (ad8 on ata4-master)
- The = problem happens when I add the slave drive

------=_NextPart_000_0F23_01C507AD.B2795580-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 17:50:26 2005 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 4312416A4D5 for ; Tue, 1 Feb 2005 17:50:26 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C562D43D1F for ; Tue, 1 Feb 2005 17:50:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j11HoNOF099829 for ; Tue, 1 Feb 2005 17:50:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j11HoNKl099827; Tue, 1 Feb 2005 17:50:23 GMT (envelope-from gnats) Resent-Date: Tue, 1 Feb 2005 17:50:23 GMT Resent-Message-Id: <200502011750.j11HoNKl099827@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, Bart Veurink Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD0B016A4CE for ; Tue, 1 Feb 2005 17:44:51 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA55343D41 for ; Tue, 1 Feb 2005 17:44:51 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j11Hipu7080051 for ; Tue, 1 Feb 2005 17:44:51 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j11Hip0E080050; Tue, 1 Feb 2005 17:44:51 GMT (envelope-from nobody) Message-Id: <200502011744.j11Hip0E080050@www.freebsd.org> Date: Tue, 1 Feb 2005 17:44:51 GMT From: Bart Veurink To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/76973: BTX Halted 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, 01 Feb 2005 17:50:26 -0000 >Number: 76973 >Category: amd64 >Synopsis: BTX Halted >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 Feb 01 17:50:23 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Bart Veurink >Release: 5.3 >Organization: >Environment: >Description: Hello FreeBSD.ORG, I got a problem with installing FreeBSD from CD (Mini and Normal). This is my first time to try a BSD. It gives the Error in the bootloader, BTX Halted. By The Way why are there not ISO's for FreeBSD 6.0 First some info and a Error: int=0000000d err=00000000 efl=00010086 eip=00027788 eax=80000011 ebx=00037000 ecx=c0000080 edx=00000000 esi=00036000 edi=00035000 ebp=000948a4 esp=0009e870 cs:eip:0f 22 c0 b8 00 20 04 00-8b 35 98 7f 04 00 8b 3d 9c 7f 04 00 0f 01 10 ea-a6 77 02 00 08 00 89 f0 ss:esp:69 95 00 00 00 40 c9 00-00 50 c9 00 10 10 04 00 00 00 00 00 00 00 04 00-00 00 00 00 58 b0 06 00 BTX Halted >How-To-Repeat: Everytime with the boot for installation. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 19:06:47 2005 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 6344A16A4CE; Tue, 1 Feb 2005 19:06:47 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BC7D43D4C; Tue, 1 Feb 2005 19:06:47 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j11J6kO20838; Tue, 1 Feb 2005 11:06:46 -0800 (PST) Date: Tue, 1 Feb 2005 11:06:46 -0800 From: Mike Hunter To: freebsd-amd64@freebsd.org Message-ID: <20050201190646.GA18651@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 19:06:47 -0000 Hey everybody, I plopped the new 300 gig drives into the K8S based dual opteron, but I got some funny stuff upon rebooting (see the Dump Card State): ----- Forwarded message from Charlie Root ----- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 root@:/usr/obj/usr/src/sys/myserver Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2192.07-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 8589934592 (8192 MB) avail memory = 8248307712 (7866 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci3: at device 6.0 (no driver attached) fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:2b:4a:e7 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:2b:4b:12 bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 miibus2: on bge1 brgphy1: on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:2b:4b:13 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle (probe2:ahd0:0:2:0): No or incomplete CDB sent to device. (probe2:ahd0:0:2:0): Protocol violation in Message-in phase. Attempting to abort. (probe2:ahd0:0:2:0): Abort Message Sent (probe2:ahd0:0:2:0): SCB 11 - Abort Tag Completed. found == 0x1 ahd0: Invalid Sequencer interrupt occurred. >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x23c Mode 0x0 Card was paused INTSTAT[0x0] SELOID[0x2] SELID[0x40] HS_MAILBOX[0x0] INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) SCSISIGI[0xe6]:(P_MESGIN|REQI|BSYI) SCSIPHASE[0x8]:(MSG_IN_PHASE) SCSIBUS[0x80] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2) SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x2] KERNEL_QFREEZE_COUNT[0x2] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x22]:(SPIORDY|SELDI) SSTAT1[0x11]:(REQINIT|PHASEMIS) SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xb NEXTSCB 0xff80 qinstart = 30 qinfifonext = 30 QINFIFO: WAITING_TID_QUEUES: Pending list: 9 FIFO_USE[0x0] SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) SCB_SCSIID[0x47] Total 1 Kernel Free SCB list: 11 12 1 2 3 4 5 6 7 8 10 13 14 15 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xc SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xb SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) LQIN: 0x8 0x0 0x0 0xc 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc]:(ENOVERRUN|ENIOERR) CCSCBCTL[0x4]:(CCSCBDIR) ahd0: REG0 == 0x3f9d, SINDEX = 0x10e, DINDEX = 0x106 ahd0: SCBPTR == 0xc, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xffdb CDB 12 20 0 81 8 82 STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 da2 at ahd0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) da0 at ahd0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da1 at ahd0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a I saw similar things referenced here: http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001561.html http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025016.html The second email talks about getting rom updates from seagate...but I called seagate and they said there's no new firmware out for these drives. The only other "answers" I'm getting about this is that "well, the 64 bit drivers aren't quite up to speed yet." The drives seem to be working fine...let me know if there's anything I can do to help. (Also, the "probe...abort message sent" stuff seems related to the 30 Gig drive...any cluse on that one?) Thanks, Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 19:12:01 2005 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 9548516A4CE; Tue, 1 Feb 2005 19:12:01 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0709D43D3F; Tue, 1 Feb 2005 19:12:01 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j11JC2d3000858; Tue, 1 Feb 2005 12:12:02 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41FFD47B.2000505@freebsd.org> Date: Tue, 01 Feb 2005 12:11:55 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050201190646.GA18651@ack.Berkeley.EDU> In-Reply-To: <20050201190646.GA18651@ack.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=3.8 tests=ALL_TRUSTED,UPPERCASE_25_50 autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 01 Feb 2005 19:12:01 -0000 Mike Hunter wrote: > Hey everybody, > > I plopped the new 300 gig drives into the K8S based dual opteron, but I > got some funny stuff upon rebooting (see the Dump Card State): > > ----- Forwarded message from Charlie Root ----- > > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 > root@:/usr/obj/usr/src/sys/myserver > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 248 (2192.07-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > Features=0x78bfbff > AMD Features=0xe0500800 > real memory = 8589934592 (8192 MB) > avail memory = 8248307712 (7866 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 6.0 on pci0 > pci3: on pcib1 > ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > pci3: at device 6.0 (no driver attached) > fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:e0:81:2b:4a:e7 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 > ahd0: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 > ahd1: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 > miibus1: on bge0 > brgphy0: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge0: Ethernet address: 00:e0:81:2b:4b:12 > bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 > miibus2: on bge1 > brgphy1: on miibus2 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge1: Ethernet address: 00:e0:81:2b:4b:13 > pci0: at device 10.1 (no driver attached) > pcib3: at device 11.0 on pci0 > pci1: on pcib3 > pci0: at device 11.1 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A, console > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > orm0: at iomem 0xc0000-0xc7fff on isa0 > ppc0: cannot reserve I/O port range > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > acd0: CDROM at ata0-master UDMA33 > Waiting 5 seconds for SCSI devices to settle > (probe2:ahd0:0:2:0): No or incomplete CDB sent to device. > (probe2:ahd0:0:2:0): Protocol violation in Message-in phase. Attempting to abort. > (probe2:ahd0:0:2:0): Abort Message Sent > (probe2:ahd0:0:2:0): SCB 11 - Abort Tag Completed. > found == 0x1 > ahd0: Invalid Sequencer interrupt occurred. > >>>>>>>>>>>>>>>>>>>Dump Card State Begins <<<<<<<<<<<<<<<<< > > ahd0: Dumping Card State at program address 0x23c Mode 0x0 > Card was paused > INTSTAT[0x0] SELOID[0x2] SELID[0x40] HS_MAILBOX[0x0] > INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] > DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) > SCSISIGI[0xe6]:(P_MESGIN|REQI|BSYI) SCSIPHASE[0x8]:(MSG_IN_PHASE) > SCSIBUS[0x80] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) > SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) > SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2) SEQ_FLAGS[0x0] > SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x2] KERNEL_QFREEZE_COUNT[0x2] > MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x22]:(SPIORDY|SELDI) > SSTAT1[0x11]:(REQINIT|PHASEMIS) SSTAT2[0x0] SSTAT3[0x0] > PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) > LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] > LQOSTAT1[0x0] LQOSTAT2[0x0] > > SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xb NEXTSCB 0xff80 > qinstart = 30 qinfifonext = 30 > QINFIFO: > WAITING_TID_QUEUES: > Pending list: > 9 FIFO_USE[0x0] SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) > SCB_SCSIID[0x47] > Total 1 > Kernel Free SCB list: 11 12 1 2 3 4 5 6 7 8 10 13 14 15 0 > Sequencer Complete DMA-inprog list: > Sequencer Complete list: > Sequencer DMA-Up and Complete list: > Sequencer On QFreeze and Complete list: > > > ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xc > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > > ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xb > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > LQIN: 0x8 0x0 0x0 0xc 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 > ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 > ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 > > SIMODE0[0xc]:(ENOVERRUN|ENIOERR) > CCSCBCTL[0x4]:(CCSCBDIR) > ahd0: REG0 == 0x3f9d, SINDEX = 0x10e, DINDEX = 0x106 > ahd0: SCBPTR == 0xc, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xffdb > CDB 12 20 0 81 8 82 > STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > da2 at ahd0 bus 0 target 4 lun 0 > da2: Fixed Direct Access SCSI-3 device > da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da2: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > da0 at ahd0 bus 0 target 1 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) > da1 at ahd0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > > I saw similar things referenced here: > > http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001561.html > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025016.html > > The second email talks about getting rom updates from seagate...but I > called seagate and they said there's no new firmware out for these drives. > > The only other "answers" I'm getting about this is that "well, the 64 bit > drivers aren't quite up to speed yet." > > The drives seem to be working fine...let me know if there's anything I can > do to help. > > (Also, the "probe...abort message sent" stuff seems related to the 30 Gig > drive...any cluse on that one?) > > Thanks, > > Mike The firmware on two of those drives is dangerouly old and broken. I'd suggest contacting Seagate for an update, and keep a fire extinguisher and some holy water nearby until they are upgraded. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 19:14:17 2005 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 682AA16A4CE for ; Tue, 1 Feb 2005 19:14:17 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24FD743D49 for ; Tue, 1 Feb 2005 19:14:17 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j11JEGG21077 for freebsd-amd64@freebsd.org; Tue, 1 Feb 2005 11:14:16 -0800 (PST) Date: Tue, 1 Feb 2005 11:14:16 -0800 From: Mike Hunter To: freebsd-amd64@freebsd.org Message-ID: <20050201191416.GB18651@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: fxp0 device timeout 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, 01 Feb 2005 19:14:17 -0000 Hi, I saw this little gem in my /var/log/messages: Feb 1 02:27:54 myserver kernel: fxp0: device timeout -bash-2.05b$ ifconfig fxp0 fxp0: flags=8843 mtu 1500 options=8 inet 123.45.67.89 netmask 0xffffffe0 broadcast 123.45.67.89 ether 00:e0:81:2b:4a:e7 media: Ethernet autoselect (100baseTX ) status: active -bash-2.05b$ dmesg | grep fxp fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 miibus0: on fxp0 fxp0: Ethernet address: 00:e0:81:2b:4a:e7 At that time of day it would probably have been doing an scp. uname -a: myserver.Net.Berkeley.EDU 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 root@:/usr/obj/usr/src/sys/myserver amd64 Any advice? Thanks! Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 19:35:04 2005 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 57A7716A4CF; Tue, 1 Feb 2005 19:35:04 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 129F643D2D; Tue, 1 Feb 2005 19:35:04 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from klendathu.lovett.com ([67.134.38.155]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1Cw3nj-0000mc-VV; Tue, 01 Feb 2005 19:35:04 +0000 Message-ID: <41FFD9EE.3070204@FreeBSD.org> Date: Tue, 01 Feb 2005 11:35:10 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> In-Reply-To: <41FFD47B.2000505@freebsd.org> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 01 Feb 2005 19:35:04 -0000 Scott Long wrote: > The firmware on two of those drives is dangerouly old and broken. I'd > suggest contacting Seagate for an update, and keep a fire extinguisher > and some holy water nearby until they are upgraded. Newer firmware doesn't make any difference to this particular problem. The combination of U320, Adaptec, Seagate, and ahd is very, very prone to weird and wonderful warnings, errors, failures, lockups, and general crapness. Somewhat unsurprisingly, things seem to be significantly worse with integrated aic7902 chipsets on the motherboard, than with the equivalent PCI-X cards. By all means update the firmware -- particularly in this case -- but don't expect it to be the Holy Grail. You *might* get lucky, but the odds are significantly stacked against you. -aDe From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 19:42:36 2005 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 78BCD16A4CE; Tue, 1 Feb 2005 19:42:36 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F297543D1D; Tue, 1 Feb 2005 19:42:35 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j11Jgd6E001017; Tue, 1 Feb 2005 12:42:39 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41FFDBA8.8070501@freebsd.org> Date: Tue, 01 Feb 2005 12:42:32 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ade Lovett References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> <41FFD9EE.3070204@FreeBSD.org> In-Reply-To: <41FFD9EE.3070204@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 01 Feb 2005 19:42:36 -0000 Ade Lovett wrote: > Scott Long wrote: > >> The firmware on two of those drives is dangerouly old and broken. I'd >> suggest contacting Seagate for an update, and keep a fire extinguisher >> and some holy water nearby until they are upgraded. > > > Newer firmware doesn't make any difference to this particular problem. > > The combination of U320, Adaptec, Seagate, and ahd is very, very prone > to weird and wonderful warnings, errors, failures, lockups, and general > crapness. > > Somewhat unsurprisingly, things seem to be significantly worse with > integrated aic7902 chipsets on the motherboard, than with the equivalent > PCI-X cards. > > By all means update the firmware -- particularly in this case -- but > don't expect it to be the Holy Grail. You *might* get lucky, but the > odds are significantly stacked against you. > > -aDe Some versions of the Adaptec U320 chips work better with cables, and some work better with backplanes. In general, none work well with anything that isn't very simple and clean. 68->80 pin converters are very problematic, for example, as are cable->backplane junctions. In any case, whomever at Seagate tech support is making wild claims about 64-bit support and FreeBSD should be ignored. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 21:03:18 2005 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 4C23516A4CE; Tue, 1 Feb 2005 21:03:18 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EA343D58; Tue, 1 Feb 2005 21:03:18 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j11L3Hv27347; Tue, 1 Feb 2005 13:03:17 -0800 (PST) Date: Tue, 1 Feb 2005 13:03:17 -0800 From: Mike Hunter To: Scott Long Message-ID: <20050201210317.GA26048@ack.Berkeley.EDU> References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> <41FFD9EE.3070204@FreeBSD.org> <41FFDBA8.8070501@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FFDBA8.8070501@freebsd.org> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org cc: freebsd-amd64@freebsd.org cc: Ade Lovett Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 01 Feb 2005 21:03:18 -0000 On Feb 01, "Scott Long" wrote: > Ade Lovett wrote: > > >Scott Long wrote: > > > >>The firmware on two of those drives is dangerouly old and broken. I'd > >>suggest contacting Seagate for an update, and keep a fire extinguisher > >>and some holy water nearby until they are upgraded. > > > >Newer firmware doesn't make any difference to this particular problem. > > > >The combination of U320, Adaptec, Seagate, and ahd is very, very prone > >to weird and wonderful warnings, errors, failures, lockups, and general > >crapness. > > > >Somewhat unsurprisingly, things seem to be significantly worse with > >integrated aic7902 chipsets on the motherboard, than with the equivalent > >PCI-X cards. > > > >By all means update the firmware -- particularly in this case -- but > >don't expect it to be the Holy Grail. You *might* get lucky, but the > >odds are significantly stacked against you. > > Some versions of the Adaptec U320 chips work better with cables, and > some work better with backplanes. In general, none work well with > anything that isn't very simple and clean. 68->80 pin converters are > very problematic, for example, as are cable->backplane junctions. In > any case, whomever at Seagate tech support is making wild claims about > 64-bit support and FreeBSD should be ignored. Thanks to everybody for their replies. I will plan to get firmware from seagate and flash all the drives. I'm downloading knoppix to use seagate's utility...or will it work under fbsd? (It's a moot point since I have a amd64 build without 32bit abi compat.) Is it possible to flash the onboard adaptec "card"? I haven't found any info on how to do that if it is. Sucks to be me! Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 1 21:06:26 2005 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 322CC16A4CE; Tue, 1 Feb 2005 21:06:26 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9965A43D41; Tue, 1 Feb 2005 21:06:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.19] (ibook-nai.samsco.home [192.168.254.19]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j11L6Hks001494; Tue, 1 Feb 2005 14:06:18 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <41FFEF44.30204@samsco.org> Date: Tue, 01 Feb 2005 14:06:12 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> <41FFD9EE.3070204@FreeBSD.org> <41FFDBA8.8070501@freebsd.org> <20050201210317.GA26048@ack.Berkeley.EDU> In-Reply-To: <20050201210317.GA26048@ack.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org cc: Ade Lovett Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 01 Feb 2005 21:06:26 -0000 Mike Hunter wrote: > On Feb 01, "Scott Long" wrote: > > >>Ade Lovett wrote: >> >> >>>Scott Long wrote: >>> >>> >>>>The firmware on two of those drives is dangerouly old and broken. I'd >>>>suggest contacting Seagate for an update, and keep a fire extinguisher >>>>and some holy water nearby until they are upgraded. >>> >>>Newer firmware doesn't make any difference to this particular problem. >>> >>>The combination of U320, Adaptec, Seagate, and ahd is very, very prone >>>to weird and wonderful warnings, errors, failures, lockups, and general >>>crapness. >>> >>>Somewhat unsurprisingly, things seem to be significantly worse with >>>integrated aic7902 chipsets on the motherboard, than with the equivalent >>>PCI-X cards. >>> >>>By all means update the firmware -- particularly in this case -- but >>>don't expect it to be the Holy Grail. You *might* get lucky, but the >>>odds are significantly stacked against you. >> >>Some versions of the Adaptec U320 chips work better with cables, and >>some work better with backplanes. In general, none work well with >>anything that isn't very simple and clean. 68->80 pin converters are >>very problematic, for example, as are cable->backplane junctions. In >>any case, whomever at Seagate tech support is making wild claims about >>64-bit support and FreeBSD should be ignored. > > > Thanks to everybody for their replies. I will plan to get firmware from > seagate and flash all the drives. I'm downloading knoppix to use > seagate's utility...or will it work under fbsd? (It's a moot point since I > have a amd64 build without 32bit abi compat.) > > Is it possible to flash the onboard adaptec "card"? I haven't found any > info on how to do that if it is. > > Sucks to be me! > > Mike The Adaptec SCSI controllers don't have an on-board firmware. BIOS updates and the associated flash tools are available from the website. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 00:13:53 2005 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 C144C16A4CE for ; Wed, 2 Feb 2005 00:13:53 +0000 (GMT) Received: from web42108.mail.yahoo.com (web42108.mail.yahoo.com [66.218.93.201]) by mx1.FreeBSD.org (Postfix) with SMTP id 78A6043D39 for ; Wed, 2 Feb 2005 00:13:53 +0000 (GMT) (envelope-from drumslayer2@yahoo.com) Received: (qmail 87998 invoked by uid 60001); 2 Feb 2005 00:13:53 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=x2WfGoCQNLkn7K2Ij/Uh7VDj4+T0Fr2X51Z44cD1/jWW8/n2pQ6CufTvhpGc2OLwOGN5lVbccpWFuqbWnzVnOLHpbD7KdoTuLF0giAxGdXSY4GBXYL+IDopNLf6FQXa+EcT1zWpWQGtwq1vl9cRsk/4m/M9BiyNfvmP+q+DiOPc= ; Message-ID: <20050202001353.87996.qmail@web42108.mail.yahoo.com> Received: from [67.112.21.27] by web42108.mail.yahoo.com via HTTP; Tue, 01 Feb 2005 16:13:53 PST Date: Tue, 1 Feb 2005 16:13:53 -0800 (PST) From: drumslayer2 To: mikel king In-Reply-To: <41FB0C2B.108@ocsny.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: hardware spec 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: Wed, 02 Feb 2005 00:13:53 -0000 --- mikel king wrote: > I am trying to ramp up on the amd64 technology. I > would like to assemble > a cheap dual cpu worstation/low end server. I found > one fairly > affordable board and am curious if anyone elase has > had experience with > this product? > > > http://www.superwarehouse.com/p.cfm?p=332508&CMP=KA18442 > > I have never used that board but I can highly recommend the Tyan boards. Especially the S2882 and the S2850. I have used both very successfully. N. > > -- > Cheers, > Mikel King > > > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 05:36:06 2005 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 3420C16A4CE; Wed, 2 Feb 2005 05:36:06 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8167143D49; Wed, 2 Feb 2005 05:36:05 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-a.dmv.com (mail-gw-cl-a.dmv.com [216.240.97.38]) j125nnEo092883; Wed, 2 Feb 2005 00:49:49 -0500 (EST) (envelope-from sven@dmv.com) Received: from [64.45.134.154] (dogpound.dyndns.org [64.45.134.154]) by mail-gw-cl-a.dmv.com (8.12.9/8.12.9) with ESMTP id j125nWw5065173; Wed, 2 Feb 2005 00:49:33 -0500 (EST) (envelope-from sven@dmv.com) Message-ID: <420066C6.9040306@dmv.com> Date: Wed, 02 Feb 2005 00:36:06 -0500 From: Sven Willenberger User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050201190646.GA18651@ack.Berkeley.EDU> In-Reply-To: <20050201190646.GA18651@ack.Berkeley.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.38 cc: freebsd-scsi@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 02 Feb 2005 05:36:06 -0000 Mike Hunter wrote: > Hey everybody, > > I plopped the new 300 gig drives into the K8S based dual opteron, but I > got some funny stuff upon rebooting (see the Dump Card State): > > ----- Forwarded message from Charlie Root ----- > > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 > root@:/usr/obj/usr/src/sys/myserver > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 248 (2192.07-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > Features=0x78bfbff > AMD Features=0xe0500800 > real memory = 8589934592 (8192 MB) > avail memory = 8248307712 (7866 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 6.0 on pci0 > pci3: on pcib1 > ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > pci3: at device 6.0 (no driver attached) > fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:e0:81:2b:4a:e7 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 > ahd0: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 > ahd1: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 > miibus1: on bge0 > brgphy0: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge0: Ethernet address: 00:e0:81:2b:4b:12 > bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 > miibus2: on bge1 > brgphy1: on miibus2 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge1: Ethernet address: 00:e0:81:2b:4b:13 > pci0: at device 10.1 (no driver attached) > pcib3: at device 11.0 on pci0 > pci1: on pcib3 > pci0: at device 11.1 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A, console > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > orm0: at iomem 0xc0000-0xc7fff on isa0 > ppc0: cannot reserve I/O port range > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > acd0: CDROM at ata0-master UDMA33 > Waiting 5 seconds for SCSI devices to settle > (probe2:ahd0:0:2:0): No or incomplete CDB sent to device. > (probe2:ahd0:0:2:0): Protocol violation in Message-in phase. Attempting to abort. > (probe2:ahd0:0:2:0): Abort Message Sent > (probe2:ahd0:0:2:0): SCB 11 - Abort Tag Completed. > found == 0x1 > ahd0: Invalid Sequencer interrupt occurred. > >>>>>>>>>>>>>>>>>>>Dump Card State Begins <<<<<<<<<<<<<<<<< > > ahd0: Dumping Card State at program address 0x23c Mode 0x0 > Card was paused > INTSTAT[0x0] SELOID[0x2] SELID[0x40] HS_MAILBOX[0x0] > INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] > DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) > SCSISIGI[0xe6]:(P_MESGIN|REQI|BSYI) SCSIPHASE[0x8]:(MSG_IN_PHASE) > SCSIBUS[0x80] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) > SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) > SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2) SEQ_FLAGS[0x0] > SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x2] KERNEL_QFREEZE_COUNT[0x2] > MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x22]:(SPIORDY|SELDI) > SSTAT1[0x11]:(REQINIT|PHASEMIS) SSTAT2[0x0] SSTAT3[0x0] > PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) > LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] > LQOSTAT1[0x0] LQOSTAT2[0x0] > > SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xb NEXTSCB 0xff80 > qinstart = 30 qinfifonext = 30 > QINFIFO: > WAITING_TID_QUEUES: > Pending list: > 9 FIFO_USE[0x0] SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) > SCB_SCSIID[0x47] > Total 1 > Kernel Free SCB list: 11 12 1 2 3 4 5 6 7 8 10 13 14 15 0 > Sequencer Complete DMA-inprog list: > Sequencer Complete list: > Sequencer DMA-Up and Complete list: > Sequencer On QFreeze and Complete list: > > > ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xc > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > > ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xb > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > LQIN: 0x8 0x0 0x0 0xc 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 > ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 > ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 > > SIMODE0[0xc]:(ENOVERRUN|ENIOERR) > CCSCBCTL[0x4]:(CCSCBDIR) > ahd0: REG0 == 0x3f9d, SINDEX = 0x10e, DINDEX = 0x106 > ahd0: SCBPTR == 0xc, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xffdb > CDB 12 20 0 81 8 82 > STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > da2 at ahd0 bus 0 target 4 lun 0 > da2: Fixed Direct Access SCSI-3 device > da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da2: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > da0 at ahd0 bus 0 target 1 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) > da1 at ahd0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > > I saw similar things referenced here: > > http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001561.html > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025016.html > > The second email talks about getting rom updates from seagate...but I > called seagate and they said there's no new firmware out for these drives. > > The only other "answers" I'm getting about this is that "well, the 64 bit > drivers aren't quite up to speed yet." > > The drives seem to be working fine...let me know if there's anything I can > do to help. > > (Also, the "probe...abort message sent" stuff seems related to the 30 Gig > drive...any cluse on that one?) > > Thanks, > > Mike > _______________________________________________ I have seen the same things on several i386 systems with the same on-board controllers (Supermicro m/b) when more than one drive was connected on a backplane using Seagate SCSI (U320) drives and just a high rate of errors/failures even with single drives. Contacting their tech support was an exercise in frustration as they suggested things like putting in a nic card (instead of the onboard intel em nic as somehow there was a conflict there) or disabling SMP; i.e. they will not acknowledge that there may be a problem. I found the cheaper and less hassle solution was to use Hitachi drives and haven't had a problem since (this issue occured on at least 1/2 dozen spec'd boxen using 5.x FreeBSD and the aic79xx drivers, etc). Even getting bios updates out of them was like pulling teeth; turns out the updates solved nothing. It may be an issue with the FreeBSD drivers, but since they seem to work perfectly fine with at least one brand of drives, I suspect not. Sven From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 12:41:19 2005 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 84BFC16A4CF for ; Wed, 2 Feb 2005 12:41:19 +0000 (GMT) Received: from web30105.mail.mud.yahoo.com (web30105.mail.mud.yahoo.com [68.142.200.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 0234643D48 for ; Wed, 2 Feb 2005 12:41:19 +0000 (GMT) (envelope-from bart_veurink@yahoo.com) Received: (qmail 79645 invoked by uid 60001); 2 Feb 2005 12:41:18 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=fIdth51Txqve4huXwZ4ajUgNArHLZOtqYvHsBkR6YP9pBPlHoOvQ/WcJ9cH8emt7O8sX0QFo8pURuNxp0JpDF8HY0TWB5L8Dzl7YCyCR4KrS8CrN6gMhYzVdW2mYKIB1wK9KkPxMvYw4PZ19Q5JXNIgAgw7QSNlHLw1zvV8A6WE= ; Message-ID: <20050202124118.79643.qmail@web30105.mail.mud.yahoo.com> Received: from [83.116.202.50] by web30105.mail.mud.yahoo.com via HTTP; Wed, 02 Feb 2005 04:41:18 PST Date: Wed, 2 Feb 2005 04:41:18 -0800 (PST) From: Bart Veurink To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org In-Reply-To: <200502011750.j11HoNF6099820@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: amd64/76973: BTX Halted 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, 02 Feb 2005 12:41:19 -0000 Hello, This is my system: Case Enlight EN4102 300 Watt Floppy Samsung Floppydrive 3,5" Memory 256MB PC3200 DDR Processor AMD Sempron 2800+ FSB 333 Cooler Coolermaster USB 6x USB 2.0 + 2x USB Front LAN 10/100 MB On-Board Graphics 64MB 2D/3D VGA card Real Graphics on=board DVD/CD BEnQ 16x DVD Burner +/_ Double layer HDD Maxtor 120GB/7200RPM ATA-133 Mouse Logitech Wheelmouse Keyboard PS/2 Keyboard USB Stick Sweex 64MB FreeBSD-gnats-submit@FreeBSD.org wrote: Thank you very much for your problem report. It has the internal identification `amd64/76973'. The individual assigned to look at your report is: freebsd-amd64. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=76973 >Category: amd64 >Responsible: freebsd-amd64 >Synopsis: BTX Halted >Arrival-Date: Tue Feb 01 17:50:23 GMT 2005 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 12:43:27 2005 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 DF6D416A4CE for ; Wed, 2 Feb 2005 12:43:27 +0000 (GMT) Received: from web30101.mail.mud.yahoo.com (web30101.mail.mud.yahoo.com [68.142.200.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 6838D43D39 for ; Wed, 2 Feb 2005 12:43:27 +0000 (GMT) (envelope-from bart_veurink@yahoo.com) Received: (qmail 12610 invoked by uid 60001); 2 Feb 2005 12:43:27 -0000 Message-ID: <20050202124327.12608.qmail@web30101.mail.mud.yahoo.com> Received: from [83.116.202.50] by web30101.mail.mud.yahoo.com via HTTP; Wed, 02 Feb 2005 04:43:26 PST Date: Wed, 2 Feb 2005 04:43:26 -0800 (PST) From: Bart Veurink To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org In-Reply-To: <200502011750.j11HoNF6099820@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: amd64/76973: BTX Halted 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, 02 Feb 2005 12:43:28 -0000 Hello, This is my system: Case Enlight EN4102 300 Watt Floppy Samsung Floppydrive 3,5" Memory 256MB PC3200 DDR Processor AMD Sempron 2800+ FSB 333 Mainboard AS K7S41GX DDr mainboard met AC97 Audio Cooler Coolermaster USB 6x USB 2.0 + 2x USB Front LAN 10/100 MB On-Board Graphics 64MB 2D/3D VGA card Real Graphics on=board DVD/CD BEnQ 16x DVD Burner +/_ Double layer HDD Maxtor 120GB/7200RPM ATA-133 Mouse Logitech Wheelmouse Keyboard PS/2 Keyboard USB Stick Sweex 64MB FreeBSD-gnats-submit@FreeBSD.org wrote: Thank you very much for your problem report. It has the internal identification `amd64/76973'. The individual assigned to look at your report is: freebsd-amd64. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=76973 >Category: amd64 >Responsible: freebsd-amd64 >Synopsis: BTX Halted >Arrival-Date: Tue Feb 01 17:50:23 GMT 2005 --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 12:50:31 2005 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 A079E16A4CE for ; Wed, 2 Feb 2005 12:50:31 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D46443D48 for ; Wed, 2 Feb 2005 12:50:31 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j12CoVd7066576 for ; Wed, 2 Feb 2005 12:50:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j12CoVqh066575; Wed, 2 Feb 2005 12:50:31 GMT (envelope-from gnats) Date: Wed, 2 Feb 2005 12:50:31 GMT Message-Id: <200502021250.j12CoVqh066575@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Bart Veurink Subject: Re: amd64/76973: BTX Halted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bart Veurink List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 12:50:31 -0000 The following reply was made to PR amd64/76973; it has been noted by GNATS. From: Bart Veurink To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/76973: BTX Halted Date: Wed, 2 Feb 2005 04:41:18 -0800 (PST) --0-35886169-1107348078=:78545 Content-Type: text/plain; charset=us-ascii Hello, This is my system: Case Enlight EN4102 300 Watt Floppy Samsung Floppydrive 3,5" Memory 256MB PC3200 DDR Processor AMD Sempron 2800+ FSB 333 Cooler Coolermaster USB 6x USB 2.0 + 2x USB Front LAN 10/100 MB On-Board Graphics 64MB 2D/3D VGA card Real Graphics on=board DVD/CD BEnQ 16x DVD Burner +/_ Double layer HDD Maxtor 120GB/7200RPM ATA-133 Mouse Logitech Wheelmouse Keyboard PS/2 Keyboard USB Stick Sweex 64MB FreeBSD-gnats-submit@FreeBSD.org wrote: Thank you very much for your problem report. It has the internal identification `amd64/76973'. The individual assigned to look at your report is: freebsd-amd64. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=76973 >Category: amd64 >Responsible: freebsd-amd64 >Synopsis: BTX Halted >Arrival-Date: Tue Feb 01 17:50:23 GMT 2005 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-35886169-1107348078=:78545 Content-Type: text/html; charset=us-ascii
Hello,
 
This is my system:
Case        Enlight EN4102 300 Watt
Floppy      Samsung Floppydrive 3,5"
Memory    256MB PC3200 DDR
Processor AMD Sempron 2800+ FSB 333
Cooler      Coolermaster
USB         6x USB 2.0 + 2x USB Front
LAN         10/100 MB On-Board
Graphics   64MB 2D/3D VGA card Real Graphics on=board
DVD/CD   BEnQ 16x DVD Burner +/_ Double layer
HDD        Maxtor 120GB/7200RPM ATA-133
Mouse     Logitech Wheelmouse
Keyboard PS/2 Keyboard
USB Stick Sweex 64MB
FreeBSD-gnats-submit@FreeBSD.org wrote:
Thank you very much for your problem report.
It has the internal identification `amd64/76973'.
The individual assigned to look at your
report is: freebsd-amd64.

You can access the state of your problem report at any time
via this link:

http://www.freebsd.org/cgi/query-pr.cgi?pr=76973

>Category: amd64
>Responsible: freebsd-amd64
>Synopsis: BTX Halted
>Ar rival-Date: Tue Feb 01 17:50:23 GMT 2005

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-35886169-1107348078=:78545-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 12:50:38 2005 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 89F5F16A4CF for ; Wed, 2 Feb 2005 12:50:38 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B8443D53 for ; Wed, 2 Feb 2005 12:50:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j12Cocm3066609 for ; Wed, 2 Feb 2005 12:50:38 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j12CocHa066608; Wed, 2 Feb 2005 12:50:38 GMT (envelope-from gnats) Date: Wed, 2 Feb 2005 12:50:38 GMT Message-Id: <200502021250.j12CocHa066608@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Bart Veurink Subject: Re: amd64/76973: BTX Halted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bart Veurink List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 12:50:38 -0000 The following reply was made to PR amd64/76973; it has been noted by GNATS. From: Bart Veurink To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/76973: BTX Halted Date: Wed, 2 Feb 2005 04:43:26 -0800 (PST) --0-2032376258-1107348206=:8905 Content-Type: text/plain; charset=us-ascii Hello, This is my system: Case Enlight EN4102 300 Watt Floppy Samsung Floppydrive 3,5" Memory 256MB PC3200 DDR Processor AMD Sempron 2800+ FSB 333 Mainboard AS K7S41GX DDr mainboard met AC97 Audio Cooler Coolermaster USB 6x USB 2.0 + 2x USB Front LAN 10/100 MB On-Board Graphics 64MB 2D/3D VGA card Real Graphics on=board DVD/CD BEnQ 16x DVD Burner +/_ Double layer HDD Maxtor 120GB/7200RPM ATA-133 Mouse Logitech Wheelmouse Keyboard PS/2 Keyboard USB Stick Sweex 64MB FreeBSD-gnats-submit@FreeBSD.org wrote: Thank you very much for your problem report. It has the internal identification `amd64/76973'. The individual assigned to look at your report is: freebsd-amd64. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=76973 >Category: amd64 >Responsible: freebsd-amd64 >Synopsis: BTX Halted >Arrival-Date: Tue Feb 01 17:50:23 GMT 2005 --------------------------------- Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. --0-2032376258-1107348206=:8905 Content-Type: text/html; charset=us-ascii

Hello,
 
This is my system:
Case        Enlight EN4102 300 Watt
Floppy      Samsung Floppydrive 3,5"
Memory    256MB PC3200 DDR
Processor AMD Sempron 2800+ FSB 333
Mainboard AS K7S41GX DDr mainboard met AC97 Audio
Cooler      Coolermaster
USB         6x USB 2.0 + 2x USB Front
LAN         10/100 MB On-Board
Graphics   64MB 2D/3D VGA card Real Graphics on=board
DVD/CD   BEnQ 16x DVD Burner +/_ Double layer
HDD        Maxtor 120GB/7200RPM ATA-133
Mouse     Logitech Wheelmouse
Keyboard PS/2 Keyboard
USB Stick Sweex 64MB
FreeBSD-gnats-submit@FreeBSD.org wrote:
Thank you very much for your problem report.
It has the internal identification `amd64/76973'.
The individual assigned to look at your
report is: freebsd-amd64.

You can access the state of your problem report at any time
via this link:

http://www.freebsd.org/cgi/query-pr.cgi?pr=76973

>Category: amd64
>Responsible: freebsd-amd64
>Synopsis: BTX Halted
>Ar rival-Date: Tue Feb 01 17:50:23 GMT 2005

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses. --0-2032376258-1107348206=:8905-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 13:12:04 2005 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 05B1C16A4CE; Wed, 2 Feb 2005 13:12:04 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFF5A43D1F; Wed, 2 Feb 2005 13:12:02 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mailhost.stack.nl (Postfix) with ESMTP id CEC7F1F081; Wed, 2 Feb 2005 14:12:01 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 333) id C08872286D; Wed, 2 Feb 2005 14:12:01 +0100 (CET) Date: Wed, 2 Feb 2005 14:12:01 +0100 From: Marc Olzheim To: Bart Veurink Message-ID: <20050202131201.GA58933@stack.nl> References: <200502011750.j11HoNF6099820@freefall.freebsd.org> <20050202124118.79643.qmail@web30105.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050202124118.79643.qmail@web30105.mail.mud.yahoo.com> X-Operating-System: FreeBSD snail.stack.nl 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.6i cc: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/76973: BTX Halted 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, 02 Feb 2005 13:12:04 -0000 On Wed, Feb 02, 2005 at 04:41:18AM -0800, Bart Veurink wrote: > Processor AMD Sempron 2800+ FSB 333 Erhm. You might want to try the i386 distribution instead of the amd64 version... Marc From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 13:20:30 2005 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 4B4AD16A4CE for ; Wed, 2 Feb 2005 13:20:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13FCB43D45 for ; Wed, 2 Feb 2005 13:20:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j12DKTLF071615 for ; Wed, 2 Feb 2005 13:20:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j12DKTgC071614; Wed, 2 Feb 2005 13:20:29 GMT (envelope-from gnats) Date: Wed, 2 Feb 2005 13:20:29 GMT Message-Id: <200502021320.j12DKTgC071614@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Marc Olzheim Subject: Re: amd64/76973: BTX Halted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Marc Olzheim List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 13:20:30 -0000 The following reply was made to PR amd64/76973; it has been noted by GNATS. From: Marc Olzheim To: Bart Veurink Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/76973: BTX Halted Date: Wed, 2 Feb 2005 14:12:01 +0100 On Wed, Feb 02, 2005 at 04:41:18AM -0800, Bart Veurink wrote: > Processor AMD Sempron 2800+ FSB 333 Erhm. You might want to try the i386 distribution instead of the amd64 version... Marc From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 15:15:31 2005 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 2AFE516A4CE for ; Wed, 2 Feb 2005 15:15:31 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9951A43D46 for ; Wed, 2 Feb 2005 15:15:30 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so30594wra for ; Wed, 02 Feb 2005 07:15:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=P8qICIL1tyLWh7ZMs0/6USOhr3cuJBdzH0fodeeHCkgqmGGefLqNtQkipFNYVrN2BJffYjpdtfX7kUUv7RXRmqb9MqKHHq9eHXcIljJmyFzblrmRCrVmDu5KjrWtpXWTpMGcNHhDKB/Go4TZHnJOnWgcs2JyYlghVxAZ1nF5cGU= Received: by 10.54.30.15 with SMTP id d15mr2343wrd; Wed, 02 Feb 2005 07:08:35 -0800 (PST) Received: by 10.54.40.65 with HTTP; Wed, 2 Feb 2005 07:08:35 -0800 (PST) Message-ID: <2fd864e05020207086dd8f7c8@mail.gmail.com> Date: Wed, 2 Feb 2005 09:08:35 -0600 From: Astrodog To: Marc Olzheim In-Reply-To: <200502021320.j12DKTgC071614@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502021320.j12DKTgC071614@freefall.freebsd.org> cc: freebsd-amd64@freebsd.org Subject: Re: amd64/76973: BTX Halted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 15:15:31 -0000 On Wed, 02 Feb 2005 05:20:55 -0800 (PST), Marc Olzheim wrote: > The following reply was made to PR amd64/76973; it has been noted by GNATS. > > From: Marc Olzheim > To: Bart Veurink > Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org > Subject: Re: amd64/76973: BTX Halted > Date: Wed, 2 Feb 2005 14:12:01 +0100 > > On Wed, Feb 02, 2005 at 04:41:18AM -0800, Bart Veurink wrote: > > Processor AMD Sempron 2800+ FSB 333 > > Erhm. You might want to try the i386 distribution instead of the amd64 > version... > > Marc > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > Yes. Sadly, the Sempron does not support the AMD64 instructions, even on Socket 754. Never tried it before though, now I'll know what the error looks like when one of the guys here tries to use an AMD64 CD in an i386 machine atleast. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 15:22:33 2005 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 C646C16A4CE; Wed, 2 Feb 2005 15:22:33 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D58443D54; Wed, 2 Feb 2005 15:22:33 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from freefall.freebsd.org (pav@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j12FMX0v085720; Wed, 2 Feb 2005 15:22:33 GMT (envelope-from pav@freefall.freebsd.org) Received: (from pav@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j12FMXQ0085716; Wed, 2 Feb 2005 15:22:33 GMT (envelope-from pav) Date: Wed, 2 Feb 2005 15:22:33 GMT From: Pav Lucistnik Message-Id: <200502021522.j12FMXQ0085716@freefall.freebsd.org> To: bart_veurink@yahoo.com, pav@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/76973: BTX Halted 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, 02 Feb 2005 15:22:33 -0000 Synopsis: BTX Halted State-Changed-From-To: open->closed State-Changed-By: pav State-Changed-When: Wed Feb 2 15:22:10 GMT 2005 State-Changed-Why: Pilot error - amd64 system on i386 hardware. http://www.freebsd.org/cgi/query-pr.cgi?pr=76973 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 15:40:25 2005 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 9CA8E16A4CE for ; Wed, 2 Feb 2005 15:40:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 571F843D49 for ; Wed, 2 Feb 2005 15:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j12FePQF087719 for ; Wed, 2 Feb 2005 15:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j12FePcn087718; Wed, 2 Feb 2005 15:40:25 GMT (envelope-from gnats) Resent-Date: Wed, 2 Feb 2005 15:40:25 GMT Resent-Message-Id: <200502021540.j12FePcn087718@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, David Gilbert Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C67B816A4CE for ; Wed, 2 Feb 2005 15:37:42 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 778CE43D3F for ; Wed, 2 Feb 2005 15:37:42 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 7B13ED802; Wed, 2 Feb 2005 10:37:41 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 0F922636C; Wed, 2 Feb 2005 10:37:39 -0500 (EST) Message-Id: <20050202153739.0F922636C@canoe.dclg.ca> Date: Wed, 2 Feb 2005 10:37:39 -0500 (EST) From: David Gilbert To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/77011: consisten 5.3-p5 make crash on installworld. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Gilbert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 15:40:25 -0000 >Number: 77011 >Category: amd64 >Synopsis: consisten 5.3-p5 make crash on installworld. >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 02 15:40:24 GMT 2005 >Closed-Date: >Last-Modified: >Originator: David Gilbert >Release: FreeBSD 5.3-RELEASE-p5 amd64 >Organization: DaveG.ca >Environment: System: FreeBSD foo.test.ca 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Wed Feb 2 09:48:16 EST 2005 root@foo.test.ca:/usr/src/sys/amd64/compile/MYK amd64 Maching was a 5.3-RELEASE-amd64 base install cvsup'd to 5.3-RELEASE-p5 binaries. make -k installworld was run to plan 5.3-p5 binaries. Make still crashes. >Description: After running 'make buildworld' (with no issues), 'make installworld' dies: ===> gnu/usr.bin/groff/doc install-info --quiet --defsection=Miscellaneous --defentry= groff.info /usr/share/info/dir install -o root -g wheel -m 444 groff.info.gz /usr/share/info ===> gnu/usr.bin/groff/font ===> gnu/usr.bin/groff/font/devX100 Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src/gnu/usr.bin/groff/font. *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. >How-To-Repeat: 'make installworld' on amd64 >Fix: None known. 'make -k installworld' gets things done. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 15:44:15 2005 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 DE28A16A4CE; Wed, 2 Feb 2005 15:44:15 +0000 (GMT) Received: from daemon.mistermishap.net (167-49.nyc.dsl.access.net [166.84.167.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 124BA43D1D; Wed, 2 Feb 2005 15:44:15 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (localhost.mistermishap.net [127.0.0.1])j12FiDkJ093716; Wed, 2 Feb 2005 10:44:13 -0500 (EST) (envelope-from rob@hudson-trading.com) Received: from localhost (rob@localhost)j12FiDgH093713; Wed, 2 Feb 2005 10:44:13 -0500 (EST) X-Authentication-Warning: daemon.mistermishap.net: rob owned process doing -bs Date: Wed, 2 Feb 2005 10:44:13 -0500 (EST) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: John Baldwin In-Reply-To: <200501311755.00391.jhb@FreeBSD.org> Message-ID: <20050202094742.A93311@daemon.mistermishap.net> References: <20050127100818.M46092@daemon.mistermishap.net> <84dead72050128204479414c88@mail.gmail.com> <200501311755.00391.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@FreeBSD.org Subject: Re: 32-bit binary compatibility on 5.3-amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 15:44:16 -0000 On Mon, 31 Jan 2005, John Baldwin wrote: > On Friday 28 January 2005 11:44 pm, Joseph Koshy wrote: > > > > Clearly our IA32 emulation needs work. I've no idea > > why we don't support a sysarch(I386_{GET,SET}_LDT) operation > > for IA32 executables. > > Because amd64 doesn't have LDTs. Peter has hacks in place in the dynamic > 32-bit libraries that amd64 uses to use the different backing methods for > implementing TLS on amd64, but that stuff wasn't in 5.3. It might be in > 5.3-STABLE. Thanks for your responses. I don't think I want to worry about what version of STABLE is on all of our machines, and I'm certainly not going to run 6.x in production any time soon. Statically compiling certain utilities may be an option, but I think instead that we will run 2 separate build for i386 and amd64 until this is more fully supported. Does anyone know if full 32-bit support is slated for 3.4? - Rob Watt From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 2 22:18:23 2005 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 1286E16A4D7 for ; Wed, 2 Feb 2005 22:18:23 +0000 (GMT) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C940043D3F for ; Wed, 2 Feb 2005 22:18:22 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21659 invoked from network); 2 Feb 2005 22:18:22 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 2 Feb 2005 22:18:21 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j12MI5ET049221; Wed, 2 Feb 2005 17:18:18 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Wed, 2 Feb 2005 15:50:27 -0500 User-Agent: KMail/1.6.2 References: <20050127100818.M46092@daemon.mistermishap.net> <200501311755.00391.jhb@FreeBSD.org> <20050202094742.A93311@daemon.mistermishap.net> In-Reply-To: <20050202094742.A93311@daemon.mistermishap.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502021550.27604.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Rob Watt Subject: Re: 32-bit binary compatibility on 5.3-amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 22:18:23 -0000 On Wednesday 02 February 2005 10:44 am, Rob Watt wrote: > On Mon, 31 Jan 2005, John Baldwin wrote: > > On Friday 28 January 2005 11:44 pm, Joseph Koshy wrote: > > > Clearly our IA32 emulation needs work. I've no idea > > > why we don't support a sysarch(I386_{GET,SET}_LDT) operation > > > for IA32 executables. > > > > Because amd64 doesn't have LDTs. Peter has hacks in place in the dynamic > > 32-bit libraries that amd64 uses to use the different backing methods for > > implementing TLS on amd64, but that stuff wasn't in 5.3. It might be in > > 5.3-STABLE. > > Thanks for your responses. I don't think I want to worry about what > version of STABLE is on all of our machines, and I'm certainly not going > to run 6.x in production any time soon. Statically compiling certain > utilities may be an option, but I think instead that we will run 2 > separate build for i386 and amd64 until this is more fully supported. > > Does anyone know if full 32-bit support is slated for 3.4? I have verified that the fixes are in RELENG_5 and thus will be in 5.4. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 06:16:53 2005 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 E04CC16A4CE for ; Thu, 3 Feb 2005 06:16:52 +0000 (GMT) Received: from ctb-mesg1.saix.net (ctb-mesg1.saix.net [196.25.240.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BB5843D46 for ; Thu, 3 Feb 2005 06:16:51 +0000 (GMT) (envelope-from mark@aboutit.co.za) Received: from hermes.aboutit.co.za (tbnb-165-201-204.telkomadsl.co.za [165.165.201.204]) by ctb-mesg1.saix.net (Postfix) with ESMTP id 61F78511C for ; Thu, 3 Feb 2005 08:16:48 +0200 (SAST) Received: by hermes.aboutit.co.za (Postfix, from userid 65534) id ABEB6C0C0E; Thu, 3 Feb 2005 08:16:44 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by hermes.aboutit.co.za (Postfix) with ESMTP id 9C50EC0C5A for ; Thu, 3 Feb 2005 08:16:42 +0200 (SAST) Received: from mark.aboutit.co.za (unknown [10.10.10.10]) by hermes.aboutit.co.za (Postfix) with ESMTP id 42C0FC0AF1 for ; Thu, 3 Feb 2005 08:16:42 +0200 (SAST) From: Mark Bojara To: freebsd-amd64@freebsd.org In-Reply-To: <41FFD47B.2000505@freebsd.org> References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> Content-Type: text/plain Organization: AboutIT Online Date: Thu, 03 Feb 2005 08:16:53 +0200 Message-Id: <1107411413.43610.20.camel@mark.aboutit.co.za> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-5.3 required=8.0 tests=AWL,BAYES_00,EMAIL_ATTRIBUTION,HTML_00_10,IN_REP_TO, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 03 Feb 2005 06:16:53 -0000 Hey Scott I have the same problem with a 18 GB Seagate SCSI drive I checked around on seagates website and I cant seem to find firmware updates anywhere. Could you perhaps direct me to a link also I see other replies to this post show that this wont necessarily fix this problem. Thanks Mark On Tue, 2005-02-01 at 12:11 -0700, Scott Long wrote: > Mike Hunter wrote: > > > Hey everybody, > > > > I plopped the new 300 gig drives into the K8S based dual opteron, but I > > got some funny stuff upon rebooting (see the Dump Card State): > > > > ----- Forwarded message from Charlie Root ----- > > > > Copyright (c) 1992-2004 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 > > root@:/usr/obj/usr/src/sys/myserver > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: AMD Opteron(tm) Processor 248 (2192.07-MHz K8-class CPU) > > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > > Features=0x78bfbff > > AMD Features=0xe0500800 > > real memory = 8589934592 (8192 MB) > > avail memory = 8248307712 (7866 MB) > > ACPI APIC Table: > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > MADT: Forcing active-low polarity and level trigger for SCI > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 24-27 on motherboard > > ioapic2 irqs 28-31 on motherboard > > acpi0: on motherboard > > acpi0: Power Button (fixed) > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > > cpu0: on acpi0 > > cpu1: on acpi0 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib1: at device 6.0 on pci0 > > pci3: on pcib1 > > ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 > > ohci0: [GIANT-LOCKED] > > usb0: OHCI version 1.0, legacy support > > usb0: on ohci0 > > usb0: USB revision 1.0 > > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 3 ports with 3 removable, self powered > > ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 > > ohci1: [GIANT-LOCKED] > > usb1: OHCI version 1.0, legacy support > > usb1: on ohci1 > > usb1: USB revision 1.0 > > uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub1: 3 ports with 3 removable, self powered > > pci3: at device 6.0 (no driver attached) > > fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 > > miibus0: on fxp0 > > inphy0: on miibus0 > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > fxp0: Ethernet address: 00:e0:81:2b:4a:e7 > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > > ata0: channel #0 on atapci0 > > ata1: channel #1 on atapci0 > > pci0: at device 7.2 (no driver attached) > > pci0: at device 7.3 (no driver attached) > > pcib2: at device 10.0 on pci0 > > pci2: on pcib2 > > ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 > > ahd0: [GIANT-LOCKED] > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > > ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 > > ahd1: [GIANT-LOCKED] > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > > bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 > > miibus1: on bge0 > > brgphy0: on miibus1 > > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > > bge0: Ethernet address: 00:e0:81:2b:4b:12 > > bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 > > miibus2: on bge1 > > brgphy1: on miibus2 > > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > > bge1: Ethernet address: 00:e0:81:2b:4b:13 > > pci0: at device 10.1 (no driver attached) > > pcib3: at device 11.0 on pci0 > > pci1: on pcib3 > > pci0: at device 11.1 (no driver attached) > > acpi_button0: on acpi0 > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > > atkbd0: flags 0x1 irq 1 on atkbdc0 > > kbd0 at atkbd0 > > atkbd0: [GIANT-LOCKED] > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > > sio0: type 16550A, console > > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > > sio1: type 16550A > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > > fdc0: [FAST] > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > orm0: at iomem 0xc0000-0xc7fff on isa0 > > ppc0: cannot reserve I/O port range > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=0x100> > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > Timecounters tick every 1.000 msec > > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > > acd0: CDROM at ata0-master UDMA33 > > Waiting 5 seconds for SCSI devices to settle > > (probe2:ahd0:0:2:0): No or incomplete CDB sent to device. > > (probe2:ahd0:0:2:0): Protocol violation in Message-in phase. Attempting to abort. > > (probe2:ahd0:0:2:0): Abort Message Sent > > (probe2:ahd0:0:2:0): SCB 11 - Abort Tag Completed. > > found == 0x1 > > ahd0: Invalid Sequencer interrupt occurred. > > > >>>>>>>>>>>>>>>>>>>Dump Card State Begins <<<<<<<<<<<<<<<<< > > > > ahd0: Dumping Card State at program address 0x23c Mode 0x0 > > Card was paused > > INTSTAT[0x0] SELOID[0x2] SELID[0x40] HS_MAILBOX[0x0] > > INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] > > DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) > > SCSISIGI[0xe6]:(P_MESGIN|REQI|BSYI) SCSIPHASE[0x8]:(MSG_IN_PHASE) > > SCSIBUS[0x80] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) > > SCSISEQ0[0x0] SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) > > SEQCTL0[0x0] SEQINTCTL[0x6]:(INTMASK1|INTMASK2) SEQ_FLAGS[0x0] > > SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x2] KERNEL_QFREEZE_COUNT[0x2] > > MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x22]:(SPIORDY|SELDI) > > SSTAT1[0x11]:(REQINIT|PHASEMIS) SSTAT2[0x0] SSTAT3[0x0] > > PERRDIAG[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) > > LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] > > LQOSTAT1[0x0] LQOSTAT2[0x0] > > > > SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xb NEXTSCB 0xff80 > > qinstart = 30 qinfifonext = 30 > > QINFIFO: > > WAITING_TID_QUEUES: > > Pending list: > > 9 FIFO_USE[0x0] SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) > > SCB_SCSIID[0x47] > > Total 1 > > Kernel Free SCB list: 11 12 1 2 3 4 5 6 7 8 10 13 14 15 0 > > Sequencer Complete DMA-inprog list: > > Sequencer Complete list: > > Sequencer DMA-Up and Complete list: > > Sequencer On QFreeze and Complete list: > > > > > > ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xc > > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > > > > ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xb > > SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) > > SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > > SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] > > SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 > > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) > > LQIN: 0x8 0x0 0x0 0xc 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > > ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 > > ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 > > ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 > > > > SIMODE0[0xc]:(ENOVERRUN|ENIOERR) > > CCSCBCTL[0x4]:(CCSCBDIR) > > ahd0: REG0 == 0x3f9d, SINDEX = 0x10e, DINDEX = 0x106 > > ahd0: SCBPTR == 0xc, SCB_NEXT == 0xff80, SCB_NEXT2 == 0xffdb > > CDB 12 20 0 81 8 82 > > STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 > > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > > Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 > > da2 at ahd0 bus 0 target 4 lun 0 > > da2: Fixed Direct Access SCSI-3 device > > da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > da2: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > > da0 at ahd0 bus 0 target 1 lun 0 > > da0: Fixed Direct Access SCSI-3 device > > da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) > > da1 at ahd0 bus 0 target 2 lun 0 > > da1: Fixed Direct Access SCSI-3 device > > da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) > > SMP: AP CPU #1 Launched! > > Mounting root from ufs:/dev/da0s1a > > > > I saw similar things referenced here: > > > > http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001561.html > > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025016.html > > > > The second email talks about getting rom updates from seagate...but I > > called seagate and they said there's no new firmware out for these drives. > > > > The only other "answers" I'm getting about this is that "well, the 64 bit > > drivers aren't quite up to speed yet." > > > > The drives seem to be working fine...let me know if there's anything I can > > do to help. > > > > (Also, the "probe...abort message sent" stuff seems related to the 30 Gig > > drive...any cluse on that one?) > > > > Thanks, > > > > Mike > > The firmware on two of those drives is dangerouly old and broken. I'd > suggest contacting Seagate for an update, and keep a fire extinguisher > and some holy water nearby until they are upgraded. > > Scott > > _______________________________________________ > 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" > -- Mark Bojara - AboutIT Online - +27-12-460-1000 From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 07:41:41 2005 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 AB07A16A4CE for ; Thu, 3 Feb 2005 07:41:41 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF1C43D41 for ; Thu, 3 Feb 2005 07:41:40 +0000 (GMT) (envelope-from nick.lozinsky@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so182759wri for ; Wed, 02 Feb 2005 23:41:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=FxfpK9DmabK/U0lwl4lmy1ryqCC3T+LKOwYIG2YVol9iDQz63j2dF7SaqiqzCclZgpIBUF2LMl7vZtdgix0MuLchnoFGBUDfiHkK9aDMP/75u84QYMCDzZ1F9p38ihlu8k4bXwmzGRNO5CuE6NgT+R2i1r7hxvGiDkQ6QFAeQmw= Received: by 10.54.43.14 with SMTP id q14mr68279wrq; Wed, 02 Feb 2005 23:41:36 -0800 (PST) Received: by 10.54.29.28 with HTTP; Wed, 2 Feb 2005 23:41:36 -0800 (PST) Message-ID: <76ff51010502022341529322fc@mail.gmail.com> Date: Thu, 3 Feb 2005 01:41:36 -0600 From: "Nick M. Lozinsky" To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: amd64 and wine support in FreeBSD 5.3-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Nick M. Lozinsky" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 07:41:41 -0000 Hi, On my 64bit AMD laptop, using FreeBSD 5.3 Stable, I an unable to make install wine from ports. Looking through the Makefile, I find that it only support i386 architectures. Ho can I make it even with i386 support under amd64, or, is it even possible to make it on amd64? -- Nick M. Lozinsky From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 18:05:01 2005 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 E1A7F16A4CE for ; Thu, 3 Feb 2005 18:05:01 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C61A43D3F for ; Thu, 3 Feb 2005 18:05:01 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j13I4r104959; Thu, 3 Feb 2005 10:04:53 -0800 (PST) Date: Thu, 3 Feb 2005 10:04:53 -0800 From: Mike Hunter To: Mark Bojara Message-ID: <20050203180453.GA3175@ack.Berkeley.EDU> References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> <1107411413.43610.20.camel@mark.aboutit.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1107411413.43610.20.camel@mark.aboutit.co.za> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 03 Feb 2005 18:05:02 -0000 On Feb 03, "Mark Bojara" wrote: > I have the same problem with a 18 GB Seagate SCSI drive I checked around > on seagates website and I cant seem to find firmware updates anywhere. > Could you perhaps direct me to a link also I see other replies to this > post show that this wont necessarily fix this problem. I was told that you either have to call them or email them: http://www.seagate.com/support/disc/asp/tools/en/webhelp/How_To_Contact_Seagate.html discsupport@seagate.com I didn't see any way to get a new bios for the onboard adaptec card. Dmesg says my adaptec "card" is "Adaptec AIC7902 Ultra320 SCSI adapter", but a bios is nowhere to be found on their website. I've been told by others it's not possible to upgrade the onboard chipset's BIOS, but Scott thinks it's there somewhere. And now, a haiku: Rumors fly around Some say this, others say that I say "moof, scsi!" Mike From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 21:19:43 2005 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 7182A16A4CE for ; Thu, 3 Feb 2005 21:19:43 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FB3343D45 for ; Thu, 3 Feb 2005 21:19:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.19] (ibook-nai.samsco.home [192.168.254.19]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j13LIoUg017203; Thu, 3 Feb 2005 14:18:50 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42029545.5090707@samsco.org> Date: Thu, 03 Feb 2005 14:19:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <20050201190646.GA18651@ack.Berkeley.EDU> <41FFD47B.2000505@freebsd.org> <1107411413.43610.20.camel@mark.aboutit.co.za> <20050203180453.GA3175@ack.Berkeley.EDU> In-Reply-To: <20050203180453.GA3175@ack.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: dump card state: amd64 + 300G seagate + Adaptec AIC7902 + 5.3-stable 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, 03 Feb 2005 21:19:43 -0000 Mike Hunter wrote: > On Feb 03, "Mark Bojara" wrote: > > >>I have the same problem with a 18 GB Seagate SCSI drive I checked around >>on seagates website and I cant seem to find firmware updates anywhere. >>Could you perhaps direct me to a link also I see other replies to this >>post show that this wont necessarily fix this problem. > > > I was told that you either have to call them or email them: > > http://www.seagate.com/support/disc/asp/tools/en/webhelp/How_To_Contact_Seagate.html > > discsupport@seagate.com > > I didn't see any way to get a new bios for the onboard adaptec card. Dmesg > says my adaptec "card" is "Adaptec AIC7902 Ultra320 SCSI adapter", but > a bios is nowhere to be found on their website. I've been told by others > it's not possible to upgrade the onboard chipset's BIOS, but Scott thinks > it's there somewhere. The BIOS version should show up in the Adaptec banner during boot. Adaptec does provide BIOS updates for the add-in cards that it sells. For the on-motherboard chips, you'll have to contact the motherboard vendor for a BIOS update since the Adaptec and System BIOS images are usually combined. BIOS updates are rarely for fixing runtime problems. The Adaptec SCSI chips do not use a traditional microprocessor and firmware image, so it's not as if updating the BIOS will give you a new firmware that will make the chip run differently, like with an LSI SCSI chip or a RAID card. At best, the BIOS might set initial state of the chip to enable/disable/tweak certain features. The OS driver is what really controls the runtime operation, though. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 22:04:23 2005 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 5A0EB16A4CE; Thu, 3 Feb 2005 22:04:23 +0000 (GMT) Received: from wmptl.net (mail.wmptl.com [216.8.159.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC92443D3F; Thu, 3 Feb 2005 22:04:22 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from r3140ca ([10.0.0.104]) by wmptl.net (8.13.1/8.12.9) with ESMTP id j13M4OMQ092789; Thu, 3 Feb 2005 17:04:24 -0500 (EST) From: "Nathan Vidican" To: Date: Thu, 3 Feb 2005 17:04:21 -0500 Message-ID: <000001c50a3c$50f2eba0$6800000a@r3140ca> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.44 cc: questions@freebsd.org Subject: Intel EMT64 Xeon vs AMD Opteron 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, 03 Feb 2005 22:04:23 -0000 Hey all, Just looking for general opinions and/or advice regarding use of one over the other. Cost wise, AMD Opteron 246 is roughly the same cost as a 3.0Ghz Xeon ... But how do they compare performance wise; specifically related to FreeBSD? (Not subscribed to both lists I sent this to, please reply directly via email and cc the list if you could - thanks) -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 22:41:44 2005 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 9DDE216A4CE for ; Thu, 3 Feb 2005 22:41:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE02043D5C for ; Thu, 3 Feb 2005 22:41:43 +0000 (GMT) (envelope-from linicks@gmail.com) Received: by rproxy.gmail.com with SMTP id 40so255296rnz for ; Thu, 03 Feb 2005 14:41:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=QeYYTvZMRfiSndJATC93WbSOlN2So8tRPo9+w2O2LrBKnBmmf+n9jKzMIj8xuBLikxDTPYuKuvtRfFWlUpphcFaYZCplpQ1TS1kbd28JJv8r8wCgc3RTw7jVVn5qLi+jKxfSM/9CGeNzdAQ6vNUNpOEazP4BiCmsfkRMei7qb9c= Received: by 10.38.8.49 with SMTP id 49mr30563rnh; Thu, 03 Feb 2005 14:41:43 -0800 (PST) Received: by 10.38.8.20 with HTTP; Thu, 3 Feb 2005 14:41:43 -0800 (PST) Message-ID: Date: Thu, 3 Feb 2005 15:41:43 -0700 From: Nick Pavlica To: Nathan Vidican In-Reply-To: <000001c50a3c$50f2eba0$6800000a@r3140ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000001c50a3c$50f2eba0$6800000a@r3140ca> cc: amd64@freebsd.org cc: questions@freebsd.org Subject: Re: Intel EMT64 Xeon vs AMD Opteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nick Pavlica List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 22:41:44 -0000 I think this would depend on your application, but I have hear allot of good things about AMD 64. --Nick On Thu, 3 Feb 2005 17:04:21 -0500, Nathan Vidican wrote: > Hey all, > > Just looking for general opinions and/or advice regarding use of one over > the other. > > Cost wise, AMD Opteron 246 is roughly the same cost as a 3.0Ghz Xeon ... But > how do they compare performance wise; specifically related to FreeBSD? > > (Not subscribed to both lists I sent this to, please reply directly via > email and cc the list if you could - thanks) > > -- > Nathan Vidican > nvidican@wmptl.com > Windsor Match Plate & Tool Ltd. > http://www.wmptl.com/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 3 22:57:58 2005 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 EA54C16A4CF for ; Thu, 3 Feb 2005 22:57:58 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFCE643D1F for ; Thu, 3 Feb 2005 22:57:56 +0000 (GMT) (envelope-from nomadlogic@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so325532rne for ; Thu, 03 Feb 2005 14:57:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=tcGhAXbn1MXWKW0u/AbRc3+kWqL3ow6OylsXbZAMzI3qmYgxikLbopAz5X6cNSI0NJnmDm/YRuvM9kwXtxS2HDiWsYg5i7B9M0O8l6udnm9sBfR3oRM06tI7umQaF6iTti8yATRXU4DezMiZqbiQiy1fkAopjrd+gjKiPJsQ9vk= Received: by 10.38.75.70 with SMTP id x70mr303341rna; Thu, 03 Feb 2005 14:57:55 -0800 (PST) Received: by 10.38.14.51 with HTTP; Thu, 3 Feb 2005 14:57:55 -0800 (PST) Message-ID: <57d71000050203145719168999@mail.gmail.com> Date: Thu, 3 Feb 2005 14:57:55 -0800 From: pete wright To: Nick Pavlica In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000001c50a3c$50f2eba0$6800000a@r3140ca> cc: amd64@freebsd.org cc: questions@freebsd.org cc: Nathan Vidican Subject: Re: Intel EMT64 Xeon vs AMD Opteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pete wright List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 22:57:59 -0000 On Thu, 3 Feb 2005 15:41:43 -0700, Nick Pavlica wrote: > I think this would depend on your application, but I have hear allot > of good things about AMD 64. > > --Nick > > > On Thu, 3 Feb 2005 17:04:21 -0500, Nathan Vidican wrote: > > Hey all, > > > > Just looking for general opinions and/or advice regarding use of one over > > the other. > > > > Cost wise, AMD Opteron 246 is roughly the same cost as a 3.0Ghz Xeon ... But > > how do they compare performance wise; specifically related to FreeBSD? > > > > (Not subscribed to both lists I sent this to, please reply directly via > > email and cc the list if you could - thanks) > > hard to say w/o knowing what you will using it for. from my experience AMD64 seems like it may be better investment for the future, seing as you are not going to be stuck with a 32 bit proc. in a year or two's time. honestly tho it really depends on what you are going to be processing. -p -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 10:37:09 2005 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 8FF3516A4CE for ; Fri, 4 Feb 2005 10:37:09 +0000 (GMT) Received: from web26801.mail.ukl.yahoo.com (web26801.mail.ukl.yahoo.com [217.146.176.77]) by mx1.FreeBSD.org (Postfix) with SMTP id E4C9643D49 for ; Fri, 4 Feb 2005 10:37:08 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 21610 invoked by uid 60001); 4 Feb 2005 10:37:08 -0000 Message-ID: <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> Received: from [194.248.174.58] by web26801.mail.ukl.yahoo.com via HTTP; Fri, 04 Feb 2005 11:37:08 CET Date: Fri, 4 Feb 2005 11:37:08 +0100 (CET) From: Claus Guttesen To: Nathan Vidican , amd64@freebsd.org In-Reply-To: <000001c50a3c$50f2eba0$6800000a@r3140ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: questions@freebsd.org Subject: Re: Intel EMT64 Xeon vs AMD Opteron 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, 04 Feb 2005 10:37:09 -0000 > Cost wise, AMD Opteron 246 is roughly the same cost > as a 3.0Ghz Xeon ... But > how do they compare performance wise; specifically > related to FreeBSD? We have a dual xeon (nocona) @ 3.2 GHz and a dual opteron @ 2 GHz, both with 4 GB RAM and running the amd64-port. My impression is that the opteron performs *slightly* better than it's Intel-cousin. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 11:51:06 2005 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 28CA816A4CE for ; Fri, 4 Feb 2005 11:51:06 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACDF343D39 for ; Fri, 4 Feb 2005 11:51:05 +0000 (GMT) (envelope-from ccnp.bsd@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so398312rne for ; Fri, 04 Feb 2005 03:51:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=EMIaaPCZ5o90n/sJdT/tETiw+FtWmaDd/uaNEnCGwTeC7eilSVdf+tnfsx8uMpmD+r5+WbX0J9OdeM7ffq/d6mSZtxvfQZ0VSYduRMf2DyVzLq+nDFBBbiLyVf50BHzB2SzLPbUI2WmtGi2XJLEf01guAgom44y86a0I/7I/1dc= Received: by 10.38.79.74 with SMTP id c74mr121887rnb; Fri, 04 Feb 2005 03:51:04 -0800 (PST) Received: by 10.38.208.42 with HTTP; Fri, 4 Feb 2005 03:51:04 -0800 (PST) Message-ID: Date: Fri, 4 Feb 2005 05:51:04 -0600 From: Nick Lozinsky To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: amd64 and wine X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nick Lozinsky List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 11:51:06 -0000 Hello: Running FreeBSD5.3-STABLE on AMD64 3200+; I've attempted to `make install' wine from the ports tree, and surprisingle enough, it is only able to compile on I386 architectures. I looked through the Makefile, and saw the i386 support, only. Does wine have any support on amd64, or is it possible to compile on amd64 for backward 32-bit compatibility? Thanks in advance. Nick From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 15:20:17 2005 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 13C5416A4CE for ; Fri, 4 Feb 2005 15:20:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4FCA43D53 for ; Fri, 4 Feb 2005 15:20:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j14FKGda086821 for ; Fri, 4 Feb 2005 15:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j14FKGdL086820; Fri, 4 Feb 2005 15:20:16 GMT (envelope-from gnats) Resent-Date: Fri, 4 Feb 2005 15:20:16 GMT Resent-Message-Id: <200502041520.j14FKGdL086820@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, John Clisham Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97A1416A4CE for ; Fri, 4 Feb 2005 15:18:22 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B0543D2F for ; Fri, 4 Feb 2005 15:18:22 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j14FIMau051492 for ; Fri, 4 Feb 2005 15:18:22 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j14FIMkh051490; Fri, 4 Feb 2005 15:18:22 GMT (envelope-from nobody) Message-Id: <200502041518.j14FIMkh051490@www.freebsd.org> Date: Fri, 4 Feb 2005 15:18:22 GMT From: John Clisham To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/77101: Please include ULi M1689 LAN, SATA, and AMD64 AGP drivers 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, 04 Feb 2005 15:20:17 -0000 >Number: 77101 >Category: amd64 >Synopsis: Please include ULi M1689 LAN, SATA, and AMD64 AGP drivers >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Feb 04 15:20:16 GMT 2005 >Closed-Date: >Last-Modified: >Originator: John Clisham >Release: 5.3-STABLE >Organization: - >Environment: N/A - FreeBSD 5.3-STABLE AMD64 >Description: The M1698 chipset from ULi is a 'fairly' new AMD64 chipset. They provide GPL'd drivers for Linux Kernel 2.6.x for LAN and SATA. They also provided a patch to AGP_AMD64 driver on linux. I've tested and used all for a couple months without issue on Linux. Looks like their targeting Linux Kernel 2.6.12 for inclusion. I'd like to see support for this chipset in FreeBSD. I have the linux source that I can email. Is this possible? >How-To-Repeat: >Fix: Include support for ULi AMD64 M1689 chipset >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 17:43:56 2005 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 A704F16A4CE for ; Fri, 4 Feb 2005 17:43:56 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 636EB43D46 for ; Fri, 4 Feb 2005 17:43:54 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j14HhsZ28455 for freebsd-amd64@freebsd.org; Fri, 4 Feb 2005 09:43:54 -0800 (PST) Date: Fri, 4 Feb 2005 09:43:54 -0800 From: Mike Hunter To: freebsd-amd64@freebsd.org Message-ID: <20050204174353.GA25414@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: "Out of ktrace request objects" 5.3-STABLE 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, 04 Feb 2005 17:43:56 -0000 Hi, Dmesg told me: Out of ktrace request objects Indeed, I was ktracing yesterday. I saw this post but no replies: http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/041586.html My system is a dual opteron: FreeBSD myserver.Net.Berkeley.EDU 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat Dec 11 10:56:35 PST 2004 root@:/usr/obj/usr/src/sys/myserver amd64 Should I be worried? Mike From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 22:12:29 2005 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 CC7F616A580 for ; Fri, 4 Feb 2005 22:12:27 +0000 (GMT) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C710E43D45 for ; Fri, 4 Feb 2005 22:12:26 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 26091 invoked from network); 4 Feb 2005 22:12:26 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 4 Feb 2005 22:12:26 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j14MCGNK065270; Fri, 4 Feb 2005 17:12:21 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: amd64@FreeBSD.org Date: Fri, 4 Feb 2005 15:58:28 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200502041558.28521.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: peter@FreeBSD.org Subject: [PATCH] Change atomic operations to use fences for memory barriers 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, 04 Feb 2005 22:12:29 -0000 The patch below changes the atomic operations on amd64 to use the cheaper fence instructions for memory barriers. I'd like people to test it to see if 1) it breaks things or not, and 2) if it impacts performance either in a good way or a bad way. For this last I'm curious about both UP and SMP as my initial guess is that it will help on UP but might hurt on SMP. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 22:12:30 2005 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 CD7FE16A5B9 for ; Fri, 4 Feb 2005 22:12:29 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B61943D2D for ; Fri, 4 Feb 2005 22:12:29 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30743 invoked from network); 4 Feb 2005 22:12:29 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 4 Feb 2005 22:12:29 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j14MCGNL065270; Fri, 4 Feb 2005 17:12:24 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Fri, 4 Feb 2005 16:06:34 -0500 User-Agent: KMail/1.6.2 References: <20050204174353.GA25414@ack.Berkeley.EDU> In-Reply-To: <20050204174353.GA25414@ack.Berkeley.EDU> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502041606.34720.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Mike Hunter Subject: Re: "Out of ktrace request objects" 5.3-STABLE 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, 04 Feb 2005 22:12:30 -0000 On Friday 04 February 2005 12:43 pm, Mike Hunter wrote: > Hi, > > Dmesg told me: > > Out of ktrace request objects > > Indeed, I was ktracing yesterday. > > I saw this post but no replies: > > http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/041586.html > > My system is a dual opteron: > > FreeBSD myserver.Net.Berkeley.EDU 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat > Dec 11 10:56:35 PST 2004 root@:/usr/obj/usr/src/sys/myserver amd64 > > Should I be worried?' It just means that some events weren't logged (kdump will tell you when there are dropped events via a 'events dropped' message, but it can't tell you how many were dropped or what kind they were). You can up the number of request objects in the pool via the kern.ktrace.request_pool sysctl. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 4 22:29:39 2005 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 8A5DD16A4CE; Fri, 4 Feb 2005 22:29:39 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E81E343D45; Fri, 4 Feb 2005 22:29:38 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j14MTD5H038306; Fri, 4 Feb 2005 15:29:13 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <4203F750.1060102@freebsd.org> Date: Fri, 04 Feb 2005 15:29:36 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200502041558.28521.jhb@FreeBSD.org> In-Reply-To: <200502041558.28521.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: amd64@freebsd.org cc: peter@freebsd.org Subject: Re: [PATCH] Change atomic operations to use fences for memory barriers 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, 04 Feb 2005 22:29:39 -0000 John Baldwin wrote: > The patch below changes the atomic operations on amd64 to use the cheaper > fence instructions for memory barriers. I'd like people to test it to see if > 1) it breaks things or not, and 2) if it impacts performance either in a good > way or a bad way. For this last I'm curious about both UP and SMP as my > initial guess is that it will help on UP but might hurt on SMP. > I think you forgot the patch. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 00:09:20 2005 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 BDBF116A4CE; Sat, 5 Feb 2005 00:09:20 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52D2343D3F; Sat, 5 Feb 2005 00:09:20 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id j1509JGd092177; Fri, 4 Feb 2005 19:09:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id j150AodS014151; Fri, 4 Feb 2005 19:10:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 80F547306E; Fri, 4 Feb 2005 19:09:19 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050205000919.80F547306E@freebsd-current.sentex.ca> Date: Fri, 4 Feb 2005 19:09:19 -0500 (EST) X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on clamscanner3 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [releng_5 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: Sat, 05 Feb 2005 00:09:21 -0000 TB --- 2005-02-04 22:53:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-04 22:53:06 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-02-04 22:53:06 - checking out the source tree TB --- 2005-02-04 22:53:06 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-02-04 22:53:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-04 23:00:59 - building world (CFLAGS=-O -pipe) TB --- 2005-02-04 23:00:59 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-04 23:00:59 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-02-04 23:53:27 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-04 23:53:27 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-04 23:53:27 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Feb 4 23:53:28 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Feb 5 00:02:46 UTC 2005 TB --- 2005-02-05 00:02:46 - generating LINT kernel config TB --- 2005-02-05 00:02:46 - cd /home/tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/conf TB --- 2005-02-05 00:02:46 - /usr/bin/make -B LINT TB --- 2005-02-05 00:02:46 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-05 00:02:46 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-05 00:02:46 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Feb 5 00:02:46 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/sched_4bsd.c:1226: warning: no previous prototype for 'sched_pctcpu' In file included from /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_switch.c:108, from /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/sched_4bsd.c:1235: ./machine/critical.h:47: warning: nested extern declaration of `cpu_critical_fork_exit' In file included from /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/sched_4bsd.c:1235: /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_switch.c:133: warning: no previous prototype for 'choosethread' /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_switch.c:281: warning: no previous prototype for 'adjustrunqueue' /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_switch.c:452: confused by earlier errors, bailing out *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2005-02-05 00:09:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-05 00:09:19 - ERROR: failed to build lint kernel TB --- 2005-02-05 00:09:19 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 03:38:45 2005 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 8B84516A4CE for ; Sat, 5 Feb 2005 03:38:45 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B167C43D2F for ; Sat, 5 Feb 2005 03:38:44 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so498409wra for ; Fri, 04 Feb 2005 19:38:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YYYb/xAB6MNP6AZHhUXHMACM3DYhdBOUxvvL5xwId1ydYH0MYftlhO+CkMbR1W5IVYgrdrUuc+AMGt/aNJjULCzf4+CAW1dfjdmnAEAxJqPFIwg71aQ09ChKWmSbAnwoB+st5hb6EwTLlKwcKZxNOrW8miaONFdYJAOrtvH8tm8= Received: by 10.54.5.12 with SMTP id 12mr285437wre; Fri, 04 Feb 2005 19:38:43 -0800 (PST) Received: by 10.54.40.65 with HTTP; Fri, 4 Feb 2005 19:38:43 -0800 (PST) Message-ID: <2fd864e05020419382a5e21b3@mail.gmail.com> Date: Fri, 4 Feb 2005 19:38:43 -0800 From: Astrodog To: Claus Guttesen In-Reply-To: <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000001c50a3c$50f2eba0$6800000a@r3140ca> <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> cc: amd64@freebsd.org cc: questions@freebsd.org cc: Nathan Vidican Subject: Re: Intel EMT64 Xeon vs AMD Opteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 03:38:45 -0000 On Fri, 4 Feb 2005 11:37:08 +0100 (CET), Claus Guttesen wrote: > > Cost wise, AMD Opteron 246 is roughly the same cost > > as a 3.0Ghz Xeon ... But > > how do they compare performance wise; specifically > > related to FreeBSD? > > We have a dual xeon (nocona) @ 3.2 GHz and a dual > opteron @ 2 GHz, both with 4 GB RAM and running the > amd64-port. My impression is that the opteron performs > *slightly* better than it's Intel-cousin. > > regards > Claus > > _______________________________________________ > 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 what I understand, EM64T is essentally an extention to x86, so it will understand the AMD64 instructions, much the same way an Athlon64 does. Opteron, once again, from what I've read on the topic is "Actual" 64-bit, not an emulated version. Generally, I find Opteron to be the best "Bang for your Buck", though what motherboard, and what features you need there may also play a role there. AMD, so far, has implied that the dual core opterons will be Socket 940, If that pans out, the 940-based solution will be significantly more expandable, since there's little to no chance of Intel continuing to use their current Xeon socket when their Dual Core offerings come out, and I suspect it would be technically impossible, given the Memory Controller issues that its bound to create. Since AMD put the memory controller on-die, they can resolve this issue in the core, and not involve the chipsets of the motherboard itself. Remember, Hyperthreading isn't dual core, its kinda like adding another "Lane" to the processing pipeline of a single processor, so that when something stalls, other things can still happen. Hypertransport, on the other hand is AMD's method of connecting SMP CPUs to eachother, memory, and devices on the motherboard. Sorry about the Hypertransport/Hyperthreading thing, but there seems to be a great deal of confusion about what each are, and what's good/bad about them, and they relate to the AMD/Intel decsion you're making pretty explicitly. Personally, I say go with the Opteron. Worst case, performance and reliability are the same, and you're supporting the underdog. Best case, it blows your socks off, and in a year, you can go dual core. Either way, you can't loose. ---- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 03:43:09 2005 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 F0A5316A4CE for ; Sat, 5 Feb 2005 03:43:08 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 910F043D49 for ; Sat, 5 Feb 2005 03:43:05 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so498622wra for ; Fri, 04 Feb 2005 19:43:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=l5/WD/LcqdzMOMW2QQrfN3LAz4ocyAOS8y/38I7abWmVWMZfWDz2RA3B8sq0+mJRPnZ6jnssNwM446BnCOfd81ZYuGDoxtR36siXu9CmpvdmlKjNEf9HJgD0ar4gVkZatGsXrd61wWBJsZ52vp8xSQ34yhi2dxDA+JogULQlRp8= Received: by 10.54.32.55 with SMTP id f55mr274619wrf; Fri, 04 Feb 2005 19:43:05 -0800 (PST) Received: by 10.54.40.65 with HTTP; Fri, 4 Feb 2005 19:43:04 -0800 (PST) Message-ID: <2fd864e05020419434705bf70@mail.gmail.com> Date: Fri, 4 Feb 2005 19:43:04 -0800 From: Astrodog To: Claus Guttesen In-Reply-To: <2fd864e05020419382a5e21b3@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000001c50a3c$50f2eba0$6800000a@r3140ca> <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> <2fd864e05020419382a5e21b3@mail.gmail.com> cc: amd64@freebsd.org cc: questions@freebsd.org cc: Nathan Vidican Subject: Re: Intel EMT64 Xeon vs AMD Opteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 03:43:09 -0000 On Fri, 4 Feb 2005 19:38:43 -0800, Astrodog wrote: > On Fri, 4 Feb 2005 11:37:08 +0100 (CET), Claus Guttesen > wrote: > > > Cost wise, AMD Opteron 246 is roughly the same cost > > > as a 3.0Ghz Xeon ... But > > > how do they compare performance wise; specifically > > > related to FreeBSD? > > > > We have a dual xeon (nocona) @ 3.2 GHz and a dual > > opteron @ 2 GHz, both with 4 GB RAM and running the > > amd64-port. My impression is that the opteron performs > > *slightly* better than it's Intel-cousin. > > > > regards > > Claus > > > > _______________________________________________ > > 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 what I understand, EM64T is essentally an extention to x86, so > it will understand the AMD64 instructions, much the same way an > Athlon64 does. Opteron, once again, from what I've read on the topic > is "Actual" 64-bit, not an emulated version. Generally, I find Opteron > to be the best "Bang for your Buck", though what motherboard, and what > features you need there may also play a role there. AMD, so far, has > implied that the dual core opterons will be Socket 940, If that pans > out, the 940-based solution will be significantly more expandable, > since there's little to no chance of Intel continuing to use their > current Xeon socket when their Dual Core offerings come out, and I > suspect it would be technically impossible, given the Memory > Controller issues that its bound to create. Since AMD put the memory > controller on-die, they can resolve this issue in the core, and not > involve the chipsets of the motherboard itself. > Remember, Hyperthreading isn't dual core, its kinda like adding > another "Lane" to the processing pipeline of a single processor, so > that when something stalls, other things can still happen. > Hypertransport, on the other hand is AMD's method of connecting SMP > CPUs to eachother, memory, and devices on the motherboard. > > Sorry about the Hypertransport/Hyperthreading thing, but there seems > to be a great deal of confusion about what each are, and what's > good/bad about them, and they relate to the AMD/Intel decsion you're > making pretty explicitly. > > Personally, I say go with the Opteron. Worst case, performance and > reliability are the same, and you're supporting the underdog. Best > case, it blows your socks off, and in a year, you can go dual core. > Either way, you can't loose. > > ---- Harrison Grundy > D'oh. One other thing. In the benchmarks I've seen, Opterons "Play Nicer" with SMP because of the Hypertransport setup in some applications. (IE, they don't fight over memory the way Xeons do). Look for a motherboard that uses a "4+4" or "4+2" memory configuration to take full advantage of this. (Differnt memory for each processor, kinda) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 04:25:40 2005 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 0E54816A4CE; Sat, 5 Feb 2005 04:25:40 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6752D43D54; Sat, 5 Feb 2005 04:25:38 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j154OrAZ062261; Fri, 4 Feb 2005 21:24:54 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <42044AAF.1010002@freebsd.org> Date: Fri, 04 Feb 2005 21:25:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <000001c50a3c$50f2eba0$6800000a@r3140ca> <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> <2fd864e05020419382a5e21b3@mail.gmail.com> In-Reply-To: <2fd864e05020419382a5e21b3@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: amd64@freebsd.org cc: questions@freebsd.org cc: Nathan Vidican Subject: Re: Intel EMT64 Xeon vs AMD Opteron 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, 05 Feb 2005 04:25:40 -0000 Astrodog wrote: > On Fri, 4 Feb 2005 11:37:08 +0100 (CET), Claus Guttesen > wrote: > >>>Cost wise, AMD Opteron 246 is roughly the same cost >>>as a 3.0Ghz Xeon ... But >>>how do they compare performance wise; specifically >>>related to FreeBSD? >> >>We have a dual xeon (nocona) @ 3.2 GHz and a dual >>opteron @ 2 GHz, both with 4 GB RAM and running the >>amd64-port. My impression is that the opteron performs >>*slightly* better than it's Intel-cousin. >> >>regards >>Claus >> >>_______________________________________________ >>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 what I understand, EM64T is essentally an extention to x86, so > it will understand the AMD64 instructions, much the same way an > Athlon64 does. Opteron, once again, from what I've read on the topic > is "Actual" 64-bit, not an emulated version. Generally, I find Opteron > to be the best "Bang for your Buck", though what motherboard, and what > features you need there may also play a role there. AMD, so far, has > implied that the dual core opterons will be Socket 940, If that pans > out, the 940-based solution will be significantly more expandable, > since there's little to no chance of Intel continuing to use their > current Xeon socket when their Dual Core offerings come out, and I > suspect it would be technically impossible, given the Memory > Controller issues that its bound to create. Since AMD put the memory > controller on-die, they can resolve this issue in the core, and not > involve the chipsets of the motherboard itself. > Remember, Hyperthreading isn't dual core, its kinda like adding > another "Lane" to the processing pipeline of a single processor, so > that when something stalls, other things can still happen. > Hypertransport, on the other hand is AMD's method of connecting SMP > CPUs to eachother, memory, and devices on the motherboard. > > Sorry about the Hypertransport/Hyperthreading thing, but there seems > to be a great deal of confusion about what each are, and what's > good/bad about them, and they relate to the AMD/Intel decsion you're > making pretty explicitly. > > Personally, I say go with the Opteron. Worst case, performance and > reliability are the same, and you're supporting the underdog. Best > case, it blows your socks off, and in a year, you can go dual core. > Either way, you can't loose. > Both the AMD and Intel offering are just extensions to the ia32 design. Opteron is no more 'true' 64-bit than Nacona is. There are differences in features; Opteron and Athlon64 have dropped some legacy features, EM64T doesn't (yet) have NX page protection support, etc, etc. Beyond that, they operate in pretty much identical ways. Where Opteron has the advantage is that it doesn't have the long instruction pipeline of Nacona, and it has HyperTransport and an embedded memory controller instead of Intel MCH bottleneck. Nacona has Hyperthreading, which can be a benefit, but it's mostly a toss-up. As far as a real-world comparison, I just did a 6-CURRENT buildworld on the following machines: 2x Nacona 2.8GHz, HTT enabled 4GB RAM FreeBSD 6-CURRENT/i386 (32 bit mode) ICH5 SATA, Maxtor 2x Opteron 246 2GB RAM FreeBSD 6-CURRENT/amd64 (64 bit mode) Adaptec U160 SCSI, Seagate The time to build world was almost identical at 31 minutes each. Granted, the buildworld test isn't a very good overall test as it's often I/O bound, but it gives a rough estimate. I haven't spent much time running the Nacona in 64 bit mode, but what I did didn't suggest that it would perform all that much better. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 04:29:14 2005 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 2AAC316A4CE; Sat, 5 Feb 2005 04:29:14 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A8A943D49; Sat, 5 Feb 2005 04:29:13 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j154Se52062543; Fri, 4 Feb 2005 21:28:40 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <42044B92.4040102@freebsd.org> Date: Fri, 04 Feb 2005 21:29:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <000001c50a3c$50f2eba0$6800000a@r3140ca> <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> <2fd864e05020419382a5e21b3@mail.gmail.com> <2fd864e05020419434705bf70@mail.gmail.com> In-Reply-To: <2fd864e05020419434705bf70@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: amd64@freebsd.org cc: questions@freebsd.org cc: Nathan Vidican Subject: Re: Intel EMT64 Xeon vs AMD Opteron 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, 05 Feb 2005 04:29:14 -0000 Astrodog wrote: > On Fri, 4 Feb 2005 19:38:43 -0800, Astrodog wrote: > >>On Fri, 4 Feb 2005 11:37:08 +0100 (CET), Claus Guttesen >> wrote: >> >>>>Cost wise, AMD Opteron 246 is roughly the same cost >>>>as a 3.0Ghz Xeon ... But >>>>how do they compare performance wise; specifically >>>>related to FreeBSD? >>> >>>We have a dual xeon (nocona) @ 3.2 GHz and a dual >>>opteron @ 2 GHz, both with 4 GB RAM and running the >>>amd64-port. My impression is that the opteron performs >>>*slightly* better than it's Intel-cousin. >>> >>>regards >>>Claus >>> >>>_______________________________________________ >>>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 what I understand, EM64T is essentally an extention to x86, so >>it will understand the AMD64 instructions, much the same way an >>Athlon64 does. Opteron, once again, from what I've read on the topic >>is "Actual" 64-bit, not an emulated version. Generally, I find Opteron >>to be the best "Bang for your Buck", though what motherboard, and what >>features you need there may also play a role there. AMD, so far, has >>implied that the dual core opterons will be Socket 940, If that pans >>out, the 940-based solution will be significantly more expandable, >>since there's little to no chance of Intel continuing to use their >>current Xeon socket when their Dual Core offerings come out, and I >>suspect it would be technically impossible, given the Memory >>Controller issues that its bound to create. Since AMD put the memory >>controller on-die, they can resolve this issue in the core, and not >>involve the chipsets of the motherboard itself. >> Remember, Hyperthreading isn't dual core, its kinda like adding >>another "Lane" to the processing pipeline of a single processor, so >>that when something stalls, other things can still happen. >> Hypertransport, on the other hand is AMD's method of connecting SMP >>CPUs to eachother, memory, and devices on the motherboard. >> >>Sorry about the Hypertransport/Hyperthreading thing, but there seems >>to be a great deal of confusion about what each are, and what's >>good/bad about them, and they relate to the AMD/Intel decsion you're >>making pretty explicitly. >> >>Personally, I say go with the Opteron. Worst case, performance and >>reliability are the same, and you're supporting the underdog. Best >>case, it blows your socks off, and in a year, you can go dual core. >>Either way, you can't loose. >> >>---- Harrison Grundy >> > > > D'oh. One other thing. In the benchmarks I've seen, Opterons "Play > Nicer" with SMP because of the Hypertransport setup in some > applications. (IE, they don't fight over memory the way Xeons do). > Look for a motherboard that uses a "4+4" or "4+2" memory configuration > to take full advantage of this. (Differnt memory for each processor, > kinda) With FreeBSD, it's a bit of a toss-up. There is no strong affinity set or enforced between process memory and where the process is running. Having some notion of affinity (i.e. NUMA support) would be a good thing. Oh, and the 4+2 configurations are typically pretty poor, regardless. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 06:14:35 2005 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 073E516A4CE for ; Sat, 5 Feb 2005 06:14:35 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4E4643D31 for ; Sat, 5 Feb 2005 06:14:34 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 7D7B72A7EA for ; Fri, 4 Feb 2005 22:14:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id C2532E2B3 for ; Fri, 4 Feb 2005 22:14:33 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id j156EXqo073425; Fri, 4 Feb 2005 22:14:33 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id j156EWtg073424; Fri, 4 Feb 2005 22:14:32 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org, Nick Lozinsky Date: Fri, 4 Feb 2005 22:14:32 -0800 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502042214.32845.peter@wemm.org> Subject: Re: amd64 and wine 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, 05 Feb 2005 06:14:35 -0000 On Friday 04 February 2005 03:51 am, Nick Lozinsky wrote: > Hello: > > Running FreeBSD5.3-STABLE on AMD64 3200+; I've attempted to `make > install' wine from the ports tree, and surprisingle enough, it is > only able to compile on I386 architectures. I looked through the > Makefile, and saw the i386 support, only. Does wine have any support > on amd64, or is it possible to compile on amd64 for backward 32-bit > compatibility? > > Thanks in advance. I'm sorry to say that no, it isn't likely in the short term. Wine depends on the USER_LDT features to use a custom x86 segmentation table within a user process. The amd64 kernel does not have this. I have been thinking about how to implement this in a lower-cost way than what currently happens on the i386 kernel though. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 11:51:12 2005 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 8BCEB16A4CE for ; Sat, 5 Feb 2005 11:51:12 +0000 (GMT) Received: from mout2.freenet.de (mout2.freenet.de [194.97.50.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161A943D31 for ; Sat, 5 Feb 2005 11:51:12 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [194.97.55.147] (helo=mx4.freenet.de) by mout2.freenet.de with esmtpa (Exim 4.47) id 1CxOT1-0005Ru-24; Sat, 05 Feb 2005 12:51:11 +0100 Received: from pd9eac040.dip0.t-ipconnect.de ([217.234.192.64] helo=amd64.bsdnet.)4.43 #13) id 1CxOT0-0004PM-QA; Sat, 05 Feb 2005 12:51:11 +0100 Date: Sat, 5 Feb 2005 12:49:56 +0100 From: Manuel =?ISO-8859-1?Q?St=FChn?= To: FreeBSDquestions Message-ID: <20050205124956.4005d7d4@amd64.bsdnet.> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; amd64-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Performance issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 11:51:12 -0000 Hi I'm a bit confused about the performance difference between FreeBSD-amd64 and FreeBSD-i386. On my machine runs FreeBSD-STABLE-amd64 and FreeBSD-STABLE-i386 built from the same source (4.Feb 2005). Kernel-config and installed ports of both installations are (nearly) identical. No Ports were installed before upgrading to STABLE. Now, on both installations xorg-6.8.1, XFCE4.2, firefox-1.0 and gvim-gtk2 are installed. When my box is running in amd64-Mode, the letters of a document edited in gvim-gtk2 need about a second to appear again after a alt-tab-switch to gvim. The system-load grows up to 20-60% until the whole document is visible again. The same effect occurs, if i alt-tab to another gtk-2 based editor e.g. leafpad, but not, when using a gtk1-based editor (gvim-gtk1 for example). On the i386-installaition i can't see this phenomenon. The ports/system are built with the same CFLAGS (-O -pipe) and identical configurations in /etc/make.conf. Any hints? Manuel -- Aus Murphy's Gesetze: Bei einem senkrechten Balkendiagramm werden die Bezeichnungen immer zu lang sein, um sie komplett unter die Balken zu bekommen. From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 22:18:11 2005 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 2F3F716A4CE for ; Sat, 5 Feb 2005 22:18:11 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4FFF43D41 for ; Sat, 5 Feb 2005 22:18:10 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j15MI9mx010200; Sat, 5 Feb 2005 14:18:09 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j15MI9rM010199; Sat, 5 Feb 2005 14:18:09 -0800 (PST) (envelope-from obrien) Date: Sat, 5 Feb 2005 14:18:08 -0800 From: "David O'Brien" To: Astrodog , freebsd-amd64@freebsd.org Message-ID: <20050205221808.GA9350@dragon.nuxi.com> References: <000001c50a3c$50f2eba0$6800000a@r3140ca> <20050204103708.21608.qmail@web26801.mail.ukl.yahoo.com> <2fd864e05020419382a5e21b3@mail.gmail.com> <42044AAF.1010002@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42044AAF.1010002@freebsd.org> 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 Subject: Re: Intel EMT64 Xeon vs AMD Opteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 22:18:11 -0000 [ Please don't cross post! ] On Fri, Feb 04, 2005 at 09:25:19PM -0700, Scott Long wrote: > Astrodog wrote: > >From what I understand, EM64T is essentally an extention to x86, so > >it will understand the AMD64 instructions, much the same way an > >Athlon64 does. Opteron, once again, from what I've read on the topic > >is "Actual" 64-bit, not an emulated version. .. > Both the AMD and Intel offering are just extensions to the ia32 design. > Opteron is no more 'true' 64-bit than Nacona is. Just as the i386 was just extensions to the 80286 design, which was just extensions to the original 8086 design. ;-) And just as the UltraSparc (Sparc v9) is just extensions to the 32-bit Sparc v8. Astrodog, I'm courous, what is the definition of a True 64-bit CPU? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 22:27:56 2005 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 96FA316A4CE for ; Sat, 5 Feb 2005 22:27:56 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CDDA43D3F for ; Sat, 5 Feb 2005 22:27:56 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j15MRsQ7010467; Sat, 5 Feb 2005 14:27:54 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j15MRsiM010466; Sat, 5 Feb 2005 14:27:54 -0800 (PST) (envelope-from obrien) Date: Sat, 5 Feb 2005 14:27:54 -0800 From: "David O'Brien" To: Sean Message-ID: <20050205222754.GD9350@dragon.nuxi.com> References: <41FC90D4.9050306@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FC90D4.9050306@comcast.net> 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: Support for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 22:27:56 -0000 On Sun, Jan 30, 2005 at 02:46:28AM -0500, Sean wrote: > So many ports, and some Linux games I bought long ago, I try to install > pop up with something about only supporting i386. > > Is there some way to make a port, perhaps pass some sort of switch, or > compile something else into the kernel to get i386 support? Post the exact error messages and give details on how you are trying to install the applications. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 22:29:44 2005 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 27D0D16A4CE for ; Sat, 5 Feb 2005 22:29:44 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50D143D4C for ; Sat, 5 Feb 2005 22:29:43 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j15MTgxw010506; Sat, 5 Feb 2005 14:29:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j15MTepB010505; Sat, 5 Feb 2005 14:29:40 -0800 (PST) (envelope-from obrien) Date: Sat, 5 Feb 2005 14:29:39 -0800 From: "David O'Brien" To: mikel king Message-ID: <20050205222939.GE9350@dragon.nuxi.com> References: <41FB0C2B.108@ocsny.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FB0C2B.108@ocsny.com> 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: hardware spec question... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 22:29:44 -0000 On Fri, Jan 28, 2005 at 11:08:11PM -0500, mikel king wrote: > I am trying to ramp up on the amd64 technology. I would like to assemble > a cheap dual cpu worstation/low end server. I found one fairly > affordable board and am curious if anyone elase has had experience with > this product? > http://www.superwarehouse.com/p.cfm?p=332508&CMP=KA18442 This product is fine. You won't get the performance you could from a 4+4 (vs. 4+0) DIMM configuration. But you've already made the $/performance decision. This board will give higher performance than a 1P Opteron server board such as the Tyan K8S Tomcat (s2850). -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 22:30:21 2005 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 7C17B16A4CE for ; Sat, 5 Feb 2005 22:30:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F70D43D1F for ; Sat, 5 Feb 2005 22:30:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j15MULTH038903 for ; Sat, 5 Feb 2005 22:30:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j15MUK64038890; Sat, 5 Feb 2005 22:30:20 GMT (envelope-from gnats) Date: Sat, 5 Feb 2005 22:30:20 GMT Message-Id: <200502052230.j15MUK64038890@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "David O'Brien" Subject: Re: amd64/76973: BTX Halted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 22:30:21 -0000 The following reply was made to PR amd64/76973; it has been noted by GNATS. From: "David O'Brien" To: Bart Veurink Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/76973: BTX Halted Date: Sat, 5 Feb 2005 14:21:43 -0800 On Tue, Feb 01, 2005 at 05:44:51PM +0000, Bart Veurink wrote: > I got a problem with installing FreeBSD from CD (Mini and Normal). This is my first time to try a BSD. It gives the Error in the bootloader, BTX Halted. > By The Way why are there not ISO's for FreeBSD 6.0 > > First some info and a Error: > int=0000000d err=00000000 efl=00010086 eip=00027788 > eax=80000011 ebx=00037000 ecx=c0000080 edx=00000000 > esi=00036000 edi=00035000 ebp=000948a4 esp=0009e870 > cs:eip:0f 22 c0 b8 00 20 04 00-8b 35 98 7f 04 00 8b 3d > 9c 7f 04 00 0f 01 10 ea-a6 77 02 00 08 00 89 f0 > ss:esp:69 95 00 00 00 40 c9 00-00 50 c9 00 10 10 04 00 > 00 00 00 00 00 00 04 00-00 00 00 00 58 b0 06 00 > BTX Halted This should not have happened. Unless something has changed lately, the FreeBSD loader and BTX are the same for both the 'i386' and 'amd64' platforms. Can you try installing from an 'i386' ISO? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 5 22:34:45 2005 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 961B116A4CE for ; Sat, 5 Feb 2005 22:34:45 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41BE343D3F for ; Sat, 5 Feb 2005 22:34:45 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j15MYiKR010708; Sat, 5 Feb 2005 14:34:44 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j15MYi19010707; Sat, 5 Feb 2005 14:34:44 -0800 (PST) (envelope-from obrien) Date: Sat, 5 Feb 2005 14:34:44 -0800 From: "David O'Brien" To: "Nick M. Lozinsky" Message-ID: <20050205223444.GG9350@dragon.nuxi.com> References: <76ff51010502022341529322fc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76ff51010502022341529322fc@mail.gmail.com> 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: amd64 and wine support in FreeBSD 5.3-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Feb 2005 22:34:45 -0000 On Thu, Feb 03, 2005 at 01:41:36AM -0600, Nick M. Lozinsky wrote: > Hi, > > On my 64bit AMD laptop, using FreeBSD 5.3 Stable, I an unable to make > install wine from ports. Looking through the Makefile, I find that it > only support i386 architectures. Ho can I make it even with i386 > support under amd64, or, is it even possible to make it on amd64? Wine isn't supported on amd64 (neither on Linux/AMD64 also). The AMD64 ISA does not support the functionality Wine uses. -- -- David (obrien@FreeBSD.org)