From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 02:49:57 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 A913816A4CE; Sun, 13 Feb 2005 02:49:57 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3049643D2F; Sun, 13 Feb 2005 02:49:57 +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 j1D2nu1p080900; Sat, 12 Feb 2005 21:49:56 -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 j1D2nuwi074868; Sat, 12 Feb 2005 21:49:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9A0207306E; Sat, 12 Feb 2005 21:49:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050213024956.9A0207306E@freebsd-current.sentex.ca> Date: Sat, 12 Feb 2005 21:49:56 -0500 (EST) X-Virus-Scanned: ClamAV 0.82/705/Fri Feb 11 11:51:32 2005 on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner2 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, 13 Feb 2005 02:49:57 -0000 TB --- 2005-02-13 02:16:35 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-13 02:16:35 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-02-13 02:16:35 - checking out the source tree TB --- 2005-02-13 02:16:35 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-02-13 02:16:35 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-02-13 02:22:15 - building world (CFLAGS=-O2 -pipe) TB --- 2005-02-13 02:22:15 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-13 02:22:15 - /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 [...] ===> lib/libgpib (all) cc -O2 -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c: In function `ibsad': /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c:475: error: `v' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c:475: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c:475: error: for each function it appears in.) /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c: At top level: /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib/ibfoo.c:469: warning: unused parameter 'sad' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libgpib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-02-13 02:49:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-13 02:49:56 - ERROR: failed to build world TB --- 2005-02-13 02:49:56 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 18:17:00 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 1A0D516A4CE; Sun, 13 Feb 2005 18:17:00 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C14243D39; Sun, 13 Feb 2005 18:16:59 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j1DIGxGN045480; Sun, 13 Feb 2005 13:16:59 -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 j1DIGxV9078841; Sun, 13 Feb 2005 13:16:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0B2747306E; Sun, 13 Feb 2005 13:16:58 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050213181658.0B2747306E@freebsd-current.sentex.ca> Date: Sun, 13 Feb 2005 13:16:58 -0500 (EST) X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner3 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, 13 Feb 2005 18:17:00 -0000 TB --- 2005-02-13 16:37:05 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-13 16:37:05 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-02-13 16:37:05 - checking out the source tree TB --- 2005-02-13 16:37:05 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-02-13 16:37:05 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-02-13 16:42:57 - building world (CFLAGS=-O2 -pipe) TB --- 2005-02-13 16:42:57 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-13 16:42:57 - /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-13 17:50:14 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-02-13 17:50:14 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-13 17:50:14 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Feb 13 17:50:14 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 Sun Feb 13 18:04:54 UTC 2005 TB --- 2005-02-13 18:04:54 - generating LINT kernel config TB --- 2005-02-13 18:04:54 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-02-13 18:04:54 - /usr/bin/make -B LINT TB --- 2005-02-13 18:04:54 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-02-13 18:04:54 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-13 18:04:54 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Feb 13 18:04:54 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 [...] touch hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/home/tinderbox/CURRENT/amd64/amd64/obj/tinderbox/CURRENT/amd64/amd64/src/make.i386/make sh /tinderbox/CURRENT/amd64/amd64/src/sys/conf/newvers.sh LINT 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 -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-builtin -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 vers.c linking kernel upd7210.o(.text+0x7d7): In function `upd7210attach': : undefined reference to `gpib_ib_cdevsw' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-02-13 18:16:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-13 18:16:58 - ERROR: failed to build lint kernel TB --- 2005-02-13 18:16:58 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 18:29:24 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 9317516A4CE for ; Sun, 13 Feb 2005 18:29:24 +0000 (GMT) Received: from mta.webmatic.de (mta.webmatic.de [212.78.99.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19F5A43D1D for ; Sun, 13 Feb 2005 18:29:23 +0000 (GMT) (envelope-from freebsd-amd64@chef-ingenieur.de) Received: (qmail 14702 invoked by uid 1003); 13 Feb 2005 18:29:19 -0000 Received: from freebsd-amd64@chef-ingenieur.de by mta.webmatic.de by uid 89 with qmail-scanner-1.22 (spamassassin: 2.63. Clear:RC:1(217.186.17.95):. Processed in 0.046523 secs); 13 Feb 2005 18:29:19 -0000 Received: from unknown (HELO ?192.168.1.100?) (freebsd-stable@chef-ingenieur.de@217.186.17.95) by mta.webmatic.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 13 Feb 2005 18:29:18 -0000 Message-ID: <420F9CA1.4040207@chef-ingenieur.de> Date: Sun, 13 Feb 2005 19:29:53 +0100 From: Thomas Krause -CI- User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 18:29:24 -0000 Hello, why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set when compiling an amd64 kernel? I think, the CPU supports all thease features. Features=0x78bfbff I have no CPUTYPE specified in /etc/make.conf, as I could not find a matching option in /usr/src/share/examples/etc/make.conf. Kind regards, Thomas From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 18:41:00 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 A84FD16A4CE for ; Sun, 13 Feb 2005 18:41:00 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6951B43D1F for ; Sun, 13 Feb 2005 18:41:00 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j1DIep4V041594; Sun, 13 Feb 2005 10:40:51 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j1DIepm2041593; Sun, 13 Feb 2005 10:40:51 -0800 (PST) (envelope-from sgk) Date: Sun, 13 Feb 2005 10:40:51 -0800 From: Steve Kargl To: Thomas Krause -CI- Message-ID: <20050213184051.GA41566@troutmask.apl.washington.edu> References: <420F9CA1.4040207@chef-ingenieur.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <420F9CA1.4040207@chef-ingenieur.de> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 18:41:00 -0000 On Sun, Feb 13, 2005 at 07:29:53PM +0100, Thomas Krause -CI- wrote: > Hello, > why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set > when compiling an amd64 kernel? I think, the CPU supports all thease > features. > AFAIK, floating point is not permitted in the kernel. Why would you need to use sse, sse2, mmx, or 3dnow? -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 18:56: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 CFBC616A4CE for ; Sun, 13 Feb 2005 18:56:40 +0000 (GMT) Received: from mta.webmatic.de (mta.webmatic.de [212.78.99.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2FA543D45 for ; Sun, 13 Feb 2005 18:56:39 +0000 (GMT) (envelope-from freebsd-amd64@chef-ingenieur.de) Received: (qmail 1044 invoked by uid 1003); 13 Feb 2005 18:56:35 -0000 Received: from freebsd-amd64@chef-ingenieur.de by mta.webmatic.de by uid 89 with qmail-scanner-1.22 (spamassassin: 2.63. Clear:RC:1(217.186.17.95):. Processed in 0.083923 secs); 13 Feb 2005 18:56:35 -0000 Received: from unknown (HELO ?192.168.1.100?) (freebsd-stable@chef-ingenieur.de@217.186.17.95) by mta.webmatic.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 13 Feb 2005 18:56:35 -0000 Message-ID: <420FA306.8010102@chef-ingenieur.de> Date: Sun, 13 Feb 2005 19:57:10 +0100 From: Thomas Krause -CI- User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Steve Kargl , freebsd-amd64@freebsd.org References: <420F9CA1.4040207@chef-ingenieur.de> <20050213184051.GA41566@troutmask.apl.washington.edu> In-Reply-To: <20050213184051.GA41566@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 18:56:41 -0000 Steve Kargl schrieb: > On Sun, Feb 13, 2005 at 07:29:53PM +0100, Thomas Krause -CI- wrote: > >>Hello, >>why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set >>when compiling an amd64 kernel? I think, the CPU supports all thease >>features. >> > > > AFAIK, floating point is not permitted in the kernel. Why would > you need to use sse, sse2, mmx, or 3dnow? > I don't know, if thease features are useful in the kernel. But when compiling a x86 kernel, they are not disabled. As I remember, you can compile libpng using mmx features. (I'm unsure, if you need a mmx-optimized kernel for that.) Regards, Thomas. From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 19:25:34 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 06E7616A4CE for ; Sun, 13 Feb 2005 19:25:34 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id C013043D5A for ; Sun, 13 Feb 2005 19:25:33 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j1DJPOvi041877; Sun, 13 Feb 2005 11:25:24 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j1DJPOig041876; Sun, 13 Feb 2005 11:25:24 -0800 (PST) (envelope-from sgk) Date: Sun, 13 Feb 2005 11:25:24 -0800 From: Steve Kargl To: Thomas Krause -CI- Message-ID: <20050213192524.GA41820@troutmask.apl.washington.edu> References: <420F9CA1.4040207@chef-ingenieur.de> <20050213184051.GA41566@troutmask.apl.washington.edu> <420FA306.8010102@chef-ingenieur.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <420FA306.8010102@chef-ingenieur.de> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 19:25:34 -0000 On Sun, Feb 13, 2005 at 07:57:10PM +0100, Thomas Krause -CI- wrote: > Steve Kargl schrieb: > >On Sun, Feb 13, 2005 at 07:29:53PM +0100, Thomas Krause -CI- wrote: > > > >>Hello, > >>why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set > >>when compiling an amd64 kernel? I think, the CPU supports all thease > >>features. > >> > > > > > >AFAIK, floating point is not permitted in the kernel. Why would > >you need to use sse, sse2, mmx, or 3dnow? > > > I don't know, if thease features are useful in the kernel. But when > compiling a x86 kernel, they are not disabled. I suggest you read the gcc.info file, in particular see the description of -mfpmathi option. It seems that if you are building i386 (or equivalent 32bit processor), then these options are automatically disabled by the compiler. If you are building for amd64 (or Intel's copycat), then these options are automatically enabled by the compiler. These options are used to compile floating point code. There is no floating point code in the kernel, so the options are useless and should be turned off. > As I remember, you can compile libpng using mmx features. (I'm unsure, > if you need a mmx-optimized kernel for that.) libpng uses floating point code, so it can take advantage of mmx. The kernel's feature list for my CPU, Features=0x183f9ff shows that the CPU supports MMX, and thus libpng compile with mmx will work just fine. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 19:33: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 77A5F16A4CE for ; Sun, 13 Feb 2005 19:33:45 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 225A943D53 for ; Sun, 13 Feb 2005 19:33:45 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IBV00KSB7O8ON@VL-MO-MR010.ip.videotron.ca> for freebsd-amd64@freebsd.org; Sun, 13 Feb 2005 14:33:44 -0500 (EST) Date: Sun, 13 Feb 2005 14:33:42 -0500 From: Nicolas Blais To: freebsd-amd64@freebsd.org Message-id: <200502131433.43567.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 Subject: Can't compile jdk15 on amd64 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: Sun, 13 Feb 2005 19:33:45 -0000 Hi, So far I've been running linux-sun-jdk-1.4.2.06_1 successfully on my box and works great in konqueror but not at all in firefox. So I tried to compile jdk15 and it gives me the following error: execv(): Bad address Error trying to exec /usr/local/linux-sun-jdk1.4.2/bin/javac. Check if file exists and permissions are set correctly. gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. I googled around and found http://lists.freebsd.org/pipermail/freebsd-java/2005-February/003446.html and several replies but no real fix for me. Apparently I'm not the only one in this situation. >From what I understand, the command "javac" that is executed before the fail point is 25814 characters long and on my 5.3-STABLE machine I max out at 16384 characters (according to many configure scripts). I tried copy pasting the javac command but I max out of the buffer near the middle of the command whether I use Konsole, Xterm or good-old ttyv + csh. Jdk15 compiles fine on my -CURRENT amd64 machine but I would like to have it work on my stable one as well. Any solutions? Thanks, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 23:30:10 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 F0ADA16A50D for ; Sun, 13 Feb 2005 23:30:09 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A45E743D3F for ; Sun, 13 Feb 2005 23:30:09 +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 j1DNU9kx080774 for ; Sun, 13 Feb 2005 23:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j1DNU9Bp080770; Sun, 13 Feb 2005 23:30:09 GMT (envelope-from gnats) Resent-Date: Sun, 13 Feb 2005 23:30:09 GMT Resent-Message-Id: <200502132330.j1DNU9Bp080770@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, Trushkin "Dreug" Eugene Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3137516A4CE for ; Sun, 13 Feb 2005 23:25:09 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C34043D2F for ; Sun, 13 Feb 2005 23:25:09 +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 j1DNP8h1002334 for ; Sun, 13 Feb 2005 23:25:08 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j1DNP8LV002333; Sun, 13 Feb 2005 23:25:08 GMT (envelope-from nobody) Message-Id: <200502132325.j1DNP8LV002333@www.freebsd.org> Date: Sun, 13 Feb 2005 23:25:08 GMT From: Trushkin "Dreug" Eugene To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/77470: Using of cyrillic filenames conversion leads to english filenames gabmbling X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 23:30:10 -0000 >Number: 77470 >Category: amd64 >Synopsis: Using of cyrillic filenames conversion leads to english filenames gabmbling >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 13 23:30:09 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Trushkin "Dreug" Eugene >Release: FreeBSD5.3-RELEASE amd64 >Organization: BMSTU >Environment: FreeBSD dreug.vxoda.net 5.3-RELEASE FreeBSD 5.3-RELEASE #4: Sun Feb 13 23:39:09 MSK 2005 root@dreug.vxoda.net:/usr/src/sys/amd64/compile/Dreug64 amd64 >Description: Hello. I use "mount_msdosfs -D cp1251 -L ru_RU.KOI8-R /dev/ad1s5 /mnt" for mounting vfat filesystem with codepage CP1251 (in system with ru_RU.KOI8-R locale). All filenames in /mnt are gambled. English filenames too! For example dot symbol become asterisk. I have the same trouble with generic kernel or when i use "-W koi2dos" instead "-D cp1251". I notice english filenames gambling only when i use -L or -W or -D in mount_msdosfs or -C in mount_cd9660. It seems to me, that this is observed only with amd64 kernel. Everything is OK with FreeBSD 5.2.1 i386 on the same hardware with identical settings (tty: cons25r, login class: russian, LANG=ru_RU.KOI8-R, MM_CHARSET=KOI8-R) and identical commands. Excuse me, my english is poor. >How-To-Repeat: In FreeBSD5.3-RELEASE amd64 mount vfat partition with codepage cp1251 using command like: mount_msdosfs -D cp1251 -L ru_RU.KOI8-R /dev/ad1s5 /mnt >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 13 23:54: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 1F50816A4CE for ; Sun, 13 Feb 2005 23:54:04 +0000 (GMT) Received: from smtp6.wanadoo.fr (smtp6.wanadoo.fr [193.252.22.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8CF43D45 for ; Sun, 13 Feb 2005 23:54:03 +0000 (GMT) (envelope-from stephan.heiligenstein@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0603.wanadoo.fr (SMTP Server) with ESMTP id 9ABE01C00226 for ; Mon, 14 Feb 2005 00:54:02 +0100 (CET) Received: from 192.168.0.6 (AStrasbourg-251-1-36-154.w82-126.abo.wanadoo.fr [82.126.153.154]) by mwinf0603.wanadoo.fr (SMTP Server) with ESMTP id 5BCE81C00223 for ; Mon, 14 Feb 2005 00:54:02 +0100 (CET) X-ME-UUID: 20050213235402376.5BCE81C00223@mwinf0603.wanadoo.fr From: steph To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Date: Mon, 14 Feb 2005 00:53:49 +0100 Message-Id: <1108338829.6015.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 8bit Subject: telecharger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 23:54:04 -0000 je r"echerche un site ou ftp me permettant de telecharger une version de freesbie 1.1 pour mon AMD64. Merci de me renseigner. Stéphan Heiligenstein From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 00:30:08 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 55F9216A4CE for ; Mon, 14 Feb 2005 00:30:08 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E0CD43D41 for ; Mon, 14 Feb 2005 00:30:08 +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 j1E0U787060271; Sun, 13 Feb 2005 16:30:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1E0U7Cp060270; Sun, 13 Feb 2005 16:30:07 -0800 (PST) (envelope-from obrien) Date: Sun, 13 Feb 2005 16:30:07 -0800 From: "David O'Brien" To: Nicolas Blais Message-ID: <20050214003007.GE68054@dragon.nuxi.com> References: <200502131433.43567.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502131433.43567.nb_root@videotron.ca> 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: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 00:30:08 -0000 On Sun, Feb 13, 2005 at 02:33:42PM -0500, Nicolas Blais wrote: > So far I've been running linux-sun-jdk-1.4.2.06_1 successfully on my box and > works great in konqueror but not at all in firefox. So I tried to compile > jdk15 and it gives me the following error: ... > I googled around and found > http://lists.freebsd.org/pipermail/freebsd-java/2005-February/003446.html and > several replies but no real fix for me. Apparently I'm not the only one in > this situation. > > From what I understand, the command "javac" that is executed before the fail > point is 25814 characters long and on my 5.3-STABLE machine I max out at > 16384 characters (according to many configure scripts). I'm willing to MFC what ever is needed to make this work, but I really can't parse this. You can build jdk15 on FreeBSD/AMD64 6-CURRENT, right? You cannot build jdk15 on FreeBSD/AMD64 6-CURRENT, right? You feel this is due to a difference in the maxium command line size (in characters), right? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 00:35: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 93AC916A4CE for ; Mon, 14 Feb 2005 00:35:58 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DE7443D1F for ; Mon, 14 Feb 2005 00:35:58 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IBV009PNLNXUH@VL-MO-MR010.ip.videotron.ca> for freebsd-amd64@freebsd.org; Sun, 13 Feb 2005 19:35:57 -0500 (EST) Date: Sun, 13 Feb 2005 19:35:56 -0500 From: Nicolas Blais In-reply-to: <20050214003007.GE68054@dragon.nuxi.com> To: freebsd-amd64@freebsd.org Message-id: <200502131935.57231.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> Subject: Re: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 00:35:58 -0000 On February 13, 2005 19:30, David O'Brien wrote: > On Sun, Feb 13, 2005 at 02:33:42PM -0500, Nicolas Blais wrote: > > So far I've been running linux-sun-jdk-1.4.2.06_1 successfully on my box > > and works great in konqueror but not at all in firefox. So I tried to > > compile jdk15 and it gives me the following error: > > ... > > > I googled around and found > > http://lists.freebsd.org/pipermail/freebsd-java/2005-February/003446.html > > and several replies but no real fix for me. Apparently I'm not the only > > one in this situation. > > > > From what I understand, the command "javac" that is executed before the > > fail point is 25814 characters long and on my 5.3-STABLE machine I max > > out at 16384 characters (according to many configure scripts). > > I'm willing to MFC what ever is needed to make this work, but I really > can't parse this. > > You can build jdk15 on FreeBSD/AMD64 6-CURRENT, right? > You cannot build jdk15 on FreeBSD/AMD64 6-CURRENT, right? > You feel this is due to a difference in the maxium command line size (in > characters), right? Actually, I can build jdk15 on a amd64 6-CURRENT machine and I can't on a amd64 5.3-STABLE. Yes I believe (as well as others) that it is due to a maximum command line size (as mentioned, the javac command during that point in the makefile is about 25000 char long and on my -STABLE I can only get 16384) Thanks for any help Nicolas From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 05:46: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 6629316A4CE for ; Mon, 14 Feb 2005 05:46:44 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4689643D55 for ; Mon, 14 Feb 2005 05:46:39 +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 j1E5krCx024704; Sun, 13 Feb 2005 22:46:54 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42103B29.8070901@samsco.org> Date: Sun, 13 Feb 2005 22:46:17 -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: Thomas Krause -CI- References: <420F9CA1.4040207@chef-ingenieur.de> In-Reply-To: <420F9CA1.4040207@chef-ingenieur.de> 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: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel 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, 14 Feb 2005 05:46:44 -0000 Thomas Krause -CI- wrote: > Hello, > why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set > when compiling an amd64 kernel? I think, the CPU supports all thease > features. > > Features=0x78bfbff > > > I have no CPUTYPE specified in /etc/make.conf, as I could not > find a matching option in /usr/src/share/examples/etc/make.conf. > > Kind regards, > Thomas Floating point, MMX, SSE, SSE2, and 3dnow, registers are not usable in the kernel. By not using these registers, we save the expense of saving and restoring them on every single syscall. Using them without saving them would run the risk of colliding with userland programs that do use them. Whether or not the kernel is compiled with instructions that use these registers has absolutely no bearing on whether userland code can use them. It's purely about trading one optimization (using optimized opcodes in the kernel) for another (not having to save and restore dozens of registers to the stack on each syscall). It might be interesting to experiment with allowing a certain class of instructions in the kernel and saving and restoring the associated registers, and seeing if GCC will actually generate code that is better and overcomes the save/restore expense. Any takers? Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 06:03:55 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 C1F4F16A4CE for ; Mon, 14 Feb 2005 06:03:55 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FFB943D2D for ; Mon, 14 Feb 2005 06:03:55 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.31.188]) by lakermmtao11.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050214060354.TULY3313.lakermmtao11.cox.net@dolphin.local.net>; Mon, 14 Feb 2005 01:03:54 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j1E63qBR008345; Mon, 14 Feb 2005 00:03:52 -0600 (CST) (envelope-from conrads@cox.net) Date: Mon, 14 Feb 2005 00:03:46 -0600 From: "Conrad J. Sabatier" To: Nicolas Blais Message-ID: <20050214000346.37e36dfb@dolphin.local.net> In-Reply-To: <200502131935.57231.nb_root@videotron.ca> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <200502131935.57231.nb_root@videotron.ca> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 06:03:55 -0000 On Sun, 13 Feb 2005 19:35:56 -0500, Nicolas Blais wrote: > On February 13, 2005 19:30, David O'Brien wrote: > > On Sun, Feb 13, 2005 at 02:33:42PM -0500, Nicolas Blais wrote: > > > So far I've been running linux-sun-jdk-1.4.2.06_1 successfully on > > > my box and works great in konqueror but not at all in firefox. So > > > I tried to compile jdk15 and it gives me the following error: > > > > ... > > > > > I googled around and found > > > http://lists.freebsd.org/pipermail/freebsd-java/2005-February/003446.html > > > and several replies but no real fix for me. Apparently I'm not the > > > only one in this situation. > > > > > > From what I understand, the command "javac" that is executed > > > before the fail point is 25814 characters long and on my > > > 5.3-STABLE machine I max out at 16384 characters (according to > > > many configure scripts). > > > > I'm willing to MFC what ever is needed to make this work, but I > > really can't parse this. > > > > You can build jdk15 on FreeBSD/AMD64 6-CURRENT, right? > > You cannot build jdk15 on FreeBSD/AMD64 6-CURRENT, right? > > You feel this is due to a difference in the maxium command line size > > (in characters), right? > > Actually, I can build jdk15 on a amd64 6-CURRENT machine and I can't > on a amd64 5.3-STABLE. Yes I believe (as well as others) that it is > due to a maximum command line size (as mentioned, the javac command > during that point in the makefile is about 25000 char long and on my > -STABLE I can only get 16384) The same problem occurs in CURRENT for amd64. Several people in the java list pointed out a workaround just to get the thing built, but this is not a proper solution. I offered Alexey use of my Athlon 64 box, but so far, he hasn't logged in here. Apparently, the problem doesn't affect Opteron boxes for some strange reason, only Athlon 64, so he wasn't able to reproduce the bogus behavior himself. Even after employing the workaround to get the build to complete, and installing the port, the bad news is that the resulting JVM is all but useless, gobbling up absolutely insane amounts of RAM (no less than one gigabyte to run even the most trivial app). Very disappointing, and very frustrating as well, to say the least. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 06:09:37 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 5466B16A4CE for ; Mon, 14 Feb 2005 06:09:37 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FF8943D1F for ; Mon, 14 Feb 2005 06:09:36 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.31.188]) by lakermmtao07.cox.net ESMTP <20050214060930.GTSC20686.lakermmtao07.cox.net@dolphin.local.net>; Mon, 14 Feb 2005 01:09:30 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j1E69Uqt008509; Mon, 14 Feb 2005 00:09:30 -0600 (CST) (envelope-from conrads@cox.net) Date: Mon, 14 Feb 2005 00:09:25 -0600 From: "Conrad J. Sabatier" To: Nicolas Blais Message-ID: <20050214000925.4b315f02@dolphin.local.net> In-Reply-To: <200502131433.43567.nb_root@videotron.ca> References: <200502131433.43567.nb_root@videotron.ca> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 06:09:37 -0000 On Sun, 13 Feb 2005 14:33:42 -0500, Nicolas Blais wrote: > Hi, > > So far I've been running linux-sun-jdk-1.4.2.06_1 successfully on my > box and works great in konqueror but not at all in firefox. Well, you're doing better than I am. :-) The linux jdk goes nuts when I try using it on my Athlon 64 box under CURRENT, launching multiple copies (no, not threads, I checked) of the same process. > So I tried to compile jdk15 and it gives me the following error: > > > execv(): Bad address > Error trying to exec /usr/local/linux-sun-jdk1.4.2/bin/javac. > Check if file exists and permissions are set correctly. > gmake[3]: *** [.compile.classlist] Error 1 > gmake[3]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] > Error 1 gmake[2]: Leaving directory > `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error > 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' > gmake: *** [j2se-build] Error 2 > *** Error code 2 > > Stop in /usr/ports/java/jdk15. > > I googled around and found > http://lists.freebsd.org/pipermail/freebsd-java/2005-February/003446.html > and several replies but no real fix for me. Apparently I'm not the > only one in this situation. > > >From what I understand, the command "javac" that is executed before > >the fail > point is 25814 characters long and on my 5.3-STABLE machine I max out > at 16384 characters (according to many configure scripts). I tried > copy pasting the javac command but I max out of the buffer near the > middle of the command whether I use Konsole, Xterm or good-old ttyv + > csh. > > Jdk15 compiles fine on my -CURRENT amd64 machine but I would like to > have it work on my stable one as well. > > Any solutions? No, none other than the workaround "solution" that appeared in the list recently, I'm sorry to say. I'm surprised you had no problems building the port under CURRENT as well. I encountered exactly the problem you're describing when I tried building under CURRENT on my Athlon 64 (amd64) box. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 08:46:05 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 C1BF916A4CE for ; Mon, 14 Feb 2005 08:46:05 +0000 (GMT) Received: from mallaury.noc.nerim.net (smtp-101-monday.noc.nerim.net [62.4.17.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69FE243D46 for ; Mon, 14 Feb 2005 08:46:05 +0000 (GMT) (envelope-from e-masson@kisoft-services.com) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoft.net1.nerim.net [62.212.107.51]) by mallaury.noc.nerim.net (Postfix) with ESMTP id 4AABE62DD0; Mon, 14 Feb 2005 09:46:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1])3CA6FC0E8; Mon, 14 Feb 2005 09:46:02 +0100 (CET) Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01574-05; Mon, 14 Feb 2005 09:45:48 +0100 (CET) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id 4BDBBC3F9; Mon, 14 Feb 2005 09:45:33 +0100 (CET) To: steph From: Eric Masson In-Reply-To: <1108338829.6015.1.camel@localhost.localdomain> (steph's message of "Mon, 14 Feb 2005 00:53:49 +0100") References: <1108338829.6015.1.camel@localhost.localdomain> X-Operating-System: FreeBSD 5.3-STABLE i386 Date: Mon, 14 Feb 2005 09:45:33 +0100 Message-ID: <86y8drjzrm.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at interne.kisoft-services.com cc: freebsd-amd64@FreeBSD.org Subject: Re: telecharger 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, 14 Feb 2005 08:46:05 -0000 >>>>> "steph" == steph writes: Hi, Sorry, answer in french. steph> je r"echerche un site ou ftp me permettant de telecharger une steph> version de freesbie 1.1 pour mon AMD64. Merci de me renseigner. steph> Stéphan Heiligenstein Tu es sur une liste dont la langue principale est l'anglais, merci de t'y conformer stp. Si tu vas sur le site du projet FreesBie tu trouveras les coordonnées des mainteneurs du projet, qui sont les plus à même de te répondre. Éric Masson -- >j'ai beau préparé une session express, elle ne se garde pas et qd je >fais ouvrir je reçois toutes les cauchonneries des usa comment faire >pour garder seulement les newgroupes qui m'interressent :-@ -+-TGV in : - Yankee go home -+- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 09:13:33 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 1DC9916A4CE for ; Mon, 14 Feb 2005 09:13:33 +0000 (GMT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8EB43D5D for ; Mon, 14 Feb 2005 09:13:32 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd11.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1D0cIM-0006y4-05; Mon, 14 Feb 2005 10:13:30 +0100 Received: from fw.reifenberger.com (GvdBCQZXQeQSP0q8APJ9Td+-WZN1PwM8Kh4ciP7VyVWDdhKbu3Cg4a@[62.158.175.56]) by fmrl11.sul.t-online.com with esmtp id 1D0cI8-1mk2AS0; Mon, 14 Feb 2005 10:13:16 +0100 Received: from localhost (mike@localhost)j1E9DFUV034207; Mon, 14 Feb 2005 10:13:15 +0100 (CET) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Mon, 14 Feb 2005 10:13:15 +0100 (CET) From: Michael Reifenberger To: "Conrad J. Sabatier" In-Reply-To: <20050214000346.37e36dfb@dolphin.local.net> Message-ID: <20050214100412.B34086@fw.reifenberger.com> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <20050214000346.37e36dfb@dolphin.local.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: GvdBCQZXQeQSP0q8APJ9Td+-WZN1PwM8Kh4ciP7VyVWDdhKbu3Cg4a@t-dialin.net X-TOI-MSGID: 340eef53-2f47-47a4-bdc7-46104ed52a36 cc: freebsd-amd64@freebsd.org Subject: Re: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 09:13:33 -0000 On Mon, 14 Feb 2005, Conrad J. Sabatier wrote: ... > Even after employing the workaround to get the build to complete, and > installing the port, the bad news is that the resulting JVM is all but > useless, gobbling up absolutely insane amounts of RAM (no less than one > gigabyte to run even the most trivial app). > Are you shure java uses(allocates) that amount of memory? Or are you just seeing the size of the whole process? I can use jboss4 just fine with the following patch: Index: os_bsd.cpp =================================================================== RCS file: /home/cvs/javacvs/jdk150/hotspot/src/os/bsd/vm/os_bsd.cpp,v retrieving revision 1.16 diff -u -r1.16 os_bsd.cpp --- os_bsd.cpp 16 Jan 2005 10:16:25 -0000 1.16 +++ os_bsd.cpp 9 Feb 2005 08:40:04 -0000 @@ -1898,7 +1898,7 @@ } while ((res == OS_ERR) && (errno == EINTR)); } else { assert(Thread::current()->is_Java_thread(), "must be java thread"); - INTERRUPTIBLE_NORESTART(nanosleep(&t, &t), res, os::Bsd::clear_interrupted); + INTERRUPTIBLE_NORESTART_VM(nanosleep(&t, &t), res, os::Bsd::clear_interrupted); } // INTERRUPTIBLE_NORESTART_VM returns res == OS_INTRPT for thread.Interrupt Top shows: last pid: 97136; load averages: 0.33, 0.90, 1.00 up 15+23:38:01 10:11:00 119 processes: 1 running, 118 sleeping CPU states: 2.7% user, 0.0% nice, 1.9% system, 1.6% interrupt, 93.8% idle Mem: 909M Active, 638M Inact, 135M Wired, 96M Cache, 210M Buf, 53M Free Swap: 4000M Total, 492K Used, 3999M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 712 root 96 0 98940K 39132K select 126:25 0.10% 0.10% Xorg 75685 root 96 0 94600K 29948K select 8:31 0.05% 0.05% kdeinit 21405 www 20 0 1823M 358M kserel 89:21 0.00% 0.00% java 75654 root 96 0 99M 26252K select 33:25 0.00% 0.00% kdeinit 96208 root 20 0 213M 106M kserel 23:55 0.00% 0.00% firefox-bin Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 09:48:48 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 9DFCA16A4CE for ; Mon, 14 Feb 2005 09:48:48 +0000 (GMT) Received: from bogotron.isy.liu.se (bogotron.isy.liu.se [130.236.48.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1386243D3F for ; Mon, 14 Feb 2005 09:48:48 +0000 (GMT) (envelope-from kentp@isy.liu.se) Received: from spamotron.isy.liu.se (spamotron-private [192.168.49.11]) by bogotron.isy.liu.se (Postfix) with ESMTP id 7B70C31A7; Mon, 14 Feb 2005 10:48:46 +0100 (MET) Received: from bogotron.isy.liu.se ([192.168.49.10]) (amavisd-new, port 10024) with ESMTP id 28443-04; Mon, 14 Feb 2005 10:48:45 +0100 (MET) Received: from kentspc.isy.liu.se (olin.isy.liu.se [130.236.49.34]) by bogotron.isy.liu.se (Postfix) with ESMTP id E43E331A6; Mon, 14 Feb 2005 10:48:44 +0100 (MET) Message-Id: <6.2.0.14.0.20050214093945.02df5698@garm.isy.liu.se> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 14 Feb 2005 10:48:14 +0100 To: Jung-uk Kim , freebsd-amd64@freebsd.org, Astrodog From: Kent Palmkvist In-Reply-To: <200502111236.53771.jkim@niksun.com> References: <6.2.0.14.0.20050211150014.02fdc380@mail.isy.liu.se> <2fd864e05021107356dcfe983@mail.gmail.com> <200502111236.53771.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new at isy.liu.se X-Spam-Checker-Version: SpamAssassin 2.63-isy (2004-01-11) on spamotron.isy.liu.se Subject: Re: Problems with a Acer Aspire 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, 14 Feb 2005 09:48:48 -0000 At 18:36 2005-02-11, Jung-uk Kim wrote: >On Friday 11 February 2005 10:35 am, Astrodog wrote: > > On Fri, 11 Feb 2005 15:43:02 +0100, Kent Palmkvist > wrote: ...snip... > > > by Kelly Black that solved a problem with the Compaq Presario > > > R3000z (http://blackk.union.edu/~black/freebsd/) but with same > > > disapointing results. > > > > > > Solution: > > > Disable the Legacy USB Support in the bios setup (at least ...snip... > > > > Tried the R3000Z line of patches? Might relate. > >If I am not mistaken completely, his problem is not related to my >patches. Acer Aspire 1522 WLMi has VIA chipsets and they have >different issues. In fact, I have Acer Ferrari 3400 and I had >experienced similar problems before. I am using 6-CURRENT on it now. > >BTW, 'turning off USB legacy support fixed problem' sounds like he has >C0 revision core (i. e., errata #93) without BIOS workaround. You >can see the CPU ID from dmesg: > >CPU: AMD Athlon(tm) 64 Processor 3000+ (2000.08-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 > >This is from my desktop. If the Id is 0xf48, you have C0 revision >core. FYI, Ferrari 3400 has Oakville core! > >CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 > >Jung-uk Kim I was under the impression that the Kelly Black ISO image would contain a release with the R3000Z patches applied. The ISO image from that site showed the same errors as the standard 5.3-RELEASE CD. I could be wrong of course. My CPU turns out to be: CPU: AMD Athlon(tm) 64 Processor 3000+ (1801.03-MHz K8-class CPU) Origin = "AutheticAMD" Id = 0xf4a Stepping = 10 And you are right, the laptop is built around a VIA chipset. Current problems with the machine includes non-working USB (not detecting new devices), non-working cardbus (complaining about Vcc request). I got the machine on tripple-boot (XP, FreeBSD 5.3 i386 and amd64). I am also thinking of installing 6-current (it is nice with big discs). /Kent Kent Palmkvist Electronics Systems Department of Electrical Engineering Linkoping University S-581 83 Linkoping Sweden Email: kentp@isy.liu.se Phone: +46 13 28 13 47 Fax: +46 13 13 92 82 www: http://www.es.isy.liu.se/staff/kentp From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 11:01:51 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 39D0616A4CF for ; Mon, 14 Feb 2005 11:01:51 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F206943D1F for ; Mon, 14 Feb 2005 11:01:50 +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 j1EB1o6M015110 for ; Mon, 14 Feb 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j1EB1oh6015104 for freebsd-amd64@freebsd.org; Mon, 14 Feb 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 14 Feb 2005 11:01:50 GMT Message-Id: <200502141101.j1EB1oh6015104@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, 14 Feb 2005 11:01:51 -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 o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A 17 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 o [2005/02/13] amd64/77470 amd64 Using of cyrillic filenames conversion le 9 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 12:01:10 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 89D9F16A4CF for ; Mon, 14 Feb 2005 12:01:10 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E12EC43D5C for ; Mon, 14 Feb 2005 12:01:09 +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 j1EC15d2020436; Mon, 14 Feb 2005 04:01:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1EC15QZ020435; Mon, 14 Feb 2005 04:01:05 -0800 (PST) (envelope-from obrien) Date: Mon, 14 Feb 2005 04:01:05 -0800 From: "David O'Brien" To: "Conrad J. Sabatier" Message-ID: <20050214120105.GA20325@dragon.nuxi.com> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <200502131935.57231.nb_root@videotron.ca> <20050214000346.37e36dfb@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050214000346.37e36dfb@dolphin.local.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: Can't compile jdk15 on amd64 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: Mon, 14 Feb 2005 12:01:10 -0000 On Mon, Feb 14, 2005 at 12:03:46AM -0600, Conrad J. Sabatier wrote: > I offered Alexey use of my Athlon 64 box, but so far, he hasn't logged > in here. Apparently, the problem doesn't affect Opteron boxes for some > strange reason, only Athlon 64, so he wasn't able to reproduce the bogus > behavior himself. There is *ZERO* way this could be the case. There is some other cause than Opteron vs. Athlon64 I promiss. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 16:52: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 C4DEA16A4CE for ; Mon, 14 Feb 2005 16:52:44 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C558C43D41 for ; Mon, 14 Feb 2005 16:52:41 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1EGqeQs085696; Mon, 14 Feb 2005 11:52:41 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Kent Palmkvist Date: Mon, 14 Feb 2005 11:52:31 -0500 User-Agent: KMail/1.6.2 References: <6.2.0.14.0.20050211150014.02fdc380@mail.isy.liu.se> <200502111236.53771.jkim@niksun.com> <6.2.0.14.0.20050214093945.02df5698@garm.isy.liu.se> In-Reply-To: <6.2.0.14.0.20050214093945.02df5698@garm.isy.liu.se> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502141152.33120.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: Problems with a Acer Aspire 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, 14 Feb 2005 16:52:45 -0000 On Monday 14 February 2005 04:48 am, Kent Palmkvist wrote: > At 18:36 2005-02-11, Jung-uk Kim wrote: > >On Friday 11 February 2005 10:35 am, Astrodog wrote: > > > On Fri, 11 Feb 2005 15:43:02 +0100, Kent Palmkvist > > > > wrote: > > ...snip... > > > > > by Kelly Black that solved a problem with the Compaq Presario > > > > R3000z (http://blackk.union.edu/~black/freebsd/) but with > > > > same disapointing results. > > > > > > > > Solution: > > > > Disable the Legacy USB Support in the bios setup (at least > > ...snip... > > > > Tried the R3000Z line of patches? Might relate. > > > >If I am not mistaken completely, his problem is not related to my > >patches. Acer Aspire 1522 WLMi has VIA chipsets and they have > >different issues. In fact, I have Acer Ferrari 3400 and I had > >experienced similar problems before. I am using 6-CURRENT on it > > now. > > > >BTW, 'turning off USB legacy support fixed problem' sounds like he > > has C0 revision core (i. e., errata #93) without BIOS workaround. > > You can see the CPU ID from dmesg: > > > >CPU: AMD Athlon(tm) 64 Processor 3000+ (2000.08-MHz K8-class CPU) > > Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 > > > >This is from my desktop. If the Id is 0xf48, you have C0 revision > >core. FYI, Ferrari 3400 has Oakville core! > > > >CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class > > CPU) Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 > > > >Jung-uk Kim > > I was under the impression that the Kelly Black ISO image would > contain a release with the R3000Z patches applied. The ISO image > from that site showed the same errors as the standard 5.3-RELEASE > CD. I could be wrong of course. Yes, that's exactly what I was saying. Your problem is not the same, i. e., his ISO image won't fix the problem. When I installed my Ferrari 3400 with 5.3 CD-ROM, I had to disable ACPI completely as you said. When I upgraded it to 6-CURRENT, everything worked perfectly fine. ACPI is on, atpic is off, and mixed mode is off. :-) > My CPU turns out to be: > CPU: AMD Athlon(tm) 64 Processor 3000+ (1801.03-MHz K8-class CPU) > Origin = "AutheticAMD" Id = 0xf4a Stepping = 10 Okay, yours is CG revision, which should have fixed errta #93. > And you are right, the laptop is built around a VIA chipset. > > Current problems with the machine includes non-working USB (not > detecting new devices), non-working cardbus (complaining about Vcc > request). I got the machine on tripple-boot (XP, FreeBSD 5.3 i386 > and amd64). I am also thinking of installing 6-current (it is nice > with big discs). 6-CURRENT may fix most of your problems, I believe. Jung-uk Kim > /Kent > > > > Kent Palmkvist > Electronics Systems > Department of Electrical Engineering > Linkoping University > S-581 83 Linkoping > Sweden > > Email: kentp@isy.liu.se > Phone: +46 13 28 13 47 > Fax: +46 13 13 92 82 > www: http://www.es.isy.liu.se/staff/kentp From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 19:49:46 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 D703816A4CE for ; Mon, 14 Feb 2005 19:49:46 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9468843D1F for ; Mon, 14 Feb 2005 19:49:46 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1D0mE8-0007C6-00; Mon, 14 Feb 2005 20:49:48 +0100 Date: Mon, 14 Feb 2005 20:49:48 +0100 To: steph Message-ID: <20050214194948.GP1145@poupinou.org> References: <1108338829.6015.1.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1108338829.6015.1.camel@localhost.localdomain> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot cc: freebsd-amd64@FreeBSD.org Subject: where is freesbie 1.1 for amd64 (was telecharger) 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, 14 Feb 2005 19:49:47 -0000 On Mon, Feb 14, 2005 at 12:53:49AM +0100, steph wrote: > je r"echerche un site ou ftp me permettant de telecharger une version de > freesbie 1.1 pour mon AMD64. > Merci de me renseigner. > Stéphan Heiligenstein The OP said that he wants to known where he can download freesbie 1.1 for AMD64. For the OP: I'm afraid its a english ML, not a french one. Bonne chance, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 14 22:21: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 BE86016A4CE for ; Mon, 14 Feb 2005 22:21:06 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EEDF43D31 for ; Mon, 14 Feb 2005 22:21:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14211 invoked from network); 14 Feb 2005 22:21:06 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 14 Feb 2005 22:21:05 -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 j1EMKxqN046899 for ; Mon, 14 Feb 2005 17:21:00 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: amd64@FreeBSD.org Date: Mon, 14 Feb 2005 17:22:10 -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: <200502141722.10259.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: [PATCH] Updated quirk-driven R3000Z patches 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, 14 Feb 2005 22:21:06 -0000 I've tweaked Jung-uk Kim's patches to be driven by a single ACPI quirk rather than multiple hints. I've included the patch below. If the quirk is not automatically detected on your laptop, you can manually set it from the loader via 'set debug.acpi.quirks=4'. If you have to manually set the quirk to get it to work, please let me know and include the FADT header from your acpidump in your reply, thanks. --- //depot/vendor/freebsd/src/sys/amd64/acpica/madt.c 2004/06/10 21:30:51 +++ //depot/user/jhb/acpipci/amd64/acpica/madt.c 2005/02/14 22:18:55 @@ -367,7 +367,7 @@ } /* First, we run through adding I/O APIC's. */ - if (madt->PCATCompat) + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) ioapic_enable_mixed_mode(); madt_walk_table(madt_parse_apics, NULL); @@ -596,8 +596,14 @@ enum intr_polarity pol; char buf[64]; + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && + intr->Interrupt == 2) { + if (bootverbose) + printf("MADT: Skipping timer override\n"); + return; + } if (bootverbose) - printf("MADT: intr override: source %u, irq %u\n", + printf("MADT: Interrupt override: source %u, irq %u\n", intr->Source, intr->Interrupt); KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); if (madt_find_interrupt(intr->Interrupt, &new_ioapic, --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_quirks 2004/10/08 18:00:57 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_quirks 2005/02/14 21:45:45 @@ -101,6 +101,13 @@ oem_rev: FADT <= 0x06040000 quirks: ACPI_Q_BROKEN +# Compaq R3000Z +name: Compaq_R3000Z +oem: FADT "NVIDIA" "CK8 " +oem_rev: FADT = 0x6040000 +creator: FADT "PTL_" +quirks: ACPI_Q_MADT_IRQ0 + # Compaq Thunder 05/18/99 # XXX Note creator rev should be "=", I think name: Compaq_Thunder --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_resource.c 2005/01/18 20:25:37 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_resource.c 2005/01/18 23:04:51 @@ -77,6 +77,12 @@ req->counter++; break; } + if (irq != rman_get_start(req->res) && irq == 0) { + if (bootverbose) + printf("IRQ is %u, resource is %lu\n", irq, + rman_get_start(req->res)); + return (AE_CTRL_TERMINATE); + } req->found = 1; KASSERT(irq == rman_get_start(req->res), ("IRQ resources do not match")); --- //depot/vendor/freebsd/src/sys/dev/acpica/acpivar.h 2004/12/13 23:35:37 +++ //depot/user/jhb/acpipci/dev/acpica/acpivar.h 2005/02/11 19:51:51 @@ -160,11 +160,20 @@ #define ACPI_INTR_APIC 1 #define ACPI_INTR_SAPIC 2 -/* Quirk flags. */ +/* + * Quirk flags. + * + * ACPI_Q_BROKEN: Disables all ACPI support. + * ACPI_Q_TIMER: Disables support for the ACPI timer. + * ACPI_Q_MADT_IRQ0: Specifies that ISA IRQ 0 is wired up to pin 0 of the + * first APIC and that the MADT should force that by ignoring the PC-AT + * compatible flag and ignoring overrides that redirect IRQ 0 to pin 2. + */ extern int acpi_quirks; #define ACPI_Q_OK 0 -#define ACPI_Q_BROKEN (1 << 0) /* Disable ACPI completely. */ -#define ACPI_Q_TIMER (1 << 1) /* Disable ACPI timer. */ +#define ACPI_Q_BROKEN (1 << 0) +#define ACPI_Q_TIMER (1 << 1) +#define ACPI_Q_MADT_IRQ0 (1 << 2) /* * Note that the low ivar values are reserved to provide --- //depot/vendor/freebsd/src/sys/i386/acpica/madt.c 2004/06/10 20:05:33 +++ //depot/user/jhb/acpipci/i386/acpica/madt.c 2005/02/14 22:18:55 @@ -367,7 +367,7 @@ } /* First, we run through adding I/O APIC's. */ - if (madt->PCATCompat) + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) ioapic_enable_mixed_mode(); madt_walk_table(madt_parse_apics, NULL); @@ -595,8 +595,14 @@ enum intr_polarity pol; char buf[64]; + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && + intr->Interrupt == 2) { + if (bootverbose) + printf("MADT: Skipping timer override\n"); + return; + } if (bootverbose) - printf("MADT: intr override: source %u, irq %u\n", + printf("MADT: Interrupt override: source %u, irq %u\n", intr->Source, intr->Interrupt); KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); if (madt_find_interrupt(intr->Interrupt, &new_ioapic, --- //depot/vendor/freebsd/src/sys/i386/i386/io_apic.c 2005/01/18 20:30:33 +++ //depot/user/jhb/acpipci/i386/i386/io_apic.c 2005/02/08 19:07:03 @@ -547,10 +547,11 @@ /* * Assume that pin 0 on the first I/O APIC is an ExtINT pin - * and that pins 1-15 are ISA interrupts. Assume that all + * if mixed mode is enabled and an ISA interrupt if not. + * Assume that pins 1-15 are ISA interrupts and that all * other pins are PCI interrupts. */ - if (intpin->io_vector == 0) + if (intpin->io_vector == 0 && mixed_mode_enabled) ioapic_set_extint(io, i); else if (intpin->io_vector < IOAPIC_ISA_INTS) { intpin->io_bus = APIC_BUS_ISA; -- 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 Feb 14 22:49: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 60E2516A50E; Mon, 14 Feb 2005 22:49:09 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF1E143D2D; Mon, 14 Feb 2005 22:49:06 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1EMn6j8097843; Mon, 14 Feb 2005 17:49:06 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 14 Feb 2005 17:48:58 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> In-Reply-To: <200502141722.10259.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502141748.58692.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 14 Feb 2005 22:49:09 -0000 On Monday 14 February 2005 05:22 pm, John Baldwin wrote: > I've tweaked Jung-uk Kim's patches to be driven by a single ACPI > quirk rather than multiple hints. I've included the patch below. > If the quirk is not automatically detected on your laptop, you can > manually set it from the loader via 'set debug.acpi.quirks=4'. If > you have to manually set the quirk to get it to work, please let me > know and include the FADT header from your acpidump in your reply, > thanks. FYI, 'debug.acpi.quirks' was committed very recently: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi.c.diff?r1=1.199&r2=1.200 If you want to try 'debug.acpi.quirks' tunable, don't forget to cvs up or patch it first. Thanks, Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 01:40:38 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 DD72A16A4CE; Tue, 15 Feb 2005 01:40:38 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AAEE43D41; Tue, 15 Feb 2005 01:40:38 +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 j1F1ebFs051493; Mon, 14 Feb 2005 17:40:37 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1F1ebg1051492; Mon, 14 Feb 2005 17:40:37 -0800 (PST) (envelope-from obrien) Date: Mon, 14 Feb 2005 17:40:37 -0800 From: "David O'Brien" To: John Baldwin Message-ID: <20050215014037.GA51389@dragon.nuxi.com> References: <200502141722.10259.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502141722.10259.jhb@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 cc: freebsd-amd64@FreeBSD.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 01:40:39 -0000 On Mon, Feb 14, 2005 at 05:22:10PM -0500, John Baldwin wrote: > it to work, please let me know and include the FADT header from your acpidump > in your reply, thanks. .. > +# Compaq R3000Z > +name: Compaq_R3000Z > +oem: FADT "NVIDIA" "CK8 " > +oem_rev: FADT = 0x6040000 > +creator: FADT "PTL_" Exactly which parts of 'acpidump -t FADT' are pulled for these entries? Given this output, I'm not sure which one would make an ACPI quirk from if they needed to. /* RSD PTR: OEM=ACPIAM, ACPI_Rev=2.0x (2) XSDT=0x1ff30100, length=33, cksum=204 */ /* XSDT: Length=60, Revision=1, Checksum=93, OEMID=A M I, OEM Table ID=OEMXSDT, OEM Revision=0x10000427, Creator ID=MSFT, Creator Revision=0x97 Entries={ 0x1ff30290, 0x1ff30390, 0x1ff40040 } */ /* FACP: Length=244, Revision=3, Checksum=239, OEMID=A M I, OEM Table ID=OEMFACP, OEM Revision=0x10000427, Creator ID=MSFT, Creator Revision=0x97 FACS=0x1ff40000, DSDT=0x1ff303e0 INT_MODEL=APIC Preferred_PM_Profile=Desktop (1) SCI_INT=9 SMI_CMD=0x82f, ACPI_ENABLE=0xe1, ACPI_DISABLE=0x1e, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0x800-0x803 PM1a_CNT_BLK=0x804-0x805 PM_TMR_BLK=0x808-0x80b GPE0_BLK=0x820-0x823 CST_CNT=0xe3 P_LVL2_LAT=101 us, P_LVL3_LAT=1001 us FLUSH_SIZE=1024, FLUSH_STRIDE=16 DUTY_OFFSET=0, DUTY_WIDTH=0 DAY_ALRM=125, MON_ALRM=126, CENTURY=50 IAPC_BOOT_ARCH={LEGACY_DEV,8042} Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,HEADLESS} X_FACS=0x1ff40000, X_DSDT=0x1ff303e0 X_PM1a_EVT_BLK=0x00:0[32] (IO) X_PM1a_CNT_BLK=0x00:0[16] (IO) X_PM_TMR_BLK=0x00:0[32] (IO) */ /* FACS: Length=64, HwSig=0x00000000, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=1 */ /* DSDT: Length=13756, Revision=1, Checksum=4, OEMID=SK8V_, OEM Table ID=SK8V_033, OEM Revision=0x33, Creator ID=MSFT, Creator Revision=0x100000d */ /* APIC: Length=74, Revision=1, Checksum=116, OEMID=A M I, OEM Table ID=OEMAPIC, OEM Revision=0x10000427, Creator ID=MSFT, Creator Revision=0x97 Local APIC ADDR=0xfee00000 Flags={PC-AT} Type=Local APIC ACPI CPU=1 Flags={ENABLED} APIC ID=0 Type=IO APIC APIC ID=1 INT BASE=0 ADDR=0x00000000fec00000 Type=INT Override BUS=0 IRQ=0 INTR=2 Flags={Polarity=conforming, Trigger=conforming} */ /* OEMB: Length=63, Revision=1, Checksum=215, OEMID=A M I, OEM Table ID=OEMBIOS, OEM Revision=0x10000427, Creator ID=MSFT, Creator Revision=0x97 */ -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 01:47: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 9A1F416A4CE; Tue, 15 Feb 2005 01:47:29 +0000 (GMT) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.43.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 553A543D39; Tue, 15 Feb 2005 01:47:29 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id E003D58866; Mon, 14 Feb 2005 17:47:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by groat.ugcs.caltech.edu (Postfix) with ESMTP id 38FF318001; Mon, 14 Feb 2005 17:47:27 -0800 (PST) Date: Mon, 14 Feb 2005 17:47:27 -0800 (PST) From: "Jonathan A. Dama" To: Doug White In-Reply-To: <20050214101303.R13953@carver.gumbysoft.com> Message-ID: References: <20050214161959.1FDC343D39@mx1.FreeBSD.org> <20050214101303.R13953@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alan Jay cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 01:47:29 -0000 We also have these boards, I've found them unusable under FreeBSD/5.3-STABLE with 8GB of RAM--other qualities appear to work okay. But I even saw some infrequent problems with 6GB. FreeBSD/amd64 is not in my opinion not actually a stable tier 1 quality release under these configurations, too many problems remain--especially in regards to ia32 emulation. Exigencies of the moment forced us to forgo further debugging and adopt linux/amd64. (Sadly, some people actually have to get work done on their hardware...) To anyone who wants to peg these problems on hardware, running linux these machines have operated without fault while under a mix of high computational and i/o load. moreover, the machines were tested extensively using memtest+ in a controlled ambient temperature range from 60F to 80F. This is a really lamentable situation. We've been a primarily FreeBSD shop for 10 years now and for the past 4 years or so a pure FreeBSD shop. Switching to linux on just these machines has been quite the headache but I'm holding on to the hope that FreeBSD/amd64 will shape up. FYI, most of the positive reports I've seen regarding FreeBSD and this motherboard are 2GB setups. In my own testing that arrangement worked _very_ well. Addendum: The RAM timing is a bit marginal on the second processor. i.e., RAM that runs fine under extensive memtest+ ing has trouble doing 400MHz DDR on the Second Processor. We ended up running it at 333MHz DDR -Jon On Mon, 14 Feb 2005, Doug White wrote: > On Mon, 14 Feb 2005, Alan Jay wrote: > > > I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S Pro > > S2882 with 8Gb of RAM and had a reasonably stable operation for a few days we > > installed a couple of databases one worked fine but the other kept on causing > > the server to crash. > > I'm about to gain access to an S2881, which is a similar board (different > layout but same parts). > > > I have searched the archive and there were issues last year but I couldn't > > work out if these have been totally resolved? > > > > The adapter does work fine in low levels of loading but when pushed (it is > > connected to a Gigabit switch) it seems to be the cause of the reboot - a what > > appeared to be stable server with moderate Ethernet activity was fine upping > > the activity with a new service caused regular reboots. > > > > There is no console message at the point of reboot to help that we have > > spotted. > > > Hm, triple fault or other hardware reset. This usually indicates bad > hardware. Have you tried swapping the RAM between the systems and seeing > if the problem follows? An unrecoverable ECC fault can cause a reboot, > along with strangeness caused by temperature/power supply/etc. Or the > board could be Just Plain Bad. > > Considering you have one working machine, adn this is a very popular > board, I don't think it s abasic problem with FreeBSD and this hardware. > The worst thing reported is interrupt routing usually. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 08:38: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 927A416A4CE; Tue, 15 Feb 2005 08:38:26 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2582243D4C; Tue, 15 Feb 2005 08:38:26 +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 j1F8cO2F062179; Tue, 15 Feb 2005 00:38:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1F8cOi0062178; Tue, 15 Feb 2005 00:38:24 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 00:38:23 -0800 From: "David O'Brien" To: "Jonathan A. Dama" Message-ID: <20050215083823.GA61934@dragon.nuxi.com> References: <20050214161959.1FDC343D39@mx1.FreeBSD.org> <20050214101303.R13953@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 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-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 08:38:26 -0000 On Mon, Feb 14, 2005 at 05:47:27PM -0800, Jonathan A. Dama wrote: > FreeBSD/amd64 is not in my opinion not actually a stable tier 1 quality > release under these configurations, too many problems remain--especially > in regards to ia32 emulation. It is not required for a Tier-1 platform to have 32-bit support. Our UltraSparc platform does not have 32-bit support. Nor does any other of our 64-bit platforms. > We also have these boards, I've found them unusable under > FreeBSD/5.3-STABLE with 8GB of RAM--other qualities appear to work okay. > But I even saw some infrequent problems with 6GB. This problem is of course valid. > This is a really lamentable situation. We've been a primarily FreeBSD > shop for 10 years now and for the past 4 years or so a pure FreeBSD shop. > Switching to linux on just these machines has been quite the headache but > I'm holding on to the hope that FreeBSD/amd64 will shape up. FreeBSD/amd64 will only get better with your bug reports, testing, and feedback. I searched the GNATS PR database and only saw you've submitted 2 PR's for something we don't claim to really support (32-bit binaries on 64-bit OS). Please submit a PR for the Broadcom and 8GB issues. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 11:36:52 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 422B416A4CE for ; Tue, 15 Feb 2005 11:36:52 +0000 (GMT) Received: from beastie.hyow.eu.org (beastie.hyow.eu.org [213.152.46.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id F155343D1F for ; Tue, 15 Feb 2005 11:36:50 +0000 (GMT) (envelope-from mark@hyow.eu.org) Received: (qmail 94997 invoked by uid 751); 15 Feb 2005 11:38:00 +0000 Received: from mark@hyow.eu.org by beastie.hyow.eu.org by uid 731 with qmail-scanner-1.22-st-qms Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 5.570517 secs); 15 Feb 2005 11:38:00 -0000 X-Spam-Status: No, hits=-2.8 required=5.0 X-Antivirus-HYOW.EU.ORG-Mail-From: mark@hyow.eu.org via beastie.hyow.eu.org X-Antivirus-HYOW.EU.ORG: 1.22-st-qms (Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 5.570517 secs Process 94991) Received: from deity.hyow.eu.org (mark@hyow.eu.org@10.0.0.11) by beastie.hyow.eu.org with AES256-SHA encrypted SMTP; 15 Feb 2005 11:37:54 +0000 Date: Tue, 15 Feb 2005 11:36:49 +0000 From: Mark Magiera To: amd64@freebsd.org Message-Id: <20050215113649.7bfcb1cd.mark@hyow.eu.org> In-Reply-To: <20050208193338.6ee460d9.mark@hyow.eu.org> References: <20050208193338.6ee460d9.mark@hyow.eu.org> X-Mailer: Sylpheed version 1.0.0-gtk2-20041224 (GTK+ 2.4.14; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 15 Feb 2005 11:36:52 -0000 On Tue, 8 Feb 2005 19:33:38 +0000 Mark Magiera wrote: > I'm finally planning on upgrading to a 64bit system this wekeend > however I'm looking for a motherboard that is high performance for > gaming in windows, but also has the hardware support in FreeBSD since > I'll be running that most of the time. > > The thing I'm unsure about is, how well are the nforce4 chipsets > supported in FreeBSD? and what about PCI-E, would one of those mobo's > in combination with a PCI-E nvidia card work? > > Also, I'm planning on running this on a RELENG_5 installation, would I > be better off with a HEAD install? > I'd rather stick with freebsd 5.x but if it doesn't support PCI-E or > something and freebsd 6 does, I'll probably end up going with that. > > Any advice would be much appreciated > > -- Mark Magiera Ok, quick update. I finally bought the mobo (Asus A8N-SLi) along with a 6600GT PCI-E and while there are a few problems, they seem the kind that can be ironed out over time. Basically, freebsd installs in both 32 and 64 bit mode but in both cases, the network card is so unrelaible that half way through a cvsup (or anything else) it dies and nothing (that I know of) but a reboot fixes it, this is for the "sk" device. As for the other nic (the nforce one), I didn't look into it much but it seems there's no driver for it except one possibly (ports/net/nvnet) but since I'm unable to even do a simple cvsup with the other card, it's not much use. Also the nvnet driver is for 32bit mode only. For some further testing, I booted a FreeSBIE cd (to see if the GPU worked) and X/xfce4 ran on that flawlesly, probabaly not with the nvidia driver but still good to know. Basically, if anyone's going for a 64 bit install with similair hardware, forget about it if you rely on network access or unless either the "sk" drivers are updated to a state where they work better, or you have all distfiles and a recent snapshot of ports on cd. For a 32bit install I guess you might be ok if you got the nvidia nic to work (I didn't get it working but then again I didn't play much), which you would still need a cd with distfiles on it since the other nic won't last long enough to download them, or a pci nic I guess. I may try putting in a proper pci nic if I have time, but for now this is all the info I have. I hope it helps anyone seeking information on this hardware combined with freebsd. Apologies if anyone finds this irrelevant but I beleive there had been no information about the usage of this mobo until now and others might find this useful should they be contemplating a similair purchase -- Mark Magiera PS. If I find anything out that contradicts anything I've said, I'll post it. Other than that, for now you can consider this mobo working, except both nic's are either non-functional or almost unusable (depeding on which nic you use) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 13:34: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 1288716A4CE for ; Tue, 15 Feb 2005 13:34:43 +0000 (GMT) Received: from gate.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B9A443D46 for ; Tue, 15 Feb 2005 13:34:42 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by gate.xbsd.org (Postfix) with ESMTP id AAF59116FA; Tue, 15 Feb 2005 14:35:19 +0100 (CET) Received: from gate.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17459-04; Tue, 15 Feb 2005 14:35:01 +0100 (CET) Received: from [192.168.20.107] (ALagny-109-1-8-82.w81-50.abo.wanadoo.fr [81.50.56.82]) by gate.xbsd.org (Postfix) with ESMTP id 1D6A8116C9; Tue, 15 Feb 2005 14:35:00 +0100 (CET) Message-ID: <4211FA51.3060302@xbsd.org> Date: Tue, 15 Feb 2005 14:34:09 +0100 From: Florent Thoumie User-Agent: Mozilla Thunderbird 1.0 (X11/20050107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Magiera References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> In-Reply-To: <20050215113649.7bfcb1cd.mark@hyow.eu.org> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB97509E52BDCB5E39FD14665" X-Virus-Scanned: amavisd-new at xbsd.org cc: amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 15 Feb 2005 13:34:43 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB97509E52BDCB5E39FD14665 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mark Magiera wrote: > Ok, quick update. I finally bought the mobo (Asus A8N-SLi) along with a > 6600GT PCI-E and while there are a few problems, they seem the kind that > can be ironed out over time. I have the same motherboard with a Geforce 6600 too. > Basically, freebsd installs in both 32 and 64 bit mode but in both > cases, the network card is so unrelaible that half way through a cvsup > (or anything else) it dies and nothing (that I know of) but a reboot > fixes it, this is for the "sk" device. As for the other nic (the nforce > one), I didn't look into it much but it seems there's no driver for it > except one possibly (ports/net/nvnet) but since I'm unable to even do a > simple cvsup with the other card, it's not much use. Also the nvnet > driver is for 32bit mode only. I tried unsuccessfully net/nvnet. > For some further testing, I booted a FreeSBIE cd (to see if the GPU > worked) and X/xfce4 ran on that flawlesly, probabaly not with the nvidia > driver but still good to know. > > Basically, if anyone's going for a 64 bit install with similair > hardware, forget about it if you rely on network access or unless > either the "sk" drivers are updated to a state where they work better, > or you have all distfiles and a recent snapshot of ports on cd. sk(4) driver included in 5.3-R is indeed unusable. It took me some hours to get a fresh src-all cvsup'd. I don't have problems now with this chip, but I think it had issues with DHCP. Not sure though. I'm waiting for new xorg to see if I can run a decent X server because Nvidia hasn't released amd64 version of their FreeBSD driver yet. -- Florent Thoumie flz@xbsd.org --------------enigB97509E52BDCB5E39FD14665 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCEfpWMxEkbVFH3PQRAi4iAJ9dP7BtCpALMrw+ZaDPLyhZQB+Y5wCfU0KI 7YKJ+X3URyegvAdmokEXW+Q= =H0eA -----END PGP SIGNATURE----- --------------enigB97509E52BDCB5E39FD14665-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 14:57: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 EC6CC16A4CF for ; Tue, 15 Feb 2005 14:57:35 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F1C43D54 for ; Tue, 15 Feb 2005 14:57:34 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so800816wra for ; Tue, 15 Feb 2005 06:57:33 -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=TgdEo3qqB0qGpsSmpV00WI6iAn2ZhSB2ZZWNpH8JhKuz5gySDL8p6U3XSmD51xSv969ZUMHe/8dCOufehmetMO7tNExxQp8sZ2FsJmTIrrqosn4OHH0ysSA85kSHI9RAL6WKCUKC+TDjO0Lnwn63057JSj2iIgQxuJOMgh87yIw= Received: by 10.54.23.34 with SMTP id 34mr184801wrw; Tue, 15 Feb 2005 06:57:33 -0800 (PST) Received: by 10.54.7.6 with HTTP; Tue, 15 Feb 2005 06:57:33 -0800 (PST) Message-ID: <6eb82e050215065762c63576@mail.gmail.com> Date: Tue, 15 Feb 2005 22:57:33 +0800 From: Rong-En Fan To: amd64@freebsd.org, stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: panic: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 14:57:36 -0000 Hello, This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM and a LSI 21320 rmpt(4) running at 160MB/s with a hardware RAID (da0, da1). HTT is enabled. When I run benchmark/blogbench on /da0/ I can *reproduce* this panic again and again: (I'm getting a dump now, let me fsck first) kernel conf & dmesg (boot -v) are at http://rafan.infor.org/tmp/236/ any suggestions are welcome. :) Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x88 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff80235b0b stack pointer = 0x10:0xffffffffb1bd5a50 frame pointer = 0x10:0xffffffffb1bd5a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 96 (pagedaemon) [thread 100114] Stopped at thread_fini+0xab: subl 0x88(%ebx),%eax db> trace thread_fini() at thread_fini+0xab zone_drain() at zone_drain+0x22d zone_foreach() at zone_foreach+0x76 uma_reclaim() at uma_reclaim+0x15 vm_pageout_scan() at vm_pageout_scan+0x170 vm_pageout() at vm_pageout+0x38e fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb1bd5d00, rbp = 0 --- db> ps pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd 615 ffffff00603348b8 ffffffffb43b5000 0 568 615 000c082 (threaded) blogbench thread 0xffffff001e7ef000 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff000881fa40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d19c40][SLP] thread 0xffffff001c25d520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d37640][SLP] thread 0xffffff000881fcd0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff001ffa27b0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff001b755520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a373640][SLP] thread 0xffffff0070700a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2d8b40][SLP] thread 0xffffff002c333cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f1c140][SLP] thread 0xffffff00462e0520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a104e40][SLP] thread 0xffffff0011002a40 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff0059594c80][SLP] thread 0xffffff006310f7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a237740][SLP] thread 0xffffff003c731520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff00087c1500][SLP] thread 0xffffff0033c33290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ee8e40][SLP] thread 0xffffff00635a7290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d86840][SLP] thread 0xffffff006ff7ccd0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff000881f520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99fbb440][SLP] thread 0xffffff006eff2520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99a01640][SLP] thread 0xffffff004d176520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a069140][SLP] thread 0xffffff0048ded520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f9c540][SLP] thread 0xffffff003689f7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d7c940][SLP] thread 0xffffff0052446cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f22d40][SLP] thread 0xffffff006eff2000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99a6c140][SLP] thread 0xffffff0054121cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff0059112500][SLP] thread 0xffffff00492bc000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a315440][SLP] thread 0xffffff003289ba40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ff1d40][SLP] thread 0xffffff0055b3ea40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99fe2140][SLP] thread 0xffffff0055b3e000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff999d1340][SLP] thread 0xffffff003689f290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2bc040][SLP] thread 0xffffff000881f000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99bc8440][SLP] thread 0xffffff006ff7c000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99c2ed40][SLP] thread 0xffffff003289b000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a0c0a40][SLP] thread 0xffffff003c731a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99c9ec40][SLP] thread 0xffffff0009f50cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99b1c240][SLP] thread 0xffffff000dbd5cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a1fff40][SLP] thread 0xffffff003c9bdcd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d06440][SLP] thread 0xffffff003c9bd7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a202c40][SLP] thread 0xffffff006ac1ba40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a30c740][SLP] thread 0xffffff00342f4290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a00ee40][SLP] thread 0xffffff004819d290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99dc3440][SLP] thread 0xffffff005cd927b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99b6ed40][SLP] thread 0xffffff00462e0290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a25ff40][SLP] thread 0xffffff0033047290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2d1040][SLP] thread 0xffffff00312cf520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a13e440][SLP] thread 0xffffff00640bf000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a1dfb40][SLP] thread 0xffffff003289b7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a144440][SLP] thread 0xffffff0060817a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff999c3840][SLP] thread 0xffffff00083a8520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005dbd5140][SLP] thread 0xffffff0049a4ccd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ac3740][SLP] thread 0xffffff0025fc4520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99e8d040][SLP] thread 0xffffff002a956000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99af9740][SLP] thread 0xffffff007821f520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005b19ec80][SLP] thread 0xffffff0039650000 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005b19ec80][SLP] thread 0xffffff00635a7000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a376940][SLP] thread 0xffffff006ac1b290 ksegrp 0xffffff007b7b7b00 [SLPQ ksesigwait 0xffffff0060334a68][SLP] 568 ffffff0062a255d0 ffffffffb426a000 0 567 568 0004002 [SLPQ pause 0xffffff0062a25640][SLP] csh 567 ffffff005fc94000 ffffffffb43c1000 0 1 567 0004102 [SLPQ wait 0xffffff005fc94000][SLP] login 566 ffffff0060a3a5d0 ffffffffb43b9000 0 1 566 0004002 [SLPQ ttyin 0xffffff007b348410][SLP] getty 565 ffffff0062a26ba0 ffffffffb4271000 0 1 565 0004002 [SLPQ ttyin 0xffffff007b348810][SLP] getty 564 ffffff0062a792e8 ffffffffb434a000 0 1 564 0004002 [SLPQ ttyin 0xffffff007b348c10][SLP] getty 563 ffffff00609bbba0 ffffffffb43c0000 0 1 563 0004002 [SLPQ ttyin 0xffffff007af69010][SLP] getty 562 ffffff00609bb5d0 ffffffffb43be000 0 1 562 0004002 [SLPQ ttyin 0xffffff007af69410][SLP] getty 561 ffffff007b2b7ba0 ffffffffb4195000 0 1 561 0004002 [SLPQ ttyin 0xffffff0000a35810][SLP] getty 560 ffffff0062bc0000 ffffffffb419b000 0 1 560 0004002 [SLPQ ttyin 0xffffff007af2c810][SLP] getty 555 ffffff0060a3aba0 ffffffffb43bb000 0 1 555 0000000 [SLPQ select 0xffffffff8052fb70][SLP] inetd 526 ffffff00600fc000 ffffffffb443e000 0 1 525 0000000 [SLPQ select 0xffffffff8052fb70][SLP] snmpd 507 ffffff006013d8b8 ffffffffb4446000 0 1 507 0000000 [SLPQ nanslp 0xffffffff80527440][SLP] cron 495 ffffff0062a628b8 ffffffffb4266000 25 1 495 0000100 [SLPQ pause 0xffffff0062a62928][SLP] sendmail 491 ffffff0060334000 ffffffffb4358000 0 1 491 0000100 [SLPQ select 0xffffffff8052fb70][SLP] sendmail 485 ffffff00602132e8 ffffffffb4354000 0 1 485 0000100 [SLPQ select 0xffffffff8052fb70][SLP] sshd 471 ffffff007b295ba0 ffffffffb414f000 0 1 471 0000000 [SLPQ select 0xffffffff8052fb70][SLP] ntpd 435 ffffff0062a625d0 ffffffffb4265000 0 429 429 0000100 [SLPQ select 0xffffffff8052fb70][SLP] rpc.lockd 429 ffffff007b2b72e8 ffffffffb4192000 0 1 429 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpc.lockd 424 ffffff0062c085d0 ffffffffb4201000 0 1 424 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpc.statd 418 ffffff0062a5d8b8 ffffffffb4261000 0 414 414 0000000 [SLPQ - 0xffffff000d749800][SLP] nfsd 417 ffffff007b2da2e8 ffffffffb4197000 0 414 414 0000000 [SLPQ - 0xffffff000dc11c00][SLP] nfsd 416 ffffff0062c08ba0 ffffffffb4203000 0 414 414 0000000 [SLPQ - 0xffffff0062b0e400][SLP] nfsd 415 ffffff0062a5dba0 ffffffffb4262000 0 414 414 0000000 [SLPQ - 0xffffff000dc11a00][SLP] nfsd 414 ffffff007b2952e8 ffffffffb414c000 0 1 414 0000000 [SLPQ accept 0xffffff00617596d6][SLP] nfsd 406 ffffff007b2b78b8 ffffffffb4194000 0 1 406 0000000 [SLPQ select 0xffffffff8052fb70][SLP] mountd 354 ffffff007b2daba0 ffffffffb419a000 0 1 354 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpcbind 341 ffffff0062a622e8 ffffffffb4264000 0 1 341 0000000 [SLPQ select 0xffffffff8052fb70][SLP] syslogd 321 ffffff0062a26000 ffffffffb426d000 0 1 321 0000000 [SLPQ select 0xffffffff8052fb70][SLP] devd 245 ffffff0062bc0ba0 ffffffffb41f9000 0 1 245 0000000 [SLPQ pause 0xffffff0062bc0c10][SLP] adjkerntz 106 ffffff007b2da000 ffffffffb4196000 0 0 0 0000204 [SLPQ - 0xffffffffb4173c0c][SLP] schedcpu 105 ffffff007b796000 ffffffffb1b8b000 0 0 0 0000204 [SLPQ - 0xffffffff805344d8][SLP] nfsiod 3 104 ffffff007b7962e8 ffffffffb1b8c000 0 0 0 0000204 [SLPQ - 0xffffffff805344d0][SLP] nfsiod 2 103 ffffff007b7965d0 ffffffffb1b8d000 0 0 0 0000204 [SLPQ - 0xffffffff805344c8][SLP] nfsiod 1 102 ffffff007b7968b8 ffffffffb1b8e000 0 0 0 0000204 [SLPQ - 0xffffffff805344c0][SLP] nfsiod 0 101 ffffff007b796ba0 ffffffffb1b8f000 0 0 0 0000204 [SLPQ syncer 0xffffffff80527120][SLP] syncer 100 ffffff007b7d8000 ffffffffb1b90000 0 0 0 0000204 [SLPQ vlruwt 0xffffff007b7d8000][SLP] vnlru 99 ffffff007b7d82e8 ffffffffb1b91000 0 0 0 0000204 [SLPQ wdrain 0xffffffff805304e8][SLP] bufdaemon 98 ffffff007b7d85d0 ffffffffb1b92000 0 0 0 000020c [SLPQ pgzero 0xffffffff8053ce74][SLP] pagezero 97 ffffff007b7d88b8 ffffffffb1b93000 0 0 0 0000204 [SLPQ psleep 0xffffffff8053cedc][SLP] vmdaemon 96 ffffff007b7d8ba0 ffffffffb1b94000 0 0 0 0000204 [CPU 2] pagedaemon 95 ffffff007b7bd000 ffffffffb1bef000 0 0 0 0000204 [IWAIT] swi0: sio 9 ffffff007b7bd2e8 ffffffffb1bf0000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task2 8 ffffff007b7bd5d0 ffffffffb1bf1000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task1 7 ffffff007b7bd8b8 ffffffffb1bf2000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task0 94 ffffff007b7bdba0 ffffffffb1bf3000 0 0 0 0000204 [IWAIT] swi6: acpitaskq 6 ffffff007b7472e8 ffffffffb1b23000 0 0 0 0000204 [SLPQ - 0xffffff00009d1100][SLP] kqueue taskq 93 ffffff007b7475d0 ffffffffb1b24000 0 0 0 0000204 [IWAIT] swi6:+ 5 ffffff007b7478b8 ffffffffb1b25000 0 0 0 0000204 [SLPQ - 0xffffff00009d1280][SLP] thread taskq 92 ffffff007b747ba0 ffffffffb1b26000 0 0 0 0000204 [IWAIT] swi6:+ 91 ffffff007b775000 ffffffffb1b27000 0 0 0 0000204 [IWAIT] swi6: task queue 90 ffffff007b7752e8 ffffffffb1b28000 0 0 0 0000204 [IWAIT] swi3: cambio 89 ffffff007b7755d0 ffffffffb1b29000 0 0 0 0000204 [IWAIT] swi2: camnet 88 ffffff007b7758b8 ffffffffb1b2a000 0 0 0 0000204 [SLPQ - 0xffffffff8051a720][SLP] yarrow 4 ffffff007b775ba0 ffffffffb1b2b000 0 0 0 0000204 [CPU 0] g_down 3 ffffff007b7f9000 ffffffffb1b86000 0 0 0 0000204 [CPU 3] g_up 2 ffffff007b7f92e8 ffffffffb1b87000 0 0 0 0000204 [SLPQ - 0xffffffff8051e490][SLP] g_event 87 ffffff007b7f95d0 ffffffffb1b88000 0 0 0 0000204 [IWAIT] swi1: net 86 ffffff007b7f98b8 ffffffffb1b89000 0 0 0 0000204 [IWAIT] swi4: vm 85 ffffff007b7f9ba0 ffffffffb1b8a000 0 0 0 000020c [RUNQ] swi5: clock sio 84 ffffff007b7518b8 ffffffffb1ada000 0 0 0 0000204 [IWAIT] irq23: 83 ffffff007b751ba0 ffffffffb1adb000 0 0 0 0000204 [IWAIT] irq22: 82 ffffff007b761000 ffffffffb1adc000 0 0 0 0000204 [IWAIT] irq21: 81 ffffff007b7612e8 ffffffffb1add000 0 0 0 0000204 [IWAIT] irq20: 80 ffffff007b7615d0 ffffffffb1ade000 0 0 0 0000204 [IWAIT] irq19: 79 ffffff007b7618b8 ffffffffb1adf000 0 0 0 0000204 [IWAIT] irq18: 78 ffffff007b761ba0 ffffffffb1ae0000 0 0 0 0000204 [IWAIT] irq17: 77 ffffff007b763000 ffffffffb1ae1000 0 0 0 0000204 [RUNQ] irq16: bge0 bge1 76 ffffff007b7632e8 ffffffffb1b1e000 0 0 0 0000204 [IWAIT] irq15: ata1 75 ffffff007b7635d0 ffffffffb1b1f000 0 0 0 0000204 [IWAIT] irq14: ata0 74 ffffff007b7638b8 ffffffffb1b20000 0 0 0 0000204 [IWAIT] irq13: 73 ffffff007b763ba0 ffffffffb1b21000 0 0 0 0000204 [IWAIT] irq12: 72 ffffff007b747000 ffffffffb1b22000 0 0 0 0000204 [IWAIT] irq11: 71 ffffff007b7d62e8 ffffffffb1a92000 0 0 0 0000204 [IWAIT] irq10: 70 ffffff007b7d65d0 ffffffffb1a93000 0 0 0 0000204 [IWAIT] irq9: acpi0 69 ffffff007b7d68b8 ffffffffb1a94000 0 0 0 0000204 [IWAIT] irq8: rtc 68 ffffff007b7d6ba0 ffffffffb1a95000 0 0 0 0000204 [IWAIT] irq7: 67 ffffff007b74e000 ffffffffb1a96000 0 0 0 0000204 [IWAIT] irq6: 66 ffffff007b74e2e8 ffffffffb1a97000 0 0 0 0000204 [IWAIT] irq5: 65 ffffff007b74e5d0 ffffffffb1a98000 0 0 0 0000204 [IWAIT] irq4: sio0 64 ffffff007b74e8b8 ffffffffb1ad5000 0 0 0 0000204 [IWAIT] irq3: sio1 63 ffffff007b74eba0 ffffffffb1ad6000 0 0 0 0000204 [IWAIT] irq0: clk 62 ffffff007b751000 ffffffffb1ad7000 0 0 0 0000204 [IWAIT] irq1: atkbd0 61 ffffff007b7512e8 ffffffffb1ad8000 0 0 0 0000204 [IWAIT] irq47: 60 ffffff007b7515d0 ffffffffb1ad9000 0 0 0 0000204 [IWAIT] irq46: 59 ffffff007b770000 ffffffffb1a4b000 0 0 0 0000204 [IWAIT] irq45: 58 ffffff007b7702e8 ffffffffb1a4c000 0 0 0 0000204 [IWAIT] irq44: 57 ffffff007b7705d0 ffffffffb1a4d000 0 0 0 0000204 [IWAIT] irq43: 56 ffffff007b7708b8 ffffffffb1a4e000 0 0 0 0000204 [IWAIT] irq42: 55 ffffff007b770ba0 ffffffffb1a4f000 0 0 0 0000204 [IWAIT] irq41: 54 ffffff007b771000 ffffffffb1a50000 0 0 0 0000204 [IWAIT] irq40: 53 ffffff007b7712e8 ffffffffb1a8d000 0 0 0 0000204 [IWAIT] irq39: 52 ffffff007b7715d0 ffffffffb1a8e000 0 0 0 0000204 [IWAIT] irq38: ips0 51 ffffff007b7718b8 ffffffffb1a8f000 0 0 0 0000204 [IWAIT] irq37: 50 ffffff007b771ba0 ffffffffb1a90000 0 0 0 0000204 [IWAIT] irq36: 49 ffffff007b7d6000 ffffffffb1a91000 0 0 0 0000204 [IWAIT] irq35: 48 ffffff007b780000 ffffffffb1a05000 0 0 0 0000204 [IWAIT] irq34: 47 ffffff007b7802e8 ffffffffb1a06000 0 0 0 0000204 [IWAIT] irq33: 46 ffffff007b7805d0 ffffffffb1a07000 0 0 0 0000204 [IWAIT] irq32: 45 ffffff007b7808b8 ffffffffb1a08000 0 0 0 0000204 [IWAIT] irq31: 44 ffffff007b780ba0 ffffffffb1a09000 0 0 0 0000204 [IWAIT] irq30: 43 ffffff007b783000 ffffffffb1a46000 0 0 0 0000204 [IWAIT] irq29: 42 ffffff007b7832e8 ffffffffb1a47000 0 0 0 0000204 [IWAIT] irq28: 41 ffffff007b7835d0 ffffffffb1a48000 0 0 0 0000204 [IWAIT] irq27: 40 ffffff007b7838b8 ffffffffb1a49000 0 0 0 0000204 [IWAIT] irq26: 39 ffffff007b783ba0 ffffffffb1a4a000 0 0 0 0000204 [IWAIT] irq25: 38 ffffff007b7662e8 ffffffffb19c0000 0 0 0 0000204 [IWAIT] irq24: 37 ffffff007b7665d0 ffffffffb19c1000 0 0 0 0000204 [IWAIT] irq71: 36 ffffff007b7668b8 ffffffffb19c2000 0 0 0 0000204 [IWAIT] irq70: 35 ffffff007b766ba0 ffffffffb19c3000 0 0 0 0000204 [IWAIT] irq69: 34 ffffff007b7b5000 ffffffffb1a00000 0 0 0 0000204 [IWAIT] irq68: 33 ffffff007b7b52e8 ffffffffb1a01000 0 0 0 0000204 [IWAIT] irq67: 32 ffffff007b7b55d0 ffffffffb1a02000 0 0 0 0000204 [IWAIT] irq66: 31 ffffff007b7b58b8 ffffffffb1a03000 0 0 0 0000204 [IWAIT] irq65: 30 ffffff007b7b5ba0 ffffffffb1a04000 0 0 0 0000204 [IWAIT] irq64: 29 ffffff007b7dc8b8 ffffffffb199a000 0 0 0 0000204 [IWAIT] irq63: 28 ffffff007b7dcba0 ffffffffb199b000 0 0 0 0000204 [IWAIT] irq62: 27 ffffff007b784000 ffffffffb199c000 0 0 0 0000204 [IWAIT] irq61: 26 ffffff007b7842e8 ffffffffb19bb000 0 0 0 0000204 [IWAIT] irq60: 25 ffffff007b7845d0 ffffffffb19bc000 0 0 0 0000204 [IWAIT] irq59: 24 ffffff007b7848b8 ffffffffb19bd000 0 0 0 0000204 [IWAIT] irq58: 23 ffffff007b784ba0 ffffffffb19be000 0 0 0 0000204 [IWAIT] irq57: 22 ffffff007b766000 ffffffffb19bf000 0 0 0 0000204 [IWAIT] irq56: 21 ffffff007b7d42e8 ffffffffb1975000 0 0 0 0000204 [IWAIT] irq55: 20 ffffff007b7d45d0 ffffffffb1976000 0 0 0 0000204 [IWAIT] irq54: 19 ffffff007b7d48b8 ffffffffb1995000 0 0 0 0000204 [IWAIT] irq53: mpt1 18 ffffff007b7d4ba0 ffffffffb1996000 0 0 0 0000204 [CPU 1] irq52: mpt0 17 ffffff007b7dc000 ffffffffb1997000 0 0 0 0000204 [IWAIT] irq51: 16 ffffff007b7dc2e8 ffffffffb1998000 0 0 0 0000204 [IWAIT] irq50: 15 ffffff007b7dc5d0 ffffffffb1999000 0 0 0 0000204 [IWAIT] irq49: 14 ffffff007b76d000 ffffffffb1933000 0 0 0 0000204 [IWAIT] irq48: 13 ffffff007b76d2e8 ffffffffb1970000 0 0 0 000020c [Can run] idle: cpu0 12 ffffff007b76d5d0 ffffffffb1971000 0 0 0 000020c [Can run] idle: cpu1 11 ffffff007b76d8b8 ffffffffb1972000 0 0 0 000020c [Can run] idle: cpu2 10 ffffff007b76dba0 ffffffffb1973000 0 0 0 000020c [Can run] idle: cpu3 1 ffffff007b7d4000 ffffffffb1974000 0 0 1 0004200 [SLPQ wait 0xffffff007b7d4000][SLP] init 0 ffffffff8051e580 ffffffff805f5000 0 0 0 0000200 [SLPQ sched 0xffffffff8051e580][SLP] swapper Regards, Rong-En Fan From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 15:15: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 07E4A16A544 for ; Tue, 15 Feb 2005 15:15:11 +0000 (GMT) Received: from mail.gattaca.yadt.co.uk (gattaca.yadt.co.uk [81.187.204.179]) by mx1.FreeBSD.org (Postfix) with SMTP id 7AA3843D46 for ; Tue, 15 Feb 2005 15:15:09 +0000 (GMT) (envelope-from davidt@yadt.co.uk) Received: (qmail 46650 invoked by uid 1000); 15 Feb 2005 14:11:55 -0000 Date: Tue, 15 Feb 2005 14:11:55 +0000 From: David Taylor To: freebsd-amd64@freebsd.org Message-ID: <20050215141155.GA29160@gattaca.yadt.co.uk> Mail-Followup-To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Cross compiling for i386 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, 15 Feb 2005 15:15:11 -0000 I've recently purchased an AMD Athlon 64 3500+ with an MSI K8T Neo2 motherboard, and FreeBSD seems to work quite well with it. Other than the re0 NIC's problems with hardware checksumming for UDP. Also I can't get make build32 to complete without compiler errors, but that's not critical for now. On to the main point of this e-mail: I also have an i386 workstation, which is significantly slower at building world. I tried to cross-build the world on the amd64 box, then install it over an NFS mount. Eventually, I managed to persuade it to build and install, but it's not really a process I'd like to repeat every time I update... I managed to eventually complete a single build/install world cycle by doing something like: $ cd /usr/src; make buildworld TARGET_ARCH=i386 $ mount :/usr/src /usr/src $ mount :/usr/obj /usr/obj $ make installworld This however had a few problems. Running installworld caused the i386 box to attempt to write to /usr/src, due to newvers.sh, so I needed to mount /usr/src rw. Also the built objects appeared to be in /usr/obj/i386, whilst installworld was looking at /usr/obj. Then, installworld wanted i386 tools to install with, so I ended up trying make _worldtmp _legacy _bootstrap-tools _build-tools _cross-tools I'm not sure they were _all_ required, but eventually it completed a installworld. But not before I did manually copied ls and dd into $INSTALLTMP. btxld also failed to compile for some reason (i.e. it wasn't built, no errors) worked correctly when manually built. The only problem I had with the resulting world was the installed locales in /usr/share/locale/ were invalid (32 vs 64 bit field somewhere?), and fortune coredumped when ran. That was fixed easily enough by recompiling libc and fortune on the i386 box. Is this supposed to be possible/supported? And does anyone have any ideas how to make it work more automatically? -- David Taylor davidt@yadt.co.uk "The future just ain't what it used to be" From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 16:53: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 9389716A4CE; Tue, 15 Feb 2005 16:53:54 +0000 (GMT) Received: from dswu231.btconnect.com (c2bapps19.btconnect.com [193.113.154.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 4452143D2D; Tue, 15 Feb 2005 16:53:52 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from AJDELL9200 (actually host 232.148.36.213.in-addr.arpa) by dswu231.btconnect.com with SMTP (XT-PP) with ESMTP; Tue, 15 Feb 2005 16:53:46 +0000 From: "Alan Jay" To: "'Jonathan A. Dama'" , "'Doug White'" Date: Tue, 15 Feb 2005 16:53:24 -0000 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcUTAFGb6pyAjDr+Sku3/+TNhJE4bgAfdxxg In-Reply-To: Message-Id: <20050215165352.4452143D2D@mx1.FreeBSD.org> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 16:53:54 -0000 Thanks Jonathan for this, can I ask the unmentionalble (which Linux implementation did you pick?). I had major problems installing with more than 4Gb but once I moved to stable we seemed to have a stable platform when doing basic stuff - we have two databases (mySQL) one is reasonably heavily used and one very extensively used. They sit on different servers to maximise performance. One worked perfectly for a couple of weeks while the other more extensive one repeatedly fell over. I think I agree wholeheartedly with your comments being a great supporter of FreeBSD it is a shame that the AMD release is not as super as the other versions we have used extensively. Thanks for your support. Regards ALan > -----Original Message----- > From: Jonathan A. Dama [mailto:jd@ugcs.caltech.edu] > Sent: Tuesday, February 15, 2005 1:47 AM > To: Doug White > Cc: Alan Jay; freebsd-stable@freebsd.org; freebsd-amd64@freebsd.org > Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan > Motherboard > > We also have these boards, I've found them unusable under > FreeBSD/5.3-STABLE with 8GB of RAM--other qualities appear to work okay. > But I even saw some infrequent problems with 6GB. > > FreeBSD/amd64 is not in my opinion not actually a stable tier 1 quality > release under these configurations, too many problems remain--especially > in regards to ia32 emulation. > > Exigencies of the moment forced us to forgo further debugging and adopt > linux/amd64. (Sadly, some people actually have to get work done on their > hardware...) > > To anyone who wants to peg these problems on hardware, running linux these > machines have operated without fault while under a mix of high > computational and i/o load. moreover, the machines were tested > extensively using memtest+ in a controlled ambient temperature range from > 60F to 80F. > > This is a really lamentable situation. We've been a primarily FreeBSD > shop for 10 years now and for the past 4 years or so a pure FreeBSD shop. > Switching to linux on just these machines has been quite the headache but > I'm holding on to the hope that FreeBSD/amd64 will shape up. > > FYI, most of the positive reports I've seen regarding FreeBSD and this > motherboard are 2GB setups. In my own testing that arrangement worked > _very_ well. > > Addendum: The RAM timing is a bit marginal on the second processor. i.e., > RAM that runs fine under extensive memtest+ ing has trouble > doing 400MHz DDR on the Second Processor. We ended up running > it at 333MHz DDR > > -Jon > > > > On Mon, 14 Feb 2005, Doug White wrote: > > > On Mon, 14 Feb 2005, Alan Jay wrote: > > > > > I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S > Pro > > > S2882 with 8Gb of RAM and had a reasonably stable operation for a few > days we > > > installed a couple of databases one worked fine but the other kept on > causing > > > the server to crash. > > > > I'm about to gain access to an S2881, which is a similar board (different > > layout but same parts). > > > > > I have searched the archive and there were issues last year but I > couldn't > > > work out if these have been totally resolved? > > > > > > The adapter does work fine in low levels of loading but when pushed (it > is > > > connected to a Gigabit switch) it seems to be the cause of the reboot - > a what > > > appeared to be stable server with moderate Ethernet activity was fine > upping > > > the activity with a new service caused regular reboots. > > > > > > There is no console message at the point of reboot to help that we have > > > spotted. > > > > > > Hm, triple fault or other hardware reset. This usually indicates bad > > hardware. Have you tried swapping the RAM between the systems and seeing > > if the problem follows? An unrecoverable ECC fault can cause a reboot, > > along with strangeness caused by temperature/power supply/etc. Or the > > board could be Just Plain Bad. > > > > Considering you have one working machine, adn this is a very popular > > board, I don't think it s abasic problem with FreeBSD and this hardware. > > The worst thing reported is interrupt routing usually. > > > > -- > > Doug White | FreeBSD: The Power to Serve > > dwhite@gumbysoft.com | www.FreeBSD.org > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:07: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 8F76A16A4CE for ; Tue, 15 Feb 2005 17:07:17 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A97443D3F for ; Tue, 15 Feb 2005 17:07:17 +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 j1FH7GUo082467 for ; Tue, 15 Feb 2005 09:07:16 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FH7GWX082466 for freebsd-amd64@freebsd.org; Tue, 15 Feb 2005 09:07:16 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 09:07:16 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20050215170716.GB38158@dragon.nuxi.com> References: <20050215141155.GA29160@gattaca.yadt.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215141155.GA29160@gattaca.yadt.co.uk> 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: Cross compiling for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 17:07:17 -0000 On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > I also have an i386 workstation, which is significantly slower at building > world. I tried to cross-build the world on the amd64 box, then install it > over an NFS mount. To date we've never guaranteed that a cross-arch built world is usable. We only officially support cross-arch compiles for compile testing. There are other things in the tree that aren't size & endian-clean that prevent usable cross-arch release builds. Many (?most?) of the result from a cross-arch 'make buildworld' are usable on the target arch; but small nuances cause the total of the result to not really be usable. > Eventually, I managed to persuade it to build and > install, but it's not really a process I'd like to repeat every time I > update... > > I managed to eventually complete a single build/install world cycle by doing > something like: > > $ cd /usr/src; make buildworld TARGET_ARCH=i386 > $ mount :/usr/src /usr/src > $ mount :/usr/obj /usr/obj > $ make installworld I would mount /usr/src read-only. Probably /usr/obj also; just to make sure you don't end up writing into these directories on the i386 machine. > This however had a few problems. Running installworld caused the i386 box > to attempt to write to /usr/src, due to newvers.sh, so I needed to mount > /usr/src rw. Please submit a PR for this, with sufficient logs to see what was going on. /usr/src should be considered read-only by 'make installworld'; else it is a bug. > Also the built objects appeared to be in /usr/obj/i386, whilst > installworld was looking at /usr/obj. See above, we don't support cross-arch built installs. Given the closeness of x86 and amd64 I can understand the desire to make this work as you're wanting. But there is still so much to be done to polish FreeBSD/AMD64 in these corner cases. The Linux 32-bit support is still very rough, as you mentioned earlier the FreeBSD 32-bit support is rough. I personally don't think either should have been exposed in 5.x until they were to the point of easy-of-use and polish users are demanding in this mailing list. > Is this supposed to be possible/supported? And does anyone have any ideas > how to make it work more automatically? My suggestion is to dual-boot your AMD Athlon 64 3500+ to do builds. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:07: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 BF5F316A4CE; Tue, 15 Feb 2005 17:07:30 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 589E243D3F; Tue, 15 Feb 2005 17:07:30 +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 j1FH7iDJ034963; Tue, 15 Feb 2005 10:07:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42122C4C.3050202@samsco.org> Date: Tue, 15 Feb 2005 10:07:24 -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: Alan Jay References: <20050215165352.4452143D2D@mx1.FreeBSD.org> In-Reply-To: <20050215165352.4452143D2D@mx1.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-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: "'Jonathan A. Dama'" Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 17:07:30 -0000 Alan Jay wrote: > Thanks Jonathan for this, can I ask the unmentionalble (which Linux > implementation did you pick?). > > I had major problems installing with more than 4Gb but once I moved to stable > we seemed to have a stable platform when doing basic stuff - we have two > databases (mySQL) one is reasonably heavily used and one very extensively > used. They sit on different servers to maximise performance. One worked > perfectly for a couple of weeks while the other more extensive one repeatedly > fell over. > > I think I agree wholeheartedly with your comments being a great supporter of > FreeBSD it is a shame that the AMD release is not as super as the other > versions we have used extensively. > > Thanks for your support. > > Regards > ALan > The >4GB problems with 5.3-RELEASE are a well known problem and affect for i386 and amd64. It's pretty much fixed in the 5.3-STABLE stream, but there are a few edge cases that I still need to fix which prevent me from feeling good about turning it into a 5.3-R errata fix. It'll definitely be fixed and fully working for 5.4-RELEASE next month. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:18:07 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 14AF716A4CE; Tue, 15 Feb 2005 17:18:07 +0000 (GMT) Received: from dswu28.btconnect.com (dswu28.btconnect.com [193.113.154.29]) by mx1.FreeBSD.org (Postfix) with SMTP id 2779B43D1F; Tue, 15 Feb 2005 17:18:06 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from AJDELL9200 (actually host 56.150.36.213.in-addr.arpa) by dswu28.btconnect.com with SMTP (XT-PP) with ESMTP; Tue, 15 Feb 2005 17:16:46 +0000 From: "Alan Jay" To: "'Scott Long'" Date: Tue, 15 Feb 2005 17:16:43 -0000 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcUTgPP7QNbeqThFRGq3vmPOGaU1/QAARJ4Q In-Reply-To: <42122C4C.3050202@samsco.org> Message-Id: <20050215171806.2779B43D1F@mx1.FreeBSD.org> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: "'Jonathan A. Dama'" Subject: RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 17:18:07 -0000 > > The >4GB problems with 5.3-RELEASE are a well known problem and affect > for i386 and amd64. It's pretty much fixed in the 5.3-STABLE stream, > but there are a few edge cases that I still need to fix which prevent me > from feeling good about turning it into a 5.3-R errata fix. It'll > definitely be fixed and fully working for 5.4-RELEASE next month. > > Scott Scott thanks for that update. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:25:34 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 BF96116A4CE; Tue, 15 Feb 2005 17:25:34 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80BCF43D4C; Tue, 15 Feb 2005 17:25:34 +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 j1FHPUkk083096; Tue, 15 Feb 2005 09:25:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FHPU3M083095; Tue, 15 Feb 2005 09:25:30 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 09:25:30 -0800 From: "David O'Brien" To: Alan Jay Message-ID: <20050215172530.GC38158@dragon.nuxi.com> References: <20050215165352.4452143D2D@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215165352.4452143D2D@mx1.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 cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: "'Jonathan A. Dama'" Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 17:25:34 -0000 [ PLEASE don't top post - it losses context, and this is a Unix mailing list] On Tue, Feb 15, 2005 at 04:53:24PM -0000, Alan Jay wrote: > I had major problems installing with more than 4Gb but once I moved to stable > we seemed to have a stable platform when doing basic stuff - we have two > databases (mySQL) one is reasonably heavily used and one very extensively > used. Just to be clear, you're stating you had stability problems with 5.3-RELEASE and >4GB. But with 5.3-STABLE and >4GB you have a stable system. Correct? > I think I agree wholeheartedly with your comments being a great supporter of > FreeBSD it is a shame that the AMD release is not as super as the other > versions we have used extensively. The problem is a major bug that has existed since FreeBSD ?3.0? was exposed very close to the 5.3 release cycle. This bug only causes a major problem with >4GB, thus few of us developers experienced it. [Most of us can't afford >4GB in our machines. Donations of 1GB DIMMs for FreeBSD developers are accepted by donations@FreeBSD.org.] Of course one reason many are moving to the AMD64 platform is to have >4GB RAM in the machine. We believe this bug has been fixed in 5.3-STABLE. But too few people are testing 5.3-STABLE and are using 5.3-RELEASE instead. This isn't helping us QA the issue so that we know all the corner cases are fixed in upcoming 5.4 release. A recent 5.3-STABLE snapshot can be found as ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001-amd64-miniinst.iso and mirrors. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:39:22 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 D0B6616A4CE; Tue, 15 Feb 2005 17:39:22 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41E8F43D58; Tue, 15 Feb 2005 17:39:22 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1FHdKd3019380; Tue, 15 Feb 2005 12:39:21 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, obrien@freebsd.org Date: Tue, 15 Feb 2005 12:39:18 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <20050215014037.GA51389@dragon.nuxi.com> In-Reply-To: <20050215014037.GA51389@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502151239.18769.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 15 Feb 2005 17:39:23 -0000 On Monday 14 February 2005 08:40 pm, David O'Brien wrote: > On Mon, Feb 14, 2005 at 05:22:10PM -0500, John Baldwin wrote: > > it to work, please let me know and include the FADT header from > > your acpidump in your reply, thanks. > > .. > > > +# Compaq R3000Z > > +name: Compaq_R3000Z > > +oem: FADT "NVIDIA" "CK8 " > > +oem_rev: FADT = 0x6040000 > > +creator: FADT "PTL_" > > Exactly which parts of 'acpidump -t FADT' are pulled for these > entries? Given this output, I'm not sure which one would make an > ACPI quirk from if they needed to. --- >8 --- SNIP!!! --- >8 --- Two lines from FADT. > /* > FACP: Length=244, Revision=3, Checksum=239, > OEMID=A M I, OEM Table ID=OEMFACP, OEM Revision=0x10000427, > Creator ID=MSFT, Creator Revision=0x97 --- >8 --- SNIP!!! --- >8 --- In your case, # ASUS SK8V name: ASUS_SK8V oem: FADT "A M I " "OEMFACP " oem_rev: FADT = 0x10000427 creator: FADT "MSFT" creator_rev: FADT = 0x97 for exact match. Name must be unique in acpi_quirks. '=', '!=', '<=', '>=', '<', and '>' are allowed for revision numbers. OEM ID is 6-byte long, OEM table ID is 8-byte long, and creator ID is 4-byte long. All ID's are space padded. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:43:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id B81F416A4CF; Tue, 15 Feb 2005 17:43:18 +0000 (GMT) Date: Tue, 15 Feb 2005 17:43:18 +0000 From: David O'Brien To: John Baldwin Message-ID: <20050215174318.GA42417@hub.freebsd.org> References: <200502141722.10259.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502141722.10259.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-RC2 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: amd64@FreeBSD.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 17:43:18 -0000 On Mon, Feb 14, 2005 at 05:22:10PM -0500, John Baldwin wrote: > I've tweaked Jung-uk Kim's patches to be driven by a single ACPI quirk rather > than multiple hints. I've included the patch below. Can you commit this to HEAD ASAP (after the first "worked for me")? We really need this in 5.4-RELEASE. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:46: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 6B1E116A4CE for ; Tue, 15 Feb 2005 17:46:43 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB14B43D54 for ; Tue, 15 Feb 2005 17:46:41 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.1/8.13.1) with ESMTP id j1FHkd7B064571 for ; Tue, 15 Feb 2005 18:46:39 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id j1FHkgsc024623 for ; Tue, 15 Feb 2005 18:46:43 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id j1FHkgYV024622 for freebsd-amd64@freebsd.org; Tue, 15 Feb 2005 18:46:42 +0100 (CET) (envelope-from ftigeot) Date: Tue, 15 Feb 2005 18:46:42 +0100 From: Francois Tigeot To: freebsd-amd64@freebsd.org Message-ID: <20050215174642.GA24251@aoi.wolfpond.org> References: <20050215141155.GA29160@gattaca.yadt.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215141155.GA29160@gattaca.yadt.co.uk> User-Agent: Mutt/1.4.2.1i Subject: Re: Cross compiling for i386 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, 15 Feb 2005 17:46:43 -0000 On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > I also have an i386 workstation, which is significantly slower at building > world. I tried to cross-build the world on the amd64 box, then install it > over an NFS mount. Eventually, I managed to persuade it to build and > install, but it's not really a process I'd like to repeat every time I > update... > [...] I succeeded in running a 32-bit world built on an amd64 machine with 5.2.1-RELEASE. I used make installworld TARGET_ARCH=i386 DESTDIR=/blah on the amd64 host, which was much easier than what you did. The only issue at the time was with binutils. See this url for details: http://lists.freebsd.org/pipermail/freebsd-amd64/2004-March/000850.html > The only problem I had with the resulting world was the installed locales > in /usr/share/locale/ were invalid (32 vs 64 bit field somewhere?), and > fortune coredumped when ran. That was fixed easily enough by recompiling > libc and fortune on the i386 box. I used the binaries in an embedded system, so I had no trouble with these. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:47:00 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 886F016A4CE for ; Tue, 15 Feb 2005 17:47:00 +0000 (GMT) Received: from mail2.leitch.com (mail2.leitch.com [204.187.61.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14A8643D58 for ; Tue, 15 Feb 2005 17:46:56 +0000 (GMT) (envelope-from Xi.Liu@Leitch.com) Received: from pelican.mars.leitch.com (pelican.mars.leitch.com [192.168.233.15]) by mail2.leitch.com (8.12.10/8.12.10) with ESMTP id j1FHksBN020803 for ; Tue, 15 Feb 2005 12:46:55 -0500 (EST) Received: by pelican.mars.leitch.com with Internet Mail Service (5.5.2657.72) id <1TYH21XR>; Tue, 15 Feb 2005 12:47:20 -0500 Message-ID: From: "Xi.Liu" To: "'freebsd-amd64@freebsd.org'" Date: Tue, 15 Feb 2005 12:47:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: Can not create slice on a SATA drive 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, 15 Feb 2005 17:47:00 -0000 Hullo, I have Dell power edge S420 with only one SATA harddrive running FreeBSD 5.3-RELEASE for AMD64 platform and the system is running fine. The hardrive right now has the following partitions: ----------------------------------------------------------------------- Disk name: ad4 Disk name: ad4 FDISK Partition Editor DISK Geometry: 9726 cyls/255 heads/63 sectors = 156248190 sectors (76293MB) Offset Size(ST) End Name PType Desc Subtype Flags 0 63 62 - 12 unused 0 63 112392 112454 ad4s1 7 fat 6 112455 16579080 16691534 ad4s2 8 freebsd 165 16691535 139558465 156249999 - 12 unused 0 I am trying to create a slice to use the all the rest unused disk space, but some how I can save the changes using "sysinstall" (see error messages below) ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------- DISK Geometry: 9726 cyls/255 heads/63 sectors = 156248190 sectors (76293MB) Offset Size(ST) End Name PType Desc Subtype Flags 0 63 62 - 12 unused 0 63 112392 112454 ad4s1 7 fat 6 = 112455 16579080 16691534 ad4s2 8 freebsd 165 = 16691535 139556655 156248189 ad4s3 8 freebsd 165 = 156248190 1810 156249999 - 12 unused 0 ????????????????? Message ?????????????????? ??ERROR: Unable to write data to disk ad4! ?k ????????????????????????????????????(100%)???x ?? [ OK ] ?j ??????????[ Press enter or space ]?????????? Does anyone know why and how to fix it? The only thing is that I was not running "sysinstall" from the a local console, but from remote telnet window as root. Do I have to run sysinstall from local console? Thanks Xi From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:47: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 4A4BA16A4CE; Tue, 15 Feb 2005 17:47:18 +0000 (GMT) Received: from c2bapps17.btconnect.com (dswu194.btconnect.com [193.113.154.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 0630443D46; Tue, 15 Feb 2005 17:47:17 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from AJDELL9200 (actually host 119.0.36.213.in-addr.arpa) by dswu194.btconnect.com with SMTP (XT-PP) with ESMTP; Tue, 15 Feb 2005 17:47:01 +0000 From: "Alan Jay" To: Date: Tue, 15 Feb 2005 17:46:55 -0000 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050215172530.GC38158@dragon.nuxi.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcUTg1zjuojWkFsSTU6saBKGy90WxQAAmUuw Message-Id: <20050215174717.0630443D46@mx1.FreeBSD.org> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: "'Jonathan A. Dama'" Subject: RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 17:47:18 -0000 > -----Original Message----- > On Tue, Feb 15, 2005 at 04:53:24PM -0000, Alan Jay wrote: > > I had major problems installing with more than 4Gb but once I moved to > stable > > we seemed to have a stable platform when doing basic stuff - we have two > > databases (mySQL) one is reasonably heavily used and one very extensively > > used. > > Just to be clear, you're stating you had stability problems with > 5.3-RELEASE and >4GB. But with 5.3-STABLE and >4GB you have a stable > system. Correct? [Alan Jay] I could not install with RELEASE but could with Stable. Once installed and running we installed mySQL on the two machines one we copied over a relatively simple database which ran fine without a problem. The second machine then had another mySQL database moved to it and it started to fall over. After a number of tests we moved the first database off the what had been working server and put the other database on it. At which point that server which had been stable fell over! > > I think I agree wholeheartedly with your comments being a great supporter > of > > FreeBSD it is a shame that the AMD release is not as super as the other > > versions we have used extensively. > > The problem is a major bug that has existed since FreeBSD ?3.0? was > exposed very close to the 5.3 release cycle. This bug only causes a > major problem with >4GB, thus few of us developers experienced it. > [Most of us can't afford >4GB in our machines. Donations of 1GB DIMMs > for FreeBSD developers are accepted by donations@FreeBSD.org.] [Alan Jay] I'll put them on my present list :) > Of course one reason many are moving to the AMD64 platform is to have > >4GB RAM in the machine. We believe this bug has been fixed in > 5.3-STABLE. But too few people are testing 5.3-STABLE and are using > 5.3-RELEASE instead. This isn't helping us QA the issue so that we know > all the corner cases are fixed in upcoming 5.4 release. [Alan Jay] Well the memory seemed to be stable on 5.3 STABLE with more than 4Gb in our case 8Gb there seems to be some other problem at work here. > A recent 5.3-STABLE snapshot can be found as > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001- > amd64-miniinst.iso > and mirrors. > > -- > -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 17:59: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 2B7A916A4CE for ; Tue, 15 Feb 2005 17:59:23 +0000 (GMT) Received: from omega.nanophys.kth.se (omega.nanophys.kth.se [130.237.35.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 554D443D41 for ; Tue, 15 Feb 2005 17:59:22 +0000 (GMT) (envelope-from kono@kth.se) Received: from omega.nanophys.kth.se (localhost [127.0.0.1]) by omega.nanophys.kth.se (8.13.1/8.13.1) with ESMTP id j1FHxK4m001007 for ; Tue, 15 Feb 2005 18:59:20 +0100 (CET) (envelope-from kono@kth.se) Received: from localhost (localhost [[UNIX: localhost]]) by omega.nanophys.kth.se (8.13.1/8.13.1/Submit) id j1FHxKrD001006 for freebsd-amd64@freebsd.org; Tue, 15 Feb 2005 18:59:20 +0100 (CET) (envelope-from kono@kth.se) X-Authentication-Warning: omega.nanophys.kth.se: kono set sender to kono@kth.se using -f From: Alexander Konovalenko Organization: KTH Date: Tue, 15 Feb 2005 18:59:20 +0100 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Disposition: inline To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502151859.20792.kono@kth.se> Subject: kernel: vge0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kono@kth.se List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 17:59:23 -0000 Hello, Recently I have installed FreeBSD 5.3 (AMD64) then I updated sources to RELENG_5 and recompiled the kernel. Everything works fine except failures of onboard NIC: Feb 15 12:13:51 omega kernel: vge0: watchdog timeout Feb 15 12:13:51 omega kernel: vge0: soft reset timed outvge0: EEPROM reload timed out Feb 15 12:13:51 omega kernel: vge0: setting CAM filter failed Feb 15 12:13:51 omega kernel: miibus0: unknown CICADA PHY model 0 Feb 15 12:13:51 omega kernel: miibus0: unknown CICADA PHY model 0 it hangs, so ifconfig shows "no carrier" and I have to reboot computer. My hardware: motheboard: ABIT AV8 with VIA K8T800 Pro + VT8237 chipset cpu: AMD Athlon 64 3000+ running at 1.8GHz NIC: VIA gigabit PCI ethernet controller with operation support ACPI & wake on LAN, running on 100Mb LAN, vge0 interface boot log: vge0: port 0xb400-0xb4ff mem0xf8120000-0xf81200ff irq 22 at device 14.0 on pci0 kernel: miibus0: on vge0 kernel: vge0: Ethernet address: 00:50:8d:d1:3d:33 However, before RELENG_5 upgrades NIC worked fine (at least for 3 days)! Is there any solution for this problem? Maybe I should disable the ACPI in the BIOS? Thanks! /Alexander Konovalenko Royal Institute of Technology Stockholm, Sweden From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 18:00:13 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 2F0EB16A4CE for ; Tue, 15 Feb 2005 18:00:13 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7257143D46 for ; Tue, 15 Feb 2005 18:00:12 +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 j1FI0BHc084494; Tue, 15 Feb 2005 10:00:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FI0BB8084492; Tue, 15 Feb 2005 10:00:11 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 10:00:11 -0800 From: "David O'Brien" To: Mark Magiera Message-ID: <20050215180011.GD38158@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215113649.7bfcb1cd.mark@hyow.eu.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 cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 15 Feb 2005 18:00:13 -0000 On Tue, Feb 15, 2005 at 11:36:49AM +0000, Mark Magiera wrote: > On Tue, 8 Feb 2005 19:33:38 +0000 > Mark Magiera wrote: > > The thing I'm unsure about is, how well are the nforce4 chipsets > > supported in FreeBSD? and what about PCI-E, would one of those mobo's > > in combination with a PCI-E nvidia card work? .. > > Any advice would be much appreciated .. > Ok, quick update. I finally bought the mobo (Asus A8N-SLi) along with a > 6600GT PCI-E and while there are a few problems, they seem the kind that > can be ironed out over time. Sorry I missed your original email, or I would have warned you. No committer had an AMD PCIe or nVidia nForce4 motherboard until this past weekend. AMD donated 2 motherboards to Scott Long who did the Intel PCIe work. So you're a little ahead of the game right now. The FreeBSD interest and work on PCIe has been for storage and network (e.g. server) devices, not graphics. So I have no idea how well PCIe (much less PCIe-SLi) is supported yet. A donation of a nice PCIe graphics card to Scottl would probably help the effort along. :-))))) > Basically, freebsd installs in both 32 and 64 bit mode but in both > cases, the network card is so unreliable that half way through a cvsup > (or anything else) it dies and nothing (that I know of) but a reboot > fixes it, this is for the "sk" device. What OS version are you running? For the AMD64 platform you really, really need to be tracking RELENG_5, if not 6-CURRENT. 5.3-RELEASE is our first real AMD64 release and of course we're now getting 2 orders of magnitude more testing exposure than when it was only a few developers with AMD64 machines. FreeBSD/AMD64 will get as polished and stable as FreeBSD/i386 over a very short time. If you have sk(4) problems with RELENG_5, please send a PR with complete details and a dmesg.boot from a verbose boot. > As for the other nic (the nforce > one), I didn't look into it much but it seems there's no driver for it > except one possibly (ports/net/nvnet) but since I'm unable to even do a > simple cvsup with the other card, it's not much use. Also the nvnet > driver is for 32bit mode only. Stop supporting nVidia by buying nForce-based motherboards. Or complain to nVidia that they (1) won't give us docs even under NDA, (2) won't provide a FreeBSD driver like they do for Linux. These mailing lists are filled with all the problems of nForce motherboards, yet FreeBSD users keep buying them... -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 18:03:07 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 B07F016A4CE for ; Tue, 15 Feb 2005 18:03:07 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 598B843D5A for ; Tue, 15 Feb 2005 18:03:07 +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 j1FI35Et084662; Tue, 15 Feb 2005 10:03:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FI31s1084659; Tue, 15 Feb 2005 10:03:01 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 10:03:01 -0800 From: "David O'Brien" To: "Xi.Liu" Message-ID: <20050215180301.GE38158@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 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: Can not create slice on a SATA drive 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, 15 Feb 2005 18:03:07 -0000 On Tue, Feb 15, 2005 at 12:47:13PM -0500, Xi.Liu wrote: > I have Dell power edge S420 with only one SATA harddrive running FreeBSD > 5.3-RELEASE for AMD64 platform and the system is running fine. .. > I am trying to create a slice to use the all the rest unused disk space, but > some how I can save the changes using "sysinstall" > (see error messages below) .. > ??ERROR: Unable to write data to disk ad4! ?k Boot single user and try to create the partition. GEOM won't allow writes to a disk after it has been mounted. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 18:09:25 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 32F5B16A4CE for ; Tue, 15 Feb 2005 18:09:25 +0000 (GMT) Received: from mail2.leitch.com (mail2.leitch.com [204.187.61.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id D10EC43D1F for ; Tue, 15 Feb 2005 18:09:24 +0000 (GMT) (envelope-from Xi.Liu@Leitch.com) Received: from pelican.mars.leitch.com (pelican.mars.leitch.com [192.168.233.15]) by mail2.leitch.com (8.12.10/8.12.10) with ESMTP id j1FI9OBN021482 for ; Tue, 15 Feb 2005 13:09:24 -0500 (EST) Received: by pelican.mars.leitch.com with Internet Mail Service (5.5.2657.72) id <1TYH21Y4>; Tue, 15 Feb 2005 13:09:50 -0500 Message-ID: From: "Xi.Liu" To: "'freebsd-amd64@freebsd.org'" Date: Tue, 15 Feb 2005 13:09:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Can not create slice on a SATA drive 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, 15 Feb 2005 18:09:25 -0000 Thanks! Still not very sure, .... (I am new using FreeBSD). I guess even I boot singel user, the disk will still be mounted as /. Do I have to boot from a bootable-CD (say the installation CD)? Xi -----Original Message----- From: David O'Brien [mailto:obrien@freebsd.org] Sent: Tuesday, February 15, 2005 1:03 PM To: Xi.Liu Cc: 'freebsd-amd64@freebsd.org' Subject: Re: Can not create slice on a SATA drive On Tue, Feb 15, 2005 at 12:47:13PM -0500, Xi.Liu wrote: > I have Dell power edge S420 with only one SATA harddrive running FreeBSD > 5.3-RELEASE for AMD64 platform and the system is running fine. .. > I am trying to create a slice to use the all the rest unused disk space, but > some how I can save the changes using "sysinstall" > (see error messages below) .. > ??ERROR: Unable to write data to disk ad4! ?k Boot single user and try to create the partition. GEOM won't allow writes to a disk after it has been mounted. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 18:21:32 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 5DE9A16A4CE for ; Tue, 15 Feb 2005 18:21:32 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F76543D41 for ; Tue, 15 Feb 2005 18:21:32 +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 j1FILVgI085514; Tue, 15 Feb 2005 10:21:31 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FILUs6085513; Tue, 15 Feb 2005 10:21:30 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 10:21:30 -0800 From: "David O'Brien" To: "Xi.Liu" Message-ID: <20050215182130.GA85174@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 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: Can not create slice on a SATA drive 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, 15 Feb 2005 18:21:32 -0000 On Tue, Feb 15, 2005 at 01:09:48PM -0500, Xi.Liu wrote: > Still not very sure, .... (I am new using FreeBSD). [ PLEASE don't top-post, it looses context. ] > I guess even I boot singel user, the disk will still be mounted as /. Correct. / will be mount read-only. > Do I have to boot from a bootable-CD (say the installation CD)? Nope, you can use /usr/sbin/sysinstall. But you'll have to mount /usr (but do it read-only!) first if you didn't combine / + /usr into a single partition. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 19:11:46 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 B3A4216A4CE; Tue, 15 Feb 2005 19:11:46 +0000 (GMT) Received: from mail.takas.lt (mail-src.takas.lt [212.59.31.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88C5D43D1F; Tue, 15 Feb 2005 19:11:45 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from mail pickup service by mail.takas.lt with Microsoft SMTPSVC; Tue, 15 Feb 2005 21:11:15 +0200 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.takas.lt with Microsoft SMTPSVC(5.0.2195.6713); Tue, 15 Feb 2005 16:58:14 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id B4368569B1; Tue, 15 Feb 2005 14:57:46 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 82E3516A4D8; Tue, 15 Feb 2005 14:57:44 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE45916A4CE for ; Tue, 15 Feb 2005 14:57:35 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7363E43D55 for ; Tue, 15 Feb 2005 14:57:34 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so800817wra for ; Tue, 15 Feb 2005 06:57:33 -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=TgdEo3qqB0qGpsSmpV00WI6iAn2ZhSB2ZZWNpH8JhKuz5gySDL8p6U3XSmD51xSv969ZUMHe/8dCOufehmetMO7tNExxQp8sZ2FsJmTIrrqosn4OHH0ysSA85kSHI9RAL6WKCUKC+TDjO0Lnwn63057JSj2iIgQxuJOMgh87yIw= Received: by 10.54.23.34 with SMTP id 34mr184801wrw; Tue, 15 Feb 2005 06:57:33 -0800 (PST) Received: by 10.54.7.6 with HTTP; Tue, 15 Feb 2005 06:57:33 -0800 (PST) Message-ID: <6eb82e050215065762c63576@mail.gmail.com> Date: Tue, 15 Feb 2005 22:57:33 +0800 From: Rong-En Fan To: amd64@freebsd.org, stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-OriginalArrivalTime: 15 Feb 2005 14:58:14.0609 (UTC) FILETIME=[C669F410:01C5136E] Subject: panic: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-amd64@freebsd.org Reply-To: Rong-En Fan List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 19:11:46 -0000 Hello, This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM and a LSI 21320 rmpt(4) running at 160MB/s with a hardware RAID (da0, da1). HTT is enabled. When I run benchmark/blogbench on /da0/ I can *reproduce* this panic again and again: (I'm getting a dump now, let me fsck first) kernel conf & dmesg (boot -v) are at http://rafan.infor.org/tmp/236/ any suggestions are welcome. :) Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x88 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff80235b0b stack pointer = 0x10:0xffffffffb1bd5a50 frame pointer = 0x10:0xffffffffb1bd5a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 96 (pagedaemon) [thread 100114] Stopped at thread_fini+0xab: subl 0x88(%ebx),%eax db> trace thread_fini() at thread_fini+0xab zone_drain() at zone_drain+0x22d zone_foreach() at zone_foreach+0x76 uma_reclaim() at uma_reclaim+0x15 vm_pageout_scan() at vm_pageout_scan+0x170 vm_pageout() at vm_pageout+0x38e fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb1bd5d00, rbp = 0 --- db> ps pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd 615 ffffff00603348b8 ffffffffb43b5000 0 568 615 000c082 (threaded) blogbench thread 0xffffff001e7ef000 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff000881fa40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d19c40][SLP] thread 0xffffff001c25d520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d37640][SLP] thread 0xffffff000881fcd0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff001ffa27b0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff001b755520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a373640][SLP] thread 0xffffff0070700a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2d8b40][SLP] thread 0xffffff002c333cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f1c140][SLP] thread 0xffffff00462e0520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a104e40][SLP] thread 0xffffff0011002a40 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff0059594c80][SLP] thread 0xffffff006310f7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a237740][SLP] thread 0xffffff003c731520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff00087c1500][SLP] thread 0xffffff0033c33290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ee8e40][SLP] thread 0xffffff00635a7290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d86840][SLP] thread 0xffffff006ff7ccd0 ksegrp 0xffffff007b1fb4d0 [RUNQ] thread 0xffffff000881f520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99fbb440][SLP] thread 0xffffff006eff2520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99a01640][SLP] thread 0xffffff004d176520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a069140][SLP] thread 0xffffff0048ded520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f9c540][SLP] thread 0xffffff003689f7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d7c940][SLP] thread 0xffffff0052446cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99f22d40][SLP] thread 0xffffff006eff2000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99a6c140][SLP] thread 0xffffff0054121cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff0059112500][SLP] thread 0xffffff00492bc000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a315440][SLP] thread 0xffffff003289ba40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ff1d40][SLP] thread 0xffffff0055b3ea40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99fe2140][SLP] thread 0xffffff0055b3e000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff999d1340][SLP] thread 0xffffff003689f290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2bc040][SLP] thread 0xffffff000881f000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99bc8440][SLP] thread 0xffffff006ff7c000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99c2ed40][SLP] thread 0xffffff003289b000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a0c0a40][SLP] thread 0xffffff003c731a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99c9ec40][SLP] thread 0xffffff0009f50cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99b1c240][SLP] thread 0xffffff000dbd5cd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a1fff40][SLP] thread 0xffffff003c9bdcd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99d06440][SLP] thread 0xffffff003c9bd7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a202c40][SLP] thread 0xffffff006ac1ba40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a30c740][SLP] thread 0xffffff00342f4290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a00ee40][SLP] thread 0xffffff004819d290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99dc3440][SLP] thread 0xffffff005cd927b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99b6ed40][SLP] thread 0xffffff00462e0290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a25ff40][SLP] thread 0xffffff0033047290 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a2d1040][SLP] thread 0xffffff00312cf520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a13e440][SLP] thread 0xffffff00640bf000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a1dfb40][SLP] thread 0xffffff003289b7b0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a144440][SLP] thread 0xffffff0060817a40 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff999c3840][SLP] thread 0xffffff00083a8520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005dbd5140][SLP] thread 0xffffff0049a4ccd0 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99ac3740][SLP] thread 0xffffff0025fc4520 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99e8d040][SLP] thread 0xffffff002a956000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff99af9740][SLP] thread 0xffffff007821f520 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005b19ec80][SLP] thread 0xffffff0039650000 ksegrp 0xffffff007b1fb4d0 [SLPQ ufs 0xffffff005b19ec80][SLP] thread 0xffffff00635a7000 ksegrp 0xffffff007b1fb4d0 [SLPQ biord 0xffffffff9a376940][SLP] thread 0xffffff006ac1b290 ksegrp 0xffffff007b7b7b00 [SLPQ ksesigwait 0xffffff0060334a68][SLP] 568 ffffff0062a255d0 ffffffffb426a000 0 567 568 0004002 [SLPQ pause 0xffffff0062a25640][SLP] csh 567 ffffff005fc94000 ffffffffb43c1000 0 1 567 0004102 [SLPQ wait 0xffffff005fc94000][SLP] login 566 ffffff0060a3a5d0 ffffffffb43b9000 0 1 566 0004002 [SLPQ ttyin 0xffffff007b348410][SLP] getty 565 ffffff0062a26ba0 ffffffffb4271000 0 1 565 0004002 [SLPQ ttyin 0xffffff007b348810][SLP] getty 564 ffffff0062a792e8 ffffffffb434a000 0 1 564 0004002 [SLPQ ttyin 0xffffff007b348c10][SLP] getty 563 ffffff00609bbba0 ffffffffb43c0000 0 1 563 0004002 [SLPQ ttyin 0xffffff007af69010][SLP] getty 562 ffffff00609bb5d0 ffffffffb43be000 0 1 562 0004002 [SLPQ ttyin 0xffffff007af69410][SLP] getty 561 ffffff007b2b7ba0 ffffffffb4195000 0 1 561 0004002 [SLPQ ttyin 0xffffff0000a35810][SLP] getty 560 ffffff0062bc0000 ffffffffb419b000 0 1 560 0004002 [SLPQ ttyin 0xffffff007af2c810][SLP] getty 555 ffffff0060a3aba0 ffffffffb43bb000 0 1 555 0000000 [SLPQ select 0xffffffff8052fb70][SLP] inetd 526 ffffff00600fc000 ffffffffb443e000 0 1 525 0000000 [SLPQ select 0xffffffff8052fb70][SLP] snmpd 507 ffffff006013d8b8 ffffffffb4446000 0 1 507 0000000 [SLPQ nanslp 0xffffffff80527440][SLP] cron 495 ffffff0062a628b8 ffffffffb4266000 25 1 495 0000100 [SLPQ pause 0xffffff0062a62928][SLP] sendmail 491 ffffff0060334000 ffffffffb4358000 0 1 491 0000100 [SLPQ select 0xffffffff8052fb70][SLP] sendmail 485 ffffff00602132e8 ffffffffb4354000 0 1 485 0000100 [SLPQ select 0xffffffff8052fb70][SLP] sshd 471 ffffff007b295ba0 ffffffffb414f000 0 1 471 0000000 [SLPQ select 0xffffffff8052fb70][SLP] ntpd 435 ffffff0062a625d0 ffffffffb4265000 0 429 429 0000100 [SLPQ select 0xffffffff8052fb70][SLP] rpc.lockd 429 ffffff007b2b72e8 ffffffffb4192000 0 1 429 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpc.lockd 424 ffffff0062c085d0 ffffffffb4201000 0 1 424 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpc.statd 418 ffffff0062a5d8b8 ffffffffb4261000 0 414 414 0000000 [SLPQ - 0xffffff000d749800][SLP] nfsd 417 ffffff007b2da2e8 ffffffffb4197000 0 414 414 0000000 [SLPQ - 0xffffff000dc11c00][SLP] nfsd 416 ffffff0062c08ba0 ffffffffb4203000 0 414 414 0000000 [SLPQ - 0xffffff0062b0e400][SLP] nfsd 415 ffffff0062a5dba0 ffffffffb4262000 0 414 414 0000000 [SLPQ - 0xffffff000dc11a00][SLP] nfsd 414 ffffff007b2952e8 ffffffffb414c000 0 1 414 0000000 [SLPQ accept 0xffffff00617596d6][SLP] nfsd 406 ffffff007b2b78b8 ffffffffb4194000 0 1 406 0000000 [SLPQ select 0xffffffff8052fb70][SLP] mountd 354 ffffff007b2daba0 ffffffffb419a000 0 1 354 0000000 [SLPQ select 0xffffffff8052fb70][SLP] rpcbind 341 ffffff0062a622e8 ffffffffb4264000 0 1 341 0000000 [SLPQ select 0xffffffff8052fb70][SLP] syslogd 321 ffffff0062a26000 ffffffffb426d000 0 1 321 0000000 [SLPQ select 0xffffffff8052fb70][SLP] devd 245 ffffff0062bc0ba0 ffffffffb41f9000 0 1 245 0000000 [SLPQ pause 0xffffff0062bc0c10][SLP] adjkerntz 106 ffffff007b2da000 ffffffffb4196000 0 0 0 0000204 [SLPQ - 0xffffffffb4173c0c][SLP] schedcpu 105 ffffff007b796000 ffffffffb1b8b000 0 0 0 0000204 [SLPQ - 0xffffffff805344d8][SLP] nfsiod 3 104 ffffff007b7962e8 ffffffffb1b8c000 0 0 0 0000204 [SLPQ - 0xffffffff805344d0][SLP] nfsiod 2 103 ffffff007b7965d0 ffffffffb1b8d000 0 0 0 0000204 [SLPQ - 0xffffffff805344c8][SLP] nfsiod 1 102 ffffff007b7968b8 ffffffffb1b8e000 0 0 0 0000204 [SLPQ - 0xffffffff805344c0][SLP] nfsiod 0 101 ffffff007b796ba0 ffffffffb1b8f000 0 0 0 0000204 [SLPQ syncer 0xffffffff80527120][SLP] syncer 100 ffffff007b7d8000 ffffffffb1b90000 0 0 0 0000204 [SLPQ vlruwt 0xffffff007b7d8000][SLP] vnlru 99 ffffff007b7d82e8 ffffffffb1b91000 0 0 0 0000204 [SLPQ wdrain 0xffffffff805304e8][SLP] bufdaemon 98 ffffff007b7d85d0 ffffffffb1b92000 0 0 0 000020c [SLPQ pgzero 0xffffffff8053ce74][SLP] pagezero 97 ffffff007b7d88b8 ffffffffb1b93000 0 0 0 0000204 [SLPQ psleep 0xffffffff8053cedc][SLP] vmdaemon 96 ffffff007b7d8ba0 ffffffffb1b94000 0 0 0 0000204 [CPU 2] pagedaemon 95 ffffff007b7bd000 ffffffffb1bef000 0 0 0 0000204 [IWAIT] swi0: sio 9 ffffff007b7bd2e8 ffffffffb1bf0000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task2 8 ffffff007b7bd5d0 ffffffffb1bf1000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task1 7 ffffff007b7bd8b8 ffffffffb1bf2000 0 0 0 0000204 [SLPQ actask 0xffffffff8051a000][SLP] acpi_task0 94 ffffff007b7bdba0 ffffffffb1bf3000 0 0 0 0000204 [IWAIT] swi6: acpitaskq 6 ffffff007b7472e8 ffffffffb1b23000 0 0 0 0000204 [SLPQ - 0xffffff00009d1100][SLP] kqueue taskq 93 ffffff007b7475d0 ffffffffb1b24000 0 0 0 0000204 [IWAIT] swi6:+ 5 ffffff007b7478b8 ffffffffb1b25000 0 0 0 0000204 [SLPQ - 0xffffff00009d1280][SLP] thread taskq 92 ffffff007b747ba0 ffffffffb1b26000 0 0 0 0000204 [IWAIT] swi6:+ 91 ffffff007b775000 ffffffffb1b27000 0 0 0 0000204 [IWAIT] swi6: task queue 90 ffffff007b7752e8 ffffffffb1b28000 0 0 0 0000204 [IWAIT] swi3: cambio 89 ffffff007b7755d0 ffffffffb1b29000 0 0 0 0000204 [IWAIT] swi2: camnet 88 ffffff007b7758b8 ffffffffb1b2a000 0 0 0 0000204 [SLPQ - 0xffffffff8051a720][SLP] yarrow 4 ffffff007b775ba0 ffffffffb1b2b000 0 0 0 0000204 [CPU 0] g_down 3 ffffff007b7f9000 ffffffffb1b86000 0 0 0 0000204 [CPU 3] g_up 2 ffffff007b7f92e8 ffffffffb1b87000 0 0 0 0000204 [SLPQ - 0xffffffff8051e490][SLP] g_event 87 ffffff007b7f95d0 ffffffffb1b88000 0 0 0 0000204 [IWAIT] swi1: net 86 ffffff007b7f98b8 ffffffffb1b89000 0 0 0 0000204 [IWAIT] swi4: vm 85 ffffff007b7f9ba0 ffffffffb1b8a000 0 0 0 000020c [RUNQ] swi5: clock sio 84 ffffff007b7518b8 ffffffffb1ada000 0 0 0 0000204 [IWAIT] irq23: 83 ffffff007b751ba0 ffffffffb1adb000 0 0 0 0000204 [IWAIT] irq22: 82 ffffff007b761000 ffffffffb1adc000 0 0 0 0000204 [IWAIT] irq21: 81 ffffff007b7612e8 ffffffffb1add000 0 0 0 0000204 [IWAIT] irq20: 80 ffffff007b7615d0 ffffffffb1ade000 0 0 0 0000204 [IWAIT] irq19: 79 ffffff007b7618b8 ffffffffb1adf000 0 0 0 0000204 [IWAIT] irq18: 78 ffffff007b761ba0 ffffffffb1ae0000 0 0 0 0000204 [IWAIT] irq17: 77 ffffff007b763000 ffffffffb1ae1000 0 0 0 0000204 [RUNQ] irq16: bge0 bge1 76 ffffff007b7632e8 ffffffffb1b1e000 0 0 0 0000204 [IWAIT] irq15: ata1 75 ffffff007b7635d0 ffffffffb1b1f000 0 0 0 0000204 [IWAIT] irq14: ata0 74 ffffff007b7638b8 ffffffffb1b20000 0 0 0 0000204 [IWAIT] irq13: 73 ffffff007b763ba0 ffffffffb1b21000 0 0 0 0000204 [IWAIT] irq12: 72 ffffff007b747000 ffffffffb1b22000 0 0 0 0000204 [IWAIT] irq11: 71 ffffff007b7d62e8 ffffffffb1a92000 0 0 0 0000204 [IWAIT] irq10: 70 ffffff007b7d65d0 ffffffffb1a93000 0 0 0 0000204 [IWAIT] irq9: acpi0 69 ffffff007b7d68b8 ffffffffb1a94000 0 0 0 0000204 [IWAIT] irq8: rtc 68 ffffff007b7d6ba0 ffffffffb1a95000 0 0 0 0000204 [IWAIT] irq7: 67 ffffff007b74e000 ffffffffb1a96000 0 0 0 0000204 [IWAIT] irq6: 66 ffffff007b74e2e8 ffffffffb1a97000 0 0 0 0000204 [IWAIT] irq5: 65 ffffff007b74e5d0 ffffffffb1a98000 0 0 0 0000204 [IWAIT] irq4: sio0 64 ffffff007b74e8b8 ffffffffb1ad5000 0 0 0 0000204 [IWAIT] irq3: sio1 63 ffffff007b74eba0 ffffffffb1ad6000 0 0 0 0000204 [IWAIT] irq0: clk 62 ffffff007b751000 ffffffffb1ad7000 0 0 0 0000204 [IWAIT] irq1: atkbd0 61 ffffff007b7512e8 ffffffffb1ad8000 0 0 0 0000204 [IWAIT] irq47: 60 ffffff007b7515d0 ffffffffb1ad9000 0 0 0 0000204 [IWAIT] irq46: 59 ffffff007b770000 ffffffffb1a4b000 0 0 0 0000204 [IWAIT] irq45: 58 ffffff007b7702e8 ffffffffb1a4c000 0 0 0 0000204 [IWAIT] irq44: 57 ffffff007b7705d0 ffffffffb1a4d000 0 0 0 0000204 [IWAIT] irq43: 56 ffffff007b7708b8 ffffffffb1a4e000 0 0 0 0000204 [IWAIT] irq42: 55 ffffff007b770ba0 ffffffffb1a4f000 0 0 0 0000204 [IWAIT] irq41: 54 ffffff007b771000 ffffffffb1a50000 0 0 0 0000204 [IWAIT] irq40: 53 ffffff007b7712e8 ffffffffb1a8d000 0 0 0 0000204 [IWAIT] irq39: 52 ffffff007b7715d0 ffffffffb1a8e000 0 0 0 0000204 [IWAIT] irq38: ips0 51 ffffff007b7718b8 ffffffffb1a8f000 0 0 0 0000204 [IWAIT] irq37: 50 ffffff007b771ba0 ffffffffb1a90000 0 0 0 0000204 [IWAIT] irq36: 49 ffffff007b7d6000 ffffffffb1a91000 0 0 0 0000204 [IWAIT] irq35: 48 ffffff007b780000 ffffffffb1a05000 0 0 0 0000204 [IWAIT] irq34: 47 ffffff007b7802e8 ffffffffb1a06000 0 0 0 0000204 [IWAIT] irq33: 46 ffffff007b7805d0 ffffffffb1a07000 0 0 0 0000204 [IWAIT] irq32: 45 ffffff007b7808b8 ffffffffb1a08000 0 0 0 0000204 [IWAIT] irq31: 44 ffffff007b780ba0 ffffffffb1a09000 0 0 0 0000204 [IWAIT] irq30: 43 ffffff007b783000 ffffffffb1a46000 0 0 0 0000204 [IWAIT] irq29: 42 ffffff007b7832e8 ffffffffb1a47000 0 0 0 0000204 [IWAIT] irq28: 41 ffffff007b7835d0 ffffffffb1a48000 0 0 0 0000204 [IWAIT] irq27: 40 ffffff007b7838b8 ffffffffb1a49000 0 0 0 0000204 [IWAIT] irq26: 39 ffffff007b783ba0 ffffffffb1a4a000 0 0 0 0000204 [IWAIT] irq25: 38 ffffff007b7662e8 ffffffffb19c0000 0 0 0 0000204 [IWAIT] irq24: 37 ffffff007b7665d0 ffffffffb19c1000 0 0 0 0000204 [IWAIT] irq71: 36 ffffff007b7668b8 ffffffffb19c2000 0 0 0 0000204 [IWAIT] irq70: 35 ffffff007b766ba0 ffffffffb19c3000 0 0 0 0000204 [IWAIT] irq69: 34 ffffff007b7b5000 ffffffffb1a00000 0 0 0 0000204 [IWAIT] irq68: 33 ffffff007b7b52e8 ffffffffb1a01000 0 0 0 0000204 [IWAIT] irq67: 32 ffffff007b7b55d0 ffffffffb1a02000 0 0 0 0000204 [IWAIT] irq66: 31 ffffff007b7b58b8 ffffffffb1a03000 0 0 0 0000204 [IWAIT] irq65: 30 ffffff007b7b5ba0 ffffffffb1a04000 0 0 0 0000204 [IWAIT] irq64: 29 ffffff007b7dc8b8 ffffffffb199a000 0 0 0 0000204 [IWAIT] irq63: 28 ffffff007b7dcba0 ffffffffb199b000 0 0 0 0000204 [IWAIT] irq62: 27 ffffff007b784000 ffffffffb199c000 0 0 0 0000204 [IWAIT] irq61: 26 ffffff007b7842e8 ffffffffb19bb000 0 0 0 0000204 [IWAIT] irq60: 25 ffffff007b7845d0 ffffffffb19bc000 0 0 0 0000204 [IWAIT] irq59: 24 ffffff007b7848b8 ffffffffb19bd000 0 0 0 0000204 [IWAIT] irq58: 23 ffffff007b784ba0 ffffffffb19be000 0 0 0 0000204 [IWAIT] irq57: 22 ffffff007b766000 ffffffffb19bf000 0 0 0 0000204 [IWAIT] irq56: 21 ffffff007b7d42e8 ffffffffb1975000 0 0 0 0000204 [IWAIT] irq55: 20 ffffff007b7d45d0 ffffffffb1976000 0 0 0 0000204 [IWAIT] irq54: 19 ffffff007b7d48b8 ffffffffb1995000 0 0 0 0000204 [IWAIT] irq53: mpt1 18 ffffff007b7d4ba0 ffffffffb1996000 0 0 0 0000204 [CPU 1] irq52: mpt0 17 ffffff007b7dc000 ffffffffb1997000 0 0 0 0000204 [IWAIT] irq51: 16 ffffff007b7dc2e8 ffffffffb1998000 0 0 0 0000204 [IWAIT] irq50: 15 ffffff007b7dc5d0 ffffffffb1999000 0 0 0 0000204 [IWAIT] irq49: 14 ffffff007b76d000 ffffffffb1933000 0 0 0 0000204 [IWAIT] irq48: 13 ffffff007b76d2e8 ffffffffb1970000 0 0 0 000020c [Can run] idle: cpu0 12 ffffff007b76d5d0 ffffffffb1971000 0 0 0 000020c [Can run] idle: cpu1 11 ffffff007b76d8b8 ffffffffb1972000 0 0 0 000020c [Can run] idle: cpu2 10 ffffff007b76dba0 ffffffffb1973000 0 0 0 000020c [Can run] idle: cpu3 1 ffffff007b7d4000 ffffffffb1974000 0 0 1 0004200 [SLPQ wait 0xffffff007b7d4000][SLP] init 0 ffffffff8051e580 ffffffff805f5000 0 0 0 0000200 [SLPQ sched 0xffffffff8051e580][SLP] swapper Regards, Rong-En Fan _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 19:55: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 3DB8016A4CF for ; Tue, 15 Feb 2005 19:55:17 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF0343D66 for ; Tue, 15 Feb 2005 19:55:16 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FJtERB028639 for ; Tue, 15 Feb 2005 21:55:14 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 70229-03 for ; Tue, 15 Feb 2005 21:55:13 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FJtDrY028636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Feb 2005 21:55:13 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1FJtIKC017982 for freebsd-amd64@freebsd.org; Tue, 15 Feb 2005 21:55:18 +0200 (EET) (envelope-from ru) Date: Tue, 15 Feb 2005 21:55:17 +0200 From: Ruslan Ermilov To: freebsd-amd64@freebsd.org Message-ID: <20050215195517.GA17904@ip.net.ua> References: <20050215141155.GA29160@gattaca.yadt.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: <20050215141155.GA29160@gattaca.yadt.co.uk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua Subject: Re: Cross compiling for i386 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, 15 Feb 2005 19:55:17 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > I've recently purchased an AMD Athlon 64 3500+ with an MSI K8T Neo2 > motherboard, and FreeBSD seems to work quite well with it. Other than th= e=20 > re0 NIC's problems with hardware checksumming for UDP. Also I can't > get make build32 to complete without compiler errors, but that's not > critical for now. >=20 > On to the main point of this e-mail: >=20 > I also have an i386 workstation, which is significantly slower at building > world. I tried to cross-build the world on the amd64 box, then install it > over an NFS mount. Eventually, I managed to persuade it to build and > install, but it's not really a process I'd like to repeat every time I > update... >=20 > I managed to eventually complete a single build/install world cycle by do= ing > something like: >=20 > $ cd /usr/src; make buildworld TARGET_ARCH=3Di386 > $ mount :/usr/src /usr/src > $ mount :/usr/obj /usr/obj > $ make installworld >=20 > This however had a few problems. Running installworld caused the i386 box > to attempt to write to /usr/src, due to newvers.sh, so I needed to mount > /usr/src rw. Also the built objects appeared to be in /usr/obj/i386, whi= lst > installworld was looking at /usr/obj. >=20 > Then, installworld wanted i386 tools to install with, so I ended up trying >=20 > make _worldtmp _legacy _bootstrap-tools _build-tools _cross-tools >=20 > I'm not sure they were _all_ required, but eventually it completed a > installworld. But not before I did manually copied ls and dd into > $INSTALLTMP. btxld also failed to compile for some reason (i.e. it wasn't > built, no errors) worked correctly when manually built. >=20 > The only problem I had with the resulting world was the installed locales > in /usr/share/locale/ were invalid (32 vs 64 bit field somewhere?), and > fortune coredumped when ran. That was fixed easily enough by recompiling > libc and fortune on the i386 box. >=20 > Is this supposed to be possible/supported? And does anyone have any ideas > how to make it work more automatically? >=20 No, this is not supported at all. What's supported is mounting i386's /, /usr, and /var onto /mnt, /mnt/usr, and /mnt/var, and doing the installworld with DESTDIR=3D/mnt from amd64. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCElOlqRfpzJluFF4RAt3+AJ97oUfSbZ9PRHtQh28g0XLi2ZOVbACeKDMe uhHtK5U62kWzlrxeq3FPEKg= =3YXx -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 19:56:37 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 76CC416A4CE; Tue, 15 Feb 2005 19:56:37 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9557B43D1D; Tue, 15 Feb 2005 19:56:36 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FJuZlQ028719; Tue, 15 Feb 2005 21:56:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 70141-12; Tue, 15 Feb 2005 21:56:35 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FJuZbu028716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2005 21:56:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1FJudAC017998; Tue, 15 Feb 2005 21:56:39 +0200 (EET) (envelope-from ru) Date: Tue, 15 Feb 2005 21:56:39 +0200 From: Ruslan Ermilov To: "David O'Brien" Message-ID: <20050215195639.GB17904@ip.net.ua> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215170716.GB38158@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aM3YZ0Iwxop3KEKx" Content-Disposition: inline In-Reply-To: <20050215170716.GB38158@dragon.nuxi.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@FreeBSD.org Subject: Re: Cross compiling for i386 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, 15 Feb 2005 19:56:37 -0000 --aM3YZ0Iwxop3KEKx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 09:07:16AM -0800, David O'Brien wrote: > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > I also have an i386 workstation, which is significantly slower at build= ing > > world. I tried to cross-build the world on the amd64 box, then install= it > > over an NFS mount. >=20 > To date we've never guaranteed that a cross-arch built world is usable. > We only officially support cross-arch compiles for compile testing. There > are other things in the tree that aren't size & endian-clean that prevent > usable cross-arch release builds. >=20 > Many (?most?) of the result from a cross-arch 'make buildworld' are > usable on the target arch; but small nuances cause the total of the > result to not really be usable. >=20 I'm working on this. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --aM3YZ0Iwxop3KEKx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCElP3qRfpzJluFF4RAkIwAJ9ZOmn/24tP+lEaokgt6ok6J9ip9wCfczKe U9GRbGMRI8BYT95Pjhgl/d4= =ngo6 -----END PGP SIGNATURE----- --aM3YZ0Iwxop3KEKx-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 20:00:51 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 4B5AA16A4E3; Tue, 15 Feb 2005 20:00:51 +0000 (GMT) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.43.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05D0D43D48; Tue, 15 Feb 2005 20:00:51 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id 3A31458866; Tue, 15 Feb 2005 12:00:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by groat.ugcs.caltech.edu (Postfix) with ESMTP id 0AA2218001; Tue, 15 Feb 2005 12:00:50 -0800 (PST) Date: Tue, 15 Feb 2005 12:00:49 -0800 (PST) From: Jon Dama To: Alan Jay In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard 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, 15 Feb 2005 20:00:51 -0000 I concur that the situation got much better with 5.3-Stable. What I experienced afterward occurred only under load. -Jonathan On Tue, 15 Feb 2005, Alan Jay wrote: > > -----Original Message----- > > On Tue, Feb 15, 2005 at 04:53:24PM -0000, Alan Jay wrote: > > > I had major problems installing with more than 4Gb but once I moved to > > stable > > > we seemed to have a stable platform when doing basic stuff - we have two > > > databases (mySQL) one is reasonably heavily used and one very extensively > > > used. > > > > Just to be clear, you're stating you had stability problems with > > 5.3-RELEASE and >4GB. But with 5.3-STABLE and >4GB you have a stable > > system. Correct? > > [Alan Jay] I could not install with RELEASE but could with Stable. > > Once installed and running we installed mySQL on the two machines one we > copied over a relatively simple database which ran fine without a problem. > > The second machine then had another mySQL database moved to it and it started > to fall over. After a number of tests we moved the first database off the > what had been working server and put the other database on it. At which point > that server which had been stable fell over! > > > > I think I agree wholeheartedly with your comments being a great supporter > > of > > > FreeBSD it is a shame that the AMD release is not as super as the other > > > versions we have used extensively. > > > > The problem is a major bug that has existed since FreeBSD ?3.0? was > > exposed very close to the 5.3 release cycle. This bug only causes a > > major problem with >4GB, thus few of us developers experienced it. > > [Most of us can't afford >4GB in our machines. Donations of 1GB DIMMs > > for FreeBSD developers are accepted by donations@FreeBSD.org.] > > [Alan Jay] I'll put them on my present list :) > > > Of course one reason many are moving to the AMD64 platform is to have > > >4GB RAM in the machine. We believe this bug has been fixed in > > 5.3-STABLE. But too few people are testing 5.3-STABLE and are using > > 5.3-RELEASE instead. This isn't helping us QA the issue so that we know > > all the corner cases are fixed in upcoming 5.4 release. > > [Alan Jay] Well the memory seemed to be stable on 5.3 STABLE with more than > 4Gb in our case 8Gb there seems to be some other problem at work here. > > > A recent 5.3-STABLE snapshot can be found as > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001- > > amd64-miniinst.iso > > and mirrors. > > > > -- > > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 20:03:00 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 BB02016A4CE; Tue, 15 Feb 2005 20:03:00 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82ED643D49; Tue, 15 Feb 2005 20:03:00 +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 j1FK30mY089726; Tue, 15 Feb 2005 12:03:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FK3056089725; Tue, 15 Feb 2005 12:03:00 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 12:03:00 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20050215200300.GC89396@dragon.nuxi.com> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215170716.GB38158@dragon.nuxi.com> <20050215195639.GB17904@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215195639.GB17904@ip.net.ua> 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: Cross compiling for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 20:03:00 -0000 On Tue, Feb 15, 2005 at 09:56:39PM +0200, Ruslan Ermilov wrote: > On Tue, Feb 15, 2005 at 09:07:16AM -0800, David O'Brien wrote: > > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > > I also have an i386 workstation, which is significantly slower at building > > > world. I tried to cross-build the world on the amd64 box, then install it > > > over an NFS mount. > > > > To date we've never guaranteed that a cross-arch built world is usable. > > We only officially support cross-arch compiles for compile testing. There > > are other things in the tree that aren't size & endian-clean that prevent > > usable cross-arch release builds. > > > > Many (?most?) of the result from a cross-arch 'make buildworld' are > > usable on the target arch; but small nuances cause the total of the > > result to not really be usable. > > > I'm working on this. I know. But currently this still falls into "Provisionally Supported". It would be nice if it fully worked. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 20:14: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 5734116A4CE; Tue, 15 Feb 2005 20:14:56 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 348D643D2F; Tue, 15 Feb 2005 20:14:55 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FKEs0f030694; Tue, 15 Feb 2005 22:14:54 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 71194-15; Tue, 15 Feb 2005 22:14:48 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1FKCLxg030446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2005 22:12:21 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1FKCQMV018131; Tue, 15 Feb 2005 22:12:26 +0200 (EET) (envelope-from ru) Date: Tue, 15 Feb 2005 22:12:25 +0200 From: Ruslan Ermilov To: "David O'Brien" Message-ID: <20050215201225.GC17904@ip.net.ua> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215170716.GB38158@dragon.nuxi.com> <20050215195639.GB17904@ip.net.ua> <20050215200300.GC89396@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sr1nOIr3CvdE5hEN" Content-Disposition: inline In-Reply-To: <20050215200300.GC89396@dragon.nuxi.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@freebsd.org Subject: Re: Cross compiling for i386 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, 15 Feb 2005 20:14:56 -0000 --Sr1nOIr3CvdE5hEN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 12:03:00PM -0800, David O'Brien wrote: > On Tue, Feb 15, 2005 at 09:56:39PM +0200, Ruslan Ermilov wrote: > > On Tue, Feb 15, 2005 at 09:07:16AM -0800, David O'Brien wrote: > > > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > > > I also have an i386 workstation, which is significantly slower at b= uilding > > > > world. I tried to cross-build the world on the amd64 box, then ins= tall it > > > > over an NFS mount. > > >=20 > > > To date we've never guaranteed that a cross-arch built world is usabl= e. > > > We only officially support cross-arch compiles for compile testing. = There > > > are other things in the tree that aren't size & endian-clean that pre= vent > > > usable cross-arch release builds. > > >=20 > > > Many (?most?) of the result from a cross-arch 'make buildworld' are > > > usable on the target arch; but small nuances cause the total of the > > > result to not really be usable. > > >=20 > > I'm working on this. >=20 > I know. But currently this still falls into "Provisionally Supported". > It would be nice if it fully worked. > =20 Sure. amd64 <-> i386 is my first target. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Sr1nOIr3CvdE5hEN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCElepqRfpzJluFF4RAv2PAJ46+pbYxN2xm4zr+8UtqqTcKi8HMgCglkdq TigpsyMP5Xqy8VKmacQsq6w= =QBCS -----END PGP SIGNATURE----- --Sr1nOIr3CvdE5hEN-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 21:47:25 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 BACD816A4CE for ; Tue, 15 Feb 2005 21:47:25 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3AE43D31 for ; Tue, 15 Feb 2005 21:47:24 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (8.13.1/8.13.1) with ESMTP id j1FLlLui091967; Tue, 15 Feb 2005 22:47:22 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <42126DED.6080501@withagen.nl> Date: Tue, 15 Feb 2005 22:47:25 +0100 From: Willem Jan Withagen User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050215182130.GA85174@dragon.nuxi.com> In-Reply-To: <20050215182130.GA85174@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: "Xi.Liu" Subject: Re: Can not create slice on a SATA drive 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, 15 Feb 2005 21:47:25 -0000 David O'Brien wrote: > On Tue, Feb 15, 2005 at 01:09:48PM -0500, Xi.Liu wrote: > >>Still not very sure, .... (I am new using FreeBSD). >>I guess even I boot singel user, the disk will still be mounted as /. > > > Correct. / will be mount read-only. > > >>Do I have to boot from a bootable-CD (say the installation CD)? > > > Nope, you can use /usr/sbin/sysinstall. > But you'll have to mount /usr (but do it read-only!) first if you didn't > combine / + /usr into a single partition. I'm always using the 'cheat' option: sysctl -w kern.geom.debugflags=16 Not shure if it is without ill effects. --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 22:00: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 E11D416A4D3 for ; Tue, 15 Feb 2005 22:00:01 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C0543D46 for ; Tue, 15 Feb 2005 22:00:01 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IBZ0054J3RI74@VL-MO-MR007.ip.videotron.ca> for freebsd-amd64@freebsd.org; Tue, 15 Feb 2005 16:59:42 -0500 (EST) Date: Tue, 15 Feb 2005 16:59:41 -0500 From: Nicolas Blais In-reply-to: <200502141722.10259.jhb@FreeBSD.org> To: freebsd-amd64@freebsd.org Message-id: <200502151659.42594.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <200502141722.10259.jhb@FreeBSD.org> Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 15 Feb 2005 22:00:41 -0000 Hi, Thanks for the patch. Will this be MFC into -STABLE? Nicolas. On February 14, 2005 17:22, John Baldwin wrote: > I've tweaked Jung-uk Kim's patches to be driven by a single ACPI quirk > rather than multiple hints. I've included the patch below. If the quirk > is not automatically detected on your laptop, you can manually set it from > the loader via 'set debug.acpi.quirks=4'. If you have to manually set the > quirk to get it to work, please let me know and include the FADT header > from your acpidump in your reply, thanks. > > --- //depot/vendor/freebsd/src/sys/amd64/acpica/madt.c 2004/06/10 21:30:51 > +++ //depot/user/jhb/acpipci/amd64/acpica/madt.c 2005/02/14 22:18:55 > @@ -367,7 +367,7 @@ > } > > /* First, we run through adding I/O APIC's. */ > - if (madt->PCATCompat) > + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) > ioapic_enable_mixed_mode(); > madt_walk_table(madt_parse_apics, NULL); > > @@ -596,8 +596,14 @@ > enum intr_polarity pol; > char buf[64]; > > + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && > + intr->Interrupt == 2) { > + if (bootverbose) > + printf("MADT: Skipping timer override\n"); > + return; > + } > if (bootverbose) > - printf("MADT: intr override: source %u, irq %u\n", > + printf("MADT: Interrupt override: source %u, irq %u\n", > intr->Source, intr->Interrupt); > KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); > if (madt_find_interrupt(intr->Interrupt, &new_ioapic, > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_quirks 2004/10/08 > 18:00:57 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_quirks 2005/02/14 > 21:45:45 @@ -101,6 +101,13 @@ > oem_rev: FADT <= 0x06040000 > quirks: ACPI_Q_BROKEN > > +# Compaq R3000Z > +name: Compaq_R3000Z > +oem: FADT "NVIDIA" "CK8 " > +oem_rev: FADT = 0x6040000 > +creator: FADT "PTL_" > +quirks: ACPI_Q_MADT_IRQ0 > + > # Compaq Thunder 05/18/99 > # XXX Note creator rev should be "=", I think > name: Compaq_Thunder > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_resource.c 2005/01/18 > 20:25:37 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_resource.c 2005/01/18 > 23:04:51 @@ -77,6 +77,12 @@ > req->counter++; > break; > } > + if (irq != rman_get_start(req->res) && irq == 0) { > + if (bootverbose) > + printf("IRQ is %u, resource is %lu\n", irq, > + rman_get_start(req->res)); > + return (AE_CTRL_TERMINATE); > + } > req->found = 1; > KASSERT(irq == rman_get_start(req->res), > ("IRQ resources do not match")); > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpivar.h 2004/12/13 23:35:37 > +++ //depot/user/jhb/acpipci/dev/acpica/acpivar.h 2005/02/11 19:51:51 > @@ -160,11 +160,20 @@ > #define ACPI_INTR_APIC 1 > #define ACPI_INTR_SAPIC 2 > > -/* Quirk flags. */ > +/* > + * Quirk flags. > + * > + * ACPI_Q_BROKEN: Disables all ACPI support. > + * ACPI_Q_TIMER: Disables support for the ACPI timer. > + * ACPI_Q_MADT_IRQ0: Specifies that ISA IRQ 0 is wired up to pin 0 of the > + * first APIC and that the MADT should force that by ignoring the PC-AT > + * compatible flag and ignoring overrides that redirect IRQ 0 to pin 2. > + */ > extern int acpi_quirks; > #define ACPI_Q_OK 0 > -#define ACPI_Q_BROKEN (1 << 0) /* Disable ACPI completely. */ > -#define ACPI_Q_TIMER (1 << 1) /* Disable ACPI timer. */ > +#define ACPI_Q_BROKEN (1 << 0) > +#define ACPI_Q_TIMER (1 << 1) > +#define ACPI_Q_MADT_IRQ0 (1 << 2) > > /* > * Note that the low ivar values are reserved to provide > --- //depot/vendor/freebsd/src/sys/i386/acpica/madt.c 2004/06/10 20:05:33 > +++ //depot/user/jhb/acpipci/i386/acpica/madt.c 2005/02/14 22:18:55 > @@ -367,7 +367,7 @@ > } > > /* First, we run through adding I/O APIC's. */ > - if (madt->PCATCompat) > + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) > ioapic_enable_mixed_mode(); > madt_walk_table(madt_parse_apics, NULL); > > @@ -595,8 +595,14 @@ > enum intr_polarity pol; > char buf[64]; > > + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && > + intr->Interrupt == 2) { > + if (bootverbose) > + printf("MADT: Skipping timer override\n"); > + return; > + } > if (bootverbose) > - printf("MADT: intr override: source %u, irq %u\n", > + printf("MADT: Interrupt override: source %u, irq %u\n", > intr->Source, intr->Interrupt); > KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); > if (madt_find_interrupt(intr->Interrupt, &new_ioapic, > --- //depot/vendor/freebsd/src/sys/i386/i386/io_apic.c 2005/01/18 20:30:33 > +++ //depot/user/jhb/acpipci/i386/i386/io_apic.c 2005/02/08 19:07:03 > @@ -547,10 +547,11 @@ > > /* > * Assume that pin 0 on the first I/O APIC is an ExtINT pin > - * and that pins 1-15 are ISA interrupts. Assume that all > + * if mixed mode is enabled and an ISA interrupt if not. > + * Assume that pins 1-15 are ISA interrupts and that all > * other pins are PCI interrupts. > */ > - if (intpin->io_vector == 0) > + if (intpin->io_vector == 0 && mixed_mode_enabled) > ioapic_set_extint(io, i); > else if (intpin->io_vector < IOAPIC_ISA_INTS) { > intpin->io_bus = APIC_BUS_ISA; From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 22:37:32 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 ECFA916A4CE for ; Tue, 15 Feb 2005 22:37:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 493FB43D2F for ; Tue, 15 Feb 2005 22:37:31 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so935579rng for ; Tue, 15 Feb 2005 14:37: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=FmpHuh4NmWxR8UVfXTrYG/wuS4yvHeBuzM5S7c8jwNorGWs5t4OUjL3I2nfy4eKebuKGATS24AbIXI+jj/dkTPmVaulktz38SCGtdyI42WxPe3cO0GsZDFISm34HbCLo1dZd5kMf00aqAXBMAv9t7Rpzy7DHzTlC3LWYlaYr1Aw= Received: by 10.38.59.3 with SMTP id h3mr167081rna; Tue, 15 Feb 2005 14:37:30 -0800 (PST) Received: by 10.38.22.22 with HTTP; Tue, 15 Feb 2005 14:37:30 -0800 (PST) Message-ID: <346a80220502151437627a9ef6@mail.gmail.com> Date: Tue, 15 Feb 2005 17:37:30 -0500 From: Coleman Kane To: Nicolas Blais In-Reply-To: <200502151659.42594.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 22:37:32 -0000 Hi, I tested the patch posted by John on a compaq R3000. Works great, except still requires device atpic (for the mixed_mode operation I think). Kim posted a patch in this email: http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003376.html. I dunno if the patch is kosher or not, however. It does allow me to run without using atpic. -- coleman On Tue, 15 Feb 2005 16:59:41 -0500, Nicolas Blais wrote: > Hi, > > Thanks for the patch. Will this be MFC into -STABLE? > > Nicolas. > > On February 14, 2005 17:22, John Baldwin wrote: > > I've tweaked Jung-uk Kim's patches to be driven by a single ACPI quirk > > rather than multiple hints. I've included the patch below. If the quirk > > is not automatically detected on your laptop, you can manually set it from > > the loader via 'set debug.acpi.quirks=4'. If you have to manually set the > > quirk to get it to work, please let me know and include the FADT header > > from your acpidump in your reply, thanks. > > > > --- //depot/vendor/freebsd/src/sys/amd64/acpica/madt.c 2004/06/10 21:30:51 > > +++ //depot/user/jhb/acpipci/amd64/acpica/madt.c 2005/02/14 22:18:55 > > @@ -367,7 +367,7 @@ > > } > > > > /* First, we run through adding I/O APIC's. */ > > - if (madt->PCATCompat) > > + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) > > ioapic_enable_mixed_mode(); > > madt_walk_table(madt_parse_apics, NULL); > > > > @@ -596,8 +596,14 @@ > > enum intr_polarity pol; > > char buf[64]; > > > > + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && > > + intr->Interrupt == 2) { > > + if (bootverbose) > > + printf("MADT: Skipping timer override\n"); > > + return; > > + } > > if (bootverbose) > > - printf("MADT: intr override: source %u, irq %u\n", > > + printf("MADT: Interrupt override: source %u, irq %u\n", > > intr->Source, intr->Interrupt); > > KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); > > if (madt_find_interrupt(intr->Interrupt, &new_ioapic, > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_quirks 2004/10/08 > > 18:00:57 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_quirks 2005/02/14 > > 21:45:45 @@ -101,6 +101,13 @@ > > oem_rev: FADT <= 0x06040000 > > quirks: ACPI_Q_BROKEN > > > > +# Compaq R3000Z > > +name: Compaq_R3000Z > > +oem: FADT "NVIDIA" "CK8 " > > +oem_rev: FADT = 0x6040000 > > +creator: FADT "PTL_" > > +quirks: ACPI_Q_MADT_IRQ0 > > + > > # Compaq Thunder 05/18/99 > > # XXX Note creator rev should be "=", I think > > name: Compaq_Thunder > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_resource.c 2005/01/18 > > 20:25:37 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_resource.c 2005/01/18 > > 23:04:51 @@ -77,6 +77,12 @@ > > req->counter++; > > break; > > } > > + if (irq != rman_get_start(req->res) && irq == 0) { > > + if (bootverbose) > > + printf("IRQ is %u, resource is %lu\n", irq, > > + rman_get_start(req->res)); > > + return (AE_CTRL_TERMINATE); > > + } > > req->found = 1; > > KASSERT(irq == rman_get_start(req->res), > > ("IRQ resources do not match")); > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpivar.h 2004/12/13 23:35:37 > > +++ //depot/user/jhb/acpipci/dev/acpica/acpivar.h 2005/02/11 19:51:51 > > @@ -160,11 +160,20 @@ > > #define ACPI_INTR_APIC 1 > > #define ACPI_INTR_SAPIC 2 > > > > -/* Quirk flags. */ > > +/* > > + * Quirk flags. > > + * > > + * ACPI_Q_BROKEN: Disables all ACPI support. > > + * ACPI_Q_TIMER: Disables support for the ACPI timer. > > + * ACPI_Q_MADT_IRQ0: Specifies that ISA IRQ 0 is wired up to pin 0 of the > > + * first APIC and that the MADT should force that by ignoring the PC-AT > > + * compatible flag and ignoring overrides that redirect IRQ 0 to pin 2. > > + */ > > extern int acpi_quirks; > > #define ACPI_Q_OK 0 > > -#define ACPI_Q_BROKEN (1 << 0) /* Disable ACPI completely. */ > > -#define ACPI_Q_TIMER (1 << 1) /* Disable ACPI timer. */ > > +#define ACPI_Q_BROKEN (1 << 0) > > +#define ACPI_Q_TIMER (1 << 1) > > +#define ACPI_Q_MADT_IRQ0 (1 << 2) > > > > /* > > * Note that the low ivar values are reserved to provide > > --- //depot/vendor/freebsd/src/sys/i386/acpica/madt.c 2004/06/10 20:05:33 > > +++ //depot/user/jhb/acpipci/i386/acpica/madt.c 2005/02/14 22:18:55 > > @@ -367,7 +367,7 @@ > > } > > > > /* First, we run through adding I/O APIC's. */ > > - if (madt->PCATCompat) > > + if (madt->PCATCompat && !(acpi_quirks & ACPI_Q_MADT_IRQ0)) > > ioapic_enable_mixed_mode(); > > madt_walk_table(madt_parse_apics, NULL); > > > > @@ -595,8 +595,14 @@ > > enum intr_polarity pol; > > char buf[64]; > > > > + if (acpi_quirks & ACPI_Q_MADT_IRQ0 && intr->Source == 0 && > > + intr->Interrupt == 2) { > > + if (bootverbose) > > + printf("MADT: Skipping timer override\n"); > > + return; > > + } > > if (bootverbose) > > - printf("MADT: intr override: source %u, irq %u\n", > > + printf("MADT: Interrupt override: source %u, irq %u\n", > > intr->Source, intr->Interrupt); > > KASSERT(intr->Bus == 0, ("bus for interrupt overrides must be zero")); > > if (madt_find_interrupt(intr->Interrupt, &new_ioapic, > > --- //depot/vendor/freebsd/src/sys/i386/i386/io_apic.c 2005/01/18 20:30:33 > > +++ //depot/user/jhb/acpipci/i386/i386/io_apic.c 2005/02/08 19:07:03 > > @@ -547,10 +547,11 @@ > > > > /* > > * Assume that pin 0 on the first I/O APIC is an ExtINT pin > > - * and that pins 1-15 are ISA interrupts. Assume that all > > + * if mixed mode is enabled and an ISA interrupt if not. > > + * Assume that pins 1-15 are ISA interrupts and that all > > * other pins are PCI interrupts. > > */ > > - if (intpin->io_vector == 0) > > + if (intpin->io_vector == 0 && mixed_mode_enabled) > > ioapic_set_extint(io, i); > > else if (intpin->io_vector < IOAPIC_ISA_INTS) { > > intpin->io_bus = APIC_BUS_ISA; > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 23:14: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 E747D16A4CE for ; Tue, 15 Feb 2005 23:14:13 +0000 (GMT) Received: from beastie.hyow.eu.org (beastie.hyow.eu.org [213.152.46.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AD3643D4C for ; Tue, 15 Feb 2005 23:14:12 +0000 (GMT) (envelope-from mark@hyow.eu.org) Received: (qmail 8290 invoked by uid 751); 15 Feb 2005 23:15:28 +0000 Received: from mark@hyow.eu.org by beastie.hyow.eu.org by uid 731 with qmail-scanner-1.22-st-qms Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 5.027307 secs); 15 Feb 2005 23:15:28 -0000 X-Spam-Status: No, hits=-2.8 required=5.0 X-Antivirus-HYOW.EU.ORG-Mail-From: mark@hyow.eu.org via beastie.hyow.eu.org X-Antivirus-HYOW.EU.ORG: 1.22-st-qms (Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 5.027307 secs Process 8284) Received: from deity.hyow.eu.org (mark@hyow.eu.org@10.0.0.11) by beastie.hyow.eu.org with AES256-SHA encrypted SMTP; 15 Feb 2005 23:15:23 +0000 Date: Tue, 15 Feb 2005 23:14:16 +0000 From: Mark Magiera To: freebsd-amd64@freebsd.org Message-Id: <20050215231416.449c8695.mark@hyow.eu.org> In-Reply-To: <20050215180011.GD38158@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> X-Mailer: Sylpheed version 1.0.0-gtk2-20041224 (GTK+ 2.4.14; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 15 Feb 2005 23:14:14 -0000 On Tue, 15 Feb 2005 10:00:11 -0800 "David O'Brien" wrote: > On Tue, Feb 15, 2005 at 11:36:49AM +0000, Mark Magiera wrote: > > On Tue, 8 Feb 2005 19:33:38 +0000 > > Mark Magiera wrote: > > > The thing I'm unsure about is, how well are the nforce4 chipsets > > > supported in FreeBSD? and what about PCI-E, would one of those > > > mobo's in combination with a PCI-E nvidia card work? > .. > > > Any advice would be much appreciated > .. > > Ok, quick update. I finally bought the mobo (Asus A8N-SLi) along > > with a 6600GT PCI-E and while there are a few problems, they seem > > the kind that can be ironed out over time. > ... > The FreeBSD interest and work on PCIe has been for storage and network > (e.g. server) devices, not graphics. So I have no idea how well PCIe > (much less PCIe-SLi) is supported yet. A donation of a nice PCIe > graphics card to Scottl would probably help the effort along. :-))))) Actaully, while I realise this card might not work with the accelerated nvidia drivers, it does work with the default xorg (nv) driver which I can live with. I'm assuming it's falling back to pci mode or something. Tested it on a FreeSBIE 1.0 livecd (I beleive it's based on 5.2.1-release), not in 64 bit mode but I assume things will be the same there. My main, if not only problem is the NIC being so unreliable. > > Basically, freebsd installs in both 32 and 64 bit mode but in both > > cases, the network card is so unreliable that half way through a > > cvsup (or anything else) it dies and nothing (that I know of) but a > > reboot fixes it, this is for the "sk" device. > > What OS version are you running? For the AMD64 platform you really, > really need to be tracking RELENG_5, if not 6-CURRENT. 5.3-RELEASE is > our first real AMD64 release and of course we're now getting 2 orders > of magnitude more testing exposure than when it was only a few > developers with AMD64 machines. FreeBSD/AMD64 will get as polished > and stable as FreeBSD/i386 over a very short time. 5.-3-RELEASE, the plan was to cvsup to at least RELENG_5 but with the network card it's rather hard to do ;) > If you have sk(4) problems with RELENG_5, please send a PR with > complete details and a dmesg.boot from a verbose boot. Ok, I'll see if I can extract any useful information but I'm thinking this is easier said than done. The card just stops dead in the water, with nothing useful being reported to dmesg or anywhere else. -- Mark Magiera From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 23:32:13 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 D45CD16A4CE for ; Tue, 15 Feb 2005 23:32:13 +0000 (GMT) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 2656A43D53 for ; Tue, 15 Feb 2005 23:32:12 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 63423 invoked from network); 15 Feb 2005 23:32:29 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 15 Feb 2005 23:32:29 -0000 Received: (qmail 13329 invoked by uid 1026); 15 Feb 2005 23:32:30 -0000 Received: from 192.168.1.32 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.23 ( Clear:RC:1(192.168.1.32):. Processed in 1.997636 secs); 15 Feb 2005 23:32:30 -0000 Received: from janm.transactionware.com (HELO ?192.168.1.32?) (192.168.1.32) by new.transactionware.com with SMTP; 15 Feb 2005 23:32:27 -0000 Message-ID: <4212868E.8080005@transactionware.com> Date: Wed, 16 Feb 2005 10:32:30 +1100 From: Jan Mikkelsen User-Agent: Mozilla Thunderbird 1.0 (X11/20050128) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> In-Reply-To: <20050215180011.GD38158@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Mark Magiera Subject: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi" or"Gigabyte K8NXP-SLI" mobos?) 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, 15 Feb 2005 23:32:13 -0000 David O'Brien wrote: > Stop supporting nVidia by buying nForce-based motherboards. Or complain > to nVidia that they (1) won't give us docs even under NDA, (2) won't > provide a FreeBSD driver like they do for Linux. These mailing lists are > filled with all the problems of nForce motherboards, yet FreeBSD users > keep buying them... HP have just announced the xw9300 workstation. According to the spec sheet the chipset is an "NVIDIA nForce Professional with AMD-8131 HyperTransport PCI-X tunnel". The xw9300 looked interesting to me, but I guess the chipset is going to be a problem for using FreeBSD on those boxes. Is HP a possible source of information on the chipset? (Incidentally, does anyone know anything about the HP DL385, or the HP Opteron blades, the BL25p and BL35p?) Regards, Jan. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 23:48:25 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 E496416A4CE; Tue, 15 Feb 2005 23:48:25 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9975343D3F; Tue, 15 Feb 2005 23:48:25 +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 j1FNmPMH097332; Tue, 15 Feb 2005 15:48:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FNmP11097331; Tue, 15 Feb 2005 15:48:25 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 15:48:25 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20050215234825.GA96584@dragon.nuxi.com> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215195517.GA17904@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215195517.GA17904@ip.net.ua> 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: Cross compiling for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 23:48:26 -0000 On Tue, Feb 15, 2005 at 09:55:17PM +0200, Ruslan Ermilov wrote: > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > Is this supposed to be possible/supported? And does anyone have any ideas > > how to make it work more automatically? > > No, this is not supported at all. What's supported is mounting i386's > /, /usr, and /var onto /mnt, /mnt/usr, and /mnt/var, and doing the > installworld with DESTDIR=/mnt from amd64. This isn't "supported" either. It happens to work most of the time. But isn't a guaranteed by The FreeBSD Project. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 23:50:24 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 73C0D16A4D6 for ; Tue, 15 Feb 2005 23:50:24 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F19143D60 for ; Tue, 15 Feb 2005 23:50:16 +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 j1FNoFXC097384; Tue, 15 Feb 2005 15:50:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FNoECM097382; Tue, 15 Feb 2005 15:50:14 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 15:50:14 -0800 From: "David O'Brien" To: Willem Jan Withagen Message-ID: <20050215235014.GB96584@dragon.nuxi.com> References: <20050215182130.GA85174@dragon.nuxi.com> <42126DED.6080501@withagen.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42126DED.6080501@withagen.nl> 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: "Xi.Liu" cc: freebsd-amd64@freebsd.org Subject: Re: Can not create slice on a SATA drive X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 23:50:24 -0000 On Tue, Feb 15, 2005 at 10:47:25PM +0100, Willem Jan Withagen wrote: > David O'Brien wrote: > >On Tue, Feb 15, 2005 at 01:09:48PM -0500, Xi.Liu wrote: > >>Still not very sure, .... (I am new using FreeBSD). > >>I guess even I boot singel user, the disk will still be mounted as /. > >Correct. / will be mount read-only. > >>Do I have to boot from a bootable-CD (say the installation CD)? > > > >Nope, you can use /usr/sbin/sysinstall. > >But you'll have to mount /usr (but do it read-only!) first if you didn't > >combine / + /usr into a single partition. > > I'm always using the 'cheat' option: > sysctl -w kern.geom.debugflags=16 > > Not shure if it is without ill effects. It allows total foot shooting and is quite dangerous. It is 'rm -rf' where the default FS to rm is / Booting single user is what most people should be doing for now. Especially someone "I am new using FreeBSD". -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 15 23:54:00 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 E4A0416A4CE for ; Tue, 15 Feb 2005 23:54:00 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4EC143D53 for ; Tue, 15 Feb 2005 23:54:00 +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 j1FNrxhY097552; Tue, 15 Feb 2005 15:54:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1FNrwPn097551; Tue, 15 Feb 2005 15:53:58 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 15:53:58 -0800 From: "David O'Brien" To: Jan Mikkelsen Message-ID: <20050215235358.GC96584@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4212868E.8080005@transactionware.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: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi" or"Gigabyte K8NXP-SLI" mobos?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 23:54:01 -0000 On Wed, Feb 16, 2005 at 10:32:30AM +1100, Jan Mikkelsen wrote: > sheet the chipset is an "NVIDIA nForce Professional with AMD-8131 > HyperTransport PCI-X tunnel". > > The xw9300 looked interesting to me, but I guess the chipset is going to > be a problem for using FreeBSD on those boxes. Is HP a possible source > of information on the chipset? Very unlikely. > (Incidentally, does anyone know anything about the HP DL385, or the HP > Opteron blades, the BL25p and BL35p?) The *5 machines are opteron versions of the Xeon offerings. See the *0 Xeon offerings to get a feel for the specs of the box. I *believe* the DL385 uses the DL380 chassis. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 00:03: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 C065316A4CE; Wed, 16 Feb 2005 00:03:09 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD2F943D3F; Wed, 16 Feb 2005 00:03:06 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (8.13.1/8.13.1) with ESMTP id j1G0300q014428; Wed, 16 Feb 2005 01:03:01 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <42128DBC.7010606@withagen.nl> Date: Wed, 16 Feb 2005 01:03:08 +0100 From: Willem Jan Withagen User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050215182130.GA85174@dragon.nuxi.com> <42126DED.6080501@withagen.nl> <20050215235014.GB96584@dragon.nuxi.com> In-Reply-To: <20050215235014.GB96584@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: "Xi.Liu" cc: freebsd-amd64@freebsd.org Subject: Re: Can not create slice on a SATA drive 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, 16 Feb 2005 00:03:09 -0000 David O'Brien wrote: > On Tue, Feb 15, 2005 at 10:47:25PM +0100, Willem Jan Withagen wrote: > >>David O'Brien wrote: >> >>>On Tue, Feb 15, 2005 at 01:09:48PM -0500, Xi.Liu wrote: >>> >>>>Still not very sure, .... (I am new using FreeBSD). >>>>I guess even I boot singel user, the disk will still be mounted as /. >>> >>>Correct. / will be mount read-only. >>> >>>>Do I have to boot from a bootable-CD (say the installation CD)? >>> >>>Nope, you can use /usr/sbin/sysinstall. >>>But you'll have to mount /usr (but do it read-only!) first if you didn't >>>combine / + /usr into a single partition. >> >>I'm always using the 'cheat' option: >>sysctl -w kern.geom.debugflags=16 >> >>Not shure if it is without ill effects. > > > It allows total foot shooting and is quite dangerous. > It is 'rm -rf' where the default FS to rm is / > > Booting single user is what most people should be doing for now. > Especially someone "I am new using FreeBSD". I knew it was loaded with footshooting options so you are true, especially with the last remark. Did not pay attention to that. --WjW From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 00:04: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 3C73116A4CE; Wed, 16 Feb 2005 00:04:26 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7193143D45; Wed, 16 Feb 2005 00:04:25 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1G04Ov3046059; Wed, 16 Feb 2005 02:04:24 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 83589-12; Wed, 16 Feb 2005 02:04:23 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1G04Ncr046056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2005 02:04:23 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1G04Sqf049360; Wed, 16 Feb 2005 02:04:28 +0200 (EET) (envelope-from ru) Date: Wed, 16 Feb 2005 02:04:28 +0200 From: Ruslan Ermilov To: "David O'Brien" Message-ID: <20050216000428.GC24447@ip.net.ua> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215195517.GA17904@ip.net.ua> <20050215234825.GA96584@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Km1U/tdNT/EmXiR1" Content-Disposition: inline In-Reply-To: <20050215234825.GA96584@dragon.nuxi.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@freebsd.org Subject: Re: Cross compiling for i386 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, 16 Feb 2005 00:04:26 -0000 --Km1U/tdNT/EmXiR1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 03:48:25PM -0800, David O'Brien wrote: > On Tue, Feb 15, 2005 at 09:55:17PM +0200, Ruslan Ermilov wrote: > > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > > Is this supposed to be possible/supported? And does anyone have any = ideas > > > how to make it work more automatically? > >=20 > > No, this is not supported at all. What's supported is mounting i386's > > /, /usr, and /var onto /mnt, /mnt/usr, and /mnt/var, and doing the > > installworld with DESTDIR=3D/mnt from amd64. >=20 > This isn't "supported" either. It happens to work most of the time. > But isn't a guaranteed by The FreeBSD Project. >=20 Cross-built binaries should be fine. Some data files generated by host tools may be corrupt due to endianness and type width issues (e.g., "long" is 8 bytes on amd64 but only 4 bytes on i386). Last time I tried installing Alpha world + kernel generated by i386, the only things I've noticed broken were NLS catalogs and locale related data files. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Km1U/tdNT/EmXiR1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCEo4MqRfpzJluFF4RAjc/AJ40CRCWTtxk3rbRFENUf0BlcNv9DQCdEBTp couNyRxgHBAkcTyFGu0wFuo= =PE5/ -----END PGP SIGNATURE----- --Km1U/tdNT/EmXiR1-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 00:21:33 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 4FDC116A4CE for ; Wed, 16 Feb 2005 00:21:33 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E9D43D2D for ; Wed, 16 Feb 2005 00:21:32 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id 3C1351F87BEE; Wed, 16 Feb 2005 01:21:30 +0100 (CET) Date: Wed, 16 Feb 2005 01:21:30 +0100 From: Roman Neuhauser To: freebsd-amd64@freebsd.org Message-ID: <20050216002130.GA73909@isis.wad.cz> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215180011.GD38158@dragon.nuxi.com> User-Agent: Mutt/1.5.6i Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 16 Feb 2005 00:21:33 -0000 # obrien@freebsd.org / 2005-02-15 10:00:11 -0800: > Stop supporting nVidia by buying nForce-based motherboards. Or complain > to nVidia that they (1) won't give us docs even under NDA, (2) won't > provide a FreeBSD driver like they do for Linux. These mailing lists are > filled with all the problems of nForce motherboards, yet FreeBSD users > keep buying them... This reminds me I wanted to raise this question: What is the recommended chipset for an athlon64 (either 754 or 939)? -- FreeBSD 4.10-STABLE 12:48AM up 4 days, 13:52, 12 users, load averages: 0.00, 0.00, 0.00 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 00:26:00 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 B337E16A4CF; Wed, 16 Feb 2005 00:26:00 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7228F43D5A; Wed, 16 Feb 2005 00:26:00 +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 j1G0Q0kg098482; Tue, 15 Feb 2005 16:26:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G0Q068098481; Tue, 15 Feb 2005 16:26:00 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 16:26:00 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20050216002600.GA97906@dragon.nuxi.com> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215195517.GA17904@ip.net.ua> <20050215234825.GA96584@dragon.nuxi.com> <20050216000428.GC24447@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050216000428.GC24447@ip.net.ua> 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: Cross compiling for i386 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 00:26:00 -0000 On Wed, Feb 16, 2005 at 02:04:28AM +0200, Ruslan Ermilov wrote: > On Tue, Feb 15, 2005 at 03:48:25PM -0800, David O'Brien wrote: > > On Tue, Feb 15, 2005 at 09:55:17PM +0200, Ruslan Ermilov wrote: > > > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > > > Is this supposed to be possible/supported? And does anyone have any ideas > > > > how to make it work more automatically? > > > > > > No, this is not supported at all. What's supported is mounting i386's > > > /, /usr, and /var onto /mnt, /mnt/usr, and /mnt/var, and doing the > > > installworld with DESTDIR=/mnt from amd64. > > > > This isn't "supported" either. It happens to work most of the time. > > But isn't a guaranteed by The FreeBSD Project. > > Cross-built binaries should be fine. Some data files generated by > host tools may be corrupt due to endianness and type width issues > (e.g., "long" is 8 bytes on amd64 but only 4 bytes on i386). > > Last time I tried installing Alpha world + kernel generated by i386, > the only things I've noticed broken were NLS catalogs and locale > related data files. Yes, and that in my book means "some brokenness" and not offically supported (ie, to be depended on). -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 01:13: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 DA4A216A4CF for ; Wed, 16 Feb 2005 01:13:56 +0000 (GMT) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 2622843D58 for ; Wed, 16 Feb 2005 01:13:55 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 63940 invoked from network); 16 Feb 2005 01:14:13 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 16 Feb 2005 01:14:13 -0000 Received: (qmail 72434 invoked by uid 1026); 16 Feb 2005 01:14:14 -0000 Received: from 192.168.1.32 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.23 ( Clear:RC:1(192.168.1.32):. Processed in 1.964871 secs); 16 Feb 2005 01:14:14 -0000 Received: from janm.transactionware.com (HELO ?192.168.1.32?) (192.168.1.32) by new.transactionware.com with SMTP; 16 Feb 2005 01:14:12 -0000 Message-ID: <42129E66.5090903@transactionware.com> Date: Wed, 16 Feb 2005 12:14:14 +1100 From: Jan Mikkelsen User-Agent: Mozilla Thunderbird 1.0 (X11/20050128) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> In-Reply-To: <20050215235358.GC96584@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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, 16 Feb 2005 01:13:57 -0000 David O'Brien wrote: >>(Incidentally, does anyone know anything about the HP DL385, or the HP >>Opteron blades, the BL25p and BL35p?) > > The *5 machines are opteron versions of the Xeon offerings. See the *0 > Xeon offerings to get a feel for the specs of the box. > I *believe* the DL385 uses the DL380 chassis. I am also interested in the chipsets they use. I believe the DL145 uses the AMD 8000 chipset, but I can't find any information on the newer servers. I was concerned that they might use nVidia chipsets, like the new workstation. However, on rereading the press release, they only tout the nVidia chipset for the workstation, so the servers probably use something much more boring! Regards, Jan. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 01:16: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 B90DA16A4CE for ; Wed, 16 Feb 2005 01:16:03 +0000 (GMT) Received: from hood.oook.cz (hood.oook.cz [212.27.205.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D466343D31 for ; Wed, 16 Feb 2005 01:16:02 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (localhost.oook.cz [127.0.0.1]) by hood.oook.cz (8.13.1/8.13.1) with ESMTP id j1G1G1E9001778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 16 Feb 2005 02:16:01 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by hood.oook.cz (8.13.1/8.13.1/Submit) id j1G1G14u001777 for freebsd-amd64@FreeBSD.org; Wed, 16 Feb 2005 02:16:01 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: hood.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: freebsd-amd64@FreeBSD.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YZpOLdAn7CzetaVa6D0U" Date: Wed, 16 Feb 2005 02:16:01 +0100 Message-Id: <1108516561.1564.4.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Subject: va_list fun X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 01:16:03 -0000 --=-YZpOLdAn7CzetaVa6D0U Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Someone please explain to me what I'm doing wrong: [legrace.c] #include #include void funny(char *format, ...) { va_list ap; va_start(ap, format); vfprintf(stdout, format, ap); vfprintf(stdout, format, ap); vfprintf(stdout, format, ap); vfprintf(stdout, format, ap); vfprintf(stdout, format, ap); va_end(ap); } int main(int argc, char *argv[]) { funny("%s\n", "string"); } [my 4-STABLE/i386 from Dec 2 2004] $ gcc legrace.c=20 $ ./a.out=20 string string string string string [my 5-STABLE/i386 from Jan 3 2005] $ gcc -O legrace.c=20 $ ./a.out=20 string string string string string [my 5-STABLE/amd64 from Feb 10 2005] $ gcc legrace.c $ ./a.out string =E7=FF=FF=FF Segmentation fault (core dumped) [sledge.freebsd.org] $ gcc legrace.c=20 $ ./a.out=20 string =F0=EC=FF=FF=FF Segmentation fault (core dumped) [pluto2.freebsd.org] $ gcc legrace.c=20 $ ./a.out=20 string string string string string --=20 Pav Lucistnik 94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box. --=-YZpOLdAn7CzetaVa6D0U Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCEp7RntdYP8FOsoIRAgClAJsHfAVyDah4LQk+5zTz9RwzhSFyDwCgjaC+ 1ChxPklSfb41Ks23pREQACE= =H/NS -----END PGP SIGNATURE----- --=-YZpOLdAn7CzetaVa6D0U-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 01:18: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 CA18B16A4CE for ; Wed, 16 Feb 2005 01:18:56 +0000 (GMT) Received: from hood.oook.cz (hood.oook.cz [212.27.205.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D96B243D55 for ; Wed, 16 Feb 2005 01:18:55 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (localhost.oook.cz [127.0.0.1]) by hood.oook.cz (8.13.1/8.13.1) with ESMTP id j1G1IsAB001799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2005 02:18:54 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by hood.oook.cz (8.13.1/8.13.1/Submit) id j1G1IsZU001798; Wed, 16 Feb 2005 02:18:54 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: hood.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Roman Neuhauser In-Reply-To: <20050216002130.GA73909@isis.wad.cz> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-HYvgt+KruyP9Phwftch8" Date: Wed, 16 Feb 2005 02:18:54 +0100 Message-Id: <1108516734.1564.6.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: freebsd-amd64@FreeBSD.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 01:18:56 -0000 --=-HYvgt+KruyP9Phwftch8 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Roman Neuhauser p=ED=B9e v st 16. 02. 2005 v 01:21 +0100: > # obrien@freebsd.org / 2005-02-15 10:00:11 -0800: > > Stop supporting nVidia by buying nForce-based motherboards. Or complai= n > > to nVidia that they (1) won't give us docs even under NDA, (2) won't > > provide a FreeBSD driver like they do for Linux. These mailing lists a= re > > filled with all the problems of nForce motherboards, yet FreeBSD users > > keep buying them... >=20 > This reminds me I wanted to raise this question: What is the > recommended chipset for an athlon64 (either 754 or 939)? Taking all the problems people head from nForce crowd, I'd suggest VIA KT800, only remaining offering on the market.. --=20 Pav Lucistnik It also explains why paper clips just lie there while you look at them, but as soon as you turn your back, they run away, giggling wildly, and transform themselves into coat hangers. --=-HYvgt+KruyP9Phwftch8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCEp9+ntdYP8FOsoIRAvd9AJsGU9wdTJpaB/LDU7p3olJf9yCc2gCfX39L B3lta3xj5S+4Pz5aJUOnwVQ= =ssPU -----END PGP SIGNATURE----- --=-HYvgt+KruyP9Phwftch8-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 02:13:32 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 F412D16A4CE for ; Wed, 16 Feb 2005 02:13:31 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 644A743D39 for ; Wed, 16 Feb 2005 02:13:31 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so12156wra for ; Tue, 15 Feb 2005 18:13: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=TIXGgm23OB7dt/wdD72k47uzwUDTLB6eQe71MB/ttCQJW1IKtuD6+J3FV1DGX7fXBWy1LrkSdatfrf/Lfqih/tYqYxq4i8XZCt/vzfooMdhQrQV3DWf5qEBfuvBU14B3CyMDgHvQK5jU4StMdE4fofqpl+GuGlRcJUVsr8gXAeE= Received: by 10.54.38.63 with SMTP id l63mr48417wrl; Tue, 15 Feb 2005 18:13:30 -0800 (PST) Received: by 10.54.40.69 with HTTP; Tue, 15 Feb 2005 18:13:30 -0800 (PST) Message-ID: <2fd864e050215181374d2e2b1@mail.gmail.com> Date: Tue, 15 Feb 2005 20:13:30 -0600 From: Astrodog To: Jan Mikkelsen In-Reply-To: <42129E66.5090903@transactionware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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, 16 Feb 2005 02:13:32 -0000 On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen wrote: > David O'Brien wrote: > >>(Incidentally, does anyone know anything about the HP DL385, or the HP > >>Opteron blades, the BL25p and BL35p?) > > > > The *5 machines are opteron versions of the Xeon offerings. See the *0 > > Xeon offerings to get a feel for the specs of the box. > > I *believe* the DL385 uses the DL380 chassis. > > I am also interested in the chipsets they use. > > I believe the DL145 uses the AMD 8000 chipset, but I can't find any > information on the newer servers. I was concerned that they might use > nVidia chipsets, like the new workstation. However, on rereading the > press release, they only tout the nVidia chipset for the workstation, so > the servers probably use something much more boring! > > Regards, > > Jan. > _______________________________________________ > 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" > I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 02:32:34 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 9781D16A4CE for ; Wed, 16 Feb 2005 02:32:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B120C43D1F for ; Wed, 16 Feb 2005 02:32:33 +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 j1G2Wj4H037451; Tue, 15 Feb 2005 19:32:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4212B0BC.5060409@samsco.org> Date: Tue, 15 Feb 2005 19:32:28 -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: Astrodog References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <2fd864e050215181374d2e2b1@mail.gmail.com> In-Reply-To: <2fd864e050215181374d2e2b1@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: Jan Mikkelsen cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "AsusA8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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, 16 Feb 2005 02:32:34 -0000 Astrodog wrote: > On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen > wrote: > >>David O'Brien wrote: >> >>>>(Incidentally, does anyone know anything about the HP DL385, or the HP >>>>Opteron blades, the BL25p and BL35p?) >>> >>>The *5 machines are opteron versions of the Xeon offerings. See the *0 >>>Xeon offerings to get a feel for the specs of the box. >>>I *believe* the DL385 uses the DL380 chassis. >> >>I am also interested in the chipsets they use. >> >>I believe the DL145 uses the AMD 8000 chipset, but I can't find any >>information on the newer servers. I was concerned that they might use >>nVidia chipsets, like the new workstation. However, on rereading the >>press release, they only tout the nVidia chipset for the workstation, so >>the servers probably use something much more boring! >> >>Regards, >> >>Jan. > > > I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. The literature for the Via K8T890 claims that it supports up to 2 CPUs, but I've only seen single-CPU boards based on it. In reality, since the bridge between the northbridge and the CPU is HyperTransport, the support for SMP comes more from that motherboard maker than from the chipset maker. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 02:43: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 274C216A4CE for ; Wed, 16 Feb 2005 02:43:49 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7CC243D31 for ; Wed, 16 Feb 2005 02:43:48 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id CC91372DD4; Tue, 15 Feb 2005 18:43:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id C884172DCB; Tue, 15 Feb 2005 18:43:48 -0800 (PST) Date: Tue, 15 Feb 2005 18:43:48 -0800 (PST) From: Doug White To: Jan Mikkelsen In-Reply-To: <4212868E.8080005@transactionware.com> Message-ID: <20050215184118.B32860@carver.gumbysoft.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi" or"Gigabyte K8NXP-SLI" mobos?) 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, 16 Feb 2005 02:43:49 -0000 On Wed, 16 Feb 2005, Jan Mikkelsen wrote: > David O'Brien wrote: > > Stop supporting nVidia by buying nForce-based motherboards. Or complain > > to nVidia that they (1) won't give us docs even under NDA, (2) won't > > provide a FreeBSD driver like they do for Linux. These mailing lists are > > filled with all the problems of nForce motherboards, yet FreeBSD users > > keep buying them... > > HP have just announced the xw9300 workstation. According to the spec > sheet the chipset is an "NVIDIA nForce Professional with AMD-8131 > HyperTransport PCI-X tunnel". > > The xw9300 looked interesting to me, but I guess the chipset is going to > be a problem for using FreeBSD on those boxes. Is HP a possible source > of information on the chipset? AMD-8131 is a generic HT-PCIX bridge. Its likely an 8111 chipset, which works fine. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 03:02: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 D24F016A4CE for ; Wed, 16 Feb 2005 03:02:09 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A57743D48 for ; Wed, 16 Feb 2005 03:02:08 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so19827rnf for ; Tue, 15 Feb 2005 19:02:07 -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=F5mN9eV2DoPqaAnR+BdlQyepQnxmCN8Xzze8sH36O0fQnVMWIkvqUxsdIQ+8ucSPr2B8mzQ23mX0H+juhMNmrnvmzh/04a95BAdh4ySn32OksTCmZsw/Hr/O6nQzfccEoJY2rMljkFdFIJKoxjyHMwYu3Bx8gKjVmS4MypGcW/8= Received: by 10.39.2.45 with SMTP id e45mr91558rni; Tue, 15 Feb 2005 19:02:07 -0800 (PST) Received: by 10.38.209.12 with HTTP; Tue, 15 Feb 2005 19:02:07 -0800 (PST) Message-ID: <84dead720502151902778f893c@mail.gmail.com> Date: Wed, 16 Feb 2005 03:02:07 +0000 From: Joseph Koshy To: Mark Magiera In-Reply-To: <20050215231416.449c8695.mark@hyow.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050215231416.449c8695.mark@hyow.eu.org> cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 03:02:09 -0000 > My main, if not only problem is the NIC being so unreliable. You may want to upgrade to 5.3-STABLE. I installed 5.3-RELEASE on an ASUS K8V (which has the same NIC). I kept the following loop running in the background while :; do sleep 20 ifconfig sk0 down ifconfig sk0 up done this kept the network driver usable while I downloaded the -stable tree. A make world later, the box was stable. If you don't want to change your userland, you could probably get by recompiling the kernel with an 5.3-STABLE version of "if_sk.c". I haven't tested this though. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 03:21: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 F201F16A4CE for ; Wed, 16 Feb 2005 03:21:27 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C6243D45 for ; Wed, 16 Feb 2005 03:21:27 +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 j1G3LQre003045; Tue, 15 Feb 2005 19:21:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G3LQoN003040; Tue, 15 Feb 2005 19:21:26 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 19:21:25 -0800 From: "David O'Brien" To: Jan Mikkelsen Message-ID: <20050216032125.GA2966@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42129E66.5090903@transactionware.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: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi" or"Gigabyte K8NXP-SLI" mobos?) 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: Wed, 16 Feb 2005 03:21:28 -0000 On Wed, Feb 16, 2005 at 12:14:14PM +1100, Jan Mikkelsen wrote: > David O'Brien wrote: > >>(Incidentally, does anyone know anything about the HP DL385, or the HP > >>Opteron blades, the BL25p and BL35p?) > > > >The *5 machines are opteron versions of the Xeon offerings. See the *0 > >Xeon offerings to get a feel for the specs of the box. > >I *believe* the DL385 uses the DL380 chassis. > > I am also interested in the chipsets they use. > > I believe the DL145 uses the AMD 8000 chipset, The HP DL145 uses the AMD 8100 chipset. The HP DL145 is an AMD design. The HP DL585 also uses the AMD 8100 chipset, with the DL585 being a Compaq design. So I expect the DL385 to use the AMD 8100 chipset also. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 03:24: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 B0C1216A4CE for ; Wed, 16 Feb 2005 03:24:29 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7578443D2F for ; Wed, 16 Feb 2005 03:24:29 +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 j1G3OTNW003133; Tue, 15 Feb 2005 19:24:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G3OPck003125; Tue, 15 Feb 2005 19:24:25 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 19:24:25 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050216032425.GB2966@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <2fd864e050215181374d2e2b1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e050215181374d2e2b1@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: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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: Wed, 16 Feb 2005 03:24:29 -0000 On Tue, Feb 15, 2005 at 08:13:30PM -0600, Astrodog wrote: > On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen > wrote: > > David O'Brien wrote: > > >>(Incidentally, does anyone know anything about the HP DL385, or the HP > > >>Opteron blades, the BL25p and BL35p?) > > > > > > The *5 machines are opteron versions of the Xeon offerings. See the *0 > > > Xeon offerings to get a feel for the specs of the box. > > > I *believe* the DL385 uses the DL380 chassis. > > > > I am also interested in the chipsets they use. > > > > I believe the DL145 uses the AMD 8000 chipset, but I can't find any > > information on the newer servers. I was concerned that they might use > > nVidia chipsets, like the new workstation. However, on rereading the > > press release, they only tout the nVidia chipset for the workstation, so > > the servers probably use something much more boring! > > I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. There is NO chipset that enables SMP. Opteron's are directly connected thru HyperTransport links. (AMD marketing now calls this Direct Connect(tm)). The various chipset pieces are only for I/O, not memory controller or MP communication. Note that the HP dual-processor workstation doesn't use the AMD chipset, yet is MP. (Opteron's also aren't SMP, but are a NUMA architecture) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 05:28: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 ABF8916A4CE; Wed, 16 Feb 2005 05:28:27 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E479643D41; Wed, 16 Feb 2005 05:28:26 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1G5RvT8036265; Wed, 16 Feb 2005 00:27:58 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, cokane@cokane.org Date: Wed, 16 Feb 2005 00:27:55 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> <346a80220502151437627a9ef6@mail.gmail.com> In-Reply-To: <346a80220502151437627a9ef6@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_bntECfMDi4sZ2i6" Message-Id: <200502160027.55420.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 05:28:27 -0000 --Boundary-00=_bntECfMDi4sZ2i6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tuesday 15 February 2005 05:37 pm, Coleman Kane wrote: > Hi, I tested the patch posted by John on a compaq R3000. Works > great, except still requires device atpic (for the mixed_mode > operation I think). Kim posted a patch in this email: > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/00337 >6.html. I dunno if the patch is kosher or not, however. It does > allow me to run without using atpic. Ouch, you're absolutely correct. jhb's patch wasn't complete for amd64. The missing piece is attached. Can you please re-test? Thanks, Jung-uk Kim --Boundary-00=_bntECfMDi4sZ2i6 Content-Type: text/plain; charset="iso-8859-1"; name="r3000-amd64.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="r3000-amd64.diff" --- src/sys/amd64/amd64/io_apic.c.orig Mon Aug 16 19:12:29 2004 +++ src/sys/amd64/amd64/io_apic.c Wed Feb 16 00:21:23 2005 @@ -548,10 +548,11 @@ /* * Assume that pin 0 on the first I/O APIC is an ExtINT pin - * and that pins 1-15 are ISA interrupts. Assume that all + * if mixed mode is enabled and an ISA interrupt if not. + * Assume that pins 1-15 are ISA interrupts and that all * other pins are PCI interrupts. */ - if (intpin->io_vector == 0) + if (intpin->io_vector == 0 && mixed_mode_enabled) ioapic_set_extint(io, i); else if (intpin->io_vector < IOAPIC_ISA_INTS) { intpin->io_bus = APIC_BUS_ISA; --Boundary-00=_bntECfMDi4sZ2i6-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 05:54: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 DAAEA16A4CE; Wed, 16 Feb 2005 05:54:19 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 886FF43D1D; Wed, 16 Feb 2005 05:54:19 +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 j1G5rnqd006834; Tue, 15 Feb 2005 21:53:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G5rmgQ006833; Tue, 15 Feb 2005 21:53:49 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 21:53:48 -0800 From: "David O'Brien" To: Jung-uk Kim Message-ID: <20050216055348.GA6793@dragon.nuxi.com> References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> <346a80220502151437627a9ef6@mail.gmail.com> <200502160027.55420.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502160027.55420.jkim@niksun.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 cc: cokane@cokane.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 05:54:20 -0000 On Wed, Feb 16, 2005 at 12:27:55AM -0500, Jung-uk Kim wrote: > On Tuesday 15 February 2005 05:37 pm, Coleman Kane wrote: > > Hi, I tested the patch posted by John on a compaq R3000. Works > > great, except still requires device atpic (for the mixed_mode > > operation I think). Kim posted a patch in this email: > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/00337 > >6.html. I dunno if the patch is kosher or not, however. It does > > allow me to run without using atpic. > > Ouch, you're absolutely correct. jhb's patch wasn't complete for > amd64. The missing piece is attached. Can you please re-test? Can we remove "device atpic" from GENERIC with this? Can an inflicted user try it out so we can add that change to the patch also? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:05: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 7629516A4CE; Wed, 16 Feb 2005 06:05:12 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10E0543D31; Wed, 16 Feb 2005 06:05:12 +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 j1G656NZ007148; Tue, 15 Feb 2005 22:05:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G656WP007147; Tue, 15 Feb 2005 22:05:06 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 22:05:06 -0800 From: "David O'Brien" To: Pav Lucistnik Message-ID: <20050216060506.GA2900@dragon.nuxi.com> References: <1108516561.1564.4.camel@hood.oook.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1108516561.1564.4.camel@hood.oook.cz> 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: va_list fun 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: Wed, 16 Feb 2005 06:05:12 -0000 On Wed, Feb 16, 2005 at 02:16:01AM +0100, Pav Lucistnik wrote: > Someone please explain to me what I'm doing wrong: > > [legrace.c] > #include > #include > > void funny(char *format, ...) { > va_list ap; > > va_start(ap, format); > vfprintf(stdout, format, ap); > vfprintf(stdout, format, ap); > vfprintf(stdout, format, ap); > vfprintf(stdout, format, ap); > vfprintf(stdout, format, ap); > va_end(ap); > } You've consumed the 'ap' after the first vfprintf() can cannot resuse it. You need to read the ISO C 1999 standard 7.15. With all GCC supported platforms except PowerPC, and now AMD64 you can get away with va_list copies via a simple '=' assignment. Now when you want a copy you either have to use va_copy() [think about why you have to use strcpy for two 'char *' vs. '=']. Or, va_end and do another va_start, which would be cleaner in your case. See /usr/src/sbin/dump/optr.c:msg() for an example of the correct way to do it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:06:05 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 03DE216A4CE; Wed, 16 Feb 2005 06:06:05 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2FF243D2D; Wed, 16 Feb 2005 06:06:04 +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 j1G661X0007187; Tue, 15 Feb 2005 22:06:01 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G660FX007185; Tue, 15 Feb 2005 22:06:00 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 22:06:00 -0800 From: "David O'Brien" To: Pav Lucistnik Message-ID: <20050216060600.GB2900@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> <1108516734.1564.6.camel@hood.oook.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1108516734.1564.6.camel@hood.oook.cz> 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: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 06:06:05 -0000 On Wed, Feb 16, 2005 at 02:18:54AM +0100, Pav Lucistnik wrote: > Roman Neuhauser p??e v st 16. 02. 2005 v 01:21 +0100: > > This reminds me I wanted to raise this question: What is the > > recommended chipset for an athlon64 (either 754 or 939)? > > Taking all the problems people head from nForce crowd, I'd suggest > VIA KT800, only remaining offering on the market.. There are also SiS and ALi based motherboards. I haven't heard of any problems with them. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:11:22 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 6E64416A4CE for ; Wed, 16 Feb 2005 06:11:22 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15E8C43D3F for ; Wed, 16 Feb 2005 06:11:22 +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 j1G6BKLe007359; Tue, 15 Feb 2005 22:11:20 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G6BDQe007352; Tue, 15 Feb 2005 22:11:13 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 22:11:13 -0800 From: "David O'Brien" To: Scott Long Message-ID: <20050216061113.GC2900@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <2fd864e050215181374d2e2b1@mail.gmail.com> <4212B0BC.5060409@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4212B0BC.5060409@samsco.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 cc: Jan Mikkelsen cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "AsusA8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 06:11:22 -0000 On Tue, Feb 15, 2005 at 07:32:28PM -0700, Scott Long wrote: > Astrodog wrote: > > >On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen > > wrote: > > > >>David O'Brien wrote: > >> > >>>>(Incidentally, does anyone know anything about the HP DL385, or the HP > >>>>Opteron blades, the BL25p and BL35p?) > >>> > >>>The *5 machines are opteron versions of the Xeon offerings. See the *0 > >>>Xeon offerings to get a feel for the specs of the box. > >>>I *believe* the DL385 uses the DL380 chassis. > >> > >>I am also interested in the chipsets they use. > >> > >>I believe the DL145 uses the AMD 8000 chipset, but I can't find any > >>information on the newer servers. I was concerned that they might use > >>nVidia chipsets, like the new workstation. However, on rereading the > >>press release, they only tout the nVidia chipset for the workstation, so > >>the servers probably use something much more boring! > >> > >>Regards, > >> > >>Jan. > > > > > >I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. > > The literature for the Via K8T890 claims that it supports up to 2 CPUs, I have no idea why they make that statment. A 2P K8T890 should look simular: | | |HT[2] |HT[2] | | |--+--| cHT[0] |--+--| | BSP +---------+ AP | |--+--| |--+--| | | |HT[1] | HT[1] | | /-+--\ |VIA | |PCIe| |Tunnel| \---+--/ | | VIA V-Link | /---------------\ |VIA southbridge| \---------------/ Neither of the VIA I/O controllers should have any idea how many CPU's are in the system. > but I've only seen single-CPU boards based on it. In reality, since the > bridge between the northbridge and the CPU is HyperTransport, the > support for SMP comes more from that motherboard maker than from the > chipset maker. s/more/100%/ -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:13: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 DA2C616A4CE for ; Wed, 16 Feb 2005 06:13:01 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A37C743D46 for ; Wed, 16 Feb 2005 06:13:01 +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 j1G6D1h2007432; Tue, 15 Feb 2005 22:13:01 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G6D082007431; Tue, 15 Feb 2005 22:13:00 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 22:13:00 -0800 From: "David O'Brien" To: Doug White Message-ID: <20050216061300.GD2900@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215184118.B32860@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050215184118.B32860@carver.gumbysoft.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: Jan Mikkelsen cc: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi" or"Gigabyte K8NXP-SLI" mobos?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 06:13:02 -0000 On Tue, Feb 15, 2005 at 06:43:48PM -0800, Doug White wrote: > AMD-8131 is a generic HT-PCIX bridge. Its likely an 8111 chipset, which > works fine. The AMD 8111 is a specfic chip of the AMD 8100 chipset. Not the name of the chipset as a whole. The 8111 is the AMD HyperTransport southbridge. 8131 and 8132 are PCI-X controllers (not sure what you mean by generic above), and 8151 an 8x AGP controller. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:13: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 99A1A16A4CE for ; Wed, 16 Feb 2005 06:13:40 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6226243D1F for ; Wed, 16 Feb 2005 06:13:40 +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 j1G6DeYW007475; Tue, 15 Feb 2005 22:13:40 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1G6Dd1I007474; Tue, 15 Feb 2005 22:13:39 -0800 (PST) (envelope-from obrien) Date: Tue, 15 Feb 2005 22:13:39 -0800 From: "David O'Brien" To: Joseph Koshy Message-ID: <20050216061339.GE2900@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050215231416.449c8695.mark@hyow.eu.org> <84dead720502151902778f893c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84dead720502151902778f893c@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: Mark Magiera cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 06:13:40 -0000 On Wed, Feb 16, 2005 at 03:02:07AM +0000, Joseph Koshy wrote: > > My main, if not only problem is the NIC being so unreliable. > You may want to upgrade to 5.3-STABLE. > I installed 5.3-RELEASE on an ASUS K8V (which has the same > NIC). I kept the following loop running in the background > > while :; do > sleep 20 > ifconfig sk0 down > ifconfig sk0 up > done > > this kept the network driver usable while I downloaded > the -stable tree. Great advice. Thanks! -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 06:50: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 768F616A4CE for ; Wed, 16 Feb 2005 06:50:17 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B049443D2D for ; Wed, 16 Feb 2005 06:50:15 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.192] [213.112.167.192]) by mxfep01.bredband.com with ESMTP id <20050216065014.CXMB17717.mxfep01.bredband.com@[192.168.245.231]> for ; Wed, 16 Feb 2005 07:50:14 +0100 Message-ID: <4212EC72.4030505@bredband.net> Date: Wed, 16 Feb 2005 07:47:14 +0100 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <2fd864e050215181374d2e2b1@mail.gmail.com> <20050216032425.GB2966@dragon.nuxi.com> In-Reply-To: <20050216032425.GB2966@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: NVidia chipsets (was Re: Any experience with "AsusA8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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, 16 Feb 2005 06:50:17 -0000 David O'Brien wrote: > On Tue, Feb 15, 2005 at 08:13:30PM -0600, Astrodog wrote: > >>On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen >> wrote: >> >>I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. > > Note that the HP dual-processor workstation doesn't use the AMD chipset, > yet is MP. (Opteron's also aren't SMP, but are a NUMA architecture) > NUMA is the opposite of UMA ( Uniform Memory Architecture) not the opposite of SMP. I see SMP as an oppsite of GRID-clusters like Beowulf. These days a NUMA architecture is radically faster than a UMA architecture ( like INTEL PC's ) because the time to transfer data to/from RAM is 50 NS on an Opteron board compared to 90 NS on an Pentium/frontside-bus board. Anyone, 10 years ago, saying that NUMA is faster than UMA would have been looked at as out of his mind. //Lars From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 07:39:46 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 CE6E316A4CE; Wed, 16 Feb 2005 07:39:46 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E63343D39; Wed, 16 Feb 2005 07:39:45 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1G7dh6S076168; Wed, 16 Feb 2005 09:39:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 95342-09; Wed, 16 Feb 2005 09:39:42 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1G7dgHa076165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2005 09:39:42 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1G7dlJg053753; Wed, 16 Feb 2005 09:39:47 +0200 (EET) (envelope-from ru) Date: Wed, 16 Feb 2005 09:39:46 +0200 From: Ruslan Ermilov To: "David O'Brien" Message-ID: <20050216073946.GC52752@ip.net.ua> References: <20050215141155.GA29160@gattaca.yadt.co.uk> <20050215195517.GA17904@ip.net.ua> <20050215234825.GA96584@dragon.nuxi.com> <20050216000428.GC24447@ip.net.ua> <20050216002600.GA97906@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: <20050216002600.GA97906@dragon.nuxi.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@freebsd.org Subject: Re: Cross compiling for i386 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, 16 Feb 2005 07:39:46 -0000 --ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 04:26:00PM -0800, David O'Brien wrote: > On Wed, Feb 16, 2005 at 02:04:28AM +0200, Ruslan Ermilov wrote: > > On Tue, Feb 15, 2005 at 03:48:25PM -0800, David O'Brien wrote: > > > On Tue, Feb 15, 2005 at 09:55:17PM +0200, Ruslan Ermilov wrote: > > > > On Tue, Feb 15, 2005 at 02:11:55PM +0000, David Taylor wrote: > > > > > Is this supposed to be possible/supported? And does anyone have = any ideas > > > > > how to make it work more automatically? > > > >=20 > > > > No, this is not supported at all. What's supported is mounting i38= 6's > > > > /, /usr, and /var onto /mnt, /mnt/usr, and /mnt/var, and doing the > > > > installworld with DESTDIR=3D/mnt from amd64. > > >=20 > > > This isn't "supported" either. It happens to work most of the time. > > > But isn't a guaranteed by The FreeBSD Project. > >=20 > > Cross-built binaries should be fine. Some data files generated by > > host tools may be corrupt due to endianness and type width issues > > (e.g., "long" is 8 bytes on amd64 but only 4 bytes on i386). > >=20 > > Last time I tried installing Alpha world + kernel generated by i386, > > the only things I've noticed broken were NLS catalogs and locale > > related data files. >=20 > Yes, and that in my book means "some brokenness" and not offically > supported (ie, to be depended on). > =20 I'm not arguing, just explaining what specifically is broken. :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCEvjCqRfpzJluFF4RAoQdAKCWSGmODyfiYPpOuQj/z4JZKY+kWACgiwWJ lQi4p3fsjaljiiJ1Uj5BUGc= =jKt+ -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 10:35:28 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 C3FFD16A4CE for ; Wed, 16 Feb 2005 10:35:28 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B95F43D53 for ; Wed, 16 Feb 2005 10:35:28 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 2B4E13000B62 for ; Wed, 16 Feb 2005 11:35:27 +0100 (CET) Message-ID: <421321F9.6010003@mail.uni-mainz.de> Date: Wed, 16 Feb 2005 11:35:37 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050202 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> In-Reply-To: <20050215180011.GD38158@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 16 Feb 2005 10:35:28 -0000 David O'Brien schrieb: > >Stop supporting nVidia by buying nForce-based motherboards. Or complain >to nVidia that they (1) won't give us docs even under NDA, (2) won't >provide a FreeBSD driver like they do for Linux. These mailing lists are >filled with all the problems of nForce motherboards, yet FreeBSD users >keep buying them... > > > That sounds bad! Is there a way how we can please nVidia to offer a more FreeBSD-friendly policy? nForce4 based AMD64 boards are said to be the fastest and best choice for AMD64 based systems. It sounds disappointing that the only supported operating system is Linux (speaking as of OpenSource operating systems). Oliver From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 11:14:52 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 ACB2E16A4CE for ; Wed, 16 Feb 2005 11:14:52 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0003243D31 for ; Wed, 16 Feb 2005 11:14:51 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd10.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1D1M3n-000484-00; Wed, 16 Feb 2005 11:05:31 +0100 Received: from Andro-Beta.Leidinger.net (V8h000ZEoeeRucwTbCBCo8hEI7r1L7Mt9+jL5xC9oXKL1Q3EII9ycj@[84.128.198.180]) by fmrl10.sul.t-online.com with esmtp id 1D1M3P-18noky0; Wed, 16 Feb 2005 11:05:07 +0100 Received: from localhost (localhost [127.0.0.1])j1GA4Y9u049617; Wed, 16 Feb 2005 11:04:34 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (Horde) with HTTP for ; Wed, 16 Feb 2005 11:04:34 +0100 Message-ID: <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> X-Priority: 3 (Normal) Date: Wed, 16 Feb 2005 11:04:34 +0100 From: Alexander Leidinger To: Attila Nagy References: <41F62EE7.6070808@fsn.hu><41FBFF17.1020007@fsn.hu> <420B3DB6.4000108@fsn.hu> <20050211105748.57k9dhldxwo0k4g8@netchild.homeip.net> <420C895D.5020604@fsn.hu> <20050211122428.0twm821xa8occss8@netchild.homeip.net> <420C970B.3000003@fsn.hu> <20050215160726.hitn7zgao0kk80ks@netchild.homeip.net> <42130C00.20703@fsn.hu> In-Reply-To: <42130C00.20703@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.2) / FreeBSD-4.11 X-ID: V8h000ZEoeeRucwTbCBCo8hEI7r1L7Mt9+jL5xC9oXKL1Q3EII9ycj@t-dialin.net X-TOI-MSGID: 90d672ff-c452-4269-9af9-1dac1a51ac29 cc: amd64@freebsd.org Subject: kernel message while running icc-em64t (was: Re: FreeBSD and icc) 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, 16 Feb 2005 11:14:52 -0000 Attila Nagy wrote: > Oh, I forgot to tell in my previous email: > > helen# icc -V ; dmesg | tail -2 > Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > FOR NON-COMMERCIAL USE ONLY > > iccbin: Command line error: no files specified; for help type "iccbin -help" > fpudna: fpcurthread == curthread 2341 times > fpudna: fpcurthread == curthread 2342 times > helen# icc -V ; dmesg | tail -2 > Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > FOR NON-COMMERCIAL USE ONLY > > iccbin: Command line error: no files specified; for help type "iccbin -help" > fpudna: fpcurthread == curthread 2342 times > fpudna: fpcurthread == curthread 2343 times > > icpc triggers the same. That's a message from the kernel. amd64@ CCed for this purpose. Regarding the issue in the previous mail: I've an idea I have to verify first. If I'm right with the idea, I will send an updated port to you for testing soon. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Good day for a change of scene. Repaper the bedroom wall. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 11:44: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 D19C416A4CF for ; Wed, 16 Feb 2005 11:44:19 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32AA843D5A for ; Wed, 16 Feb 2005 11:44:19 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so80842rnf for ; Wed, 16 Feb 2005 03:44:18 -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=ZcD0fj04oWoXYmTxalLdpVgGB3VrncU2/s69hjXOdKBu+7c2JvM8HLjl/wDFH2dks7idYCBtO8HCMAbQfjKupmWs1sYu4h/MrZuZlIfuouYx3wOcNjIg67HVh9R3ThdvhbvxyglV6yq7tQ3zcPLn5EdnO8dbCt72xB3S43/Teis= Received: by 10.38.208.17 with SMTP id f17mr89099rng; Wed, 16 Feb 2005 03:44:18 -0800 (PST) Received: by 10.38.209.12 with HTTP; Wed, 16 Feb 2005 03:44:18 -0800 (PST) Message-ID: <84dead7205021603445155fafc@mail.gmail.com> Date: Wed, 16 Feb 2005 11:44:18 +0000 From: Joseph Koshy To: obrien@freebsd.org In-Reply-To: <20050216060600.GB2900@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> <1108516734.1564.6.camel@hood.oook.cz> <20050216060600.GB2900@dragon.nuxi.com> cc: Pav Lucistnik cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 11:44:20 -0000 > There are also SiS and ALi based motherboards. I haven't heard of any > problems with them. I tried FreeBSD on an ASUS K8S-MX which is based on the SiS SiS760GX and 965L chipsets. Our ATA driver had problems with UDMA modes with the 965 chipset; it only worked in PIO4 mode. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 12:08: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 E87C516A4CE for ; Wed, 16 Feb 2005 12:08:43 +0000 (GMT) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6312C43D1F for ; Wed, 16 Feb 2005 12:08:43 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 3FFB884451; Wed, 16 Feb 2005 13:08:42 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10871-01; Wed, 16 Feb 2005 13:08:35 +0100 (CET) Received: from [172.16.129.72] (japan.axelero.com [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTP id B3DE684446; Wed, 16 Feb 2005 13:08:34 +0100 (CET) Message-ID: <421337C2.7040800@fsn.hu> Date: Wed, 16 Feb 2005 13:08:34 +0100 From: Attila Nagy User-Agent: Mozilla Thunderbird 1.0 (X11/20050103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <41F62EE7.6070808@fsn.hu> <20050129110130.78983fa5@Magellan.Leidinger.net> <41FBFF17.1020007@fsn.hu> <20050130122414.3741452d@Magellan.Leidinger.net> <420B3DB6.4000108@fsn.hu> <20050211105748.57k9dhldxwo0k4g8@netchild.homeip.net> <420C895D.5020604@fsn.hu> <20050211122428.0twm821xa8occss8@netchild.homeip.net> <420C970B.3000003@fsn.hu> <20050215160726.hitn7zgao0kk80ks@netchild.homeip.net> <42130C00.20703@fsn.hu> <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> In-Reply-To: <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu cc: amd64@freebsd.org Subject: Re: kernel message while running icc-em64t 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, 16 Feb 2005 12:08:44 -0000 Alexander Leidinger wrote: >> helen# icc -V ; dmesg | tail -2 >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. >> FOR NON-COMMERCIAL USE ONLY >> >> iccbin: Command line error: no files specified; for help type "iccbin >> -help" >> fpudna: fpcurthread == curthread 2341 times >> fpudna: fpcurthread == curthread 2342 times >> helen# icc -V ; dmesg | tail -2 >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. >> FOR NON-COMMERCIAL USE ONLY >> >> iccbin: Command line error: no files specified; for help type "iccbin >> -help" >> fpudna: fpcurthread == curthread 2342 times >> fpudna: fpcurthread == curthread 2343 times >> >> icpc triggers the same. > That's a message from the kernel. amd64@ CCed for this purpose. To clarify what's this: Alexander sent me a icc-em64t port, which should make Intel's C compiler work on FreeBSD/AMD64 to produce EM64T (AMD64) code. It is based on the EM64T version of the compiler, which is in fact a 32 bit Linux binary. When I invoke icc, or icpc (the C++ compiler) I get the above kernel messages. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Adopt a directory on our free software phone @work: +361 371 3536 server! http://www.fsn.hu/?f=brick cell.: +3630 306 6758 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 16:01: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 714F916A4CE for ; Wed, 16 Feb 2005 16:01:20 +0000 (GMT) Received: from beastie.hyow.eu.org (beastie.hyow.eu.org [213.152.46.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3501743D1D for ; Wed, 16 Feb 2005 16:01:19 +0000 (GMT) (envelope-from mark@hyow.eu.org) Received: (qmail 30168 invoked by uid 751); 16 Feb 2005 16:02:43 +0000 Received: from mark@hyow.eu.org by beastie.hyow.eu.org by uid 731 with qmail-scanner-1.22-st-qms Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 11.364104 secs); 16 Feb 2005 16:02:43 -0000 X-Spam-Status: No, hits=-2.8 required=5.0 X-Antivirus-HYOW.EU.ORG-Mail-From: mark@hyow.eu.org via beastie.hyow.eu.org X-Antivirus-HYOW.EU.ORG: 1.22-st-qms (Clear:RC:0(10.0.0.11):SA:0(-2.8/5.0):. Processed in 11.364104 secs Process 30162) Received: from deity.hyow.eu.org (mark@hyow.eu.org@10.0.0.11) by beastie.hyow.eu.org with AES256-SHA encrypted SMTP; 16 Feb 2005 16:02:31 +0000 Date: Wed, 16 Feb 2005 16:01:14 +0000 From: Mark Magiera To: freebsd-amd64@freebsd.org Message-Id: <20050216160114.647afdb1.mark@hyow.eu.org> In-Reply-To: <20050216061339.GE2900@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050215231416.449c8695.mark@hyow.eu.org> <84dead720502151902778f893c@mail.gmail.com> <20050216061339.GE2900@dragon.nuxi.com> X-Mailer: Sylpheed version 1.0.0-gtk2-20041224 (GTK+ 2.4.14; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 16 Feb 2005 16:01:20 -0000 On Tue, 15 Feb 2005 22:13:39 -0800 "David O'Brien" wrote: > On Wed, Feb 16, 2005 at 03:02:07AM +0000, Joseph Koshy wrote: > > > My main, if not only problem is the NIC being so unreliable. > > You may want to upgrade to 5.3-STABLE. > > I installed 5.3-RELEASE on an ASUS K8V (which has the same > > NIC). I kept the following loop running in the background > > > > while :; do > > sleep 20 > > ifconfig sk0 down > > ifconfig sk0 up > > done > > > > this kept the network driver usable while I downloaded > > the -stable tree. > > Great advice. Thanks! Indeed, thank you very much. -stable here I come :) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:02:02 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 D171016A4CE; Wed, 16 Feb 2005 17:02:02 +0000 (GMT) Received: from dswu28.btconnect.com (dswu28.btconnect.com [193.113.154.29]) by mx1.FreeBSD.org (Postfix) with SMTP id D1D3B43D46; Wed, 16 Feb 2005 17:02:01 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from AJDELL9200 (actually host 55.4.36.213.in-addr.arpa) by dswu28.btconnect.com with SMTP (XT-PP) with ESMTP; Wed, 16 Feb 2005 17:01:52 +0000 From: "Alan Jay" To: Date: Wed, 16 Feb 2005 16:56:55 -0000 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcUTg1zjuojWkFsSTU6saBKGy90WxQAEcN1A X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20050215172530.GC38158@dragon.nuxi.com> Message-Id: <20050216170201.D1D3B43D46@mx1.FreeBSD.org> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: "'Jonathan A. Dama'" Subject: RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard (2) 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, 16 Feb 2005 17:02:03 -0000 > -----Original Message----- > From: David O'Brien [mailto:obrien@freebsd.org] > > On Tue, Feb 15, 2005 at 04:53:24PM -0000, Alan Jay wrote: > > I had major problems installing with more than 4Gb but once I moved to > stable > > we seemed to have a stable platform when doing basic stuff - we have two > > databases (mySQL) one is reasonably heavily used and one very extensively > > used. > > Just to be clear, you're stating you had stability problems with > 5.3-RELEASE and >4GB. But with 5.3-STABLE and >4GB you have a stable > system. Correct? [Alan Jay] Further to my comments yesterday - I would say that the system appeared to be stable. It is possible that when we ran a more extensive and more often hit database that it used more memory and that is what caused the problem. BUT all the tests we did relating to memory didn't turn up any issues - so we looked for other culprits. One of the few errors we saw was relating to the Broadcom Gigabit link - I will try to do some tests in the next week or so using the other onboard Ethernet controller to see if that rules out the Broadcom or focuses the cause of the problem. > > I think I agree wholeheartedly with your comments being a great supporter > of > > FreeBSD it is a shame that the AMD release is not as super as the other > > versions we have used extensively. > > Of course one reason many are moving to the AMD64 platform is to have > >4GB RAM in the machine. We believe this bug has been fixed in > 5.3-STABLE. But too few people are testing 5.3-STABLE and are using > 5.3-RELEASE instead. This isn't helping us QA the issue so that we know > all the corner cases are fixed in upcoming 5.4 release. [Alan Jay] Thanks for this and it was exactly the reason we moved to the AMD64 platform. > A recent 5.3-STABLE snapshot can be found as > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001- > amd64-miniinst.iso > and mirrors. > > -- > -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:33: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 04AF916A4CE for ; Wed, 16 Feb 2005 17:33:03 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CCA443D48 for ; Wed, 16 Feb 2005 17:33:02 +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 j1GHWw5F082697; Wed, 16 Feb 2005 09:32:58 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1GHWwaL082695; Wed, 16 Feb 2005 09:32:58 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2005 09:32:54 -0800 From: "David O'Brien" To: Lars Tunkrans Message-ID: <20050216173254.GA81923@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <2fd864e050215181374d2e2b1@mail.gmail.com> <20050216032425.GB2966@dragon.nuxi.com> <4212EC72.4030505@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4212EC72.4030505@bredband.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: NVidia chipsets (was Re: Any experience with "AsusA8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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: Wed, 16 Feb 2005 17:33:03 -0000 On Wed, Feb 16, 2005 at 07:47:14AM +0100, Lars Tunkrans wrote: > David O'Brien wrote: > >On Tue, Feb 15, 2005 at 08:13:30PM -0600, Astrodog wrote: > > > >>On Wed, 16 Feb 2005 12:14:14 +1100, Jan Mikkelsen > >> wrote: > > >>I'm not sure anyone but AMD makes SMP-capible chipsets for Opteron. > > > >Note that the HP dual-processor workstation doesn't use the AMD chipset, > >yet is MP. (Opteron's also aren't SMP, but are a NUMA architecture) > > NUMA is the opposite of UMA ( Uniform Memory Architecture) not the > opposite of SMP. > I see SMP as an oppsite of GRID-clusters like Beowulf. You're the only one then. Google for "smp numa". Most in the NUMA world treat SMP the opposite. ccNUMA (cache-coherent) isn't "symmetric" in its memory latency or I/O paths, thus not SMP. FreeBSD treats MP Opteron as SMP. Note that a single package(socket) AMD dual-core CPU is indeed SMP. http://whatis.techtarget.com/definition/0,,sid9_gci212678,00.html An SMP system is a "tightly-coupled," "share everything" system in which multiple processors working under a single operating system access each other's memory over a common bus or "interconnect" path. This does not define a NUMA system. A 2nd source: http://lse.sourceforge.net/numa/faq/ 3. What is the difference between NUMA and SMP? The NUMA architecture was designed to surpass the scalability limits of the SMP architecture. With SMP, which stands for Symmetric Multi-Processing, all memory access are posted to the same shared memory bus. While technically correct about "UMA" (remove the 'N' in NUMA and "UMA" is what you get). In the AMD64 context, UMA, mean on-board graphics and the "unified" speaks of video RAM and system RAM. > These days a NUMA architecture is radically faster than a UMA architecture .. > Anyone, 10 years ago, saying that NUMA > is faster than UMA > would have been looked at as out of his mind. Uh, no. You design a NUMA architecture exactly to get some very fast memory to processors. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:40:10 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 569F216A4CE for ; Wed, 16 Feb 2005 17:40:10 +0000 (GMT) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D20243D41 for ; Wed, 16 Feb 2005 17:40:09 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx6.fuse.net ([216.196.253.14]) by smtp1.fuse.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050216173754.GLUR20052.smtp1.fuse.net@gx6.fuse.net> for ; Wed, 16 Feb 2005 12:37:54 -0500 Received: from ramen.cokane.org ([216.196.253.14]) by gx6.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20050216173633.QUAO22756.gx6.fuse.net@ramen.cokane.org> for ; Wed, 16 Feb 2005 12:36:33 -0500 Received: (qmail 99820 invoked by uid 1001); 16 Feb 2005 13:47:31 -0000 Date: Wed, 16 Feb 2005 13:47:31 +0000 From: Coleman Kane To: David O'Brien Message-ID: <20050216134731.GB99724@ramen> References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> <346a80220502151437627a9ef6@mail.gmail.com> <200502160027.55420.jkim@niksun.com> <20050216055348.GA6793@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline In-Reply-To: <20050216055348.GA6793@dragon.nuxi.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 17:40:10 -0000 --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I will try this out on thursday. The owner of the laptop is not at school today. FYI, I applied John's Kim-derived Mega-patch and realized this was missing. It died without atpic. After adding atpic, I was able to make it work. One question, does MIXED_MODE require atpic to be built-in? It seems like you are using the mixed_mode flag to enable this fix here. Also, there is another patch missing. The following allows you to use=20 PCCARD devices to work. I found this email: http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003365.ht= ml Which has the problem detailed. Without this, the IO ranges attached to the PCCARD devices asre screwed up, and thus you cannot use them. -- coleman On Tue, Feb 15, 2005 at 09:53:48PM -0800, David O'Brien wrote, and it was p= roclaimed: > On Wed, Feb 16, 2005 at 12:27:55AM -0500, Jung-uk Kim wrote: > > On Tuesday 15 February 2005 05:37 pm, Coleman Kane wrote: > > > Hi, I tested the patch posted by John on a compaq R3000. Works > > > great, except still requires device atpic (for the mixed_mode > > > operation I think). Kim posted a patch in this email: > > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/00337 > > >6.html. I dunno if the patch is kosher or not, however. It does > > > allow me to run without using atpic. > >=20 > > Ouch, you're absolutely correct. jhb's patch wasn't complete for=20 > > amd64. The missing piece is attached. Can you please re-test? >=20 > Can we remove "device atpic" from GENERIC with this? > Can an inflicted user try it out so we can add that change to the patch > also? >=20 > --=20 > -- David (obrien@FreeBSD.org) --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCE07zuDFwFZcwSdoRAjCbAJ0al8LVcSHqS848xCqTQYPWoi1H6QCeMk4I 07XTy93/LUCv4YYyK79qaj4= =qk/R -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:40: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 5F84616A4CE; Wed, 16 Feb 2005 17:40:45 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 247E643D53; Wed, 16 Feb 2005 17:40:44 +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 j1GHeauU083034; Wed, 16 Feb 2005 09:40:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1GHeVYe083031; Wed, 16 Feb 2005 09:40:31 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2005 09:40:31 -0800 From: "David O'Brien" To: Joseph Koshy Message-ID: <20050216174031.GB82895@dragon.nuxi.com> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> <1108516734.1564.6.camel@hood.oook.cz> <20050216060600.GB2900@dragon.nuxi.com> <84dead7205021603445155fafc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84dead7205021603445155fafc@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: Pav Lucistnik cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 17:40:45 -0000 On Wed, Feb 16, 2005 at 11:44:18AM +0000, Joseph Koshy wrote: > > There are also SiS and ALi based motherboards. I haven't heard of any > > problems with them. > > I tried FreeBSD on an ASUS K8S-MX which is based on the SiS > SiS760GX and 965L chipsets. Our ATA driver had problems with > UDMA modes with the 965 chipset; it only worked in PIO4 mode. Can you try ATA-mkIII? Otherwise can you report the issue to Soren? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:46:05 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 DD4D016A4CE; Wed, 16 Feb 2005 17:46:05 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7B6743D48; Wed, 16 Feb 2005 17:46:05 +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 j1GHjZcD083328; Wed, 16 Feb 2005 09:45:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1GHjUQq083321; Wed, 16 Feb 2005 09:45:30 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2005 09:45:30 -0800 From: "David O'Brien" To: Coleman Kane Message-ID: <20050216174530.GD82895@dragon.nuxi.com> References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> <346a80220502151437627a9ef6@mail.gmail.com> <200502160027.55420.jkim@niksun.com> <20050216055348.GA6793@dragon.nuxi.com> <20050216134731.GB99724@ramen> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050216134731.GB99724@ramen> 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: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 17:46:06 -0000 On Wed, Feb 16, 2005 at 01:47:31PM +0000, Coleman Kane wrote: > Also, there is another patch missing. The following allows you to use > PCCARD devices to work. I found this email: > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003365.html > > Which has the problem detailed. Without this, the IO ranges attached to the > PCCARD devices asre screwed up, and thus you cannot use them. But this patch has nothing to do with the ATPIC issue (that I can see). So it should be left out of jhb's patch. Also that patch isn't in a committable form. Can someone make it in a commitable form and I'll commit it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:55:52 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 363DA16A4CE for ; Wed, 16 Feb 2005 17:55:52 +0000 (GMT) Received: from smtp3.fuse.net (mail-out3.fuse.net [216.68.8.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8249443D45 for ; Wed, 16 Feb 2005 17:55:51 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx4.fuse.net ([216.196.253.14]) by smtp3.fuse.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050216175253.NMM10020.smtp3.fuse.net@gx4.fuse.net> for ; Wed, 16 Feb 2005 12:52:53 -0500 Received: from ramen.cokane.org ([216.196.253.14]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20050216175356.RIFZ13848.gx4.fuse.net@ramen.cokane.org> for ; Wed, 16 Feb 2005 12:53:56 -0500 Received: (qmail 99900 invoked by uid 1001); 16 Feb 2005 14:03:14 -0000 Date: Wed, 16 Feb 2005 14:03:14 +0000 From: Coleman Kane To: David O'Brien Message-ID: <20050216140314.GD99724@ramen> References: <200502141722.10259.jhb@FreeBSD.org> <200502151659.42594.nb_root@videotron.ca> <346a80220502151437627a9ef6@mail.gmail.com> <200502160027.55420.jkim@niksun.com> <20050216055348.GA6793@dragon.nuxi.com> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uxuisgdDHaNETlh8" Content-Disposition: inline In-Reply-To: <20050216174530.GD82895@dragon.nuxi.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 17:55:52 -0000 --uxuisgdDHaNETlh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Oh, okay it doesn't have anything to do with that, yes. I think this is also another nforce across-the-board fix. What is not commitable about it? I was able to apply it to -current just fine. Sorry, I've been out of the style loop for some time. -- coleman On Wed, Feb 16, 2005 at 09:45:30AM -0800, David O'Brien wrote, and it was p= roclaimed: >=20 > But this patch has nothing to do with the ATPIC issue (that I can see). > So it should be left out of jhb's patch. Also that patch isn't in a > committable form. Can someone make it in a commitable form and I'll > commit it. >=20 > --=20 > -- David (obrien@FreeBSD.org) --uxuisgdDHaNETlh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCE1KiuDFwFZcwSdoRAlzvAJ9DLZQPcXe6vAivydXxGT+hG/qOIACdFcWP pSwtXaNHMGqm+UYQ+liLZQk= =sltM -----END PGP SIGNATURE----- --uxuisgdDHaNETlh8-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 17:57: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 54A6016A4CE; Wed, 16 Feb 2005 17:57:15 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 898D143D31; Wed, 16 Feb 2005 17:57:12 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1GHua9c052456; Wed, 16 Feb 2005 12:56:37 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: obrien@freebsd.org Date: Wed, 16 Feb 2005 12:56:34 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> In-Reply-To: <20050216174530.GD82895@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502161256.34505.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org cc: Coleman Kane Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 17:57:15 -0000 On Wednesday 16 February 2005 12:45 pm, David O'Brien wrote: > On Wed, Feb 16, 2005 at 01:47:31PM +0000, Coleman Kane wrote: > > Also, there is another patch missing. The following allows you to > > use PCCARD devices to work. I found this email: > > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January > >/003365.html > > > > Which has the problem detailed. Without this, the IO ranges > > attached to the PCCARD devices asre screwed up, and thus you > > cannot use them. > > But this patch has nothing to do with the ATPIC issue (that I can > see). So it should be left out of jhb's patch. Also that patch > isn't in a committable form. Can someone make it in a commitable > form and I'll commit it. All you need is the second hunk, which is commitable, I believe. The first hunk has to be fixed from BIOS or manually corrected by: pciconf -w -b pci0:10:0 0x1a 0x0a Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 18:00:46 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 165B316A4D0 for ; Wed, 16 Feb 2005 18:00:46 +0000 (GMT) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B39643D53 for ; Wed, 16 Feb 2005 18:00:45 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx4.fuse.net ([216.196.253.14]) by smtp1.fuse.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050216175831.GUWT20052.smtp1.fuse.net@gx4.fuse.net> for ; Wed, 16 Feb 2005 12:58:31 -0500 Received: from ramen.cokane.org ([216.196.253.14]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20050216175849.RIXN13848.gx4.fuse.net@ramen.cokane.org> for ; Wed, 16 Feb 2005 12:58:49 -0500 Received: (qmail 99936 invoked by uid 1001); 16 Feb 2005 14:08:08 -0000 Date: Wed, 16 Feb 2005 14:08:08 +0000 From: Coleman Kane To: Jung-uk Kim Message-ID: <20050216140808.GF99724@ramen> References: <200502141722.10259.jhb@FreeBSD.org> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> <200502161256.34505.jkim@niksun.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hUH5gZbnpyIv7Mn4" Content-Disposition: inline In-Reply-To: <200502161256.34505.jkim@niksun.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 18:00:46 -0000 --hUH5gZbnpyIv7Mn4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yeah the recipient of the fix just emailed me about this, I am guessing that the #if 0 is the uncommitable part. Is there any way that this can be done by the kernel (the PCI reg write, that is)? Is there any reason that it can't be done there? On Wed, Feb 16, 2005 at 12:56:34PM -0500, Jung-uk Kim wrote, and it was pro= claimed: > On Wednesday 16 February 2005 12:45 pm, David O'Brien wrote: > > On Wed, Feb 16, 2005 at 01:47:31PM +0000, Coleman Kane wrote: > > > Also, there is another patch missing. The following allows you to > > > use PCCARD devices to work. I found this email: > > > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January > > >/003365.html > > > > > > Which has the problem detailed. Without this, the IO ranges > > > attached to the PCCARD devices asre screwed up, and thus you > > > cannot use them. > > > > But this patch has nothing to do with the ATPIC issue (that I can > > see). So it should be left out of jhb's patch. Also that patch > > isn't in a committable form. Can someone make it in a commitable > > form and I'll commit it. >=20 > All you need is the second hunk, which is commitable, I believe. The=20 > first hunk has to be fixed from BIOS or manually corrected by: >=20 > pciconf -w -b pci0:10:0 0x1a 0x0a >=20 > Jung-uk Kim --hUH5gZbnpyIv7Mn4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCE1PIuDFwFZcwSdoRAm7YAKCLrcTBnAyz7OtFEjFNCV8pKt4+5ACfciSL hiiwACpTfIqo3pzCIqKkrmc= =Q9Uk -----END PGP SIGNATURE----- --hUH5gZbnpyIv7Mn4-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 18:02:38 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 4B03216A4CE; Wed, 16 Feb 2005 18:02:38 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDABB43D45; Wed, 16 Feb 2005 18:02:37 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1GI1sfV052638; Wed, 16 Feb 2005 13:01:55 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Coleman Kane Date: Wed, 16 Feb 2005 13:01:51 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <20050216055348.GA6793@dragon.nuxi.com> <20050216134731.GB99724@ramen> In-Reply-To: <20050216134731.GB99724@ramen> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200502161301.51898.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 18:02:38 -0000 On Wednesday 16 February 2005 08:47 am, Coleman Kane wrote: > I will try this out on thursday. The owner of the laptop is not at > school today. FYI, I applied John's Kim-derived Mega-patch and > realized this was missing. It died without atpic. After adding > atpic, I was able to make it work. > > One question, does MIXED_MODE require atpic to be built-in? It > seems like you are using the mixed_mode flag to enable this fix > here. No, it's opposite. We turn off mixed mode and skip ioapic_set_extint(). Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 18:37:02 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 4EC9916A4CE; Wed, 16 Feb 2005 18:37:02 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7DF343D45; Wed, 16 Feb 2005 18:37:01 +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 j1GIaS4g085353; Wed, 16 Feb 2005 10:36:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1GIaStf085352; Wed, 16 Feb 2005 10:36:28 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2005 10:36:28 -0800 From: "David O'Brien" To: Coleman Kane Message-ID: <20050216183628.GB83553@dragon.nuxi.com> References: <200502141722.10259.jhb@FreeBSD.org> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050216140808.GF99724@ramen> 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: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 18:37:02 -0000 [ PLEASE don't top-post, else I may not reply. This is a Unix list. ] On Wed, Feb 16, 2005 at 02:08:08PM +0000, Coleman Kane wrote: > Yeah the recipient of the fix just emailed me about this, I am guessing > that the #if 0 is the uncommitable part. Is there any way that this can > be done by the kernel (the PCI reg write, that is)? Is there any reason > that it can't be done there? Yes, the "#if 0" in http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003365.html isn't commitable. > > All you need is the second hunk, which is commitable, I believe. The > > first hunk has to be fixed from BIOS or manually corrected by: Jung-uk, can you post another patch with just this fix? In a commitable form please. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 19:07: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 C38EC16A4CE; Wed, 16 Feb 2005 19:07:41 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3387C43D1F; Wed, 16 Feb 2005 19:07:41 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1GJ713n054778; Wed, 16 Feb 2005 14:07:02 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: obrien@freebsd.org Date: Wed, 16 Feb 2005 14:06:59 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <20050216140808.GF99724@ramen> <20050216183628.GB83553@dragon.nuxi.com> In-Reply-To: <20050216183628.GB83553@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_Tn5ECYXYqpx0fBB" Message-Id: <200502161406.59169.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org cc: Coleman Kane Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 19:07:41 -0000 --Boundary-00=_Tn5ECYXYqpx0fBB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 16 February 2005 01:36 pm, David O'Brien wrote: > [ PLEASE don't top-post, else I may not reply. This is a Unix list. > ] > > On Wed, Feb 16, 2005 at 02:08:08PM +0000, Coleman Kane wrote: > > Yeah the recipient of the fix just emailed me about this, I am > > guessing that the #if 0 is the uncommitable part. Is there any > > way that this can be done by the kernel (the PCI reg write, that > > is)? Is there any reason that it can't be done there? > > Yes, the "#if 0" in > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/0 >03365.html isn't commitable. > > > > All you need is the second hunk, which is commitable, I > > > believe. The first hunk has to be fixed from BIOS or manually > > > corrected by: > > Jung-uk, can you post another patch with just this fix? In a > commitable form please. Sure. Attached. Jung-uk Kim --Boundary-00=_Tn5ECYXYqpx0fBB Content-Type: text/plain; charset="iso-8859-1"; name="pci_pci.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pci_pci.diff" Index: pci_pci.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pci/pci_pci.c,v retrieving revision 1.33 diff -u -r1.33 pci_pci.c --- src/sys/dev/pci/pci_pci.c 1 Jul 2004 07:46:28 -0000 1.33 +++ src/sys/dev/pci/pci_pci.c 16 Feb 2005 19:04:30 -0000 @@ -319,6 +319,8 @@ start = sc->iobase; if (end > sc->iolimit) end = sc->iolimit; + if (start <= end) + ok = 1; } } else { ok = 1; --Boundary-00=_Tn5ECYXYqpx0fBB-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 19:21:48 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 C373316A4CE; Wed, 16 Feb 2005 19:21:48 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10C3F43D2D; Wed, 16 Feb 2005 19:21:48 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1GJKqSZ055312; Wed, 16 Feb 2005 14:20:53 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Coleman Kane Date: Wed, 16 Feb 2005 14:20:49 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> In-Reply-To: <20050216140808.GF99724@ramen> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502161420.49924.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 19:21:48 -0000 On Wednesday 16 February 2005 09:08 am, Coleman Kane wrote: > Yeah the recipient of the fix just emailed me about this, I am > guessing that the #if 0 is the uncommitable part. Is there any way > that this can be done by the kernel (the PCI reg write, that is)? > Is there any reason that it can't be done there? Yes, it can be done from kernel. Linux has a patch here: http://bugzilla.kernel.org/attachment.cgi?id=3324 We can do something similar but it may cause regression for us. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 19:49:34 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 9459B16A4CE; Wed, 16 Feb 2005 19:49:34 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D75E843D5E; Wed, 16 Feb 2005 19:49:33 +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 j1GJnWVB023999; Wed, 16 Feb 2005 14:49:32 -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 j1GJnTDG042886; Wed, 16 Feb 2005 14:49:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0885B7306E; Wed, 16 Feb 2005 14:49:28 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050216194928.0885B7306E@freebsd-current.sentex.ca> Date: Wed, 16 Feb 2005 14:49:28 -0500 (EST) X-Virus-Scanned: ClamAV 0.82/706/Sun Feb 13 19:14:02 2005 on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner1 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: Wed, 16 Feb 2005 19:49:34 -0000 TB --- 2005-02-16 18:45:44 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-16 18:45:44 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-02-16 18:45:44 - checking out the source tree TB --- 2005-02-16 18:45:44 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-02-16 18:45:44 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-16 18:53:42 - building world (CFLAGS=-O -pipe) TB --- 2005-02-16 18:53:42 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-16 18:53:42 - /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-16 19:46:34 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-16 19:46:34 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-16 19:46:34 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Feb 16 19:46:34 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 -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7770.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/ahc_isa.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/ahc_pci.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7xxx.c /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7xxx.c: In function `ahc_alloc': /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7xxx.c:3854: error: `ahd' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7xxx.c:3854: error: (Each undeclared identifier is reported only once /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/aic7xxx/aic7xxx.c:3854: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/GENERIC. *** 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-16 19:49:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-16 19:49:28 - ERROR: failed to build generic kernel TB --- 2005-02-16 19:49:28 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 20:27: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 96F2316A4ED for ; Wed, 16 Feb 2005 20:27:12 +0000 (GMT) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5E3343D55 for ; Wed, 16 Feb 2005 20:27:11 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx4.fuse.net ([216.196.253.14]) by smtp1.fuse.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050216202457.JUBE20052.smtp1.fuse.net@gx4.fuse.net> for ; Wed, 16 Feb 2005 15:24:57 -0500 Received: from ramen.cokane.org ([216.196.253.14]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20050216202516.SGWU13848.gx4.fuse.net@ramen.cokane.org> for ; Wed, 16 Feb 2005 15:25:16 -0500 Received: (qmail 606 invoked by uid 1001); 16 Feb 2005 16:34:34 -0000 Date: Wed, 16 Feb 2005 16:34:34 +0000 From: Coleman Kane To: Jung-uk Kim Message-ID: <20050216163434.GA577@ramen> References: <200502141722.10259.jhb@FreeBSD.org> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> <200502161420.49924.jkim@niksun.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <200502161420.49924.jkim@niksun.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 16 Feb 2005 20:27:12 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 16, 2005 at 02:20:49PM -0500, Jung-uk Kim wrote, and it was pro= claimed: > On Wednesday 16 February 2005 09:08 am, Coleman Kane wrote: > > Yeah the recipient of the fix just emailed me about this, I am > > guessing that the #if 0 is the uncommitable part. Is there any way > > that this can be done by the kernel (the PCI reg write, that is)? > > Is there any reason that it can't be done there? >=20 > Yes, it can be done from kernel. Linux has a patch here: >=20 > http://bugzilla.kernel.org/attachment.cgi?id=3D3324 >=20 > We can do something similar but it may cause regression for us. >=20 > Jung-uk Kim Don't we have a PCI quirks facility to allow us to do this, similar to how the ACPI quirks have been documented? If not, should we? -- coleman --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCE3YauDFwFZcwSdoRAmSQAJ9C24O81EfeAZ7B7paOa3itTwprzgCfdVva YF1SaZSOuQ29bXJtL/sqzCA= =FDtn -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 21:21:33 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 3EAC716A4CE for ; Wed, 16 Feb 2005 21:21:33 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 911B243D41 for ; Wed, 16 Feb 2005 21:21:30 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so183535rng for ; Wed, 16 Feb 2005 13:21:29 -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=L521d3bzCh1nBs08FJcVo4+NX12YseoxRNabuODhnn2Vb3W+B89Jio4KYWisgbazW6wSfOXcIQHVbJ2ennaelbOTaD2Ku/Y8I6KQfrQ7Z7raPYvWzjjK9qtqJQLrtTbj4HMu5IVOPoPtLGJvhiAIB4E+aoJL7+oMQBDvKxNb4eM= Received: by 10.38.218.39 with SMTP id q39mr27078rng; Wed, 16 Feb 2005 13:21:28 -0800 (PST) Received: by 10.38.22.22 with HTTP; Wed, 16 Feb 2005 13:21:27 -0800 (PST) Message-ID: <346a8022050216132169d2fee5@mail.gmail.com> Date: Wed, 16 Feb 2005 16:21:27 -0500 From: Coleman Kane To: obrien@freebsd.org In-Reply-To: <20050216183628.GB83553@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502141722.10259.jhb@FreeBSD.org> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> <20050216183628.GB83553@dragon.nuxi.com> cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 21:21:33 -0000 On Wed, 16 Feb 2005 10:36:28 -0800, David O'Brien wrote: > [ PLEASE don't top-post, else I may not reply. This is a Unix list. ] > > On Wed, Feb 16, 2005 at 02:08:08PM +0000, Coleman Kane wrote: > > Yeah the recipient of the fix just emailed me about this, I am guessing > > that the #if 0 is the uncommitable part. Is there any way that this can > > be done by the kernel (the PCI reg write, that is)? Is there any reason > > that it can't be done there? > > Yes, the "#if 0" in > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003365.html > isn't commitable. > > > All you need is the second hunk, which is commitable, I believe. The > > > first hunk has to be fixed from BIOS or manually corrected by: > > Jung-uk, can you post another patch with just this fix? In a commitable > form please. > > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > I have attached the patch with the #if 0 / #endif removed. Can anyone please enlighten me as to why the first hunk would be a 'regression'? -- coleman From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 16 21:39: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 D480916A4CE for ; Wed, 16 Feb 2005 21:39:20 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id E876443D1D for ; Wed, 16 Feb 2005 21:39:19 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so186422rng for ; Wed, 16 Feb 2005 13:39:19 -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:references; b=ItEStU03Zmky2/vyaJKK1uUd/diEYHNhlvfUrVzS9NjviGFcxmqOjDIQeTBvZsIUtNRyM/3+vB/58P/VxDYkt9JjrNQ3oeTOT5lizCcuoTRRdZgSuN63d6D8TFS0FekYYwyEyLHtlncOdniwcT1TqlqFoldmlSbsT/vQaXcIJTU= Received: by 10.38.218.39 with SMTP id q39mr39010rng; Wed, 16 Feb 2005 13:39:18 -0800 (PST) Received: by 10.38.22.22 with HTTP; Wed, 16 Feb 2005 13:39:18 -0800 (PST) Message-ID: <346a80220502161339c53acd5@mail.gmail.com> Date: Wed, 16 Feb 2005 16:39:18 -0500 From: Coleman Kane To: obrien@freebsd.org In-Reply-To: <346a8022050216132169d2fee5@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_420_9094870.1108589958816" References: <200502141722.10259.jhb@FreeBSD.org> <20050216134731.GB99724@ramen> <20050216174530.GD82895@dragon.nuxi.com> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> <20050216183628.GB83553@dragon.nuxi.com> <346a8022050216132169d2fee5@mail.gmail.com> cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 21:39:20 -0000 ------=_Part_420_9094870.1108589958816 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, 16 Feb 2005 16:21:27 -0500, Coleman Kane wrote: > > I have attached the patch with the #if 0 / #endif removed. Can anyone > please enlighten me as to why the first hunk would be a 'regression'? > > -- > coleman > No, I haven't. I don't know what happened, here it is attached for real. ------=_Part_420_9094870.1108589958816 Content-Type: application/octet-stream; name="pci_pci.c.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pci_pci.c.patch" LS0tIHNyYy9zeXMvZGV2L3BjaS9wY2lfcGNpLmMub3JpZwlUaHUgSnVsICAxIDAzOjQ2OjI4IDIw MDQKKysrIHNyYy9zeXMvZGV2L3BjaS9wY2lfcGNpLmMJU2F0IEphbiAyMiAwMToyMTo1MCAyMDA1 CkBAIC0xODUsNiArMTg1LDEwIEBACiAgICAgY2FzZSAweDA2MDUxM2Q3OgkJLyogVG9zaGliYSA/ Pz8/ICovCiAJc2MtPmZsYWdzIHw9IFBDSUJfU1VCVFJBQ1RJVkU7CiAJYnJlYWs7CisKKyAgICBj YXNlIDB4MDBkZDEwZGU6CQkvKiBYWFg6IENvbXBhcSBSMzAwMCAqLworCXBjaV93cml0ZV9jb25m aWcoZGV2LCBQQ0lSX1NVQkJVU18xLCAweGEsIDEpOworCWJyZWFrOwogICAgIH0KIAogICAgIC8q CkBAIC0zMTksNiArMzE5LDggQEAKIAkJCQkJc3RhcnQgPSBzYy0+aW9iYXNlOwogCQkJCWlmIChl bmQgPiBzYy0+aW9saW1pdCkKIAkJCQkJZW5kID0gc2MtPmlvbGltaXQ7CisJCQkJaWYgKHN0YXJ0 IDw9IGVuZCkKKwkJCQkJb2sgPSAxOwogCQkJfQogCQl9IGVsc2UgewogCQkJb2sgPSAxOwo= ------=_Part_420_9094870.1108589958816-- From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 02:42:13 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 9CE2816A4CE; Thu, 17 Feb 2005 02:42:13 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46EE143D2D; Thu, 17 Feb 2005 02:42:13 +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 j1H2fhhV017881; Wed, 16 Feb 2005 18:41: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 j1H2fgsB017880; Wed, 16 Feb 2005 18:41:42 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2005 18:41:42 -0800 From: "David O'Brien" To: Jung-uk Kim Message-ID: <20050217024142.GA13595@dragon.nuxi.com> References: <200502141722.10259.jhb@FreeBSD.org> <20050216140808.GF99724@ramen> <20050216183628.GB83553@dragon.nuxi.com> <200502161406.59169.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502161406.59169.jkim@niksun.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 cc: Coleman Kane Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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: Thu, 17 Feb 2005 02:42:13 -0000 On Wed, Feb 16, 2005 at 02:06:59PM -0500, Jung-uk Kim wrote: > Index: pci_pci.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/pci/pci_pci.c,v > retrieving revision 1.33 > diff -u -r1.33 pci_pci.c > --- src/sys/dev/pci/pci_pci.c 1 Jul 2004 07:46:28 -0000 1.33 > +++ src/sys/dev/pci/pci_pci.c 16 Feb 2005 19:04:30 -0000 > @@ -319,6 +319,8 @@ > start = sc->iobase; > if (end > sc->iolimit) > end = sc->iolimit; > + if (start <= end) > + ok = 1; Now we need some people to test this that experience the problem. Anyone? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 07:30:19 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 CAF4416A4CE for ; Thu, 17 Feb 2005 07:30:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A98943D58 for ; Thu, 17 Feb 2005 07:30:19 +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 j1H7UJSC096125 for ; Thu, 17 Feb 2005 07:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j1H7UJYN096120; Thu, 17 Feb 2005 07:30:19 GMT (envelope-from gnats) Resent-Date: Thu, 17 Feb 2005 07:30:19 GMT Resent-Message-Id: <200502170730.j1H7UJYN096120@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, Markus Trippelsdorf Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3224816A4CE for ; Thu, 17 Feb 2005 07:26:20 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA2443D5A for ; Thu, 17 Feb 2005 07:26:20 +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 j1H7QJbs019915 for ; Thu, 17 Feb 2005 07:26:19 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j1H7QJNv019914; Thu, 17 Feb 2005 07:26:19 GMT (envelope-from nobody) Message-Id: <200502170726.j1H7QJNv019914@www.freebsd.org> Date: Thu, 17 Feb 2005 07:26:19 GMT From: Markus Trippelsdorf To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/77629: aMule hardlocks AMD64 system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 07:30:19 -0000 >Number: 77629 >Category: amd64 >Synopsis: aMule hardlocks AMD64 system >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 17 07:30:18 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Markus Trippelsdorf >Release: 5.3-STABLE >Organization: >Environment: FreeBSD bsd.trippelsdorf.de 5.3-STABLE FreeBSD 5.3-STABLE #5: Sat Feb 12 21:34:47 UTC 2005 markus@bsd.trippelsdorf.de:/usr/obj/usr/src/sys/MYKERNEL amd64 >Description: running aMule for >1h deterministicly hardlocks my system. No problem is reported in dmesg and the only way to proceed is a soft reset. >How-To-Repeat: Run ports/net/amule and use the program in it's intended way. >Fix: No fix is known. I would be glad to help in debugging the problem, just let me know what other infos you need. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 09:24: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 9C91516A4CE for ; Thu, 17 Feb 2005 09:24:40 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7308E43D54 for ; Thu, 17 Feb 2005 09:24:40 +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 51B282A8FC; Thu, 17 Feb 2005 01:24:40 -0800 (PST) (envelope-from peter@wemm.org) Received: from [127.0.0.1] (dhcp53.wemm.org [10.0.0.53]) by fw.wemm.org (Postfix) with ESMTP id EC7C7E2B3; Thu, 17 Feb 2005 01:24:39 -0800 (PST) (envelope-from peter@wemm.org) Message-ID: <421462D1.3000009@wemm.org> Date: Thu, 17 Feb 2005 01:24:33 -0800 From: Peter Wemm User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roman Neuhauser References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> In-Reply-To: <20050216002130.GA73909@isis.wad.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Any experience with "Asus A8N-SLi" or "Gigabyte K8NXP-SLI" mobos? 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, 17 Feb 2005 09:24:40 -0000 Roman Neuhauser wrote: ># obrien@freebsd.org / 2005-02-15 10:00:11 -0800: > > >>Stop supporting nVidia by buying nForce-based motherboards. Or complain >>to nVidia that they (1) won't give us docs even under NDA, (2) won't >>provide a FreeBSD driver like they do for Linux. These mailing lists are >>filled with all the problems of nForce motherboards, yet FreeBSD users >>keep buying them... >> >> > > This reminds me I wanted to raise this question: What is the > recommended chipset for an athlon64 (either 754 or 939)? > > Personally, unless there are cost reasons, take the 939. It has double the memory bandwidth. It doesn't make a huge amount of difference to unix type apps. In my experience, it make a small to medium improvement for most apps, and a large improvement to some. Yes, that is over generalized. Also in general, both are excellent platforms. Both of my primary development boxes are still 754's. I haven't felt the urge to upgrade them to 939's yet. Once the Rev-E's come out, I think I'll take the plunge though. -Peter From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 09:27: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 3AECB16A4CE for ; Thu, 17 Feb 2005 09:27:15 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1593043D48 for ; Thu, 17 Feb 2005 09:27:15 +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 E99ED2A8FC; Thu, 17 Feb 2005 01:27:14 -0800 (PST) (envelope-from peter@wemm.org) Received: from [127.0.0.1] (dhcp53.wemm.org [10.0.0.53]) by fw.wemm.org (Postfix) with ESMTP id 93E2CE2B3; Thu, 17 Feb 2005 01:27:14 -0800 (PST) (envelope-from peter@wemm.org) Message-ID: <4214636B.9050005@wemm.org> Date: Thu, 17 Feb 2005 01:27:07 -0800 From: Peter Wemm User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <4212868E.8080005@transactionware.com> <20050215235358.GC96584@dragon.nuxi.com> <42129E66.5090903@transactionware.com> <20050216032125.GA2966@dragon.nuxi.com> In-Reply-To: <20050216032125.GA2966@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jan Mikkelsen Subject: Re: NVidia chipsets (was Re: Any experience with "Asus A8N-SLi"or"Gigabyte K8NXP-SLI" mobos?) 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, 17 Feb 2005 09:27:15 -0000 David O'Brien wrote: >On Wed, Feb 16, 2005 at 12:14:14PM +1100, Jan Mikkelsen wrote: > > >>David O'Brien wrote: >> >> >>>>(Incidentally, does anyone know anything about the HP DL385, or the HP >>>>Opteron blades, the BL25p and BL35p?) >>>> >>>> >>>The *5 machines are opteron versions of the Xeon offerings. See the *0 >>>Xeon offerings to get a feel for the specs of the box. >>>I *believe* the DL385 uses the DL380 chassis. >>> >>> >>I am also interested in the chipsets they use. >> >>I believe the DL145 uses the AMD 8000 chipset, >> >> > >The HP DL145 uses the AMD 8100 chipset. The HP DL145 is an AMD design. >The HP DL585 also uses the AMD 8100 chipset, with the DL585 being a >Compaq design. So I expect the DL385 to use the AMD 8100 chipset also. > > > Yes, the DL385 is very similar to the 380, but with the 8000 series chipset on a compaq flavored motherboard. It is a very sweet design from what I briefly saw of it.. -Peter From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 19:04: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 1A02316A4CE for ; Thu, 17 Feb 2005 19:04:29 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC4E943D53 for ; Thu, 17 Feb 2005 19:04:26 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IC2KZH03.L54 for ; Thu, 17 Feb 2005 11:04:29 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005021711074616714 for ; Thu, 17 Feb 2005 11:07:46 -0800 From: "Vinod Kashyap" To: freebsd-amd64@freebsd.org Date: Thu, 17 Feb 2005 11:04:03 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: Subject: CLI and 3DM2 for 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: Thu, 17 Feb 2005 19:04:29 -0000 CLI and 3DM2, the management tools for 3ware's 7xxx/8xxx and 9xxx controllers are now available for FreeBSD amd64, here: http://www.3ware.com/support/downloadnew.asp Please note that these are not official releases, and have not gone through exhaustive testing. However, they are expected to work satisfactorily. Please report any problems to 3ware support. Thanks, Vinod. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 17 21:49: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 1003916A4CE for ; Thu, 17 Feb 2005 21:49:31 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA17543D5D for ; Thu, 17 Feb 2005 21:49:30 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 64C621976A; Thu, 17 Feb 2005 13:49:30 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 17 Feb 2005 13:49:29 -0800 User-Agent: KMail/1.7.2 References: <420F9CA1.4040207@chef-ingenieur.de> In-Reply-To: <420F9CA1.4040207@chef-ingenieur.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502171349.30085.peter@wemm.org> Subject: Re: -mno-sse -mno-sse2 -mno-mmx -mno-3dnow when compiling kernel 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, 17 Feb 2005 21:49:31 -0000 On Sunday 13 February 2005 10:29 am, Thomas Krause -CI- wrote: > Hello, > why are the Switches "-mno-sse -mno-sse2 -mno-mmx -mno-3dnow" are set > when compiling an amd64 kernel? I think, the CPU supports all thease > features. > > Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > I have no CPUTYPE specified in /etc/make.conf, as I could not > find a matching option in /usr/src/share/examples/etc/make.conf. For speed reasons, we restrict the kernel to using integer instructions only. This means we can avoid the considerable expense of saving/restoring floating point context unnecessarily for syscalls, interrupts, etc. On FreeBSD/i386, the compiler generally doesn't generate floating point instructions unless there is a reason to. But on FreeBSD/amd64, the compiler will do it readily because things like MMX, SSE and SSE2 are *known* to exist on this family and are part of the function calling conventions, especially for things like varargs functions. The upshot of this is that we are not in a lot of danger of the i386 compiler accidently generating floating point code for the kernel, but on FreeBSD/amd64, it can and does if you give it the chance. How the code for the kernel is generated has no bearing on the user code environment at all. The floating point/mmx/sse/sse2 context is reserved entirely for the user. Note that we *could* concievably set aside a few xmm registers for faster data copies inside the kernel, but we don't do it yet. I believe linux makes %xmm0 and %xmm1 available in the kernel and saves them with every trap into kernel mode. -- 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 Thu Feb 17 22:11:16 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 71E7D16A4CE; Thu, 17 Feb 2005 22:11:16 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B1F43D1D; Thu, 17 Feb 2005 22:11:16 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 222041976A; Thu, 17 Feb 2005 14:11:16 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 17 Feb 2005 14:11:15 -0800 User-Agent: KMail/1.7.2 References: <41F62EE7.6070808@fsn.hu> <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> <421337C2.7040800@fsn.hu> In-Reply-To: <421337C2.7040800@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502171411.15827.peter@wemm.org> cc: amd64@freebsd.org cc: Alexander Leidinger Subject: Re: kernel message while running icc-em64t 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, 17 Feb 2005 22:11:16 -0000 On Wednesday 16 February 2005 04:08 am, Attila Nagy wrote: > Alexander Leidinger wrote: > >> helen# icc -V ; dmesg | tail -2 > >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > >> FOR NON-COMMERCIAL USE ONLY > >> > >> iccbin: Command line error: no files specified; for help type > >> "iccbin -help" > >> fpudna: fpcurthread == curthread 2341 times > >> fpudna: fpcurthread == curthread 2342 times > >> helen# icc -V ; dmesg | tail -2 > >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > >> FOR NON-COMMERCIAL USE ONLY > >> > >> iccbin: Command line error: no files specified; for help type > >> "iccbin -help" > >> fpudna: fpcurthread == curthread 2342 times > >> fpudna: fpcurthread == curthread 2343 times > >> > >> icpc triggers the same. > > > > That's a message from the kernel. amd64@ CCed for this purpose. > > To clarify what's this: > Alexander sent me a icc-em64t port, which should make Intel's C > compiler work on FreeBSD/AMD64 to produce EM64T (AMD64) code. It is > based on the EM64T version of the compiler, which is in fact a 32 bit > Linux binary. > > When I invoke icc, or icpc (the C++ compiler) I get the above kernel > messages. If I had to guess, I'd guess that it is trying to issue SSE3 instructions to see if they work.. -- 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 Thu Feb 17 22:11:16 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 71E7D16A4CE; Thu, 17 Feb 2005 22:11:16 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B1F43D1D; Thu, 17 Feb 2005 22:11:16 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 222041976A; Thu, 17 Feb 2005 14:11:16 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 17 Feb 2005 14:11:15 -0800 User-Agent: KMail/1.7.2 References: <41F62EE7.6070808@fsn.hu> <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> <421337C2.7040800@fsn.hu> In-Reply-To: <421337C2.7040800@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502171411.15827.peter@wemm.org> cc: amd64@freebsd.org cc: Alexander Leidinger Subject: Re: kernel message while running icc-em64t 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, 17 Feb 2005 22:11:16 -0000 On Wednesday 16 February 2005 04:08 am, Attila Nagy wrote: > Alexander Leidinger wrote: > >> helen# icc -V ; dmesg | tail -2 > >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > >> FOR NON-COMMERCIAL USE ONLY > >> > >> iccbin: Command line error: no files specified; for help type > >> "iccbin -help" > >> fpudna: fpcurthread == curthread 2341 times > >> fpudna: fpcurthread == curthread 2342 times > >> helen# icc -V ; dmesg | tail -2 > >> Intel(R) C Compiler for Intel(R) EM64T-based applications, Version > >> 8.1 Build20041123 Package ID: l_cce_pc_8.1.024 > >> Copyright (C) 1985-2004 Intel Corporation. All rights reserved. > >> FOR NON-COMMERCIAL USE ONLY > >> > >> iccbin: Command line error: no files specified; for help type > >> "iccbin -help" > >> fpudna: fpcurthread == curthread 2342 times > >> fpudna: fpcurthread == curthread 2343 times > >> > >> icpc triggers the same. > > > > That's a message from the kernel. amd64@ CCed for this purpose. > > To clarify what's this: > Alexander sent me a icc-em64t port, which should make Intel's C > compiler work on FreeBSD/AMD64 to produce EM64T (AMD64) code. It is > based on the EM64T version of the compiler, which is in fact a 32 bit > Linux binary. > > When I invoke icc, or icpc (the C++ compiler) I get the above kernel > messages. If I had to guess, I'd guess that it is trying to issue SSE3 instructions to see if they work.. -- 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 Fri Feb 18 00:04: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 DD91516A4CE for ; Fri, 18 Feb 2005 00:04:29 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA95143D31 for ; Fri, 18 Feb 2005 00:04:27 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IC200E8PYUQKN@VL-MO-MR011.ip.videotron.ca> for freebsd-amd64@freebsd.org; Thu, 17 Feb 2005 19:04:02 -0500 (EST) Date: Thu, 17 Feb 2005 19:04:02 -0500 From: Nicolas Blais To: freebsd-amd64@freebsd.org Message-id: <200502171904.03591.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Content-disposition: inline User-Agent: KMail/1.7.2 Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 18 Feb 2005 00:04:30 -0000 I can help if you want to know if it runs on -STABLE but I have no idea whi= ch=20 of the late fix-it-all patches is the real one. =A0Currently on my R3000Z s= ystem=20 I'm running with=20 Jung-uk Kim's patchs (including DSDT fix), not the recently unified patch. Which of the many posted unified patch is the right one and do I still need= to=20 perform acpidump and install the keyboard-boot fix? Thanks, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 05:59:24 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 EAC4616A4CE for ; Fri, 18 Feb 2005 05:59:24 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8654643D31 for ; Fri, 18 Feb 2005 05:59:24 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so446414rng for ; Thu, 17 Feb 2005 21:59:24 -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=aK4naHbIww30VDdgxZh89NDjZtEVoK7mlTtupOt+plOyo4Rd8J/pS5O81y1KgUQ1ZBrTA3+3kWjhyado9cWlEtDUn2lT5oQ9f8x+n1MvJHjz4iOwvzbka2PfshsXYHUTInzpMIT83WuHWrXuvFaN2TZfF8McYMGM/qb3zslxNek= Received: by 10.38.153.46 with SMTP id a46mr192384rne; Thu, 17 Feb 2005 21:59:23 -0800 (PST) Received: by 10.38.22.22 with HTTP; Thu, 17 Feb 2005 21:59:23 -0800 (PST) Message-ID: <346a8022050217215967ecd8be@mail.gmail.com> Date: Fri, 18 Feb 2005 00:59:23 -0500 From: Coleman Kane To: Nicolas Blais In-Reply-To: <200502171904.03591.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502171904.03591.nb_root@videotron.ca> cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 05:59:25 -0000 On Thu, 17 Feb 2005 19:04:02 -0500, Nicolas Blais wrote: > I can help if you want to know if it runs on -STABLE but I have no idea which > of the late fix-it-all patches is the real one. Currently on my R3000Z system > I'm running with > Jung-uk Kim's patchs (including DSDT fix), not the recently unified patch. > > Which of the many posted unified patch is the right one and do I still need to > perform acpidump and install the keyboard-boot fix? > > Thanks, > Nicolas. > The unified patch does not include the ExtINT patch. It also doesn't include the PCI patch to get pccard working. I still needed to apply both of those, in addition to the DSDT update when using the unified patch. The work I needed to do in order to get a RELENG_5 system working are at: http://www.cokane.org/amd64.html. I am in the lucky position of having access to both the Gateway VIA-based Mobile Athlon64 laptop and a notorious Compaq R3000 Athlon64 laptop. -- coleman From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 08:04: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 986AD16A4CE for ; Fri, 18 Feb 2005 08:04:06 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3553543D3F for ; Fri, 18 Feb 2005 08:04:06 +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 j1I845Uj085745; Fri, 18 Feb 2005 00:04:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1I844sZ085744; Fri, 18 Feb 2005 00:04:04 -0800 (PST) (envelope-from obrien) Date: Fri, 18 Feb 2005 00:04:04 -0800 From: "David O'Brien" To: Nicolas Blais Message-ID: <20050218080404.GA76967@dragon.nuxi.com> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <200502131935.57231.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502131935.57231.nb_root@videotron.ca> 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: Can't compile jdk15 on amd64 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: Fri, 18 Feb 2005 08:04:06 -0000 On Sun, Feb 13, 2005 at 07:35:56PM -0500, Nicolas Blais wrote: > Actually, I can build jdk15 on a amd64 6-CURRENT machine and I can't on a > amd64 5.3-STABLE. Yes I believe (as well as others) that it is due to a > maximum command line size (as mentioned, the javac command during that point > in the makefile is about 25000 char long and on my -STABLE I can only get > 16384) I don't know why so many think that 6-CURRENT has a greater maximum command line size than 5-STABLE. Anyway, I just committed a change to 6-STABLE to increase it (based on a thread in freebsd-current@ from back in Sept. 2004). I'll MFC it for 5-STABLE. If there is some other sizing difference, then those affected need to track it down and point out what it is so we can deal with it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 08:12: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 4E1EA16A4CE for ; Fri, 18 Feb 2005 08:12:43 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A6E643D48 for ; Fri, 18 Feb 2005 08:12:43 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C6353F368D; Fri, 18 Feb 2005 00:12:42 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85746-06; Fri, 18 Feb 2005 00:12:33 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 700F4F368B; Fri, 18 Feb 2005 00:12:33 -0800 (PST) From: Sean McNeil To: freebsd-amd64@freebsd.org In-Reply-To: <20050218080404.GA76967@dragon.nuxi.com> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <200502131935.57231.nb_root@videotron.ca> <20050218080404.GA76967@dragon.nuxi.com> Content-Type: text/plain Date: Fri, 18 Feb 2005 00:12:33 -0800 Message-Id: <1108714353.99230.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: Re: Can't compile jdk15 on amd64 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, 18 Feb 2005 08:12:43 -0000 On Fri, 2005-02-18 at 00:04 -0800, David O'Brien wrote: > On Sun, Feb 13, 2005 at 07:35:56PM -0500, Nicolas Blais wrote: > > Actually, I can build jdk15 on a amd64 6-CURRENT machine and I can't on a > > amd64 5.3-STABLE. Yes I believe (as well as others) that it is due to a > > maximum command line size (as mentioned, the javac command during that point > > in the makefile is about 25000 char long and on my -STABLE I can only get > > 16384) > > I don't know why so many think that 6-CURRENT has a greater maximum > command line size than 5-STABLE. Anyway, I just committed a change to > 6-STABLE to increase it (based on a thread in freebsd-current@ from back > in Sept. 2004). I'll MFC it for 5-STABLE. > > If there is some other sizing difference, then those affected need to > track it down and point out what it is so we can deal with it. The problem is that a Linux emulated program (linux-sun-jdk) would die with something like bad address printed to the stderr/stdout. It isn't the command line size alone (I don't think). Once I got past that initial failure, I am able to rebuilt jdk15 natively without any issues. So I'd say there is a problem with the linux32 emulation. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 12:41:21 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 1BD8416A4CE for ; Fri, 18 Feb 2005 12:41:21 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 994FA43D1F for ; Fri, 18 Feb 2005 12:41:20 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so507177rnf for ; Fri, 18 Feb 2005 04:41:19 -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=GYMXABXpqCDLbFZ+BB4/fGWL9Z7JZRRsOTKFm1hdPdYmWSsnyUvNdUvcDeXccDfNb7olWpK8QWBFyeMsi7hsB9rakg2RRT3o++lmuhO+xL3IGWqv1KRnBIGYsDmdfGGd3x7Xu+AlNcO7o+tXIyZHt4Mj3hKna5hLdyQJAPZek2U= Received: by 10.38.208.9 with SMTP id f9mr85563rng; Fri, 18 Feb 2005 04:41:18 -0800 (PST) Received: by 10.38.208.52 with HTTP; Fri, 18 Feb 2005 04:41:18 -0800 (PST) Message-ID: <28edec3c0502180441444a4af@mail.gmail.com> Date: Fri, 18 Feb 2005 20:41:18 +0800 From: "Mars G. Miro" To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: NOFOO->NO_FOO changes breaks installworld to 5.3p5 in RELENG_5_3 in FreeBSD/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Mars G. Miro" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 12:41:21 -0000 At: ===> 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 The fix is to go to /usr/src/gnu/usr.bin/groff/font and grep for the Makefiles having NOFOO and change them to NO_FOO, e.g.: % sh $ cd /usr/src/gnu/usr.bin/groff/font $ for i in $(grep -r NO * | cut -f1 -d/); do echo $i; sed 's/NOO/NO_O/g' $i/Makefile > $i/Makefile.tmp && mv $i/Makefile $i/Makefile.orig && mv $i/Makefile.tmp $i/Makefile;done If you have already built world, you have to do a $ make clean && make cleandir && make obj && make all in the same directory and do the installworld process again. If you haven't, you can skip the previous commands. This was also experienced by a FreeBSD/AMD64 user at: http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/075915.html This does not happen in FreeBSD/i386, upgrading to 5.3p5. Thanks. cheers mars From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 16:37:02 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 9858716A4CE for ; Fri, 18 Feb 2005 16:37:02 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8C3043D1F for ; Fri, 18 Feb 2005 16:37:01 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1IGb06G026230; Fri, 18 Feb 2005 18:37:00 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 57822-14; Fri, 18 Feb 2005 18:37:00 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j1IGb0Gf026221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2005 18:37:00 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j1IGb6H3050566; Fri, 18 Feb 2005 18:37:06 +0200 (EET) (envelope-from ru) Date: Fri, 18 Feb 2005 18:37:05 +0200 From: Ruslan Ermilov To: "Mars G. Miro" Message-ID: <20050218163705.GD50352@ip.net.ua> References: <28edec3c0502180441444a4af@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cQXOx3fnlpmgJsTP" Content-Disposition: inline In-Reply-To: <28edec3c0502180441444a4af@mail.gmail.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@FreeBSD.org Subject: Re: NOFOO->NO_FOO changes breaks installworld to 5.3p5 in RELENG_5_3 in FreeBSD/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 16:37:02 -0000 --cQXOx3fnlpmgJsTP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 18, 2005 at 08:41:18PM +0800, Mars G. Miro wrote: > At: >=20 > =3D=3D=3D> gnu/usr.bin/groff/font/devX100 > Segmentation fault (core dumped) > *** Error code 139 >=20 What's dumping core here, make(1)? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --cQXOx3fnlpmgJsTP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCFhmxqRfpzJluFF4RAlCYAJ4uiymIC4LExVAmiTOL+etv32hj3QCfSPDW LsdhtnBrx0yCJHchkPrMw+4= =An4a -----END PGP SIGNATURE----- --cQXOx3fnlpmgJsTP-- From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 17:25: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 8C11B16A4CE for ; Fri, 18 Feb 2005 17:25:11 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D22CF43D5E for ; Fri, 18 Feb 2005 17:25:10 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1IHNBnd046216 for ; Fri, 18 Feb 2005 10:23:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 18 Feb 2005 10:23:10 -0700 (MST) Message-Id: <20050218.102310.74705720.imp@bsdimp.com> To: amd64@freebsd.org From: Warner Losh X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: PC Card subpart to R3000 thread 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, 18 Feb 2005 17:25:11 -0000 # I'll note that I really like to be cc'd on changes that impact the # pccard part of the system :-) : Yeah the recipient of the fix just emailed me about this, I am : guessing that the #if 0 is the uncommitable part. Is there any way : that this can be done by the kernel (the PCI reg write, that is)? Is : there any reason that it can't be done there? I'd be extremely reluctant to commit the #if 0 part of the fix. The problem is that we don't quite do bus numbering/renumbering correctly for pci busses in general. There's some kludges in cardbus bridge to cope with this, but I don't like them much at all. So, yes, something can be done about this in the kernel, but that something is rather more complicated than this overly simplistic kludge. --- src/sys/dev/pci/pci_pci.c.orig Thu Jul 1 03:46:28 2004 +++ src/sys/dev/pci/pci_pci.c Sat Jan 22 01:21:50 2005 @@ -319,6 +319,8 @@ start = sc->iobase; if (end > sc->iolimit) end = sc->iolimit; + if (start <= end) + ok = 1; This looks OK to me. At first I thought it was crazy and unnecessary to set this, but I think it might be OK. It does seem very odd that we've not seen this before now. Oh, wait, the <= should be <. == would imply that the range is 0. Warner From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 17:28:50 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 7493416A4CE for ; Fri, 18 Feb 2005 17:28:50 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42DB743D58 for ; Fri, 18 Feb 2005 17:28:50 +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 j1IHSnwn005519; Fri, 18 Feb 2005 09:28:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j1IHSn6n005518; Fri, 18 Feb 2005 09:28:49 -0800 (PST) (envelope-from obrien) Date: Fri, 18 Feb 2005 09:28:49 -0800 From: "David O'Brien" To: Sean McNeil Message-ID: <20050218172849.GA5422@dragon.nuxi.com> References: <200502131433.43567.nb_root@videotron.ca> <20050214003007.GE68054@dragon.nuxi.com> <200502131935.57231.nb_root@videotron.ca> <20050218080404.GA76967@dragon.nuxi.com> <1108714353.99230.3.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1108714353.99230.3.camel@server.mcneil.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: Can't compile jdk15 on amd64 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: Fri, 18 Feb 2005 17:28:50 -0000 On Fri, Feb 18, 2005 at 12:12:33AM -0800, Sean McNeil wrote: > So I'd say there is a problem with the linux32 emulation. Its still rather "green" so this doesn't surprise me. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 17:50: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 47D8016A560 for ; Fri, 18 Feb 2005 17:50:11 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CD9E43D5C for ; Fri, 18 Feb 2005 17:50:06 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j1IHnu2p017605; Fri, 18 Feb 2005 12:49:56 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Fri, 18 Feb 2005 12:49:53 -0500 User-Agent: KMail/1.6.2 References: <20050218.102310.74705720.imp@bsdimp.com> In-Reply-To: <20050218.102310.74705720.imp@bsdimp.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502181249.53139.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/709/Fri Feb 18 09:37:50 2005 on anuket.mj.niksun.com X-Virus-Status: Clean cc: Warner Losh Subject: Re: PC Card subpart to R3000 thread 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, 18 Feb 2005 17:50:40 -0000 On Friday 18 February 2005 12:23 pm, Warner Losh wrote: > # I'll note that I really like to be cc'd on changes that impact > the # pccard part of the system :-) > > : Yeah the recipient of the fix just emailed me about this, I am > : guessing that the #if 0 is the uncommitable part. Is there any > : way that this can be done by the kernel (the PCI reg write, that > : is)? Is there any reason that it can't be done there? > > I'd be extremely reluctant to commit the #if 0 part of the fix. > The problem is that we don't quite do bus numbering/renumbering > correctly for pci busses in general. There's some kludges in > cardbus bridge to cope with this, but I don't like them much at > all. > > So, yes, something can be done about this in the kernel, but that > something is rather more complicated than this overly simplistic > kludge. Exactly. :-) > --- src/sys/dev/pci/pci_pci.c.orig Thu Jul 1 03:46:28 2004 > +++ src/sys/dev/pci/pci_pci.c Sat Jan 22 01:21:50 2005 > @@ -319,6 +319,8 @@ > start = sc->iobase; > if (end > sc->iolimit) > end = sc->iolimit; > + if (start <= end) > + ok = 1; > > > This looks OK to me. At first I thought it was crazy and > unnecessary to set this, but I think it might be OK. It does seem > very odd that we've not seen this before now. Oh, wait, the <= > should be <. == would imply that the range is 0. Oops, my bad. Thanks for committing this! Jung-uk Kim > Warner From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 18:21:05 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 42F5016A4CE for ; Fri, 18 Feb 2005 18:21:05 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC28043D3F for ; Fri, 18 Feb 2005 18:21:04 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IC4DN702.9DH; Fri, 18 Feb 2005 10:21:07 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005021810250830882 ; Fri, 18 Feb 2005 10:25:08 -0800 From: "Vinod Kashyap" To: Lawrence Farr Date: Fri, 18 Feb 2005 10:20:46 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-amd64@freebsd.org Subject: RE: CLI and 3DM2 for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 18:21:05 -0000 i386 CLI and 3DM2 for 7xxx/8xxx are already available here: http://www.3ware.com/support/download.asp. They are the same as the ones for 9xxx. CLI and 3DM2 for 9xxx are compatible with 7xxx/8xxx as well. Note this on the main Software Download page on the 3ware website (http://www.3ware.com/support/index.asp): "The Linux/FreeBSD CLI and 3DM 2 for the 9000 series are compatible with the 7000/8000 series products." > -----Original Message----- > From: Lawrence Farr [mailto:freebsd-smp@epcdirect.co.uk] > Sent: Friday, February 18, 2005 12:47 AM > To: 'Vinod Kashyap' > Subject: RE: CLI and 3DM2 for amd64 > = > = > Are there any plans to release a 3DM2 that will work with > i386 on a 7xxx/8xxx controller? > = > Regards, > = > > -----Original Message----- > > From: owner-freebsd-amd64@freebsd.org = > > [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of Vinod Kashyap > > Sent: 17 February 2005 19:04 > > To: freebsd-amd64@freebsd.org > > Subject: CLI and 3DM2 for amd64 > > = > > = > > CLI and 3DM2, the management tools for 3ware's 7xxx/8xxx and > > 9xxx controllers are now available for FreeBSD amd64, here: > > http://www.3ware.com/support/downloadnew.asp > > = > > Please note that these are not official releases, and have not gone > > through exhaustive testing. However, they are expected to work > > satisfactorily. Please report any problems to 3ware support. > > = > > = > > Thanks, > > = > > Vinod. > > = > > = > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to = > > "freebsd-amd64-unsubscribe@freebsd.org" > > = > = > From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 19:31:57 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 D54D616A4CE for ; Fri, 18 Feb 2005 19:31:56 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 004D043D66 for ; Fri, 18 Feb 2005 19:31:55 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so565245rng for ; Fri, 18 Feb 2005 11:31:54 -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=DQZMFA1kSxKSLRW9hE4JHvVXUh1ejgwicnjIUM7KYbIuv6IeRldsSj8JJUctY5IjvE5qbcHyNK8WKe5PAntvVChCIgA2k0aQvYkgjRlo8aWwH+EneQszHdELsKAQ4XvTogF7TPAq8qNy/1W4xrEtrWUbQsRz6dKL8ig06sLF9TY= Received: by 10.38.68.14 with SMTP id q14mr198347rna; Fri, 18 Feb 2005 11:31:53 -0800 (PST) Received: by 10.38.22.22 with HTTP; Fri, 18 Feb 2005 11:31:48 -0800 (PST) Message-ID: <346a8022050218113126c1af5f@mail.gmail.com> Date: Fri, 18 Feb 2005 14:31:48 -0500 From: Coleman Kane To: Jung-uk Kim In-Reply-To: <200502181249.53139.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050218.102310.74705720.imp@bsdimp.com> <200502181249.53139.jkim@niksun.com> cc: Warner Losh cc: freebsd-amd64@freebsd.org Subject: Re: PC Card subpart to R3000 thread X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 19:31:57 -0000 On Fri, 18 Feb 2005 12:49:53 -0500, Jung-uk Kim wrote: > On Friday 18 February 2005 12:23 pm, Warner Losh wrote: > > # I'll note that I really like to be cc'd on changes that impact > > the # pccard part of the system :-) > > > > : Yeah the recipient of the fix just emailed me about this, I am > > : guessing that the #if 0 is the uncommitable part. Is there any > > : way that this can be done by the kernel (the PCI reg write, that > > : is)? Is there any reason that it can't be done there? > > > > I'd be extremely reluctant to commit the #if 0 part of the fix. > > The problem is that we don't quite do bus numbering/renumbering > > correctly for pci busses in general. There's some kludges in > > cardbus bridge to cope with this, but I don't like them much at > > all. > > > > So, yes, something can be done about this in the kernel, but that > > something is rather more complicated than this overly simplistic > > kludge. > > Exactly. :-) Oh, cool. I was not aware of this numbering issue. > > > --- src/sys/dev/pci/pci_pci.c.orig Thu Jul 1 03:46:28 2004 > > +++ src/sys/dev/pci/pci_pci.c Sat Jan 22 01:21:50 2005 > > @@ -319,6 +319,8 @@ > > start = sc->iobase; > > if (end > sc->iolimit) > > end = sc->iolimit; > > + if (start <= end) > > + ok = 1; > > > > > > This looks OK to me. At first I thought it was crazy and > > unnecessary to set this, but I think it might be OK. It does seem > > very odd that we've not seen this before now. Oh, wait, the <= > > should be <. == would imply that the range is 0. > > Oops, my bad. > > Thanks for committing this! > > Jung-uk Kim > > > Warner > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 20:17: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 BE36216A4CE for ; Fri, 18 Feb 2005 20:17:12 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDBE43D55 for ; Fri, 18 Feb 2005 20:17:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1IKDBx5048086; Fri, 18 Feb 2005 13:13:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 18 Feb 2005 13:13:11 -0700 (MST) Message-Id: <20050218.131311.104079154.imp@bsdimp.com> To: cokane@cokane.org, zombyfork@gmail.com From: Warner Losh In-Reply-To: <346a8022050218113126c1af5f@mail.gmail.com> References: <20050218.102310.74705720.imp@bsdimp.com> <200502181249.53139.jkim@niksun.com> <346a8022050218113126c1af5f@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: PC Card subpart to R3000 thread 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, 18 Feb 2005 20:17:12 -0000 From: Coleman Kane Subject: Re: PC Card subpart to R3000 thread Date: Fri, 18 Feb 2005 14:31:48 -0500 > On Fri, 18 Feb 2005 12:49:53 -0500, Jung-uk Kim wrote: > > On Friday 18 February 2005 12:23 pm, Warner Losh wrote: > > > # I'll note that I really like to be cc'd on changes that impact > > > the # pccard part of the system :-) > > > > > > : Yeah the recipient of the fix just emailed me about this, I am > > > : guessing that the #if 0 is the uncommitable part. Is there any > > > : way that this can be done by the kernel (the PCI reg write, that > > > : is)? Is there any reason that it can't be done there? > > > > > > I'd be extremely reluctant to commit the #if 0 part of the fix. > > > The problem is that we don't quite do bus numbering/renumbering > > > correctly for pci busses in general. There's some kludges in > > > cardbus bridge to cope with this, but I don't like them much at > > > all. > > > > > > So, yes, something can be done about this in the kernel, but that > > > something is rather more complicated than this overly simplistic > > > kludge. > > > > Exactly. :-) > > Oh, cool. I was not aware of this numbering issue. There are a number of issues relating to it, which makes it hard to solve generically (well, one could always write 255 as the subbus number, but that has some rather severe performance implications... Warner From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 18 21:33:08 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 DB8FF16A4E4 for ; Fri, 18 Feb 2005 21:33:08 +0000 (GMT) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 705F943D2F for ; Fri, 18 Feb 2005 21:33:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 31372 invoked from network); 18 Feb 2005 21:33:08 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 18 Feb 2005 21:33:07 -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 j1ILWpgX085625; Fri, 18 Feb 2005 16:33:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Jung-uk Kim Date: Fri, 18 Feb 2005 10:13:58 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <346a80220502151437627a9ef6@mail.gmail.com> <200502160027.55420.jkim@niksun.com> In-Reply-To: <200502160027.55420.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502181013.59005.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: David O'Brien cc: freebsd-amd64@FreeBSD.org cc: cokane@cokane.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 18 Feb 2005 21:33:09 -0000 On Wednesday 16 February 2005 12:27 am, Jung-uk Kim wrote: > On Tuesday 15 February 2005 05:37 pm, Coleman Kane wrote: > > Hi, I tested the patch posted by John on a compaq R3000. Works > > great, except still requires device atpic (for the mixed_mode > > operation I think). Kim posted a patch in this email: > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/00337 > >6.html. I dunno if the patch is kosher or not, however. It does > > allow me to run without using atpic. > > Ouch, you're absolutely correct. jhb's patch wasn't complete for > amd64. The missing piece is attached. Can you please re-test? > > Thanks, > > Jung-uk Kim Doh. :-P -- 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 18 21:33: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 D8E4916A4CF for ; Fri, 18 Feb 2005 21:33:14 +0000 (GMT) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8CF43D48 for ; Fri, 18 Feb 2005 21:33:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 3641 invoked from network); 18 Feb 2005 21:33:12 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 18 Feb 2005 21:33:11 -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 j1ILWpgY085625; Fri, 18 Feb 2005 16:33:06 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Coleman Kane Date: Fri, 18 Feb 2005 10:15:59 -0500 User-Agent: KMail/1.6.2 References: <200502141722.10259.jhb@FreeBSD.org> <200502161256.34505.jkim@niksun.com> <20050216140808.GF99724@ramen> In-Reply-To: <20050216140808.GF99724@ramen> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502181015.59593.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: freebsd-amd64@FreeBSD.org cc: obrien@FreeBSD.org Subject: Re: [PATCH] Updated quirk-driven R3000Z patches 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, 18 Feb 2005 21:33:15 -0000 On Wednesday 16 February 2005 09:08 am, Coleman Kane wrote: > Yeah the recipient of the fix just emailed me about this, I am guessing > that the #if 0 is the uncommitable part. Is there any way that this can > be done by the kernel (the PCI reg write, that is)? Is there any reason > that it can't be done there? The kernel PCI code should do it. NetBSD does it I think. Basically, we need to assign bus numbers to PCI busses that don't already have one. Warner Losh (imp@) has talked about this before. Doing it correctly might be a bit tricky. > On Wed, Feb 16, 2005 at 12:56:34PM -0500, Jung-uk Kim wrote, and it was proclaimed: > > On Wednesday 16 February 2005 12:45 pm, David O'Brien wrote: > > > On Wed, Feb 16, 2005 at 01:47:31PM +0000, Coleman Kane wrote: > > > > Also, there is another patch missing. The following allows you to > > > > use PCCARD devices to work. I found this email: > > > > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January > > > >/003365.html > > > > > > > > Which has the problem detailed. Without this, the IO ranges > > > > attached to the PCCARD devices asre screwed up, and thus you > > > > cannot use them. > > > > > > But this patch has nothing to do with the ATPIC issue (that I can > > > see). So it should be left out of jhb's patch. Also that patch > > > isn't in a committable form. Can someone make it in a commitable > > > form and I'll commit it. > > > > All you need is the second hunk, which is commitable, I believe. The > > first hunk has to be fixed from BIOS or manually corrected by: > > > > pciconf -w -b pci0:10:0 0x1a 0x0a > > > > Jung-uk Kim -- 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 18 22:21: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 7362C16A4CE; Fri, 18 Feb 2005 22:21:31 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC57743D5F; Fri, 18 Feb 2005 22:21:30 +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 j1IMLUk0088963; Fri, 18 Feb 2005 17:21:30 -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 j1IMLUCT005879; Fri, 18 Feb 2005 17:21:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 00B977306E; Fri, 18 Feb 2005 17:21:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050218222129.00B977306E@freebsd-current.sentex.ca> Date: Fri, 18 Feb 2005 17:21:29 -0500 (EST) X-Virus-Scanned: ClamAV 0.82/709/Fri Feb 18 09:37:50 2005 on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner4 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: Fri, 18 Feb 2005 22:21:31 -0000 TB --- 2005-02-18 21:01:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-18 21:01:59 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-02-18 21:01:59 - checking out the source tree TB --- 2005-02-18 21:01:59 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-02-18 21:01:59 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-02-18 21:07:40 - building world (CFLAGS=-O2 -pipe) TB --- 2005-02-18 21:07:40 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-18 21:07:40 - /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-18 22:15:01 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-02-18 22:15:01 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-02-18 22:15:01 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Feb 18 22:15:01 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/kern/uipc_mbuf.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/uipc_mbuf2.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/uipc_proto.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/uipc_socket.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/uipc_socket2.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/uipc_syscalls.c /tinderbox/CURRENT/amd64/amd64/src/sys/kern/uipc_syscalls.c: In function `kern_connect': /tinderbox/CURRENT/amd64/amd64/src/sys/kern/uipc_syscalls.c:504: warning: unused variable `s' *** 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-02-18 22:21:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-18 22:21:29 - ERROR: failed to build generic kernel TB --- 2005-02-18 22:21:29 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 00:35: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 EF74316A4CE for ; Sat, 19 Feb 2005 00:35:27 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91D4943D46 for ; Sat, 19 Feb 2005 00:35:27 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so12913rne for ; Fri, 18 Feb 2005 16:35:27 -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=alGa41fY155SfDNhX1OCFZig4pDLKHP40wzb1qmepzQh7xBFhrSPBQOSNyS4vP42u5CC3A4TdX9NtR6o0XiESBn/2ER4+U9QCirYkIBruyPoJwcn6a5P4RRZoLpNpCPeymmT9XDfBU/N7JLXTqQFibY7J/cvWx8/jN78KfTmQl8= Received: by 10.38.68.14 with SMTP id q14mr99999rna; Fri, 18 Feb 2005 16:35:26 -0800 (PST) Received: by 10.38.22.22 with HTTP; Fri, 18 Feb 2005 16:35:26 -0800 (PST) Message-ID: <346a802205021816354ebbd91e@mail.gmail.com> Date: Fri, 18 Feb 2005 19:35:26 -0500 From: Coleman Kane To: Warner Losh In-Reply-To: <20050218.131311.104079154.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050218.102310.74705720.imp@bsdimp.com> <200502181249.53139.jkim@niksun.com> <346a8022050218113126c1af5f@mail.gmail.com> <20050218.131311.104079154.imp@bsdimp.com> cc: freebsd-amd64@freebsd.org Subject: Re: PC Card subpart to R3000 thread X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2005 00:35:28 -0000 On Fri, 18 Feb 2005 13:13:11 -0700 (MST), Warner Losh wrote: > > There are a number of issues relating to it, which makes it hard to > solve generically (well, one could always write 255 as the subbus > number, but that has some rather severe performance implications... > > Warner > How do we keep track of the busses now? What considerations must be taken into account regarding setting the numbering this subordinate bus number? In the patch code it seems that it is setting this register to the same value as the bus number (10). You are stating that it can be set to any number (PCIR_SUBBUS_1 that is)? -- coleman From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 00:46: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 B588D16A4CE for ; Sat, 19 Feb 2005 00:46:53 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 151FC43D39 for ; Sat, 19 Feb 2005 00:46:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1J0j4D9050797; Fri, 18 Feb 2005 17:45:04 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 18 Feb 2005 17:45:04 -0700 (MST) Message-Id: <20050218.174504.85362426.imp@bsdimp.com> To: cokane@cokane.org, zombyfork@gmail.com From: Warner Losh In-Reply-To: <346a802205021816354ebbd91e@mail.gmail.com> References: <346a8022050218113126c1af5f@mail.gmail.com> <20050218.131311.104079154.imp@bsdimp.com> <346a802205021816354ebbd91e@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: PC Card subpart to R3000 thread 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, 19 Feb 2005 00:46:53 -0000 From: Coleman Kane Subject: Re: PC Card subpart to R3000 thread Date: Fri, 18 Feb 2005 19:35:26 -0500 > On Fri, 18 Feb 2005 13:13:11 -0700 (MST), Warner Losh wrote: > > > > There are a number of issues relating to it, which makes it hard to > > solve generically (well, one could always write 255 as the subbus > > number, but that has some rather severe performance implications... > > > > Warner > > > > How do we keep track of the busses now? What considerations must be > taken into account regarding setting the numbering this subordinate > bus number? In the patch code it seems that it is setting this > register to the same value as the bus number (10). You are stating > that it can be set to any number (PCIR_SUBBUS_1 that is)? We don't keep track of the busses now, other than what's in the hardware. We'd have to walk the pci tree to know what the right numbers would be, possibly renumbering. The renumbering part is hard, since it impacts ACPI. I believe that setting to 255 would work. Warner From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 10:27:25 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 04ABB16A4CE; Sat, 19 Feb 2005 10:27:25 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7575E43D53; Sat, 19 Feb 2005 10:27:24 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j1JARNxQ040649; Sat, 19 Feb 2005 05:27:23 -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 j1JARNOT072232; Sat, 19 Feb 2005 05:27:23 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7BF0A7306E; Sat, 19 Feb 2005 05:27:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050219102723.7BF0A7306E@freebsd-current.sentex.ca> Date: Sat, 19 Feb 2005 05:27:23 -0500 (EST) X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner4 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, 19 Feb 2005 10:27:25 -0000 TB --- 2005-02-19 09:11:05 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-19 09:11:05 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-02-19 09:11:05 - checking out the source tree TB --- 2005-02-19 09:11:05 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-02-19 09:11:05 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-19 09:24:20 - building world (CFLAGS=-O -pipe) TB --- 2005-02-19 09:24:20 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-19 09:24:20 - /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-19 10:23:07 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-19 10:23:07 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-19 10:23:07 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Feb 19 10:23:08 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 -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_mib.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: "struct freebsd32_modstat_args" declared inside parameter list /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:442: warning: no previous prototype for 'freebsd32_modstat' /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c: In function `freebsd32_modstat': /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:451: error: dereferencing pointer to incomplete type /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:465: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/GENERIC. *** 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-19 10:27:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-19 10:27:23 - ERROR: failed to build generic kernel TB --- 2005-02-19 10:27:23 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 16:07:22 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 0E7F616A4CE for ; Sat, 19 Feb 2005 16:07:22 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79A343D54 for ; Sat, 19 Feb 2005 16:07:21 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IC600MI522PGY@VL-MO-MR010.ip.videotron.ca> for freebsd-amd64@freebsd.org; Sat, 19 Feb 2005 11:06:25 -0500 (EST) Date: Sat, 19 Feb 2005 11:06:16 -0500 From: Nicolas Blais To: freebsd-amd64@freebsd.org Message-id: <200502191106.17830.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_D7qeCpnA75tVdU+tGkWaEA)" User-Agent: KMail/1.7.2 Subject: Latest changes to STABLE doesn't compile on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2005 16:07:22 -0000 --Boundary_(ID_D7qeCpnA75tVdU+tGkWaEA) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline Hi, While making world this morning with updated source (as of this morning too) on 2 amd64 systems (including the cursed R3240) I get the following error : cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/kern/kern_module.c /usr/src/sys/kern/kern_module.c:441: warning: "struct freebsd32_modstat_args" declared inside parameter list /usr/src/sys/kern/kern_module.c:441: warning: its scope is only this definition or declaration, which is probably notwhat you want /usr/src/sys/kern/kern_module.c:442: warning: no previous prototype for 'freebsd32_modstat' /usr/src/sys/kern/kern_module.c: In function `freebsd32_modstat': /usr/src/sys/kern/kern_module.c:451: error: dereferencing pointer to incomplete type /usr/src/sys/kern/kern_module.c:465: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/obj/usr/src/sys/CLK02. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Attached is my kernel file for my R3240 (my A8N is basically the same). Thanks for any help, Nicolas. --Boundary_(ID_D7qeCpnA75tVdU+tGkWaEA) Content-type: text/plain; charset=us-ascii; name=CLK02 Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=CLK02 # # COMPAQ R3240CA -- Kernel configuration file for FreeBSD/amd64 # machine amd64 cpu HAMMER ident CLK02 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler options PREEMPTION options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options NTFS # NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. options SMBFS #SMB/CIFS filesystem options NETSMB #SMB/CIFS requester options NETSMBCRYPTO #encrypted password support for SMB # mchain library. It can be either loaded as KLD or compiled into kernel options LIBMCHAIN options LIBICONV options LINPROCFS options COMPAT_43 options COMPAT_LINUX32 # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability options NO_MIXED_MODE # Don't penalize working chipsets # Bus support. Do not remove isa, even if you have no isa slots device acpi device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device agp # support several AGP chipsets device splash # Splash screen and screen saver support device sound device snd_ich # syscons is the default console driver, resembling an SCO console device sc # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) --Boundary_(ID_D7qeCpnA75tVdU+tGkWaEA)-- From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 20:47: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 9857316A4CE; Sat, 19 Feb 2005 20:47:12 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF5343D97; Sat, 19 Feb 2005 20:47:12 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd11.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1D2bUs-000891-01; Sat, 19 Feb 2005 21:46:38 +0100 Received: from Andro-Beta.Leidinger.net (TWxar4ZvYeG5Z2WdI7F3Mslm9Pr-chk5eO4WpgX+o1ndpH4h+LQSoK@[84.128.202.126]) by fmrl11.sul.t-online.com with esmtp id 1D2bUp-1PuyUS0; Sat, 19 Feb 2005 21:46:35 +0100 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) j1JKjwmC057413; Sat, 19 Feb 2005 21:45:58 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sat, 19 Feb 2005 21:47:19 +0100 From: Alexander Leidinger To: Peter Wemm Message-ID: <20050219214719.2b4c8c59@Magellan.Leidinger.net> In-Reply-To: <200502171411.15827.peter@wemm.org> References: <41F62EE7.6070808@fsn.hu> <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> <421337C2.7040800@fsn.hu> <200502171411.15827.peter@wemm.org> X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: TWxar4ZvYeG5Z2WdI7F3Mslm9Pr-chk5eO4WpgX+o1ndpH4h+LQSoK@t-dialin.net X-TOI-MSGID: b8e952a8-672b-43a0-834c-fead815bfa0b cc: amd64@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel message while running icc-em64t 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, 19 Feb 2005 20:47:12 -0000 On Thu, 17 Feb 2005 14:11:15 -0800 Peter Wemm wrote: > > >> fpudna: fpcurthread == curthread 2342 times > > >> fpudna: fpcurthread == curthread 2343 times > If I had to guess, I'd guess that it is trying to issue SSE3 > instructions to see if they work.. I think the question is: Does this needs to get printed and if yes, does the information it represents has to be that cryptic? Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 20:47: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 9857316A4CE; Sat, 19 Feb 2005 20:47:12 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF5343D97; Sat, 19 Feb 2005 20:47:12 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd11.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1D2bUs-000891-01; Sat, 19 Feb 2005 21:46:38 +0100 Received: from Andro-Beta.Leidinger.net (TWxar4ZvYeG5Z2WdI7F3Mslm9Pr-chk5eO4WpgX+o1ndpH4h+LQSoK@[84.128.202.126]) by fmrl11.sul.t-online.com with esmtp id 1D2bUp-1PuyUS0; Sat, 19 Feb 2005 21:46:35 +0100 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) j1JKjwmC057413; Sat, 19 Feb 2005 21:45:58 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sat, 19 Feb 2005 21:47:19 +0100 From: Alexander Leidinger To: Peter Wemm Message-ID: <20050219214719.2b4c8c59@Magellan.Leidinger.net> In-Reply-To: <200502171411.15827.peter@wemm.org> References: <41F62EE7.6070808@fsn.hu> <20050216110434.rmi718fcw0o44sgs@netchild.homeip.net> <421337C2.7040800@fsn.hu> <200502171411.15827.peter@wemm.org> X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: TWxar4ZvYeG5Z2WdI7F3Mslm9Pr-chk5eO4WpgX+o1ndpH4h+LQSoK@t-dialin.net X-TOI-MSGID: b8e952a8-672b-43a0-834c-fead815bfa0b cc: amd64@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel message while running icc-em64t 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, 19 Feb 2005 20:47:12 -0000 On Thu, 17 Feb 2005 14:11:15 -0800 Peter Wemm wrote: > > >> fpudna: fpcurthread == curthread 2342 times > > >> fpudna: fpcurthread == curthread 2343 times > If I had to guess, I'd guess that it is trying to issue SSE3 > instructions to see if they work.. I think the question is: Does this needs to get printed and if yes, does the information it represents has to be that cryptic? Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7