From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 19 06:04:42 2007 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 1BF5C16A41B; Sun, 19 Aug 2007 06:04:42 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id D7FF413C45B; Sun, 19 Aug 2007 06:04:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l7J64d29029453; Sun, 19 Aug 2007 02:04:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l7J64cr5044382; Sun, 19 Aug 2007 02:04:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 0A667241A2; Sun, 19 Aug 2007 02:04:49 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070819060450.0A667241A2@freebsd-stable.sentex.ca> Date: Sun, 19 Aug 2007 02:04:49 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 06:04:42 -0000 TB --- 2007-08-19 04:15:22 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-19 04:15:22 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2007-08-19 04:15:22 - cleaning the object tree TB --- 2007-08-19 04:16:14 - checking out the source tree TB --- 2007-08-19 04:16:14 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2007-08-19 04:16:14 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-19 04:26:18 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-19 04:26:18 - cd /src TB --- 2007-08-19 04:26:18 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2007-08-19 05:59:38 - generating LINT kernel config TB --- 2007-08-19 05:59:38 - cd /src/sys/amd64/conf TB --- 2007-08-19 05:59:38 - /usr/bin/make -B LINT TB --- 2007-08-19 05:59:38 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-19 05:59:38 - cd /src TB --- 2007-08-19 05:59:38 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Aug 19 05:59:38 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_set_rxmode': /src/sys/dev/cxgb/cxgb_main.c:1739: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_stop_locked': /src/sys/dev/cxgb/cxgb_main.c:1750: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c:1751: error: `SA_UNLOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_start_tx': /src/sys/dev/cxgb/cxgb_main.c:1934: warning: implicit declaration of function `m_sanity' /src/sys/dev/cxgb/cxgb_main.c:1934: warning: nested extern declaration of `m_sanity' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-19 06:04:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-19 06:04:49 - ERROR: failed to build lint kernel TB --- 2007-08-19 06:04:49 - tinderbox aborted TB --- 1.57 user 5.04 system 6567.17 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 20 11:08:12 2007 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 CEF3116A4E0 for ; Mon, 20 Aug 2007 11:08:12 +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 80B6013C459 for ; Mon, 20 Aug 2007 11:08:12 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7KB8Bnx087338 for ; Mon, 20 Aug 2007 11:08:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7KB8AHY087334 for freebsd-amd64@FreeBSD.org; Mon, 20 Aug 2007 11:08:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Aug 2007 11:08:10 GMT Message-Id: <200708201108.l7KB8AHY087334@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, 20 Aug 2007 11:17:00 +0000 Cc: Subject: Current problem reports assigned to you 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, 20 Aug 2007 11:08:12 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 2 problems total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/80691 amd64 amd64 kernel hangs on load o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G a amd64/96981 amd64 reproducible instant reboot by unprivileged user o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 o amd64/105514 amd64 FreeBSD/amd64 - Fails to boot on HP Pavilion dv8000 La o amd64/105531 amd64 [sata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - doe o amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on o amd64/106604 amd64 saslauthd crashes with signal 6 on FreeBSD 6.2-PREREL o amd64/106918 amd64 [re] Asus P5B with internal RealTek PCIe Ethernet gets o amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work f amd64/109584 amd64 zdump doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 o amd64/111955 amd64 [install] Install CD boot panic due to missing BIOS sm o amd64/111992 amd64 BTX failed - HP Laptop dv2315nr s gnu/112215 amd64 [patch] gcc(1): "gcc -m32" attempts to link against 64 o amd64/112677 amd64 [aac] Adaptec 4805SAS causes 6.2 (AMD64) to panic (amd f amd64/112828 amd64 Complete data loss after upgrade 6.1 -> 6.2 (Amd64) o amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c 48 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu s amd64/85273 amd64 FreeBSD (NetBSD or OpenBSD) not install on laptop Comp o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 [nve] NIC on GA-K8NF-9 motherboard is recognized, but o amd64/97489 amd64 [ata] nForce 410 ATA controller dma time out (ASUS K8N o amd64/100326 amd64 [fdc] /dev/fd0 not created after installation FreeBSD o amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi f amd64/101132 amd64 [smp] Incorrect cpu idle and usage statistics in top a o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/107858 amd64 ASRock Conroe-945G-DVI motherboard: non-working sound f amd64/108345 amd64 6.2-* GENERIC will not boot Intel PD EMT64 w/ ACPI o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot o amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported f amd64/113111 amd64 Potentially wrong instructions will be produced for EM o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [patch] -mfancy-math-387 has no effect 21 problems total. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 12:10:02 2007 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 6EA9216A420 for ; Tue, 21 Aug 2007 12:10:02 +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 356DC13C491 for ; Tue, 21 Aug 2007 12:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LCA2SV088828 for ; Tue, 21 Aug 2007 12:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LCA224088827; Tue, 21 Aug 2007 12:10:02 GMT (envelope-from gnats) Resent-Date: Tue, 21 Aug 2007 12:10:02 GMT Resent-Message-Id: <200708211210.l7LCA224088827@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, Prasanth Thampi <30may1984@gmail.com> Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A080916A469 for ; Tue, 21 Aug 2007 12:02:42 +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 69D5813C47E for ; Tue, 21 Aug 2007 12:02:42 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LC2gTc010072 for ; Tue, 21 Aug 2007 12:02:42 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id l7LC2gSR010071; Tue, 21 Aug 2007 12:02:42 GMT (envelope-from nobody) Message-Id: <200708211202.l7LC2gSR010071@www.freebsd.org> Date: Tue, 21 Aug 2007 12:02:42 GMT From: Prasanth Thampi <30may1984@gmail.com> To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Tue, 21 Aug 2007 12:19:14 +0000 Cc: Subject: amd64/115681: how to get into gui mode 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, 21 Aug 2007 12:10:02 -0000 >Number: 115681 >Category: amd64 >Synopsis: how to get into gui mode >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Aug 21 12:10:01 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Prasanth Thampi >Release: FreeBSD 6.2-RELEASE >Organization: ER&DCI IT >Environment: >Description: sir i am using an amd 4200+(AM2) computer having 1GB RAM , my chipset is nVidia 6150 /430 .Day before i had installed freebsd v 6.2 this is the first time i am installing free bsd in my system, after the installation i am not abled to get into its gui interface please mail me the way to access my desktop what is the use of the second image file given containing some packages how can i install those packages.. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 12:40:07 2007 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 3D13616A41B for ; Tue, 21 Aug 2007 12:40:07 +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 23FEF13C4A8 for ; Tue, 21 Aug 2007 12:40:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LCe6S3093267 for ; Tue, 21 Aug 2007 12:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LCe6xP093265; Tue, 21 Aug 2007 12:40:06 GMT (envelope-from gnats) Date: Tue, 21 Aug 2007 12:40:06 GMT Message-Id: <200708211240.l7LCe6xP093265@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Simun Mikecin" X-Mailman-Approved-At: Tue, 21 Aug 2007 13:30:17 +0000 Cc: Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Simun Mikecin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 12:40:07 -0000 The following reply was made to PR amd64/115581; it has been noted by GNATS. From: "Simun Mikecin" To: bug-followup@freebsd.org, brde@optusnet.com.au Cc: Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect Date: Tue, 21 Aug 2007 14:12:29 +0200 On Fri, 17 Aug 2007, Bruce Evans wrote: > It should not be used, especially on amd64 systems since basic FP > instructions are relatively fast compared with the fancy instructions > (except for sqrt). The 64-bit amd64 libm intentionally never uses the > fancy instructions (except for sqrt), partly because they are not much > faster and partly because they are much less accurate. The fancy > instructions are not used for float precision (unless you pessimize > things using -mfancy-math-387) since they are about 3 times slower > than the library versions on small args. This PR is about -mfancy-math-387 usage when compiling 32-bit compatibility libraries that are gone be used on FreeBSD/amd64. As far as I can see FreeBSD's libm on i386 uses those fancy instructions (for example /usr/src.current/lib/msun/i387/s_sin.S), so the same libm will be used for running 32-bit apps on FreeBSD/amd64. Is your statement about fancy instructions been 3 times slower also valid for FreeBSD/i386 and 32-bit apps running on FreeBSD/amd64? From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 14:37:13 2007 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 413F516A417 for ; Tue, 21 Aug 2007 14:37:13 +0000 (UTC) (envelope-from craig001@lerwick.hopto.org) Received: from lerwick.hopto.org (81-86-235-79.dsl.pipex.com [81.86.235.79]) by mx1.freebsd.org (Postfix) with SMTP id 72C5913C4B7 for ; Tue, 21 Aug 2007 14:37:12 +0000 (UTC) (envelope-from craig001@lerwick.hopto.org) Received: (qmail 47042 invoked by uid 98); 21 Aug 2007 15:10:12 +0100 Received: from 10.0.0.2 by polaris.lerwick.hopto.org (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.88.4/1789. hbedv: 7.1.1.11/6.35.1.178. f-prot: 4.6.6/3.16.14. spamassassin: 3.1.4. Clear:RC:1(10.0.0.2):. Processed in 8.454066 secs); 21 Aug 2007 14:10:12 -0000 Received: from lerwick.hopto.org (10.0.0.2) by lerwick.hopto.org with SMTP; 21 Aug 2007 15:10:03 +0100 Received: from 193.113.57.167 (SquirrelMail authenticated user lug) by lerwick.hopto.org with HTTP; Tue, 21 Aug 2007 15:10:03 +0100 (BST) Message-ID: <54696.193.113.57.167.1187705403.squirrel@lerwick.hopto.org> Date: Tue, 21 Aug 2007 15:10:03 +0100 (BST) From: craig001@lerwick.hopto.org To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: [Fwd: Re: amd64/115681: how to get into gui mode] 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, 21 Aug 2007 14:37:13 -0000 forgot to cc freebsd-amd64 :S ------------------------------- Original Message ------------------------------- Subject: Re: amd64/115681: how to get into gui mode From: craig001@lerwick.hopto.org Date: Tue, August 21, 2007 3:06 pm To: "Prasanth Thampi" <30may1984@gmail.com> Cc: freebsd-gnats-submit@freebsd.org bug_followup@freebsd.org -------------------------------------------------------------------------------- Hi Prasanth Please read the handbook, it breaks it down step by step.. I think the section you will be interested in will be found at; http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11.html I am will help you if you get stuck anywhere, just send me an email off list. -- Kind Regards Craig Butler craig001@lerwick.hopto.org ============================================================ This email has been handled by lerwick.hopto.org mail server and has been scanned by 3 virus killers and spamassassin ============================================================ From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 14:40:08 2007 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 9DC3816A419 for ; Tue, 21 Aug 2007 14:40:08 +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 8362C13C48E for ; Tue, 21 Aug 2007 14:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LEe891099559 for ; Tue, 21 Aug 2007 14:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LEe81W099555; Tue, 21 Aug 2007 14:40:08 GMT (envelope-from gnats) Date: Tue, 21 Aug 2007 14:40:08 GMT Message-Id: <200708211440.l7LEe81W099555@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: craig001@lerwick.hopto.org Cc: Subject: Re: amd64/115681: how to get into gui mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: craig001@lerwick.hopto.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 14:40:08 -0000 The following reply was made to PR amd64/115681; it has been noted by GNATS. From: craig001@lerwick.hopto.org To: "Prasanth Thampi" <30may1984@gmail.com> Cc: freebsd-gnats-submit@freebsd.org, bug_followup@freebsd.org Subject: Re: amd64/115681: how to get into gui mode Date: Tue, 21 Aug 2007 15:06:02 +0100 (BST) Hi Prasanth Please read the handbook, it breaks it down step by step.. I think the section you will be interested in will be found at; http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11.html I am will help you if you get stuck anywhere, just send me an email. -- Kind Regards Craig Butler craig001@lerwick.hopto.org ============================================================ This email has been handled by lerwick.hopto.org mail server and has been scanned by 3 virus killers and spamassassin ============================================================ From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 15:10:08 2007 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 6E1F016A47A for ; Tue, 21 Aug 2007 15:10:08 +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 5112E13C46B for ; Tue, 21 Aug 2007 15:10:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LFA8Dd000280 for ; Tue, 21 Aug 2007 15:10:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LFA8nv000277; Tue, 21 Aug 2007 15:10:08 GMT (envelope-from gnats) Date: Tue, 21 Aug 2007 15:10:08 GMT Message-Id: <200708211510.l7LFA8nv000277@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Simun Mikecin X-Mailman-Approved-At: Tue, 21 Aug 2007 16:22:40 +0000 Cc: Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Simun Mikecin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:10:08 -0000 The following reply was made to PR amd64/115581; it has been noted by GNATS. From: Simun Mikecin To: Bruce Evans Cc: bug-followup@freebsd.org Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect Date: Tue, 21 Aug 2007 07:37:41 -0700 (PDT) --- Bruce Evans wrote: > > This PR is about -mfancy-math-387 usage when compiling 32-bit compatibility > > libraries that are gone be used on FreeBSD/amd64. > > As far as I can see FreeBSD's libm on i386 uses those fancy instructions (for > > example /usr/src.current/lib/msun/i387/s_sin.S), so the same libm will be > > used for running 32-bit apps on FreeBSD/amd64. > Well, that's in asm so it is not affected by compiler flags. Compiler > flags can cause the library to be not used at all in some cases where > the library is better. I'm just wondering will it have a positive impact on performance if FreeBSD/i386 libm is changed not to use that asm code with fancy instructions (just like FreeBSD/amd64 does). Sime ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 16:16:19 2007 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 82BFC16A41A; Tue, 21 Aug 2007 16:16:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5150413C4DE; Tue, 21 Aug 2007 16:16:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LGGJem003557; Tue, 21 Aug 2007 16:16:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LGGJP5003553; Tue, 21 Aug 2007 16:16:19 GMT (envelope-from linimon) Date: Tue, 21 Aug 2007 16:16:19 GMT Message-Id: <200708211616.l7LGGJP5003553@freefall.freebsd.org> To: 30may1984@gmail.com, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Tue, 21 Aug 2007 16:22:40 +0000 Cc: Subject: Re: amd64/115681: how to get into gui mode 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, 21 Aug 2007 16:16:19 -0000 Synopsis: how to get into gui mode State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Aug 21 16:15:43 UTC 2007 State-Changed-Why: This is more a request for assistance than a problem report, so it should go onto one of the mailing lists such as freebsd-questions@. http://www.freebsd.org/cgi/query-pr.cgi?pr=115681 From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 21 17:20:09 2007 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 60E3516A417 for ; Tue, 21 Aug 2007 17:20:09 +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 4440913C46E for ; Tue, 21 Aug 2007 17:20:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7LHK8ed008566 for ; Tue, 21 Aug 2007 17:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7LHK8F9008565; Tue, 21 Aug 2007 17:20:08 GMT (envelope-from gnats) Date: Tue, 21 Aug 2007 17:20:08 GMT Message-Id: <200708211720.l7LHK8F9008565@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Bruce Evans Cc: Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Evans List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 17:20:09 -0000 The following reply was made to PR amd64/115581; it has been noted by GNATS. From: Bruce Evans To: Simun Mikecin Cc: bug-followup@freebsd.org, brde@optusnet.com.au Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect Date: Tue, 21 Aug 2007 22:47:15 +1000 (EST) On Tue, 21 Aug 2007, Simun Mikecin wrote: > On Fri, 17 Aug 2007, Bruce Evans wrote: >> It should not be used, especially on amd64 systems since basic FP >> instructions are relatively fast compared with the fancy instructions >> (except for sqrt). The 64-bit amd64 libm intentionally never uses the >> fancy instructions (except for sqrt), partly because they are not much >> faster and partly because they are much less accurate. The fancy >> instructions are not used for float precision (unless you pessimize >> things using -mfancy-math-387) since they are about 3 times slower >> than the library versions on small args. > > This PR is about -mfancy-math-387 usage when compiling 32-bit compatibility > libraries that are gone be used on FreeBSD/amd64. > As far as I can see FreeBSD's libm on i386 uses those fancy instructions (for > example /usr/src.current/lib/msun/i387/s_sin.S), so the same libm will be > used for running 32-bit apps on FreeBSD/amd64. Well, that's in asm so it is not affected by compiler flags. Compiler flags can cause the library to be not used at all in some cases where the library is better. > Is your statement about fancy instructions been 3 times slower also valid for > FreeBSD/i386 and 32-bit apps running on FreeBSD/amd64? In some cases -- not for most cases, but for float precision trig functions on small args, except possibly on very old CPUs. The i387 library intentionally doesn't use many hardware transcendental instructions in float precision since they are slower and/or very inaccurate. This includes all trig instructions. Bruce From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 00:21:17 2007 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 4271816A51F for ; Wed, 22 Aug 2007 00:21:17 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34510.mail.mud.yahoo.com (web34510.mail.mud.yahoo.com [66.163.178.176]) by mx1.freebsd.org (Postfix) with SMTP id E017E13C458 for ; Wed, 22 Aug 2007 00:21:16 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 35124 invoked by uid 60001); 21 Aug 2007 23:54:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=3wAWQfV7T8y8Ao3JqXasJRO2ih1syyX4uTMnYEWtjjTf1G2xbJwwfufUNLsbztUrxegJP58kqvTxQNbtN9MVjW+QnoiXjLCd6ZiFXxv9mWAQgpDrtVrdUedUrh/TAMCioATMoT74TkmKu6jjUN+SxYMsPND4jKfiaEDeDzr2QMs=; X-YMail-OSG: vsPNL.wVM1mt_5R8YlCIGRMvk2zvSEhPhMkeb0Y8ThYe5CyG Received: from [67.112.21.27] by web34510.mail.mud.yahoo.com via HTTP; Tue, 21 Aug 2007 16:54:36 PDT Date: Tue, 21 Aug 2007 16:54:36 -0700 (PDT) From: "N. Harrington" To: freebsd-amd64@freebsd.org, questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <835936.35104.qm@web34510.mail.mud.yahoo.com> Cc: Subject: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 00:21:17 -0000 Hello I feel stupid, but I am confused about kern.maxdsiz (or datasize via limits command) on FreeBSD amd64. I have seen many posts and suggestions to raise it to 1G. However it seems this only applies to i386. By default, on servers I have with 4G of physical memory, and 2X that of swap, I am showing a reported datasize limit of 33554432KB. far in excess of even my physical and swap combined! I have seen suggestions from mysql for maxdsize to be set to 1G. Obviously no such problem with amd64? Is this just a high number chosen to let things run wild? (basically unlimited) I have been having some problems with running squid and my servers locking up. I think, from the process exceeding my physical memory and the server getting very unhappy trying use so much swap. (since it seems the process size is so unlimited) Could anyone help shed some light on this for me? If I have a server with 4G of memory, what would be a safe /sane allowable maximum for datasize? (assuming a light networking load) Thanks! Nicole From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 00:28:33 2007 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 5966716A41B for ; Wed, 22 Aug 2007 00:28:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 41AAF13C428 for ; Wed, 22 Aug 2007 00:28:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 01EC9F1B06D; Tue, 21 Aug 2007 17:13:16 -0700 (PDT) Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id E0AE128DA6; Tue, 21 Aug 2007 17:13:15 -0700 (PDT) X-AuditID: 1180711d-a021bbb000001006-d6-46cb7f9b9f78 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay13.apple.com (Symantec Mail Security) with ESMTP id C1C7128DD7; Tue, 21 Aug 2007 17:13:15 -0700 (PDT) In-Reply-To: <835936.35104.qm@web34510.mail.mud.yahoo.com> References: <835936.35104.qm@web34510.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Tue, 21 Aug 2007 17:13:15 -0700 To: N. Harrington X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== X-Mailman-Approved-At: Wed, 22 Aug 2007 02:37:29 +0000 Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 00:28:33 -0000 On Aug 21, 2007, at 4:54 PM, N. Harrington wrote: > I have seen many posts and suggestions to raise it to 1G. However > it seems this only applies to > i386. By default, on servers I have with 4G of physical memory, and > 2X that of swap, I am showing > a reported datasize limit of 33554432KB. far in excess of even my > physical and swap combined! True...that a big part of what you gain from running in 64-bit mode-- a huge address space. > I have seen suggestions from mysql for maxdsize to be set to 1G. > Obviously no such problem with > amd64? Right. > Is this just a high number chosen to let things run wild? > (basically unlimited) I have been > having some problems with running squid and my servers locking up. > I think, from the process > exceeding my physical memory and the server getting very unhappy > trying use so much swap. (since > it seems the process size is so unlimited) You should configure squid to use no more than about 60 - 70% of the available physical RAM-- ie, set the cache_mem parameter to about 2.5 or 3GB. > Could anyone help shed some light on this for me? If I have a > server with 4G of memory, what > would be a safe /sane allowable maximum for datasize? (assuming a > light networking load) It wouldn't be unreasonable to limit datasize to 3 GB on such a machine, assuming that nothing you run will ever need to grow larger... -- -Chuck From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 10:00:08 2007 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 314C516A417 for ; Wed, 22 Aug 2007 10:00:08 +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 1770913C46A for ; Wed, 22 Aug 2007 10:00:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7MA07sF068115 for ; Wed, 22 Aug 2007 10:00:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7MA079d068108; Wed, 22 Aug 2007 10:00:07 GMT (envelope-from gnats) Date: Wed, 22 Aug 2007 10:00:07 GMT Message-Id: <200708221000.l7MA079d068108@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Bruce Evans Cc: Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Evans List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 10:00:08 -0000 The following reply was made to PR amd64/115581; it has been noted by GNATS. From: Bruce Evans To: Simun Mikecin Cc: Bruce Evans , bug-followup@FreeBSD.org Subject: Re: amd64/115581: [patch] -mfancy-math-387 has no effect Date: Wed, 22 Aug 2007 19:50:17 +1000 (EST) On Tue, 21 Aug 2007, Simun Mikecin wrote: > --- Bruce Evans wrote: >>> This PR is about -mfancy-math-387 usage when compiling 32-bit compatibility >>> libraries that are gone be used on FreeBSD/amd64. >>> As far as I can see FreeBSD's libm on i386 uses those fancy instructions (for >>> example /usr/src.current/lib/msun/i387/s_sin.S), so the same libm will be >>> used for running 32-bit apps on FreeBSD/amd64. >> Well, that's in asm so it is not affected by compiler flags. Compiler >> flags can cause the library to be not used at all in some cases where >> the library is better. > > I'm just wondering will it have a positive impact on performance if FreeBSD/i386 libm is changed > not to use that asm code with fancy instructions (just like FreeBSD/amd64 does). Maybe someday. The easy cases have already been looked at and resulted in removing the asm implementations of functions like sinf() and asin(). Bruce From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 10:53:40 2007 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 18E6C16A494 for ; Wed, 22 Aug 2007 10:53:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id B89D113C457 for ; Wed, 22 Aug 2007 10:53:39 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id DE4D920B0; Wed, 22 Aug 2007 12:53:34 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 516B6208A; Wed, 22 Aug 2007 12:53:34 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 3315A84479; Wed, 22 Aug 2007 12:53:34 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Chuck Swiger References: <835936.35104.qm@web34510.mail.mud.yahoo.com> Date: Wed, 22 Aug 2007 12:53:34 +0200 In-Reply-To: (Chuck Swiger's message of "Tue\, 21 Aug 2007 17\:13\:15 -0700") Message-ID: <86r6lvalht.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 10:53:40 -0000 Chuck Swiger writes: > You should configure squid to use no more than about 60 - 70% of the > available physical RAM-- ie, set the cache_mem parameter to about 2.5 > or 3GB. Better yet, don't run Squid at all. It was designed for a computer architecture that was already obsolete when Squid was first written. > It wouldn't be unreasonable to limit datasize to 3 GB on such a > machine, assuming that nothing you run will ever need to grow > larger... ...actually, maxdsiz is meaningless in FreeBSD 7, because the new allocator uses mmap(2) instead of brk(2) / sbrk(2), so malloc() counts towards the resident set size (ulimit -m), not the data segment size (ulimit -d). (unless, of course, your application has its own allocator, in which case you can kiss performance goodbye) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 11:26:02 2007 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 98E2016A418; Wed, 22 Aug 2007 11:26:02 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 4687413C494; Wed, 22 Aug 2007 11:26:02 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INnvS-000NHI-Sa; Wed, 22 Aug 2007 19:59:03 +0900 Message-ID: <46CC16F6.7020904@micom.mng.net> Date: Wed, 22 Aug 2007 18:59:02 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> In-Reply-To: <86r6lvalht.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Chuck Swiger , questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 11:26:02 -0000 Dag-Erling Smørgrav wrote: > Chuck Swiger writes: > >> You should configure squid to use no more than about 60 - 70% of the >> available physical RAM-- ie, set the cache_mem parameter to about 2.5 >> or 3GB. >> > > Better yet, don't run Squid at all. Ok, then what do you recommend instead of Squid? thanks, Ganbold > It was designed for a computer > architecture that was already obsolete when Squid was first written. > > >> It wouldn't be unreasonable to limit datasize to 3 GB on such a >> machine, assuming that nothing you run will ever need to grow >> larger... >> > > ..actually, maxdsiz is meaningless in FreeBSD 7, because the new > allocator uses mmap(2) instead of brk(2) / sbrk(2), so malloc() counts > towards the resident set size (ulimit -m), not the data segment size > (ulimit -d). > > (unless, of course, your application has its own allocator, in which > case you can kiss performance goodbye) > > DES > -- Heuristics are bug ridden by definition. If they didn't have bugs, then they'd be algorithms. From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 11:57:30 2007 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 B484C16A418 for ; Wed, 22 Aug 2007 11:57:30 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.freebsd.org (Postfix) with ESMTP id 6D7F513C458 for ; Wed, 22 Aug 2007 11:57:30 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so136471wxd for ; Wed, 22 Aug 2007 04:57:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mU7Fr71bcKEnG5WP/sI01b9PJouNQTy0nTiMfBR2AugbhSKvkgPmvB0ysCjc+BvLI8soNbuHPTXkz/mInuUD/Dd5kvomyDqgkugHwp+wRnc/qRL6589qw4DvbUNOkwkf27tz30Ar70II+2tU9QRNKP4vKzA+K01Mcgm86RD9E/M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=o/mM6U4PJEdWHUL1HyzqfcGIO1IscJMVxI9DkkL0yuma1G+gSB3sEtDNftvss/5xyV5WsPYNgrksBz58N5lz9vEXR1KSQ5Lyj2QtwHYhqdLFYDYDW9Rszc/EXu9aoU1jiEQtaR0eH1pwEmcjVuDWwDt9roTACBo3IoEHbM8sFw8= Received: by 10.70.7.13 with SMTP id 13mr963596wxg.1187782325597; Wed, 22 Aug 2007 04:32:05 -0700 (PDT) Received: by 10.70.109.20 with HTTP; Wed, 22 Aug 2007 04:32:05 -0700 (PDT) Message-ID: Date: Wed, 22 Aug 2007 13:32:05 +0200 From: "Claus Guttesen" To: Ganbold In-Reply-To: <46CC16F6.7020904@micom.mng.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Chuck Swiger , questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 11:57:30 -0000 > >> You should configure squid to use no more than about 60 - 70% of the > >> available physical RAM-- ie, set the cache_mem parameter to about 2.5 > >> or 3GB. > >> > > > > Better yet, don't run Squid at all. > > Ok, then what do you recommend instead of Squid? Varnish. http://varnish.projects.linpro.no/ -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 12:04:41 2007 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 02D1216A475; Wed, 22 Aug 2007 12:04:41 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id ADC5E13C461; Wed, 22 Aug 2007 12:04:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 4539420B3; Wed, 22 Aug 2007 14:04:36 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 27A92208A; Wed, 22 Aug 2007 14:04:36 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 0B57384479; Wed, 22 Aug 2007 14:04:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ganbold References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> Date: Wed, 22 Aug 2007 14:04:35 +0200 In-Reply-To: <46CC16F6.7020904@micom.mng.net> (ganbold@micom.mng.net's message of "Wed\, 22 Aug 2007 18\:59\:02 +0800") Message-ID: <86ejhvai7g.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Chuck Swiger , questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 12:04:41 -0000 Ganbold writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Better yet, don't run Squid at all. > Ok, then what do you recommend instead of Squid? That depends on what you use it for... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 13:40:10 2007 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 3C95616A41A; Wed, 22 Aug 2007 13:40:09 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E6A4B13C465; Wed, 22 Aug 2007 13:40:08 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id EE2D820B0; Wed, 22 Aug 2007 15:40:03 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D0EF3208A; Wed, 22 Aug 2007 15:40:03 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id A7B9684447; Wed, 22 Aug 2007 15:40:03 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Alexandre Biancalana" References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> <86ejhvai7g.fsf@ds4.des.no> <8e10486b0708220627t5d7bc3d9v1104a4e3cbfcd6cd@mail.gmail.com> Date: Wed, 22 Aug 2007 15:40:03 +0200 In-Reply-To: <8e10486b0708220627t5d7bc3d9v1104a4e3cbfcd6cd@mail.gmail.com> (Alexandre Biancalana's message of "Wed\, 22 Aug 2007 10\:27\:04 -0300") Message-ID: <86odgz8z7w.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 13:40:10 -0000 "Alexandre Biancalana" writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Ganbold writes: > > > Ok, then what do you recommend instead of Squid? > > That depends on what you use it for... > What the options for forward proxy/cache with user authentication and > access control ? I'm not really into forward proxies, but there are a few (mod_proxy, privoxy, wwwoffle). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 13:54:17 2007 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 3D2D916A418 for ; Wed, 22 Aug 2007 13:54:17 +0000 (UTC) (envelope-from biancalana@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id E626413C457 for ; Wed, 22 Aug 2007 13:54:16 +0000 (UTC) (envelope-from biancalana@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so159263wxd for ; Wed, 22 Aug 2007 06:54:16 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=JrlE+AUysU41kMgQkbirJNnVAOiMH5n7/YfapG8ovP5WzTTo1Cv3nI4IZfNdGUP4mpGV/Eg1uzDwDv1gDTP1R4HBx8NaapiF+vqI6lQK1LEt3kNWpyWw8SnPur4hoTbCd8FBqJRvIMBfQwmz6Lq8GEn+ImXmqRiW97RZAPeP0vY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=NSteISrIUqfXYa0e6+zhbh4MORXvMgx+zFDpHu5IWgr15SUnXxZoG79CT3H+tTyt6QXZ3RRT/lhWEB4c10b9GXswu9M22Tqkbx8UGCh5q7xje8lA0bXMzlLXO3uslvrSV3gxsknm+l8PZF2nOSgNHJ6hBD+tVamgnaRcDFadsiw= Received: by 10.90.113.18 with SMTP id l18mr1883206agc.1187789224293; Wed, 22 Aug 2007 06:27:04 -0700 (PDT) Received: by 10.100.92.13 with HTTP; Wed, 22 Aug 2007 06:27:04 -0700 (PDT) Message-ID: <8e10486b0708220627t5d7bc3d9v1104a4e3cbfcd6cd@mail.gmail.com> Date: Wed, 22 Aug 2007 10:27:04 -0300 From: "Alexandre Biancalana" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86ejhvai7g.fsf@ds4.des.no> MIME-Version: 1.0 References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> <86ejhvai7g.fsf@ds4.des.no> X-Mailman-Approved-At: Wed, 22 Aug 2007 14:23:28 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 13:54:17 -0000 On 8/22/07, Dag-Erling Sm=F8rgrav wrote: > > Ganbold writes: > > Dag-Erling Sm=F8rgrav writes: > > > Better yet, don't run Squid at all. > > Ok, then what do you recommend instead of Squid? > > That depends on what you use it for... What the options for forward proxy/cache with user authentication and acces= s control ? From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 14:27:49 2007 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 7D6E916A468 for ; Wed, 22 Aug 2007 14:27:49 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id F274D13C483 for ; Wed, 22 Aug 2007 14:27:48 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7MERjfX007018; Wed, 22 Aug 2007 11:27:45 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org, freebsd-amd64@freebsd.org Date: Wed, 22 Aug 2007 11:27:41 -0300 User-Agent: KMail/1.9.7 References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <46CC16F6.7020904@micom.mng.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708221127.42627.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Chuck Swiger , questions@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 14:27:49 -0000 On Wednesday 22 August 2007 08:32:05 Claus Guttesen wrote: > > >> You should configure squid to use no more than about 60 - 70% of the > > >> available physical RAM-- ie, set the cache_mem parameter to about 2.5 > > >> or 3GB. > > > > > > Better yet, don't run Squid at all. > > > > Ok, then what do you recommend instead of Squid? > > Varnish. > > http://varnish.projects.linpro.no/ that certainly is a really hotty for caching :) =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 14:38:13 2007 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 256BD16A480; Wed, 22 Aug 2007 14:38:13 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8934513C4CA; Wed, 22 Aug 2007 14:38:09 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7MEc99a007989; Wed, 22 Aug 2007 11:38:09 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Wed, 22 Aug 2007 11:38:06 -0300 User-Agent: KMail/1.9.7 References: <835936.35104.qm@web34510.mail.mud.yahoo.com> In-Reply-To: <835936.35104.qm@web34510.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708221138.07278.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: questions@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 14:38:13 -0000 On Tuesday 21 August 2007 20:54:36 N. Harrington wrote: > Hello > I feel stupid, but I am confused about kern.maxdsiz (or datasize via > limits command) on FreeBSD amd64. > > I have seen many posts and suggestions to raise it to 1G. However it see= ms > this only applies to i386. By default, on servers I have with 4G of > physical memory, and 2X that of swap, I am showing a reported datasize > limit of 33554432KB. far in excess of even my physical and swap combined!= I > have seen suggestions from mysql for maxdsize to be set to 1G. Obviously = no > such problem with amd64? on amd64 when maxdsiz not set it stops at 512 limit but soon you set it to = 1G =20 it appearently is able to use more this is not the case on i386 - but I=20 would say don't worry about it on i386 your machine could hang at boot when setting maxdsiz higher than=20 installed physical memory but that never happened to me with amd64 I have some server running squid for caching perfect with 4, 8 and 16G of R= AM=20 I set maxdsiz do 3G on machines with 4Gigs of RAM but I do not run anything= =20 else so then I adjust cache_mem with maximum_object_size_in_memory to use t= he=20 most possible amount of memory without doing swap.=20 anyway you set it in boot.loader there is no need to compile something into= =20 the kernel =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 22 16:48:52 2007 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 C96CA16A418; Wed, 22 Aug 2007 16:48:52 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id AB1E713C465; Wed, 22 Aug 2007 16:48:52 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out4.apple.com (Postfix) with ESMTP id 9EED7F89E9B; Wed, 22 Aug 2007 09:48:52 -0700 (PDT) Received: from relay12.apple.com (unknown [127.0.0.1]) by relay12.apple.com (Symantec Mail Security) with ESMTP id 87CF529027; Wed, 22 Aug 2007 09:48:52 -0700 (PDT) X-AuditID: 11807135-a5f64bb000000813-b4-46cc68f4b488 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay12.apple.com (Symantec Mail Security) with ESMTP id 78F02290A6; Wed, 22 Aug 2007 09:48:52 -0700 (PDT) In-Reply-To: <86r6lvalht.fsf@ds4.des.no> References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Chuck Swiger Date: Wed, 22 Aug 2007 09:48:51 -0700 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== X-Mailman-Approved-At: Wed, 22 Aug 2007 17:13:22 +0000 Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 22 Aug 2007 16:48:52 -0000 On Aug 22, 2007, at 3:53 AM, Dag-Erling Sm=F8rgrav wrote: > Chuck Swiger writes: >> You should configure squid to use no more than about 60 - 70% of the >> available physical RAM-- ie, set the cache_mem parameter to about 2.5 >> or 3GB. > > Better yet, don't run Squid at all. It was designed for a computer > architecture that was already obsolete when Squid was first written. This could be said of a lot of software, including many Unix =20 flavors. :-) I can think of several things to criticise about Squid-- a config =20 file which falls between Apache's httpd.conf and a sendmail.cf in =20 terms of complexity is probably close to the top of my list, but for =20 the simple purpose of saving limited network bandwidth using on-disk =20 or in-memory caching, squid does just fine. I'd be happy to look at =20 Varnish when I get a chance, though. >> It wouldn't be unreasonable to limit datasize to 3 GB on such a >> machine, assuming that nothing you run will ever need to grow >> larger... > > ...actually, maxdsiz is meaningless in FreeBSD 7, because the new > allocator uses mmap(2) instead of brk(2) / sbrk(2), so malloc() counts > towards the resident set size (ulimit -m), not the data segment size > (ulimit -d). OK. Nicole, the OP, mentioned "amd64", not "-CURRENT", but I'll keep =20= this in mind for future reference. Regards, --=20 -Chuck From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 23 01:26:22 2007 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 1C51816A419 for ; Thu, 23 Aug 2007 01:26:21 +0000 (UTC) (envelope-from peter@wemm.org) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.freebsd.org (Postfix) with ESMTP id CE65813C4B3 for ; Thu, 23 Aug 2007 01:26:21 +0000 (UTC) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 95E1119774; Wed, 22 Aug 2007 18:08:28 -0700 (PDT) From: Peter Wemm To: amd64@freebsd.org Date: Wed, 22 Aug 2007 18:08:27 -0700 User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708221808.28272.peter@wemm.org> Cc: Subject: Evil hack. Running 64 bit code in a 32 bit application. Proof-of-concept. 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, 23 Aug 2007 01:26:22 -0000 We have a problem at work. Old apps that we run on amd64 boxes. For various reasons, a recompile usually isn't an option. (don't ask) One question that keeps coming up, is "Can we somehow use large mmap areas and keep the rest unchanged?" Well, the answer is yes. On the FreeBSD/amd64 kernel, we expose both 32 bit and 64 bit %cs segment descriptors to applications. We context switch all 64 bits of registers, even on 32 bit apps. Even signals seem to be workable. (%cs is reloaded for 32 bit mode on 32 bit apps). The proof of concept code is here: http://people.freebsd.org/~peter/emm64/ It is cheap and nasty, but does a simple 64 bit operation in a 32 bit app. Most of the difficulty is convincing binutils to not have a heart attack while linking it. The second part of the puzzle is a kernel module to allow mmaping above the 4GB boundary. Then we can do an API to access the high memory data, just a glorified 64 bit memcpy to/from 32 bit space. We have a bunch of code at work that does this via socket/pipe rpc to an external 64 bit proxy process. Being able to directly mmap saves context switches and has less IPC overhead. Anyway, it is there FYI, and for your amusement. I'll be doing something more realistic with it at work over the next few days. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 23 01:33:29 2007 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 71CE516A418; Thu, 23 Aug 2007 01:33:29 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id E0CA713C45A; Thu, 23 Aug 2007 01:33:28 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IO1Zd-0001Fw-Rj; Thu, 23 Aug 2007 10:33:25 +0900 Message-ID: <46CCE3E5.9060100@micom.mng.net> Date: Thu, 23 Aug 2007 09:33:25 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> <86ejhvai7g.fsf@ds4.des.no> In-Reply-To: <86ejhvai7g.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Chuck Swiger , questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 23 Aug 2007 01:33:29 -0000 Dag-Erling Smørgrav wrote: > Ganbold writes: > >> Dag-Erling Smørgrav writes: >> >>> Better yet, don't run Squid at all. >>> >> Ok, then what do you recommend instead of Squid? >> > > That depends on what you use it for... > > DES > We are using several squid machines (6 machines, each have all others as a siblings) for transparent caching/proxying using gre tunnel and wccp2 (with Cisco router). Can varnish work in such situation? thanks, Ganbold -- A [golf] ball hitting a tree shall be deemed not to have hit the tree. Hitting a tree is simply bad luck and has no place in a scientific game. The player should estimate the distance the ball would have traveled if it had not hit the tree and play the ball from there, preferably atop a nice firm tuft of grass. -- Donald A. Metz From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 23 08:45:31 2007 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 C54F916A417; Thu, 23 Aug 2007 08:45:31 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7D45013C428; Thu, 23 Aug 2007 08:45:29 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id E7A8E20B2; Thu, 23 Aug 2007 10:45:24 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id CE73E20B1; Thu, 23 Aug 2007 10:45:24 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id B4EF784479; Thu, 23 Aug 2007 10:45:24 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ganbold References: <835936.35104.qm@web34510.mail.mud.yahoo.com> <86r6lvalht.fsf@ds4.des.no> <46CC16F6.7020904@micom.mng.net> <86ejhvai7g.fsf@ds4.des.no> <46CCE3E5.9060100@micom.mng.net> Date: Thu, 23 Aug 2007 10:45:24 +0200 In-Reply-To: <46CCE3E5.9060100@micom.mng.net> (ganbold@micom.mng.net's message of "Thu\, 23 Aug 2007 09\:33\:25 +0800") Message-ID: <864piq3ahn.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Chuck Swiger , questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 23 Aug 2007 08:45:31 -0000 Ganbold writes: > We are using several squid machines (6 machines, each have all others > as a siblings) for transparent caching/proxying using gre tunnel and > wccp2 (with Cisco router). Can varnish work in such situation? Probably not; Varnish is a reverse proxy. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 23 23:07:04 2007 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 9F53216A417 for ; Thu, 23 Aug 2007 23:07:04 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: from web34514.mail.mud.yahoo.com (web34514.mail.mud.yahoo.com [66.163.178.180]) by mx1.freebsd.org (Postfix) with SMTP id 2464713C494 for ; Thu, 23 Aug 2007 23:07:04 +0000 (UTC) (envelope-from drumslayer2@yahoo.com) Received: (qmail 60952 invoked by uid 60001); 23 Aug 2007 23:07:03 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=UVXFk7YCUugT0HWS37VHE3PcE3cp18KWoXfeUjnkQMLgHl6t6/48Esis4gdr1iFkqs/Vq0JVaHKnOUaYydoFMMXCc4fuLe5Zu5SLgPB2gWzsb35DRYy60mWPDCggPHAbjHY/N1VR46fojC++lIZXRHWkdt9MoFAQI52UswQoQBo=; X-YMail-OSG: qVmwy4QVM1lwnubXJPQpo4wPbNbZZHsQSp8I7XLyHOUE4x7uE9myV5tURPfH3i_3yAFVpA-- Received: from [67.112.21.27] by web34514.mail.mud.yahoo.com via HTTP; Thu, 23 Aug 2007 16:07:03 PDT Date: Thu, 23 Aug 2007 16:07:03 -0700 (PDT) From: "N. Harrington" To: JoaoBR , freebsd-amd64@freebsd.org In-Reply-To: <200708221138.07278.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <445153.60892.qm@web34514.mail.mud.yahoo.com> Cc: questions@freebsd.org Subject: Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply. 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, 23 Aug 2007 23:07:04 -0000 --- JoaoBR wrote: > On Tuesday 21 August 2007 20:54:36 N. Harrington wrote: > > Hello > > I feel stupid, but I am confused about kern.maxdsiz (or datasize via > > limits command) on FreeBSD amd64. > > > > > I have seen many posts and suggestions to raise it to 1G. However it seems > > this only applies to i386. By default, on servers I have with 4G of > > physical memory, and 2X that of swap, I am showing a reported datasize > > limit of 33554432KB. far in excess of even my physical and swap combined! I > > have seen suggestions from mysql for maxdsize to be set to 1G. Obviously no > > such problem with amd64? > > on amd64 when maxdsiz not set it stops at 512 limit but soon you set it to 1G > it appearently is able to use more this is not the case on i386 - but I > would say don't worry about it > > on i386 your machine could hang at boot when setting maxdsiz higher than > installed physical memory but that never happened to me with amd64 > > I have some server running squid for caching perfect with 4, 8 and 16G of RAM > > I set maxdsiz do 3G on machines with 4Gigs of RAM but I do not run anything > else so then I adjust cache_mem with maximum_object_size_in_memory to use the > most possible amount of memory without doing swap. > > anyway you set it in boot.loader there is no need to compile something into > the kernel > > -- > > João Thanks everyone. I tried setting my maxd size to 3.5G on a machine with 4gigs ram. It caused squid to seem to rop out on occasion. It seems so odd that on i366, maxd size is so small that one likely needs to set it higher to allow access to more memory. However on amd64, is such a high number that one would need to lower it to prevent accessing too much memory? Something really odd about that. I also found that I could even double the datasize / maxd size to 2X 33554432kB and it would boot and run just fine on a machine with 8 gigs of ram. How weird is that! Did amd64 just cause this setting to add 3 zero's? I can see the legacy documentation for i386 BSD and applications is going to cause some weirdness and problems if not careful. As for squid, just like Sendmail and Apache, yes there and plenty of "I do it better and I am newer", alternatives out. But some things stay old favorites for a reason. I will take a look at Varnish, but it seemed much less user friendly to me that squid and much much less feature laden. Also, I saw no way to purge individual files from storage. (something I have to have) So it's always nicer to know how to make things work with what one has or needs to use, rather than just being told to use something else. I have over 30 machines with various configurations of squid in accelerator mode and most seem to work fine. However I will say they do have a preference for running on (1) Single core cpu and SCSI hard drives. On an average server with ~300G of disk, I have over 10M objects in storage. As usual though, I am dealing with a program(squid) that seems to be, Linux first, it happens to also run on FreeBSD second. Even though it seems many people seem to be using it with FreeBSD. Squid has also been great for me to test/beatup on gjournal (which should be in 6 by now and be available standard) and zfs. Nicole The Large Print Giveth And The Small Print Taketh Away -- Anon From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 24 14:30:01 2007 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 AD81C16A418 for ; Fri, 24 Aug 2007 14:30:01 +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 8DA9D13C45B for ; Fri, 24 Aug 2007 14:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7OEU171081495 for ; Fri, 24 Aug 2007 14:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7OEU1aG081494; Fri, 24 Aug 2007 14:30:01 GMT (envelope-from gnats) Resent-Date: Fri, 24 Aug 2007 14:30:01 GMT Resent-Message-Id: <200708241430.l7OEU1aG081494@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, Rene Gollent Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9D4716A417 for ; Fri, 24 Aug 2007 14:28:18 +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 8301A13C442 for ; Fri, 24 Aug 2007 14:28:18 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l7OESIX0016131 for ; Fri, 24 Aug 2007 14:28:18 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id l7OESIl1016130; Fri, 24 Aug 2007 14:28:18 GMT (envelope-from nobody) Message-Id: <200708241428.l7OESIl1016130@www.freebsd.org> Date: Fri, 24 Aug 2007 14:28:18 GMT From: Rene Gollent To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Fri, 24 Aug 2007 19:58:11 +0000 Cc: Subject: amd64/115784: Compiling with -m32 breaks on FreeBSD/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, 24 Aug 2007 14:30:01 -0000 >Number: 115784 >Category: amd64 >Synopsis: Compiling with -m32 breaks on FreeBSD/amd64 >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 24 14:30:01 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Rene Gollent >Release: FreeBSD 7.0-CURRENT-200708 #0: Fri Aug 17 04:42:11 UTC 2007 >Organization: >Environment: FreeBSD leviathan.boldlygoingnowhere.org 7.0-CURRENT-200708 FreeBSD 7.0-CURRENT-200708 #0: Fri Aug 17 04:42:11 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: If you attempt to compile with gcc -m32 on the above platform, the following issues occur: 1) if you #include , compilation fails with the following errors: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter If not including new or another problem header, linking fails: /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc >How-To-Repeat: Attempt to compile the following code: #include int main(int, char **) { char *blah = new char[5]; return 0; } >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 24 22:24:35 2007 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 7286116A417; Fri, 24 Aug 2007 22:24:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 33BC613C428; Fri, 24 Aug 2007 22:24:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l7OMOYbL023234; Fri, 24 Aug 2007 18:24:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l7OMOYik089972; Fri, 24 Aug 2007 18:24:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 6D02A241A2; Fri, 24 Aug 2007 18:24:39 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070824222439.6D02A241A2@freebsd-stable.sentex.ca> Date: Fri, 24 Aug 2007 18:24:39 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 22:24:35 -0000 TB --- 2007-08-24 20:32:50 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-24 20:32:50 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2007-08-24 20:32:50 - cleaning the object tree TB --- 2007-08-24 20:33:30 - checking out the source tree TB --- 2007-08-24 20:33:30 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2007-08-24 20:33:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-24 20:43:48 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-24 20:43:48 - cd /src TB --- 2007-08-24 20:43:48 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2007-08-24 22:18:05 - generating LINT kernel config TB --- 2007-08-24 22:18:05 - cd /src/sys/amd64/conf TB --- 2007-08-24 22:18:05 - /usr/bin/make -B LINT TB --- 2007-08-24 22:18:05 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-24 22:18:05 - cd /src TB --- 2007-08-24 22:18:05 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Aug 24 22:18:05 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/mcd/mcd_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/md/md.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mem/memdev.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mfi/mfi.c /src/sys/dev/mfi/mfi.c: In function `mfi_ldprobe': /src/sys/dev/mfi/mfi.c:877: error: `SA_XLOCKED' undeclared (first use in this function) /src/sys/dev/mfi/mfi.c:877: error: (Each undeclared identifier is reported only once /src/sys/dev/mfi/mfi.c:877: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-24 22:24:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-24 22:24:39 - ERROR: failed to build lint kernel TB --- 2007-08-24 22:24:39 - tinderbox aborted TB --- 1.61 user 4.85 system 6708.82 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Sat Aug 25 16:40:01 2007 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 A4C9616A468 for ; Sat, 25 Aug 2007 16:40:01 +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 7AB6713C461 for ; Sat, 25 Aug 2007 16:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7PGe1Gk075273 for ; Sat, 25 Aug 2007 16:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7PGe17v075272; Sat, 25 Aug 2007 16:40:01 GMT (envelope-from gnats) Resent-Date: Sat, 25 Aug 2007 16:40:01 GMT Resent-Message-Id: <200708251640.l7PGe17v075272@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, Alain Zwingelstein Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD47516A417 for ; Sat, 25 Aug 2007 16:36:33 +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 8E28413C480 for ; Sat, 25 Aug 2007 16:36:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l7PGaXiR074245 for ; Sat, 25 Aug 2007 16:36:33 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id l7PGaXdZ074244; Sat, 25 Aug 2007 16:36:33 GMT (envelope-from nobody) Message-Id: <200708251636.l7PGaXdZ074244@www.freebsd.org> Date: Sat, 25 Aug 2007 16:36:33 GMT From: Alain Zwingelstein To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Sat, 25 Aug 2007 17:04:06 +0000 Cc: Subject: amd64/115815: Gigabyte GA-M61P-S3 Motherboard unsupported SATA 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, 25 Aug 2007 16:40:01 -0000 >Number: 115815 >Category: amd64 >Synopsis: Gigabyte GA-M61P-S3 Motherboard unsupported SATA >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Aug 25 16:40:00 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Alain Zwingelstein >Release: FreeBSD 6.4 amd64 >Organization: private >Environment: >Description: no recognition of SATA hard Drives, neither in RAID mode not as single drives. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Aug 25 22:11:17 2007 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 0DA8516A41A; Sat, 25 Aug 2007 22:11:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D6EFB13C45B; Sat, 25 Aug 2007 22:11:16 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7PMBGdS092597; Sat, 25 Aug 2007 22:11:16 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7PMBGWv092593; Sat, 25 Aug 2007 22:11:16 GMT (envelope-from linimon) Date: Sat, 25 Aug 2007 22:11:16 GMT Message-Id: <200708252211.l7PMBGWv092593@freefall.freebsd.org> To: alain@zwingelstein.org, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Sat, 25 Aug 2007 22:46:38 +0000 Cc: Subject: Re: amd64/115815: [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SATA 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, 25 Aug 2007 22:11:17 -0000 Synopsis: [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SATA State-Changed-From-To: open->suspended State-Changed-By: linimon State-Changed-When: Sat Aug 25 22:10:56 UTC 2007 State-Changed-Why: Suspended awaiting someone to take an interest in doing this. http://www.freebsd.org/cgi/query-pr.cgi?pr=115815 From owner-freebsd-amd64@FreeBSD.ORG Sat Aug 25 23:33:00 2007 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 BEF7216A419 for ; Sat, 25 Aug 2007 23:33:00 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4960513C442 for ; Sat, 25 Aug 2007 23:33:00 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7PNX20A021404; Sat, 25 Aug 2007 20:33:02 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Sat, 25 Aug 2007 20:32:58 -0300 User-Agent: KMail/1.9.7 References: <200708252211.l7PMBGWv092593@freefall.freebsd.org> In-Reply-To: <200708252211.l7PMBGWv092593@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708252032.59679.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: alain@zwingelstein.org, linimon@freebsd.org Subject: Re: amd64/115815: [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SATA 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, 25 Aug 2007 23:33:00 -0000 On Saturday 25 August 2007 19:11:16 linimon@freebsd.org wrote: > Synopsis: [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SA= TA > > State-Changed-From-To: open->suspended > State-Changed-By: linimon > State-Changed-When: Sat Aug 25 22:10:56 UTC 2007 > State-Changed-Why: > Suspended awaiting someone to take an interest in doing this. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D115815 > _______________________________________________ well ... I believe that this patch could resolve your issue http://suporte.matik.com.br/arquivos/nvidia-mcp61.tar.gz =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br