From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 15 11:05:13 2009 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD069106564A; Sun, 15 Feb 2009 11:05:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 56A6F8FC1A; Sun, 15 Feb 2009 11:05:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n1FB5AFb035731; Sun, 15 Feb 2009 06:05:10 -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.14.3/8.14.3) with ESMTP id n1FB5A3S065413; Sun, 15 Feb 2009 06:05:10 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4F3B27302F; Sun, 15 Feb 2009 06:05:10 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090215110510.4F3B27302F@freebsd-current.sentex.ca> Date: Sun, 15 Feb 2009 06:05:10 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.1/8983/Thu Feb 12 07:48:01 2009 clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2009 11:05:14 -0000 TB --- 2009-02-15 09:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-02-15 09:40:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-02-15 09:40:00 - cleaning the object tree TB --- 2009-02-15 09:40:52 - cvsupping the source tree TB --- 2009-02-15 09:40:52 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-02-15 09:41:00 - building world TB --- 2009-02-15 09:41:00 - MAKEOBJDIRPREFIX=/obj TB --- 2009-02-15 09:41:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-02-15 09:41:00 - TARGET=amd64 TB --- 2009-02-15 09:41:00 - TARGET_ARCH=amd64 TB --- 2009-02-15 09:41:00 - TZ=UTC TB --- 2009-02-15 09:41:00 - __MAKE_CONF=/dev/null TB --- 2009-02-15 09:41:00 - cd /src TB --- 2009-02-15 09:41:00 - /usr/bin/make -B buildworld >>> World build started on Sun Feb 15 09:41:02 UTC 2009 >>> 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 >>> stage 5.1: building 32 bit shim libraries [...] cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 netnatm/*.h /obj/amd64/src/lib32/usr/include/netnatm cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 netncp/*.h /obj/amd64/src/lib32/usr/include/netncp cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 netsmb/*.h /obj/amd64/src/lib32/usr/include/netsmb cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 nfs/*.h /obj/amd64/src/lib32/usr/include/nfs cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 nfsclient/*.h /obj/amd64/src/lib32/usr/include/nfsclient cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 nfsserver/*.h /obj/amd64/src/lib32/usr/include/nfsserver cd /src/include/../sys; sh /src/tools/install.sh -C -o root -g wheel -m 444 pccard/*.h /obj/amd64/src/lib32/usr/include/pccard install: pccard/*.h: No such file or directory *** Error code 71 Stop in /src/include. *** Error code 1 Stop in /src/include. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-02-15 11:05:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-02-15 11:05:10 - ERROR: failed to build world TB --- 2009-02-15 11:05:10 - 3992.06 user 389.40 system 5109.67 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 01:43:20 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5511F106566B for ; Mon, 16 Feb 2009 01:43:20 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 280AD8FC0A for ; Mon, 16 Feb 2009 01:43:20 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by wa-out-1112.google.com with SMTP id k34so1005829wah.27 for ; Sun, 15 Feb 2009 17:43:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EjvY5wf8FHSKma3mnXORDNjdSbCbn48OXzDBGv2Zk8g=; b=YaDmOpecjc1QLTkThyNDNPa9O+1276ATEbF7jKKCa3n7M9HnCNAZTrvd1eG32fUGqb 4pQZP+zvAgsCBYWz++WeoD8KnvCLCMyiHJsG7r8aAQ8pctimr42+8ZjBWSuOtOG9fuea eqGBQoOVA9F8nzAWaf4IJHfB0s+DALkjvmdGI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XoBEWxK8mBPWVIB6RpiRLZ940i0y2URnl7Rnm2fC54gb2tqKaVZ21kCVRTrZwT2DlL gwlprBbsahOWet2mJt+M1jlZ4tJoMCeJVNDKt7oVU6UQs91cvzbP/w8WgUQoXsVdEVM5 2xg0Bls0dRbbX1fnU+AsR1dBOC5XsvaTJDti8= MIME-Version: 1.0 Received: by 10.114.73.14 with SMTP id v14mr1890323waa.104.1234747347119; Sun, 15 Feb 2009 17:22:27 -0800 (PST) In-Reply-To: <442505824.71673.1234559053919.JavaMail.apache@mail53.abv.bg> References: <442505824.71673.1234559053919.JavaMail.apache@mail53.abv.bg> Date: Sun, 15 Feb 2009 17:22:27 -0800 Message-ID: <7d6fde3d0902151722x24aeed88na79ed5093f5d2569@mail.gmail.com> From: Garrett Cooper To: Mario Pavlov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: dev@lists.pcbsd.org, kris@pcbsd.com, freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [Fw: Re: [PC-BSD Dev] vmap()-like kernel interface ] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2009 01:43:20 -0000 On Fri, Feb 13, 2009 at 1:04 PM, Mario Pavlov wrote: > Hi, > please find the attached e-mail > > regards > mgp > > P.S. thanks, PC-BSD team I'm not a kernel dev, but I noted that pmap_unmapcontig doesn't take into consideration when va is NULL; I know it's bad driver programming if uncontig is implicitly called with NULL, but there should be some error handling or something here (a NULL deref will occur in pmap_qremove, which will cause a panic). Thanks, -Garrett From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 19:01:10 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 588241065673 for ; Tue, 17 Feb 2009 19:01:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id C389B8FC37 for ; Tue, 17 Feb 2009 19:01:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n1HJ17qb022115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 Feb 2009 06:01:07 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n1HJ16E7001788 for ; Wed, 18 Feb 2009 06:01:06 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n1HJ16Q6001787 for freebsd-amd64@freebsd.org; Wed, 18 Feb 2009 06:01:06 +1100 (EST) (envelope-from peter) Date: Wed, 18 Feb 2009 06:01:06 +1100 From: Peter Jeremy To: freebsd-amd64@freebsd.org Message-ID: <20090217190106.GB1351@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.19 (2009-01-05) Subject: 32-bit truncation of 64-bit values X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 19:01:11 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Having just tracked down an issue caused by a pointer-to-int truncation, it occurs to me that it might be "instructive" to change the amd64 memory map so that the botton 4GB of address-space was unmapped by default (ie code, data, bss, stack and mmap all default to above 4GB). I notice that the process space layout has already changed since 7.x was branched (at least the same executable runs on 7.x and SEGVs on -current due to a truncated pointer) and making this change might reveal more broken code. Given how close we are to 8.0, this might need to wait until after 8 is branched. --=20 Peter Jeremy --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmbCXIACgkQ/opHv/APuIe0jQCeMbNbzkt0l6QwMl9srEkWm1Um vhcAoJgA9OEiRGWHgdHGEV4dzRKqAQSq =qwXM -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 20:07:13 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32A60106566B for ; Tue, 17 Feb 2009 20:07:13 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout021.mac.com (asmtpout021.mac.com [17.148.16.96]) by mx1.freebsd.org (Postfix) with ESMTP id 1F2318FC16 for ; Tue, 17 Feb 2009 20:07:13 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from hsheth-mbp.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp021.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KF8001YD539MW10@asmtp021.mac.com> for freebsd-amd64@freebsd.org; Tue, 17 Feb 2009 11:06:46 -0800 (PST) Message-id: From: Marcel Moolenaar To: Peter Jeremy In-reply-to: <20090217190106.GB1351@server.vk2pj.dyndns.org> Date: Tue, 17 Feb 2009 11:06:45 -0800 References: <20090217190106.GB1351@server.vk2pj.dyndns.org> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-amd64@freebsd.org Subject: Re: 32-bit truncation of 64-bit values X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 20:07:13 -0000 On Feb 17, 2009, at 11:01 AM, Peter Jeremy wrote: > Having just tracked down an issue caused by a pointer-to-int > truncation, it occurs to me that it might be "instructive" to change > the amd64 memory map so that the botton 4GB of address-space was > unmapped by default (ie code, data, bss, stack and mmap all default to > above 4GB). I notice that the process space layout has already > changed since 7.x was branched (at least the same executable runs on > 7.x and SEGVs on -current due to a truncated pointer) and making > this change might reveal more broken code. Use ia64 :-) On ia64 the upper 3 bits of the 64-bit pointer are used for the region (there are 8 obviously). Region 0 is reserved for 32-bit processes, so all native processes have pointers that can't fit in an int. This used to be a *very* big problem, but it has improved significantly. If you cannot run on ia64, at least try compiling on ia64. The compiler for ia64 is more sensitive about these things so you may be able to spot potential problems at compile time. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 00:00:48 2009 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9199106566C; Wed, 18 Feb 2009 00:00:48 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9DAE08FC13; Wed, 18 Feb 2009 00:00:48 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n1I00jWW047487; Tue, 17 Feb 2009 19:00:45 -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.14.3/8.14.3) with ESMTP id n1I00jRS073180; Tue, 17 Feb 2009 19:00:45 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 890FF7302F; Tue, 17 Feb 2009 19:00:45 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090218000045.890FF7302F@freebsd-current.sentex.ca> Date: Tue, 17 Feb 2009 19:00:45 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 00:00:50 -0000 TB --- 2009-02-17 22:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-02-17 22:40:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-02-17 22:40:00 - cleaning the object tree TB --- 2009-02-17 22:40:50 - cvsupping the source tree TB --- 2009-02-17 22:40:50 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-02-17 22:40:58 - building world TB --- 2009-02-17 22:40:58 - MAKEOBJDIRPREFIX=/obj TB --- 2009-02-17 22:40:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-02-17 22:40:58 - TARGET=amd64 TB --- 2009-02-17 22:40:58 - TARGET_ARCH=amd64 TB --- 2009-02-17 22:40:58 - TZ=UTC TB --- 2009-02-17 22:40:58 - __MAKE_CONF=/dev/null TB --- 2009-02-17 22:40:58 - cd /src TB --- 2009-02-17 22:40:58 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 17 22:41:00 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/libevent -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../sys/contrib/pf -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/ftp-proxy/ftp-proxy.c cc -O2 -pipe -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/libevent -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../sys/contrib/pf -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/ftp-proxy/filter.c cc -O2 -pipe -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/libevent -I/src/usr.sbin/ftp-proxy/ftp-proxy/../../../sys/contrib/pf -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -o ftp-proxy ftp-proxy.o filter.o /obj/amd64/src/usr.sbin/ftp-proxy/ftp-proxy/../libevent/libevent.a gzip -cn /src/usr.sbin/ftp-proxy/ftp-proxy/../../../contrib/pf/ftp-proxy/ftp-proxy.8 > ftp-proxy.8.gz ===> usr.sbin/fwcontrol (all) cc -O2 -pipe -I/src/usr.sbin/fwcontrol -I/src/usr.sbin/fwcontrol/../../sys -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/fwcontrol/fwcontrol.c /src/usr.sbin/fwcontrol/fwcontrol.c: In function 'show_topology_map': /src/usr.sbin/fwcontrol/fwcontrol.c:546: error: 'struct ' has no member named 'phy_delay' *** Error code 1 Stop in /src/usr.sbin/fwcontrol. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-02-18 00:00:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-02-18 00:00:45 - ERROR: failed to build world TB --- 2009-02-18 00:00:45 - 3769.54 user 377.65 system 4845.09 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 07:57:58 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B973106564A for ; Wed, 18 Feb 2009 07:57:58 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from dir.bg (mail.dir.bg [194.145.63.28]) by mx1.freebsd.org (Postfix) with ESMTP id 9ECC78FC15 for ; Wed, 18 Feb 2009 07:57:56 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from [84.238.192.16] (account jgordeev@dir.bg [84.238.192.16] verified) by srv.dir.bg (CommuniGate Pro SMTP 5.2.12) with ESMTPSA id 67256522; Wed, 18 Feb 2009 09:27:53 +0200 Message-ID: <499BB870.9060801@dir.bg> Date: Wed, 18 Feb 2009 09:27:44 +0200 From: Jordan Gordeev User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20070606 X-Accept-Language: bg, en MIME-Version: 1.0 To: Peter Jeremy References: <20090217190106.GB1351@server.vk2pj.dyndns.org> In-Reply-To: <20090217190106.GB1351@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: 32-bit truncation of 64-bit values X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 07:57:58 -0000 Peter Jeremy wrote: >Having just tracked down an issue caused by a pointer-to-int >truncation, it occurs to me that it might be "instructive" to change >the amd64 memory map so that the botton 4GB of address-space was >unmapped by default (ie code, data, bss, stack and mmap all default to >above 4GB). I notice that the process space layout has already >changed since 7.x was branched (at least the same executable runs on >7.x and SEGVs on -current due to a truncated pointer) and making >this change might reveal more broken code. > >Given how close we are to 8.0, this might need to wait until after >8 is branched. > > > My understanding is that implementing this idea is impossible. The AMD64 ABI (available at http://www.x86-64.org/documentation/abi-0.99.pdf) describes several "code models": small, medium, large + some more. The most popular is the small memory model, which prescribes that both code and data fit into the first 2 GB of virtual address space. The medium code model lifts this limitation for data, but preserves it for text. The large memory model is of theoretical significance, in my opinion, and I'm not sure gcc even implements it. So, unless FreeBSD starts using its own amd64 ABI, or we start playing with unpopular (and slower) memory models, I don't see how the otherwise nice idea can be implemented. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 18:49:53 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 656C11065674 for ; Thu, 19 Feb 2009 18:49:53 +0000 (UTC) (envelope-from linux@chesterdkat.com) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by mx1.freebsd.org (Postfix) with ESMTP id 19B7B8FC22 for ; Thu, 19 Feb 2009 18:49:53 +0000 (UTC) (envelope-from linux@chesterdkat.com) Received: from [192.168.13.100] (pool-72-81-141-84.bltmmd.fios.verizon.net [72.81.141.84]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1LaDlu05A6-000NXE; Thu, 19 Feb 2009 13:37:19 -0500 Message-Id: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> From: "D.M. Ovad" To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 19 Feb 2009 13:37:16 -0500 X-Mailer: Apple Mail (2.930.3) X-Provags-ID: V01U2FsdGVkX1/D0uNQTi+VltWVq7pUF/d5tuC3drKVV8dnPts SgigKHzyPwnas8sT1Zq96x8/9rrEadYPASOnbrrdwXTIAOYr2N 0vVAA1fjlt2LgFkH3K6mdc6rtaG28en Subject: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 18:49:54 -0000 I am compiling a custom kernel to add Netatalk capability and weed out unnecessary drivers. My system has two Intel Xeon Quad Core processors. It's not clear to me what I should specify in the "cpu" field. The default kernel specifies the cpu as "HAMMER". Is this also correct for a dual quad core Intel Xeon system? Thanks... From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 18:54:51 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C10A11065672 for ; Thu, 19 Feb 2009 18:54:51 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from dir.bg (mail.dir.bg [194.145.63.28]) by mx1.freebsd.org (Postfix) with ESMTP id 0DA3B8FC0C for ; Thu, 19 Feb 2009 18:54:50 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from [84.238.192.16] (account jgordeev@dir.bg HELO sometimes2.studgrad.net) by srv.dir.bg (CommuniGate Pro SMTP 5.2.12) with ESMTPSA id 67533289; Thu, 19 Feb 2009 20:54:48 +0200 Message-ID: <499DAAF8.4030005@dir.bg> Date: Thu, 19 Feb 2009 20:54:48 +0200 From: Jordan Gordeev User-Agent: Mozilla/5.0 (X11; U; DragonFly i386; en-US; rv:1.8.1.19) Gecko/20090204 SeaMonkey/1.1.14 MIME-Version: 1.0 To: "D.M. Ovad" References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> In-Reply-To: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 18:54:52 -0000 D.M. Ovad wrote: > I am compiling a custom kernel to add Netatalk capability and weed out > unnecessary drivers. My system has two Intel Xeon Quad Core > processors. It's not clear to me what I should specify in the "cpu" > field. The default kernel specifies the cpu as "HAMMER". Is this > also correct for a dual quad core Intel Xeon system? > > Thanks... It is the only value that you can put there AFAIK. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 19:08:58 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27A411065670 for ; Thu, 19 Feb 2009 19:08:58 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mx1.freebsd.org (Postfix) with ESMTP id B04AD8FC14 for ; Thu, 19 Feb 2009 19:08:57 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: by fxm12 with SMTP id 12so121058fxm.19 for ; Thu, 19 Feb 2009 11:08:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eAQxarWH6sjYyOdLE6fGIE8caQ2llPX4nfJgvLGGmhs=; b=YOaNnZjMRxoGJL2QMb1vAHiHFXINkGRIhKDOVTzvSzrsOuhdF99QSwWqB1+/+9uQQf WTEHqt0ed8qQk4vReZuf3cNr04I3K3nYQbzOQSD1SzMfAn0RGPiAh+0Eos8FJwMy2Kb3 MT/uZqUh5Jz7KQkupBENrpFd+0YMAjSvVSPuE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=La6nu0IkRfkv+fjkMkwNm33wgAQTYp8E49FKrooDXkc8VlwlZfcoIRlvK0gZUKWyoj AYip9u5TeHb+/wCBN8wAOuKWvTZbszkn7TJPLXrehV+VL7ypU/4sHu+vtnI6uGkXNDRa nBF01A8HEEx9UH0tyqao1QwKZTemagWUwH+GU= MIME-Version: 1.0 Received: by 10.103.49.12 with SMTP id b12mr903789muk.65.1235070536805; Thu, 19 Feb 2009 11:08:56 -0800 (PST) In-Reply-To: <499DAAF8.4030005@dir.bg> References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> <499DAAF8.4030005@dir.bg> Date: Thu, 19 Feb 2009 20:08:56 +0100 Message-ID: <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> From: Oliver Pinter To: Jordan Gordeev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "D.M. Ovad" , freebsd-amd64@freebsd.org Subject: Re: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 19:08:58 -0000 add this line to /etc/make.conf CPUTYPE?=core2 On 2/19/09, Jordan Gordeev wrote: > D.M. Ovad wrote: >> I am compiling a custom kernel to add Netatalk capability and weed out >> unnecessary drivers. My system has two Intel Xeon Quad Core >> processors. It's not clear to me what I should specify in the "cpu" >> field. The default kernel specifies the cpu as "HAMMER". Is this >> also correct for a dual quad core Intel Xeon system? >> >> Thanks... > It is the only value that you can put there AFAIK. > _______________________________________________ > 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 Thu Feb 19 22:27:43 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13302106567A; Thu, 19 Feb 2009 22:27:43 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DB79F8FC36; Thu, 19 Feb 2009 22:27:42 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1JMRgbC060686; Thu, 19 Feb 2009 22:27:42 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1JMRg7a060682; Thu, 19 Feb 2009 22:27:42 GMT (envelope-from gavin) Date: Thu, 19 Feb 2009 22:27:42 GMT Message-Id: <200902192227.n1JMRg7a060682@freefall.freebsd.org> To: mail@rudybrinkman.nl, gavin@FreeBSD.org, freebsd-amd64@FreeBSD.org, gavin@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: amd64/116670: [ata] onboard SATA RAID1 controllers not supported for Asus M2A-VM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 22:27:43 -0000 Synopsis: [ata] onboard SATA RAID1 controllers not supported for Asus M2A-VM State-Changed-From-To: feedback->closed State-Changed-By: gavin State-Changed-When: Thu Feb 19 22:26:50 UTC 2009 State-Changed-Why: Feedback timeout (1 year), not enough info to resolve as-is. To submitter: if you can provide the requested info, we can see about getting this sorted. Responsible-Changed-From-To: freebsd-amd64->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Thu Feb 19 22:26:50 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=116670 From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 14:22:46 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F1AB106564A for ; Fri, 20 Feb 2009 14:22:46 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.freebsd.org (Postfix) with ESMTP id 18EDB8FC19 for ; Fri, 20 Feb 2009 14:22:45 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from HDLDESKTOP64 (hdl-desktop-64.leadmon.net [207.114.24.3]) (authenticated bits=0) by ibm.leadmon.net (8.14.3/8.14.3/LNSG+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id n1KE6Em2073546; Fri, 20 Feb 2009 09:06:14 -0500 (EST) (envelope-from howard@leadmon.net) X-DKIM: Sendmail DKIM Filter v2.7.2 ibm.leadmon.net n1KE6Em2073546 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leadmon.net; s=default; t=1235138774; bh=vYVztnDYVXV/HXj0ecUUfXxnoYUT45ekHh1FF9v 0+hY=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=rNPrxR36wGj xH53F0nJJGIxOUgetCS4AH0iauiJKzfSxrMZC92MN0kHc04doLXjCbsN7wDB7IOfm66 RMBoCens2H5BqRoOvEM/JVmZvKqXZxpNijanqMdad5upqcE+7iTUGa174BCsPTKval6 Fpb4QYbgFyvt+Euh/DtF1Yt/IY= X-DomainKeys: Sendmail DomainKeys Filter v1.0.1 ibm.leadmon.net n1KE6Em2073546 DomainKey-Signature: a=rsa-sha1; s=default; d=leadmon.net; c=simple; q=dns; h=x-senderid:authentication-results:from:to:cc:references: in-reply-to:subject:date:message-id:mime-version:content-type: content-transfer-encoding:x-mailer:thread-index:content-language; b=DmBWbGTQTtZN6+0JFsNrfIsSF6HjoloJrYWwboLSgDlKarSYhThsGBhzM3EnKJqVZ Fd34gOU01CCb9VVZpjPK9O8wXCeW30s9apr0e7Au8Z9aXMgfWhvtdbA3Mt+YMLyF+g/ V0lWZDirUW55NWvJeD6olyWfKAiWvW2btPZBDpE= X-SenderID: Sendmail Sender-ID Filter v1.0.0 ibm.leadmon.net n1KE6Em2073546 Authentication-Results: ibm.leadmon.net; sender-id=pass header.from=howard@leadmon.net; spf=pass smtp.mfrom=howard@leadmon.net From: "Howard Leadmon" To: "'Oliver Pinter'" References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> <499DAAF8.4030005@dir.bg> <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> In-Reply-To: <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> Date: Fri, 20 Feb 2009 09:05:46 -0500 Message-ID: <013f01c99364$5689e4a0$039dade0$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcmSxY5G8/behKEyQ9aXvF0cUra0KgAngiDw Content-Language: en-us X-Virus-Scanned: ClamAV 0.94.2/9016/Thu Feb 19 23:03:22 2009 on ibm.leadmon.net X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: RE: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 14:22:46 -0000 I knew HAMMER was the only type for making your kernel, but what CPUTYPE's are OK for 64bit? I was under the impression that nocona was the 64bit processor, but guess maybe there are more. I don't have a quad, but do have a pair of dual core processors in a few machines that are running FBSD7. CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf48 Stepping = 8 Features=0xbfebfbff Features2=0x649d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs So should this stuff be set to nocona, core2, or what?? --- Howard > -----Original Message----- > Subject: Re: Intel Xeon Processor kernel compile CPU type. > > add this line to /etc/make.conf > > CPUTYPE?=core2 > > > On 2/19/09, Jordan Gordeev wrote: > > D.M. Ovad wrote: > >> I am compiling a custom kernel to add Netatalk capability and weed out > >> unnecessary drivers. My system has two Intel Xeon Quad Core > >> processors. It's not clear to me what I should specify in the "cpu" > >> field. The default kernel specifies the cpu as "HAMMER". Is this > >> also correct for a dual quad core Intel Xeon system? > >> > >> Thanks... > > It is the only value that you can put there AFAIK. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 16:10:06 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12D28106566C for ; Fri, 20 Feb 2009 16:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E2F838FC14 for ; Fri, 20 Feb 2009 16:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1KGA5JE093651 for ; Fri, 20 Feb 2009 16:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1KGA5Fr093650; Fri, 20 Feb 2009 16:10:05 GMT (envelope-from gnats) Resent-Date: Fri, 20 Feb 2009 16:10:05 GMT Resent-Message-Id: <200902201610.n1KGA5Fr093650@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, Arne Steinkamm Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 925311065670 for ; Fri, 20 Feb 2009 16:08:35 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 80A738FC08 for ; Fri, 20 Feb 2009 16:08:35 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n1KG8ZOI071401 for ; Fri, 20 Feb 2009 16:08:35 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n1KG8YOK071388; Fri, 20 Feb 2009 16:08:34 GMT (envelope-from nobody) Message-Id: <200902201608.n1KG8YOK071388@www.freebsd.org> Date: Fri, 20 Feb 2009 16:08:34 GMT From: Arne Steinkamm To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Fri, 20 Feb 2009 16:37:50 +0000 Cc: Subject: amd64/131906: SATA data corruption X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 16:10:06 -0000 >Number: 131906 >Category: amd64 >Synopsis: SATA data corruption >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 20 16:10:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Arne Steinkamm >Release: 7.1-RELEASE >Organization: >Environment: FreeBSD amd64.lab.steinkamm.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Machine has (old) Asus A8V Deluxe Motherboard with onboard Promise SATA controller. Promise is BIOS-configured to RAID mode. Machine is equipped with 4 gig mem, memory hole handling is switched off in BIOS. CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2202.83-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 [...] Cores per package: 2 usable memory = 3341815808 (3187 MB) avail memory = 3231543296 (3081 MB) [...] atapci0: port 0x9000-0x903f,0x8800-0x880f,0x8400-0x847f mem 0xf9700000-0xf9700fff,0xf9600000-0xf961ffff irq 18 at device 8.0 on pci0 [...] ad4: 1430799MB at ata2-master SATA150 ad6: 1430799MB at ata3-master SATA150 ar0: 1430511MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master I have several of these boxes in daily use without any problems running FreeBSD 6.2 i386 and amd64. I installed a fresh installation of 7.1 release (GENERIC kernel from distribution) from CD and saw data corruption on the disks: $ df . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ar0s2f 1361274282 883732236 368640104 71% /l/ldisk1 $ ls -l Testfile* -rw-r--r-- 1 root wheel 2810811312 Dec 31 01:14 Testfile1 -rw-r--r-- 1 root wheel 2926088400 Dec 31 01:59 Testfile2 -rw-r--r-- 1 root wheel 2798053632 Dec 31 02:45 Testfile3 $ md5 Testfile* MD5 (Testfile1) = 14f9908220acd2388ec09703dc8baaad MD5 (Testfile2) = c6f2c84ec25fd97985b6374bdc89b343 MD5 (Testfile3) = 5630706a77bc7ee965076ba2a7a8dcdf $ md5 Testfile* MD5 (Testfile1) = d215c9fb3369d125d17e579f5ddf7ca8 MD5 (Testfile2) = c6f2c84ec25fd97985b6374bdc89b343 MD5 (Testfile3) = 8632aa26eec5966a49323c714f9b085e $ md5 Testfile* MD5 (Testfile1) = fb4d186d5fb900dd9271049e29eab152 MD5 (Testfile2) = 429511875320aef36a700ef67d1462c2 MD5 (Testfile3) = f7be094c9a38c198152536dffca3d733 Trying to find the problem, I booted the system from CD and accessed the subdisks ad4 and ad6 directly. Same problem with both disks so it seems not related to the ar0 device and the software raid behind it. Then I booted FreeBSD 7.1-Release i386 from CD and found no problem anymore. This indicates that the hardware is not part of the problem. Full dmesg: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2202.83-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x3 Cores per package: 2 usable memory = 3341815808 (3187 MB) avail memory = 3231543296 (3081 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, c7ef0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xfb000000-0xfbffffff,0xe0000000-0xefffffff,0xfa000000-0xfaffffff irq 16 at device 0.0 on pci1 fwohci0: port 0x8000-0x807f mem 0xf9500000-0xf95007ff irq 16 at device 7.0 on pci0 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:00:6f:2b:1e fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x28c4000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:6f:2b:1e fwe0: Ethernet address: 02:11:d8:6f:2b:1e fwip0: on firewire0 fwip0: Firewire address: 00:11:d8:00:00:6f:2b:1e @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode atapci0: port 0x9000-0x903f,0x8800-0x880f,0x8400-0x847f mem 0xf9700000-0xf9700fff,0xf9600000-0xf961ffff irq 18 at device 8.0 on pci0 atapci0: [ITHREAD] atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] vgapci1: mem 0xf8000000-0xf8ffffff,0xd0000000-0xdfffffff,0xf7000000-0xf7ffffff irq 16 at device 9.0 on pci0 skc0: port 0x9400-0x94ff mem 0xf9a00000-0xf9a03fff irq 17 at device 10.0 on pci0 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 sk0: Ethernet address: 00:15:f2:0a:78:17 miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0: [ITHREAD] atapci1: port 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem 0xf9c00000-0xf9c003ff irq 19 at device 14.0 on pci0 atapci1: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] atapci2: port 0xd000-0xd007,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xb800-0xb80f,0xb400-0xb4ff irq 20 at device 15.0 on pci0 atapci2: [ITHREAD] ata9: on atapci2 ata9: [ITHREAD] ata10: on atapci2 ata10: [ITHREAD] atapci3: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci3 ata0: [ITHREAD] ata1: on atapci3 ata1: [ITHREAD] uhci0: port 0xd400-0xd41f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe000-0xe01f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xe400-0xe41f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf9e00000-0xf9e000ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered umass0: on uhub4 isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A sio1: [FILTER] cpu0: on acpi0 powernow0: on cpu0 device_attach: powernow0 attach returned 6 cpu1: on acpi0 powernow1: on cpu1 device_attach: powernow1 attach returned 6 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) acd0: CDRW at ata0-master UDMA33 ad4: 1430799MB at ata2-master SATA150 ad6: 1430799MB at ata3-master SATA150 ar0: 1430511MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master SMP: AP CPU #1 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ar0s1a pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x80a31043 chip=0x02821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI hostb1@pci0:0:0:1: class=0x060000 card=0x00000000 chip=0x12821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI hostb2@pci0:0:0:2: class=0x060000 card=0x00000000 chip=0x22821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI hostb3@pci0:0:0:3: class=0x060000 card=0x00000000 chip=0x32821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI hostb4@pci0:0:0:4: class=0x060000 card=0x00000000 chip=0x42821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI hostb5@pci0:0:0:7: class=0x060000 card=0x00000000 chip=0x72821106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8T880Pro CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x00000000 chip=0xb1881106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'VT8237 K8HTB CPU to AGP 2.0/3.0 Bridge' class = bridge subclass = PCI-PCI fwohci0@pci0:0:7:0: class=0x0c0010 card=0x808a1043 chip=0x30441106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' class = serial bus subclass = FireWire atapci0@pci0:0:8:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20378 FastTrak 378/SATA 378 RAID Controller' class = mass storage subclass = RAID vgapci1@pci0:0:9:0: class=0x030000 card=0x00000000 chip=0x022110de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'GeForce 6200' class = display subclass = VGA skc0@pci0:0:10:0: class=0x020000 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet atapci1@pci0:0:14:0: class=0x010400 card=0x31141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'Sil 3114 SATALink/SATARaid Controller' class = mass storage subclass = RAID atapci2@pci0:0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 VT6410 SATA RAID Controller' class = mass storage subclass = RAID atapci3@pci0:0:15:1: class=0x01018a card=0x80ed1043 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C586A/B/VT82C686/A/B/VT823x/A/C Bus Master IDE Controller' class = mass storage subclass = ATA uhci0@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host Controller' class = serial bus subclass = USB uhci1@pci0:0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host Controller' class = serial bus subclass = USB uhci2@pci0:0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host Controller' class = serial bus subclass = USB uhci3@pci0:0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT83C572, VT6202 VIA Rev 5 or later USB Universal Host Controller' class = serial bus subclass = USB ehci0@pci0:0:16:4: class=0x0c0320 card=0x80ed1043 chip=0x31041106 rev=0x86 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202/12 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:0:17:0: class=0x060100 card=0x80ed1043 chip=0x32271106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 PCI-to-ISA Bridge' class = bridge subclass = PCI-ISA none0@pci0:0:17:5: class=0x040100 card=0x812a1043 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 AC97 Enhanced Audio Controller - the 8251 controller is different' class = multimedia subclass = audio hostb6@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = '(K8) Athlon 64/Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb7@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = '(K8) Athlon 64/Opteron Address Map' class = bridge subclass = HOST-PCI hostb8@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = '(K8) Athlon 64/Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb9@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = '(K8) Athlon 64/Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI vgapci0@pci0:1:0:0: class=0x030000 card=0x080110b0 chip=0x00f510de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'GeForce 7800 GS' class = display subclass = VGA >How-To-Repeat: Just check the integrity of large files (several gigabytes) after writing them. Files fitting in the filesystem cache will hide the sata problem. >Fix: Using FreeBSD 6.x amd64 or FreeBSD 7.1 i386 instead of FreeBSD 7.1 amd64. This is not a sollution! >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 19:11:48 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC226106566B for ; Fri, 20 Feb 2009 19:11:48 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.freebsd.org (Postfix) with ESMTP id 634B18FC1C for ; Fri, 20 Feb 2009 19:11:48 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr8.xs4all.nl (8.13.8/8.13.8) with ESMTP id n1KIxSo5003910; Fri, 20 Feb 2009 19:59:28 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 533DCBA97; Fri, 20 Feb 2009 19:59:28 +0100 (CET) Date: Fri, 20 Feb 2009 19:59:28 +0100 From: Roland Smith To: Howard Leadmon Message-ID: <20090220185928.GB7314@slackbox.xs4all.nl> References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> <499DAAF8.4030005@dir.bg> <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> <013f01c99364$5689e4a0$039dade0$@net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JYK4vJDZwFMowpUq" Content-Disposition: inline In-Reply-To: <013f01c99364$5689e4a0$039dade0$@net> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.19 (2009-01-05) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 19:11:49 -0000 --JYK4vJDZwFMowpUq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 20, 2009 at 09:05:46AM -0500, Howard Leadmon wrote: > I knew HAMMER was the only type for making your kernel, but what CPUTYPE= 's > are OK for 64bit?=20 > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf48 Stepping =3D 8 > =20 > Features=3D0xbfebfbff ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=3D0x649d > AMD Features=3D0x20100800 > AMD Features2=3D0x1 > Cores per package: 2 > Logical CPUs per core: 2 > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs >=20 > So should this stuff be set to nocona, core2, or what?? Have a look at /usr/share/mk/bsd.cpu.mk. If you are using the amd64 architecture, you can use CPUTYPE=3Dprescott or CPUTYPE=3Dcore2, but both will be converted to CPUTYPE=3Dnocona. That's probably because that is the latest variant that the gcc in base understands. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --JYK4vJDZwFMowpUq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkme/ZAACgkQEnfvsMMhpyWvkQCfWjwdM9kDps8Qf6x72H/amDu4 YzIAoK4c2vvoDKGmFh8wW1ODSzAy7fRd =utvE -----END PGP SIGNATURE----- --JYK4vJDZwFMowpUq-- From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 23:45:58 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A7781065674 for ; Fri, 20 Feb 2009 23:45:58 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.freebsd.org (Postfix) with ESMTP id 0E15D8FC16 for ; Fri, 20 Feb 2009 23:45:57 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from HDLDESKTOP64 (hdl-desktop-64.leadmon.net [207.114.24.3]) (authenticated bits=0) by ibm.leadmon.net (8.14.3/8.14.3/LNSG+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id n1KNjulg026749; Fri, 20 Feb 2009 18:45:57 -0500 (EST) (envelope-from howard@leadmon.net) X-DKIM: Sendmail DKIM Filter v2.7.2 ibm.leadmon.net n1KNjulg026749 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leadmon.net; s=default; t=1235173557; bh=h1z75Sgby2eKNA8B7lRULWU6YrEZzBAr7byQOxV hV9I=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=TaiQOhu4Arx TO/R9csECvc/uZsAb+W3DEcmIh6dpdcaa9mzFTlE+9ACCcizc7hjuMp0LWXGs7MH8gB d2G7AoQstyQjm9O+7etGjCbJo0UdPXevD0vzhifjcjJ22sG3pAbisivRniKdasm+K9M Wdl/t9eXDssknE3L86gUaNyHFo= X-DomainKeys: Sendmail DomainKeys Filter v1.0.1 ibm.leadmon.net n1KNjulg026749 DomainKey-Signature: a=rsa-sha1; s=default; d=leadmon.net; c=simple; q=dns; h=x-senderid:authentication-results:from:to:cc:references: in-reply-to:subject:date:message-id:mime-version:content-type: content-transfer-encoding:x-mailer:thread-index:content-language; b=qn2fXPgjBBJpbXcXuQprJJFhNcd49MFbEAQbf+nBE8zmOf0sOX91j2ROUI/lRPwDI reFJ9J+8p5UHKvbzLv+krcHLf4yq1IbiZX4MP69YGaIiZQnzaEsIteBWOSOcblnB2tz JVmYgjiP3HqpqKh0oSRSLRqXIWrMBczeRaKXZIo= X-SenderID: Sendmail Sender-ID Filter v1.0.0 ibm.leadmon.net n1KNjulg026749 Authentication-Results: ibm.leadmon.net; sender-id=pass header.from=howard@leadmon.net; spf=pass smtp.mfrom=howard@leadmon.net From: "Howard Leadmon" To: "'Roland Smith'" References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> <499DAAF8.4030005@dir.bg> <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> <013f01c99364$5689e4a0$039dade0$@net> <20090220185928.GB7314@slackbox.xs4all.nl> In-Reply-To: <20090220185928.GB7314@slackbox.xs4all.nl> Date: Fri, 20 Feb 2009 18:45:28 -0500 Message-ID: <01b401c993b5$525b7960$f7126c20$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcmTjWDFepkYGGVMTE6JCRXU211NVAAJ6cTw Content-Language: en-us X-Virus-Scanned: ClamAV 0.94.2/9018/Fri Feb 20 14:07:43 2009 on ibm.leadmon.net X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: RE: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 23:45:58 -0000 Good, so nocona is really the right one to specify. Good to know I have been doing it correctly on my x64 machines, and heck nice document/defines there, I'll keep that in my notes so I know how to find stuff like that in the future.. --- Howard Leadmon > -----Original Message----- > From: Roland Smith [mailto:rsmith@xs4all.nl] > Sent: Friday, February 20, 2009 1:59 PM > To: Howard Leadmon > Cc: 'Oliver Pinter'; freebsd-amd64@freebsd.org > Subject: Re: Intel Xeon Processor kernel compile CPU type. > > On Fri, Feb 20, 2009 at 09:05:46AM -0500, Howard Leadmon wrote: > > I knew HAMMER was the only type for making your kernel, but what > CPUTYPE's > > are OK for 64bit? > > > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU) > > Origin = "GenuineIntel" Id = 0xf48 Stepping = 8 > > > > > Features=0xbfebfbff CA > > ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0x649d > > AMD Features=0x20100800 > > AMD Features2=0x1 > > Cores per package: 2 > > Logical CPUs per core: 2 > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > > So should this stuff be set to nocona, core2, or what?? > > Have a look at /usr/share/mk/bsd.cpu.mk. If you are using the amd64 > architecture, you can use CPUTYPE=prescott or CPUTYPE=core2, but both > will be converted to CPUTYPE=nocona. That's probably because that is the > latest variant that the gcc in base understands. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 00:55:57 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CC69106564A for ; Sat, 21 Feb 2009 00:55:57 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 0366C8FC13 for ; Sat, 21 Feb 2009 00:55:56 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so450609ywt.13 for ; Fri, 20 Feb 2009 16:55:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=QsevqtBjYoQ+PDYGB73hfBQqc5fEhyBF5XlTOfVlASk=; b=fKxRC2ZcRx5X8H8wfKD/Zfg70WvgS1GMhpi5y48Nf588Nm7QRv/EYjYPra2GNpQZxh Dh2O2zqnvabPJCFzZviCYXCoU8jDD39F5oVuTssSIhFV1d93pb8aErDwHT7vHrTaMQKl km+Khp8PuDh2Y/YM3MeZl2T/DJOvXodd6GYF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qgJQ3hz7XYV5t1uIqf32medu4lBkxtLLMgPk5VhWlx1geYu+ZQH27SPVwyIlKX3bYV 8wG7skFaRof8OH9x+196/t9Y4iIgtiAxxNoqAd9ULNBKPkrw812TycS0gDh17DYLZ51r dVB/Ffr0cQsMH22CMm8p+UUtAFMkbRQ3FttLQ= MIME-Version: 1.0 Received: by 10.90.35.15 with SMTP id i15mr105092agi.83.1235177755995; Fri, 20 Feb 2009 16:55:55 -0800 (PST) In-Reply-To: <01b401c993b5$525b7960$f7126c20$@net> References: <9D0C41D6-5EDB-4D17-8258-352FE8ADAFBD@chesterdkat.com> <499DAAF8.4030005@dir.bg> <6101e8c40902191108w2234b13k84466dfd9f1fe4ee@mail.gmail.com> <013f01c99364$5689e4a0$039dade0$@net> <20090220185928.GB7314@slackbox.xs4all.nl> <01b401c993b5$525b7960$f7126c20$@net> Date: Fri, 20 Feb 2009 16:55:55 -0800 Message-ID: <7d6fde3d0902201655r5a69985cubd8f21fb38b0771@mail.gmail.com> From: Garrett Cooper To: Howard Leadmon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Xeon Processor kernel compile CPU type. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 00:55:57 -0000 On Fri, Feb 20, 2009 at 3:45 PM, Howard Leadmon wrote: > Good, so nocona is really the right one to specify. Good to know I have > been doing it correctly on my x64 machines, and heck nice document/defines > there, I'll keep that in my notes so I know how to find stuff like that in > the future.. > > > --- > Howard Leadmon > > >> -----Original Message----- >> From: Roland Smith [mailto:rsmith@xs4all.nl] >> Sent: Friday, February 20, 2009 1:59 PM >> To: Howard Leadmon >> Cc: 'Oliver Pinter'; freebsd-amd64@freebsd.org >> Subject: Re: Intel Xeon Processor kernel compile CPU type. >> >> On Fri, Feb 20, 2009 at 09:05:46AM -0500, Howard Leadmon wrote: >> > I knew HAMMER was the only type for making your kernel, but what >> CPUTYPE's >> > are OK for 64bit? >> >> > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU) >> > Origin = "GenuineIntel" Id = 0xf48 Stepping = 8 >> > >> > >> Features=0xbfebfbff> CA >> > ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >> > Features2=0x649d >> > AMD Features=0x20100800 >> > AMD Features2=0x1 >> > Cores per package: 2 >> > Logical CPUs per core: 2 >> > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs >> > >> > So should this stuff be set to nocona, core2, or what?? >> >> Have a look at /usr/share/mk/bsd.cpu.mk. If you are using the amd64 >> architecture, you can use CPUTYPE=prescott or CPUTYPE=core2, but both >> will be converted to CPUTYPE=nocona. That's probably because that is the >> latest variant that the gcc in base understands. I know it's already been said, but Intel recommends (with the compiler version that we have) to use prescott for i686 and nocona for amd64 because it best matches the caching / instruction scheduling for the Core 2 CPU's. If we actually move to gcc 4.3+ they have improved support for -march=core2. HTH, -Garrett