From owner-freebsd-amd64@FreeBSD.ORG Mon May 31 04:59:48 2010 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 206B2106564A; Mon, 31 May 2010 04:59:48 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EB8438FC1C; Mon, 31 May 2010 04:59:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o4V4xkpa050120; Mon, 31 May 2010 04:59:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o4V4xkKQ050116; Mon, 31 May 2010 04:59:46 GMT (envelope-from linimon) Date: Mon, 31 May 2010 04:59:46 GMT Message-Id: <201005310459.o4V4xkKQ050116@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/146661: [ata] damage files on ufs on ata pseudo raid when running find from script 100.chksetuid 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, 31 May 2010 04:59:48 -0000 Old Synopsis: damage files on ufs on ata pseudo raid when running find from script 100.chksetuid New Synopsis: [ata] damage files on ufs on ata pseudo raid when running find from script 100.chksetuid Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 31 04:59:04 UTC 2010 Responsible-Changed-Why: This is probably not amd64-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=146661 From owner-freebsd-amd64@FreeBSD.ORG Mon May 31 05:02:03 2010 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 F0BA41065673; Mon, 31 May 2010 05:02:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C7F9A8FC12; Mon, 31 May 2010 05:02:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o4V523Tw059614; Mon, 31 May 2010 05:02:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o4V523eI059610; Mon, 31 May 2010 05:02:03 GMT (envelope-from linimon) Date: Mon, 31 May 2010 05:02:03 GMT Message-Id: <201005310502.o4V523eI059610@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-jail@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/147162: [jail] [panic] Page Fault / Kernel panic when jail starts on boot 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, 31 May 2010 05:02:04 -0000 Old Synopsis: Page Fault / Kernel panic when jail starts on boot New Synopsis: [jail] [panic] Page Fault / Kernel panic when jail starts on boot Responsible-Changed-From-To: freebsd-amd64->freebsd-jail Responsible-Changed-By: linimon Responsible-Changed-When: Mon May 31 05:01:35 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=147162 From owner-freebsd-amd64@FreeBSD.ORG Mon May 31 11:06:52 2010 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 0A5D61065677 for ; Mon, 31 May 2010 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D234B8FC1F for ; Mon, 31 May 2010 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o4VB6pht045929 for ; Mon, 31 May 2010 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o4VB6pgk045927 for freebsd-amd64@FreeBSD.org; Mon, 31 May 2010 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 31 May 2010 11:06:51 GMT Message-Id: <201005311106.o4VB6pgk045927@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org 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, 31 May 2010 11:06:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/145991 amd64 [patch] Add a requires line to /sys/amd64/conf/NOTES o amd64/145873 amd64 [build] cannot buildworld 8.0-STABLE o amd64/145761 amd64 [lor] rt2870 lock order reversal hold up system in 8.0 o amd64/145039 amd64 spin lock held too long amd64 mp_machdep.c o amd64/144756 amd64 [panic] Transferring files on samba causes the kernel f amd64/144503 amd64 [boot] 8.0-RELEASE does not boot on DL585 [regression] o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t o amd64/144376 amd64 [panic] continuous reboot on motherboards with ATI SB7 f amd64/144151 amd64 [ata] Can not burn CD/DVD with AHCI enabled f amd64/144113 amd64 [ata] 8.0-RELEASE fails to detect SATA hard disks on a o amd64/143992 amd64 [panic] Random reboot o amd64/143854 amd64 [build] error in make world during upgrade from 7 to 8 s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' o amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/141112 amd64 [ata] [panic] Kernel panic when booting with any sATA o amd64/141060 amd64 [install] Can't install 8.0-RELEASE on the server wher o amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit o amd64/140596 amd64 [panic] Kernel panic/crash o amd64/140391 amd64 [hang] powerd(8) freezes computer on Phenom II compute o amd64/140145 amd64 [boot] Installation boot sequence freezes o amd64/139998 amd64 [panic] 7.2 amd64 panic in kern_mutex.c:339 o amd64/139924 amd64 [boot] cd or dvd not load o amd64/139614 amd64 [minidump] minidumps fail when many interrupts fire f amd64/138661 amd64 [panic] Kernel Panic after typing "reboot" o amd64/138029 amd64 [panic] periodically kernel panic and reboot o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT f amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 f amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe o amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd p amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 108 problems total. From owner-freebsd-amd64@FreeBSD.ORG Fri May 28 13:32:30 2010 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 0C3721065676; Fri, 28 May 2010 13:32:30 +0000 (UTC) (envelope-from mcj@bluetonic.org) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D1E4C8FC18; Fri, 28 May 2010 13:32:29 +0000 (UTC) Received: by pwj4 with SMTP id 4so673707pwj.13 for ; Fri, 28 May 2010 06:32:29 -0700 (PDT) Received: by 10.140.179.25 with SMTP id b25mr204612rvf.54.1275052023691; Fri, 28 May 2010 06:07:03 -0700 (PDT) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx.google.com with ESMTPS id h11sm2035255rvm.9.2010.05.28.06.07.02 (version=SSLv3 cipher=RC4-MD5); Fri, 28 May 2010 06:07:02 -0700 (PDT) Received: by pvg16 with SMTP id 16so542527pvg.13 for ; Fri, 28 May 2010 06:07:01 -0700 (PDT) Received: by 10.143.85.4 with SMTP id n4mr130177wfl.312.1275052021203; Fri, 28 May 2010 06:07:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.30.7 with HTTP; Fri, 28 May 2010 06:06:41 -0700 (PDT) In-Reply-To: <4BFF894F.4010008@icyb.net.ua> References: <060401cafe37$a411b240$ec3516c0$__21811.5672738806$1275032797$gmane$org@net> <4BFF894F.4010008@icyb.net.ua> From: Carey Jones Date: Fri, 28 May 2010 08:06:41 -0500 Message-ID: To: amd64@freebsd.org, freebsd-fs@freebsd.org X-Mailman-Approved-At: Tue, 01 Jun 2010 05:33:30 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 28 May 2010 13:32:30 -0000 On Fri, May 28, 2010 at 4:13 AM, Andriy Gapon wrote: > on 28/05/2010 10:30 Howard Leadmon said the following: > > panic:kmem_malloc(131072):kmem_map to small: 1296826368 total allocated > > > > cupid=4 > > O wow, this is an amd64 system (with 4G RAM) and you've got "kmem_map too > small". That's very very strange. > Are you sure you don't have any backwards-tuning in your configuration or > environment? > What value vm.kmem_size_max has? > I had a similar issue this morning, while doing a large compile (qt4). I do not have a debug kernel going, so I can't get a dump or anything, but I had exactly the same error as above (a different total allocated, of course, but in the same neighborhood). If this happens again, I'll get a debug kernel compiled, but hopefully it doesn't. :-) FreeBSD 8.1-PRERELEASE #0: Wed May 19 00:23:09 CDT 2010 root@ark.bluetonc.org:/usr/obj/usr/src/sys/ARK amd64 real memory = 4294967296 (4096 MB) avail memory = 3852931072 (3674 MB) mcj@ark ~ % sysctl vm.kmem_size_max vm.kmem_size_max: 329853485875 Not a lot of info here, I know, but it's just another data point. Thanks, -c From owner-freebsd-amd64@FreeBSD.ORG Fri May 28 13:59:10 2010 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 3B8A5106566B for ; Fri, 28 May 2010 13:59:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id F161D8FC0C for ; Fri, 28 May 2010 13:59:09 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta09.westchester.pa.mail.comcast.net with comcast id Nylt1e0030bG4ec591ltV8; Fri, 28 May 2010 13:45:53 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.westchester.pa.mail.comcast.net with comcast id P1lq1e00N3S48mS3P1lrSc; Fri, 28 May 2010 13:45:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7D1229B418; Fri, 28 May 2010 06:45:49 -0700 (PDT) Date: Fri, 28 May 2010 06:45:49 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20100528134549.GA75411@icarus.home.lan> References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BFF894F.4010008@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Tue, 01 Jun 2010 06:02:54 +0000 Cc: amd64@freebsd.org, freebsd-fs@freebsd.org Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 28 May 2010 13:59:10 -0000 On Fri, May 28, 2010 at 12:13:51PM +0300, Andriy Gapon wrote: > on 28/05/2010 10:30 Howard Leadmon said the following: > > I know there used to be some issues with this a while back, but thought > > with the 8.x FBSD servers most of this tuned itself, or then again maybe > > this is something different. > > > > > > > > For the first time I ever recall, I found my FreeBSD 8 server was crashed > > this past morning, with the following error: > > > > > > > > panic:kmem_malloc(131072):kmem_map to small: 1296826368 total allocated > > > > cupid=4 > > O wow, this is an amd64 system (with 4G RAM) and you've got "kmem_map too > small". That's very very strange. It is? On amd64, vm.kmem_size (not vm.kmem_size_max) is what has to be increased. I can point folks to the "official" statement from pjd@ and some others if need be. For a very long time I questioned this because for an even longer amount of time we were being told to increase vm.kmem_size_max. vm.kmem_size_max, by default, is already huge on amd64 (~320GB or something like that). Proof: vm.kmem_size_max: 329853485875 To the OP: you will need to increase vm.kmem_size in /boot/loader.conf and reboot the system. "What value do I pick?" With 4GB, I would recommend you use these two variables: vm.kmem_size="2048M" vfs.zfs.arc_max="1536M" This will increase the available kmem, and also limit the ARC size explicitly to nothing larger than 1.5GB. This should stabilise your system. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-amd64@FreeBSD.ORG Fri May 28 16:49:44 2010 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 1E040106564A; Fri, 28 May 2010 16:49:44 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2D4468FC1C; Fri, 28 May 2010 16:49:42 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA15166; Fri, 28 May 2010 19:49:27 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4BFFF416.1080901@icyb.net.ua> Date: Fri, 28 May 2010 19:49:26 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: Jeremy Chadwick References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> <20100528134549.GA75411@icarus.home.lan> In-Reply-To: <20100528134549.GA75411@icarus.home.lan> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 01 Jun 2010 06:03:06 +0000 Cc: amd64@freebsd.org, freebsd-fs@freebsd.org Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 28 May 2010 16:49:44 -0000 on 28/05/2010 16:45 Jeremy Chadwick said the following: > It is? On amd64, vm.kmem_size (not vm.kmem_size_max) is what has to be > increased. I can point folks to the "official" statement from pjd@ and > some others if need be. For a very long time I questioned this because > for an even longer amount of time we were being told to increase > vm.kmem_size_max. > > vm.kmem_size_max, by default, is already huge on amd64 (~320GB or > something like that). Proof: > > vm.kmem_size_max: 329853485875 > > To the OP: you will need to increase vm.kmem_size in /boot/loader.conf > and reboot the system. "What value do I pick?" With 4GB, I would > recommend you use these two variables: > > vm.kmem_size="2048M" > vfs.zfs.arc_max="1536M" > > This will increase the available kmem, and also limit the ARC size > explicitly to nothing larger than 1.5GB. This should stabilise your > system. > Jeremy, you are correct, I was confused about what kmem_size_max and kmem_size meant. kmem_size_max is what could be available, in principle, for kmem_map. But in practice kmem_map size is auto-set to about 1/3 of physical memory available, this is on amd64. BTW, the "6GB" change you mentioned in your other email was more relevant to kmem_size_max, it was overridden since then with 512GB change. kmem size calculations are very well explained here: http://www.mailinglistarchive.com/freebsd-current@freebsd.org/msg10986.html BTW, I don't see why we set kmem size to a fraction of physical memory on amd64 where we have plenty of KVM available. I don't buy the argument that larger kmem size would allow kernel to exhaust all physical memory which would lead to a "bad thing", e.g. a panic - right now kernel can exhaust all kmem which does lead to a panic. Perhaps, default value of VM_KMEM_SIZE_SCALE should be change to one on amd64? -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 15:26:49 2010 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 4799D1065674; Tue, 1 Jun 2010 15:26:49 +0000 (UTC) (envelope-from andrew.hotlab@hotmail.com) Received: from blu0-omc1-s25.blu0.hotmail.com (blu0-omc1-s25.blu0.hotmail.com [65.55.116.36]) by mx1.freebsd.org (Postfix) with ESMTP id 10A5D8FC2C; Tue, 1 Jun 2010 15:26:48 +0000 (UTC) Received: from BLU138-W12 ([65.55.116.8]) by blu0-omc1-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 1 Jun 2010 08:14:46 -0700 Message-ID: X-Originating-IP: [81.174.54.98] From: Andrew Hotlab To: , , Date: Tue, 1 Jun 2010 15:14:46 +0000 Importance: Normal In-Reply-To: <201005310502.o4V523eI059610@freefall.freebsd.org> References: <201005310502.o4V523eI059610@freefall.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 01 Jun 2010 15:14:46.0923 (UTC) FILETIME=[2BF60DB0:01CB019D] X-Mailman-Approved-At: Tue, 01 Jun 2010 16:01:07 +0000 Cc: Subject: RE: kern/147162: [jail] [panic] Page Fault / Kernel panic when jail starts on boot 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, 01 Jun 2010 15:26:49 -0000 ---------------------------------------- > Date: Mon=2C 31 May 2010 05:02:03 +0000 > To: linimon@FreeBSD.org=3B freebsd-amd64@FreeBSD.org=3B freebsd-jail@Free= BSD.org > From: linimon@FreeBSD.org > CC: > Subject: Re: kern/147162: [jail] [panic] Page Fault / Kernel panic when j= ail starts on boot > > Old Synopsis: Page Fault / Kernel panic when jail starts on boot > New Synopsis: [jail] [panic] Page Fault / Kernel panic when jail starts o= n boot > > Responsible-Changed-From-To: freebsd-amd64->freebsd-jail > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon May 31 05:01:35 UTC 2010 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D147162 Please do not get me wrong=2C I'm sure that all FreeBSD developers are doin= g an amazing job=2C and I cannot thank them enough... =A0but it's the first= time I'm worried by a bug in FreeBSD: I manage several jail hosts=2C and t= o encounter such a problem because of the latest security patch made my min= d back to those days when I was coping with the Microsoft Security Response= Center! :S I actually do not have the right to criticize (I barely know how difficult = is producing secure code)=2C neither I want to complain... I only=A0sincere= ly hope this has been my first and last "bad experience" with FreeBSD! :) Thank very much to all people that make FreeBSD one of the most reliable OS= out here. Andrew =20 _________________________________________________________________ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. https://signup.live.com/signup.aspx?id=3D60969= From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:13:35 2010 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 76532106566B; Tue, 1 Jun 2010 19:13:35 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from baumren.bluerosetech.com (baumren.bluerosetech.com [69.55.234.33]) by mx1.freebsd.org (Postfix) with ESMTP id 43D3C8FC19; Tue, 1 Jun 2010 19:13:35 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [131.252.214.6]) by baumren.bluerosetech.com (Postfix) with ESMTPSA id EFC2ECF889; Tue, 1 Jun 2010 11:55:13 -0700 (PDT) Received: from [IPv6:2001:470:8244:970:d978:ff31:cfda:924e] (unknown [IPv6:2001:470:8244:970:d978:ff31:cfda:924e]) by vivi.cat.pdx.edu (Postfix) with ESMTPSA id CA02724DFE; Tue, 1 Jun 2010 11:55:11 -0700 (PDT) Message-ID: <4C05577F.7040001@bitfreak.org> Date: Tue, 01 Jun 2010 11:54:55 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Jeremy Chadwick References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> <20100528134549.GA75411@icarus.home.lan> In-Reply-To: <20100528134549.GA75411@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org, freebsd-fs@freebsd.org Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 01 Jun 2010 19:13:35 -0000 Jeremy Chadwick wrote: > To the OP: you will need to increase vm.kmem_size in /boot/loader.conf > and reboot the system. "What value do I pick?" With 4GB, I would > recommend you use these two variables: > > vm.kmem_size="2048M" > vfs.zfs.arc_max="1536M" > > This will increase the available kmem, and also limit the ARC size > explicitly to nothing larger than 1.5GB. This should stabilise your > system. What are the general guidelines for sizing these given the amount of physical RAM? For example, I have a machine with 6 GB, so I have: vm.kmem_size="3072M" vfs.zfs.arc_max="2048M" From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 19:23:46 2010 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 DCE47106567A for ; Tue, 1 Jun 2010 19:23:46 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by mx1.freebsd.org (Postfix) with ESMTP id 896838FC14 for ; Tue, 1 Jun 2010 19:23:45 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta12.westchester.pa.mail.comcast.net with comcast id QahC1e0040bG4ec5CjPlr5; Tue, 01 Jun 2010 19:23:46 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.westchester.pa.mail.comcast.net with comcast id QjPk1e00U3S48mS3PjPlqc; Tue, 01 Jun 2010 19:23:45 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 461E69B418; Tue, 1 Jun 2010 12:23:43 -0700 (PDT) Date: Tue, 1 Jun 2010 12:23:43 -0700 From: Jeremy Chadwick To: Darren Pilgrim Message-ID: <20100601192343.GA44238@icarus.home.lan> References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> <20100528134549.GA75411@icarus.home.lan> <4C05577F.7040001@bitfreak.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C05577F.7040001@bitfreak.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Tue, 01 Jun 2010 20:01:03 +0000 Cc: amd64@freebsd.org, freebsd-fs@freebsd.org Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 01 Jun 2010 19:23:46 -0000 On Tue, Jun 01, 2010 at 11:54:55AM -0700, Darren Pilgrim wrote: > Jeremy Chadwick wrote: > >To the OP: you will need to increase vm.kmem_size in /boot/loader.conf > >and reboot the system. "What value do I pick?" With 4GB, I would > >recommend you use these two variables: > > > >vm.kmem_size="2048M" > >vfs.zfs.arc_max="1536M" > > > >This will increase the available kmem, and also limit the ARC size > >explicitly to nothing larger than 1.5GB. This should stabilise your > >system. > > What are the general guidelines for sizing these given the amount of > physical RAM? For example, I have a machine with 6 GB, so I have: > > vm.kmem_size="3072M" > vfs.zfs.arc_max="2048M" There really aren't any, as far as I know, since it depends on each system, it's role, and what architecture type (i386 vs. amd64). I'm focusing solely on amd64. Method I tend to follow: vm.kmem_size = 1/2 of available RAM (think physical/installed) vfs.zfs.arc_max = vm.kmem_size minus 512MB I believe there were some reported cases of panics on systems with vm.kmem_size == vfs.zfs.arc_max, but I could be remembering incorrectly. There's too many posts/people to remember who said what and when. I think there's a kstat.zfs.misc.arcstats sysctl counter which tracks the maximum ARC ever used, but could be mistaken here too. One of our 8GB systems that uses ZFS also runs MySQL, which requires me to use these values in addition to the above. Note that, AFAIK, the below values *do not* affect ZFS directly; I'm pointing them out as necessities, else a "heavy" mysqld crashes and complains about there not being enough memory (directly correlating to maxdsiz). kern.maxdsiz="1536M" kern.dfldsiz="1536M" kern.maxssiz="256M" Rather than try to pick values that "all add up to 8GB" (don't do this), I leave a lot of extra space for other things (kernel bits, network buffers, blah blah) that I don't want to think about. I try to avoid being OCD with tuning unless I have reason to be. All I really care about is providing enough memory for userland daemons and ZFS to run reliably/not panic the box. I'd welcome the community and developers to chime in here, especially folks familiar with the VM and how all of these tunables interact with one another. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 1 20:09:48 2010 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 D50F9106568B for ; Tue, 1 Jun 2010 20:09:48 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 9767D8FC15 for ; Tue, 1 Jun 2010 20:09:47 +0000 (UTC) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Tue, 01 Jun 2010 15:56:03 -0400 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::1379 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: amd64@freebsd.org X-SMFBL: YW1kNjRAZnJlZWJzZC5vcmc= Message-ID: <4C05657A.7060900@comcast.net> Date: Tue, 01 Jun 2010 15:54:34 -0400 From: Steve Polyack User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100311 Thunderbird/3.0.1 MIME-Version: 1.0 To: Darren Pilgrim References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> <20100528134549.GA75411@icarus.home.lan> <4C05577F.7040001@bitfreak.org> In-Reply-To: <4C05577F.7040001@bitfreak.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org, freebsd-fs@freebsd.org, Jeremy Chadwick Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. 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, 01 Jun 2010 20:09:48 -0000 On 06/01/10 14:54, Darren Pilgrim wrote: > Jeremy Chadwick wrote: >> To the OP: you will need to increase vm.kmem_size in /boot/loader.conf >> and reboot the system. "What value do I pick?" With 4GB, I would >> recommend you use these two variables: >> >> vm.kmem_size="2048M" >> vfs.zfs.arc_max="1536M" >> >> This will increase the available kmem, and also limit the ARC size >> explicitly to nothing larger than 1.5GB. This should stabilise your >> system. > > What are the general guidelines for sizing these given the amount of > physical RAM? For example, I have a machine with 6 GB, so I have: > > vm.kmem_size="3072M" > vfs.zfs.arc_max="2048M" > Things may have changed, but I would recommend 'vm.kmem_size="9G"' (1.5x physical memory size) and an ARC max of 3GB (half memory size). If you are doing more than just serving ZFS on the box, you may want to keep the ARC max around 2GB or less to leave some for other applications. The vm.kmem_size recommendation is based on a a good bit of list reading I did several months ago when setting my ZFS system up. That machine has made it over 6 months of production usage without a crash while serving a few terabytes of data to various NFS clients. It has 8GB of physical RAM, a vm.kmem_size of 12G, and a vfs.zfs.arc_max of 4G. It's been running 8-STABLE since 03/24/2010. Side note: Jeremy's values may work great, but these are the values I've been using myself and have not had a single problem. ZFS rocks. Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 3 13:05:23 2010 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 9C388106567B for ; Thu, 3 Jun 2010 13:05:23 +0000 (UTC) (envelope-from supportsobaka@mail.ru) Received: from finland-espoo1.intervipnet.com (finland-espoo1.intervipnet.com [89.250.63.98]) by mx1.freebsd.org (Postfix) with ESMTP id 5887C8FC16 for ; Thu, 3 Jun 2010 13:05:20 +0000 (UTC) Received: from 87-93-3-124.bb.dnainternet.fi ([87.93.3.124] helo=LN.my-domain) by finland-espoo1.intervipnet.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OK9Q1-000BlP-Bt for freebsd-amd64@freebsd.org; Thu, 03 Jun 2010 16:21:06 +0400 Date: Thu, 3 Jun 2010 15:21:02 +0300 From: supportsobaka@mail.ru Organization: supportsobaka@mail.ru X-Priority: 3 (Normal) Message-ID: <47077168.20100603152102@mail.ru> To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Thu, 03 Jun 2010 15:50:44 +0000 Subject: updating lib32 on amd64 through freebsd-update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: supportsobaka@mail.ru List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2010 13:05:23 -0000 Hello Is there any plans to do updating lib32 on amd64 through freebsd-update possible? What is the main problem with it? How can I check if I am using those libs for some binaries? May be I never use it and don't need to recompile "world". Is it unsecured to keep lib32 not updated if I am not using it at all? -- Supportsobaka From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 05:53:30 2010 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 C3B671065670 for ; Fri, 4 Jun 2010 05:53:30 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 7220D8FC2D for ; Fri, 4 Jun 2010 05:53:30 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o545rMPG059732 for ; Thu, 3 Jun 2010 22:53:29 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Thu, 3 Jun 2010 22:53:29 -0700 (PDT) Message-ID: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> Date: Thu, 3 Jun 2010 22:53:29 -0700 (PDT) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: who broke config(8) and why? 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, 04 Jun 2010 05:53:30 -0000 Greetings, In an attempt to build an AMD64 kernel, after a buildworld session. I was greeted with a couple of unexpected surprises: make buildkernel KERNCONF=MYAMDKERN returns ERROR MYAMDKERN not found... Aparently FreeBSD only put the sys/amd64,ia64,etc... to _appear_ to support architectures other than "i386". Fine. I'll use the older method: cd sys/amd64/conf config MYAMDCONF ERROR: version of config(8) does not match kernel! config version = 600007, version required = 600009 Make sure that /usr/src/usr.sbin/config is in sync with your /usr/src/sys and install a new config binary before trying this again. If running the new config fails check your config file against the GENERIC or LINT config files for changes in config syntax, or option/device naming conventions LOOK. I already read about this in UPDIATING. I've _already_ builtworld from an 8-RELEASE CD w/cvsupped src && ports. What gives? According to UPDATING: 20100502: The config(8) command has been updated to maintain compatibility with config files from 8.0-RELEASE. You will need a new version of config to build kernels (this version can be used from 8.0-RELEASE forward). ### (this version can be used from 8.0-RELEASE forward). I'm using 8-RELEASE ### The buildworld target will generate it, ### so following the instructions in this file for updating will work glitch-free. Merely doing a make buildkernel without first doing a make buildworld ### I just DID a buildworld ### (or kernel-toolchain), or attempting to build a kernel using traidtional methods will generate a config version warning, indicating you should update. I don't get it. Why was the config(8) toolchain deliberately broken in "midstream" (the middle of a release)?! Shouldn't this/ese change(s) been made at the start of an _upcomming_ version? I suppose I have to spend another few days downloading 9-RELEASE, and tailoring it for my needs as I have already done in preparation for this build/install. _Please_ if I can avoid starting from start, all over again. Can someone tell me where I can download a pre-compiled config-toolchain. So that I can resume a biuld/install. Thank you for all your time and consideration in thia matter. --Chris From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 06:14:56 2010 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 EAD271065677 for ; Fri, 4 Jun 2010 06:14:55 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF668FC19 for ; Fri, 4 Jun 2010 06:14:55 +0000 (UTC) Received: by vws19 with SMTP id 19so667151vws.13 for ; Thu, 03 Jun 2010 23:14:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6oPUTygsbbgQvQyWCWw0R3sHO1rVYUtRTJ3QI94G21s=; b=xlIt9BUvAChMp+OU4YERs0iWpW1bYCH+6zr1dtUn/z23EFH2Cpq0+fX/PNbC41g37f I+f68A8F3KRr5AqoZwkTYzW2OWSBOzz5++6C9gqxI7mEepv3TZTIhKN6KR+UuaaaGZ7b otkwaXss3KbZRU3mneTuTrbH8ar8P6V1hiVRo= 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=iIitQkTEFfgeSuzrB6880iTDl81ksefA7VyVQM7uQmvxXpvNI2AEKaAtwsOdd3q/o3 zpTw06UWu+skT7ua5nMUSiPDXiKm83O8ckLlF92K/q0k4x4+wWCj5b9nD+KYaorkHOlk 5DIl2bgs276nTqxmXqSVO+4onW90+vXr5QUUo= MIME-Version: 1.0 Received: by 10.224.78.142 with SMTP id l14mr5593613qak.174.1275632094067; Thu, 03 Jun 2010 23:14:54 -0700 (PDT) Received: by 10.229.233.74 with HTTP; Thu, 3 Jun 2010 23:14:54 -0700 (PDT) In-Reply-To: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> References: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> Date: Thu, 3 Jun 2010 23:14:54 -0700 Message-ID: From: Garrett Cooper To: fbsdmail@dnswatch.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: who broke config(8) and why? 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, 04 Jun 2010 06:14:56 -0000 On Thu, Jun 3, 2010 at 10:53 PM, wrote: > Greetings, > =A0In an attempt to build an AMD64 kernel, after a buildworld session. I = was > greeted with a couple of unexpected surprises: > make buildkernel KERNCONF=3DMYAMDKERN returns ERROR MYAMDKERN not found..= . > > Aparently FreeBSD only put the sys/amd64,ia64,etc... to _appear_ to suppo= rt > architectures other than "i386". > > Fine. I'll use the older method: > cd sys/amd64/conf > config MYAMDCONF > > ERROR: version of config(8) does not match kernel! > config version =3D 600007, version required =3D 600009 > > Make sure that /usr/src/usr.sbin/config is in sync > with your /usr/src/sys and install a new config binary > before trying this again. > > If running the new config fails check your config > file against the GENERIC or LINT config files for > changes in config syntax, or option/device naming > conventions > > LOOK. I already read about this in UPDIATING. I've _already_ builtworld > from an 8-RELEASE CD w/cvsupped src && ports. > What gives? According to UPDATING: > 20100502: > =A0 =A0 =A0 =A0The config(8) command has been updated to maintain compati= bility > =A0 =A0 =A0 =A0with config files from 8.0-RELEASE. =A0You will need a new= version > =A0 =A0 =A0 =A0of config to build kernels (this version can be used from = 8.0-RELEASE > =A0 =A0 =A0 =A0forward). > ### > (this version can be used from 8.0-RELEASE forward). > I'm using 8-RELEASE > ### > =A0The buildworld target will generate it, > ### > =A0so following > =A0 =A0 =A0 =A0the instructions in this file for updating will work glitc= h-free. > =A0 =A0 =A0 =A0Merely doing a make buildkernel without first doing a make= buildworld > ### > I just DID a buildworld > ### > =A0 =A0 =A0 =A0(or kernel-toolchain), or attempting to build a kernel usi= ng > =A0 =A0 =A0 =A0traidtional methods will generate a config version warning= , indicating > =A0 =A0 =A0 =A0you should update. > > > I don't get it. Why was the config(8) toolchain deliberately broken in > "midstream" (the middle of a release)?! Shouldn't this/ese change(s) been > made at the start of an _upcomming_ version? > > I suppose I have to spend another few days downloading 9-RELEASE, and > tailoring it for my needs as I have already done in preparation for this > build/install. > > _Please_ if I can avoid starting from start, all over again. Can someone > tell me where I can download a pre-compiled config-toolchain. So that I > can resume a biuld/install. > > Thank you for all your time and consideration in thia matter. make -C usr.sbin/config all install Done. -Garrett From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 06:40:07 2010 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 E3BB61065673 for ; Fri, 4 Jun 2010 06:40:07 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8B9B88FC18 for ; Fri, 4 Jun 2010 06:40:07 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o546dxZU059928; Thu, 3 Jun 2010 23:40:06 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Thu, 3 Jun 2010 23:40:06 -0700 (PDT) Message-ID: <284084f5a1a0a48ff64cedd859cf5669.dnswclient@www.dnswatch.com> In-Reply-To: References: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> Date: Thu, 3 Jun 2010 23:40:06 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Garrett Cooper" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: who broke config(8) and why? 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, 04 Jun 2010 06:40:08 -0000 On Thu, June 3, 2010 11:14 pm, Garrett Cooper wrote: > On Thu, Jun 3, 2010 at 10:53 PM, wrote: > >> Greetings, >> In an attempt to build an AMD64 kernel, after a buildworld session. I >> was greeted with a couple of unexpected surprises: make buildkernel >> KERNCONF=MYAMDKERN returns ERROR MYAMDKERN not found... >> >> >> Aparently FreeBSD only put the sys/amd64,ia64,etc... to _appear_ to >> support architectures other than "i386". >> >> Fine. I'll use the older method: >> cd sys/amd64/conf config MYAMDCONF >> >> ERROR: version of config(8) does not match kernel! >> config version = 600007, version required = 600009 >> >> Make sure that /usr/src/usr.sbin/config is in sync >> with your /usr/src/sys and install a new config binary before trying this >> again. >> >> If running the new config fails check your config >> file against the GENERIC or LINT config files for changes in config >> syntax, or option/device naming conventions >> >> LOOK. I already read about this in UPDIATING. I've _already_ builtworld >> from an 8-RELEASE CD w/cvsupped src && ports. What gives? According to >> UPDATING: >> 20100502: >> The config(8) command has been updated to maintain compatibility >> with config files from 8.0-RELEASE.  You will need a new version of >> config to build kernels (this version can be used from 8.0-RELEASE >> forward). ### >> (this version can be used from 8.0-RELEASE forward). >> I'm using 8-RELEASE >> ### >> The buildworld target will generate it, >> ### >> so following the instructions in this file for updating will work >> glitch-free. Merely doing a make buildkernel without first doing a make >> buildworld ### >> I just DID a buildworld >> ### >> (or kernel-toolchain), or attempting to build a kernel using >> traidtional methods will generate a config version warning, indicating >> you should update. >> >> >> I don't get it. Why was the config(8) toolchain deliberately broken in >> "midstream" (the middle of a release)?! Shouldn't this/ese change(s) >> been made at the start of an _upcomming_ version? >> >> I suppose I have to spend another few days downloading 9-RELEASE, and >> tailoring it for my needs as I have already done in preparation for this >> build/install. >> >> _Please_ if I can avoid starting from start, all over again. Can >> someone tell me where I can download a pre-compiled config-toolchain. So >> that I can resume a biuld/install. >> >> Thank you for all your time and consideration in thia matter. >> > > make -C usr.sbin/config all install > > LOL Thank you Garrett, you ROCK! :-) --Chris out... > > > Done. > -Garrett > > From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 07:16:52 2010 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 3F54B106567A for ; Fri, 4 Jun 2010 07:16:52 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 00DD48FC0C for ; Fri, 4 Jun 2010 07:16:51 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o547Gi5U060055 for ; Fri, 4 Jun 2010 00:16:50 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 00:16:50 -0700 (PDT) Message-ID: Date: Fri, 4 Jun 2010 00:16:50 -0700 (PDT) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: When will the amd64 be supported? 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, 04 Jun 2010 07:16:52 -0000 Greetings, If it isn't already apparent, this is my first attempt building kernel on an AMD based arch. I have spent some 20yrs building world/kernel on the arch i386. But, after reading everything I thought I would need to know, I'm /still/ unable to complete a successful kernel build on the amd64 arch. cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: MYAMDKERN not found cd sys/amd64/ config MYAMDKERN OK cd ../compile/MYAMDKERN make cleandepend && make depend fails with alot of "i386" errors So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, now running GENERIC, with a successful buildworld... Is it possible to build for the amd64 arch? If so, can anyone suggest where I went wrong? Thank you for all your time and consideration in this matter. --Chris P.S. of /course/ I read the kernel section of the handbook. :) From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 07:22:09 2010 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 293621065674 for ; Fri, 4 Jun 2010 07:22:09 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 081328FC14 for ; Fri, 4 Jun 2010 07:22:09 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id o547LxjX081757; Fri, 4 Jun 2010 00:21:59 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id o547Lxfq081756; Fri, 4 Jun 2010 00:21:59 -0700 (PDT) (envelope-from sgk) Date: Fri, 4 Jun 2010 00:21:59 -0700 From: Steve Kargl To: fbsdmail@dnswatch.com Message-ID: <20100604072158.GA81748@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 07:22:09 -0000 On Fri, Jun 04, 2010 at 12:16:50AM -0700, fbsdmail@dnswatch.com wrote: > Greetings, > If it isn't already apparent, this is my first attempt building kernel > on an AMD based arch. I have spent some 20yrs building world/kernel on > the arch i386. But, after reading everything I thought I would need to > know, I'm /still/ unable to complete a successful kernel build on the > amd64 arch. > > cd /usr/src > make buildkernel KERNCONF=MYAMDKERN > fails: MYAMDKERN not found > cd sys/amd64/ > config MYAMDKERN > OK > cd ../compile/MYAMDKERN > make cleandepend && make depend > fails with alot of "i386" errors > > So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, now > running GENERIC, with a successful buildworld... > Is it possible to build for the amd64 arch? > > If so, can anyone suggest where I went wrong? > What does uname -a return? -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 07:31:34 2010 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 1E6C8106566B for ; Fri, 4 Jun 2010 07:31:34 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id D93788FC3C for ; Fri, 4 Jun 2010 07:31:33 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o547VMH3060141; Fri, 4 Jun 2010 00:31:28 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 00:31:32 -0700 (PDT) Message-ID: In-Reply-To: References: Date: Fri, 4 Jun 2010 00:31:32 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Garrett Cooper" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 07:31:34 -0000 On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: > On Fri, Jun 4, 2010 at 12:16 AM, wrote: > >> Greetings, >> If it isn't already apparent, this is my first attempt building kernel >> on an AMD based arch. I have spent some 20yrs building world/kernel on >> the arch i386. But, after reading everything I thought I would need to >> know, I'm /still/ unable to complete a successful kernel build on the >> amd64 arch. >> >> cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: MYAMDKERN not >> found cd sys/amd64/ config MYAMDKERN OK >> cd ../compile/MYAMDKERN make cleandepend && make depend fails with alot of >> "i386" errors >> >> >> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, now >> running GENERIC, with a successful buildworld... Is it possible to build >> for the amd64 arch? >> >> If so, can anyone suggest where I went wrong? >> >> >> Thank you for all your time and consideration in this matter. >> > > Try sys/amd64/conf ;)... Right you are! Sorry that was a /typo/ on my part. That /should/ have read: cd /usr/src/sys/amd64/conf config OK cd ../compile/MYAMDKERN make cleandepend && make depend which fails w/ alot of "i386" related errors. Did I understand you correctly? Thank you for all your time and consideration. --Chris > -Garrett > > From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 07:37:35 2010 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 70F11106566C for ; Fri, 4 Jun 2010 07:37:35 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 61F3A8FC1D for ; Fri, 4 Jun 2010 07:37:30 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o547bBwN060179; Fri, 4 Jun 2010 00:37:21 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 00:37:22 -0700 (PDT) Message-ID: <9d7434c839075159c2001c1129aad13e.dnswclient@www.dnswatch.com> In-Reply-To: <20100604072158.GA81748@troutmask.apl.washington.edu> References: <20100604072158.GA81748@troutmask.apl.washington.edu> Date: Fri, 4 Jun 2010 00:37:22 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Steve Kargl" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 07:37:35 -0000 On Fri, June 4, 2010 12:21 am, Steve Kargl wrote: > On Fri, Jun 04, 2010 at 12:16:50AM -0700, fbsdmail@dnswatch.com wrote: > >> Greetings, >> If it isn't already apparent, this is my first attempt building kernel >> on an AMD based arch. I have spent some 20yrs building world/kernel on >> the arch i386. But, after reading everything I thought I would need to >> know, I'm /still/ unable to complete a successful kernel build on the >> amd64 arch. >> >> cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: MYAMDKERN not >> found cd sys/amd64/ config MYAMDKERN OK >> cd ../compile/MYAMDKERN make cleandepend && make depend fails with alot of >> "i386" errors >> >> >> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, now >> running GENERIC, with a successful buildworld... Is it possible to build >> for the amd64 arch? >> >> If so, can anyone suggest where I went wrong? >> >> > > What does uname -a return? Hmmm... Looks like you're on to something here, Steve; FreeBSD 8-RELEASE GENERIC i386 That "i386" doesn't look right, does it? I guess I've done something terribly wrong during makeworld (make installworld hasn't been done yet). I've /obviously/ overlooked something. Would anyone care to /kick/ me in the right direction? Apologies for the "niose" Thank you for all your time and consideration. --Chris > > > -- > Steve > > From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 07:55:27 2010 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 C6F3D106566C for ; Fri, 4 Jun 2010 07:55:27 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 709A48FC27 for ; Fri, 4 Jun 2010 07:55:27 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o547tJAf060270; Fri, 4 Jun 2010 00:55:25 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 00:55:26 -0700 (PDT) Message-ID: <84a3304dae11aa775584e2e934a15420.dnswclient@www.dnswatch.com> In-Reply-To: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> References: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> Date: Fri, 4 Jun 2010 00:55:26 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Garrett Cooper" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 07:55:27 -0000 On Fri, June 4, 2010 12:38 am, Garrett Cooper wrote: > On Jun 4, 2010, at 12:31 AM, fbsdmail@dnswatch.com wrote: > > >> On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: >> >>> On Fri, Jun 4, 2010 at 12:16 AM, wrote: >>> >>> >>>> Greetings, >>>> If it isn't already apparent, this is my first attempt building >>>> kernel on an AMD based arch. I have spent some 20yrs building >>>> world/kernel on the arch i386. But, after reading everything I >>>> thought I would need to know, I'm /still/ unable to complete a >>>> successful kernel build on the amd64 arch. >>>> >>>> cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: MYAMDKERN >>>> not found cd sys/amd64/ config MYAMDKERN OK cd ../compile/MYAMDKERN >>>> make cleandepend && make depend fails with alot of "i386" errors >>>> >>>> >>>> >>>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, >>>> now running GENERIC, with a successful buildworld... Is it possible >>>> to build for the amd64 arch? >>>> >>>> If so, can anyone suggest where I went wrong? >>>> >>>> >>>> >>>> Thank you for all your time and consideration in this matter. >>>> >>>> >>> >>> Try sys/amd64/conf ;)... >>> >> Right you are! Sorry that was a /typo/ on my part. >> That /should/ have read: >> cd /usr/src/sys/amd64/conf config OK >> cd ../compile/MYAMDKERN make cleandepend && make depend >> >> which fails w/ alot of "i386" related errors. >> >> Did I understand you correctly? >> >> >> Thank you for all your time and consideration. >> > > uname -m and providing your MYAMDKERN would help too... I've been running > amd64 for at least 5 years now, so I doubt it's the architecture. Thanks, I hope to be running the /same/ -- soon! :) Well, as you're now already aware, I've builtworld for the "i386" -- I have no idea how I ended up that way. That said, you can find the KERNCONF I'm using form: /usr/src/sys/amd64/conf @ https://ultimatedns.NET/XIII.gz Thank you very much for your continued time and consideration. --Chris > -Garrett From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:11:00 2010 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 186D31065673 for ; Fri, 4 Jun 2010 08:11:00 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id C92C88FC2C for ; Fri, 4 Jun 2010 08:10:59 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o548AqTt060351; Fri, 4 Jun 2010 01:10:58 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 01:10:58 -0700 (PDT) Message-ID: In-Reply-To: References: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> <84a3304dae11aa775584e2e934a15420.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 01:10:58 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Garrett Cooper" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:11:00 -0000 On Fri, June 4, 2010 1:05 am, Garrett Cooper wrote: > On Jun 4, 2010, at 12:55 AM, fbsdmail@dnswatch.com wrote: > > >> On Fri, June 4, 2010 12:38 am, Garrett Cooper wrote: >> >>> On Jun 4, 2010, at 12:31 AM, fbsdmail@dnswatch.com wrote: >>> >>> >>> >>>> On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: >>>> >>>> >>>>> On Fri, Jun 4, 2010 at 12:16 AM, wrote: >>>>> >>>>> >>>>> >>>>>> Greetings, >>>>>> If it isn't already apparent, this is my first attempt building >>>>>> kernel on an AMD based arch. I have spent some 20yrs building >>>>>> world/kernel on the arch i386. But, after reading everything I >>>>>> thought I would need to know, I'm /still/ unable to complete a >>>>>> successful kernel build on the amd64 arch. >>>>>> >>>>>> cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: >>>>>> MYAMDKERN >>>>>> not found cd sys/amd64/ config MYAMDKERN OK cd >>>>>> ../compile/MYAMDKERN >>>>>> make cleandepend && make depend fails with alot of "i386" errors >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && >>>>>> ports, now running GENERIC, with a successful buildworld... Is >>>>>> it possible to build for the amd64 arch? >>>>>> >>>>>> If so, can anyone suggest where I went wrong? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Thank you for all your time and consideration in this matter. >>>>>> >>>>>> >>>>>> >>>>> >>>>> Try sys/amd64/conf ;)... >>>>> >>>>> >>>> Right you are! Sorry that was a /typo/ on my part. >>>> That /should/ have read: >>>> cd /usr/src/sys/amd64/conf config OK cd ../compile/MYAMDKERN make >>>> cleandepend && make depend >>>> >>>> which fails w/ alot of "i386" related errors. >>>> >>>> Did I understand you correctly? >>>> >>>> >>>> >>>> Thank you for all your time and consideration. >>>> >>>> >>> >>> uname -m and providing your MYAMDKERN would help too... I've been >>> running amd64 for at least 5 years now, so I doubt it's the >>> architecture. Thanks, >> I hope to be running the /same/ -- soon! :) >> >> >> Well, as you're now already aware, I've builtworld for the "i386" -- I >> have no idea how I ended up that way. >> >> That said, you can find the KERNCONF I'm using form: >> /usr/src/sys/amd64/conf >> >> >> @ https://ultimatedns.NET/XIII.gz >> >> >> Thank you very much for your continued time and consideration. >> > > Your config looks ok. You just need to cross-build or build under amd64 > native. HTH, Thank you again, Garrett. At the risk of sounding like a /complete/ dweeb... How do I manage "amd64 native"? While I've read the docs regarding setting up a cross-compile env. I'm /really/ just trying to convert all my i386 boxen to amd64. Thank you again -- /really/ --Chris > -Garrett From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:15:28 2010 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 587F41065673 for ; Fri, 4 Jun 2010 08:15:28 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id BEA2F8FC1C for ; Fri, 4 Jun 2010 08:15:27 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o548FIiQ060387; Fri, 4 Jun 2010 01:15:24 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 01:15:24 -0700 (PDT) Message-ID: <0824f2739c4bd495504471dad8a0fca8.dnswclient@www.dnswatch.com> In-Reply-To: References: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> <84a3304dae11aa775584e2e934a15420.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 01:15:24 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Garrett Cooper" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:15:28 -0000 On Fri, June 4, 2010 1:05 am, Garrett Cooper wrote: > On Jun 4, 2010, at 12:55 AM, fbsdmail@dnswatch.com wrote: > > >> On Fri, June 4, 2010 12:38 am, Garrett Cooper wrote: >> >>> On Jun 4, 2010, at 12:31 AM, fbsdmail@dnswatch.com wrote: >>> >>> >>> >>>> On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: >>>> >>>> >>>>> On Fri, Jun 4, 2010 at 12:16 AM, wrote: >>>>> >>>>> >>>>> >>>>>> Greetings, >>>>>> If it isn't already apparent, this is my first attempt building >>>>>> kernel on an AMD based arch. I have spent some 20yrs building >>>>>> world/kernel on the arch i386. But, after reading everything I >>>>>> thought I would need to know, I'm /still/ unable to complete a >>>>>> successful kernel build on the amd64 arch. >>>>>> >>>>>> cd /usr/src make buildkernel KERNCONF=MYAMDKERN fails: >>>>>> MYAMDKERN >>>>>> not found cd sys/amd64/ config MYAMDKERN OK cd >>>>>> ../compile/MYAMDKERN >>>>>> make cleandepend && make depend fails with alot of "i386" errors >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && >>>>>> ports, now running GENERIC, with a successful buildworld... Is >>>>>> it possible to build for the amd64 arch? >>>>>> >>>>>> If so, can anyone suggest where I went wrong? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Thank you for all your time and consideration in this matter. >>>>>> >>>>>> >>>>>> >>>>> >>>>> Try sys/amd64/conf ;)... >>>>> >>>>> >>>> Right you are! Sorry that was a /typo/ on my part. >>>> That /should/ have read: >>>> cd /usr/src/sys/amd64/conf config OK cd ../compile/MYAMDKERN make >>>> cleandepend && make depend >>>> >>>> which fails w/ alot of "i386" related errors. >>>> >>>> Did I understand you correctly? >>>> >>>> >>>> >>>> Thank you for all your time and consideration. >>>> >>>> >>> >>> uname -m and providing your MYAMDKERN would help too... I've been >>> running amd64 for at least 5 years now, so I doubt it's the >>> architecture. Thanks, >> I hope to be running the /same/ -- soon! :) >> >> >> Well, as you're now already aware, I've builtworld for the "i386" -- I >> have no idea how I ended up that way. >> >> That said, you can find the KERNCONF I'm using form: >> /usr/src/sys/amd64/conf >> >> >> @ https://ultimatedns.NET/XIII.gz >> >> >> Thank you very much for your continued time and consideration. >> > > Your config looks ok. You just need to cross-build or build under amd64 > native. HTH, PLEASE ignore my last question. I was a DOPE, I overlooked the /obvious/ I used the /wrong/ DVD. Apologies for the noise... I'll shut up now. --Chris > -Garrett From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:30:30 2010 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 C52921065672 for ; Fri, 4 Jun 2010 08:30:30 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8C6208FC20 for ; Fri, 4 Jun 2010 08:30:30 +0000 (UTC) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OKSIE-000P5n-Cv; Fri, 04 Jun 2010 09:30:18 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OKSIE-000GYr-C6; Fri, 04 Jun 2010 09:30:18 +0100 Date: Fri, 04 Jun 2010 09:30:18 +0100 Message-Id: To: fbsdmail@dnswatch.com, yaneurabeya@gmail.com In-Reply-To: From: Pete French Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:30:30 -0000 > I'm /really/ just trying to convert all my i386 boxen to amd64. ....this is the source of your problem. What you were trying to do in builing amd64 is correct, but only if you are already on an amd64 platform. Those instrcutions are for building the native architecture. If you want to convert an existing system 'in-lace' from i386 to amd64, then you need to get an install of amd64 on some portable drive that you can boot from, boot the machine on that, mount the original drive under '/mnt' or somewhere, and then do an 'installkernel' and 'installworld' specifying the mountpoint as the destination. It does work - but I would do it with a GENERIC kernel first before trying a custom kernel. Oh, and also you should delete all your ports beforehand and then rebuild them afterwards so they get rebuilt for amd64. I would not recommend the above though. You are better off doing an amd64 install froms cratch. Much less error prone. -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:40:09 2010 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 AA95210656F2 for ; Fri, 4 Jun 2010 08:40:09 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 594F08FC1A for ; Fri, 4 Jun 2010 08:40:09 +0000 (UTC) Received: by vws19 with SMTP id 19so849737vws.13 for ; Fri, 04 Jun 2010 01:40:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=G09xi0LU4T6H9lrT/g2B1wE0e57USAUHMFSkb+9i/0I=; b=Xh0TC1T5HZVc6MLSliJoIPvXMK5XT3Ncmq9LSHMNWcuKOPe9i10DlD1iLDYUGS2xsm mtF/I02Jg174YYRoUyzR5/p0vrNAd7lnuaXkixmREVMz2VT/VO2Dla2eYF85zRkcq43J Y6e7Lm1X3qlFiUgi7LwpoiJgy1o7nU8lSK1s8= 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; b=f0Vlu+k5uP5rM+/RALBet9v9pTBzSUVY84EYvyAGK+832q/RGJNSIRuDEYap6p9Ugs yw9AJ9ezOLMrjcdLmaSuGVkUN4QJ+nHtZ+sK84atfviBlJNUxqZb0YV+Y4Q9ZXLV6eNr rWoUXNn2uEtWDo1vuglm0jfQgUNJVoaD8zf04= MIME-Version: 1.0 Received: by 10.224.58.74 with SMTP id f10mr5411326qah.317.1275640808190; Fri, 04 Jun 2010 01:40:08 -0700 (PDT) Received: by 10.229.233.74 with HTTP; Fri, 4 Jun 2010 01:40:07 -0700 (PDT) In-Reply-To: References: Date: Fri, 4 Jun 2010 01:40:07 -0700 Message-ID: From: Garrett Cooper To: Pete French Content-Type: text/plain; charset=ISO-8859-1 Cc: fbsdmail@dnswatch.com, freebsd-amd64@freebsd.org, yaneurabeya@gmail.com Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:40:09 -0000 On Fri, Jun 4, 2010 at 1:30 AM, Pete French wrote: >> I'm /really/ just trying to convert all my i386 boxen to amd64. > > ....this is the source of your problem. What you were trying to > do in builing amd64 is correct, but only if you are already > on an amd64 platform. Those instrcutions are for building the > native architecture. > > If you want to convert an existing system 'in-lace' from i386 > to amd64, then you need to get an install of amd64 on some portable > drive that you can boot from, boot the machine on that, mount the > original drive under '/mnt' or somewhere, and then do an 'installkernel' > and 'installworld' specifying the mountpoint as the destination. That seems to be overcomplicating things a bit, but yes.. the general strategy would be something along those lines. > It does work - but I would do it with a GENERIC kernel first before trying > a custom kernel. Oh, and also you should delete all your ports beforehand > and then rebuild them afterwards so they get rebuilt for amd64. Yeah, that needs to be done. > I would not recommend the above though. You are better off doing > an amd64 install froms cratch. Much less error prone. Wholeheartedly agree. -Garrett From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 09:04:17 2010 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 31D4C1065675 for ; Fri, 4 Jun 2010 09:04:17 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id EE0298FC17 for ; Fri, 4 Jun 2010 09:04:16 +0000 (UTC) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OKSp1-000PH5-62; Fri, 04 Jun 2010 10:04:11 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OKSp1-000Gew-5B; Fri, 04 Jun 2010 10:04:11 +0100 Date: Fri, 04 Jun 2010 10:04:11 +0100 Message-Id: To: yanefbsd@gmail.com In-Reply-To: From: Pete French Cc: fbsdmail@dnswatch.com, yaneurabeya@gmail.com, freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 09:04:17 -0000 > That seems to be overcomplicating things a bit, but yes.. the general > strategy would be something along those lines. Am curious that you think it's overcomplicating matters - can you think of a way of doing it with only one drive ? That the simplest procedure I amnaged to come up with when migrating machine from 32 to 64. As I;ve got a few which still need ding then any simpler method is of great interest (especially one which doesnt require a 2nd drive!) cheers, -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 10:12:33 2010 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 7A690106567C for ; Fri, 4 Jun 2010 10:12:33 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id 0B7178FC35 for ; Fri, 4 Jun 2010 10:12:32 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c211-30-160-13.mirnd2.nsw.optusnet.com.au [211.30.160.13] (may be forged)) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o54ACSml031752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jun 2010 20:12:30 +1000 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.4/8.14.4) with ESMTP id o54ACQru056004; Fri, 4 Jun 2010 20:12:26 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o54ACPgE056003; Fri, 4 Jun 2010 20:12:25 +1000 (EST) (envelope-from peter) Date: Fri, 4 Jun 2010 20:12:25 +1000 From: Peter Jeremy To: Pete French Message-ID: <20100604101225.GA55626@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 10:12:33 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Jun-04 10:04:11 +0100, Pete French wr= ote: >> That seems to be overcomplicating things a bit, but yes.. the general >> strategy would be something along those lines. > >Am curious that you think it's overcomplicating matters - can you think >of a way of doing it with only one drive ? That the simplest procedure >I amnaged to come up with when migrating machine from 32 to 64. As >I;ve got a few which still need ding then any simpler method is of >great interest (especially one which doesnt require a 2nd drive!) In theory, you should be able to just steal a disk partition - swap being the most obvious: Disable swap, newfs it and mount it as /mnt, install kernel and world into it and configure it as root. Reboot onto /mnt (manually specify the 'b' partition to boot1) and do an installkernel/world onto your original partitions then reboot back into them. It might be slightly quicker and easier to dump/restore your existing i386 root (and minimal parts of /usr) into /mnt, boot into it and the just do a single installkernel/world onto your original partitions. I'm not sure of the exact parts of /usr that will be necessary. Keep in mind that you'll need to rebuild all your ports as soon as you rebuild any. And anything that gets too chummy with the kernel innards won't work until it's rebuilt. Some time ago, I did manage to do an in-place amd64 to i386 conversion (and revert using a ZFS snapshot). --=20 Peter Jeremy --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwI0YkACgkQ/opHv/APuIeEGwCgvMgWXPUr89T2cZYwVrwOWShD s8oAoLhSueh8fkYrMlVYZWEBXEMv3mE/ =v213 -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:01:07 2010 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 157CF1065672 for ; Fri, 4 Jun 2010 08:01:07 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id D7AE18FC1C for ; Fri, 4 Jun 2010 08:01:06 +0000 (UTC) Received: by pvh11 with SMTP id 11so599646pvh.13 for ; Fri, 04 Jun 2010 01:01:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=E2FwEYp3K/Fd1cBLJ+ulzoB59+XsV6B0DrBgmIFaNKg=; b=nqHGOs2yYVNORPmeApnF0S+2bUgb0Ni48t5yEzJwHG5wviBur7AS6FhPA1bY/zky1y iMEAHIaPxWLS3X2PmvVzLu1CF63ITK5jvtIvvb953TRwrJAotSuXzNCSFlBf8TLB4iCT wJhEDYH8YFYozposNjPlUbToUkoI0KI/Da3JE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=d8r6Dtqh2KIf8gK5gVf1eJVZUWzuloqmMix+Lepuuu1dC0JsAYphWGyiNP2jIKSNPS NZ2QvtPwIttOTraTB0G2Oislksdu4j+yRW8jXfRaoCt6iUV6GsTEAlD4g2GPXNjUiJNx Cw1Qch+sOGqpo+xQstiMwmB49rDGqqZv2p4iU= Received: by 10.114.251.23 with SMTP id y23mr8171486wah.42.1275637160253; Fri, 04 Jun 2010 00:39:20 -0700 (PDT) Received: from [192.168.0.203] (deviant.freebsdgirl.com [173.8.183.73]) by mx.google.com with ESMTPS id c14sm6388936waa.1.2010.06.04.00.39.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 04 Jun 2010 00:39:19 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: <9d7434c839075159c2001c1129aad13e.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 00:39:18 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5DC17728-9AF8-4F2B-AB68-142D4FEFFD5B@gmail.com> References: <20100604072158.GA81748@troutmask.apl.washington.edu> <9d7434c839075159c2001c1129aad13e.dnswclient@www.dnswatch.com> To: fbsdmail@dnswatch.com X-Mailer: Apple Mail (2.1078) X-Mailman-Approved-At: Fri, 04 Jun 2010 11:37:25 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:01:07 -0000 On Jun 4, 2010, at 12:37 AM, fbsdmail@dnswatch.com wrote: > On Fri, June 4, 2010 12:21 am, Steve Kargl wrote: >> On Fri, Jun 04, 2010 at 12:16:50AM -0700, fbsdmail@dnswatch.com = wrote: >>=20 >>> Greetings, >>> If it isn't already apparent, this is my first attempt building = kernel >>> on an AMD based arch. I have spent some 20yrs building world/kernel = on >>> the arch i386. But, after reading everything I thought I would need = to >>> know, I'm /still/ unable to complete a successful kernel build on = the >>> amd64 arch. >>>=20 >>> cd /usr/src make buildkernel KERNCONF=3DMYAMDKERN fails: MYAMDKERN = not >>> found cd sys/amd64/ config MYAMDKERN OK >>> cd ../compile/MYAMDKERN make cleandepend && make depend fails with = alot of >>> "i386" errors >>>=20 >>>=20 >>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, = now >>> running GENERIC, with a successful buildworld... Is it possible to = build >>> for the amd64 arch? >>>=20 >>> If so, can anyone suggest where I went wrong? >>>=20 >>>=20 >>=20 >> What does uname -a return? >=20 > Hmmm... Looks like you're on to something here, Steve; > FreeBSD 8-RELEASE GENERIC i386 >=20 > That "i386" doesn't look right, does it? >=20 > I guess I've done something terribly wrong during makeworld > (make installworld hasn't been done yet). > I've /obviously/ overlooked something. Would anyone care to > /kick/ me in the right direction? > Apologies for the "niose" >=20 > Thank you for all your time and consideration. You can cross-build amd64, but it's a bit more involved than a standard = update. Cheers, -Garrett= From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:05:11 2010 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 133D2106564A for ; Fri, 4 Jun 2010 08:05:11 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id D4B208FC18 for ; Fri, 4 Jun 2010 08:05:10 +0000 (UTC) Received: by pvh11 with SMTP id 11so601194pvh.13 for ; Fri, 04 Jun 2010 01:05:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=6dSkpJ32sLlUCbJdsj8cnT2v6dMmddQEoDWI3aCIIQY=; b=laQ5g4guqWpqN62d0BF/KzTcqeCDxUYxEFNc1vrlV/ApUDS6/275sQgKe6mazSCJM7 O/fd/T7/5R/zzQrlxopI6eGUEnBlFAAIZykjHT9Ou96blciSDpvOVzDDe3srnRHA+O4U pqmcA94AYV9s2P8YScyHkwD/HCs90HqfettKg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=bltmMRkBkCmoJiBIZvDfWaNaO32uyqcp88QsXuKrXttE5aasF/kjHsKqwg3nAkZf4d t47xk0OtL7tZlOLKjlCYo201sV1hIbAXajZQEzo+RXQMngBM3oYERWXQL9qT054vuDNJ 80gHMPHVNHpq9YdpPU5HmtLGJ3OGhTGolRHD0= Received: by 10.115.39.17 with SMTP id r17mr8256536waj.40.1275638708795; Fri, 04 Jun 2010 01:05:08 -0700 (PDT) Received: from [192.168.0.203] (deviant.freebsdgirl.com [173.8.183.73]) by mx.google.com with ESMTPS id r20sm6572639wam.17.2010.06.04.01.05.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 04 Jun 2010 01:05:07 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: <84a3304dae11aa775584e2e934a15420.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 01:05:05 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> <84a3304dae11aa775584e2e934a15420.dnswclient@www.dnswatch.com> To: fbsdmail@dnswatch.com X-Mailer: Apple Mail (2.1078) X-Mailman-Approved-At: Fri, 04 Jun 2010 11:37:56 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:05:11 -0000 On Jun 4, 2010, at 12:55 AM, fbsdmail@dnswatch.com wrote: > On Fri, June 4, 2010 12:38 am, Garrett Cooper wrote: >> On Jun 4, 2010, at 12:31 AM, fbsdmail@dnswatch.com wrote: >>=20 >>=20 >>> On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: >>>=20 >>>> On Fri, Jun 4, 2010 at 12:16 AM, wrote: >>>>=20 >>>>=20 >>>>> Greetings, >>>>> If it isn't already apparent, this is my first attempt building >>>>> kernel on an AMD based arch. I have spent some 20yrs building >>>>> world/kernel on the arch i386. But, after reading everything I >>>>> thought I would need to know, I'm /still/ unable to complete a >>>>> successful kernel build on the amd64 arch. >>>>>=20 >>>>> cd /usr/src make buildkernel KERNCONF=3DMYAMDKERN fails: MYAMDKERN >>>>> not found cd sys/amd64/ config MYAMDKERN OK cd = ../compile/MYAMDKERN >>>>> make cleandepend && make depend fails with alot of "i386" errors >>>>>=20 >>>>>=20 >>>>>=20 >>>>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, >>>>> now running GENERIC, with a successful buildworld... Is it = possible >>>>> to build for the amd64 arch? >>>>>=20 >>>>> If so, can anyone suggest where I went wrong? >>>>>=20 >>>>>=20 >>>>>=20 >>>>> Thank you for all your time and consideration in this matter. >>>>>=20 >>>>>=20 >>>>=20 >>>> Try sys/amd64/conf ;)... >>>>=20 >>> Right you are! Sorry that was a /typo/ on my part. >>> That /should/ have read: >>> cd /usr/src/sys/amd64/conf config OK >>> cd ../compile/MYAMDKERN make cleandepend && make depend >>>=20 >>> which fails w/ alot of "i386" related errors. >>>=20 >>> Did I understand you correctly? >>>=20 >>>=20 >>> Thank you for all your time and consideration. >>>=20 >>=20 >> uname -m and providing your MYAMDKERN would help too... I've been = running >> amd64 for at least 5 years now, so I doubt it's the architecture. = Thanks, > I hope to be running the /same/ -- soon! :) >=20 > Well, as you're now already aware, I've builtworld for the "i386" -- I > have no idea how I ended up that way. >=20 > That said, you can find the KERNCONF I'm using form: > /usr/src/sys/amd64/conf >=20 > @ https://ultimatedns.NET/XIII.gz >=20 > Thank you very much for your continued time and consideration. Your config looks ok. You just need to cross-build or build under amd64 = native. HTH, -Garrett= From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:08:13 2010 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 140A8106566C for ; Fri, 4 Jun 2010 08:08:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by mx1.freebsd.org (Postfix) with ESMTP id D74CB8FC15 for ; Fri, 4 Jun 2010 08:08:12 +0000 (UTC) Received: by pzk5 with SMTP id 5so545204pzk.14 for ; Fri, 04 Jun 2010 01:08:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=UfQ/OmiC0J1DIeaJ2wKWvmUlWQt7nhN6szdbOVWj7UU=; b=CDWmnlDRhf5oYM5Xb+kjfZSw1ecSW7JOlRlcgf6hmkqqGX0QvPSZhkPvEccZpfNHe/ N6y7C8NvTZp+jxEFzJEKFh7mYEREa9i+ZnOwuXFEvam7S3vY6U7Xdb9mJmkZYL7JioPh OzwHrfj0yjYrd6eYhCJ4QvA3FH1qTQfVKgH18= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=WV7/5b5oY3/uXwEQoVTFXJ4kTQgjwCfa7qT0+i1u3CnHw3oPOxVzsRTTZ/U5qN3KFm GLTS5ejy4zR8PJlhdeKNhV4Ona7qy9tkHlg0xcnaX9q5xAcszoQjhBICtlI/0+RF4WnL cnotf5kooKA5HggHd4+EuHPTGyYkNMEbqGY6g= Received: by 10.115.117.6 with SMTP id u6mr8234478wam.191.1275637099193; Fri, 04 Jun 2010 00:38:19 -0700 (PDT) Received: from [192.168.0.203] (deviant.freebsdgirl.com [173.8.183.73]) by mx.google.com with ESMTPS id c14sm6388936waa.1.2010.06.04.00.38.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 04 Jun 2010 00:38:18 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: Date: Fri, 4 Jun 2010 00:38:15 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <78A980B2-E533-48DD-A47D-03DA6A58D366@gmail.com> References: To: fbsdmail@dnswatch.com X-Mailer: Apple Mail (2.1078) X-Mailman-Approved-At: Fri, 04 Jun 2010 11:38:21 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 08:08:13 -0000 On Jun 4, 2010, at 12:31 AM, fbsdmail@dnswatch.com wrote: > On Fri, June 4, 2010 12:19 am, Garrett Cooper wrote: >> On Fri, Jun 4, 2010 at 12:16 AM, wrote: >>=20 >>> Greetings, >>> If it isn't already apparent, this is my first attempt building = kernel >>> on an AMD based arch. I have spent some 20yrs building world/kernel = on >>> the arch i386. But, after reading everything I thought I would need = to >>> know, I'm /still/ unable to complete a successful kernel build on = the >>> amd64 arch. >>>=20 >>> cd /usr/src make buildkernel KERNCONF=3DMYAMDKERN fails: MYAMDKERN = not >>> found cd sys/amd64/ config MYAMDKERN OK >>> cd ../compile/MYAMDKERN make cleandepend && make depend fails with = alot of >>> "i386" errors >>>=20 >>>=20 >>> So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, = now >>> running GENERIC, with a successful buildworld... Is it possible to = build >>> for the amd64 arch? >>>=20 >>> If so, can anyone suggest where I went wrong? >>>=20 >>>=20 >>> Thank you for all your time and consideration in this matter. >>>=20 >>=20 >> Try sys/amd64/conf ;)... > Right you are! Sorry that was a /typo/ on my part. > That /should/ have read: > cd /usr/src/sys/amd64/conf > config > OK > cd ../compile/MYAMDKERN > make cleandepend && make depend >=20 > which fails w/ alot of "i386" related errors. >=20 > Did I understand you correctly? >=20 > Thank you for all your time and consideration. uname -m and providing your MYAMDKERN would help too... I've been = running amd64 for at least 5 years now, so I doubt it's the = architecture. Thanks, -Garrett= From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 08:45:40 2010 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 5FF21106566B; Fri, 4 Jun 2010 08:45:40 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 385C98FC14; Fri, 4 Jun 2010 08:45:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o548jelN071267; Fri, 4 Jun 2010 08:45:40 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o548jeVO071263; Fri, 4 Jun 2010 08:45:40 GMT (envelope-from jh) Date: Fri, 4 Jun 2010 08:45:40 GMT Message-Id: <201006040845.o548jeVO071263@freefall.freebsd.org> To: mjacob@freebsd.org, jh@FreeBSD.org, freebsd-amd64@FreeBSD.org From: jh@FreeBSD.org X-Mailman-Approved-At: Fri, 04 Jun 2010 11:39:00 +0000 Cc: Subject: Re: amd64/102716: ex with no argument in an xterm gets SIGSEGV 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, 04 Jun 2010 08:45:40 -0000 Synopsis: ex with no argument in an xterm gets SIGSEGV State-Changed-From-To: open->feedback State-Changed-By: jh State-Changed-When: Fri Jun 4 08:45:39 UTC 2010 State-Changed-Why: Note that submitter has been asked for feedback. http://www.freebsd.org/cgi/query-pr.cgi?pr=102716 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 15:35:34 2010 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 D34A9106584B for ; Fri, 4 Jun 2010 15:35:34 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.freebsd.org (Postfix) with ESMTP id 493F68FC15 for ; Fri, 4 Jun 2010 15:35:33 +0000 (UTC) Received: from slackbox.erewhon.net (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id o54FZQpY015515; Fri, 4 Jun 2010 17:35:30 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.erewhon.net (Postfix, from userid 1001) id ED847BAAC; Fri, 4 Jun 2010 17:35:25 +0200 (CEST) Date: Fri, 4 Jun 2010 17:35:25 +0200 From: Roland Smith To: fbsdmail@dnswatch.com Message-ID: <20100604153525.GA26412@slackbox.erewhon.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: 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.20 (2009-06-14) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 15:35:34 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 04, 2010 at 12:16:50AM -0700, fbsdmail@dnswatch.com wrote: > Greetings, > If it isn't already apparent, this is my first attempt building kernel > on an AMD based arch. I have spent some 20yrs building world/kernel on > the arch i386. But, after reading everything I thought I would need to > know, I'm /still/ unable to complete a successful kernel build on the > amd64 arch. >=20 > cd /usr/src > make buildkernel KERNCONF=3DMYAMDKERN You need to copy MYAMDKERN to /usr/src/sys/amd64/conf/ first! > fails with alot of "i386" errors > So, on a fresh 8-RELEASE install from DVD w/cvsupped src && ports, now > running GENERIC, with a successful buildworld... > Is it possible to build for the amd64 arch? You _did_ install the amd64 architecture, right? Not i386? Because if you installed the i386 it is better to install the amd64 version from scratch t= han to try and cross-build and install amd64 on an i386 system. > If so, can anyone suggest where I went wrong? Cross-building and especially installing an amd64 kernel and userland on i3= 86 is quite involved and not recommended. Save yourself the trouble and don't = go there. Just re-install using the CD or DVD built for the amd64 architecture. It's = less painfull. You should also delete all your ports and rebuild them for amd64. 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) --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwJHT0ACgkQEnfvsMMhpyW2IACfa2YdgfMQtw2PS7gnEKYrzYqg MekAn1xyRPuEUB0HqDRwvkraS22QWVCa =c9z0 -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 20:44:42 2010 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 958E21065670 for ; Fri, 4 Jun 2010 20:44:42 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 3FB0A8FC1E for ; Fri, 4 Jun 2010 20:44:42 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o54KiYf7063590; Fri, 4 Jun 2010 13:44:40 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 13:44:41 -0700 (PDT) Message-ID: <7b58de2db44961fb34bf7a64ed2dc51d.dnswclient@www.dnswatch.com> In-Reply-To: <20100604153525.GA26412@slackbox.erewhon.net> References: <20100604153525.GA26412@slackbox.erewhon.net> Date: Fri, 4 Jun 2010 13:44:41 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Roland Smith" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 20:44:42 -0000 On Fri, June 4, 2010 8:35 am, Roland Smith wrote: > On Fri, Jun 04, 2010 at 12:16:50AM -0700, fbsdmail@dnswatch.com wrote: > >> Greetings, >> If it isn't already apparent, this is my first attempt building kernel >> on an AMD based arch. I have spent some 20yrs building world/kernel on >> the arch i386. But, after reading everything I thought I would need to >> know, I'm /still/ unable to complete a successful kernel build on the >> amd64 arch. >> >> cd /usr/src make buildkernel KERNCONF=MYAMDKERN > > You need to copy MYAMDKERN to /usr/src/sys/amd64/conf/ first! > > >> fails with alot of "i386" errors So, on a fresh 8-RELEASE install from >> DVD w/cvsupped src && ports, now >> running GENERIC, with a successful buildworld... Is it possible to build >> for the amd64 arch? > > You _did_ install the amd64 architecture, right? Not i386? Because if you > installed the i386 it is better to install the amd64 version from > scratch than to try and cross-build and install amd64 on an i386 system. > >> If so, can anyone suggest where I went wrong? >> > > Cross-building and especially installing an amd64 kernel and userland on > i386 is quite involved and not recommended. Save yourself the trouble and > don't go there. > > Just re-install using the CD or DVD built for the amd64 architecture. > It's less > painfull. You should also delete all your ports and rebuild them for > amd64. > > Roland I was a _complete_ DOPE. I had been working on several systems simultaneously with too few hrs. sleep. That I _completely_ overlooked all the "i386" messages during boot. So it didn't _finally_ occur to me _until_ I started to try to determine what would cause world to be built as "i386". Then, like a "ton of bricks" I realized -- D'OH! I shoved the _wrong_ DVD into the system. :-0 Sorry for all the UN-necessary noise, and thanks to everyone for their indulgence. --Chris > -- > 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) > > -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 21:10:44 2010 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 DE6111065676 for ; Fri, 4 Jun 2010 21:10:44 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 896328FC13 for ; Fri, 4 Jun 2010 21:10:43 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o54LAZj0063695; Fri, 4 Jun 2010 14:10:42 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 14:10:42 -0700 (PDT) Message-ID: <5aaba37531e34d9c58c25dc87afdcc74.dnswclient@www.dnswatch.com> In-Reply-To: References: Date: Fri, 4 Jun 2010 14:10:42 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Pete French" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: When will the amd64 be supported? 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, 04 Jun 2010 21:10:44 -0000 On Fri, June 4, 2010 1:30 am, Pete French wrote: >> I'm /really/ just trying to convert all my i386 boxen to amd64. >> > > ....this is the source of your problem. What you were trying to > do in builing amd64 is correct, but only if you are already on an amd64 > platform. Those instrcutions are for building the native architecture. > > If you want to convert an existing system 'in-lace' from i386 > to amd64, then you need to get an install of amd64 on some portable drive > that you can boot from, boot the machine on that, mount the original drive > under '/mnt' or somewhere, and then do an 'installkernel' and > 'installworld' specifying the mountpoint as the destination. > > > It does work - but I would do it with a GENERIC kernel first before > trying a custom kernel. Oh, and also you should delete all your ports > beforehand and then rebuild them afterwards so they get rebuilt for amd64. > > > I would not recommend the above though. You are better off doing > an amd64 install froms cratch. Much less error prone. Thank you for your thoughtful reply, Pete. I'm afraid I got _way_ ahead of myself in my "quest" to get on the AMD64 train. I've been wanting to do it for a great while. But insisted I wait until I had the time and $$ to get really nice && new hardware. So having /finally/ got it, I went straight at it, in spite of the fact that I had already been working too long w/o enough sleep. But having just obtained all that new equipment (see sig below), the adrenalin told me I was fine, just do it. Well, in hind sight; my better judgment _should_ have told me otherwise. :( In short; I was excited about finally getting the hardware I wanted, and neglected to notice I had shoved the _i386_ DVD in the system, instead of the 64bit DVD. Apologies for all the un-necessary noise, and thank you again for your thoughtful reply. --Chris I'm sorry > > -pete. > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 23:09:14 2010 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 723381065676 for ; Fri, 4 Jun 2010 23:09:14 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 3880E8FC0A for ; Fri, 4 Jun 2010 23:09:13 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o54N96bw064076 for ; Fri, 4 Jun 2010 16:09:13 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 16:09:13 -0700 (PDT) Message-ID: <6ff97edb831f3b94f9ace6755bbcda75.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 16:09:13 -0700 (PDT) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: disk oddities on amd64... 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, 04 Jun 2010 23:09:14 -0000 Greetings, Well after using the correct DVD to install FreeBSD on my nice new AMD MD && CPU. I discovered it wasn't possible to complete the install using the official DVD. preface: DVD/RW on usb2 wire (pass) FreeBSD target drive on SATA2/3 port using SATA2 500Gb drive additional drive (untouched by install) UATA/133 40Gb PATA The install process: Boot to install DVD (no problem) Choose "standard" install (no problen) Proceed to FDISK && DISKLEBEL (no problem) Choose "install media" (OOPS! the DVD disappeared!) I finally succeeded by eventually choosing FTP as install media after FDISK && DISKLABEL. But what is really odd about this, is that when I accidentally chose the i386 DVD in an earlier attempt to install to this system. I had zero trouble, and nothing has changed in the BIOS settings, or my procedure - save using the correct DVD this time. ;) In both cases FBSD echoed the BIOS representation of the drive numbering. In both installs the order was the same - both BIOS && FBSD. Now that I have it installed & have built/installed world && kernel, I am experiencing an additional problem w/ drive identification that I didn't experience w/ the i386 version. But I'll post that in a different thread. Thank you for all your time and consideration. --Chris -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 23:36:10 2010 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 129C81065675 for ; Fri, 4 Jun 2010 23:36:10 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id CACAE8FC12 for ; Fri, 4 Jun 2010 23:36:09 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o54Na2cX064218 for ; Fri, 4 Jun 2010 16:36:08 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 16:36:08 -0700 (PDT) Message-ID: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> Date: Fri, 4 Jun 2010 16:36:08 -0700 (PDT) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: why does UATA/133 == UATA/100 on amd64? 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, 04 Jun 2010 23:36:10 -0000 Greetings, After _finally_ making the correct decisions to install amd64 on an AMD64 system. I was able to make/build/install world && kernel, I see a difference in drive recognition. GENERIC kernel from DVD install: kernel: ata3: New devices: 00000001 kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire kernel: ad6: 476940MB at ata3-master SATA300 kernel: ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue NY KERNEL after build/install world/kernel: kernel: ata3: New devices: 00000001 kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire kernel: ad6: setting UDMA100 kernel: ad6: 476940MB at ata3-master UDMA100 SATA 3Gb/s kernel: ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue Did I mention I'm using a STATA cable (like I have a choice). Anyway, interestingly enough, the UATA/133 40Gb PATA drive is correctly recognized in both GENERIC, and MY kernel. The KERNCONF I used is @ https://ultimatedns.NET/XIII_2.gz In case anyone can see something I did wrong. System details are in my "SIG" @ the bottom of this email. Thank you for all your time and consideration. --Chris -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 05:22:20 2010 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 3C6FC106566C for ; Sat, 5 Jun 2010 05:22:20 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id BF5168FC12 for ; Sat, 5 Jun 2010 05:22:19 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c211-30-160-13.mirnd2.nsw.optusnet.com.au [211.30.160.13] (may be forged)) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o555MCtD007873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jun 2010 15:22:14 +1000 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.4/8.14.4) with ESMTP id o555MCdB014474; Sat, 5 Jun 2010 15:22:12 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o555MB0A014473; Sat, 5 Jun 2010 15:22:11 +1000 (EST) (envelope-from peter) Date: Sat, 5 Jun 2010 15:22:11 +1000 From: Peter Jeremy To: fbsdmail@dnswatch.com Message-ID: <20100605052211.GC55626@server.vk2pj.dyndns.org> References: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kVXhAStRUZ/+rrGn" Content-Disposition: inline In-Reply-To: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-amd64@freebsd.org Subject: Re: why does UATA/133 == UATA/100 on amd64? 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, 05 Jun 2010 05:22:20 -0000 --kVXhAStRUZ/+rrGn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: > After _finally_ making the correct decisions to install amd64 on an >AMD64 system. I was able to make/build/install world && kernel, I see >a difference in drive recognition. Can you please do a verbose boot and post the resultant dmesg somewhere (preferably with your USB DVD drive connected). >kernel: ata3-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUDMA133 cable=3D40 wire >kernel: ad6: 476940MB at ata3-master SATA300 >kernel: ata3-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUDMA133 cable=3D40 wire >kernel: ad6: setting UDMA100 >kernel: ad6: 476940MB at ata3-master UDMA100 >SATA 3Gb/s The 'UDMA' numbers are meaningless for SATA controllers/drives. --=20 Peter Jeremy --kVXhAStRUZ/+rrGn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwJ3wMACgkQ/opHv/APuId46ACgpgrNheBnmUIFmTQfk5572FPb fjUAn0iQKejZYKM0uQCBHHr8Gx4xnnV7 =ysnH -----END PGP SIGNATURE----- --kVXhAStRUZ/+rrGn-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 05:58:50 2010 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 599B51065677 for ; Sat, 5 Jun 2010 05:58:50 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D80F28FC0C for ; Sat, 5 Jun 2010 05:58:49 +0000 (UTC) Received: by fxm20 with SMTP id 20so1190420fxm.13 for ; Fri, 04 Jun 2010 22:58:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=XwSajaYpI4KAB2BUyYhDym8+zzx2pvHKWmHj1YuYEfg=; b=oOE+bYyw5QGiFWJ311WUUWDGYbSBPcXwsksGE0OMu6fK0uR9MhcCBYrQ2vvH8K+lSS YID+GaFKNVuqX2nmkCkzRasx9os+m7WS86RLugQehBf2KDTpBgAxK3RcuWQubGx4XsHM G4rAHHS7MtQGyDmjzsWqRCA28PH4pwtzBFMvc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=GXvmMzc3qQyJUD+Z7dv/r4Kuez3cTcWjJlQ8WI8qU4ycM62euUh04xVEyrU21rG3D1 HQ20BrXAHVcRJ9NDADZE7ghLxMrFmq9HaCX2N/iaGAESF8SnkN2PhbtSLcXn8h50WAZk K++g6Z87Skb0p0+BRaHwV4nqJHxTTosCTDm9c= Received: by 10.223.50.193 with SMTP id a1mr693287fag.34.1275717528581; Fri, 04 Jun 2010 22:58:48 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id r25sm8822869fai.11.2010.06.04.22.58.47 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Jun 2010 22:58:48 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C09E783.9090007@FreeBSD.org> Date: Sat, 05 Jun 2010 08:58:27 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Re: why does UATA/133 == UATA/100 on amd64? 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, 05 Jun 2010 05:58:50 -0000 Peter Jeremy wrote: > On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: >> After _finally_ making the correct decisions to install amd64 on an >> AMD64 system. I was able to make/build/install world && kernel, I see >> a difference in drive recognition. > > Can you please do a verbose boot and post the resultant dmesg somewhere > (preferably with your USB DVD drive connected). > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: 476940MB at ata3-master SATA300 > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: setting UDMA100 >> kernel: ad6: 476940MB at ata3-master UDMA100 >> SATA 3Gb/s > > The 'UDMA' numbers are meaningless for SATA controllers/drives. The 'UDMA' numbers are meaningless for _native_ SATA controllers/drives. They may be not meaningless for legacy SATA devices, using SATA->PATA bridge inside. Some bridges do not support UDMA133 on PATA part, so ata(4) prefers not to use it. But in this case it is indeed meaningless. -- Alexander Motin From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 06:25:53 2010 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 C3EBE1065675 for ; Sat, 5 Jun 2010 06:25:53 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8A6EF8FC14 for ; Sat, 5 Jun 2010 06:25:53 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o556Pfor065274; Fri, 4 Jun 2010 23:25:47 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 23:25:48 -0700 (PDT) Message-ID: In-Reply-To: <20100605052211.GC55626@server.vk2pj.dyndns.org> References: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> <20100605052211.GC55626@server.vk2pj.dyndns.org> Date: Fri, 4 Jun 2010 23:25:48 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Peter Jeremy" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: why does UATA/133 == UATA/100 on amd64? 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, 05 Jun 2010 06:25:53 -0000 Greetings Peter, and thank you for your response. On Fri, June 4, 2010 10:22 pm, Peter Jeremy wrote: > On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: > >> After _finally_ making the correct decisions to install amd64 on an >> AMD64 system. I was able to make/build/install world && kernel, I see >> a difference in drive recognition. > > Can you please do a verbose boot and post the resultant dmesg somewhere > (preferably with your USB DVD drive connected). Funny you should ask. I saved one for just this reason. :) To ensure mail clients don't wrap the lines which make it harder to read, I've posted it @ https://ultimatedns.NET/dmesg_2.gz > > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: 476940MB at ata3-master SATA300 >> > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: setting UDMA100 >> kernel: ad6: 476940MB at ata3-master UDMA100 >> SATA 3Gb/s >> > > The 'UDMA' numbers are meaningless for SATA controllers/drives. Then why them emit at all? Thanks again for taking the time to respond. --Chris > > > -- > Peter Jeremy > > -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 06:46:41 2010 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 343F01065672; Sat, 5 Jun 2010 06:46:41 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id D1EB98FC08; Sat, 5 Jun 2010 06:46:40 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o556kXYW065345; Fri, 4 Jun 2010 23:46:39 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 4 Jun 2010 23:46:39 -0700 (PDT) Message-ID: In-Reply-To: <4C09E783.9090007@FreeBSD.org> References: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> <4C09E783.9090007@FreeBSD.org> Date: Fri, 4 Jun 2010 23:46:39 -0700 (PDT) From: fbsdmail@dnswatch.com To: "Alexander Motin" User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: why does UATA/133 == UATA/100 on amd64? 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, 05 Jun 2010 06:46:41 -0000 On Fri, June 4, 2010 10:58 pm, Alexander Motin wrote: > Peter Jeremy wrote: > >> On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: >> >>> After _finally_ making the correct decisions to install amd64 on an >>> AMD64 system. I was able to make/build/install world && kernel, I see >>> a difference in drive recognition. >> >> Can you please do a verbose boot and post the resultant dmesg somewhere >> (preferably with your USB DVD drive connected). >> >> >>> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >>> kernel: ad6: 476940MB at ata3-master >>> SATA300 >>> >> >>> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >>> kernel: ad6: setting UDMA100 >>> kernel: ad6: 476940MB at ata3-master >>> UDMA100 >>> SATA 3Gb/s >>> >> >> The 'UDMA' numbers are meaningless for SATA controllers/drives. >> > > The 'UDMA' numbers are meaningless for _native_ SATA controllers/drives. > > > They may be not meaningless for legacy SATA devices, using SATA->PATA > bridge inside. Some bridges do not support UDMA133 on PATA part, so ata(4) > prefers not to use it. But in this case it is indeed meaningless. If it's not already apparent. The board has an AMD 880G chipset, that provides RAID support on 6 ports @ 6GBs. Now, from a purely logistical standpoint. The numbers _can't_ be meaningless. It's clear that the kernel is making a "judgment call" here: kernel: ad6: setting UDMA100 The "judgment call" on both GENERIC/i386, and GENERIC/amd64 was never made. The capability of both the port && the drive were accepted. Both cases were booted using "verbose" (5). Please understand, I'm not attempting to be argumentative here. I just observe this to be true. In other words; it must have _some_ meaning - no? Thanks for taking the time to respond, Alexander. --Chris > > -- > Alexander Motin > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 10:39:49 2010 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 472BF1065672 for ; Sat, 5 Jun 2010 10:39:49 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C3F778FC15 for ; Sat, 5 Jun 2010 10:39:48 +0000 (UTC) Received: by fxm20 with SMTP id 20so1288105fxm.13 for ; Sat, 05 Jun 2010 03:39:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=siCK+SmPPv56/vKOHVkTPBEbzqKbDtuOq5BtsJ9Q7Z8=; b=uRhzpVEL01+Jp/TDS1rbteKhdtz66VD7xTXMLbzG/jq3fFdOVNu0VTU0La2jugf+0n /wQX6/uyCAE9sf62ejxrdx6wQOcPy7nJT/QR72bZIOIb6z32AoWLKcZSCUbiH1LHhI1G e41zJFEQ7xpIwkG2UdzYdnuUxRKC+4PjbfH8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=ekPkd6XMSb1IqedU7g0ZGHBQX8Ylv6U9Ozkm80OfMWz9H9nAisUHzPHTyyOHfEsf5+ O7wdn+gajEzoTvXCG2BlUoSVJ8FxwNJhbthBUABsI3vw7htwcrRLQdn14n3QMQx7HMTQ 2EoTbHbeicVXTTN5FgXCAp+4UDOsvgF/eWfCU= Received: by 10.223.92.154 with SMTP id r26mr12857320fam.33.1275734387648; Sat, 05 Jun 2010 03:39:47 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 15sm9768718fad.22.2010.06.05.03.39.46 (version=SSLv3 cipher=RC4-MD5); Sat, 05 Jun 2010 03:39:47 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C0A295E.5060809@FreeBSD.org> Date: Sat, 05 Jun 2010 13:39:26 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: fbsdmail@dnswatch.com, freebsd-amd64@freebsd.org References: <4C09E783.9090007@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: why does UATA/133 == UATA/100 on amd64? 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, 05 Jun 2010 10:39:49 -0000 fbsdmail@dnswatch.com wrote: > On Fri, June 4, 2010 10:58 pm, Alexander Motin wrote: >> Peter Jeremy wrote: >>> On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: >>> >>>> After _finally_ making the correct decisions to install amd64 on an >>>> AMD64 system. I was able to make/build/install world && kernel, I see >>>> a difference in drive recognition. >>> Can you please do a verbose boot and post the resultant dmesg somewhere >>> (preferably with your USB DVD drive connected). >>> >>>> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >>>> kernel: ad6: 476940MB at ata3-master >>>> SATA300 >>>> >>>> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >>>> kernel: ad6: setting UDMA100 >>>> kernel: ad6: 476940MB at ata3-master >>>> UDMA100 >>>> SATA 3Gb/s >>>> >>> The 'UDMA' numbers are meaningless for SATA controllers/drives. >>> >> The 'UDMA' numbers are meaningless for _native_ SATA controllers/drives. >> >> They may be not meaningless for legacy SATA devices, using SATA->PATA >> bridge inside. Some bridges do not support UDMA133 on PATA part, so ata(4) >> prefers not to use it. But in this case it is indeed meaningless. > > If it's not already apparent. The board has an AMD 880G chipset, that > provides RAID support on 6 ports @ 6GBs. Now, from a purely logistical > standpoint. The numbers _can't_ be meaningless. It's clear that the kernel > is making a "judgment call" here: kernel: ad6: setting UDMA100 It is impossible to detect SATA->PATA bridge presence, so kernel has to always follow worst scenario. But as I have said, for this particular device this value affects nothing. > The "judgment call" on both GENERIC/i386, and GENERIC/amd64 was never > made. The capability of both the port && the drive were accepted. Both > cases were booted using "verbose" (5). Please understand, I'm not > attempting to be argumentative here. I just observe this to be true. > In other words; it must have _some_ meaning - no? I have feeling that you have updated your sources while building custom kernel. I can't explain difference you have shown by other reasons. -- Alexander Motin From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 19:03:55 2010 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 4D6FD106566B for ; Sat, 5 Jun 2010 19:03:55 +0000 (UTC) (envelope-from hmj@elgert.dk) Received: from smtp.fullrate.dk (smtp.fullrate.dk [90.185.1.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0BA798FC12 for ; Sat, 5 Jun 2010 19:03:54 +0000 (UTC) Received: from mugin.localhost (2404ds2-nivaa.0.fullrate.dk [89.150.160.57]) by smtp.fullrate.dk (Postfix) with ESMTP id A6DB59CEE5 for ; Sat, 5 Jun 2010 20:46:20 +0200 (CEST) Received: from mugin.localhost (localhost [127.0.0.1]) by mugin.localhost (8.14.4/8.14.4) with ESMTP id o55IkLN8008918 for ; Sat, 5 Jun 2010 20:46:21 +0200 (CEST) (envelope-from hmj@mugin.localhost) Received: (from hmj@localhost) by mugin.localhost (8.14.4/8.14.4/Submit) id o55IkL28008917 for freebsd-amd64@freebsd.org; Sat, 5 Jun 2010 20:46:21 +0200 (CEST) (envelope-from hmj) Date: Sat, 5 Jun 2010 20:46:16 +0200 From: Harry Matthiesen Jensen To: freebsd-amd64@freebsd.org Message-ID: <20100605184616.GA8878@mugin.localhost> References: <6ff97edb831f3b94f9ace6755bbcda75.dnswclient@www.dnswatch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <6ff97edb831f3b94f9ace6755bbcda75.dnswclient@www.dnswatch.com> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: disk oddities on amd64... 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, 05 Jun 2010 19:03:55 -0000 On Fri, Jun 04, 2010 at 04:09:13PM -0700, fbsdmail@dnswatch.com wrote: > The install process: > Boot to install DVD (no problem) > Choose "standard" install (no problen) > Proceed to FDISK && DISKLEBEL (no problem) > Choose "install media" (OOPS! the DVD disappeared!) I saw something similar in another thread, which I also experienced, when using a memstick "FIXIT"... maybe that hint also will help you: When you discover the DVD disappear in sysinstall, try the menu item "Options", and select the "Re-scan devices", and then go back to whatever you is trying to do ;-) (for the memstick issue, it is a known issue, but give it a try for the DVD as well) -- Mvh/Brgds Harry FreeBSD 8.1-PRERELEASE #2: Compiled at Wed Jun 2 00:56:50 CEST 2010