From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 17 08:49:38 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 2430716A492 for ; Sun, 17 Sep 2006 08:49:38 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from graf.pompo.net (graf.pompo.net [81.56.186.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A01643D58 for ; Sun, 17 Sep 2006 08:49:37 +0000 (GMT) (envelope-from thierry@pompo.net) Received: by graf.pompo.net (Postfix, from userid 1001) id 4561B1144C; Sun, 17 Sep 2006 10:48:02 +0200 (CEST) Date: Sun, 17 Sep 2006 10:48:02 +0200 From: Thierry Thomas To: Liste FreeBSD-amd64 Message-ID: <20060917084802.GA29881@graf.pompo.net> Mail-Followup-To: Liste FreeBSD-amd64 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i X-Operating-System: FreeBSD 6.1-STABLE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 Cc: Subject: make: strange behaviour when building net/mpich2. 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: Sun, 17 Sep 2006 08:49:38 -0000 Hello, I'm the maintainer of the port net/mpich2, and I have just committed the following patch: --- Makefile 6 Sep 2006 21:14:00 -0000 1.48 +++ Makefile 17 Sep 2006 08:40:21 -0000 1.49 @@ -194,6 +194,11 @@ WITHOUT_JAVA= yo # No package for Java ATM .endif +.if ${ARCH} == "amd64" +# gmake should not be required, this is a work-around +USE_GMAKE= yes +.endif + PREFIX:= ${PREFIX}/${PORTNAME} pre-configure: The original problem has been reported to me by two users, Andrzej Tobola and Jaroslaw Gruca: it was a linkage failure due to missing symbols on amd64 / 7.0. After investigations, I have noticed that with native make, compilation stops at: Making src/logging .... make /tmp/ports/mpich2/mpich2-1.0.4p1/src/mpe2/lib/libmpe_nompi.a `/tmp/ports/mpich2/mpich2-1.0.4p1/src/mpe2/lib/libmpe_nompi.a' is up to date. On i386, or with gmake, libmpe_nompi.a is not considered "up to date", and several objects are created in this subdirectory src/logging, and then archived in the library. There is no configure issue, and the generated Makefiles are normal. Any idea? -- Th. Thomas. From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 17 22:07:01 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 409F916A49E for ; Sun, 17 Sep 2006 22:07:01 +0000 (UTC) (envelope-from jared@little-miracles.org) Received: from mail-ihug.icp-qv1-irony6.iinet.net.au (ihug-mail.icp-qv1-irony6.iinet.net.au [203.59.1.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 889AA43D7F for ; Sun, 17 Sep 2006 22:06:59 +0000 (GMT) (envelope-from jared@little-miracles.org) Received: from 203-206-78-223.dyn.iinet.net.au (HELO eternity.thanhandjared.net) ([203.206.78.223]) by mail-ihug.icp-qv1-irony6.iinet.net.au with ESMTP; 18 Sep 2006 06:06:57 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,177,1157299200"; d="scan'208"; a="460408772:sNHT29278264" Received: from [192.168.0.1] (seduction.thanhandjared.net [192.168.0.1]) by eternity.thanhandjared.net (Postfix) with ESMTP id 88FDFB911 for ; Mon, 18 Sep 2006 08:10:23 +1000 (EST) Message-ID: <450DC701.3030505@little-miracles.org> Date: Mon, 18 Sep 2006 08:06:57 +1000 From: Jared Ring User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Compiling an amd64 and i386 world X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Sep 2006 22:07:01 -0000 Hi, please reprimand me if this was the wrong list to ask on I have a number of i386 machines, for maintaining them only one tracks -stable and builds the kernel and world,the others mount /usr/obj and /usr/src from this host and install from there. This is all described in the handbook. Now we have purchased some more machines, and these are amd64 architecture. Is it possible to setup my buildmachine to build both i386 and amd64 worlds/kernels and then configure make.conf on the appropriate clients so that they install the right one? Thanks for your time and help in answering this. On this one point, the handbook doesnt really seem clear. I'd be happy to provide a bit of doco for the handbook if it really is okay. Cheers Jared From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 17 22:31:18 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 CBE5416A403 for ; Sun, 17 Sep 2006 22:31:18 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50BFD43D53 for ; Sun, 17 Sep 2006 22:31:18 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 3D3215E53; Mon, 18 Sep 2006 02:31:17 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 355A65E4E; Mon, 18 Sep 2006 02:31:17 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8HMVL7o085234; Mon, 18 Sep 2006 02:31:21 +0400 (MSD) (envelope-from ru) Date: Mon, 18 Sep 2006 02:31:21 +0400 From: Ruslan Ermilov To: Jared Ring Message-ID: <20060917223121.GD84871@rambler-co.ru> References: <450DC701.3030505@little-miracles.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6WlEvdN9Dv0WHSBl" Content-Disposition: inline In-Reply-To: <450DC701.3030505@little-miracles.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-amd64@FreeBSD.org Subject: Re: Compiling an amd64 and i386 world X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Sep 2006 22:31:18 -0000 --6WlEvdN9Dv0WHSBl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 18, 2006 at 08:06:57AM +1000, Jared Ring wrote: > Hi, please reprimand me if this was the wrong list to ask on >=20 > I have a number of i386 machines, for maintaining them only one tracks=20 > -stable and builds the kernel and world,the others mount /usr/obj and=20 > /usr/src from this host and install from there. This is all described in= =20 > the handbook. >=20 > Now we have purchased some more machines, and these are amd64=20 > architecture. Is it possible to setup my buildmachine to build both i386= =20 > and amd64 worlds/kernels and then configure make.conf on the appropriate= =20 > clients so that they install the right one? >=20 > Thanks for your time and help in answering this. On this one point, the= =20 > handbook doesnt really seem clear. I'd be happy to provide a bit of doco= =20 > for the handbook if it really is okay. >=20 We support cross-building and installing for a different hardware architecture. Remote root, /usr and /var partitions should be mounted on say /mnt of the build host, then doing "make installworld DESTDIR=3D/mnt" together with other options used to build will DTRT. See the build(7) manpage for details, especially the bits about TARGET_ARCH/TARGET and rpc.lockd(8). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --6WlEvdN9Dv0WHSBl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFDcy5qRfpzJluFF4RAtrFAJwPA9+SwpLvs/OJGPjLW+pr7UZgrwCfQjV1 9pfcok6WKhXXu46CrIN99Bs= =KYAK -----END PGP SIGNATURE----- --6WlEvdN9Dv0WHSBl-- From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 01:40:26 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8964316A403 for ; Mon, 18 Sep 2006 01:40:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42F6C43D45 for ; Mon, 18 Sep 2006 01:40:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8I1eQTr087493 for ; Mon, 18 Sep 2006 01:40:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8I1eQ0O087492; Mon, 18 Sep 2006 01:40:26 GMT (envelope-from gnats) Date: Mon, 18 Sep 2006 01:40:26 GMT Message-Id: <200609180140.k8I1eQ0O087492@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Jan Mikkelsen" Cc: Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Mikkelsen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 01:40:26 -0000 The following reply was made to PR amd64/89550; it has been noted by GNATS. From: "Jan Mikkelsen" To: , Cc: Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) Date: Mon, 18 Sep 2006 11:39:42 +1000 I am seeing this too. Tyan S2865 motherboard, Athlon X2, 6.1-RELEASE-p5. Booting from a 6.0-RELEASE/i386 CD seems to work fine, at least as far as the fixit shell. The behaviour below is consistent; it always dies with "panic: sym: VTOBUS FAILED!" after finding the sym0 controller. dmesg below. Thanks, Jan Mikkelsen janm@transactionware.com Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE-p5 #0: Tue Sep 12 13:32:17 EST 2006 root@test.transactionware.com:/work/home/janm/p4/image-freebsd-std-fileserv/work/base-freebsd/work/home/janm/p4/image-freebsd-std-fileserv/FreeBSD/src/sys/TW-SMP ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2210.20-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20fb1 Stepping = 1 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x3 Cores per package: 2 real memory = 2146304000 (2046 MB) avail memory = 2061185024 (1965 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebff000-0xfebfffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: waiting for BIOS to give up control usb1: timed out waiting for BIOS usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xcc00-0xcc0f mem 0xfebfb000-0xfebfbfff irq 21 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xb800-0xb80f mem 0xfebfa000-0xfebfafff irq 22 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 9.0 on pci0 pci1: on pcib1 pci2: at device 5.0 (no driver attached) fwohci0: port 0xa800-0xa87f mem 0xfcffe000-0xfcffe7ff irq 18 at device 6.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:81:00:00:26:37:41 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:e0:81:26:37:41 fwe0: Ethernet address: 02:e0:81:26:37:41 fwe0: if_start running deferred for Giant 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) sym0: <1010-66> port 0xa400-0xa4ff mem 0xfcffd000-0xfcffd3ff,0xfcffa000-0xfcffbfff irq 18 at device 9.0 on pci1 panic: sym: VTOBUS FAILED! cpuid = 0 Uptime: 1s From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 07:11:43 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 4E8A216A407 for ; Mon, 18 Sep 2006 07:11:43 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1B8543D45 for ; Mon, 18 Sep 2006 07:11:42 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GPDI3-0000j3-TF; Mon, 18 Sep 2006 10:11:39 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: am-utils@fsl.cs.sunysb.edu In-reply-to: References: Comments: In-reply-to Danny Braniss message dated "Sat, 16 Sep 2006 19:55:27 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2006 10:11:39 +0300 From: Danny Braniss Message-ID: Cc: Christos Zoulas , freebsd-amd64@FreeBSD.org Subject: Re: mlockall() failes on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 07:11:43 -0000 > > On Sep 16, 7:17pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > -- Subject: Re: mlockall() failes on amd64 > > > > | > On Sep 16, 2:55pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > | > -- Subject: mlockall() failes on amd64 > > | > > > | > | with am-utils 6.1.5, on a amd64 6.1-STABLE kernel i see: > > | > | Couldn't lock process pages in memory using mlockall() > > | > | while it's ok on a i386: > > | > | Locked process pages in memory > > | > | > > | > > > | > We should really fix amd to print the errno string when system calls > > | > fail; now we can only scratch our heads. > > | > > > | > christos > > | sorry, here is the full message: > > | Couldn't lock process pages in memory using mlockall(): Resource temporarily > > | unavailable > > | > > | or error = EAGAIN (ED :-) > > > > heh! > > > > FreeBSD's vm system is very different from NetBSD's, and I am not familiar > > with it. The first and easiest thing to do is to check if the resource limit > > for locked memory is set too low. Then hunt in the kernel sources for mlockall > > and print the arguments it passes to the vm system. Anyway, the error is not > > fatal, and amd should keep working after that. > > > > christos > > im trying to figure out why it core dumped, for the very first time, > (and i don't have the core :-(, and the only thing that was special > on this host, is that we are trying out postgres with allot of memory > requierements, so i thought that maybe it's memory ... > oh well, bug-hunting hat still on :-) some more information: an am-utils child will exit on signal 11 (so far can't get the core) whenever memory gets tite. danny From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 09:11:43 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 368F516A407 for ; Mon, 18 Sep 2006 09:11:43 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 470FD43D5D for ; Mon, 18 Sep 2006 09:11:42 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx34.stngva01.us.mxservers.net (204.202.242.42) by mail08b.verio.de (RS ver 1.0.95vs) with SMTP id 3-02143698; Mon, 18 Sep 2006 11:11:40 +0200 (CEST) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx34.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id cc26e054.27422.276.mx34.stngva01.us.mxservers.net; Mon, 18 Sep 2006 05:11:40 -0400 (EDT) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.7/8.11.6) with ESMTP id k8I9BZjS001141; Mon, 18 Sep 2006 11:11:35 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200609180911.k8I9BZjS001141@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Danny Braniss In-reply-to: Your message of "Mon, 18 Sep 2006 10:11:39 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2006 11:11:35 +0200 From: Gary Jennejohn X-Spam: [F=0.4661187465; heur=0.500(-19800); stat=0.466; spamtraq-heur=0.500(2006091702)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: Christos Zoulas , freebsd-amd64@FreeBSD.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gary Jennejohn List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 09:11:43 -0000 Danny Braniss writes: > > > On Sep 16, 7:17pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > > -- Subject: Re: mlockall() failes on amd64 > > > > > > | > On Sep 16, 2:55pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > > | > -- Subject: mlockall() failes on amd64 > > > | > > > > | > | with am-utils 6.1.5, on a amd64 6.1-STABLE kernel i see: > > > | > | Couldn't lock process pages in memory using mlockall() > > > | > | while it's ok on a i386: > > > | > | Locked process pages in memory > > > | > | > > > | > > > > | > We should really fix amd to print the errno string when system calls > > > | > fail; now we can only scratch our heads. > > > | > > > > | > christos > > > | sorry, here is the full message: > > > | Couldn't lock process pages in memory using mlockall(): Resource tempor > arily > > > | unavailable > > > | > > > | or error = EAGAIN (ED :-) > > > > > > heh! > > > > > > FreeBSD's vm system is very different from NetBSD's, and I am not familia > r > > > with it. The first and easiest thing to do is to check if the resource li > mit > > > for locked memory is set too low. Then hunt in the kernel sources for mlo > ckall > > > and print the arguments it passes to the vm system. Anyway, the error is > not > > > fatal, and amd should keep working after that. > > > > > > christos > > > > im trying to figure out why it core dumped, for the very first time, > > (and i don't have the core :-(, and the only thing that was special > > on this host, is that we are trying out postgres with allot of memory > > requierements, so i thought that maybe it's memory ... > > oh well, bug-hunting hat still on :-) > > some more information: > an am-utils child will exit on signal 11 > (so far can't get the core) whenever memory gets tite. > Maybe you need to set kern.sugid_coredump to 1? --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 09:38:59 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 4F06116A403 for ; Mon, 18 Sep 2006 09:38:59 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BEF943D97 for ; Mon, 18 Sep 2006 09:34:28 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GPFW4-000CHJ-ED; Mon, 18 Sep 2006 12:34:16 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Gary Jennejohn In-reply-to: <200609180911.k8I9BZjS001141@peedub.jennejohn.org> References: <200609180911.k8I9BZjS001141@peedub.jennejohn.org> Comments: In-reply-to Gary Jennejohn message dated "Mon, 18 Sep 2006 11:11:35 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2006 12:34:16 +0300 From: Danny Braniss Message-ID: Cc: Christos Zoulas , freebsd-amd64@FreeBSD.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 09:38:59 -0000 > Danny Braniss writes: > > > > On Sep 16, 7:17pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > > > -- Subject: Re: mlockall() failes on amd64 > > > > > > > > | > On Sep 16, 2:55pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > > > | > -- Subject: mlockall() failes on amd64 > > > > | > > > > > | > | with am-utils 6.1.5, on a amd64 6.1-STABLE kernel i see: > > > > | > | Couldn't lock process pages in memory using mlockall() > > > > | > | while it's ok on a i386: > > > > | > | Locked process pages in memory > > > > | > | > > > > | > > > > > | > We should really fix amd to print the errno string when system calls > > > > | > fail; now we can only scratch our heads. > > > > | > > > > > | > christos > > > > | sorry, here is the full message: > > > > | Couldn't lock process pages in memory using mlockall(): Resource tempor > > arily > > > > | unavailable > > > > | > > > > | or error = EAGAIN (ED :-) > > > > > > > > heh! > > > > > > > > FreeBSD's vm system is very different from NetBSD's, and I am not familia > > r > > > > with it. The first and easiest thing to do is to check if the resource li > > mit > > > > for locked memory is set too low. Then hunt in the kernel sources for mlo > > ckall > > > > and print the arguments it passes to the vm system. Anyway, the error is > > not > > > > fatal, and amd should keep working after that. > > > > > > > > christos > > > > > > im trying to figure out why it core dumped, for the very first time, > > > (and i don't have the core :-(, and the only thing that was special > > > on this host, is that we are trying out postgres with allot of memory > > > requierements, so i thought that maybe it's memory ... > > > oh well, bug-hunting hat still on :-) > > > > some more information: > > an am-utils child will exit on signal 11 > > (so far can't get the core) whenever memory gets tite. > > > > Maybe you need to set kern.sugid_coredump to 1? no luck :-(, and btw amd is not set-uid, it's just run as root. danny From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 11:08:03 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 7F26016A4E6 for ; Mon, 18 Sep 2006 11:08:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE7D43D5C for ; Mon, 18 Sep 2006 11:08:03 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8IB83Fm040897 for ; Mon, 18 Sep 2006 11:08:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8IB81wd040893 for freebsd-amd64@FreeBSD.org; Mon, 18 Sep 2006 11:08:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Sep 2006 11:08:01 GMT Message-Id: <200609181108.k8IB81wd040893@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org 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, 18 Sep 2006 11:08:03 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/73775 amd64 Kernel panic (trap 12) when booting with (not from!) P o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Trap 12: Page fa o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not work on amd64 o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/84930 amd64 [msdosfs] something wrong with msdosfs on amd64 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun 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/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes 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 a amd64/87328 amd64 [boot] BTX halted error o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on AMD64 archit 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/88299 amd64 swapcontext fails with errno 0 f 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/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s 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/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 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/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. 60 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) 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 o amd64/85812 amd64 "Rebooting..." on serial console appears garbled o amd64/85820 amd64 1.5 times slower performance with SCHED_ULE than SCHED o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy 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/92527 amd64 [ciphy.c] no driver for "CICADA VSC 8201 Gigabit LAN P o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out o amd64/98346 amd64 [kbd] caps lock and other keys are always illuminated o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100348 amd64 No hardware support: Marvell 88E8053 Yukon PCI-E Gigab o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102148 amd64 The description of which Intel chips have EM64T is out o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 26 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 15:04:02 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 C298216A664 for ; Mon, 18 Sep 2006 15:04:02 +0000 (UTC) (envelope-from sql82@list.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A84643D49 for ; Mon, 18 Sep 2006 15:03:59 +0000 (GMT) (envelope-from sql82@list.ru) Received: from [195.66.208.53] (port=34513 helo=squirlhome) by mx27.mail.ru with asmtp id 1GPKf7-0004Zp-00 for freebsd-amd64@freebsd.org; Mon, 18 Sep 2006 19:03:57 +0400 Date: Mon, 18 Sep 2006 18:11:37 +0300 From: Andriy Tovstik To: freebsd-amd64@freebsd.org Message-Id: <20060918181137.0a7371c9.sql82@list.ru> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.20; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: qemu and -kernel-kqemu option trouble 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, 18 Sep 2006 15:04:02 -0000 hi, all I installed qemu and kqemu-kmod ports on my machine. I loaded kemu module with kldload, and made sure that it's working with kldstat. Then I tried to start qemu with option -kernel-kqemu but I saw the following message: [squirl@squirlhome ~]$ qemu -kernel-kqemu qemu: invalid option -- '-kernel-kqemu' I installed qemu the following way: cd /usr/ports/emulators/qemu make -DWITH_KQEMU intall clean So it looks like qemu ignores WITH_KQEMU option Version of qemu is 0.8.2_1 My workstation uname -a is: [code]FreeBSD squirlhome.ilyichevsk.net 6.1-RELEASE FreeBSD 6.1-RELEASE #7: Sun Sep 17 15:53:11 EEST 2006 squirl@squirlhome.ilyichevsk.net:/usr/src/sys/amd64/compile/CUSTOM [/code] thanks! and sorry for my english :) From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 15:23:17 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 B873716A40F for ; Mon, 18 Sep 2006 15:23:17 +0000 (UTC) (envelope-from sql82@list.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id E653B43D80 for ; Mon, 18 Sep 2006 15:23:07 +0000 (GMT) (envelope-from sql82@list.ru) Received: from [195.66.208.53] (port=42740 helo=squirlhome) by mx27.mail.ru with asmtp id 1GPKxU-000KDB-00 for freebsd-amd64@freebsd.org; Mon, 18 Sep 2006 19:22:56 +0400 Date: Mon, 18 Sep 2006 18:30:36 +0300 From: Andriy Tovstik To: freebsd-amd64@freebsd.org Message-Id: <20060918183036.0147a87c.sql82@list.ru> In-Reply-To: <20060918181137.0a7371c9.sql82@list.ru> References: <20060918181137.0a7371c9.sql82@list.ru> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.20; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: SOLVED: qemu and -kernel-kqemu option trouble 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, 18 Sep 2006 15:23:17 -0000 My mistake... on x64 - the qemu-system-x86_64 binary uses On Mon, 18 Sep 2006 18:11:37 +0300 Andriy Tovstik wrote: > hi, all > > I installed qemu and kqemu-kmod ports on my machine. > I loaded kemu module with kldload, and made sure that it's working with kldstat. Then I tried to start qemu with option -kernel-kqemu but I saw the following message: > > [squirl@squirlhome ~]$ qemu -kernel-kqemu > qemu: invalid option -- '-kernel-kqemu' > > I installed qemu the following way: > > cd /usr/ports/emulators/qemu > make -DWITH_KQEMU intall clean > > So it looks like qemu ignores WITH_KQEMU option > > Version of qemu is 0.8.2_1 > My workstation uname -a is: > [code]FreeBSD squirlhome.ilyichevsk.net 6.1-RELEASE FreeBSD 6.1-RELEASE #7: Sun Sep 17 15:53:11 EEST 2006 squirl@squirlhome.ilyichevsk.net:/usr/src/sys/amd64/compile/CUSTOM [/code] > > thanks! and sorry for my english :) > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 19:22:07 2006 Return-Path: X-Original-To: amd64@freebsd.org 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 BC51416A4E9; Mon, 18 Sep 2006 19:22:07 +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 4334D43DB0; Mon, 18 Sep 2006 19:21:05 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id k8IJL4E3087757; Mon, 18 Sep 2006 15:21:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id k8IJL3nw024757; Mon, 18 Sep 2006 15:21:03 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C046F7302F; Mon, 18 Sep 2006 15:21:03 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060918192103.C046F7302F@freebsd-current.sentex.ca> Date: Mon, 18 Sep 2006 15:21:03 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 19:22:08 -0000 TB --- 2006-09-18 17:31:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-09-18 17:31:41 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-09-18 17:31:41 - cleaning the object tree TB --- 2006-09-18 17:32:19 - checking out the source tree TB --- 2006-09-18 17:32:19 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-09-18 17:32:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-09-18 17:39:15 - building world (CFLAGS=-O2 -pipe) TB --- 2006-09-18 17:39:15 - cd /src TB --- 2006-09-18 17:39:15 - /usr/bin/make -B buildworld >>> World build started on Mon Sep 18 17:39:17 UTC 2006 >>> 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 >>> World build completed on Mon Sep 18 19:18:50 UTC 2006 TB --- 2006-09-18 19:18:50 - generating LINT kernel config TB --- 2006-09-18 19:18:50 - cd /src/sys/amd64/conf TB --- 2006-09-18 19:18:50 - /usr/bin/make -B LINT TB --- 2006-09-18 19:18:50 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-09-18 19:18:50 - cd /src TB --- 2006-09-18 19:18:50 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Sep 18 19:18:50 UTC 2006 >>> 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 [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/serdev_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/libkern/iconv_converter_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/pci/agp_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/dev/acpica/acpi_if.m -h rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -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 -I/src/sys/gnu/fs/xfs/FreeBSD -I/src/sys/gnu/fs/xfs/FreeBSD/support -I/src/sys/gnu/fs/xfs -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 cc: /src/sys/dev/mii/mvphy.c: No such file or directory mkdep: compile failed *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-09-18 19:21:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-09-18 19:21:03 - ERROR: failed to build lint kernel TB --- 2006-09-18 19:21:03 - tinderbox aborted TB --- 1.41 user 7.30 system 6562.40 real From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 03:18:15 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 0244B16A40F for ; Tue, 19 Sep 2006 03:18:15 +0000 (UTC) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from sbcs.cs.sunysb.edu (sbcs.cs.sunysb.edu [130.245.1.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D20543D58 for ; Tue, 19 Sep 2006 03:18:14 +0000 (GMT) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from agora.fsl.cs.sunysb.edu (agora.fsl.cs.sunysb.edu [130.245.126.12]) by sbcs.cs.sunysb.edu (8.13.6/8.12.11) with ESMTP id k8J3D4o2013163; Mon, 18 Sep 2006 23:18:02 -0400 (EDT) Received: from agora.fsl.cs.sunysb.edu (localhost.localdomain [127.0.0.1]) by agora.fsl.cs.sunysb.edu (8.13.1/8.13.1) with ESMTP id k8J0Xnp6021841; Mon, 18 Sep 2006 20:33:49 -0400 Received: (from ezk@localhost) by agora.fsl.cs.sunysb.edu (8.13.1/8.12.8/Submit) id k8J0XnX0021838; Mon, 18 Sep 2006 20:33:49 -0400 Date: Mon, 18 Sep 2006 20:33:49 -0400 Message-Id: <200609190033.k8J0XnX0021838@agora.fsl.cs.sunysb.edu> From: Erez Zadok To: Danny Braniss In-reply-to: Your message of "Mon, 18 Sep 2006 10:11:39 +0300." X-MailKey: Erez_Zadok Cc: Christos Zoulas , freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 [resend] 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, 19 Sep 2006 03:18:15 -0000 Danny, try something simple first like turning off plock use in amd.conf: plock = no And let's see if Amd runs w/o trying any plock'ing first. Erez. From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 05:40:25 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E33B16A40F for ; Tue, 19 Sep 2006 05:40:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3911643D4C for ; Tue, 19 Sep 2006 05:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8J5eP7N056889 for ; Tue, 19 Sep 2006 05:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8J5ePux056888; Tue, 19 Sep 2006 05:40:25 GMT (envelope-from gnats) Date: Tue, 19 Sep 2006 05:40:25 GMT Message-Id: <200609190540.k8J5ePux056888@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Jan Mikkelsen" Cc: Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Mikkelsen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 05:40:25 -0000 The following reply was made to PR amd64/89550; it has been noted by GNATS. From: "Jan Mikkelsen" To: , Cc: Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) Date: Tue, 19 Sep 2006 15:39:32 +1000 I've just been looking at this. The problem seems to be caused by the sym driver assuming that the = virtual address of the memory allocated by bus_dmamem_alloc will be aligned to = an address 2*PAGE_SIZE. The physical address is aligned like that, but the virtual address isn't. This also breaks the buddy algorithm. Here are the changes I have made to make it work on my system. Summary: Allocate additional pages and adjust the virtual address if necessary to = get memory with the right alignment. Other changes (possibly incorrect): - Adjusted the contigmalloc call because the boundary argument didn't = make sense to me compared to the man page. - Adjusted the highaddr argument in the bus_dma_tag_create() call, = again, the usage didn't really match what I expected from the man page. Little testing; I have used it to boot and dd over an old 4GB drive. = With the original version it never made it past sym_pci_attach. *** FreeBSD/src/sys/dev/sym/sym_hipd.c Tue Aug 8 00:43:31 2006 --- /home/janm/sym_hipd.c Tue Sep 19 15:27:55 2006 *************** *** 439,445 **** #define free_pages(p) free((p), M_DEVBUF) #else #define get_pages() contigmalloc(MEMO_CLUSTER_SIZE, M_DEVBUF, \ ! 0, 0, 1LL << 32, PAGE_SIZE, 1LL << 32) #define free_pages(p) contigfree((p), MEMO_CLUSTER_SIZE, M_DEVBUF) #endif =20 --- 439,446 ---- #define free_pages(p) free((p), M_DEVBUF) #else #define get_pages() contigmalloc(MEMO_CLUSTER_SIZE, M_DEVBUF, \ ! 0, 0, 1LL << 32, PAGE_SIZE, \ ! MEMO_CLUSTER_SIZE) #define free_pages(p) contigfree((p), MEMO_CLUSTER_SIZE, M_DEVBUF) #endif =20 *************** *** 453,458 **** --- 454,462 ---- struct m_vtob *next; bus_dmamap_t dmamap; /* Map for this chunk */ m_addr_t vaddr; /* Virtual address */ + #if PAGE_SIZE < MEMO_CLUSTER_SIZE + m_addr_t adjusted_vaddr; /* Virtual address adjusted for buddy */ + #endif m_addr_t baddr; /* Bus physical address */ } m_vtob_s; /* Hash this stuff a bit to speed up translations */ *************** *** 674,685 **** if (bus_dmamem_alloc(mp->dmat, &vaddr, BUS_DMA_NOWAIT, &vbp->dmamap)) goto out_err; bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr, MEMO_CLUSTER_SIZE, getbaddrcb, &baddr, 0); if (baddr) { ! int hc =3D VTOB_HASH_CODE(vaddr); vbp->vaddr =3D (m_addr_t) vaddr; vbp->baddr =3D (m_addr_t) baddr; vbp->next =3D mp->vtob[hc]; mp->vtob[hc] =3D vbp; ++mp->nump; --- 678,711 ---- if (bus_dmamem_alloc(mp->dmat, &vaddr, BUS_DMA_NOWAIT, &vbp->dmamap)) goto out_err; + #if PAGE_SIZE < MEMO_CLUSTER_SIZE + bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr, + MEMO_CLUSTER_SIZE * 2, getbaddrcb, &baddr, 0); + #else bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr, MEMO_CLUSTER_SIZE, getbaddrcb, &baddr, 0); + #endif if (baddr) { ! int hc; !=20 vbp->vaddr =3D (m_addr_t) vaddr; vbp->baddr =3D (m_addr_t) baddr; + #if PAGE_SIZE < MEMO_CLUSTER_SIZE + /* + * Adjusting vaddr is OK here because we do not error out. + * If that changes, the bus_dmamem_free() call below would + * need to be fixed. + * + * This code assumes that we will be at most one page away + * from having things aligned the way we want. + */ +=20 + if (((m_addr_t) vaddr & ~MEMO_CLUSTER_MASK) !=3D (m_addr_t) vaddr) + vaddr =3D (void*) ((m_addr_t) vaddr + PAGE_SIZE); +=20 + vbp->adjusted_vaddr =3D (m_addr_t) vaddr; + #endif + hc =3D VTOB_HASH_CODE(vaddr); vbp->next =3D mp->vtob[hc]; mp->vtob[hc] =3D vbp; ++mp->nump; *************** *** 733,744 **** mp =3D __sym_calloc(&mp0, sizeof(*mp), "MPOOL"); if (mp) { mp->dev_dmat =3D dev_dmat; ! if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR_32BIT, NULL, NULL, MEMO_CLUSTER_SIZE, 1, MEMO_CLUSTER_SIZE, 0, busdma_lock_mutex, &Giant, &mp->dmat)) { mp->getp =3D ___dma_getp; #ifdef MEMO_FREE_UNUSED mp->freep =3D ___dma_freep; --- 759,779 ---- mp =3D __sym_calloc(&mp0, sizeof(*mp), "MPOOL"); if (mp) { mp->dev_dmat =3D dev_dmat; ! #if PAGE_SIZE < MEMO_CLUSTER_SIZE ! if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE * 2, BUS_SPACE_MAXADDR_32BIT, + BUS_SPACE_MAXADDR, + NULL, NULL, MEMO_CLUSTER_SIZE * 2, 1, + MEMO_CLUSTER_SIZE * 2, 0, + busdma_lock_mutex, &Giant, &mp->dmat)) { + #else + if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE, BUS_SPACE_MAXADDR_32BIT, + BUS_SPACE_MAXADDR, NULL, NULL, MEMO_CLUSTER_SIZE, 1, MEMO_CLUSTER_SIZE, 0, busdma_lock_mutex, &Giant, &mp->dmat)) { + #endif mp->getp =3D ___dma_getp; #ifdef MEMO_FREE_UNUSED mp->freep =3D ___dma_freep; *************** *** 815,827 **** mp =3D ___get_dma_pool(dev_dmat); if (mp) { vp =3D mp->vtob[hc]; while (vp && (m_addr_t) vp->vaddr !=3D a) vp =3D vp->next; } /* Unlock */ if (!vp) panic("sym: VTOBUS FAILED!\n"); ! return vp ? vp->baddr + (((m_addr_t) m) - a) : 0; } =20 =20 --- 850,872 ---- mp =3D ___get_dma_pool(dev_dmat); if (mp) { vp =3D mp->vtob[hc]; + #if (PAGE_SIZE < MEMO_CLUSTER_SIZE) + while (vp && (m_addr_t) vp->adjusted_vaddr !=3D a) + #else while (vp && (m_addr_t) vp->vaddr !=3D a) + #endif vp =3D vp->next; } +=20 /* Unlock */ if (!vp) panic("sym: VTOBUS FAILED!\n"); ! #if (PAGE_SIZE < MEMO_CLUSTER_SIZE) ! return vp->baddr + (((m_addr_t) m) - a) + ! (vp->adjusted_vaddr - vp->vaddr); ! #else ! return vp->baddr + (((m_addr_t) m) - a); ! #endif } =20 =20 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 05:42:08 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 E7E5416A412 for ; Tue, 19 Sep 2006 05:42:08 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 2261643D53 for ; Tue, 19 Sep 2006 05:42:07 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 86290 invoked from network); 19 Sep 2006 05:42:28 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 19 Sep 2006 05:42:28 -0000 Received: (qmail 57024 invoked by uid 1026); 19 Sep 2006 05:42:28 -0000 Received: from 127.0.0.1 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.25 (spamassassin: 3.0.2. Clear:RC:1(127.0.0.1):. Processed in 3.312381 secs); 19 Sep 2006 05:42:28 -0000 Received: from unknown (HELO JMLAPTOP) (unknown) by unknown with SMTP; 19 Sep 2006 05:42:24 -0000 From: "Jan Mikkelsen" To: Date: Tue, 19 Sep 2006 15:42:10 +1000 Organization: Transactionware Message-ID: <011c01c6dbae$59f32fe0$c801a8c0@transactionware.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_011D_01C6DC02.2B9F3FE0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Subject: sym(4) and 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: Tue, 19 Sep 2006 05:42:09 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_011D_01C6DC02.2B9F3FE0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I have been looking at the sym(4) problems on amd64, and have come up with the attached patch. See also amd/89550. Would someone mind taking a look at this to see that it makes sense? Thanks, Jan Mikkelsen ------=_NextPart_000_011D_01C6DC02.2B9F3FE0 Content-Type: application/octet-stream; name="sym_hipd.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="sym_hipd.diff" *** FreeBSD/src/sys/dev/sym/sym_hipd.c Tue Aug 8 00:43:31 2006=0A= --- /home/janm/sym_hipd.c Tue Sep 19 15:27:55 2006=0A= ***************=0A= *** 439,445 ****=0A= #define free_pages(p) free((p), M_DEVBUF)=0A= #else=0A= #define get_pages() contigmalloc(MEMO_CLUSTER_SIZE, M_DEVBUF, \=0A= ! 0, 0, 1LL << 32, PAGE_SIZE, 1LL << 32)=0A= #define free_pages(p) contigfree((p), MEMO_CLUSTER_SIZE, M_DEVBUF)=0A= #endif=0A= =0A= --- 439,446 ----=0A= #define free_pages(p) free((p), M_DEVBUF)=0A= #else=0A= #define get_pages() contigmalloc(MEMO_CLUSTER_SIZE, M_DEVBUF, \=0A= ! 0, 0, 1LL << 32, PAGE_SIZE, \=0A= ! MEMO_CLUSTER_SIZE)=0A= #define free_pages(p) contigfree((p), MEMO_CLUSTER_SIZE, M_DEVBUF)=0A= #endif=0A= =0A= ***************=0A= *** 453,458 ****=0A= --- 454,462 ----=0A= struct m_vtob *next;=0A= bus_dmamap_t dmamap; /* Map for this chunk */=0A= m_addr_t vaddr; /* Virtual address */=0A= + #if PAGE_SIZE < MEMO_CLUSTER_SIZE=0A= + m_addr_t adjusted_vaddr; /* Virtual address adjusted for buddy */=0A= + #endif=0A= m_addr_t baddr; /* Bus physical address */=0A= } m_vtob_s;=0A= /* Hash this stuff a bit to speed up translations */=0A= ***************=0A= *** 674,685 ****=0A= if (bus_dmamem_alloc(mp->dmat, &vaddr,=0A= BUS_DMA_NOWAIT, &vbp->dmamap))=0A= goto out_err;=0A= bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr,=0A= MEMO_CLUSTER_SIZE, getbaddrcb, &baddr, 0);=0A= if (baddr) {=0A= ! int hc =3D VTOB_HASH_CODE(vaddr);=0A= vbp->vaddr =3D (m_addr_t) vaddr;=0A= vbp->baddr =3D (m_addr_t) baddr;=0A= vbp->next =3D mp->vtob[hc];=0A= mp->vtob[hc] =3D vbp;=0A= ++mp->nump;=0A= --- 678,711 ----=0A= if (bus_dmamem_alloc(mp->dmat, &vaddr,=0A= BUS_DMA_NOWAIT, &vbp->dmamap))=0A= goto out_err;=0A= + #if PAGE_SIZE < MEMO_CLUSTER_SIZE=0A= + bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr,=0A= + MEMO_CLUSTER_SIZE * 2, getbaddrcb, &baddr, 0);=0A= + #else=0A= bus_dmamap_load(mp->dmat, vbp->dmamap, vaddr,=0A= MEMO_CLUSTER_SIZE, getbaddrcb, &baddr, 0);=0A= + #endif=0A= if (baddr) {=0A= ! int hc;=0A= ! =0A= vbp->vaddr =3D (m_addr_t) vaddr;=0A= vbp->baddr =3D (m_addr_t) baddr;=0A= + #if PAGE_SIZE < MEMO_CLUSTER_SIZE=0A= + /*=0A= + * Adjusting vaddr is OK here because we do not error out.=0A= + * If that changes, the bus_dmamem_free() call below would=0A= + * need to be fixed.=0A= + *=0A= + * This code assumes that we will be at most one page away=0A= + * from having things aligned the way we want.=0A= + */=0A= + =0A= + if (((m_addr_t) vaddr & ~MEMO_CLUSTER_MASK) !=3D (m_addr_t) vaddr)=0A= + vaddr =3D (void*) ((m_addr_t) vaddr + PAGE_SIZE);=0A= + =0A= + vbp->adjusted_vaddr =3D (m_addr_t) vaddr;=0A= + #endif=0A= + hc =3D VTOB_HASH_CODE(vaddr);=0A= vbp->next =3D mp->vtob[hc];=0A= mp->vtob[hc] =3D vbp;=0A= ++mp->nump;=0A= ***************=0A= *** 733,744 ****=0A= mp =3D __sym_calloc(&mp0, sizeof(*mp), "MPOOL");=0A= if (mp) {=0A= mp->dev_dmat =3D dev_dmat;=0A= ! if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE,=0A= BUS_SPACE_MAXADDR_32BIT,=0A= BUS_SPACE_MAXADDR_32BIT,=0A= NULL, NULL, MEMO_CLUSTER_SIZE, 1,=0A= MEMO_CLUSTER_SIZE, 0,=0A= busdma_lock_mutex, &Giant, &mp->dmat)) {=0A= mp->getp =3D ___dma_getp;=0A= #ifdef MEMO_FREE_UNUSED=0A= mp->freep =3D ___dma_freep;=0A= --- 759,779 ----=0A= mp =3D __sym_calloc(&mp0, sizeof(*mp), "MPOOL");=0A= if (mp) {=0A= mp->dev_dmat =3D dev_dmat;=0A= ! #if PAGE_SIZE < MEMO_CLUSTER_SIZE=0A= ! if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE * 2,=0A= BUS_SPACE_MAXADDR_32BIT,=0A= + BUS_SPACE_MAXADDR,=0A= + NULL, NULL, MEMO_CLUSTER_SIZE * 2, 1,=0A= + MEMO_CLUSTER_SIZE * 2, 0,=0A= + busdma_lock_mutex, &Giant, &mp->dmat)) {=0A= + #else=0A= + if (!bus_dma_tag_create(dev_dmat, 1, MEMO_CLUSTER_SIZE,=0A= BUS_SPACE_MAXADDR_32BIT,=0A= + BUS_SPACE_MAXADDR,=0A= NULL, NULL, MEMO_CLUSTER_SIZE, 1,=0A= MEMO_CLUSTER_SIZE, 0,=0A= busdma_lock_mutex, &Giant, &mp->dmat)) {=0A= + #endif=0A= mp->getp =3D ___dma_getp;=0A= #ifdef MEMO_FREE_UNUSED=0A= mp->freep =3D ___dma_freep;=0A= ***************=0A= *** 815,827 ****=0A= mp =3D ___get_dma_pool(dev_dmat);=0A= if (mp) {=0A= vp =3D mp->vtob[hc];=0A= while (vp && (m_addr_t) vp->vaddr !=3D a)=0A= vp =3D vp->next;=0A= }=0A= /* Unlock */=0A= if (!vp)=0A= panic("sym: VTOBUS FAILED!\n");=0A= ! return vp ? vp->baddr + (((m_addr_t) m) - a) : 0;=0A= }=0A= =0A= =0A= --- 850,872 ----=0A= mp =3D ___get_dma_pool(dev_dmat);=0A= if (mp) {=0A= vp =3D mp->vtob[hc];=0A= + #if (PAGE_SIZE < MEMO_CLUSTER_SIZE)=0A= + while (vp && (m_addr_t) vp->adjusted_vaddr !=3D a)=0A= + #else=0A= while (vp && (m_addr_t) vp->vaddr !=3D a)=0A= + #endif=0A= vp =3D vp->next;=0A= }=0A= + =0A= /* Unlock */=0A= if (!vp)=0A= panic("sym: VTOBUS FAILED!\n");=0A= ! #if (PAGE_SIZE < MEMO_CLUSTER_SIZE)=0A= ! return vp->baddr + (((m_addr_t) m) - a) +=0A= ! (vp->adjusted_vaddr - vp->vaddr);=0A= ! #else=0A= ! return vp->baddr + (((m_addr_t) m) - a);=0A= ! #endif=0A= }=0A= =0A= =0A= ------=_NextPart_000_011D_01C6DC02.2B9F3FE0-- From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 07:19:02 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 EE09616A416 for ; Tue, 19 Sep 2006 07:19:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8F0A43D4C for ; Tue, 19 Sep 2006 07:19:01 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GPZse-0000Da-Gf; Tue, 19 Sep 2006 10:18:56 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Erez Zadok In-reply-to: <200609190033.k8J0XnX0021838@agora.fsl.cs.sunysb.edu> References: <200609190033.k8J0XnX0021838@agora.fsl.cs.sunysb.edu> Comments: In-reply-to Erez Zadok message dated "Mon, 18 Sep 2006 20:33:49 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2006 10:18:56 +0300 From: Danny Braniss Message-ID: Cc: Christos Zoulas , freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 [resend] 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, 19 Sep 2006 07:19:03 -0000 > Danny, try something simple first like turning off plock use in amd.conf: > > plock = no > > And let's see if Amd runs w/o trying any plock'ing first. > > Erez. does it have a command line equivalent? danny From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 09:41:57 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2413216A417; Tue, 19 Sep 2006 09:41:57 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26B6443D67; Tue, 19 Sep 2006 09:41:54 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (ru@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8J9fsD2078030; Tue, 19 Sep 2006 09:41:54 GMT (envelope-from ru@freefall.freebsd.org) Received: (from ru@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8J9frTl078026; Tue, 19 Sep 2006 09:41:53 GMT (envelope-from ru) Date: Tue, 19 Sep 2006 09:41:53 GMT From: Ruslan Ermilov Message-Id: <200609190941.k8J9frTl078026@freefall.freebsd.org> To: adhoniran.gomes@ig.com.br, ru@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated 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, 19 Sep 2006 09:41:57 -0000 Synopsis: [kbd] caps lock and other keys are always illuminated State-Changed-From-To: open->feedback State-Changed-By: ru State-Changed-When: Tue Sep 19 09:41:08 UTC 2006 State-Changed-Why: Does disabling device kbdmux0 either in the kernel or in loader.conf help? http://www.freebsd.org/cgi/query-pr.cgi?pr=98346 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 12:50:28 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0085A16A415 for ; Tue, 19 Sep 2006 12:50:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8508C43D4C for ; Tue, 19 Sep 2006 12:50:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8JCoR5V093468 for ; Tue, 19 Sep 2006 12:50:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8JCoRnT093467; Tue, 19 Sep 2006 12:50:27 GMT (envelope-from gnats) Date: Tue, 19 Sep 2006 12:50:27 GMT Message-Id: <200609191250.k8JCoRnT093467@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: JoaoBR Cc: Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: JoaoBR List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 12:50:28 -0000 The following reply was made to PR amd64/98346; it has been noted by GNATS. From: JoaoBR To: bug-followup@freebsd.org, adhoniran.gomes@ig.com.br Cc: Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated Date: Tue, 19 Sep 2006 09:49:45 -0300 not my bug but I add something if allowed it does not matter if kbmux is compiled in or not on certain computers using releng_6 it seems to work know and on others sti= ll=20 not on certain computers then the caps-lock mecanism works but the led stays off probably related, sometimes the boot probe hangs atkbdc0: port 0x60,0x64 irq 1 on acpi0 <=3D=3Dexactly here, only power off resolve =2E.. atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] =2D-=20 Jo=E3o From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 16:55:59 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 7338816A407 for ; Tue, 19 Sep 2006 16:55:59 +0000 (UTC) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from sbexim0.cs.sunysb.edu (sbexim0.cs.sunysb.edu [130.245.1.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E9D43D72 for ; Tue, 19 Sep 2006 16:55:53 +0000 (GMT) (envelope-from ezk@agora.fsl.cs.sunysb.edu) Received: from agora.fsl.cs.sunysb.edu (agora.fsl.cs.sunysb.edu [130.245.126.12]) by sbexim0.cs.sunysb.edu (8.13.6/8.12.10) with ESMTP id k8JGtcHm020782; Tue, 19 Sep 2006 12:55:38 -0400 (EDT) Received: from agora.fsl.cs.sunysb.edu (localhost.localdomain [127.0.0.1]) by agora.fsl.cs.sunysb.edu (8.13.1/8.13.1) with ESMTP id k8JGtW7p021004; Tue, 19 Sep 2006 12:55:32 -0400 Received: (from ezk@localhost) by agora.fsl.cs.sunysb.edu (8.13.1/8.12.8/Submit) id k8JGtWRi021001; Tue, 19 Sep 2006 12:55:32 -0400 Date: Tue, 19 Sep 2006 12:55:32 -0400 Message-Id: <200609191655.k8JGtWRi021001@agora.fsl.cs.sunysb.edu> From: Erez Zadok To: Danny Braniss In-reply-to: Your message of "Tue, 19 Sep 2006 10:18:56 +0300." X-MailKey: Erez_Zadok Cc: Erez Zadok , Christos Zoulas , freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 [resend] 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, 19 Sep 2006 16:55:59 -0000 In message , Danny Braniss writes: > > Danny, try something simple first like turning off plock use in amd.conf: > > > > plock = no > > > > And let's see if Amd runs w/o trying any plock'ing first. > > > > Erez. > > does it have a command line equivalent? No. Many amd.conf options don't have command-line equivalents: there's just too many amd.conf options. > danny Erez. From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 19 18:13:04 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 7478916A40F for ; Tue, 19 Sep 2006 18:13:04 +0000 (UTC) (envelope-from christos@zoulas.com) Received: from rebar.astron.com (rebar.astron.com [38.117.134.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35F2A43D70 for ; Tue, 19 Sep 2006 18:13:03 +0000 (GMT) (envelope-from christos@zoulas.com) Received: by rebar.astron.com (Postfix, from userid 10080) id 00A7D56539; Tue, 19 Sep 2006 18:13:02 +0000 (UTC) From: christos@zoulas.com (Christos Zoulas) Date: Tue, 19 Sep 2006 14:13:02 -0400 In-Reply-To: <200609191655.k8JGtWRi021001@agora.fsl.cs.sunysb.edu> from Erez Zadok (Sep 19, 12:55pm) Organization: Astron Software X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Erez Zadok , Danny Braniss Message-Id: <20060919181303.00A7D56539@rebar.astron.com> Cc: freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 [resend] 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, 19 Sep 2006 18:13:04 -0000 On Sep 19, 12:55pm, ezk@cs.sunysb.edu (Erez Zadok) wrote: -- Subject: Re: mlockall() failes on amd64 [resend] | In message , Danny Braniss writes: | > > Danny, try something simple first like turning off plock use in amd.conf: | > > | > > plock = no | > > | > > And let's see if Amd runs w/o trying any plock'ing first. | > > | > > Erez. | > | > does it have a command line equivalent? | | No. Many amd.conf options don't have command-line equivalents: there's just | too many amd.conf options. It would be nice to add -O 'plock=no' etc. though :-) If -O is not taken that is. christos From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 20 06:20:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 12AB216A4A7 for ; Wed, 20 Sep 2006 06:20:22 +0000 (UTC) (envelope-from zspqrpiyqw@classifiedtoday.com) Received: from classifiedtoday.com (cmo116.neoplus.adsl.tpnet.pl [83.31.142.116]) by mx1.FreeBSD.org (Postfix) with SMTP id EDB5043D76 for ; Wed, 20 Sep 2006 06:20:18 +0000 (GMT) (envelope-from zspqrpiyqw@classifiedtoday.com) Received: from 83.31.142.116 by classifiedtoday.com Date: Wed, 20 Sep 2006 08:20:16 +0100 From: "nikki Alys" X-Sender: zspqrpiyqw@classifiedtoday.com To: Message-Id: <2967771762.RgozKqwYbNa-5018598-420801408@classifiedtoday.com> MIME-Version: 1.0 Content-Type: text/plain Subject: A tree does not move unless there is wind. 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, 20 Sep 2006 06:20:22 -0000 HOT ALERT - THIS ONE IS STILL CLIMBING THE CHARTS ALERT -- BREAKING MARKET NEWS REPORT ---- WBRS.PK Company Name: WILD BRUSH ENERGY Lookup: WBRS.PK Current Price: .05 Expected: STEADILY CLIMB FOR THE TOP Breaking News: Wild Brush Acquires Additional Powder River Oil & Gas Lease Wild Brush Energy (PINKSHEETS: WBRS) announces the purchase of an additional Powder River Basin Federal Oil & Gas Lease in the State of Wyoming. The lease is located on the eastern side of the Basin in Weston County. This is the fifth lease the Company now controls in the region. Wild Brush maintains its expansion strategy through acquisition of low risk, high probability oil and gas properties in proven regions such as Powder River basin. Wild Brush will continue to concentrate on the Powder River Basin area, due to the number of lease acre ages it currently controls. The Powder River Basin claims a high probability rate of discoveries and proven production as demonstrated by such companies as Chevron and Western Gas. There are presently over 12,000 gas wells, in addition to nearly 400 new wells monthly, producing over 330 billion cubic feet annually, in an area with an estimated 32 trillion cubic feet of natural gas. About WBRS.PK Wild Brush Energy is a diversified energy company whose primary goal is to identify and develop Oil & Coalbed Methane sites within the State of Wyoming. In addition, Wild Brush Energy continues to evaluate clean air alternative energy producing technologies such as Wind Power. Wild Brush trades in the U.S. under the symbol "WBRS." WATCH THIS STOCK GO HIGHER AND HIGHER -------------------------------------------------------------------------------- once you look you'll want to get in does 300% increase get your attention ----------------------- We'll cross that bridge when we come to it. What's good for the goose is good for the gander. Sweating blood. Useless as tits on bull. That's a whole new can of worms. When pigs fly. Tall as a tree. When we love - we grow. Throw pearls before swine. Shiver me timber. A rolling stone gathers no moss. This is for the birds. This is for the birds. The shoes on the other foot now. She's the apple of my eye. There's no time like the present. Put off the scent. Shake like a leaf. Useless as tits on bull. Salt of the Earth. She has a green thumb. You can't teach an old dog new tricks. Through the grapevine. That's a whole new can of worms. Save it for a rainy day. A stick in the mud. To gild refined gold, to paint the lily. Play a harp before a cow. Plant kindness and gather love. Stop, look and listen. A place in the sun. Where man is not nature is barren. Root it out. Say it with flowers. When pigs fly. Weed out. From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 09:59:54 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 68F9316A40F for ; Thu, 21 Sep 2006 09:59:54 +0000 (UTC) (envelope-from me@lmnk.de) Received: from mail2.lmnk.de (mail2.lmnk.de [212.79.196.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 106AE43D64 for ; Thu, 21 Sep 2006 09:59:52 +0000 (GMT) (envelope-from me@lmnk.de) Received: from [212.79.197.11] (helo=smtp.lmnk.de) by mail2.lmnk.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GQLLO-000KIs-6C for freebsd-amd64@freebsd.org; Thu, 21 Sep 2006 09:59:46 +0000 Received: from fw0-wis ([195.248.67.8] helo=[172.17.1.10]) by smtp.lmnk.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GQLLN-000K2a-GM for freebsd-amd64@freebsd.org; Thu, 21 Sep 2006 09:59:45 +0000 Message-ID: <45126297.8060303@lmnk.de> Date: Thu, 21 Sep 2006 11:59:51 +0200 From: Lars Mainka User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: TYAN Tempest I5000VS (S5372) 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, 21 Sep 2006 09:59:54 -0000 Hello! I'm playing around with the new TYAN Tempest I5000VS, two Intel Xeon 3.00 GHz Dual Core processors and FreeBSD6.1/amd64 Release - p7. When ACPI is enabled in BIOS, the system will not boot. With disabled ACPI, there will be only one cpu and an interrupt storm detected on IRQ11 (without any hint on which device), but the system boots completly. Some lines from dmesg: CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.52-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff,> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 ... acd0: Medium: no/blank disc Interrupt storm detected on "irq11:"; throttling interrupt source ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Can anyone help me, to make the other cpu detected, or does anyone know, if or when this chipset will be supported? Any suggestions wellcome! Thanx! Lars -- When God needs a new secure certificate, he uses Bruce Schneier as the signing authority. From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 10:00:11 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1656D16A407 for ; Thu, 21 Sep 2006 10:00:10 +0000 (UTC) (envelope-from me@warbird.tv) Received: from mail2.lmnk.de (mail2.lmnk.de [212.79.196.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F73343D5C for ; Thu, 21 Sep 2006 10:00:09 +0000 (GMT) (envelope-from me@warbird.tv) Received: from [212.79.197.11] (helo=smtp.lmnk.de) by mail2.lmnk.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GQLLk-000KJ2-Vi for freebsd-amd64@freebsd.org; Thu, 21 Sep 2006 10:00:09 +0000 Received: from fw0-wis ([195.248.67.8] helo=[172.17.1.10]) by smtp.lmnk.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GQLLk-000K39-9h for freebsd-amd64@freebsd.org; Thu, 21 Sep 2006 10:00:08 +0000 Message-ID: <451262AE.6000301@warbird.tv> Date: Thu, 21 Sep 2006 12:00:14 +0200 From: Lars Mainka User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: TYAN Tempest I5000VS (S5372) 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, 21 Sep 2006 10:00:11 -0000 Hello! I'm playing around with the new TYAN Tempest I5000VS, two Intel Xeon 3.00 GHz Dual Core processors and FreeBSD6.1/amd64 Release - p7. When ACPI is enabled in BIOS, the system will not boot. With disabled ACPI, there will be only one cpu and an interrupt storm detected on IRQ11 (without any hint on which device), but the system boots completly. Some lines from dmesg: CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.52-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff,> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 ... acd0: Medium: no/blank disc Interrupt storm detected on "irq11:"; throttling interrupt source ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Can anyone help me, to make the other cpu detected, or does anyone know, if or when this chipset will be supported? Any suggestions wellcome! Thanx! Lars From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 15:45:46 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 D176E16A412 for ; Thu, 21 Sep 2006 15:45:46 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AF8F43D46 for ; Thu, 21 Sep 2006 15:45:45 +0000 (GMT) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k8LFja3t051617; Thu, 21 Sep 2006 17:45:36 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.13.8/8.13.8/Submit) id k8LFjSY2051614; Thu, 21 Sep 2006 11:45:28 -0400 (EDT) (envelope-from cracauer) Date: Thu, 21 Sep 2006 11:45:28 -0400 From: Martin Cracauer To: Danny Braniss Message-ID: <20060921154528.GA51442@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: Christos Zoulas , freebsd-amd64@freebsd.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 15:45:46 -0000 Danny Braniss wrote on Sat, Sep 16, 2006 at 07:17:11PM +0300: > > On Sep 16, 2:55pm, danny@cs.huji.ac.il (Danny Braniss) wrote: > > -- Subject: mlockall() failes on amd64 > > > > | with am-utils 6.1.5, on a amd64 6.1-STABLE kernel i see: > > | Couldn't lock process pages in memory using mlockall() > > | while it's ok on a i386: > > | Locked process pages in memory > > | > > > > We should really fix amd to print the errno string when system calls > > fail; now we can only scratch our heads. > > > > christos > sorry, here is the full message: > Couldn't lock process pages in memory using mlockall(): Resource temporarily > unavailable > > or error = EAGAIN (ED :-) I didn't read the code, but one thing to check is that there is enough paging space to move all dirty/cow/anonymous pages from all other processes to to make room for your current process (including file-backed pages which might not yet be in). I imagine that on AMD64 some programs might overcommit much more since it's "free" (you won't run out of virtual address space). But mlockall will choke on it. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 19:52:55 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 8A62C16A4C8 for ; Thu, 21 Sep 2006 19:52:55 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate01.zdv.uni-mainz.de (mailgate01.zdv.Uni-Mainz.DE [134.93.178.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21B7E43D68 for ; Thu, 21 Sep 2006 19:52:43 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront02.zdv.uni-mainz.de ([134.93.176.56]) by mailgate01.zdv.uni-mainz.de with ESMTP; 21 Sep 2006 21:52:41 +0200 Received: from mail.uni-mainz.de ([134.93.176.49]) by exfront02.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Sep 2006 21:52:41 +0200 Received: from [192.168.1.128] ([85.178.26.45] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Sep 2006 21:52:40 +0200 Message-ID: <4512ED7F.1030400@mail.uni-mainz.de> Date: Thu, 21 Sep 2006 21:52:31 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Sep 2006 19:52:40.0883 (UTC) FILETIME=[7F29B030:01C6DDB7] Subject: FBSD 6.2-PRE/AMD64: two times SMBUS on ASUS A8N32-SLI? 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, 21 Sep 2006 19:52:55 -0000 Running FreeBSD 6.2-PRE/AMD64 on an ASUS A8N32-SLI shows up two smbus- interfaces as you can see in the short dmesg-excerpt. In kernel config there is only nfsmb mentioned, so I do not expect more than one smb-bus on that kind of motherboard. Can anyone explain this odd behaviour? Temperature- and fanspeed monitoring is still not possible, neither through ACPI, nor mbmon utility found in ports. Regards, Oliver -- nfsmb0: port 0xcc00-0xcc1f,0x600-0x63f,0x700-0x73f irq 20 at device 10.1 on pci 0 smbus0: on nfsmb0 smb0: on smbus0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 smb1: on smbus1 From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 20:22:48 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 879B016A403 for ; Thu, 21 Sep 2006 20:22:48 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from batman.home4u.ch (batman1.home4u.ch [217.8.211.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0D2C43D67 for ; Thu, 21 Sep 2006 20:22:44 +0000 (GMT) (envelope-from fabian@wenks.ch) Received: from [62.2.85.181] (flashback.wenks.ch [62.2.85.181]) (authenticated bits=0) by batman.home4u.ch (8.13.1/8.13.1) with ESMTP id k8LKMgH0023120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Sep 2006 22:22:43 +0200 (CEST) (envelope-from fabian@wenks.ch) Message-ID: <4512F48D.1060205@wenks.ch> Date: Thu, 21 Sep 2006 22:22:37 +0200 From: Fabian Wenk User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <45126297.8060303@lmnk.de> In-Reply-To: <45126297.8060303@lmnk.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: Re: TYAN Tempest I5000VS (S5372) 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, 21 Sep 2006 20:22:48 -0000 Hello Lars Lars Mainka wrote: > I'm playing around with the new TYAN Tempest I5000VS, two Intel Xeon 3.00 GHz Dual Core processors > and FreeBSD6.1/amd64 Release - p7. > > When ACPI is enabled in BIOS, the system will not boot. With disabled ACPI, there will be only one > cpu and an interrupt storm detected on IRQ11 (without any hint on which device), but the system > boots completly. I do not know exactly about your model of system board, but I have FreeBSD/i386 6.0 and 6.1 running on a Tyan S5360, but only with a single CPU. When I did the first install of FreeBSD/amd64 6.0-RELEASE and then later FreeBSD/i386 6.0-RELEASE on this board, I had to do this in "safe mode", else it did not even boot completely. Afterwards I set the following two options in /boot/loader.conf to normaly boot: hint.acpi.0.disabled="1" hint.apic.0.disabled="1" After upgrading to FreeBSD/i386 6.1-RELEASE I could remove them and it is running fine. Did not try with FreeBSD/amd64 again, as the tool for the used ICP-Vortex RAID controller are only available for i386. About the interrupt storm, I guess it could be a problem with the on board parallel port or maybe the usb. I did try a few things and in the end I change or set the following setting in the BIOS: - Advanced Installed O/S: [Other] Reset Configuration Data: [Yes] Large Disk Access Mode: [Other] > Advanced Chipset Control Integrated USB 1.1: [Disabled] > I/O Device Configuration Parallel port: [Enabled] Legacy USB Support: [Disabled] And I also did change the following in my kernel config, beside disabling all the H/W and other options I don't have or need anyway: # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da and also disabled all the USB stuff towards the end of the config file. Afterwards the problematic unknown IRQ11 was gone in the 'systat -vm 1' output. For using the second CPU on your board, I guess you need to build a kernel with SMP support. Informations are in /usr/src/sys/amd64/conf/SMP. Hope this helps. bye Fabian From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 21 20:26:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6461A16A403 for ; Thu, 21 Sep 2006 20:26:58 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9F0143D4C for ; Thu, 21 Sep 2006 20:26:57 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 07A1D5DB6; Fri, 22 Sep 2006 00:26:57 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id D98985D92; Fri, 22 Sep 2006 00:26:56 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8LKR0rd024165; Fri, 22 Sep 2006 00:27:00 +0400 (MSD) (envelope-from ru) Date: Fri, 22 Sep 2006 00:27:00 +0400 From: Ruslan Ermilov To: "O. Hartmann" Message-ID: <20060921202700.GE45341@rambler-co.ru> References: <4512ED7F.1030400@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2iBwrppp/7QCDedR" Content-Disposition: inline In-Reply-To: <4512ED7F.1030400@mail.uni-mainz.de> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-amd64@freebsd.org Subject: Re: FBSD 6.2-PRE/AMD64: two times SMBUS on ASUS A8N32-SLI? 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, 21 Sep 2006 20:26:58 -0000 --2iBwrppp/7QCDedR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 21, 2006 at 09:52:31PM +0200, O. Hartmann wrote: > Running FreeBSD 6.2-PRE/AMD64 on an ASUS A8N32-SLI shows up two smbus-=20 > interfaces as you can see in the short dmesg-excerpt. In kernel config=20 > there is only nfsmb mentioned, so I do not expect more than one smb-bus= =20 > on that kind of motherboard. > Can anyone explain this odd behaviour? >=20 NVIDIA nForce chips implement two SMBus controllers, master and slave. > Temperature- and fanspeed monitoring is still not possible, neither=20 > through ACPI, nor mbmon utility found in ports. >=20 Either because they don't have temperature sensors attached to SMBus, or most likely these sensor chips are not known to mbmon. mbmon is not actively developed nowadays. The lm-sensors project should be considered for adoptation if you want to add support for newer sensor/SMBus chips. > nfsmb0: port=20 > 0xcc00-0xcc1f,0x600-0x63f,0x700-0x73f irq 20 at device 10.1 on pci 0 > smbus0: on nfsmb0 > smb0: on smbus0 > nfsmb1: on nfsmb0 ^^^^^^ ^^^^^^^^^ > smbus1: on nfsmb1 > smb1: on smbus1 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --2iBwrppp/7QCDedR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFEvWUqRfpzJluFF4RAtbAAKCDfNnu6YoVIgFuFwVNOxdlZvz3RwCfUrdf a+q4Q7QAH0DUJQk3b5KUJ0U= =zckM -----END PGP SIGNATURE----- --2iBwrppp/7QCDedR-- From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 23 09:16:07 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4253716A747 for ; Sat, 23 Sep 2006 09:16:07 +0000 (UTC) (envelope-from fmhihbuflk@est.it) Received: from est.it (cjm79.neoplus.adsl.tpnet.pl [83.31.62.79]) by mx1.FreeBSD.org (Postfix) with SMTP id BCC3A43D53 for ; Sat, 23 Sep 2006 09:16:04 +0000 (GMT) (envelope-from fmhihbuflk@est.it) Date: Sat, 23 Sep 2006 11:16:04 +0100 From: "boothe Tildy" To: Cc: Message-Id: <1291012111.JWHBcKJG-6893-308398398@est.it> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Subject: Investor News 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, 23 Sep 2006 09:16:07 -0000 Company- A L L I A N C E E N T E R P R I S E Symbol - A E T R (Pink Sheets) C u r r e n t P r i c e: $ 0.48 Estimated Target - $ 2.00 + S T R O N G B U Y AE TR is undergoing a massive promotion and NOW is the time to get in. Add this Gem to your Watch list. Watch it Start a run monday About A L L I A N C E E N T E R P R I S E (.TaeCorp.) TaeCorp's vision is to be the recognized leader in providing Aerial Detection Systems including global de-mining, clearing a path to a safer planet for all humankind. TaeCorp's mission is to reclaim lands around the globe embedded with landmines that victimize countries and their stakeholders. N E W S TaeCorp Appoints TAM Oilfield Services as Representative in Sudan The A L L I A N C E E N T E R P R I S E Corporation ("TaeCorp") (AETR - News) is pleased to announce that it has appointed TAM Oilfield Services ("TAM"), of Khartoum, the capital of Sudan, as its representative to introduce and establish business relationships with oil and related companies interested in TaeCorp's unique landmine detection, location, mapping and removal systems and services. TAM Oilfield Services, established in 2001 under the laws and regulations of the Sudan government, has forged strong relationships with the leading petroleum companies that operate in the Sudan. "TAM's experience in the petroleum field, both with government and operating companies, will allow TaeCorp to 0ffer its services more efficiently and effectively and we are very pleased to have TAM join our team," says Ralph Proceviat, CFO of TaeCorp. Read more A C T N O W on this great news and get in before the move starts. When you get lemons, make lemonade.(When life gives you scraps make quilts.) Tall as a tree. Sow much, reap much; sow little, reap little. The way to a man's heart is through his stomach. There is always next year. A stick in the mud. You can lead a horse to water but you can't make him drink. Thick as a brick. Useless as tits on bull. Welcome to my garden. Top of the morning. Water under the bridge. Spring rain, Fall gold. Schools out for summer. Salt of the Earth. What goes down usually comes up. From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 23 09:27:00 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 CD3F316A47B; Sat, 23 Sep 2006 09:27:00 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate02.zdv.uni-mainz.de (mailgate02.zdv.Uni-Mainz.DE [134.93.178.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB88543D60; Sat, 23 Sep 2006 09:26:56 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront01.zdv.uni-mainz.de ([134.93.176.49]) by mailgate02.zdv.uni-mainz.de with ESMTP; 23 Sep 2006 11:26:55 +0200 Received: from mail.uni-mainz.de ([134.93.176.49]) by exfront01.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Sat, 23 Sep 2006 11:26:54 +0200 Received: from [192.168.1.128] ([85.178.18.198] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sat, 23 Sep 2006 11:26:54 +0200 Message-ID: <4514FDD1.70804@mail.uni-mainz.de> Date: Sat, 23 Sep 2006 11:26:41 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Jonathan Gray , freebsd-amd64@freebsd.org, freebsd-questions@freebsd.org References: <20060923061837.GA457@mail.netspace.net.au> In-Reply-To: <20060923061837.GA457@mail.netspace.net.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Sep 2006 09:26:54.0805 (UTC) FILETIME=[68C85850:01C6DEF2] Cc: Subject: Re: FBSD 6.2-PRE/AMD64: two times SMBUS on ASUS A8N32-SLI? 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, 23 Sep 2006 09:27:00 -0000 Jonathan Gray wrote: > The sensors are part of the Super-IO chip and appear in the ISA address space. > > On my A8N32-SLI board with OpenBSD I get > > it2 at isa0 port 0xd00/8: IT87 > > hw.sensors.0=it2, Fan1, 3154 RPM > hw.sensors.2=it2, Fan3, 767 RPM > hw.sensors.3=it2, VCORE_A, 1.41 V DC > hw.sensors.4=it2, VCORE_B, 4.08 V DC > hw.sensors.5=it2, +3.3V, 3.20 V DC > hw.sensors.6=it2, +5V, 4.95 V DC > hw.sensors.7=it2, +12V, 11.90 V DC > hw.sensors.8=it2, Unused, 4.05 V DC > hw.sensors.9=it2, -12V, 4.01 V DC > hw.sensors.10=it2, +5VSB, 6.85 V DC > hw.sensors.11=it2, VBAT, 3.10 V DC > hw.sensors.12=it2, Temp 1, 34.00 degC > hw.sensors.13=it2, Temp 2, 37.00 degC > hw.sensors.14=it2, Temp 3, 128.00 degC > > hw.vendor=ASUSTeK Computer INC. > hw.product=A8N32-SLI-Deluxe > Dear Jonathan. Thank you very much. FreeBSD 6.2-PRE amd64 does not show anything like you showed above, I regret. As I can see, OpenBSD already addressed the Super-IO chip on those boards while FreeBSD does obviously not - or there is a secret I havn't discovered yet. I'm a little bit confused by the Temp 3 value. What is connected to this sensor line? It looks strange, mearly 130 degree Celsius ... Regards, Oliver From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 23 16:53:32 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 9A85116A412; Sat, 23 Sep 2006 16:53:32 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29D3E43D79; Sat, 23 Sep 2006 16:53:31 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GRAkk-0005nJ-00; Sat, 23 Sep 2006 18:53:22 +0200 Date: Sat, 23 Sep 2006 18:53:22 +0200 To: "O. Hartmann" Message-ID: <20060923165322.GW4945@poupinou.org> References: <20060923061837.GA457@mail.netspace.net.au> <4514FDD1.70804@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4514FDD1.70804@mail.uni-mainz.de> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: Jonathan Gray , freebsd-amd64@freebsd.org, freebsd-questions@freebsd.org Subject: Re: FBSD 6.2-PRE/AMD64: two times SMBUS on ASUS A8N32-SLI? 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, 23 Sep 2006 16:53:32 -0000 On Sat, Sep 23, 2006 at 11:26:41AM +0200, O. Hartmann wrote: > I'm a little bit confused by the Temp 3 value. What is connected to this > sensor line? It looks strange, mearly 130 degree Celsius ... > More likely bit 8 is used for error. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.