From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 11 12:20:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2E3916A4CE; Sun, 11 Apr 2004 12:20:13 -0700 (PDT) Received: from madison.lisco.com (madison.lisco.com [69.18.32.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id E267A43D2F; Sun, 11 Apr 2004 12:20:12 -0700 (PDT) (envelope-from freebsd@thebeatbox.org) Received: from rw (69-18-60-38.lisco.net [69.18.60.38]) by madison.lisco.com (8.11.6/8.11.2) with ESMTP id i3BJK7J00333; Sun, 11 Apr 2004 14:20:11 -0500 (CDT) From: "Roland Wells" To: "'Jeffrey Racine'" , , Date: Sun, 11 Apr 2004 14:20:01 -0500 Message-ID: <024f01c41ffa$029327e0$0c03a8c0@internal.thebeatbox.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <1081635706.67575.26.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: RE: LAM MPI on dual processor opteron box sees only one cpu... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2004 19:20:14 -0000 Jeffrey, I am not familiar with the LAM MPI issue, but in a dual proc box, you should also get an additional line towards the bottom in your dmesg, similar to: SMP: AP CPU #1 Launched! -Roland -----Original Message----- From: owner-freebsd-cluster@freebsd.org [mailto:owner-freebsd-cluster@freebsd.org] On Behalf Of Jeffrey Racine Sent: Saturday, April 10, 2004 5:22 PM To: freebsd-amd64@freebsd.org; freebsd-cluster@freebsd.org Subject: LAM MPI on dual processor opteron box sees only one cpu... Hi. I am converging on getting a new dual opteron box running. Now I am setting up and testing LAM MPI, however, the OS is not farming out=20 the job as expected, and only sees one processor.=20 This runs fine on RH 7.3 and RH 9.0 both on a cluster and on a dual processor PIV desktop. I am running 5-current. Basically, mpirun -np 1 binaryfile has the same runtime as mpirun -np 2 binaryfile, while on the dual PIV box it runs in half the time. When I check top, mpirun -np 2 both run on CPU 0... here is the relevant portion from top with -np 2... 9306 jracine 4 0 7188K 2448K sbwait 0 0:03 19.53% 19.53% n_lam 29307 jracine 119 0 7148K 2372K CPU0 0 0:03 19.53% 19.53% n_lam I include output from laminfo, dmesg (cpu relevnt info), and lamboot -d bhost.lam... any suggestions most appreciated, and thanks in advance! -- laminfo LAM/MPI: 7.0.4 Prefix: /usr/local Architecture: amd64-unknown-freebsd5.2 Configured by: root Configured on: Sat Apr 10 11:22:02 EDT 2004 Configure host: jracine.maxwell.syr.edu C bindings: yes C++ bindings: yes Fortran bindings: yes C profiling: yes C++ profiling: yes Fortran profiling: yes ROMIO support: yes IMPI support: no Debug support: no Purify clean: no SSI boot: globus (Module v0.5) SSI boot: rsh (Module v1.0) SSI coll: lam_basic (Module v7.0) SSI coll: smp (Module v1.0) SSI rpi: crtcp (Module v1.0.1) SSI rpi: lamd (Module v7.0) SSI rpi: sysv (Module v7.0) SSI rpi: tcp (Module v7.0) SSI rpi: usysv (Module v7.0) -- dmesg sees two cpus... CPU: AMD Opteron(tm) Processor 248 (2205.02-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf58 Stepping =3D 8 Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 3623813120 (3455 MB) avail memory =3D 3494363136 (3332 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 -- bhost has the requisite information 128.230.130.10 cpu=3D2 user=3Djracine -- Here are the results from lamboot -d bhost.lam -bash-2.05b$ lamboot -d ~/bhost.lam n0<29283> ssi:boot: Opening n0<29283> ssi:boot: opening module globus n0<29283> ssi:boot: initializing module globus n0<29283> ssi:boot:globus: globus-job-run not found, globus boot will not run n0<29283> ssi:boot: module not available: globus n0<29283> ssi:boot: opening module rsh n0<29283> ssi:boot: initializing module rsh n0<29283> ssi:boot:rsh: module initializing n0<29283> ssi:boot:rsh:agent: rsh n0<29283> ssi:boot:rsh:username: n0<29283> ssi:boot:rsh:verbose: 1000 n0<29283> ssi:boot:rsh:algorithm: linear n0<29283> ssi:boot:rsh:priority: 10 n0<29283> ssi:boot: module available: rsh, priority: 10 n0<29283> ssi:boot: finalizing module globus n0<29283> ssi:boot:globus: finalizing n0<29283> ssi:boot: closing module globus n0<29283> ssi:boot: Selected boot module rsh =20 LAM 7.0.4/MPI 2 C++/ROMIO - Indiana University =20 n0<29283> ssi:boot:base: looking for boot schema in following directories: n0<29283> ssi:boot:base: n0<29283> ssi:boot:base: $TROLLIUSHOME/etc n0<29283> ssi:boot:base: $LAMHOME/etc n0<29283> ssi:boot:base: /usr/local/etc n0<29283> ssi:boot:base: looking for boot schema file: n0<29283> ssi:boot:base: /home/jracine/bhost.lam n0<29283> ssi:boot:base: found boot schema: /home/jracine/bhost.lam n0<29283> ssi:boot:rsh: found the following hosts: n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu (cpu=3D2) n0<29283> ssi:boot:rsh: resolved hosts: n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu --> 128.230.130.10 (origin)n0<29283> ssi:boot:rsh: starting RTE procs n0<29283> ssi:boot:base:linear: starting n0<29283> ssi:boot:base:server: opening server TCP socket n0<29283> ssi:boot:base:server: opened port 49832 n0<29283> ssi:boot:base:linear: booting n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting lamd on (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting on n0 (jracine.maxwell.syr.edu): hboot -t -c lam-conf.lamd -d -I -H 128.230.130.10 -P 49832 -n 0 -o 0 n0<29283> ssi:boot:rsh: launching locally hboot: performing tkill hboot: tkill -d tkill: setting prefix to (null) tkill: setting suffix to (null) tkill: got killname back: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile tkill: removing socket file ... tkill: socket file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-kernel-socketd tkill: removing IO daemon socket file ... tkill: IO daemon socket file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-io-socket tkill: f_kill =3D = "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" tkill: nothing to kill: "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" hboot: booting... hboot: fork /usr/local/bin/lamd [1] 29286 lamd -H 128.230.130.10 -P 49832 -n 0 -o 0 -d n0<29283> ssi:boot:rsh: successfully launched on n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:base:server: expecting connection from finite list hboot: attempting to execute n-1<29286> ssi:boot: Opening n-1<29286> ssi:boot: opening module globus n-1<29286> ssi:boot: initializing module globus n-1<29286> ssi:boot:globus: globus-job-run not found, globus boot will not run n-1<29286> ssi:boot: module not available: globus n-1<29286> ssi:boot: opening module rsh n-1<29286> ssi:boot: initializing module rsh n-1<29286> ssi:boot:rsh: module initializing n-1<29286> ssi:boot:rsh:agent: rsh n-1<29286> ssi:boot:rsh:username: n-1<29286> ssi:boot:rsh:verbose: 1000 n-1<29286> ssi:boot:rsh:algorithm: linear n-1<29286> ssi:boot:rsh:priority: 10 n-1<29286> ssi:boot: module available: rsh, priority: 10 n-1<29286> ssi:boot: finalizing module globus n-1<29286> ssi:boot:globus: finalizing n-1<29286> ssi:boot: closing module globus n-1<29286> ssi:boot: Selected boot module rsh n0<29283> ssi:boot:base:server: got connection from 128.230.130.10 n0<29283> ssi:boot:base:server: this connection is expected (n0) n0<29283> ssi:boot:base:server: remote lamd is at 128.230.130.10:50206 n0<29283> ssi:boot:base:server: closing server socket n0<29283> ssi:boot:base:server: connecting to lamd at 128.230.130.10:49833 n0<29283> ssi:boot:base:server: connected n0<29283> ssi:boot:base:server: sending number of links (1) n0<29283> ssi:boot:base:server: sending info: n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:base:server: finished sending n0<29283> ssi:boot:base:server: disconnected from 128.230.130.10:49833 n0<29283> ssi:boot:base:linear: finished n0<29283> ssi:boot:rsh: all RTE procs started n0<29283> ssi:boot:rsh: finalizing n0<29283> ssi:boot: Closing n-1<29286> ssi:boot:rsh: finalizing n-1<29286> ssi:boot: Closing _______________________________________________ freebsd-cluster@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-cluster To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 12 06:04:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36F9216A4CE; Mon, 12 Apr 2004 06:04:31 -0700 (PDT) Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9405243D53; Mon, 12 Apr 2004 06:04:30 -0700 (PDT) (envelope-from jracine@maxwell.syr.edu) Received: from [24.59.145.52] (syr-24-59-145-52.twcny.rr.com [24.59.145.52]) i3CD4Rdd013237; Mon, 12 Apr 2004 09:04:27 -0400 (EDT) From: Jeffrey Racine To: Roland Wells In-Reply-To: <024f01c41ffa$029327e0$0c03a8c0@internal.thebeatbox.org> References: <024f01c41ffa$029327e0$0c03a8c0@internal.thebeatbox.org> Content-Type: text/plain Organization: Syracuse University Message-Id: <1081775064.990.13.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.6.2FreeBSD GNOME Team Port Date: Mon, 12 Apr 2004 09:04:24 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: freebsd-cluster@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: LAM MPI on dual processor opteron box sees only one cpu... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2004 13:04:31 -0000 Hi Roland. I do get CPU #1 launched. This is not the problem. The problem appears to be with the way that current is scheduling. With mpirun np 2 I get the job running on CPU 0 (two instances on one proc). However, it turns out that with np 4 I get the job running on CPU 0 and 1 though with 4 instances (and associated overhead). Here is top for np 4... notice that in the C column it is using both procs. PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 96090 jracine 131 0 7148K 2172K CPU1 1 0:19 44.53% 44.53% n_lam 96088 jracine 125 0 7148K 2172K RUN 0 0:18 43.75% 43.75% n_lam 96089 jracine 136 0 7148K 2172K RUN 1 0:19 42.19% 42.19% n_lam 96087 jracine 135 0 7188K 2248K RUN 0 0:19 41.41% 41.41% n_lam One run (once when I rebooted lam) did allocate the job correctly with np 2, but this is not in general the case. On other systems I use, however, they correctly farm out np 2 to CPU 0 and 1... Thanks, and any suggestions welcome. -- Jeff On Sun, 2004-04-11 at 14:20 -0500, Roland Wells wrote: > Jeffrey, > I am not familiar with the LAM MPI issue, but in a dual proc box, you > should also get an additional line towards the bottom in your dmesg, > similar to: > > SMP: AP CPU #1 Launched! > > -Roland > -----Original Message----- > From: owner-freebsd-cluster@freebsd.org > [mailto:owner-freebsd-cluster@freebsd.org] On Behalf Of Jeffrey Racine > Sent: Saturday, April 10, 2004 5:22 PM > To: freebsd-amd64@freebsd.org; freebsd-cluster@freebsd.org > Subject: LAM MPI on dual processor opteron box sees only one cpu... > > > Hi. > > I am converging on getting a new dual opteron box running. Now I am > setting up and testing LAM MPI, however, the OS is not farming out > the job as expected, and only sees one processor. > > This runs fine on RH 7.3 and RH 9.0 both on a cluster and on a dual > processor PIV desktop. I am running 5-current. Basically, mpirun -np 1 > binaryfile has the same runtime as mpirun -np 2 binaryfile, while on the > dual PIV box it runs in half the time. When I check top, mpirun -np 2 > both run on CPU 0... here is the relevant portion from top with -np 2... > > 9306 jracine 4 0 7188K 2448K sbwait 0 0:03 19.53% 19.53% n_lam > 29307 jracine 119 0 7148K 2372K CPU0 0 0:03 19.53% 19.53% > n_lam > > I include output from laminfo, dmesg (cpu relevnt info), and lamboot -d > bhost.lam... any suggestions most appreciated, and thanks in advance! > > -- laminfo > > LAM/MPI: 7.0.4 > Prefix: /usr/local > Architecture: amd64-unknown-freebsd5.2 > Configured by: root > Configured on: Sat Apr 10 11:22:02 EDT 2004 > Configure host: jracine.maxwell.syr.edu > C bindings: yes > C++ bindings: yes > Fortran bindings: yes > C profiling: yes > C++ profiling: yes > Fortran profiling: yes > ROMIO support: yes > IMPI support: no > Debug support: no > Purify clean: no > SSI boot: globus (Module v0.5) > SSI boot: rsh (Module v1.0) > SSI coll: lam_basic (Module v7.0) > SSI coll: smp (Module v1.0) > SSI rpi: crtcp (Module v1.0.1) > SSI rpi: lamd (Module v7.0) > SSI rpi: sysv (Module v7.0) > SSI rpi: tcp (Module v7.0) > SSI rpi: usysv (Module v7.0) > > -- dmesg sees two cpus... > > CPU: AMD Opteron(tm) Processor 248 (2205.02-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > > Features=0x78bfbff MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=0xe0500800 > real memory = 3623813120 (3455 MB) > avail memory = 3494363136 (3332 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > > -- bhost has the requisite information > > 128.230.130.10 cpu=2 user=jracine > > -- Here are the results from lamboot -d bhost.lam > > -bash-2.05b$ lamboot -d ~/bhost.lam > n0<29283> ssi:boot: Opening > n0<29283> ssi:boot: opening module globus > n0<29283> ssi:boot: initializing module globus > n0<29283> ssi:boot:globus: globus-job-run not found, globus boot will > not run n0<29283> ssi:boot: module not available: globus n0<29283> > ssi:boot: opening module rsh n0<29283> ssi:boot: initializing module rsh > n0<29283> ssi:boot:rsh: module initializing n0<29283> > ssi:boot:rsh:agent: rsh n0<29283> ssi:boot:rsh:username: > n0<29283> ssi:boot:rsh:verbose: 1000 n0<29283> ssi:boot:rsh:algorithm: > linear n0<29283> ssi:boot:rsh:priority: 10 n0<29283> ssi:boot: module > available: rsh, priority: 10 n0<29283> ssi:boot: finalizing module > globus n0<29283> ssi:boot:globus: finalizing n0<29283> ssi:boot: closing > module globus n0<29283> ssi:boot: Selected boot module rsh > > LAM 7.0.4/MPI 2 C++/ROMIO - Indiana University > > n0<29283> ssi:boot:base: looking for boot schema in following > directories: > n0<29283> ssi:boot:base: > n0<29283> ssi:boot:base: $TROLLIUSHOME/etc > n0<29283> ssi:boot:base: $LAMHOME/etc > n0<29283> ssi:boot:base: /usr/local/etc > n0<29283> ssi:boot:base: looking for boot schema file: > n0<29283> ssi:boot:base: /home/jracine/bhost.lam > n0<29283> ssi:boot:base: found boot schema: /home/jracine/bhost.lam > n0<29283> ssi:boot:rsh: found the following hosts: > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu (cpu=2) > n0<29283> ssi:boot:rsh: resolved hosts: > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu --> 128.230.130.10 > (origin)n0<29283> ssi:boot:rsh: starting RTE procs > n0<29283> ssi:boot:base:linear: starting > n0<29283> ssi:boot:base:server: opening server TCP socket n0<29283> > ssi:boot:base:server: opened port 49832 n0<29283> ssi:boot:base:linear: > booting n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting > lamd on (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting on n0 > (jracine.maxwell.syr.edu): hboot -t -c lam-conf.lamd -d -I -H > 128.230.130.10 -P 49832 -n 0 -o 0 n0<29283> ssi:boot:rsh: launching > locally > hboot: performing tkill > hboot: tkill -d > tkill: setting prefix to (null) > tkill: setting suffix to (null) > tkill: got killname > back: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile > tkill: removing socket file ... > tkill: socket > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-kernel-socketd > tkill: removing IO daemon socket file ... > tkill: IO daemon socket > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-io-socket > tkill: f_kill = "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > tkill: nothing to kill: > "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > hboot: booting... > hboot: fork /usr/local/bin/lamd > [1] 29286 lamd -H 128.230.130.10 -P 49832 -n 0 -o 0 -d n0<29283> > ssi:boot:rsh: successfully launched on n0 > (jracine.maxwell.syr.edu) > n0<29283> ssi:boot:base:server: expecting connection from finite list > hboot: attempting to execute > n-1<29286> ssi:boot: Opening > n-1<29286> ssi:boot: opening module globus > n-1<29286> ssi:boot: initializing module globus > n-1<29286> ssi:boot:globus: globus-job-run not found, globus boot will > not run n-1<29286> ssi:boot: module not available: globus n-1<29286> > ssi:boot: opening module rsh n-1<29286> ssi:boot: initializing module > rsh n-1<29286> ssi:boot:rsh: module initializing n-1<29286> > ssi:boot:rsh:agent: rsh n-1<29286> ssi:boot:rsh:username: > n-1<29286> ssi:boot:rsh:verbose: 1000 n-1<29286> ssi:boot:rsh:algorithm: > linear n-1<29286> ssi:boot:rsh:priority: 10 n-1<29286> ssi:boot: module > available: rsh, priority: 10 n-1<29286> ssi:boot: finalizing module > globus n-1<29286> ssi:boot:globus: finalizing n-1<29286> ssi:boot: > closing module globus n-1<29286> ssi:boot: Selected boot module rsh > n0<29283> ssi:boot:base:server: got connection from 128.230.130.10 > n0<29283> ssi:boot:base:server: this connection is expected (n0) > n0<29283> ssi:boot:base:server: remote lamd is at 128.230.130.10:50206 > n0<29283> ssi:boot:base:server: closing server socket n0<29283> > ssi:boot:base:server: connecting to lamd at 128.230.130.10:49833 > n0<29283> ssi:boot:base:server: connected n0<29283> > ssi:boot:base:server: sending number of links (1) n0<29283> > ssi:boot:base:server: sending info: n0 > (jracine.maxwell.syr.edu) > n0<29283> ssi:boot:base:server: finished sending > n0<29283> ssi:boot:base:server: disconnected from 128.230.130.10:49833 > n0<29283> ssi:boot:base:linear: finished n0<29283> ssi:boot:rsh: all RTE > procs started n0<29283> ssi:boot:rsh: finalizing n0<29283> ssi:boot: > Closing n-1<29286> ssi:boot:rsh: finalizing n-1<29286> ssi:boot: Closing > > > > _______________________________________________ > freebsd-cluster@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > To unsubscribe, send any mail to > "freebsd-cluster-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 12 06:13:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C48E16A4CE; Mon, 12 Apr 2004 06:13:17 -0700 (PDT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB51043D2D; Mon, 12 Apr 2004 06:13:16 -0700 (PDT) (envelope-from bob@immure.com) Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1])i3CDDFuO220884; Mon, 12 Apr 2004 09:13:15 -0400 Received: (from root@localhost) by maul.immure.com (8.12.11/8.12.11) id i3CDDFOt086742; Mon, 12 Apr 2004 08:13:15 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (luke.immure.com [10.1.132.3]) by maul.immure.com (8.12.11/8.12.3) with ESMTP id i3CDDDcX086717; Mon, 12 Apr 2004 08:13:13 -0500 (CDT) (envelope-from bob@immure.com) Received: from luke.immure.com (localhost [127.0.0.1]) by luke.immure.com (8.12.11/8.12.11) with ESMTP id i3CDDDga071341; Mon, 12 Apr 2004 08:13:13 -0500 (CDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.12.11/8.12.11/Submit) id i3CDDDZM071340; Mon, 12 Apr 2004 08:13:13 -0500 (CDT) (envelope-from bob) Date: Mon, 12 Apr 2004 08:13:13 -0500 From: Bob Willcox To: Jeffrey Racine Message-ID: <20040412131313.GA70050@luke.immure.com> References: <024f01c41ffa$029327e0$0c03a8c0@internal.thebeatbox.org> <1081775064.990.13.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1081775064.990.13.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> User-Agent: Mutt/1.5.6i X-scanner: scanned by Inflex 1.0.12.3 on maul.immure.com cc: Roland Wells cc: freebsd-amd64@freebsd.org cc: freebsd-cluster@freebsd.org Subject: Re: LAM MPI on dual processor opteron box sees only one cpu... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bob Willcox List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2004 13:13:18 -0000 On Mon, Apr 12, 2004 at 09:04:24AM -0400, Jeffrey Racine wrote: > Hi Roland. > > I do get CPU #1 launched. This is not the problem. > > The problem appears to be with the way that current is scheduling. > > With mpirun np 2 I get the job running on CPU 0 (two instances on one > proc). However, it turns out that with np 4 I get the job running on CPU > 0 and 1 though with 4 instances (and associated overhead). Here is top > for np 4... notice that in the C column it is using both procs. > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU > COMMAND > 96090 jracine 131 0 7148K 2172K CPU1 1 0:19 44.53% 44.53% > n_lam > 96088 jracine 125 0 7148K 2172K RUN 0 0:18 43.75% 43.75% > n_lam > 96089 jracine 136 0 7148K 2172K RUN 1 0:19 42.19% 42.19% > n_lam > 96087 jracine 135 0 7188K 2248K RUN 0 0:19 41.41% 41.41% > n_lam > > > One run (once when I rebooted lam) did allocate the job correctly with > np 2, but this is not in general the case. On other systems I use, > however, they correctly farm out np 2 to CPU 0 and 1... > > Thanks, and any suggestions welcome. What scheduler are you using? I've seen this behavior on my 5-current Athlon MP system when running two instances of setiathome (when running with the default SCHED_ULE scheduler). Sometimes it would run both setiathome processes on the same CPU for hours (even days) leaving one CPU essentially idle. When I switched to the SCHED_4BSD scheduler it then ran setiathome on both CPUs. Bob > > -- Jeff > > On Sun, 2004-04-11 at 14:20 -0500, Roland Wells wrote: > > Jeffrey, > > I am not familiar with the LAM MPI issue, but in a dual proc box, you > > should also get an additional line towards the bottom in your dmesg, > > similar to: > > > > SMP: AP CPU #1 Launched! > > > > -Roland > > -----Original Message----- > > From: owner-freebsd-cluster@freebsd.org > > [mailto:owner-freebsd-cluster@freebsd.org] On Behalf Of Jeffrey Racine > > Sent: Saturday, April 10, 2004 5:22 PM > > To: freebsd-amd64@freebsd.org; freebsd-cluster@freebsd.org > > Subject: LAM MPI on dual processor opteron box sees only one cpu... > > > > > > Hi. > > > > I am converging on getting a new dual opteron box running. Now I am > > setting up and testing LAM MPI, however, the OS is not farming out > > the job as expected, and only sees one processor. > > > > This runs fine on RH 7.3 and RH 9.0 both on a cluster and on a dual > > processor PIV desktop. I am running 5-current. Basically, mpirun -np 1 > > binaryfile has the same runtime as mpirun -np 2 binaryfile, while on the > > dual PIV box it runs in half the time. When I check top, mpirun -np 2 > > both run on CPU 0... here is the relevant portion from top with -np 2... > > > > 9306 jracine 4 0 7188K 2448K sbwait 0 0:03 19.53% 19.53% n_lam > > 29307 jracine 119 0 7148K 2372K CPU0 0 0:03 19.53% 19.53% > > n_lam > > > > I include output from laminfo, dmesg (cpu relevnt info), and lamboot -d > > bhost.lam... any suggestions most appreciated, and thanks in advance! > > > > -- laminfo > > > > LAM/MPI: 7.0.4 > > Prefix: /usr/local > > Architecture: amd64-unknown-freebsd5.2 > > Configured by: root > > Configured on: Sat Apr 10 11:22:02 EDT 2004 > > Configure host: jracine.maxwell.syr.edu > > C bindings: yes > > C++ bindings: yes > > Fortran bindings: yes > > C profiling: yes > > C++ profiling: yes > > Fortran profiling: yes > > ROMIO support: yes > > IMPI support: no > > Debug support: no > > Purify clean: no > > SSI boot: globus (Module v0.5) > > SSI boot: rsh (Module v1.0) > > SSI coll: lam_basic (Module v7.0) > > SSI coll: smp (Module v1.0) > > SSI rpi: crtcp (Module v1.0.1) > > SSI rpi: lamd (Module v7.0) > > SSI rpi: sysv (Module v7.0) > > SSI rpi: tcp (Module v7.0) > > SSI rpi: usysv (Module v7.0) > > > > -- dmesg sees two cpus... > > > > CPU: AMD Opteron(tm) Processor 248 (2205.02-MHz K8-class CPU) > > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > > > > Features=0x78bfbff > MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > AMD Features=0xe0500800 > > real memory = 3623813120 (3455 MB) > > avail memory = 3494363136 (3332 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > > > -- bhost has the requisite information > > > > 128.230.130.10 cpu=2 user=jracine > > > > -- Here are the results from lamboot -d bhost.lam > > > > -bash-2.05b$ lamboot -d ~/bhost.lam > > n0<29283> ssi:boot: Opening > > n0<29283> ssi:boot: opening module globus > > n0<29283> ssi:boot: initializing module globus > > n0<29283> ssi:boot:globus: globus-job-run not found, globus boot will > > not run n0<29283> ssi:boot: module not available: globus n0<29283> > > ssi:boot: opening module rsh n0<29283> ssi:boot: initializing module rsh > > n0<29283> ssi:boot:rsh: module initializing n0<29283> > > ssi:boot:rsh:agent: rsh n0<29283> ssi:boot:rsh:username: > > n0<29283> ssi:boot:rsh:verbose: 1000 n0<29283> ssi:boot:rsh:algorithm: > > linear n0<29283> ssi:boot:rsh:priority: 10 n0<29283> ssi:boot: module > > available: rsh, priority: 10 n0<29283> ssi:boot: finalizing module > > globus n0<29283> ssi:boot:globus: finalizing n0<29283> ssi:boot: closing > > module globus n0<29283> ssi:boot: Selected boot module rsh > > > > LAM 7.0.4/MPI 2 C++/ROMIO - Indiana University > > > > n0<29283> ssi:boot:base: looking for boot schema in following > > directories: > > n0<29283> ssi:boot:base: > > n0<29283> ssi:boot:base: $TROLLIUSHOME/etc > > n0<29283> ssi:boot:base: $LAMHOME/etc > > n0<29283> ssi:boot:base: /usr/local/etc > > n0<29283> ssi:boot:base: looking for boot schema file: > > n0<29283> ssi:boot:base: /home/jracine/bhost.lam > > n0<29283> ssi:boot:base: found boot schema: /home/jracine/bhost.lam > > n0<29283> ssi:boot:rsh: found the following hosts: > > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu (cpu=2) > > n0<29283> ssi:boot:rsh: resolved hosts: > > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu --> 128.230.130.10 > > (origin)n0<29283> ssi:boot:rsh: starting RTE procs > > n0<29283> ssi:boot:base:linear: starting > > n0<29283> ssi:boot:base:server: opening server TCP socket n0<29283> > > ssi:boot:base:server: opened port 49832 n0<29283> ssi:boot:base:linear: > > booting n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting > > lamd on (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting on n0 > > (jracine.maxwell.syr.edu): hboot -t -c lam-conf.lamd -d -I -H > > 128.230.130.10 -P 49832 -n 0 -o 0 n0<29283> ssi:boot:rsh: launching > > locally > > hboot: performing tkill > > hboot: tkill -d > > tkill: setting prefix to (null) > > tkill: setting suffix to (null) > > tkill: got killname > > back: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile > > tkill: removing socket file ... > > tkill: socket > > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-kernel-socketd > > tkill: removing IO daemon socket file ... > > tkill: IO daemon socket > > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-io-socket > > tkill: f_kill = "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > > tkill: nothing to kill: > > "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > > hboot: booting... > > hboot: fork /usr/local/bin/lamd > > [1] 29286 lamd -H 128.230.130.10 -P 49832 -n 0 -o 0 -d n0<29283> > > ssi:boot:rsh: successfully launched on n0 > > (jracine.maxwell.syr.edu) > > n0<29283> ssi:boot:base:server: expecting connection from finite list > > hboot: attempting to execute > > n-1<29286> ssi:boot: Opening > > n-1<29286> ssi:boot: opening module globus > > n-1<29286> ssi:boot: initializing module globus > > n-1<29286> ssi:boot:globus: globus-job-run not found, globus boot will > > not run n-1<29286> ssi:boot: module not available: globus n-1<29286> > > ssi:boot: opening module rsh n-1<29286> ssi:boot: initializing module > > rsh n-1<29286> ssi:boot:rsh: module initializing n-1<29286> > > ssi:boot:rsh:agent: rsh n-1<29286> ssi:boot:rsh:username: > > n-1<29286> ssi:boot:rsh:verbose: 1000 n-1<29286> ssi:boot:rsh:algorithm: > > linear n-1<29286> ssi:boot:rsh:priority: 10 n-1<29286> ssi:boot: module > > available: rsh, priority: 10 n-1<29286> ssi:boot: finalizing module > > globus n-1<29286> ssi:boot:globus: finalizing n-1<29286> ssi:boot: > > closing module globus n-1<29286> ssi:boot: Selected boot module rsh > > n0<29283> ssi:boot:base:server: got connection from 128.230.130.10 > > n0<29283> ssi:boot:base:server: this connection is expected (n0) > > n0<29283> ssi:boot:base:server: remote lamd is at 128.230.130.10:50206 > > n0<29283> ssi:boot:base:server: closing server socket n0<29283> > > ssi:boot:base:server: connecting to lamd at 128.230.130.10:49833 > > n0<29283> ssi:boot:base:server: connected n0<29283> > > ssi:boot:base:server: sending number of links (1) n0<29283> > > ssi:boot:base:server: sending info: n0 > > (jracine.maxwell.syr.edu) > > n0<29283> ssi:boot:base:server: finished sending > > n0<29283> ssi:boot:base:server: disconnected from 128.230.130.10:49833 > > n0<29283> ssi:boot:base:linear: finished n0<29283> ssi:boot:rsh: all RTE > > procs started n0<29283> ssi:boot:rsh: finalizing n0<29283> ssi:boot: > > Closing n-1<29286> ssi:boot:rsh: finalizing n-1<29286> ssi:boot: Closing > > > > > > > > _______________________________________________ > > freebsd-cluster@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > > To unsubscribe, send any mail to > > "freebsd-cluster-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" -- Bob Willcox What's done to children, they will do to society. bob@immure.com Austin, TX From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 12 06:37:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F72A16A4CE; Mon, 12 Apr 2004 06:37:22 -0700 (PDT) Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 039C343D58; Mon, 12 Apr 2004 06:37:22 -0700 (PDT) (envelope-from jracine@maxwell.syr.edu) Received: from exchange.maxwell.syr.edu (excluster1.maxwell.syr.edu [128.230.129.230]) by maxwell.syr.edu (8.12.10/8.9.1) with ESMTP id i3CDbKo2005159; Mon, 12 Apr 2004 09:37:20 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 12 Apr 2004 09:36:18 -0400 Message-ID: <32A8B2CB12BFC84D8D11D872C787AA9A015E9AD2@EXCHANGE.forest.maxwell.syr.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LAM MPI on dual processor opteron box sees only one cpu... Thread-Index: AcQgj+3mBKYbA9a3QJuXp89m+1xauwAAzTUM From: "Jeff Racine" To: "Bob Willcox" cc: Roland Wells cc: freebsd-amd64@freebsd.org cc: freebsd-cluster@freebsd.org Subject: RE: LAM MPI on dual processor opteron box sees only one cpu... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2004 13:37:22 -0000 Hi Bob. Good to hear someone else has seen this behavior. re: what scheduler am I using... ULE... Thanks! -- Jeff -----Original Message----- From: Bob Willcox [mailto:bob@immure.com] Sent: Mon 4/12/2004 9:13 AM To: Jeff Racine Cc: Roland Wells; freebsd-cluster@freebsd.org; freebsd-amd64@freebsd.org Subject: Re: LAM MPI on dual processor opteron box sees only one cpu... =20 On Mon, Apr 12, 2004 at 09:04:24AM -0400, Jeffrey Racine wrote: > Hi Roland. >=20 > I do get CPU #1 launched. This is not the problem. >=20 > The problem appears to be with the way that current is scheduling. >=20 > With mpirun np 2 I get the job running on CPU 0 (two instances on one > proc). However, it turns out that with np 4 I get the job running on = CPU > 0 and 1 though with 4 instances (and associated overhead). Here is top > for np 4... notice that in the C column it is using both procs. >=20 > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU > COMMAND > 96090 jracine 131 0 7148K 2172K CPU1 1 0:19 44.53% 44.53% > n_lam > 96088 jracine 125 0 7148K 2172K RUN 0 0:18 43.75% 43.75% > n_lam > 96089 jracine 136 0 7148K 2172K RUN 1 0:19 42.19% 42.19% > n_lam > 96087 jracine 135 0 7188K 2248K RUN 0 0:19 41.41% 41.41% > n_lam >=20 >=20 > One run (once when I rebooted lam) did allocate the job correctly with > np 2, but this is not in general the case. On other systems I use, > however, they correctly farm out np 2 to CPU 0 and 1... >=20 > Thanks, and any suggestions welcome. What scheduler are you using? I've seen this behavior on my 5-current Athlon MP system when running two instances of setiathome (when running with the default SCHED_ULE scheduler). Sometimes it would run both setiathome processes on the same CPU for hours (even days) leaving one CPU essentially idle. When I switched to the SCHED_4BSD scheduler it then ran setiathome on both CPUs. Bob >=20 > -- Jeff >=20 > On Sun, 2004-04-11 at 14:20 -0500, Roland Wells wrote: > > Jeffrey, > > I am not familiar with the LAM MPI issue, but in a dual proc box, = you > > should also get an additional line towards the bottom in your dmesg, > > similar to: > >=20 > > SMP: AP CPU #1 Launched! > >=20 > > -Roland > > -----Original Message----- > > From: owner-freebsd-cluster@freebsd.org > > [mailto:owner-freebsd-cluster@freebsd.org] On Behalf Of Jeffrey = Racine > > Sent: Saturday, April 10, 2004 5:22 PM > > To: freebsd-amd64@freebsd.org; freebsd-cluster@freebsd.org > > Subject: LAM MPI on dual processor opteron box sees only one cpu... > >=20 > >=20 > > Hi. > >=20 > > I am converging on getting a new dual opteron box running. Now I am > > setting up and testing LAM MPI, however, the OS is not farming out=20 > > the job as expected, and only sees one processor.=20 > >=20 > > This runs fine on RH 7.3 and RH 9.0 both on a cluster and on a dual > > processor PIV desktop. I am running 5-current. Basically, mpirun -np = 1 > > binaryfile has the same runtime as mpirun -np 2 binaryfile, while on = the > > dual PIV box it runs in half the time. When I check top, mpirun -np = 2 > > both run on CPU 0... here is the relevant portion from top with -np = 2... > >=20 > > 9306 jracine 4 0 7188K 2448K sbwait 0 0:03 19.53% 19.53% = n_lam > > 29307 jracine 119 0 7148K 2372K CPU0 0 0:03 19.53% 19.53% > > n_lam > >=20 > > I include output from laminfo, dmesg (cpu relevnt info), and lamboot = -d > > bhost.lam... any suggestions most appreciated, and thanks in = advance! > >=20 > > -- laminfo > >=20 > > LAM/MPI: 7.0.4 > > Prefix: /usr/local > > Architecture: amd64-unknown-freebsd5.2 > > Configured by: root > > Configured on: Sat Apr 10 11:22:02 EDT 2004 > > Configure host: jracine.maxwell.syr.edu > > C bindings: yes > > C++ bindings: yes > > Fortran bindings: yes > > C profiling: yes > > C++ profiling: yes > > Fortran profiling: yes > > ROMIO support: yes > > IMPI support: no > > Debug support: no > > Purify clean: no > > SSI boot: globus (Module v0.5) > > SSI boot: rsh (Module v1.0) > > SSI coll: lam_basic (Module v7.0) > > SSI coll: smp (Module v1.0) > > SSI rpi: crtcp (Module v1.0.1) > > SSI rpi: lamd (Module v7.0) > > SSI rpi: sysv (Module v7.0) > > SSI rpi: tcp (Module v7.0) > > SSI rpi: usysv (Module v7.0) > >=20 > > -- dmesg sees two cpus... > >=20 > > CPU: AMD Opteron(tm) Processor 248 (2205.02-MHz K8-class CPU) > > Origin =3D "AuthenticAMD" Id =3D 0xf58 Stepping =3D 8 > >=20 > > = Features=3D0x78bfbff > MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > AMD Features=3D0xe0500800 > > real memory =3D 3623813120 (3455 MB) > > avail memory =3D 3494363136 (3332 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > >=20 > > -- bhost has the requisite information > >=20 > > 128.230.130.10 cpu=3D2 user=3Djracine > >=20 > > -- Here are the results from lamboot -d bhost.lam > >=20 > > -bash-2.05b$ lamboot -d ~/bhost.lam > > n0<29283> ssi:boot: Opening > > n0<29283> ssi:boot: opening module globus > > n0<29283> ssi:boot: initializing module globus > > n0<29283> ssi:boot:globus: globus-job-run not found, globus boot = will > > not run n0<29283> ssi:boot: module not available: globus n0<29283> > > ssi:boot: opening module rsh n0<29283> ssi:boot: initializing module = rsh > > n0<29283> ssi:boot:rsh: module initializing n0<29283> > > ssi:boot:rsh:agent: rsh n0<29283> ssi:boot:rsh:username: > > n0<29283> ssi:boot:rsh:verbose: 1000 n0<29283> = ssi:boot:rsh:algorithm: > > linear n0<29283> ssi:boot:rsh:priority: 10 n0<29283> ssi:boot: = module > > available: rsh, priority: 10 n0<29283> ssi:boot: finalizing module > > globus n0<29283> ssi:boot:globus: finalizing n0<29283> ssi:boot: = closing > > module globus n0<29283> ssi:boot: Selected boot module rsh > > =20 > > LAM 7.0.4/MPI 2 C++/ROMIO - Indiana University > > =20 > > n0<29283> ssi:boot:base: looking for boot schema in following > > directories: > > n0<29283> ssi:boot:base: > > n0<29283> ssi:boot:base: $TROLLIUSHOME/etc > > n0<29283> ssi:boot:base: $LAMHOME/etc > > n0<29283> ssi:boot:base: /usr/local/etc > > n0<29283> ssi:boot:base: looking for boot schema file: > > n0<29283> ssi:boot:base: /home/jracine/bhost.lam > > n0<29283> ssi:boot:base: found boot schema: /home/jracine/bhost.lam > > n0<29283> ssi:boot:rsh: found the following hosts: > > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu (cpu=3D2) > > n0<29283> ssi:boot:rsh: resolved hosts: > > n0<29283> ssi:boot:rsh: n0 jracine.maxwell.syr.edu --> = 128.230.130.10 > > (origin)n0<29283> ssi:boot:rsh: starting RTE procs > > n0<29283> ssi:boot:base:linear: starting > > n0<29283> ssi:boot:base:server: opening server TCP socket n0<29283> > > ssi:boot:base:server: opened port 49832 n0<29283> = ssi:boot:base:linear: > > booting n0 (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: = starting > > lamd on (jracine.maxwell.syr.edu) n0<29283> ssi:boot:rsh: starting = on n0 > > (jracine.maxwell.syr.edu): hboot -t -c lam-conf.lamd -d -I -H > > 128.230.130.10 -P 49832 -n 0 -o 0 n0<29283> ssi:boot:rsh: launching > > locally > > hboot: performing tkill > > hboot: tkill -d > > tkill: setting prefix to (null) > > tkill: setting suffix to (null) > > tkill: got killname > > back: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile > > tkill: removing socket file ... > > tkill: socket > > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-kernel-socketd > > tkill: removing IO daemon socket file ... > > tkill: IO daemon socket > > file: /tmp/lam-jracine@jracine.maxwell.syr.edu/lam-io-socket > > tkill: f_kill =3D = "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > > tkill: nothing to kill: > > "/tmp/lam-jracine@jracine.maxwell.syr.edu/lam-killfile" > > hboot: booting... > > hboot: fork /usr/local/bin/lamd > > [1] 29286 lamd -H 128.230.130.10 -P 49832 -n 0 -o 0 -d n0<29283> > > ssi:boot:rsh: successfully launched on n0 > > (jracine.maxwell.syr.edu) > > n0<29283> ssi:boot:base:server: expecting connection from finite = list > > hboot: attempting to execute > > n-1<29286> ssi:boot: Opening > > n-1<29286> ssi:boot: opening module globus > > n-1<29286> ssi:boot: initializing module globus > > n-1<29286> ssi:boot:globus: globus-job-run not found, globus boot = will > > not run n-1<29286> ssi:boot: module not available: globus n-1<29286> > > ssi:boot: opening module rsh n-1<29286> ssi:boot: initializing = module > > rsh n-1<29286> ssi:boot:rsh: module initializing n-1<29286> > > ssi:boot:rsh:agent: rsh n-1<29286> ssi:boot:rsh:username: > > n-1<29286> ssi:boot:rsh:verbose: 1000 n-1<29286> = ssi:boot:rsh:algorithm: > > linear n-1<29286> ssi:boot:rsh:priority: 10 n-1<29286> ssi:boot: = module > > available: rsh, priority: 10 n-1<29286> ssi:boot: finalizing module > > globus n-1<29286> ssi:boot:globus: finalizing n-1<29286> ssi:boot: > > closing module globus n-1<29286> ssi:boot: Selected boot module rsh > > n0<29283> ssi:boot:base:server: got connection from 128.230.130.10 > > n0<29283> ssi:boot:base:server: this connection is expected (n0) > > n0<29283> ssi:boot:base:server: remote lamd is at = 128.230.130.10:50206 > > n0<29283> ssi:boot:base:server: closing server socket n0<29283> > > ssi:boot:base:server: connecting to lamd at 128.230.130.10:49833 > > n0<29283> ssi:boot:base:server: connected n0<29283> > > ssi:boot:base:server: sending number of links (1) n0<29283> > > ssi:boot:base:server: sending info: n0 > > (jracine.maxwell.syr.edu) > > n0<29283> ssi:boot:base:server: finished sending > > n0<29283> ssi:boot:base:server: disconnected from = 128.230.130.10:49833 > > n0<29283> ssi:boot:base:linear: finished n0<29283> ssi:boot:rsh: all = RTE > > procs started n0<29283> ssi:boot:rsh: finalizing n0<29283> ssi:boot: > > Closing n-1<29286> ssi:boot:rsh: finalizing n-1<29286> ssi:boot: = Closing > >=20 > >=20 > >=20 > > _______________________________________________ > > freebsd-cluster@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-cluster > > To unsubscribe, send any mail to > > "freebsd-cluster-unsubscribe@freebsd.org" > >=20 >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to = "freebsd-amd64-unsubscribe@freebsd.org" --=20 Bob Willcox What's done to children, they will do to = society. bob@immure.com Austin, TX From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 12 11:01:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D77116A4ED for ; Mon, 12 Apr 2004 11:01:28 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 772BC43D39 for ; Mon, 12 Apr 2004 11:01:28 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i3CI1Sbv084365 for ; Mon, 12 Apr 2004 11:01:28 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i3CI1RXX084359 for freebsd-amd64@freebsd.org; Mon, 12 Apr 2004 11:01:27 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Apr 2004 11:01:27 -0700 (PDT) Message-Id: <200404121801.i3CI1RXX084359@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2004 18:01:28 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64 Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA8EA16A4CE for ; Tue, 13 Apr 2004 05:09:14 -0700 (PDT) Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AB8643D31 for ; Tue, 13 Apr 2004 05:09:12 -0700 (PDT) (envelope-from jracine@maxwell.syr.edu) Received: from [24.59.145.52] (syr-24-59-145-52.twcny.rr.com [24.59.145.52]) i3DC99dd002194 for ; Tue, 13 Apr 2004 08:09:10 -0400 (EDT) From: Jeffrey Racine To: freebsd-amd64@freebsd.org Content-Type: text/plain Organization: Syracuse University Message-Id: <1081858148.795.4.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.6.2FreeBSD GNOME Team Port Date: Tue, 13 Apr 2004 08:09:09 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Openoffice on amd64... possible? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 12:09:14 -0000 Hi. I have scoured newsgroups and the web, and have yet to come across any mention of openoffice & amd64. Has anyone managed to get this running, or is this somewhere in the future? By the way, thanks for the kind and helpful responses I have had on my recent posts to this newsgroup. Sincerely appreciated, and my new system is now humming along thanks to your help. Thanks! -- Jeff From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 13 05:35:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B507816A4D1 for ; Tue, 13 Apr 2004 05:35:15 -0700 (PDT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E30643D78 for ; Tue, 13 Apr 2004 05:35:08 -0700 (PDT) (envelope-from tilman@arved.at) Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1]) i3DCZ7i5011973; Tue, 13 Apr 2004 14:35:07 +0200 (CEST) (envelope-from tilman@arved.at) Received: (from tilman@localhost) by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i3DCZ7EA011972; Tue, 13 Apr 2004 14:35:07 +0200 (CEST) X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to tilman@arved.at using -f Date: Tue, 13 Apr 2004 14:35:07 +0200 From: Tilman Linneweh To: Jeffrey Racine Message-ID: <20040413123507.GA11950@arved.at> References: <1081858148.795.4.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1081858148.795.4.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org Subject: Re: Openoffice on amd64... possible? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 12:35:16 -0000 * Jeffrey Racine [Di, 13 Apr 2004 at 14:09 GMT]: > I have scoured newsgroups and the web, and have yet to come across any > mention of openoffice & amd64. Has anyone managed to get this running, > or is this somewhere in the future? > > By the way, thanks for the kind and helpful responses I have had on my > recent posts to this newsgroup. Sincerely appreciated, and my new system > is now humming along thanks to your help. Do you have a working jdk? From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 13 05:38:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31F9116A4CE for ; Tue, 13 Apr 2004 05:38:08 -0700 (PDT) Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9E7F43D5C for ; Tue, 13 Apr 2004 05:38:07 -0700 (PDT) (envelope-from jracine@maxwell.syr.edu) Received: from [24.59.145.52] (syr-24-59-145-52.twcny.rr.com [24.59.145.52]) i3DCc2dd025374; Tue, 13 Apr 2004 08:38:03 -0400 (EDT) From: Jeffrey Racine To: Tilman Linneweh In-Reply-To: <20040413123507.GA11950@arved.at> References: <1081858148.795.4.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> <20040413123507.GA11950@arved.at> Content-Type: text/plain Organization: Syracuse University Message-Id: <1081859881.795.9.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.6.2FreeBSD GNOME Team Port Date: Tue, 13 Apr 2004 08:38:01 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: amd64@FreeBSD.org Subject: Re: Openoffice on amd64... possible? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 12:38:08 -0000 Hi Tilman. This was the problem when I tried an install as I recall... I got a message to the effect that lib-elf (if I recall correctly) was not currently supported, and the compile stopped. I presume that this needs binary emulation which is not yet supported? -- Jeff On Tue, 2004-04-13 at 14:35 +0200, Tilman Linneweh wrote: > * Jeffrey Racine [Di, 13 Apr 2004 at 14:09 GMT]: > > I have scoured newsgroups and the web, and have yet to come across any > > mention of openoffice & amd64. Has anyone managed to get this running, > > or is this somewhere in the future? > > > > By the way, thanks for the kind and helpful responses I have had on my > > recent posts to this newsgroup. Sincerely appreciated, and my new system > > is now humming along thanks to your help. > > Do you have a working jdk? From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 13 06:28:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D95FE16A4CE for ; Tue, 13 Apr 2004 06:28:43 -0700 (PDT) Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5207C43D46 for ; Tue, 13 Apr 2004 06:28:43 -0700 (PDT) (envelope-from jracine@maxwell.syr.edu) Received: from [128.230.130.10] (jracine.maxwell.syr.edu [128.230.130.10]) by maxwell.syr.edu (8.12.10/8.9.1) with ESMTP id i3DDSWo2009152; Tue, 13 Apr 2004 09:28:32 -0400 (EDT) From: Jeffrey Racine To: Tilman Linneweh In-Reply-To: <20040413123507.GA11950@arved.at> References: <1081858148.795.4.camel@x1-6-00-b0-d0-c2-67-0e.twcny.rr.com> <20040413123507.GA11950@arved.at> Content-Type: text/plain Organization: Syracuse University Message-Id: <1081862927.644.3.camel@jracine.maxwell.syr.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 13 Apr 2004 09:28:47 -0400 Content-Transfer-Encoding: 7bit cc: amd64@FreeBSD.org Subject: Re: Openoffice on amd64... possible? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 13:28:44 -0000 Hi. Sorry for the vagueness of the previous post. I had attempted numerous ways of installing and that was one of the messages I received. Below you will see the exact error message during install (I include uname & dmesg as well) Here is the output from a fresh install. It is the version of gcc that is not supported by default... as always, thanks! -- OpenOffice install output jracine# portinstall openoffice ---> 2 ports match the given pattern 'openoffice': editors/openoffice-1.0 editors/openoffice-1.1 Install 'editors/openoffice-1.0'? [yes] no Install 'editors/openoffice-1.1'? [yes] yes ---> Installing 'openoffice-1.1.1' from a port (editors/openoffice-1.1) ---> Building '/usr/ports/editors/openoffice-1.1' ===> Cleaning for atk-1.6.0 ===> Cleaning for rpm-3.0.6_9 ===> Cleaning for unzip-5.50_2 ===> Cleaning for zip-2.3_1 ===> Cleaning for libiconv-1.9.1_3 ===> Cleaning for ORBit-0.5.17_2 ===> Cleaning for apache-ant-1.6.1_1 ===> Cleaning for autoconf-2.53_1 ===> Cleaning for autoconf-2.13.000227_5 ===> Cleaning for automake-1.4.5_9 ===> Cleaning for bison-1.75_2 ===> Cleaning for gettext-0.13.1_1 ===> Cleaning for glib-1.2.10_10 ===> Cleaning for glib-2.4.0 ===> Cleaning for gmake-3.80_2 ===> Cleaning for imake-4.3.0_2 ===> Cleaning for libtool-1.3.5_2 ===> Cleaning for m4-1.4_1 ===> Cleaning for nspr-4.4.1_1 ===> Cleaning for p5-gettext-1.01_4 ===> Cleaning for pkgconfig-0.15.0_1 ===> Cleaning for popt-1.6.4_2 ===> Cleaning for linux_base-7.1_6 ===> Cleaning for jpeg-6b_2 ===> Cleaning for lcms-1.09_1,1 ===> Cleaning for libmng-1.0.7 ===> Cleaning for png-1.2.5_3 ===> Cleaning for tiff-3.6.1_1 ===> Cleaning for diablo-jdk-1.3.1.0_1===> Cleaning for javavmwrapper-1.5 ===> Cleaning for jdk-1.4.2p6_4===> Cleaning for linux-sun-jdk-1.4.2.04 ===> Cleaning for gcc-3.2.3_1 ===> Cleaning for perl-5.8.2_5 ===> Cleaning for python-2.3.3_4 ===> Cleaning for compat4x-amd64-5.2.1 ===> Cleaning for help2man-1.33.1 ===> Cleaning for hicolor-icon-theme-0.5 ===> Cleaning for shared-mime-info-0.14_2 ===> Cleaning for freetype2-2.1.7_2 ===> Cleaning for coreutils-5.2.1 ===> Cleaning for expat-1.95.7 ===> Cleaning for intltool-0.30_1 ===> Cleaning for libxml2-2.6.8 ===> Cleaning for p5-XML-Parser-2.34_1 ===> Cleaning for XFree86-fontDefaultBitmaps-4.3.0 ===> Cleaning for XFree86-fontEncodings-4.3.0 ===> Cleaning for XFree86-fontScalable-4.3.0 ===> Cleaning for fontconfig-2.2.2,1 ===> Cleaning for libXft-2.1.6 ===> Cleaning for urwfonts-1.0 ===> Cleaning for XFree86-VirtualFramebufferServer-4.3.0_4 ===> Cleaning for gtk-1.2.10_11 ===> Cleaning for gtk-2.4.0 ===> Cleaning for open-motif-2.2.2_2 ===> Cleaning for pango-1.4.0 ===> Cleaning for XFree86-clients-4.3.0_7 ===> Cleaning for XFree86-libraries-4.3.0_6 ===> Cleaning for openoffice-1.1.1 ===> Vulnerability check disabled REQUIREMENTS: OO requires that the ENV variable LANG is set to a proper value. Dependent on which language port you use, OO does automatically set LANG to a suitable value. You can change this with: USE_LANG="preferred language" and set a different language like: en_US.ISO8859-15 en_US.ISO8859-1 US-ASCII Your current setting is: USE_LANG=en_US.ISO8859-15 OPTIONS: You can compile OO with debug symbols if you call make with WITH_DEBUG=1 If you set WITH_DEBUG=2, you add internal OO.org debug support. You may set WITH_TTF_BYTECODE_ENABLED=YES if you like to use the Freetype library to render TTF fonts. Normally the TTF lib is not used to render fonts. If you have licensed the Apple patents US05155805 US05159668 and US05325479 you can enable this option to get better quality of glyphs at small bitmap sizes. You may set WITH_GIF_LZW_COMPRESSION=YES If you want to make compressed gif images If must have license from the Unisys and IBM patents to enable this option to get compressed GIF images. According to http://www.unisys.com/about__unisys/lzw Patent expires: June 20, 2003 : U.S. June 18, 2004 : U.K., France, Germany and Italy June 20, 2004 : Japan July 7, 2004 : Canada NOTICE: To build Openoffice, you should have a lot of free diskspace (~ 4GB). If you want SDK and/or solver, please type make sdk and/or make solver >> OOo_1.1.1p1_source.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/openoffice1.1. >> Attempting to fetch from ftp://www.t.ring.gr.jp/pub/misc/openoffice/stable/1.1.1/. OOo_1.1.1p1_source.tar.bz2 100% of 183 MB 284 kBps 00m00s >> gpc231.tar.Z doesn't seem to exist in /usr/ports/distfiles/openoffice1.1. >> Attempting to fetch from ftp://ftp.cs.man.ac.uk/pub/toby/gpc/. gpc231.tar.Z 100% of 27 kB 50 kBps >> patch-openoffice-mozilla101-2002-10-14 doesn't seem to exist in /usr/ports/distfiles/openoffice1.1. >> Attempting to fetch from http://people.freebsd.org/~mbr/ooo/. patch-openoffice-mozilla101-2002-10-14 100% of 28 kB 86 kBps >> mozilla-vendor-1.0.2a.tgz doesn't seem to exist in /usr/ports/distfiles/openoffice1.1. >> Attempting to fetch from http://people.freebsd.org/~mbr/ooo/. mozilla-vendor-1.0.2a.tgz 100% of 7292 B 44 kBps ===> Extracting for openoffice-1.1.1 >> Checksum OK for openoffice1.1/OOo_1.1.1p1_source.tar.bz2. >> Checksum OK for openoffice1.1/gpc231.tar.Z. >> Checksum OK for openoffice1.1/patch-openoffice-mozilla101-2002-10-14. >> Checksum OK for openoffice1.1/mozilla-vendor-1.0.2a.tgz. ===> Extracting mozilla sub project ===> Vulnerability check disabled >> mozilla-source-1.0.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.0.2/src/. mozilla-source-1.0.2.tar.bz2 100% of 28 MB 1712 kBps 00m00s >> libart_lgpl-1.0.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/. fetch: ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/marcus/libart_lgpl-1.0.2.tar.bz2: File unavailable (e.g., file not found, no access) >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. libart_lgpl-1.0.2.tar.bz2 100% of 95 kB 56 kBps ===> Extracting for mozilla-1.0.2_1 >> Checksum OK for mozilla-source-1.0.2.tar.bz2. >> Checksum OK for libart_lgpl-1.0.2.tar.bz2. ===> Patching for openoffice-1.1.1 ===> Applying FreeBSD patches for openoffice-1.1.1 ===> Patching for mozilla-1.0.2_1 ===> Applying FreeBSD patches for mozilla-1.0.2_1 ===> Removing GIF LZW compression for openoffice-1.1.1 ===> openoffice-1.1.1 depends on executable: gcc32 - not found ===> Verifying install for gcc32 in /usr/ports/lang/gcc32 ===> gcc-3.2.3_1 is only for i386, and you are running amd64. *** Error code 1 Stop in /usr/ports/lang/gcc32. *** Error code 1 Stop in /usr/ports/editors/openoffice-1.1. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall43979.0 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! editors/openoffice-1.1 (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- dmesg FreeBSD jracine.maxwell.syr.edu 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Fri Apr 9 15:39:47 EDT 2004 root@jracine.maxwell.syr.edu:/usr/obj/usr/src/sys/OPTERON amd64 [jracine@jracine jracine]$ dmesg Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #0: Fri Apr 9 15:39:47 EDT 2004 root@jracine.maxwell.syr.edu:/usr/obj/usr/src/sys/OPTERON WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8090b000. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2205.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 3674144768 (3503 MB) avail memory = 3543220224 (3379 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard random: acpi0: on motherboard acpi0: [GIANT-LOCKED] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_cpu1: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0:0:0: setting power state D0 pci0:7:0: setting power state D0 pci0:7:1: setting power state D0 pci0:7:3: setting power state D0 pci0:7:5: setting power state D0 pci0:10:1: setting power state D0 pci0:11:1: setting power state D0 pci0:24:0: setting power state D0 pci0:24:1: setting power state D0 pci0:24:2: setting power state D0 pci0:24:3: setting power state D0 pci0:25:0: setting power state D0 pci0:25:1: setting power state D0 pci0:25:2: setting power state D0 pci0:25:3: setting power state D0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1:0:0: setting power state D0 pci1: at device 0.0 (no driver attached) pcib2: at device 6.0 on pci0 pci2: on pcib2 pci2:0:0: setting power state D0 pci2:0:1: setting power state D0 pci2:6:0: setting power state D0 pci2:7:0: setting power state D0 pci2:7:1: setting power state D0 pci2:7:2: setting power state D0 ohci0: mem 0xfd8fe000-0xfd8fefff irq 19 at device 0.0 on pci2 ohci0: Bus reserved 0x1000 bytes for rid 0x10 type 3 at 0xfd8fe000 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfd8ff000-0xfd8fffff irq 19 at device 0.1 on pci2 ohci1: Bus reserved 0x1000 bytes for rid 0x10 type 3 at 0xfd8ff000 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered fwohci0: mem 0xfd8f8000-0xfd8fbfff,0xfd8fd800-0xfd8fdfff irq 18 at device 6.0 on pci2 fwohci0: Bus reserved 0x800 bytes for rid 0x10 type 3 at 0xfd8fd800 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:00:00:00:00:01:0e:f8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:01:0e:f8 fwe0: Ethernet address: 02:00:00:01:0e:f8 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ohci2: mem 0xfd8f7000-0xfd8f7fff irq 19 at device 7.0 on pci2 ohci2: Bus reserved 0x1000 bytes for rid 0x10 type 3 at 0xfd8f7000 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0 usb2: on ohci2 usb2: USB revision 1.0 uhub2: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered ohci3: mem 0xfd8fc000-0xfd8fcfff irq 16 at device 7.1 on pci2 ohci3: Bus reserved 0x1000 bytes for rid 0x10 type 3 at 0xfd8fc000 ohci3: [GIANT-LOCKED] usb3: OHCI version 1.0 usb3: on ohci3 usb3: USB revision 1.0 uhub3: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci2: at device 7.2 (no driver attached) pci2: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER pci2:7:2: setting power state D3 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 atapci0: Bus reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.3 (no driver attached) pci0:7:3: setting power state D3 pcm0: port 0xcc00-0xcc3f,0xc800-0xc8ff irq 17 at device 7.5 on pci0 pcm0: Bus reserved 0x100 bytes for rid 0x10 type 4 at 0xc800 pcm0: Bus reserved 0x40 bytes for rid 0x14 type 4 at 0xcc00 pcm0: [GIANT-LOCKED] pcm0: pcib3: at device 10.0 on pci0 pci3: on pcib3 pci3:3:0: setting power state D0 skc0: port 0xa800-0xa8ff mem 0xfd9fc000-0xfd9fffff irq 19 at device 3.0 on pci3 skc0: Bus reserved 0x4000 bytes for rid 0x10 type 3 at 0xfd9fc000 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter sk0: on skc0 malloc() of "512" with the following non-sleepable locks held: exclusive sleep mutex skc0 (network driver) r = 0 (0xffffff00d33ada70) locked @ /usr/src/sys/pci/if_sk.c:1368 Stack backtrace: witness_warn() at witness_warn+0x1a5 uma_zalloc_arg() at uma_zalloc_arg+0x6a malloc() at malloc+0x9e if_attach() at if_attach+0x21f ether_ifattach() at ether_ifattach+0x27 sk_attach() at sk_attach+0x2e6 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 skc_attach() at skc_attach+0x30b device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pci_attach() at acpi_pci_attach+0xed device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pcib_attach() at acpi_pcib_attach+0xc7 acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x89 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pci_attach() at acpi_pci_attach+0xed device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pcib_attach() at acpi_pcib_attach+0xc7 acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0xd3 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_probe_children() at acpi_probe_children+0x58 acpi_attach() at acpi_attach+0x52e device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 nexus_attach() at nexus_attach+0x17 device_probe_and_attach() at device_probe_and_attach+0xbe root_bus_configure() at root_bus_configure+0x20 configure() at configure+0x1f mi_startup() at mi_startup+0xaa btext() at btext+0x2c sk0: Ethernet address: 00:d0:68:03:d4:99 miibus0: on sk0 e1000phy0: on miibus0 lock order reversal 1st 0xffffff00d33ada70 skc0 (network driver) @ /usr/src/sys/pci/if_sk.c:672 2nd 0xffffffff8078a220 kernel environment (kernel environment) @ /usr/src/sys/kern/kern_environment.c:288 Stack backtrace: witness_checkorder() at witness_checkorder+0x4ac _sx_slock() at _sx_slock+0x4d getenv() at getenv+0x37 getenv_quad() at getenv_quad+0x13 getenv_int() at getenv_int+0x13 e1000phy_attach() at e1000phy_attach+0x24 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 miibus_attach() at miibus_attach+0x4b device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 mii_phy_probe() at mii_phy_probe+0xc4 sk_attach() at sk_attach+0x311 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 skc_attach() at skc_attach+0x30b device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pci_attach() at acpi_pci_attach+0xed device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pcib_attach() at acpi_pcib_attach+0xc7 acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x89 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pci_attach() at acpi_pci_attach+0xed device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_pcib_attach() at acpi_pcib_attach+0xc7 acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0xd3 device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 acpi_probe_children() at acpi_probe_children+0x58 acpi_attach() at acpi_attach+0x52e device_probe_and_attach() at device_probe_and_attach+0xbe bus_generic_attach() at bus_generic_attach+0x18 nexus_attach() at nexus_attach+0x17 device_probe_and_attach() at device_probe_and_attach+0xbe root_bus_configure() at root_bus_configure+0x20 configure() at configure+0x1f mi_startup() at mi_startup+0xaa btext() at btext+0x2c e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, autoskc0: [GIANT-LOCKED] pci0: at device 10.1 (no driver attached) pci0:10:1: setting power state D3 pcib4: at device 11.0 on pci0 pci4: on pcib4 pci4:1:0: setting power state D0 twe0: <3ware 7000 series Storage Controller. Driver version 1.50.01.000> port 0xbc00-0xbc0f mem 0xfe000000-0xfe7fffff irq 17 at device 1.0 on pci4 twe0: Bus reserved 0x10 bytes for rid 0x10 type 4 at 0xbc00 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 pci0: at device 11.1 (no driver attached) pci0:11:1: setting power state D3 acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 cpu0 on motherboard cpu1 on motherboard orm0: