From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:18:26 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C57916A407; Sun, 8 Oct 2006 17:18:26 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A546643D49; Sun, 8 Oct 2006 17:18:25 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98HIPY4058230; Sun, 8 Oct 2006 17:18:25 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98HIPfT058226; Sun, 8 Oct 2006 17:18:25 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 17:18:25 GMT From: Ceri Davies Message-Id: <200610081718.k98HIPfT058226@freefall.freebsd.org> To: winmyint@mail.ru, ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/87328: [boot] BTX halted error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:18:26 -0000 Synopsis: [boot] BTX halted error State-Changed-From-To: analyzed->closed State-Changed-By: ceri State-Changed-When: Sun Oct 8 17:16:46 UTC 2006 State-Changed-Why: Feedback timeout, and popssibly an attempt to boot the amd64 distribution on non-amd64 hardware. http://www.freebsd.org/cgi/query-pr.cgi?pr=87328 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:20:46 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8820A16A407; Sun, 8 Oct 2006 17:20:46 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F09F43D49; Sun, 8 Oct 2006 17:20:46 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98HKkC4058988; Sun, 8 Oct 2006 17:20:46 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98HKkQx058984; Sun, 8 Oct 2006 17:20:46 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 17:20:46 GMT From: Ceri Davies Message-Id: <200610081720.k98HKkQx058984@freefall.freebsd.org> To: maho@FreeBSD.org, ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:20:46 -0000 Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD State-Changed-From-To: open->closed State-Changed-By: ceri State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 State-Changed-Why: ULE is no longer the default scheduler, and no longer has a maintainer. This is an interesting test case though. Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: ceri Responsible-Changed-When: Sun Oct 8 17:19:36 UTC 2006 Responsible-Changed-Why: Scheduler problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=85820 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:29:08 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F62916A47C; Sun, 8 Oct 2006 17:29:08 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D70B143D78; Sun, 8 Oct 2006 17:29:02 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98HT2Ya059435; Sun, 8 Oct 2006 17:29:02 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98HT29H059431; Sun, 8 Oct 2006 17:29:02 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 17:29:02 GMT From: Ceri Davies Message-Id: <200610081729.k98HT29H059431@freefall.freebsd.org> To: ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: Subject: Re: docs/102148: The description of which Intel chips have EM64T is out of date X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:29:08 -0000 Synopsis: The description of which Intel chips have EM64T is out of date Responsible-Changed-From-To: freebsd-amd64->freebsd-doc Responsible-Changed-By: ceri Responsible-Changed-When: Sun Oct 8 17:28:20 UTC 2006 Responsible-Changed-Why: Docs pr, one for a mamber of re, please. http://www.freebsd.org/cgi/query-pr.cgi?pr=102148 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:30:33 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21B5116A415 for ; Sun, 8 Oct 2006 17:30:33 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F26B43D5D for ; Sun, 8 Oct 2006 17:30:32 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98HUVlZ059666 for ; Sun, 8 Oct 2006 17:30:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98HUVQc059664; Sun, 8 Oct 2006 17:30:31 GMT (envelope-from gnats) Date: Sun, 8 Oct 2006 17:30:31 GMT Message-Id: <200610081730.k98HUVQc059664@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Astrodog Cc: Subject: Re: amd64/102975: NIC unknown X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Oct 2006 17:30:33 -0000 The following reply was made to PR amd64/102975; it has been noted by GNATS. From: Astrodog To: bug-followup@FreeBSD.org, Morten.Gulbrandsen@rwth-Aachen.de Cc: Subject: Re: amd64/102975: NIC unknown Date: Sun, 8 Oct 2006 12:24:54 -0500 Can you please send the output of pciconf -l -v and dmesg? From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:33:59 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1884016A416; Sun, 8 Oct 2006 17:33:59 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A51243D49; Sun, 8 Oct 2006 17:33:58 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98HXw0H061455; Sun, 8 Oct 2006 17:33:58 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98HXvBb061451; Sun, 8 Oct 2006 17:33:57 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 17:33:57 GMT From: Ceri Davies Message-Id: <200610081733.k98HXvBb061451@freefall.freebsd.org> To: Morten.Gulbrandsen@rwth-Aachen.de, ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/102975: NIC unknown X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:33:59 -0000 Synopsis: NIC unknown State-Changed-From-To: open->feedback State-Changed-By: ceri State-Changed-When: Sun Oct 8 17:32:54 UTC 2006 State-Changed-Why: It's very unclear what the actual problem was here. Could you please let us know where *you* were having difficulties? http://www.freebsd.org/cgi/query-pr.cgi?pr=102975 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:51:54 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C9516A40F; Sun, 8 Oct 2006 17:51:54 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate01.zdv.uni-mainz.de (mailgate01.zdv.Uni-Mainz.DE [134.93.178.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EAF943D46; Sun, 8 Oct 2006 17:51:52 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront02.zdv.uni-mainz.de ([134.93.176.56]) by mailgate01.zdv.uni-mainz.de with ESMTP; 08 Oct 2006 19:51:52 +0200 Received: from mail.uni-mainz.de ([134.93.176.56]) by exfront02.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Sun, 8 Oct 2006 19:51:52 +0200 Received: from [192.168.1.128] ([85.178.18.39] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sun, 8 Oct 2006 19:51:51 +0200 Message-ID: <45293AAD.9090205@mail.uni-mainz.de> Date: Sun, 08 Oct 2006 19:51:41 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Ceri Davies References: <200610081720.k98HKkQx058984@freefall.freebsd.org> In-Reply-To: <200610081720.k98HKkQx058984@freefall.freebsd.org> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Oct 2006 17:51:51.0885 (UTC) FILETIME=[6F721FD0:01C6EB02] Cc: maho@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:51:54 -0000 Ceri Davies wrote: > Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD > > State-Changed-From-To: open->closed > State-Changed-By: ceri > State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > State-Changed-Why: > ULE is no longer the default scheduler, and no longer has a maintainer. > This is an interesting test case though. > > > Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs > Responsible-Changed-By: ceri > Responsible-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > Responsible-Changed-Why: > Scheduler problem. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=85820 > _______________________________________________ > 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" > Very interesting to read. And this is now the end of the newly introduced allround weapon for more scalability? From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:54:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5272016A697; Sun, 8 Oct 2006 17:54:58 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC4743D62; Sun, 8 Oct 2006 17:54:55 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id k98HsrHE089102; Sun, 8 Oct 2006 21:54:53 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Sun, 8 Oct 2006 21:54:53 +0400 (MSD) From: Maxim Konovalov To: Ceri Davies In-Reply-To: <200610081720.k98HKkQx058984@freefall.freebsd.org> Message-ID: <20061008215308.W89071@mp2.macomnet.net> References: <200610081720.k98HKkQx058984@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: maho@freebsd.org, freebsd-bugs@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:54:58 -0000 On Sun, 8 Oct 2006, 17:20-0000, Ceri Davies wrote: > Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD > > State-Changed-From-To: open->closed > State-Changed-By: ceri > State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > State-Changed-Why: > ULE is no longer the default scheduler, and no longer has a maintainer. > This is an interesting test case though. I think better mark ULE bugs as suspended. I have plans to take them over. -- Maxim Konovalov From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 17:59:02 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDD9716A407; Sun, 8 Oct 2006 17:59:02 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F8043D46; Sun, 8 Oct 2006 17:59:02 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GWcvV-000ONB-9u; Sun, 08 Oct 2006 18:59:01 +0100 Date: Sun, 8 Oct 2006 18:59:01 +0100 From: Ceri Davies To: "O. Hartmann" Message-ID: <20061008175901.GW21333@submonkey.net> Mail-Followup-To: Ceri Davies , "O. Hartmann" , maho@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org References: <200610081720.k98HKkQx058984@freefall.freebsd.org> <45293AAD.9090205@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="su+CkryO4QJrkqP3" Content-Disposition: inline In-Reply-To: <45293AAD.9090205@mail.uni-mainz.de> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Ceri Davies Cc: maho@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 17:59:02 -0000 --su+CkryO4QJrkqP3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 08, 2006 at 07:51:41PM +0200, O. Hartmann wrote: > Ceri Davies wrote: > > Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD > > > > State-Changed-From-To: open->closed > > State-Changed-By: ceri > > State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > > State-Changed-Why:=20 > > ULE is no longer the default scheduler, and no longer has a maintainer. > > This is an interesting test case though. > > > > > > Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs > > Responsible-Changed-By: ceri > > Responsible-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > > Responsible-Changed-Why:=20 > > Scheduler problem. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D85820 > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > =20 > Very interesting to read. And this is now the end of the newly > introduced allround weapon for more scalability? There is some one working on SCHED_ULE, but they are not a committer and they suggested that this PR could be closed. It contains an interesting test case but no real problem as such, only that one scheduler is slower that the other for certain loads. That is always going to be true. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --su+CkryO4QJrkqP3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFKTxlocfcwTS3JF8RApnrAKC+eJAQRg7/bj0ZRmstY9usXPqS9gCgiqt4 8FtuLC7jNeJsYUkNytR2py8= =dfZK -----END PGP SIGNATURE----- --su+CkryO4QJrkqP3-- From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 18:01:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAA8016A412; Sun, 8 Oct 2006 18:01:22 +0000 (UTC) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-0-0-cust107.cdif.cable.ntl.com [81.104.168.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5D6E43D55; Sun, 8 Oct 2006 18:01:21 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GWcxk-000AHE-LB; Sun, 08 Oct 2006 19:01:20 +0100 Date: Sun, 8 Oct 2006 19:01:20 +0100 From: Ceri Davies To: Maxim Konovalov Message-ID: <20061008180120.GX21333@submonkey.net> Mail-Followup-To: Ceri Davies , Maxim Konovalov , maho@freebsd.org, freebsd-amd64@freebsd.org, freebsd-bugs@freebsd.org References: <200610081720.k98HKkQx058984@freefall.freebsd.org> <20061008215308.W89071@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7d9k4kQHj3EPdFyS" Content-Disposition: inline In-Reply-To: <20061008215308.W89071@mp2.macomnet.net> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Ceri Davies Cc: maho@freebsd.org, freebsd-bugs@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 18:01:22 -0000 --7d9k4kQHj3EPdFyS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 08, 2006 at 09:54:53PM +0400, Maxim Konovalov wrote: > On Sun, 8 Oct 2006, 17:20-0000, Ceri Davies wrote: >=20 > > Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD > > > > State-Changed-From-To: open->closed > > State-Changed-By: ceri > > State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 > > State-Changed-Why: > > ULE is no longer the default scheduler, and no longer has a maintainer. > > This is an interesting test case though. >=20 > I think better mark ULE bugs as suspended. I have plans to take them > over. I don't intend to sweep them all. I just didn't see a problem statement in this PR, and figured that it was due to the fact that ULE was default at the time the PR was raised. Feel free to reopen it if you disagree. Ceri --=20 That must be wonderful! I don't understand it at all. -- Moliere --7d9k4kQHj3EPdFyS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFKTzwocfcwTS3JF8RAn8JAJ0Y06NqI0yDOr/YFLSsAO//ldtSigCcCvw6 9WwNv8cjuH4CC7y1aTWo1X4= =TjpD -----END PGP SIGNATURE----- --7d9k4kQHj3EPdFyS-- From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 18:25:43 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01C2C16A40F; Sun, 8 Oct 2006 18:25:43 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD11143D45; Sun, 8 Oct 2006 18:25:42 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98IPgCw065130; Sun, 8 Oct 2006 18:25:42 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98IPgXZ065126; Sun, 8 Oct 2006 18:25:42 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 18:25:42 GMT From: Ceri Davies Message-Id: <200610081825.k98IPgXZ065126@freefall.freebsd.org> To: pasky.org@gmail.com, ceri@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/85273: FreeBSD (NetBSD or OpenBSD) not install on laptop Compaq R4000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 18:25:43 -0000 Synopsis: FreeBSD (NetBSD or OpenBSD) not install on laptop Compaq R4000 State-Changed-From-To: open->suspended State-Changed-By: ceri State-Changed-When: Sun Oct 8 18:24:14 UTC 2006 State-Changed-Why: I'm told this is unfixable. There is a workaround which Harrison Grundy is going to send me, and we'll try to get it in the release notes. Responsible-Changed-From-To: freebsd-i386->freebsd-amd64 Responsible-Changed-By: ceri Responsible-Changed-When: Sun Oct 8 18:24:14 UTC 2006 Responsible-Changed-Why: AMD64 PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=85273 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 8 18:26:03 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B20E16A403; Sun, 8 Oct 2006 18:26:03 +0000 (UTC) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 482AA43D46; Sun, 8 Oct 2006 18:26:03 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k98IQ3QT065181; Sun, 8 Oct 2006 18:26:03 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k98IQ3J5065177; Sun, 8 Oct 2006 18:26:03 GMT (envelope-from ceri) Date: Sun, 8 Oct 2006 18:26:03 GMT From: Ceri Davies Message-Id: <200610081826.k98IQ3J5065177@freefall.freebsd.org> To: ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org, ceri@FreeBSD.org Cc: Subject: Re: amd64/85273: FreeBSD (NetBSD or OpenBSD) not install on laptop Compaq R4000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 18:26:03 -0000 Synopsis: FreeBSD (NetBSD or OpenBSD) not install on laptop Compaq R4000 Responsible-Changed-From-To: freebsd-amd64->ceri Responsible-Changed-By: ceri Responsible-Changed-When: Sun Oct 8 18:25:46 UTC 2006 Responsible-Changed-Why: To me, rather. http://www.freebsd.org/cgi/query-pr.cgi?pr=85273 From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 9 11:09:21 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AC9A16A4C8 for ; Mon, 9 Oct 2006 11:09:21 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F05B043DAB for ; Mon, 9 Oct 2006 11:08:33 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k99B8ICC071446 for ; Mon, 9 Oct 2006 11:08:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k99B8Gxm071442 for freebsd-amd64@FreeBSD.org; Mon, 9 Oct 2006 11:08:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Oct 2006 11:08:16 GMT Message-Id: <200610091108.k99B8Gxm071442@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 11:09:21 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/73775 amd64 Kernel panic (trap 12) when booting with (not from!) P o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Trap 12: Page fa o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not work on amd64 o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/84930 amd64 [msdosfs] something wrong with msdosfs on amd64 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on AMD64 archit o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88299 amd64 swapcontext fails with errno 0 f amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. o amd64/103918 amd64 LSI 53C1030 SCSI controller timing out on mpt driver o amd64/104123 amd64 libglade fails to build o amd64/104125 amd64 libglade fails to build, breaks gimp build and others. 62 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu o amd64/85812 amd64 "Rebooting..." on serial console appears garbled o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/92527 amd64 [ciphy.c] no driver for "CICADA VSC 8201 Gigabit LAN P o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out f amd64/98346 amd64 [kbd] caps lock and other keys are always illuminated o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100348 amd64 No hardware support: Marvell 88E8053 Yukon PCI-E Gigab o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 24 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 9 16:00:38 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA80216A415 for ; Mon, 9 Oct 2006 16:00:38 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6939343D46 for ; Mon, 9 Oct 2006 16:00:37 +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 276DDB80F for ; Mon, 9 Oct 2006 12:00:36 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <20060303133844.451cb4f7.kgunders@teamcool.net> <200603031343.10334.fcash@ocis.net> <20060305123941.4a890a73.kgunders@teamcool.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-10--433675753; protocol="application/pkcs7-signature" Message-Id: <28EB4EFA-E21E-45B2-ABBD-8402F7E0F034@khera.org> From: Vivek Khera Date: Mon, 9 Oct 2006 12:00:33 -0400 To: FreeBSD AMD list X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dell U320 disk array (was Re: major pita w/LSI Tyan TA26 combo) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 16:00:38 -0000 --Apple-Mail-10--433675753 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Mar 6, 2006, at 10:41 AM, Vivek Khera wrote: >>> From myunderstanding from talking to LSI support Adaptec cards will >> automatically drop to U160 if they can't keep up w/U320?? > > they told me this too. however, if i query the card with aaccli, > it reports every device is running at 320 speed. So someone/ > something is not entirely truthful. Following up from an ancient thread... for the archives: Last week, the Adaptec card reported some drives on the Dell enclosure as "missing" or failed. Pulling them out and putting them back in brought them back to life nicely, except they all reported in at U160 speed instead of U320. Once rebuild was complete, a reboot resulted in all drives showing up again as U320. I'm placing blame squarely on the enclosure now. I do not believe it is truly up to full U320 spec. Even after replacing the backplane, etc. Dell claims otherwise, naturally. Guess what *I* won't be buying ever again. --Apple-Mail-10--433675753-- From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 9 17:46:26 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 429E016A416 for ; Mon, 9 Oct 2006 17:46:26 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B88A643D45 for ; Mon, 9 Oct 2006 17:46:23 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k99HkJel071887; Mon, 9 Oct 2006 13:46:19 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-amd64@FreeBSD.org, John-Mark Gurney Date: Mon, 9 Oct 2006 13:45:57 -0400 User-Agent: KMail/1.6.2 References: <20061007214336.GJ793@funkthat.com> In-Reply-To: <20061007214336.GJ793@funkthat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200610091346.02064.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/2015/Mon Oct 9 10:16:43 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: amd64 agp driver bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 17:46:26 -0000 On Saturday 07 October 2006 05:43 pm, John-Mark Gurney wrote: > I was looking at the agp driver and the BIOS and Kernel Developer's > Guide, and noticed that it appears we program the page register > incorrectly... > > Currently we do, in sys/pci/agp_amd64.c: > sc->gatt->ag_virtual[offset >> AGP_PAGE_SHIFT] = physical; > > but according to Table 38 in the guide, it looks like it should be: > sc->gatt->ag_virtual[offset >> AGP_PAGE_SHIFT] = > (physical & 0xfffff000) | ((physical >> 28) & 0xff0) | > 1; > > To support physical addresses above 4G... > > Has anyone used AGP w/ >4GB of memmory? I'm also puzzled by the > fact that the guide says to set bit 0, but we don't do that... As you can see, this part of the documentation is very confusing. :-( I'll take care of it soon. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 9 20:29:02 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E43716A415; Mon, 9 Oct 2006 20:29:02 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate02.zdv.uni-mainz.de (mailgate02.zdv.Uni-Mainz.DE [134.93.178.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id D821543D66; Mon, 9 Oct 2006 20:28:59 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront02.zdv.uni-mainz.de ([134.93.176.56]) by mailgate02.zdv.uni-mainz.de with ESMTP; 09 Oct 2006 22:28:58 +0200 Received: from mail.uni-mainz.de ([134.93.176.49]) by exfront02.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Oct 2006 22:28:57 +0200 Received: from [192.168.1.128] ([85.178.18.209] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Oct 2006 22:28:57 +0200 Message-ID: <452AB103.8030305@mail.uni-mainz.de> Date: Mon, 09 Oct 2006 22:28:51 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Ceri Davies , Maxim Konovalov , maho@freebsd.org, freebsd-amd64@freebsd.org, freebsd-bugs@freebsd.org References: <200610081720.k98HKkQx058984@freefall.freebsd.org> <20061008215308.W89071@mp2.macomnet.net> <20061008180120.GX21333@submonkey.net> In-Reply-To: <20061008180120.GX21333@submonkey.net> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Oct 2006 20:28:57.0292 (UTC) FILETIME=[8BD6D8C0:01C6EBE1] Cc: Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 20:29:02 -0000 Ceri Davies wrote: > On Sun, Oct 08, 2006 at 09:54:53PM +0400, Maxim Konovalov wrote: > >> On Sun, 8 Oct 2006, 17:20-0000, Ceri Davies wrote: >> >> >>> Synopsis: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD >>> >>> State-Changed-From-To: open->closed >>> State-Changed-By: ceri >>> State-Changed-When: Sun Oct 8 17:19:36 UTC 2006 >>> State-Changed-Why: >>> ULE is no longer the default scheduler, and no longer has a maintainer. >>> This is an interesting test case though. >>> >> I think better mark ULE bugs as suspended. I have plans to take them >> over. >> > > I don't intend to sweep them all. I just didn't see a problem statement > in this PR, and figured that it was due to the fact that ULE was default > at the time the PR was raised. > > Feel free to reopen it if you disagree. > > Ceri > Well, maybe I'm the only 'stupid' in this round, so be patient with me. I never realized, that SCHED_ULE has been discarded from being the default scheduler in FreeBSD 6.X, as I can remember, SCHED_ULE has been promoted to be the default scheduler due to its improvements to SMP. Yesterday I read about some bugs, but I read this in this list and therefore I do not exactly know whether these problems are AMD64 related or also be an issue on i386. Well, let me tell you some remarkeable experiences I made since yesterday. Besides my lab's work I uitilize a FreeBSD 6.2-PRE/AMD64 box with a single core Athlon64 3500+ at 2,2 GHz. This box got really slow when walking through 6.1-STABLE up to now and I tried to figure out why. At my lab's desk I use an i386 based box running a P4 at 3,0 GHz with HT capabilities, enabled both in BIOS and in the system, so this box is configured as a SMP machine. On this box, also using SCHED_ULE, I did never realize the significant performance drop as seen on AMD64. After reading about the scheduler problems, I first changed SCHED_ULE to SCHED_4BSD on my AMD64 box and realized a quite impressive performance boost (something strange and not quantified, because I see this only when working with Firefox, Thunderbird and disk access, which seem to be smoother and quite faster than before). On the lab's box, I changed also scheduler back to SCHED_4BSD, but I did not realize this massive peroformance impact as I did on the AMD64 box. Either this problem is highly related to UP kernel configs and/or UP systems as well or it is only related to the 64Bit FreeBSD or only to AMD CPUs, I do not know but would like to know more about that. Well, 'feeling' a performance impact in both directions isn't a very qualifying statement, so I would like to aks you whether you have some suitable benchmarks I can perform on both boxes to confirm my observations and give some numbers. In the first days of FreeBSD 5.0 I remember myself having seen an impressive performance boost using SCHED_ULE on a dual P3/933 Mhz box acting as a file- and databaseserver, but this advantage has obviously gone over the past. Well, Im not very close to the development issue, I'm only a FreeBSD user for scientific purposes and therefore I would appreciate any public informations on this subject. I guess many others around here still being 'stuck' on a faulty SCHED_ULE, not knowing this scheduler is about to be doomed and slowing down a box. Those guys also may act like me - installing once a system and then migrating from one minor release to the next via cvsupdate/buildworld (due to driver/hardware/support issues) and still keeping a kernel config from days, when SCHED_ULE was said to be the new ultimative scheduler even for SMP and UP boxes. Well, I may be wrong, but it would be much more convenient having those important informations being released more public , this will keep guys like me from sending stupid PRs about slowed down boxes suspecting other hardware or bugs elsewhere in the OS. Thnaks in advance, Oliver From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 9 22:15:54 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A559116A47B; Mon, 9 Oct 2006 22:15:54 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F36843D58; Mon, 9 Oct 2006 22:15:54 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id C42F52EC4; Mon, 9 Oct 2006 17:15:53 -0500 (CDT) Date: Mon, 9 Oct 2006 17:15:53 -0500 To: "O. Hartmann" Message-ID: <20061009221553.GC6561@soaustin.net> References: <200610081720.k98HKkQx058984@freefall.freebsd.org> <20061008215308.W89071@mp2.macomnet.net> <20061008180120.GX21333@submonkey.net> <452AB103.8030305@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452AB103.8030305@mail.uni-mainz.de> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: maho@freebsd.org, Maxim Konovalov , freebsd-bugs@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: kern/85820: 1.5 times slower performance with SCHED_ULE than SCHED_4BSD X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 22:15:54 -0000 On Mon, Oct 09, 2006 at 10:28:51PM +0200, O. Hartmann wrote: > I never realized, that SCHED_ULE has been discarded from being the > default scheduler in FreeBSD 6.X, as I can remember, SCHED_ULE has been > promoted to be the default scheduler due to its improvements to SMP. Yes, it was, but as time went on, more work was being done on the kernel in performance improvements in areas other than the scheduler. Whether or not these affected ULE's performance is not clear to me. However, this is a good example of the type of thing that you have to follow discussions on the -current mailing list to keep up with. > Well, I may be wrong, but it would be much more convenient having those > important informations being released more public There hasn't been any effort to keep this information confidential. It's just that individuals' efforts have been going on in areas other than ULE, and it is possible that ULE just hasn't kept up with those changes. These things aren't as cut-and-dried as you seem to think that they are. mcl From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 10 02:01:36 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 379FB16A412; Tue, 10 Oct 2006 02:01:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E524F43D45; Tue, 10 Oct 2006 02:01:35 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9A21ZpT060244; Tue, 10 Oct 2006 02:01:35 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9A21ZMf060240; Tue, 10 Oct 2006 02:01:35 GMT (envelope-from linimon) Date: Tue, 10 Oct 2006 02:01:35 GMT From: Mark Linimon Message-Id: <200610100201.k9A21ZMf060240@freefall.freebsd.org> To: mcawdewit@gmail.com, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Cc: Subject: Re: ports/104123: libglade fails to build X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 02:01:36 -0000 Synopsis: libglade fails to build State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Oct 10 02:00:55 UTC 2006 State-Changed-Why: Duplicate of ports/104117. Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Oct 10 02:00:55 UTC 2006 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=104123 From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 10 02:03:22 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52AD416A40F; Tue, 10 Oct 2006 02:03:22 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F042343D49; Tue, 10 Oct 2006 02:03:21 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9A23LnA060336; Tue, 10 Oct 2006 02:03:21 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9A23L4T060332; Tue, 10 Oct 2006 02:03:21 GMT (envelope-from linimon) Date: Tue, 10 Oct 2006 02:03:21 GMT From: Mark Linimon Message-Id: <200610100203.k9A23L4T060332@freefall.freebsd.org> To: mcawdewit@gmail.com, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Cc: Subject: Re: ports/104125: libglade fails to build, breaks gimp build and others. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 02:03:22 -0000 Synopsis: libglade fails to build, breaks gimp build and others. State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Oct 10 02:01:56 UTC 2006 State-Changed-Why: Duplicate of ports/104117. Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Oct 10 02:01:56 UTC 2006 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=104125 From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 10 02:09:25 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE86616A40F; Tue, 10 Oct 2006 02:09:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6618343D46; Tue, 10 Oct 2006 02:09:25 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9A29P6j060541; Tue, 10 Oct 2006 02:09:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9A29PhM060537; Tue, 10 Oct 2006 02:09:25 GMT (envelope-from linimon) Date: Tue, 10 Oct 2006 02:09:25 GMT From: Mark Linimon Message-Id: <200610100209.k9A29PhM060537@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: kern/103918: [mpt] LSI 53C1030 SCSI controller timing out on mpt driver X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 02:09:25 -0000 Old Synopsis: LSI 53C1030 SCSI controller timing out on mpt driver New Synopsis: [mpt] LSI 53C1030 SCSI controller timing out on mpt driver Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Oct 10 02:07:47 UTC 2006 Responsible-Changed-Why: This sounds as though it is symptomatic to mpt and not amd64. http://www.freebsd.org/cgi/query-pr.cgi?pr=103918 From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 10 20:22:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEE4616A415 for ; Tue, 10 Oct 2006 20:22:22 +0000 (UTC) (envelope-from alecn2002@yandex.ru) Received: from tide.yandex.ru (tide.yandex.ru [213.180.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B69143D45 for ; Tue, 10 Oct 2006 20:22:21 +0000 (GMT) (envelope-from alecn2002@yandex.ru) Received: from YAMAIL (tide.yandex.ru) by mail.yandex.ru id ; Wed, 11 Oct 2006 00:22:05 +0400 Received: from [91.76.91.157] ([91.76.91.157]) by mail.yandex.ru with HTTP; Wed, 11 Oct 2006 00:22:05 +0400 (MSD) Date: Wed, 11 Oct 2006 00:22:05 +0400 (MSD) From: "alecn2002" Sender: alecn2002@yandex.ru Message-Id: <452C00ED.000001.27046@tide.yandex.ru> MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] Errors-To: alecn2002@yandex.ru To: freebsd-amd64@freebsd.org X-Source-Ip: 91.76.91.157 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alecn2002@yandex.ru List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 20:22:22 -0000 Well, probably this question was discussed here many times, but the last thread about "transiting from i386 to amd64" dated year 2004, so it's very posible things change since that time... So, I've just upgraded my home comp from AMD Sempron to Athlon64. Only CPU upgrade, nothing else. I've booted my old good i386-arched FreeBSD 6.1 and it looks like it works fine. The question is: will I have any benefits if I'll move to amd64 system, or it's safer and better to stay with i386 arch? About 50% of time my children use it to watch movies (DVD, DivX, MPEG-4). >From the rest I use it for working at home (RadRails, KDevelop, a lot of C/C++ compilation), and my wife use it to access Internet and use OpenOffice. Problem-free operation and stability have precedense for me over system speed. Technical details: M/B: ASUS K8N, with on-board PATA/SATA, audio, 10/100/1000 Ethernet Processor: AMD Athlon64 3000+ 2GHz (Was: AMD Sempron 2800+ 1.8 GHz) RAM: 1 * 512 Mb PC-400 HDD: 80 Gb SATA-150 (Seagate ) Video: NVidia GeForce 4 FX 5800 128 Mb AGP 8x System: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sat Sep 23 00:12:24 MSD 2006 root@:/usr/src/sys/i386/compile/ALECN61 i386 XFree86-4.5 + nvidia-driver-1.0.8774 KDE 3.5.4 One more detail: I do need linuxlator, b/c I use RadRails a lot and it runs in Linux mode only. AFAIK there is no 64-bit linuxlator exist and amd64 system use 32-bit linuxlator, is it efficient and reliable enough? Even more detail: AFAIK there is no amd64 NVidia driver for direct rendering available, is it correct? And one side question: will I benefit if I move to amd64 system and install gcc-4.1, over current gcc-3.4.4 that came with system? And the same - if I'll stay in i386 mode but upgrade to gcc-4.1? I mean here both compilation speed and efficiency of generated code. --- With best regards, Alexander Novitsky From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 10 20:29:07 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A30F16A4AB for ; Tue, 10 Oct 2006 20:29:07 +0000 (UTC) (envelope-from alecn2002@yandex.ru) Received: from pantene.mail.yandex.net (pantene.mail.yandex.net [213.180.223.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CE843D45 for ; Tue, 10 Oct 2006 20:29:06 +0000 (GMT) (envelope-from alecn2002@yandex.ru) Received: from YAMAIL (pantene.yandex.ru) by mail.yandex.ru id ; Wed, 11 Oct 2006 00:28:54 +0400 Received: from [91.76.91.157] ([91.76.91.157]) by mail.yandex.ru with HTTP; Wed, 11 Oct 2006 00:28:54 +0400 (MSD) Date: Wed, 11 Oct 2006 00:28:54 +0400 (MSD) From: "alecn2002" Sender: alecn2002@yandex.ru Message-Id: <452C0286.000005.20759@pantene.yandex.ru> MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] Errors-To: alecn2002@yandex.ru To: freebsd-amd64@freebsd.org X-Source-Ip: 91.76.91.157 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alecn2002@yandex.ru List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 20:29:07 -0000 Well, probably this question was discussed here many times, but the last thread about "transiting from i386 to amd64" dated year 2004, so it's very posible things change since that time... So, I've just upgraded my home comp from AMD Sempron to Athlon64. Only CPU upgrade, nothing else. I've booted my old good i386-arched FreeBSD 6.1 and it looks like it works fine. The question is: will I have any benefits if I'll move to amd64 system, or it's safer and better to stay with i386 arch? About 50% of time my children use it to watch movies (DVD, DivX, MPEG-4). >From the rest I use it for working at home (RadRails, KDevelop, a lot of C/C++ compilation), and my wife use it to access Internet and use OpenOffice. Problem-free operation and stability have precedense for me over system speed. Technical details: M/B: ASUS K8N, with on-board PATA/SATA, audio, 10/100/1000 Ethernet Processor: AMD Athlon64 3000+ 2GHz (Was: AMD Sempron 2800+ 1.8 GHz) RAM: 1 * 512 Mb PC-400 HDD: 80 Gb SATA-150 (Seagate ) Video: NVidia GeForce 4 FX 5800 128 Mb AGP 8x System: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sat Sep 23 00:12:24 MSD 2006 root@:/usr/src/sys/i386/compile/ALECN61 i386 XFree86-4.5 + nvidia-driver-1.0.8774 KDE 3.5.4 One more detail: I do need linuxlator, b/c I use RadRails a lot and it runs in Linux mode only. AFAIK there is no 64-bit linuxlator exist and amd64 system use 32-bit linuxlator, is it efficient and reliable enough? Even more detail: AFAIK there is no amd64 NVidia driver for direct rendering available, is it correct? And one side question: will I benefit if I move to amd64 system and install gcc-4.1, over current gcc-3.4.4 that came with system? And the same - if I'll stay in i386 mode but upgrade to gcc-4.1? I mean here both compilation speed and efficiency of generated code. --- With best regards, Alexander Novitsky From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 11:49:41 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C478A16A40F for ; Wed, 11 Oct 2006 11:49:41 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mail08a.verio.de (mail08a.verio.de [213.198.55.73]) by mx1.FreeBSD.org (Postfix) with SMTP id AD36543D58 for ; Wed, 11 Oct 2006 11:49:40 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx02.stngva01.us.mxservers.net (204.202.242.66) by mail08a.verio.de (RS ver 1.0.95vs) with SMTP id 3-0771137378; Wed, 11 Oct 2006 13:49:39 +0200 (CEST) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx02.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id 4f9dc254.23509.143.mx02.stngva01.us.mxservers.net; Wed, 11 Oct 2006 07:48:04 -0400 (EDT) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.7/8.11.6) with ESMTP id k9BBnaxm001133; Wed, 11 Oct 2006 13:49:36 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200610111149.k9BBnaxm001133@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: alecn2002@yandex.ru In-Reply-To: Message from "alecn2002" of "Wed, 11 Oct 2006 00:28:54 +0400." <452C0286.000005.20759@pantene.yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Oct 2006 13:49:36 +0200 From: Gary Jennejohn X-Spam: [F=0.0424868680; heur=0.500(-19800); stat=0.028; spamtraq-heur=0.600(2006101101)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: freebsd-amd64@freebsd.org Subject: Re: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 11:49:41 -0000 "alecn2002" writes: > The question is: will I have any benefits if I'll move to amd64 system, or it > 's safer and better to stay with i386 arch? > [snip] > Problem-free operation and stability have precedense for me over system speed > The only real advantage of 64-bit over 32-bit is that you can put more than 4 GB of RAM into the box. If you don't plan to do that, then stick with i386. I've been using a dual-core AMD64 for a while now and I've decided to stick with i386. [snip] > And one side question: will I benefit if I move to amd64 system and install g > cc-4.1, over current gcc-3.4.4 that came with system? > And the same - if I'll stay in i386 mode but upgrade to gcc-4.1? > I mean here both compilation speed and efficiency of generated code. > I can't answer this, but I don't think that all ports and sources are gcc-4.1 clean yet. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 12:08:41 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C81E016A407 for ; Wed, 11 Oct 2006 12:08:41 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate02.zdv.uni-mainz.de (mailgate02.zdv.Uni-Mainz.DE [134.93.178.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A4D543D77 for ; Wed, 11 Oct 2006 12:08:40 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from exfront02.zdv.uni-mainz.de ([134.93.176.56]) by mailgate02.zdv.uni-mainz.de with ESMTP; 11 Oct 2006 14:08:39 +0200 Received: from mail.uni-mainz.de ([134.93.176.49]) by exfront02.zdv.Uni-Mainz.DE with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Oct 2006 14:08:39 +0200 Received: from [130.133.86.198] ([130.133.86.198] RDNS failed) by mail.uni-mainz.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Oct 2006 14:08:38 +0200 Message-ID: <452CDEC1.5000303@uni-mainz.de> Date: Wed, 11 Oct 2006 14:08:33 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: Gary Jennejohn References: <200610111149.k9BBnaxm001133@peedub.jennejohn.org> In-Reply-To: <200610111149.k9BBnaxm001133@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Oct 2006 12:08:38.0853 (UTC) FILETIME=[FC480F50:01C6ED2D] Cc: alecn2002@yandex.ru, freebsd-amd64@freebsd.org Subject: Re: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 12:08:41 -0000 Gary Jennejohn wrote: > "alecn2002" writes: >> The question is: will I have any benefits if I'll move to amd64 system, or it >> 's safer and better to stay with i386 arch? >> > [snip] >> Problem-free operation and stability have precedense for me over system speed >> > > The only real advantage of 64-bit over 32-bit is that you can put more than > 4 GB of RAM into the box. If you don't plan to do that, then stick with > i386. I've been using a dual-core AMD64 for a while now and I've decided to > stick with i386. Well, in many cases you'll prefere the amd64 architecture in case of the need of more than 3 or 3.5 GB RAM. Due to architectural and BIOS limitations memory remapping on 32Bit systems doesn't work properly or is sometimes slow (my experiences). On the other hand, for scientific usage the 64Bit architecture delievers benefits to me, but at home usage it sometimes like a pitfall. Several codecs still aren't portet to 64Bit and my impression is that some kind of software based on JAVA is really flaky and/or slow. OpenOffice still has no pure/clean 64Bit port as I know so far. Linuxulator in FreeBSD is still not capable running 64Bit Linux-native applications, but you can run FreeBSD/Linuxulator in a 32Bit comapt mode also. Memory consumption on AMD64/64Bit CPU is 20% - 30% more than on i386/32Bit - in some cases. > > [snip] >> And one side question: will I benefit if I move to amd64 system and install g >> cc-4.1, over current gcc-3.4.4 that came with system? >> And the same - if I'll stay in i386 mode but upgrade to gcc-4.1? >> I mean here both compilation speed and efficiency of generated code. >> > > I can't answer this, but I don't think that all ports and sources are > gcc-4.1 clean yet. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 12:45:13 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AF0716A519 for ; Wed, 11 Oct 2006 12:45:13 +0000 (UTC) (envelope-from jasen.gibson@ge.com) Received: from ext-ch1gw-7.online-age.net (ext-ch1gw-7.online-age.net [64.37.194.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD2E443DDC for ; Wed, 11 Oct 2006 12:44:22 +0000 (GMT) (envelope-from jasen.gibson@ge.com) Received: from int-ch1gw-4.online-age.net (int-ch1gw-4 [3.159.232.68]) by ext-ch1gw-7.online-age.net (8.13.6/8.13.6/20051111-SVVS-TLS-DNSBL) with ESMTP id k9BClS1r027301 for ; Wed, 11 Oct 2006 08:47:28 -0400 Received: from cinmlef12.e2k.ad.ge.com (int-ch1gw-4 [3.159.232.68]) by int-ch1gw-4.online-age.net (8.13.6/8.13.6/20050510-SVVS) with ESMTP id k9BCi01q012360 for ; Wed, 11 Oct 2006 08:44:00 -0400 (EDT) Received: from LOUMLVEM05.e2k.ad.ge.com ([3.159.160.56]) by cinmlef12.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 11 Oct 2006 08:44:11 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Oct 2006 08:44:10 -0400 Message-ID: <11A5C7FB9726324A8ACCF5C0922195E91956C6@LOUMLVEM05.e2k.ad.ge.com> In-Reply-To: <20061011120033.C8E1F16A51C@hub.freebsd.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: freebsd-amd64 Digest, Vol 175, Issue 3 Thread-Index: AcbtLP9h2R4/eOgrRnKZ+0Hl1nr0oAAApYrA From: "Gibson, Jasen \(GE Indust, ConsInd, consultant\)" To: , X-OriginalArrivalTime: 11 Oct 2006 12:44:11.0492 (UTC) FILETIME=[F36EF240:01C6ED32] Cc: Subject: RE: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 12:45:13 -0000 -----Original Message----- >Well, probably this question was discussed here many times, but the = last thread about "transiting from i386 to >amd64" dated year 2004, so it's very posible things change since that = time... > >I've just upgraded my home comp from AMD Sempron to Athlon64. Only CPU = upgrade, nothing else. > >I've booted my old good i386-arched FreeBSD 6.1 and it looks like it = works fine. >The question is: will I have any benefits if I'll move to amd64 system, = or it's safer and better to stay with i386 >arch? > >About 50% of time my children use it to watch movies (DVD, DivX, = MPEG-4). >From the rest I use it for working at home (RadRails, KDevelop, a lot = of C/C++ compilation), and my wife use it to >access Internet and use = OpenOffice. > >Problem-free operation and stability have precedense for me over system = speed. >Even more detail: AFAIK there is no amd64 NVidia driver for direct = rendering available, is it correct? > >And one side question: will I benefit if I move to amd64 system and = install gcc-4.1, over current gcc-3.4.4 that=20 >came with system? >And the same - if I'll stay in i386 mode but upgrade to gcc-4.1? >I mean here both compilation speed and efficiency of generated code. I can't answer all of your specific questions, as I do not use FreeBSD = as a desktop system, but I can tell you that the current release of the = amd64 port is just as stable as the i386 for me. I switched from an AthlonMP system to an Opteron platform for a = production server. I ran both the 32-bit and 64-bit ports on the new = system during the testing phase, and they pretty much seemed identical = in terms of stability. I didn't benchmark to see if there was much = performance difference, but I doubt that there was. I'm using the = server for Apache and Mysql. The other main benefit besides the 4GB limit is that the 64-bit = extensions give you more register space, which could significantly speed = up computational-heavy applications. Things like webbrowsers or = OpenOffice, not so much. I'd imagine a compiler would fit that category = though. There is no amd64 nVidia driver yet, which is annoying. They released = one for Linux, just not FreeBSD yet. If that's important, then i386 may = be the best bet for you. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 13:10:47 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65DAC16A412 for ; Wed, 11 Oct 2006 13:10:47 +0000 (UTC) (envelope-from sql82@list.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0727D43D53 for ; Wed, 11 Oct 2006 13:10:46 +0000 (GMT) (envelope-from sql82@list.ru) Received: from [195.66.208.53] (port=58845 helo=squirlhome) by mx27.mail.ru with asmtp id 1GXdql-000KQV-00; Wed, 11 Oct 2006 17:10:19 +0400 Date: Wed, 11 Oct 2006 16:19:08 +0300 From: Andriy Tovstik To: alecn2002@yandex.ru Message-Id: <20061011161908.48c75078.sql82@list.ru> In-Reply-To: <452C0286.000005.20759@pantene.yandex.ru> References: <452C0286.000005.20759@pantene.yandex.ru> X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.20; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 13:10:47 -0000 Hi, Alex i have a FreeBSD AMD64 based desktop machine, and it works fine. BUT! Vidia driver for 64-bit platform is missing... Some ports ( such as wine or opera ) exist only for i386 platform... You can easily continue i386 using, it is too early to switch to amd64 IMHO :) WBR, Andriy "squirL" Tovstik ICQ UIN 325540316 mailto:sql82@list.ru From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 13:35:46 2006 Return-Path: X-Original-To: Freebsd-amd64@freebsd.org Delivered-To: Freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5444916A49E for ; Wed, 11 Oct 2006 13:35:46 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C52243D5D for ; Wed, 11 Oct 2006 13:35:32 +0000 (GMT) (envelope-from ler@lerctr.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:In-Reply-To:X-MimeOLE:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=r1zUNf+QAj1o9b7JAjttmq9vlbZ5yjvLYM+8+wSzXyK9h8A4vlFgQs14vacAShJOKY0H6+GYsC6WjolegbW2tn5b+8+GpAqTucA5veDzEASz9BDGYwj9t1LwXH8V/i6kqbANy5a0GT2+HYwjS94LyRrlOzI15mZyCMo7RAPEwMU=; Received: from [66.179.40.122] (port=37282 helo=SURGLROSENMAN) by thebighonker.lerctr.org with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GXeF7-0008So-Kr; Wed, 11 Oct 2006 08:35:31 -0500 From: "Larry Rosenman" To: "'Gavin Atkinson'" Date: Wed, 11 Oct 2006 08:35:19 -0500 Message-ID: <000001c6ed3a$1e31e3f0$0202fea9@SURGIENT.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbtNksQevOrVcbASkeeFYbcpUSTpwAAtekg In-Reply-To: <1160572063.67896.26.camel@buffy.york.ac.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 X-LERCTR-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 DomainKey-Status: no signature Cc: Freebsd-amd64@freebsd.org Subject: RE: Random Crash/Dump/6.2-PRE (30/Sep/2006 sources).... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 13:35:46 -0000 Gavin Atkinson wrote: > What is line 378 of this file on your system? As far as I can tell, > it's not actually part of pmap_remove_pages(). With the corefile, > using kgdb to print the panicstr (with "p panicstr") may be of use, > to confirm it is connected. > > Gavin PMAP_INLINE pt_entry_t * vtopte(vm_offset_t va) { u_int64_t mask = ((1ul << (NPTEPGSHIFT + NPDEPGSHIFT + NPDPEPGSHIFT + NP ML4EPGSHIFT)) - 1); return (PTmap + ((va >> PAGE_SHIFT) & mask)); } Line 378 is the first line of that function. (kgdb) p panicstr $1 = 0xffffffff80657ee0 "page fault" (kgdb) I have the core and kernel saved off, as well as the sources..... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 13:57:06 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4589316A51A; Wed, 11 Oct 2006 13:57:06 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CF5F43D5E; Wed, 11 Oct 2006 13:57:05 +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.6/8.13.6) with ESMTP id k9BDv4rR047585; Wed, 11 Oct 2006 09:57:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id k9BDv4nA070681; Wed, 11 Oct 2006 09:57:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1A3997305F; Wed, 11 Oct 2006 09:57:03 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061011135704.1A3997305F@freebsd-current.sentex.ca> Date: Wed, 11 Oct 2006 09:57:03 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner3 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 13:57:06 -0000 TB --- 2006-10-11 12:07:26 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-11 12:07:26 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-11 12:07:26 - cleaning the object tree TB --- 2006-10-11 12:08:12 - checking out the source tree TB --- 2006-10-11 12:08:12 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-11 12:08:12 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-11 12:17:14 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-11 12:17:14 - cd /src TB --- 2006-10-11 12:17:14 - /usr/bin/make -B buildworld >>> World build started on Wed Oct 11 12:17:16 UTC 2006 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Wed Oct 11 13:31:40 UTC 2006 TB --- 2006-10-11 13:31:40 - generating LINT kernel config TB --- 2006-10-11 13:31:40 - cd /src/sys/amd64/conf TB --- 2006-10-11 13:31:40 - /usr/bin/make -B LINT TB --- 2006-10-11 13:31:40 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-11 13:31:40 - cd /src TB --- 2006-10-11 13:31:40 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 11 13:31:40 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Wed Oct 11 13:50:11 UTC 2006 TB --- 2006-10-11 13:50:11 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-11 13:50:11 - cd /src TB --- 2006-10-11 13:50:11 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Oct 11 13:50:11 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/amd64/amd64/intr_machdep.c:382: error: `ICW1_RESET' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:382: error: `ICW1_IC4' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:383: error: `ICU_IMR_OFFSET' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:383: error: `IDT_IO_INTS' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:385: error: `ICW4_8086' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: `OCW3_SEL' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: `OCW3_RR' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:389: error: `IO_ICU2' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-11 13:57:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-11 13:57:03 - ERROR: failed to build GENERIC kernel TB --- 2006-10-11 13:57:03 - tinderbox aborted TB --- 0.89 user 3.46 system 6576.93 real From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 14:00:34 2006 Return-Path: X-Original-To: Freebsd-amd64@freebsd.org Delivered-To: Freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EFBD16A4C9 for ; Wed, 11 Oct 2006 14:00:34 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038AF43D6B for ; Wed, 11 Oct 2006 14:00:13 +0000 (GMT) (envelope-from ler@lerctr.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:In-Reply-To:X-MimeOLE:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=SNqcTnODAFpYggxRJhH/wiCpIXT+3i0T2dxDIQVe3UggE7wW6vmfoy9TCowocdDCMVwPpSC8eXFuUSsPbFanF/kv+zEtUHnci+ftf4uTBoriOxUIK6tnvkrslW0zb7njEnfEC799QVy9vJZSirmG0pdsVkha0M0CHkiw0mhIFgQ=; Received: from [66.179.40.122] (port=41000 helo=SURGLROSENMAN) by thebighonker.lerctr.org with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GXecw-0008u3-5i for Freebsd-amd64@freebsd.org; Wed, 11 Oct 2006 09:00:13 -0500 From: "Larry Rosenman" To: Date: Wed, 11 Oct 2006 08:59:55 -0500 Message-ID: <004701c6ed3d$8e0f4070$0202fea9@SURGIENT.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbtNksQevOrVcbASkeeFYbcpUSTpwAAtekgAAEM8iA= In-Reply-To: <000001c6ed3a$1e31e3f0$0202fea9@SURGIENT.COM> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: -4.3 (----) X-LERCTR-Spam-Score: -4.3 (----) X-Spam-Report: (-4.3 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 TW_RB=0.077 X-LERCTR-Spam-Report: (-4.3 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 TW_RB=0.077 DomainKey-Status: no signature Cc: Subject: RE: Random Crash/Dump/6.2-PRE (30/Sep/2006 sources).... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 14:00:34 -0000 Larry Rosenman wrote: > Gavin Atkinson wrote: >> What is line 378 of this file on your system? As far as I can tell, >> it's not actually part of pmap_remove_pages(). With the corefile, >> using kgdb to print the panicstr (with "p panicstr") may be of use, >> to confirm it is connected. >> >> Gavin > > PMAP_INLINE pt_entry_t * > vtopte(vm_offset_t va) > { > u_int64_t mask = ((1ul << (NPTEPGSHIFT + NPDEPGSHIFT + > NPDPEPGSHIFT + NP > ML4EPGSHIFT)) - 1); > > return (PTmap + ((va >> PAGE_SHIFT) & mask)); } > > Line 378 is the first line of that function. > > (kgdb) p panicstr > $1 = 0xffffffff80657ee0 "page fault" > (kgdb) > > I have the core and kernel saved off, as well as the sources..... My offer of a shell account and access to the dump/kernel/whatever Still stands. Here's the bt again: $ cat script.0 Script started on Mon Oct 2 05:59:35 2006 # kgdb kernel.0 vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffff800000004200 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff80448c6b stack pointer = 0x10:0xffffffffb5f0aa70 frame pointer = 0x10:0x840 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 82598 (exim-4.63-0) trap number = 12 panic: page fault cpuid = 0 Uptime: 1d10h4m44s Dumping 4095 MB (3 chunks) chunk 0: 1MB (152 pages) ... ok chunk 1: 3071MB (786032 pages) 3055 3039 3023 3007 2991 2975 2959 2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok chunk 2: 1024MB (262144 pages) 1009 993 977 961 945 929 913 897 881 865 849 833 817 801 785 769 753 737 721 705 689 673 657 641 625 609 593 577 561 545 529 513 497 481 465 449 433 417 401 385 369 353 337 321 305 289 273 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff802abcd7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0xffffffff802ac371 in panic (fmt=0xffffff0061c20000 "Xs\021\217") at /usr/src/sys/kern/kern_shutdown.c:565 #4 0xffffffff8044e1bf in trap_fatal (frame=0xffffff0061c20000, eva=18446742976598209368) at /usr/src/sys/amd64/amd64/trap.c:660 #5 0xffffffff8044e4df in trap_pfault (frame=0xffffffffb5f0a9c0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:573 #6 0xffffffff8044e80d in trap (frame= {tf_rdi = -140737488355328, tf_rsi = -140737488338432, tf_rdx = 0, tf_rcx = 8650752, tf_r8 = 178, tf_r9 = -1096448638976, tf_rax = 0, tf_rbx = -2131593008, tf_rbp = 2112, tf_r10 = 1249540, tf_r11 = 132564, tf_r12 = -1096474529440, tf_r13 = -140462610448384, tf_r14 = 140737488355328, tf_r15 = 0, tf_trapno = 12, tf_addr = -140737488338432, tf_flags = -2104448720, tf_err = 0, tf_rip = -2142991253, tf_cs = 8, tf_rflags = 66050, tf_rsp = -1242518912, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:352 #7 0xffffffff80439a3b in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #8 0xffffffff80448c6b in pmap_remove_pages (pmap=0xffffff00b5067160, sva=0, eva=140737488355328) at /usr/src/sys/amd64/amd64/pmap.c:378 #9 0xffffffff80407364 in vmspace_exit (td=0xffffff0061c20000) at vm_map.h:251 ---Type to continue, or q to quit--- #10 0xffffffff8028d59d in exit1 (td=0xffffff0061c20000, rv=0) at /usr/src/sys/kern/kern_exit.c:295 #11 0xffffffff8028e5ee in sys_exit (td=0xffff800000000000, uap=0xffff800000004200) at /usr/src/sys/kern/kern_exit.c:99 #12 0xffffffff8044f081 in syscall (frame= {tf_rdi = 0, tf_rsi = 6311936, tf_rdx = 23, tf_rcx = 48, tf_r8 = -1242518944, tf_r9 = 140737488349032, tf_rax = 1, tf_rbx = 0, tf_rbp = 6291740, tf_r10 = 140737488347824, tf_r11 = 4, tf_r12 = 0, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = 6262784, tf_flags = 1, tf_err = 2, tf_rip = 34384922508, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488349160, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:792 #13 0xffffffff80439bd8 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #14 0x000000080180478c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) # Script done on Mon Oct 2 05:59:55 2006 $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 16:34:12 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84A7A16A40F; Wed, 11 Oct 2006 16:34:12 +0000 (UTC) (envelope-from gabriele@sssup.it) Received: from sssup.it (ms01.sssup.it [193.205.80.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB81A43D80; Wed, 11 Oct 2006 16:34:00 +0000 (GMT) (envelope-from gabriele@sssup.it) Received: from [193.205.82.27] (HELO [127.0.0.1]) by sssup.it (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 24863619; Wed, 11 Oct 2006 18:25:43 +0200 Message-ID: <452D1CDF.90208@sssup.it> Date: Wed, 11 Oct 2006 18:33:35 +0200 From: Gabriele Cecchetti User-Agent: Mozilla Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org, pjd@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Any progress for: amd64/91799: ggated core dumps on amd64 after client connection X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 16:34:12 -0000 Any progress about problem amd64/91799 ? (info at: http://www.freebsd.org/cgi/query-pr.cgi?pr=91799) A patch was proposed, but for some reason has not yet been submitted. Any chance to see a working patch inside 6-STABLE ? Thanks for your attention. Gabriele Cecchetti From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 17:12:42 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE68816A407 for ; Wed, 11 Oct 2006 17:12:42 +0000 (UTC) (envelope-from mwm-dated-1161450388.c730ea@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 5078943EE7 for ; Wed, 11 Oct 2006 17:06:28 +0000 (GMT) (envelope-from mwm-dated-1161450388.c730ea@mired.org) Received: (qmail 28078 invoked by uid 1001); 11 Oct 2006 17:06:28 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 11 Oct 2006 13:06:27 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17709.9363.443239.897184@bhuda.mired.org> Date: Wed, 11 Oct 2006 13:06:27 -0400 To: Gary Jennejohn In-Reply-To: <200610111149.k9BBnaxm001133@peedub.jennejohn.org> References: <452C0286.000005.20759@pantene.yandex.ru> <200610111149.k9BBnaxm001133@peedub.jennejohn.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: alecn2002@yandex.ru, freebsd-amd64@freebsd.org Subject: Re: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 17:12:42 -0000 In <200610111149.k9BBnaxm001133@peedub.jennejohn.org>, Gary Jennejohn typed: > "alecn2002" writes: > > The question is: will I have any benefits if I'll move to amd64 system, or it > > 's safer and better to stay with i386 arch? > [snip] > > Problem-free operation and stability have precedense for me over system speed > The only real advantage of 64-bit over 32-bit is that you can put more than > 4 GB of RAM into the box. Personally, I think the 30% performance improvment I see using amd64 is a real benefit. The amd64 architecture has twice as many registers as i386, and they're twice as wide. If you can run code built for amd64, you win. If you're running mostly i386 apps (as with certain proprietary systems), you don't. It took a little bit of doing, but I got everything I used on my desktop on i386 working on amd64. The biggest headach was openoffice, but that was because one of the repositories had a broken tarball; once I got the right tarball, it built just fine. Two ports required tweaking to get the code to build on amd64. I wound up installing another port from the package. The other 400+ ports I use all worked with no problems. That 1% problem rate sounds about right for i386 ports as well. 32 bit emulation works, and as others have said, is how you run Linux binaries. The linuxolator works fine. In fact, that may be the best way to use 32 bit software. Whlle you can run 32 bit freebsd binaries, the ports system doesn't work for them, because there's no way to specify that you need the 32-bit version of a library, not the 64-bit version (if there is, please point me at the docs), so you don't get the library dependencies installed properly. The other gotcha is that, while gcc knows how to build 32 bit binaries, the system compiler isn't configured to do the right thing by default. It's probably possible to make this work right, or maybe a gcc installed from ports will do the right thing. I haven't checked. Oh yeah - if you're running the proprietary NVidia driver, it doesn't exist for amd64 on FreeBSD. The open source driver works fine. Personally, I think converting is worth it, and would recommend it if you can. However, there are things that don't work. The only real way to tell if everything you need works is to try and see. If you've got critical things that you *have* to have, you might ask here. But the answer may not be reliable, because some options that you require may not work, like the OpenOffice/Mozilla integration. Personally, I bought a second disk identical to my system disk, copied the partition table and set up a dual boot system with /home from the original system disk on both systems. After I was happy, I moved everything to one disk and set them up as a RAID 1. While you're doing this, check your motherboard specs, and see if it supports dual channel memory access. If it will, buy another stick of RAM so that you'll get dual channel mode. That's another relatively cheap way to improve system performmance. Since amd64 uses a bit more memory, you may want to do this anyway. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 18:02:25 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D17B16A49E for ; Wed, 11 Oct 2006 18:02:25 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3509C43D69 for ; Wed, 11 Oct 2006 17:58:55 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7945745CD9; Wed, 11 Oct 2006 19:58:47 +0200 (CEST) Received: from localhost (dkq102.neoplus.adsl.tpnet.pl [83.24.20.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id EFE95456B1; Wed, 11 Oct 2006 19:58:38 +0200 (CEST) Date: Wed, 11 Oct 2006 19:58:29 +0200 From: Pawel Jakub Dawidek To: Gabriele Cecchetti Message-ID: <20061011175829.GA57686@garage.freebsd.pl> References: <452D1CDF.90208@sssup.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <452D1CDF.90208@sssup.it> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-amd64@freebsd.org Subject: Re: Any progress for: amd64/91799: ggated core dumps on amd64 after client connection X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 18:02:25 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 11, 2006 at 06:33:35PM +0200, Gabriele Cecchetti wrote: > Any progress about problem amd64/91799 ? > (info at: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D91799) >=20 > A patch was proposed, but for some reason has not yet been submitted. > Any chance to see a working patch inside 6-STABLE ? I'm sorry that it takes so long... I just tried to reproduce it on: beast:root:~# uname -a FreeBSD beast.wheel.pl 6.1-STABLE FreeBSD 6.1-STABLE #2: Thu May 11 02:05:= 14 CEST 2006 root@beast.wheel.pl:/usr/home/obj/usr/home/src/REL6/src/sy= s/BEAST amd64 No luck, it works just fine. I need more info to reproduce it. Could you start both ggated and ggatec with -v option and send me the output from right before the crash? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFLTDFForvXbEpPzQRAruJAKDGdz2tBz5dla30UYACMt3VsQ9NagCfbjry J0I1vond5wfEGRWWa/ZzsUU= =5fFp -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 20:54:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C57C716A407 for ; Wed, 11 Oct 2006 20:54:58 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 342BA43D5F for ; Wed, 11 Oct 2006 20:54:58 +0000 (GMT) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k9BKskqa006646; Wed, 11 Oct 2006 22:54:46 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.13.8/8.13.8/Submit) id k9BKskgJ006645; Wed, 11 Oct 2006 16:54:46 -0400 (EDT) (envelope-from cracauer) Date: Wed, 11 Oct 2006 16:54:46 -0400 From: Martin Cracauer To: Gary Jennejohn Message-ID: <20061011205446.GA6548@cons.org> References: <452C0286.000005.20759@pantene.yandex.ru> <200610111149.k9BBnaxm001133@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200610111149.k9BBnaxm001133@peedub.jennejohn.org> User-Agent: Mutt/1.4.2.2i Cc: alecn2002@yandex.ru, freebsd-amd64@freebsd.org Subject: Re: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 20:54:58 -0000 Gary Jennejohn wrote on Wed, Oct 11, 2006 at 01:49:36PM +0200: > > "alecn2002" writes: > > The question is: will I have any benefits if I'll move to amd64 system, or it > > 's safer and better to stay with i386 arch? > > > [snip] > > Problem-free operation and stability have precedense for me over system speed > > > > The only real advantage of 64-bit over 32-bit is that you can put more than > 4 GB of RAM into the box. If you don't plan to do that, then stick with > i386. I've been using a dual-core AMD64 for a while now and I've decided to > stick with i386. This is incorrect. 32bit with PAE uses 4GB RAM and more just fine. However, userlevel processes are limited to 3 GB virtual memory on 32 bit FreeBSD, each. As for the original question, amd64 complicated things quite a bit as some people need to keep some 64 bit stuff around, e.g. a firefox chain for flash (I use a Linux chain anyway) and xine/mplayer for the 32 bit Windows dlls. Also, no NVidia driver means you might have lousy quality of the videos in question (although you certainly have enough CPU power to live without video acceleration). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 21:14:36 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64D9C16A412 for ; Wed, 11 Oct 2006 21:14:36 +0000 (UTC) (envelope-from vazquez@iqm.unicamp.br) Received: from penelope.iqm.unicamp.br (penelope.iqm.unicamp.br [143.106.51.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE16143D5C for ; Wed, 11 Oct 2006 21:14:35 +0000 (GMT) (envelope-from vazquez@iqm.unicamp.br) Received: by penelope.iqm.unicamp.br (VMTA, from userid 105) id 1269B91; Wed, 11 Oct 2006 19:14:33 -0200 (EDT) Date: Wed, 11 Oct 2006 19:14:33 -0200 From: Pedro A M Vazquez To: freebsd-amd64@freebsd.org Message-ID: <20061011191433.A22753@penelope.iqm.unicamp.br> References: <452C0286.000005.20759@pantene.yandex.ru> <200610111149.k9BBnaxm001133@peedub.jennejohn.org> <20061011205446.GA6548@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20061011205446.GA6548@cons.org>; from cracauer@cons.org on Wed, Oct 11, 2006 at 04:54:46PM -0400 Subject: Re: Fw: To amd64 or not to amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 21:14:36 -0000 Wed, Oct 11, 2006 at 04:54:46PM -0400, Martin Cracauer wrote: > > > > The only real advantage of 64-bit over 32-bit is that you can put more than > > 4 GB of RAM into the box. If you don't plan to do that, then stick with > > i386. I've been using a dual-core AMD64 for a while now and I've decided to > > stick with i386. > > This is incorrect. 32bit with PAE uses 4GB RAM and more just fine. > > However, userlevel processes are limited to 3 GB virtual memory on 32 > bit FreeBSD, each. > > As for the original question, amd64 complicated things quite a bit as > some people need to keep some 64 bit stuff around, e.g. a firefox > chain for flash (I use a Linux chain anyway) and xine/mplayer for the > 32 bit Windows dlls. Also, no NVidia driver means you might have > lousy quality of the videos in question (although you certainly have > enough CPU power to live without video acceleration). > Well, for scientific computing in my area (Quantum Chemistry) on the other hand, amd64 is a big leap forward and, thanks to gfortran41, some legacy codes have already done the migration from i386 to it and removed several limitations of the 32bit architeture and added 64bit performance at a fraction of the cost it used to be. Pedro From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 22:53:50 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D7F16A403 for ; Wed, 11 Oct 2006 22:53:50 +0000 (UTC) (envelope-from stephanie@mail.sosdg.org) Received: from mail.sosdg.org (everest.sosdg.org [66.93.203.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1320E43D67 for ; Wed, 11 Oct 2006 22:53:49 +0000 (GMT) (envelope-from stephanie@mail.sosdg.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=everest; d=mail.sosdg.org; h=Received:Date:From:To:Subject:Message-ID:MIME-Version:Content-Type:Content-Disposition:User-Agent:Sender:X-SA-Exim-Connect-IP:X-SA-Exim-Mail-From; b=tDTV0r08nNFpH5ZYcc943bcU+s3cvDAqhZ2fCzBeS5v4pNYI74gnkB46OBuRPPXkshrgPcchSSmNvJkach65Jmf2ambX6K7QajEl9Kq3KfB6+OsVcA2xJjjeP81Covcw; Received: from stephanie by mail.sosdg.org with local (Exim 4.63-SOSDG) id 1GXmxR-0007u0-6Z by authid for ; Wed, 11 Oct 2006 18:53:49 -0400 Date: Wed, 11 Oct 2006 18:53:49 -0400 From: Stephanie Erin Daugherty To: freebsd-amd64@freebsd.org Message-ID: <20061011225348.GA16838@everest.sosdg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: Stephanie Erin Daugherty X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: stephanie@mail.sosdg.org Subject: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 22:53:50 -0000 Out of curiosity, is there no demand for wine under amd64, or does noone with the know-how to make it work care to do so? its been over a year, and a couple of releases later, and theres still not a working port offered. What's taking so long? From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 23:10:48 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24FFA16A4F6 for ; Wed, 11 Oct 2006 23:10:48 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3C9943D67 for ; Wed, 11 Oct 2006 23:10:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9BNAHLP016964 for ; Wed, 11 Oct 2006 23:10:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9BNAHfo016963; Wed, 11 Oct 2006 23:10:17 GMT (envelope-from gnats) Resent-Date: Wed, 11 Oct 2006 23:10:17 GMT Resent-Message-Id: <200610112310.k9BNAHfo016963@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, Stephanie Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F2D216A40F for ; Wed, 11 Oct 2006 23:07:26 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F44A43D64 for ; Wed, 11 Oct 2006 23:07:22 +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 k9BN7MjO039796 for ; Wed, 11 Oct 2006 23:07:22 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k9BN7MD6039794; Wed, 11 Oct 2006 23:07:22 GMT (envelope-from nobody) Message-Id: <200610112307.k9BN7MD6039794@www.freebsd.org> Date: Wed, 11 Oct 2006 23:07:22 GMT From: Stephanie To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 23:10:48 -0000 >Number: 104311 >Category: amd64 >Synopsis: ports/wine should be installable on amd64 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 11 23:10:17 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Stephanie >Release: 6.2-BETA2 >Organization: . >Environment: 6.2-BETA GENERIC amd64 >Description: ports/wine is not installable under amd64 under any version of freebsd to date. I don't remember what the underlying technical problem is, but this makes the amd64 build of freebsd absolutely useless to me, due to the need to run some Windows applications. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 11 23:27:03 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29EB616A4A0 for ; Wed, 11 Oct 2006 23:27:03 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 697DD43DA2 for ; Wed, 11 Oct 2006 23:25:41 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.8/8.13.8) with ESMTP id k9BNNGZb002785; Wed, 11 Oct 2006 16:23:16 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.8/8.13.8/Submit) id k9BNNGOD002784; Wed, 11 Oct 2006 16:23:16 -0700 (PDT) (envelope-from sgk) Date: Wed, 11 Oct 2006 16:23:16 -0700 From: Steve Kargl To: Stephanie Erin Daugherty Message-ID: <20061011232316.GA2751@troutmask.apl.washington.edu> References: <20061011225348.GA16838@everest.sosdg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061011225348.GA16838@everest.sosdg.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 23:27:03 -0000 On Wed, Oct 11, 2006 at 06:53:49PM -0400, Stephanie Erin Daugherty wrote: > Out of curiosity, is there no demand for wine under amd64, or > does noone with the know-how to make it work care to do so? its > been over a year, and a couple of releases later, and theres > still not a working port offered. > > What's taking so long? Perhaps, you should take up the challenge and port wine to amd64. You've had over a year to study the problem. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 00:57:54 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5143A16A417 for ; Thu, 12 Oct 2006 00:57:54 +0000 (UTC) (envelope-from stephanie@sosdg.org) Received: from mail.sosdg.org (everest.sosdg.org [66.93.203.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD55343D5C for ; Thu, 12 Oct 2006 00:57:53 +0000 (GMT) (envelope-from stephanie@sosdg.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=everest; d=sosdg.org; h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Scan-Signature:X-SA-Exim-Connect-IP:X-SA-Exim-Mail-From; b=p9ItdHOFBTJ1nrPQgS1EfGgYKGlV4gBW8mAHsQ94HkM9HpxFKaRHzjJ+3wYKwgYn0K3oH+xhzaMujaaC66XlQzCfjINY16fI4JGzwsL1A/kWz29LTAFdiOlyWcW55ik7; Received: from cpe-066-026-052-024.nc.res.rr.com ([66.26.52.24] helo=[192.168.1.135]) by mail.sosdg.org with esmtpa (Exim 4.63-SOSDG) id 1GXotU-0004T9-HL by authid ; Wed, 11 Oct 2006 20:57:52 -0400 Message-ID: <452D9305.5060901@sosdg.org> Date: Wed, 11 Oct 2006 20:57:41 -0400 From: Stephanie User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> In-Reply-To: <20061011232316.GA2751@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scan-Signature: 198a7e145b2f20f117ef3a7ea282ce03 X-SA-Exim-Connect-IP: 66.26.52.24 X-SA-Exim-Mail-From: stephanie@sosdg.org Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 00:57:54 -0000 Steve Kargl wrote: >Perhaps, you should take up the challenge and port wine to >amd64. You've had over a year to study the problem. > > > I appreciate your overconfidence in my abilities, but if it were within my technical capabilities to fix, it would have been and patches would have been submitted. Since its not, I'm still waiting on anyone that possesses the level of knowledge required to fix the problem to actually do so. -Stephanie From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 01:06:01 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D07E16A407 for ; Thu, 12 Oct 2006 01:06:01 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C6F043D58 for ; Thu, 12 Oct 2006 01:06:01 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 066171A4D88; Wed, 11 Oct 2006 18:06:01 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5A3B55128A; Wed, 11 Oct 2006 21:05:59 -0400 (EDT) Date: Wed, 11 Oct 2006 21:05:58 -0400 From: Kris Kennaway To: Stephanie Message-ID: <20061012010558.GA27445@xor.obsecurity.org> References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <452D9305.5060901@sosdg.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 01:06:01 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 11, 2006 at 08:57:41PM -0400, Stephanie wrote: > Steve Kargl wrote: >=20 > >Perhaps, you should take up the challenge and port wine to=20 > >amd64. You've had over a year to study the problem. > > > >=20 > > >=20 > I appreciate your overconfidence in my abilities, but if it were within= =20 > my technical capabilities to fix, it would have been and patches would=20 > have been submitted. >=20 > Since its not, I'm still waiting on anyone that possesses the level of=20 > knowledge required to fix the problem to actually do so. Don't hold your breath ;-) Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFLZT2Wry0BWjoQKURAkOiAKDG28Vocot5zeYvfVD56egua9Aj6ACdG2u+ 2xjLuGxEwHjfPEtRTbGe6ZE= =m1VY -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 01:07:33 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A5EC16A403 for ; Thu, 12 Oct 2006 01:07:33 +0000 (UTC) (envelope-from igor@hybrid-lab.co.uk) Received: from mra05.ch.as12513.net (mra05.ch.as12513.net [82.153.254.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2881543D5C for ; Thu, 12 Oct 2006 01:07:32 +0000 (GMT) (envelope-from igor@hybrid-lab.co.uk) Received: from localhost (localhost [127.0.0.1]) by mra05.ch.as12513.net (Postfix) with ESMTP id 185F7C037D; Thu, 12 Oct 2006 02:07:32 +0100 (BST) Received: from mra05.ch.as12513.net ([127.0.0.1]) by localhost (mra05.ch.as12513.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01037-01-89; Thu, 12 Oct 2006 02:07:31 +0100 (BST) Received: from [81.168.65.143] (unknown [81.168.65.143]) by mra05.ch.as12513.net (Postfix) with ESMTP id 75161C02EF; Thu, 12 Oct 2006 02:07:31 +0100 (BST) In-Reply-To: <452D9305.5060901@sosdg.org> References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> Content-Transfer-Encoding: 7bit From: Igor Mozolevsky Date: Thu, 12 Oct 2006 02:07:48 +0100 To: Stephanie X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 01:07:33 -0000 I do like the FreeBSD community approach to bug reports - fix it yourself and send us a patch! Having thought that PR stood for Problem Report, it is becoming clear that it actually stands for Problem Resolution!.. On 12 Oct 2006, at 01:57, Stephanie wrote: > Steve Kargl wrote: > >> Perhaps, you should take up the challenge and port wine to amd64. >> You've had over a year to study the problem. >> >> > > I appreciate your overconfidence in my abilities, but if it were > within my technical capabilities to fix, it would have been and > patches would have been submitted. > > Since its not, I'm still waiting on anyone that possesses the level > of knowledge required to fix the problem to actually do so. > > -Stephanie > > _______________________________________________ > 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 Thu Oct 12 01:17:30 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FDB916A40F for ; Thu, 12 Oct 2006 01:17:30 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEED443D5D for ; Thu, 12 Oct 2006 01:17:29 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D4B721A3C20; Wed, 11 Oct 2006 18:17:29 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F074A512BD; Wed, 11 Oct 2006 21:17:28 -0400 (EDT) Date: Wed, 11 Oct 2006 21:17:28 -0400 From: Kris Kennaway To: Igor Mozolevsky Message-ID: <20061012011728.GA27584@xor.obsecurity.org> References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 01:17:30 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 12, 2006 at 02:07:48AM +0100, Igor Mozolevsky wrote: > I do like the FreeBSD community approach to bug reports - fix it =20 > yourself and send us a patch! Having thought that PR stood for =20 > Problem Report, it is becoming clear that it actually stands for =20 > Problem Resolution!.. The PR database is primarily intended for reports of bugs in FreeBSD, not "new features I'd like to see that will take someone dozens or hundreds of hours to implement". While there is a "wish-list" category in GNATS, a realistic submitter will not expect action on such items just because they submit a PR. Finally, yes, FreeBSD is a community project, not a mysterious closed system where you submit your requests into the black box of developers and out pops your answer as if by magic. So it's not at all unreasonable that submitters of difficult or unrealistic requests be invited to participate in the process of solving them. Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFLZeoWry0BWjoQKURAoOVAKCajW1RGgMf/GKrV8WqoPNEtNEBUwCeK6G1 zK4gHckUaXoYNffNgezV0XQ= =bR8y -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 01:25:49 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F5C216A416 for ; Thu, 12 Oct 2006 01:25:49 +0000 (UTC) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35DA843D45 for ; Thu, 12 Oct 2006 01:25:49 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id BE307F1D16; Wed, 11 Oct 2006 18:25:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at mcneil.com Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShUQRiRmnMBL; Wed, 11 Oct 2006 18:25:46 -0700 (PDT) Received: from ferrari (ferrari.mcneil.com [10.1.0.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.mcneil.com (Postfix) with ESMTP id DCF76F1835; Wed, 11 Oct 2006 18:25:46 -0700 (PDT) Message-ID: <001e01c6ed9d$56a74910$67e90b93@ferrari> From: "Sean McNeil" To: "Stephanie" , "Steve Kargl" References: <20061011225348.GA16838@everest.sosdg.org><20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> Date: Wed, 11 Oct 2006 18:25:43 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 01:25:49 -0000 ----- Original Message ----- From: "Stephanie" To: "Steve Kargl" Cc: Sent: Wednesday, October 11, 2006 5:57 PM Subject: Re: wine still unusable? > Steve Kargl wrote: > >>Perhaps, you should take up the challenge and port wine to amd64. You've >>had over a year to study the problem. >> >> > > I appreciate your overconfidence in my abilities, but if it were within my > technical capabilities to fix, it would have been and patches would have > been submitted. > > Since its not, I'm still waiting on anyone that possesses the level of > knowledge required to fix the problem to actually do so. You could try to install wine under linux emulation. That is 32-bits and works for a lot of other things. From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 01:47:45 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A88516A403 for ; Thu, 12 Oct 2006 01:47:45 +0000 (UTC) (envelope-from igor@hybrid-lab.co.uk) Received: from mra02.ch.as12513.net (mra02.ch.as12513.net [82.153.254.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAAE243D53 for ; Thu, 12 Oct 2006 01:47:44 +0000 (GMT) (envelope-from igor@hybrid-lab.co.uk) Received: from localhost (localhost [127.0.0.1]) by mra02.ch.as12513.net (Postfix) with ESMTP id 205EED447F; Thu, 12 Oct 2006 02:47:43 +0100 (BST) Received: from mra02.ch.as12513.net ([127.0.0.1]) by localhost (mra02.ch.as12513.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30543-01-81; Thu, 12 Oct 2006 02:47:42 +0100 (BST) Received: from [81.168.65.143] (unknown [81.168.65.143]) by mra02.ch.as12513.net (Postfix) with ESMTP id D2EC6D4277; Thu, 12 Oct 2006 02:47:41 +0100 (BST) In-Reply-To: <001e01c6ed9d$56a74910$67e90b93@ferrari> References: <20061011225348.GA16838@everest.sosdg.org><20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> <001e01c6ed9d$56a74910$67e90b93@ferrari> Mime-Version: 1.0 (Apple Message framework v752.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <93884FD6-3D72-4067-BAB8-181403B3B092@hybrid-lab.co.uk> Content-Transfer-Encoding: 7bit From: Igor Mozolevsky Date: Thu, 12 Oct 2006 02:47:59 +0100 To: Sean McNeil X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 01:47:45 -0000 On 12 Oct 2006, at 02:25, Sean McNeil wrote: > > You could try to install wine under linux emulation. That is 32- > bits and works for a lot of other things. Has anybody tried win4bsd? From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 02:21:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6746616A40F for ; Thu, 12 Oct 2006 02:21:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDECA43D5D for ; Thu, 12 Oct 2006 02:21:54 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.8/8.13.8) with ESMTP id k9C2Jel9003839; Wed, 11 Oct 2006 19:19:40 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.8/8.13.8/Submit) id k9C2JeZH003838; Wed, 11 Oct 2006 19:19:40 -0700 (PDT) (envelope-from sgk) Date: Wed, 11 Oct 2006 19:19:40 -0700 From: Steve Kargl To: Igor Mozolevsky , g@troutmask.apl.washington.edu Message-ID: <20061012021940.GA3783@troutmask.apl.washington.edu> References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 02:21:58 -0000 On Thu, Oct 12, 2006 at 02:07:48AM +0100, Igor Mozolevsky wrote: > > I do like the FreeBSD community approach to bug reports - fix it > yourself and send us a patch! Having thought that PR stood for > Problem Report, it is becoming clear that it actually stands for > Problem Resolution!.. > It's simply reality. There are too few developers and too many bugs and feature requests. If someone has been waiting over a year for progress on a port and nothing has appeared, then it's probably easy to guess no one is working on that particular port. You have three choices: 1) Pay someone to fix, 2) fix it yourself, or 3) waiting until it appears from Kris' black box. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 02:22:28 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3BE616A407 for ; Thu, 12 Oct 2006 02:22:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A899D43D78 for ; Thu, 12 Oct 2006 02:22:22 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.8/8.13.8) with ESMTP id k9C2K85e003864; Wed, 11 Oct 2006 19:20:08 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.8/8.13.8/Submit) id k9C2K84q003863; Wed, 11 Oct 2006 19:20:08 -0700 (PDT) (envelope-from sgk) Date: Wed, 11 Oct 2006 19:20:08 -0700 From: Steve Kargl To: Igor Mozolevsky Message-ID: <20061012021940.GA3783@troutmask.apl.washington.edu> References: <20061011225348.GA16838@everest.sosdg.org> <20061011232316.GA2751@troutmask.apl.washington.edu> <452D9305.5060901@sosdg.org> <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40E10B8D-B3DB-4D53-9195-561B9DE50135@hybrid-lab.co.uk> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@freebsd.org Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 02:22:28 -0000 On Thu, Oct 12, 2006 at 02:07:48AM +0100, Igor Mozolevsky wrote: > > I do like the FreeBSD community approach to bug reports - fix it > yourself and send us a patch! Having thought that PR stood for > Problem Report, it is becoming clear that it actually stands for > Problem Resolution!.. > It's simply reality. There are too few developers and too many bugs and feature requests. If someone has been waiting over a year for progress on a port and nothing has appeared, then it's probably easy to guess no one is working on that particular port. You have three choices: 1) Pay someone to fix, 2) fix it yourself, or 3) waiting until it appears from Kris' black box. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 02:34:42 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70C3B16A412; Thu, 12 Oct 2006 02:34:42 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1131D43D53; Thu, 12 Oct 2006 02:34:41 +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.6/8.13.6) with ESMTP id k9C2YfpV015346; Wed, 11 Oct 2006 22:34:41 -0400 (EDT) (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.8/8.13.8) with ESMTP id k9C2YfBI026483; Wed, 11 Oct 2006 22:34:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B425A7305F; Wed, 11 Oct 2006 22:34:40 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061012023440.B425A7305F@freebsd-current.sentex.ca> Date: Wed, 11 Oct 2006 22:34:40 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 02:34:42 -0000 TB --- 2006-10-12 00:44:20 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-12 00:44:20 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-12 00:44:20 - cleaning the object tree TB --- 2006-10-12 00:45:13 - checking out the source tree TB --- 2006-10-12 00:45:13 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-12 00:45:13 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-12 00:55:57 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-12 00:55:57 - cd /src TB --- 2006-10-12 00:55:57 - /usr/bin/make -B buildworld >>> World build started on Thu Oct 12 00:55:58 UTC 2006 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Oct 12 02:10:37 UTC 2006 TB --- 2006-10-12 02:10:37 - generating LINT kernel config TB --- 2006-10-12 02:10:37 - cd /src/sys/amd64/conf TB --- 2006-10-12 02:10:37 - /usr/bin/make -B LINT TB --- 2006-10-12 02:10:37 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-12 02:10:37 - cd /src TB --- 2006-10-12 02:10:37 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Oct 12 02:10:37 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Thu Oct 12 02:28:06 UTC 2006 TB --- 2006-10-12 02:28:06 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-12 02:28:06 - cd /src TB --- 2006-10-12 02:28:06 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Oct 12 02:28:06 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/amd64/amd64/intr_machdep.c:382: error: `ICW1_RESET' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:382: error: `ICW1_IC4' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:383: error: `ICU_IMR_OFFSET' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:383: error: `IDT_IO_INTS' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:385: error: `ICW4_8086' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: `OCW3_SEL' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: `OCW3_RR' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:389: error: `IO_ICU2' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-12 02:34:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-12 02:34:40 - ERROR: failed to build GENERIC kernel TB --- 2006-10-12 02:34:40 - tinderbox aborted TB --- 0.97 user 3.03 system 6619.48 real From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 05:53:13 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 538DE16A403 for ; Thu, 12 Oct 2006 05:53:13 +0000 (UTC) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 057BF43D55 for ; Thu, 12 Oct 2006 05:53:12 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id D064CF887 for ; Wed, 11 Oct 2006 23:53:11 -0600 (MDT) Received: from shredder.teamcool.net (unknown [192.168.1.58]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 9754DF881 for ; Wed, 11 Oct 2006 23:53:11 -0600 (MDT) Date: Wed, 11 Oct 2006 23:53:11 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20061011235311.e687ca06.kgunders@teamcool.net> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: tyan am2 boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 05:53:13 -0000 Greetings All: Perchance does anyone have any experience with either of these Tyan AM2 boards they could share?? Tomcat n3400B (S2925) - nVidia nForce Pro 3400 based Tomcat h1000S (S3950) - Broadcom ht1000 based TIA-- -- Best regards, Ken Gunderson "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 05:54:53 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF5CC16A412 for ; Thu, 12 Oct 2006 05:54:53 +0000 (UTC) (envelope-from simakin@dtd.peterstar.com) Received: from relay.peterstar.ru (news.peterstar.ru [217.195.65.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1D4843D4C for ; Thu, 12 Oct 2006 05:54:52 +0000 (GMT) (envelope-from simakin@dtd.peterstar.com) Received: from alx.dtd (D0-2-321.ip.PeterStar.net [217.195.91.5]) by relay.peterstar.ru (8.13.8/8.11.4) with ESMTP id k9C5sn2B025247 for ; Thu, 12 Oct 2006 09:54:50 +0400 (MSD) Date: Thu, 12 Oct 2006 09:55:49 +0400 From: Simakin Alexandr X-Mailer: The Bat! (v3.0.1.33) Professional Organization: PeterStar X-Priority: 3 (Normal) Message-ID: <185585601.20061012095549@dtd.peterstar.com> To: amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 352 [Oct 11 2006] X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0242], KAS30/Release Cc: Subject: Opteron 2000 Series with DDR2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Simakin Alexandr List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 05:54:54 -0000 Hello! Does anybody have test 6.1-STABLE on new CPU from AMD Opteron "Next-Generation AMD Opteron processors with DDR2 2000 Series"? -- Best regards, Alexandr Simakin mailto:simakin@dtd.peterstar.com From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 06:30:20 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E71316A403 for ; Thu, 12 Oct 2006 06:30:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6FE43D55 for ; Thu, 12 Oct 2006 06:30:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9C6UJtN057841 for ; Thu, 12 Oct 2006 06:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9C6UJdK057840; Thu, 12 Oct 2006 06:30:19 GMT (envelope-from gnats) Date: Thu, 12 Oct 2006 06:30:19 GMT Message-Id: <200610120630.k9C6UJdK057840@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Scot Hetzel" Cc: Subject: Re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Oct 2006 06:30:20 -0000 The following reply was made to PR amd64/104311; it has been noted by GNATS. From: "Scot Hetzel" To: bug-followup@FreeBSD.org, stephanie@sosdg.org Cc: Subject: Re: amd64/104311: ports/wine should be installable on amd64 Date: Thu, 12 Oct 2006 01:25:37 -0500 > ports/wine is not installable under amd64 under any version of freebsd to date. I don't remember what the underlying technical problem is, but this makes the amd64 build of freebsd absolutely useless to me, due to the need to run some Windows applications. The technical problem is that to build wine under amd64, you need to be able to build 32bit libraries for all of wine's dependant ports. You can make wine run on amd64, but you must first build it on i386. Then copy it to your amd64 system, including all of the library dependancies (untested). Wine64 (the 64bit version of wine) will not build on FreeBSD/amd64 due to it needs someone to write the code to save/restore the cpu registers. Wine64 will only run 64bit windows applications, you won't be able to run 32bit windows applications on wine64. If wine is important to you, then you have 3 choices: 1. submit patches to create the lib32-* library ports and the necessary patches to Mk/bsd.ports.mk and emulators/wine to allow it to build on the amd64 architecture. 2. Set your system to dual boot FreeBSD/amd64 and FreeBSD/i386. 3. Reinstall your system with FreeBSD/i386 only. Scot From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 07:00:07 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57DA216A407 for ; Thu, 12 Oct 2006 07:00:07 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta02ps.mx.bigpond.com (omta02ps.mx.bigpond.com [144.140.83.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F73743D5A for ; Thu, 12 Oct 2006 07:00:05 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.2.3]) by omta02ps.mx.bigpond.com with ESMTP id <20061012070003.XMYV16502.omta02ps.mx.bigpond.com@areilly.bpa.nu> for ; Thu, 12 Oct 2006 07:00:03 +0000 Received: (qmail 49494 invoked by uid 501); 12 Oct 2006 06:58:29 -0000 Date: Thu, 12 Oct 2006 16:58:29 +1000 From: Andrew Reilly To: Scot Hetzel Message-ID: <20061012065829.GA49071@duncan.reilly.home> References: <200610120630.k9C6UJdK057840@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200610120630.k9C6UJdK057840@freefall.freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 07:00:07 -0000 On Thu, Oct 12, 2006 at 06:30:19AM +0000, Scot Hetzel wrote: > The technical problem is that to build wine under amd64, you need to > be able to build 32bit libraries for all of wine's dependant ports. > > You can make wine run on amd64, but you must first build it on i386. > Then copy it to your amd64 system, including all of the library > dependancies (untested). That's what I thought, although I haven't needed Wine for so long that I haven't tried it, yet. > Wine64 (the 64bit version of wine) will not build on FreeBSD/amd64 due > to it needs someone to write the code to save/restore the cpu > registers. Wine64 will only run 64bit windows applications, you won't > be able to run 32bit windows applications on wine64. Not very interesting, then :-) > If wine is important to you, then you have 3 choices: > > 1. submit patches to create the lib32-* library ports and the > necessary patches to Mk/bsd.ports.mk and emulators/wine to allow it to > build on the amd64 architecture. > > 2. Set your system to dual boot FreeBSD/amd64 and FreeBSD/i386. > > 3. Reinstall your system with FreeBSD/i386 only. 4. Set up a FreeBSD/i386 build environment inside a qemu (or similar) virtual session. 5. Build it and make a package on another (i386) pc. 6.(?) There seems to have been some discussion about doing Linux-i386 builds within the linuxulator. Emulating windows on a linux emulation isn't such a stretch :-) [Personally, I think that option 1 going to be very useful and quite widely applicable, and therefore bound to happen sooner or later. The win32 binary video codec afficianados will probably get there first...] Cheers, -- Andrew From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 10:50:25 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97AFA16A412 for ; Thu, 12 Oct 2006 10:50:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B2D043D55 for ; Thu, 12 Oct 2006 10:50:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9CAoNuZ080787 for ; Thu, 12 Oct 2006 10:50:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9CAoN6V080786; Thu, 12 Oct 2006 10:50:23 GMT (envelope-from gnats) Date: Thu, 12 Oct 2006 10:50:23 GMT Message-Id: <200610121050.k9CAoN6V080786@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "James O'Gorman" Cc: Subject: Re: amd64/85812: "Rebooting..." on serial console appears garbled X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: James O'Gorman List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 10:50:25 -0000 The following reply was made to PR amd64/85812; it has been noted by GNATS. From: James O'Gorman To: bug-followup@FreeBSD.org, james@netinertia.co.uk Cc: Subject: Re: amd64/85812: "Rebooting..." on serial console appears garbled Date: Thu, 12 Oct 2006 11:49:20 +0100 Having just realised I still have this PR open, I do wonder whether it's more to do with my Dell server (or its BIOS) than FreeBSD itself; when booting loader seems to redraw the entire screen for every new character, or during the autoboot countdown (which is very slow over 9600 baud connection!) As I put very little information in the PR and it's not a huge issue, this can probably be closed. James From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 14:16:14 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10EFC16A403 for ; Thu, 12 Oct 2006 14:16:14 +0000 (UTC) (envelope-from mwm-dated-1161526325.c27e33@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id E9F5D43DBB for ; Thu, 12 Oct 2006 14:12:02 +0000 (GMT) (envelope-from mwm-dated-1161526325.c27e33@mired.org) Received: (qmail 38204 invoked by uid 1001); 12 Oct 2006 14:12:05 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 12 Oct 2006 10:12:05 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17710.19765.93325.631579@bhuda.mired.org> Date: Thu, 12 Oct 2006 10:12:05 -0400 To: Andrew Reilly In-Reply-To: <20061012065829.GA49071@duncan.reilly.home> References: <200610120630.k9C6UJdK057840@freefall.freebsd.org> <20061012065829.GA49071@duncan.reilly.home> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 14:16:14 -0000 In <20061012065829.GA49071@duncan.reilly.home>, Andrew Reilly typed: > > Wine64 (the 64bit version of wine) will not build on FreeBSD/amd64 due > > to it needs someone to write the code to save/restore the cpu > > registers. Wine64 will only run 64bit windows applications, you won't > > be able to run 32bit windows applications on wine64. > Not very interesting, then :-) The official wine wiki page on Wine64 starts by saying "This port is not yet functional", and gives a long list of problems. That would make it seem that answer to the OP's question might be "It won't get here until the wine people finish the port." > > If wine is important to you, then you have 3 choices: > > > > 1. submit patches to create the lib32-* library ports and the > > necessary patches to Mk/bsd.ports.mk and emulators/wine to allow it to > > build on the amd64 architecture. > > > > 2. Set your system to dual boot FreeBSD/amd64 and FreeBSD/i386. > > > > 3. Reinstall your system with FreeBSD/i386 only. > > 4. Set up a FreeBSD/i386 build environment inside a qemu (or > similar) virtual session. > > 5. Build it and make a package on another (i386) pc. The package has to include the dependency libs down to the system level - and instructions on how to install 32-bit versions of the system library. > 6.(?) There seems to have been some discussion about doing > Linux-i386 builds within the linuxulator. Emulating windows on > a linux emulation isn't such a stretch :-) Since both Wine and the linuxolartor are compatability layers rather than emulators, this shouldn't be to bad. In particular, you should be able to install the binaries. > [Personally, I think that option 1 going to be very useful and > quite widely applicable, and therefore bound to happen sooner or > later. The win32 binary video codec afficianados will probably > get there first...] Yeah, I ran into that with the Perforce port. It needed a 32-bit library, and when trying to install the port it built the 64-bit version, then croaked because it was already installed. Fixing the base system compiler so that '-m32' works properly would be nice as well, and may get done as part of this. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 14:31:45 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C842316A4F1 for ; Thu, 12 Oct 2006 14:31:45 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F8D743E81 for ; Thu, 12 Oct 2006 14:30:31 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1GY1Zu-000CWv-1D for amd64@freebsd.org; Thu, 12 Oct 2006 15:30:30 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GY1Zt-000Gi6-Lr for amd64@freebsd.org; Thu, 12 Oct 2006 15:30:29 +0100 To: amd64@freebsd.org Message-Id: From: Pete French Date: Thu, 12 Oct 2006 15:30:29 +0100 Cc: Subject: re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 14:31:45 -0000 > If wine is important to you, then you have 3 choices: > > 1. submit patches to create the lib32-* library ports and the > necessary patches to Mk/bsd.ports.mk and emulators/wine to allow it to > build on the amd64 architecture. Hmmm, now what I am about to suggest is probably going to sound stupid, but when I need to run a 32 bit executable under 64 bit I dont bother with all that library junk, I simply static link it. So would it not be possible just to produce a staticly linked wine executable and install that ? No need for library ports and fixing dynamic linking or any of that stuff. It's always worked fine for me with my own code, I dont see why it couldnt be applied to ports too. How hard is it to tell wine (or any other port) to build staticly when it is being compiled on an i386 box ? -pete. From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 15:36:55 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A7516A4A7; Thu, 12 Oct 2006 15:36:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE2F343D5D; Thu, 12 Oct 2006 15:36:36 +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.6/8.13.6) with ESMTP id k9CFaZu6009780; Thu, 12 Oct 2006 11:36:35 -0400 (EDT) (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.8/8.13.8) with ESMTP id k9CFaZQD025101; Thu, 12 Oct 2006 11:36:35 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2F2277305F; Thu, 12 Oct 2006 11:36:35 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061012153635.2F2277305F@freebsd-current.sentex.ca> Date: Thu, 12 Oct 2006 11:36:35 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner3 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 15:36:55 -0000 TB --- 2006-10-12 13:47:49 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-12 13:47:49 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-12 13:47:49 - cleaning the object tree TB --- 2006-10-12 13:48:25 - checking out the source tree TB --- 2006-10-12 13:48:25 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-12 13:48:25 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-12 13:57:20 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-12 13:57:20 - cd /src TB --- 2006-10-12 13:57:20 - /usr/bin/make -B buildworld >>> World build started on Thu Oct 12 13:57:23 UTC 2006 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Oct 12 15:12:22 UTC 2006 TB --- 2006-10-12 15:12:22 - generating LINT kernel config TB --- 2006-10-12 15:12:22 - cd /src/sys/amd64/conf TB --- 2006-10-12 15:12:22 - /usr/bin/make -B LINT TB --- 2006-10-12 15:12:25 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-12 15:12:25 - cd /src TB --- 2006-10-12 15:12:25 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Oct 12 15:12:25 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Thu Oct 12 15:30:10 UTC 2006 TB --- 2006-10-12 15:30:10 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-12 15:30:10 - cd /src TB --- 2006-10-12 15:30:10 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Oct 12 15:30:10 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -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 /src/sys/amd64/amd64/initcpu.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -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 /src/sys/amd64/amd64/intr_machdep.c /src/sys/amd64/amd64/intr_machdep.c: In function `atpic_reset': /src/sys/amd64/amd64/intr_machdep.c:387: error: `IO_ICU1' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: (Each undeclared identifier is reported only once /src/sys/amd64/amd64/intr_machdep.c:387: error: for each function it appears in.) /src/sys/amd64/amd64/intr_machdep.c:388: error: `IDT_IO_INTS' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:394: error: `IO_ICU2' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-12 15:36:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-12 15:36:34 - ERROR: failed to build GENERIC kernel TB --- 2006-10-12 15:36:34 - tinderbox aborted TB --- 0.96 user 3.02 system 6525.12 real From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 12 16:24:15 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F5C216A4AB for ; Thu, 12 Oct 2006 16:24:15 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E319543D80 for ; Thu, 12 Oct 2006 16:23:47 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J7100FHG6VMCF50@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 12 Oct 2006 18:23:46 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.21.224]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J71008B26VMTS62@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 12 Oct 2006 18:23:46 +0200 (CEST) Date: Thu, 12 Oct 2006 18:23:45 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20061011225348.GA16838@everest.sosdg.org> To: freebsd-amd64@freebsd.org Message-id: <20061012182345.8990a6da.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable References: <20061011225348.GA16838@everest.sosdg.org> Subject: Re: wine still unusable? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 16:24:15 -0000 On Wed, 11 Oct 2006 18:53:49 -0400 Stephanie Erin Daugherty wrote: > Out of curiosity, is there no demand for wine under amd64, or does No there is no demand. What would you use Wine for? There are good alternative choices for 99% of all applications that run under Windows. (Yes, I know some will disagree with that number - don't bikeshed this issue.) > What's taking so long? I guess you having done anything about it, for example trying to port Wine. Just my 0.002 =BD --=20 Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 13 04:20:50 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA0A716A403; Fri, 13 Oct 2006 04:20:50 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6625243D45; Fri, 13 Oct 2006 04:20:50 +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.6/8.13.6) with ESMTP id k9D4Kn7Q018114; Fri, 13 Oct 2006 00:20:49 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id k9D4KnFm095023; Fri, 13 Oct 2006 00:20:49 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1B8747305F; Fri, 13 Oct 2006 00:20:48 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061013042049.1B8747305F@freebsd-current.sentex.ca> Date: Fri, 13 Oct 2006 00:20:48 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner4 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 04:20:50 -0000 TB --- 2006-10-13 02:30:47 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-13 02:30:47 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-13 02:30:47 - cleaning the object tree TB --- 2006-10-13 02:31:29 - checking out the source tree TB --- 2006-10-13 02:31:29 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-13 02:31:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-13 02:40:32 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-13 02:40:32 - cd /src TB --- 2006-10-13 02:40:32 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 13 02:40:33 UTC 2006 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Fri Oct 13 03:56:29 UTC 2006 TB --- 2006-10-13 03:56:29 - generating LINT kernel config TB --- 2006-10-13 03:56:29 - cd /src/sys/amd64/conf TB --- 2006-10-13 03:56:29 - /usr/bin/make -B LINT TB --- 2006-10-13 03:56:29 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-13 03:56:29 - cd /src TB --- 2006-10-13 03:56:29 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Oct 13 03:56:29 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Oct 13 04:14:12 UTC 2006 TB --- 2006-10-13 04:14:12 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-10-13 04:14:12 - cd /src TB --- 2006-10-13 04:14:12 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Oct 13 04:14:12 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -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 /src/sys/amd64/amd64/initcpu.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -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 /src/sys/amd64/amd64/intr_machdep.c /src/sys/amd64/amd64/intr_machdep.c: In function `atpic_reset': /src/sys/amd64/amd64/intr_machdep.c:387: error: `IO_ICU1' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:387: error: (Each undeclared identifier is reported only once /src/sys/amd64/amd64/intr_machdep.c:387: error: for each function it appears in.) /src/sys/amd64/amd64/intr_machdep.c:388: error: `IDT_IO_INTS' undeclared (first use in this function) /src/sys/amd64/amd64/intr_machdep.c:394: error: `IO_ICU2' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-13 04:20:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-13 04:20:48 - ERROR: failed to build GENERIC kernel TB --- 2006-10-13 04:20:48 - tinderbox aborted TB --- 0.89 user 3.09 system 6601.73 real From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 13 04:32:16 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBF2B16A403 for ; Fri, 13 Oct 2006 04:32:16 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta05ps.mx.bigpond.com (omta05ps.mx.bigpond.com [144.140.83.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2750B43D58 for ; Fri, 13 Oct 2006 04:32:15 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.2.3]) by omta05ps.mx.bigpond.com with ESMTP id <20061013043210.ITAL22583.omta05ps.mx.bigpond.com@areilly.bpa.nu> for ; Fri, 13 Oct 2006 04:32:10 +0000 Received: (qmail 72607 invoked by uid 501); 13 Oct 2006 04:30:34 -0000 Date: Fri, 13 Oct 2006 14:30:34 +1000 From: Andrew Reilly To: Pete French Message-ID: <20061013043034.GA71990@duncan.reilly.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: amd64@freebsd.org Subject: Re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 04:32:16 -0000 On Thu, Oct 12, 2006 at 03:30:29PM +0100, Pete French wrote: > > If wine is important to you, then you have 3 choices: > > > > 1. submit patches to create the lib32-* library ports and the > > necessary patches to Mk/bsd.ports.mk and emulators/wine to allow it to > > build on the amd64 architecture. > > Hmmm, now what I am about to suggest is probably going to sound stupid, > but when I need to run a 32 bit executable under 64 bit I dont bother with > all that library junk, I simply static link it. So would it not be possible > just to produce a staticly linked wine executable and install that ? No > need for library ports and fixing dynamic linking or any of that stuff. > It's always worked fine for me with my own code, I dont see why it couldnt > be applied to ports too. > > How hard is it to tell wine (or any other port) to build staticly when it is > being compiled on an i386 box ? That won't work with wine, I'm fairly certain. In order to look sufficiently similar to a Windows environment, you have to have something that looks like DLLs. Wine, just like Windows, has a gazillion dynamically loadable libraries, for that reason. Run-time linking is very much part of the windows experience... Cheers, -- Andrew From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 13 10:55:58 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE72E16A403 for ; Fri, 13 Oct 2006 10:55:58 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B1A943D69 for ; Fri, 13 Oct 2006 10:55:58 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1GYKhl-000NpV-PO; Fri, 13 Oct 2006 11:55:53 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GYKhl-0002M0-Ke; Fri, 13 Oct 2006 11:55:53 +0100 To: andrew-freebsd@areilly.bpc-users.org In-Reply-To: <20061013043034.GA71990@duncan.reilly.home> Message-Id: From: Pete French Date: Fri, 13 Oct 2006 11:55:53 +0100 Cc: amd64@freebsd.org Subject: Re: amd64/104311: ports/wine should be installable on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 10:55:59 -0000 > That won't work with wine, I'm fairly certain. In order to look > sufficiently similar to a Windows environment, you have to have > something that looks like DLLs. Wine, just like Windows, has a > gazillion dynamically loadable libraries, for that reason. > Run-time linking is very much part of the windows experience... Ah, O.K. - do theres a Unix linkable shared library to match each Windows DLL ? Didn't realise that, I assumed it just used the actual Windows DLL's directly somehow. The other part of the question about making ports link staticly still stands though - anyone know of an easy way to do this ? cheers, -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 13 12:58:11 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 128B016A492; Fri, 13 Oct 2006 12:58:11 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8053D43D53; Fri, 13 Oct 2006 12:58:10 +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.6/8.13.6) with ESMTP id k9DCw91v001450; Fri, 13 Oct 2006 08:58:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.8/8.13.8) with ESMTP id k9DCw9OK011520; Fri, 13 Oct 2006 08:58:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C85187305F; Fri, 13 Oct 2006 08:58:08 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061013125808.C85187305F@freebsd-current.sentex.ca> Date: Fri, 13 Oct 2006 08:58:08 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner1 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 12:58:11 -0000 TB --- 2006-10-13 12:06:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-13 12:06:14 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2006-10-13 12:06:14 - cleaning the object tree TB --- 2006-10-13 12:06:45 - checking out the source tree TB --- 2006-10-13 12:06:45 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2006-10-13 12:06:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-10-13 12:18:00 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-13 12:18:00 - cd /src TB --- 2006-10-13 12:18:00 - /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 [...] rm -f .depend mkdep -f .depend -a -DRESCUE /src/sbin/mount/mount.c /src/sbin/mount/mount_ufs.c /src/sbin/mount/getmntopts.c /src/sbin/mount/vfslist.c echo mount: /obj/amd64/src/tmp/usr/lib/libc.a >> .depend cc -O2 -pipe -DRESCUE -c /src/sbin/mount/mount.c /src/sbin/mount/mount.c: In function `mountfs': /src/sbin/mount/mount.c:432: error: `fstab' undeclared (first use in this function) /src/sbin/mount/mount.c:432: error: (Each undeclared identifier is reported only once /src/sbin/mount/mount.c:432: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/mount. *** Error code 1 Stop in /obj/amd64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-13 12:58:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-13 12:58:08 - ERROR: failed to build world TB --- 2006-10-13 12:58:08 - tinderbox aborted TB --- 0.96 user 3.06 system 3114.29 real From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 13 18:33:57 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D54AD16A407; Fri, 13 Oct 2006 18:33:57 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7563043D78; Fri, 13 Oct 2006 18:33:57 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9DIXv1w058878; Fri, 13 Oct 2006 18:33:57 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9DIXu05058874; Fri, 13 Oct 2006 18:33:56 GMT (envelope-from linimon) Date: Fri, 13 Oct 2006 18:33:56 GMT From: Mark Linimon Message-Id: <200610131833.k9DIXu05058874@freefall.freebsd.org> To: james@netinertia.co.uk, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/85812: "Rebooting..." on serial console appears garbled X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 18:33:57 -0000 Synopsis: "Rebooting..." on serial console appears garbled State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Fri Oct 13 18:33:42 UTC 2006 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=85812