From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 14 11:06:54 2009 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99441106568D for ; Mon, 14 Sep 2009 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 86D738FC1E for ; Mon, 14 Sep 2009 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8EB6sRq072235 for ; Mon, 14 Sep 2009 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8EB6r7i072231 for freebsd-amd64@FreeBSD.org; Mon, 14 Sep 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Sep 2009 11:06:53 GMT Message-Id: <200909141106.n8EB6r7i072231@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 X-Mailman-Approved-At: Mon, 14 Sep 2009 11:27:22 +0000 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, 14 Sep 2009 11:06:54 -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 -------------------------------------------------------------------------------- f amd64/138661 amd64 [panic] Kernel Panic after typing "reboot" o amd64/138626 amd64 telepites o amd64/138318 amd64 [libc] [patch] select(2) in i386 emulation can overwri o amd64/138220 amd64 [amd64] [patch] FreeBSD/amd64 can't see all system mem 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 o amd64/136814 amd64 [mxge] mxge driver error 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 o amd64/132372 amd64 [ata] No disks found (nVidia nForce MCP55 sata control o 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 o 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/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128686 amd64 [ata] can't detect SATA Disk on 8.0-Current with NF550 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/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 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 o 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/122624 amd64 unusable minimal installation of FreeBSD-7.0 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 o 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/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 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/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 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 96 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 14 21:35:13 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A8BA1065697; Mon, 14 Sep 2009 21:35:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4C6B08FC14; Mon, 14 Sep 2009 21:35:13 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id EE5D346B35; Mon, 14 Sep 2009 17:35:12 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id EDF038A01B; Mon, 14 Sep 2009 17:35:11 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org, "James R. Van Artsdalen" Date: Mon, 14 Sep 2009 17:35:04 -0400 User-Agent: KMail/1.9.7 References: <200908262239.n7QMdeHV045328@bigtex.housenet.jrv> In-Reply-To: <200908262239.n7QMdeHV045328@bigtex.housenet.jrv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909141735.05018.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 14 Sep 2009 17:35:11 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/138220: [patch] FreeBSD/amd64 can't see all system memory 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, 14 Sep 2009 21:35:13 -0000 Can you try this alternate patch instead? I am leery of manipulating the SMAP directly since it resides in the kernel's module metadata which in theory should be read-only. This patch changes the SMAP code to do an insertion sort into the physmap[] array for each new entry that is added. I also changed the amd64 code to use a separate static routine to add each entry similar to i386 which fixes the bug with overlapping regions that you noted while keeping the SMAP code identical between the two archs. --- //depot/vendor/freebsd/src/sys/amd64/amd64/machdep.c 2009/08/20 23:00:20 +++ //depot/user/jhb/numa/sys/amd64/amd64/machdep.c 2009/09/14 19:37:10 @@ -1192,6 +1192,77 @@ u_int basemem; +static int +add_smap_entry(struct bios_smap *smap, vm_paddr_t *physmap, int *physmap_idxp) +{ + int i, insert_idx, physmap_idx; + + physmap_idx = *physmap_idxp; + + if (boothowto & RB_VERBOSE) + printf("SMAP type=%02x base=%016lx len=%016lx\n", + smap->type, smap->base, smap->length); + + if (smap->type != SMAP_TYPE_MEMORY) + return (1); + + if (smap->length == 0) + return (0); + + /* + * Find insertion point while checking for overlap. Start off by + * assuming the new entry will be added to the end. + */ + insert_idx = physmap_idx + 2; + for (i = 0; i <= physmap_idx; i += 2) { + if (smap->base < physmap[i + 1]) { + if (smap->base + smap->length <= physmap[i]) { + insert_idx = i; + break; + } + if (boothowto & RB_VERBOSE) + printf( + "Overlapping or non-monotonic memory region, ignoring second region\n"); + return (1); + } + } + + /* See if we can prepend to the next entry. */ + if (insert_idx <= physmap_idx && + smap->base + smap->length == physmap[insert_idx]) { + physmap[insert_idx] = smap->base; + return (1); + } + + /* See if we can append to the previous entry. */ + if (insert_idx > 0 && smap->base == physmap[insert_idx - 1]) { + physmap[insert_idx - 1] += smap->length; + return (1); + } + + physmap_idx += 2; + *physmap_idxp = physmap_idx; + if (physmap_idx == PHYSMAP_SIZE) { + printf( + "Too many segments in the physical address map, giving up\n"); + return (0); + } + + /* + * Move the last 'N' entries down to make room for the new + * entry if needed. + */ + for (i = physmap_idx - 2; i > insert_idx; i -= 2) { + physmap[i] = physmap[i - 2]; + physmap[i + 1] = physmap[i - 1]; + } + + /* Insert the new entry. */ + physmap[insert_idx] = smap->base; + physmap[insert_idx + 1] = smap->base + smap->length; + return (1); +} + /* * Populate the (physmap) array with base/bound pairs describing the * available physical memory in the system, then test this memory and @@ -1235,40 +1306,9 @@ smapsize = *((u_int32_t *)smapbase - 1); smapend = (struct bios_smap *)((uintptr_t)smapbase + smapsize); - for (smap = smapbase; smap < smapend; smap++) { - if (boothowto & RB_VERBOSE) - printf("SMAP type=%02x base=%016lx len=%016lx\n", - smap->type, smap->base, smap->length); - - if (smap->type != SMAP_TYPE_MEMORY) - continue; - - if (smap->length == 0) - continue; - - for (i = 0; i <= physmap_idx; i += 2) { - if (smap->base < physmap[i + 1]) { - if (boothowto & RB_VERBOSE) - printf( - "Overlapping or non-monotonic memory region, ignoring second region\n"); - continue; - } - } - - if (smap->base == physmap[physmap_idx + 1]) { - physmap[physmap_idx + 1] += smap->length; - continue; - } - - physmap_idx += 2; - if (physmap_idx == PHYSMAP_SIZE) { - printf( - "Too many segments in the physical address map, giving up\n"); + for (smap = smapbase; smap < smapend; smap++) + if (!add_smap_entry(smap, physmap, &physmap_idx)) break; - } - physmap[physmap_idx] = smap->base; - physmap[physmap_idx + 1] = smap->base + smap->length; - } /* * Find the 'base memory' segment for SMP --- //depot/vendor/freebsd/src/sys/i386/i386/machdep.c 2009/09/04 14:55:14 +++ //depot/user/jhb/numa/sys/i386/i386/machdep.c 2009/09/14 19:37:10 @@ -1946,7 +1946,7 @@ static int add_smap_entry(struct bios_smap *smap, vm_paddr_t *physmap, int *physmap_idxp) { - int i, physmap_idx; + int i, insert_idx, physmap_idx; physmap_idx = *physmap_idxp; @@ -1968,8 +1968,17 @@ } #endif + /* + * Find insertion point while checking for overlap. Start off by + * assuming the new entry will be added to the end. + */ + insert_idx = physmap_idx + 2; for (i = 0; i <= physmap_idx; i += 2) { if (smap->base < physmap[i + 1]) { + if (smap->base + smap->length <= physmap[i]) { + insert_idx = i; + break; + } if (boothowto & RB_VERBOSE) printf( "Overlapping or non-monotonic memory region, ignoring second region\n"); @@ -1977,8 +1986,16 @@ } } - if (smap->base == physmap[physmap_idx + 1]) { - physmap[physmap_idx + 1] += smap->length; + /* See if we can prepend to the next entry. */ + if (insert_idx <= physmap_idx && + smap->base + smap->length == physmap[insert_idx]) { + physmap[insert_idx] = smap->base; + return (1); + } + + /* See if we can append to the previous entry. */ + if (insert_idx > 0 && smap->base == physmap[insert_idx - 1]) { + physmap[insert_idx - 1] += smap->length; return (1); } @@ -1989,8 +2006,19 @@ "Too many segments in the physical address map, giving up\n"); return (0); } - physmap[physmap_idx] = smap->base; - physmap[physmap_idx + 1] = smap->base + smap->length; + + /* + * Move the last 'N' entries down to make room for the new + * entry if needed. + */ + for (i = physmap_idx - 2; i > insert_idx; i -= 2) { + physmap[i] = physmap[i - 2]; + physmap[i + 1] = physmap[i - 1]; + } + + /* Insert the new entry. */ + physmap[insert_idx] = smap->base; + physmap[insert_idx + 1] = smap->base + smap->length; return (1); } -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 14 21:40:04 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49F801065670 for ; Mon, 14 Sep 2009 21:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC148FC08 for ; Mon, 14 Sep 2009 21:40:04 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8ELe4wN008181 for ; Mon, 14 Sep 2009 21:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8ELe4pb008180; Mon, 14 Sep 2009 21:40:04 GMT (envelope-from gnats) Date: Mon, 14 Sep 2009 21:40:04 GMT Message-Id: <200909142140.n8ELe4pb008180@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/138220: [patch] FreeBSD/amd64 can't see all system memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2009 21:40:04 -0000 The following reply was made to PR amd64/138220; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org, "James R. Van Artsdalen" Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/138220: [patch] FreeBSD/amd64 can't see all system memory Date: Mon, 14 Sep 2009 17:35:04 -0400 Can you try this alternate patch instead? I am leery of manipulating the SMAP directly since it resides in the kernel's module metadata which in theory should be read-only. This patch changes the SMAP code to do an insertion sort into the physmap[] array for each new entry that is added. I also changed the amd64 code to use a separate static routine to add each entry similar to i386 which fixes the bug with overlapping regions that you noted while keeping the SMAP code identical between the two archs. --- //depot/vendor/freebsd/src/sys/amd64/amd64/machdep.c 2009/08/20 23:00:20 +++ //depot/user/jhb/numa/sys/amd64/amd64/machdep.c 2009/09/14 19:37:10 @@ -1192,6 +1192,77 @@ u_int basemem; +static int +add_smap_entry(struct bios_smap *smap, vm_paddr_t *physmap, int *physmap_idxp) +{ + int i, insert_idx, physmap_idx; + + physmap_idx = *physmap_idxp; + + if (boothowto & RB_VERBOSE) + printf("SMAP type=%02x base=%016lx len=%016lx\n", + smap->type, smap->base, smap->length); + + if (smap->type != SMAP_TYPE_MEMORY) + return (1); + + if (smap->length == 0) + return (0); + + /* + * Find insertion point while checking for overlap. Start off by + * assuming the new entry will be added to the end. + */ + insert_idx = physmap_idx + 2; + for (i = 0; i <= physmap_idx; i += 2) { + if (smap->base < physmap[i + 1]) { + if (smap->base + smap->length <= physmap[i]) { + insert_idx = i; + break; + } + if (boothowto & RB_VERBOSE) + printf( + "Overlapping or non-monotonic memory region, ignoring second region\n"); + return (1); + } + } + + /* See if we can prepend to the next entry. */ + if (insert_idx <= physmap_idx && + smap->base + smap->length == physmap[insert_idx]) { + physmap[insert_idx] = smap->base; + return (1); + } + + /* See if we can append to the previous entry. */ + if (insert_idx > 0 && smap->base == physmap[insert_idx - 1]) { + physmap[insert_idx - 1] += smap->length; + return (1); + } + + physmap_idx += 2; + *physmap_idxp = physmap_idx; + if (physmap_idx == PHYSMAP_SIZE) { + printf( + "Too many segments in the physical address map, giving up\n"); + return (0); + } + + /* + * Move the last 'N' entries down to make room for the new + * entry if needed. + */ + for (i = physmap_idx - 2; i > insert_idx; i -= 2) { + physmap[i] = physmap[i - 2]; + physmap[i + 1] = physmap[i - 1]; + } + + /* Insert the new entry. */ + physmap[insert_idx] = smap->base; + physmap[insert_idx + 1] = smap->base + smap->length; + return (1); +} + /* * Populate the (physmap) array with base/bound pairs describing the * available physical memory in the system, then test this memory and @@ -1235,40 +1306,9 @@ smapsize = *((u_int32_t *)smapbase - 1); smapend = (struct bios_smap *)((uintptr_t)smapbase + smapsize); - for (smap = smapbase; smap < smapend; smap++) { - if (boothowto & RB_VERBOSE) - printf("SMAP type=%02x base=%016lx len=%016lx\n", - smap->type, smap->base, smap->length); - - if (smap->type != SMAP_TYPE_MEMORY) - continue; - - if (smap->length == 0) - continue; - - for (i = 0; i <= physmap_idx; i += 2) { - if (smap->base < physmap[i + 1]) { - if (boothowto & RB_VERBOSE) - printf( - "Overlapping or non-monotonic memory region, ignoring second region\n"); - continue; - } - } - - if (smap->base == physmap[physmap_idx + 1]) { - physmap[physmap_idx + 1] += smap->length; - continue; - } - - physmap_idx += 2; - if (physmap_idx == PHYSMAP_SIZE) { - printf( - "Too many segments in the physical address map, giving up\n"); + for (smap = smapbase; smap < smapend; smap++) + if (!add_smap_entry(smap, physmap, &physmap_idx)) break; - } - physmap[physmap_idx] = smap->base; - physmap[physmap_idx + 1] = smap->base + smap->length; - } /* * Find the 'base memory' segment for SMP --- //depot/vendor/freebsd/src/sys/i386/i386/machdep.c 2009/09/04 14:55:14 +++ //depot/user/jhb/numa/sys/i386/i386/machdep.c 2009/09/14 19:37:10 @@ -1946,7 +1946,7 @@ static int add_smap_entry(struct bios_smap *smap, vm_paddr_t *physmap, int *physmap_idxp) { - int i, physmap_idx; + int i, insert_idx, physmap_idx; physmap_idx = *physmap_idxp; @@ -1968,8 +1968,17 @@ } #endif + /* + * Find insertion point while checking for overlap. Start off by + * assuming the new entry will be added to the end. + */ + insert_idx = physmap_idx + 2; for (i = 0; i <= physmap_idx; i += 2) { if (smap->base < physmap[i + 1]) { + if (smap->base + smap->length <= physmap[i]) { + insert_idx = i; + break; + } if (boothowto & RB_VERBOSE) printf( "Overlapping or non-monotonic memory region, ignoring second region\n"); @@ -1977,8 +1986,16 @@ } } - if (smap->base == physmap[physmap_idx + 1]) { - physmap[physmap_idx + 1] += smap->length; + /* See if we can prepend to the next entry. */ + if (insert_idx <= physmap_idx && + smap->base + smap->length == physmap[insert_idx]) { + physmap[insert_idx] = smap->base; + return (1); + } + + /* See if we can append to the previous entry. */ + if (insert_idx > 0 && smap->base == physmap[insert_idx - 1]) { + physmap[insert_idx - 1] += smap->length; return (1); } @@ -1989,8 +2006,19 @@ "Too many segments in the physical address map, giving up\n"); return (0); } - physmap[physmap_idx] = smap->base; - physmap[physmap_idx + 1] = smap->base + smap->length; + + /* + * Move the last 'N' entries down to make room for the new + * entry if needed. + */ + for (i = physmap_idx - 2; i > insert_idx; i -= 2) { + physmap[i] = physmap[i - 2]; + physmap[i + 1] = physmap[i - 1]; + } + + /* Insert the new entry. */ + physmap[insert_idx] = smap->base; + physmap[insert_idx + 1] = smap->base + smap->length; return (1); } -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 16 15:40:04 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 879B810656A3 for ; Wed, 16 Sep 2009 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 652378FC22 for ; Wed, 16 Sep 2009 15:40:04 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8GFe4Hp025716 for ; Wed, 16 Sep 2009 15:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8GFe4DI025715; Wed, 16 Sep 2009 15:40:04 GMT (envelope-from gnats) Resent-Date: Wed, 16 Sep 2009 15:40:04 GMT Resent-Message-Id: <200909161540.n8GFe4DI025715@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Zhambolat Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B18E510656C0 for ; Wed, 16 Sep 2009 15:38:08 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id A07228FC08 for ; Wed, 16 Sep 2009 15:38:08 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n8GFc8P8045960 for ; Wed, 16 Sep 2009 15:38:08 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n8GFc7RT045958; Wed, 16 Sep 2009 15:38:07 GMT (envelope-from nobody) Message-Id: <200909161538.n8GFc7RT045958@www.freebsd.org> Date: Wed, 16 Sep 2009 15:38:07 GMT From: Zhambolat To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Wed, 16 Sep 2009 18:35:03 +0000 Cc: Subject: amd64/138882: Can't install FreeBSD 7.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2009 15:40:04 -0000 >Number: 138882 >Category: amd64 >Synopsis: Can't install FreeBSD 7.2 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 16 15:40:04 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Zhambolat >Release: 7.2 >Organization: >Environment: >Description: Hi! I'm new in FreeBSD. During installation of FreeBSD 7.2 I get an error message of this kind: panic: ohci_add_done: addr 0xd7ef17d0 not found cpuid = 0 Uptime: 1s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot? --> or switch off the system now. How this problem could be solved? Thank you! My configuration: AMD Athlon64 X2 on ASUS M2A-VM(North-AMD690G,South-ATI SB600) with 4Gb of DDR800. HDD - Seagate 500Gb on SATA. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 17 12:25:08 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9071A106568B; Thu, 17 Sep 2009 12:25:08 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 667F98FC14; Thu, 17 Sep 2009 12:25:08 +0000 (UTC) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8HCP8iI027295; Thu, 17 Sep 2009 12:25:08 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8HCP7xG027291; Thu, 17 Sep 2009 12:25:07 GMT (envelope-from vwe) Date: Thu, 17 Sep 2009 12:25:07 GMT Message-Id: <200909171225.n8HCP7xG027291@freefall.freebsd.org> To: open@di.mon.net.ua, vwe@FreeBSD.org, freebsd-amd64@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: amd64/132019: [install] kernel trap 12 while installation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 12:25:08 -0000 Synopsis: [install] kernel trap 12 while installation State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Thu Sep 17 12:24:03 UTC 2009 State-Changed-Why: your CPU-ID looks quite strange. Can we please see a dmesg of a working operating system (say NetBSD or any other *nix)? http://www.freebsd.org/cgi/query-pr.cgi?pr=132019 From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 17 13:00:17 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CFAE106568F for ; Thu, 17 Sep 2009 13:00:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1BBBD8FC13 for ; Thu, 17 Sep 2009 13:00:17 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8HD0GrX059268 for ; Thu, 17 Sep 2009 13:00:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8HD0GbZ059265; Thu, 17 Sep 2009 13:00:16 GMT (envelope-from gnats) Date: Thu, 17 Sep 2009 13:00:16 GMT Message-Id: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/138882: Can't install FreeBSD 7.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 13:00:17 -0000 The following reply was made to PR amd64/138882; it has been noted by GNATS. From: John Baldwin To: Zhambolat Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/138882: Can't install FreeBSD 7.2 Date: Thu, 17 Sep 2009 08:59:46 -0400 Zhambolat wrote: >> Number: 138882 >> Category: amd64 >> Synopsis: Can't install FreeBSD 7.2 >> Confidential: no >> Severity: critical >> Priority: high >> Responsible: freebsd-amd64 >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: sw-bug >> Submitter-Id: current-users >> Arrival-Date: Wed Sep 16 15:40:04 UTC 2009 >> Closed-Date: >> Last-Modified: >> Originator: Zhambolat >> Release: 7.2 >> Organization: >> Environment: >> Description: > Hi! > I'm new in FreeBSD. > During installation of FreeBSD 7.2 I get an error message of this kind: > > panic: ohci_add_done: addr 0xd7ef17d0 not found > cpuid = 0 > Uptime: 1s > Cannot dump. No dump device defined. > Automatic reboot in 15 seconds - press a key on the console to abort > --> Press a key on the console to reboot? > --> or switch off the system now. > > How this problem could be solved? Try turning off legacy USB support in your BIOS. I have a machine at home that has run 6.x and 7.x/i386 that has this same issue. The problem appears to be that ohci_reset() doesn't fully clear the state of the ohci(4) controller and when the driver first probes it sees a completed USB request that was the last request initiated by the BIOS. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 08:27:02 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E847B1065672 for ; Fri, 18 Sep 2009 08:27:02 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id A6EEF8FC0A for ; Fri, 18 Sep 2009 08:27:02 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KQ500KRJRH103C0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 18 Sep 2009 10:27:01 +0200 (CEST) Received: from kg-v2.kg4.no ([84.48.215.119]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0KQ500DB6RH0M080@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 18 Sep 2009 10:27:01 +0200 (CEST) Date: Fri, 18 Sep 2009 10:27:00 +0200 From: Torfinn Ingolfsen To: freebsd-amd64@freebsd.org Message-id: <20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> In-reply-to: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> References: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; amd64-portbld-freebsd7.2) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: amd64/138882: Can't install FreeBSD 7.2 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, 18 Sep 2009 08:27:03 -0000 On Thu, 17 Sep 2009 13:00:16 +0000 (GMT) John Baldwin wrote: > Try turning off legacy USB support in your BIOS. I have a machine > at home that has run 6.x and 7.x/i386 that has this same issue. The > problem appears to be that ohci_reset() doesn't fully clear the > state of the ohci(4) controller and when the driver first probes it > sees a completed USB request that was the last request initiated by > the BIOS. Or if that doesn't work (I have a M2A-VM HDMI, but I don't know how old a BIOS he has) he can remove all usb attached devices during boot. For some reason, most devices work fine when plugged in after the machine has booted. (Some devices will panic the machine, but that is another story) HTH -- Regards, Torfinn Ingolfsen From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 09:55:23 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7993106566C for ; Fri, 18 Sep 2009 09:55:23 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id BA9268FC0C for ; Fri, 18 Sep 2009 09:55:23 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 6929446B06; Fri, 18 Sep 2009 05:55:23 -0400 (EDT) Received: from John-Baldwins-Macbook-Pro.local (localhost [IPv6:::1]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 43B558A01B; Fri, 18 Sep 2009 05:55:22 -0400 (EDT) Message-ID: <4AB3590A.5040805@FreeBSD.org> Date: Fri, 18 Sep 2009 05:55:22 -0400 From: John Baldwin User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Torfinn Ingolfsen References: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> <20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 18 Sep 2009 05:55:22 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/138882: Can't install FreeBSD 7.2 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, 18 Sep 2009 09:55:24 -0000 Torfinn Ingolfsen wrote: > On Thu, 17 Sep 2009 13:00:16 +0000 (GMT) > John Baldwin wrote: > >> Try turning off legacy USB support in your BIOS. I have a machine >> at home that has run 6.x and 7.x/i386 that has this same issue. The >> problem appears to be that ohci_reset() doesn't fully clear the >> state of the ohci(4) controller and when the driver first probes it >> sees a completed USB request that was the last request initiated by >> the BIOS. > > Or if that doesn't work (I have a M2A-VM HDMI, but I don't know how old > a BIOS he has) he can remove all usb attached devices during boot. > For some reason, most devices work fine when plugged in after the > machine has booted. > (Some devices will panic the machine, but that is another story) Yes, that is true in my experience as well. In my case I have a UPS with a USB adapter plugged in and removing it during boot was another workaround. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 14:36:01 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FD9B106566B for ; Fri, 18 Sep 2009 14:36:01 +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 70CE28FC14 for ; Fri, 18 Sep 2009 14:36:00 +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 RAA14871; Fri, 18 Sep 2009 17:20:09 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AB39719.5030709@icyb.net.ua> Date: Fri, 18 Sep 2009 17:20:09 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: John Baldwin References: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> <20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> <4AB3590A.5040805@FreeBSD.org> In-Reply-To: <4AB3590A.5040805@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 18 Sep 2009 16:15:57 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/138882: Can't install FreeBSD 7.2 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, 18 Sep 2009 14:36:01 -0000 on 18/09/2009 12:55 John Baldwin said the following: > Torfinn Ingolfsen wrote: >> On Thu, 17 Sep 2009 13:00:16 +0000 (GMT) >> John Baldwin wrote: >> >>> Try turning off legacy USB support in your BIOS. I have a machine >>> at home that has run 6.x and 7.x/i386 that has this same issue. The >>> problem appears to be that ohci_reset() doesn't fully clear the >>> state of the ohci(4) controller and when the driver first probes it >>> sees a completed USB request that was the last request initiated by >>> the BIOS. >> >> Or if that doesn't work (I have a M2A-VM HDMI, but I don't know how old >> a BIOS he has) he can remove all usb attached devices during boot. >> For some reason, most devices work fine when plugged in after the >> machine has booted. >> (Some devices will panic the machine, but that is another story) > > Yes, that is true in my experience as well. In my case I have a UPS > with a USB adapter plugged in and removing it during boot was another > workaround. I am debugging a somewhat related problem with head code and SB700 ohci. The problem is that certain ports become unusable of there is a keyboard or mouse attached to them during boot. My findings so far: 1) the problem happens only with ports provided by ohci0 (the very first PCI OHCI device) 2) the problem is that some configuration registers of ohci controller get mysteriously changed after ohci driver configures them and before the first interrupt gets generated by the controller; registers in question are HcControlHeadED and HcDoneHead. Looks like perhaps either the controller doesn't get "sufficiently" reset/re-initialized or firmware/SMM code touches the controller after handover procedure completes. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 16:06:01 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C006106566C for ; Fri, 18 Sep 2009 16:06:01 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CCEAC8FC0C for ; Fri, 18 Sep 2009 16:06:00 +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 SAA16137; Fri, 18 Sep 2009 18:50:39 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4AB3AC4E.4060506@freebsd.org> Date: Fri, 18 Sep 2009 18:50:38 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: John Baldwin References: <200909171300.n8HD0GbZ059265@freefall.freebsd.org> <20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> <4AB3590A.5040805@FreeBSD.org> <4AB39719.5030709@icyb.net.ua> In-Reply-To: <4AB39719.5030709@icyb.net.ua> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 18 Sep 2009 16:42:35 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/138882: Can't install FreeBSD 7.2 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, 18 Sep 2009 16:06:01 -0000 on 18/09/2009 17:20 Andriy Gapon said the following: > I am debugging a somewhat related problem with head code and SB700 ohci. > The problem is that certain ports become unusable of there is a keyboard or mouse > attached to them during boot. > My findings so far: > 1) the problem happens only with ports provided by ohci0 (the very first PCI OHCI > device) > 2) the problem is that some configuration registers of ohci controller get > mysteriously changed after ohci driver configures them and before the first > interrupt gets generated by the controller; registers in question are > HcControlHeadED and HcDoneHead. > > Looks like perhaps either the controller doesn't get "sufficiently" > reset/re-initialized or firmware/SMM code touches the controller after handover > procedure completes. My current suspicion is that ohci(4) doesn't clear some memory that it allocates for shared use with HC (hardware) and sets a HC register to point to that memory. So when HC goes to operation state and examines that memory and sees something that looks like valid data, HC uses it and goes bad way. But this is just a hypothesis that I've just dreamed up. I am going to test it some time later. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 22:11:11 2009 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD9E01065670; Fri, 18 Sep 2009 22:11:11 +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 B53938FC0C; Fri, 18 Sep 2009 22:11:11 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n8IMBBpg005918; Fri, 18 Sep 2009 15:11:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n8IMBBWo005917; Fri, 18 Sep 2009 15:11:11 -0700 (PDT) (envelope-from sgk) Date: Fri, 18 Sep 2009 15:11:11 -0700 From: Steve Kargl To: "b. f." Message-ID: <20090918221111.GA5821@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: jeff@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: new to 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, 18 Sep 2009 22:11:11 -0000 On Fri, Sep 18, 2009 at 09:49:57PM +0000, b. f. wrote: > Steve Kargl wrote: > > > >If you are running any floating point intensive applications > >and these applications are multithreaded, you may want to use > >the 4BSD scheduler rathar than ULE. The last time I tested > >ULE with an MPI application, it display miserable performance > >on a dual, quad-core opteron system. > > Have you made any attempt to analyze this problem, or discussed it > with the primary author of ULE? yes and yes. > If so, to what do you attribute the poor performance, and do you > have any ideas on how to improve ULE performance in this context? The only acceptable solution I found was to switch to 4BSD. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 18 22:11:37 2009 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B8751065679; Fri, 18 Sep 2009 22:11:37 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 742788FC08; Fri, 18 Sep 2009 22:11:36 +0000 (UTC) Received: by ewy4 with SMTP id 4so861199ewy.36 for ; Fri, 18 Sep 2009 15:11:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=s0nibVD6mAjZrRGw2OSRKtxwCoLXBDiIi0VkMR/ZkZw=; b=ahw1zWRJXBCpIzwczdG/sqSw/EgPdR4XOTePEy+qEht0TUHSAIUcVKBM3BTYk1JPez QwbiEatdKQ3qj8Dl4QAg6bqFAGnYqstcazhpP0F3HvgnNVn1KonWRNxamBErzT0r848p cCIax5wOPXKaL00fOOhtOa1d5xYn9fzJffTDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=NENUcKLVFaVdAQbfv+u2xTR8OGFdTAAHs5WWybL4qlXj9etkOIXemYyBsFub0IA1By bK3vYsF6+RM78YLa45E/Utyu1MkHmGJoSU2p2T58KFjbNtR33hbhWIOd7CwRQqpqYcir O3vwPieVJs6EbEcDy/7AHVxWJVyRFcA4Sz5Ag= MIME-Version: 1.0 Received: by 10.216.1.11 with SMTP id 11mr648588wec.147.1253310597906; Fri, 18 Sep 2009 14:49:57 -0700 (PDT) Date: Fri, 18 Sep 2009 21:49:57 +0000 Message-ID: From: "b. f." To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Fri, 18 Sep 2009 22:25:47 +0000 Cc: jeff@FreeBSD.org Subject: Re: new to 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, 18 Sep 2009 22:11:37 -0000 Steve Kargl wrote: > >If you are running any floating point intensive applications >and these applications are multithreaded, you may want to use >the 4BSD scheduler rathar than ULE. The last time I tested >ULE with an MPI application, it display miserable performance >on a dual, quad-core opteron system. Have you made any attempt to analyze this problem, or discussed it with the primary author of ULE? If so, to what do you attribute the poor performance, and do you have any ideas on how to improve ULE performance in this context? Regards, b. From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 19 17:30:36 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B01C41065670 for ; Sat, 19 Sep 2009 17:30:36 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 8C60A8FC12 for ; Sat, 19 Sep 2009 17:30:36 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Mp3lb-0004v1-R1 for freebsd-amd64@freebsd.org; Sat, 19 Sep 2009 10:30:35 -0700 Message-ID: <25523741.post@talk.nabble.com> Date: Sat, 19 Sep 2009 10:30:35 -0700 (PDT) From: JonathanGilpin To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jonathan@fluent.ltd.uk X-Mailman-Approved-At: Sat, 19 Sep 2009 18:03:27 +0000 Subject: Switching to AMD64 from I386 using make world 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, 19 Sep 2009 17:30:36 -0000 Hi, I have an i386 system running and I want to switch to AMD64. Is this possible using make world and a kernel recompile? If so, could someone point me in the right direction as I'm getting errors on make depend on the kernel compile.. Jonathan -- View this message in context: http://www.nabble.com/Switching-to-AMD64-from-I386-using-make-world-tp25523741p25523741.html Sent from the freebsd-amd64 mailing list archive at Nabble.com. From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 19 18:14:34 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16E3D1065679 for ; Sat, 19 Sep 2009 18:14:34 +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 F305A8FC19 for ; Sat, 19 Sep 2009 18:14:33 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n8JIEWGx011830; Sat, 19 Sep 2009 11:14:32 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n8JIEWSR011829; Sat, 19 Sep 2009 11:14:32 -0700 (PDT) (envelope-from sgk) Date: Sat, 19 Sep 2009 11:14:32 -0700 From: Steve Kargl To: JonathanGilpin Message-ID: <20090919181432.GA11815@troutmask.apl.washington.edu> References: <25523741.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25523741.post@talk.nabble.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-amd64@freebsd.org Subject: Re: Switching to AMD64 from I386 using make world 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, 19 Sep 2009 18:14:34 -0000 On Sat, Sep 19, 2009 at 10:30:35AM -0700, JonathanGilpin wrote: > > I have an i386 system running and I want to switch to AMD64. Is this > possible using make world and a kernel recompile? At one time, the answer was 'no' I don't know if this is still true. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 19 20:06:45 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6EE91065676 for ; Sat, 19 Sep 2009 20:06:45 +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 7DBF58FC1B for ; Sat, 19 Sep 2009 20:06:44 +0000 (UTC) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id n8JK6hwo081759; Sat, 19 Sep 2009 22:06:43 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 3F9FFBAAD; Sat, 19 Sep 2009 22:06:43 +0200 (CEST) Date: Sat, 19 Sep 2009 22:06:43 +0200 From: Roland Smith To: JonathanGilpin Message-ID: <20090919200643.GA70447@slackbox.xs4all.nl> References: <25523741.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: <25523741.post@talk.nabble.com> 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: Switching to AMD64 from I386 using make world 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, 19 Sep 2009 20:06:46 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 19, 2009 at 10:30:35AM -0700, JonathanGilpin wrote: >=20 > Hi, >=20 > I have an i386 system running and I want to switch to AMD64. Is this > possible using make world and a kernel recompile? If so, could someone po= int > me in the right direction as I'm getting errors on make depend on the ker= nel > compile.. =20 It should be possible. But you'd have to write the new kernel and userland = to a separate partition or disk. And on the next boot you would have to boot f= rom that partition/disk. Since most people do not have a separate partition handy, a better option would be to make a full backup of your data and install amd64. Keep in mind that amd64 binaries are somewhat larger on disk than i386 ones, so you might want to adjust partition sizes. You will also have to install all your ports again as amd64 binaries. While you are at it, try the 8.0-RC ISO to reinstall from (it has just popp= ed up on ftp.freebsd.org, so you might have to wait for it to get to a mirror near you). I've installed 8.0-BETA4 amd64 on my new laptop and it runs OK. 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) --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkq1OdMACgkQEnfvsMMhpyU03wCdHcodL522qecC/tJYOB2q1te6 fZwAoIZuBDtUKTMzV+TwQIO/KqEZXYFe =zxLn -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 19 20:19:29 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33F16106566B for ; Sat, 19 Sep 2009 20:19:29 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 889038FC12 for ; Sat, 19 Sep 2009 20:19:28 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n8JKJL2X097315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 19 Sep 2009 23:19:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n8JKJKP0004564; Sat, 19 Sep 2009 23:19:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n8JKJKRs004563; Sat, 19 Sep 2009 23:19:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 19 Sep 2009 23:19:20 +0300 From: Kostik Belousov To: Roland Smith Message-ID: <20090919201920.GI47688@deviant.kiev.zoral.com.ua> References: <25523741.post@talk.nabble.com> <20090919200643.GA70447@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Oe/ScElO4SkQHdx9" Content-Disposition: inline In-Reply-To: <20090919200643.GA70447@slackbox.xs4all.nl> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: JonathanGilpin , freebsd-amd64@freebsd.org Subject: Re: Switching to AMD64 from I386 using make world 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, 19 Sep 2009 20:19:29 -0000 --Oe/ScElO4SkQHdx9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 19, 2009 at 10:06:43PM +0200, Roland Smith wrote: > On Sat, Sep 19, 2009 at 10:30:35AM -0700, JonathanGilpin wrote: > >=20 > > Hi, > >=20 > > I have an i386 system running and I want to switch to AMD64. Is this > > possible using make world and a kernel recompile? If so, could someone = point > > me in the right direction as I'm getting errors on make depend on the k= ernel > > compile.. > =20 > It should be possible. But you'd have to write the new kernel and userlan= d to > a separate partition or disk. And on the next boot you would have to boot= from > that partition/disk. >=20 > Since most people do not have a separate partition handy, a better option Use swap. This is well-known trick called miniroot. > would be to make a full backup of your data and install amd64. Keep in mi= nd > that amd64 binaries are somewhat larger on disk than i386 ones, so you mi= ght > want to adjust partition sizes. You will also have to install all your po= rts > again as amd64 binaries. Not system-management 32bit applications should mostly work on amd64. --Oe/ScElO4SkQHdx9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkq1PMgACgkQC3+MBN1Mb4j18ACgjYiEIHkt5q7qeSpqkEpxvBK3 lEMAoL+kEAe/D1fLfEaEmLOZaGSxNy3a =qN6A -----END PGP SIGNATURE----- --Oe/ScElO4SkQHdx9-- From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 19 21:00:52 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F316C1065670 for ; Sat, 19 Sep 2009 21:00:52 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id B20DE8FC08 for ; Sat, 19 Sep 2009 21:00:52 +0000 (UTC) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 19 Sep 2009 16:32:42 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.7-GA) with ESMTP id LDD83529; Sat, 19 Sep 2009 16:31:22 -0400 (EDT) Received: from 209-6-22-227.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.227]) by smtp01.lnh.mail.rcn.net with ESMTP; 19 Sep 2009 16:31:22 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19125.16281.481644.877279@jerusalem.litteratus.org> Date: Sat, 19 Sep 2009 16:31:21 -0400 To: Kostik Belousov In-Reply-To: <20090919201920.GI47688@deviant.kiev.zoral.com.ua> References: <25523741.post@talk.nabble.com> <20090919200643.GA70447@slackbox.xs4all.nl> <20090919201920.GI47688@deviant.kiev.zoral.com.ua> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Cc: JonathanGilpin , freebsd-amd64@freebsd.org Subject: Re: Switching to AMD64 from I386 using make world 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, 19 Sep 2009 21:00:53 -0000 Kostik Belousov writes: > > You will also have to install all your ports again as amd64 binaries. > > Not system-management 32bit applications should mostly work on > amd64. True, with due respect to "should mostly". On the other hand ... if you're installing from scratch, why not go completely native? I recently built an amd64 desktop which now has 650+ ports installed. (About 100 are X related.) As far as I know all build using amd64 binaries/libraries. Robert Huff