From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 23:33:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C3A416A4CE; Sat, 26 Mar 2005 23:33:07 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C57143D1F; Sat, 26 Mar 2005 23:33:07 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 48BF151262; Sat, 26 Mar 2005 15:33:06 -0800 (PST) Date: Sat, 26 Mar 2005 15:33:06 -0800 From: Kris Kennaway To: Sean McNeil Message-ID: <20050326233305.GA41648@xor.obsecurity.org> References: <1111862662.3953.1.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <1111862662.3953.1.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i cc: jdp@FreeBSD.org cc: amd64@freebsd.org cc: obrien@FreeBSD.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 23:33:07 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 26, 2005 at 10:44:22AM -0800, Sean McNeil wrote: > With the introduction of a patch to net/cvsup, it will no longer work > for amd64: >=20 > ---> Upgrading 'cvsup-without-gui-16.1h' to 'cvsup-without-gui-16.1h_1' = (net/cvsup-without-gui) > ---> Building '/usr/ports/net/cvsup-without-gui' > =3D=3D=3D> Cleaning for cvsup-without-gui-16.1h_1 > =3D=3D=3D> Vulnerability check disabled, database not found > =3D=3D=3D> Extracting for cvsup-without-gui-16.1h_1 > =3D> Checksum OK for cvsup-without-gui.amd64.tar.bz2. > =3D=3D=3D> Patching for cvsup-without-gui-16.1h_1 > =3D=3D=3D> Applying FreeBSD patches for cvsup-without-gui-16.1h_1 > File to patch: This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. Ideally someone will rebuild the precompiled amd64 binary so it also has the bug fix. David, can you do this? Kris=20 --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRfExWry0BWjoQKURAo9TAJ0QBCil2jcV1Mh7GtXVA/cgRE4C8gCggPMX 443cAJHSHB+PY+/ZRdO2BqA= =CnDt -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 00:57:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E6E816A4CE; Sun, 27 Mar 2005 00:57:58 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA8D43D1F; Sun, 27 Mar 2005 00:57:57 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DFM6F-0001af-00; Sun, 27 Mar 2005 00:57:56 +0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Sun, 27 Mar 2005 00:57:55 +0000 From: Michael Hopkins To: , "freebsd-amd64@freebsd.org" Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Remote machine suddenly can't open X display X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 00:57:58 -0000 Hi all I have been happily connecting to a remote machine (with ssh -X -c blowfish) for 2 weeks and running X apps over the network. It has been working very well, but this afternoon I started getting messages like this: mwh@Athlon ~ % gedit & [1] 609 mwh@Athlon ~ % (gedit:609): Gtk-WARNING **: cannot open display: [1]+ Exit 1 gedit mwh@Athlon ~ % dx & [1] 610 mwh@Athlon ~ % Error: Can't open display: :0.0 [1]+ Exit 1 dx mwh@Athlon ~ % wish8.4 Application initialization failed: this isn't a Tk applicationcouldn't connect to display ":0.0" % mwh@Athlon ~ % ...and now I cannot run any X apps at all. I can't remember having made any controversial changes that would have caused this so I rebooted both my local machine (OS X laptop) and the remote server (FreeBSD 5.3p5 amd64) but no change. Can anyone advise me where to look to solve this problem? Error logs? Environment variables? (<- my local login .bash_profile contains DISPLAY=:0.0 and export DISPLAY as recommended). Diagnostic tools? TIA Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 01:31:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8C8E16A4CE for ; Sun, 27 Mar 2005 01:31:48 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A7243D2D for ; Sun, 27 Mar 2005 01:31:48 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DFMd1-000381-00 for freebsd-amd64@freebsd.org; Sun, 27 Mar 2005 02:31:47 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Sun, 27 Mar 2005 02:31:46 +0000 From: Michael Hopkins To: "freebsd-amd64@freebsd.org" Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: SSH login issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 01:31:48 -0000 Hi all Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64 server called Athlon? reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN ATTEMPT! It lets me in fine after I supply the password. TIA Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 02:36:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE60616A4CE; Sun, 27 Mar 2005 02:36:12 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6561643D46; Sun, 27 Mar 2005 02:36:12 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j2R2aB8A093825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Mar 2005 18:36:11 -0800 (PST) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id j2R2a9oK000282; Sat, 26 Mar 2005 18:36:09 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20050326233305.GA41648@xor.obsecurity.org> Date: Sat, 26 Mar 2005 18:36:09 -0800 (PST) From: John Polstra To: Kris Kennaway X-Bogosity: No, tests=bogofilter, spamicity=0.083988, version=0.14.5 cc: amd64@FreeBSD.org cc: obrien@FreeBSD.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 02:36:13 -0000 On 26-Mar-2005 Kris Kennaway wrote: > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. I would fix it if I knew how. All I did was add a patch; I wasn't expecting that to break anything. I didn't put in the binary-only amd64 stuff and I don't know how to fix it. If push comes to shove, I'll back out my commit and leave it at that. Johh From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 02:41:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18C5E16A4CE for ; Sun, 27 Mar 2005 02:41:46 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB12B43D46 for ; Sun, 27 Mar 2005 02:41:45 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so41170wra for ; Sat, 26 Mar 2005 18:41:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=tnOHuiHGIPzk45QWrEZ4gNACTkm7g9oTwkGiJKedSdDb2diNbDcn5eGF3ME7TGvAqKwJwfLqQpv+0wOaCD2ApbKfjn/VktHPzSnL04DEXwWRegaUAvTXRdlQS7y9SNkyaocjQ0UsxZkYRlsI5w29Kw2yGfJVQ3wS4BkdUwp948g= Received: by 10.54.33.61 with SMTP id g61mr320157wrg; Sat, 26 Mar 2005 18:41:45 -0800 (PST) Received: by 10.54.40.69 with HTTP; Sat, 26 Mar 2005 18:41:45 -0800 (PST) Message-ID: <2fd864e05032618419b6b2a5@mail.gmail.com> Date: Sat, 26 Mar 2005 18:41:45 -0800 From: Astrodog To: John Polstra In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050326233305.GA41648@xor.obsecurity.org> cc: amd64@freebsd.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 02:41:46 -0000 On Sat, 26 Mar 2005 18:36:09 -0800 (PST), John Polstra wrote: > On 26-Mar-2005 Kris Kennaway wrote: > > > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. > > I would fix it if I knew how. All I did was add a patch; I wasn't > expecting that to break anything. I didn't put in the binary-only > amd64 stuff and I don't know how to fix it. > > If push comes to shove, I'll back out my commit and leave it at > that. > > Johh What does the patch do? From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 03:20:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F9716A4D6 for ; Sun, 27 Mar 2005 03:20:04 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79F8943D41 for ; Sun, 27 Mar 2005 03:20:03 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from t30w.polstra.com (dsl081-189-078.sea1.dsl.speakeasy.net [64.81.189.78]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j2R3K2qo094147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp@mail.polstra.com) Received: from t30w.polstra.com (localhost [127.0.0.1]) by t30w.polstra.com (8.12.11/8.12.11) with ESMTP id j2R3K2d3000840; Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp@t30w.polstra.com) Received: (from jdp@localhost) by t30w.polstra.com (8.12.11/8.12.11/Submit) id j2R3K2Oc000839; Sat, 26 Mar 2005 19:20:02 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2fd864e05032618419b6b2a5@mail.gmail.com> Date: Sat, 26 Mar 2005 19:20:02 -0800 (PST) From: John Polstra To: Astrodog X-Bogosity: No, tests=bogofilter, spamicity=0.000912, version=0.14.5 cc: amd64@freebsd.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 03:20:04 -0000 On 27-Mar-2005 Astrodog wrote: > On Sat, 26 Mar 2005 18:36:09 -0800 (PST), John Polstra wrote: >> I would fix it if I knew how. All I did was add a patch; I wasn't >> expecting that to break anything. I didn't put in the binary-only >> amd64 stuff and I don't know how to fix it. >> >> If push comes to shove, I'll back out my commit and leave it at >> that. >> > What does the patch do? It fixes a bug that causes people's INDEX files to be deleted. The amd64 build is failing because it's binary-only, but it is still trying to apply the patch. John From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 08:00:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0750316A4CF for ; Sun, 27 Mar 2005 08:00:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17FF843D39 for ; Sun, 27 Mar 2005 08:00:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5D69B1FF91D; Sun, 27 Mar 2005 10:00:07 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 526891FF931; Sun, 27 Mar 2005 10:00:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 072F31538C; Sun, 27 Mar 2005 07:59:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id F01E615384; Sun, 27 Mar 2005 07:59:02 +0000 (UTC) Date: Sun, 27 Mar 2005 07:59:02 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John Polstra In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: amd64@freebsd.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 08:00:12 -0000 On Sat, 26 Mar 2005, John Polstra wrote: > On 27-Mar-2005 Astrodog wrote: > > On Sat, 26 Mar 2005 18:36:09 -0800 (PST), John Polstra wrote: > >> I would fix it if I knew how. All I did was add a patch; I wasn't > >> expecting that to break anything. I didn't put in the binary-only > >> amd64 stuff and I don't know how to fix it. > >> > >> If push comes to shove, I'll back out my commit and leave it at > >> that. > >> > > What does the patch do? > > It fixes a bug that causes people's INDEX files to be deleted. The > amd64 build is failing because it's binary-only, but it is still > trying to apply the patch. I will build a new binary during the day. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 13:02:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F48C16A4CE; Sun, 27 Mar 2005 13:02:19 +0000 (GMT) Received: from hotmail.com (bay2-dav13.bay2.hotmail.com [65.54.246.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5796643D31; Sun, 27 Mar 2005 13:02:19 +0000 (GMT) (envelope-from mwh_acs@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 27 Mar 2005 05:02:19 -0800 Message-ID: Received: from 83.216.132.201 by BAY2-DAV13.phx.gbl with DAV; Sun, 27 Mar 2005 13:02:18 +0000 X-Originating-IP: [83.216.132.201] X-Originating-Email: [mwh_acs@hotmail.com] X-Sender: mwh_acs@hotmail.com User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Sun, 27 Mar 2005 14:02:17 +0100 From: Michael To: "freebsd-amd64@freebsd.org" , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 27 Mar 2005 13:02:19.0256 (UTC) FILETIME=[35394F80:01C532CD] Subject: GNUStep broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 13:02:19 -0000 Hi all Wanting to do some cross-platform Objective-C development on OS X and FreeBSD amd64 5.3p5 but this is going to slow me down. ================================================================== ===> gnustep-make-1.10.0 depends on file: /usr/local/lib/gcc-lib/x86_64-portbl d-freebsd5.3/3.3.6/libobjc.so - not found ===> Verifying install for /usr/local/lib/gcc-lib/x86_64-portbld-freebsd5.3/3 3.6/libobjc.so in /usr/ports/lang/gcc-objc ===> gcc-objc-3.3.6_20050223 is marked as broken: Bus errors in stage2; system compiler may be broken.. *** Error code 1 Stop in /usr/ports/lang/gcc-objc. *** Error code 1 Stop in /usr/ports/devel/gnustep-make. *** Error code 1 Stop in /usr/ports/devel/gnustep. ===> gnustep-objc-1.3.0,1 does not run on ia64 amd64, and you are running amd64. ==================================================================== Is this something relatively easy to fix or will it cause grief? I am an experienced coder but new to FreeBSD and ports. Michael From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 13:43:34 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B233516A4CE for ; Sun, 27 Mar 2005 13:43:34 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0658243D39 for ; Sun, 27 Mar 2005 13:43:34 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IE0000MLJ789O80@bgo1smout1.broadpark.no> for amd64@freebsd.org; Sun, 27 Mar 2005 15:37:56 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IE00047NJJ3X070@bgo1sminn1.broadpark.no> for amd64@freebsd.org; Sun, 27 Mar 2005 15:45:03 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id BF3B2BDC5E; Sun, 27 Mar 2005 15:43:27 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 57E4CBDC4B; Sun, 27 Mar 2005 15:43:23 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 4A67933C3E; Sun, 27 Mar 2005 15:43:23 +0200 (CEST) Date: Sun, 27 Mar 2005 15:43:23 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: To: Danny Braniss Message-id: <86k6ntw6f8.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: amd64@freebsd.org Subject: Re: INCLUDE_CONFIG_FILE broken? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 13:43:34 -0000 Danny Braniss writes: > it seems that options INCLUDE_CONFIG_FILE in the kernel conf. file > does not work: > > strings -n 3 /boot/kernel/kernel | sed -n 's/^___//p' > _````QQQQ > _ > The compiler optimizes it away because it's declared static. I have no idea why this wasn't a problem before; probably a change in compiler flags or in the compiler itself. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 13:55:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AE6A16A4CE for ; Sun, 27 Mar 2005 13:55:09 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 147F343D39 for ; Sun, 27 Mar 2005 13:55:09 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IE00004UJQA9O90@bgo1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 27 Mar 2005 15:49:22 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IE0004DAK25X870@bgo1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 27 Mar 2005 15:56:29 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id 149FC9F4F9; Sun, 27 Mar 2005 15:54:54 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id A9693BDC60; Sun, 27 Mar 2005 15:54:49 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id A04ED33C3E; Sun, 27 Mar 2005 15:54:49 +0200 (CEST) Date: Sun, 27 Mar 2005 15:54:49 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: <4245D504.9040004@mail.uni-mainz.de> To: "O. Hartmann" Message-id: <86fyyhw5w6.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <4245D504.9040004@mail.uni-mainz.de> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: freebsd-amd64@freebsd.org Subject: Re: ASUS A8N-SLI Deluxe FreeBSD 5.4-Beta problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 13:55:09 -0000 "O. Hartmann" writes: > Booting from installation CDROM is not possible until acpi gets > disabled and this stays so when already did make world / new kernel > with a most recent CTM set of the kernel stuff. Try to remove NO_MIXED_MODE from your kernel config, and see if it boots with ACPI enabled. > I read some time ago about nVidia nForce3/4 issues and I wonder that > this is still status quo. The nForce 3 chipset is fairly well supported, while nForce 4 is still too new. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 15:44:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E755716A4CE for ; Sun, 27 Mar 2005 15:44:41 +0000 (GMT) Received: from smtp808.mail.sc5.yahoo.com (smtp808.mail.sc5.yahoo.com [66.163.168.187]) by mx1.FreeBSD.org (Postfix) with SMTP id 9FABF43D2F for ; Sun, 27 Mar 2005 15:44:41 +0000 (GMT) (envelope-from rwideman@sbcglobal.net) Received: from unknown (HELO ?192.168.0.102?) (rwideman@sbcglobal.net@66.143.142.211 with plain) by smtp808.mail.sc5.yahoo.com with SMTP; 27 Mar 2005 15:44:41 -0000 Message-ID: <4246D5B0.309@sbcglobal.net> Date: Sun, 27 Mar 2005 09:48:00 -0600 From: Robert Wideman User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050325) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 32 bit compatibility on FreeBSD 5.3 Amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 15:44:42 -0000 I'm running FreeBSD 5.3-Release AMD64 version. When I try to compile my source that im writing for 32 bit compatibility I receive errors. gcc -m32 ERROR: '/usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc' Ive read that 5.3 has problems with 32 bit compatibility and that 5.4 should resolve this. Does anyone know of a workaround on this? From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 16:45:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7939D16A4CE for ; Sun, 27 Mar 2005 16:45:48 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E41D43D48 for ; Sun, 27 Mar 2005 16:45:48 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j2RGjmN1097365; Sun, 27 Mar 2005 08:45:48 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j2RGjlWm097364; Sun, 27 Mar 2005 08:45:47 -0800 (PST) (envelope-from sgk) Date: Sun, 27 Mar 2005 08:45:47 -0800 From: Steve Kargl To: Robert Wideman Message-ID: <20050327164547.GA97330@troutmask.apl.washington.edu> References: <4246D5B0.309@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4246D5B0.309@sbcglobal.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: 32 bit compatibility on FreeBSD 5.3 Amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 16:45:48 -0000 On Sun, Mar 27, 2005 at 09:48:00AM -0600, Robert Wideman wrote: > I'm running FreeBSD 5.3-Release AMD64 version. When I try to compile my > source that im writing for 32 bit compatibility I receive errors. > > gcc -m32 > I don't think you can use the -m32 multilib options, yet. AMD64 has compatibility for *running* 32-bit binaries. It does not have 32-bit *building* capabilities. > Ive read that 5.3 has problems with 32 bit compatibility and that 5.4 > should resolve this. Does anyone know of a workaround on this? 32-bit compatibility for executions appears to work fine on my system. One work-around you can use is to actually use a 32-bit system to build your software. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 18:35:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0635316A4CE for ; Sun, 27 Mar 2005 18:35:49 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8759143D2F for ; Sun, 27 Mar 2005 18:35:48 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from [66.92.151.195] (july.chuckr.org [66.92.151.195]) by april.chuckr.org (Postfix) with ESMTP id 7342111F96; Sun, 27 Mar 2005 13:33:54 -0500 (EST) Message-ID: <4246FC58.3050005@chuckr.org> Date: Sun, 27 Mar 2005 18:32:56 +0000 From: Chuck Robey User-Agent: Mozilla Thunderbird 1.0 (X11/20050316) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Hopkins References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: "freebsd-amd64@freebsd.org" Subject: Re: SSH login issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 18:35:49 -0000 Michael Hopkins wrote: > > Hi all > > Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64 > server called Athlon? > > reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN > ATTEMPT! > > It lets me in fine after I supply the password. ssh caches info on the servers that you connect to, and stores that info in ~/.ssh/known_hosts, so if you're getting that message, and you decide that there's no security problem (ssh giving you a false alarm) then just take your favorite editor onto that file, and edit out the lines that refer to the server. It hasn't got any sensitivity to "Athlon" built in, but it's trying to help you out and tell you about servers that have info that changes alarmingly. > > TIA > > Michael > > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > _/ _/ _/_/_/ Hopkins Research Ltd > _/ _/ _/ _/ > _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ > _/ _/ _/ _/ > _/ _/ _/ _/ 'touch the future' > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > > _______________________________________________ > 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 Sun Mar 27 18:51:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F23E16A4CE; Sun, 27 Mar 2005 18:51:23 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C293D43D5A; Sun, 27 Mar 2005 18:51:22 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j2RIpMD6099511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Mar 2005 10:51:22 -0800 (PST) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id j2RIpLT8014305; Sun, 27 Mar 2005 10:51:21 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20050326233305.GA41648@xor.obsecurity.org> Date: Sun, 27 Mar 2005 10:51:21 -0800 (PST) From: John Polstra To: Kris Kennaway X-Bogosity: No, tests=bogofilter, spamicity=0.017101, version=0.14.5 cc: amd64@FreeBSD.org cc: obrien@FreeBSD.org Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 18:51:23 -0000 On 26-Mar-2005 Kris Kennaway wrote: > On Sat, Mar 26, 2005 at 10:44:22AM -0800, Sean McNeil wrote: >> With the introduction of a patch to net/cvsup, it will no longer work >> for amd64: >> >> ---> Upgrading 'cvsup-without-gui-16.1h' to 'cvsup-without-gui-16.1h_1' >> (net/cvsup-without-gui) >> ---> Building '/usr/ports/net/cvsup-without-gui' >> ===> Cleaning for cvsup-without-gui-16.1h_1 >> ===> Vulnerability check disabled, database not found >> ===> Extracting for cvsup-without-gui-16.1h_1 >> => Checksum OK for cvsup-without-gui.amd64.tar.bz2. >> ===> Patching for cvsup-without-gui-16.1h_1 >> ===> Applying FreeBSD patches for cvsup-without-gui-16.1h_1 >> File to patch: > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. Could one of you amd64 folks please try this patch for ports/net/cvsup/Makefile and let me know if it fixes the build of the port? Index: Makefile =================================================================== RCS file: /home/ncvs/ports/net/cvsup/Makefile,v retrieving revision 1.58 diff -u -r1.58 Makefile --- Makefile 25 Mar 2005 21:38:06 -0000 1.58 +++ Makefile 27 Mar 2005 18:48:47 -0000 @@ -86,6 +86,9 @@ .if ${ARCH} == "amd64" PROGS= bin/cvsup sbin/cvsupd bin/cvpasswd +do-patch: + @${TRUE} + do-configure: @${TOUCH} ${WRKSRC}/License @${TOUCH} ${TOUCH_FLAGS} ${CONFIGURE_COOKIE} Thanks, John From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 18:59:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1606216A4CE for ; Sun, 27 Mar 2005 18:59:54 +0000 (GMT) Received: from smartmx-01.inode.at (smartmx-01.inode.at [213.229.60.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7988143D39 for ; Sun, 27 Mar 2005 18:59:53 +0000 (GMT) (envelope-from cassini@inode.at) Received: from [81.223.23.66] (port=37426 helo=[192.168.0.2]) by smartmx-01.inode.at with asmtp (Exim 4.34) id 1DFczI-0004Ai-6T for freebsd-amd64@freebsd.org; Sun, 27 Mar 2005 20:59:52 +0200 From: Bernd Malle To: freebsd-amd64@freebsd.org Date: Sun, 27 Mar 2005 20:59:52 +0200 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503272059.52778.cassini@inode.at> Subject: cassini@inode.at X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cassini@inode.at List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 18:59:54 -0000 From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 19:06:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 263CF16A4CE; Sun, 27 Mar 2005 19:06:58 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67EEB43D31; Sun, 27 Mar 2005 19:06:57 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 18E181FF931; Sun, 27 Mar 2005 21:06:55 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id E60391FF91D; Sun, 27 Mar 2005 21:06:52 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 335E3157E5; Sun, 27 Mar 2005 19:06:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 27019153C4; Sun, 27 Mar 2005 19:06:46 +0000 (UTC) Date: Sun, 27 Mar 2005 19:06:46 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John Polstra In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: amd64@FreeBSD.org cc: obrien@FreeBSD.org cc: Kris Kennaway Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 19:06:58 -0000 On Sun, 27 Mar 2005, John Polstra wrote: > On 26-Mar-2005 Kris Kennaway wrote: > > On Sat, Mar 26, 2005 at 10:44:22AM -0800, Sean McNeil wrote: > >> With the introduction of a patch to net/cvsup, it will no longer work > >> for amd64: > >> > >> ---> Upgrading 'cvsup-without-gui-16.1h' to 'cvsup-without-gui-16.1h_1' > >> (net/cvsup-without-gui) > >> ---> Building '/usr/ports/net/cvsup-without-gui' > >> ===> Cleaning for cvsup-without-gui-16.1h_1 > >> ===> Vulnerability check disabled, database not found > >> ===> Extracting for cvsup-without-gui-16.1h_1 > >> => Checksum OK for cvsup-without-gui.amd64.tar.bz2. > >> ===> Patching for cvsup-without-gui-16.1h_1 > >> ===> Applying FreeBSD patches for cvsup-without-gui-16.1h_1 > >> File to patch: > > > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. > > Could one of you amd64 folks please try this patch for > ports/net/cvsup/Makefile and let me know if it fixes the build of the > port? yes, it does. bz@amd64:/usr/ports/net/cvsup> make ===> Vulnerability check disabled, database not found ***************************************************** * To build CVSup without X11 (and without the GUI), * * use the "net/cvsup-without-gui" port. * ***************************************************** >> cvsup-without-gui.amd64.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/. cvsup-without-gui.amd64.tar.bz2 100% of 327 kB 109 kBps ===> Extracting for cvsup-16.1h_1 >> Checksum OK for cvsup-without-gui.amd64.tar.bz2. ===> Patching for cvsup-16.1h_1 ===> Configuring for cvsup-16.1h_1 bz@amd64:/usr/ports/net/cvsup> -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 19:09:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0531516A4CE; Sun, 27 Mar 2005 19:09:00 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6A343D46; Sun, 27 Mar 2005 19:08:59 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j2RJ8wJA099617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Mar 2005 11:08:59 -0800 (PST) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id j2RJ8wne014355; Sun, 27 Mar 2005 11:08:58 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 27 Mar 2005 11:08:58 -0800 (PST) From: John Polstra To: "Bjoern A. Zeeb" X-Bogosity: No, tests=bogofilter, spamicity=0.017467, version=0.14.5 cc: amd64@FreeBSD.org cc: obrien@FreeBSD.org cc: Kris Kennaway Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 19:09:00 -0000 On 27-Mar-2005 Bjoern A. Zeeb wrote: >> Could one of you amd64 folks please try this patch for >> ports/net/cvsup/Makefile and let me know if it fixes the build of the >> port? > > yes, it does. Thanks! I'll commit that to unbreak the build, then. John From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 19:10:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40C8016A4CE; Sun, 27 Mar 2005 19:10:45 +0000 (GMT) Received: from falcon.loomes.de (smtp.loomes.de [212.40.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31F8743D39; Sun, 27 Mar 2005 19:10:44 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from port-212-202-35-78.dynamic.qsc.de ([212.202.35.78] helo=bsd.trippelsdorf.de) by falcon.loomes.de with asmtp (Exim 4.30) id 1DFd9g-00020p-Hm; Sun, 27 Mar 2005 21:10:36 +0200 Date: Sun, 27 Mar 2005 21:10:35 +0200 From: Markus Trippelsdorf To: John Polstra Message-ID: <20050327191035.GA2703@bsd.trippelsdorf.de> References: <20050326233305.GA41648@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: amd64@FreeBSD.org cc: obrien@FreeBSD.org cc: Kris Kennaway Subject: Re: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 19:10:45 -0000 On Sun, Mar 27, 2005 at 10:51:21AM -0800, John Polstra wrote: > On 26-Mar-2005 Kris Kennaway wrote: > > On Sat, Mar 26, 2005 at 10:44:22AM -0800, Sean McNeil wrote: > >> With the introduction of a patch to net/cvsup, it will no longer work > >> for amd64: > >> > >> ---> Upgrading 'cvsup-without-gui-16.1h' to 'cvsup-without-gui-16.1h_1' > >> (net/cvsup-without-gui) > >> ---> Building '/usr/ports/net/cvsup-without-gui' > >> ===> Cleaning for cvsup-without-gui-16.1h_1 > >> ===> Vulnerability check disabled, database not found > >> ===> Extracting for cvsup-without-gui-16.1h_1 > >> => Checksum OK for cvsup-without-gui.amd64.tar.bz2. > >> ===> Patching for cvsup-without-gui-16.1h_1 > >> ===> Applying FreeBSD patches for cvsup-without-gui-16.1h_1 > >> File to patch: > > > > This will obviously need to be fixed ASAP for the 5.4-RELEASE builds. > > Could one of you amd64 folks please try this patch for > ports/net/cvsup/Makefile and let me know if it fixes the build of the > port? It's working fine now (thank you): root cvsup # make ===> Vulnerability check disabled, database not found ***************************************************** * To build CVSup without X11 (and without the GUI), * * use the "net/cvsup-without-gui" port. * ***************************************************** => cvsup-without-gui.amd64.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/. cvsup-without-gui.amd64.tar.bz2 100% of 327 kB 54 kBps ===> Extracting for cvsup-16.1h_1 => Checksum OK for cvsup-without-gui.amd64.tar.bz2. ===> Patching for cvsup-16.1h_1 ===> Configuring for cvsup-16.1h_1 -- Markus From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 20:26:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1786F16A4CE; Sun, 27 Mar 2005 20:26:11 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AFA43D39; Sun, 27 Mar 2005 20:26:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BC81F5337A; Sun, 27 Mar 2005 12:26:09 -0800 (PST) Date: Sun, 27 Mar 2005 12:26:09 -0800 From: Kris Kennaway To: Michael Message-ID: <20050327202607.GA66339@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: GNUStep broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 20:26:11 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 27, 2005 at 02:02:17PM +0100, Michael wrote: > =3D=3D=3D> gnustep-objc-1.3.0,1 does not run on ia64 amd64, and you are = running > amd64. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Is this something relatively easy to fix or will it cause grief? I am an > experienced coder but new to FreeBSD and ports. Try commenting out the ONLY_FOR_ARCHS/BROKEN and see what breaks, then try to fix it :) Talk to the developers of the software if you need more help. Kris --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRxbfWry0BWjoQKURAsM9AKCiiATAdzDQYrkIXFZ5Ihxsdm1FlACeMWvo Dw23trsPmiV7Ylm8KNe0XsE= =8ED0 -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 04:41:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB96516A4CE; Mon, 28 Mar 2005 04:41:58 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3786343D4C; Mon, 28 Mar 2005 04:41:58 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j2S4fvPP079149; Sun, 27 Mar 2005 23:41:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j2S4fvhl007898; Sun, 27 Mar 2005 23:41:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4D7707306E; Sun, 27 Mar 2005 23:41:57 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050328044157.4D7707306E@freebsd-current.sentex.ca> Date: Sun, 27 Mar 2005 23:41:57 -0500 (EST) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 04:41:59 -0000 TB --- 2005-03-28 03:15:49 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-03-28 03:15:49 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-03-28 03:15:49 - checking out the source tree TB --- 2005-03-28 03:15:49 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-03-28 03:15:49 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-03-28 03:22:36 - building world (CFLAGS=-O2 -pipe) TB --- 2005-03-28 03:22:36 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-28 03:22:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-03-28 04:30:22 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-03-28 04:30:22 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-28 04:30:22 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Mar 28 04:30:23 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function `KfAcquireSpinLock': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:299: error: `KefAcquireSpinLockAtDpcLevel' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:299: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:299: error: for each function it appears in.) /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function `KfReleaseSpinLock': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:307: error: `KefReleaseSpinLockFromDpcLevel' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-03-28 04:41:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-03-28 04:41:57 - ERROR: failed to build generic kernel TB --- 2005-03-28 04:41:57 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 09:13:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C48FF16A4CE for ; Mon, 28 Mar 2005 09:13:17 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8EA243D5C for ; Mon, 28 Mar 2005 09:13:15 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id 90633BDCE; Mon, 28 Mar 2005 12:13:05 +0200 (EET) Received: from [192.168.150.107] (localhost [127.0.0.1]) by mail.komvista.lt (Postfix) with ESMTP id 9F235BDCA for ; Mon, 28 Mar 2005 12:13:03 +0200 (EET) Message-ID: <4247CAA3.90804@komvista.lt> Date: Mon, 28 Mar 2005 12:13:07 +0300 From: Stasys Smailys User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[FreeBSD-AMD64]" Content-Type: multipart/mixed; boundary="------------060405060408090009070802" Subject: Re: Problem Report amd64/78848 "sis driver on FreeBSD 5.x does not work on amd64" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 09:13:18 -0000 This is a multi-part message in MIME format. --------------060405060408090009070802 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello there! I've had the same problem with SiS 755 and SiS 964 on ASRock K8S8X, the only difference was that MAC address had all zeros (00:00:00:00:00:00). The problem is that integrated NIC doesn't have any eeprom to read from. I solved it by applying this patch. As by now it works for me. AFAIK it is not solved properly even in -CURRENT. By the way I noticed some typo in /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c and /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c. IMHO when calling sysarch(int, void *) it should look like this: /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: [...] ret = sysarch(_AMD64_GET_FSBASE, (void *)(&addr64)); [...] /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c: [...] ret = sysarch(_AMD64_GET_GSBASE, (void *)(&addr64)); [...] WBR, Stasys Smailys --------------060405060408090009070802 Content-Type: text/plain; name="if_sis.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_sis.c.patch" --- /usr/src/sys/pci/if_sis.c.orig Thu Mar 3 06:16:17 2005 +++ /usr/src/sys/pci/if_sis.c Sat Mar 26 09:25:54 2005 @@ -139,7 +139,7 @@ static void sis_eeprom_putbyte (struct sis_softc *, int); static void sis_eeprom_getword (struct sis_softc *, int, u_int16_t *); static void sis_read_eeprom (struct sis_softc *, caddr_t, int, int, int); -#ifdef __i386__ +#if defined(__i386__) || defined(__amd64__) static void sis_read_cmos (struct sis_softc *, device_t, caddr_t, int, int); static void sis_read_mac (struct sis_softc *, device_t, caddr_t); @@ -418,7 +418,7 @@ return; } -#ifdef __i386__ +#if defined(__i386__) || defined(__amd64__) static device_t sis_find_bridge(dev) device_t dev; @@ -476,7 +476,11 @@ pci_write_config(bridge, 0x48, reg|0x40, 1); /* XXX */ +#if defined(__i386__) btag = I386_BUS_SPACE_IO; +#elif defined(__amd64__) + btag = AMD64_BUS_SPACE_IO; +#endif for (i = 0; i < cnt; i++) { bus_space_write_1(btag, 0x0, 0x70, i + off); @@ -1144,7 +1148,7 @@ break; case SIS_VENDORID: default: -#ifdef __i386__ +#if defined(__i386__) || defined(__amd64__) /* * If this is a SiS 630E chipset with an embedded * SiS 900 controller, we have to read the MAC address @@ -1603,7 +1607,7 @@ } /* No errors; receive the packet. */ -#ifdef __i386__ +#if defined(__i386__) || defined(__amd64__) /* * On the x86 we do not have alignment problems, so try to * allocate a new buffer for the receive ring, and pass up --------------060405060408090009070802 Content-Type: text/plain; name="_amd64_get_fsbase.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="_amd64_get_fsbase.c.patch" --- /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c.orig Sat Nov 27 22:24:31 2004 +++ /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c Thu Mar 24 23:16:48 2005 @@ -37,7 +37,7 @@ int ret; addr64 = 0; - ret = sysarch(_AMD64_GET_FSBASE, (void **)(&addr64)); + ret = sysarch(_AMD64_GET_FSBASE, (void *)(&addr64)); if (ret != -1) *addr = (void *)(uintptr_t)addr64; return ret; --------------060405060408090009070802 Content-Type: text/plain; name="_amd64_get_gsbase.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="_amd64_get_gsbase.c.patch" --- /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c.orig Sat Nov 27 22:24:31 2004 +++ /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c Thu Mar 24 23:16:51 2005 @@ -37,7 +37,7 @@ int ret; addr64 = 0; - ret = sysarch(_AMD64_GET_GSBASE, (void **)(&addr64)); + ret = sysarch(_AMD64_GET_GSBASE, (void *)(&addr64)); if (ret != -1) *addr = (void *)(uintptr_t)addr64; return ret; --------------060405060408090009070802-- From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 11:01:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E89A16A4D0 for ; Mon, 28 Mar 2005 11:01:35 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 391D943D31 for ; Mon, 28 Mar 2005 11:01:35 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2SB1YOJ035387 for ; Mon, 28 Mar 2005 11:01:34 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2SB1XIr035382 for freebsd-amd64@freebsd.org; Mon, 28 Mar 2005 11:01:33 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 28 Mar 2005 11:01:33 GMT Message-Id: <200503281101.j2SB1XIr035382@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 11:01:35 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/10] amd64/78677 amd64 IPSEC causes panic on AMD64 FreeBSD >5.2. o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o 23 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 o [2005/02/13] amd64/77470 amd64 Using of cyrillic filenames conversion le o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build 10 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 12:24:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5E1A16A4CE for ; Mon, 28 Mar 2005 12:24:38 +0000 (GMT) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6449943D48 for ; Mon, 28 Mar 2005 12:24:38 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id C140D11699; Mon, 28 Mar 2005 14:26:40 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37769-06; Mon, 28 Mar 2005 14:26:34 +0200 (CEST) Received: from [192.168.42.2] (gatecrasher.xbsd.org [192.168.42.2]) by smtp.xbsd.org (Postfix) with ESMTP id B521B11440; Mon, 28 Mar 2005 14:26:33 +0200 (CEST) Message-ID: <4247F777.5080708@xbsd.org> Date: Mon, 28 Mar 2005 14:24:23 +0200 From: Florent Thoumie User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: fr, en MIME-Version: 1.0 To: "O. Hartmann" References: <4245D504.9040004@mail.uni-mainz.de> In-Reply-To: <4245D504.9040004@mail.uni-mainz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at xbsd.org cc: freebsd-amd64@freebsd.org Subject: Re: ASUS A8N-SLI Deluxe FreeBSD 5.4-Beta problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 12:24:38 -0000 O. Hartmann a écrit : > Dear Sirs. > I just tried to install a most recent set of FreeBSD > 5.4-PRERELEASE/5.4-BETA1 on an ASUS A8N-SLI Deluxe mobo. The system has > a Maxtor 6B200M0 200GB harddisk attached to the nForce4 SATA connector > (due to NCQ) and a NEC 3500AG DVD+RW attached to the nForce4 ATA133 > connector. > Booting from installation CDROM is not possible until acpi gets disabled > and this stays so when already did make world / new kernel with a most > recent CTM set of the kernel stuff. > It seems that FreeBSD does not know much about the SATA/SATA2 controller > (it shows up as ATA Generic). The harddisk shows up as UDMA33 drive > (like the DVDRW). > Performance is crude, copying from DVD while compiling makes the system > hang for some seconds on console. > > Sorry, I'm not connected to the net with that machine so I lack in > dmesg-output. > > I read some time ago about nVidia nForce3/4 issues and I wonder that > this is still status quo. > > Compiling kernel without "atpic" seems to leave the operating system > inoperable, ACPI seems not to work. My question is whether FreeBSD 5.4 > will support this type of hardware or maybe 5.5 or will FreeBSD not > support this? > > Sorry bothering somebody around here, maybe this has been completely > discussed here but I do not read regularily this mailing list. > > Can someone send me hints/tips for a fast kerl config and say something > about the trapdoors? I'm not sure what's wrong with your configuration but I have this motherboard and had no problems with 5.3-R (except acpi and broken sk(4) which is resolved now). -- Florent Thoumie flz@xbsd.org From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 16:25:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99F6316A4CE; Mon, 28 Mar 2005 16:25:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 718D343D2F; Mon, 28 Mar 2005 16:25:17 +0000 (GMT) (envelope-from jdp@FreeBSD.org) Received: from freefall.freebsd.org (jdp@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2SGPHC1004972; Mon, 28 Mar 2005 16:25:17 GMT (envelope-from jdp@freefall.freebsd.org) Received: (from jdp@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2SGPHp5004968; Mon, 28 Mar 2005 16:25:17 GMT (envelope-from jdp) Date: Mon, 28 Mar 2005 16:25:17 GMT From: John Polstra Message-Id: <200503281625.j2SGPHp5004968@freefall.freebsd.org> To: jdp@FreeBSD.org, jdp@FreeBSD.org, amd64@FreeBSD.org Subject: Re: ports/75015: cvsup on amd64 with runsocks (socks5) coredumps X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 16:25:17 -0000 Synopsis: cvsup on amd64 with runsocks (socks5) coredumps Responsible-Changed-From-To: jdp->amd64 Responsible-Changed-By: jdp Responsible-Changed-When: Mon Mar 28 16:23:17 GMT 2005 Responsible-Changed-Why: Thanks for the report, but I have no idea how to fix this and I don't have an amd64 system to attempt it. The amd64 support for CVSup is very spotty; it's a miracle it works at all. I'm reassigning this bug to amd64@freebsd.org. http://www.freebsd.org/cgi/query-pr.cgi?pr=75015 From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 17:43:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0991F16A4CE for ; Mon, 28 Mar 2005 17:43:49 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4851F43D41 for ; Mon, 28 Mar 2005 17:43:46 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2SHhhbj094658; Mon, 28 Mar 2005 12:43:44 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 28 Mar 2005 12:43:37 -0500 User-Agent: KMail/1.6.2 References: <20050208163758.GA1086@NitroPhys.welchsmnet.net> <200502081156.51114.nb_root@videotron.ca> <200503261117.29939.nb_root@videotron.ca> In-Reply-To: <200503261117.29939.nb_root@videotron.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503281243.37327.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/791/Sat Mar 26 17:26:49 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: Compaq R3000Z keyboard doesn't work without DSDT patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 17:43:49 -0000 On Saturday 26 March 2005 11:17 am, Nicolas Blais wrote: > Hi, > > Without the following lines in loader.conf: > acpi_dsdt_load="YES" > acpi_dsdt_name="/boot/DSDT.aml" > > and of course in device.hints: > hint.atkbd.0.flags="0x9" > > and Jung-uk Kim's r3000z-asl.diff found on this list, my keyboard > not work at all but the booting process is fine and I can move my > mouse, log on thru ssh etc... > > I was under the impression that 5.4 would be "R3000 friendly" and > that the only things needed were hint.atkbd.0.flags="0x9" in > device.hints and the powernow module (which stays at 800mhz while > acpi_ppc works). Is there something I'm doing wrong? You are not doing anything wrong. The real problem is the BIOS is so broken that some problems cannot be worked around. :-( Keyboard resource is overlapped with something else. We cannot fix all problems without breaking other platforms, unfortunately. Jung-uk Kim > Thanks, > Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 17:47:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C3016A4CE for ; Mon, 28 Mar 2005 17:47:59 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 110BE43D53 for ; Mon, 28 Mar 2005 17:47:59 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2SHlufb094785; Mon, 28 Mar 2005 12:47:57 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 28 Mar 2005 12:47:50 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <200503261054.14614.nb_root@videotron.ca> In-Reply-To: <200503261054.14614.nb_root@videotron.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503281247.50186.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/791/Sat Mar 26 17:26:49 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 17:47:59 -0000 On Saturday 26 March 2005 10:54 am, Nicolas Blais wrote: > On March 21, 2005 10:49, Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > I was wondering if the R3000Z fixes have been committed to the > > > RELENG_5 branch, I don't see anything on the lists about it. > > > Should I expect 5.4 to work with the R3000 line? > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > latest snapshot and let us know. > > > > Thanks, > > > > Jung-uk Kim > > > > > --- Harrison Grundy > > With an update from acpi_ppc kernel module to the new powernow > module, my cpu speed stays fixed at approx 800 mhz, even during the > complete kde 3.4 build. I see that the module loaded successfully > at boot, and kldstat shows that it loaded. Is there anything else I > must do appart from "make install" and kldload the module at boot ? You have to use 'powerd' instead. http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/powerd/ > Also, I kept the old chkfreq from the acpi_ppc package as it isn't > available in the newer powernow package. The chkfreq is quite broken. I have slightly less broken one if you are interested. Jung-uk Kim > Running on 5.4-PRE > > Thanks, > Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 18:00:22 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 110A816A4CE for ; Mon, 28 Mar 2005 18:00:22 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C926243D39 for ; Mon, 28 Mar 2005 18:00:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2SHx2JB005916; Mon, 28 Mar 2005 09:59:02 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2SHx2B5005915; Mon, 28 Mar 2005 09:59:02 -0800 (PST) (envelope-from obrien) Date: Mon, 28 Mar 2005 09:59:02 -0800 From: "David O'Brien" To: cokane@cokane.org Message-ID: <20050328175902.GB2398@dragon.NUXI.org> References: <200502102038.41536.nb_root@videotron.ca> <346a8022050211071268dc6fa4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <346a8022050211071268dc6fa4@mail.gmail.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 18:00:22 -0000 On Fri, Feb 11, 2005 at 10:12:51AM -0500, Coleman Kane wrote: > I think you will also need to apply the skip_timer_override patch, > available here: > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003320.html > You will want to set the sysctl in loader.conf > > There's also a cradbus (PCI) patch, in addition. > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003365.html > > There is another sysctl+patch that you will need to get as well. This > one is for the APIC: > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003376.html > > You'll also want to set hw.apic.skip_set_extint=1 in loader.conf as > well to activate this one. I think both of these will enable the timer > to actually work in freebsd. All of this this should be in 5.3-STABLE (ie, RELENG_5). Are you finding that some of it isn't? We really need some Compaq R3000 testers for the 5.4-BETA snapshots. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 18:33:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 517EE16A4CE for ; Mon, 28 Mar 2005 18:33:45 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E78843D1D for ; Mon, 28 Mar 2005 18:33:45 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j2SIXipB019523; Mon, 28 Mar 2005 10:33:44 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j2SIXiel019521; Mon, 28 Mar 2005 10:33:44 -0800 Date: Mon, 28 Mar 2005 10:33:44 -0800 From: Brooks Davis To: Michael Hopkins Message-ID: <20050328183344.GB14375@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z6Eq5LdranGa6ru8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: "freebsd-amd64@freebsd.org" Subject: Re: SSH login issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 18:33:45 -0000 --z6Eq5LdranGa6ru8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 27, 2005 at 02:31:46AM +0000, Michael Hopkins wrote: >=20 >=20 > Hi all >=20 > Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64 > server called Athlon? >=20 > reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN > ATTEMPT! >=20 > It lets me in fine after I supply the password. It's highly unlikely this has anything do with amd64. This error is usually caused by failure to have matchine forward and reverse DNS entries. I'm not exactly sure what needs to match to avoid this error. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --z6Eq5LdranGa6ru8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCSE4IXY6L6fI4GtQRAkdiAKC6Ru5SuBIV4EdX4uEJEcgrKrnDjwCePSlI E9+CLarYbchGunfPEi0/5Yk= =UaPV -----END PGP SIGNATURE----- --z6Eq5LdranGa6ru8-- From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 19:25:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D9EB16A4CE for ; Mon, 28 Mar 2005 19:25:00 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 696F443D55 for ; Mon, 28 Mar 2005 19:24:59 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from ip11.vpn.uk.psi.com ([154.8.4.11] helo=macros) by mail.uk.psi.com with esmtp (Exim 4.41) id 1DFzr7-0003E9-OU; Mon, 28 Mar 2005 20:24:58 +0100 From: "alan barrow" To: , Date: Mon, 28 Mar 2005 20:29:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20050328175902.GB2398@dragon.NUXI.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcUzwAkj5/lK8bwSTfa83NoQJgfFfgADFD+Q Message-ID: Subject: RE: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 19:25:00 -0000 I've got a r3000, I can test. Yours a.r.b. -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of David O'Brien Sent: 28 March 2005 18:59 To: cokane@cokane.org Cc: freebsd-amd64@freebsd.org Subject: Re: About the cursed Compaq R3000 On Fri, Feb 11, 2005 at 10:12:51AM -0500, Coleman Kane wrote: > I think you will also need to apply the skip_timer_override patch, > available here: > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003320.html > You will want to set the sysctl in loader.conf > > There's also a cradbus (PCI) patch, in addition. > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003365.html > > There is another sysctl+patch that you will need to get as well. This > one is for the APIC: > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003376.htm l > > You'll also want to set hw.apic.skip_set_extint=1 in loader.conf as > well to activate this one. I think both of these will enable the timer > to actually work in freebsd. All of this this should be in 5.3-STABLE (ie, RELENG_5). Are you finding that some of it isn't? We really need some Compaq R3000 testers for the 5.4-BETA snapshots. -- -- David (obrien@FreeBSD.org) _______________________________________________ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 20:18:24 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C28C16A4CE for ; Mon, 28 Mar 2005 20:18:24 +0000 (GMT) Received: from mail22.sea5.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id D83B043D4C for ; Mon, 28 Mar 2005 20:18:23 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9961 invoked from network); 28 Mar 2005 20:18:23 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 28 Mar 2005 20:18:18 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2SKHwu6002552; Mon, 28 Mar 2005 15:18:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 28 Mar 2005 13:51:13 -0500 User-Agent: KMail/1.6.2 References: <4247CAA3.90804@komvista.lt> In-Reply-To: <4247CAA3.90804@komvista.lt> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <200503281351.13440.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Stasys Smailys Subject: Re: Problem Report amd64/78848 "sis driver on FreeBSD 5.x does not work on amd64" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 20:18:24 -0000 On Monday 28 March 2005 04:13 am, Stasys Smailys wrote: > Hello there! > > I've had the same problem with SiS 755 and SiS 964 on ASRock K8S8X, the > only difference was that MAC address had all zeros (00:00:00:00:00:00). > The problem is that integrated NIC doesn't have any eeprom to read from. > I solved it by applying this patch. As by now it works for me. AFAIK it > is not solved properly even in -CURRENT. > > By the way I noticed some typo in > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c and > /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c. IMHO when calling > sysarch(int, void *) it should look like this: > > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: > [...] > ret = sysarch(_AMD64_GET_FSBASE, (void *)(&addr64)); > [...] > > /usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c: > [...] > ret = sysarch(_AMD64_GET_GSBASE, (void *)(&addr64)); > [...] addr64 is supposed to be a pointer though, so it really is a pointer to a pointer that's being passed (void **). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 20:40:22 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA96B16A4CE for ; Mon, 28 Mar 2005 20:40:22 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A20643D2D for ; Mon, 28 Mar 2005 20:40:22 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so614683wra for ; Mon, 28 Mar 2005 12:40:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=egAbI6L3xA3N9tHsxzVwxNLfzQN3kh9NZJHIgcq+5bPzwg5ybHAC3stiw2FaHipKuwIKQRLPVZ2phJkOeaM/xPWC2ORqIFets+pwHW2YMYFLqhY8SsBAjfppnFen4G70FCV4RUb5NofopZjC9Mu3zM7+mii9/VOkPhnpAKl2rq8= Received: by 10.54.40.38 with SMTP id n38mr1739999wrn; Mon, 28 Mar 2005 12:40:20 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 28 Mar 2005 12:40:20 -0800 (PST) Message-ID: <2fd864e0503281240bdcc716@mail.gmail.com> Date: Mon, 28 Mar 2005 12:40:20 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050328175902.GB2398@dragon.NUXI.org> Subject: Re: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 20:40:22 -0000 On Mon, 28 Mar 2005 20:29:06 +0100, alan barrow wrote: > I've got a r3000, I can test. > > Yours a.r.b. > > -----Original Message----- > From: owner-freebsd-amd64@freebsd.org > [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of David O'Brien > Sent: 28 March 2005 18:59 > To: cokane@cokane.org > Cc: freebsd-amd64@freebsd.org > Subject: Re: About the cursed Compaq R3000 > > On Fri, Feb 11, 2005 at 10:12:51AM -0500, Coleman Kane wrote: > > I think you will also need to apply the skip_timer_override patch, > > available here: > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003320.html > > You will want to set the sysctl in loader.conf > > > > There's also a cradbus (PCI) patch, in addition. > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-January/003365.html > > > > There is another sysctl+patch that you will need to get as well. This > > one is for the APIC: > > > http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2005-January/003376.htm > l > > > > You'll also want to set hw.apic.skip_set_extint=1 in loader.conf as > > well to activate this one. I think both of these will enable the timer > > to actually work in freebsd. > > All of this this should be in 5.3-STABLE (ie, RELENG_5). Are you finding > that some of it isn't? > > We really need some Compaq R3000 testers for the 5.4-BETA snapshots. > Due to the DSDT patch, I'm not entire sure complete R3000 support can become part of a release. Without that patch, if you run the laptop with ACPI enabled, the keyboard doesn't work. If there's a way around that, let me know, I'm up for testing. > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > _______________________________________________ > 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 Mar 28 22:12:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B22D616A540; Mon, 28 Mar 2005 22:12:01 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id C115943D2D; Mon, 28 Mar 2005 22:12:00 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id 57518BDCE; Tue, 29 Mar 2005 01:11:50 +0200 (EET) Received: from [192.168.150.107] (localhost [127.0.0.1]) by mail.komvista.lt (Postfix) with ESMTP id 8E714BDCA; Tue, 29 Mar 2005 01:11:48 +0200 (EET) Message-ID: <42488129.80608@komvista.lt> Date: Tue, 29 Mar 2005 01:11:53 +0300 From: Stasys Smailys User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <4247CAA3.90804@komvista.lt> <200503281351.13440.jhb@FreeBSD.org> In-Reply-To: <200503281351.13440.jhb@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit cc: "\[FreeBSD-AMD64\]" Subject: Re: Problem Report amd64/78848 "sis driver on FreeBSD 5.x does not work on amd64" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 22:12:02 -0000 John Baldwin wrote: > On Monday 28 March 2005 04:13 am, Stasys Smailys wrote: > [skipped] >>/usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: >>[...] >>ret = sysarch(_AMD64_GET_FSBASE, (void *)(&addr64)); >>[...] >> >>/usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c: >>[...] >>ret = sysarch(_AMD64_GET_GSBASE, (void *)(&addr64)); >>[...] > > > addr64 is supposed to be a pointer though, so it really is a pointer to a > pointer that's being passed (void **). > Strange. If this is an expected behavior why then I couldn't "make buildworld" till I changed (void **) to (void *)? cc -m32 -march=athlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT -I/usr/obj/usr/src/lib32/usr/include -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32 -O2 -frename-registers -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: In function `_amd64_get_fsbase': /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c:40: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Ah, I see now. Because of -Werror, right? cya From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 28 22:44:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B15C16A4CE for ; Mon, 28 Mar 2005 22:44:08 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F1543D2F for ; Mon, 28 Mar 2005 22:44:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6019 invoked from network); 28 Mar 2005 22:44:08 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 28 Mar 2005 22:44:06 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2SMi0It003376; Mon, 28 Mar 2005 17:44:01 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 28 Mar 2005 17:36:28 -0500 User-Agent: KMail/1.6.2 References: <4247CAA3.90804@komvista.lt> <200503281351.13440.jhb@FreeBSD.org> <42488129.80608@komvista.lt> In-Reply-To: <42488129.80608@komvista.lt> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <200503281736.28191.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Stasys Smailys Subject: Re: Problem Report amd64/78848 "sis driver on FreeBSD 5.x does not work on amd64" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 22:44:08 -0000 On Monday 28 March 2005 05:11 pm, Stasys Smailys wrote: > John Baldwin wrote: > > On Monday 28 March 2005 04:13 am, Stasys Smailys wrote: > > [skipped] > > >>/usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: > >>[...] > >>ret = sysarch(_AMD64_GET_FSBASE, (void *)(&addr64)); > >>[...] > >> > >>/usr/src/lib/libc/i386/sys/_amd64_get_gsbase.c: > >>[...] > >>ret = sysarch(_AMD64_GET_GSBASE, (void *)(&addr64)); > >>[...] > > > > addr64 is supposed to be a pointer though, so it really is a pointer to a > > pointer that's being passed (void **). > > Strange. If this is an expected behavior why then I couldn't "make > buildworld" till I changed (void **) to (void *)? > > cc -m32 -march=athlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT > -I/usr/obj/usr/src/lib32/usr/include -L/usr/obj/usr/src/lib32/usr/lib32 > -B/usr/obj/usr/src/lib32/usr/lib32 -O2 -frename-registers -pipe > -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include > -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE > -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 > -I/usr/obj/lib32/usr/src/lib/libc -DPOSIX_MISTAKE > -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN > -I/usr/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall > -Wno-format-y2k -Wno-uninitialized -c > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: In function > `_amd64_get_fsbase': > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c:40: warning: > dereferencing type-punned pointer will break strict-aliasing rules > *** Error code 1 > > Stop in /usr/src/lib/libc. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > Ah, I see now. Because of -Werror, right? Yes. It needs some set of gymnastics to get around that I suppose. It probably has to do with the fact that this is -m32 code in which void * is a uint32_t, not a uint64_t. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 08:39:31 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93D7216A4CE for ; Tue, 29 Mar 2005 08:39:31 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 396A543D39 for ; Tue, 29 Mar 2005 08:39:31 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so456105wra for ; Tue, 29 Mar 2005 00:39:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=e263LOUs+yS1X4gfAbrI6SaBcH4+3tJt/3j1D5MVZ3Z8LffETG1vBFs+NzOe4mJK/k4iMXTqkwSTFkLMXGXeNIKiQ2IuvXoCrUcZBaci5d2pEIVgYw5TWYqnE+soY8LVjJfANIsIDTJZ7wOJWqJeKD+lXBLwq5Op7Z1g3JoqyIc= Received: by 10.54.79.8 with SMTP id c8mr618282wrb; Tue, 29 Mar 2005 00:39:29 -0800 (PST) Received: by 10.54.40.69 with HTTP; Tue, 29 Mar 2005 00:39:29 -0800 (PST) Message-ID: <2fd864e05032900397d7733e8@mail.gmail.com> Date: Tue, 29 Mar 2005 00:39:29 -0800 From: Astrodog To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 08:39:31 -0000 Through about an hour of tinkering, I've gotten NVidia's i386 driver to compile, sans final linking, for AMD64. In as far as I can tell, the code appears to be AMD64 safe, and there doesn't seem to be a difference between what calls the i386 version makes, as compared to the ones the AMD64 version would make. The i386 version is already compiled with support for 64-bit pointers and ints, so it appears to potentially be possible to use the i386 nv-kernel.o, with the AMD64 kernel, if there's a way to get that to link with the rest of the AMD64 compiled object files. The error I get is: ld: Relocatable linking with relocations from format elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is not supported. I tried with, and without the -r option. Without -r, it has a bunch of unresolved references. If anyone has a thought on how to get around the above error, or to resolve the reference problem that comes up... that'd be great. I'm just incredibly fed up with not having AMD64 NVidia drivers. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 10:03:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ABFC16A4CF for ; Tue, 29 Mar 2005 10:03:09 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC75443D49 for ; Tue, 29 Mar 2005 10:03:08 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 330AFB80C for ; Tue, 29 Mar 2005 05:03:08 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-amd64@freebsd.org From: Vivek Khera Date: Tue, 29 Mar 2005 05:03:08 -0500 X-Mailer: Apple Mail (2.619.2) Subject: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 10:03:09 -0000 I have a brand new Tyan k8sr based system with a megaraid 320-2X controller in it. This is my second copy of this box (the first one is being replaced since it keeps locking up and reporting "memory size changed" in the BIOS, even with a new motherboard)... Anynow, this particular machine has just simply locked up with no errors reported to console or syslog or BIOS. It does have a newer BIOS rev, so perhaps that is why nothing is logged to BIOS... This happens during times of heavy loads (large database reports, database dump, database replication all simultaneously running). If the machine doesn't crash, I'll see a "bge0 timeout -- resetting" in the syslog most days during the time of heavy load (reports run on a remote client). I see at http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2005-03/ 0419.html that this is happening to at least one other person on this motherboard, but using the on-board controller. Someone else just noted similar lockups with 5.3 with SMP running mysql, and about 2 weeks ago there was a discussion about amr driver panic under 5.4-PRERELEASE, both on the stable@ list. However these were not amd64 systems, if that matters. FreeBSD 5.4-PRERELEASE as of March 22, 2005 is running on this system. It has a dual Opteron 246 2GHz and 4GB RAM. Could it be some strange interaction of the K8SR and the 320-2X megaraid card? This makes two machines exhibiting very unstable behavior, and I've already replaced the motherboard on one of them. From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 11:09:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C996F16A4CF for ; Tue, 29 Mar 2005 11:09:17 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C6D843D1D for ; Tue, 29 Mar 2005 11:09:17 +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 1DGEay-000GJn-Dw for freebsd-amd64@freebsd.org; Tue, 29 Mar 2005 13:09:16 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Mar 2005 13:09:16 +0200 From: Danny Braniss Message-ID: Subject: panic: userret: Returning with 1 locks held. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 11:09:17 -0000 this happens at boot, current as of this morning, but can't remember when current worked on this box, so the problem is not new, btw, 5.4 works ok. the console is at ftp://ftp.cs.huji.ac.il/users/danny/freebsd/console-opteron.log From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 11:11:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40AFA16A4CE for ; Tue, 29 Mar 2005 11:11:45 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id B93B343D54 for ; Tue, 29 Mar 2005 11:11:44 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 83BED300083D; Tue, 29 Mar 2005 13:11:43 +0200 (CEST) Message-ID: <424937DF.1060400@mail.uni-mainz.de> Date: Tue, 29 Mar 2005 13:11:27 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050317 X-Accept-Language: de-de, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <4245D504.9040004@mail.uni-mainz.de> <86fyyhw5w6.fsf@xps.des.no> In-Reply-To: <86fyyhw5w6.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at uni-mainz.de cc: freebsd-amd64@freebsd.org Subject: Re: ASUS A8N-SLI Deluxe FreeBSD 5.4-Beta problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 11:11:45 -0000 Dag-Erling Smørgrav schrieb: >"O. Hartmann" writes: > > >>Booting from installation CDROM is not possible until acpi gets >>disabled and this stays so when already did make world / new kernel >>with a most recent CTM set of the kernel stuff. >> >> > >Try to remove NO_MIXED_MODE from your kernel config, and see if it >boots with ACPI enabled. > > Sorry for waiting so long for the answers. I will try this. > > >>I read some time ago about nVidia nForce3/4 issues and I wonder that >>this is still status quo. >> >> > >The nForce 3 chipset is fairly well supported, while nForce 4 is still >too new. > >DES > > Well, this is what I expected but it means there will be support in the nearer future as I know this from FreeBSD. The machine runs with ACPI disabled, seems to need atpic in the kernel (but I thought this is legacy?). Due to not being connected to the net I have to burn dmesg output to DVD/CD RW if it will be helpfull. Thanks, Oliver From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 11:14:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E08416A4CE for ; Tue, 29 Mar 2005 11:14:37 +0000 (GMT) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE3643D68 for ; Tue, 29 Mar 2005 11:14:36 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 93FB430001B9; Tue, 29 Mar 2005 13:14:35 +0200 (CEST) Message-ID: <4249388B.1080906@mail.uni-mainz.de> Date: Tue, 29 Mar 2005 13:14:19 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050317 X-Accept-Language: de-de, en MIME-Version: 1.0 To: Florent Thoumie References: <4245D504.9040004@mail.uni-mainz.de> <4247F777.5080708@xbsd.org> In-Reply-To: <4247F777.5080708@xbsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at uni-mainz.de cc: freebsd-amd64@freebsd.org Subject: Re: ASUS A8N-SLI Deluxe FreeBSD 5.4-Beta problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 11:14:37 -0000 Florent Thoumie schrieb: > O. Hartmann a écrit : > >> Dear Sirs. >> I just tried to install a most recent set of FreeBSD >> 5.4-PRERELEASE/5.4-BETA1 on an ASUS A8N-SLI Deluxe mobo. The system >> has a Maxtor 6B200M0 200GB harddisk attached to the nForce4 SATA >> connector (due to NCQ) and a NEC 3500AG DVD+RW attached to the >> nForce4 ATA133 connector. >> Booting from installation CDROM is not possible until acpi gets >> disabled and this stays so when already did make world / new kernel >> with a most recent CTM set of the kernel stuff. >> It seems that FreeBSD does not know much about the SATA/SATA2 >> controller (it shows up as ATA Generic). The harddisk shows up as >> UDMA33 drive (like the DVDRW). >> Performance is crude, copying from DVD while compiling makes the >> system hang for some seconds on console. >> >> Sorry, I'm not connected to the net with that machine so I lack in >> dmesg-output. >> >> I read some time ago about nVidia nForce3/4 issues and I wonder that >> this is still status quo. >> >> Compiling kernel without "atpic" seems to leave the operating system >> inoperable, ACPI seems not to work. My question is whether FreeBSD >> 5.4 will support this type of hardware or maybe 5.5 or will FreeBSD >> not support this? >> >> Sorry bothering somebody around here, maybe this has been completely >> discussed here but I do not read regularily this mailing list. >> >> Can someone send me hints/tips for a fast kerl config and say >> something about the trapdoors? > > > I'm not sure what's wrong with your configuration but I have > this motherboard and had no problems with 5.3-R (except acpi > and broken sk(4) which is resolved now). > Dear Florent Thoumie. The boards runs with FreeBSD 5.4-PRE with ACPI disabled and atpic legacy support enabled. It 'runs' means I can work with the machine, but still having performance impacts due to lack in support of the new chips, see another posting of mine and DES. Thanks for your answer. Oliver From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 11:32:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FCC316A4CE; Tue, 29 Mar 2005 11:32:08 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7330D43D58; Tue, 29 Mar 2005 11:32:07 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DGEx3-0007Vm-00; Tue, 29 Mar 2005 12:32:05 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Tue, 29 Mar 2005 12:32:05 +0100 From: Michael Hopkins To: "freebsd-amd64@freebsd.org" , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 11:32:08 -0000 Hi all I have just installed mingwin32 from the ports and it works beautifully - can now port all my Unix command line code (including linking to win32 libraries) to win32 with the flick of a make switch. Marvellous! Now to linux... I haven't tried any of the linux compatibility stuff yet, either for running binaries or cross-compiling. I thought I would ask here first because I have seen quite a few messages suggesting potential issues on amd64. At the moment I am mainly interested in cross-compiling and wanting to target 32-bit linux, but obviously 64-bit will be useful in the future. Would like to get some advice on what to install and any kernel configuration or module loading that I might need to do. On a related topic - I can see that there are ports for converting binaries between different formats (e.g. ELF to a.out). As there is already a runtime compatibility established, how easy would it be to build something that reads in a FreeBSD binary or library and outputs a linux one? Just a thought. TIA Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 15:36:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 5A9D616A4CF; Tue, 29 Mar 2005 15:36:25 +0000 (GMT) Date: Tue, 29 Mar 2005 15:36:25 +0000 From: David O'Brien To: Astrodog Message-ID: <20050329153625.GA13242@hub.freebsd.org> References: <20050328175902.GB2398@dragon.NUXI.org> <2fd864e0503281240bdcc716@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e0503281240bdcc716@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 15:36:25 -0000 On Mon, Mar 28, 2005 at 12:40:20PM -0800, Astrodog wrote: > Due to the DSDT patch, I'm not entire sure complete R3000 support can > become part of a release. Without that patch, if you run the laptop > with ACPI enabled, the keyboard doesn't work. I thought that was the purpose of the .atkbd=0x9 was to get over this hurdle with stock DSDT. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 16:09:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75BBF16A4CE; Tue, 29 Mar 2005 16:09:02 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7C0043D2F; Tue, 29 Mar 2005 16:09:01 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j2TG8xZc051436; Tue, 29 Mar 2005 10:08:59 -0600 (CST) (envelope-from dan) Date: Tue, 29 Mar 2005 10:08:59 -0600 From: Dan Nelson To: Michael Hopkins Message-ID: <20050329160858.GB72462@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: freebsd-emulation@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 16:09:02 -0000 In the last episode (Mar 29), Michael Hopkins said: > On a related topic - I can see that there are ports for converting > binaries between different formats (e.g. ELF to a.out). As there is > already a runtime compatibility established, how easy would it be to > build something that reads in a FreeBSD binary or library and outputs > a linux one? Just a thought. That would be near impossible. The elf2aout program in ports has a specific purpose: to convert static elf binaries to a.out format so simple bootloaders can execute them. The binary format is the least of your worries when trying to run under a different OS. You've got structure changes (FILE for example), constant changes (ioctls, signals, errnos), syscall number changes (even the method to invoke syscalls is different), possibly different reserved registers, etc. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 18:09:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC5CF16A4CE; Tue, 29 Mar 2005 18:09:10 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D591843D1D; Tue, 29 Mar 2005 18:09:06 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2TI95Ek029420; Tue, 29 Mar 2005 13:09:05 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Tue, 29 Mar 2005 13:09:01 -0500 User-Agent: KMail/1.6.2 References: <20050328175902.GB2398@dragon.NUXI.org> <2fd864e0503281240bdcc716@mail.gmail.com> <20050329153625.GA13242@hub.freebsd.org> In-Reply-To: <20050329153625.GA13242@hub.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503291309.02385.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/792/Mon Mar 28 17:10:20 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 18:09:10 -0000 On Tuesday 29 March 2005 10:36 am, David O'Brien wrote: > On Mon, Mar 28, 2005 at 12:40:20PM -0800, Astrodog wrote: > > Due to the DSDT patch, I'm not entire sure complete R3000 support > > can become part of a release. Without that patch, if you run the > > laptop with ACPI enabled, the keyboard doesn't work. > > I thought that was the purpose of the .atkbd=0x9 was to get > over this hurdle with stock DSDT. No, the purpose of the flag is to boot without ACPI. With ACPI, there's another problem (i.e., resource conflict). Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 21:14:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5618C16A4CE for ; Tue, 29 Mar 2005 21:14:48 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89EFE43D5A for ; Tue, 29 Mar 2005 21:14:47 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by smtp-gw-cl-c.dmv.com (8.12.10/8.12.10) with ESMTP id j2TLYfEo000860 for ; Tue, 29 Mar 2005 16:34:41 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Tue, 29 Mar 2005 16:15:00 -0500 Message-Id: <1112130900.3883.5.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 Subject: amr monitor for megaraid on amd64 platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 21:14:48 -0000 Having perused the forums/google/etc I have found some references to megaraid (amr) monitoring software for FreeBSD that included a) a linux version from LSI that won't work because linux compat does not work for ioctl and b) a freebsd megacontrol utiltiy that won't work because it requires compat4x (or at least libc.so.4) and compat4x does not install on amd64 platform. So has anyone come up with some type of monitoring or basic status type software for the amr driver? I imagine drive failure(s) would show up in /var/log/messages but I would prefer to be able to write some type of shellscript that would check the status of the individual drives in the raid array. Sven From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 29 22:12:33 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DE1E16A4CE for ; Tue, 29 Mar 2005 22:12:33 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9BBD43D48 for ; Tue, 29 Mar 2005 22:12:32 +0000 (GMT) (envelope-from nb_root@videotron.com) Received: from clk02 ([66.130.198.54]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IE400BGPWB9SD@VL-MO-MR010.ip.videotron.ca> for freebsd-amd64@freebsd.org; Tue, 29 Mar 2005 17:11:33 -0500 (EST) Date: Tue, 29 Mar 2005 17:11:32 -0500 From: Nicolas Blais In-reply-to: <2fd864e0503281240bdcc716@mail.gmail.com> To: freebsd-amd64@freebsd.org Message-id: <200503291711.33163.nb_root@videotron.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.8 References: <20050328175902.GB2398@dragon.NUXI.org> <2fd864e0503281240bdcc716@mail.gmail.com> Subject: Re: About the cursed Compaq R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 22:12:33 -0000 > If there's a way around that, let me know, I'm up for testing. > I'm up for testing too, if it makes it to -STABLE ;) which is compiled every 2nd days on all my boxes. Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:09:20 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CCA216A4CE for ; Wed, 30 Mar 2005 00:09:20 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BB6543D67 for ; Wed, 30 Mar 2005 00:09:19 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A7B37.dip.t-dialin.net [84.154.123.55]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j2R9qifZ067691; Sun, 27 Mar 2005 11:52:45 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j2R8t2JR001087; Sun, 27 Mar 2005 10:55:05 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j2R8ssJC003927; Sun, 27 Mar 2005 10:54:54 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200503270854.j2R8ssJC003927@fire.jhs.private> To: Michael Hopkins In-Reply-To: Message from Michael Hopkins Date: Sun, 27 Mar 2005 10:54:54 +0200 From: "Julian H. Stacey" cc: "freebsd-amd64@freebsd.org" Subject: Re: SSH login issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:09:20 -0000 Michael Hopkins wrote: > > > Hi all > > Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64 > server called Athlon? > > reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN > ATTEMPT! Did you check with nslookup (or dig or whatever) ? Looks like a name server (named) err. - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:13:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EFF316A4CE for ; Wed, 30 Mar 2005 00:13:09 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0772443D2D for ; Wed, 30 Mar 2005 00:13:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CC03451287; Tue, 29 Mar 2005 16:13:07 -0800 (PST) Date: Tue, 29 Mar 2005 16:13:07 -0800 From: Kris Kennaway To: Danny Braniss Message-ID: <20050330001307.GA44798@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: panic: userret: Returning with 1 locks held. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:13:09 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 29, 2005 at 01:09:16PM +0200, Danny Braniss wrote: > this happens at boot, current as of this morning, but can't remember > when current worked on this box, so the problem is not new, > btw, 5.4 works ok. >=20 > the console is at > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/console-opteron.log What does 'show alllocks' say? You may need to compile in WITNESS support first. Kris --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCSe8TWry0BWjoQKURAiIUAJ9Q1jk30+aaR45ZAfwhAG/h+kmjRACeIWXw m+QE+I9SIIErzAQx+0m43G0= =Dx1z -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:32:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0F9316A4F8 for ; Wed, 30 Mar 2005 00:32:48 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED94443D46 for ; Wed, 30 Mar 2005 00:32:47 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A70A6.dip.t-dialin.net [84.154.112.166]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j2TBo5fZ074606; Tue, 29 Mar 2005 13:50:06 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j2TAqRxC002270; Tue, 29 Mar 2005 12:52:29 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j2TAqQCF007783; Tue, 29 Mar 2005 12:52:26 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200503291052.j2TAqQCF007783@fire.jhs.private> To: Michael Hopkins In-Reply-To: Message from Michael Hopkins Date: Tue, 29 Mar 2005 12:52:26 +0200 From: "Julian H. Stacey" cc: "freebsd-amd64@freebsd.org" Subject: Re: SSH login issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:32:48 -0000 Resend on bounce (to @freebsd not bounce to @hopkins) Michael Hopkins wrote: > > > Hi all > > Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64 > server called Athlon? > > reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN > ATTEMPT! Did you check with nslookup (or dig or whatever) ? Looks like a name server (named) err. - - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:39:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88CC016A4CE for ; Wed, 30 Mar 2005 00:39:27 +0000 (GMT) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4A9343D31 for ; Wed, 30 Mar 2005 00:39:26 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id 32D6B3F295; Wed, 30 Mar 2005 02:39:25 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 9E5E0266; Wed, 30 Mar 2005 02:39:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 846661BD; Wed, 30 Mar 2005 02:39:24 +0200 (CEST) Date: Wed, 30 Mar 2005 02:39:24 +0200 (CEST) From: Sten Spans To: Vivek Khera In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:39:27 -0000 On Tue, 29 Mar 2005, Vivek Khera wrote: > I have a brand new Tyan k8sr based system with a megaraid 320-2X controller > in it. > > This is my second copy of this box (the first one is being replaced since it > keeps locking up and reporting "memory size changed" in the BIOS, even with a > new motherboard)... > > Anynow, this particular machine has just simply locked up with no errors > reported to console or syslog or BIOS. It does have a newer BIOS rev, so > perhaps that is why nothing is logged to BIOS... This happens during times > of heavy loads (large database reports, database dump, database replication > all simultaneously running). If the machine doesn't crash, I'll see a "bge0 > timeout -- resetting" in the syslog most days during the time of heavy load > (reports run on a remote client). > > I see at http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2005-03/ > 0419.html that this is happening to at least one other person on this > motherboard, but using the on-board controller. > > Someone else just noted similar lockups with 5.3 with SMP running mysql, and > about 2 weeks ago there was a discussion about amr driver panic under > 5.4-PRERELEASE, both on the stable@ list. However these were not amd64 > systems, if that matters. There was an amr panic related to the management ioctls which was fixed and backported to RELENG_5. You should have this fix. amr controllers a supported quite well on freebsd thanks to Scott's great work. The only way to get closer to solving these problems is to dig and try to narrow it down: - Have you tried running with debugging ? - Have you tried using other network cards ? ( yeah that sucks I know ) - Are you absolutely sure that all the disks are working ? ( there have been reports of amr cards acting strange with silently failing disks ) - Have you got the ufs fixes recently backported to releng_5 ? These are the first I can think of. RELENG_5 seems to be a bit of a moving target with some quite critical fixes going in ( which is good offcourse :). HTH, HAND -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:39:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71F2816A4CE; Wed, 30 Mar 2005 00:39:53 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBA5D43D1D; Wed, 30 Mar 2005 00:39:52 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j2U0dqx2037604; Tue, 29 Mar 2005 19:39:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j2U0dqfU075345; Tue, 29 Mar 2005 19:39:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1EEFB7306E; Tue, 29 Mar 2005 19:39:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050330003952.1EEFB7306E@freebsd-current.sentex.ca> Date: Tue, 29 Mar 2005 19:39:52 -0500 (EST) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:39:53 -0000 TB --- 2005-03-29 23:16:19 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-03-29 23:16:19 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-03-29 23:16:19 - checking out the source tree TB --- 2005-03-29 23:16:19 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-03-29 23:16:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-03-29 23:23:23 - building world (CFLAGS=-O2 -pipe) TB --- 2005-03-29 23:23:23 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-29 23:23:23 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-03-30 00:30:51 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-03-30 00:30:51 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-30 00:30:51 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Mar 30 00:30:51 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] touch export_syms awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/modules/an/../../conf/kmod_syms.awk if_an.ko.debug export_syms | xargs -J% objcopy % if_an.ko.debug objcopy --strip-debug if_an.ko.debug if_an.ko ===> ath (all) cc -O2 -pipe -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../contrib/dev/ath -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../contrib/dev/ath -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../dev/ath/if_ath.c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../dev/ath/if_ath.c: In function `ath_recv_mgmt': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../dev/ath/if_ath.c:2471: warning: long long unsigned int format, u_int64_t arg (arg 3) /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath/../../dev/ath/if_ath.c:2471: warning: long long unsigned int format, u_int64_t arg (arg 4) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ath. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-03-30 00:39:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-03-30 00:39:51 - ERROR: failed to build generic kernel TB --- 2005-03-30 00:39:51 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 00:46:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6FE016A4CE for ; Wed, 30 Mar 2005 00:46:04 +0000 (GMT) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78C2E43D58 for ; Wed, 30 Mar 2005 00:46:04 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id CD7023F294; Wed, 30 Mar 2005 02:46:03 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 59C10266; Wed, 30 Mar 2005 02:46:03 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 3F2061BD; Wed, 30 Mar 2005 02:46:03 +0200 (CEST) Date: Wed, 30 Mar 2005 02:46:03 +0200 (CEST) From: Sten Spans To: Sven Willenberger In-Reply-To: <1112130900.3883.5.camel@lanshark.dmv.com> Message-ID: References: <1112130900.3883.5.camel@lanshark.dmv.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: amr monitor for megaraid on amd64 platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 00:46:04 -0000 On Tue, 29 Mar 2005, Sven Willenberger wrote: > Having perused the forums/google/etc I have found some references to > megaraid (amr) monitoring software for FreeBSD that included a) a linux > version from LSI that won't work because linux compat does not work for > ioctl and b) a freebsd megacontrol utiltiy that won't work because it > requires compat4x (or at least libc.so.4) and compat4x does not install > on amd64 platform. > > So has anyone come up with some type of monitoring or basic status type > software for the amr driver? I imagine drive failure(s) would show up > in /var/log/messages but I would prefer to be able to write some type of > shellscript that would check the status of the individual drives in the > raid array. source for an amr monitoring tool (amrstat) was posted on -current about a week ago. I have it online somewhere if you can't find it. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 03:30:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F196616A4CE for ; Wed, 30 Mar 2005 03:30:11 +0000 (GMT) Received: from web52306.mail.yahoo.com (web52306.mail.yahoo.com [206.190.39.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A23143D2D for ; Wed, 30 Mar 2005 03:30:11 +0000 (GMT) (envelope-from dystopianrebel@yahoo.com) Received: (qmail 29348 invoked by uid 60001); 30 Mar 2005 03:30:10 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Ea2SWeeRAentw9297tft2JHV2ebuo+IzEsApRcajR7ONPA6sEl/8yjgJxK/eBd1/J/LioBww1rfY4OvV2mY66A1eI7KYbW/TThFZX6mhcLFpUDPwzeF7NaVKiWcFqQRixEPw4Gy5jdZsiSIfy/aoFrwv4XrdkUgqK15hfUPM0ek= ; Message-ID: <20050330033010.29346.qmail@web52306.mail.yahoo.com> Received: from [64.26.160.170] by web52306.mail.yahoo.com via HTTP; Tue, 29 Mar 2005 19:30:10 PST Date: Tue, 29 Mar 2005 19:30:10 -0800 (PST) From: dR To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: OpenOffice (Linux binary) blows up if not run by root X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 03:30:12 -0000 OS: FreeBSD 5.3 Release; 64-bit AMD64; kernel built with Linux compatibility Application: OpenOffice 2.0 Linux Linux JDK 1.4 When I start OpenOffice as a non-root user, OpenOffice blows up at the very first touch of the keyboard. If I run OpenOffice as root, it is stable. Would one of you wise folks tell me how to remedy this? m! __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 04:22:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DEAE16A4CF; Wed, 30 Mar 2005 04:22:42 +0000 (GMT) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C1EF43D53; Wed, 30 Mar 2005 04:22:42 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from dsl-200-95-2-41.prod-infinitum.com.mx (dsl-200-95-2-41.prod-infinitum.com.mx [200.95.2.41]) by sophia3.e-shell.net (Postfix) with ESMTP id 6929A656836; Tue, 29 Mar 2005 22:22:41 -0600 (CST) From: Axel Gonzalez To: freebsd-amd64@freebsd.org Date: Tue, 29 Mar 2005 22:22:39 -0600 User-Agent: KMail/1.8 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503292222.39751.loox@e-shell.net> cc: Michael Hopkins cc: freebsd-emulation@freebsd.org Subject: Re: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 04:22:42 -0000 On Tuesday 29 March 2005 05:32, Michael Hopkins wrote: > Hi all > > I have just installed mingwin32 from the ports and it works beautifully - > can now port all my Unix command line code (including linking to win32 > libraries) to win32 with the flick of a make switch. Marvellous! Glad to know it works now.. I should have checked more often > > Now to linux... I haven't tried any of the linux compatibility stuff yet, > either for running binaries or cross-compiling. I thought I would ask here > first because I have seen quite a few messages suggesting potential issues > on amd64. > > At the moment I am mainly interested in cross-compiling and wanting to > target 32-bit linux, but obviously 64-bit will be useful in the future. > Would like to get some advice on what to install and any kernel > configuration or module loading that I might need to do. This should be well documented elsewhere, if i remember correctly: on kernel, add the options: options LINPROCFS options COMPAT_43 options COMPAT_LINUX32 Install the emulators/linux_base-8 port and enable on rc.conf linux_enable="YES" After that you should have a running linux enviroment $ /compat/linux/bin/bash $ uname -a Linux moonlight 2.4.2 FreeBSD 5.3-STABLE #0: Thu Feb 3 23:08:02 CST 2005 amd64 amd64 amd64 GNU/Linux Then, the real thing, the cross compile NOTE: At this point I'm guessing, tell us if it works ;) Get a GCC RPM and install it (check the Makefile on the linux port, to see the flags it uses, and see you dont overwrite system GCC) Maybe some extra RPMs.. make, libtool etc Run gcc from the linux bash (check the path to be sure its really using linux's gcc) *IF* this work, you should be able to compile and run linux32 programs (you using a linux compiler right ?) For linux64, well first step is to get binaries working From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 05:21:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DD2516A4CE for ; Wed, 30 Mar 2005 05:21:21 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FA9A43D1D for ; Wed, 30 Mar 2005 05:21:21 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 55EF572DD9; Tue, 29 Mar 2005 21:21:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 50D5F72DCB; Tue, 29 Mar 2005 21:21:21 -0800 (PST) Date: Tue, 29 Mar 2005 21:21:21 -0800 (PST) From: Doug White To: Astrodog In-Reply-To: <2fd864e05032900397d7733e8@mail.gmail.com> Message-ID: <20050329211942.P59551@carver.gumbysoft.com> References: <2fd864e05032900397d7733e8@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 05:21:21 -0000 On Tue, 29 Mar 2005, Astrodog wrote: > Through about an hour of tinkering, I've gotten NVidia's i386 driver > to compile, sans final linking, for AMD64. [...] > The error I get is: > ld: Relocatable linking with relocations from format > elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is > not supported. This message doesn't lie -- we don't support mixed-mode objects. Solaris doesn't either and I doubt we have plans to grow this support. You'll need all amd64-compiled object files; without them, you're sunk. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 08:25:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA19416A4CE for ; Wed, 30 Mar 2005 08:25:10 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43E4743D54 for ; Wed, 30 Mar 2005 08:25:10 +0000 (GMT) (envelope-from ecespedes@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so53061rng for ; Wed, 30 Mar 2005 00:25:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=tuHVW4zH102JERtLXZwufrVDBUIhZr7rIAoCyZGzqitMusZz0xk0wDO4XeIIJ2BRSPgGfBOFjjCFhgw/Kz5iWBFS2v9K6I8TpDj7eUakltW5sTV2ZczBukFGqDt6ZfKrgRSdUVtynsMN7QmxCb2oPcnh6I53Hqv+8KkbJWOIKe4= Received: by 10.38.12.35 with SMTP id 35mr236547rnl; Wed, 30 Mar 2005 00:25:09 -0800 (PST) Received: by 10.38.67.74 with HTTP; Wed, 30 Mar 2005 00:25:09 -0800 (PST) Message-ID: <8ce510620503300025116da2fd@mail.gmail.com> Date: Wed, 30 Mar 2005 10:25:09 +0200 From: =?ISO-8859-1?Q?Enrique_F=2E_C=E9spedes_S=E1nchez?= To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: cvsup never update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-1?Q?Enrique_F=2E_C=E9spedes_S=E1nchez?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 08:25:11 -0000 Hi, cvsup is working ok? It never updates collection src-all/cvs in my system: uname says: FreeBSD beethoven.fullpull.dyndns.org 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0 standard-supfile: *default host=cvsup2.es.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_3 *default delete use-rel-suffix *default compress *src-all Thanks E. Cespedes From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 08:28:52 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BAF516A4CE for ; Wed, 30 Mar 2005 08:28:52 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C7D343D68 for ; Wed, 30 Mar 2005 08:28:52 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 9132 invoked from network); 30 Mar 2005 08:28:51 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail26.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Mar 2005 08:28:50 -0000 Received: from hydrogen.funkthat.com (hupcry@localhost.funkthat.com [127.0.0.1])j2U8SnGH065791; Wed, 30 Mar 2005 00:28:50 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id j2U8SnU0065790; Wed, 30 Mar 2005 00:28:49 -0800 (PST) Date: Wed, 30 Mar 2005 00:28:49 -0800 From: John-Mark Gurney To: Enrique =?iso-8859-1?Q?F=2E_C=E9spedes_S=E1nchez?= Message-ID: <20050330082849.GF37984@funkthat.com> Mail-Followup-To: Enrique =?iso-8859-1?Q?F=2E_C=E9spedes_S=E1nchez?= , freebsd-amd64@freebsd.org References: <8ce510620503300025116da2fd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ce510620503300025116da2fd@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-amd64@freebsd.org Subject: Re: cvsup never update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 08:28:52 -0000 Enrique F. Céspedes Sánchez wrote this message on Wed, Mar 30, 2005 at 10:25 +0200: > cvsup is working ok? It never updates collection src-all/cvs in my system: [...] > *default release=cvs tag=RELENG_5_3 Yep, it's working.. Not much is going into the 5.3-R branch anymore... If you want to track the source leading up to 5.4, then you should change your tag to RELENG_5, and then once 5.4 has branched, change it to RELENG_5_4... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 08:33:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E892A16A4CE for ; Wed, 30 Mar 2005 08:33:39 +0000 (GMT) Received: from phoenix.severttk.ru (phoenix.severttk.ru [80.92.0.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DD7243D58 for ; Wed, 30 Mar 2005 08:33:39 +0000 (GMT) (envelope-from freebsd-maillists@vibrators.ru) Received: from phoenix.severttk.ru (localhost [127.0.0.1]) by phoenix.severttk.ru (Postfix) with SMTP id 6AB45AB55 for ; Wed, 30 Mar 2005 12:33:38 +0400 (MSD) Received: from gate-sttk.km.vibrators.ru (vlan101-sv-yar03ra.severttk.ru [80.92.2.130]) by phoenix.severttk.ru (Postfix) with ESMTP id 3163EAB54 for ; Wed, 30 Mar 2005 12:33:35 +0400 (MSD) Received: from asu-reaper.km.vibrators.ru (reaper [192.168.1.36] (may be forged))j2U8XU5a057242; Wed, 30 Mar 2005 12:33:31 +0400 (MSD) (envelope-from freebsd-maillists@vibrators.ru) Date: Wed, 30 Mar 2005 12:33:30 +0400 To: =?utf-8?Q?=5C=22Enrique_F=2E_C=C3=A9spedes_S=5C=22?= =?utf-8?Q?=C3=A1nchez?= References: <8ce510620503300025116da2fd@mail.gmail.com> From: "Michael Lednev" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <8ce510620503300025116da2fd@mail.gmail.com> User-Agent: Opera M2(BETA3)/8.0 (Win32, build 7522) cc: freebsd-amd64@freebsd.org Subject: Re: cvsup never update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 08:33:40 -0000 On Wed, 30 Mar 2005 12:25:09 +0400, Enrique F. Céspedes Sánchez wrote: > cvsup is working ok? It never updates collection src-all/cvs in my try again with different server, sources for releng_5_3 updated to p6 about 2 days ago Best Regards, Michael. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 09:06:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD8F16A4CE for ; Wed, 30 Mar 2005 09:06:13 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48AC843D1D for ; Wed, 30 Mar 2005 09:06:13 +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 1DGZ9P-000GG4-K8; Wed, 30 Mar 2005 11:06:11 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Kris Kennaway In-reply-to: Your message of Tue, 29 Mar 2005 16:13:07 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Mar 2005 11:06:11 +0200 From: Danny Braniss Message-ID: cc: freebsd-amd64@freebsd.org Subject: Re: panic: userret: Returning with 1 locks held. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 09:06:13 -0000 > > --OXfL5xGRrasGEqWY > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue, Mar 29, 2005 at 01:09:16PM +0200, Danny Braniss wrote: > > this happens at boot, current as of this morning, but can't remember > > when current worked on this box, so the problem is not new, > > btw, 5.4 works ok. > >=20 > > the console is at > > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/console-opteron.log > > What does 'show alllocks' say? You may need to compile in WITNESS > support first. > > Kris db> show alllocks db> shows nothing, and yes it's compiled with: options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN maybe too many? danny From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 10:29:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D972C16A4CE for ; Wed, 30 Mar 2005 10:29:30 +0000 (GMT) Received: from web30708.mail.mud.yahoo.com (web30708.mail.mud.yahoo.com [68.142.200.141]) by mx1.FreeBSD.org (Postfix) with SMTP id 578B743D55 for ; Wed, 30 Mar 2005 10:29:30 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 24497 invoked by uid 60001); 30 Mar 2005 10:29:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Cq/NpfvjOFZfYuJSb+8mEEuEzyN9N6pSJDhPEPGAd/bVhxor7/BVoUywBstxiwEP+9Pru5t9qKFR2cQ7DHqfmxrAr42ORRQLYy5jOiNSJYHowWZmYpFaq/lvS3/BM5f6q14zB5hz+Z02J3m4Z+DlvYHwjApnfR1V+LwvGIQXgKk= ; Message-ID: <20050330102929.24495.qmail@web30708.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30708.mail.mud.yahoo.com via HTTP; Wed, 30 Mar 2005 02:29:29 PST Date: Wed, 30 Mar 2005 02:29:29 -0800 (PST) From: Neil Short To: freebsd-mobile@freebsd.org, freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: nvidia-driver slow X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 10:29:31 -0000 The xorg "nv" driver works great - at the cost of not being able to return to console-land. The nvidia driver works horribly. Molasses in winter comes to mind. The moused daemon starts running hard and the processor runs at 100%. I'm hoping the problem is some dumb mistake on my part. I'm hoping it will be apparent to you all. Here's what I have: /boot/loader.conf: linux_load="YES" nvidia_load="YES" /etc/rc.conf: ... linux_enable="YES" moused_enable="YES" moused_flags="-3 -E 100" moused_type="auto" # "auto" is the default sshd_enable="YES" usbd_enable="YES" ... uname -a: FreeBSD carmen.opera 5.4-BETA1 FreeBSD 5.4-BETA1 #0: Fri Mar 18 09:28:57 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 EQUIPMENT HP Pavilion zv5000 (same family as the famous Compaq R3000z.) Processor: XP-M. And in that vein, here's `head device.hints`: ... # my stuff: hint.atkbd.0.flags="0x9" hint.acpi.0.disabled="1" # ======== ... If history always begins this morning, the world holds exciting surprises around every corner (241). --Ann Coulter. Treason. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 11:39:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64D5916A4CE; Wed, 30 Mar 2005 11:39:46 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC2943D55; Wed, 30 Mar 2005 11:39:45 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DGbXt-0003Sx-00; Wed, 30 Mar 2005 12:39:37 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Wed, 30 Mar 2005 12:39:30 +0100 From: Michael Hopkins To: Axel Gonzalez , "freebsd-amd64@freebsd.org" Message-ID: In-Reply-To: <200503292222.39751.loox@e-shell.net> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable cc: freebsd-emulation@freebsd.org Subject: Re: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 11:39:46 -0000 On 30/3/05 5:22 am, "Axel Gonzalez" wrote: > On Tuesday 29 March 2005 05:32, Michael Hopkins wrote: >> Hi all >>=20 >> I have just installed mingwin32 from the ports and it works beautifully = - >> can now port all my Unix command line code (including linking to win32 >> libraries) to win32 with the flick of a make switch. Marvellous! >=20 > Glad to know it works now.. I should have checked more often >=20 Hi Axel Seems to work well but not tested exhaustively across different code and Windows versions yet. >>=20 >> Now to linux... I haven't tried any of the linux compatibility stuff ye= t, >> either for running binaries or cross-compiling. I thought I would ask h= ere >> first because I have seen quite a few messages suggesting potential issu= es >> on amd64. >>=20 >> At the moment I am mainly interested in cross-compiling and wanting to >> target 32-bit linux, but obviously 64-bit will be useful in the future. >> Would like to get some advice on what to install and any kernel >> configuration or module loading that I might need to do. >=20 > This should be well documented elsewhere, if i remember correctly: >=20 > on kernel, add the options: >=20 > options LINPROCFS > options COMPAT_43 > options COMPAT_LINUX32 >=20 > Install the emulators/linux_base-8 port >=20 > and enable on rc.conf >=20 > linux_enable=3D"YES" >=20 > After that you should have a running linux enviroment >=20 > $ /compat/linux/bin/bash > $ uname -a > Linux moonlight 2.4.2 FreeBSD 5.3-STABLE #0: Thu Feb 3 23:08:02 CST 2005 > amd64 amd64 amd64 GNU/Linux >=20 Did exactly these steps and got this far at 4:30am this morning! :o} root@Athlon ~ # cd /compat/linux/bin root@Athlon /compat/linux/bin # ./uname -a Linux Athlon 2.4.2 FreeBSD 5.3-RELEASE-p5 #2: Wed Mar 30 01:46:52 BST 2005 amd64 amd64 amd64 GNU/Linux >=20 > Then, the real thing, the cross compile >=20 > NOTE: At this point I'm guessing, tell us if it works ;) >=20 > Get a GCC RPM and install it (check the Makefile on the linux port, to se= e the > flags it uses, and see you dont overwrite system GCC) >=20 This is where I got badly stuck, though I might have the answer - see below= . =20 I first tried about 10 RPMs from various places that are meant to be for Redhat 8 on i386 (or i586 or i686 - I am guessing it shouldn=B9t matter?) and whenever I try to install them with the recommended command, e.g. : rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm I get this message: "package apt-0.5.5cnc6-fr0.rh80.1 is for a different architecture" I then thought that the recently-installed linux rpm might be the right way to deal with this, so: /compat/linux/bin/rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm warning: /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm: V3 DSA signature: NOKEY, key ID e42d547b error: Failed dependencies: rpm >=3D 4.0.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 libstdc++ is needed by apt-0.5.5cnc6-fr0.rh80.1 /sbin/ldconfig is needed by apt-0.5.5cnc6-fr0.rh80.1 /bin/sh is needed by apt-0.5.5cnc6-fr0.rh80.1 libbz2.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6 is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.1) is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.1.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.2) is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.2.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 libc.so.6(GLIBC_2.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 libelf.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 libgcc_s.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 libgcc_s.so.1(GCC_3.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 libm.so.6 is needed by apt-0.5.5cnc6-fr0.rh80.1 libncurses.so.5 is needed by apt-0.5.5cnc6-fr0.rh80.1 libpopt.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 libpthread.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 libpthread.so.0(GLIBC_2.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 libpthread.so.0(GLIBC_2.1) is needed by apt-0.5.5cnc6-fr0.rh80.1 libreadline.so.4 is needed by apt-0.5.5cnc6-fr0.rh80.1 librpm-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 librpmdb-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 librpmio-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 librt.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 libstdc++.so.5 is needed by apt-0.5.5cnc6-fr0.rh80.1 libstdc++.so.5(GLIBCPP_3.2) is needed by apt-0.5.5cnc6-fr0.rh80.1 libz.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 Even though all of these executables and libraries are installed as standar= d in linux_base-8. Then another thought; use '--ignorearch' with the FreeBSD rpm command. This seems to install linux apt as required! :o) Maybe this is the right way t= o go? I will investigate further and let you know. > Maybe some extra RPMs.. make, libtool etc >=20 > Run gcc from the linux bash (check the path to be sure its really using > linux's gcc) >=20 Will try these later today. > *IF* this work, you should be able to compile and run linux32 programs (y= ou > using a linux compiler right ?) >=20 So I can't get to these steps until I have worked out how to install the GC= C tools for linux. As far as I can tell I have the following options: 1) Work out how to make RPMs work as discussed above. Would like this anyway to be able to use more linux stuff. 2) Install linux_devtools from ports - but: /usr/ports/devel/linux_devtools % make =3D=3D=3D> linux_devtools-8.0_3 is only for i386, and you are running amd64. 3) Find a tarball of the GCC toolset for RH8 i*86 and extract it into /compat/linux 4) ? Any others ? > For linux64, well first step is to get binaries working >=20 I will just be happy to have 32-bit working for now! Thanks for the input Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_= / _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' =20 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_= / From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 14:38:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 123E816A4CE for ; Wed, 30 Mar 2005 14:38:46 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A88943D45 for ; Wed, 30 Mar 2005 14:38:45 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) j2UEwgEo026486; Wed, 30 Mar 2005 09:58:42 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: Sten Spans In-Reply-To: References: <1112130900.3883.5.camel@lanshark.dmv.com> Content-Type: text/plain Date: Wed, 30 Mar 2005 09:38:57 -0500 Message-Id: <1112193537.4895.18.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 cc: freebsd-amd64@freebsd.org Subject: Re: amr monitor for megaraid on amd64 platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 14:38:46 -0000 On Wed, 2005-03-30 at 02:46 +0200, Sten Spans wrote: > On Tue, 29 Mar 2005, Sven Willenberger wrote: > > > Having perused the forums/google/etc I have found some references to > > megaraid (amr) monitoring software for FreeBSD that included a) a linux > > version from LSI that won't work because linux compat does not work for > > ioctl and b) a freebsd megacontrol utiltiy that won't work because it > > requires compat4x (or at least libc.so.4) and compat4x does not install > > on amd64 platform. > > > > So has anyone come up with some type of monitoring or basic status type > > software for the amr driver? I imagine drive failure(s) would show up > > in /var/log/messages but I would prefer to be able to write some type of > > shellscript that would check the status of the individual drives in the > > raid array. > > source for an amr monitoring tool (amrstat) was posted > on -current about a week ago. I have it online somewhere if you > can't find it. > Thanks!! Found the source (it seems the thread was "Panic with amr and 5.4-PRERELEASE" http://lists.freebsd.org/pipermail/freebsd-current/2005-March/047479.html ) and a couple of added #include 's and some braces later was able to compile and run it. Seems to provide the basic functionality that I need. Thanks again, Sven From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 14:44:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8101816A4CE for ; Wed, 30 Mar 2005 14:44:49 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47E1343D3F for ; Wed, 30 Mar 2005 14:44:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 16B72511F4; Wed, 30 Mar 2005 06:44:48 -0800 (PST) Date: Wed, 30 Mar 2005 06:44:48 -0800 From: Kris Kennaway To: Danny Braniss Message-ID: <20050330144447.GA83108@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: panic: userret: Returning with 1 locks held. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 14:44:49 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 30, 2005 at 11:06:11AM +0200, Danny Braniss wrote: > >=20 > > --OXfL5xGRrasGEqWY > > Content-Type: text/plain; charset=3Dus-ascii > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > >=20 > > On Tue, Mar 29, 2005 at 01:09:16PM +0200, Danny Braniss wrote: > > > this happens at boot, current as of this morning, but can't remember > > > when current worked on this box, so the problem is not new, > > > btw, 5.4 works ok. > > >=3D20 > > > the console is at > > > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/console-opteron.log > >=20 > > What does 'show alllocks' say? You may need to compile in WITNESS > > support first. > >=20 > > Kris >=20 > db> show alllocks > db> Ah, OK, this is a panic about lockmgr locks. 'show lockedvnods' instead, then for each process listed do 'tr '. CC Jeff Roberson in the reply. 'show lockedbufs' might also be useful if your kernel is new enough. Kris --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCSrtfWry0BWjoQKURAiXgAKCdCn8X5wotNPHdvqQewLxelw+KgwCfXIki rOLWetEoXvBjpkGR8JTJ7j0= =cFZj -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 15:20:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F61416A4CF for ; Wed, 30 Mar 2005 15:20:50 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDAEA43D5D for ; Wed, 30 Mar 2005 15:20:49 +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 1DGezw-000P0q-DY; Wed, 30 Mar 2005 17:20:48 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Kris Kennaway In-Reply-To: Message from Kris Kennaway <20050330144447.GA83108@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Mar 2005 17:20:48 +0200 From: Danny Braniss Message-ID: cc: Jeff Roberson cc: freebsd-amd64@freebsd.org Subject: Re: panic: userret: Returning with 1 locks held. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 15:20:50 -0000 > On Wed, Mar 30, 2005 at 11:06:11AM +0200, Danny Braniss wrote: > > >=20 > > > --OXfL5xGRrasGEqWY > > > Content-Type: text/plain; charset=3Dus-ascii > > > Content-Disposition: inline > > > Content-Transfer-Encoding: quoted-printable > > >=20 > > > On Tue, Mar 29, 2005 at 01:09:16PM +0200, Danny Braniss wrote: > > > > this happens at boot, current as of this morning, but can't remember > > > > when current worked on this box, so the problem is not new, > > > > btw, 5.4 works ok. > > > >=3D20 > > > > the console is at > > > > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/console-opteron.log > > >=20 > > > What does 'show alllocks' say? You may need to compile in WITNESS > > > support first. > > >=20 > > > Kris > >=20 > > db> show alllocks > > db> > > Ah, OK, this is a panic about lockmgr locks. 'show lockedvnods' > instead, then for each process listed do 'tr '. CC Jeff Roberson > in the reply. 'show lockedbufs' might also > be useful if your kernel is new enough. > it seems to be the unionfs: db> show lockedvnods Locked vnodes 0xffffff0061bfea28: tag union, type VDIR usecount 3, writecount 0, refcount 3 mountedhere 0 flags (VV_ROOT) lock type union: EXCL (count 1) by thread 0xffffff006209a250 (pid 104) vp=0xffffff0061bfea28, uppervp=0xffffff006199f410, lowervp=0xffffff003baa3a28 union: upper 0xffffff006199f410: tag ufs, type VDIR usecount 3, writecount 0, refcount 5 mountedhere 0 flags (VV_ROOT) v_object 0xffffff007c3a52a0 ref 0 pages 0 ino 2, on dev md0 union: lower 0xffffff003baa3a28: tag nfs, type VDIR usecount 3, writecount 0, refcount 5 mountedhere 0xffffff0031be1400 flags () v_object 0xffffff006243ce00 ref 0 pages 1 fileid 47104 fsid 0x500ff01 db> tr 104 Tracing pid 104 tid 100099 td 0xffffff006209a250 kdb_enter() at kdb_enter+0x2f panic() at panic+0x249 userret() at userret+0x131 syscall() at syscall+0x286 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (0, FreeBSD ELF64, nosys), rip = 0x8008e5218, rsp = 0x7fffffffe648, rbp = 0x7fffffffe650 --- db> show lockedbufs db> From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 17:57:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E077A16A4CE; Wed, 30 Mar 2005 17:57:03 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92EF743D31; Wed, 30 Mar 2005 17:57:03 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DGhR8-0008VH-00; Wed, 30 Mar 2005 18:57:02 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Wed, 30 Mar 2005 18:57:01 +0100 From: Michael Hopkins To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit cc: freebsd-emulation@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Package management within linux_base-debian X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 17:57:04 -0000 Hi Trevor Am trying to get a linux development environment going on a FreeBSD 5.3 amd64 server. Wanting to keep it simple and well-managed i.e. as close to ports idea as possible. Gentoo (with portage) was ideal but is apparently broken: Starting Terminal in /usr/ports/emulators/linux_base-gentoo-stage1... bash-2.05b# make ===> linux_base-gentoo-stage1-2004.3 is marked as broken: Incorrect pkg-plist. My question is - is it safe to use apt-get, dpkg and dselect with the debian port? What I mean is, does it _automatically_ know to install things in the right place (e.g. /compat/linux/usr/bin *NOT* /usr/bin)? A related question is; will those package management programs know to look for their various databases with /compat/linux/ acting as the root directory? TIA Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 18:34:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EC0616A4CE; Wed, 30 Mar 2005 18:34:43 +0000 (GMT) Received: from post.00t.org (feynman.00t.org [217.160.135.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DA643D46; Wed, 30 Mar 2005 18:34:42 +0000 (GMT) (envelope-from ulrik@00t.org) Received: from [172.24.0.14] (pD9E1F83D.dip.t-dialin.net [217.225.248.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by post.00t.org (Postfix) with ESMTP id 9D35E192BD; Wed, 30 Mar 2005 20:34:39 +0200 (CEST) Message-ID: <424AF144.2060503@00t.org> Date: Wed, 30 Mar 2005 20:34:44 +0200 From: Ulrik Guenther User-Agent: Mozilla Thunderbird 1.0 (X11/20050309) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Hopkins References: In-Reply-To: X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-emulation@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 18:34:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Heya! For me the redhat packages did not work as I wanted them to work. Maybe you should give the following tutorial a try: http://people.freebsd.org/~tjr/linux32.html There it is explained how to get the Linux32 emulation running with Slackware 10 as base (10.1 might work as well). With Slackware you will not have to mess around with creepy tools like RPM. And of course, on the Slackware mirrors you will also find pre-packaged versions of the GCC. By the way, if you still want to use RPMs, try to use the switches - --ignoreos, --ignorearch and --nodeps, these ones worked for me when installing OOo 2.0 beta. Hope I helped :) Have a nice day, Ulrik Guenther Michael Hopkins wrote: | On 30/3/05 5:22 am, "Axel Gonzalez" wrote: | | |>On Tuesday 29 March 2005 05:32, Michael Hopkins wrote: |> |>>Hi all |>> |>>I have just installed mingwin32 from the ports and it works beautifully - |>>can now port all my Unix command line code (including linking to win32 |>>libraries) to win32 with the flick of a make switch. Marvellous! |> |>Glad to know it works now.. I should have checked more often |> | | Hi Axel | | Seems to work well but not tested exhaustively across different code and | Windows versions yet. | | |>>Now to linux... I haven't tried any of the linux compatibility stuff yet, |>>either for running binaries or cross-compiling. I thought I would ask here |>>first because I have seen quite a few messages suggesting potential issues |>>on amd64. |>> |>>At the moment I am mainly interested in cross-compiling and wanting to |>>target 32-bit linux, but obviously 64-bit will be useful in the future. |>>Would like to get some advice on what to install and any kernel |>>configuration or module loading that I might need to do. |> |>This should be well documented elsewhere, if i remember correctly: |> |>on kernel, add the options: |> |>options LINPROCFS |>options COMPAT_43 |>options COMPAT_LINUX32 |> |>Install the emulators/linux_base-8 port |> |>and enable on rc.conf |> |>linux_enable="YES" |> |>After that you should have a running linux enviroment |> |>$ /compat/linux/bin/bash |>$ uname -a |>Linux moonlight 2.4.2 FreeBSD 5.3-STABLE #0: Thu Feb 3 23:08:02 CST 2005 |>amd64 amd64 amd64 GNU/Linux |> | | Did exactly these steps and got this far at 4:30am this morning! :o} | | root@Athlon ~ # cd /compat/linux/bin | root@Athlon /compat/linux/bin # ./uname -a | Linux Athlon 2.4.2 FreeBSD 5.3-RELEASE-p5 #2: Wed Mar 30 01:46:52 BST 2005 | amd64 amd64 amd64 GNU/Linux | | |>Then, the real thing, the cross compile |> |>NOTE: At this point I'm guessing, tell us if it works ;) |> |>Get a GCC RPM and install it (check the Makefile on the linux port, to see the |>flags it uses, and see you dont overwrite system GCC) |> | | This is where I got badly stuck, though I might have the answer - see below. | | I first tried about 10 RPMs from various places that are meant to be for | Redhat 8 on i386 (or i586 or i686 - I am guessing it shouldn¹t matter?) and | whenever I try to install them with the recommended command, e.g. : | | rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm | /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm | | I get this message: | | "package apt-0.5.5cnc6-fr0.rh80.1 is for a different architecture" | | I then thought that the recently-installed linux rpm might be the right way | to deal with this, so: | | /compat/linux/bin/rpm -i --ignoreos --root /compat/linux --dbpath | /var/lib/rpm /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm | | warning: /mnt/Desktop/apt-0.5.5cnc6-fr0.rh80.1.i386.rpm: V3 DSA signature: | NOKEY, key ID e42d547b | error: Failed dependencies: | rpm >= 4.0.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libstdc++ is needed by apt-0.5.5cnc6-fr0.rh80.1 | /sbin/ldconfig is needed by apt-0.5.5cnc6-fr0.rh80.1 | /bin/sh is needed by apt-0.5.5cnc6-fr0.rh80.1 | libbz2.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.1) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.1.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.2) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.2.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libc.so.6(GLIBC_2.3) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libelf.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libgcc_s.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libgcc_s.so.1(GCC_3.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libm.so.6 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libncurses.so.5 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libpopt.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libpthread.so.0 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libpthread.so.0(GLIBC_2.0) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libpthread.so.0(GLIBC_2.1) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libreadline.so.4 is needed by apt-0.5.5cnc6-fr0.rh80.1 | librpm-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 | librpmdb-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 | librpmio-4.1.so is needed by apt-0.5.5cnc6-fr0.rh80.1 | librt.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libstdc++.so.5 is needed by apt-0.5.5cnc6-fr0.rh80.1 | libstdc++.so.5(GLIBCPP_3.2) is needed by apt-0.5.5cnc6-fr0.rh80.1 | libz.so.1 is needed by apt-0.5.5cnc6-fr0.rh80.1 | | Even though all of these executables and libraries are installed as standard | in linux_base-8. | | Then another thought; use '--ignorearch' with the FreeBSD rpm command. This | seems to install linux apt as required! :o) Maybe this is the right way to | go? I will investigate further and let you know. | | |>Maybe some extra RPMs.. make, libtool etc |> |>Run gcc from the linux bash (check the path to be sure its really using |>linux's gcc) |> | | | Will try these later today. | | |>*IF* this work, you should be able to compile and run linux32 programs (you |>using a linux compiler right ?) |> | | | So I can't get to these steps until I have worked out how to install the GCC | tools for linux. As far as I can tell I have the following options: | | 1) Work out how to make RPMs work as discussed above. Would like this | anyway to be able to use more linux stuff. | | 2) Install linux_devtools from ports - but: | /usr/ports/devel/linux_devtools % make | ===> linux_devtools-8.0_3 is only for i386, and you are running amd64. | | 3) Find a tarball of the GCC toolset for RH8 i*86 and extract it into | /compat/linux | | 4) ? Any others ? | | |>For linux64, well first step is to get binaries working |> | | I will just be happy to have 32-bit working for now! | | Thanks for the input | | Michael | | | | _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ | | _/ _/ _/_/_/ Hopkins Research Ltd | _/ _/ _/ _/ | _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ | _/ _/ _/ _/ | _/ _/ _/ _/ 'touch the future' | | _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ | | | _______________________________________________ | 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" | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCSvFEy06DkvPH780RAo/eAJwPYUdswhVwX1+eAw9UWq82kBmZWQCgoZdZ dwwjNDwP+/FxC/6V8Ve1Csc= =VHf7 -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 18:45:26 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 816CA16A4CE for ; Wed, 30 Mar 2005 18:45:26 +0000 (GMT) Received: from post.00t.org (feynman.00t.org [217.160.135.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B81543D3F for ; Wed, 30 Mar 2005 18:45:26 +0000 (GMT) (envelope-from ulrik@00t.org) Received: from [172.24.0.14] (pD9E1F83D.dip.t-dialin.net [217.225.248.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by post.00t.org (Postfix) with ESMTP id B14AF192BD; Wed, 30 Mar 2005 20:45:24 +0200 (CEST) Message-ID: <424AF3CE.4080209@00t.org> Date: Wed, 30 Mar 2005 20:45:34 +0200 From: Ulrik Guenther User-Agent: Mozilla Thunderbird 1.0 (X11/20050309) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> In-Reply-To: <20050329211942.P59551@carver.gumbysoft.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 18:45:26 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, NVidia currently seems not wanting to make binary drivers for FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread in their forum with the plea for drivers for AMD64, the URL is http://www.nvnews.net/vbulletin/showthread.php?t=41545 Maybe it helps if many people post there and tell the guys at NVidia that there really is need for these certain drivers. Thanks for listening, Ulrik Doug White wrote: | On Tue, 29 Mar 2005, Astrodog wrote: | | |>Through about an hour of tinkering, I've gotten NVidia's i386 driver |>to compile, sans final linking, for AMD64. | | | [...] | | |>The error I get is: |>ld: Relocatable linking with relocations from format |>elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is |>not supported. | | | This message doesn't lie -- we don't support mixed-mode objects. Solaris | doesn't either and I doubt we have plans to grow this support. You'll | need all amd64-compiled object files; without them, you're sunk. | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCSvPOy06DkvPH780RAntEAJ4igvPNeKcTIMOPYGj5bF32W2GRKwCeNcmN Bt+NSQeTEce4Y2LvU0Bw46k= =AfOf -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 20:20:09 2005 Return-Path: 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 1A65516A4CF for ; Wed, 30 Mar 2005 20:20:09 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BD0543D67 for ; Wed, 30 Mar 2005 20:20:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2UKK8hi021802 for ; Wed, 30 Mar 2005 20:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2UKK8e4021801; Wed, 30 Mar 2005 20:20:08 GMT (envelope-from gnats) Resent-Date: Wed, 30 Mar 2005 20:20:08 GMT Resent-Message-Id: <200503302020.j2UKK8e4021801@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, guo Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FE6016A4CE for ; Wed, 30 Mar 2005 20:11:15 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21F5E43D53 for ; Wed, 30 Mar 2005 20:11:15 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j2UKBEXd043686 for ; Wed, 30 Mar 2005 20:11:14 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j2UKBEqK043685; Wed, 30 Mar 2005 20:11:14 GMT (envelope-from nobody) Message-Id: <200503302011.j2UKBEqK043685@www.freebsd.org> Date: Wed, 30 Mar 2005 20:11:14 GMT From: guo To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/79381: AMD64 build if "device ath_hal" "device ath" fails X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 20:20:09 -0000 >Number: 79381 >Category: amd64 >Synopsis: AMD64 build if "device ath_hal" "device ath" fails >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Mar 30 20:20:08 GMT 2005 >Closed-Date: >Last-Modified: >Originator: guo >Release: 5-CURRENT >Organization: >Environment: FreeBSD p22-bsd.ixwin.com 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Sun Mar 20 00:48:36 CST 2005 tc@p22-bsd.ixwin.com:/usr/obj/usr/src/sys/p22at amd64 >Description: make buildkernl breaks with error messages: ah_osdep.o(.text+0x157): In function `ath_hal_modevent': : undefined reference to `ath_hal_version' ah_osdep.o(.data+0x1b8): undefined reference to `ath_hal_version' if_ath.o(.text+0x1ed2): In function `ath_start': : undefined reference to `ath_hal_computetxtime' if_ath.o(.text+0x1f43): In function `ath_start': : undefined reference to `ath_hal_computetxtime' if_ath.o(.text+0x268a): In function `ath_start': : undefined reference to `ath_hal_computetxtime' if_ath.o(.text+0x26af): In function `ath_start': : undefined reference to `ath_hal_computetxtime' if_ath.o(.text+0x4a47): In function `ath_attach': : undefined reference to `ath_hal_attach' if_ath.o(.text+0x4b58): In function `ath_attach': : undefined reference to `ath_hal_init_channels' if_ath.o(.text+0x4b80): In function `ath_attach': : undefined reference to `ath_hal_mhz2ieee' if_ath_pci.o(.text+0xad): In function `ath_pci_probe': : undefined reference to `ath_hal_probe' *** Error code 1 >How-To-Repeat: 1. add the following two lines into the sys/amd64/conf/GENERIC kernel device ath device ath_hal 2. cd /usr/src 3. make buildkernel >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 20:35:21 2005 Return-Path: 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 BD2B716A4CE; Wed, 30 Mar 2005 20:35:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F84043D1F; Wed, 30 Mar 2005 20:35:21 +0000 (GMT) (envelope-from brooks@FreeBSD.org) Received: from freefall.freebsd.org (brooks@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2UKZL0t024093; Wed, 30 Mar 2005 20:35:21 GMT (envelope-from brooks@freefall.freebsd.org) Received: (from brooks@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2UKZLFT024089; Wed, 30 Mar 2005 20:35:21 GMT (envelope-from brooks) Date: Wed, 30 Mar 2005 20:35:21 GMT From: Brooks Davis Message-Id: <200503302035.j2UKZLFT024089@freefall.freebsd.org> To: embix@optushome.com.au, brooks@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/79381: AMD64 build if "device ath_hal" "device ath" fails X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 20:35:21 -0000 Synopsis: AMD64 build if "device ath_hal" "device ath" fails State-Changed-From-To: open->closed State-Changed-By: brooks State-Changed-When: Wed Mar 30 20:33:42 GMT 2005 State-Changed-Why: There is no ath_hal binary for amd64 on 5.x and the support will not be MFC'd from 6.x due to major source incompatabilities. If you want to use Atheros cards on amd64, you will have to run 6-CURRENT. http://www.freebsd.org/cgi/query-pr.cgi?pr=79381 From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 21:21:36 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7750816A4CE for ; Wed, 30 Mar 2005 21:21:36 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1817443D1D for ; Wed, 30 Mar 2005 21:21:36 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so322214wra for ; Wed, 30 Mar 2005 13:21:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=HDKTH9FamuA8fGzmqLzNv1Y7k0zh1Nbbyxr62RS+0dyiszj78zJDnva5HQLRpe6aNP7/h0ssjG1IxYdvDh6hj66cJC9yU0alwQTp5GV4qYrppgkmukFcbBAobVDhYCFHMjHUEx6VtWBltGLgZP7Fuie17XuHNJ14Lv1DGV/M3+Q= Received: by 10.54.52.42 with SMTP id z42mr146913wrz; Wed, 30 Mar 2005 13:21:31 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 30 Mar 2005 13:20:54 -0800 (PST) Message-ID: <2fd864e05033013208e43bf9@mail.gmail.com> Date: Wed, 30 Mar 2005 13:20:54 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <424AF3CE.4080209@00t.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> <424AF3CE.4080209@00t.org> Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 21:21:36 -0000 On Wed, 30 Mar 2005 20:45:34 +0200, Ulrik Guenther wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello everyone, > > NVidia currently seems not wanting to make binary drivers for > FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread in > their forum with the plea for drivers for AMD64, the URL is > > http://www.nvnews.net/vbulletin/showthread.php?t=41545 > > Maybe it helps if many people post there and tell the guys at NVidia > that there really is need for these certain drivers. > > Thanks for listening, > > Ulrik > > Doug White wrote: > | On Tue, 29 Mar 2005, Astrodog wrote: > | > | > |>Through about an hour of tinkering, I've gotten NVidia's i386 driver > |>to compile, sans final linking, for AMD64. > | > | > | [...] > | > | > |>The error I get is: > |>ld: Relocatable linking with relocations from format > |>elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is > |>not supported. > | > | > | This message doesn't lie -- we don't support mixed-mode objects. Solaris > | doesn't either and I doubt we have plans to grow this support. You'll > | need all amd64-compiled object files; without them, you're sunk. > | > Perhaps it would be possible to statically link things to the kernel itself? ld doesn't seem to complain unless you try to make a relocatable object. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 21:21:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AADDA16A4CE for ; Wed, 30 Mar 2005 21:21:40 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C29743D45 for ; Wed, 30 Mar 2005 21:21:40 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so322262wra for ; Wed, 30 Mar 2005 13:21:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=cE2BUOQ0WlW1AR/6n9Tu08yHofZ9UvnzQjtdElGugVTWzkjT7KDbfwy/xp3TWcFQLFIh7sQBt+1jnU26CLlku9ouK3bOc7Cat9W7YnLXcb2El97YSXTTHWlHdC3Wj/0ZYDCvYrzLyRDWsDrDh/wPRd/5cgL9ewAmw6b0IXlx9fM= Received: by 10.54.7.4 with SMTP id 4mr879616wrg; Wed, 30 Mar 2005 13:21:31 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 30 Mar 2005 13:20:54 -0800 (PST) Message-ID: <2fd864e05033013208e43bf9@mail.gmail.com> Date: Wed, 30 Mar 2005 13:20:54 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <424AF3CE.4080209@00t.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> <424AF3CE.4080209@00t.org> Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 21:21:40 -0000 On Wed, 30 Mar 2005 20:45:34 +0200, Ulrik Guenther wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello everyone, > > NVidia currently seems not wanting to make binary drivers for > FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread in > their forum with the plea for drivers for AMD64, the URL is > > http://www.nvnews.net/vbulletin/showthread.php?t=41545 > > Maybe it helps if many people post there and tell the guys at NVidia > that there really is need for these certain drivers. > > Thanks for listening, > > Ulrik > > Doug White wrote: > | On Tue, 29 Mar 2005, Astrodog wrote: > | > | > |>Through about an hour of tinkering, I've gotten NVidia's i386 driver > |>to compile, sans final linking, for AMD64. > | > | > | [...] > | > | > |>The error I get is: > |>ld: Relocatable linking with relocations from format > |>elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is > |>not supported. > | > | > | This message doesn't lie -- we don't support mixed-mode objects. Solaris > | doesn't either and I doubt we have plans to grow this support. You'll > | need all amd64-compiled object files; without them, you're sunk. > | > Perhaps it would be possible to statically link things to the kernel itself? ld doesn't seem to complain unless you try to make a relocatable object. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 21:29:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF48216A4CE for ; Wed, 30 Mar 2005 21:29:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4779F43D5A for ; Wed, 30 Mar 2005 21:29:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2ULXcbb012470; Wed, 30 Mar 2005 14:33:39 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B19D0.6010905@samsco.org> Date: Wed, 30 Mar 2005 14:27:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> <424AF3CE.4080209@00t.org> <2fd864e05033013208e43bf9@mail.gmail.com> In-Reply-To: <2fd864e05033013208e43bf9@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 21:29:53 -0000 Astrodog wrote: > On Wed, 30 Mar 2005 20:45:34 +0200, Ulrik Guenther wrote: > >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Hello everyone, >> >>NVidia currently seems not wanting to make binary drivers for >>FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread in >>their forum with the plea for drivers for AMD64, the URL is >> >>http://www.nvnews.net/vbulletin/showthread.php?t=41545 >> >>Maybe it helps if many people post there and tell the guys at NVidia >>that there really is need for these certain drivers. >> >>Thanks for listening, >> >>Ulrik >> >>Doug White wrote: >>| On Tue, 29 Mar 2005, Astrodog wrote: >>| >>| >>|>Through about an hour of tinkering, I've gotten NVidia's i386 driver >>|>to compile, sans final linking, for AMD64. >>| >>| >>| [...] >>| >>| >>|>The error I get is: >>|>ld: Relocatable linking with relocations from format >>|>elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is >>|>not supported. >>| >>| >>| This message doesn't lie -- we don't support mixed-mode objects. Solaris >>| doesn't either and I doubt we have plans to grow this support. You'll >>| need all amd64-compiled object files; without them, you're sunk. >>| >> > > > Perhaps it would be possible to statically link things to the kernel > itself? ld doesn't seem to complain unless you try to make a > relocatable object. In case Doug's message wasn't clear enough: We do not support mixed-mode objects. You cannot run i386 object code in an amd64 kernel. It doesn't matter whether or not ld stops you, it's just a simple fact of life. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:08:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A814116A4CE for ; Wed, 30 Mar 2005 22:08:01 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 389FA43D39 for ; Wed, 30 Mar 2005 22:08:01 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so338108wra for ; Wed, 30 Mar 2005 14:08:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=P9xRhhupI9trZnPfxFzMplRBDX9G4TOAfof8lFCx6noev9xf862g8o9obGld6x6ZKcXJErwxsd8splQFoCiNjmhylq5UkelAFExMDdTDjvABj0TdPmGpywgqBV7Qib8yVde78ofhQTGa08IRLHxZ+br7psDowtqRYKSXuftN15o= Received: by 10.54.7.4 with SMTP id 4mr917753wrg; Wed, 30 Mar 2005 14:08:00 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 30 Mar 2005 14:08:00 -0800 (PST) Message-ID: <2fd864e05033014084d5a0ef9@mail.gmail.com> Date: Wed, 30 Mar 2005 14:08:00 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <424B19D0.6010905@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> <424AF3CE.4080209@00t.org> <2fd864e05033013208e43bf9@mail.gmail.com> <424B19D0.6010905@samsco.org> Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:08:01 -0000 On Wed, 30 Mar 2005 14:27:44 -0700, Scott Long wrote: > Astrodog wrote: > > On Wed, 30 Mar 2005 20:45:34 +0200, Ulrik Guenther wrote: > > > >>-----BEGIN PGP SIGNED MESSAGE----- > >>Hash: SHA1 > >> > >>Hello everyone, > >> > >>NVidia currently seems not wanting to make binary drivers for > >>FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread in > >>their forum with the plea for drivers for AMD64, the URL is > >> > >>http://www.nvnews.net/vbulletin/showthread.php?t=41545 > >> > >>Maybe it helps if many people post there and tell the guys at NVidia > >>that there really is need for these certain drivers. > >> > >>Thanks for listening, > >> > >>Ulrik > >> > >>Doug White wrote: > >>| On Tue, 29 Mar 2005, Astrodog wrote: > >>| > >>| > >>|>Through about an hour of tinkering, I've gotten NVidia's i386 driver > >>|>to compile, sans final linking, for AMD64. > >>| > >>| > >>| [...] > >>| > >>| > >>|>The error I get is: > >>|>ld: Relocatable linking with relocations from format > >>|>elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64 (nvidia.ko) is > >>|>not supported. > >>| > >>| > >>| This message doesn't lie -- we don't support mixed-mode objects. Solaris > >>| doesn't either and I doubt we have plans to grow this support. You'll > >>| need all amd64-compiled object files; without them, you're sunk. > >>| > >> > > > > > > Perhaps it would be possible to statically link things to the kernel > > itself? ld doesn't seem to complain unless you try to make a > > relocatable object. > > In case Doug's message wasn't clear enough: > > We do not support mixed-mode objects. You cannot run i386 object code > in an amd64 kernel. It doesn't matter whether or not ld stops you, it's > just a simple fact of life. > > Scott > Ah, damn. I guess I'll move on to my second idea, which is a 64-bit "Wrapper" for the 32-bit module, so that the module is never actually part of the kernel. I suspect thats going to be harder than I'm actually anticipating, but, oughta keep me busy for awhile atleast. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:24:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65CD816A4CE; Wed, 30 Mar 2005 22:24:45 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 348E743D1F; Wed, 30 Mar 2005 22:24:42 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 41D7385617; Thu, 31 Mar 2005 07:54:39 +0930 (CST) Date: Thu, 31 Mar 2005 07:54:39 +0930 From: Greg 'groggy' Lehey To: FreeBSD Stable Users Message-ID: <20050330222439.GU84137@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2tWkrNKppd65XSnD" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD-amd64@FreeBSD.org Subject: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:24:45 -0000 --2tWkrNKppd65XSnD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've recently acquired an AMD64 box (dual Opteron 242, SiS Master@-FAR motherboard (http://www.msi.com.tw/program/products/server/svr/pro_svr_detail.php?UID= =3D484). See below for more details). I find it very unstable running with 8 GB memory, though 4 GB are not a problem. At first I thought it was the onboard peripherals, but after disabling them it still persisted. What's unstable? I only once got it through the boot process. Running a 5.3-RELEASE i386 kernel it panics, though I haven't investigated the panic (yet), since I'm not interested in the i386 kernel. The amd64 5.4-PRERELEASE kernel just hangs/freezes. When the peripherals are enabled, it's after probing the onboard NIC (bge) and before probing SATA (no drives present). I've done a verbose boot, of course, but no additional information is present. The NIC is recognized, and that's all. Without the peripherals, but with a 3Com 3c905 PCI NIC, it continues beyond this point, but doesn't enable the NIC. I don't have dmesg output for these attempts, so I can't produce the exact message, and I suspect it's not important. It continues until trying to mount NFS file systems, where it hangs for obvious reasons. Pressing ^C causes the system to either panic (and be unable to dump because I don't have that much swap) or just hang. None of these problems occur when I use 4 GB memory. About the only strangeness, which seems to come from the BIOS, is that it recognizes only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB memory. I realize that this isn't enough to diagnose the problem. The reason for this message now is to ask: 1. Has anybody else seen this problem? 2. Has anybody else used this hardware configuration and *not* seen this problem? 3. Where should I look next? I'm attaching the (non-verbose) dmesg from a successful boot. Greg -- See complete headers for address and phone numbers. Mar 30 14:17:16 obelix kernel: FreeBSD 5.4-PRERELEASE #0: Tue Mar 22 04:02:= 17 UTC 2005 Mar 30 14:17:16 obelix kernel: root@obelix:/usr/obj/src/FreeBSD/OBELIX/src/= sys/OBELIX Mar 30 14:17:16 obelix kernel: Timecounter "i8254" frequency 1193182 Hz qua= lity 0 Mar 30 14:17:16 obelix kernel: CPU: AMD Opteron(tm) Processor 242 (1603.65-= MHz K8-class CPU) Mar 30 14:17:16 obelix kernel: Origin =3D "AuthenticAMD" Id =3D 0xf5a Ste= pping =3D 10 Mar 30 14:17:16 obelix kernel: Features=3D0x78bfbff Mar 30 14:17:16 obelix kernel: AMD Features=3D0xe0500800 Mar 30 14:17:16 obelix kernel: real memory =3D 3756916736 (3582 MB) Mar 30 14:17:16 obelix kernel: avail memory =3D 3623907328 (3456 MB) Mar 30 14:17:16 obelix kernel: ACPI APIC Table: Mar 30 14:17:16 obelix kernel: FreeBSD/SMP: Multiprocessor System Detected:= 2 CPUs Mar 30 14:17:16 obelix kernel: cpu0 (BSP): APIC ID: 0 Mar 30 14:17:16 obelix kernel: cpu1 (AP): APIC ID: 1 Mar 30 14:17:16 obelix kernel: ioapic0: Changing APIC ID to 2 Mar 30 14:17:16 obelix kernel: ioapic0 irqs 0-23 on motherboa= rd Mar 30 14:17:16 obelix kernel: acpi0: on motherboard Mar 30 14:17:16 obelix kernel: acpi0: Power Button (fixed) Mar 30 14:17:16 obelix kernel: Timecounter "ACPI-fast" frequency 3579545 Hz= quality 1000 Mar 30 14:17:16 obelix kernel: acpi_timer0: <24-bit timer at 3.579545MHz> p= ort 0x4008-0x400b on acpi0 Mar 30 14:17:16 obelix kernel: cpu0: on acpi0 Mar 30 14:17:16 obelix kernel: cpu1: on acpi0 Mar 30 14:17:16 obelix kernel: acpi_button0: on acpi0 Mar 30 14:17:16 obelix kernel: pcib0: port 0xcf8-0xc= ff on acpi0 Mar 30 14:17:16 obelix kernel: pci0: on pcib0 Mar 30 14:17:16 obelix kernel: pcib1: at device 1.0 on pci0 Mar 30 14:17:16 obelix kernel: pci1: on pcib1 Mar 30 14:17:16 obelix kernel: pci1: at device 0.0 (no drive= r attached) Mar 30 14:17:16 obelix kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port= 0xd000-0xd07f mem 0xfb000000-0xfb00007f irq=20 18 at device 7.0 on pci0 Mar 30 14:17:16 obelix kernel: miibus0: on xl0 Mar 30 14:17:16 obelix kernel: xlphy0: <3c905C 10/100 internal PHY> on miib= us0 Mar 30 14:17:16 obelix kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 10= 0baseTX-FDX, auto Mar 30 14:17:16 obelix kernel: xl0: Ethernet address: 00:50:da:cf:17:d3 Mar 30 14:17:16 obelix kernel: atapci0: port = 0xd400-0xd40f,0x376,0x170-0x177,0x3f6,0x1f0-0 x1f7 at device 15.0 on pci0 Mar 30 14:17:16 obelix kernel: ata0: channel #0 on atapci0 Mar 30 14:17:16 obelix kernel: ata1: channel #1 on atapci0 Mar 30 14:17:16 obelix kernel: uhci0: port 0xd8= 00-0xd81f irq 21 at device 16.0 on pci0 Mar 30 14:17:16 obelix kernel: usb0: on uhci0 Mar 30 14:17:16 obelix kernel: usb0: USB revision 1.0 Mar 30 14:17:16 obelix kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.0= 0/1.00, addr 1 Mar 30 14:17:16 obelix kernel: uhub0: 2 ports with 2 removable, self powered Mar 30 14:17:16 obelix kernel: uhci1: port 0xdc= 00-0xdc1f irq 21 at device 16.1 on pci0 Mar 30 14:17:16 obelix kernel: usb1: on uhci1 Mar 30 14:17:16 obelix kernel: usb1: USB revision 1.0 Mar 30 14:17:16 obelix kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.0= 0/1.00, addr 1 Mar 30 14:17:16 obelix kernel: uhub1: 2 ports with 2 removable, self powered Mar 30 14:17:16 obelix kernel: uhci2: port 0xe0= 00-0xe01f irq 21 at device 16.2 on pci0 Mar 30 14:17:16 obelix kernel: usb2: on uhci2 Mar 30 14:17:16 obelix kernel: usb2: USB revision 1.0 Mar 30 14:17:16 obelix kernel: uhub2: VIA UHCI root hub, class 9/0, rev 1.0= 0/1.00, addr 1 Mar 30 14:17:16 obelix kernel: uhub2: 2 ports with 2 removable, self powered Mar 30 14:17:16 obelix kernel: pci0: at device 16.4 (no d= river attached) Mar 30 14:17:16 obelix kernel: isab0: at device 17.0 on pc= i0 Mar 30 14:17:16 obelix kernel: isa0: on isab0 Mar 30 14:17:16 obelix kernel: pci0: at device 17.5 (no= driver attached) Mar 30 14:17:16 obelix kernel: acpi_tz0: on acpi0 Mar 30 14:17:16 obelix kernel: fdc0: port 0x3f7,0= x3f0-0x3f5 irq 6 drq 2 on acpi0 Mar 30 14:17:16 obelix kernel: sio0: <16550A-compatible COM port> port 0x3f= 8-0x3ff irq 4 flags 0x10 on acpi0 Mar 30 14:17:16 obelix kernel: sio0: type 16550A Mar 30 14:17:16 obelix kernel: sio1: <16550A-compatible COM port> port 0x2f= 8-0x2ff irq 3 on acpi0 Mar 30 14:17:16 obelix kernel: sio1: type 16550A Mar 30 14:17:16 obelix kernel: ppc0: port = 0x778-0x77b,0x378-0x37f irq 7 on acpi0 Mar 30 14:17:16 obelix kernel: ppc0: Generic chipset (NIBBLE-only) in COMPA= TIBLE mode Mar 30 14:17:16 obelix kernel: ppbus0: on ppc0 Mar 30 14:17:16 obelix kernel: plip0: on ppbus0 Mar 30 14:17:16 obelix kernel: lpt0: on ppbus0 Mar 30 14:17:16 obelix kernel: lpt0: Interrupt-driven port Mar 30 14:17:16 obelix kernel: ppi0: on ppbus0 Mar 30 14:17:16 obelix kernel: atkbdc0: port = 0x64,0x60 irq 1 on acpi0 Mar 30 14:17:16 obelix kernel: atkbd0: flags 0x1 irq 1 on atk= bdc0 Mar 30 14:17:16 obelix kernel: kbd0 at atkbd0 Mar 30 14:17:16 obelix kernel: orm0: at iomem 0xd0000-0xd= 07ff,0xc0000-0xcffff on isa0 Mar 30 14:17:16 obelix kernel: sc0: at flags 0x100 on isa0 Mar 30 14:17:16 obelix kernel: sc0: VGA <16 virtual consoles, flags=3D0x300> Mar 30 14:17:16 obelix kernel: vga0: at port 0x3c0-0x3df = iomem 0xa0000-0xbffff on isa0 Mar 30 14:17:16 obelix kernel: Timecounters tick every 1.000 msec Mar 30 14:17:16 obelix kernel: ad0: 190782MB [387621/16/6= 3] at ata0-master UDMA100 Mar 30 14:17:16 obelix kernel: ad1: 190782MB [387621/16/6= 3] at ata0-slave UDMA100 Mar 30 14:17:16 obelix kernel: acd0: DVDR at = ata1-master UDMA66 Mar 30 14:17:16 obelix kernel: SMP: AP CPU #1 Launched! Mar 30 14:17:16 obelix kernel: Mounting root from ufs:/dev/ad0s1a --2tWkrNKppd65XSnD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSycnIubykFB6QiMRAnV6AKCyRuce58cEVhAKoTM1i97zaNYMkwCgl7Ab ANyhrh7QeNVjUWfx0uprP24= =kMQs -----END PGP SIGNATURE----- --2tWkrNKppd65XSnD-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:32:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A391E16A4CE; Wed, 30 Mar 2005 22:32:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 969AE43D49; Wed, 30 Mar 2005 22:32:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2UMadHg012726; Wed, 30 Mar 2005 15:36:39 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B288D.80303@samsco.org> Date: Wed, 30 Mar 2005 15:30:37 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> In-Reply-To: <20050330222439.GU84137@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:32:53 -0000 Greg 'groggy' Lehey wrote: > I've recently acquired an AMD64 box (dual Opteron 242, SiS Master@-FAR > motherboard > (http://www.msi.com.tw/program/products/server/svr/pro_svr_detail.php?UID=484). > See below for more details). I find it very unstable running with 8 > GB memory, though 4 GB are not a problem. At first I thought it was > the onboard peripherals, but after disabling them it still persisted. > > What's unstable? I only once got it through the boot process. > Running a 5.3-RELEASE i386 kernel it panics, though I haven't > investigated the panic (yet), since I'm not interested in the i386 > kernel. The amd64 5.4-PRERELEASE kernel just hangs/freezes. When the > peripherals are enabled, it's after probing the onboard NIC (bge) and > before probing SATA (no drives present). I've done a verbose boot, of > course, but no additional information is present. The NIC is > recognized, and that's all. > > Without the peripherals, but with a 3Com 3c905 PCI NIC, it continues > beyond this point, but doesn't enable the NIC. I don't have dmesg > output for these attempts, so I can't produce the exact message, and I > suspect it's not important. It continues until trying to mount NFS > file systems, where it hangs for obvious reasons. Pressing ^C causes > the system to either panic (and be unable to dump because I don't have > that much swap) or just hang. > > None of these problems occur when I use 4 GB memory. About the only > strangeness, which seems to come from the BIOS, is that it recognizes > only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB > memory. > > I realize that this isn't enough to diagnose the problem. The reason > for this message now is to ask: > > 1. Has anybody else seen this problem? > 2. Has anybody else used this hardware configuration and *not* seen > this problem? > 3. Where should I look next? > > I'm attaching the (non-verbose) dmesg from a successful boot. > > Greg > -- > See complete headers for address and phone numbers. > 5.3-RELEASE has a lot of problems with >4GB due to busdma issues. Those should no longer be an issue in RELENG_5, including 5.4-PRE. You'll need to dig in and provide some more details, I guess. I have an HDAMA dual Opteron system that behaves fine now with 8GB of RAM, so your problem might lie with particular hardware and/or drivers. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:35:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D053216A4CE; Wed, 30 Mar 2005 22:35:46 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6D6743D46; Wed, 30 Mar 2005 22:35:46 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j2UMZkqi004792; Wed, 30 Mar 2005 14:35:46 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j2UMZkXk004791; Wed, 30 Mar 2005 14:35:46 -0800 (PST) (envelope-from sgk) Date: Wed, 30 Mar 2005 14:35:46 -0800 From: Steve Kargl To: "Greg 'groggy' Lehey" Message-ID: <20050330223546.GA4705@troutmask.apl.washington.edu> References: <20050330222439.GU84137@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050330222439.GU84137@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:35:47 -0000 On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: > None of these problems occur when I use 4 GB memory. About the only > strangeness, which seems to come from the BIOS, is that it recognizes > only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB > memory. > > I realize that this isn't enough to diagnose the problem. The reason > for this message now is to ask: > > 1. Has anybody else seen this problem? > 2. Has anybody else used this hardware configuration and *not* seen > this problem? > 3. Where should I look next? > Have you run sysutils/memtest86 with the 8 GB? I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB Reg. ECC DIMMs. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:38:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31F9016A4CE; Wed, 30 Mar 2005 22:38:14 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABBAC43D46; Wed, 30 Mar 2005 22:38:13 +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.1/8.13.1) with ESMTP id j2UMcDFJ065064; Wed, 30 Mar 2005 17:38:13 -0500 (EST) (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.1/8.13.1) with ESMTP id j2UMcD6j077050; Wed, 30 Mar 2005 17:38:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D23F67306E; Wed, 30 Mar 2005 17:38:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050330223812.D23F67306E@freebsd-current.sentex.ca> Date: Wed, 30 Mar 2005 17:38:12 -0500 (EST) X-Virus-Scanned: ClamAV 0.82/796/Wed Mar 30 16:28:33 2005 on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:38:14 -0000 TB --- 2005-03-30 21:02:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-03-30 21:02:14 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-03-30 21:02:14 - checking out the source tree TB --- 2005-03-30 21:02:14 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-03-30 21:02:14 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-03-30 21:09:02 - building world (CFLAGS=-O2 -pipe) TB --- 2005-03-30 21:09:02 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-30 21:09:02 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-03-30 22:18:02 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-03-30 22:18:02 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-30 22:18:02 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Mar 30 22:18:02 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Wed Mar 30 22:33:13 UTC 2005 TB --- 2005-03-30 22:33:13 - generating LINT kernel config TB --- 2005-03-30 22:33:13 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-03-30 22:33:13 - /usr/bin/make -B LINT TB --- 2005-03-30 22:33:13 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-03-30 22:33:13 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-03-30 22:33:13 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Mar 30 22:33:13 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:334: warning: passing arg 1 of `ata_reinit' from incompatible pointer type /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:417: warning: implicit declaration of function `ata_prtdev' /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:417: warning: nested extern declaration of `ata_prtdev' /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:494: error: structure has no member named `device' /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c: In function `atapi_cb': /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:567: error: structure has no member named `device' /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c: In function `get_ata_device': /tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/atapi-cam.c:797: error: structure has no member named `device' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-03-30 22:38:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-03-30 22:38:12 - ERROR: failed to build lint kernel TB --- 2005-03-30 22:38:12 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:43:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 399CA16A4CE; Wed, 30 Mar 2005 22:43:56 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7946F43D39; Wed, 30 Mar 2005 22:43:54 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id E2B3A85666; Thu, 31 Mar 2005 08:13:51 +0930 (CST) Date: Thu, 31 Mar 2005 08:13:51 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050330224351.GV84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <424B288D.80303@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HKOZ/JADkehwFk9I" Content-Disposition: inline In-Reply-To: <424B288D.80303@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:43:56 -0000 --HKOZ/JADkehwFk9I Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> I've recently acquired an AMD64 box ... >> >> What's unstable? ... The amd64 5.4-PRERELEASE kernel just >> hangs/freezes. > > 5.3-RELEASE has a lot of problems with >4GB due to busdma issues. > Those should no longer be an issue in RELENG_5, including 5.4-PRE. They appear to be. >> I realize that this isn't enough to diagnose the problem. The reason >> for this message now is to ask: >> >> 3. Where should I look next? > > You'll need to dig in and provide some more details, I guess. Yes, my guess too. > I have an HDAMA dual Opteron system that behaves fine now with 8GB > of RAM, so your problem might lie with particular hardware and/or > drivers. As I described, it doesn't appear to be the drivers. Greg -- See complete headers for address and phone numbers. --HKOZ/JADkehwFk9I Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSyunIubykFB6QiMRAk78AJ9E/ZVmvOXdaXisc9acZ53S9miVBgCeKjV6 M6j6ZNR80tIaoCjVGTeHXx0= =WgK7 -----END PGP SIGNATURE----- --HKOZ/JADkehwFk9I-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:44:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B34B16A4D5; Wed, 30 Mar 2005 22:44:48 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4438C43D53; Wed, 30 Mar 2005 22:44:47 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 37F288564D; Thu, 31 Mar 2005 08:14:45 +0930 (CST) Date: Thu, 31 Mar 2005 08:14:45 +0930 From: Greg 'groggy' Lehey To: Steve Kargl Message-ID: <20050330224445.GW84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BkCcXYe/IK2urb/q" Content-Disposition: inline In-Reply-To: <20050330223546.GA4705@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:44:48 -0000 --BkCcXYe/IK2urb/q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: > On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: >> None of these problems occur when I use 4 GB memory. About the only >> strangeness, which seems to come from the BIOS, is that it recognizes >> only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB >> memory. >> >> I realize that this isn't enough to diagnose the problem. The reason >> for this message now is to ask: >> >> 1. Has anybody else seen this problem? >> 2. Has anybody else used this hardware configuration and *not* seen >> this problem? >> 3. Where should I look next? > > Have you run sysutils/memtest86 with the 8 GB? Heh. Difficult when the system doesn't run. > I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB > Reg. ECC DIMMs. OK, this makes sense. It might also explain why the 4 GB configuration only recognizes 3.5 GB. Greg -- See complete headers for address and phone numbers. --BkCcXYe/IK2urb/q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSyvdIubykFB6QiMRAqEMAJ4rCxVHAHy62OIXn5Q2ENeOKXozVACgrWqZ UT4k8Ij7ChT8g0yUZ6UmBjQ= =zVJ2 -----END PGP SIGNATURE----- --BkCcXYe/IK2urb/q-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 22:57:15 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0A0216A4CE; Wed, 30 Mar 2005 22:57:15 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8121F43D41; Wed, 30 Mar 2005 22:57:15 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j2UMvFVs004979; Wed, 30 Mar 2005 14:57:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j2UMvF9x004978; Wed, 30 Mar 2005 14:57:15 -0800 (PST) (envelope-from sgk) Date: Wed, 30 Mar 2005 14:57:15 -0800 From: Steve Kargl To: "Greg 'groggy' Lehey" Message-ID: <20050330225715.GA4816@troutmask.apl.washington.edu> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050330224445.GW84137@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 22:57:15 -0000 On Thu, Mar 31, 2005 at 08:14:45AM +0930, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: > > On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: > >> None of these problems occur when I use 4 GB memory. About the only > >> strangeness, which seems to come from the BIOS, is that it recognizes > >> only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB > >> memory. > >> > >> I realize that this isn't enough to diagnose the problem. The reason > >> for this message now is to ask: > >> > >> 3. Where should I look next? > > > > Have you run sysutils/memtest86 with the 8 GB? > > Heh. Difficult when the system doesn't run. That's what happens when 1 of 8 (1 of 4?) DIMM is bad :-) > > I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB > > Reg. ECC DIMMs. > > OK, this makes sense. It might also explain why the 4 GB > configuration only recognizes 3.5 GB. Search amd64 mailing list. The missing memory is reserved for something which escapes me at the moment. Similar to the infamous ISA memory hole. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:03:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D402116A4CE; Wed, 30 Mar 2005 23:03:19 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 215FA43D31; Wed, 30 Mar 2005 23:03:19 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2UN772D012921; Wed, 30 Mar 2005 16:07:07 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B2FBA.1020102@samsco.org> Date: Wed, 30 Mar 2005 16:01:14 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> In-Reply-To: <20050330224445.GW84137@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:03:20 -0000 Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: > >>On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: >> >>>None of these problems occur when I use 4 GB memory. About the only >>>strangeness, which seems to come from the BIOS, is that it recognizes >>>only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB >>>memory. >>> >>>I realize that this isn't enough to diagnose the problem. The reason >>>for this message now is to ask: >>> >>>1. Has anybody else seen this problem? >>>2. Has anybody else used this hardware configuration and *not* seen >>> this problem? >>>3. Where should I look next? >> >>Have you run sysutils/memtest86 with the 8 GB? > > > Heh. Difficult when the system doesn't run. > > >>I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB >>Reg. ECC DIMMs. > > > OK, this makes sense. It might also explain why the 4 GB > configuration only recognizes 3.5 GB. > No, and I'm going to make this an FAQ and post it in a very obvious place, since 4+ GB is so easy to get and people don't seem to understand the PC architecture very well. Almost all systems put the PCI Memory Mapped IO window into the 3.75-4GB region of the physical memory map. The registers for the APICs and other system resources are also typically in this region. Now with PCI-Express, the Memory Mapped PCI config registers are typically being mapped in the 3.5-3.75GB range. The memory controllers, host bridges, north-bridges, and/or whatever else glues the memory to the bus to the CPU decode these addresses into PCI cycles, not RAM cycles. Some systems are smart and re-map the RAM that is hidden by these holes into a region >4GB. Some systems are dumb, though, and just deny you access to the RAM that is covered up. It's very much like the old days of the XT/AT architecture when you had 1MB of RAM but everything above 640k was hidden by the VGA framebuffer, ISA option ROMs, and system BIOS, but some systems where smart enough to relocate the hidden RAM. So, your missing .5GB is almost certainly not due to defective RAM, it's just due to The Way Things Are. It's a lot harder for Opteron systems to be smart about this than Xeon systems since all of the remapping magic can happen in the hostbridge on the Xeon, while the Opertons need to have their built-in memory controllers programmed specially for it. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:06:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20ECF16A4CE; Wed, 30 Mar 2005 23:06:49 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85B9343D48; Wed, 30 Mar 2005 23:06:48 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2UNAbwv012942; Wed, 30 Mar 2005 16:10:37 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B308C.7070506@samsco.org> Date: Wed, 30 Mar 2005 16:04:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <424B288D.80303@samsco.org> <20050330224351.GV84137@wantadilla.lemis.com> In-Reply-To: <20050330224351.GV84137@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:06:49 -0000 Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: > >>Greg 'groggy' Lehey wrote: >> >>>I've recently acquired an AMD64 box ... >>> >>>What's unstable? ... The amd64 5.4-PRERELEASE kernel just >>>hangs/freezes. >> >>5.3-RELEASE has a lot of problems with >4GB due to busdma issues. >>Those should no longer be an issue in RELENG_5, including 5.4-PRE. > > > They appear to be. > I don't understand what you mean here. > >>>I realize that this isn't enough to diagnose the problem. The reason >>>for this message now is to ask: >>> >>>3. Where should I look next? >> >>You'll need to dig in and provide some more details, I guess. > > > Yes, my guess too. > > >>I have an HDAMA dual Opteron system that behaves fine now with 8GB >>of RAM, so your problem might lie with particular hardware and/or >>drivers. > > > As I described, it doesn't appear to be the drivers. I don't see how you proved or disproved this. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:09:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DE6B16A4CE; Wed, 30 Mar 2005 23:09:56 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id C526043D49; Wed, 30 Mar 2005 23:09:54 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id E109D85689; Thu, 31 Mar 2005 08:39:51 +0930 (CST) Date: Thu, 31 Mar 2005 08:39:51 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050330230951.GY84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <424B288D.80303@samsco.org> <20050330224351.GV84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ng9nCnWcMXS7n1y7" Content-Disposition: inline In-Reply-To: <424B308C.7070506@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:09:56 -0000 --Ng9nCnWcMXS7n1y7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 16:04:44 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: >> >>> Greg 'groggy' Lehey wrote: >>> >>>> I've recently acquired an AMD64 box ... >>>> >>>> What's unstable? ... The amd64 5.4-PRERELEASE kernel just >>>> hangs/freezes. >>> >>> 5.3-RELEASE has a lot of problems with >4GB due to busdma issues. >>> Those should no longer be an issue in RELENG_5, including 5.4-PRE. >> >> They appear to be. > > I don't understand what you mean here. As I said above (and trimmed for convenience), this problem occurs on 5.4-PRERELEASE as of yesterday morning. The dmesg shows that too. >> As I described, it doesn't appear to be the drivers. > > I don't see how you proved or disproved this. Shall I resend the original message? It seems independent of any particular driver. That's not proof, of course, but I didn't claim it was. Greg -- See complete headers for address and phone numbers. --Ng9nCnWcMXS7n1y7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSzG/IubykFB6QiMRApinAJ9CbvkJLbmghlc0k4vh3l038oVm0wCfReJF im1IhVgfwjN2DvSZjjzPF9A= =3jja -----END PGP SIGNATURE----- --Ng9nCnWcMXS7n1y7-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:15:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 571DD16A4CE; Wed, 30 Mar 2005 23:15:44 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1DF443D1F; Wed, 30 Mar 2005 23:15:42 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 1E83A8564F; Thu, 31 Mar 2005 08:45:41 +0930 (CST) Date: Thu, 31 Mar 2005 08:45:41 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050330231541.GZ84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <424B2FBA.1020102@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vDpQvD79HZx/5O2q" Content-Disposition: inline In-Reply-To: <424B2FBA.1020102@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:15:44 -0000 --vDpQvD79HZx/5O2q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 16:01:14 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: >> >>> On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: >>> >>>> None of these problems occur when I use 4 GB memory. About the only >>>> strangeness, which seems to come from the BIOS, is that it recognizes >>>> only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB >>>> memory. >>> >>> I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB >>> Reg. ECC DIMMs. >> >> OK, this makes sense. It might also explain why the 4 GB >> configuration only recognizes 3.5 GB. > > No, and I'm going to make this an FAQ and post it in a very obvious > place, since 4+ GB is so easy to get and people don't seem to understand > the PC architecture very well. That's not easy to understand when it's barely documented. Thanks for the info: it helps a lot. This may still be a hint, though: that memory hole doesn't show up during a boot with 8 GB RAM. How come? Is the system trying to map RAM over the PCI hole? It looks as if I should get a verbose boot listing with 8 GB. It'll be a couple of hours before I find time to reboot this machine. In the meantime, there's a verbose boot with 4 GB at http://www.lemis.com/grog/Images/20050331/obelix-dmesg. I'm told it shows a number of strange things, including incorrect reporting of on-chip cache sizes. Greg -- See complete headers for address and phone numbers. --vDpQvD79HZx/5O2q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSzMdIubykFB6QiMRAkrBAKCESZB6S1NDAmsQhPl+wU5aHK06wQCfQxOO XSLk29dQDExbNfzD9Nwsxys= =W5rD -----END PGP SIGNATURE----- --vDpQvD79HZx/5O2q-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:17:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01DA016A4CF for ; Wed, 30 Mar 2005 23:17:13 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id D77B843D1F for ; Wed, 30 Mar 2005 23:17:12 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id D62F319764; Wed, 30 Mar 2005 15:17:12 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 30 Mar 2005 15:17:12 -0800 User-Agent: KMail/1.7.2 References: <2fd864e05032900397d7733e8@mail.gmail.com> <20050329211942.P59551@carver.gumbysoft.com> <424AF3CE.4080209@00t.org> In-Reply-To: <424AF3CE.4080209@00t.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503301517.12581.peter@wemm.org> cc: Ulrik Guenther Subject: Re: NVidia i386 Driver on FreeBSD AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:17:13 -0000 On Wednesday 30 March 2005 10:45 am, Ulrik Guenther wrote: > Hello everyone, > > NVidia currently seems not wanting to make binary drivers for > FreeBSD/AMD64. Some time ago somebody at nvnews.net started a thread > in their forum with the plea for drivers for AMD64, the URL is > > http://www.nvnews.net/vbulletin/showthread.php?t=41545 > > Maybe it helps if many people post there and tell the guys at NVidia > that there really is need for these certain drivers. For FreeBSD, we need to resolve some kernel issues first - some missing functionality in particular.. I hate to say "Real Soon Now", but it's going to have to do for the moment because I'm not sure how much I'm allowed to talk about. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:17:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B70E16A4CF; Wed, 30 Mar 2005 23:17:56 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EA2D43D41; Wed, 30 Mar 2005 23:17:55 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 62C028564C; Thu, 31 Mar 2005 08:47:53 +0930 (CST) Date: Thu, 31 Mar 2005 08:47:53 +0930 From: Greg 'groggy' Lehey To: Steve Kargl Message-ID: <20050330231753.GA84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <20050330225715.GA4816@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QxSStYAgvEtE+iQJ" Content-Disposition: inline In-Reply-To: <20050330225715.GA4816@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:17:56 -0000 --QxSStYAgvEtE+iQJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 14:57:15 -0800, Steve Kargl wrote: > On Thu, Mar 31, 2005 at 08:14:45AM +0930, Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: >>> On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: >>>> None of these problems occur when I use 4 GB memory. About the only >>>> strangeness, which seems to come from the BIOS, is that it recognizes >>>> only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB >>>> memory. >>>> >>>> I realize that this isn't enough to diagnose the problem. The reason >>>> for this message now is to ask: >>>> >>>> 3. Where should I look next? >>> >>> Have you run sysutils/memtest86 with the 8 GB? >> >> Heh. Difficult when the system doesn't run. > > That's what happens when 1 of 8 (1 of 4?) DIMM is bad :-) I've booted with the other 2 DIMMs now (I have 4 2 GB DIMMs, all the MB will hold). No problems. See my last reply to Scott: I'm wondering if the system is ignoring the PCI hole. Greg -- See complete headers for address and phone numbers. --QxSStYAgvEtE+iQJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSzOhIubykFB6QiMRAlTsAKCuYHL3smT4m6l1gjoxxJ0YDJLZFgCcCRFd QrXTuMRenj//tyfBI6ivGKU= =WpQ9 -----END PGP SIGNATURE----- --QxSStYAgvEtE+iQJ-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:22:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7370D16A4CE; Wed, 30 Mar 2005 23:22:28 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 411AA43D5F; Wed, 30 Mar 2005 23:22:28 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 4519319764; Wed, 30 Mar 2005 15:22:28 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 30 Mar 2005 15:22:27 -0800 User-Agent: KMail/1.7.2 References: <20050330222439.GU84137@wantadilla.lemis.com> <424B2FBA.1020102@samsco.org> <20050330231541.GZ84137@wantadilla.lemis.com> In-Reply-To: <20050330231541.GZ84137@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503301522.27892.peter@wemm.org> cc: FreeBSD Stable Users Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:22:28 -0000 On Wednesday 30 March 2005 03:15 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 16:01:14 -0700, Scott Long wrote: > > Greg 'groggy' Lehey wrote: > >> On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: > >>> On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: > >>>> None of these problems occur when I use 4 GB memory. About the > >>>> only strangeness, which seems to come from the BIOS, is that it > >>>> recognizes only 3.5 GB. If I put all DIMMS in, it recognizes > >>>> the full 8 GB memory. > >>> > >>> I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 > >>> 2GB Reg. ECC DIMMs. > >> > >> OK, this makes sense. It might also explain why the 4 GB > >> configuration only recognizes 3.5 GB. > > > > No, and I'm going to make this an FAQ and post it in a very obvious > > place, since 4+ GB is so easy to get and people don't seem to > > understand the PC architecture very well. > > That's not easy to understand when it's barely documented. Thanks > for the info: it helps a lot. > > This may still be a hint, though: that memory hole doesn't show up > during a boot with 8 GB RAM. How come? Is the system trying to map > RAM over the PCI hole? Nope, its still there. When you boot -v, you'll see the hole in the "Physical memory chunk(s)" list. However, I suspect that some of the bioses will set the 4GB hole partition in the physical ram lower so that there will be 4.5GB of ram above the 4GB mark. I haven't looked too closely to see for sure. > It looks as if I should get a verbose boot listing with 8 GB. It'll > be a couple of hours before I find time to reboot this machine. In > the meantime, there's a verbose boot with 4 GB at > http://www.lemis.com/grog/Images/20050331/obelix-dmesg. I'm told it > shows a number of strange things, including incorrect reporting of > on-chip cache sizes. Nope, it is correct. You have 1MB of L2 cache. L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative > Greg > -- > See complete headers for address and phone numbers. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:22:47 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F003016A4D3 for ; Wed, 30 Mar 2005 23:22:46 +0000 (GMT) Received: from x8.develooper.com (x8.develooper.com [216.52.237.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 994FE43D1D for ; Wed, 30 Mar 2005 23:22:46 +0000 (GMT) (envelope-from ask@develooper.com) Received: (qmail 11433 invoked from network); 30 Mar 2005 23:22:43 -0000 Received: from m090e36d0.tmodns.net (HELO ?10.178.116.227?) (asktreo@mail.dev@208.54.14.9) by smtp.develooper.com with (RC4-MD5 encrypted) SMTP; 30 Mar 2005 23:22:43 -0000 Mime-Version: 1.0 X-Mailer: SnapperMail 2.2.4.01 by Snapperfish, www.snappermail.com To: "Greg 'groggy' Lehey" , "Steve Kargl" Message-ID: <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> In-Reply-To: <20050330224445.GW84137@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= Date: Wed, 30 Mar 2005 15:22:16 -0800 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit cc: FreeBSD Stable Users cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:22:47 -0000 ...... Original Message ....... On Thu, 31 Mar 2005 08:14:45 +0930 "Greg 'groggy' Lehey" wrote: >> Have you run sysutils/memtest86 with the 8 GB? > >Heh. Difficult when the system doesn't run. There is a bootable ISO version of memtest86 that you could try. - ask -- http://askask.com/ From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:23:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62BDB16A4CE; Wed, 30 Mar 2005 23:23:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE33F43D31; Wed, 30 Mar 2005 23:23:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2UNRGfj013042; Wed, 30 Mar 2005 16:27:16 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B3473.9010108@samsco.org> Date: Wed, 30 Mar 2005 16:21:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <424B2FBA.1020102@samsco.org> <20050330231541.GZ84137@wantadilla.lemis.com> In-Reply-To: <20050330231541.GZ84137@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:23:28 -0000 Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 16:01:14 -0700, Scott Long wrote: > >>Greg 'groggy' Lehey wrote: >> >>>On Wednesday, 30 March 2005 at 14:35:46 -0800, Steve Kargl wrote: >>> >>> >>>>On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: >>>> >>>> >>>>>None of these problems occur when I use 4 GB memory. About the only >>>>>strangeness, which seems to come from the BIOS, is that it recognizes >>>>>only 3.5 GB. If I put all DIMMS in, it recognizes the full 8 GB >>>>>memory. >>>> >>>>I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB >>>>Reg. ECC DIMMs. >>> >>>OK, this makes sense. It might also explain why the 4 GB >>>configuration only recognizes 3.5 GB. >> >>No, and I'm going to make this an FAQ and post it in a very obvious >>place, since 4+ GB is so easy to get and people don't seem to understand >>the PC architecture very well. > > > That's not easy to understand when it's barely documented. Thanks for > the info: it helps a lot. > > This may still be a hint, though: that memory hole doesn't show up > during a boot with 8 GB RAM. How come? Is the system trying to map > RAM over the PCI hole? > > It looks as if I should get a verbose boot listing with 8 GB. It'll > be a couple of hours before I find time to reboot this machine. In > the meantime, there's a verbose boot with 4 GB at > http://www.lemis.com/grog/Images/20050331/obelix-dmesg. I'm told it > shows a number of strange things, including incorrect reporting of > on-chip cache sizes. > The SMAP will show the hole. It's well documented in most PC archtitecure books. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:25:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAD5716A4CF; Wed, 30 Mar 2005 23:25:40 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C28543D64; Wed, 30 Mar 2005 23:25:38 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2UNTQrd013064; Wed, 30 Mar 2005 16:29:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B34F6.6020705@samsco.org> Date: Wed, 30 Mar 2005 16:23:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <424B288D.80303@samsco.org> <20050330224351.GV84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> <20050330230951.GY84137@wantadilla.lemis.com> In-Reply-To: <20050330230951.GY84137@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:25:40 -0000 Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 16:04:44 -0700, Scott Long wrote: > >>Greg 'groggy' Lehey wrote: >> >>>On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: >>> >>> >>>>Greg 'groggy' Lehey wrote: >>>> >>>> >>>>>I've recently acquired an AMD64 box ... >>>>> >>>>>What's unstable? ... The amd64 5.4-PRERELEASE kernel just >>>>>hangs/freezes. >>>> >>>>5.3-RELEASE has a lot of problems with >4GB due to busdma issues. >>>>Those should no longer be an issue in RELENG_5, including 5.4-PRE. >>> >>>They appear to be. >> >>I don't understand what you mean here. > > > As I said above (and trimmed for convenience), this problem occurs on > 5.4-PRERELEASE as of yesterday morning. The dmesg shows that too. > And you're certain that it's due to the same busdma issues that I was describing? I must have missed the evidence that you use to support this. > >>>As I described, it doesn't appear to be the drivers. >> >>I don't see how you proved or disproved this. > > > Shall I resend the original message? It seems independent of any > particular driver. That's not proof, of course, but I didn't claim it > was. Again, I must have missed the part where you investigated the drivers that apply to your particular system. I highly doubt that they apply to every 8GB Opteron system available on the market. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:25:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 347E316A4CF; Wed, 30 Mar 2005 23:25:41 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 541D643D60; Wed, 30 Mar 2005 23:25:38 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 2843B19764; Wed, 30 Mar 2005 15:25:38 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 30 Mar 2005 15:25:37 -0800 User-Agent: KMail/1.7.2 References: <20050330222439.GU84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> <20050330230951.GY84137@wantadilla.lemis.com> In-Reply-To: <20050330230951.GY84137@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503301525.37798.peter@wemm.org> cc: FreeBSD Stable Users Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:25:41 -0000 On Wednesday 30 March 2005 03:09 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 16:04:44 -0700, Scott Long wrote: > > Greg 'groggy' Lehey wrote: > >> On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: > >>> Greg 'groggy' Lehey wrote: > >>>> I've recently acquired an AMD64 box ... > >>>> > >>>> What's unstable? ... The amd64 5.4-PRERELEASE kernel just > >>>> hangs/freezes. > >>> > >>> 5.3-RELEASE has a lot of problems with >4GB due to busdma issues. > >>> Those should no longer be an issue in RELENG_5, including > >>> 5.4-PRE. > >> > >> They appear to be. > > > > I don't understand what you mean here. > > As I said above (and trimmed for convenience), this problem occurs on > 5.4-PRERELEASE as of yesterday morning. The dmesg shows that too. > > >> As I described, it doesn't appear to be the drivers. > > > > I don't see how you proved or disproved this. > > Shall I resend the original message? It seems independent of any > particular driver. That's not proof, of course, but I didn't claim > it was. Greg: The busdma problems from 5.3-RELEASE are fixed. That doesn't mean that there are no *other* problems. Scott is saying "the old busdma bug shouldn't be affecting 5.4-PRE", and he's correct. Most likely, something else is happening, eg: you're running out of KVM or something silly like that. I know we're right on the brink at 8GB. The layout of the devices may be just enough to tip it over the edge. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:27:29 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F2BA16A4CE; Wed, 30 Mar 2005 23:27:29 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 030E443D45; Wed, 30 Mar 2005 23:27:29 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id E65C1197A9; Wed, 30 Mar 2005 15:27:28 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 30 Mar 2005 15:27:28 -0800 User-Agent: KMail/1.7.2 References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> In-Reply-To: <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200503301527.28612.peter@wemm.org> cc: Ask =?iso-8859-1?q?Bj=F8rn_Hansen?= cc: FreeBSD Stable Users Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:27:29 -0000 On Wednesday 30 March 2005 03:22 pm, Ask Bj=F8rn Hansen wrote: > ...... Original Message ....... > On Thu, 31 Mar 2005 08:14:45 +0930 "Greg 'groggy' Lehey" > > > wrote: > >> Have you run sysutils/memtest86 with the 8 GB? > > > >Heh. Difficult when the system doesn't run. > > There is a bootable ISO version of memtest86 that you could try. Thats what the port does.. It produces a bootable floppy or ISO. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:38:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A09116A4CE; Wed, 30 Mar 2005 23:38:06 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A732E43D1D; Wed, 30 Mar 2005 23:38:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j2UNbec3024224; Wed, 30 Mar 2005 16:37:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 30 Mar 2005 16:37:47 -0700 (MST) Message-Id: <20050330.163747.105583958.imp@bsdimp.com> To: grog@freebsd.org From: "M. Warner Losh" In-Reply-To: <20050330231753.GA84137@wantadilla.lemis.com> References: <20050330224445.GW84137@wantadilla.lemis.com> <20050330225715.GA4816@troutmask.apl.washington.edu> <20050330231753.GA84137@wantadilla.lemis.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:38:06 -0000 In message: <20050330231753.GA84137@wantadilla.lemis.com> "Greg 'groggy' Lehey" writes: : I've booted with the other 2 DIMMs now (I have 4 2 GB DIMMs, all the : MB will hold). No problems. See my last reply to Scott: I'm : wondering if the system is ignoring the PCI hole. Unlikely. If it was, you'd not have enough of a system to complain about. Warner From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:38:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B608F16A4CE; Wed, 30 Mar 2005 23:38:28 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 014EE43D1D; Wed, 30 Mar 2005 23:38:27 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 89E6C85669; Thu, 31 Mar 2005 09:08:23 +0930 (CST) Date: Thu, 31 Mar 2005 09:08:23 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050330233823.GA6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <424B288D.80303@samsco.org> <20050330224351.GV84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> <20050330230951.GY84137@wantadilla.lemis.com> <424B34F6.6020705@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <424B34F6.6020705@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:38:28 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Format recovered--see http://www.lemis.com/email/email-format.html] [gratuitous empty lines removed] On Wednesday, 30 March 2005 at 16:23:34 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 16:04:44 -0700, Scott Long wrote: >>> Greg 'groggy' Lehey wrote: >>>> On Wednesday, 30 March 2005 at 15:30:37 -0700, Scott Long wrote: >>>>> Greg 'groggy' Lehey wrote: >>>>>> I've recently acquired an AMD64 box ... >>>>>> >>>>>> What's unstable? ... The amd64 5.4-PRERELEASE kernel just >>>>>> hangs/freezes. >>>>> >>>>> 5.3-RELEASE has a lot of problems with >4GB due to busdma issues. >>>>> Those should no longer be an issue in RELENG_5, including 5.4-PRE. >>>> >>>> They appear to be. >>> >>> I don't understand what you mean here. >> >> As I said above (and trimmed for convenience), this problem occurs on >> 5.4-PRERELEASE as of yesterday morning. The dmesg shows that too. > > And you're certain that it's due to the same busdma issues that I > was describing? No. > I must have missed the evidence that you use to support this. I didn't give any. It appears that I misunderstood what you were saying. >>>> As I described, it doesn't appear to be the drivers. >>> >>> I don't see how you proved or disproved this. >> >> Shall I resend the original message? It seems independent of any >> particular driver. That's not proof, of course, but I didn't claim it >> was. > > Again, I must have missed the part where you investigated the drivers > that apply to your particular system. The description is still there. > I highly doubt that they apply to every 8GB Opteron system available > on the market. I never suggested that they did. There's every reason to believe that it's something to do with this particular motherboard, but that doesn't mean that FreeBSD is blameless. Greg -- When replying to this message, please take care not to mutilate the original text. =20 For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers. --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSzhvIubykFB6QiMRAlwtAJ9WO4/fOj8MwW/EIDoSA6oA3oqnMgCfeqja Re0zQiZ9Ww6bvFXjCLSuyWg= =dpRK -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:39:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E65116A4CE; Wed, 30 Mar 2005 23:39:50 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1711043D3F; Wed, 30 Mar 2005 23:39:49 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 0C63885671; Thu, 31 Mar 2005 09:09:47 +0930 (CST) Date: Thu, 31 Mar 2005 09:09:47 +0930 From: Greg 'groggy' Lehey To: Peter Wemm Message-ID: <20050330233946.GB6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> <20050330230951.GY84137@wantadilla.lemis.com> <200503301525.37798.peter@wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline In-Reply-To: <200503301525.37798.peter@wemm.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Stable Users cc: freebsd-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:39:50 -0000 --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 30 March 2005 at 15:25:37 -0800, Peter Wemm wrote: > On Wednesday 30 March 2005 03:09 pm, Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 16:04:44 -0700, Scott Long wrote: >>> Greg 'groggy' Lehey wrote: >>>> As I described, it doesn't appear to be the drivers. >>> >>> I don't see how you proved or disproved this. >> >> Shall I resend the original message? It seems independent of any >> particular driver. That's not proof, of course, but I didn't claim >> it was. > > Greg: The busdma problems from 5.3-RELEASE are fixed. That doesn't > mean that there are no *other* problems. Scott is saying "the old > busdma bug shouldn't be affecting 5.4-PRE", and he's correct. Yes, now I understand. > Most likely, something else is happening, eg: you're running out of KVM > or something silly like that. I know we're right on the brink at 8GB. > The layout of the devices may be just enough to tip it over the edge. Yes, this seems reasonable. Where should I look next? I'm currently rebuilding world and will attempt a verbose boot via serial console when it's done. Anything else I should try? Greg -- See complete headers for address and phone numbers. --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCSzjCIubykFB6QiMRAtlJAJ43Etwpf1ha/R0v82fiwc8Xc3hvFgCfQOsb xoGRrstX3t3lfBLP8vD7Qz0= =9O6g -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC-- From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 30 23:46:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F9CC16A4CE; Wed, 30 Mar 2005 23:46:04 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DB0643D31; Wed, 30 Mar 2005 23:46:04 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j2UNk3P20261; Wed, 30 Mar 2005 15:46:03 -0800 (PST) Date: Wed, 30 Mar 2005 15:46:03 -0800 From: Mike Hunter To: Peter Wemm Message-ID: <20050330234603.GA18631@ack.Berkeley.EDU> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> <200503301527.28612.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200503301527.28612.peter@wemm.org> User-Agent: Mutt/1.5.6i cc: Ask =?unknown-8bit?Q?Bj=F8rn?= Hansen cc: FreeBSD Stable Users cc: freebsd-amd64@freebsd.org Subject: [OT] memtest86 (Was: Problems with AMD64 and 8 GB RAM?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 23:46:04 -0000 On Mar 30, "Peter Wemm" wrote: > On Wednesday 30 March 2005 03:22 pm, Ask Bjørn Hansen wrote: > > ...... Original Message ....... > > On Thu, 31 Mar 2005 08:14:45 +0930 "Greg 'groggy' Lehey" > > > > > > wrote: > > >> Have you run sysutils/memtest86 with the 8 GB? > > > > > >Heh. Difficult when the system doesn't run. > > > > There is a bootable ISO version of memtest86 that you could try. > > Thats what the port does.. It produces a bootable floppy or ISO. This reminds me, I noticed that gentoo includes a memtest86 "kernel" in their install ISO. Would this be a hard feature to include in FreeBSD? Mike From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 01:02:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AB8F16A4CE; Thu, 31 Mar 2005 01:02:43 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0F7143D1D; Thu, 31 Mar 2005 01:02:38 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j2V12YwQ029366; Thu, 31 Mar 2005 10:32:34 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 31 Mar 2005 10:32:33 +0930 User-Agent: KMail/1.8 References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> In-Reply-To: <20050330224445.GW84137@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1712303.1chSQSiMmU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200503311032.33718.doconnor@gsoft.com.au> X-Spam-Score: -1.7 () IN_REP_TO,PGP_SIGNATURE_2,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 01:02:43 -0000 --nextPart1712303.1chSQSiMmU Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: > > Have you run sysutils/memtest86 with the 8 GB? > > Heh. Difficult when the system doesn't run. You could try http://www.memtest86.com although that doesn't do >4Gb :( =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1712303.1chSQSiMmU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBCS0wp5ZPcIHs/zowRAjSJAJ9eHLHoMrfSk/YA8afYC4mOG0hmQACfXDm2 GrvuNRt5zCSRFO0s7YeSxdQ= =7Oke -----END PGP SIGNATURE----- --nextPart1712303.1chSQSiMmU-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 01:10:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CC4F16A4CE; Thu, 31 Mar 2005 01:10:11 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3647343D31; Thu, 31 Mar 2005 01:10:11 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j2V1AAaG006205; Wed, 30 Mar 2005 17:10:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j2V1AA4W006204; Wed, 30 Mar 2005 17:10:10 -0800 (PST) (envelope-from sgk) Date: Wed, 30 Mar 2005 17:10:10 -0800 From: Steve Kargl To: "Daniel O'Connor" Message-ID: <20050331011010.GA6151@troutmask.apl.washington.edu> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503311032.33718.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 01:10:11 -0000 On Thu, Mar 31, 2005 at 10:32:33AM +0930, Daniel O'Connor wrote: > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: > > > Have you run sysutils/memtest86 with the 8 GB? > > > > Heh. Difficult when the system doesn't run. > > You could try http://www.memtest86.com although that doesn't do >4Gb :( > http://www.memtest.org/ -- Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 01:19:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A70F616A4CE; Thu, 31 Mar 2005 01:19:45 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC7A043D1D; Thu, 31 Mar 2005 01:19:44 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j2V1Jf4h029892; Thu, 31 Mar 2005 10:49:41 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Steve Kargl Date: Thu, 31 Mar 2005 10:49:38 +0930 User-Agent: KMail/1.8 References: <20050330222439.GU84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331011010.GA6151@troutmask.apl.washington.edu> In-Reply-To: <20050331011010.GA6151@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3331214.TbhGTi0eAW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200503311049.38443.doconnor@gsoft.com.au> X-Spam-Score: -2.5 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 01:19:45 -0000 --nextPart3331214.TbhGTi0eAW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 31 Mar 2005 10:40, Steve Kargl wrote: > On Thu, Mar 31, 2005 at 10:32:33AM +0930, Daniel O'Connor wrote: > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: > > > > Have you run sysutils/memtest86 with the 8 GB? > > > > > > Heh. Difficult when the system doesn't run. > > > > You could try http://www.memtest86.com although that doesn't do >4Gb :( > > http://www.memtest.org/ Ahh well there you go :) Thanks! =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3331214.TbhGTi0eAW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBCS1Aq5ZPcIHs/zowRAj1yAKCGqOhHbpI1ZI8lLfKwP7bBbYC/OACfU2e9 g8Hf49h/sUqgtW5ZeAyYp9c= =hRxa -----END PGP SIGNATURE----- --nextPart3331214.TbhGTi0eAW-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 01:22:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE12F16A4CE for ; Thu, 31 Mar 2005 01:22:54 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id C85C843D60 for ; Thu, 31 Mar 2005 01:22:51 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 3033AB80C for ; Wed, 30 Mar 2005 20:22:51 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <97964ce32490a368d64fa9b3500a8ba6@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 30 Mar 2005 20:22:52 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 01:22:55 -0000 On Mar 29, 2005, at 7:39 PM, Sten Spans wrote: > There was an amr panic related to the management ioctls > which was fixed and backported to RELENG_5. You should have > this fix. amr controllers a supported quite well on freebsd > thanks to Scott's great work. > Yes, that was part of the reason I cvsup'd again last week... to ensure I had the latest fixes to the amr driver. > The only way to get closer to solving these problems > is to dig and try to narrow it down: > > - Have you tried running with debugging ? any more than having the kernel debugger installed? When the box locked up I couldn't even drop into the kernel debugger from the serial console. neither the BREAK signal nor the alt key sequence invoked it. > > - Have you tried using other network cards ? > ( yeah that sucks I know ) Nope. Machine is brand spanking new. Was in service a whole of 5 days before it locked up. The twin of this machine also has issues with the BIOS reporting "memory size changed" while the machine is running... so I'm a bit concerned that there is some generic problem with the K8SR and a megaraid controller. But that one never had any complaints about the ethernet, and the memory size error persisted across two motherboards. I have yet to try the other ethernet port on this box as well. > > - Are you absolutely sure that all the disks are working ? > ( there have been reports of amr cards acting strange with > silently failing disks ) The megaraid bios showed all disks as active. How would one tell if you had a silently failing disk? :-( > - Have you got the ufs fixes recently backported to releng_5 ? If it was prior to March 22, then yes I have them. Where in cvsweb might I look to test? > These are the first I can think of. RELENG_5 seems to be > a bit of a moving target with some quite critical fixes > going in ( which is good offcourse :). Yes, it is good.... until you can't figure out if it is your hardware or software flaking out on ya... Thanks so much for responding. For price-no-object, which vendor would you choose for an AMD system today? Same question if price is somewhat of a concern. Thanks. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 01:54:36 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9E5516A4CE; Thu, 31 Mar 2005 01:54:36 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F3B43D41; Thu, 31 Mar 2005 01:54:33 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 5320B85689; Thu, 31 Mar 2005 11:24:29 +0930 (CST) Date: Thu, 31 Mar 2005 11:24:29 +0930 From: Greg 'groggy' Lehey To: Daniel O'Connor Message-ID: <20050331015429.GH6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X0cz4bGbQuRbxrVl" Content-Disposition: inline In-Reply-To: <200503311032.33718.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 01:54:37 -0000 --X0cz4bGbQuRbxrVl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 31 March 2005 at 10:32:33 +0930, Daniel O'Connor wrote: > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: >>> Have you run sysutils/memtest86 with the 8 GB? >> >> Heh. Difficult when the system doesn't run. > > You could try http://www.memtest86.com although that doesn't do >4Gb :( I'm pretty sure it's not the memory. I've tried each pair individually, and it's only when they're both in there together that it's a problem. And yes, I've tried them in each pair of slots. I now have dmesg output for verbose boots with both 4 GB and 8 GB memory. The complete dmesg output is at http://www.lemis.com/grog/Images/20050331/dmesg.4GB and http://www.lemis.com/grog/Images/20050331/dmesg.8GB. The diffs are at http://www.lemis.com/grog/Images/20050331/dmesg.diff. Here's a truncated summary: > --- dmesg.4GB Thu Mar 31 10:47:16 2005 > +++ dmesg.8GB Thu Mar 31 10:52:32 2005 > @@ -64,6 +10,7 @@ > SMAP type=01 base=0000000000100000 len=00000000dfde0000 > SMAP type=03 base=00000000dfee3000 len=000000000000d000 > SMAP type=04 base=00000000dfee0000 len=0000000000003000 > +SMAP type=01 base=0000000100000000 len=0000000100000000 > Copyright (c) 1992-2005 The FreeBSD Project. > @@ -75,7 +22,7 @@ > Calibrating clock(s) ... i8254 clock: 1193283 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > -Calibrating TSC clock ... TSC clock: 1603647337 Hz > +Calibrating TSC clock ... TSC clock: 1603647241 Hz > CPU: AMD Opteron(tm) Processor 242 (1603.65-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 > Features=0x78bfbff > @@ -90,11 +37,12 @@ > L2 4KB data TLB: 512 entries, 4-way associative > L2 4KB instruction TLB: 512 entries, 4-way associative > L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative > -real memory = 3756916736 (3582 MB) > +real memory = 8589934592 (8192 MB) This is interesting in that it has gained 4.5 GB. > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) > -0x0000000000a05000 - 0x00000000d95b7fff, 3636146176 bytes (887731 pages) > -avail memory = 3623817216 (3455 MB) > +0x0000000000a09000 - 0x00000000dfedffff, 3746394112 bytes (914647 pages) > +0x0000000100000000 - 0x00000001f0fcffff, 4043112448 bytes (987088 pages) > +avail memory = 7777177600 (7416 MB) > ACPI APIC Table: > APIC ID: physical 0, logical 0:0 > APIC ID: physical 1, logical 0:1 > @@ -138,41 +86,12 @@ > ioapic0: intpin 9 trigger: level > ioapic0: intpin 9 polarity: low > lapic0: Routing NMI -> LINT1 > -A IRQ 3 (edge, high) > -ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) > -ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) > -ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) > -ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) > -ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) > -ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) > -ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) > -ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) > -ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) > -ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) > -ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) > -ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) > -ioapic0: intpin 16 -> PCI IRQ 16 (level, low) > -ioapic0: intpin 17 -> PCI IRQ 17 (level, low) > -ioapic0: intpin 18 -> PCI IRQ 18 (level, low) > -ioapic0: intpin 19 -> PCI IRQ 19 (level, low) > -ioapic0: intpin 20 -> PCI IRQ 20 (level, low) > -ioapic0: intpin 21 -> PCI IRQ 21 (level, low) > -ioapic0: intpin 22 -> PCI IRQ 22 (level, low) > -ioapic0: intpin 23 -> PCI IRQ 23 (level, low) > -MADT: Interrupt override: source 0, irq 2 > -ioapic0: Routing IRQ 0 -> intpin 2 > -ioapic0: intpin 2 trigger: edge > -ioapic0: intpin 2 polarity: high > -MADT: Interrupt override: source 9, irq 9 > -ioapic0: intpin 9 trigger: level > -ioapic0: intpin 9 polarity: low > -lapic0: Routing NMI -> LINT1 This stuff is puzzling. I suppose it could be related. Does anybody have any ideas? > lapic0: LINT1 trigger: edge > lapic0: LINT1 polarity: high > lapic1: Routing NMI -> LINT1 > lapic1: LINT1 trigger: edge > lapic1: LINT1 polarity: high > -ioapic0 irqs 0-23 on motherboard > +ioapic0 irqs 0-23 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff The last lines in the 8 GB dmesg are: > bge0: mem 0xfa000000-0xfa00ffff irq 16 at device 11.0 on pci0 > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfa000000 They're identical in each probe. Greg -- See complete headers for address and phone numbers. --X0cz4bGbQuRbxrVl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS1hVIubykFB6QiMRArcQAJ9GqhMKnFIjw1m6TcPkLFDNNQh6iACaAnUq KDp8Cg6RH7e8+/A0ShUTuv0= =5UnY -----END PGP SIGNATURE----- --X0cz4bGbQuRbxrVl-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 02:00:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B856B16A4CE; Thu, 31 Mar 2005 02:00:44 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC49743D49; Thu, 31 Mar 2005 02:00:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j2V20efv030465; Thu, 31 Mar 2005 11:30:40 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Greg 'groggy' Lehey" Date: Thu, 31 Mar 2005 11:30:31 +0930 User-Agent: KMail/1.8 References: <20050330222439.GU84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> In-Reply-To: <20050331015429.GH6252@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1215408.9mMY9VAgPs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200503311130.39539.doconnor@gsoft.com.au> X-Spam-Score: -2.5 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 02:00:44 -0000 --nextPart1215408.9mMY9VAgPs Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 31 Mar 2005 11:24, Greg 'groggy' Lehey wrote: > I'm pretty sure it's not the memory. I've tried each pair > individually, and it's only when they're both in there together that > it's a problem. And yes, I've tried them in each pair of slots. Could be a marginal timing issue.. You could try winding out the RAM timing= =20 slightly. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1215408.9mMY9VAgPs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBCS1nH5ZPcIHs/zowRAiJtAJwK6VJTAl1F5i50DsEEq8oGLglQjACeJ7p7 rGvg9LUEcBeYvZ0lkArkbGI= =3Fen -----END PGP SIGNATURE----- --nextPart1215408.9mMY9VAgPs-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 02:53:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5771116A4CE; Thu, 31 Mar 2005 02:53:03 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00AD043D1D; Thu, 31 Mar 2005 02:53:03 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p3E9E28E6.dip.t-dialin.net [62.158.40.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id E52D432C85; Thu, 31 Mar 2005 04:52:58 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j2V3sJK3011447; Thu, 31 Mar 2005 05:54:19 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j2V3sIYj011446; Thu, 31 Mar 2005 05:54:18 +0200 (CEST) (envelope-from mkb) Date: Thu, 31 Mar 2005 05:54:17 +0200 From: Matthias Buelow To: "Greg 'groggy' Lehey" Message-ID: <20050331035417.GD10394@drjekyll.mkbuelow.net> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050331015429.GH6252@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i cc: Daniel O'Connor cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 02:53:03 -0000 Greg 'groggy' Lehey wrote: >I'm pretty sure it's not the memory. I've tried each pair >individually, and it's only when they're both in there together that >it's a problem. And yes, I've tried them in each pair of slots. I'm sure you have checked this aswell but just for completeness, they aren't different pairs? Like one pair is single-sided and the other double-sided (had some nasty and obscure problems with such a combination myself)? mkb. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 03:26:47 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E41E616A4CE; Thu, 31 Mar 2005 03:26:47 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4536643D2F; Thu, 31 Mar 2005 03:26:46 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 21FA88564C; Thu, 31 Mar 2005 12:56:43 +0930 (CST) Date: Thu, 31 Mar 2005 12:56:43 +0930 From: Greg 'groggy' Lehey To: Matthias Buelow Message-ID: <20050331032643.GJ6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <20050331035417.GD10394@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hl1kWnBARzJiTscN" Content-Disposition: inline In-Reply-To: <20050331035417.GD10394@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Daniel O'Connor cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 03:26:48 -0000 --hl1kWnBARzJiTscN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 31 March 2005 at 5:54:17 +0200, Matthias Buelow wrote: > Greg 'groggy' Lehey wrote: > >> I'm pretty sure it's not the memory. I've tried each pair >> individually, and it's only when they're both in there together that >> it's a problem. And yes, I've tried them in each pair of slots. > > I'm sure you have checked this aswell but just for completeness, > they aren't different pairs? Like one pair is single-sided and the > other double-sided (had some nasty and obscure problems with such > a combination myself)? No, they're all the same. Greg -- See complete headers for address and phone numbers. --hl1kWnBARzJiTscN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS23zIubykFB6QiMRAnpaAJ9rCIB6oBi3cZ1k+N9d/2NFuT2OiQCgnO2/ anH0kFG84jwGIMfMROtaAm4= =ewsF -----END PGP SIGNATURE----- --hl1kWnBARzJiTscN-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 04:01:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5C0816A4CF for ; Thu, 31 Mar 2005 04:01:12 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F2AF43D54 for ; Thu, 31 Mar 2005 04:01:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9819 invoked from network); 31 Mar 2005 04:01:12 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 04:01:11 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2V414e2021188; Wed, 30 Mar 2005 23:01:05 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <20050331015429.GH6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Wed, 30 Mar 2005 23:01:03 -0500 To: "Greg 'groggy' Lehey" X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Daniel O'Connor cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 04:01:13 -0000 On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >> lapic0: LINT1 trigger: edge >> lapic0: LINT1 polarity: high >> lapic1: Routing NMI -> LINT1 >> lapic1: LINT1 trigger: edge >> lapic1: LINT1 polarity: high >> -ioapic0 irqs 0-23 on motherboard >> +ioapic0 irqs 0-23 on motherboard >> cpu0 BSP: >> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff This shows that in the - case the APIC is broken somehow (0.0 isn't a valid I/O APIC version). It would seem that the system has mapped RAM over top of the I/O APIC perhaps? It would be interesting to see the contents of your MADT to see if it's trying to use a 64-bit PA for your APIC. The local APIC portion seems ok though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 04:08:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2455C16A4CE; Thu, 31 Mar 2005 04:08:16 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661D343D45; Thu, 31 Mar 2005 04:08:14 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id DBFAE85686; Thu, 31 Mar 2005 13:38:11 +0930 (CST) Date: Thu, 31 Mar 2005 13:38:11 +0930 From: Greg 'groggy' Lehey To: John Baldwin Message-ID: <20050331040811.GL6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9ToWwKEyhugL+MAz" Content-Disposition: inline In-Reply-To: <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Daniel O'Connor cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 04:08:16 -0000 --9ToWwKEyhugL+MAz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: > > On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>> lapic0: LINT1 trigger: edge >>> lapic0: LINT1 polarity: high >>> lapic1: Routing NMI -> LINT1 >>> lapic1: LINT1 trigger: edge >>> lapic1: LINT1 polarity: high >>> -ioapic0 irqs 0-23 on motherboard >>> +ioapic0 irqs 0-23 on motherboard >>> cpu0 BSP: >>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > > This shows that in the - case the APIC is broken somehow (0.0 isn't a > valid I/O APIC version).=20 You mean the + case, I suppose. Yes, that's what I suspected. > It would seem that the system has mapped RAM over top of the I/O > APIC perhaps? That's what I suspected too, but imp doesn't think so. > It would be interesting to see the contents of your MADT to see if > it's trying to use a 64-bit PA for your APIC. Any suggestions about how to do so? Greg -- See complete headers for address and phone numbers. --9ToWwKEyhugL+MAz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS3erIubykFB6QiMRArPcAJ9dFcCebTmKRN1LFO0WUQQ7aBfLTgCeNWjj /BNhl4GFpP2ltV92pYXTLNk= =2eZR -----END PGP SIGNATURE----- --9ToWwKEyhugL+MAz-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 04:30:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 279F816A4CE; Thu, 31 Mar 2005 04:30:44 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C2243D46; Thu, 31 Mar 2005 04:30:43 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2V4YRjo014442; Wed, 30 Mar 2005 21:34:27 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B7C74.4060203@samsco.org> Date: Wed, 30 Mar 2005 21:28:36 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> In-Reply-To: <20050331040811.GL6252@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: Daniel O'Connor cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 04:30:44 -0000 Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: > >>On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >> >>>>lapic0: LINT1 trigger: edge >>>>lapic0: LINT1 polarity: high >>>>lapic1: Routing NMI -> LINT1 >>>>lapic1: LINT1 trigger: edge >>>>lapic1: LINT1 polarity: high >>>>-ioapic0 irqs 0-23 on motherboard >>>>+ioapic0 irqs 0-23 on motherboard >>>>cpu0 BSP: >>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff >> >>This shows that in the - case the APIC is broken somehow (0.0 isn't a >>valid I/O APIC version). > > > You mean the + case, I suppose. Yes, that's what I suspected. > > >>It would seem that the system has mapped RAM over top of the I/O >>APIC perhaps? > > > That's what I suspected too, but imp doesn't think so. > I'd be more inclined to believe that there is an erroneous mapping by the OS, not that things are fundamentally broken in hardware. Your SMAP table shows everything correctly. It's becoming hard to break through your pre-concieved notions here and explain how things actually work. > >>It would be interesting to see the contents of your MADT to see if >>it's trying to use a 64-bit PA for your APIC. > > > Any suggestions about how to do so? > man acpidump From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:15:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 273CB16A4CE; Thu, 31 Mar 2005 05:15:03 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5036D43D5F; Thu, 31 Mar 2005 05:15:01 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 35EA185686; Thu, 31 Mar 2005 14:44:58 +0930 (CST) Date: Thu, 31 Mar 2005 14:44:58 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050331051458.GM6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1R6ZDISWaA1muLP0" Content-Disposition: inline In-Reply-To: <424B7C74.4060203@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Daniel O'Connor cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 05:15:03 -0000 --1R6ZDISWaA1muLP0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [gratuitous empty lines removed] On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: > Greg 'groggy' Lehey wrote: >> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >> >>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>> >>>>> lapic0: LINT1 trigger: edge >>>>> lapic0: LINT1 polarity: high >>>>> lapic1: Routing NMI -> LINT1 >>>>> lapic1: LINT1 trigger: edge >>>>> lapic1: LINT1 polarity: high >>>>> -ioapic0 irqs 0-23 on motherboard >>>>> +ioapic0 irqs 0-23 on motherboard >>>>> cpu0 BSP: >>>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff >>> >>> This shows that in the - case the APIC is broken somehow (0.0 isn't a >>> valid I/O APIC version). >> >> You mean the + case, I suppose. Yes, that's what I suspected. >> >>> It would seem that the system has mapped RAM over top of the I/O >>> APIC perhaps? >> >> That's what I suspected too, but imp doesn't think so. > > I'd be more inclined to believe that there is an erroneous mapping > by the OS, not that things are fundamentally broken in hardware. Agreed. This has been my favourite hypothesis all along. But isn't that what jhb is saying? > Your SMAP table shows everything correctly. It's becoming hard to > break through your pre-concieved notions here and explain how things > actually work. No, there's nothing to break through. I think you're just having problems 1. expressing yourself, and 2. understanding what I'm saying. I have no preconceived notions. All I can see here is an antagonistic attitude on your part. What's the problem? You'll recall from my first message that I asked for suggestions about how to approach the issue. jhb provided some; you haven't so far. From what you've written, it's unclear whether you disagree with jhb or not. If you do, why? If you don't, what's your point here? >>> It would be interesting to see the contents of your MADT to see if >>> it's trying to use a 64-bit PA for your APIC. >> >> Any suggestions about how to do so? > > man acpidump How do you run that on a system that won't boot? Greg -- See complete headers for address and phone numbers. --1R6ZDISWaA1muLP0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS4dSIubykFB6QiMRAvWEAJ0dXk9mzjVeGL8811rkivhYRc6VZwCdGtVB xyalBFLEPelz1kM7a6YmIt4= =vfu0 -----END PGP SIGNATURE----- --1R6ZDISWaA1muLP0-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:29:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B4CA16A4D2 for ; Thu, 31 Mar 2005 05:29:00 +0000 (GMT) Received: from smtp812.mail.sc5.yahoo.com (smtp812.mail.sc5.yahoo.com [66.163.170.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 07AFE43D2D for ; Thu, 31 Mar 2005 05:28:59 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noacks@swbell.net@70.240.208.130 with login) by smtp812.mail.sc5.yahoo.com with SMTP; 31 Mar 2005 05:28:58 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 4B16560F7; Wed, 30 Mar 2005 23:28:57 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08538-14; Wed, 30 Mar 2005 23:28:55 -0600 (CST) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id F156960D7; Wed, 30 Mar 2005 23:28:54 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.3/8.13.3) with ESMTP id j2V5Sq0w055701; Wed, 30 Mar 2005 23:28:52 -0600 (CST) (envelope-from noackjr@alumni.rice.edu) Message-ID: <424B8A94.5070300@alumni.rice.edu> Date: Wed, 30 Mar 2005 23:28:52 -0600 From: Jon Noack User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> In-Reply-To: <20050331051458.GM6252@wantadilla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org cc: freebsd-stable@FreeBSD.org cc: John Baldwin cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 05:29:00 -0000 On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: >>Greg 'groggy' Lehey wrote: >>>On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >>>>On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>>>>>lapic0: LINT1 trigger: edge >>>>>>lapic0: LINT1 polarity: high >>>>>>lapic1: Routing NMI -> LINT1 >>>>>>lapic1: LINT1 trigger: edge >>>>>>lapic1: LINT1 polarity: high >>>>>>-ioapic0 irqs 0-23 on motherboard >>>>>>+ioapic0 irqs 0-23 on motherboard >>>>>>cpu0 BSP: >>>>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >>>>>>lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff >>>> >>>>This shows that in the - case the APIC is broken somehow (0.0 isn't a >>>>valid I/O APIC version). >>> >>>You mean the + case, I suppose. Yes, that's what I suspected. >>> >>> >>>>It would seem that the system has mapped RAM over top of the I/O >>>>APIC perhaps? >>> >>>That's what I suspected too, but imp doesn't think so. >> >>I'd be more inclined to believe that there is an erroneous mapping >>by the OS, not that things are fundamentally broken in hardware. > > Agreed. This has been my favourite hypothesis all along. But isn't > that what jhb is saying? > >>Your SMAP table shows everything correctly. It's becoming hard to >>break through your pre-concieved notions here and explain how things >>actually work. > > No, there's nothing to break through. I think you're just having > problems > > 1. expressing yourself, and > 2. understanding what I'm saying. > > I have no preconceived notions. All I can see here is an antagonistic > attitude on your part. What's the problem? You'll recall from my > first message that I asked for suggestions about how to approach the > issue. jhb provided some; you haven't so far. From what you've > written, it's unclear whether you disagree with jhb or not. If you > do, why? If you don't, what's your point here? > >>>>It would be interesting to see the contents of your MADT to see if >>>>it's trying to use a 64-bit PA for your APIC. >>> >>>Any suggestions about how to do so? >> >>man acpidump > > How do you run that on a system that won't boot? You said the system worked with 4 GB (albeit detecting only 3.5 GB). My perception of this whole ACPI thing is that it is fixed in your BIOS (although it can be overridden by the OS). As such, the amount of RAM you have in the machine shouldn't change acpidump results. Is that not correct? Jon From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:30:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41F5516A4CF; Thu, 31 Mar 2005 05:30:02 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39A2343D41; Thu, 31 Mar 2005 05:29:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2V5XX8W014716; Wed, 30 Mar 2005 22:33:33 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <424B8A4F.7050607@samsco.org> Date: Wed, 30 Mar 2005 22:27:43 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: noackjr@alumni.rice.edu References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> In-Reply-To: <424B8A94.5070300@alumni.rice.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: Greg 'groggy' Lehey cc: freebsd-stable@FreeBSD.org cc: John Baldwin cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 05:30:02 -0000 Jon Noack wrote: > On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: >> >>> Greg 'groggy' Lehey wrote: >>> >>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >>>> >>>>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>>>> >>>>>>> lapic0: LINT1 trigger: edge >>>>>>> lapic0: LINT1 polarity: high >>>>>>> lapic1: Routing NMI -> LINT1 >>>>>>> lapic1: LINT1 trigger: edge >>>>>>> lapic1: LINT1 polarity: high >>>>>>> -ioapic0 irqs 0-23 on motherboard >>>>>>> +ioapic0 irqs 0-23 on motherboard >>>>>>> cpu0 BSP: >>>>>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >>>>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff >>>>> >>>>> >>>>> This shows that in the - case the APIC is broken somehow (0.0 isn't a >>>>> valid I/O APIC version). >>>> >>>> >>>> You mean the + case, I suppose. Yes, that's what I suspected. >>>> >>>> >>>>> It would seem that the system has mapped RAM over top of the I/O >>>>> APIC perhaps? >>>> >>>> >>>> That's what I suspected too, but imp doesn't think so. >>> >>> >>> I'd be more inclined to believe that there is an erroneous mapping >>> by the OS, not that things are fundamentally broken in hardware. >> >> >> Agreed. This has been my favourite hypothesis all along. But isn't >> that what jhb is saying? >> >>> Your SMAP table shows everything correctly. It's becoming hard to >>> break through your pre-concieved notions here and explain how things >>> actually work. >> >> >> No, there's nothing to break through. I think you're just having >> problems >> >> 1. expressing yourself, and >> 2. understanding what I'm saying. >> >> I have no preconceived notions. All I can see here is an antagonistic >> attitude on your part. What's the problem? You'll recall from my >> first message that I asked for suggestions about how to approach the >> issue. jhb provided some; you haven't so far. From what you've >> written, it's unclear whether you disagree with jhb or not. If you >> do, why? If you don't, what's your point here? >> >>>>> It would be interesting to see the contents of your MADT to see if >>>>> it's trying to use a 64-bit PA for your APIC. >>>> >>>> >>>> Any suggestions about how to do so? >>> >>> >>> man acpidump >> >> >> How do you run that on a system that won't boot? > > > You said the system worked with 4 GB (albeit detecting only 3.5 GB). My > perception of this whole ACPI thing is that it is fixed in your BIOS > (although it can be overridden by the OS). As such, the amount of RAM > you have in the machine shouldn't change acpidump results. Is that not > correct? > > Jon This is absolutely correct. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:32:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 869B816A4CE for ; Thu, 31 Mar 2005 05:32:30 +0000 (GMT) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03D4C43D54 for ; Thu, 31 Mar 2005 05:32:30 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-a.dmv.com (mail-gw-cl-a.dmv.com [216.240.97.38]) j2V5oRWa079168; Thu, 31 Mar 2005 00:50:27 -0500 (EST) (envelope-from sven@dmv.com) Received: from [64.45.134.154] (dogpound.dyndns.org [64.45.134.154]) by mail-gw-cl-a.dmv.com (8.12.9/8.12.9) with ESMTP id j2V5q2w5054539; Thu, 31 Mar 2005 00:52:05 -0500 (EST) (envelope-from sven@dmv.com) Message-ID: <424B8B73.8040100@dmv.com> Date: Thu, 31 Mar 2005 00:32:35 -0500 From: Sven Willenberger User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vivek Khera References: <97964ce32490a368d64fa9b3500a8ba6@khera.org> In-Reply-To: <97964ce32490a368d64fa9b3500a8ba6@khera.org> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.38 cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 05:32:30 -0000 Vivek Khera presumably uttered the following on 03/30/05 20:22: > > On Mar 29, 2005, at 7:39 PM, Sten Spans wrote: > >> There was an amr panic related to the management ioctls >> which was fixed and backported to RELENG_5. You should have >> this fix. amr controllers a supported quite well on freebsd >> thanks to Scott's great work. >> > > Yes, that was part of the reason I cvsup'd again last week... to ensure > I had the latest fixes to the amr driver. > >> The only way to get closer to solving these problems >> is to dig and try to narrow it down: >> >> - Have you tried running with debugging ? > > > any more than having the kernel debugger installed? When the box locked > up I couldn't even drop into the kernel debugger from the serial > console. neither the BREAK signal nor the alt key sequence invoked it. > >> >> - Have you tried using other network cards ? >> ( yeah that sucks I know ) > > > Nope. Machine is brand spanking new. Was in service a whole of 5 days > before it locked up. The twin of this machine also has issues with the > BIOS reporting "memory size changed" while the machine is running... so > I'm a bit concerned that there is some generic problem with the K8SR and > a megaraid controller. But that one never had any complaints about the > ethernet, and the memory size error persisted across two motherboards. > > I have yet to try the other ethernet port on this box as well. > >> >> - Are you absolutely sure that all the disks are working ? >> ( there have been reports of amr cards acting strange with >> silently failing disks ) > > > The megaraid bios showed all disks as active. How would one tell if you > had a silently failing disk? :-( > >> - Have you got the ufs fixes recently backported to releng_5 ? > > > If it was prior to March 22, then yes I have them. Where in cvsweb > might I look to test? > >> These are the first I can think of. RELENG_5 seems to be >> a bit of a moving target with some quite critical fixes >> going in ( which is good offcourse :). > > > Yes, it is good.... until you can't figure out if it is your hardware or > software flaking out on ya... > > Thanks so much for responding. > > For price-no-object, which vendor would you choose for an AMD system > today? Same question if price is somewhat of a concern. Thanks. > For a piece of anecdotal evidence we are running a dual opteron k8s pro with 8GB of RAM and the 320-2x Megaraid controller (which controls all the harddrives) Except for a problem with fxp (which I haven't gone back to reinvestigate but rather just used the Broadcom gigE instead) the system so far has run fairly stable (running Postgres under a medium load at the moment). We had one issue of a "spontaneous" reboot that left no indication of what happened in messages; this box is still in our testing area so it is possible that it was the result of a power[cord] issue. This is running 5.4-PRERELEASE from 17 March. Also, we disabled the onboard adaptec controllers in the bios (as we don't use them). Sven From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:49:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C209B16A4CE; Thu, 31 Mar 2005 05:49:18 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDC2E43D3F; Thu, 31 Mar 2005 05:49:13 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 4F11A8564F; Thu, 31 Mar 2005 15:19:11 +0930 (CST) Date: Thu, 31 Mar 2005 15:19:11 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050331054911.GN6252@wantadilla.lemis.com> References: <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="djJN5oi3zFpblwUd" Content-Disposition: inline In-Reply-To: <424B8A4F.7050607@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org cc: noackjr@alumni.rice.edu cc: John Baldwin Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 05:49:18 -0000 --djJN5oi3zFpblwUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott Long wrote: > Jon Noack wrote: >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: >>>> Greg 'groggy' Lehey wrote: >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >>>>>> It would be interesting to see the contents of your MADT to see if >>>>>> it's trying to use a 64-bit PA for your APIC. >>>>> >>>>> Any suggestions about how to do so? >>>> >>>> man acpidump >>> >>> How do you run that on a system that won't boot? >> >> You said the system worked with 4 GB (albeit detecting only 3.5 >> GB). Yes, this is correct. A number of people have explained why it only detected 3.5 GB in this configuration. >> My perception of this whole ACPI thing is that it is fixed in your >> BIOS (although it can be overridden by the OS). As such, the >> amount of RAM you have in the machine shouldn't change acpidump >> results. Is that not correct? > > This is absolutely correct. Ah, so you meant to say that the output from the system running with 4 GB memory is useful? That wasn't in the man page you pointed to. What it does say is: > When invoked with the -t flag, the acpidump utility dumps contents of > the following tables: > > ... MADT This may be the case, but between man page and output some terminology must have changed. I can't see any reference to anything like an MADT there. Does that mean that there isn't one, or that ACPI can't find it, or does the section APIC refer to/dump the MADT? Here's the complete output of acpidump -t, anyway: /* RSD PTR: OEM=3DVIAK8, ACPI_Rev=3D1.0x (0) RSDT=3D0xdfee3000, cksum=3D97 */ /* RSDT: Length=3D44, Revision=3D1, Checksum=3D4, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 Entries=3D{ 0xdfee3040, 0xdfee7b40 } */ /* FACP: Length=3D116, Revision=3D1, Checksum=3D255, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 FACS=3D0xdfee0000, DSDT=3D0xdfee30c0 INT_MODEL=3DPIC Preferred_PM_Profile=3DUnspecified (0) SCI_INT=3D9 SMI_CMD=3D0x402f, ACPI_ENABLE=3D0xa1, ACPI_DISABLE=3D0xa0, S4BIOS_R= EQ=3D0x0 PSTATE_CNT=3D0x0 PM1a_EVT_BLK=3D0x4000-0x4003 PM1a_CNT_BLK=3D0x4004-0x4005 PM_TMR_BLK=3D0x4008-0x400b GPE0_BLK=3D0x4020-0x4023 P_LVL2_LAT=3D101 us, P_LVL3_LAT=3D1001 us FLUSH_SIZE=3D0, FLUSH_STRIDE=3D0 DUTY_OFFSET=3D0, DUTY_WIDTH=3D1 DAY_ALRM=3D125, MON_ALRM=3D126, CENTURY=3D50 IAPC_BOOT_ARCH=3D Flags=3D{WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,RESET_REG} RESET_REG=3D0x00000000:0[0] (Memory), RESET_VALUE=3D0x44 */ /* FACS: Length=3D64, HwSig=3D0x00000000, Firm_Wake_Vec=3D0x00000000 Global_Lock=3D Flags=3D Version=3D0 */ /* DSDT: Length=3D19020, Revision=3D1, Checksum=3D28, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x1000, Creator ID=3DMSFT, Creator Revision=3D0x100000e */ /* APIC: Length=3D104, Revision=3D1, Checksum=3D145, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 Local APIC ADDR=3D0xfee00000 Flags=3D{PC-AT} Type=3DLocal APIC ACPI CPU=3D0 Flags=3D{ENABLED} APIC ID=3D0 Type=3DLocal APIC ACPI CPU=3D1 Flags=3D{ENABLED} APIC ID=3D1 Type=3DIO APIC APIC ID=3D2 INT BASE=3D0 ADDR=3D0x00000000fec00000 Type=3DINT Override BUS=3D0 IRQ=3D0 INTR=3D2 Flags=3D{Polarity=3Dconforming, Trigger=3Dconforming} Type=3DINT Override BUS=3D0 IRQ=3D9 INTR=3D9 Flags=3D{Polarity=3Dactive-lo, Trigger=3Dlevel} Type=3DLocal NMI ACPI CPU=3D0 LINT Pin=3D1 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge} Type=3DLocal NMI ACPI CPU=3D1 LINT Pin=3D1 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge} */ Since I don't know anything about ACPI, this doesn't say too much to me. Suggestions welcome. If the APIC section is the MADT, it looks as if we should update the docco. Greg --=20 See complete headers for address and phone numbers. --djJN5oi3zFpblwUd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS49XIubykFB6QiMRAsrtAJ9Su5scTK77GwMfpNlY9226M3PmBgCeJAuW jnGEA6QAiww8SWKmY9EftpM= =qNE4 -----END PGP SIGNATURE----- --djJN5oi3zFpblwUd-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 06:00:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A7DA16A4CE for ; Thu, 31 Mar 2005 06:00:37 +0000 (GMT) Received: from smtp803.mail.sc5.yahoo.com (smtp803.mail.sc5.yahoo.com [66.163.168.182]) by mx1.FreeBSD.org (Postfix) with SMTP id 02EF643D5A for ; Thu, 31 Mar 2005 06:00:36 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noacks@swbell.net@70.240.208.130 with login) by smtp803.mail.sc5.yahoo.com with SMTP; 31 Mar 2005 06:00:35 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 86FB461BC; Thu, 31 Mar 2005 00:00:34 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08538-15; Thu, 31 Mar 2005 00:00:23 -0600 (CST) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 0ADD7612E; Thu, 31 Mar 2005 00:00:23 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.3/8.13.3) with ESMTP id j2V60MMf051937; Thu, 31 Mar 2005 00:00:22 -0600 (CST) (envelope-from noackjr@alumni.rice.edu) Message-ID: <424B91F6.4000400@alumni.rice.edu> Date: Thu, 31 Mar 2005 00:00:22 -0600 From: Jon Noack User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> In-Reply-To: <20050331054911.GN6252@wantadilla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org cc: freebsd-stable@FreeBSD.org cc: John Baldwin cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 06:00:37 -0000 On 03/30/05 23:49, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott Long wrote: >>Jon Noack wrote: >>>On 03/30/05 23:14, Greg 'groggy' Lehey wrote: >>>>On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: >>>>>Greg 'groggy' Lehey wrote: >>>>>>On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >>>>>>>It would be interesting to see the contents of your MADT to see if >>>>>>>it's trying to use a 64-bit PA for your APIC. >>>>>> >>>>>>Any suggestions about how to do so? >>>>> >>>>>man acpidump >>>> >>>>How do you run that on a system that won't boot? >>> >>>You said the system worked with 4 GB (albeit detecting only 3.5 >>>GB). > > Yes, this is correct. A number of people have explained why it only > detected 3.5 GB in this configuration. > >>>My perception of this whole ACPI thing is that it is fixed in your >>>BIOS (although it can be overridden by the OS). As such, the >>>amount of RAM you have in the machine shouldn't change acpidump >>>results. Is that not correct? >> >>This is absolutely correct. > > Ah, so you meant to say that the output from the system running with 4 > GB memory is useful? That wasn't in the man page you pointed to. > What it does say is: > >>When invoked with the -t flag, the acpidump utility dumps contents of >>the following tables: >> >>... MADT > > This may be the case, but between man page and output some terminology > must have changed. I can't see any reference to anything like an MADT > there. Does that mean that there isn't one, or that ACPI can't find > it, or does the section APIC refer to/dump the MADT? Here's the > complete output of acpidump -t, anyway: > > > > Since I don't know anything about ACPI, this doesn't say too much to > me. Suggestions welcome. If the APIC section is the MADT, it looks > as if we should update the docco. My limited research (as in, Google) shows that the MADT was defined as part of ACPI 2.0: http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx According to your previous link the motherboard specs, it supports both ACPI 1.0A and 2.0. Perhaps there is a BIOS knob to toggle between the two? Jon From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 06:15:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B204A16A4CE for ; Thu, 31 Mar 2005 06:15:11 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A985643D1F for ; Thu, 31 Mar 2005 06:15:10 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 9A89A78C62 for ; Thu, 31 Mar 2005 01:15:36 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85925-10 for ; Thu, 31 Mar 2005 01:15:23 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id F2A3B78C35 for ; Thu, 31 Mar 2005 01:15:21 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id F071228DF1; Thu, 31 Mar 2005 01:15:28 -0500 (EST) Date: Thu, 31 Mar 2005 01:15:28 -0500 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050331061527.GF701@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> <200503301527.28612.peter@wemm.org> <20050330234603.GA18631@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050330234603.GA18631@ack.Berkeley.EDU> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: [OT] memtest86 (Was: Problems with AMD64 and 8 GB RAM?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 06:15:11 -0000 Thus spake Mike Hunter (mhunter@ack.Berkeley.EDU) [30/03/05 18:46]: : This reminds me, I noticed that gentoo includes a memtest86 "kernel" in : their install ISO. Would this be a hard feature to include in FreeBSD? In the case of AMD64, it'd be almost pointless. I've not yet been able to run a copy of memtest86 on my machine (though it could have been due to memory problems at the time). memtest86+[1] works great, though. It's a fork from memtest86. [1] http://www.memtest.org/ From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 06:18:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A579416A4CE; Thu, 31 Mar 2005 06:18:18 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 358CD43D3F; Thu, 31 Mar 2005 06:18:15 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id C012D8564D; Thu, 31 Mar 2005 15:48:11 +0930 (CST) Date: Thu, 31 Mar 2005 15:48:11 +0930 From: Greg 'groggy' Lehey To: Jon Noack Message-ID: <20050331061811.GQ6252@wantadilla.lemis.com> References: <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> <424B91F6.4000400@alumni.rice.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VmyrZ50r30oK77nV" Content-Disposition: inline In-Reply-To: <424B91F6.4000400@alumni.rice.edu> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@FreeBSD.org cc: John Baldwin cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 06:18:18 -0000 --VmyrZ50r30oK77nV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 31 March 2005 at 0:00:22 -0600, Jon Noack wrote: > On 03/30/05 23:49, Greg 'groggy' Lehey wrote: >> Here's the complete output of acpidump -t, anyway: >> >> >> >> Since I don't know anything about ACPI, this doesn't say too much to >> me. Suggestions welcome. If the APIC section is the MADT, it looks >> as if we should update the docco. > > My limited research (as in, Google) shows that the MADT was defined as > part of ACPI 2.0: > http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx Thanks for the link. > According to your previous link the motherboard specs, it supports > both ACPI 1.0A and 2.0. Perhaps there is a BIOS knob to toggle > between the two? I've taken a look, but I can't find anything. Greg -- See complete headers for address and phone numbers. --VmyrZ50r30oK77nV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS5YjIubykFB6QiMRAqoBAJ0aUsse9IbnoEaarPvWHDBsop+uEwCcCmdA fZ2rGMvJslk1sSmAgSlpK8c= =F/O7 -----END PGP SIGNATURE----- --VmyrZ50r30oK77nV-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 08:36:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1EDA16A4CE; Thu, 31 Mar 2005 08:36:34 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92E343D41; Thu, 31 Mar 2005 08:36:34 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 79CE12A910; Thu, 31 Mar 2005 00:36:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (dhcp49.wemm.org [10.0.0.49]) by fw.wemm.org (Postfix) with ESMTP id 0CE8CE2B5; Thu, 31 Mar 2005 00:36:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (localhost [127.0.0.1]) by peter-laptop.wemm.org (8.13.3/8.13.3) with ESMTP id j2V8V1TV000822; Thu, 31 Mar 2005 00:31:01 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by peter-laptop.wemm.org (8.13.3/8.13.3/Submit) id j2V8UvMB000818; Thu, 31 Mar 2005 00:30:57 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: peter-laptop.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 31 Mar 2005 00:30:56 -0800 User-Agent: KMail/1.7.2 References: <20050330223546.GA4705@troutmask.apl.washington.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> In-Reply-To: <20050331054911.GN6252@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503310030.57519.peter@wemm.org> cc: freebsd-stable@freebsd.org cc: noackjr@alumni.rice.edu Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 08:36:35 -0000 On Wednesday 30 March 2005 09:49 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott Long wrote: > > Jon Noack wrote: > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: > >>>> Greg 'groggy' Lehey wrote: > >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: > >>>>>> It would be interesting to see the contents of your MADT to see if > >>>>>> it's trying to use a 64-bit PA for your APIC. > >>>>> > >>>>> Any suggestions about how to do so? > >>>> > >>>> man acpidump > >>> > >>> How do you run that on a system that won't boot? > >> > >> You said the system worked with 4 GB (albeit detecting only 3.5 > >> GB). > > Yes, this is correct. A number of people have explained why it only > detected 3.5 GB in this configuration. > You're also being confused by the implementation of the 'real memory' report. If you take a 30 second glance at the code, you'll see that it is reporting the same units that the hw.maxmem tunable uses. ie: it is the LIMIT or Highest Address that the system has, not the sum total of all the parts. eg: see the machdep.c comment next to the printf * Maxmem isn't the "maximum memory", it's one larger than the * highest page of the physical address space. It should be * called something like "Maxphyspage". We may adjust this * based on ``hw.physmem'' and the results of the memory test. The SMAP lines are what you need to pay attention to. In the output you posted with 8G, you can see the 4GB going from the 4->8GB range, exactly. SMAP type 1 is "usable memory". -Peter From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 09:28:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C504616A4CE for ; Thu, 31 Mar 2005 09:28:48 +0000 (GMT) Received: from ZCCCXC.dsl.saunalahti.fi (ZCCCXC.dsl.saunalahti.fi [85.76.68.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id C959043D41 for ; Thu, 31 Mar 2005 09:28:47 +0000 (GMT) (envelope-from backi@backi.iki.fi) Received: from backi.iki.fi (localhost [127.0.0.1])j2V9SkqC030352 for ; Thu, 31 Mar 2005 12:28:46 +0300 (EEST) (envelope-from backi@backi.iki.fi) Received: (from backi@localhost) by backi.iki.fi (8.13.3/8.13.1/Submit) id j2V9SkOH030351 for freebsd-amd64@freebsd.org; Thu, 31 Mar 2005 12:28:46 +0300 (EEST) (envelope-from backi) Date: Thu, 31 Mar 2005 12:28:46 +0300 From: Patrik Backlund To: freebsd-amd64@freebsd.org Message-ID: <20050331092846.GA30291@backi.iki.fi> References: <20050208193338.6ee460d9.mark@hyow.eu.org> <20050215113649.7bfcb1cd.mark@hyow.eu.org> <20050215180011.GD38158@dragon.nuxi.com> <20050216002130.GA73909@isis.wad.cz> <1108516734.1564.6.camel@hood.oook.cz> <20050216060600.GB2900@dragon.nuxi.com> <84dead7205021603445155fafc@mail.gmail.com> <20050216174031.GB82895@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050216174031.GB82895@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i Subject: Re: Asus K8S-MX X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 09:28:48 -0000 On Wed, Feb 16, 2005 at 09:40:31AM -0800, David O'Brien wrote: > On Wed, Feb 16, 2005 at 11:44:18AM +0000, Joseph Koshy wrote: > > > There are also SiS and ALi based motherboards. I haven't heard of any > > > problems with them. > > > > I tried FreeBSD on an ASUS K8S-MX which is based on the SiS > > SiS760GX and 965L chipsets. Our ATA driver had problems with > > UDMA modes with the 965 chipset; it only worked in PIO4 mode. > > Can you try ATA-mkIII? > Otherwise can you report the issue to Soren? Søren has now committed the necessary device ids for this board to work in current. I've applied his ata patches to my RELENG_5 and at least the SATA part works just fine. See kern/70296 for a one line patch to get the on-board sound working. -Patrik From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 10:16:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A45116A4FB for ; Thu, 31 Mar 2005 10:16:28 +0000 (GMT) Received: from post.00t.org (feynman.00t.org [217.160.135.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id E327C43D55 for ; Thu, 31 Mar 2005 10:16:27 +0000 (GMT) (envelope-from ulrik@00t.org) Received: from [172.24.0.14] (pD9E1F9E4.dip.t-dialin.net [217.225.249.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by post.00t.org (Postfix) with ESMTP id 21E7C192BD; Thu, 31 Mar 2005 12:16:26 +0200 (CEST) Message-ID: <424BCDFD.8050701@00t.org> Date: Thu, 31 Mar 2005 12:16:29 +0200 From: Ulrik Guenther User-Agent: Mozilla Thunderbird 1.0 (X11/20050309) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Hopkins References: In-Reply-To: X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: "freebsd-amd64@freebsd.org" Subject: Re: Cross-compiling/porting to Linux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 10:16:28 -0000 Hi Michael, the following commands have to be issued for correct installation of the packages: mkdir /compat/linux cd /compat/linux tar xvpzf /somewhere/aaa_base-10.0.0-noarch-1.tgz sh install/doinst.sh rmdir dev home root tmp var/tmp tar xvpzf /somewhere/aaa_elflibs-9.2.0-i486-1.tgz sh install/doinst.sh tar xvpzf /somewhere/glibc-solibs-2.3.2-i486-6.tgz !!! sed -e 's,/sbin/ldconfig,/nonexistent,g' -e 's,cp -a,cp -p,g' -i '' install/doinst.sh sh install/doinst.sh tar xvpzf /somewhere/x11-6.7.0-i486-4.tgz sh install/doinst.sh echo '/usr/X11R6/lib' >etc/ld.so.conf brandelf -t Linux sbin/ldconfig sbin/ldconfig The sed command (before which I put the three !) is of utmost importance, otherwise one *will* get the error you got. If you have done all correctly, just try it again, it's a bit tricky. I already used this procedure on about three installations (two i386 and one amd64) and for me it works better than the redhat rpms from the ports. But I have to say that I had the same problem like you once, I think it was on the amd64 machine, I tried it again and it worked very well. Have you used Slackware 10 or 10.1 by the way? Have fun ;) Ulrik Michael Hopkins wrote: > Hmmm... > > All Linux commands fail with this :o{ > > root@Athlon /usr/compat/linux/usr/bin # ./gcc -v > > ELF interpreter /lib/ld-linux.so.2 not found > Abort trap > > > I wonder if this is to do with the error message I got when running this at > the end of section 2? > > sbin/ldconfig > > M > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > _/ _/ _/_/_/ Hopkins Research Ltd > _/ _/ _/ _/ > _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ > _/ _/ _/ _/ > _/ _/ _/ _/ 'touch the future' > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 11:04:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D0B516A4CE for ; Thu, 31 Mar 2005 11:04:19 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D092143D49 for ; Thu, 31 Mar 2005 11:04:18 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id F1CFB97066 for ; Thu, 31 Mar 2005 03:04:17 -0800 (PST) Message-Id: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Thu, 31 Mar 2005 03:04:34 -0800 To: freebsd-amd64@freebsd.org From: ray@redshift.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: AMD64 kernel config file question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 11:04:19 -0000 Hi, I'm setting up FreeBSD 5.3 for the first time on an Tyan dual opteron board. I've done plenty of i386 installs, but this is the first on AMD. Anyway, I'm stripping down the kernel for a re-compile and I was wondering if anyone either had a sample config file they could send over and/or if someone could let me know what they are running for these lines? For the CPU/machine stuff, does this look okay (i.e. is K8 the correct option for the Opteron 246's?) machine amd64 cpu K8 ident AMD64 And for dual CPU's, I use this on i386 - is it the same for AMD? # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC Thanks! Ray From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 11:14:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D669416A4CE; Thu, 31 Mar 2005 11:14:50 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 436C143D5F; Thu, 31 Mar 2005 11:14:50 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DGxdQ-0008J0-00; Thu, 31 Mar 2005 12:14:48 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 31 Mar 2005 12:14:47 +0100 From: Michael Hopkins To: "freebsd-amd64@freebsd.org" , , , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 11:14:51 -0000 Hi all I have been installing a few Linux environments from the ports in the last few days to try and establish a cross-compiler for 32-bit Linux on amd64 (see my other post for the story so far). I thought it might be useful for others on this path to be told about what works and what doesn't. System is: root@Athlon ~ # uname -a FreeBSD Athlon 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #2: Wed Mar 30 01:46:52 BST 2005 root@Athlon:/usr/obj/usr/src/sys/ATHLON amd64 First steps ----------- First of all, I believe you need to do this as pointed out by Axel Gonzalez. Add these to the kernel and rebuild: options LINPROCFS options COMPAT_43 options COMPAT_LINUX32 and on rc.conf: linux_enable="YES" Working ------- linux_base-8 (redhat 8) linux_base-suse (suse 9.2) linux_base-debian (debian woody) All installed OK and gave correct answers to /compat/linux/bin/uname -a emulators/linux_base-gentoo-stage1 ---------------------------------- Starting Terminal in /usr/ports/emulators/linux_base-gentoo-stage1... bash-2.05b# make ===> linux_base-gentoo-stage1-2004.3 is marked as broken: Incorrect pkg-plist. devel/linux_devtools-7 ---------------------- Starting Terminal in /usr/ports/devel/linux_devtools-7... bash-2.05b# make ===> linux_devtools-7.1_3 is marked as broken: Incomplete pkg-plist. emulators/linux_base-rh-9 ------------------------- Makes OK but fails on install with a message something like "script error for glibc-..." - sorry I didn't copy output so that's from memory. Slackware 10.1 -------------- I also followed the instructions from here to try slackware which was suggested by Ulrik Guenther http://people.freebsd.org/~tjr/linux32.html Unfortunately the install process didn't happen exactly like on the page: # sbin/ldconfig sbin/ldconfig: Can't open configuration file /etc/ld.so.conf: No such file or directory And all Linux commands gave this error: # ./gcc -v ELF interpreter /lib/ld-linux.so.2 not found Abort trap Ulrik has just sent me some more detailed instructions, so I may give this another go. mkdir /compat/linux cd /compat/linux tar xvpzf /somewhere/aaa_base-10.0.0-noarch-1.tgz sh install/doinst.sh rmdir dev home root tmp var/tmp tar xvpzf /somewhere/aaa_elflibs-9.2.0-i486-1.tgz sh install/doinst.sh tar xvpzf /somewhere/glibc-solibs-2.3.2-i486-6.tgz sed -e 's,/sbin/ldconfig,/nonexistent,g' -e 's,cp -a,cp -p,g' -i '' install/doinst.sh sh install/doinst.sh tar xvpzf /somewhere/x11-6.7.0-i486-4.tgz sh install/doinst.sh echo '/usr/X11R6/lib' >etc/ld.so.conf brandelf -t Linux sbin/ldconfig sbin/ldconfig In general ---------- A lot of Linux ports are giving this message which I suspect may not always be appropriate: ...is only for i386, and you are running amd64. hth Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 11:14:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7080116A4EB for ; Thu, 31 Mar 2005 11:14:57 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7ACA43D39 for ; Thu, 31 Mar 2005 11:14:56 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id B3A4A1F09B; Thu, 31 Mar 2005 13:14:55 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 8F6D0697F; Thu, 31 Mar 2005 13:14:55 +0200 (CEST) Date: Thu, 31 Mar 2005 13:14:55 +0200 From: Marc Olzheim To: ray@redshift.com Message-ID: <20050331111455.GC34216@stack.nl> References: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> X-Operating-System: FreeBSD hammer.stack.nl 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 kernel config file question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 11:14:57 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 31, 2005 at 03:04:34AM -0800, ray@redshift.com wrote: > Hi, >=20 > I'm setting up FreeBSD 5.3 for the first time on an Tyan dual opteron b= oard. > I've done plenty of i386 installs, but this is the first on AMD. Anyway,= I'm > stripping down the kernel for a re-compile and I was wondering if anyone = either > had a sample config file they could send over and/or if someone could let= me > know what they are running for these lines? =20 See /usr/src/sys/amd64/conf/* (GENERIC for instance) Use "cpu HAMMER" Marc --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCS9uvezjnobFOgrERAqxnAJsGxCEb4sGRTfLgJwdTcmaJzdCPWACff/Y9 eQtEH2zgtF5iU5drIpfpR/o= =+9nx -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 11:17:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C5A416A4CE; Thu, 31 Mar 2005 11:17:37 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30B3E43D5C; Thu, 31 Mar 2005 11:17:37 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id F1CD22A8F3; Thu, 31 Mar 2005 03:17:36 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (dhcp49.wemm.org [10.0.0.49]) by fw.wemm.org (Postfix) with ESMTP id 7E06CE2B3; Thu, 31 Mar 2005 03:17:36 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (localhost [127.0.0.1]) by peter-laptop.wemm.org (8.13.3/8.13.3) with ESMTP id j2VBDcJt001335; Thu, 31 Mar 2005 03:13:40 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by peter-laptop.wemm.org (8.13.3/8.13.3/Submit) id j2V8UvMB000818; Thu, 31 Mar 2005 00:30:57 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: peter-laptop.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 31 Mar 2005 00:30:56 -0800 User-Agent: KMail/1.7.2 References: <20050330223546.GA4705@troutmask.apl.washington.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> In-Reply-To: <20050331054911.GN6252@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503310030.57519.peter@wemm.org> cc: freebsd-stable@freebsd.org cc: noackjr@alumni.rice.edu Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 11:17:37 -0000 On Wednesday 30 March 2005 09:49 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott Long wrote: > > Jon Noack wrote: > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: > >>>> Greg 'groggy' Lehey wrote: > >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: > >>>>>> It would be interesting to see the contents of your MADT to see if > >>>>>> it's trying to use a 64-bit PA for your APIC. > >>>>> > >>>>> Any suggestions about how to do so? > >>>> > >>>> man acpidump > >>> > >>> How do you run that on a system that won't boot? > >> > >> You said the system worked with 4 GB (albeit detecting only 3.5 > >> GB). > > Yes, this is correct. A number of people have explained why it only > detected 3.5 GB in this configuration. > You're also being confused by the implementation of the 'real memory' report. If you take a 30 second glance at the code, you'll see that it is reporting the same units that the hw.maxmem tunable uses. ie: it is the LIMIT or Highest Address that the system has, not the sum total of all the parts. eg: see the machdep.c comment next to the printf * Maxmem isn't the "maximum memory", it's one larger than the * highest page of the physical address space. It should be * called something like "Maxphyspage". We may adjust this * based on ``hw.physmem'' and the results of the memory test. The SMAP lines are what you need to pay attention to. In the output you posted with 8G, you can see the 4GB going from the 4->8GB range, exactly. SMAP type 1 is "usable memory". -Peter From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 11:19:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F2C116A4CE for ; Thu, 31 Mar 2005 11:19:37 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E20143D5D for ; Thu, 31 Mar 2005 11:19:37 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id 716FD9706A; Thu, 31 Mar 2005 03:19:36 -0800 (PST) Message-Id: <3.0.1.32.20050331031951.00a8f798@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Thu, 31 Mar 2005 03:19:51 -0800 To: Marc Olzheim From: ray@redshift.com In-Reply-To: <20050331111455.GC34216@stack.nl> References: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 kernel config file question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 11:19:37 -0000 Thanks very much Marc - I'm hunting around and looking at the different files in there and sorting it out. I'll look through your file as well. Thanks again! Ray At 01:14 PM 3/31/2005 +0200, Marc Olzheim wrote: | On Thu, Mar 31, 2005 at 03:04:34AM -0800, ray@redshift.com wrote: | > Hi, | > | > I'm setting up FreeBSD 5.3 for the first time on an Tyan dual opteron board. | > I've done plenty of i386 installs, but this is the first on AMD. Anyway, I'm | > stripping down the kernel for a re-compile and I was wondering if anyone either | > had a sample config file they could send over and/or if someone could let me | > know what they are running for these lines? | | See /usr/src/sys/amd64/conf/* (GENERIC for instance) | | Use "cpu HAMMER" | | Marc | | Attachment Converted: "c:\eudora2\ATTACH\Re AMD64 kernel config file qu" | From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:20:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA17616A4CE; Thu, 31 Mar 2005 13:20:53 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFA3643D31; Thu, 31 Mar 2005 13:20:52 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DGzbP-0008GR-00; Thu, 31 Mar 2005 14:20:51 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 31 Mar 2005 14:20:50 +0100 From: Michael Hopkins To: "freebsd-amd64@freebsd.org" , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Installing GCC tools for linux cross-compile on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:20:53 -0000 Hi all I have been installing a few Linux environments from the ports in the last few days to try and establish a cross-compiler for 32-bit Linux on amd64. I have established that the Redhat 8, SUSE 9.2 and Debian Woody ports install OK. I've been told that Slackware 10 can also be installed manually (see my other post for more details on all of the above). The next step is to get a working set of gcc tools. Unfortunately, the linux_devtools port is broken and so is the gentoo port which I believe would bootstrap itself and then install everything (including gcc tools, I assume) from source. Gentoo was also my preference because portage would seem to be the most port-like way of system maintenance. With the above working Linux environments I seem to have the following options for installing the gcc toolset. 1) binary RPMs 2) tarballs 3) apt-get/dpkg/dselect Although the first two are a bit of a fiddle to carry out that is not a real problem. I have done (1) for the SUSE port, but when I use gcc I get this: cc: installation problem, cannot exec `cc1': No such file or directory make: *** [LD_search.o] Error 1 Checking cc -v gives: Using built-in specs. Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc version 3.3.4 (pre 3.3.5 20040809) So I guess it is looking in all the wrong places for it's libraries. I have tried to alleviate that in the makefile C flags with: CC = /compat/linux/usr/bin/cc -B/usr/compat/linux/usr -B/usr/compat/linux/usr/local -B/usr/compat/linux/lib -B/usr/compat/linux/usr/lib -I/usr/compat/linux/usr/include/g++ But it doesn't change anything. I haven't tried (2) because I couldn't successfully install slackware yet. I'm not clear whether the problem of hard-coded directories mentioned above would be alleviated or not. Maybe someone has already produced a tarball or RPM which contains the gcc tools set up correctly for /compat/linux/? I like (3) - which is probably the default method in Debian - because it is automatic and would handle dependencies, but I am worried that the automatic tools could install stuff all over my / directory rather than inside /compat/linux/ where I want it all to stay. Also not sure whether they would/should store their databases inside /compat/linux or on /. Any thoughts or tips that lead to a safe and effective solution for this much appreciated and a great help to the software development community on FreeBSD who want to target Linux. If I can get it working and learn enough about port makefiles then I could try to automate it and make it available. TIA Michael _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:29:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB5C816A4CE for ; Thu, 31 Mar 2005 13:29:14 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E1C543D49 for ; Thu, 31 Mar 2005 13:29:12 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 9E6ECB80C for ; Thu, 31 Mar 2005 08:29:11 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <424B8B73.8040100@dmv.com> References: <97964ce32490a368d64fa9b3500a8ba6@khera.org> <424B8B73.8040100@dmv.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 31 Mar 2005 08:29:13 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:29:14 -0000 On Mar 31, 2005, at 12:32 AM, Sven Willenberger wrote: > For a piece of anecdotal evidence we are running a dual opteron k8s > pro with 8GB of RAM and the 320-2x Megaraid controller (which controls > all the harddrives) Except for a problem with fxp (which I haven't > gone back to reinvestigate but rather just used the Broadcom gigE > instead) the system so far has run fairly stable (running Postgres > under a medium load at the moment). We had one issue of a > "spontaneous" reboot that left no indication of what happened in > messages; this box is still in our testing area so it is possible that > it was the result of a power[cord] issue. This is running > 5.4-PRERELEASE from 17 March. Also, we disabled the onboard adaptec > controllers in the bios (as we don't use them). If you can try under very heavy network + disk load, I'd appreciate it. I'm usually locking up and/or having ethernet timeouts when the postgres DB is being dumped and some large reports are running. The DB is about 51Gb on disk, and the dump is going across the network to another machine. The ethernet is connected to a gigE switch. Throw in a postgres VACUUM in there and I'm almost guaranteed a lockup of some sort. I'm not sure the difference of the K8SR and K8S Pro, so it may still be something with the K8SR for all I know. Thanks for responding. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:30:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E96E16A4CE for ; Thu, 31 Mar 2005 13:30:45 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E7143D45 for ; Thu, 31 Mar 2005 13:30:44 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 92AEFB80C for ; Thu, 31 Mar 2005 08:30:44 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <20050331061527.GF701@afflictions.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> <200503301527.28612.peter@wemm.org> <20050330234603.GA18631@ack.Berkeley.EDU> <20050331061527.GF701@afflictions.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 31 Mar 2005 08:30:46 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: [OT] memtest86 (Was: Problems with AMD64 and 8 GB RAM?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:30:45 -0000 On Mar 31, 2005, at 1:15 AM, Damian Gerow wrote: > In the case of AMD64, it'd be almost pointless. I've not yet been > able to > run a copy of memtest86 on my machine (though it could have been due to > memory problems at the time). > I found that memtest86 runs on a dual opteron, but doesn't discover my entire 4Gb of RAM. It found 4032Mb only. However, FreeBSD found the whole 4GB. I shall try the memtest86+ next time. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:39:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1313916A4D5 for ; Thu, 31 Mar 2005 13:39:13 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3626C43D2D for ; Thu, 31 Mar 2005 13:39:13 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20079 invoked from network); 31 Mar 2005 13:39:13 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 13:39:12 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VD270A024492; Thu, 31 Mar 2005 08:03:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <424B91F6.4000400@alumni.rice.edu> References: <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> <424B91F6.4000400@alumni.rice.edu> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <709d5024c676e940e8c16e3d3d6aae85@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Thu, 31 Mar 2005 08:03:16 -0500 To: noackjr@alumni.rice.edu X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Greg 'groggy' Lehey cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:39:14 -0000 On Mar 31, 2005, at 1:00 AM, Jon Noack wrote: > My limited research (as in, Google) shows that the MADT was defined as > part of ACPI 2.0: > http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx > > According to your previous link the motherboard specs, it supports > both ACPI 1.0A and 2.0. Perhaps there is a BIOS knob to toggle > between the two? It's part if ACPI 1.0 as well. Trust me, I have machines built before ACPI 2.0 was defined that have MADTs. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:39:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12C8B16A4CE for ; Thu, 31 Mar 2005 13:39:16 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78B0543D2F for ; Thu, 31 Mar 2005 13:39:15 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20112 invoked from network); 31 Mar 2005 13:39:15 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 13:39:13 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VCsj3Z024429; Thu, 31 Mar 2005 07:54:46 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <20050331040811.GL6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4fb44703937dc361f23148ee7956746c@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Thu, 31 Mar 2005 07:54:45 -0500 To: "Greg 'groggy' Lehey" X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Daniel O'Connor cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:39:16 -0000 On Mar 30, 2005, at 11:08 PM, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >> >> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>>> lapic0: LINT1 trigger: edge >>>> lapic0: LINT1 polarity: high >>>> lapic1: Routing NMI -> LINT1 >>>> lapic1: LINT1 trigger: edge >>>> lapic1: LINT1 polarity: high >>>> -ioapic0 irqs 0-23 on motherboard >>>> +ioapic0 irqs 0-23 on motherboard >>>> cpu0 BSP: >>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: >>>> 0x0fffffff >>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: >>>> 0x000001ff >> >> This shows that in the - case the APIC is broken somehow (0.0 isn't a >> valid I/O APIC version). > > You mean the + case, I suppose. Yes, that's what I suspected. > >> It would seem that the system has mapped RAM over top of the I/O >> APIC perhaps? > > That's what I suspected too, but imp doesn't think so. Actually, if the full version register were zero, it would not have had 24 IRQs (irqs 0-23 part), so I'm not sure what it is doing. 0.3 isn't really a valid APIC version AFAIK either, though I'm more familiar with the versions used in Intel APICs (usually 1.1, 1.2, or 2.0). >> It would be interesting to see the contents of your MADT to see if >> it's trying to use a 64-bit PA for your APIC. > > Any suggestions about how to do so? Boot with 4g or boot an i386 version and get acpidump -t output. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:39:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FFE916A4DD for ; Thu, 31 Mar 2005 13:39:17 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDE6443D2F for ; Thu, 31 Mar 2005 13:39:16 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20170 invoked from network); 31 Mar 2005 13:39:16 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 13:39:15 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VD2709024492; Thu, 31 Mar 2005 08:02:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <20050331054911.GN6252@wantadilla.lemis.com> References: <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7e7866bad9099b3d8a8e0f174b6229ce@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Thu, 31 Mar 2005 08:02:07 -0500 To: "Greg 'groggy' Lehey" X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org cc: noackjr@alumni.rice.edu Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:39:17 -0000 On Mar 31, 2005, at 12:49 AM, Greg 'groggy' Lehey wrote: > This may be the case, but between man page and output some terminology > must have changed. I can't see any reference to anything like an MADT > there. Does that mean that there isn't one, or that ACPI can't find > it, or does the section APIC refer to/dump the MADT? Here's the > complete output of acpidump -t, anyway: MADT is the name of the table (Multiple APIC Descriptor Table or some such), but "APIC" is the 4 character signature of the MADT, hence seeing 'APIC' output from acpidump -t when looking at the MADT. Similarly, the MP Table is known as the MP Table, but the signature for the table that you search for in the BIOS is "_MP_". > /* > APIC: Length=104, Revision=1, Checksum=145, > OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, > Creator ID=AWRD, Creator Revision=0x0 > Local APIC ADDR=0xfee00000 > Flags={PC-AT} > > Type=Local APIC > ACPI CPU=0 > Flags={ENABLED} > APIC ID=0 > > Type=Local APIC > ACPI CPU=1 > Flags={ENABLED} > APIC ID=1 > > Type=IO APIC > APIC ID=2 > INT BASE=0 > ADDR=0x00000000fec00000 > > Type=INT Override > BUS=0 > IRQ=0 > INTR=2 > Flags={Polarity=conforming, Trigger=conforming} > > Type=INT Override > BUS=0 > IRQ=9 > INTR=9 > Flags={Polarity=active-lo, Trigger=level} > > Type=Local NMI > ACPI CPU=0 > LINT Pin=1 > Flags={Polarity=active-hi, Trigger=edge} > > Type=Local NMI > ACPI CPU=1 > LINT Pin=1 > Flags={Polarity=active-hi, Trigger=edge} > */ Nothing strange here, and it is giving a 64-bit PA for the I/O APIC, albeit one that is < 4GB. One thing to verify is that the physical addresses listed here for the APICs (0xfec00000 and 0xfee00000) aren't included in the SMAP as valid RAM addresses in both cases. It might be useful to boot an i386 CD with 8GB in the machine to see if the MADT looks any different in that case. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:39:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DB7D16A4DC for ; Thu, 31 Mar 2005 13:39:19 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DBC843D2F for ; Thu, 31 Mar 2005 13:39:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20196 invoked from network); 31 Mar 2005 13:39:18 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 13:39:17 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VCvRHw024457; Thu, 31 Mar 2005 07:57:27 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <424B8A4F.7050607@samsco.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8019fdb08e141c32fc2621d399301455@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Thu, 31 Mar 2005 07:57:27 -0500 To: Scott Long X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Greg 'groggy' Lehey cc: freebsd-stable@FreeBSD.org cc: noackjr@alumni.rice.edu cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:39:19 -0000 On Mar 31, 2005, at 12:27 AM, Scott Long wrote: > Jon Noack wrote: >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: >>> >>>> Greg 'groggy' Lehey wrote: >>>> >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: >>>>> >>>>>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >>>>>> >>>>>>>> lapic0: LINT1 trigger: edge >>>>>>>> lapic0: LINT1 polarity: high >>>>>>>> lapic1: Routing NMI -> LINT1 >>>>>>>> lapic1: LINT1 trigger: edge >>>>>>>> lapic1: LINT1 polarity: high >>>>>>>> -ioapic0 irqs 0-23 on motherboard >>>>>>>> +ioapic0 irqs 0-23 on motherboard >>>>>>>> cpu0 BSP: >>>>>>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: >>>>>>>> 0x0fffffff >>>>>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: >>>>>>>> 0x000001ff >>>>>> >>>>>> >>>>>> This shows that in the - case the APIC is broken somehow (0.0 >>>>>> isn't a >>>>>> valid I/O APIC version). >>>>> >>>>> >>>>> You mean the + case, I suppose. Yes, that's what I suspected. >>>>> >>>>> >>>>>> It would seem that the system has mapped RAM over top of the I/O >>>>>> APIC perhaps? >>>>> >>>>> >>>>> That's what I suspected too, but imp doesn't think so. >>>> >>>> >>>> I'd be more inclined to believe that there is an erroneous mapping >>>> by the OS, not that things are fundamentally broken in hardware. >>> >>> >>> Agreed. This has been my favourite hypothesis all along. But isn't >>> that what jhb is saying? >>> >>>> Your SMAP table shows everything correctly. It's becoming hard to >>>> break through your pre-concieved notions here and explain how things >>>> actually work. >>> >>> >>> No, there's nothing to break through. I think you're just having >>> problems >>> >>> 1. expressing yourself, and >>> 2. understanding what I'm saying. >>> >>> I have no preconceived notions. All I can see here is an >>> antagonistic >>> attitude on your part. What's the problem? You'll recall from my >>> first message that I asked for suggestions about how to approach the >>> issue. jhb provided some; you haven't so far. From what you've >>> written, it's unclear whether you disagree with jhb or not. If you >>> do, why? If you don't, what's your point here? >>> >>>>>> It would be interesting to see the contents of your MADT to see if >>>>>> it's trying to use a 64-bit PA for your APIC. >>>>> >>>>> >>>>> Any suggestions about how to do so? >>>> >>>> >>>> man acpidump >>> >>> >>> How do you run that on a system that won't boot? >> You said the system worked with 4 GB (albeit detecting only 3.5 GB). >> My perception of this whole ACPI thing is that it is fixed in your >> BIOS (although it can be overridden by the OS). As such, the amount >> of RAM you have in the machine shouldn't change acpidump results. Is >> that not correct? >> Jon > > This is absolutely correct. It might though. Notice the change in APIC version with 4GB of RAM vs 8GB. The APIC hardware is the same, so that's already indicative of something fishy going on. I think that his APIC address is correct though as otherwise no interrupts at all would work and it wouldn't claim to have 24 IRQs on the APIC in both cases. One can always boot an i386 non-PAE kernel with 8GB in the machine and get an acpidump though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:41:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FB4916A4CE for ; Thu, 31 Mar 2005 13:41:01 +0000 (GMT) Received: from web60007.mail.yahoo.com (web60007.mail.yahoo.com [216.109.116.245]) by mx1.FreeBSD.org (Postfix) with SMTP id AD67643D58 for ; Thu, 31 Mar 2005 13:41:00 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 28319 invoked by uid 60001); 31 Mar 2005 13:40:59 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=sxs8WulATWaSdUakxy2ucgh56gEwkkb4XWYt5/JrdkbezKaQjsV5WnKX24wFXj1rRG7xCIofOysQDzwMbr8+0FsY4V5ymn9iZQgvKhCn0PKXkFI+2r1H7luegr28zEyjKKjEKAsBsBLLGtmGdhUW82UI+QYQQ+xUFR6e/A8aatk= ; Message-ID: <20050331134059.28315.qmail@web60007.mail.yahoo.com> Received: from [68.223.154.92] by web60007.mail.yahoo.com via HTTP; Thu, 31 Mar 2005 05:40:59 PST Date: Thu, 31 Mar 2005 05:40:59 -0800 (PST) From: Tom Shafron To: freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: AMD64 kernel config file question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:41:01 -0000 Neither the amd6/conf/GENERIC nor SMP config file included: device apic I built my dual proc amd64s (5.3 release) on a tyan k8s pro without it and the SMP is seems to be working ok (tested it with openssl and got 2300 rsa1024 signs/sec). Would it help performance if I added it? p.s. Sorry Ray... didn't realize I was replying directly to you... meant to send it to the mailing list... just joined ;) Tom Shafron --- ray@redshift.com wrote: > Thanks very much Marc - I'm hunting around and > looking at the different files in > there and sorting it out. I'll look through your > file as well. Thanks again! > > Ray > > > At 01:14 PM 3/31/2005 +0200, Marc Olzheim wrote: > | On Thu, Mar 31, 2005 at 03:04:34AM -0800, > ray@redshift.com wrote: > | > Hi, > | > > | > I'm setting up FreeBSD 5.3 for the first time > on an Tyan dual opteron board. > | > I've done plenty of i386 installs, but this is > the first on AMD. Anyway, I'm > | > stripping down the kernel for a re-compile and I > was wondering if anyone either > | > had a sample config file they could send over > and/or if someone could let me > | > know what they are running for these lines? > | > | See /usr/src/sys/amd64/conf/* (GENERIC for > instance) > | > | Use "cpu HAMMER" > | > | Marc > | > | Attachment Converted: "c:\eudora2\ATTACH\Re AMD64 > kernel config file qu" > | > _______________________________________________ > 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" > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:41:15 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DD1716A4CE for ; Thu, 31 Mar 2005 13:41:15 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id C622A43D48 for ; Thu, 31 Mar 2005 13:41:14 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 6EBE2B80C for ; Thu, 31 Mar 2005 08:41:14 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <20050331061811.GQ6252@wantadilla.lemis.com> References: <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> <424B91F6.4000400@alumni.rice.edu> <20050331061811.GQ6252@wantadilla.lemis.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <793c088b415f178f50eee5c40224c5d2@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 31 Mar 2005 08:41:16 -0500 To: FreeBSD-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:41:15 -0000 On Mar 31, 2005, at 1:18 AM, Greg 'groggy' Lehey wrote: > On Thursday, 31 March 2005 at 0:00:22 -0600, Jon Noack wrote: >> >> My limited research (as in, Google) shows that the MADT was defined as >> part of ACPI 2.0: >> http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx > > Thanks for the link. > >> According to your previous link the motherboard specs, it supports >> both ACPI 1.0A and 2.0. Perhaps there is a BIOS knob to toggle >> between the two? > > I've taken a look, but I can't find anything. I just ran acpidump -t on one of my dual opterons, and it produced no MADT info, and I *know* I enabled ACPI 2.0 on it in the BIOS... Tyan K8SR. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 13:48:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBA5816A4D0 for ; Thu, 31 Mar 2005 13:48:42 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F0D743D68 for ; Thu, 31 Mar 2005 13:48:42 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.4] (pcp04418836pcs.nrockv01.md.comcast.net [69.140.110.248]) by yertle.kcilink.com (Postfix) with ESMTP id 46F0FB80C for ; Thu, 31 Mar 2005 08:48:42 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 31 Mar 2005 08:48:44 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 13:48:43 -0000 On Mar 29, 2005, at 7:39 PM, Sten Spans wrote: > - Have you tried using other network cards ? > Someone over in stable@ list suggested this: btw, i turn "debug.mpsafenet=0" in /boot/loader.conf to evade the possible network stack deadlock under SMP. in the thread "FreeBSD 5.3 SMP freezes with MySQL 4.1" the last few days. Does this claim of possible network deadlock have any real merit? If so, is it still the case in 5.4-PRE? If I try the above tunable, am I gonna kill some performance? Thanks. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 16:05:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 282FE16A4CF for ; Thu, 31 Mar 2005 16:05:40 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F3A243D5D for ; Thu, 31 Mar 2005 16:05:39 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so574911wri for ; Thu, 31 Mar 2005 08:05:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=pSBCCJ19+N75p54pz05OyZjhWbiGd8L+z8s05OowpEAqaonE/3Zn7XP6XU7t7fb/r5FF0ZMbgpsHxdI79/noqjuIX9HgFv4wvALD1V1qE6RGf6L0Q7+OiZkf5eTBHJArjzYjSJFZ5bfmcRovgOh6p+mx77IUdpUwijUPs6N5PXQ= Received: by 10.54.3.35 with SMTP id 35mr1049466wrc; Thu, 31 Mar 2005 08:05:38 -0800 (PST) Received: by 10.54.29.77 with HTTP; Thu, 31 Mar 2005 08:05:37 -0800 (PST) Message-ID: <790a9fff050331080572081eb6@mail.gmail.com> Date: Thu, 31 Mar 2005 10:05:37 -0600 From: Scot Hetzel To: Michael Hopkins In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: cc: freebsd-ports-bugs@freebsd.org cc: freebsd-emulation@freebsd.org cc: freebsd-ports@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 16:05:40 -0000 On Thu, 31 Mar 2005 12:14:47 +0100, Michael Hopkins wrote: > In general > ---------- > A lot of Linux ports are giving this message which I suspect may not always > be appropriate: > > ...is only for i386, and you are running amd64. > For the ports that are giving you that message, try adding amd64 to the ONLY_FOR_ARCHS variable, and try to install and run the program. If it works, submit a PR with a patch to update the port. This is the only way we'll know if it works on the amd64. Scot From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 16:16:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB63316A4CE for ; Thu, 31 Mar 2005 16:16:25 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DAD343D4C for ; Thu, 31 Mar 2005 16:16:25 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id F22E8B80C for ; Thu, 31 Mar 2005 11:16:24 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <424C215E.5080201@infotechfl.com> References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 31 Mar 2005 11:16:26 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 16:16:25 -0000 On Mar 31, 2005, at 11:12 AM, Gary Mu1der wrote: > Well I can just now reliably hang (no panic, have to reset) my shiny > new AMD64 dual processor box (2 x Opteron 246, Tyan Thunder K8S PRO, > 6GB, Adaptec 2200S) with a simple dd of /dev/mem: > if you've got > 4GB ram, you pretty much *must* run something newer than 5.3-REL. Try bringing it up to 5_STABLE cvs branch and see if you can still lock it up. I don't have my spare machine at the moment to test this theory out, or I would... rather not lockup the production box more often than it does by itself :-( Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 17:06:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF16D16A4CE for ; Thu, 31 Mar 2005 17:06:44 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F76C43D46 for ; Thu, 31 Mar 2005 17:06:44 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so605989wra for ; Thu, 31 Mar 2005 09:06:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YlZwXUn9frkodeKGomiWehPcLckLABsjCghY55bdze+eOmWoZfPnTVVIgIftgkoE92o0a6xGB1lwcGxPCjF2MRPl1IzWKgzhg9z9qCvHz7d1lbsbtVDRZ7cSh0fIGyR0DlyByb5CfRxmawweQZ1CIFqYO8ZbBcdePXoPWjeCEOc= Received: by 10.54.52.42 with SMTP id z42mr958036wrz; Thu, 31 Mar 2005 09:06:43 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 31 Mar 2005 09:06:43 -0800 (PST) Message-ID: <2fd864e05033109061a68554d@mail.gmail.com> Date: Thu, 31 Mar 2005 09:06:43 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <790a9fff050331080572081eb6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <790a9fff050331080572081eb6@mail.gmail.com> cc: Michael Hopkins Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 17:06:44 -0000 On Thu, 31 Mar 2005 10:05:37 -0600, Scot Hetzel wrote: > On Thu, 31 Mar 2005 12:14:47 +0100, Michael Hopkins > wrote: > > In general > > ---------- > > A lot of Linux ports are giving this message which I suspect may not always > > be appropriate: > > > > ...is only for i386, and you are running amd64. > > > For the ports that are giving you that message, try adding amd64 to > the ONLY_FOR_ARCHS variable, and try to install and run the program. > There's another slight issue. Some ports try to use system RPM, (Which causes the error he's talking about), and others try to use Linux RPM. The only way I've found to make this work, is to set it to always use Linux RPM, and to allow amd64 in the ONLY FOR ARCHS... Otherwise, it barfs somewhere along the way, either during the RPM, or during the make. Is there any way, currently in ports, to detect linux emulation? Or better yet, could we just make linux_base_8 a prereq for Linux ports (Or something along those lines), then resolve this AMD64/i386 stuff on that ONE port, and have all the other linux ports just trust, that if that one is there, things will work? From what I understand, the goal is to have complete Linux32 compat... (Or, atleast as good as i386's), in which case any port that doesn't work under Linux32 has a bug of some sort to resolve, and should be considered a special case. I may try adding a "Linux Compat" dependancy.... (IE, /usr/compat/linux must exist, or the kernel must have Linux support). Then we can just go off the assumption that if Linux support is there, the arch you're installing to is irrelevent. Long term.... Perhaps a Linux32 and Linux64 dep? Not sure. Anyone have thoughts on that? I know its been discussed before, but I don't think a resolution ever came out of it. Same goes for /usr/compat, I suppose. For now, I'm going to go with the assumption that there will be /compat/linux32 and linux64. If this has been resolved, let me know so I can make the ports fix I'm gonna work on reflect that. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 17:11:05 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4930816A4CE for ; Thu, 31 Mar 2005 17:11:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98EE443D46 for ; Thu, 31 Mar 2005 17:11:04 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so607304wra for ; Thu, 31 Mar 2005 09:11:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Jgxchfm+nGlo42x6rPvphxsrNzqEsBBaKIQw5Zg/Bt1acrBm1veiEG+HPswc0baUzWffkfy/9DJMODUgMWDnKYRUJiIaO+ySwcHzY+GDz1vUwmevcJZo8d6+JniXs17z0sDmy2qZaJ9rqdi0ATg/CvkZa1YsX45P/hNA5EyPHFQ= Received: by 10.54.98.14 with SMTP id v14mr1536063wrb; Thu, 31 Mar 2005 09:11:04 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 31 Mar 2005 09:11:04 -0800 (PST) Message-ID: <2fd864e0503310911663c460b@mail.gmail.com> Date: Thu, 31 Mar 2005 09:11:04 -0800 From: Astrodog To: Michael Hopkins In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: cc: freebsd-amd64@freebsd.org Subject: Re: Installing GCC tools for linux cross-compile on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 17:11:05 -0000 On Thu, 31 Mar 2005 14:20:50 +0100, Michael Hopkins wrote: > > > Hi all > > I have been installing a few Linux environments from the ports in the last > few days to try and establish a cross-compiler for 32-bit Linux on amd64. > > I have established that the Redhat 8, SUSE 9.2 and Debian Woody ports > install OK. I've been told that Slackware 10 can also be installed manually > (see my other post for more details on all of the above). > > The next step is to get a working set of gcc tools. Unfortunately, the > linux_devtools port is broken and so is the gentoo port which I believe > would bootstrap itself and then install everything (including gcc tools, I > assume) from source. Gentoo was also my preference because portage would > seem to be the most port-like way of system maintenance. > > With the above working Linux environments I seem to have the following > options for installing the gcc toolset. > > 1) binary RPMs > > 2) tarballs > > 3) apt-get/dpkg/dselect > > Although the first two are a bit of a fiddle to carry out that is not a real > problem. I have done (1) for the SUSE port, but when I use gcc I get this: > > cc: installation problem, cannot exec `cc1': No such file or directory > make: *** [LD_search.o] Error 1 > > Checking cc -v gives: > > Using built-in specs. > Configured with: ../configure --enable-threads=posix --prefix=/usr > --with-local-prefix=/usr/local --infodir=/usr/share/info > --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada > --disable-checking --libdir=/usr/lib --enable-libgcj > --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib > --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux > Thread model: posix > gcc version 3.3.4 (pre 3.3.5 20040809) > > So I guess it is looking in all the wrong places for it's libraries. I have > tried to alleviate that in the makefile C flags with: > > CC = /compat/linux/usr/bin/cc -B/usr/compat/linux/usr > -B/usr/compat/linux/usr/local -B/usr/compat/linux/lib > -B/usr/compat/linux/usr/lib -I/usr/compat/linux/usr/include/g++ > > But it doesn't change anything. > > I haven't tried (2) because I couldn't successfully install slackware yet. > I'm not clear whether the problem of hard-coded directories mentioned above > would be alleviated or not. Maybe someone has already produced a tarball or > RPM which contains the gcc tools set up correctly for /compat/linux/? > > I like (3) - which is probably the default method in Debian - because it is > automatic and would handle dependencies, but I am worried that the automatic > tools could install stuff all over my / directory rather than inside > /compat/linux/ where I want it all to stay. Also not sure whether they > would/should store their databases inside /compat/linux or on /. > > Any thoughts or tips that lead to a safe and effective solution for this > much appreciated and a great help to the software development community on > FreeBSD who want to target Linux. If I can get it working and learn enough > about port makefiles then I could try to automate it and make it available. > > TIA > > Michael I suspect an RPM gcc install would work, just make sure you use the RPM with the /compat/linux RPM. If it just can't find the cc1 thing, you may try symlinking in compat linux cc -> cc1. I'll see if I can get anything done on this today, I have 2 AMD64 machines I'd kinda like to be able to compile Linux32 on. I also want to test cross-compiling FreeBSD IA32 ports to i386 from AMD64, I'll let you know how that goes as well. (Sending to freebsd-amd64 only, since this seems to be a very specific issue.) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 17:33:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05FDF16A4CE; Thu, 31 Mar 2005 17:33:45 +0000 (GMT) Received: from neon.webfusion.co.uk (neon.webfusion.co.uk [212.67.202.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3496D43D49; Thu, 31 Mar 2005 17:33:44 +0000 (GMT) (envelope-from michael.hopkins@hopkins-research.com) Received: from 83-216-132-201.markch725.adsl.metronet.co.uk ([83.216.132.201] helo=[192.168.0.5]) by neon.webfusion.co.uk with asmtp (Exim 3.36 #1) id 1DH3Y6-0006Lv-00; Thu, 31 Mar 2005 18:33:42 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 31 Mar 2005 18:33:41 +0100 From: Michael Hopkins To: "freebsd-amd64@freebsd.org" , Message-ID: In-Reply-To: <20050327202607.GA66339@xor.obsecurity.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Re: GNUStep broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 17:33:45 -0000 On 27/3/05 9:26 pm, "Kris Kennaway" wrote: > On Sun, Mar 27, 2005 at 02:02:17PM +0100, Michael wrote: > >> ===> gnustep-objc-1.3.0,1 does not run on ia64 amd64, and you are running >> amd64. >> >> Is this something relatively easy to fix or will it cause grief? I am an >> experienced coder but new to FreeBSD and ports. > > Try commenting out the ONLY_FOR_ARCHS/BROKEN and see what breaks, then > try to fix it :) > > Talk to the developers of the software if you need more help. > > Kris > Started to poke around, and found the error below when trying to make in /usr/ports/devel/gnustep. It seems to be choking on the /usr/ports/lang/gcc-objc make on a header file called output.h (/usr/src/contrib/gcc/output.h, I think). I believe the relevant macro might be this: extern void asm_fprintf (FILE *file, const char *p, ...) ATTRIBUTE_ASM_FPRINTF(2, 3); Defined a few lines above as this: /* Output a string of assembler code, substituting numbers, strings and fixed syntactic prefixes. */ #if GCC_VERSION >= 3004 #define ATTRIBUTE_ASM_FPRINTF(m, n) __attribute__ ((__format__ (__asm_fprintf__, m, n))) ATTRIBUTE_NONNULL(m) /* This is a magic identifier which allows GCC to figure out the type of HOST_WIDE_INT for %wd specifier checks. You must issue this typedef before using the __asm_fprintf__ format attribute. */ typedef HOST_WIDE_INT __gcc_host_wide_int__; #else #define ATTRIBUTE_ASM_FPRINTF(m, n) ATTRIBUTE_NONNULL(m) #endif I'm afraid I can't get into this right now, but it's posted in case someone else understands what is going on here. M ======================= error output from make ============================ cc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-error -DHAVE_CONFIG_H -DGENERATOR_FILE -I/usr/local/include -I. -I. -I.././..//gcc-3.4-20050311/gcc -I.././..//gcc-3.4-20050311/gcc/. -I.././..//gcc-3.4-20050311/gcc/../include insn-conditions.c In file included from insn-conditions.c:30: .././..//gcc-3.4-20050311/gcc/output.h:122: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/output.h:122: warning: ISO C does not allow extra `;' outside of a function In file included from insn-conditions.c:34: .././..//gcc-3.4-20050311/gcc/toplev.h:57: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/toplev.h:58: warning: empty declaration .././..//gcc-3.4-20050311/gcc/toplev.h:61: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/toplev.h:62: warning: empty declaration .././..//gcc-3.4-20050311/gcc/toplev.h:65: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/toplev.h:65: warning: ISO C does not allow extra `;' outside of a function .././..//gcc-3.4-20050311/gcc/toplev.h:74: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/toplev.h:74: warning: ISO C does not allow extra `;' outside of a function .././..//gcc-3.4-20050311/gcc/toplev.h:75: error: syntax error before "ATTRIBUTE_NONNULL" .././..//gcc-3.4-20050311/gcc/toplev.h:75: warning: ISO C does not allow extra `;' outside of a function insn-conditions.c:739: warning: string length `534' is greater than the length `509' ISO C89 compilers are required to support insn-conditions.c:1025: warning: string length `533' is greater than the length `509' ISO C89 compilers are required to support insn-conditions.c:1565: warning: string length `597' is greater than the length `509' ISO C89 compilers are required to support gmake[2]: *** [insn-conditions.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/gcc-objc/work/build/gcc' gmake[1]: *** [stage1_build] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc-objc/work/build/gcc' gmake: *** [bootstrap-lean] Error 2 *** Error code 2 Stop in /usr/ports/lang/gcc-objc. *** Error code 1 Stop in /usr/ports/devel/gnustep-make. *** Error code 1 Stop in /usr/ports/devel/gnustep. _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/_/_/ Hopkins Research Ltd _/ _/ _/ _/ _/_/_/_/ _/_/_/ http://www.hopkins-research.com/ _/ _/ _/ _/ _/ _/ _/ _/ 'touch the future' _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 17:49:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E839116A4CE for ; Thu, 31 Mar 2005 17:49:40 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D084943D53 for ; Thu, 31 Mar 2005 17:49:37 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j2VGCI231994; Thu, 31 Mar 2005 11:12:18 -0500 Message-ID: <424C215E.5080201@infotechfl.com> Date: Thu, 31 Mar 2005 11:12:14 -0500 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vivek Khera References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> In-Reply-To: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 17:49:41 -0000 All, Well I can just now reliably hang (no panic, have to reset) my shiny new AMD64 dual processor box (2 x Opteron 246, Tyan Thunder K8S PRO, 6GB, Adaptec 2200S) with a simple dd of /dev/mem: $ uname -a FreeBSD d10.bidx.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 $ dd if=/dev/mem of=/dev/null bs=1024k (hang after about 5 seconds of watching it via top) How do I force a kernel dump or get other diagnostics? The keyboard doesn't seem to respond. Thought it might be due to the fact that I wasn't using a AMD64 kernel, but the same command crashes the following: $ uname -a FreeBSD d10.bidx.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC amd64 I ran memtest+ over night for 16 hours last night with no reported memory errors. Gary From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:05:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AB7E16A4CE for ; Thu, 31 Mar 2005 18:05:57 +0000 (GMT) Received: from web20026.mail.yahoo.com (web20026.mail.yahoo.com [216.136.225.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 87C9843D1D for ; Thu, 31 Mar 2005 18:05:56 +0000 (GMT) (envelope-from mb_jobs@yahoo.com) Received: (qmail 92370 invoked by uid 60001); 31 Mar 2005 18:05:56 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=rLwfGKH22mQW8EfCe+kUJfnJfFL/TsOgbgtae/pXkexwVdAWXKq9PAGGKks5UNIXLQpeeMEVJHi+XA/r9msObLB8Gx66jCFxfFC6SJ9xK2SSsNAPeuq82b68P5SFHOtwlLleGaaiXDUQv/aNm81j85y5N/R1S4puZdKwV7qPqxw= ; Message-ID: <20050331180556.92368.qmail@web20026.mail.yahoo.com> Received: from [65.213.201.18] by web20026.mail.yahoo.com via HTTP; Thu, 31 Mar 2005 10:05:55 PST Date: Thu, 31 Mar 2005 10:05:55 -0800 (PST) From: Michael Bernstein To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: question about quantum computing with 64 bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:05:57 -0000 Can FreeBSD 64 bit on parallel opterons as a core connected via gigabit cards with cross-over cables to other 64 AMD Athlon running FreeBSD and the right algorithm "make a quantum computing network". ?????? Would much RAM be required? and SCSI disks needed as well. Thanks. Mike --- freebsd-amd64-request@freebsd.org wrote: > From: freebsd-amd64-request@freebsd.org > Subject: freebsd-amd64 Digest, Vol 95, Issue 5 > To: freebsd-amd64@freebsd.org > Date: Thu, 31 Mar 2005 11:17:52 +0000 (GMT) > > Send freebsd-amd64 mailing list submissions to > freebsd-amd64@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > or, via email, send a message with subject or body > 'help' to > freebsd-amd64-request@freebsd.org > > You can reach the person managing the list at > freebsd-amd64-owner@freebsd.org > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of freebsd-amd64 digest..." > > > Today's Topics: > > 1. Re: Problems with AMD64 and 8 GB RAM? (Peter > Wemm) > 2. Re: Problems with AMD64 and 8 GB RAM? (M. > Warner Losh) > 3. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 4. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 5. [OT] memtest86 (Was: Problems with AMD64 and 8 > GB RAM?) > (Mike Hunter) > 6. Re: Problems with AMD64 and 8 GB RAM? (Daniel > O'Connor) > 7. Re: Problems with AMD64 and 8 GB RAM? (Steve > Kargl) > 8. Re: Problems with AMD64 and 8 GB RAM? (Daniel > O'Connor) > 9. Re: Tyan k8sr lockups (Vivek Khera) > 10. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 11. Re: Problems with AMD64 and 8 GB RAM? (Daniel > O'Connor) > 12. Re: Problems with AMD64 and 8 GB RAM? > (Matthias Buelow) > 13. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 14. Re: Problems with AMD64 and 8 GB RAM? (John > Baldwin) > 15. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 16. Re: Problems with AMD64 and 8 GB RAM? (Scott > Long) > 17. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 18. Re: Problems with AMD64 and 8 GB RAM? (Jon > Noack) > 19. Re: Problems with AMD64 and 8 GB RAM? (Scott > Long) > 20. Re: Tyan k8sr lockups (Sven Willenberger) > 21. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 22. Re: Problems with AMD64 and 8 GB RAM? (Jon > Noack) > 23. Re: [OT] memtest86 (Was: Problems with AMD64 > and 8 GB RAM?) > (Damian Gerow) > 24. Re: Problems with AMD64 and 8 GB RAM? (Greg > 'groggy' Lehey) > 25. Re: Problems with AMD64 and 8 GB RAM? (Peter > Wemm) > 26. Re: Asus K8S-MX (Patrik Backlund) > 27. Re: Cross-compiling/porting to Linux (Ulrik > Guenther) > 28. AMD64 kernel config file question > (ray@redshift.com) > 29. Working and broken Linux ports on amd64 > (Michael Hopkins) > 30. Re: AMD64 kernel config file question (Marc > Olzheim) > 31. Re: Problems with AMD64 and 8 GB RAM? (Peter > Wemm) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Mar 2005 15:27:28 -0800 > From: Peter Wemm > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: freebsd-amd64@freebsd.org > Cc: AskBj?rn Hansen > Message-ID: <200503301527.28612.peter@wemm.org> > Content-Type: text/plain; charset="iso-8859-1" > > On Wednesday 30 March 2005 03:22 pm, Ask Bjørn > Hansen wrote: > > ...... Original Message ....... > > On Thu, 31 Mar 2005 08:14:45 +0930 "Greg 'groggy' > Lehey" > > > > > > wrote: > > >> Have you run sysutils/memtest86 with the 8 GB? > > > > > >Heh. Difficult when the system doesn't run. > > > > There is a bootable ISO version of memtest86 that > you could try. > > Thats what the port does.. It produces a bootable > floppy or ISO. > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; > peter@yahoo-inc.com > "All of this is for nothing if we don't go to the > stars" - JMS/B5 > > ------------------------------ > > Message: 2 > Date: Wed, 30 Mar 2005 16:37:47 -0700 (MST) > From: "M. Warner Losh" > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: grog@freebsd.org > Cc: freebsd-stable@freebsd.org > Message-ID: > <20050330.163747.105583958.imp@bsdimp.com> > Content-Type: Text/Plain; charset=us-ascii > > In message: > <20050330231753.GA84137@wantadilla.lemis.com> > "Greg 'groggy' Lehey" > writes: > : I've booted with the other 2 DIMMs now (I have 4 2 > GB DIMMs, all the > : MB will hold). No problems. See my last reply to > Scott: I'm > : wondering if the system is ignoring the PCI hole. > > Unlikely. If it was, you'd not have enough of a > system to complain > about. > > Warner > > ------------------------------ > > Message: 3 > Date: Thu, 31 Mar 2005 09:08:23 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Scott Long > Cc: FreeBSD Stable Users > > Message-ID: > <20050330233823.GA6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > [Format recovered--see > http://www.lemis.com/email/email-format.html] > > [gratuitous empty lines removed] > > On Wednesday, 30 March 2005 at 16:23:34 -0700, Scott > Long wrote: > > Greg 'groggy' Lehey wrote: > >> On Wednesday, 30 March 2005 at 16:04:44 -0700, > Scott Long wrote: > >>> Greg 'groggy' Lehey wrote: > >>>> On Wednesday, 30 March 2005 at 15:30:37 -0700, > Scott Long wrote: > >>>>> Greg 'groggy' Lehey wrote: > >>>>>> I've recently acquired an AMD64 box ... > >>>>>> > >>>>>> What's unstable? ... The amd64 > 5.4-PRERELEASE kernel just > >>>>>> hangs/freezes. > >>>>> > >>>>> 5.3-RELEASE has a lot of problems with >4GB > due to busdma issues. > >>>>> Those should no longer be an issue in > RELENG_5, including 5.4-PRE. > >>>> > >>>> They appear to be. > >>> > >>> I don't understand what you mean here. > >> > >> As I said above (and trimmed for convenience), > this problem occurs on > >> 5.4-PRERELEASE as of yesterday morning. The > dmesg shows that too. > > > > And you're certain that it's due to the same > busdma issues that I > > was describing? > > No. > > > I must have missed the evidence that you use to > support this. > > I didn't give any. It appears that I misunderstood > what you were > saying. > > >>>> As I described, it doesn't appear to be the > drivers. > >>> > >>> I don't see how you proved or disproved this. > >> > >> Shall I resend the original message? It seems > independent of any > >> particular driver. That's not proof, of course, > but I didn't claim it > >> was. > > > > Again, I must have missed the part where you > investigated the drivers > > that apply to your particular system. > > The description is still there. > > > I highly doubt that they apply to every 8GB > Opteron system available > > on the market. > > I never suggested that they did. There's every > reason to believe that > it's something to do with this particular > motherboard, but that > doesn't mean that FreeBSD is blameless. > > Greg > -- > When replying to this message, please take care not > to mutilate the > original text. > For more information, see > http://www.lemis.com/email.html > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/ed6de15f/attachment-0001.bin > > ------------------------------ > > Message: 4 > Date: Thu, 31 Mar 2005 09:09:47 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Peter Wemm > Cc: FreeBSD Stable Users > > Message-ID: > <20050330233946.GB6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Wednesday, 30 March 2005 at 15:25:37 -0800, Peter > Wemm wrote: > > On Wednesday 30 March 2005 03:09 pm, Greg 'groggy' > Lehey wrote: > >> On Wednesday, 30 March 2005 at 16:04:44 -0700, > Scott Long wrote: > >>> Greg 'groggy' Lehey wrote: > >>>> As I described, it doesn't appear to be the > drivers. > >>> > >>> I don't see how you proved or disproved this. > >> > >> Shall I resend the original message? It seems > independent of any > >> particular driver. That's not proof, of course, > but I didn't claim > >> it was. > > > > Greg: The busdma problems from 5.3-RELEASE are > fixed. That doesn't > > mean that there are no *other* problems. Scott is > saying "the old > > busdma bug shouldn't be affecting 5.4-PRE", and > he's correct. > > Yes, now I understand. > > > Most likely, something else is happening, eg: > you're running out of KVM > > or something silly like that. I know we're right > on the brink at 8GB. > > The layout of the devices may be just enough to > tip it over the edge. > > Yes, this seems reasonable. Where should I look > next? I'm currently > rebuilding world and will attempt a verbose boot via > serial console > when it's done. Anything else I should try? > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/0221a9f4/attachment-0001.bin > > ------------------------------ > > Message: 5 > Date: Wed, 30 Mar 2005 15:46:03 -0800 > From: Mike Hunter > Subject: [OT] memtest86 (Was: Problems with AMD64 > and 8 GB RAM?) > To: Peter Wemm > Cc: Ask =?unknown-8bit?Q?Bj=F8rn?= Hansen > > Message-ID: > <20050330234603.GA18631@ack.Berkeley.EDU> > Content-Type: text/plain; charset=unknown-8bit > > On Mar 30, "Peter Wemm" wrote: > > > On Wednesday 30 March 2005 03:22 pm, Ask Bjørn > Hansen wrote: > > > ...... Original Message ....... > > > On Thu, 31 Mar 2005 08:14:45 +0930 "Greg > 'groggy' Lehey" > > > > > > > > > wrote: > > > >> Have you run sysutils/memtest86 with the 8 > GB? > > > > > > > >Heh. Difficult when the system doesn't run. > > > > > > There is a bootable ISO version of memtest86 > that you could try. > > > > Thats what the port does.. It produces a bootable > floppy or ISO. > > This reminds me, I noticed that gentoo includes a > memtest86 "kernel" in > their install ISO. Would this be a hard feature to > include in FreeBSD? > > Mike > > ------------------------------ > > Message: 6 > Date: Thu, 31 Mar 2005 10:32:33 +0930 > From: "Daniel O'Connor" > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: freebsd-stable@freebsd.org > Cc: FreeBSD-amd64@freebsd.org > Message-ID: > <200503311032.33718.doconnor@gsoft.com.au> > Content-Type: text/plain; charset="utf-8" > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey > wrote: > > > Have you run sysutils/memtest86 with the 8 GB? > > > > Heh. Difficult when the system doesn't run. > > You could try http://www.memtest86.com although that > doesn't do >4Gb :( > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 > DC20 7B3F CE8C > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/b5b8ee65/attachment-0001.bin > > ------------------------------ > > Message: 7 > Date: Wed, 30 Mar 2005 17:10:10 -0800 > From: Steve Kargl > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Daniel O'Connor" > Cc: freebsd-stable@freebsd.org > Message-ID: > <20050331011010.GA6151@troutmask.apl.washington.edu> > Content-Type: text/plain; charset=us-ascii > > On Thu, Mar 31, 2005 at 10:32:33AM +0930, Daniel > O'Connor wrote: > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey > wrote: > > > > Have you run sysutils/memtest86 with the 8 GB? > > > > > > Heh. Difficult when the system doesn't run. > > > > You could try http://www.memtest86.com although > that doesn't do >4Gb :( > > > > http://www.memtest.org/ > > -- > Steve > > ------------------------------ > > Message: 8 > Date: Thu, 31 Mar 2005 10:49:38 +0930 > From: "Daniel O'Connor" > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Steve Kargl > Cc: freebsd-stable@freebsd.org > Message-ID: > <200503311049.38443.doconnor@gsoft.com.au> > Content-Type: text/plain; charset="iso-8859-1" > > On Thu, 31 Mar 2005 10:40, Steve Kargl wrote: > > On Thu, Mar 31, 2005 at 10:32:33AM +0930, Daniel > O'Connor wrote: > > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey > wrote: > > > > > Have you run sysutils/memtest86 with the 8 > GB? > > > > > > > > Heh. Difficult when the system doesn't run. > > > > > > You could try http://www.memtest86.com although > that doesn't do >4Gb :( > > > > http://www.memtest.org/ > > Ahh well there you go :) > Thanks! > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 > DC20 7B3F CE8C > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/d52257da/attachment-0001.bin > > ------------------------------ > > Message: 9 > Date: Wed, 30 Mar 2005 20:22:52 -0500 > From: Vivek Khera > Subject: Re: Tyan k8sr lockups > To: freebsd-amd64@freebsd.org > Message-ID: > <97964ce32490a368d64fa9b3500a8ba6@khera.org> > Content-Type: text/plain; charset=US-ASCII; > format=flowed > > > On Mar 29, 2005, at 7:39 PM, Sten Spans wrote: > > > There was an amr panic related to the management > ioctls > > which was fixed and backported to RELENG_5. You > should have > > this fix. amr controllers a supported quite well > on freebsd > > thanks to Scott's great work. > > > > Yes, that was part of the reason I cvsup'd again > last week... to ensure > I had the latest fixes to the amr driver. > > > The only way to get closer to solving these > problems > > is to dig and try to narrow it down: > > > > - Have you tried running with debugging ? > > any more than having the kernel debugger installed? > When the box > locked up I couldn't even drop into the kernel > debugger from the serial > console. neither the BREAK signal nor the alt key > sequence invoked it. > > > > > - Have you tried using other network cards ? > > ( yeah that sucks I know ) > > Nope. Machine is brand spanking new. Was in > service a whole of 5 days > before it locked up. The twin of this machine also > has issues with the > BIOS reporting "memory size changed" while the > machine is running... so > I'm a bit concerned that there is some generic > problem with the K8SR > and a megaraid controller. But that one never had > any complaints about > the ethernet, and the memory size error persisted > across two > motherboards. > > I have yet to try the other ethernet port on this > box as well. > > > > > - Are you absolutely sure that all the disks are > working ? > > ( there have been reports of amr cards acting > strange with > > silently failing disks ) > > The megaraid bios showed all disks as active. How > would one tell if > you had a silently failing disk? :-( > > > - Have you got the ufs fixes recently backported > to releng_5 ? > > If it was prior to March 22, then yes I have them. > Where in cvsweb > might I look to test? > > > These are the first I can think of. RELENG_5 seems > to be > > a bit of a moving target with some quite critical > fixes > > going in ( which is good offcourse :). > > Yes, it is good.... until you can't figure out if it > is your hardware > or software flaking out on ya... > > Thanks so much for responding. > > For price-no-object, which vendor would you choose > for an AMD system > today? Same question if price is somewhat of a > concern. Thanks. > > > ------------------------------ > > Message: 10 > Date: Thu, 31 Mar 2005 11:24:29 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Daniel O'Connor > Cc: freebsd-stable@freebsd.org > Message-ID: > <20050331015429.GH6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Thursday, 31 March 2005 at 10:32:33 +0930, Daniel > O'Connor wrote: > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey > wrote: > >>> Have you run sysutils/memtest86 with the 8 GB? > >> > >> Heh. Difficult when the system doesn't run. > > > > You could try http://www.memtest86.com although > that doesn't do >4Gb > :( > > I'm pretty sure it's not the memory. I've tried > each pair > individually, and it's only when they're both in > there together that > it's a problem. And yes, I've tried them in each > pair of slots. > > I now have dmesg output for verbose boots with both > 4 GB and 8 GB > memory. The complete dmesg output is at > http://www.lemis.com/grog/Images/20050331/dmesg.4GB > and > http://www.lemis.com/grog/Images/20050331/dmesg.8GB. > The diffs are at > http://www.lemis.com/grog/Images/20050331/dmesg.diff. > Here's a > truncated summary: > > > --- dmesg.4GB Thu Mar 31 10:47:16 2005 > > +++ dmesg.8GB Thu Mar 31 10:52:32 2005 > > @@ -64,6 +10,7 @@ > > SMAP type=01 base=0000000000100000 > len=00000000dfde0000 > > SMAP type=03 base=00000000dfee3000 > len=000000000000d000 > > SMAP type=04 base=00000000dfee0000 > len=0000000000003000 > > +SMAP type=01 base=0000000100000000 > len=0000000100000000 > > Copyright (c) 1992-2005 The FreeBSD Project. > > @@ -75,7 +22,7 @@ > > Calibrating clock(s) ... i8254 clock: 1193283 Hz > > CLK_USE_I8254_CALIBRATION not specified - using > default frequency > > Timecounter "i8254" frequency 1193182 Hz quality > 0 > > -Calibrating TSC clock ... TSC clock: 1603647337 > Hz > > +Calibrating TSC clock ... TSC clock: 1603647241 > Hz > > CPU: AMD Opteron(tm) Processor 242 (1603.65-MHz > K8-class CPU) > > Origin = "AuthenticAMD" Id = 0xf5a Stepping = > 10 > > > Features=0x78bfbff > > @@ -90,11 +37,12 @@ > > L2 4KB data TLB: 512 entries, 4-way associative > > L2 4KB instruction TLB: 512 entries, 4-way > associative > > L2 unified cache: 1024 kbytes, 64 bytes/line, 1 > lines/tag, 16-way associative > > -real memory = 3756916736 (3582 MB) > > +real memory = 8589934592 (8192 MB) > > This is interesting in that it has gained 4.5 GB. > > > Physical memory chunk(s): > > 0x0000000000001000 - 0x000000000009bfff, 634880 > bytes (155 pages) > > -0x0000000000a05000 - 0x00000000d95b7fff, > 3636146176 bytes (887731 pages) > > -avail memory = 3623817216 (3455 MB) > > +0x0000000000a09000 - 0x00000000dfedffff, > 3746394112 bytes (914647 pages) > > +0x0000000100000000 - 0x00000001f0fcffff, > 4043112448 bytes (987088 pages) > > +avail memory = 7777177600 (7416 MB) > > ACPI APIC Table: > > APIC ID: physical 0, logical 0:0 > > APIC ID: physical 1, logical 0:1 > > @@ -138,41 +86,12 @@ > > ioapic0: intpin 9 trigger: level > > ioapic0: intpin 9 polarity: low > > lapic0: Routing NMI -> LINT1 > > -A IRQ 3 (edge, high) > > -ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) > > -ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) > > -ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) > > -ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) > > -ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) > > -ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) > > -ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) > > -ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) > > -ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) > > -ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) > > -ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) > > -ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) > > -ioapic0: intpin 16 -> PCI IRQ 16 (level, low) > > -ioapic0: intpin 17 -> PCI IRQ 17 (level, low) > > -ioapic0: intpin 18 -> PCI IRQ 18 (level, low) > > -ioapic0: intpin 19 -> PCI IRQ 19 (level, low) > > -ioapic0: intpin 20 -> PCI IRQ 20 (level, low) > > -ioapic0: intpin 21 -> PCI IRQ 21 (level, low) > > -ioapic0: intpin 22 -> PCI IRQ 22 (level, low) > > -ioapic0: intpin 23 -> PCI IRQ 23 (level, low) > > -MADT: Interrupt override: source 0, irq 2 > > -ioapic0: Routing IRQ 0 -> intpin 2 > > -ioapic0: intpin 2 trigger: edge > > -ioapic0: intpin 2 polarity: high > > -MADT: Interrupt override: source 9, irq 9 > > -ioapic0: intpin 9 trigger: level > > -ioapic0: intpin 9 polarity: low > > -lapic0: Routing NMI -> LINT1 > > This stuff is puzzling. I suppose it could be > related. Does anybody > have any ideas? > > > lapic0: LINT1 trigger: edge > > lapic0: LINT1 polarity: high > > lapic1: Routing NMI -> LINT1 > > lapic1: LINT1 trigger: edge > > lapic1: LINT1 polarity: high > > -ioapic0 irqs 0-23 on motherboard > > +ioapic0 irqs 0-23 on motherboard > > cpu0 BSP: > > ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > > lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > > The last lines in the 8 GB dmesg are: > > > bge0: rev. 0x3003> mem 0xfa000000-0xfa00ffff irq 16 at > device 11.0 on pci0 > > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 > at 0xfa000000 > > They're identical in each probe. > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/ef36ee32/attachment-0001.bin > > ------------------------------ > > Message: 11 > Date: Thu, 31 Mar 2005 11:30:31 +0930 > From: "Daniel O'Connor" > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: freebsd-stable@FreeBSD.org > Message-ID: > <200503311130.39539.doconnor@gsoft.com.au> > Content-Type: text/plain; charset="utf-8" > > On Thu, 31 Mar 2005 11:24, Greg 'groggy' Lehey > wrote: > > I'm pretty sure it's not the memory. I've tried > each pair > > individually, and it's only when they're both in > there together that > > it's a problem. And yes, I've tried them in each > pair of slots. > > Could be a marginal timing issue.. You could try > winding out the RAM timing > slightly. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 > DC20 7B3F CE8C > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/77399356/attachment-0001.bin > > ------------------------------ > > Message: 12 > Date: Thu, 31 Mar 2005 05:54:17 +0200 > From: Matthias Buelow > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: Daniel O'Connor > Message-ID: > <20050331035417.GD10394@drjekyll.mkbuelow.net> > Content-Type: text/plain; charset=us-ascii > > Greg 'groggy' Lehey wrote: > > >I'm pretty sure it's not the memory. I've tried > each pair > >individually, and it's only when they're both in > there together that > >it's a problem. And yes, I've tried them in each > pair of slots. > > I'm sure you have checked this aswell but just for > completeness, > they aren't different pairs? Like one pair is > single-sided and the > other double-sided (had some nasty and obscure > problems with such > a combination myself)? > > mkb. > > > ------------------------------ > > Message: 13 > Date: Thu, 31 Mar 2005 12:56:43 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Matthias Buelow > Cc: Daniel O'Connor > Message-ID: > <20050331032643.GJ6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Thursday, 31 March 2005 at 5:54:17 +0200, > Matthias Buelow wrote: > > Greg 'groggy' Lehey wrote: > > > >> I'm pretty sure it's not the memory. I've tried > each pair > >> individually, and it's only when they're both in > there together that > >> it's a problem. And yes, I've tried them in each > pair of slots. > > > > I'm sure you have checked this aswell but just for > completeness, > > they aren't different pairs? Like one pair is > single-sided and the > > other double-sided (had some nasty and obscure > problems with such > > a combination myself)? > > No, they're all the same. > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/d100ba50/attachment-0001.bin > > ------------------------------ > > Message: 14 > Date: Wed, 30 Mar 2005 23:01:03 -0500 > From: John Baldwin > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: Daniel O'Connor > Message-ID: > <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> > Content-Type: text/plain; charset=US-ASCII; > format=flowed > > > On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey > wrote: > >> lapic0: LINT1 trigger: edge > >> lapic0: LINT1 polarity: high > >> lapic1: Routing NMI -> LINT1 > >> lapic1: LINT1 trigger: edge > >> lapic1: LINT1 polarity: high > >> -ioapic0 irqs 0-23 on motherboard > >> +ioapic0 irqs 0-23 on motherboard > >> cpu0 BSP: > >> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >> lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > > This shows that in the - case the APIC is broken > somehow (0.0 isn't a > valid I/O APIC version). It would seem that the > system has mapped RAM > over top of the I/O APIC perhaps? It would be > interesting to see the > contents of your MADT to see if it's trying to use a > 64-bit PA for your > APIC. The local APIC portion seems ok though. > > -- > > John Baldwin <>< > http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = > http://www.FreeBSD.org > > > ------------------------------ > > Message: 15 > Date: Thu, 31 Mar 2005 13:38:11 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: John Baldwin > Cc: Daniel O'Connor > Message-ID: > <20050331040811.GL6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Wednesday, 30 March 2005 at 23:01:03 -0500, John > Baldwin wrote: > > > > On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey > wrote: > >>> lapic0: LINT1 trigger: edge > >>> lapic0: LINT1 polarity: high > >>> lapic1: Routing NMI -> LINT1 > >>> lapic1: LINT1 trigger: edge > >>> lapic1: LINT1 polarity: high > >>> -ioapic0 irqs 0-23 on motherboard > >>> +ioapic0 irqs 0-23 on motherboard > >>> cpu0 BSP: > >>> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >>> lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > > > > This shows that in the - case the APIC is broken > somehow (0.0 isn't a > > valid I/O APIC version). > > You mean the + case, I suppose. Yes, that's what I > suspected. > > > It would seem that the system has mapped RAM over > top of the I/O > > APIC perhaps? > > That's what I suspected too, but imp doesn't think > so. > > > It would be interesting to see the contents of > your MADT to see if > > it's trying to use a 64-bit PA for your APIC. > > Any suggestions about how to do so? > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/51140500/attachment-0001.bin > > ------------------------------ > > Message: 16 > Date: Wed, 30 Mar 2005 21:28:36 -0700 > From: Scott Long > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: Daniel O'Connor > Message-ID: <424B7C74.4060203@samsco.org> > Content-Type: text/plain; charset=us-ascii; > format=flowed > > Greg 'groggy' Lehey wrote: > > On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > > > >>On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey > wrote: > >> > >>>>lapic0: LINT1 trigger: edge > >>>>lapic0: LINT1 polarity: high > >>>>lapic1: Routing NMI -> LINT1 > >>>>lapic1: LINT1 trigger: edge > >>>>lapic1: LINT1 polarity: high > >>>>-ioapic0 irqs 0-23 on motherboard > >>>>+ioapic0 irqs 0-23 on motherboard > >>>>cpu0 BSP: > >>>> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >>>> lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > >> > >>This shows that in the - case the APIC is broken > somehow (0.0 isn't a > >>valid I/O APIC version). > > > > > > You mean the + case, I suppose. Yes, that's what > I suspected. > > > > > >>It would seem that the system has mapped RAM over > top of the I/O > >>APIC perhaps? > > > > > > That's what I suspected too, but imp doesn't think > so. > > > > I'd be more inclined to believe that there is an > erroneous mapping by > the OS, not that things are fundamentally broken in > hardware. Your SMAP > table shows everything correctly. It's becoming > hard to break through > your pre-concieved notions here and explain how > things actually work. > > > > >>It would be interesting to see the contents of > your MADT to see if > >>it's trying to use a 64-bit PA for your APIC. > > > > > > Any suggestions about how to do so? > > > > man acpidump > > ------------------------------ > > Message: 17 > Date: Thu, 31 Mar 2005 14:44:58 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Scott Long > Cc: Daniel O'Connor > Message-ID: > <20050331051458.GM6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > [gratuitous empty lines removed] > > On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott > Long wrote: > > Greg 'groggy' Lehey wrote: > >> On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > >> > >>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey > wrote: > >>> > >>>>> lapic0: LINT1 trigger: edge > >>>>> lapic0: LINT1 polarity: high > >>>>> lapic1: Routing NMI -> LINT1 > >>>>> lapic1: LINT1 trigger: edge > >>>>> lapic1: LINT1 polarity: high > >>>>> -ioapic0 irqs 0-23 on > motherboard > >>>>> +ioapic0 irqs 0-23 on > motherboard > >>>>> cpu0 BSP: > >>>>> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > >>> > >>> This shows that in the - case the APIC is broken > somehow (0.0 isn't a > >>> valid I/O APIC version). > >> > >> You mean the + case, I suppose. Yes, that's what > I suspected. > >> > >>> It would seem that the system has mapped RAM > over top of the I/O > >>> APIC perhaps? > >> > >> That's what I suspected too, but imp doesn't > think so. > > > > I'd be more inclined to believe that there is an > erroneous mapping > > by the OS, not that things are fundamentally > broken in hardware. > > Agreed. This has been my favourite hypothesis all > along. But isn't > that what jhb is saying? > > > Your SMAP table shows everything correctly. It's > becoming hard to > > break through your pre-concieved notions here and > explain how things > > actually work. > > No, there's nothing to break through. I think > you're just having > problems > > 1. expressing yourself, and > 2. understanding what I'm saying. > > I have no preconceived notions. All I can see here > is an antagonistic > attitude on your part. What's the problem? You'll > recall from my > first message that I asked for suggestions about how > to approach the > issue. jhb provided some; you haven't so far. From > what you've > written, it's unclear whether you disagree with jhb > or not. If you > do, why? If you don't, what's your point here? > > >>> It would be interesting to see the contents of > your MADT to see if > >>> it's trying to use a 64-bit PA for your APIC. > >> > >> Any suggestions about how to do so? > > > > man acpidump > > How do you run that on a system that won't boot? > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/3878297d/attachment-0001.bin > > ------------------------------ > > Message: 18 > Date: Wed, 30 Mar 2005 23:28:52 -0600 > From: Jon Noack > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: freebsd-stable@FreeBSD.org > Message-ID: <424B8A94.5070300@alumni.rice.edu> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > > On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > >>Greg 'groggy' Lehey wrote: > >>>On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > >>>>On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey > wrote: > >>>>>>lapic0: LINT1 trigger: edge > >>>>>>lapic0: LINT1 polarity: high > >>>>>>lapic1: Routing NMI -> LINT1 > >>>>>>lapic1: LINT1 trigger: edge > >>>>>>lapic1: LINT1 polarity: high > >>>>>>-ioapic0 irqs 0-23 on > motherboard > >>>>>>+ioapic0 irqs 0-23 on > motherboard > >>>>>>cpu0 BSP: > >>>>>> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >>>>>>lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > >>>> > >>>>This shows that in the - case the APIC is broken > somehow (0.0 isn't a > >>>>valid I/O APIC version). > >>> > >>>You mean the + case, I suppose. Yes, that's what > I suspected. > >>> > >>> > >>>>It would seem that the system has mapped RAM > over top of the I/O > >>>>APIC perhaps? > >>> > >>>That's what I suspected too, but imp doesn't > think so. > >> > >>I'd be more inclined to believe that there is an > erroneous mapping > >>by the OS, not that things are fundamentally > broken in hardware. > > > > Agreed. This has been my favourite hypothesis all > along. But isn't > > that what jhb is saying? > > > >>Your SMAP table shows everything correctly. It's > becoming hard to > >>break through your pre-concieved notions here and > explain how things > >>actually work. > > > > No, there's nothing to break through. I think > you're just having > > problems > > > > 1. expressing yourself, and > > 2. understanding what I'm saying. > > > > I have no preconceived notions. All I can see > here is an antagonistic > > attitude on your part. What's the problem? > You'll recall from my > > first message that I asked for suggestions about > how to approach the > > issue. jhb provided some; you haven't so far. > From what you've > > written, it's unclear whether you disagree with > jhb or not. If you > > do, why? If you don't, what's your point here? > > > >>>>It would be interesting to see the contents of > your MADT to see if > >>>>it's trying to use a 64-bit PA for your APIC. > >>> > >>>Any suggestions about how to do so? > >> > >>man acpidump > > > > How do you run that on a system that won't boot? > > You said the system worked with 4 GB (albeit > detecting only 3.5 GB). My > perception of this whole ACPI thing is that it is > fixed in your BIOS > (although it can be overridden by the OS). As such, > the amount of RAM > you have in the machine shouldn't change acpidump > results. Is that not > correct? > > Jon > > ------------------------------ > > Message: 19 > Date: Wed, 30 Mar 2005 22:27:43 -0700 > From: Scott Long > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: noackjr@alumni.rice.edu > Cc: Greg 'groggy' Lehey > Message-ID: <424B8A4F.7050607@samsco.org> > Content-Type: text/plain; charset=us-ascii; > format=flowed > > Jon Noack wrote: > > On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > > > >> On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > >> > >>> Greg 'groggy' Lehey wrote: > >>> > >>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > >>>> > >>>>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' > Lehey wrote: > >>>>> > >>>>>>> lapic0: LINT1 trigger: edge > >>>>>>> lapic0: LINT1 polarity: high > >>>>>>> lapic1: Routing NMI -> LINT1 > >>>>>>> lapic1: LINT1 trigger: edge > >>>>>>> lapic1: LINT1 polarity: high > >>>>>>> -ioapic0 irqs 0-23 on > motherboard > >>>>>>> +ioapic0 irqs 0-23 on > motherboard > >>>>>>> cpu0 BSP: > >>>>>>> ID: 0x00000000 VER: 0x00040010 LDR: > 0x01000000 DFR: 0x0fffffff > >>>>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: > 0x00000000 SVR: 0x000001ff > >>>>> > >>>>> > >>>>> This shows that in the - case the APIC is > broken somehow (0.0 isn't a > >>>>> valid I/O APIC version). > >>>> > >>>> > >>>> You mean the + case, I suppose. Yes, that's > what I suspected. > >>>> > >>>> > >>>>> It would seem that the system has mapped RAM > over top of the I/O > >>>>> APIC perhaps? > >>>> > >>>> > >>>> That's what I suspected too, but imp doesn't > think so. > >>> > >>> > >>> I'd be more inclined to believe that there is an > erroneous mapping > >>> by the OS, not that things are fundamentally > broken in hardware. > >> > >> > >> Agreed. This has been my favourite hypothesis > all along. But isn't > >> that what jhb is saying? > >> > >>> Your SMAP table shows everything correctly. > It's becoming hard to > >>> break through your pre-concieved notions here > and explain how things > >>> actually work. > >> > >> > >> No, there's nothing to break through. I think > you're just having > >> problems > >> > >> 1. expressing yourself, and > >> 2. understanding what I'm saying. > >> > >> I have no preconceived notions. All I can see > here is an antagonistic > >> attitude on your part. What's the problem? > You'll recall from my > >> first message that I asked for suggestions about > how to approach the > >> issue. jhb provided some; you haven't so far. > From what you've > >> written, it's unclear whether you disagree with > jhb or not. If you > >> do, why? If you don't, what's your point here? > >> > >>>>> It would be interesting to see the contents of > your MADT to see if > >>>>> it's trying to use a 64-bit PA for your APIC. > >>>> > >>>> > >>>> Any suggestions about how to do so? > >>> > >>> > >>> man acpidump > >> > >> > >> How do you run that on a system that won't boot? > > > > > > You said the system worked with 4 GB (albeit > detecting only 3.5 GB). My > > perception of this whole ACPI thing is that it is > fixed in your BIOS > > (although it can be overridden by the OS). As > such, the amount of RAM > > you have in the machine shouldn't change acpidump > results. Is that not > > correct? > > > > Jon > > This is absolutely correct. > > Scott > > ------------------------------ > > Message: 20 > Date: Thu, 31 Mar 2005 00:32:35 -0500 > From: Sven Willenberger > Subject: Re: Tyan k8sr lockups > To: Vivek Khera > Cc: freebsd-amd64@freebsd.org > Message-ID: <424B8B73.8040100@dmv.com> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > > > Vivek Khera presumably uttered the following on > 03/30/05 20:22: > > > > On Mar 29, 2005, at 7:39 PM, Sten Spans wrote: > > > >> There was an amr panic related to the management > ioctls > >> which was fixed and backported to RELENG_5. You > should have > >> this fix. amr controllers a supported quite well > on freebsd > >> thanks to Scott's great work. > >> > > > > Yes, that was part of the reason I cvsup'd again > last week... to ensure > > I had the latest fixes to the amr driver. > > > >> The only way to get closer to solving these > problems > >> is to dig and try to narrow it down: > >> > >> - Have you tried running with debugging ? > > > > > > any more than having the kernel debugger > installed? When the box locked > > up I couldn't even drop into the kernel debugger > from the serial > > console. neither the BREAK signal nor the alt key > sequence invoked it. > > > >> > >> - Have you tried using other network cards ? > >> ( yeah that sucks I know ) > > > > > > Nope. Machine is brand spanking new. Was in > service a whole of 5 days > > before it locked up. The twin of this machine > also has issues with the > > BIOS reporting "memory size changed" while the > machine is running... so > > I'm a bit concerned that there is some generic > problem with the K8SR and > > a megaraid controller. But that one never had any > complaints about the > > ethernet, and the memory size error persisted > across two motherboards. > > > > I have yet to try the other ethernet port on this > box as well. > > > >> > >> - Are you absolutely sure that all the disks are > working ? > >> ( there have been reports of amr cards acting > strange with > >> silently failing disks ) > > > > > > The megaraid bios showed all disks as active. How > would one tell if you > > had a silently failing disk? :-( > > > >> - Have you got the ufs fixes recently backported > to releng_5 ? > > > > > > If it was prior to March 22, then yes I have them. > Where in cvsweb > > might I look to test? > > > >> These are the first I can think of. RELENG_5 > seems to be > >> a bit of a moving target with some quite critical > fixes > >> going in ( which is good offcourse :). > > > > > > Yes, it is good.... until you can't figure out if > it is your hardware or > > software flaking out on ya... > > > > Thanks so much for responding. > > > > For price-no-object, which vendor would you choose > for an AMD system > > today? Same question if price is somewhat of a > concern. Thanks. > > > > For a piece of anecdotal evidence we are running a > dual opteron k8s pro > with 8GB of RAM and the 320-2x Megaraid controller > (which controls all > the harddrives) Except for a problem with fxp (which > I haven't gone back > to reinvestigate but rather just used the Broadcom > gigE instead) the > system so far has run fairly stable (running > Postgres under a medium > load at the moment). We had one issue of a > "spontaneous" reboot that > left no indication of what happened in messages; > this box is still in > our testing area so it is possible that it was the > result of a > power[cord] issue. This is running 5.4-PRERELEASE > from 17 March. Also, > we disabled the onboard adaptec controllers in the > bios (as we don't use > them). > > Sven > > ------------------------------ > > Message: 21 > Date: Thu, 31 Mar 2005 15:19:11 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Scott Long > Cc: freebsd-stable@FreeBSD.org > Message-ID: > <20050331054911.GN6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott > Long wrote: > > Jon Noack wrote: > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > >>>> Greg 'groggy' Lehey wrote: > >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > >>>>>> It would be interesting to see the contents > of your MADT to see if > >>>>>> it's trying to use a 64-bit PA for your APIC. > >>>>> > >>>>> Any suggestions about how to do so? > >>>> > >>>> man acpidump > >>> > >>> How do you run that on a system that won't boot? > >> > >> You said the system worked with 4 GB (albeit > detecting only 3.5 > >> GB). > > Yes, this is correct. A number of people have > explained why it only > detected 3.5 GB in this configuration. > > >> My perception of this whole ACPI thing is that it > is fixed in your > >> BIOS (although it can be overridden by the OS). > As such, the > >> amount of RAM you have in the machine shouldn't > change acpidump > >> results. Is that not correct? > > > > This is absolutely correct. > > Ah, so you meant to say that the output from the > system running with 4 > GB memory is useful? That wasn't in the man page > you pointed to. > What it does say is: > > > When invoked with the -t flag, the acpidump > utility dumps contents of > > the following tables: > > > > ... MADT > > This may be the case, but between man page and > output some terminology > must have changed. I can't see any reference to > anything like an MADT > there. Does that mean that there isn't one, or that > ACPI can't find > it, or does the section APIC refer to/dump the MADT? > Here's the > complete output of acpidump -t, anyway: > > /* > RSD PTR: OEM=VIAK8, ACPI_Rev=1.0x (0) > RSDT=0xdfee3000, cksum=97 > */ > /* > RSDT: Length=44, Revision=1, Checksum=4, > OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM > Revision=0x42302e31, > Creator ID=AWRD, Creator Revision=0x0 > Entries={ 0xdfee3040, 0xdfee7b40 } > */ > /* > FACP: Length=116, Revision=1, Checksum=255, > OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM > Revision=0x42302e31, > Creator ID=AWRD, Creator Revision=0x0 > FACS=0xdfee0000, DSDT=0xdfee30c0 > INT_MODEL=PIC > Preferred_PM_Profile=Unspecified (0) > SCI_INT=9 > SMI_CMD=0x402f, ACPI_ENABLE=0xa1, > ACPI_DISABLE=0xa0, S4BIOS_REQ=0x0 > PSTATE_CNT=0x0 > PM1a_EVT_BLK=0x4000-0x4003 > PM1a_CNT_BLK=0x4004-0x4005 > PM_TMR_BLK=0x4008-0x400b > GPE0_BLK=0x4020-0x4023 > P_LVL2_LAT=101 us, P_LVL3_LAT=1001 us > FLUSH_SIZE=0, FLUSH_STRIDE=0 > DUTY_OFFSET=0, DUTY_WIDTH=1 > DAY_ALRM=125, MON_ALRM=126, CENTURY=50 > IAPC_BOOT_ARCH= > > Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,RESET_REG} > RESET_REG=0x00000000:0[0] (Memory), > RESET_VALUE=0x44 > */ > /* > FACS: Length=64, HwSig=0x00000000, > Firm_Wake_Vec=0x00000000 > Global_Lock= > Flags= > Version=0 > */ > /* > DSDT: Length=19020, Revision=1, Checksum=28, > OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM > Revision=0x1000, > Creator ID=MSFT, Creator Revision=0x100000e > */ > /* > APIC: Length=104, Revision=1, Checksum=145, > OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM > Revision=0x42302e31, > Creator ID=AWRD, Creator Revision=0x0 > Local APIC ADDR=0xfee00000 > Flags={PC-AT} > > Type=Local APIC > ACPI CPU=0 > Flags={ENABLED} > APIC ID=0 > > Type=Local APIC > ACPI CPU=1 > Flags={ENABLED} > APIC ID=1 > > Type=IO APIC > APIC ID=2 > INT BASE=0 > ADDR=0x00000000fec00000 > > Type=INT Override > BUS=0 > IRQ=0 > INTR=2 > Flags={Polarity=conforming, > Trigger=conforming} > > Type=INT Override > BUS=0 > IRQ=9 > INTR=9 > Flags={Polarity=active-lo, Trigger=level} > > Type=Local NMI > ACPI CPU=0 > LINT Pin=1 > Flags={Polarity=active-hi, Trigger=edge} > > Type=Local NMI > ACPI CPU=1 > LINT Pin=1 > Flags={Polarity=active-hi, Trigger=edge} > */ > > Since I don't know anything about ACPI, this doesn't > say too much to > me. Suggestions welcome. If the APIC section is > the MADT, it looks > as if we should update the docco. > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/3d97eaaa/attachment-0001.bin > > ------------------------------ > > Message: 22 > Date: Thu, 31 Mar 2005 00:00:22 -0600 > From: Jon Noack > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: "Greg 'groggy' Lehey" > Cc: freebsd-stable@FreeBSD.org > Message-ID: <424B91F6.4000400@alumni.rice.edu> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > On 03/30/05 23:49, Greg 'groggy' Lehey wrote: > > On Wednesday, 30 March 2005 at 22:27:43 -0700, > Scott Long wrote: > >>Jon Noack wrote: > >>>On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >>>>On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > >>>>>Greg 'groggy' Lehey wrote: > >>>>>>On Wednesday, 30 March 2005 at 23:01:03 -0500, > John Baldwin wrote: > >>>>>>>It would be interesting to see the contents > of your MADT to see if > >>>>>>>it's trying to use a 64-bit PA for your APIC. > >>>>>> > >>>>>>Any suggestions about how to do so? > >>>>> > >>>>>man acpidump > >>>> > >>>>How do you run that on a system that won't boot? > >>> > >>>You said the system worked with 4 GB (albeit > detecting only 3.5 > >>>GB). > > > > Yes, this is correct. A number of people have > explained why it only > > detected 3.5 GB in this configuration. > > > >>>My perception of this whole ACPI thing is that it > is fixed in your > >>>BIOS (although it can be overridden by the OS). > As such, the > >>>amount of RAM you have in the machine shouldn't > change acpidump > >>>results. Is that not correct? > >> > >>This is absolutely correct. > > > > Ah, so you meant to say that the output from the > system running with 4 > > GB memory is useful? That wasn't in the man page > you pointed to. > > What it does say is: > > > >>When invoked with the -t flag, the acpidump > utility dumps contents of > >>the following tables: > >> > >>... MADT > > > > This may be the case, but between man page and > output some terminology > > must have changed. I can't see any reference to > anything like an MADT > > there. Does that mean that there isn't one, or > that ACPI can't find > > it, or does the section APIC refer to/dump the > MADT? Here's the > > complete output of acpidump -t, anyway: > > > > > > > > Since I don't know anything about ACPI, this > doesn't say too much to > > me. Suggestions welcome. If the APIC section is > the MADT, it looks > > as if we should update the docco. > > My limited research (as in, Google) shows that the > MADT was defined as > part of ACPI 2.0: > http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx > > According to your previous link the motherboard > specs, it supports both > ACPI 1.0A and 2.0. Perhaps there is a BIOS knob to > toggle between the two? > > Jon > > ------------------------------ > > Message: 23 > Date: Thu, 31 Mar 2005 01:15:28 -0500 > From: Damian Gerow > Subject: Re: [OT] memtest86 (Was: Problems with > AMD64 and 8 GB RAM?) > To: freebsd-amd64@freebsd.org > Message-ID: <20050331061527.GF701@afflictions.org> > Content-Type: text/plain; charset=us-ascii > > Thus spake Mike Hunter (mhunter@ack.Berkeley.EDU) > [30/03/05 18:46]: > : This reminds me, I noticed that gentoo includes a > memtest86 "kernel" in > : their install ISO. Would this be a hard feature > to include in FreeBSD? > > In the case of AMD64, it'd be almost pointless. > I've not yet been able to > run a copy of memtest86 on my machine (though it > could have been due to > memory problems at the time). > > memtest86+[1] works great, though. It's a fork from > memtest86. > > [1] http://www.memtest.org/ > > ------------------------------ > > Message: 24 > Date: Thu, 31 Mar 2005 15:48:11 +0930 > From: Greg 'groggy' Lehey > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: Jon Noack > Cc: freebsd-stable@FreeBSD.org > Message-ID: > <20050331061811.GQ6252@wantadilla.lemis.com> > Content-Type: text/plain; charset="us-ascii" > > On Thursday, 31 March 2005 at 0:00:22 -0600, Jon > Noack wrote: > > On 03/30/05 23:49, Greg 'groggy' Lehey wrote: > >> Here's the complete output of acpidump -t, > anyway: > >> > >> > >> > >> Since I don't know anything about ACPI, this > doesn't say too much to > >> me. Suggestions welcome. If the APIC section is > the MADT, it looks > >> as if we should update the docco. > > > > My limited research (as in, Google) shows that the > MADT was defined as > > part of ACPI 2.0: > > > http://www.microsoft.com/whdc/system/platform/64bit/IA64_ACPI.mspx > > Thanks for the link. > > > According to your previous link the motherboard > specs, it supports > > both ACPI 1.0A and 2.0. Perhaps there is a BIOS > knob to toggle > > between the two? > > I've taken a look, but I can't find anything. > > Greg > -- > See complete headers for address and phone numbers. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/bab59d62/attachment-0001.bin > > ------------------------------ > > Message: 25 > Date: Thu, 31 Mar 2005 00:30:56 -0800 > From: Peter Wemm > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: freebsd-amd64@freebsd.org > Cc: freebsd-stable@freebsd.org > Message-ID: <200503310030.57519.peter@wemm.org> > Content-Type: text/plain; charset="iso-8859-1" > > On Wednesday 30 March 2005 09:49 pm, Greg 'groggy' > Lehey wrote: > > On Wednesday, 30 March 2005 at 22:27:43 -0700, > Scott Long wrote: > > > Jon Noack wrote: > > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > > >>>> Greg 'groggy' Lehey wrote: > > >>>>> On Wednesday, 30 March 2005 at 23:01:03 > -0500, John Baldwin wrote: > > >>>>>> It would be interesting to see the contents > of your MADT to see if > > >>>>>> it's trying to use a 64-bit PA for your > APIC. > > >>>>> > > >>>>> Any suggestions about how to do so? > > >>>> > > >>>> man acpidump > > >>> > > >>> How do you run that on a system that won't > boot? > > >> > > >> You said the system worked with 4 GB (albeit > detecting only 3.5 > > >> GB). > > > > Yes, this is correct. A number of people have > explained why it only > > detected 3.5 GB in this configuration. > > > > You're also being confused by the implementation of > the 'real memory' report. > If you take a 30 second glance at the code, you'll > see that it is reporting > the same units that the hw.maxmem tunable uses. ie: > it is the LIMIT or > Highest Address that the system has, not the sum > total of all the parts. > > eg: see the machdep.c comment next to the printf > * Maxmem isn't the "maximum memory", it's > one larger than the > * highest page of the physical address > space. It should be > * called something like "Maxphyspage". We > may adjust this > * based on ``hw.physmem'' and the results > of the memory test. > > The SMAP lines are what you need to pay attention > to. In the output you > posted with 8G, you can see the 4GB going from the > 4->8GB range, exactly. > SMAP type 1 is "usable memory". > > -Peter > > ------------------------------ > > Message: 26 > Date: Thu, 31 Mar 2005 12:28:46 +0300 > From: Patrik Backlund > Subject: Re: Asus K8S-MX > To: freebsd-amd64@freebsd.org > Message-ID: <20050331092846.GA30291@backi.iki.fi> > Content-Type: text/plain; charset=iso-8859-1 > > On Wed, Feb 16, 2005 at 09:40:31AM -0800, David > O'Brien wrote: > > On Wed, Feb 16, 2005 at 11:44:18AM +0000, Joseph > Koshy wrote: > > > > There are also SiS and ALi based motherboards. > I haven't heard of any > > > > problems with them. > > > > > > I tried FreeBSD on an ASUS K8S-MX which is based > on the SiS > > > SiS760GX and 965L chipsets. Our ATA driver had > problems with > > > UDMA modes with the 965 chipset; it only worked > in PIO4 mode. > > > > Can you try ATA-mkIII? > > Otherwise can you report the issue to Soren? > > Søren has now committed the necessary device ids for > this board to work in > current. I've applied his ata patches to my RELENG_5 > and at least the SATA > part works just fine. > > See kern/70296 for a one line patch to get the > on-board sound working. > > -Patrik > > ------------------------------ > > Message: 27 > Date: Thu, 31 Mar 2005 12:16:29 +0200 > From: Ulrik Guenther > Subject: Re: Cross-compiling/porting to Linux > To: Michael Hopkins > > Cc: "freebsd-amd64@freebsd.org" > > Message-ID: <424BCDFD.8050701@00t.org> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > Hi Michael, > > the following commands have to be issued for correct > installation of the > packages: > mkdir /compat/linux > cd /compat/linux > tar xvpzf /somewhere/aaa_base-10.0.0-noarch-1.tgz > sh install/doinst.sh > rmdir dev home root tmp var/tmp > tar xvpzf /somewhere/aaa_elflibs-9.2.0-i486-1.tgz > sh install/doinst.sh > tar xvpzf /somewhere/glibc-solibs-2.3.2-i486-6.tgz > !!! sed -e 's,/sbin/ldconfig,/nonexistent,g' -e > 's,cp -a,cp -p,g' -i '' > install/doinst.sh > sh install/doinst.sh > tar xvpzf /somewhere/x11-6.7.0-i486-4.tgz > sh install/doinst.sh > echo '/usr/X11R6/lib' >etc/ld.so.conf > brandelf -t Linux sbin/ldconfig > sbin/ldconfig > > The sed command (before which I put the three !) is > of utmost > importance, otherwise one *will* get the error you > got. > If you have done all correctly, just try it again, > it's a bit tricky. > I already used this procedure on about three > installations (two i386 and > one amd64) and for me it works better than the > redhat rpms from the > ports. But I have to say that I had the same problem > like you once, I > think it was on the amd64 machine, I tried it again > and it worked very > well. Have you used Slackware 10 or 10.1 by the way? > > Have fun ;) > > Ulrik > Michael Hopkins wrote: > > Hmmm... > > > > All Linux commands fail with this :o{ > > > > root@Athlon /usr/compat/linux/usr/bin # ./gcc -v > > > > ELF interpreter /lib/ld-linux.so.2 not found > > Abort trap > > > > > > I wonder if this is to do with the error message I > got when running this at > > the end of section 2? > > > > sbin/ldconfig > > > > M > > > > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > > > _/ _/ _/_/_/ Hopkins > Research Ltd > > _/ _/ _/ _/ > > _/_/_/_/ _/_/_/ > http://www.hopkins-research.com/ > > _/ _/ _/ _/ > > _/ _/ _/ _/ 'touch the > future' > > > > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > > > > > > ------------------------------ > > Message: 28 > Date: Thu, 31 Mar 2005 03:04:34 -0800 > From: ray@redshift.com > Subject: AMD64 kernel config file question > To: freebsd-amd64@freebsd.org > Message-ID: > <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > I'm setting up FreeBSD 5.3 for the first time on > an Tyan dual opteron board. > I've done plenty of i386 installs, but this is the > first on AMD. Anyway, I'm > stripping down the kernel for a re-compile and I was > wondering if anyone either > had a sample config file they could send over and/or > if someone could let me > know what they are running for these lines? > > For the CPU/machine stuff, does this look okay (i.e. > is K8 the correct option > for the Opteron 246's?) > > machine amd64 > cpu K8 > ident AMD64 > > And for dual CPU's, I use this on i386 - is it the > same for AMD? > > # To make an SMP kernel, the next two are needed > options SMP # Symmetric > MultiProcessor Kernel > device apic # I/O APIC > > Thanks! > > Ray > > > ------------------------------ > > Message: 29 > Date: Thu, 31 Mar 2005 12:14:47 +0100 > From: Michael Hopkins > > Subject: Working and broken Linux ports on amd64 > To: "freebsd-amd64@freebsd.org" > , > , > , > > Message-ID: > > Content-Type: text/plain; charset="US-ASCII" > > > > Hi all > > I have been installing a few Linux environments from > the ports in the last > few days to try and establish a cross-compiler for > 32-bit Linux on amd64 > (see my other post for the story so far). > > I thought it might be useful for others on this path > to be told about what > works and what doesn't. System is: > > root@Athlon ~ # uname -a > FreeBSD Athlon 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 > #2: Wed Mar 30 01:46:52 > BST 2005 root@Athlon:/usr/obj/usr/src/sys/ATHLON > amd64 > > > First steps > ----------- > First of all, I believe you need to do this as > pointed out by Axel Gonzalez. > > Add these to the kernel and rebuild: > > options LINPROCFS > options COMPAT_43 > options COMPAT_LINUX32 > > and on rc.conf: > > linux_enable="YES" > > > Working > ------- > linux_base-8 (redhat 8) > linux_base-suse (suse 9.2) > linux_base-debian (debian woody) > > All installed OK and gave correct answers to > /compat/linux/bin/uname -a > > > emulators/linux_base-gentoo-stage1 > ---------------------------------- > Starting Terminal in > /usr/ports/emulators/linux_base-gentoo-stage1... > > bash-2.05b# make > ===> linux_base-gentoo-stage1-2004.3 is marked as > broken: Incorrect > pkg-plist. > > > devel/linux_devtools-7 > ---------------------- > Starting Terminal in > /usr/ports/devel/linux_devtools-7... > > bash-2.05b# make > ===> linux_devtools-7.1_3 is marked as broken: > Incomplete pkg-plist. > > > emulators/linux_base-rh-9 > ------------------------- > Makes OK but fails on install with a message > something like "script error > for glibc-..." - sorry I didn't copy output so > that's from memory. > > > Slackware 10.1 > -------------- > I also followed the instructions from here to try > slackware which was > suggested by Ulrik Guenther > > http://people.freebsd.org/~tjr/linux32.html > > Unfortunately the install process didn't happen > exactly like on the page: > > # sbin/ldconfig > sbin/ldconfig: Can't open configuration file > /etc/ld.so.conf: No such file > or directory > > And all Linux commands gave this error: > > # ./gcc -v > ELF interpreter /lib/ld-linux.so.2 not found > Abort trap > > Ulrik has just sent me some more detailed > instructions, so I may give this > another go. > > mkdir /compat/linux > cd /compat/linux > tar xvpzf /somewhere/aaa_base-10.0.0-noarch-1.tgz > sh install/doinst.sh > rmdir dev home root tmp var/tmp > tar xvpzf /somewhere/aaa_elflibs-9.2.0-i486-1.tgz > sh install/doinst.sh > tar xvpzf /somewhere/glibc-solibs-2.3.2-i486-6.tgz > sed -e 's,/sbin/ldconfig,/nonexistent,g' -e 's,cp > -a,cp -p,g' -i '' > install/doinst.sh > sh install/doinst.sh > tar xvpzf /somewhere/x11-6.7.0-i486-4.tgz > sh install/doinst.sh > echo '/usr/X11R6/lib' >etc/ld.so.conf > brandelf -t Linux sbin/ldconfig > sbin/ldconfig > > > In general > ---------- > A lot of Linux ports are giving this message which I > suspect may not always > be appropriate: > > ...is only for i386, and you are running amd64. > > > hth > > Michael > > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > _/ _/ _/_/_/ Hopkins > Research Ltd > _/ _/ _/ _/ > _/_/_/_/ _/_/_/ > http://www.hopkins-research.com/ > _/ _/ _/ _/ > _/ _/ _/ _/ 'touch the > future' > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > > > > ------------------------------ > > Message: 30 > Date: Thu, 31 Mar 2005 13:14:55 +0200 > From: Marc Olzheim > Subject: Re: AMD64 kernel config file question > To: ray@redshift.com > Cc: freebsd-amd64@freebsd.org > Message-ID: <20050331111455.GC34216@stack.nl> > Content-Type: text/plain; charset="us-ascii" > > On Thu, Mar 31, 2005 at 03:04:34AM -0800, > ray@redshift.com wrote: > > Hi, > > > > I'm setting up FreeBSD 5.3 for the first time on > an Tyan dual opteron board. > > I've done plenty of i386 installs, but this is the > first on AMD. Anyway, I'm > > stripping down the kernel for a re-compile and I > was wondering if anyone either > > had a sample config file they could send over > and/or if someone could let me > > know what they are running for these lines? > > See /usr/src/sys/amd64/conf/* (GENERIC for instance) > > Use "cpu HAMMER" > > Marc > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050331/57577e4a/attachment.bin > > ------------------------------ > > Message: 31 > Date: Thu, 31 Mar 2005 00:30:56 -0800 > From: Peter Wemm > Subject: Re: Problems with AMD64 and 8 GB RAM? > To: freebsd-amd64@freebsd.org > Cc: freebsd-stable@freebsd.org > Message-ID: <200503310030.57519.peter@wemm.org> > Content-Type: text/plain; charset="iso-8859-1" > > On Wednesday 30 March 2005 09:49 pm, Greg 'groggy' > Lehey wrote: > > On Wednesday, 30 March 2005 at 22:27:43 -0700, > Scott Long wrote: > > > Jon Noack wrote: > > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, > Scott Long wrote: > > >>>> Greg 'groggy' Lehey wrote: > > >>>>> On Wednesday, 30 March 2005 at 23:01:03 > -0500, John Baldwin wrote: > > >>>>>> It would be interesting to see the contents > of your MADT to see if > > >>>>>> it's trying to use a 64-bit PA for your > APIC. > > >>>>> > > >>>>> Any suggestions about how to do so? > > >>>> > > >>>> man acpidump > > >>> > > >>> How do you run that on a system that won't > boot? > > >> > > >> You said the system worked with 4 GB (albeit > detecting only 3.5 > > >> GB). > > > > Yes, this is correct. A number of people have > explained why it only > > detected 3.5 GB in this configuration. > > > > You're also being confused by the implementation of > the 'real memory' report. > If you take a 30 second glance at the code, you'll > see that it is reporting > the same units that the hw.maxmem tunable uses. ie: > it is the LIMIT or > Highest Address that the system has, not the sum > total of all the parts. > > eg: see the machdep.c comment next to the printf > * Maxmem isn't the "maximum memory", it's > one larger than the > * highest page of the physical address > space. It should be > * called something like "Maxphyspage". We > may adjust this > * based on ``hw.physmem'' and the results > of the memory test. > > The SMAP lines are what you need to pay attention > to. In the output you > posted with 8G, you can see the 4GB going from the > 4->8GB range, exactly. > SMAP type 1 is "usable memory". > > -Peter > > ------------------------------ > > _______________________________________________ > 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" > > > End of freebsd-amd64 Digest, Vol 95, Issue 5 > ******************************************** > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:07:26 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C763716A4CE for ; Thu, 31 Mar 2005 18:07:26 +0000 (GMT) Received: from ipe.cnpm.embrapa.br (ipe.cnpm.embrapa.br [200.136.111.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6D143D2F for ; Thu, 31 Mar 2005 18:07:20 +0000 (GMT) (envelope-from pan@cnpm.embrapa.br) Received: from localhost (localhost.cnpm.embrapa.br [127.0.0.1]) by ipe.cnpm.embrapa.br (Postfix) with ESMTP id 19C1784499 for ; Thu, 31 Mar 2005 15:07:18 -0300 (BRT) Received: from [200.136.111.44] (oliveira.cnpm.embrapa.br [200.136.111.44]) by ipe.cnpm.embrapa.br (Postfix) with ESMTP id 7B3168447D for ; Thu, 31 Mar 2005 15:07:16 -0300 (BRT) Message-ID: <424C3C98.30602@cnpm.embrapa.br> Date: Thu, 31 Mar 2005 15:08:24 -0300 From: "Carlos F. A. Paniago" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050328) X-Accept-Language: pt-br, pt MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd 0.1 Subject: fstatfs break in amd64 ia32 emulation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:07:26 -0000 hi: I'm tring to compile in an amd64 and running in an i386.. I read in the list that is not possible, but some things work if we compile using: gcc -Di386 -D__i386__ -Uamd64 -U__amd64__ -m32 -B/lib32 -B/usr/lib32 -g -o test-i386.amd test-i386.c some simple program could be compiled in an amd64 machine and run in a i386 machine. but this program don't work: -- #include #include #include #include int main(int argc, char** argv) { struct statfs buf; if (fstatfs(0, &buf) < 0) { perror("fstatfs"); } printf("%d %d\n", sizeof(buf), sizeof(&buf)); return 0; } -- the result is: --- ipe# ./test-i386 472 4 ipe# ./test-i386.amd 384 4 Segmentation fault (core dumped) ipe# --- this ipe machine is an i386 machine... the ./test-i386 is compiled in this machine as gcc -g -o test-i386 test-i386.c and the ./test-i386.amd is compiled in an amd64 using: gcc -Di386 -D__i386__ -Uamd64 -U__amd64__ -m32 -B/lib32 -B/usr/lib32 -g -o test-i386.amd test-i386.c The strange thing is the size of struct statfs that changes... If I compile this in an amd64 machine (oliveira is an amd64 machine) --- oliveira: {248} gcc -g -o test-i386.amd test-i386.c oliveira: {249} ./test-i386.amd 472 8 oliveira: {250} --- strange the size of the struct is the same as in i386 and the size of the pointer is 8 (instead of 4), but in the compilation using the -m32 the sizeof is strange... Someone know how to solve this problem??? Paniago -- Nome: Carlos Fernando Assis Paniago Email: pan@cnpm.embrapa.br Fone: +55 (19) 3256-60-30 Web: http://www.cnpm.embrapa.br/ Fax: +55 (19) 3254-11-00 -- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:38:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA01816A4CE for ; Thu, 31 Mar 2005 18:38:39 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854F843D31 for ; Thu, 31 Mar 2005 18:38:39 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j2VIcYT01628; Thu, 31 Mar 2005 10:38:34 -0800 (PST) Date: Thu, 31 Mar 2005 10:38:34 -0800 From: Mike Hunter To: ray@redshift.com Message-ID: <20050331183834.GA1119@ack.Berkeley.EDU> References: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.1.32.20050331030434.00a8f798@pop.redshift.com> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 kernel config file question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:38:39 -0000 On Mar 31, "ray@redshift.com" wrote: > Hi, > > I'm setting up FreeBSD 5.3 for the first time on an Tyan dual opteron board. > I've done plenty of i386 installs, but this is the first on AMD. Anyway, I'm > stripping down the kernel for a re-compile and I was wondering if anyone either > had a sample config file they could send over and/or if someone could let me > know what they are running for these lines? > > For the CPU/machine stuff, does this look okay (i.e. is K8 the correct option > for the Opteron 246's?) > > machine amd64 > cpu K8 > ident AMD64 > > And for dual CPU's, I use this on i386 - is it the same for AMD? > > # To make an SMP kernel, the next two are needed > options SMP # Symmetric MultiProcessor Kernel > device apic # I/O APIC I wrote to the list a few months ago about apic: apic is implicit for the AMD64 arch. It was incorrectly carried over to the config and doc files from x86. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=125292+0+archive/2004/freebsd-amd64/20041212.freebsd-amd64 Mike From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:42:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1962616A4CE; Thu, 31 Mar 2005 18:42:35 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9FD943D60; Thu, 31 Mar 2005 18:42:34 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIgY3K001753; Thu, 31 Mar 2005 10:42:34 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIgYXQ001752; Thu, 31 Mar 2005 10:42:34 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:42:34 -0800 From: "David O'Brien" To: "Greg 'groggy' Lehey" Message-ID: <20050331184234.GA1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050330222439.GU84137@wantadilla.lemis.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:42:35 -0000 On Thu, Mar 31, 2005 at 07:54:39AM +0930, Greg 'groggy' Lehey wrote: > I've recently acquired an AMD64 box (dual Opteron 242, SiS Master@-FAR > motherboard > (http://www.msi.com.tw/program/products/server/svr/pro_svr_detail.php?UID=484). > See below for more details). I find it very unstable running with 8 > GB memory, though 4 GB are not a problem. Exactly what is the OPN (first line on the CPU's that includes the model number)? Exactly what DIMM's are you using? Make + part number. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:45:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C8E816A4CE; Thu, 31 Mar 2005 18:45:25 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6143E43D70; Thu, 31 Mar 2005 18:45:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIjObD001820; Thu, 31 Mar 2005 10:45:25 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIjOSu001819; Thu, 31 Mar 2005 10:45:24 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:45:24 -0800 From: "David O'Brien" To: Peter Wemm Message-ID: <20050331184524.GB1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <424B308C.7070506@samsco.org> <20050330230951.GY84137@wantadilla.lemis.com> <200503301525.37798.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503301525.37798.peter@wemm.org> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: FreeBSD Stable Users cc: freebsd-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:45:25 -0000 On Wed, Mar 30, 2005 at 03:25:37PM -0800, Peter Wemm wrote: > Greg: The busdma problems from 5.3-RELEASE are fixed. That doesn't > mean that there are no *other* problems. Scott is saying "the old > busdma bug shouldn't be affecting 5.4-PRE", and he's correct. > > Most likely, something else is happening, eg: you're running out of KVM > or something silly like that. I know we're right on the brink at 8GB. > The layout of the devices may be just enough to tip it over the edge. Grog's motherboard is a 4+0 configuration -- which would mean he is using (trying to) 2GB DIMM's. There are memory bus loading specifictions he may be out of spec of. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:47:33 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 931FC16A4CE; Thu, 31 Mar 2005 18:47:33 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5077E43D3F; Thu, 31 Mar 2005 18:47:33 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIlXkE001848; Thu, 31 Mar 2005 10:47:33 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIlXSK001847; Thu, 31 Mar 2005 10:47:33 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:47:33 -0800 From: "David O'Brien" To: "Greg 'groggy' Lehey" Message-ID: <20050331184733.GC1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050330224445.GW84137@wantadilla.lemis.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: FreeBSD Stable Users cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD Stable Users , FreeBSD-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:47:33 -0000 On Thu, Mar 31, 2005 at 08:14:45AM +0930, Greg 'groggy' Lehey wrote: > > I had 4 bad out of 12 tested where the DIMMs were Crucial PC2700 2GB > > Reg. ECC DIMMs. > > OK, this makes sense. It might also explain why the 4 GB > configuration only recognizes 3.5 GB. No. This is due to the 3.5-4.0GB PA address range that the PeeCee architecture reserves for the PCI config space, AGP GART, memory mapped I/O, etc... Many Opteron BIOS's don't bother to hoist the "covered" memory above 4GB. Please see the freebsd-amd64 archives -- this has been discussed many times. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:53:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B911416A4CE for ; Thu, 31 Mar 2005 18:53:04 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 765CE43D45 for ; Thu, 31 Mar 2005 18:53:04 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIr4E5001920 for ; Thu, 31 Mar 2005 10:53:04 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIr4n0001919 for freebsd-amd64@freebsd.org; Thu, 31 Mar 2005 10:53:04 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:53:04 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20050331185304.GD1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330224445.GW84137@wantadilla.lemis.com> <1616-SnapperMsg8FB730CABE70E540@[10.178.116.227]> <200503301527.28612.peter@wemm.org> <20050330234603.GA18631@ack.Berkeley.EDU> <20050331061527.GF701@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050331061527.GF701@afflictions.org> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Subject: Re: [OT] memtest86 (Was: Problems with AMD64 and 8 GB RAM?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:53:04 -0000 On Thu, Mar 31, 2005 at 01:15:28AM -0500, Damian Gerow wrote: > Thus spake Mike Hunter (mhunter@ack.Berkeley.EDU) [30/03/05 18:46]: > : This reminds me, I noticed that gentoo includes a memtest86 "kernel" in > : their install ISO. Would this be a hard feature to include in FreeBSD? > > In the case of AMD64, it'd be almost pointless. I've not yet been able to > run a copy of memtest86 on my machine (though it could have been due to > memory problems at the time). > > memtest86+ (http://www.memtest.org/) works great, though. It's a fork > from memtest86. FEH! memtest86+ can be crap. Version 1.30 had a very bad bug where it would report all memory above 4GB on Opteron systems as bad. I replaced a motherboard and a complete set of 8x1GB DIMM's because of it. Very unfortunately for me 1.30 was the latest version when FreeBSD/amd64 had the busdma bug that would corrumpt data. (thus why I was bothering to test my memory). Anyone using memtest86+ on AMD64 should make sure they have version 1.40. memtest86 (the original) versions below 3.2 had fatal bugs on AMD64 CPU's also. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:54:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C874A16A4CE; Thu, 31 Mar 2005 18:54:16 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9719543D39; Thu, 31 Mar 2005 18:54:16 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIsF3D001972; Thu, 31 Mar 2005 10:54:16 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIsEdI001967; Thu, 31 Mar 2005 10:54:14 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:54:14 -0800 From: "David O'Brien" To: "Daniel O'Connor" Message-ID: <20050331185414.GE1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503311032.33718.doconnor@gsoft.com.au> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-stable@freebsd.org cc: FreeBSD-amd64@freebsd.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org, FreeBSD-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:54:16 -0000 On Thu, Mar 31, 2005 at 10:32:33AM +0930, Daniel O'Connor wrote: > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: > > > Have you run sysutils/memtest86 with the 8 GB? > > > > Heh. Difficult when the system doesn't run. > > You could try http://www.memtest86.com although that doesn't do >4Gb :( Are you sure version 3.2 does not? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 18:59:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF16B16A4CE; Thu, 31 Mar 2005 18:59:02 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AE7743D58; Thu, 31 Mar 2005 18:59:02 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VIx2xl002075; Thu, 31 Mar 2005 10:59:02 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VIx28q002074; Thu, 31 Mar 2005 10:59:02 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 10:59:02 -0800 From: "David O'Brien" To: "Greg 'groggy' Lehey" Message-ID: <20050331185902.GF1687@dragon.NUXI.org> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050331015429.GH6252@wantadilla.lemis.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.org, FreeBSD-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 18:59:03 -0000 On Thu, Mar 31, 2005 at 11:24:29AM +0930, Greg 'groggy' Lehey wrote: > On Thursday, 31 March 2005 at 10:32:33 +0930, Daniel O'Connor wrote: > > On Thu, 31 Mar 2005 08:14, Greg 'groggy' Lehey wrote: > >>> Have you run sysutils/memtest86 with the 8 GB? > >> > >> Heh. Difficult when the system doesn't run. > > > > You could try http://www.memtest86.com although that doesn't do >4Gb > :( > > I'm pretty sure it's not the memory. I've tried each pair > individually, and it's only when they're both in there together that > it's a problem. And yes, I've tried them in each pair of slots. You have a dual-channel memory controller. If you insert one DIMM you perform 64-bit data accesses. If you install DIMM's in pairs (making sure you're using the right "paired" sockets), you perform 128-bit data accesses. Thus your access pattern is different between these two situations. I'm highly suspious that you can us 4x2GB DIMM's with out knowing the exact part number. Don't forget 2GB DIMM's are double-stacked and thus look like double the electrical bus loads. The same is true for older 1GB DIMM's. Install all the memory you would like to use into your motherboard, download memtest86+ version 1.40 from http://www.memtest.org, dd to floppy or burn the ISO, and report back your findings from running it. Also what version of the BIOS are you using? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 19:07:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4646516A4CE; Thu, 31 Mar 2005 19:07:04 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E230543D1D; Thu, 31 Mar 2005 19:07:03 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VJ72dC002257; Thu, 31 Mar 2005 11:07:03 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VJ722Z002256; Thu, 31 Mar 2005 11:07:02 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 11:07:02 -0800 From: "David O'Brien" To: Michael Hopkins Message-ID: <20050331190702.GG1687@dragon.NUXI.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-ports-bugs@freebsd.org cc: freebsd-emulation@freebsd.org cc: freebsd-ports@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-ports@freebsd.org, freebsd-emulation@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 19:07:04 -0000 Please DO NOT cross post to 4 different mailing lists. We have unique mailing lists for a purpose. On Thu, Mar 31, 2005 at 12:14:47PM +0100, Michael Hopkins wrote: > I have been installing a few Linux environments from the ports in the last > few days to try and establish a cross-compiler for 32-bit Linux on amd64 > (see my other post for the story so far). What you want to do is install the linux_base-8 port. It is the standard default linux emulation port. Ensure your ability to run 32-bit Linux binaries is OK. Install some port that requires linux_base-8 (I use Acrobat Reader - print/acroread). > devel/linux_devtools-7 > ---------------------- > Starting Terminal in /usr/ports/devel/linux_devtools-7... > bash-2.05b# make > ===> linux_devtools-7.1_3 is marked as broken: Incomplete pkg-plist. This is your basic problem -- the devtools port hasn't been updated to RH8 yet to match the default stock linux_base. If you are skilled with the Ports Collection update this port and send a patch. :-) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 19:26:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16ECE16A4CE for ; Thu, 31 Mar 2005 19:26:42 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 651B943D55 for ; Thu, 31 Mar 2005 19:26:41 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j2VJQe220001 for ; Thu, 31 Mar 2005 14:26:40 -0500 Message-ID: <424C4EED.5070601@infotechfl.com> Date: Thu, 31 Mar 2005 14:26:37 -0500 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 19:26:42 -0000 All, Pulled 2GB of RAM and the system still hangs after a few seconds of running the dd w/4GB RAM and amd64 generic on FreeBSD 5.3-REL. Upgraded the kernel to: $ uname -a FreeBSD d10.bidx.com 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Thu Mar 31 13:55:10 EST 2005 root@d10.bidx.com:/usr/obj/usr/src/sys/GENERIC amd64 ... and got the exact same hang w/4GB of RAM and 5.4-PRE... Can someone/anyone with a Tyan motherboard and 1 or 2 CPUs (I'm currently using the non-SMP GENERIC kernel even though I have dual Opteron 246's) try to reproduce this problem when running: dd if=/dev/mem of=/dev/null bs=1024k Thanks, Gary Vivek Khera wrote: > if you've got > 4GB ram, you pretty much *must* run something newer > than 5.3-REL. Try bringing it up to 5_STABLE cvs branch and see if > you can still lock it up. > > I don't have my spare machine at the moment to test this theory out, > or I would... rather not lockup the production box more often than > it does by itself :-( From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 20:39:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F4016A4CE for ; Thu, 31 Mar 2005 20:39:17 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B63F543D76 for ; Thu, 31 Mar 2005 20:39:16 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2VKdFeD005592; Thu, 31 Mar 2005 12:39:16 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2VKdFKu005591; Thu, 31 Mar 2005 12:39:15 -0800 (PST) (envelope-from obrien) Date: Thu, 31 Mar 2005 12:39:15 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050331203915.GH1687@dragon.NUXI.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05033109061a68554d@mail.gmail.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 20:39:17 -0000 On Thu, Mar 31, 2005 at 09:06:43AM -0800, Astrodog wrote: > Long term.... Perhaps a > Linux32 and Linux64 dep? Not sure. Anyone have thoughts on that? I > know its been discussed before, but I don't think a resolution ever > came out of it. No. There will only be /compat/linux. No linux32 or linux64 versions. Sometime in the future the linux_base port will be larger (ie, contain 64-bit objects also). The 64-bit things will live in the places specified by the Linux LSB spec. > For now, I'm > going to go with the assumption that there will be /compat/linux32 and > linux64. If this has been resolved, let me know so I can make the > ports fix I'm gonna work on reflect that. For right now, add amd64 to 'ONLY_FOR_ARCHS'. And add any of the rest of the below that is needed: .if (${ARCH} == "amd64") ARCH= i386 FALLBACK_ELF_MIB= kern.elf32.fallback_brand RPMFLAGS+= --noscripts .endif Doesn't anyone read the ports' Makefile any more?? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 21:50:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0109A16A4CE; Thu, 31 Mar 2005 21:50:54 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3627A43D1D; Thu, 31 Mar 2005 21:50:53 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.31.246]) by lakermmtao07.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20050331215052.HGUZ19214.lakermmtao07.cox.net@dolphin.local.net>; Thu, 31 Mar 2005 16:50:52 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.3/8.13.3) with ESMTP id j2VLoplJ038140; Thu, 31 Mar 2005 15:50:51 -0600 (CST) (envelope-from conrads@cox.net) Date: Thu, 31 Mar 2005 15:50:46 -0600 From: "Conrad J. Sabatier" To: freebsd-amd64@freebsd.org Message-ID: <20050331155046.21a5d323@dolphin.local.net> In-Reply-To: <20050331203915.GH1687@dragon.NUXI.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> X-Mailer: Sylpheed-Claws 1.0.4 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 21:50:54 -0000 On Thu, 31 Mar 2005 12:39:15 -0800, "David O'Brien" wrote: > On Thu, Mar 31, 2005 at 09:06:43AM -0800, Astrodog wrote: > > Long term.... Perhaps a > > Linux32 and Linux64 dep? Not sure. Anyone have thoughts on that? I > > know its been discussed before, but I don't think a resolution ever > > came out of it. > > No. There will only be /compat/linux. No linux32 or linux64 > versions. Sometime in the future the linux_base port will be larger > (ie, contain 64-bit objects also). The 64-bit things will live in the > places specified by the Linux LSB spec. > > > For now, I'm > > going to go with the assumption that there will be /compat/linux32 > > and linux64. If this has been resolved, let me know so I can make > > the ports fix I'm gonna work on reflect that. > > For right now, add amd64 to 'ONLY_FOR_ARCHS'. And add any of the rest > of the below that is needed: > > .if (${ARCH} == "amd64") > ARCH= i386 > FALLBACK_ELF_MIB= kern.elf32.fallback_brand > RPMFLAGS+= --noscripts > .endif > > Doesn't anyone read the ports' Makefile any more?? I already see one linux port for which the above additions are insufficient, namely, graphics/linux-jpeg: PORTNAME= jpeg PORTVERSION= 6b.15 PORTREVISION= 3 CATEGORIES= graphics linux MAINTAINER= freebsd-emulation@FreeBSD.org COMMENT= RPM of the JPEG lib RPM_SET= libjpeg-6b-15.${MACHINE_ARCH}.rpm ^^^^^^^^^^^^^^^ .include "../../x11-toolkits/linux-gtk/Makefile" -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 23:07:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 724C116A4D3 for ; Thu, 31 Mar 2005 23:07:06 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F85A43D49 for ; Thu, 31 Mar 2005 23:07:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14254 invoked from network); 31 Mar 2005 23:07:06 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 31 Mar 2005 23:07:05 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2VN6iQV028069; Thu, 31 Mar 2005 18:06:58 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Thu, 31 Mar 2005 17:27:44 -0500 User-Agent: KMail/1.6.2 References: <424C3C98.30602@cnpm.embrapa.br> In-Reply-To: <424C3C98.30602@cnpm.embrapa.br> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <200503311727.44841.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: "Carlos F. A. Paniago" Subject: Re: fstatfs break in amd64 ia32 emulation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 23:07:06 -0000 On Thursday 31 March 2005 01:08 pm, Carlos F. A. Paniago wrote: > hi: > I'm tring to compile in an amd64 and running in an i386.. I read in the > list that is not possible, but some things work if we compile using: > gcc -Di386 -D__i386__ -Uamd64 -U__amd64__ -m32 -B/lib32 -B/usr/lib32 -g > -o test-i386.amd test-i386.c > some simple program could be compiled in an amd64 machine and run in a > i386 machine. > but this program don't work: > -- > #include > #include > #include > #include > > int main(int argc, char** argv) > { > struct statfs buf; > > if (fstatfs(0, &buf) < 0) { > perror("fstatfs"); > } > > printf("%d %d\n", sizeof(buf), sizeof(&buf)); > return 0; > } > -- > the result is: > --- > ipe# ./test-i386 > 472 4 > ipe# ./test-i386.amd > 384 4 > Segmentation fault (core dumped) > ipe# > --- > this ipe machine is an i386 machine... the ./test-i386 is compiled in > this machine as > gcc -g -o test-i386 test-i386.c > and the ./test-i386.amd is compiled in an amd64 using: gcc -Di386 > -D__i386__ -Uamd64 -U__amd64__ -m32 -B/lib32 -B/usr/lib32 -g -o > test-i386.amd test-i386.c > The strange thing is the size of struct statfs that changes... If I > compile this in an amd64 machine (oliveira is an amd64 machine) > --- > oliveira: {248} gcc -g -o test-i386.amd test-i386.c > oliveira: {249} ./test-i386.amd > 472 8 > oliveira: {250} > --- > strange the size of the struct is the same as in i386 and the size of > the pointer is 8 (instead of 4), but in the compilation using the -m32 > the sizeof is strange... Someone know how to solve this problem??? You need to be using a different /usr/include, specifically a different /usr/include/machine (one from an i386 machine) when trying to compile -m32. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 23:37:15 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E9A016A4CE for ; Thu, 31 Mar 2005 23:37:15 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E46843D2D for ; Thu, 31 Mar 2005 23:37:14 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) j2VNvGEo097121; Thu, 31 Mar 2005 18:57:23 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: Gary Mu1der In-Reply-To: <424C4EED.5070601@infotechfl.com> References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> Content-Type: text/plain Date: Thu, 31 Mar 2005 18:37:23 -0500 Message-Id: <1112312243.6323.10.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 23:37:15 -0000 On Thu, 2005-03-31 at 14:26 -0500, Gary Mu1der wrote: > All, > > Pulled 2GB of RAM and the system still hangs after a few seconds of > running the dd w/4GB RAM and amd64 generic on FreeBSD 5.3-REL. > > Upgraded the kernel to: > > $ uname -a > FreeBSD d10.bidx.com 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Thu Mar > 31 13:55:10 EST 2005 root@d10.bidx.com:/usr/obj/usr/src/sys/GENERIC > amd64 > > ... and got the exact same hang w/4GB of RAM and 5.4-PRE... > > Can someone/anyone with a Tyan motherboard and 1 or 2 CPUs (I'm > currently using the non-SMP GENERIC kernel even though I have dual > Opteron 246's) try to reproduce this problem when running: > > dd if=/dev/mem of=/dev/null bs=1024k > > Thanks, > Gary Confirmed the hang with a dual opteron system (248's) with 8GB of ram using the dd command above. System hung within seconds of issuing said command using an SMP-enabled kernel. FreeBSD 5.4-PRERELEASE #0: Thu Mar 17 22:41:53 EST 2005 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2190.55-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 8589934592 (8192 MB) avail memory = 8250437632 (7868 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 Sven From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 04:00:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4C0A16A4CE for ; Fri, 1 Apr 2005 04:00:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4213143D31 for ; Fri, 1 Apr 2005 04:00:56 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so759415wra for ; Thu, 31 Mar 2005 20:00:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=exg006fUKILzHORXUTpRlB8JCumQpbg6AURYDzYPF64xeLluyVl0o5cb0K09ZAy9KPSL4W5Wl0jaFPGhqW+17bNuk0oqon1QyB8R8rN1XbybB7SMC8jGSptxsWZOXWmTk6nj3sMcvpSvP4KzSeM2TctZUxa4BdfBEj0VYV10u6w= Received: by 10.54.35.35 with SMTP id i35mr323971wri; Thu, 31 Mar 2005 20:00:55 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 31 Mar 2005 20:00:55 -0800 (PST) Message-ID: <2fd864e0503312000701c87c2@mail.gmail.com> Date: Thu, 31 Mar 2005 20:00:55 -0800 From: Astrodog To: "Conrad J. Sabatier" In-Reply-To: <20050331155046.21a5d323@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 04:00:56 -0000 On Mar 31, 2005 1:50 PM, Conrad J. Sabatier wrote: > On Thu, 31 Mar 2005 12:39:15 -0800, "David O'Brien" > wrote: > > > On Thu, Mar 31, 2005 at 09:06:43AM -0800, Astrodog wrote: > > > Long term.... Perhaps a > > > Linux32 and Linux64 dep? Not sure. Anyone have thoughts on that? I > > > know its been discussed before, but I don't think a resolution ever > > > came out of it. > > > > No. There will only be /compat/linux. No linux32 or linux64 > > versions. Sometime in the future the linux_base port will be larger > > (ie, contain 64-bit objects also). The 64-bit things will live in the > > places specified by the Linux LSB spec. > > > > > For now, I'm > > > going to go with the assumption that there will be /compat/linux32 > > > and linux64. If this has been resolved, let me know so I can make > > > the ports fix I'm gonna work on reflect that. > > > > For right now, add amd64 to 'ONLY_FOR_ARCHS'. And add any of the rest > > of the below that is needed: > > > > .if (${ARCH} == "amd64") > > ARCH= i386 > > FALLBACK_ELF_MIB= kern.elf32.fallback_brand > > RPMFLAGS+= --noscripts > > .endif > > > > Doesn't anyone read the ports' Makefile any more?? > > I already see one linux port for which the above additions are > insufficient, namely, graphics/linux-jpeg: > > PORTNAME= jpeg > PORTVERSION= 6b.15 > PORTREVISION= 3 > CATEGORIES= graphics linux > > MAINTAINER= freebsd-emulation@FreeBSD.org > COMMENT= RPM of the JPEG lib > > RPM_SET= libjpeg-6b-15.${MACHINE_ARCH}.rpm > ^^^^^^^^^^^^^^^ > .include "../../x11-toolkits/linux-gtk/Makefile" > > -- > Conrad J. Sabatier -- "In Unix veritas" > Those are going to be the ugliest to get working. My fix thus far has been to simply s/${MACHINE_ARCH}/i386 on the linux ports. Seemed to work alright. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 05:57:29 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCA8D16A4CE for ; Fri, 1 Apr 2005 05:57:29 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2616443D45 for ; Fri, 1 Apr 2005 05:57:28 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j315vLvE098655; Fri, 1 Apr 2005 07:57:21 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j315vLfi082731; Fri, 1 Apr 2005 07:57:21 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j315vLkc082730; Fri, 1 Apr 2005 07:57:21 +0200 (CEST) (envelope-from ftigeot) Date: Fri, 1 Apr 2005 07:57:21 +0200 From: Francois Tigeot To: "Conrad J. Sabatier" Message-ID: <20050401055721.GA72973@aoi.wolfpond.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050331155046.21a5d323@dolphin.local.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 05:57:30 -0000 On Thu, Mar 31, 2005 at 03:50:46PM -0600, Conrad J. Sabatier wrote: > On Thu, 31 Mar 2005 12:39:15 -0800, "David O'Brien" > wrote: > > > > For right now, add amd64 to 'ONLY_FOR_ARCHS'. And add any of the rest > > of the below that is needed: > > > > .if (${ARCH} == "amd64") > > ARCH= i386 > > FALLBACK_ELF_MIB= kern.elf32.fallback_brand > > RPMFLAGS+= --noscripts > > .endif > > > > Doesn't anyone read the ports' Makefile any more?? > > I already see one linux port for which the above additions are > insufficient, namely, graphics/linux-jpeg: > > PORTNAME= jpeg > PORTVERSION= 6b.15 > PORTREVISION= 3 > CATEGORIES= graphics linux > > MAINTAINER= freebsd-emulation@FreeBSD.org > COMMENT= RPM of the JPEG lib > > RPM_SET= libjpeg-6b-15.${MACHINE_ARCH}.rpm > ^^^^^^^^^^^^^^^ > .include "../../x11-toolkits/linux-gtk/Makefile" This one can be fixed by the patch in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79009 -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 06:18:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7AAF16A4CE for ; Fri, 1 Apr 2005 06:18:42 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49F8743D46 for ; Fri, 1 Apr 2005 06:18:42 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so571217rnf for ; Thu, 31 Mar 2005 22:18:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=kChqyEb7u0UoxeLSPBaENHeYvNdgGFhgz3UZ8bckm89InZMMB/nJfuV8xGp2Ahd0yrHoT1Mc+u3N7B+Dy/cfq5VMpcQrcDdn4fr9RkG0NdRbxrv0ULaAY9wg8JM6nJzQ+Z8D0XEtYHd8wwxwxMCKWWs6BTHw1y/z3Sq4PhoL5o0= Received: by 10.38.101.60 with SMTP id y60mr2135450rnb; Thu, 31 Mar 2005 22:18:41 -0800 (PST) Received: by 10.39.2.24 with HTTP; Thu, 31 Mar 2005 22:18:41 -0800 (PST) Message-ID: <346a80220503312218926bfdb@mail.gmail.com> Date: Fri, 1 Apr 2005 01:18:41 -0500 From: Coleman Kane To: Jung-uk Kim In-Reply-To: <200503281243.37327.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050208163758.GA1086@NitroPhys.welchsmnet.net> <200502081156.51114.nb_root@videotron.ca> <200503261117.29939.nb_root@videotron.ca> <200503281243.37327.jkim@niksun.com> cc: freebsd-amd64@freebsd.org Subject: Re: Compaq R3000Z keyboard doesn't work without DSDT patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 06:18:43 -0000 On Mar 28, 2005 12:43 PM, Jung-uk Kim wrote: > On Saturday 26 March 2005 11:17 am, Nicolas Blais wrote: > > Hi, > > > > Without the following lines in loader.conf: > > acpi_dsdt_load="YES" > > acpi_dsdt_name="/boot/DSDT.aml" > > > > and of course in device.hints: > > hint.atkbd.0.flags="0x9" > > > > and Jung-uk Kim's r3000z-asl.diff found on this list, my keyboard > > not work at all but the booting process is fine and I can move my > > mouse, log on thru ssh etc... > > > > I was under the impression that 5.4 would be "R3000 friendly" and > > that the only things needed were hint.atkbd.0.flags="0x9" in > > device.hints and the powernow module (which stays at 800mhz while > > acpi_ppc works). Is there something I'm doing wrong? > > You are not doing anything wrong. The real problem is the BIOS is so > broken that some problems cannot be worked around. :-( Keyboard > resource is overlapped with something else. We cannot fix all > problems without breaking other platforms, unfortunately. > > Jung-uk Kim > > > Thanks, > > Nicolas. > _______________________________________________ > 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" > FYI, I had to apply this cange manually to my prof's R3000. The diff just didn't line up. I suspect various revisions of this laptop will have slight differences in the BIOS code. Perhaps one of these will be accidentally fixed by them....If you really want to fix it, contact HP/Compaq and tell them that their stuff is broke and they should fix it. -- coleman From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 06:47:20 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88AAD16A4CE for ; Fri, 1 Apr 2005 06:47:20 +0000 (GMT) Received: from web30703.mail.mud.yahoo.com (web30703.mail.mud.yahoo.com [68.142.200.136]) by mx1.FreeBSD.org (Postfix) with SMTP id 28D9643D48 for ; Fri, 1 Apr 2005 06:47:20 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 30059 invoked by uid 60001); 1 Apr 2005 06:47:19 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=jUMnfCdxxVGdkf5Mh1CW6ILJu2oLWU36LGA7o3v727YI/rn2Fe5Gnu/UPAbzOy3ALWF7dapI5yL/Eu9It0xEsPLJ8P8jxVvIy3lsXDqOGxZt2/OsuYBg6sv2R7NegMxuSzNOwHndf7FbLvJLmUPmvxevZx1wnrpg1HktJ8zlkes= ; Message-ID: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30703.mail.mud.yahoo.com via HTTP; Thu, 31 Mar 2005 22:47:19 PST Date: Thu, 31 Mar 2005 22:47:19 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Dumb R3000Z / zv5000 questions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 06:47:20 -0000 1) are there any instructions on how to use the powerd (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/powerd/) or the powernow tools? It's not intuitive to me. 1a) Does it work with the XP-M (32 bit) processor? 2) what is the recommended sound module for this equipment? I know this was answered somewhere before but I sure can't find it. Thanks. __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 07:29:33 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5282816A4CE for ; Fri, 1 Apr 2005 07:29:33 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4FDE43D54 for ; Fri, 1 Apr 2005 07:29:32 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so790389wra for ; Thu, 31 Mar 2005 23:29:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=N63PpALQiScT0hYCUPorpoG/yDRqYD0beW/MoEBB/ngpLmmDFBO+WN9KM20eZJUTzoMTRwgB4o+8C9hyeHhasY/DLzxzaXxisYue9VVOwVXU+MPfLmMBXWnjPtt08VmlW0UNc3ovg5dJMW6WDsR5aXlpRzM2Qukc5VTanCSAhNA= Received: by 10.54.35.35 with SMTP id i35mr447426wri; Thu, 31 Mar 2005 23:29:29 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 31 Mar 2005 23:29:29 -0800 (PST) Message-ID: <2fd864e0503312329460f4027@mail.gmail.com> Date: Thu, 31 Mar 2005 23:29:29 -0800 From: Astrodog To: Neil Short In-Reply-To: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> cc: freebsd-amd64@freebsd.org Subject: Re: Dumb R3000Z / zv5000 questions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 07:29:33 -0000 On Mar 31, 2005 10:47 PM, Neil Short wrote: > 1) are there any instructions on how to use the powerd > (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/powerd/) > or the powernow tools? It's not intuitive to me. > > 1a) Does it work with the XP-M (32 bit) processor? > Some of the patches are amd64 specific, you might need to fix those. > 2) what is the recommended sound module for this > equipment? I know this was answered somewhere before > but I sure can't find it. > snd_ich on mine. > Thanks. > > __________________________________ > Do you Yahoo!? > Yahoo! Personals - Better first dates. More second dates. > http://personals.yahoo.com > > _______________________________________________ > 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 Fri Apr 1 09:31:29 2005 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93B8116A4CE for ; Fri, 1 Apr 2005 09:31:29 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7219743D39 for ; Fri, 1 Apr 2005 09:31:29 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 37758554BB for ; Fri, 1 Apr 2005 09:31:29 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 353E516A4CE for ; Fri, 1 Apr 2005 09:31:29 +0000 (GMT) Received: from mail.martymac.com (martymac.com [82.224.94.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1A2043D45 for ; Fri, 1 Apr 2005 09:31:28 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from martymac.com (localhost [127.0.0.1]) by mail.martymac.com (Postfix) with ESMTP id 72DEC1BF for ; Fri, 1 Apr 2005 11:32:45 +0200 (CEST) From: "Ganael Laplanche" To: freebsd-amd64@lists.freebsd.org Date: Fri, 1 Apr 2005 09:32:45 +0000 Message-Id: <20050401090927.M62447@martymac.com> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 192.168.1.1 (martymac) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 09:31:29 -0000 Hi all, I'm running 5.4-PRERELEASE #13 for AMD64 and can't get agp working. My graphic card is an ATI Radeon 9000. Xorg works well, but drm can't load because of the lack of agp device. I get these errors each time I start X : # dmesg [...] error: [drm:pid564:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:pid564:radeon_unlock] *ERROR* Process 564 using kernel context 0 [...] However, an agp device should be detected ; here is my kernel conf file : [...] device acpi device isa device pci device agp device vga device splash device radeondrm # ATI Radeon 9000 [...] But no device is detected at boot : # dmesg | grep -i agp doesn't show anything Isn't nforce3 250 agp controller supported yet ? I know I'm not the only one, since I saw a thread on a forum a few weeks ago (I can't remember the URL...). I also went to http://dri.freedesktop.org/wiki/DriTroubleshooting but without success... Any idea ? Does someone get the same errors ? Ganaël LAPLANCHE ganael.laplanche@martymac.com http://www.martymac.com Tel : (+33)6.84.03.57.24. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 10:05:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF6416A4CE for ; Fri, 1 Apr 2005 10:05:44 +0000 (GMT) Received: from web30708.mail.mud.yahoo.com (web30708.mail.mud.yahoo.com [68.142.200.141]) by mx1.FreeBSD.org (Postfix) with SMTP id 7F31443D31 for ; Fri, 1 Apr 2005 10:05:44 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 41054 invoked by uid 60001); 1 Apr 2005 10:05:44 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=nUVHf2rTNd/0DewCX5xE0+BMacV3Z5sjicUHz6qVb4+kBqdH+kFsoykEIcdTkY6rhy5VR9DH3qzDep570dgGQOkmiQJ1xxHqOaeGKgMLNRF1HKTMqE67NJr2Awog/NZyVwmwAD1Aq08m08uVHyyWl9rweixJcQyU7wcYOHuC4n4= ; Message-ID: <20050401100544.41052.qmail@web30708.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30708.mail.mud.yahoo.com via HTTP; Fri, 01 Apr 2005 02:05:43 PST Date: Fri, 1 Apr 2005 02:05:43 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org, freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: growisofs DVD write woes on HP/Compaq laptop X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 10:05:45 -0000 Has anybody had success writing DVDs on this equipment? here's my sad effort: carmen# growisofs -Z /dev/cd0 -dvd-compat dvd1 :-( /dev/cd0: media is not recognized as recordable DVD: 10 What is in the drive is a blank DVD-R pertinant dmesg stuff: ... acd0: CDRW at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [174027 x 2048 byte records] ... If history always begins this morning, the world holds exciting surprises around every corner (241). --Ann Coulter. Treason. __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 12:35:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0310016A4CE for ; Fri, 1 Apr 2005 12:35:02 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E18D43D31 for ; Fri, 1 Apr 2005 12:35:01 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1DHLMM-0001bD-00; Fri, 01 Apr 2005 14:34:46 +0200 Date: Fri, 1 Apr 2005 14:34:46 +0200 To: Neil Short Message-ID: <20050401123446.GN2298@poupinou.org> References: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot cc: freebsd-amd64@freebsd.org Subject: Re: Dumb R3000Z / zv5000 questions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 12:35:02 -0000 On Thu, Mar 31, 2005 at 10:47:19PM -0800, Neil Short wrote: > 1) are there any instructions on how to use the powerd > (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/powerd/) > or the powernow tools? It's not intuitive to me. for -current, just kldload cpufreq, or compile kernel with device cpufreq then you can configure powerd via /etc/rc.conf for RELENG_5, specific low level drivers are not yet been MFC, but the cpufreq infrastucture is. So you have to do something like that in the time beeing: On, say, $HOME/cpufreq, cvs co src/sys/dev/acpica/acpi_perf.c cvs co -P src/sys/dev/cpufreq cvs co -P src/sys/i386/cpufreq cvs co -P src/usr.sbin/powerd mkdir acpi_perf cp src/sys/dev/acpica/acpi_perf.c acpi_perf cp -r src/sys/i386/cpufreq . cp src/sys/dev/cpufreq/ichss.c cpufreq cp -r src/usr.sbin/powerd . Then modify or add some Makefile: I'm using the following: cat Makefile SUBDIR = acpi_perf cpufreq powerd .include cat acpi_perf/Makefile CFLAGS+= -I@/contrib/dev/acpica KMOD= acpi_perf WARNS?= 2 SRCS= acpi_perf.c SRCS+= acpi_if.h bus_if.h cpufreq_if.h device_if.h opt_acpi.h \ pci_if.h .include cat cpufreq/Makefile KMOD= cpufreq SRCS= est.c ichss.c p4tcc.c powernow.c SRCS+= bus_if.h cpufreq_if.h device_if.h .include I also have to modify a little the Makefile for powerd as such: # $FreeBSD: src/usr.sbin/powerd/Makefile,v 1.2 2005/02/26 22:50:25 njl # Exp $ PROG= powerd MAN= powerd.8 WARNS?= 6 BINDIR= /usr/sbin .include Then do a make followed by a make install. You can then, in order: kldload acpi_perf kldload cpufreq and launch powerd(8) with option '-v' for testing purpose. > 1a) Does it work with the XP-M (32 bit) processor? Yes > > 2) what is the recommended sound module for this > equipment? I know this was answered somewhere before > but I sure can't find it. Don't know. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 12:29:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE61116A4CE; Fri, 1 Apr 2005 12:29:39 +0000 (GMT) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 414BC43D3F; Fri, 1 Apr 2005 12:29:39 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd29.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1DHLHN-0000of-02; Fri, 01 Apr 2005 14:29:37 +0200 Received: from Andro-Beta.Leidinger.net (r9l2ocZB8eosZihJDct1+3UDw0Z8rA7NxKD-nJsyNSLrWDpeXtI3ZH@[217.83.21.129]) by fwd29.sul.t-online.de with esmtp id 1DHLHE-0ng4oK0; Fri, 1 Apr 2005 14:29:28 +0200 Received: from localhost (localhost [127.0.0.1])j31CTQSW036558; Fri, 1 Apr 2005 14:29:26 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (Horde) with HTTP for ; Fri, 1 Apr 2005 14:29:26 +0200 Message-ID: <20050401142926.ffayz4h19ssk4s04@netchild.homeip.net> X-Priority: 3 (Normal) Date: Fri, 1 Apr 2005 14:29:26 +0200 From: Alexander Leidinger To: freebsd-ports@freebsd.org, freebsd-emulation@freebsd.org References: <20050331190702.GG1687@dragon.NUXI.org> In-Reply-To: <20050331190702.GG1687@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.2) / FreeBSD-4.11 X-ID: r9l2ocZB8eosZihJDct1+3UDw0Z8rA7NxKD-nJsyNSLrWDpeXtI3ZH@t-dialin.net X-TOI-MSGID: 14bbf44b-d46a-42a6-8aab-96db2cc3674a X-Mailman-Approved-At: Fri, 01 Apr 2005 12:38:55 +0000 cc: Michael Hopkins cc: freebsd-ports-bugs@freebsd.org cc: freebsd-emulation@freebsd.org cc: "freebsd-amd64@freebsd.org" cc: freebsd-ports@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 12:29:40 -0000 David O'Brien wrote: > This is your basic problem -- the devtools port hasn't been updated to > RH8 yet to match the default stock linux_base. If you are skilled with > the Ports Collection update this port and send a patch. :-) We have some inconsistencies in our linux ports (this is just one of them)... the RH8 version of the devtools lives in devel/linux_devtools. As Scott already mentioned they are lacking the amd64 entry in ONLY_FOR_ARCHES. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 12:47:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68F7216A4CE for ; Fri, 1 Apr 2005 12:47:04 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267C943D4C for ; Fri, 1 Apr 2005 12:47:04 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1DHLYA-0001cR-00; Fri, 01 Apr 2005 14:46:58 +0200 Date: Fri, 1 Apr 2005 14:46:58 +0200 To: Astrodog Message-ID: <20050401124658.GO2298@poupinou.org> References: <20050401064719.30057.qmail@web30703.mail.mud.yahoo.com> <2fd864e0503312329460f4027@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e0503312329460f4027@mail.gmail.com> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot cc: freebsd-amd64@freebsd.org Subject: Re: Dumb R3000Z / zv5000 questions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 12:47:04 -0000 On Thu, Mar 31, 2005 at 11:29:29PM -0800, Astrodog wrote: > On Mar 31, 2005 10:47 PM, Neil Short wrote: > > 1) are there any instructions on how to use the powerd ... > > 1a) Does it work with the XP-M (32 bit) processor? > > > Some of the patches are amd64 specific, you might need to fix those. FYI powernow in -current have been written first for Athlon-XP (mobile and low powered models) and Mobile Duron, and then some functions taken from acpi_ppc and modified have been integrated to it. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 15:42:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2263916A4CE for ; Fri, 1 Apr 2005 15:42:54 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06CB043D1F for ; Fri, 1 Apr 2005 15:42:53 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j31ELk205396; Fri, 1 Apr 2005 09:21:46 -0500 Message-ID: <424D58F7.1010005@infotechfl.com> Date: Fri, 01 Apr 2005 09:21:43 -0500 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sven Willenberger References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> <1112312243.6323.10.camel@lanshark.dmv.com> In-Reply-To: <1112312243.6323.10.camel@lanshark.dmv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 15:42:54 -0000 Sven, Thanks for testing. It is not SMP causing the problem, as I can cause the hang with the GENERIC amd64 uniproccesor kernel as well. Any idea how we can get more diagnostics on what in FreeBSD is causing the crash? I suppose I can truss the dd and copy the truss output off the remote terminal session after is hangs... Is there a way to force a crash dump? I heard mention of a key combo on the console to force a crash dump, but I suspect the console keyboard is totally hung as well. Does anyone have a doc on how to run the kernel under gdb or something and log what is happening to a serial console? Gary Sven Willenberger wrote: > Confirmed the hang with a dual opteron system (248's) with 8GB of ram > using the dd command above. System hung within seconds of issuing said > command using an SMP-enabled kernel. > > FreeBSD 5.4-PRERELEASE #0: Thu Mar 17 22:41:53 EST 2005 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 248 (2190.55-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 > > Features=0x78bfbff > AMD Features=0xe0500800 > real memory = 8589934592 (8192 MB) > avail memory = 8250437632 (7868 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > cpu1: on acpi0 > > > Sven > > From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 16:18:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2953616A4CE for ; Fri, 1 Apr 2005 16:18:50 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5D0243D39 for ; Fri, 1 Apr 2005 16:18:49 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.149] (host-149.int.kcilink.com [192.168.7.149]) by yertle.kcilink.com (Postfix) with ESMTP id 7C0DFB80C for ; Fri, 1 Apr 2005 11:18:49 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <424D58F7.1010005@infotechfl.com> References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> <1112312243.6323.10.camel@lanshark.dmv.com> <424D58F7.1010005@infotechfl.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Fri, 1 Apr 2005 11:18:47 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619.2) Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 16:18:50 -0000 On Apr 1, 2005, at 9:21 AM, Gary Mu1der wrote: > Is there a way to force a crash dump? I heard mention of a key combo > on the console to force a crash dump, but I suspect the console > keyboard is totally hung as well. > > Does anyone have a doc on how to run the kernel under gdb or something > and log what is happening to a serial console? > when I get my lockups (had another this A.M.) the serial console line is non-responsive as well. I cannot break into the kernel debugger at all. There is no evidence of *anything* going bad other than the machine is totally unresponsive to network and console. nothing is logged anywhere, including the BIOS. when it happens it is during time of heavy I/O + network load. I'm now running with debug.mpsafenet=0 to see if i'm tickling a bug in the network stack, given that I saw some bge0 timeouts earlier. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 17:35:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8FD316A4CE for ; Fri, 1 Apr 2005 17:35:12 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9B343D31 for ; Fri, 1 Apr 2005 17:35:09 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j31HZ8J7036612; Fri, 1 Apr 2005 12:35:09 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Fri, 1 Apr 2005 12:35:05 -0500 User-Agent: KMail/1.6.2 References: <20050401090927.M62447@martymac.com> In-Reply-To: <20050401090927.M62447@martymac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_JZYTCVKHiPq+FQk" Message-Id: <200504011235.05993.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/799/Fri Apr 1 05:49:13 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 17:35:13 -0000 --Boundary-00=_JZYTCVKHiPq+FQk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline On Friday 01 April 2005 04:32 am, Ganael Laplanche wrote: > Hi all, > > I'm running 5.4-PRERELEASE #13 for AMD64 and can't get agp working. > > My graphic card is an ATI Radeon 9000. Xorg works well, but drm > can't load because of the lack of agp device. I get these errors > each time I start X : > > # dmesg > [...] > error: [drm:pid564:radeon_cp_init] *ERROR* radeon_cp_init called > without lock held error: [drm:pid564:radeon_unlock] *ERROR* Process > 564 using kernel context 0 [...] > > However, an agp device should be detected ; here is my kernel conf > file : > > [...] > device acpi > device isa > device pci > device agp > > device vga > device splash > device radeondrm # ATI Radeon 9000 > [...] > > But no device is detected at boot : > # dmesg | grep -i agp > doesn't show anything > > Isn't nforce3 250 agp controller supported yet ? Try the attached patch. I had it for long time but I forgot to file a PR. ;-) Jung-uk Kim > I know I'm not the only one, since I saw a thread on a forum a few > weeks ago (I can't remember the URL...). I also went to > http://dri.freedesktop.org/wiki/DriTroubleshooting but without > success... > > Any idea ? Does someone get the same errors ? > > Ganaël LAPLANCHE > ganael.laplanche@martymac.com > http://www.martymac.com > Tel : (+33)6.84.03.57.24. --Boundary-00=_JZYTCVKHiPq+FQk Content-Type: text/x-diff; charset="iso-8859-1"; name="agp_nforce3.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="agp_nforce3.diff" Index: agp_amd64.c =================================================================== RCS file: /home/ncvs/src/sys/pci/agp_amd64.c,v retrieving revision 1.5 diff -u -r1.5 agp_amd64.c --- src/sys/pci/agp_amd64.c 24 Feb 2005 21:32:55 -0000 1.5 +++ src/sys/pci/agp_amd64.c 1 Apr 2005 17:31:33 -0000 @@ -82,6 +82,8 @@ return ("AMD 8151 AGP graphics tunnel"); case 0x07551039: return ("SiS 755 host to AGP bridge"); + case 0x00d110de: + return ("NVIDIA nForce3 AGP Controller"); case 0x02041106: return ("VIA 8380 host to PCI bridge"); case 0x02821106: Index: agp_nvidia.c =================================================================== RCS file: /home/ncvs/src/sys/pci/agp_nvidia.c,v retrieving revision 1.8 diff -u -r1.8 agp_nvidia.c --- src/sys/pci/agp_nvidia.c 24 Feb 2005 22:33:05 -0000 1.8 +++ src/sys/pci/agp_nvidia.c 1 Apr 2005 17:31:33 -0000 @@ -109,7 +109,7 @@ case NVIDIA_DEVICEID_NFORCE2: return ("NVIDIA nForce2 AGP Controller"); } - return ("NVIDIA Generic AGP Controller"); + return (NULL); } static int --Boundary-00=_JZYTCVKHiPq+FQk-- From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 18:13:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45DEB16A4CE for ; Fri, 1 Apr 2005 18:13:09 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBF1843D2F for ; Fri, 1 Apr 2005 18:13:08 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j31ID4mr027869; Fri, 1 Apr 2005 10:13:04 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j31ID4lW027868; Fri, 1 Apr 2005 10:13:04 -0800 (PST) (envelope-from obrien) Date: Fri, 1 Apr 2005 10:13:04 -0800 From: "David O'Brien" To: "Conrad J. Sabatier" Message-ID: <20050401181304.GB27705@dragon.NUXI.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050331155046.21a5d323@dolphin.local.net> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 18:13:09 -0000 [ Please respect Reply-To: ] On Thu, Mar 31, 2005 at 03:50:46PM -0600, Conrad J. Sabatier wrote: > On Thu, 31 Mar 2005 12:39:15 -0800, "David O'Brien" wrote: > I already see one linux port for which the above additions are > insufficient, namely, graphics/linux-jpeg: .. > RPM_SET= libjpeg-6b-15.${MACHINE_ARCH}.rpm > ^^^^^^^^^^^^^^^ Ports are not suppose to use MACHINE_ARCH, but rather ARCH. I will fix this after the ports thaw. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 18:34:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B875B16A4CE; Fri, 1 Apr 2005 18:34:04 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3723D43D31; Fri, 1 Apr 2005 18:34:04 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id j31IY3u7090983; Fri, 1 Apr 2005 13:34:03 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j31IY3g9023168; Fri, 1 Apr 2005 13:34:03 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 390107306E; Fri, 1 Apr 2005 13:34:03 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050401183403.390107306E@freebsd-current.sentex.ca> Date: Fri, 1 Apr 2005 13:34:03 -0500 (EST) X-Virus-Scanned: ClamAV 0.82/799/Fri Apr 1 05:49:13 2005 on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 18:34:04 -0000 TB --- 2005-04-01 17:18:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-01 17:18:09 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-01 17:18:09 - checking out the source tree TB --- 2005-04-01 17:18:09 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-01 17:18:09 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-01 17:25:01 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-01 17:25:01 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-01 17:25:01 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-04-01 18:34:02 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-01 18:34:02 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-01 18:34:02 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Apr 1 18:34:02 UTC 2005 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/legacy/usr/sbin:/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/legacy/usr/bin:/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/legacy/usr/games:/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/sbin:/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/bin:/home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/GENERIC config: Error: device "arcmsr" is unknown config: 1 errors *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-01 18:34:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-01 18:34:02 - ERROR: failed to build generic kernel TB --- 2005-04-01 18:34:02 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 21:43:55 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1869A16A4CE for ; Fri, 1 Apr 2005 21:43:55 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2062E43D2F for ; Fri, 1 Apr 2005 21:43:54 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j31Jis208643 for ; Fri, 1 Apr 2005 14:44:56 -0500 Message-ID: <424DA4B3.3070703@infotechfl.com> Date: Fri, 01 Apr 2005 14:44:51 -0500 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> <1112312243.6323.10.camel@lanshark.dmv.com> <424D58F7.1010005@infotechfl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 21:43:55 -0000 All, I have isolated the crash to the following dd command: dd if=/dev/mem of=/dev/null bs=1024k skip=4040 count=1 I'm trying to think of a way to obtain more diagnostics. It looks like truss is broken due to the the lack of /proc in 5.3. I'll compile a kernel with procfs and see if I can obtain more detail trussing the dd. I really need guidance from the list on how to proceed and obtain more debugging info. Thanks, Gary From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 23:17:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F69C16A4CE for ; Fri, 1 Apr 2005 23:17:57 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BC743D1D for ; Fri, 1 Apr 2005 23:17:57 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so778085rng for ; Fri, 01 Apr 2005 15:17:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ILslbI7qoZI6eqvRvBx0q5NRsqtWvCN57iLoZ0rsNDu1mglf2tKueHjMiuUsiR7PbCKjkQY5YKKPfPMujqa1exL5YvZxZDpbW+qBQHDNm/EjXsljZvND32aibXBNN+DZZ3jHwpvdW9dZN9S/vQUj0o5scVwyvwShkk4ywHNTDO0= Received: by 10.38.69.34 with SMTP id r34mr3257140rna; Fri, 01 Apr 2005 15:17:56 -0800 (PST) Received: by 10.38.74.23 with HTTP; Fri, 1 Apr 2005 15:17:56 -0800 (PST) Message-ID: Date: Sat, 2 Apr 2005 01:17:56 +0200 From: Gert Cuykens To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Our beloved nforce 3 chipset X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 23:17:57 -0000 FX-53R kldload /usr/src/sys/modules/sound/driver/ich/snd_ich.ko FX-53R kldstat Id Refs Address Size Name 1 9 0xffffffff80100000 5b49f0 kernel 2 1 0xffffffffa75ff000 add4 if_nv.ko 3 1 0xffffffffa7856000 1cd blank_saver.ko 4 1 0xffffffffa7924000 227d snd_ich.ko 5 1 0xffffffffa7927000 12e1a sound.ko FX-53R dmesg ... pcm0: port 0xe400-0xe47f,0xe800-0xe8ff mem 0xff6fb000-0xff6fbfff irq 5 at device 6.0 on pci0 pcm0: [GIANT-LOCKED] pcm0: cannot reset channel 0 pcm0: unable to initialize the card device_attach: pcm0 attach returned 6 My sound use to work perfect? I dont know why i get this ? Any idea how to fix this please ? From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 1 23:55:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0C2A16A4CE for ; Fri, 1 Apr 2005 23:55:54 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8277743D2F for ; Fri, 1 Apr 2005 23:55:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AF1E651452; Fri, 1 Apr 2005 15:55:53 -0800 (PST) Date: Fri, 1 Apr 2005 15:55:53 -0800 From: Kris Kennaway To: Michael Bernstein Message-ID: <20050401235553.GA8510@xor.obsecurity.org> References: <20050331180556.92368.qmail@web20026.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <20050331180556.92368.qmail@web20026.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: question about quantum computing with 64 bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 23:55:54 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Mar 31, 2005 at 10:05:55AM -0800, Michael Bernstein wrote: > Can FreeBSD 64 bit on parallel opterons as a core > connected via gigabit cards with cross-over cables to > other 64 AMD Athlon running FreeBSD and the right > algorithm "make a quantum computing network". ?????? > Would much RAM be required? and SCSI disks needed as > well. Depending on what you want to do with it, you may only need a few hundred qubits of RAM. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCTd+JWry0BWjoQKURAqpbAKCf3Xe720zGfC6Dm4X7SIJuQSFh3ACfaXzd 0JBQkf2alXaPNM3OqwPB5as= =ozNp -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 01:13:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 3C3AF16A4CF; Sat, 2 Apr 2005 01:13:44 +0000 (GMT) Date: Sat, 2 Apr 2005 01:13:44 +0000 From: David O'Brien To: "Carlos F. A. Paniago" Message-ID: <20050402011344.GA61029@hub.freebsd.org> References: <424C3C98.30602@cnpm.embrapa.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <424C3C98.30602@cnpm.embrapa.br> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: fstatfs break in amd64 ia32 emulation X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 01:13:44 -0000 On Thu, Mar 31, 2005 at 03:08:24PM -0300, Carlos F. A. Paniago wrote: > hi: > I'm tring to compile in an amd64 and running in an i386.. I read in the > list that is not possible, but some things work if we compile using: > gcc -Di386 -D__i386__ -Uamd64 -U__amd64__ -m32 -B/lib32 -B/usr/lib32 -g > -o test-i386.amd test-i386.c > some simple program could be compiled in an amd64 machine and run in a > i386 machine. > but this program don't work: ... > Segmentation fault (core dumped) > ipe# ... > the sizeof is strange... Someone know how to solve this problem??? YES -- the solution is: DON'T DO THAT THEN!! We do NOT support building 32-bit binaries under FreeBSD/AMD64 yet. So don't bother the list with 1/2 attempts at doing so. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 01:15:55 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9D7C16A4CE for ; Sat, 2 Apr 2005 01:15:55 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F75343D45 for ; Sat, 2 Apr 2005 01:15:55 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j321FgYS034924; Fri, 1 Apr 2005 17:15:42 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j321FfX6034923; Fri, 1 Apr 2005 17:15:41 -0800 (PST) (envelope-from obrien) Date: Fri, 1 Apr 2005 17:15:41 -0800 From: "David O'Brien" To: Francois Tigeot Message-ID: <20050402011541.GA33607@dragon.NUXI.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> <20050401055721.GA72973@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050401055721.GA72973@aoi.wolfpond.org> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 01:15:56 -0000 On Fri, Apr 01, 2005 at 07:57:21AM +0200, Francois Tigeot wrote: > This one can be fixed by the patch in this PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79009 The patch isn't quite right -- don't [re]define MACHINE_ARCH, change any instance of "MACHINE_ARCH" to "ARCH". -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 01:52:09 2005 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A38416A4CE for ; Sat, 2 Apr 2005 01:52:09 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AAB243D4C for ; Sat, 2 Apr 2005 01:52:09 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id E716755AA3 for ; Sat, 2 Apr 2005 01:52:08 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E51CF16A4CE for ; Sat, 2 Apr 2005 01:52:08 +0000 (GMT) Received: from mail.martymac.com (martymac.com [82.224.94.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D42043D4C for ; Sat, 2 Apr 2005 01:52:08 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from martymac.com (localhost [127.0.0.1]) by mail.martymac.com (Postfix) with ESMTP id 062BF1F7; Sat, 2 Apr 2005 03:53:23 +0200 (CEST) From: "Ganael Laplanche" To: freebsd-amd64@lists.freebsd.org Date: Sat, 2 Apr 2005 01:53:23 +0000 Message-Id: <20050402013119.M28803@martymac.com> In-Reply-To: <200504011235.05993.jkim@niksun.com> References: <20050401090927.M62447@martymac.com> <200504011235.05993.jkim@niksun.com> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 192.168.1.1 (martymac) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=OPENWEBMAIL_ATT_0.172811147291213" Subject: Re: [PATCH test] K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 01:52:09 -0000 This is a multi-part message in MIME format. ------=OPENWEBMAIL_ATT_0.172811147291213 Content-Type: text/plain; charset=iso-8859-1 Hi Kim, Thank you very much for you answer. I tried your patch, but unfortunately, no agp device was detected... so I modified it a bit and managed to get this : # dmesg [...] Apr 2 03:00:13 odie kernel: Copyright (c) 1992-2005 The FreeBSD Project. Apr 2 03:00:13 odie kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Apr 2 03:00:13 odie kernel: The Regents of the University of California. All rights reserved. Apr 2 03:00:13 odie kernel: FreeBSD 5.4-PRERELEASE #0: Sat Apr 2 02:48:51 CEST 2005 Apr 2 03:00:13 odie kernel: martymac@odie.martymac.com:/usr/src/sys/amd64/compile/MYKERNEL Apr 2 03:00:13 odie kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Apr 2 03:00:13 odie kernel: CPU: AMD Athlon(tm) 64 Processor 3200+ (2210.77-MHz K8-class CPU) Apr 2 03:00:13 odie kernel: Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Apr 2 03:00:13 odie kernel: Features=0x78bfbff Apr 2 03:00:13 odie kernel: AMD Features=0xe0500800 Apr 2 03:00:13 odie kernel: real memory = 536608768 (511 MB) Apr 2 03:00:13 odie kernel: avail memory = 509628416 (486 MB) Apr 2 03:00:13 odie kernel: netsmb_dev: loaded Apr 2 03:00:13 odie kernel: cpu0 on motherboard Apr 2 03:00:13 odie kernel: pcib0: pcibus 0 on motherboard Apr 2 03:00:13 odie kernel: pci0: on pcib0 Apr 2 03:00:13 odie kernel: agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 Apr 2 03:00:13 odie kernel: isab0: at device 1.0 on pci0 Apr 2 03:00:13 odie kernel: isa0: on isab0 Apr 2 03:00:13 odie kernel: pci0: at device 1.1 (no driver attached) Apr 2 03:00:13 odie kernel: ohci0: mem 0xff6fd000-0xff6fdfff irq 5 at device 2.0 on pci0 Apr 2 03:00:13 odie kernel: usb0: OHCI version 1.0, legacy support Apr 2 03:00:13 odie kernel: usb0: SMM does not respond, resetting Apr 2 03:00:13 odie kernel: usb0: on ohci0 Apr 2 03:00:13 odie kernel: usb0: USB revision 1.0 Apr 2 03:00:13 odie kernel: uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Apr 2 03:00:13 odie kernel: uhub0: 4 ports with 4 removable, self powered Apr 2 03:00:13 odie kernel: ohci1: mem 0xff6fe000-0xff6fefff irq 9 at device 2.1 on pci0 Apr 2 03:00:13 odie kernel: usb1: OHCI version 1.0, legacy support Apr 2 03:00:13 odie kernel: usb1: SMM does not respond, resetting Apr 2 03:00:13 odie kernel: usb1: on ohci1 Apr 2 03:00:13 odie kernel: usb1: USB revision 1.0 Apr 2 03:00:13 odie kernel: uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Apr 2 03:00:13 odie kernel: uhub1: 4 ports with 4 removable, self powered Apr 2 03:00:13 odie kernel: pci0: at device 2.2 (no driver attached) Apr 2 03:00:13 odie kernel: pci0: at device 5.0 (no driver attached) Apr 2 03:00:13 odie kernel: pcm0: port 0xe400-0xe47f,0xe800-0xe8ff mem 0xff6fb000-0xff6fbfff irq 4 at device 6.0 on pci0 Apr 2 03:00:13 odie kernel: pcm0: [...] # pciconf -vl [...] agp0@pci0:0:0: class=0x060000 card=0x813f1043 chip=0x00e110de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = bridge subclass = HOST-PCI [...] It seems that your patch can manage nforce3, not nforce3-250. My patch makes nforce3-250 detected, but unfortunately, the system hangs at X startup... so it is not yet usable. Here it is (also attached) : --- src/sys/pci/agp_amd64.c.orig Sat Apr 2 03:37:51 2005 +++ src/sys/pci/agp_amd64.c Sat Apr 2 03:38:16 2005 @@ -82,6 +82,10 @@ return ("AMD 8151 AGP graphics tunnel"); case 0x07551039: return ("SiS 755 host to AGP bridge"); + case 0x00d110de: + return ("nForce3 AGP Host"); + case 0x00e110de: + return ("nForce3 250 AGP Host"); case 0x02041106: return ("VIA 8380 host to PCI bridge"); case 0x02821106: --- src/sys/pci/agp_nvidia.c.orig Sat Apr 2 03:38:03 2005 +++ src/sys/pci/agp_nvidia.c Sat Apr 2 03:40:53 2005 @@ -67,6 +67,8 @@ #define NVIDIA_VENDORID 0x10de #define NVIDIA_DEVICEID_NFORCE 0x01a4 #define NVIDIA_DEVICEID_NFORCE2 0x01e0 +#define NVIDIA_DEVICEID_NFORCE3 0x00d1 +#define NVIDIA_DEVICEID_NFORCE3_250 0x00e1 struct agp_nvidia_softc { struct agp_softc agp; @@ -108,6 +110,10 @@ return ("NVIDIA nForce AGP Controller"); case NVIDIA_DEVICEID_NFORCE2: return ("NVIDIA nForce2 AGP Controller"); + case NVIDIA_DEVICEID_NFORCE3: + return ("NVIDIA nForce3 AGP Controller"); + case NVIDIA_DEVICEID_NFORCE3_250 + return ("NVIDIA nForce3 250 AGP Controller"); } return ("NVIDIA Generic AGP Controller"); } I must be missing something, maybe someone can help in correcting these patches... and finally getting nforce-3 (250) agp support ?!? Thank you, Ganaël LAPLANCHE ganael.laplanche@martymac.com http://www.martymac.com Tel : (+33)6.84.03.57.24. ---------- Original Message ----------- From: Jung-uk Kim To: freebsd-amd64@freebsd.org Cc: "Ganael Laplanche" Sent: Fri, 1 Apr 2005 12:35:05 -0500 Subject: Re: K8N-E deluxe / Nforce3 250 : no agp support yet ? > On Friday 01 April 2005 04:32 am, Ganael Laplanche wrote: > > Hi all, > > > > I'm running 5.4-PRERELEASE #13 for AMD64 and can't get agp working. > > > > My graphic card is an ATI Radeon 9000. Xorg works well, but drm > > can't load because of the lack of agp device. I get these errors > > each time I start X : > > > > # dmesg > > [...] > > error: [drm:pid564:radeon_cp_init] *ERROR* radeon_cp_init called > > without lock held error: [drm:pid564:radeon_unlock] *ERROR* Process > > 564 using kernel context 0 [...] > > > > However, an agp device should be detected ; here is my kernel conf > > file : > > > > [...] > > device acpi > > device isa > > device pci > > device agp > > > > device vga > > device splash > > device radeondrm # ATI Radeon 9000 > > [...] > > > > But no device is detected at boot : > > # dmesg | grep -i agp > > doesn't show anything > > > > Isn't nforce3 250 agp controller supported yet ? > > Try the attached patch. I had it for long time but I forgot to file a > PR. ;-) > > Jung-uk Kim > > > I know I'm not the only one, since I saw a thread on a forum a few > > weeks ago (I can't remember the URL...). I also went to > > http://dri.freedesktop.org/wiki/DriTroubleshooting but without > > success... > > > > Any idea ? Does someone get the same errors ? > > > > Ganaël LAPLANCHE > > ganael.laplanche@martymac.com > > http://www.martymac.com > > Tel : (+33)6.84.03.57.24. ------- End of Original Message ------- ------=OPENWEBMAIL_ATT_0.172811147291213 Content-Type: text/x-patch; name="patch-nvidia.diff" Content-Disposition: attachment; filename="patch-nvidia.diff" Content-Transfer-Encoding: base64 LS0tIHNyYy9zeXMvcGNpL2FncF9hbWQ2NC5jLm9yaWcJU2F0IEFwciAgMiAwMzozNzo1MSAyMDA1 CisrKyBzcmMvc3lzL3BjaS9hZ3BfYW1kNjQuYwlTYXQgQXByICAyIDAzOjM4OjE2IDIwMDUKQEAg LTgyLDYgKzgyLDEwIEBACiAJCXJldHVybiAoIkFNRCA4MTUxIEFHUCBncmFwaGljcyB0dW5uZWwi KTsKIAljYXNlIDB4MDc1NTEwMzk6CiAJCXJldHVybiAoIlNpUyA3NTUgaG9zdCB0byBBR1AgYnJp ZGdlIik7CisJY2FzZSAweDAwZDExMGRlOgorCQlyZXR1cm4gKCJuRm9yY2UzIEFHUCBIb3N0Iik7 CisJY2FzZSAweDAwZTExMGRlOgorCQlyZXR1cm4gKCJuRm9yY2UzIDI1MCBBR1AgSG9zdCIpOwog CWNhc2UgMHgwMjA0MTEwNjoKIAkJcmV0dXJuICgiVklBIDgzODAgaG9zdCB0byBQQ0kgYnJpZGdl Iik7CiAJY2FzZSAweDAyODIxMTA2OgotLS0gc3JjL3N5cy9wY2kvYWdwX252aWRpYS5jLm9yaWcJ U2F0IEFwciAgMiAwMzozODowMyAyMDA1CisrKyBzcmMvc3lzL3BjaS9hZ3BfbnZpZGlhLmMJU2F0 IEFwciAgMiAwMzo0MDo1MyAyMDA1CkBAIC02Nyw2ICs2Nyw4IEBACiAjZGVmaW5lCU5WSURJQV9W RU5ET1JJRAkJMHgxMGRlCiAjZGVmaW5lCU5WSURJQV9ERVZJQ0VJRF9ORk9SQ0UJMHgwMWE0CiAj ZGVmaW5lCU5WSURJQV9ERVZJQ0VJRF9ORk9SQ0UyCTB4MDFlMAorI2RlZmluZQlOVklESUFfREVW SUNFSURfTkZPUkNFMwkweDAwZDEKKyNkZWZpbmUJTlZJRElBX0RFVklDRUlEX05GT1JDRTNfMjUw CTB4MDBlMQogCiBzdHJ1Y3QgYWdwX252aWRpYV9zb2Z0YyB7CiAJc3RydWN0IGFncF9zb2Z0Ywlh Z3A7CkBAIC0xMDgsNiArMTEwLDEwIEBACiAJCXJldHVybiAoIk5WSURJQSBuRm9yY2UgQUdQIENv bnRyb2xsZXIiKTsKIAljYXNlIE5WSURJQV9ERVZJQ0VJRF9ORk9SQ0UyOgogCQlyZXR1cm4gKCJO VklESUEgbkZvcmNlMiBBR1AgQ29udHJvbGxlciIpOworCWNhc2UgTlZJRElBX0RFVklDRUlEX05G T1JDRTM6CisJCXJldHVybiAoIk5WSURJQSBuRm9yY2UzIEFHUCBDb250cm9sbGVyIik7CisJY2Fz ZSBOVklESUFfREVWSUNFSURfTkZPUkNFM18yNTAKKwkJcmV0dXJuICgiTlZJRElBIG5Gb3JjZTMg MjUwIEFHUCBDb250cm9sbGVyIik7CiAJfQogCXJldHVybiAoIk5WSURJQSBHZW5lcmljIEFHUCBD b250cm9sbGVyIik7CiB9Cg== ------=OPENWEBMAIL_ATT_0.172811147291213-- From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 02:03:47 2005 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A0A016A4CE for ; Sat, 2 Apr 2005 02:03:47 +0000 (GMT) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDF7143D45 for ; Sat, 2 Apr 2005 02:03:46 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.3/8.13.1) with ESMTP id j3223dp9009691; Fri, 1 Apr 2005 18:03:39 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.3/8.13.1/Submit) id j3223cuj009690; Fri, 1 Apr 2005 18:03:38 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Ganael Laplanche In-Reply-To: <20050402013119.M28803@martymac.com> References: <20050401090927.M62447@martymac.com> <20050402013119.M28803@martymac.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 01 Apr 2005 18:03:37 -0800 Message-Id: <1112407417.6647.11.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.2.0 FreeBSD GNOME Team Port cc: freebsd-amd64@www.freebsd.org Subject: Re: [PATCH test] K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 02:03:47 -0000 On Sat, 2005-04-02 at 01:53 +0000, Ganael Laplanche wrote: > Hi Kim, > > Thank you very much for you answer. > > I tried your patch, but unfortunately, no agp device was detected... so I > modified it a bit and managed to get this : ... > It seems that your patch can manage nforce3, not nforce3-250. My patch makes > nforce3-250 detected, but unfortunately, the system hangs at X startup... so it > is not yet usable. It looks like more is required than just PCI IDs for nforce3 support. I would recommend anyone interested take a look at the nvidia-agp driver in linux for the process. http://linux.bkbits.net:8080/linux-2.5/anno/drivers/char/agp/amd64-agp.c@1.86?nav=index.html|src/drivers/char/agp From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 04:22:47 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6867116A4CE; Sat, 2 Apr 2005 04:22:47 +0000 (GMT) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F5D43D48; Sat, 2 Apr 2005 04:22:46 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) by mail.jrv.org (8.13.1/8.13.1) with ESMTP id j324Mkgf051585; Fri, 1 Apr 2005 22:22:46 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <424E1E15.1040503@jrv.org> Date: Fri, 01 Apr 2005 22:22:45 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050330222439.GU84137@wantadilla.lemis.com> In-Reply-To: <20050330222439.GU84137@wantadilla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD-amd64@freebsd.org Subject: Re: (no) Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 04:22:47 -0000 Greg 'groggy' Lehey wrote: >I've recently acquired an AMD64 box (dual Opteron 242, SiS Master@-FAR >motherboard I find it very unstable running with 8 >GB memory, though 4 GB are not a problem. > I installed 5.4 beta 1 amd64 on a 8 GB Tyan Thunder K8W with two 244 CPUs. It's been looping on buildworld for about 60 hours, no problems. From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 04:26:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85CCE16A4CE for ; Sat, 2 Apr 2005 04:26:03 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B5543D2D for ; Sat, 2 Apr 2005 04:26:03 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3AC1372DD9; Fri, 1 Apr 2005 20:26:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3618472DCB; Fri, 1 Apr 2005 20:26:03 -0800 (PST) Date: Fri, 1 Apr 2005 20:26:03 -0800 (PST) From: Doug White To: Gary Mu1der In-Reply-To: <424DA4B3.3070703@infotechfl.com> Message-ID: <20050401201907.U95587@carver.gumbysoft.com> References: <424C215E.5080201@infotechfl.com><424C4EED.5070601@infotechfl.com> <424D58F7.1010005@infotechfl.com><424DA4B3.3070703@infotechfl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 04:26:03 -0000 On Fri, 1 Apr 2005, Gary Mu1der wrote: > I have isolated the crash to the following dd command: > > dd if=/dev/mem of=/dev/null bs=1024k skip=4040 count=1 Reading from random places in /dev/mem will cause unpredicatable behavior. Memory at that offset is in PCI memory-mapped device space, and reading from there may disrupt the PCI bridge, enable or disable interrupts, or worse. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 04:53:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B980816A4CE for ; Sat, 2 Apr 2005 04:53:21 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E7CA43D45 for ; Sat, 2 Apr 2005 04:53:21 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so811510rng for ; Fri, 01 Apr 2005 20:53:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=bfCUanIPi0xZEx4LNShC4GPfe/S431jy0MQjlZRFIFZ6BfKxhRrclp4WFKc8eIIRfQ1EMO+MzRbApgFeNFJ7UtSd0gwWh5r8K9B6a/3A/cRshWa0IPi9FvsQ7KHSK5eryIheua2H6Wsm7y0LFEvmONgdxIvuY7yooLvs49IOYdA= Received: by 10.38.12.33 with SMTP id 33mr3424620rnl; Fri, 01 Apr 2005 20:53:20 -0800 (PST) Received: by 10.38.74.23 with HTTP; Fri, 1 Apr 2005 20:53:20 -0800 (PST) Message-ID: Date: Sat, 2 Apr 2005 06:53:20 +0200 From: Gert Cuykens To: freebsd-amd64@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: Subject: Re: Our beloved nforce 3 chipset X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 04:53:21 -0000 On Apr 2, 2005 1:17 AM, Gert Cuykens wrote: > FX-53R kldload /usr/src/sys/modules/sound/driver/ich/snd_ich.ko > > FX-53R kldstat > Id Refs Address Size Name > 1 9 0xffffffff80100000 5b49f0 kernel > 2 1 0xffffffffa75ff000 add4 if_nv.ko > 3 1 0xffffffffa7856000 1cd blank_saver.ko > 4 1 0xffffffffa7924000 227d snd_ich.ko > 5 1 0xffffffffa7927000 12e1a sound.ko > > FX-53R dmesg > ... > pcm0: port 0xe400-0xe47f,0xe800-0xe8ff mem > 0xff6fb000-0xff6fbfff irq 5 at device 6.0 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: cannot reset channel 0 > pcm0: unable to initialize the card > device_attach: pcm0 attach returned 6 > > My sound use to work perfect? I dont know why i get this ? Any idea > how to fix this please ? > i have been testing and testing and testing and this is what made the sound work BUT there is a BUT BIOS ------- AUDIO [ENABLED] IOAPIC [ENABLED] ACPI 2.0 [YES] ACPI-APIC [DISABLED] BIOS-AML-ACPI-TABLE [DISABLED] Now when i did that it made the mixer work but still output errors when doing osstest. So after banging my head on my desk saying why every time my head hit the table. I rembert the only thing i ever did was adding this FX-53R kldstat Id Refs Address Size Name 1 9 0xffffffff80100000 5b49f0 kernel 2 1 0xffffffffa75ff000 add4 if_nv.ko <-------------- 3 1 0xffffffffa7856000 1cd blank_saver.ko 4 1 0xffffffffa7924000 227d snd_ich.ko 5 1 0xffffffffa7927000 12e1a sound.ko As soon as i removed the nvidia netwerk driver kaboom sounds works again. Does anybody know how to fix this and make sound and net driver work togheter ? From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 04:54:34 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADAA616A4CE for ; Sat, 2 Apr 2005 04:54:34 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2552443D3F for ; Sat, 2 Apr 2005 04:54:34 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so811671rng for ; Fri, 01 Apr 2005 20:54:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=TmRAF2FtEJd6FqPTNCuSPgw7bGrh/O1NVw63MpGmISeJNEcu0Aw/9nVngsfqPz7zK97VNVVM82n3Ua4GLbl1orqjZDieeUE4S9zk4Rb5tmZq1RyA+s3qh5fWvoubbhNPrtsJjEZPm6gVsIV3pRCSM+fyCRhab8Srx6fbpTwsrhw= Received: by 10.38.86.68 with SMTP id j68mr3511580rnb; Fri, 01 Apr 2005 20:54:33 -0800 (PST) Received: by 10.38.74.23 with HTTP; Fri, 1 Apr 2005 20:54:33 -0800 (PST) Message-ID: Date: Sat, 2 Apr 2005 06:54:33 +0200 From: Gert Cuykens To: freebsd-amd64@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: Subject: Re: Our beloved nforce 3 chipset X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 04:54:34 -0000 On Apr 2, 2005 6:53 AM, Gert Cuykens wrote: > On Apr 2, 2005 1:17 AM, Gert Cuykens wrote: > > FX-53R kldload /usr/src/sys/modules/sound/driver/ich/snd_ich.ko > > > > FX-53R kldstat > > Id Refs Address Size Name > > 1 9 0xffffffff80100000 5b49f0 kernel > > 2 1 0xffffffffa75ff000 add4 if_nv.ko > > 3 1 0xffffffffa7856000 1cd blank_saver.ko > > 4 1 0xffffffffa7924000 227d snd_ich.ko > > 5 1 0xffffffffa7927000 12e1a sound.ko > > > > FX-53R dmesg > > ... > > pcm0: port 0xe400-0xe47f,0xe800-0xe8ff mem > > 0xff6fb000-0xff6fbfff irq 5 at device 6.0 on pci0 > > pcm0: [GIANT-LOCKED] > > pcm0: cannot reset channel 0 > > pcm0: unable to initialize the card > > device_attach: pcm0 attach returned 6 > > > > My sound use to work perfect? I dont know why i get this ? Any idea > > how to fix this please ? > > > > i have been testing and testing and testing and this is what made the > sound work BUT there is a BUT > > BIOS > ------- > AUDIO [ENABLED] > IOAPIC [ENABLED] > ACPI 2.0 [YES] > ACPI-APIC [DISABLED] > BIOS-AML-ACPI-TABLE [DISABLED] > > Now when i did that it made the mixer work but still output errors > when doing osstest. So after banging my head on my desk saying why > every time my head hit the table. I rembert the only thing i ever did > was adding this > > FX-53R kldstat > Id Refs Address Size Name > 1 9 0xffffffff80100000 5b49f0 kernel > 2 1 0xffffffffa75ff000 add4 if_nv.ko <-------------- > 3 1 0xffffffffa7856000 1cd blank_saver.ko > 4 1 0xffffffffa7924000 227d snd_ich.ko > 5 1 0xffffffffa7927000 12e1a sound.ko > > As soon as i removed the nvidia netwerk driver kaboom sounds works again. > > Does anybody know how to fix this and make sound and net driver work togheter ? > 10$ there is a bug in if_nv.ko :) From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 05:13:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4AF116A4CE for ; Sat, 2 Apr 2005 05:13:27 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA19C43D2F for ; Sat, 2 Apr 2005 05:13:26 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j325DPvo053590; Sat, 2 Apr 2005 00:13:26 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: "Ganael Laplanche" Date: Sat, 2 Apr 2005 00:13:23 -0500 User-Agent: KMail/1.6.2 References: <20050401090927.M62447@martymac.com> <200504011235.05993.jkim@niksun.com> <20050402013119.M28803@martymac.com> In-Reply-To: <20050402013119.M28803@martymac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <200504020013.23514.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/799/Fri Apr 1 05:49:13 2005 on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH test] K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 05:13:27 -0000 On Friday 01 April 2005 08:53 pm, Ganael Laplanche wrote: > Hi Kim, > > Thank you very much for you answer. > > I tried your patch, but unfortunately, no agp device was > detected... so I modified it a bit and managed to get this : --- >8 --- SNIP!!! --- >8 --- > It seems that your patch can manage nforce3, not nforce3-250. My > patch makes nforce3-250 detected, but unfortunately, the system > hangs at X startup... so it is not yet usable. I am sorry. I didn't read your e-mail carefully. Yes, my patch only works with the original nForce3 chipset. > Here it is (also attached) : > > --- src/sys/pci/agp_amd64.c.orig Sat Apr 2 03:37:51 2005 > +++ src/sys/pci/agp_amd64.c Sat Apr 2 03:38:16 2005 > @@ -82,6 +82,10 @@ > return ("AMD 8151 AGP graphics tunnel"); > case 0x07551039: > return ("SiS 755 host to AGP bridge"); > + case 0x00d110de: > + return ("nForce3 AGP Host"); > + case 0x00e110de: > + return ("nForce3 250 AGP Host"); > case 0x02041106: > return ("VIA 8380 host to PCI bridge"); > case 0x02821106: This is okay. > --- src/sys/pci/agp_nvidia.c.orig Sat Apr 2 03:38:03 2005 > +++ src/sys/pci/agp_nvidia.c Sat Apr 2 03:40:53 2005 > @@ -67,6 +67,8 @@ > #define NVIDIA_VENDORID 0x10de > #define NVIDIA_DEVICEID_NFORCE 0x01a4 > #define NVIDIA_DEVICEID_NFORCE2 0x01e0 > +#define NVIDIA_DEVICEID_NFORCE3 0x00d1 > +#define NVIDIA_DEVICEID_NFORCE3_250 0x00e1 > > struct agp_nvidia_softc { > struct agp_softc agp; > @@ -108,6 +110,10 @@ > return ("NVIDIA nForce AGP Controller"); > case NVIDIA_DEVICEID_NFORCE2: > return ("NVIDIA nForce2 AGP Controller"); > + case NVIDIA_DEVICEID_NFORCE3: > + return ("NVIDIA nForce3 AGP Controller"); > + case NVIDIA_DEVICEID_NFORCE3_250 > + return ("NVIDIA nForce3 250 AGP Controller"); > } > return ("NVIDIA Generic AGP Controller"); > } This is not because you cannot attach the same device from two different drivers. You have to use my previous patch here. > I must be missing something, maybe someone can help in correcting > these patches... and finally getting nforce-3 (250) agp support ?!? Maybe but I have no hardware to test. :-( JK > Thank you, > > Ganaël LAPLANCHE > ganael.laplanche@martymac.com > http://www.martymac.com > Tel : (+33)6.84.03.57.24. --- >8 --- SNIP!!! --- >8 --- From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 05:19:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1BE616A4CE for ; Sat, 2 Apr 2005 05:19:46 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 371DE43D48 for ; Sat, 2 Apr 2005 05:19:46 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j325Ji1I053680; Sat, 2 Apr 2005 00:19:45 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Sat, 2 Apr 2005 00:19:43 -0500 User-Agent: KMail/1.6.2 References: <20050401090927.M62447@martymac.com> <20050402013119.M28803@martymac.com> <1112407417.6647.11.camel@leguin> In-Reply-To: <1112407417.6647.11.camel@leguin> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200504020019.43594.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/799/Fri Apr 1 05:49:13 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: [PATCH test] K8N-E deluxe / Nforce3 250 : no agp support yet ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 05:19:46 -0000 On Friday 01 April 2005 09:03 pm, Eric Anholt wrote: > On Sat, 2005-04-02 at 01:53 +0000, Ganael Laplanche wrote: > > Hi Kim, > > > > Thank you very much for you answer. > > > > I tried your patch, but unfortunately, no agp device was > > detected... so I modified it a bit and managed to get this : > > ... > > > It seems that your patch can manage nforce3, not nforce3-250. My > > patch makes nforce3-250 detected, but unfortunately, the system > > hangs at X startup... so it is not yet usable. > > It looks like more is required than just PCI IDs for nforce3 > support. I would recommend anyone interested take a look at the > nvidia-agp driver in linux for the process. My patch worked fine for nForce3. I just don't have nForce3 250. > http://linux.bkbits.net:8080/linux-2.5/anno/drivers/char/agp/amd64- >agp.c@1.86?nav=index.html|src/drivers/char/agp That's interesting. However, I don't have hardware or document to verify. :-( Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 06:01:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54DF216A4CE for ; Sat, 2 Apr 2005 06:01:06 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F9143D54 for ; Sat, 2 Apr 2005 06:01:05 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1034807wra for ; Fri, 01 Apr 2005 22:01:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ik6vHXikHkydTXLnDL5rdvlDcc2Yhda8ddP6EH7OMHDFAaO6WIbNNDXyFde7EhtLxvXpOl3O+K/BecaPprOSGTm00lzZjl7QkiG1fXKXT5vxqZXtDuIbT2SfORQs+iMcQ0rTKeMl8xND3Ha+uvova3LvK9jUr6sOKOK05J7Lu0U= Received: by 10.54.52.76 with SMTP id z76mr959825wrz; Fri, 01 Apr 2005 22:01:04 -0800 (PST) Received: by 10.54.40.69 with HTTP; Fri, 1 Apr 2005 22:01:04 -0800 (PST) Message-ID: <2fd864e05040122013d8fd812@mail.gmail.com> Date: Fri, 1 Apr 2005 22:01:04 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050401201907.U95587@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> <424D58F7.1010005@infotechfl.com> <424DA4B3.3070703@infotechfl.com> <20050401201907.U95587@carver.gumbysoft.com> Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 06:01:06 -0000 On Apr 1, 2005 8:26 PM, Doug White wrote: > On Fri, 1 Apr 2005, Gary Mu1der wrote: > > > I have isolated the crash to the following dd command: > > > > dd if=/dev/mem of=/dev/null bs=1024k skip=4040 count=1 > > Reading from random places in /dev/mem will cause unpredicatable behavior. > Memory at that offset is in PCI memory-mapped device space, and reading > from there may disrupt the PCI bridge, enable or disable interrupts, or > worse. > > -- I think the basic idea here is that dd'ing from /dev/mem may or may not work, on any given hardware, and is certainly not reccomended. If you want to test this "Safely", do an mdconfig, and dd onto, or from the md device. From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 08:19:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BD3D16A4CE; Sat, 2 Apr 2005 08:19:27 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDDDE43D3F; Sat, 2 Apr 2005 08:19:25 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j328JJka005884; Sat, 2 Apr 2005 10:19:19 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j328JQmh074530; Sat, 2 Apr 2005 10:19:26 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j328JQk1074529; Sat, 2 Apr 2005 10:19:26 +0200 (CEST) (envelope-from ftigeot) Date: Sat, 2 Apr 2005 10:19:26 +0200 From: Francois Tigeot To: "David O'Brien" Message-ID: <20050402081925.GB38154@aoi.wolfpond.org> References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> <20050401055721.GA72973@aoi.wolfpond.org> <20050402011541.GA33607@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050402011541.GA33607@dragon.NUXI.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 08:19:27 -0000 On Fri, Apr 01, 2005 at 05:15:41PM -0800, David O'Brien wrote: > On Fri, Apr 01, 2005 at 07:57:21AM +0200, Francois Tigeot wrote: > > This one can be fixed by the patch in this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79009 > > The patch isn't quite right -- don't [re]define MACHINE_ARCH, change any > instance of "MACHINE_ARCH" to "ARCH". This part is for graphics/linux-jpeg. This port includes the Makefile of x11-toolkits/linux-gtk instead of bsd.port.{post|pre}.mk . With the current port, MACHINE_ARCH is defined and ARCH is not. I believe ARCH is defined in bsd.port.pre.mk. Since bsd.port.pre.mk cannot be included twice, I would need to copy most of the content of x11-toolkits/linux-gtk/Makefile into linux-jpeg/Makefile just to use the ARCH variable. I would like to avoid this if there is a better way. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 09:11:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C79D16A4E3 for ; Sat, 2 Apr 2005 09:11:23 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7037E43D46 for ; Sat, 2 Apr 2005 09:11:22 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1050459wra for ; Sat, 02 Apr 2005 01:11:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=QeHzhMkIa43b0LaVFH+bTUCTkKI/ijlvBKUxm9NjW2DD6JETcJahiOTVxX3veYodpW24cb9dwanrd/JljY19VuwCqKY6MnlyuJ1MTisBuThywrkd19p6J1YHMchNeiJeXPgntz345qqyNN+mdM5UxUiHzReFqUgybVmEvh8yn5o= Received: by 10.54.35.35 with SMTP id i35mr1431403wri; Sat, 02 Apr 2005 01:11:19 -0800 (PST) Received: by 10.54.40.69 with HTTP; Sat, 2 Apr 2005 01:11:19 -0800 (PST) Message-ID: <2fd864e05040201113b8ab644@mail.gmail.com> Date: Sat, 2 Apr 2005 01:11:19 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050402081925.GB38154@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <790a9fff050331080572081eb6@mail.gmail.com> <2fd864e05033109061a68554d@mail.gmail.com> <20050331203915.GH1687@dragon.NUXI.org> <20050331155046.21a5d323@dolphin.local.net> <20050401055721.GA72973@aoi.wolfpond.org> <20050402011541.GA33607@dragon.NUXI.org> <20050402081925.GB38154@aoi.wolfpond.org> Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 09:11:23 -0000 On Apr 2, 2005 12:19 AM, Francois Tigeot wrote: > On Fri, Apr 01, 2005 at 05:15:41PM -0800, David O'Brien wrote: > > On Fri, Apr 01, 2005 at 07:57:21AM +0200, Francois Tigeot wrote: > > > This one can be fixed by the patch in this PR: > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79009 > > > > The patch isn't quite right -- don't [re]define MACHINE_ARCH, change any > > instance of "MACHINE_ARCH" to "ARCH". > > This part is for graphics/linux-jpeg. This port includes the Makefile of > x11-toolkits/linux-gtk instead of bsd.port.{post|pre}.mk . > > With the current port, MACHINE_ARCH is defined and ARCH is not. > I believe ARCH is defined in bsd.port.pre.mk. > > Since bsd.port.pre.mk cannot be included twice, I would need to copy most > of the content of x11-toolkits/linux-gtk/Makefile into linux-jpeg/Makefile > just to use the ARCH variable. > > I would like to avoid this if there is a better way. > > -- > Francois Tigeot > _______________________________________________ > 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" > I'm going to try making all Linux compat ports AMD64 capible over the next few weeks. Since we have Linux32 compat, this shouldn't be a problem, and ports that don't work seem to be a special case, as opposed to the general rule. How should I submit the diff for this, and how should I report ports that don't work in this scenario? From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 10:12:47 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53E6F16A4CE for ; Sat, 2 Apr 2005 10:12:47 +0000 (GMT) Received: from web30707.mail.mud.yahoo.com (web30707.mail.mud.yahoo.com [68.142.200.140]) by mx1.FreeBSD.org (Postfix) with SMTP id EA3FF43D3F for ; Sat, 2 Apr 2005 10:12:46 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 61944 invoked by uid 60001); 2 Apr 2005 10:12:46 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=yaE0lwk0RWjVUby6L9gQ6rG+5CGAh96vD8KHptDLvjTxQROwpuxBS4OTTqlR3tW5mD0ZUq7K/uW6hRiwnfrp0tauI+Udepuq8+Mzj6PM8l+6Cnbkn/gSQNDx5X3rXy/wd0uCtnJfW7AJI1B39KyEBP3n+pzom07Jd30S7tywVMY= ; Message-ID: <20050402101246.61942.qmail@web30707.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30707.mail.mud.yahoo.com via HTTP; Sat, 02 Apr 2005 02:12:46 PST Date: Sat, 2 Apr 2005 02:12:46 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Dumb R3000Z / zv5000 questions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 10:12:47 -0000 Thank you for the detailed explanation. -N --- Bruno Ducrot wrote: > On Thu, Mar 31, 2005 at 10:47:19PM -0800, Neil Short > wrote: > > 1) are there any instructions on how to use the > powerd > > > (http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/powerd/) > > or the powernow tools? It's not intuitive to me. > > > for -current, just kldload cpufreq, or compile > kernel with > device cpufreq > then you can configure powerd via /etc/rc.conf > for RELENG_5, specific low level drivers are not yet > been MFC, > but the cpufreq infrastucture is. So you have to do > something > like that in the time beeing: > On, say, $HOME/cpufreq, > > cvs co src/sys/dev/acpica/acpi_perf.c > cvs co -P src/sys/dev/cpufreq > cvs co -P src/sys/i386/cpufreq > cvs co -P src/usr.sbin/powerd > mkdir acpi_perf > cp src/sys/dev/acpica/acpi_perf.c acpi_perf > cp -r src/sys/i386/cpufreq . > cp src/sys/dev/cpufreq/ichss.c cpufreq > cp -r src/usr.sbin/powerd . > > Then modify or add some Makefile: > > I'm using the following: > cat Makefile > SUBDIR = acpi_perf cpufreq powerd > > .include > > > cat acpi_perf/Makefile > CFLAGS+= -I@/contrib/dev/acpica > > KMOD= acpi_perf > WARNS?= 2 > SRCS= acpi_perf.c > SRCS+= acpi_if.h bus_if.h cpufreq_if.h > device_if.h opt_acpi.h \ > pci_if.h > > .include > cat cpufreq/Makefile > KMOD= cpufreq > SRCS= est.c ichss.c p4tcc.c powernow.c > SRCS+= bus_if.h cpufreq_if.h device_if.h > > .include > > I also have to modify a little the Makefile for > powerd as such: > # $FreeBSD: src/usr.sbin/powerd/Makefile,v 1.2 > 2005/02/26 22:50:25 njl > # Exp $ > > PROG= powerd > MAN= powerd.8 > WARNS?= 6 > > BINDIR= /usr/sbin > > .include > > > Then do a make followed by a make install. > > You can then, in order: > kldload acpi_perf > kldload cpufreq > > and launch powerd(8) with option '-v' for testing > purpose. > > 1a) Does it work with the XP-M (32 bit) processor? > > Yes > > > > > 2) what is the recommended sound module for this > > equipment? I know this was answered somewhere > before > > but I sure can't find it. > > Don't know. > > Cheers, > > -- > Bruno Ducrot > > -- Which is worse: ignorance or apathy? > -- Don't know. Don't care. > If history always begins this morning, the world holds exciting surprises around every corner (241). --Ann Coulter. Treason. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 18:32:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 616D316A4CE; Sat, 2 Apr 2005 18:32:01 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6761F43D2F; Sat, 2 Apr 2005 18:32:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j32IVxQ8072460; Sat, 2 Apr 2005 13:31:59 -0500 (EST) (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.1/8.13.1) with ESMTP id j32IVxSo058872; Sat, 2 Apr 2005 13:31:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 84CBE7306E; Sat, 2 Apr 2005 13:31:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050402183159.84CBE7306E@freebsd-current.sentex.ca> Date: Sat, 2 Apr 2005 13:31:59 -0500 (EST) X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 18:32:01 -0000 TB --- 2005-04-02 16:48:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-02 16:48:09 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-02 16:48:09 - checking out the source tree TB --- 2005-04-02 16:48:09 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-02 16:48:09 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-02 16:55:05 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-02 16:55:05 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-02 16:55:05 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-04-02 18:04:18 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-02 18:04:18 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-02 18:04:18 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Apr 2 18:04:19 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Apr 2 18:19:53 UTC 2005 TB --- 2005-04-02 18:19:53 - generating LINT kernel config TB --- 2005-04-02 18:19:53 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-02 18:19:53 - /usr/bin/make -B LINT TB --- 2005-04-02 18:19:53 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-02 18:19:53 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-02 18:19:53 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Apr 2 18:19:53 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/compat/freebsd32/freebsd32_sysent.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/compat/ia32/ia32_sysvec.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/kern/imgact_elf32.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/amd64/linux32/linux32_dummy.c cc -c -x assembler-with-cpp -DLOCORE -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -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 -ffreestandin g -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/linux32/linux32_locore.s cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/amd64/linux32/linux32_machdep.c /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/linux32/linux32_machdep.c: In function `linux_mmap': /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/linux32/linux32_machdep.c:593: error: structure has no member named `pos' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-02 18:31:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-02 18:31:59 - ERROR: failed to build lint kernel TB --- 2005-04-02 18:31:59 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 21:01:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D24CD16A4CE; Sat, 2 Apr 2005 21:01:14 +0000 (GMT) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 839D243D45; Sat, 2 Apr 2005 21:01:14 +0000 (GMT) (envelope-from marquis@roble.com) Date: Sat, 2 Apr 2005 13:01:14 -0800 (PST) From: Roger Marquis To: freebsd-amd64@freebsd.org In-Reply-To: <20050402120023.3E94F16A4D1@hub.freebsd.org> Message-ID: <20050402125456.B5092@roble.com> References: <20050402120023.3E94F16A4D1@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-scsi@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 21:01:15 -0000 Gary Mu1der wrote: >Any idea how we can get more diagnostics on what in FreeBSD is causing >the crash? This wasn't a U320 SCSI system by any chance? The reason I ask is that it is very similar to problem a few months ago, on a Tyan S2881, which turned out to be pci-x bus related. Have also seen similar/identical issues with other Tyan boards when used with U320 SCSI controllers. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ >>From: Ramberto Cumagun >>Cc: Patricia Jadrich , >> Anton Rajakoone , Randy Arruda , >> Chuck Bartlett >>Subject: S2881 / Adaptec 2200S issue >>Date: Tue, 14 Sep 2004 12:09:33 -0700 >> >> >>Purpose of this email is to notify you that we have verified the >>compatibility issue with Tyan S2881 and Adaptec 2200S. Root cause seems >>to be timing margin issue with the AMD8131 PCI-X bus. There is an ECN >>that addresses this issue which has been implemented on the S2881 based >>system that was delivered to Tyan Fremont. With this ECN stability has, >>so far, improved though the testings are not yet complete. Results of >>this testing should be done within the next few days. From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 2 23:30:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB74C16A4CE for ; Sat, 2 Apr 2005 23:30:32 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BE543D2D for ; Sat, 2 Apr 2005 23:30:32 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id BBF4272DE9; Sat, 2 Apr 2005 15:30:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id BA43172DD9; Sat, 2 Apr 2005 15:30:32 -0800 (PST) Date: Sat, 2 Apr 2005 15:30:32 -0800 (PST) From: Doug White To: Roger Marquis In-Reply-To: <20050402125456.B5092@roble.com> Message-ID: <20050402152215.B1503@carver.gumbysoft.com> References: <20050402120023.3E94F16A4D1@hub.freebsd.org> <20050402125456.B5092@roble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: Tyan k8sr lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 23:30:33 -0000 Dropping scsi cc as this isn't specifically scsi related On Sat, 2 Apr 2005, Roger Marquis wrote: > Gary Mu1der wrote: > >Any idea how we can get more diagnostics on what in FreeBSD is causing > >the crash? > > This wasn't a U320 SCSI system by any chance? The reason I ask is > that it is very similar to problem a few months ago, on a Tyan > S2881, which turned out to be pci-x bus related. Have also seen > similar/identical issues with other Tyan boards when used with U320 > SCSI controllers. 3ware cards have a similar issue and 3ware recommends 1U riser cards with components onboard to mitigate timing and signal loss issues if the system has hang/lockup or mysterious disk failures. The ordering information I have is: Adex P/N: PCITX8-3R (be sure and ask for the R part) Cheryl Roberts Tel: 949-597-1772 Fax: 949-597-1729 Email: cheryl@adexelec.com http://www.adexelec.com >From tyan 9/2004: > >>Purpose of this email is to notify you that we have verified the > >>compatibility issue with Tyan S2881 and Adaptec 2200S. Root cause seems > >>to be timing margin issue with the AMD8131 PCI-X bus. There is an ECN > >>that addresses this issue which has been implemented on the S2881 based > >>system that was delivered to Tyan Fremont. With this ECN stability has, > >>so far, improved though the testings are not yet complete. Results of > >>this testing should be done within the next few days. Good to know. It may be beneficial to start tracking motherboard revisions. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org