From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:00: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 380B716A422; Sun, 2 Apr 2006 10:00:20 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C867243D45; Sun, 2 Apr 2006 10:00:19 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A0J78013632; Sun, 2 Apr 2006 10:00:19 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A0ImM013628; Sun, 2 Apr 2006 10:00:18 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:00:18 GMT From: Matteo Riondato Message-Id: <200604021000.k32A0ImM013628@freefall.freebsd.org> To: tomaz.borstnar@over.net, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M 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, 02 Apr 2006 10:00:20 -0000 Synopsis: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M State-Changed-From-To: open->closed State-Changed-By: matteo State-Changed-When: Sun Apr 2 09:59:51 UTC 2006 State-Changed-Why: submitter said this has been fixed in 5.4 http://www.freebsd.org/cgi/query-pr.cgi?pr=71471 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:02:21 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 13A5816A426; Sun, 2 Apr 2006 10:02:21 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C648243D45; Sun, 2 Apr 2006 10:02:20 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A2KQd013797; Sun, 2 Apr 2006 10:02:20 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A2KYY013793; Sun, 2 Apr 2006 10:02:20 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:02:20 GMT From: Matteo Riondato Message-Id: <200604021002.k32A2KYY013793@freefall.freebsd.org> To: tobias.m81@web.de, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/74014: 5.3-RELEASE-AMD64 freezes on boot during installation due to USB problems 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, 02 Apr 2006 10:02:21 -0000 Synopsis: 5.3-RELEASE-AMD64 freezes on boot during installation due to USB problems State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:01:53 UTC 2006 State-Changed-Why: Are you still having this issue? http://www.freebsd.org/cgi/query-pr.cgi?pr=74014 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:02: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 9BC8516A423; Sun, 2 Apr 2006 10:02:48 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BFD843D48; Sun, 2 Apr 2006 10:02:48 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A2mk3013846; Sun, 2 Apr 2006 10:02:48 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A2mEA013842; Sun, 2 Apr 2006 10:02:48 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:02:48 GMT From: Matteo Riondato Message-Id: <200604021002.k32A2mEA013842@freefall.freebsd.org> To: matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/74014: 5.3-RELEASE-AMD64 freezes on boot during installation due to USB problems 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, 02 Apr 2006 10:02:48 -0000 Synopsis: 5.3-RELEASE-AMD64 freezes on boot during installation due to USB problems Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:02:25 UTC 2006 Responsible-Changed-Why: Grab this so I can take care of feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=74014 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:04:17 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 632FE16A426; Sun, 2 Apr 2006 10:04:17 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FF6743D46; Sun, 2 Apr 2006 10:04:17 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A4Gp5013983; Sun, 2 Apr 2006 10:04:16 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A4Gd9013979; Sun, 2 Apr 2006 10:04:16 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:04:16 GMT From: Matteo Riondato Message-Id: <200604021004.k32A4Gd9013979@freefall.freebsd.org> To: tastyummy@hotmail.com, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/75209: 5.3-Release panics on attempted boot from install CD 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, 02 Apr 2006 10:04:17 -0000 Synopsis: 5.3-Release panics on attempted boot from install CD State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:03:33 UTC 2006 State-Changed-Why: Are you still having this issue with recent 5.x or 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:03:33 UTC 2006 Responsible-Changed-Why: grab this so I can take care of feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=75209 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:05:37 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 E586C16A425; Sun, 2 Apr 2006 10:05:37 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E0B343D82; Sun, 2 Apr 2006 10:05:34 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A5Xjd014107; Sun, 2 Apr 2006 10:05:33 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A5XKt014103; Sun, 2 Apr 2006 10:05:33 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:05:33 GMT From: Matteo Riondato Message-Id: <200604021005.k32A5XKt014103@freefall.freebsd.org> To: stukov@xeatech.net, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/75417: ACPI: SATA Hard-disk 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, 02 Apr 2006 10:05:38 -0000 Synopsis: ACPI: SATA Hard-disk State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:04:40 UTC 2006 State-Changed-Why: Are you still having this issue with recent 5.x / 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:04:40 UTC 2006 Responsible-Changed-Why: Grab this so I can take care of the feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=75417 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:08:00 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 4C87D16A422; Sun, 2 Apr 2006 10:08:00 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07BF243D6D; Sun, 2 Apr 2006 10:08:00 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32A7x0W014219; Sun, 2 Apr 2006 10:07:59 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32A7vXR014206; Sun, 2 Apr 2006 10:07:57 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:07:57 GMT From: Matteo Riondato Message-Id: <200604021007.k32A7vXR014206@freefall.freebsd.org> To: dgilbert@daveg.ca, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/77011: consisten 5.3-p5 make crash on installworld. 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, 02 Apr 2006 10:08:00 -0000 Synopsis: consisten 5.3-p5 make crash on installworld. State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:07:13 UTC 2006 State-Changed-Why: Are you still having this issue with recent 5.x / 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:07:13 UTC 2006 Responsible-Changed-Why: Grab this, so I can take care of the feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=77011 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:12:01 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 5301016A401; Sun, 2 Apr 2006 10:12:01 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E01443D45; Sun, 2 Apr 2006 10:12:01 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32AC06J014421; Sun, 2 Apr 2006 10:12:00 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32AC073014412; Sun, 2 Apr 2006 10:12:00 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:12:00 GMT From: Matteo Riondato Message-Id: <200604021012.k32AC073014412@freefall.freebsd.org> To: frankzen@infinito.it, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/78558: installation 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, 02 Apr 2006 10:12:01 -0000 Synopsis: installation State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:11:20 UTC 2006 State-Changed-Why: Are you still having this issue with recent 5.x / 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:11:20 UTC 2006 Responsible-Changed-Why: Grab this, so I can take care of the feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=78558 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:13:34 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 47E1216A422; Sun, 2 Apr 2006 10:13:34 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0848B43D48; Sun, 2 Apr 2006 10:13:34 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32ADXX7014546; Sun, 2 Apr 2006 10:13:33 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32ADX1q014542; Sun, 2 Apr 2006 10:13:33 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:13:33 GMT From: Matteo Riondato Message-Id: <200604021013.k32ADX1q014542@freefall.freebsd.org> To: lenaig@wanadoo.fr, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/77949: Pb boot FreeBSD 64 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, 02 Apr 2006 10:13:34 -0000 Synopsis: Pb boot FreeBSD 64 State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:12:49 UTC 2006 State-Changed-Why: Are yuo still having this issue with recent 5.x / 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:12:49 UTC 2006 Responsible-Changed-Why: Grab this, so I can take care of the feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=77949 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:15: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 287C816A41F; Sun, 2 Apr 2006 10:15:25 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E2943D45; Sun, 2 Apr 2006 10:15:24 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32AFOXH014656; Sun, 2 Apr 2006 10:15:24 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32AFOpn014652; Sun, 2 Apr 2006 10:15:24 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:15:24 GMT From: Matteo Riondato Message-Id: <200604021015.k32AFOpn014652@freefall.freebsd.org> To: roemer.ulrich@gmx.de, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org, matteo@FreeBSD.org Cc: Subject: Re: amd64/59714: device timeout and ad0: WARNING - WRITE_DMA 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, 02 Apr 2006 10:15:25 -0000 Synopsis: device timeout and ad0: WARNING - WRITE_DMA State-Changed-From-To: open->feedback State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:14:36 UTC 2006 State-Changed-Why: Are you still having this issue with recent 5.x / 6.x ? Responsible-Changed-From-To: freebsd-amd64->matteo Responsible-Changed-By: matteo Responsible-Changed-When: Sun Apr 2 10:14:36 UTC 2006 Responsible-Changed-Why: Grab this, so I can take care of the feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=59714 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 10:19:10 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 3E12F16A423; Sun, 2 Apr 2006 10:19:10 +0000 (UTC) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F33C243D46; Sun, 2 Apr 2006 10:19:09 +0000 (GMT) (envelope-from matteo@FreeBSD.org) Received: from freefall.freebsd.org (matteo@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k32AJ98l014779; Sun, 2 Apr 2006 10:19:09 GMT (envelope-from matteo@freefall.freebsd.org) Received: (from matteo@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k32AJ9uE014775; Sun, 2 Apr 2006 10:19:09 GMT (envelope-from matteo) Date: Sun, 2 Apr 2006 10:19:09 GMT From: Matteo Riondato Message-Id: <200604021019.k32AJ9uE014775@freefall.freebsd.org> To: ted@hotmail.com, matteo@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/90798: asking if motherboard is compatible 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, 02 Apr 2006 10:19:10 -0000 Synopsis: asking if motherboard is compatible State-Changed-From-To: open->closed State-Changed-By: matteo State-Changed-When: Sun Apr 2 10:18:39 UTC 2006 State-Changed-Why: This kind of questions should be asked to the questions or amd64 mailing lists. Thanks http://www.freebsd.org/cgi/query-pr.cgi?pr=90798 From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 2 18:48:09 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 3C9CF16A427 for ; Sun, 2 Apr 2006 18:48:09 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp108.rog.mail.re2.yahoo.com (smtp108.rog.mail.re2.yahoo.com [68.142.225.206]) by mx1.FreeBSD.org (Postfix) with SMTP id AA85F43D49 for ; Sun, 2 Apr 2006 18:48:08 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 96746 invoked from network); 2 Apr 2006 18:48:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=AwF15iL2PTPGuadjIzbRIByZVYGazrj0xaNFOQ66Fw8O4rZbgoic/qYLaR8+Tgolc/eVyMU2Txn1TPbQbqW7BPpXZgWLQbB5UioAZla6V3tTUNZxkVKeWwB0gKamZ3ORJE3HPS86zl+wFPQ0ImshtLf3Yj3v1gPt3AXNuzYtCr8= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp108.rog.mail.re2.yahoo.com with SMTP; 2 Apr 2006 18:48:07 -0000 Message-ID: <44301C6D.3010206@rogers.com> Date: Sun, 02 Apr 2006 14:48:13 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Status of NX bit support. 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, 02 Apr 2006 18:48:09 -0000 I was wondering what the status of the NX bit support is. Is the pmap.c code still broken or is support enabled and functioning by default? From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 06:27:37 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 3799916A431 for ; Mon, 3 Apr 2006 06:27:37 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BC943D55 for ; Mon, 3 Apr 2006 06:27:34 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FQIXE-000GUg-Go for freebsd-amd64@freebsd.org; Mon, 03 Apr 2006 10:27:32 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FQIWt-000DmQ-Qm for freebsd-amd64@freebsd.org; Mon, 03 Apr 2006 10:27:11 +0400 Date: Mon, 3 Apr 2006 10:27:11 +0400 From: Igor Robul To: freebsd-amd64@freebsd.org Message-ID: <20060403062711.GA52962@sysadm.stc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: recommended PCI-E video card? 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, 03 Apr 2006 06:27:37 -0000 Hello, I'm planing to build AMD64 based workstation, and have one question: which PCI-Express video card works best with X.org on freebsd-amd64 in x64 mode? AFAIK nVidia does not have binary drivers for FreeBSD on AMD64, so what opensource driver works best for X.org+FreeBSD+AMD64? From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 07:05: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 6CE9C16A42D for ; Mon, 3 Apr 2006 07:05:07 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEDC943D5F for ; Mon, 3 Apr 2006 07:05:05 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k33753CG036700; Mon, 3 Apr 2006 01:05:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4430C91F.6070006@samsco.org> Date: Mon, 03 Apr 2006 01:05:03 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Igor Robul References: <20060403062711.GA52962@sysadm.stc> In-Reply-To: <20060403062711.GA52962@sysadm.stc> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: recommended PCI-E video card? 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, 03 Apr 2006 07:05:07 -0000 Igor Robul wrote: > Hello, > > I'm planing to build AMD64 based workstation, and have one question: > > which PCI-Express video card works best with X.org on freebsd-amd64 in > x64 mode? > > AFAIK nVidia does not have binary drivers for FreeBSD on AMD64, so what > opensource driver works best for X.org+FreeBSD+AMD64? When I looked at this a couple of months ago, the answer was that 2D works just fine, but there simply isn't any support for this configuration for 3D acceleration. Maybe that has changed recently. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 07:59: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 77AFC16A400 for ; Mon, 3 Apr 2006 07:59:38 +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 2028043D45 for ; Mon, 3 Apr 2006 07:59:37 +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 CD580F829 for ; Mon, 3 Apr 2006 01:59:32 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 98F8EF828 for ; Mon, 3 Apr 2006 01:59:32 -0600 (MDT) Date: Mon, 3 Apr 2006 01:59:31 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060403015931.2df6d5bb.kgunders@teamcool.net> In-Reply-To: <4430C91F.6070006@samsco.org> References: <20060403062711.GA52962@sysadm.stc> <4430C91F.6070006@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: recommended PCI-E video card? 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, 03 Apr 2006 07:59:38 -0000 On Mon, 03 Apr 2006 01:05:03 -0600 Scott Long wrote: > Igor Robul wrote: > > > Hello, > > > > I'm planing to build AMD64 based workstation, and have one question: > > > > which PCI-Express video card works best with X.org on freebsd-amd64 in > > x64 mode? > > > > AFAIK nVidia does not have binary drivers for FreeBSD on AMD64, so what > > opensource driver works best for X.org+FreeBSD+AMD64? > > When I looked at this a couple of months ago, the answer was that 2D > works just fine, but there simply isn't any support for this > configuration for 3D acceleration. Maybe that has changed recently. I looked at it a couple weeks back and nothing has changed. At lease w.r.t. ATI based pci-e cards. I've got some fairly inexpensive Radeon 300 based PCI- E cards w/128MB ram that I figure will be supported sooner or later... But if you want/need 3D today then look to an AGP based card. That puts you into an older MB though so.... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 08:45: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 823C616A425 for ; Mon, 3 Apr 2006 08:45:28 +0000 (UTC) (envelope-from taob@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3557243D53 for ; Mon, 3 Apr 2006 08:45:28 +0000 (GMT) (envelope-from taob@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id 203924AEF; Mon, 3 Apr 2006 04:45:27 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id 18CA14AED for ; Mon, 3 Apr 2006 04:45:27 -0400 (EDT) Date: Mon, 3 Apr 2006 04:45:26 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: freebsd-amd64@freebsd.org In-Reply-To: <20060208105613.GA1181@flame.pc> Message-ID: <20060403041523.N3698-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Disk I/O-related panics in 6.0-RELEASE? 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, 03 Apr 2006 08:45:28 -0000 Not sure if this is specifically an AMD64 issue or a 6.0 issue, but I'm leaning towards the former, so I'll start here. ;-) FreeBSD 6.0-RELEASE-p4 #2: Tue Feb 7 18:04:40 EST 2006 taob@cabal.dm.egate.net:/depot/obj/depot/src/sys/LUXOKERNEL I'm seeing unpredictable kernel panics that appear to be related to filesystem activity. I have yet to be able to produce the panic on demand. I've seen panics after 30 seconds of running the postmark benchmark, and other times it runs for hours without incident. buildworlds will cause a panic maybe 1 out of 3 attempts. The server is very lightly loaded (it is not yet in full-scale production). Crash dumps show that a variety of processes can trigger the panic. I've seen pax, ar, fgrep, and even sync, bufdaemon and fsck_ufs. The instruction pointer in the kernel dump points to a variety of places: # fgrep -h "is in" vmcore*/kgdb.txt 0xffffffff802a01c9 is in cluster_wbuild (/depot/src/sys/kern/vfs_cluster.c:904). 0xffffffff8034bc96 is in softdep_disk_io_initiation (/depot/src/sys/ufs/ffs/ffs_softdep.c:3597). 0xffffffff8037e010 is in vm_page_io_start (/depot/src/sys/vm/vm_page.c:345). 0xffffffff8029d5c0 is in bufstrategy (vnode_if.h:928). 0xffffffff802a8f49 is in buf_vlist_remove (/depot/src/sys/kern/vfs_subr.c:1343). 0xffffffff8034bc96 is in softdep_disk_io_initiation (/depot/src/sys/ufs/ffs/ffs_softdep.c:3597). 0xffffffff8037e010 is in vm_page_io_start (/depot/src/sys/vm/vm_page.c:345). I've collected the output of kgdb from nine crash dumps, my kernel config and the dmesg.boot here: http://www.luxography.ca/tmp/amd64_panics.tgz The system has probably panicked about twenty times in the past two months (it was turned up at the beginning of February). I'm hoping I can stick to the amd64 kernel, but I need better stability than this. Any help would be appreciated! -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 11:02:43 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE0BC16A401 for ; Mon, 3 Apr 2006 11:02:43 +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 3B4E543D5A for ; Mon, 3 Apr 2006 11:02:42 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k33B2fZs005803 for ; Mon, 3 Apr 2006 11:02:41 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k33B2eWn005797 for freebsd-amd64@freebsd.org; Mon, 3 Apr 2006 11:02:40 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Apr 2006 11:02:40 GMT Message-Id: <200604031102.k33B2eWn005797@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org 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, 03 Apr 2006 11:02:43 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing o [2006/03/01] amd64/93961 amd64 Problem in bounce buffer handling in sys/ 3 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMP o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/24] amd64/89501 amd64 System crashes on install using ftp on lo o [2005/11/24] amd64/89503 amd64 Cant Boot Installation Disk o [2005/11/25] amd64/89546 amd64 [geom] GEOM error o [2005/11/25] amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o [2005/11/25] amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o [2005/12/05] amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem o [2006/01/06] amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr o [2006/01/08] amd64/91492 amd64 BTX halted o [2006/01/26] amd64/92337 amd64 FreeBsd 6.0 Release Intel Pro 1000 MT em1 o [2006/02/06] amd64/92889 amd64 xdr double buffer overflow o [2006/02/07] amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk o [2006/02/08] amd64/93065 amd64 Running make depend on GENERIC kernel fai o [2006/02/14] amd64/93325 amd64 mount_ufs fails mounting Nero UFS DVD+RW o [2006/02/16] amd64/93413 amd64 lpd does not remove lock file from /var/s o [2006/02/17] amd64/93469 amd64 uninitialised struct stat in lpd prevents o [2006/03/19] amd64/94677 amd64 panic in amd64 install at non-root user c o [2006/03/24] amd64/94896 amd64 Where support VESA Modes for AMD64 kernel o [2006/03/27] amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 ( o [2006/03/28] amd64/95056 amd64 Nvidia Nforce ETH Driver -> Timeout Error o [2006/03/31] amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AI 61 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins o [2006/01/02] amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP o [2006/01/30] amd64/92527 amd64 no driver for "CICADA VSC 8201 Gigabit LA o [2006/02/07] amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable ti o [2006/02/09] amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognize o [2006/02/28] amd64/93930 amd64 Page fault on `kldunload snd_driver` 19 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 13:34: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 2675E16A475 for ; Mon, 3 Apr 2006 13:34:13 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av7-1-sn3.vrr.skanova.net (av7-1-sn3.vrr.skanova.net [81.228.9.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC5B943D4C for ; Mon, 3 Apr 2006 13:34:12 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 13E023815E; Mon, 3 Apr 2006 15:13:50 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 05DAE380C3; Mon, 3 Apr 2006 15:13:50 +0200 (CEST) Received: from 62-20-235-92-no21.tbcn.telia.com (62-20-235-92-no21.tbcn.telia.com [62.20.235.92]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 00AF837E4A; Mon, 3 Apr 2006 15:34:06 +0200 (CEST) From: Joel Dahl To: Scott Long In-Reply-To: <4430C91F.6070006@samsco.org> References: <20060403062711.GA52962@sysadm.stc> <4430C91F.6070006@samsco.org> Content-Type: text/plain Date: Mon, 03 Apr 2006 15:33:44 +0200 Message-Id: <1144071224.686.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: recommended PCI-E video card? 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, 03 Apr 2006 13:34:13 -0000 On Mon, 2006-04-03 at 01:05 -0600, Scott Long wrote: > Igor Robul wrote: > > > Hello, > > > > I'm planing to build AMD64 based workstation, and have one question: > > > > which PCI-Express video card works best with X.org on freebsd-amd64 in > > x64 mode? > > > > AFAIK nVidia does not have binary drivers for FreeBSD on AMD64, so what > > opensource driver works best for X.org+FreeBSD+AMD64? > > When I looked at this a couple of months ago, the answer was that 2D > works just fine, but there simply isn't any support for this > configuration for 3D acceleration. Maybe that has changed recently. True, however jhb is working on PAT (which AFAIK Nvidia needs if they're going to produce a driver for FreeBSD/amd64) in perforce and this commit message is quite interesting, especially the last sentence: http://perforce.freebsd.org/changeView.cgi?CH=93413 -- Joel From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 18:42: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 5D40E16A400 for ; Mon, 3 Apr 2006 18:42:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9760B43D45 for ; Mon, 3 Apr 2006 18:42:46 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k33IgjcI044311; Mon, 3 Apr 2006 14:42:45 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 3 Apr 2006 14:42:42 -0400 User-Agent: KMail/1.9.1 References: <44301C6D.3010206@rogers.com> In-Reply-To: <44301C6D.3010206@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604031442.43477.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1370/Mon Apr 3 13:31:59 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: Status of NX bit support. 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, 03 Apr 2006 18:42:47 -0000 On Sunday 02 April 2006 14:48, Mike Jakubik wrote: > I was wondering what the status of the NX bit support is. Is the pmap.c > code still broken or is support enabled and functioning by default? I don't think the status has changed. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 18:57: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 31DC116A401; Mon, 3 Apr 2006 18:57:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FD0743D48; Mon, 3 Apr 2006 18:57:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k33IuxJD044464; Mon, 3 Apr 2006 14:56:59 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 3 Apr 2006 14:43:51 -0400 User-Agent: KMail/1.9.1 References: <20060403062711.GA52962@sysadm.stc> <4430C91F.6070006@samsco.org> <1144071224.686.6.camel@localhost> In-Reply-To: <1144071224.686.6.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604031443.53372.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1370/Mon Apr 3 13:31:59 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: recommended PCI-E video card? 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, 03 Apr 2006 18:57:01 -0000 On Monday 03 April 2006 09:33, Joel Dahl wrote: > On Mon, 2006-04-03 at 01:05 -0600, Scott Long wrote: > > Igor Robul wrote: > > > > > Hello, > > > > > > I'm planing to build AMD64 based workstation, and have one question: > > > > > > which PCI-Express video card works best with X.org on freebsd-amd64 in > > > x64 mode? > > > > > > AFAIK nVidia does not have binary drivers for FreeBSD on AMD64, so what > > > opensource driver works best for X.org+FreeBSD+AMD64? > > > > When I looked at this a couple of months ago, the answer was that 2D > > works just fine, but there simply isn't any support for this > > configuration for 3D acceleration. Maybe that has changed recently. > > True, however jhb is working on PAT (which AFAIK Nvidia needs if they're > going to produce a driver for FreeBSD/amd64) in perforce and this commit > message is quite interesting, especially the last sentence: > > http://perforce.freebsd.org/changeView.cgi?CH=93413 I'm still waiting for feedback on the patch from Nvidia. Hopefully they will test the current PAT patch soon. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 20:01:10 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 72E5D16A427 for ; Mon, 3 Apr 2006 20:01:10 +0000 (UTC) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6D6643DD3 for ; Mon, 3 Apr 2006 20:00:43 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.80.165] (manz-d9b950a5.pool.mediaWays.net [217.185.80.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 8BF653000884; Mon, 3 Apr 2006 22:00:39 +0200 (CEST) Message-ID: <44317EE0.4010605@mail.uni-mainz.de> Date: Mon, 03 Apr 2006 22:00:32 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5 (X11/20060331) MIME-Version: 1.0 To: Anton Berezin , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> In-Reply-To: <20060327100330.GD58186@heechee.tobez.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 03 Apr 2006 20:01:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Berezin wrote: > On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: > >> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, but >> while compiling works on FreeBSD 6.1-PRE/AMD64, starting application >> results in segmentation fault: Signal 11. This leads me into conclusion >> Celestia 1.3.2 is not 64 Bit clean. >> Therefore, I tried compiling the sources of Celestia 1.4.1 taken from >> www.shatters.net on FreeBSD 6.1/i386, but this task ends up in compiler >> errors: >> >> -------------------------------------- >> Making all in cel3ds >> if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -Wnon-virtual-dtor >> -Wno-long-lon g >> -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 >> -pipe -pthread >> -march=pentium4 -ffast-math -fno-strict-aliasing -fno-exceptions -fno- >> check-new >> -fno-common -O2 -Wall -ffast-math -fexpensive-optimizations -fomit-fr >> ame-pointer >> -DXTHREADS -DXUSE_MTSAFE_API -I/usr/local/include/atk-1.0 -I/usr/loc >> al/include/cairo >> -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include >> >> -I/usr/X11R6/include/gtk-2.0 -I/usr/X11R6/lib/gtk-2.0/include >> -I/usr/X11R6/incl >> ude/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/freetype2 >> -I/usr/local/i >> nclude -I/usr/X11R6/include/gtkglext-1.0 >> -I/usr/X11R6/lib/gtkglext-1.0/include >> -I/usr/local/include/cairo -MT 3dsread.o -MD >> -MP -MF ".deps/3dsread.Tpo" -c - >> o 3dsread.o `test -f '3dsread.cpp' || echo >> './'`3dsread.cpp; then mv -f ".deps/ >> 3dsread.Tpo" ".deps/3dsread.Po"; else rm -f >> ".deps/3dsread.Tpo"; exit 1; fi >> In file included from ../celutil/bytes.h:15, >> from 3dsread.cpp:15: >> ../../config.h:256: error: declaration of C function `long unsigned int >> strlcat( char*, >> const char*, long unsigned int)' conflicts with >> /usr/include/string.h:87: error: previous declaration `size_t >> strlcat(char*, con >> st char*, size_t)' here >> ../../config.h:268: error: declaration of C function `long unsigned int >> strlcpy( char*, >> const char*, long unsigned int)' conflicts with >> /usr/include/string.h:88: error: previous declaration `size_t >> strlcpy(char*, con >> st char*, size_t)' here >> 3dsread.cpp:514: warning: unused parameter 'contentSize' >> 3dsread.cpp:490: warning: unused parameter 'contentSize' >> 3dsread.cpp:344: warning: unused parameter 'contentSize' >> 3dsread.cpp:308: warning: unused parameter 'in' >> 3dsread.cpp:308: warning: unused parameter 'chunkType' >> 3dsread.cpp:308: warning: unused parameter 'contentSize' >> 3dsread.cpp:308: warning: unused parameter 'obj' >> 3dsread.cpp:276: warning: unused parameter 'nBytes' >> 3dsread.cpp:264: warning: unused parameter 'nBytes' >> 3dsread.cpp:252: warning: unused parameter 'nBytes' >> 3dsread.cpp:119: warning: unused parameter 'chunkSize' >> ../celutil/bytes.h:24: warning: 'short unsigned int bswap_16(short >> unsigned int) ' >> defined but not used >> ../celutil/bytes.h:28: warning: 'unsigned int bswap_32(unsigned int)' >> defined but not used >> *** Error code 1 >> >> Stop in /usr/data/gnu/compile/system/celestia-1.4.1/src/cel3ds. >> *** Error code 1 >> >> Stop in /usr/data/gnu/compile/system/celestia-1.4.1/src. >> *** Error code 1 >> >> Stop in /usr/data/gnu/compile/system/celestia-1.4.1. >> *** Error code 1 >> >> Stop in /usr/data/gnu/compile/system/celestia-1.4.1. >> -------------------------------------- >> >> This looks like a very simple mistake where config.h overwrites >> declarations done via string.h, but I'm not sure. > > Well. You are very welcome to produce necessary patches, esp. since the > port is not maintained! > >> Compiling the same port on a box with same software releases, but >> amd64, results in very different errors (not just here, due to the >> fact the box is at home). > > I, for one, would love to have celestia both upgraded to 1.4.1 *and* > working on amd64. If you make this work, I'll commit it in a heartbeat. > :-) > > Thanks, > \Anton. Hello Anton. I'm not very familiar with C++ and libtool/autoconf, so some minor problems still keep me away from testing a working amd64 port. I fiddled around on my private amd64 machine and my lab's i386 box and at this stage, both dies now at the same point, concerning a libtool error. How familiar are you with libtool and debugging libtool'ed build processes? Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEMX7c9PZHcThI6nsRAgbbAJ4yTD9gcYMMGiE/XqBsSmVrgnnFuwCfWGYX fd4+nnmSU9xczBbXzAlUXjE= =lDtW -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:00:35 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 EF65E16A423 for ; Mon, 3 Apr 2006 21:00:34 +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 2C0C643D4C for ; Mon, 3 Apr 2006 21:00:34 +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 k33L0YSZ050639 for ; Mon, 3 Apr 2006 21:00:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k33L0XgS050632; Mon, 3 Apr 2006 21:00:33 GMT (envelope-from gnats) Resent-Date: Mon, 3 Apr 2006 21:00:33 GMT Resent-Message-Id: <200604032100.k33L0XgS050632@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, Juergen Lock Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 851D016A401 for ; Mon, 3 Apr 2006 20:59:53 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABDE143D64 for ; Mon, 3 Apr 2006 20:59:47 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.13.4/8.13.4/Debian-3) with ESMTP id k33KxkL9015868 for ; Mon, 3 Apr 2006 22:59:46 +0200 Received: from saturn.kn-bremen.de (uucp@localhost) by gwyn.kn-bremen.de (8.13.4/8.13.4/Submit) with UUCP id k33KxkmL015865 for FreeBSD-gnats-submit@freebsd.org; Mon, 3 Apr 2006 22:59:46 +0200 Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.3/8.13.1) with ESMTP id k33KuTuD007155 for ; Mon, 3 Apr 2006 22:56:29 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.3/8.13.1/Submit) id k33KuThM007154; Mon, 3 Apr 2006 22:56:29 +0200 (CEST) (envelope-from nox) Message-Id: <200604032056.k33KuThM007154@saturn.kn-bremen.de> Date: Mon, 3 Apr 2006 22:56:29 +0200 (CEST) From: Juergen Lock To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/95282: patch: fix ed for RELENG_5 amd64 so that it has network as a qemu guest X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Juergen Lock List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 21:00:35 -0000 >Number: 95282 >Category: amd64 >Synopsis: patch: fix ed for RELENG_5 amd64 so that it has network as a qemu guest >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Apr 03 21:00:32 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Juergen Lock >Release: FreeBSD 5.5-PRERELEASE i386 >Organization: me? organized?? >Environment: System: FreeBSD saturn 5.5-PRERELEASE FreeBSD 5.5-PRERELEASE #0: Fri Mar 17 04:37:54 CET 2006 nox@saturn:/usr/obj/usr/home/nox/src-r5/src/sys/NEPTUNu i386 >Description: (resending as a pr in the hope that it doesnt get lost this time :) I just noticed RELENG_5 still doesn't seem to have the ed driver patched for amd64, which would mean 5.5 wouldn't have network as a qemu guest. How about updating RELENG_5's ed, or at least committing a patch like the one in http://docs.freebsd.org/cgi/mid.cgi?20050801215410.GA10633 (and adding ed to sys/modules/Makefile and maybe to GENERIC too?) >How-To-Repeat: boot a RELENG_5 amd64 guest in qemu, watch it seeing no network >Fix: http://docs.freebsd.org/cgi/mid.cgi?20050801215410.GA10633 (or MFC ed), then add ed to sys/modules/Makefile for amd64 and maybe to GENERIC too >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:06: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 6710A16A423 for ; Mon, 3 Apr 2006 21:06:02 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp107.rog.mail.re2.yahoo.com (smtp107.rog.mail.re2.yahoo.com [68.142.225.205]) by mx1.FreeBSD.org (Postfix) with SMTP id 6B05843D53 for ; Mon, 3 Apr 2006 21:06:01 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 80362 invoked from network); 3 Apr 2006 21:06:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Gh1mmhJM3Wow5Ppe7dViGu0lB+AJQpMZjxocxBaL/VVgTTPtlLiX4LWKWC+onI8HBgnKIW56qh9lsnfUM8DVDJ1Fseuzbm0hUUfDMA2eUQGkEcMElcGKK7mUwM2PGN13h8EUN4ZFvrmC7QxMldAQ2swmb8WWxXpu8LrUqR1QR5k= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp107.rog.mail.re2.yahoo.com with SMTP; 3 Apr 2006 21:06:00 -0000 Message-ID: <44318E3F.6080808@rogers.com> Date: Mon, 03 Apr 2006 17:06:07 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John Baldwin References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> In-Reply-To: <200604031442.43477.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 03 Apr 2006 21:06:02 -0000 John Baldwin wrote: > On Sunday 02 April 2006 14:48, Mike Jakubik wrote: > >> I was wondering what the status of the NX bit support is. Is the pmap.c >> code still broken or is support enabled and functioning by default? >> > > I don't think the status has changed. > > Well that sucks.. I guess then there really is no reason for someone to run in amd64 mode unless you need more than 4GB of ram. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:08: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 4941516A400 for ; Mon, 3 Apr 2006 21:08:49 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8256443D48 for ; Mon, 3 Apr 2006 21:08:48 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr10.xs4all.nl (8.13.6/8.13.6) with ESMTP id k33L8btZ064262; Mon, 3 Apr 2006 23:08:38 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 2AA43B828; Mon, 3 Apr 2006 23:08:37 +0200 (CEST) Date: Mon, 3 Apr 2006 23:08:37 +0200 From: Roland Smith To: "O. Hartmann" Message-ID: <20060403210837.GA38539@slackbox.xs4all.nl> Mail-Followup-To: "O. Hartmann" , Anton Berezin , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> <44317EE0.4010605@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <44317EE0.4010605@mail.uni-mainz.de> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org, Anton Berezin Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 03 Apr 2006 21:08:49 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 03, 2006 at 10:00:32PM +0200, O. Hartmann wrote: > Anton Berezin wrote: > > On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: > >=20 > >> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, but > >> while compiling works on FreeBSD 6.1-PRE/AMD64, starting application > >> results in segmentation fault: Signal 11. This leads me into conclusion > >> Celestia 1.3.2 is not 64 Bit clean. It compiles fine on my amd64 box, and it works OK too. (celestia-1.3.2_2). Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMY7VEnfvsMMhpyURAlzqAJ93T0BkWGtenv4gbq5csIrRJUXSRgCdGIyQ HtB6Fma5pDVxmoq24Wc01tw= =3+kt -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:19:43 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED7FF16A423; Mon, 3 Apr 2006 21:19:43 +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 A3AD243D48; Mon, 3 Apr 2006 21:19:43 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k33LJhSM099296; Mon, 3 Apr 2006 14:19:43 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k33LJhiD099295; Mon, 3 Apr 2006 14:19:43 -0700 (PDT) (envelope-from sgk) Date: Mon, 3 Apr 2006 14:19:43 -0700 From: Steve Kargl To: Mike Jakubik Message-ID: <20060403211943.GA99241@troutmask.apl.washington.edu> References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> <44318E3F.6080808@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44318E3F.6080808@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 03 Apr 2006 21:19:44 -0000 On Mon, Apr 03, 2006 at 05:06:07PM -0400, Mike Jakubik wrote: > John Baldwin wrote: > >On Sunday 02 April 2006 14:48, Mike Jakubik wrote: > > > >>I was wondering what the status of the NX bit support is. Is the pmap.c > >>code still broken or is support enabled and functioning by default? > >> > > > >I don't think the status has changed. > > > > > > Well that sucks.. I guess then there really is no reason for someone to > run in amd64 mode unless you need more than 4GB of ram. > You're joking, right? How many registers are available for the i386? How many registers are available to an AMD64 cpu in 64-bit mode? -- Steve From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:23:09 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 0876B16A41F for ; Mon, 3 Apr 2006 21:23:09 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp105.rog.mail.re2.yahoo.com (smtp105.rog.mail.re2.yahoo.com [206.190.36.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 21F3F43D46 for ; Mon, 3 Apr 2006 21:23:07 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 40008 invoked from network); 3 Apr 2006 21:23:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=U8tj8MYE1Xihzgy1JqtW+kP7ei1gaIJM/n7Byqo3S/8QOpR6pcRd6YjEaQsyAG27Z09mGDSrEThynnO+4Zgp1gV4KryGjvTr4FX0nirUBfdACTM/TGjbFJWyXUTgUmftQMsN3EhySbyR5pk3F/XZCycaH5cFg4zc0CtR5rrXaTU= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp105.rog.mail.re2.yahoo.com with SMTP; 3 Apr 2006 21:23:07 -0000 Message-ID: <44319241.7080208@rogers.com> Date: Mon, 03 Apr 2006 17:23:13 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Steve Kargl References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> <44318E3F.6080808@rogers.com> <20060403211943.GA99241@troutmask.apl.washington.edu> In-Reply-To: <20060403211943.GA99241@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 03 Apr 2006 21:23:09 -0000 Steve Kargl wrote: > On Mon, Apr 03, 2006 at 05:06:07PM -0400, Mike Jakubik wrote: > >> John Baldwin wrote: >> >>> On Sunday 02 April 2006 14:48, Mike Jakubik wrote: >>> >>> >>>> I was wondering what the status of the NX bit support is. Is the pmap.c >>>> code still broken or is support enabled and functioning by default? >>>> >>>> >>> I don't think the status has changed. >>> >>> >>> >> Well that sucks.. I guess then there really is no reason for someone to >> run in amd64 mode unless you need more than 4GB of ram. >> >> > > You're joking, right? How many registers are available for the > i386? How many registers are available to an AMD64 cpu in > 64-bit mode? > > Yes, but doesn't the software have to be written to take advantage of these? (What about Intels 64bit extensions, do they have the same extra registers as the amd cpus?). As far as i can see so far, amd64 mode just eats more memory. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:23: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 D7BEC16A456; Mon, 3 Apr 2006 21:23:15 +0000 (UTC) (envelope-from dpz@ack.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A86043D46; Mon, 3 Apr 2006 21:23:15 +0000 (GMT) (envelope-from dpz@ack.berkeley.edu) Received: from [128.32.155.51] (soliloquy.Net.Berkeley.EDU [128.32.155.51]) (authenticated bits=0) by malcolm.berkeley.edu (8.13.6/8.13.3) with ESMTP id k33LNFY7052339 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 3 Apr 2006 14:23:15 -0700 (PDT) (envelope-from dpz@ack.berkeley.edu) Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> Content-Transfer-Encoding: 7bit From: David Paul Zimmerman Date: Mon, 3 Apr 2006 14:23:08 -0700 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.623) X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [128.32.206.239]); Mon, 03 Apr 2006 14:23:15 -0700 (PDT) Cc: David Robillard , Matthew Jacob Subject: Sun Fire X4100 now booting from LSI1064 SAS 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, 03 Apr 2006 21:23:15 -0000 *Many* thanks to mjacob for his mpt driver improvements. I was able to boot 7.0-CURRENT-SNAP013-amd64-disc1.iso (3/10/2006 snapshot) from CD on my X4100 and install from scratch directly to a SAS disk in slot 0. Booted perfectly. Did a csup at ~3/30/2006 15:17, buildworld/kernel, installkernel/world, all is still good. Now I get to go back and do it all again with two drives in a hardware RAID 1. Silly metadata. dp From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:23: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 8371816A420 for ; Mon, 3 Apr 2006 21:23:21 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E047043D46 for ; Mon, 3 Apr 2006 21:23:20 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k33LNHai041584; Mon, 3 Apr 2006 15:23:18 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44319240.8070203@samsco.org> Date: Mon, 03 Apr 2006 15:23:12 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> <44318E3F.6080808@rogers.com> <20060403211943.GA99241@troutmask.apl.washington.edu> In-Reply-To: <20060403211943.GA99241@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 03 Apr 2006 21:23:21 -0000 Steve Kargl wrote: > On Mon, Apr 03, 2006 at 05:06:07PM -0400, Mike Jakubik wrote: > >>John Baldwin wrote: >> >>>On Sunday 02 April 2006 14:48, Mike Jakubik wrote: >>> >>> >>>>I was wondering what the status of the NX bit support is. Is the pmap.c >>>>code still broken or is support enabled and functioning by default? >>>> >>> >>>I don't think the status has changed. >>> >>> >> >>Well that sucks.. I guess then there really is no reason for someone to >>run in amd64 mode unless you need more than 4GB of ram. >> > > > You're joking, right? How many registers are available for the > i386? How many registers are available to an AMD64 cpu in > 64-bit mode? > You also get less efficient cache utilization due to the wider data types that are in use. It seems to be mostly a wash between the advantages of more registers and the cost of lower cache efficiency. amd64 is nice when you need more kernel address space and/or more process address space. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 21:37:39 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 157DE16A401; Mon, 3 Apr 2006 21:37:39 +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 BDDBE43D46; Mon, 3 Apr 2006 21:37:38 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k33Lbcqc099466; Mon, 3 Apr 2006 14:37:38 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k33Lbcd1099465; Mon, 3 Apr 2006 14:37:38 -0700 (PDT) (envelope-from sgk) Date: Mon, 3 Apr 2006 14:37:38 -0700 From: Steve Kargl To: Mike Jakubik Message-ID: <20060403213738.GA99346@troutmask.apl.washington.edu> References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> <44318E3F.6080808@rogers.com> <20060403211943.GA99241@troutmask.apl.washington.edu> <44319241.7080208@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44319241.7080208@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 03 Apr 2006 21:37:39 -0000 On Mon, Apr 03, 2006 at 05:23:13PM -0400, Mike Jakubik wrote: > Steve Kargl wrote: > >On Mon, Apr 03, 2006 at 05:06:07PM -0400, Mike Jakubik wrote: > > > >>John Baldwin wrote: > >> > >>>On Sunday 02 April 2006 14:48, Mike Jakubik wrote: > >>> > >>>>I was wondering what the status of the NX bit support is. Is the pmap.c > >>>>code still broken or is support enabled and functioning by default? > >>>> > >>>I don't think the status has changed. > >>> > >>Well that sucks.. I guess then there really is no reason for someone to > >>run in amd64 mode unless you need more than 4GB of ram. > >> > > > >You're joking, right? How many registers are available for the > >i386? How many registers are available to an AMD64 cpu in > >64-bit mode? > > > > Yes, but doesn't the software have to be written to take advantage of > these? (What about Intels 64bit extensions, do they have the same extra > registers as the amd cpus?). As far as i can see so far, amd64 mode just > eats more memory. Do you do a large amount of number crunching? AMD paid for work on GCC to optimize gcc's machine description. I've never tried a benchmark of FreeBSD i386 versus FreeBSD amd64 for number crunching. It would be interesting to see a comparison of math/atlas on amd64 hardware under FreeBSD i386 and amd64. Someday, if I have time .... The livermore loops may also be interesting. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 3 23:59:18 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F20E16A426 for ; Mon, 3 Apr 2006 23:59:18 +0000 (UTC) (envelope-from root@vn1030.fireboxhosting.com) Received: from vn1030.fireboxhosting.com (vn1030.fireboxhosting.com [204.11.233.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82A8F43D7B for ; Mon, 3 Apr 2006 23:58:51 +0000 (GMT) (envelope-from root@vn1030.fireboxhosting.com) Received: from root by vn1030.fireboxhosting.com with local (Exim 4.52) id 1FQYqs-0001up-RK for freebsd-amd64@FreeBSD.org; Mon, 03 Apr 2006 19:52:54 -0400 To: freebsd-amd64@FreeBSD.org FROM: Ricardo Ribeiro - Atendimento Fácil Errors-to: retornomala@atendimentofacil.com.br Message-Id: Date: Mon, 03 Apr 2006 19:52:54 -0400 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vn1030.fireboxhosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - vn1030.fireboxhosting.com X-Source: X-Source-Args: X-Source-Dir: MIME-Version: 1.0 Content-Type: text/plain; X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: =?iso-8859-1?q?Sistema_de_Atendimento_Online_para_Sites_-_Atendi?= =?iso-8859-1?q?mento_F=E1cil?= 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, 03 Apr 2006 23:59:18 -0000 [mainborder01.gif] [mainborder02.gif] [mainborder03.gif] [mainborder04.gif] [topborder01.gif] [pixel.gif] [1][logo.gif] [2]Sobre nossa empresa [3]Cadastre-se [4]Dúvidas frequentes [5]Fale conosco [topborder03.gif] [pixel.gif] [menutitle.gif] [pixel.gif] [6]O que é? [7]Como funciona? [8]Recursos e Benefícios [9]Planos [10]Demonstração gratuita [11]Fale conosco [12][on_icon_status1.gif] [menusep.gif] Sistema de Atendimento Online O Atendimento Fácil é um serviço de atendimento online que fornece um meio para que as empresas de internet se comuniquem com seus usuários diretamente pelo website. Com ela é possível ver e conversar com os visitantes que estão navegando em seu site em tempo real. Desenvolvida por profissionais que utilizam as mais modernas ferramentas de comunicação online. Utilize o Atendimento Fácil em seu site por 20 dias gratuitamente para avaliação e comprove. [13][20dias.gif] [boxgreen.gif] [14]Aprenda como funciona [boxgreen.gif] [15]Peça sua demonstração Caso não deseje mais receber nossas mensagens envie um email para [16]remover@atendimentofacil.com.br. _________________________________________________________________ [17]Página inicial | [18]Cadastre-se | [19]Nossa empresa | [20]Política de uso | [21]Política de privacidade | [mainborder06.gif] [mainborder07.gif] [mainborder08.gif] [mainborder09.gif] References 1. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil 2. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/quemsomos.php 3. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/cadastro.php 4. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/faq.php 5. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/faleconosco.php 6. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil 7. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/comofunciona.php?wiz=livehelp 8. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/recursos.php 9. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/planos.php 10. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/cadastro.php 11. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/faleconosco.php 12. http://www.atendimentofacil.com.br/resources/www/visitor/index.php?COMPANY_ID=1&SITE_ID=1&info[Origem]=Email 13. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/cadastro.php 14. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/comofunciona.php?wiz=livehelp 15. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/cadastro.php 16. mailto:remover@atendimentofacil.com.br 17. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil 18. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/cadastro.php 19. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/quemsomos.php 20. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/politicauso.php 21. http://www.atendimentofacil.com.br/resources/www/website/atendimentofacil/politicaprivacidade.php From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 00:56:51 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 3B76716A401 for ; Tue, 4 Apr 2006 00:56:51 +0000 (UTC) (envelope-from taob@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7B5143D53 for ; Tue, 4 Apr 2006 00:56:50 +0000 (GMT) (envelope-from taob@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id D7A624B0B; Mon, 3 Apr 2006 20:56:49 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id CF4264AF6 for ; Mon, 3 Apr 2006 20:56:49 -0400 (EDT) Date: Mon, 3 Apr 2006 20:56:49 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: freebsd-amd64@freebsd.org In-Reply-To: <20060403041523.N3698-100000@as2.dm.egate.net> Message-ID: <20060403205241.C3698-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 04 Apr 2006 00:56:51 -0000 On Mon, 3 Apr 2006, Brian Tao wrote: > > Not sure if this is specifically an AMD64 issue or a 6.0 issue, > but I'm leaning towards the former, so I'll start here. ;-) > > FreeBSD 6.0-RELEASE-p4 #2: Tue Feb 7 18:04:40 EST 2006 taob@cabal.dm.egate.net:/depot/obj/depot/src/sys/LUXOKERNEL cvsuppsed to RELENG_6 to get the 6.1beta4 build. Managed to successfully buildworld, but the box went down during a buildkernel, and hasn't come back up on its own. :( I'll have to check in on it tomorrow and slap a serial console on it. If 6.1 isn't much better, I'll try putting an i386 kernel on it instead and see if I can rule out flakey hardware. -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 05:46: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 A9B7216A401 for ; Tue, 4 Apr 2006 05:46:46 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1869743D46 for ; Tue, 4 Apr 2006 05:46:45 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FQeNI-000Jeq-HO for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 09:46:44 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FQeMw-000G0f-SQ for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 09:46:22 +0400 Date: Tue, 4 Apr 2006 09:46:22 +0400 From: Igor Robul To: freebsd-amd64@freebsd.org Message-ID: <20060404054622.GJ61445@sysadm.stc> References: <20060403062711.GA52962@sysadm.stc> <4430C91F.6070006@samsco.org> <1144071224.686.6.camel@localhost> <200604031443.53372.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604031443.53372.jhb@freebsd.org> User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: Re: recommended PCI-E video card? 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, 04 Apr 2006 05:46:46 -0000 On Mon, Apr 03, 2006 at 02:43:51PM -0400, John Baldwin wrote: > I'm still waiting for feedback on the patch from Nvidia. Hopefully > they will test the current PAT patch soon. This looks very promising. So, I can safe buy medium-priced PCI-E nVidia card for 2D, and I have chances, that 3D will work after not so long time? From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 08:55: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 56C3F16A400 for ; Tue, 4 Apr 2006 08:55:07 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D39143D45 for ; Tue, 4 Apr 2006 08:55:06 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zgzuvq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k348sxcs087546 for ; Tue, 4 Apr 2006 10:55:04 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k348swpW087545; Tue, 4 Apr 2006 10:54:58 +0200 (CEST) (envelope-from olli) Date: Tue, 4 Apr 2006 10:54:58 +0200 (CEST) Message-Id: <200604040854.k348swpW087545@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <44318E3F.6080808@rogers.com> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 04 Apr 2006 10:55:04 +0200 (CEST) Cc: Subject: Re: Status of NX bit support. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2006 08:55:07 -0000 Mike Jakubik wrote: > John Baldwin wrote: > > On Sunday 02 April 2006 14:48, Mike Jakubik wrote: > > > I was wondering what the status of the NX bit support is. Is the pmap.c > > > code still broken or is support enabled and functioning by default? > > > > I don't think the status has changed. > > Well that sucks.. I guess then there really is no reason for someone to > run in amd64 mode unless you need more than 4GB of ram. Rather: Unless you need more than 32 bit of address space. That's a significant difference. You can take advantage of the 64 bit address space even if you don't have more than 4 GB of RAM. On the other hand, if you only need more than 4 GB of RAM, but don't require a larger address space, you could run in 32 bits with PAE enabled (although that's a crutch which I'd rather avoid). Apart from that, in 64 bit mode there are more registers available, which gcc takes advantage of to generate more efficient code. However, on the other hand, the additional registers also have to be saved and restored upon context switches, which costs CPU cycles. Also, long data types take up more memory, which can reduce cache efficiency. Whether a specific usage benfits from 64 bit mode (in terms of performance) needs to be checked by benchmarking it, and then deciding whether FreeBSD/i386 or FreeBSD/amd64 should be used. Of course, there are cases where you don't have a choice: If software is required which hasn't been ported to 64bit, you're stuck with /i386. If you need more than 32 bit of address space, you must use /amd64. If you need both, you're out of luck. :-) As you can see, there are quite a lot of advantages and disadvantages to both /i386 and /amd64 (and I've certainly missed a few). The NX bit and the 4 GB barrier aren't the only ones by far. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll." -- Frank Klemm, de.comp.os.unix.discussion From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 09:19: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 4054B16A401 for ; Tue, 4 Apr 2006 09:19:21 +0000 (UTC) (envelope-from tobez@tobez.org) Received: from heechee.tobez.org (heechee.tobez.org [194.255.56.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C698543D45 for ; Tue, 4 Apr 2006 09:19:20 +0000 (GMT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 4BE64125429; Tue, 4 Apr 2006 11:19:18 +0200 (CEST) Date: Tue, 4 Apr 2006 11:19:18 +0200 From: Anton Berezin To: "O. Hartmann" , freebsd-amd64@freebsd.org Message-ID: <20060404091918.GA58655@heechee.tobez.org> Mail-Followup-To: Anton Berezin , "O. Hartmann" , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> <44317EE0.4010605@mail.uni-mainz.de> <20060403210837.GA38539@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403210837.GA38539@slackbox.xs4all.nl> User-Agent: Mutt/1.4.2.1i X-Powered-By: FreeBSD http://www.freebsd.org/ Cc: Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 04 Apr 2006 09:19:21 -0000 On Mon, Apr 03, 2006 at 11:08:37PM +0200, Roland Smith wrote: > On Mon, Apr 03, 2006 at 10:00:32PM +0200, O. Hartmann wrote: > > > Anton Berezin wrote: > > > On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: > > > > > >> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, but > > >> while compiling works on FreeBSD 6.1-PRE/AMD64, starting application > > >> results in segmentation fault: Signal 11. This leads me into conclusion > > >> Celestia 1.3.2 is not 64 Bit clean. > > It compiles fine on my amd64 box, and it works OK too. (celestia-1.3.2_2). What options did you use to build the port? I am getting segfaults, just like Oliver. \Anton. -- An undefined problem has an infinite number of solutions. -- Robert A. Humphrey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 12:03: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 40D8316A422 for ; Tue, 4 Apr 2006 12:03:46 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E2A543D5E for ; Tue, 4 Apr 2006 12:03:32 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FQkFv-0008d8-48 for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 16:03:31 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FQkFZ-000GIa-9E for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 16:03:09 +0400 Date: Tue, 4 Apr 2006 16:03:09 +0400 From: Igor Robul To: freebsd-amd64@freebsd.org Message-ID: <20060404120309.GC62595@sysadm.stc> References: <44318E3F.6080808@rogers.com> <200604040854.k348swpW087545@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604040854.k348swpW087545@lurza.secnetix.de> User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: Re: Status of NX bit support. 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, 04 Apr 2006 12:03:46 -0000 On Tue, Apr 04, 2006 at 10:54:58AM +0200, Oliver Fromme wrote: > Mike Jakubik wrote: > As you can see, there are quite a lot of advantages and > disadvantages to both /i386 and /amd64 (and I've certainly > missed a few). The NX bit and the 4 GB barrier aren't the > only ones by far. I'm very new to FreeBSD on AMD64 (really, I dont have AMD64 based PC), so I have two questions: 1) can I use i386-jail on FreeBSD/AMD64 host (I hope this is possible)? 2) and also, can I use amd64-jail on FreeBSD/i386 on AMD64 host (I think this is not possible)? From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 12:27: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 34B8516A423 for ; Tue, 4 Apr 2006 12:27:30 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 770A243D46 for ; Tue, 4 Apr 2006 12:27:29 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (inaxyd@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k34CRMTS094548 for ; Tue, 4 Apr 2006 14:27:27 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k34CRMnX094547; Tue, 4 Apr 2006 14:27:22 +0200 (CEST) (envelope-from olli) Date: Tue, 4 Apr 2006 14:27:22 +0200 (CEST) Message-Id: <200604041227.k34CRMnX094547@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20060404120309.GC62595@sysadm.stc> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 04 Apr 2006 14:27:28 +0200 (CEST) Cc: Subject: Re: Status of NX bit support. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2006 12:27:30 -0000 Igor Robul wrote: > I'm very new to FreeBSD on AMD64 (really, I dont have AMD64 based PC), > so I have two questions: This isn't answering your questions, but it might be helpful anyway: If you want to try FreeBSD/amd64, but you don't have AMD64 hardware, then you can run it inside qemu-system-x86_64 on a FreeBSD/i386 host. > 2) and also, can I use amd64-jail on FreeBSD/i386 on AMD64 host > (I think this is not possible)? That's not possible, but you can run it inside qemu, if you need it (see above). The performance will not be very good, of course, because all of the amd64 instructions have to be emulated in software, but it's good enough for testing and checking things out. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 12:47: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 65ADA16A401 for ; Tue, 4 Apr 2006 12:47:21 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta01ps.mx.bigpond.com (omta01ps.mx.bigpond.com [144.140.82.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFC6E43D75 for ; Tue, 4 Apr 2006 12:47:07 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.4.160]) by omta01ps.mx.bigpond.com with ESMTP id <20060404124706.QEEJ19070.omta01ps.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 4 Apr 2006 12:47:06 +0000 Received: (qmail 37966 invoked by uid 501); 4 Apr 2006 12:48:45 -0000 Date: Tue, 4 Apr 2006 22:48:45 +1000 From: Andrew Reilly To: Scott Long Message-ID: <20060404124845.GA37816@gurney.reilly.home> References: <44301C6D.3010206@rogers.com> <200604031442.43477.jhb@freebsd.org> <44318E3F.6080808@rogers.com> <20060403211943.GA99241@troutmask.apl.washington.edu> <44319240.8070203@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44319240.8070203@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Status of NX bit support. 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, 04 Apr 2006 12:47:21 -0000 On Mon, Apr 03, 2006 at 03:23:12PM -0600, Scott Long wrote: > Steve Kargl wrote: > >You're joking, right? How many registers are available for the > >i386? How many registers are available to an AMD64 cpu in > >64-bit mode? > > You also get less efficient cache utilization due to the wider data > types that are in use. It seems to be mostly a wash between the > advantages of more registers and the cost of lower cache efficiency. > amd64 is nice when you need more kernel address space and/or more > process address space. I know I'm probably being barking mad, here, but what I'd really like for my AMD64 workstation system is to be able to run it in AMD64-mode, but with 32-bit pointers. I vaguely remember reading some early AMD bumpf that that could be a supported configuration, somehow. Seems like it should just be a compiler switch, to specify 32-bit loads and stores for pointer values, and probably some checking in the pmap system to make sure that nothing is mapped outside the 32-bit range... Anyone know if it's been done? How it performs, if it's been done? I do a fair bit of DSP simulation work, and 64-bit long-longs are very handy to have go fast, and more registers and register-based calling conventions are always a good thing. I have no need for 64-bit addresses, at least at the process level, and I suspect that most workstation users would be in much the same boat... Didn't MIPS, Sun and Apple support such an arrangement on R4000+, SPARCv?8 and PowerPC970 (G5) systems? Cheers, -- Andrew From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 13:31:10 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 AF66B16A424 for ; Tue, 4 Apr 2006 13:31:10 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4886543D45 for ; Tue, 4 Apr 2006 13:31:07 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FQlcf-000BTQ-JK for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 17:31:05 +0400 Received: from igorr by sysadm.stc with local (Exim 4.54 (FreeBSD)) id 1FQlcJ-000Ioc-O4 for freebsd-amd64@freebsd.org; Tue, 04 Apr 2006 17:30:43 +0400 Date: Tue, 4 Apr 2006 17:30:43 +0400 From: Igor Robul To: freebsd-amd64@freebsd.org Message-ID: <20060404133043.GA72319@sysadm.stc> References: <20060404120309.GC62595@sysadm.stc> <200604041227.k34CRMnX094547@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604041227.k34CRMnX094547@lurza.secnetix.de> User-Agent: Mutt/1.5.11 Sender: Igor Robul X-Archived: Yes Subject: Re: Status of NX bit support. 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, 04 Apr 2006 13:31:10 -0000 On Tue, Apr 04, 2006 at 02:27:22PM +0200, Oliver Fromme wrote: > Igor Robul wrote: > > I'm very new to FreeBSD on AMD64 (really, I dont have AMD64 based PC), > > so I have two questions: > > This isn't answering your questions, but it might be helpful > anyway: If you want to try FreeBSD/amd64, but you don't have > AMD64 hardware, then you can run it inside qemu-system-x86_64 > on a FreeBSD/i386 host. I'm planing to purchase AMD64 workstation (see my question about recommended video card). From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 13:38:04 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE49A16A401 for ; Tue, 4 Apr 2006 13:38:04 +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 4A04A43D46 for ; Tue, 4 Apr 2006 13:38:03 +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 46D74B81E; Tue, 4 Apr 2006 09:38:00 -0400 (EDT) In-Reply-To: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> References: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1B74953F-6F15-4DB7-A80D-FBC5626F08E9@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 4 Apr 2006 09:37:53 -0400 To: David Paul Zimmerman X-Mailer: Apple Mail (2.746.3) Cc: FreeBSD AMD list Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 13:38:04 -0000 Awesome! What kind of numbers do you get out of "diskinfo -v -t" in the RAID1 config? On Apr 3, 2006, at 5:23 PM, David Paul Zimmerman wrote: > *Many* thanks to mjacob for his mpt driver improvements. I was > able to boot 7.0-CURRENT-SNAP013-amd64-disc1.iso (3/10/2006 > snapshot) from CD on my X4100 and install from scratch directly to > a SAS disk in slot 0. Booted perfectly. Did a csup at ~3/30/2006 > 15:17, buildworld/kernel, installkernel/world, all is still good. > > Now I get to go back and do it all again with two drives in a > hardware RAID 1. Silly metadata. > > dp > From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 14:51: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 02FD216A41F for ; Tue, 4 Apr 2006 14:51:47 +0000 (UTC) (envelope-from dpz@ack.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B2043D4C for ; Tue, 4 Apr 2006 14:51:46 +0000 (GMT) (envelope-from dpz@ack.berkeley.edu) Received: from [10.0.1.5] (adsl-63-193-25-74.dsl.snfc21.pacbell.net [63.193.25.74]) (authenticated bits=0) by malcolm.berkeley.edu (8.13.6/8.13.3) with ESMTP id k34Epjms078407 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 4 Apr 2006 07:51:45 -0700 (PDT) (envelope-from dpz@ack.berkeley.edu) In-Reply-To: <1B74953F-6F15-4DB7-A80D-FBC5626F08E9@khera.org> References: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> <1B74953F-6F15-4DB7-A80D-FBC5626F08E9@khera.org> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9420324abff5db4117993ab4f327e0e3@ack.berkeley.edu> Content-Transfer-Encoding: 7bit From: David Paul Zimmerman Date: Tue, 4 Apr 2006 07:51:42 -0700 To: Vivek Khera X-Mailer: Apple Mail (2.623) X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [128.32.206.239]); Tue, 04 Apr 2006 07:51:46 -0700 (PDT) Cc: FreeBSD AMD list Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 14:51:47 -0000 This is what I get after a minimum OS install from the snapshot CD: $ sudo diskinfo -v -t da0s1 da0s1 512 # sectorsize 72999327744 # mediasize in bytes (68G) 142576812 # mediasize in sectors 8874 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. Seek times: Full stroke: 250 iter in 1.081320 sec = 4.325 msec Half stroke: 250 iter in 1.008685 sec = 4.035 msec Quarter stroke: 500 iter in 2.842515 sec = 5.685 msec Short forward: 400 iter in 1.369284 sec = 3.423 msec Short backward: 400 iter in 1.313750 sec = 3.284 msec Seq outer: 2048 iter in 0.274178 sec = 0.134 msec Seq inner: 2048 iter in 0.277063 sec = 0.135 msec Transfer rates: outside: 102400 kbytes in 1.640884 sec = 62405 kbytes/sec middle: 102400 kbytes in 1.896519 sec = 53994 kbytes/sec inside: 102400 kbytes in 2.723277 sec = 37602 kbytes/sec I'll be doing a csup today to bring it up to date. Here's my current kernel log, if it's interesting to anyone (the virtual CD and floppy errors don't bother me): $ dmesg Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT-SNAP013 #0: Fri Mar 10 07:51:58 UTC 2006 root@harrison.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.77-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f51 Stepping = 1 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 usable memory = 1062342656 (1013 MB) avail memory = 1023963136 (976 MB) MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard ioapic3 irqs 32-35 on motherboard ioapic4 irqs 36-39 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 em0: port 0x9c00-0x9c3f mem 0xfbfe0000-0xfbffffff irq 26 at device 1.0 on pci1 em0: Ethernet address: 00:14:4f:01:a4:94 em0: [FAST] em1: port 0x9800-0x983f mem 0xfbfc0000-0xfbfdffff irq 27 at device 1.1 on pci1 em1: Ethernet address: 00:14:4f:01:a4:95 em1: [FAST] em2: port 0x9400-0x943f mem 0xfbfa0000-0xfbfbffff irq 24 at device 2.0 on pci1 em2: Ethernet address: 00:14:4f:01:a4:96 em2: [FAST] em3: port 0x9000-0x903f mem 0xfbf80000-0xfbf9ffff irq 25 at device 2.1 on pci1 em3: Ethernet address: 00:14:4f:01:a4:97 em3: [FAST] pci0: at device 1.1 (no driver attached) pcib2: at device 2.0 on pci0 pci2: on pcib2 mpt0: port 0xa800-0xa8ff mem 0xfc2fc000-0xfc2fffff,0xfc2e0000-0xfc2effff irq 28 at device 3.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.9.0 mpt0: Capabilities: ( RAID-0 RAID-1 ) mpt0: 1 Active Volume (2 Max) mpt0: 2 Hidden Drive Members (10 Max) pci0: at device 2.1 (no driver attached) pcib3: at device 6.0 on pci0 pci3: on pcib3 ohci0: mem 0xfe3fe000-0xfe3fefff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe3fd000-0xfe3fdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered vgapci0: port 0xb800-0xb8ff mem 0xfd000000-0xfdffffff,0xfe3ff000-0xfe3fffff irq 16 at device 3.0 on pci3 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib4: on acpi0 pci4: on pcib4 pcib5: at device 1.0 on pci4 pci5: on pcib5 pci4: at device 1.1 (no driver attached) pcib6: at device 2.0 on pci4 pci6: on pcib6 pci4: at device 2.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FAST] acpi_hpet0: iomem 0xfec01000-0xfec013ff irq 0,8 on acpi0 acpi_hpet0: Vendor: 0x1022 acpi_hpet0: Leg_Route_Cap: 1 acpi_hpet0: Count_Size_Cap: 0 acpi_hpet0: Num_Tim_Cap: 8 acpi_hpet0: Rev_id: 0x3 acpi_hpet0: Period: 69841279 fs (14318180 Hz) acpi_hpet0: HPET attach orm0: at iomem 0xc0000-0xc9fff,0xca000-0xcafff,0xcb000-0xcbfff,0xcc000 -0xccfff,0xcd000-0xcdfff,0xce000-0xd27ff,0xd2800-0xd37ff pnpid ORM0000 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: on uhub0 kbd0 at ukbd0 ums0: on uhub0 ums0: X report 0x0002 not supported device_attach: ums0 attach returned 6 umass0: on uhub1 umass1: on uhub1 Timecounter "TSC" frequency 2193768131 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff80603100, 0) error 6 mpt0: mpt_read_cfg_page: Config Info Status 22 mpt0:vol0(mpt0:0:0): mpt_refresh_raid_vol: Failed to read RAID Vol Page(0) mpt0:vol0(mpt0:0:0): Settings ( ) mpt0:vol0(mpt0:0:0): 0 Members: mpt0:vol0(mpt0:0:0): RAID-0 - Optimal (mpt0:0:3): Physical (mpt0:0:3), Pass-thru (mpt0:1:0) (mpt0:0:3): Online (mpt0:0:4): Physical (mpt0:0:4), Pass-thru (mpt0:1:1) (mpt0:0:4): Online acd0: DVDROM at ata0-master UDMA33 pass1 at mpt0 bus 1 target 0 lun 0 pass1: Fixed unknown SCSI-4 device pass1: 300.000MB/s transfers, Tagged Queueing Enabled pass2 at mpt0 bus 1 target 1 lun 0 pass2: Fixed unknown SCSI-4 device pass2: 300.000MB/s transfers, Tagged Queueing Enabled da0 at mpt0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 69618MB (142577664 512 byte sectors: 255H 63S/T 8875C) cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 1.000MB/s transfers cd0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, medium may have changed da1 at umass-sim1 bus 1 target 0 lun 0 da1: Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da1:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da1:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da1:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da1:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da1:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da1:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da1:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da1:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): NOT READY asc:3a,0 (da1:umass-sim1:1:0:0): Medium not present (da1:umass-sim1:1:0:0): Unretryable error Opened disk da1 -> 6 (da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da1:umass-sim1:1:0:0): SCSI Status: Check Condition (da1:umass-sim1:1:0:0): NOT READY asc:3a,0 (da1:umass-sim1:1:0:0): Medium not present (da1:umass-sim1:1:0:0): Unretryable error Opened disk da1 -> 6 Trying to mount root from ufs:/dev/da0s1a em0: link state changed to UP dp On Apr 4, 2006, at 6:37 AM, Vivek Khera wrote: > Awesome! What kind of numbers do you get out of "diskinfo -v -t" in > the RAID1 config? > > On Apr 3, 2006, at 5:23 PM, David Paul Zimmerman wrote: > >> *Many* thanks to mjacob for his mpt driver improvements. I was able >> to boot 7.0-CURRENT-SNAP013-amd64-disc1.iso (3/10/2006 snapshot) from >> CD on my X4100 and install from scratch directly to a SAS disk in >> slot 0. Booted perfectly. Did a csup at ~3/30/2006 15:17, >> buildworld/kernel, installkernel/world, all is still good. >> >> Now I get to go back and do it all again with two drives in a >> hardware RAID 1. Silly metadata. >> >> dp From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 15:01:57 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 7D53216A420 for ; Tue, 4 Apr 2006 15:01:57 +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 2F30643D45 for ; Tue, 4 Apr 2006 15:01:56 +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 69891B816; Tue, 4 Apr 2006 11:01:56 -0400 (EDT) In-Reply-To: <9420324abff5db4117993ab4f327e0e3@ack.berkeley.edu> References: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> <1B74953F-6F15-4DB7-A80D-FBC5626F08E9@khera.org> <9420324abff5db4117993ab4f327e0e3@ack.berkeley.edu> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 4 Apr 2006 11:01:55 -0400 To: David Paul Zimmerman X-Mailer: Apple Mail (2.746.3) Cc: FreeBSD AMD list Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 15:01:57 -0000 On Apr 4, 2006, at 10:51 AM, David Paul Zimmerman wrote: > I'll be doing a csup today to bring it up to date. Here's my > current kernel log, if it's interesting to anyone (the virtual CD > and floppy errors don't bother me): I tried *every* possible bios config to turn off those stupid virtual devices, but they won't go away. I think it is a bug in the BIOS that turning them of doesn't really turn them off :-( Also, if you have >= 4GB RAM, you have to go in and enable the software "PCI HOLE" remapping or you lose 1GB of it. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 15:07: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 10A7F16A41F for ; Tue, 4 Apr 2006 15:07:07 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8620C43D48 for ; Tue, 4 Apr 2006 15:07:05 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k34F6rvP046841; Tue, 4 Apr 2006 17:06:53 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id DA62EB828; Tue, 4 Apr 2006 17:06:52 +0200 (CEST) Date: Tue, 4 Apr 2006 17:06:52 +0200 From: Roland Smith To: Anton Berezin , "O. Hartmann" , freebsd-amd64@freebsd.org Message-ID: <20060404150652.GA70058@slackbox.xs4all.nl> Mail-Followup-To: Anton Berezin , "O. Hartmann" , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> <44317EE0.4010605@mail.uni-mainz.de> <20060403210837.GA38539@slackbox.xs4all.nl> <20060404091918.GA58655@heechee.tobez.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <20060404091918.GA58655@heechee.tobez.org> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 04 Apr 2006 15:07:07 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 04, 2006 at 11:19:18AM +0200, Anton Berezin wrote: > On Mon, Apr 03, 2006 at 11:08:37PM +0200, Roland Smith wrote: > > On Mon, Apr 03, 2006 at 10:00:32PM +0200, O. Hartmann wrote: > >=20 > > > Anton Berezin wrote: > > > > On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: > > > >=20 > > > >> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, = but > > > >> while compiling works on FreeBSD 6.1-PRE/AMD64, starting applicati= on > > > >> results in segmentation fault: Signal 11. This leads me into concl= usion > > > >> Celestia 1.3.2 is not 64 Bit clean. > >=20 > > It compiles fine on my amd64 box, and it works OK too. (celestia-1.3.2_= 2). >=20 > What options did you use to build the port? I am getting segfaults, > just like Oliver. These are the options that I have selected. Lua is enabled because I happen to have it on my system. ---------- /var/db/ports/celestia/options ---------- # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for celestia-1.3.2_2 _OPTIONS_READ=3Dcelestia-1.3.2_2 WITH_LUA=3Dtrue WITHOUT_GLUT=3Dtrue WITH_GTK=3Dtrue WITHOUT_GNOME=3Dtrue WITHOUT_KDE=3Dtrue ---------- /var/db/ports/celestia/options ---------- I'm using the system compiler (3.4.4), and no special optimizations: ---------- /etc/make.conf ---------- # For ports. WITHOUT_NLS=3Dtrue # Compiler flags CFLAGS=3D-O -pipe COPTFLAGS=3D-O -pipe ---------- /etc/make.conf ---------- Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEMouMEnfvsMMhpyURAl0SAJ4zFPmlYELQzM6KeacoXBfOy6ropQCgsP+i DsuZxfMNfKBseIlMn1aUDzc= =IiRi -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 15:07: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 F0E7916A423 for ; Tue, 4 Apr 2006 15:07:38 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C03F43D62 for ; Tue, 4 Apr 2006 15:07:38 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.180.123] (ipamzra.Physik.Uni-Mainz.DE [134.93.180.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id C8D113000333; Tue, 4 Apr 2006 17:07:36 +0200 (CEST) Message-ID: <44328BB9.8060301@uni-mainz.de> Date: Tue, 04 Apr 2006 17:07:37 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Anton Berezin , "O. Hartmann" , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> <44317EE0.4010605@mail.uni-mainz.de> <20060403210837.GA38539@slackbox.xs4all.nl> <20060404091918.GA58655@heechee.tobez.org> In-Reply-To: <20060404091918.GA58655@heechee.tobez.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 04 Apr 2006 15:07:39 -0000 Anton Berezin schrieb: > On Mon, Apr 03, 2006 at 11:08:37PM +0200, Roland Smith wrote: >> On Mon, Apr 03, 2006 at 10:00:32PM +0200, O. Hartmann wrote: >> >>> Anton Berezin wrote: >>>> On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: >>>> >>>>> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, but >>>>> while compiling works on FreeBSD 6.1-PRE/AMD64, starting application >>>>> results in segmentation fault: Signal 11. This leads me into conclusion >>>>> Celestia 1.3.2 is not 64 Bit clean. >> It compiles fine on my amd64 box, and it works OK too. (celestia-1.3.2_2). > > What options did you use to build the port? I am getting segfaults, > just like Oliver. > > \Anton. We should build the port again with option -rRf to ensure every necessary and dependend port is built and up to date. I'll try this evening. Oliver From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 15:11:19 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 2AFB016A423 for ; Tue, 4 Apr 2006 15:11:19 +0000 (UTC) (envelope-from ohartman@uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 552BC43D45 for ; Tue, 4 Apr 2006 15:11:15 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.180.123] (ipamzra.Physik.Uni-Mainz.DE [134.93.180.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 1EABA300033D; Tue, 4 Apr 2006 17:11:14 +0200 (CEST) Message-ID: <44328C92.5090906@uni-mainz.de> Date: Tue, 04 Apr 2006 17:11:14 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Anton Berezin , "O. Hartmann" , freebsd-amd64@freebsd.org References: <4424047D.8090800@uni-mainz.de> <20060327100330.GD58186@heechee.tobez.org> <44317EE0.4010605@mail.uni-mainz.de> <20060403210837.GA38539@slackbox.xs4all.nl> <20060404091918.GA58655@heechee.tobez.org> <20060404150652.GA70058@slackbox.xs4all.nl> In-Reply-To: <20060404150652.GA70058@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: Re: FreeBSD 6.1/AMD64: Celestia 1.3.2/1.4.1 not working? 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, 04 Apr 2006 15:11:19 -0000 Roland Smith schrieb: > On Tue, Apr 04, 2006 at 11:19:18AM +0200, Anton Berezin wrote: >> On Mon, Apr 03, 2006 at 11:08:37PM +0200, Roland Smith wrote: >>> On Mon, Apr 03, 2006 at 10:00:32PM +0200, O. Hartmann wrote: >>> >>>> Anton Berezin wrote: >>>>> On Fri, Mar 24, 2006 at 03:38:53PM +0100, O. Hartmann wrote: >>>>> >>>>>> Compiling port Celestia 1.3.2 on FreeBSD 6.1-PRE/i386 works fine, but >>>>>> while compiling works on FreeBSD 6.1-PRE/AMD64, starting application >>>>>> results in segmentation fault: Signal 11. This leads me into conclusion >>>>>> Celestia 1.3.2 is not 64 Bit clean. >>> It compiles fine on my amd64 box, and it works OK too. (celestia-1.3.2_2). >> What options did you use to build the port? I am getting segfaults, >> just like Oliver. > > These are the options that I have selected. Lua is enabled because I > happen to have it on my system. > ---------- /var/db/ports/celestia/options ---------- > # This file is auto-generated by 'make config'. > # No user-servicable parts inside! > # Options for celestia-1.3.2_2 > _OPTIONS_READ=celestia-1.3.2_2 > WITH_LUA=true > WITHOUT_GLUT=true > WITH_GTK=true > WITHOUT_GNOME=true > WITHOUT_KDE=true > ---------- /var/db/ports/celestia/options ---------- > > I'm using the system compiler (3.4.4), and no special optimizations: > ---------- /etc/make.conf ---------- > # For ports. > WITHOUT_NLS=true > > # Compiler flags > CFLAGS=-O -pipe > COPTFLAGS=-O -pipe > ---------- /etc/make.conf ---------- > > Roland All right, my compiler options are -O2 -pipe -fno-strict-aliasing as recommended in make.conf (no special options choosen in make.conf, port selects options itself). Will try this ... Oliver From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 18:05:09 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 62F9816A401; Tue, 4 Apr 2006 18:05:09 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C875F43D49; Tue, 4 Apr 2006 18:05:08 +0000 (GMT) (envelope-from tom.hurst@clara.net) Received: from [81.104.145.173] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQptq-000JZq-AX; Tue, 04 Apr 2006 19:05:06 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.54 (FreeBSD)) id 1FQptr-000KXR-B1; Tue, 04 Apr 2006 19:05:07 +0100 Date: Tue, 4 Apr 2006 19:05:07 +0100 From: Thomas Hurst To: David Paul Zimmerman Message-ID: <20060404180507.GA75325@voi.aagh.net> Mail-Followup-To: David Paul Zimmerman , freebsd-amd64@freebsd.org, David Robillard , Matthew Jacob References: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e904fab0b3c4704c1bc045b480b9fce@ack.berkeley.edu> Organization: Not much. User-Agent: Mutt/1.5.11 Sender: Thomas Hurst Cc: David Robillard , Matthew Jacob , freebsd-amd64@freebsd.org Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 18:05:09 -0000 * David Paul Zimmerman (dpz@ack.berkeley.edu) wrote: > *Many* thanks to mjacob for his mpt driver improvements. I was able > to boot 7.0-CURRENT-SNAP013-amd64-disc1.iso (3/10/2006 snapshot) > from CD on my X4100 and install from scratch directly to a SAS disk > in slot 0. Booted perfectly. Did a csup at ~3/30/2006 15:17, > buildworld/kernel, installkernel/world, all is still good. Well, that's what we[1] paid him for; thanks Matt :) We're running the CURRENT mpt driver copied back to several RELENG_6 machines without problems, ranging from 2GB to 10GB, 2 to 4 drives, and 2 to 4 cores; they've proved to be stable enough for production use, although IO seemed to be somewhat bottlenecked with MySQL and gmirror+gstripe based RAID10. They make lovely general purpose servers, not least because of the excellent lights out management, and they of course run Linux fine too, which is good for MySQL throughput if nothing else. Hope to see an mpt MFC before long :) 1: http://www.newzbin.com/ -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 18:25: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 86D0C16A401; Tue, 4 Apr 2006 18:25:58 +0000 (UTC) (envelope-from mjacob@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51EC443D6A; Tue, 4 Apr 2006 18:25:58 +0000 (GMT) (envelope-from mjacob@FreeBSD.org) Received: from freefall.freebsd.org (mjacob@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k34IPwCu040830; Tue, 4 Apr 2006 18:25:58 GMT (envelope-from mjacob@freefall.freebsd.org) Received: (from mjacob@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k34IPvVa040829; Tue, 4 Apr 2006 18:25:57 GMT (envelope-from mjacob) Date: Tue, 4 Apr 2006 18:25:57 GMT From: Matt Jacob Message-Id: <200604041825.k34IPvVa040829@freefall.freebsd.org> To: tom.hurst@clara.net Cc: david.robillard@gmail.com, Robillard@FreeBSD.org, freebsd-amd64@freebsd.org, Paul@FreeBSD.org, David@FreeBSD.org, Zimmerman@FreeBSD.org Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 18:25:58 -0000 > Well, that's what we[1] paid him for; thanks Matt :) > > We're running the CURRENT mpt driver copied back to several RELENG_6 > machines without problems, ranging from 2GB to 10GB, 2 to 4 drives, and > 2 to 4 cores; they've proved to be stable enough for production use, > although IO seemed to be somewhat bottlenecked with MySQL and > gmirror+gstripe based RAID10. > > They make lovely general purpose servers, not least because of the > excellent lights out management, and they of course run Linux fine too, > which is good for MySQL throughput if nothing else. > > Hope to see an mpt MFC before long :) That's in negotiation with RE right now. > > 1: http://www.newzbin.com/ Not getting this one. I had some support from Chris Ellsworth in England for this work. LSI-Logic is having me do mostly target mode fibre channel right now, and Yahoo is having me look at some of the U320 issues. Data Domain, my former employer as of yesterday, graciously allowed me to use their N-Stor and Xyratex SAS/SATA arrays and SuperMicro systems under the guise of me shaking out the SAS connectivity for their Linux based product. I've had lots of good feedback and support from folks, but I don't get the newzbin reference. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 4 22:52: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 23AE316A425; Tue, 4 Apr 2006 22:52:03 +0000 (UTC) (envelope-from tom@hur.st) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2562343D48; Tue, 4 Apr 2006 22:52:01 +0000 (GMT) (envelope-from tom@hur.st) Received: from [81.104.145.173] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQuNU-000LFr-B8; Tue, 04 Apr 2006 23:52:00 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.54 (FreeBSD)) id 1FQuNV-000PRp-A6; Tue, 04 Apr 2006 23:52:01 +0100 Date: Tue, 4 Apr 2006 23:52:01 +0100 From: Thomas Hurst To: Matt Jacob Message-ID: <20060404225201.GA93690@voi.aagh.net> Mail-Followup-To: Matt Jacob , david.robillard@gmail.com, dpz@ack.berkeley.edu, David@FreeBSD.org, freebsd-amd64@freebsd.org, Paul@FreeBSD.org, Robillard@FreeBSD.org, Zimmerman@FreeBSD.org References: <200604041825.k34IPvVa040829@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604041825.k34IPvVa040829@freefall.freebsd.org> Organization: Not much. User-Agent: Mutt/1.5.11 Sender: Thomas Hurst Cc: david.robillard@gmail.com, Robillard@FreeBSD.org, freebsd-amd64@freebsd.org, Paul@FreeBSD.org, David@FreeBSD.org, Zimmerman@FreeBSD.org Subject: Re: Sun Fire X4100 now booting from LSI1064 SAS 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, 04 Apr 2006 22:52:03 -0000 * Matt Jacob (mjacob@FreeBSD.org) wrote: > > Hope to see an mpt MFC before long :) > > That's in negotiation with RE right now. Wonderful. Might see it in 6.1-RELEASE then? > > 1: http://www.newzbin.com/ > > Not getting this one. > > I had some support from Chris Ellsworth in England for this work. .. > I've had lots of good feedback and support from folks, but I don't > get the newzbin reference. Ah, sorry; Chris == Newzbin: -% whois newzbin.com |grep Chris Elsworth, Chris Sorry for the confusion :) -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 04:59: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 AFE6E16A400 for ; Wed, 5 Apr 2006 04:59:26 +0000 (UTC) (envelope-from taob@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 671AB43D45 for ; Wed, 5 Apr 2006 04:59:26 +0000 (GMT) (envelope-from taob@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id 6AC1C4B43; Wed, 5 Apr 2006 00:59:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id 5DE094B36 for ; Wed, 5 Apr 2006 00:59:25 -0400 (EDT) Date: Wed, 5 Apr 2006 00:59:25 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: freebsd-amd64@freebsd.org In-Reply-To: <20060403205241.C3698-100000@as2.dm.egate.net> Message-ID: <20060405005220.X3698-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 04:59:26 -0000 On Mon, 3 Apr 2006, Brian Tao wrote: > > I'll have to check in on it tomorrow and slap a serial console on > it. If 6.1 isn't much better, I'll try putting an i386 kernel on it > instead and see if I can rule out flakey hardware. No go with RELENG_6... kernel panic during a buildworld attempt with the new kernel. Additionally, on reboot, the background fsck eventually hangs in disk wait on snaplk. The system slowly becomes inaccessible as more and more processes access the filesystem and also hang on snaplk. There doesn't seem to be anything for savecore to dump when the system tries to come back up either. Any other information I should be providing, beyond what is included in the tar file below (kernel config file, dmesg, kgdb output)? http://www.luxography.ca/tmp/amd64_panics.tgz -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 05:02:23 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 51C6C16A400 for ; Wed, 5 Apr 2006 05:02:23 +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 0583743D46 for ; Wed, 5 Apr 2006 05:02:23 +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 987811A4D7C; Tue, 4 Apr 2006 22:02:22 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 060CC517D2; Wed, 5 Apr 2006 01:02:21 -0400 (EDT) Date: Wed, 5 Apr 2006 01:02:21 -0400 From: Kris Kennaway To: Brian Tao Message-ID: <20060405050221.GA92737@xor.obsecurity.org> References: <20060403205241.C3698-100000@as2.dm.egate.net> <20060405005220.X3698-100000@as2.dm.egate.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <20060405005220.X3698-100000@as2.dm.egate.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 05:02:23 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 12:59:25AM -0400, Brian Tao wrote: > On Mon, 3 Apr 2006, Brian Tao wrote: > > > > I'll have to check in on it tomorrow and slap a serial console on > > it. If 6.1 isn't much better, I'll try putting an i386 kernel on it > > instead and see if I can rule out flakey hardware. >=20 > No go with RELENG_6... kernel panic during a buildworld attempt > with the new kernel. Additionally, on reboot, the background fsck > eventually hangs in disk wait on snaplk. The system slowly becomes > inaccessible as more and more processes access the filesystem and also > hang on snaplk. >=20 > There doesn't seem to be anything for savecore to dump when the > system tries to come back up either. Any other information I should > be providing, beyond what is included in the tar file below (kernel > config file, dmesg, kgdb output)? >=20 > http://www.luxography.ca/tmp/amd64_panics.tgz It would be helpful (i.e. more likely to get responses) if you could post a relevant extract, so people don't have to download the tarball. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEM09dWry0BWjoQKURAtkTAJ9Wea8XqNFOktlUKZN3WslKwfey2QCeLqH7 cqotwMtMwEaCFyG8Y5YSEWs= =DhOu -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 05:12:29 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 047D416A400 for ; Wed, 5 Apr 2006 05:12:29 +0000 (UTC) (envelope-from brian@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3869F43D48 for ; Wed, 5 Apr 2006 05:12:28 +0000 (GMT) (envelope-from brian@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id A41914B04; Wed, 5 Apr 2006 01:12:27 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id 97CF34AE7; Wed, 5 Apr 2006 01:12:27 -0400 (EDT) Date: Wed, 5 Apr 2006 01:12:27 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: Kris Kennaway In-Reply-To: <20060405050221.GA92737@xor.obsecurity.org> Message-ID: <20060405010819.J3698-300000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2054668743-1144213947=:3698" Cc: freebsd-amd64@freebsd.org Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 05:12:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2054668743-1144213947=:3698 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 5 Apr 2006, Kris Kennaway wrote: > > It would be helpful (i.e. more likely to get responses) if you could > post a relevant extract, so people don't have to download the tarball. Sorry, sure... the one kgdb output is below, and I've attached the dmesg.boot and kernel config files. It's just that it appears the panic is in a different part of the kernel each time,, so I figured it would be best to include more examples. [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 fault virtual address = 0xffffff083ecca57a fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802a01c9 stack pointer = 0x10:0xffffffffa54ea710 frame pointer = 0x10:0xffffff0013eea7c0 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 = 766 (pax) trap number = 12 panic: page fault Uptime: 52m40s Dumping 1022 MB (2 chunks) chunk 0: 1MB (157 pages) ... ok chunk 1: 1022MB (261600 pages) 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list *0xffffffff802a01c9 0xffffffff802a01c9 is in cluster_wbuild (/depot/src/sys/kern/vfs_cluster.c:904). 899 900 VM_OBJECT_LOCK(tbp->b_bufobj->bo_object); 901 if (i != 0) { /* if not first buffer */ 902 for (j = 0; j < tbp->b_npages; j += 1) { 903 m = tbp->b_pages[j]; 904 if (m->flags & PG_BUSY) { 905 VM_OBJECT_UNLOCK( 906 tbp->b_object); 907 bqrelse(tbp); 908 goto finishcluster; (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff80243313 in boot (howto=260) at /depot/src/sys/kern/kern_shutdown.c:399 #3 0xffffffff80243946 in panic (fmt=0xffffff003d9daa00 "@3\235.") at /depot/src/sys/kern/kern_shutdown.c:555 #4 0xffffffff8039bfcf in trap_fatal (frame=0xffffff003d9daa00, eva=18446742974979978048) at /depot/src/sys/amd64/amd64/trap.c:655 #5 0xffffffff8039c2ef in trap_pfault (frame=0xffffffffa54ea660, usermode=0) at /depot/src/sys/amd64/amd64/trap.c:571 #6 0xffffffff8039c5a3 in trap (frame= {tf_rdi = -1099177219824, tf_rsi = -1064098290408, tf_rdx = 4, tf_rcx = 4, tf_r8 = 0, tf_r9 = 0, tf_rax = 1, tf_rbx = -1790840384, tf_rbp = -1099177220160, tf_r10 = -1098729573568, tf_r11 = -1098477884928, tf_r12 = -1099056953600, tf_r13 = 8, tf_r14 = 4, tf_r15 = 105, tf_trapno = 12, tf_addr = -1064098290310, tf_flags = -1790840384, tf_err = 0, tf_rip = -2144730679, tf_cs = 8, tf_rflags = 66050, tf_rsp = -1521572064, tf_ss = 16}) at /depot/src/sys/amd64/amd64/trap.c:350 #7 0xffffffff8038bb7b in calltrap () at /depot/src/sys/amd64/amd64/exception.S:168 #8 0xffffffff802a01c9 in cluster_wbuild (vp=0xffffff0013eea7c0, size=16384, start_lbn=105, len=8) at /depot/src/sys/kern/vfs_cluster.c:903 #9 0xffffffff802a0a9b in cluster_write (vp=0xffffff0013eea7c0, bp=0xffffffff95300198, filesize=1835008, seqcount=117) at /depot/src/sys/kern/vfs_cluster.c:570 #10 0xffffffff8035886f in ffs_write (ap=0xffffffffa54eaa30) at /depot/src/sys/ufs/ffs/ffs_vnops.c:713 #11 0xffffffff803dd37b in VOP_WRITE_APV (vop=0xffffffff80558d20, a=0xffffffffa54eaa30) at vnode_if.c:698 #12 0xffffffff802ba941 in vn_write (fp=0xffffff001408f7f8, uio=0xffffffffa54eab50, active_cred=0xffffffffa54eaa30, flags=0, td=0xffffff003d9daa00) at vnode_if.h:372 #13 0xffffffff8026c5c7 in dofilewrite (td=0xffffff003d9daa00, fd=7, fp=0xffffff001408f7f8, auio=0xffffffffa54eab50, offset=0, flags=0) at file.h:246 #14 0xffffffff8026c910 in kern_writev (td=0xffffff003d9daa00, fd=7, auio=0xffffffffa54eab50) at /depot/src/sys/kern/sys_generic.c:402 #15 0xffffffff8026ca08 in write (td=0xffffff0013eea910, uap=0xffffff083ecca518) at /depot/src/sys/kern/sys_generic.c:326 #16 0xffffffff8039cde1 in syscall (frame= {tf_rdi = 7, tf_rsi = 5334752, tf_rdx = 64512, tf_rcx = 34366613852, tf_r8 = -1099352823536, tf_r9 = 140737488339832, tf_rax = 4, tf_rbx = 64512, tf_rbp = 64512, tf_r10 = 0, tf_r11 = 514, tf_r12 = 1806336, tf_r13 = 7, tf_r14 = 6, tf_r15 = 140737488343184, tf_trapno = 12, tf_addr = 5840992, tf_flags = 0, tf_err = 2, tf_rip = 34366613820, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488339832, tf_ss = 35}) at /depot/src/sys/amd64/amd64/trap.c:787 #17 0xffffffff8038bd18 in Xfast_syscall () at /depot/src/sys/amd64/amd64/exception.S:270 #18 0x000000080068e93c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) quit -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" --0-2054668743-1144213947=:3698 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.boot" Content-Transfer-Encoding: BASE64 Content-ID: <20060405011227.F3698@as2.dm.egate.net> Content-Description: dmesg.boot Content-Disposition: attachment; filename="dmesg.boot" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDUgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDYuMC1SRUxFQVNFLXA0ICMyOiBUdWUgRmViICA3 IDE4OjA0OjQwIEVTVCAyMDA2DQogICAgdGFvYkBjYWJhbC5kbS5lZ2F0ZS5u ZXQ6L2RlcG90L29iai9kZXBvdC9zcmMvc3lzL0xVWE9LRVJORUwNCkFDUEkg QVBJQyBUYWJsZTogPEs4VDg5MCBBV1JEQUNQST4NClRpbWVjb3VudGVyICJp ODI1NCIgZnJlcXVlbmN5IDExOTMxODIgSHogcXVhbGl0eSAwDQpDUFU6IEFN RCBBdGhsb24odG0pIDY0IFByb2Nlc3NvciAzMDAwKyAoMTgwMC4wOC1NSHog SzgtY2xhc3MgQ1BVKQ0KICBPcmlnaW4gPSAiQXV0aGVudGljQU1EIiAgSWQg PSAweDIwZmYyICBTdGVwcGluZyA9IDINCiAgRmVhdHVyZXM9MHg3OGJmYmZm PEZQVSxWTUUsREUsUFNFLFRTQyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAs TVRSUixQR0UsTUNBLENNT1YsUEFULFBTRTM2LENMRkxVU0gsTU1YLEZYU1Is U1NFLFNTRTI+DQogIEZlYXR1cmVzMj0weDE8U1NFMz4NCiAgQU1EIEZlYXR1 cmVzPTB4ZTI1MDA4MDA8U1lTQ0FMTCxOWCxNTVgrLDxiMjU+LExNLDNETm93 KywzRE5vdz4NCnJlYWwgbWVtb3J5ICA9IDEwNzI1NjIxNzYgKDEwMjIgTUIp DQphdmFpbCBtZW1vcnkgPSAxMDI3NDExOTY4ICg5NzkgTUIpDQppb2FwaWMw IDxWZXJzaW9uIDAuMz4gaXJxcyAwLTIzIG9uIG1vdGhlcmJvYXJkDQppb2Fw aWMxIDxWZXJzaW9uIDAuMz4gaXJxcyAyNC00NyBvbiBtb3RoZXJib2FyZA0K YWNwaTA6IDxLOFQ4OTAgQVdSREFDUEk+IG9uIG1vdGhlcmJvYXJkDQphY3Bp X2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6 IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBf QURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1 c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNh bid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURS DQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19u dW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0 IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQph Y3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1i ZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdl dCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3Bp X2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6 IGNhbid0IGdldCBfQURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBf QURSDQphY3BpX2J1c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpX2J1 c19udW1iZXI6IGNhbid0IGdldCBfQURSDQphY3BpMDogUG93ZXIgQnV0dG9u IChmaXhlZCkNCnBjaV9saW5rMDogPEFDUEkgUENJIExpbmsgTE5LQT4gaXJx IDUgb24gYWNwaTANCnBjaV9saW5rMTogPEFDUEkgUENJIExpbmsgTE5LQj4g aXJxIDExIG9uIGFjcGkwDQpwY2lfbGluazI6IDxBQ1BJIFBDSSBMaW5rIExO S0M+IGlycSAxMSBvbiBhY3BpMA0KcGNpX2xpbmszOiA8QUNQSSBQQ0kgTGlu ayBMTktEPiBvbiBhY3BpMA0KcGNpX2xpbms0OiA8QUNQSSBQQ0kgTGluayBM TktFPiBvbiBhY3BpMA0KcGNpX2xpbms1OiA8QUNQSSBQQ0kgTGluayBMTktG PiBvbiBhY3BpMA0KcGNpX2xpbms2OiA8QUNQSSBQQ0kgTGluayBMTkswPiBv biBhY3BpMA0KcGNpX2xpbms3OiA8QUNQSSBQQ0kgTGluayBMTksxPiBpcnEg MyBvbiBhY3BpMA0KcGNpX2xpbms4OiA8QUNQSSBQQ0kgTGluayBBTEtBPiBp cnEgMjAgb24gYWNwaTANCnBjaV9saW5rOTogPEFDUEkgUENJIExpbmsgQUxL Qj4gaXJxIDIxIG9uIGFjcGkwDQpwY2lfbGluazEwOiA8QUNQSSBQQ0kgTGlu ayBBTEtDPiBpcnEgMjIgb24gYWNwaTANCnBjaV9saW5rMTE6IDxBQ1BJIFBD SSBMaW5rIEFMS0Q+IGlycSAyMyBvbiBhY3BpMA0KVGltZWNvdW50ZXIgIkFD UEktZmFzdCIgZnJlcXVlbmN5IDM1Nzk1NDUgSHogcXVhbGl0eSAxMDAwDQph Y3BpX3RpbWVyMDogPDI0LWJpdCB0aW1lciBhdCAzLjU3OTU0NU1Iej4gcG9y dCAweDQwMDgtMHg0MDBiIG9uIGFjcGkwDQpjcHUwOiA8QUNQSSBDUFU+IG9u IGFjcGkwDQphY3BpX2J1dHRvbjA6IDxQb3dlciBCdXR0b24+IG9uIGFjcGkw DQpwY2liMDogPEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2Y4LTB4 Y2ZmIG9uIGFjcGkwDQpwY2lfbGluazEwOiBCSU9TIElSUSAxMSBmb3IgLTIx NDU5NjQyMDAuMTcuSU5UQyBpcyBpbnZhbGlkDQpwY2lfbGluazg6IEJJT1Mg SVJRIDExIGZvciAtMjE0NTk2NDIwMC4xNS5JTlRCIGlzIGludmFsaWQNCnBj aTA6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIwDQpwY2kwOiA8YmFzZSBwZXJp cGhlcmFsLCBpbnRlcnJ1cHQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDAuNSAo bm8gZHJpdmVyIGF0dGFjaGVkKQ0KcGNpYjE6IDxQQ0ktUENJIGJyaWRnZT4g YXQgZGV2aWNlIDEuMCBvbiBwY2kwDQpwY2kxOiA8UENJIGJ1cz4gb24gcGNp YjENCnBjaWIyOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gaXJxIDI3IGF0IGRl dmljZSAyLjAgb24gcGNpMA0KcGNpMjogPEFDUEkgUENJIGJ1cz4gb24gcGNp YjINCnBjaWIzOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gaXJxIDMxIGF0IGRl dmljZSAzLjAgb24gcGNpMA0KcGNpMzogPEFDUEkgUENJIGJ1cz4gb24gcGNp YjMNCnBjaWI0OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDMu MSBvbiBwY2kwDQpwY2k0OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liNA0KcGNp YjU6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBpcnEgMzkgYXQgZGV2aWNlIDMu MiBvbiBwY2kwDQpwY2k1OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liNQ0KcGNp NTogPG5ldHdvcmssIGV0aGVybmV0PiBhdCBkZXZpY2UgMC4wIChubyBkcml2 ZXIgYXR0YWNoZWQpDQpwY2liNjogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGly cSA0MyBhdCBkZXZpY2UgMy4zIG9uIHBjaTANCnBjaTY6IDxBQ1BJIFBDSSBi dXM+IG9uIHBjaWI2DQphdGFwY2kwOiA8UHJvbWlzZSBQREM0MDcxOCBTQVRB MzAwIGNvbnRyb2xsZXI+IHBvcnQgMHhiMDAwLTB4YjA3ZiwweGI0MDAtMHhi NGZmIG1lbSAweGRiODIxMDAwLTB4ZGI4MjFmZmYsMHhkYjgwMDAwMC0weGRi ODFmZmZmIGlycSAxNiBhdCBkZXZpY2UgMTEuMCBvbiBwY2kwDQphdGEyOiA8 QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMA0KYXRhMzogPEFUQSBjaGFubmVs IDE+IG9uIGF0YXBjaTANCmF0YTQ6IDxBVEEgY2hhbm5lbCAyPiBvbiBhdGFw Y2kwDQphdGE1OiA8QVRBIGNoYW5uZWwgMz4gb24gYXRhcGNpMA0KcmwwOiA8 RC1MaW5rIERGRS01MzBUWCsgMTAvMTAwQmFzZVRYPiBwb3J0IDB4YjgwMC0w eGI4ZmYgbWVtIDB4ZGI4MjAwMDAtMHhkYjgyMDBmZiBpcnEgMTcgYXQgZGV2 aWNlIDEyLjAgb24gcGNpMA0KbWlpYnVzMDogPE1JSSBidXM+IG9uIHJsMA0K cmxwaHkwOiA8UmVhbFRlayBpbnRlcm5hbCBtZWRpYSBpbnRlcmZhY2U+IG9u IG1paWJ1czANCnJscGh5MDogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBi YXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1dG8NCnJsMDogRXRoZXJuZXQgYWRk cmVzczogMDA6MTE6OTU6NjU6MzU6N2UNCnBjaTA6IDxkaXNwbGF5LCBWR0E+ IGF0IGRldmljZSAxMy4wIChubyBkcml2ZXIgYXR0YWNoZWQpDQphdGFwY2kx OiA8VklBIDY0MjAgU0FUQTE1MCBjb250cm9sbGVyPiBwb3J0IDB4YmMwMC0w eGJjMDcsMHhjMDAwLTB4YzAwMywweGM0MDAtMHhjNDA3LDB4YzgwMC0weGM4 MDMsMHhjYzAwLTB4Y2MwZiwweGQwMDAtMHhkMGZmIGlycSAyMCBhdCBkZXZp Y2UgMTUuMCBvbiBwY2kwDQphdGE2OiA8QVRBIGNoYW5uZWwgMD4gb24gYXRh cGNpMQ0KYXRhNzogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTENCmF0YXBj aTI6IDxWSUEgODIzNyBVRE1BMTMzIGNvbnRyb2xsZXI+IHBvcnQgMHgxZjAt MHgxZjcsMHgzZjYsMHgxNzAtMHgxNzcsMHgzNzYsMHhkNDAwLTB4ZDQwZiBh dCBkZXZpY2UgMTUuMSBvbiBwY2kwDQphdGEwOiA8QVRBIGNoYW5uZWwgMD4g b24gYXRhcGNpMg0KYXRhMTogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTIN CnVoY2kwOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxlcj4gcG9ydCAweGQ4 MDAtMHhkODFmIGF0IGRldmljZSAxNi4wIG9uIHBjaTANCnVoY2kwOiBbR0lB TlQtTE9DS0VEXQ0KdXNiMDogPFZJQSA4M0M1NzIgVVNCIGNvbnRyb2xsZXI+ IG9uIHVoY2kwDQp1c2IwOiBVU0IgcmV2aXNpb24gMS4wDQp1aHViMDogVklB IFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRk ciAxDQp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBv d2VyZWQNCnVoY2kxOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxlcj4gcG9y dCAweGRjMDAtMHhkYzFmIGF0IGRldmljZSAxNi4xIG9uIHBjaTANCnVoY2kx OiBbR0lBTlQtTE9DS0VEXQ0KdXNiMTogPFZJQSA4M0M1NzIgVVNCIGNvbnRy b2xsZXI+IG9uIHVoY2kxDQp1c2IxOiBVU0IgcmV2aXNpb24gMS4wDQp1aHVi MTogVklBIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4w MCwgYWRkciAxDQp1aHViMTogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBz ZWxmIHBvd2VyZWQNCnVoY2kyOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxl cj4gcG9ydCAweGUwMDAtMHhlMDFmIGF0IGRldmljZSAxNi4yIG9uIHBjaTAN CnVoY2kyOiBbR0lBTlQtTE9DS0VEXQ0KdXNiMjogPFZJQSA4M0M1NzIgVVNC IGNvbnRyb2xsZXI+IG9uIHVoY2kyDQp1c2IyOiBVU0IgcmV2aXNpb24gMS4w DQp1aHViMjogVklBIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEu MDAvMS4wMCwgYWRkciAxDQp1aHViMjogMiBwb3J0cyB3aXRoIDIgcmVtb3Zh YmxlLCBzZWxmIHBvd2VyZWQNCnVoY2kzOiA8VklBIDgzQzU3MiBVU0IgY29u dHJvbGxlcj4gcG9ydCAweGU0MDAtMHhlNDFmIGF0IGRldmljZSAxNi4zIG9u IHBjaTANCnVoY2kzOiBbR0lBTlQtTE9DS0VEXQ0KdXNiMzogPFZJQSA4M0M1 NzIgVVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kzDQp1c2IzOiBVU0IgcmV2aXNp b24gMS4wDQp1aHViMzogVklBIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwg cmV2IDEuMDAvMS4wMCwgYWRkciAxDQp1aHViMzogMiBwb3J0cyB3aXRoIDIg cmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQNCmVoY2kwOiA8VklBIFZUNjIwMiBV U0IgMi4wIGNvbnRyb2xsZXI+IG1lbSAweGRiODIyMDAwLTB4ZGI4MjIwZmYg YXQgZGV2aWNlIDE2LjQgb24gcGNpMA0KZWhjaTA6IFtHSUFOVC1MT0NLRURd DQp1c2I0OiBFSENJIHZlcnNpb24gMS4wDQp1c2I0OiBjb21wYW5pb24gY29u dHJvbGxlcnMsIDIgcG9ydHMgZWFjaDogdXNiMCB1c2IxIHVzYjIgdXNiMw0K dXNiNDogPFZJQSBWVDYyMDIgVVNCIDIuMCBjb250cm9sbGVyPiBvbiBlaGNp MA0KdXNiNDogVVNCIHJldmlzaW9uIDIuMA0KdWh1YjQ6IFZJQSBFSENJIHJv b3QgaHViLCBjbGFzcyA5LzAsIHJldiAyLjAwLzEuMDAsIGFkZHIgMQ0KdWh1 YjQ6IDggcG9ydHMgd2l0aCA4IHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkDQp1 bWFzczA6IEdlbmVyaWMgTWFzcyBTdG9yYWdlIERldmljZSwgcmV2IDIuMDAv MS4xMCwgYWRkciAyDQppc2FiMDogPFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZp Y2UgMTcuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCnBj aTA6IDxtdWx0aW1lZGlhLCBhdWRpbz4gYXQgZGV2aWNlIDE3LjUgKG5vIGRy aXZlciBhdHRhY2hlZCkNCmFjcGlfdHowOiA8VGhlcm1hbCBab25lPiBvbiBh Y3BpMA0Kc2lvMDogY29uZmlndXJlZCBpcnEgNCBub3QgaW4gYml0bWFwIG9m IHByb2JlZCBpcnFzIDANCnNpbzA6IHBvcnQgbWF5IG5vdCBiZSBlbmFibGVk DQpzaW8wOiA8MTY1NTBBLWNvbXBhdGlibGUgQ09NIHBvcnQ+IHBvcnQgMHgz ZjgtMHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBhY3BpMA0Kc2lvMDogdHlw ZSAxNjU1MEENCm9ybTA6IDxJU0EgT3B0aW9uIFJPTXM+IGF0IGlvbWVtIDB4 YzAwMDAtMHhjN2ZmZiwweGM4MDAwLTB4Y2NmZmYgb24gaXNhMA0KYXRrYmRj MDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYw LDB4NjQgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdz IDB4MTAwIG9uIGlzYTANCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVz LCBmbGFncz0weDMwMD4NCnNpbzE6IGNvbmZpZ3VyZWQgaXJxIDMgbm90IGlu IGJpdG1hcCBvZiBwcm9iZWQgaXJxcyAwDQpzaW8xOiBwb3J0IG1heSBub3Qg YmUgZW5hYmxlZA0KdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQgcG9ydCAw eDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNhMA0KVGlt ZWNvdW50ZXIgIlRTQyIgZnJlcXVlbmN5IDE4MDAwNzkyNjkgSHogcXVhbGl0 eSA4MDANClRpbWVjb3VudGVycyB0aWNrIGV2ZXJ5IDEuMDAwIG1zZWMNCmFj ZDA6IERWRFIgPE5FQyBEVkQgUlcgTkQtMzU0MEEvMS4wMT4gYXQgYXRhMC1t YXN0ZXIgVURNQTMzDQphZDQ6IDIzODQ3NU1CIDxXREMgV0QyNTAwS1MtMDBN SkIwIDAyLjAxQzAzPiBhdCBhdGEyLW1hc3RlciBTQVRBMzAwDQphZDY6IDIz ODQ3NU1CIDxXREMgV0QyNTAwS1MtMDBNSkIwIDAyLjAxQzAzPiBhdCBhdGEz LW1hc3RlciBTQVRBMzAwDQphZDg6IDIzODQ3NU1CIDxXREMgV0QyNTAwS1Mt MDBNSkIwIDAyLjAxQzAzPiBhdCBhdGE0LW1hc3RlciBTQVRBMzAwDQphZDEw OiAyMzg0NzVNQiA8V0RDIFdEMjUwMEtTLTAwTUpCMCAwMi4wMUMwMz4gYXQg YXRhNS1tYXN0ZXIgU0FUQTMwMA0KYWQxMjogMjM4NDc1TUIgPFdEQyBXRDI1 MDBLUy0wME1KQjAgMDIuMDFDMDM+IGF0IGF0YTYtbWFzdGVyIFNBVEExNTAN CmFkMTQ6IDIzODQ3NU1CIDxXREMgV0QyNTAwS1MtMDBNSkIwIDAyLjAxQzAz PiBhdCBhdGE3LW1hc3RlciBTQVRBMTUwDQpkYTAgYXQgdW1hc3Mtc2ltMCBi dXMgMCB0YXJnZXQgMCBsdW4gMA0KZGEwOiA8R2VuZXJpYyBVU0IgU0QgUmVh ZGVyIDEuMDA+IFJlbW92YWJsZSBEaXJlY3QgQWNjZXNzIFNDU0ktMCBkZXZp Y2UgDQpkYTA6IDQwLjAwME1CL3MgdHJhbnNmZXJzDQpkYTA6IEF0dGVtcHQg dG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFksIE1lZGl1 bSBub3QgcHJlc2VudA0KZGExIGF0IHVtYXNzLXNpbTAgYnVzIDAgdGFyZ2V0 IDAgbHVuIDENCmRhMTogPEdlbmVyaWMgVVNCIENGIFJlYWRlciAxLjAxPiBS ZW1vdmFibGUgRGlyZWN0IEFjY2VzcyBTQ1NJLTAgZGV2aWNlIA0KZGExOiA0 MC4wMDBNQi9zIHRyYW5zZmVycw0KZGExOiBBdHRlbXB0IHRvIHF1ZXJ5IGRl dmljZSBzaXplIGZhaWxlZDogTk9UIFJFQURZLCBNZWRpdW0gbm90IHByZXNl bnQNCmRhMiBhdCB1bWFzcy1zaW0wIGJ1cyAwIHRhcmdldCAwIGx1biAyDQpk YTI6IDxHZW5lcmljIFVTQiBTTSBSZWFkZXIgMS4wMj4gUmVtb3ZhYmxlIERp cmVjdCBBY2Nlc3MgU0NTSS0wIGRldmljZSANCmRhMjogNDAuMDAwTUIvcyB0 cmFuc2ZlcnMNCmRhMjogQXR0ZW1wdCB0byBxdWVyeSBkZXZpY2Ugc2l6ZSBm YWlsZWQ6IE5PVCBSRUFEWSwgTWVkaXVtIG5vdCBwcmVzZW50DQpkYTMgYXQg dW1hc3Mtc2ltMCBidXMgMCB0YXJnZXQgMCBsdW4gMw0KZGEzOiA8R2VuZXJp YyBVU0IgTVMgUmVhZGVyIDEuMDM+IFJlbW92YWJsZSBEaXJlY3QgQWNjZXNz IFNDU0ktMCBkZXZpY2UgDQpkYTM6IDQwLjAwME1CL3MgdHJhbnNmZXJzDQpk YTM6IEF0dGVtcHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1Qg UkVBRFksIE1lZGl1bSBub3QgcHJlc2VudA0KKGRhMDp1bWFzcy1zaW0wOjA6 MDowKTogUkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSAwIDAgMCAwIDAgMCAwIDAg MCANCihkYTA6dW1hc3Mtc2ltMDowOjA6MCk6IENBTSBTdGF0dXM6IFNDU0kg U3RhdHVzIEVycm9yDQooZGEwOnVtYXNzLXNpbTA6MDowOjApOiBTQ1NJIFN0 YXR1czogQ2hlY2sgQ29uZGl0aW9uDQooZGEwOnVtYXNzLXNpbTA6MDowOjAp OiBOT1QgUkVBRFkgY3NpOjAsYWEsNTUsNDAgYXNjOjNhLDANCihkYTA6dW1h c3Mtc2ltMDowOjA6MCk6IE1lZGl1bSBub3QgcHJlc2VudCBmaWVsZCByZXBs YWNlYWJsZSB1bml0OiA0MA0KKGRhMDp1bWFzcy1zaW0wOjA6MDowKTogVW5y ZXRyeWFibGUgZXJyb3INCk9wZW5lZCBkaXNrIGRhMCAtPiA2DQooZGEwOnVt YXNzLXNpbTA6MDowOjApOiBSRUFEIENBUEFDSVRZLiBDREI6IDI1IDAgMCAw IDAgMCAwIDAgMCAwIA0KKGRhMDp1bWFzcy1zaW0wOjA6MDowKTogQ0FNIFN0 YXR1czogU0NTSSBTdGF0dXMgRXJyb3INCihkYTA6dW1hc3Mtc2ltMDowOjA6 MCk6IFNDU0kgU3RhdHVzOiBDaGVjayBDb25kaXRpb24NCihkYTA6dW1hc3Mt c2ltMDowOjA6MCk6IE5PVCBSRUFEWSBjc2k6MCxhYSw1NSw0MCBhc2M6M2Es MA0KKGRhMDp1bWFzcy1zaW0wOjA6MDowKTogTWVkaXVtIG5vdCBwcmVzZW50 IGZpZWxkIHJlcGxhY2VhYmxlIHVuaXQ6IDQwDQooZGEwOnVtYXNzLXNpbTA6 MDowOjApOiBVbnJldHJ5YWJsZSBlcnJvcg0KT3BlbmVkIGRpc2sgZGEwIC0+ IDYNCihkYTA6dW1hc3Mtc2ltMDowOjA6MCk6IFJFQUQgQ0FQQUNJVFkuIENE QjogMjUgMCAwIDAgMCAwIDAgMCAwIDAgDQooZGEwOnVtYXNzLXNpbTA6MDow OjApOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJvcg0KKGRhMDp1bWFz cy1zaW0wOjA6MDowKTogU0NTSSBTdGF0dXM6IENoZWNrIENvbmRpdGlvbg0K KGRhMDp1bWFzcy1zaW0wOjA6MDowKTogTk9UIFJFQURZIGNzaTowLGFhLDU1 LDQwIGFzYzozYSwwDQooZGEwOnVtYXNzLXNpbTA6MDowOjApOiBNZWRpdW0g bm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFibGUgdW5pdDogNDANCihkYTA6 dW1hc3Mtc2ltMDowOjA6MCk6IFVucmV0cnlhYmxlIGVycm9yDQpPcGVuZWQg ZGlzayBkYTAgLT4gNg0KKGRhMTp1bWFzcy1zaW0wOjA6MDoxKTogUkVBRCBD QVBBQ0lUWS4gQ0RCOiAyNSAyMCAwIDAgMCAwIDAgMCAwIDAgDQooZGExOnVt YXNzLXNpbTA6MDowOjEpOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJv cg0KKGRhMTp1bWFzcy1zaW0wOjA6MDoxKTogU0NTSSBTdGF0dXM6IENoZWNr IENvbmRpdGlvbg0KKGRhMTp1bWFzcy1zaW0wOjA6MDoxKTogTk9UIFJFQURZ IGNzaTowLGFhLDU1LDQwIGFzYzozYSwwDQooZGExOnVtYXNzLXNpbTA6MDow OjEpOiBNZWRpdW0gbm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFibGUgdW5p dDogNDANCihkYTE6dW1hc3Mtc2ltMDowOjA6MSk6IFVucmV0cnlhYmxlIGVy cm9yDQpPcGVuZWQgZGlzayBkYTEgLT4gNg0KKGRhMTp1bWFzcy1zaW0wOjA6 MDoxKTogUkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSAyMCAwIDAgMCAwIDAgMCAw IDAgDQooZGExOnVtYXNzLXNpbTA6MDowOjEpOiBDQU0gU3RhdHVzOiBTQ1NJ IFN0YXR1cyBFcnJvcg0KKGRhMTp1bWFzcy1zaW0wOjA6MDoxKTogU0NTSSBT dGF0dXM6IENoZWNrIENvbmRpdGlvbg0KKGRhMTp1bWFzcy1zaW0wOjA6MDox KTogTk9UIFJFQURZIGNzaTowLGFhLDU1LDQwIGFzYzozYSwwDQooZGExOnVt YXNzLXNpbTA6MDowOjEpOiBNZWRpdW0gbm90IHByZXNlbnQgZmllbGQgcmVw bGFjZWFibGUgdW5pdDogNDANCihkYTE6dW1hc3Mtc2ltMDowOjA6MSk6IFVu cmV0cnlhYmxlIGVycm9yDQpPcGVuZWQgZGlzayBkYTEgLT4gNg0KKGRhMTp1 bWFzcy1zaW0wOjA6MDoxKTogUkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSAyMCAw IDAgMCAwIDAgMCAwIDAgDQooZGExOnVtYXNzLXNpbTA6MDowOjEpOiBDQU0g U3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJvcg0KKGRhMTp1bWFzcy1zaW0wOjA6 MDoxKTogU0NTSSBTdGF0dXM6IENoZWNrIENvbmRpdGlvbg0KKGRhMTp1bWFz cy1zaW0wOjA6MDoxKTogTk9UIFJFQURZIGNzaTowLGFhLDU1LDQwIGFzYzoz YSwwDQooZGExOnVtYXNzLXNpbTA6MDowOjEpOiBNZWRpdW0gbm90IHByZXNl bnQgZmllbGQgcmVwbGFjZWFibGUgdW5pdDogNDANCihkYTE6dW1hc3Mtc2lt MDowOjA6MSk6IFVucmV0cnlhYmxlIGVycm9yDQpPcGVuZWQgZGlzayBkYTEg LT4gNg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogUkVBRCBDQVBBQ0lUWS4g Q0RCOiAyNSA0MCAwIDAgMCAwIDAgMCAwIDAgDQooZGEyOnVtYXNzLXNpbTA6 MDowOjIpOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJvcg0KKGRhMjp1 bWFzcy1zaW0wOjA6MDoyKTogU0NTSSBTdGF0dXM6IENoZWNrIENvbmRpdGlv bg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogTk9UIFJFQURZIGNzaTowLGFh LDU1LDQwIGFzYzozYSwwDQooZGEyOnVtYXNzLXNpbTA6MDowOjIpOiBNZWRp dW0gbm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFibGUgdW5pdDogNDANCihk YTI6dW1hc3Mtc2ltMDowOjA6Mik6IFVucmV0cnlhYmxlIGVycm9yDQpPcGVu ZWQgZGlzayBkYTIgLT4gNg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogUkVB RCBDQVBBQ0lUWS4gQ0RCOiAyNSA0MCAwIDAgMCAwIDAgMCAwIDAgDQooZGEy OnVtYXNzLXNpbTA6MDowOjIpOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBF cnJvcg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogU0NTSSBTdGF0dXM6IENo ZWNrIENvbmRpdGlvbg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogTk9UIFJF QURZIGNzaTowLGFhLDU1LDQwIGFzYzozYSwwDQooZGEyOnVtYXNzLXNpbTA6 MDowOjIpOiBNZWRpdW0gbm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFibGUg dW5pdDogNDANCihkYTI6dW1hc3Mtc2ltMDowOjA6Mik6IFVucmV0cnlhYmxl IGVycm9yDQpPcGVuZWQgZGlzayBkYTIgLT4gNg0KKGRhMjp1bWFzcy1zaW0w OjA6MDoyKTogUkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSA0MCAwIDAgMCAwIDAg MCAwIDAgDQooZGEyOnVtYXNzLXNpbTA6MDowOjIpOiBDQU0gU3RhdHVzOiBT Q1NJIFN0YXR1cyBFcnJvcg0KKGRhMjp1bWFzcy1zaW0wOjA6MDoyKTogU0NT SSBTdGF0dXM6IENoZWNrIENvbmRpdGlvbg0KKGRhMjp1bWFzcy1zaW0wOjA6 MDoyKTogTk9UIFJFQURZIGNzaTowLGFhLDU1LDQwIGFzYzozYSwwDQooZGEy OnVtYXNzLXNpbTA6MDowOjIpOiBNZWRpdW0gbm90IHByZXNlbnQgZmllbGQg cmVwbGFjZWFibGUgdW5pdDogNDANCihkYTI6dW1hc3Mtc2ltMDowOjA6Mik6 IFVucmV0cnlhYmxlIGVycm9yDQpPcGVuZWQgZGlzayBkYTIgLT4gNg0KKGRh Mzp1bWFzcy1zaW0wOjA6MDozKTogUkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSA2 MCAwIDAgMCAwIDAgMCAwIDAgDQooZGEzOnVtYXNzLXNpbTA6MDowOjMpOiBD QU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJvcg0KKGRhMzp1bWFzcy1zaW0w OjA6MDozKTogU0NTSSBTdGF0dXM6IENoZWNrIENvbmRpdGlvbg0KKGRhMzp1 bWFzcy1zaW0wOjA6MDozKTogTk9UIFJFQURZIGNzaTowLGFhLDU1LDQwIGFz YzozYSwwDQooZGEzOnVtYXNzLXNpbTA6MDowOjMpOiBNZWRpdW0gbm90IHBy ZXNlbnQgZmllbGQgcmVwbGFjZWFibGUgdW5pdDogNDANCihkYTM6dW1hc3Mt c2ltMDowOjA6Myk6IFVucmV0cnlhYmxlIGVycm9yDQpPcGVuZWQgZGlzayBk YTMgLT4gNg0KKGRhMzp1bWFzcy1zaW0wOjA6MDozKTogUkVBRCBDQVBBQ0lU WS4gQ0RCOiAyNSA2MCAwIDAgMCAwIDAgMCAwIDAgDQooZGEzOnVtYXNzLXNp bTA6MDowOjMpOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1cyBFcnJvcg0KKGRh Mzp1bWFzcy1zaW0wOjA6MDozKTogU0NTSSBTdGF0dXM6IENoZWNrIENvbmRp dGlvbg0KKGRhMzp1bWFzcy1zaW0wOjA6MDozKTogTk9UIFJFQURZIGNzaTow LGFhLDU1LDQwIGFzYzozYSwwDQooZGEzOnVtYXNzLXNpbTA6MDowOjMpOiBN ZWRpdW0gbm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFibGUgdW5pdDogNDAN CihkYTM6dW1hc3Mtc2ltMDowOjA6Myk6IFVucmV0cnlhYmxlIGVycm9yDQpP cGVuZWQgZGlzayBkYTMgLT4gNg0KKGRhMzp1bWFzcy1zaW0wOjA6MDozKTog UkVBRCBDQVBBQ0lUWS4gQ0RCOiAyNSA2MCAwIDAgMCAwIDAgMCAwIDAgDQoo ZGEzOnVtYXNzLXNpbTA6MDowOjMpOiBDQU0gU3RhdHVzOiBTQ1NJIFN0YXR1 cyBFcnJvcg0KKGRhMzp1bWFzcy1zaW0wOjA6MDozKTogU0NTSSBTdGF0dXM6 IENoZWNrIENvbmRpdGlvbg0KKGRhMzp1bWFzcy1zaW0wOjA6MDozKTogTk9U IFJFQURZIGNzaTowLGFhLDU1LDQwIGFzYzozYSwwDQooZGEzOnVtYXNzLXNp bTA6MDowOjMpOiBNZWRpdW0gbm90IHByZXNlbnQgZmllbGQgcmVwbGFjZWFi bGUgdW5pdDogNDANCihkYTM6dW1hc3Mtc2ltMDowOjA6Myk6IFVucmV0cnlh YmxlIGVycm9yDQpPcGVuZWQgZGlzayBkYTMgLT4gNg0KVHJ5aW5nIHRvIG1v dW50IHJvb3QgZnJvbSB1ZnM6L2Rldi9hZDEyczFhDQpXQVJOSU5HOiAvIHdh cyBub3QgcHJvcGVybHkgZGlzbW91bnRlZA0KV0FSTklORzogL2RlcG90IHdh cyBub3QgcHJvcGVybHkgZGlzbW91bnRlZA0KV0FSTklORzogL2RlcG90MiB3 YXMgbm90IHByb3Blcmx5IGRpc21vdW50ZWQNCldBUk5JTkc6IC90bXAgd2Fz IG5vdCBwcm9wZXJseSBkaXNtb3VudGVkDQpXQVJOSU5HOiAvdXNyIHdhcyBu b3QgcHJvcGVybHkgZGlzbW91bnRlZA0KV0FSTklORzogL3ZhciB3YXMgbm90 IHByb3Blcmx5IGRpc21vdW50ZWQNCnJsMDogbGluayBzdGF0ZSBjaGFuZ2Vk IHRvIFVQDQo= --0-2054668743-1144213947=:3698 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=LUXOKERNEL Content-Transfer-Encoding: BASE64 Content-ID: <20060405011227.F3698@as2.dm.egate.net> Content-Description: LUXOKERNEL Content-Disposition: attachment; filename=LUXOKERNEL Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMga2VybmVsIGNvbmZpZ3VyYXRpb24g ZmlsZSBmb3IgRnJlZUJTRC9hbWQ2NA0KIw0KIyBGb3IgbW9yZSBpbmZvcm1h dGlvbiBvbiB0aGlzIGZpbGUsIHBsZWFzZSByZWFkIHRoZSBoYW5kYm9vayBz ZWN0aW9uIG9uDQojIEtlcm5lbCBDb25maWd1cmF0aW9uIEZpbGVzOg0KIw0K IyAgICBodHRwOi8vd3d3LkZyZWVCU0Qub3JnL2RvYy9lbl9VUy5JU084ODU5 LTEvYm9va3MvaGFuZGJvb2sva2VybmVsY29uZmlnLWNvbmZpZy5odG1sDQoj DQojIFRoZSBoYW5kYm9vayBpcyBhbHNvIGF2YWlsYWJsZSBsb2NhbGx5IGlu IC91c3Ivc2hhcmUvZG9jL2hhbmRib29rDQojIGlmIHlvdSd2ZSBpbnN0YWxs ZWQgdGhlIGRvYyBkaXN0cmlidXRpb24sIG90aGVyd2lzZSBhbHdheXMgc2Vl IHRoZQ0KIyBGcmVlQlNEIFdvcmxkIFdpZGUgV2ViIHNlcnZlciAoaHR0cDov L3d3dy5GcmVlQlNELm9yZy8pIGZvciB0aGUNCiMgbGF0ZXN0IGluZm9ybWF0 aW9uLg0KIw0KIyBBbiBleGhhdXN0aXZlIGxpc3Qgb2Ygb3B0aW9ucyBhbmQg bW9yZSBkZXRhaWxlZCBleHBsYW5hdGlvbnMgb2YgdGhlDQojIGRldmljZSBs aW5lcyBpcyBhbHNvIHByZXNlbnQgaW4gdGhlIC4uLy4uL2NvbmYvTk9URVMg YW5kIE5PVEVTIGZpbGVzLg0KIyBJZiB5b3UgYXJlIGluIGRvdWJ0IGFzIHRv IHRoZSBwdXJwb3NlIG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZp cnN0DQojIGluIE5PVEVTLg0KIw0KIyAkRnJlZUJTRDogc3JjL3N5cy9hbWQ2 NC9jb25mL0dFTkVSSUMsdiAxLjQzOS4yLjYuMi4xIDIwMDUvMTAvMjggMTk6 MjI6NDEgamhiIEV4cCAkDQojICRIZWFkZXI6IC9yb290L1JDUy9MVVhPS0VS TkVMLHYgMS40IDIwMDYvMDIvMDcgMTY6NDE6MDkgdGFvYiBFeHAgdGFvYiAk DQoNCm1hY2hpbmUJCWFtZDY0DQpjcHUJCUhBTU1FUg0KaWRlbnQJCUxVWE9L RVJORUwNCg0KIyBUbyBzdGF0aWNhbGx5IGNvbXBpbGUgaW4gZGV2aWNlIHdp cmluZyBpbnN0ZWFkIG9mIC9ib290L2RldmljZS5oaW50cw0KI2hpbnRzCQki R0VORVJJQy5oaW50cyIJCSMgRGVmYXVsdCBwbGFjZXMgdG8gbG9vayBmb3Ig ZGV2aWNlcy4NCg0KbWFrZW9wdGlvbnMJREVCVUc9LWcJCSMgQnVpbGQga2Vy bmVsIHdpdGggZ2RiKDEpIGRlYnVnIHN5bWJvbHMNCg0Kb3B0aW9ucyAJU0NI RURfVUxFCQkjIFVMRSBzY2hlZHVsZXINCiNvcHRpb25zIAlTQ0hFRF80QlNE CQkjIDRCU0Qgc2NoZWR1bGVyDQpvcHRpb25zIAlQUkVFTVBUSU9OCQkjIEVu YWJsZSBrZXJuZWwgdGhyZWFkIHByZWVtcHRpb24NCm9wdGlvbnMgCUlORVQJ CQkjIEludGVyTkVUd29ya2luZw0KI29wdGlvbnMgCUlORVQ2CQkJIyBJUHY2 IGNvbW11bmljYXRpb25zIHByb3RvY29scw0Kb3B0aW9ucyAJRkZTCQkJIyBC ZXJrZWxleSBGYXN0IEZpbGVzeXN0ZW0NCm9wdGlvbnMgCVNPRlRVUERBVEVT CQkjIEVuYWJsZSBGRlMgc29mdCB1cGRhdGVzIHN1cHBvcnQNCm9wdGlvbnMg CVVGU19BQ0wJCQkjIFN1cHBvcnQgZm9yIGFjY2VzcyBjb250cm9sIGxpc3Rz DQpvcHRpb25zIAlVRlNfRElSSEFTSAkJIyBJbXByb3ZlIHBlcmZvcm1hbmNl IG9uIGJpZyBkaXJlY3Rvcmllcw0Kb3B0aW9ucyAJTURfUk9PVAkJCSMgTUQg aXMgYSBwb3RlbnRpYWwgcm9vdCBkZXZpY2UNCm9wdGlvbnMgCU5GU0NMSUVO VAkJIyBOZXR3b3JrIEZpbGVzeXN0ZW0gQ2xpZW50DQpvcHRpb25zIAlORlNT RVJWRVIJCSMgTmV0d29yayBGaWxlc3lzdGVtIFNlcnZlcg0Kb3B0aW9ucyAJ TkZTX1JPT1QJCSMgTkZTIHVzYWJsZSBhcyAvLCByZXF1aXJlcyBORlNDTElF TlQNCm9wdGlvbnMgCU5URlMJCQkjIE5UIEZpbGUgU3lzdGVtDQpvcHRpb25z IAlNU0RPU0ZTCQkJIyBNU0RPUyBGaWxlc3lzdGVtDQpvcHRpb25zIAlDRDk2 NjAJCQkjIElTTyA5NjYwIEZpbGVzeXN0ZW0NCm9wdGlvbnMgCVBST0NGUwkJ CSMgUHJvY2VzcyBmaWxlc3lzdGVtIChyZXF1aXJlcyBQU0VVRE9GUykNCm9w dGlvbnMgCVBTRVVET0ZTCQkjIFBzZXVkby1maWxlc3lzdGVtIGZyYW1ld29y aw0Kb3B0aW9ucyAJR0VPTV9HUFQJCSMgR1VJRCBQYXJ0aXRpb24gVGFibGVz Lg0Kb3B0aW9ucyAJQ09NUEFUXzQzCQkjIE5lZWRlZCBieSBDT01QQVRfTElO VVgzMg0Kb3B0aW9ucyAJQ09NUEFUX0lBMzIJCSMgQ29tcGF0aWJsZSB3aXRo IGkzODYgYmluYXJpZXMNCm9wdGlvbnMgCUNPTVBBVF9GUkVFQlNENAkJIyBD b21wYXRpYmxlIHdpdGggRnJlZUJTRDQNCm9wdGlvbnMgCUNPTVBBVF9GUkVF QlNENQkJIyBDb21wYXRpYmxlIHdpdGggRnJlZUJTRDUNCm9wdGlvbnMgCUNP TVBBVF9MSU5VWDMyCQkjIENvbXBhdGlibGUgd2l0aCBpMzg2IGxpbnV4IGJp bmFyaWVzIA0KI29wdGlvbnMgCVNDU0lfREVMQVk9NTAwMAkJIyBEZWxheSAo aW4gbXMpIGJlZm9yZSBwcm9iaW5nIFNDU0kNCm9wdGlvbnMgCUtUUkFDRQkJ CSMga3RyYWNlKDEpIHN1cHBvcnQNCm9wdGlvbnMgCVNZU1ZTSE0JCQkjIFNZ U1Ytc3R5bGUgc2hhcmVkIG1lbW9yeQ0Kb3B0aW9ucyAJU1lTVk1TRwkJCSMg U1lTVi1zdHlsZSBtZXNzYWdlIHF1ZXVlcw0Kb3B0aW9ucyAJU1lTVlNFTQkJ CSMgU1lTVi1zdHlsZSBzZW1hcGhvcmVzDQpvcHRpb25zIAlfS1BPU0lYX1BS SU9SSVRZX1NDSEVEVUxJTkcgIyBQT1NJWCBQMTAwM18xQiByZWFsLXRpbWUg ZXh0ZW5zaW9ucw0Kb3B0aW9ucyAJS0JEX0lOU1RBTExfQ0RFVgkjIGluc3Rh bGwgYSBDREVWIGVudHJ5IGluIC9kZXYNCiNvcHRpb25zIAlBSENfUkVHX1BS RVRUWV9QUklOVAkjIFByaW50IHJlZ2lzdGVyIGJpdGZpZWxkcyBpbiBkZWJ1 Zw0KCQkJCQkjIG91dHB1dC4gIEFkZHMgfjEyOGsgdG8gZHJpdmVyLg0KI29w dGlvbnMgCUFIRF9SRUdfUFJFVFRZX1BSSU5UCSMgUHJpbnQgcmVnaXN0ZXIg Yml0ZmllbGRzIGluIGRlYnVnDQoJCQkJCSMgb3V0cHV0LiAgQWRkcyB+MjE1 ayB0byBkcml2ZXIuDQpvcHRpb25zIAlBREFQVElWRV9HSUFOVAkJIyBHaWFu dCBtdXRleCBpcyBhZGFwdGl2ZS4NCm9wdGlvbnMJCU1BQwkJCSMgTWFuZGF0 b3J5IEFjY2VzcyBDb250cm9sIHN1cHBvcnQNCm9wdGlvbnMgCUlQRklMVEVS X0xPRwkJIyBpcGZpbHRlciBsb2dnaW5nIChpcG1vbikNCm9wdGlvbnMJCVFV T1RBCQkJI2VuYWJsZSBkaXNrIHF1b3Rhcw0KDQojIFdvcmthcm91bmRzIGZv ciBzb21lIGtub3duLXRvLWJlLWJyb2tlbiBjaGlwc2V0cyAoblZpZGlhIG5G b3JjZTMtUHJvMTUwKQ0KZGV2aWNlCQlhdHBpYwkJCSMgODI1OUEgY29tcGF0 YWJpbGl0eQ0KDQojIExpbnV4IDMyLWJpdCBBQkkgc3VwcG9ydA0Kb3B0aW9u cyAJTElOUFJPQ0ZTCQkjIENhbm5vdCBiZSBhIG1vZHVsZSB5ZXQuDQoNCiMg QnVzIHN1cHBvcnQuDQpkZXZpY2UJCWFjcGkNCmRldmljZQkJcGNpDQoNCiMg RmxvcHB5IGRyaXZlcw0KZGV2aWNlCQlmZGMNCg0KIyBBVEEgYW5kIEFUQVBJ IGRldmljZXMNCmRldmljZQkJYXRhDQpkZXZpY2UJCWF0YWRpc2sJCSMgQVRB IGRpc2sgZHJpdmVzDQpkZXZpY2UJCWF0YXJhaWQJCSMgQVRBIFJBSUQgZHJp dmVzDQpkZXZpY2UJCWF0YXBpY2QJCSMgQVRBUEkgQ0RST00gZHJpdmVzDQoj ZGV2aWNlCQlhdGFwaWZkCQkjIEFUQVBJIGZsb3BweSBkcml2ZXMNCiNkZXZp Y2UJCWF0YXBpc3QJCSMgQVRBUEkgdGFwZSBkcml2ZXMNCm9wdGlvbnMgCUFU QV9TVEFUSUNfSUQJIyBTdGF0aWMgZGV2aWNlIG51bWJlcmluZw0KDQojIFND U0kgQ29udHJvbGxlcnMNCiNkZXZpY2UJCWFoYwkJIyBBSEEyOTQwIGFuZCBv bmJvYXJkIEFJQzd4eHggZGV2aWNlcw0KI2RldmljZQkJYWhkCQkjIEFIQTM5 MzIwLzI5MzIwIGFuZCBvbmJvYXJkIEFJQzc5eHggZGV2aWNlcw0KI2Rldmlj ZQkJYW1kCQkjIEFNRCA1M0M5NzQgKFRla3JhbSBEQy0zOTAoVCkpDQojZGV2 aWNlCQlpc3AJCSMgUWxvZ2ljIGZhbWlseQ0KIyNkZXZpY2UgCWlzcGZ3CQkj IEZpcm13YXJlIGZvciBRTG9naWMgSEJBcy0gbm9ybWFsbHkgYSBtb2R1bGUN CiNkZXZpY2UJCW1wdAkJIyBMU0ktTG9naWMgTVBULUZ1c2lvbg0KI2Rldmlj ZQkJbmNyCQkjIE5DUi9TeW1iaW9zIExvZ2ljDQojZGV2aWNlCQlzeW0JCSMg TkNSL1N5bWJpb3MgTG9naWMgKG5ld2VyIGNoaXBzZXRzICsgdGhvc2Ugb2Yg YG5jcicpDQojZGV2aWNlCQl0cm0JCSMgVGVrcmFtIERDMzk1VS9VVy9GIERD MzE1VSBhZGFwdGVycw0KDQojZGV2aWNlCQlhZHYJCSMgQWR2YW5zeXMgU0NT SSBhZGFwdGVycw0KI2RldmljZQkJYWR3CQkjIEFkdmFuc3lzIHdpZGUgU0NT SSBhZGFwdGVycw0KI2RldmljZQkJYWljCQkjIEFkYXB0ZWMgMTVbMDEyXXgg U0NTSSBhZGFwdGVycywgQUlDLTZbMjNdNjAuDQojZGV2aWNlCQlidAkJIyBC dXNsb2dpYy9NeWxleCBNdWx0aU1hc3RlciBTQ1NJIGFkYXB0ZXJzDQoNCg0K IyBTQ1NJIHBlcmlwaGVyYWxzDQpkZXZpY2UJCXNjYnVzCQkjIFNDU0kgYnVz IChyZXF1aXJlZCBmb3IgU0NTSSkNCiNkZXZpY2UJCWNoCQkjIFNDU0kgbWVk aWEgY2hhbmdlcnMNCmRldmljZQkJZGEJCSMgRGlyZWN0IEFjY2VzcyAoZGlz a3MpDQojZGV2aWNlCQlzYQkJIyBTZXF1ZW50aWFsIEFjY2VzcyAodGFwZSBl dGMpDQojZGV2aWNlCQljZAkJIyBDRA0KZGV2aWNlCQlwYXNzCQkjIFBhc3N0 aHJvdWdoIGRldmljZSAoZGlyZWN0IFNDU0kgYWNjZXNzKQ0KI2RldmljZQkJ c2VzCQkjIFNDU0kgRW52aXJvbm1lbnRhbCBTZXJ2aWNlcyAoYW5kIFNBRi1U RSkNCg0KIyBSQUlEIGNvbnRyb2xsZXJzIGludGVyZmFjZWQgdG8gdGhlIFND U0kgc3Vic3lzdGVtDQojZGV2aWNlCQlhbXIJCSMgQU1JIE1lZ2FSQUlEDQoj ZGV2aWNlCQlhcmNtc3IJCSMgQXJlY2EgU0FUQSBJSSBSQUlEDQojZGV2aWNl CQljaXNzCQkjIENvbXBhcSBTbWFydCBSQUlEIDUqDQojZGV2aWNlCQlkcHQJ CSMgRFBUIFNtYXJ0Y2FjaGUgSUlJLCBJViAtIFNlZSBOT1RFUyBmb3Igb3B0 aW9ucw0KI2RldmljZQkJaHB0bXYJCSMgSGlnaHBvaW50IFJvY2tldFJBSUQg MTgyeA0KI2RldmljZQkJaWlyCQkjIEludGVsIEludGVncmF0ZWQgUkFJRA0K I2RldmljZQkJaXBzCQkjIElCTSAoQWRhcHRlYykgU2VydmVSQUlEDQojZGV2 aWNlCQltbHkJCSMgTXlsZXggQWNjZWxlUkFJRC9lWHRyZW1lUkFJRA0KI2Rl dmljZQkJdHdhCQkjIDN3YXJlIDkwMDAgc2VyaWVzIFBBVEEvU0FUQSBSQUlE DQoNCiMgUkFJRCBjb250cm9sbGVycw0KI2RldmljZQkJYWFjCQkjIEFkYXB0 ZWMgRlNBIFJBSUQNCiNkZXZpY2UJCWFhY3AJCSMgU0NTSSBwYXNzdGhyb3Vn aCBmb3IgYWFjIChyZXF1aXJlcyBDQU0pDQojZGV2aWNlCQlpZGEJCSMgQ29t cGFxIFNtYXJ0IFJBSUQNCiNkZXZpY2UJCW1seAkJIyBNeWxleCBEQUM5NjAg ZmFtaWx5DQojWFhYIHBvaW50ZXIvaW50IHdhcm5pbmdzDQojZGV2aWNlCQlw c3QJCSMgUHJvbWlzZSBTdXBlcnRyYWsgU1g2MDAwDQojZGV2aWNlCQl0d2UJ CSMgM3dhcmUgQVRBIFJBSUQNCg0KIyBhdGtiZGMwIGNvbnRyb2xzIGJvdGgg dGhlIGtleWJvYXJkIGFuZCB0aGUgUFMvMiBtb3VzZQ0KZGV2aWNlCQlhdGti ZGMJCSMgQVQga2V5Ym9hcmQgY29udHJvbGxlcg0KZGV2aWNlCQlhdGtiZAkJ IyBBVCBrZXlib2FyZA0KZGV2aWNlCQlwc20JCSMgUFMvMiBtb3VzZQ0KDQpk ZXZpY2UJCXZnYQkJIyBWR0EgdmlkZW8gY2FyZCBkcml2ZXINCg0KZGV2aWNl CQlzcGxhc2gJCSMgU3BsYXNoIHNjcmVlbiBhbmQgc2NyZWVuIHNhdmVyIHN1 cHBvcnQNCg0KIyBzeXNjb25zIGlzIHRoZSBkZWZhdWx0IGNvbnNvbGUgZHJp dmVyLCByZXNlbWJsaW5nIGFuIFNDTyBjb25zb2xlDQpkZXZpY2UJCXNjDQoN CmRldmljZQkJYWdwCQkjIHN1cHBvcnQgc2V2ZXJhbCBBR1AgY2hpcHNldHMN Cg0KIyBQQ0NBUkQgKFBDTUNJQSkgc3VwcG9ydA0KIyBQQ01DSUEgYW5kIGNh cmRidXMgYnJpZGdlIHN1cHBvcnQNCiNkZXZpY2UJCWNiYgkJIyBjYXJkYnVz ICh5ZW50YSkgYnJpZGdlDQojZGV2aWNlCQlwY2NhcmQJCSMgUEMgQ2FyZCAo MTYtYml0KSBidXMNCiNkZXZpY2UJCWNhcmRidXMJCSMgQ2FyZEJ1cyAoMzIt Yml0KSBidXMNCg0KIyBTZXJpYWwgKENPTSkgcG9ydHMNCmRldmljZQkJc2lv CQkjIDgyNTAsIDE2WzQ1XTUwIGJhc2VkIHNlcmlhbCBwb3J0cw0KDQojIFBh cmFsbGVsIHBvcnQNCiNkZXZpY2UJCXBwYw0KI2RldmljZQkJcHBidXMJCSMg UGFyYWxsZWwgcG9ydCBidXMgKHJlcXVpcmVkKQ0KI2RldmljZQkJbHB0CQkj IFByaW50ZXINCiNkZXZpY2UJCXBsaXAJCSMgVENQL0lQIG92ZXIgcGFyYWxs ZWwNCiNkZXZpY2UJCXBwaQkJIyBQYXJhbGxlbCBwb3J0IGludGVyZmFjZSBk ZXZpY2UNCiNkZXZpY2UJCXZwbwkJIyBSZXF1aXJlcyBzY2J1cyBhbmQgZGEN Cg0KIyBJZiB5b3UndmUgZ290IGEgImR1bWIiIHNlcmlhbCBvciBwYXJhbGxl bCBQQ0kgY2FyZCB0aGF0IGlzDQojIHN1cHBvcnRlZCBieSB0aGUgcHVjKDQp IGdsdWUgZHJpdmVyLCB1bmNvbW1lbnQgdGhlIGZvbGxvd2luZw0KIyBsaW5l IHRvIGVuYWJsZSBpdCAoY29ubmVjdHMgdG8gdGhlIHNpbyBhbmQvb3IgcHBj IGRyaXZlcnMpOg0KI2RldmljZQkJcHVjDQoNCiMgUENJIEV0aGVybmV0IE5J Q3MuDQojZGV2aWNlCQlkZQkJIyBERUMvSW50ZWwgREMyMXg0eCAoYGBUdWxp cCcnKQ0KI2RldmljZQkJZW0JCSMgSW50ZWwgUFJPLzEwMDAgYWRhcHRlciBH aWdhYml0IEV0aGVybmV0IENhcmQNCiNkZXZpY2UJCWl4Z2IJCSMgSW50ZWwg UFJPLzEwR2JFIEV0aGVybmV0IENhcmQNCiNkZXZpY2UJCXR4cAkJIyAzQ29t IDNjUjk5MCAoYGBUeXBob29uJycpDQojZGV2aWNlCQl2eAkJIyAzQ29tIDNj NTkwLCAzYzU5NSAoYGBWb3J0ZXgnJykNCg0KIyBQQ0kgRXRoZXJuZXQgTklD cyB0aGF0IHVzZSB0aGUgY29tbW9uIE1JSSBidXMgY29udHJvbGxlciBjb2Rl Lg0KIyBOT1RFOiBCZSBzdXJlIHRvIGtlZXAgdGhlICdkZXZpY2UgbWlpYnVz JyBsaW5lIGluIG9yZGVyIHRvIHVzZSB0aGVzZSBOSUNzIQ0KZGV2aWNlCQlt aWlidXMJCSMgTUlJIGJ1cyBzdXBwb3J0DQojZGV2aWNlCQliZmUJCSMgQnJv YWRjb20gQkNNNDQweCAxMC8xMDAgRXRoZXJuZXQNCiNkZXZpY2UJCWJnZQkJ IyBCcm9hZGNvbSBCQ001NzB4eCBHaWdhYml0IEV0aGVybmV0DQojZGV2aWNl CQlkYwkJIyBERUMvSW50ZWwgMjExNDMgYW5kIHZhcmlvdXMgd29ya2FsaWtl cw0KI2RldmljZQkJZnhwCQkjIEludGVsIEV0aGVyRXhwcmVzcyBQUk8vMTAw QiAoODI1NTcsIDgyNTU4KQ0KI2RldmljZQkJbGdlCQkjIExldmVsIDEgTFhU MTAwMSBnaWdhYml0IEV0aGVybmV0DQojZGV2aWNlCQluZ2UJCSMgTmF0U2Vt aSBEUDgzODIwIGdpZ2FiaXQgRXRoZXJuZXQNCiNkZXZpY2UJCW52ZQkJIyBu VmlkaWEgbkZvcmNlIE1DUCBvbi1ib2FyZCBFdGhlcm5ldCBOZXR3b3JraW5n DQojZGV2aWNlCQlwY24JCSMgQU1EIEFtNzlDOTd4IFBDSSAxMC8xMDAocHJl Y2VkZW5jZSBvdmVyICdsbmMnKQ0KI2RldmljZQkJcmUJCSMgUmVhbFRlayA4 MTM5QysvODE2OS84MTY5Uy84MTEwUw0KZGV2aWNlCQlybAkJIyBSZWFsVGVr IDgxMjkvODEzOQ0KI2RldmljZQkJc2YJCSMgQWRhcHRlYyBBSUMtNjkxNSAo YGBTdGFyZmlyZScnKQ0KI2RldmljZQkJc2lzCQkjIFNpbGljb24gSW50ZWdy YXRlZCBTeXN0ZW1zIFNpUyA5MDAvU2lTIDcwMTYNCiNkZXZpY2UJCXNrCQkj IFN5c0tvbm5lY3QgU0stOTg0eCAmIFNLLTk4MnggZ2lnYWJpdCBFdGhlcm5l dA0KI2RldmljZQkJc3RlCQkjIFN1bmRhbmNlIFNUMjAxIChELUxpbmsgREZF LTU1MFRYKQ0KI2RldmljZQkJdGkJCSMgQWx0ZW9uIE5ldHdvcmtzIFRpZ29u IEkvSUkgZ2lnYWJpdCBFdGhlcm5ldA0KI2RldmljZQkJdGwJCSMgVGV4YXMg SW5zdHJ1bWVudHMgVGh1bmRlckxBTg0KI2RldmljZQkJdHgJCSMgU01DIEV0 aGVyUG93ZXIgSUkgKDgzYzE3MCBgYEVQSUMnJykNCiNkZXZpY2UJCXZnZQkJ IyBWSUEgVlQ2MTJ4IGdpZ2FiaXQgRXRoZXJuZXQNCiNkZXZpY2UJCXZyCQkj IFZJQSBSaGluZSwgUmhpbmUgSUkNCiNkZXZpY2UJCXdiCQkjIFdpbmJvbmQg Vzg5Qzg0MEYNCiNkZXZpY2UJCXhsCQkjIDNDb20gM2M5MHggKGBgQm9vbWVy YW5nJycsIGBgQ3ljbG9uZScnKQ0KDQojIElTQSBFdGhlcm5ldCBOSUNzLiAg cGNjYXJkIE5JQ3MgaW5jbHVkZWQuDQojZGV2aWNlCQljcwkJIyBDcnlzdGFs IFNlbWljb25kdWN0b3IgQ1M4OXgwIE5JQw0KIyAnZGV2aWNlIGVkJyByZXF1 aXJlcyAnZGV2aWNlIG1paWJ1cycNCiNkZXZpY2UJCWVkCQkjIE5FWzEyXTAw MCwgU01DIFVsdHJhLCAzYzUwMywgRFM4MzkwIGNhcmRzDQojZGV2aWNlCQll eAkJIyBJbnRlbCBFdGhlckV4cHJlc3MgUHJvLzEwIGFuZCBQcm8vMTArDQoj ZGV2aWNlCQllcAkJIyBFdGhlcmxpbmsgSUlJIGJhc2VkIGNhcmRzDQojZGV2 aWNlCQlmZQkJIyBGdWppdHN1IE1CODY5NnggYmFzZWQgY2FyZHMNCiMgWFhY IGt2dG9wIGJyb2tlbm5lc3MsIHBvaW50ZXIvaW50IHdhcm5pbmdzDQojZGV2 aWNlCQlsbmMJCSMgTkUyMTAwLCBORTMyLVZMIExhbmNlIEV0aGVybmV0IGNh cmRzDQojZGV2aWNlCQlzbgkJIyBTTUMncyA5MDAwIHNlcmllcyBvZiBFdGhl cm5ldCBjaGlwcw0KI2RldmljZQkJeGUJCSMgWGlyY29tIHBjY2FyZCBFdGhl cm5ldA0KDQojIFdpcmVsZXNzIE5JQyBjYXJkcw0KI2RldmljZQkJd2xhbgkJ IyA4MDIuMTEgc3VwcG9ydA0KI2RldmljZQkJYW4JCSMgQWlyb25ldCA0NTAw LzQ4MDAgODAyLjExIHdpcmVsZXNzIE5JQ3MuDQojZGV2aWNlCQlhd2kJCSMg QmF5U3RhY2sgNjYwIGFuZCBvdGhlcnMNCiNkZXZpY2UJCXJhbAkJIyBSYWxp bmsgVGVjaG5vbG9neSBSVDI1MDAgd2lyZWxlc3MgTklDcy4NCiNkZXZpY2UJ CXdpCQkjIFdhdmVMQU4vSW50ZXJzaWwvU3ltYm9sIDgwMi4xMSB3aXJlbGVz cyBOSUNzLg0KDQojIFBzZXVkbyBkZXZpY2VzLg0KZGV2aWNlCQlsb29wCQkj IE5ldHdvcmsgbG9vcGJhY2sNCmRldmljZQkJcmFuZG9tCQkjIEVudHJvcHkg ZGV2aWNlDQpkZXZpY2UJCWV0aGVyCQkjIEV0aGVybmV0IHN1cHBvcnQNCiNk ZXZpY2UJCXNsCQkjIEtlcm5lbCBTTElQDQojZGV2aWNlCQlwcHAJCSMgS2Vy bmVsIFBQUA0KZGV2aWNlCQl0dW4JCSMgUGFja2V0IHR1bm5lbC4NCmRldmlj ZQkJcHR5CQkjIFBzZXVkby10dHlzICh0ZWxuZXQgZXRjKQ0KZGV2aWNlCQlt ZAkJIyBNZW1vcnkgImRpc2tzIg0KI2RldmljZQkJZ2lmCQkjIElQdjYgYW5k IElQdjQgdHVubmVsaW5nDQojZGV2aWNlCQlmYWl0aAkJIyBJUHY2LXRvLUlQ djQgcmVsYXlpbmcgKHRyYW5zbGF0aW9uKQ0KDQojIFRoZSBgYnBmJyBkZXZp Y2UgZW5hYmxlcyB0aGUgQmVya2VsZXkgUGFja2V0IEZpbHRlci4NCiMgQmUg YXdhcmUgb2YgdGhlIGFkbWluaXN0cmF0aXZlIGNvbnNlcXVlbmNlcyBvZiBl bmFibGluZyB0aGlzIQ0KIyBOb3RlIHRoYXQgJ2JwZicgaXMgcmVxdWlyZWQg Zm9yIERIQ1AuDQpkZXZpY2UJCWJwZgkJIyBCZXJrZWxleSBwYWNrZXQgZmls dGVyDQoNCiMgVVNCIHN1cHBvcnQNCmRldmljZQkJdWhjaQkJIyBVSENJIFBD SS0+VVNCIGludGVyZmFjZQ0KZGV2aWNlCQlvaGNpCQkjIE9IQ0kgUENJLT5V U0IgaW50ZXJmYWNlDQpkZXZpY2UJCWVoY2kJCSMgRUhDSSBQQ0ktPlVTQiBp bnRlcmZhY2UgKFVTQiAyLjApDQpkZXZpY2UJCXVzYgkJIyBVU0IgQnVzIChy ZXF1aXJlZCkNCiNkZXZpY2UJCXVkYnAJCSMgVVNCIERvdWJsZSBCdWxrIFBp cGUgZGV2aWNlcw0KZGV2aWNlCQl1Z2VuCQkjIEdlbmVyaWMNCmRldmljZQkJ dWhpZAkJIyAiSHVtYW4gSW50ZXJmYWNlIERldmljZXMiDQpkZXZpY2UJCXVr YmQJCSMgS2V5Ym9hcmQNCiNkZXZpY2UJCXVscHQJCSMgUHJpbnRlcg0KZGV2 aWNlCQl1bWFzcwkJIyBEaXNrcy9NYXNzIHN0b3JhZ2UgLSBSZXF1aXJlcyBz Y2J1cyBhbmQgZGENCiNkZXZpY2UJCXVtcwkJIyBNb3VzZQ0KI2RldmljZQkJ dXJhbAkJIyBSYWxpbmsgVGVjaG5vbG9neSBSVDI1MDBVU0Igd2lyZWxlc3Mg TklDcw0KI2RldmljZQkJdXJpbwkJIyBEaWFtb25kIFJpbyA1MDAgTVAzIHBs YXllcg0KI2RldmljZQkJdXNjYW5uZXIJIyBTY2FubmVycw0KIyBVU0IgRXRo ZXJuZXQsIHJlcXVpcmVzIG1paWJ1cw0KI2RldmljZQkJYXVlCQkjIEFETXRl ayBVU0IgRXRoZXJuZXQNCiNkZXZpY2UJCWF4ZQkJIyBBU0lYIEVsZWN0cm9u aWNzIFVTQiBFdGhlcm5ldA0KI2RldmljZQkJY2RjZQkJIyBHZW5lcmljIFVT QiBvdmVyIEV0aGVybmV0DQojZGV2aWNlCQljdWUJCSMgQ0FUQyBVU0IgRXRo ZXJuZXQNCiNkZXZpY2UJCWt1ZQkJIyBLYXdhc2FraSBMU0kgVVNCIEV0aGVy bmV0DQojZGV2aWNlCQlydWUJCSMgUmVhbFRlayBSVEw4MTUwIFVTQiBFdGhl cm5ldA0KDQojIEZpcmVXaXJlIHN1cHBvcnQNCiNkZXZpY2UJCWZpcmV3aXJl CSMgRmlyZVdpcmUgYnVzIGNvZGUNCiNkZXZpY2UJCXNicAkJIyBTQ1NJIG92 ZXIgRmlyZVdpcmUgKFJlcXVpcmVzIHNjYnVzIGFuZCBkYSkNCiNkZXZpY2UJ CWZ3ZQkJIyBFdGhlcm5ldCBvdmVyIEZpcmVXaXJlIChub24tc3RhbmRhcmQh KQ0K --0-2054668743-1144213947=:3698-- From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 05:21: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 6FDB316A401 for ; Wed, 5 Apr 2006 05:21: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 2BAF743D45 for ; Wed, 5 Apr 2006 05:21:30 +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 142B01A4D88; Tue, 4 Apr 2006 22:21:30 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 69C7C53CA9; Wed, 5 Apr 2006 01:21:29 -0400 (EDT) Date: Wed, 5 Apr 2006 01:21:29 -0400 From: Kris Kennaway To: Brian Tao Message-ID: <20060405052129.GA93087@xor.obsecurity.org> References: <20060405050221.GA92737@xor.obsecurity.org> <20060405010819.J3698-300000@as2.dm.egate.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <20060405010819.J3698-300000@as2.dm.egate.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 05:21:30 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 01:12:27AM -0400, Brian Tao wrote: > On Wed, 5 Apr 2006, Kris Kennaway wrote: > > > > It would be helpful (i.e. more likely to get responses) if you could > > post a relevant extract, so people don't have to download the tarball. >=20 > Sorry, sure... the one kgdb output is below, and I've attached the > dmesg.boot and kernel config files. It's just that it appears the > panic is in a different part of the kernel each time,, so I figured it > would be best to include more examples. That's often an indication that your hardware is falling apart... > FreeBSD 6.0-RELEASE-p4 #2: Tue Feb 7 18:04:40 EST 2006 > options SCHED_ULE # ULE scheduler Don't use ULE if you have stability problems, it's known to have problems. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > options MAC # Mandatory Access Control support > options IPFILTER_LOG # ipfilter logging (ipmon) > options QUOTA #enable disk quotas QUOTA is broken in 6.0, try 6.1 or disable it. Also disable bg fsck until you can upgrade since it can deadlock or panic in 6.0. Kris --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEM1PYWry0BWjoQKURAnIiAKDyu+UBoZdiDCMDCqwGNmi3unQWWwCeKiht RzS/Na6S55FrRUEZ1Y8Hw2Y= =C7s4 -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 05:28: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 C2F3616A400 for ; Wed, 5 Apr 2006 05:28:13 +0000 (UTC) (envelope-from brian@luxography.ca) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7991F43D46 for ; Wed, 5 Apr 2006 05:28:13 +0000 (GMT) (envelope-from brian@luxography.ca) Received: by as2.dm.egate.net (Postfix, from userid 8159) id CD23E4B0E; Wed, 5 Apr 2006 01:28:12 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id C20C04B0B; Wed, 5 Apr 2006 01:28:12 -0400 (EDT) Date: Wed, 5 Apr 2006 01:28:12 -0400 (EDT) From: Brian Tao X-X-Sender: taob@as2.dm.egate.net To: Kris Kennaway In-Reply-To: <20060405052129.GA93087@xor.obsecurity.org> Message-ID: <20060405012556.Q3698-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-amd64@freebsd.org Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 05:28:13 -0000 On Wed, 5 Apr 2006, Kris Kennaway wrote: > > That's often an indication that your hardware is falling apart... Eeech, I was thinking that given the random panics... it's all brand-new hardware, vendor-recommended RAM, ample cooling, ample and clean power, etc. I'll try some of the suggestions below before swapping out hardware components. > > FreeBSD 6.0-RELEASE-p4 #2: Tue Feb 7 18:04:40 EST 2006 > > > options SCHED_ULE # ULE scheduler > > Don't use ULE if you have stability problems, it's known to have > problems. > > > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > options MAC # Mandatory Access Control support > > options IPFILTER_LOG # ipfilter logging (ipmon) > > options QUOTA #enable disk quotas > > QUOTA is broken in 6.0, try 6.1 or disable it. Also disable bg fsck > until you can upgrade since it can deadlock or panic in 6.0. Great, thanks for the suggestions... muchly appreciated! -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 13:31:05 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 7588216A422 for ; Wed, 5 Apr 2006 13:31:05 +0000 (UTC) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from svinew.natur.cuni.cz (svinew.natur.cuni.cz [195.113.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE38943D46 for ; Wed, 5 Apr 2006 13:31:04 +0000 (GMT) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from svinew.natur.cuni.cz (svinew.natur.cuni.cz [127.0.0.1]) by svinew.natur.cuni.cz (8.13.1/8.13.1) with ESMTP id k35DUv9Z018802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Apr 2006 15:31:02 +0200 Received: from localhost (xdavid@localhost) by svinew.natur.cuni.cz (8.13.1/8.13.1/Submit) with ESMTP id k35DUvZH018799 for ; Wed, 5 Apr 2006 15:30:57 +0200 Date: Wed, 5 Apr 2006 15:30:57 +0200 (CEST) From: xdavid@lib-eth.natur.cuni.cz To: freebsd-amd64@freebsd.org In-Reply-To: <20060405005220.X3698-100000@as2.dm.egate.net> Message-ID: References: <20060405005220.X3698-100000@as2.dm.egate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: connection rate limitation for sshd - is it possible ? 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, 05 Apr 2006 13:31:05 -0000 Hi all, please, is there a way to limit the number of connections to openssh daemon per time period per source ip address ? I am using this on linux boxes with iptables, but couldn't figure out how to do this with IPF on FreeBSD. If it is not possible, is there another way how to do this ? Or do you think it is (un)wise to run sshd under inetd with "-C" switch or "max-connections-per-ip-per-minute" parameter ? Thanks in advance, David Komanek From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 5 15:24: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 20D9116A423 for ; Wed, 5 Apr 2006 15:24:50 +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 5F6A443D69 for ; Wed, 5 Apr 2006 15:24:38 +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 1C243B81E for ; Wed, 5 Apr 2006 11:24:38 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <20060405012556.Q3698-100000@as2.dm.egate.net> References: <20060405012556.Q3698-100000@as2.dm.egate.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 5 Apr 2006 11:24:37 -0400 To: FreeBSD AMD list X-Mailer: Apple Mail (2.749.3) Subject: Re: Disk I/O-related panics in 6.0-RELEASE? 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, 05 Apr 2006 15:24:50 -0000 On Apr 5, 2006, at 1:28 AM, Brian Tao wrote: > Eeech, I was thinking that given the random panics... it's all > brand-new hardware, vendor-recommended RAM, ample cooling, ample and > clean power, etc. I'll try some of the suggestions below before > swapping out hardware components. All hardware is not created the same.... Last year I went through 5 motherboards, two full systems, lots of RAM sticks, yada yada yada, all to get *one* stable server out of it. Needless to say, I don't buy that vendor anymore. Last system I got was a SunFire X4100. Rock solid stable from day one. Worth every premium penny I paid for the Q/A they put in it. From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 03:53:06 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 81D7B16A400 for ; Thu, 6 Apr 2006 03:53:06 +0000 (UTC) (envelope-from freebsd-amd64@molecon.ru) Received: from mail.migtel.ru (mail.migtel.ru [80.240.208.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1869743D46 for ; Thu, 6 Apr 2006 03:53:05 +0000 (GMT) (envelope-from freebsd-amd64@molecon.ru) Received: from mail.migtel.ru (unknown [80.240.208.45]) by mail.migtel.ru (Postfix) with ESMTP id 450654BF073 for ; Thu, 6 Apr 2006 07:53:05 +0400 (MSD) Received: from [10.20.5.22] (unknown [10.20.5.22]) by mail.migtel.ru (Postfix) with ESMTP for ; Thu, 6 Apr 2006 07:53:05 +0400 (MSD) Date: Thu, 6 Apr 2006 07:52:21 +0400 From: Oleg Rusanov X-Mailer: The Bat! (v3.65.03) Professional Organization: Molecon X-Priority: 3 (Normal) Message-ID: <944389706.20060406075221@molecon.ru> To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP on Free.migtel.ru Subject: WCPU = 194.21% for mysqld X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oleg Rusanov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 03:53:06 -0000 Çäðàâñòâóéòå, . amd64# top last pid: 1278; load averages: 1.93, 0.57, 0.21 up 0+00:03:30 00:31:40 86 processes: 3 running, 83 sleeping CPU states: 97.9% user, 0.0% nice, 1.6% system, 0.5% interrupt, 0.0% idle Mem: 270M Active, 959M Inact, 237M Wired, 7080K Cache, 214M Buf, 480M Free Swap: 8192M Total, 8192M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 1102 mysql 4 20 0 323M 80084K kserel 0 1:55 194.21% mysqld is this ok? -- Regards, Oleg mailto:freebsd-amd64@molecon.ru From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 04:01: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 9296416A425 for ; Thu, 6 Apr 2006 04:01:07 +0000 (UTC) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F23A543D45 for ; Thu, 6 Apr 2006 04:01:06 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id E4F69131DF1; Thu, 6 Apr 2006 13:31:05 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id CA57D86F6C; Thu, 6 Apr 2006 13:31:05 +0930 (CST) Date: Thu, 6 Apr 2006 13:31:05 +0930 From: Greg 'groggy' Lehey To: Oleg Rusanov Message-ID: <20060406040105.GN53269@wantadilla.lemis.com> References: <944389706.20060406075221@molecon.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U6leaJ20qZQc29iB" Content-Disposition: inline In-Reply-To: <944389706.20060406075221@molecon.ru> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 VoIP: sip:0871270137@sip.internode.on.net WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: freebsd-amd64@freebsd.org Subject: Re: WCPU = 194.21% for mysqld 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, 06 Apr 2006 04:01:07 -0000 --U6leaJ20qZQc29iB Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thursday, 6 April 2006 at 7:52:21 +0400, Oleg Rusanov wrote: > =C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5, . > > amd64# top > last pid: 1278; load averages: 1.93, 0.57, 0.21 = up 0+00:03:30 00:31:40 > 86 processes: 3 running, 83 sleeping > CPU states: 97.9% user, 0.0% nice, 1.6% system, 0.5% interrupt, 0.0% = idle > Mem: 270M Active, 959M Inact, 237M Wired, 7080K Cache, 214M Buf, 480M Free > Swap: 8192M Total, 8192M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 1102 mysql 4 20 0 323M 80084K kserel 0 1:55 194.21% mysqld > > is this ok? It's harmless, anyway. At worst it's an error in process time accounting. Which version of FreeBSD? Some people have seen mysqld crash on AMD 64 machines, and some think that there's a relationship with the hardware. Have you had any crashes? Greg -- See complete headers for address and phone numbers. --U6leaJ20qZQc29iB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFENJKBIubykFB6QiMRAqvwAJ48d+IerEOfR3ln5m5w8/t1LIVybgCfcqqm UqVZVqVDXKIdNAzd4s9Svf8= =hH+F -----END PGP SIGNATURE----- --U6leaJ20qZQc29iB-- From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 04:09: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 7D08016A424 for ; Thu, 6 Apr 2006 04:09:36 +0000 (UTC) (envelope-from freebsd-amd64@molecon.ru) Received: from mail.migtel.ru (mail.migtel.ru [80.240.208.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D6CE43D45 for ; Thu, 6 Apr 2006 04:09:32 +0000 (GMT) (envelope-from freebsd-amd64@molecon.ru) Received: from mail.migtel.ru (unknown [80.240.208.45]) by mail.migtel.ru (Postfix) with ESMTP id BBC4B4BF07B for ; Thu, 6 Apr 2006 08:09:30 +0400 (MSD) Received: from [10.20.5.22] (unknown [10.20.5.22]) by mail.migtel.ru (Postfix) with ESMTP for ; Thu, 6 Apr 2006 08:09:30 +0400 (MSD) Date: Thu, 6 Apr 2006 08:08:48 +0400 From: Oleg Rusanov X-Mailer: The Bat! (v3.65.03) Professional Organization: Molecon X-Priority: 3 (Normal) Message-ID: <1884573694.20060406080848@molecon.ru> To: freebsd-amd64@freebsd.org In-Reply-To: <20060406040105.GN53269@wantadilla.lemis.com> References: <944389706.20060406075221@molecon.ru> <20060406040105.GN53269@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on Free.migtel.ru Subject: Re[2]: WCPU = 194.21% for mysqld X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oleg Rusanov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 04:09:36 -0000 >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND >> 1102 mysql 4 20 0 323M 80084K kserel 0 1:55 194.21% mysqld > It's harmless, anyway. At worst it's an error in process time > accounting. Which version of FreeBSD? > Some people have seen mysqld crash on AMD 64 machines, and some think > that there's a relationship with the hardware. Have you had any > crashes? > Greg 6.0-RELEASE-p6 FreeBSD There were crashes, but it seemed to me that from a dust on modules of memory. -- Regards, Oleg mailto:freebsd-amd64@molecon.ru From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 04:20:57 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 F413316A424 for ; Thu, 6 Apr 2006 04:20:56 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D23943D55 for ; Thu, 6 Apr 2006 04:20:55 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (knnb8mj9or7qfn55@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k364Krhe036616; Wed, 5 Apr 2006 21:20:53 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k364KqPj036615; Wed, 5 Apr 2006 21:20:52 -0700 (PDT) (envelope-from jmg) Date: Wed, 5 Apr 2006 21:20:52 -0700 From: John-Mark Gurney To: Oleg Rusanov Message-ID: <20060406042052.GO53811@funkthat.com> Mail-Followup-To: Oleg Rusanov , freebsd-amd64@freebsd.org References: <944389706.20060406075221@molecon.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <944389706.20060406075221@molecon.ru> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-amd64@freebsd.org Subject: Re: WCPU = 194.21% for mysqld X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 04:20:57 -0000 Oleg Rusanov wrote this message on Thu, Apr 06, 2006 at 07:52 +0400: > ????????????, . > > amd64# top > last pid: 1278; load averages: 1.93, 0.57, 0.21 up 0+00:03:30 00:31:40 > 86 processes: 3 running, 83 sleeping > CPU states: 97.9% user, 0.0% nice, 1.6% system, 0.5% interrupt, 0.0% idle > Mem: 270M Active, 959M Inact, 237M Wired, 7080K Cache, 214M Buf, 480M Free > Swap: 8192M Total, 8192M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 1102 mysql 4 20 0 323M 80084K kserel 0 1:55 194.21% mysqld > > > is this ok? Probably... run top w/ -H this will display the individual threads, it's that mysqld is running on multiple processors, so consuming more cpu cycles than a single cpu which is 100%... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 04:22:55 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FDE816A41F for ; Thu, 6 Apr 2006 04:22:55 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A51743D46 for ; Thu, 6 Apr 2006 04:22:54 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k364MrO8098468; Wed, 5 Apr 2006 22:22:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44349793.2060302@samsco.org> Date: Wed, 05 Apr 2006 22:22:43 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Oleg Rusanov References: <944389706.20060406075221@molecon.ru> In-Reply-To: <944389706.20060406075221@molecon.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: WCPU = 194.21% for mysqld 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, 06 Apr 2006 04:22:55 -0000 Oleg Rusanov wrote: > version=3.1.1 > X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org > > Çäðàâñòâóéòå, . > > amd64# top > last pid: 1278; load averages: 1.93, 0.57, 0.21 up 0+00:03:30 00:31:40 > 86 processes: 3 running, 83 sleeping > CPU states: 97.9% user, 0.0% nice, 1.6% system, 0.5% interrupt, 0.0% idle > Mem: 270M Active, 959M Inact, 237M Wired, 7080K Cache, 214M Buf, 480M Free > Swap: 8192M Total, 8192M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 1102 mysql 4 20 0 323M 80084K kserel 0 1:55 194.21% mysqld > > > is this ok? > WCPU is an aggregate of the time used on all CPUs. Since mysql is threaded, and since you are likely on an SMP system, you're seeing the cumulative effect of SMP. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 11:33:52 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 8F75F16A401 for ; Thu, 6 Apr 2006 11:33:52 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FC8C43D8A for ; Thu, 6 Apr 2006 11:33:36 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (cfqpsz@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k36BXUfR097809 for ; Thu, 6 Apr 2006 13:33:35 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k36BXTve097808; Thu, 6 Apr 2006 13:33:29 +0200 (CEST) (envelope-from olli) Date: Thu, 6 Apr 2006 13:33:29 +0200 (CEST) Message-Id: <200604061133.k36BXTve097808@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 06 Apr 2006 13:33:35 +0200 (CEST) Cc: Subject: Re: connection rate limitation for sshd - is it possible ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 11:33:52 -0000 This is off-topic (not amd64-related), and you hijacked another thread, but anyway ... xdavid@svinew.natur.cuni.cz wrote: > please, is there a way to limit the number of connections to openssh > daemon per time period per source ip address ? I am using this on linux > boxes with iptables, but couldn't figure out how to do this with IPF on > FreeBSD. If it is not possible, is there another way how to do this ? Or > do you think it is (un)wise to run sshd under inetd with "-C" switch or > "max-connections-per-ip-per-minute" parameter ? It is unwise, because sshd has to generate the server key each time it is started -- if started from inetd, that would be each time a client connection is accepted. Please read the description of the "-i" option in the sshd manpage. It explains it pretty well. Maybe using "MaxStartups" in your sshd_config would be a better solution (refer to the manpage for details). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 14:50:15 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 3034816A423 for ; Thu, 6 Apr 2006 14:50:15 +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 9919643D7D for ; Thu, 6 Apr 2006 14:50:12 +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 k36EoCAZ022378 for ; Thu, 6 Apr 2006 14:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k36EoC2g022377; Thu, 6 Apr 2006 14:50:12 GMT (envelope-from gnats) Resent-Date: Thu, 6 Apr 2006 14:50:12 GMT Resent-Message-Id: <200604061450.k36EoC2g022377@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, Armin Mohring Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2F8116A400 for ; Thu, 6 Apr 2006 14:43:32 +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 6392A43D76 for ; Thu, 6 Apr 2006 14:43:32 +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 k36EhVE6018616 for ; Thu, 6 Apr 2006 14:43:31 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k36EhVsF018615; Thu, 6 Apr 2006 14:43:31 GMT (envelope-from nobody) Message-Id: <200604061443.k36EhVsF018615@www.freebsd.org> Date: Thu, 6 Apr 2006 14:43:31 GMT From: Armin Mohring To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/95414: kernel crashes during install 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, 06 Apr 2006 14:50:15 -0000 >Number: 95414 >Category: amd64 >Synopsis: kernel crashes during install >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 06 14:50:10 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Armin Mohring >Release: 5.4 and 6.0 >Organization: >Environment: AMD Athlon 64 X86_64 >Description: 1. Using the disc1 of the 2 cd set (availaible for download). 2. choosing boot freebsd 3. kernel hangs at initialising floppy drive (no dma) 4. kernel hangs at initialising OHCI USB. 5. no dump - reboot in 15 seconds >How-To-Repeat: every time I want to install freebsd. >Fix: ? >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 6 19:09: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 BEC5B16A4FD for ; Thu, 6 Apr 2006 19:09: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 9B4DB43FF1 for ; Thu, 6 Apr 2006 15:40:16 +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 k36FeGEA025348 for ; Thu, 6 Apr 2006 15:40:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k36FeGPp025347; Thu, 6 Apr 2006 15:40:16 GMT (envelope-from gnats) Resent-Date: Thu, 6 Apr 2006 15:40:16 GMT Resent-Message-Id: <200604061540.k36FeGPp025347@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, Pavel Merdin Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DDCE16A400 for ; Thu, 6 Apr 2006 15:31:28 +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 61A2543D9A for ; Thu, 6 Apr 2006 15:31:08 +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 k36FV8hH031555 for ; Thu, 6 Apr 2006 15:31:08 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k36FV8kZ031554; Thu, 6 Apr 2006 15:31:08 GMT (envelope-from nobody) Message-Id: <200604061531.k36FV8kZ031554@www.freebsd.org> Date: Thu, 6 Apr 2006 15:31:08 GMT From: Pavel Merdin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/95418: pthread segmentation fault 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, 06 Apr 2006 19:09:49 -0000 >Number: 95418 >Category: amd64 >Synopsis: pthread segmentation fault >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 06 15:40:15 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Pavel Merdin >Release: FreeBSD 6-stable >Organization: Fotki Inc. >Environment: 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #6: Fri Feb 17 12:47:19 EST 2006 >Description: The pthread library forces mysql 4.1.18-log to crash with a message like: Feb 19 14:26:00 kernel: pid 33539 (mysqld), uid 1001: exited on signal 11 It happens when mysql is heavily used. Seems like compiler bug as AX register cannot normally be equal to 218 at 0x800d13aff. gdb dump: Program received signal SIGSEGV, Segmentation fault. 0x0000000800d13aff in _thr_gc (curthread=0x925000) at /usr/src/lib/libpthread/thread/thr_kern.c:1343 1343 TAILQ_INSERT_HEAD(&worklist, kseg, kg_qe); Current language: auto; currently c No locals. (gdb) x/30i 0x0000000800d13a50 0x800d13a50 <_thr_gc+1296>: out %eax,$0xe8 0x800d13a52 <_thr_gc+1298>: jle 0x800d13a1c <_thr_gc+1244> 0x800d13a54 <_thr_gc+1300>: (bad) 0x800d13a55 <_thr_gc+1301>: decl 0x64(%rbx,%rcx,4) 0x800d13a59 <_thr_gc+1305>: and $0x10,%al 0x800d13a5b <_thr_gc+1307>: test %r12,%r12 0x800d13a5e <_thr_gc+1310>: jne 0x800d139f1 <_thr_gc+1201> 0x800d13a60 <_thr_gc+1312>: mov 1092225(%rip),%rsi # 0x800e1e4e8 <_thread_list+12472> 0x800d13a67 <_thr_gc+1319>: mov (%rsi),%eax 0x800d13a69 <_thr_gc+1321>: test %eax,%eax 0x800d13a6b <_thr_gc+1323>: jle 0x800d13c3a <_thr_gc+1786> 0x800d13a71 <_thr_gc+1329>: cmpl $0x64,1092504(%rip) # 0x800e1e610 <_thread_off_tcb+184> 0x800d13a78 <_thr_gc+1336>: jle 0x800d13bf3 <_thr_gc+1715> 0x800d13a7e <_thr_gc+1342>: callq 0x800d0fd80 <_kse_critical_enter> 0x800d13a83 <_thr_gc+1347>: mov 0x180(%r13),%rdx 0x800d13a8a <_thr_gc+1354>: mov %rax,%rbp 0x800d13a8d <_thr_gc+1357>: mov 0x130(%rdx),%eax 0x800d13a93 <_thr_gc+1363>: cmp $0x4,%eax 0x800d13a96 <_thr_gc+1366>: jg 0x800d13c00 <_thr_gc+1728> 0x800d13a9c <_thr_gc+1372>: inc %eax 0x800d13a9e <_thr_gc+1374>: lea 1092571(%rip),%rdi # 0x800e1e680 <_thread_off_tcb+296> 0x800d13aa5 <_thr_gc+1381>: mov %eax,0x130(%rdx) 0x800d13aab <_thr_gc+1387>: mov 0x180(%r13),%rax 0x800d13ab2 <_thr_gc+1394>: xor %edx,%edx 0x800d13ab4 <_thr_gc+1396>: movslq 0x130(%rax),%rsi 0x800d13abb <_thr_gc+1403>: lea (%rsi,%rsi,4),%rsi 0x800d13abf <_thr_gc+1407>: lea 0x40(%rax,%rsi,8),%rsi 0x800d13ac4 <_thr_gc+1412>: callq 0x800d19830 <_lock_acquire> 0x800d13ac9 <_thr_gc+1417>: mov 1092120(%rip),%rsi # 0x800e1e4e8 <_thread_list+12472> 0x800d13ad0 <_thr_gc+1424>: mov %rsp,%rcx (gdb) x/25i 0x800d13ad3 <_thr_gc+1427>: jmp 0x800d13b0b <_thr_gc+1483> 0x800d13ad5 <_thr_gc+1429>: mov 0x28(%rbx),%rax 0x800d13ad9 <_thr_gc+1433>: mov %rax,0x28(%rdx) 0x800d13add <_thr_gc+1437>: mov 0x28(%rbx),%rax 0x800d13ae1 <_thr_gc+1441>: mov %rdx,(%rax) 0x800d13ae4 <_thr_gc+1444>: mov (%rsp),%rdx 0x800d13ae8 <_thr_gc+1448>: decl 1092386(%rip) # 0x800e1e610 <_thread_off_tcb+184> 0x800d13aee <_thr_gc+1454>: test %rdx,%rdx 0x800d13af1 <_thr_gc+1457>: mov %rdx,0x20(%rbx) 0x800d13af5 <_thr_gc+1461>: je 0x800d13b53 <_thr_gc+1555> 0x800d13af7 <_thr_gc+1463>: mov (%rsp),%rax 0x800d13afb <_thr_gc+1467>: lea 0x20(%rbx),%rdx 0x800d13aff <_thr_gc+1471>: mov %rdx,0x28(%rax) 0x800d13b03 <_thr_gc+1475>: mov %rbx,(%rsp) 0x800d13b07 <_thr_gc+1479>: mov %rcx,0x28(%rbx) 0x800d13b0b <_thr_gc+1483>: mov (%rsi),%eax 0x800d13b0d <_thr_gc+1485>: test %eax,%eax 0x800d13b0f <_thr_gc+1487>: jle 0x800d13b60 <_thr_gc+1568> 0x800d13b11 <_thr_gc+1489>: cmpl $0x64,1092344(%rip) # 0x800e1e610 <_thread_off_tcb+184> 0x800d13b18 <_thr_gc+1496>: jle 0x800d13b69 <_thr_gc+1577> 0x800d13b1a <_thr_gc+1498>: mov 1092383(%rip),%rbx # 0x800e1e640 <_thread_off_tcb+232> 0x800d13b21 <_thr_gc+1505>: mov 0x20(%rbx),%rdx 0x800d13b25 <_thr_gc+1509>: test %rdx,%rdx 0x800d13b28 <_thr_gc+1512>: jne 0x800d13ad5 <_thr_gc+1429> 0x800d13b2a <_thr_gc+1514>: mov 0x28(%rbx),%rax (gdb) info registers rax 0xd8 216 rbx 0x709adf00 1889197824 rcx 0x7fffffffe700 140737488348928 rdx 0x709adf20 1889197856 rsi 0x800e1eb30 34374544176 rdi 0x800e1e680 34374542976 rbp 0x8008ac060 0x8008ac060 rsp 0x7fffffffe700 0x7fffffffe700 r8 0x0 0 r9 0x1 1 r10 0x7fffff12ffd8 140737472823256 r11 0x1000 4096 r12 0x0 0 r13 0x925000 9588736 r14 0x7fffffffe720 140737488348960 r15 0x23 35 rip 0x800d13aff 0x800d13aff <_thr_gc+1471> eflags 0x10206 66054 cs 0x2b 43 ss 0x23 35 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 >How-To-Repeat: Try to load mysql with queries and many connections. I used a real application under heavy load. >Fix: Recompiling pthread without -O2 fixes the issue. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 06:06:16 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 8ECDA16A400 for ; Fri, 7 Apr 2006 06:06:16 +0000 (UTC) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (217-19-20-65.dsl.cambrium.nl [217.19.20.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FFA743D45 for ; Fri, 7 Apr 2006 06:06:15 +0000 (GMT) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (localhost [127.0.0.1]) by gandalf.cyberwizards.nl (8.13.4/8.13.4) with ESMTP id k3766B3G023233 for ; Fri, 7 Apr 2006 08:06:11 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) Received: from localhost (pbm@localhost) by gandalf.cyberwizards.nl (8.13.4/8.13.4/Submit) with ESMTP id k3766AmU023230 for ; Fri, 7 Apr 2006 08:06:11 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) X-Authentication-Warning: gandalf.cyberwizards.nl: pbm owned process doing -bs Date: Fri, 7 Apr 2006 08:06:10 +0200 (CEST) From: patrick X-X-Sender: pbm@gandalf.cyberwizards.nl To: freebsd-amd64@freebsd.org Message-ID: <20060407075301.I21526@gandalf.cyberwizards.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 06:06:16 -0000 Hello, Hope someone can shine a light for me on this, I have several boxes running STABLE 4/5/6 one of them is amd64/stable6 on dual opterons. I notice that on this amd system the httpd 2.2 and perl 5.8.8 binairies alocateds a lot of memory: 76562 www 1 20 0 156M 38528K lockf 0 0:00 0.00% httpd 76561 www 1 20 0 156M 38528K lockf 0 0:00 0.00% httpd 76830 www 1 20 0 155M 37740K lockf 0 0:00 0.00% httpd 76560 www 1 20 0 155M 37736K lockf 0 0:00 0.00% httpd 76563 www 1 4 0 155M 37736K kqread 0 0:00 0.00% httpd 61338 root 1 8 0 155M 37668K nanslp 0 0:02 0.00% httpd 73328 root 1 8 0 142M 102M nanslp 0 0:03 0.00% perl5.8.8 73611 root 1 8 0 142M 101M nanslp 0 0:03 0.00% perl5.8.8 75475 root 1 8 0 142M 99M nanslp 0 0:02 0.00% perl5.8.8 76966 root 1 8 0 142M 99M nanslp 0 0:02 0.00% perl5.8.8 75736 root 1 8 0 142M 101M nanslp 0 0:02 0.00% perl5.8.8 The binairy self has normal size: ~$ ls -lah /usr/local/sbin/httpd -rwxr-xr-x 1 root wheel 510K Apr 6 22:46 /usr/local/sbin/httpd ~$ ls -lah /usr/local/bin/perl5.8.8 -rwxr-xr-x 2 root wheel 12K Mar 4 09:48 /usr/local/bin/perl5.8.8 on the other systems (all i386 archs) the allocation for these binairies is a lot nomalizer, think about 52440K / 41492K : 26322 root 2 0 52440K 50040K poll 0:19 0.00% 0.00% perl5.8 26296 root 2 0 52340K 49964K poll 0:20 0.00% 0.00% perl5.8 26411 root 2 0 52328K 50024K poll 0:25 0.00% 0.00% perl5.8 69338 www 18 0 41492K 35560K lockf 2:00 0.00% 0.00% httpd 69387 www 18 0 29856K 23992K lockf 1:48 0.00% 0.00% httpd 69376 www 18 0 29816K 23940K lockf 1:49 0.00% 0.00% httpd Stripping the configs so that there is almost nothing in there , the allocated mem size still remains 150Mbs.. The only big diff in this case is the AMD64 arch. The packages are default builds from port. Anyone any ideas ? Thanks in advanced. patrick -- From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 07:25: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 5D49316A402 for ; Fri, 7 Apr 2006 07:25:14 +0000 (UTC) (envelope-from freebsd@rtl.fmailbox.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 049F643D45 for ; Fri, 7 Apr 2006 07:25:13 +0000 (GMT) (envelope-from freebsd@rtl.fmailbox.com) Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 31E2BD47714; Fri, 7 Apr 2006 03:25:12 -0400 (EDT) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Fri, 07 Apr 2006 03:24:59 -0400 X-Sasl-enc: TGuSonhhs8ksh4K0E3YGGW0lsV6uZJk+wInNG+uiuT5P 1144394698 Received: from [192.168.1.51] (CWPP-p-144-134-229-39.prem.tmns.net.au [144.134.229.39]) by frontend3.messagingengine.com (Postfix) with ESMTP id 284AC30F0; Fri, 7 Apr 2006 03:24:54 -0400 (EDT) Message-ID: <443613D0.80801@rtl.fmailbox.com> Date: Fri, 07 Apr 2006 17:25:04 +1000 From: Robert Leftwich User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: patrick References: <20060407075301.I21526@gandalf.cyberwizards.nl> In-Reply-To: <20060407075301.I21526@gandalf.cyberwizards.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 07:25:14 -0000 patrick wrote: > > Hope someone can shine a light for me on this, Sorry, I can't do a lot more than 'me too' I reported similar issues on an asus a8n-sli with dual athlon's running STABLE 6 some time back w/o anyone being able to shed light on it. Do you have the ability to run the latest 6.1 beta? If so, and your experience is like mine, the problem goes away. I'm running the exact same setup on 6.1b4 as I was on 6 stable and I don't see anywhere near the same amount of mem usage as I did before - in fact I've been able to triple some of my Postgres buffer settings with the 4G of ram not even 1/2 fully utilised. I saw very similar memory sizes with httpd as you reported before I switched to lighttpd (which interestingly did not have the same problem on STABLE 6 - always using around 17M) but some Python processes I was running regularly maxed out at over 1.4G, now it's down in the 400M range doing the same processing on significantly more data. HTH Robert From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 08:16: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 2025416A401 for ; Fri, 7 Apr 2006 08:16:30 +0000 (UTC) (envelope-from patrick@barmentlo.nl) Received: from gandalf.cyberwizards.nl (217-19-20-65.dsl.cambrium.nl [217.19.20.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7627143D4C for ; Fri, 7 Apr 2006 08:16:28 +0000 (GMT) (envelope-from patrick@barmentlo.nl) Received: from gandalf.cyberwizards.nl (localhost [127.0.0.1]) by gandalf.cyberwizards.nl (8.13.4/8.13.4) with ESMTP id k378GNnv028479; Fri, 7 Apr 2006 10:16:23 +0200 (CEST) (envelope-from patrick@barmentlo.nl) Received: from localhost (pbm@localhost) by gandalf.cyberwizards.nl (8.13.4/8.13.4/Submit) with ESMTP id k378GMkF028476; Fri, 7 Apr 2006 10:16:23 +0200 (CEST) (envelope-from patrick@barmentlo.nl) X-Authentication-Warning: gandalf.cyberwizards.nl: pbm owned process doing -bs Date: Fri, 7 Apr 2006 10:16:22 +0200 (CEST) From: patrick X-X-Sender: pbm@gandalf.cyberwizards.nl To: Robert Leftwich In-Reply-To: <443613D0.80801@rtl.fmailbox.com> Message-ID: <20060407101400.R28178@gandalf.cyberwizards.nl> References: <20060407075301.I21526@gandalf.cyberwizards.nl> <443613D0.80801@rtl.fmailbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 08:16:30 -0000 On Fri, 7 Apr 2006, Robert Leftwich wrote: Thanks for your reply, starting to get real concerned now. we are on the moment of migration and taking this server life.. thinking what is wise.. Even consuring to 'downgrade' to 1386 at this moment. it this do-able on this amd system, a build world , would i be able to do a install world/kernels without crashing on the way??? Regards, Patrick >> Hope someone can shine a light for me on this, > > Sorry, I can't do a lot more than 'me too' > > I reported similar issues on an asus a8n-sli with dual athlon's running > STABLE 6 some time back w/o anyone being able to shed light on it. > > Do you have the ability to run the latest 6.1 beta? If so, and your > experience is like mine, the problem goes away. I'm running the exact same > setup on 6.1b4 as I was on 6 stable and I don't see anywhere near the same > amount of mem usage as I did before - in fact I've been able to triple some > of my Postgres buffer settings with the 4G of ram not even 1/2 fully > utilised. > > I saw very similar memory sizes with httpd as you reported before I switched > to lighttpd (which interestingly did not have the same problem on STABLE 6 - > always using around 17M) but some Python processes I was running regularly > maxed out at over 1.4G, now it's down in the 400M range doing the same > processing on significantly more data. > > HTH > > Robert > From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 08:23:23 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 2166E16A406 for ; Fri, 7 Apr 2006 08:23:23 +0000 (UTC) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (217-19-20-65.dsl.cambrium.nl [217.19.20.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F06543D58 for ; Fri, 7 Apr 2006 08:23:22 +0000 (GMT) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (localhost [127.0.0.1]) by gandalf.cyberwizards.nl (8.13.4/8.13.4) with ESMTP id k378NI52028750; Fri, 7 Apr 2006 10:23:18 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) Received: from localhost (pbm@localhost) by gandalf.cyberwizards.nl (8.13.4/8.13.4/Submit) with ESMTP id k378NIgd028747; Fri, 7 Apr 2006 10:23:18 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) X-Authentication-Warning: gandalf.cyberwizards.nl: pbm owned process doing -bs Date: Fri, 7 Apr 2006 10:23:17 +0200 (CEST) From: patrick@cyberwizards.nl X-X-Sender: pbm@gandalf.cyberwizards.nl To: Robert Leftwich In-Reply-To: <443613D0.80801@rtl.fmailbox.com> Message-ID: <20060407102130.R28667@gandalf.cyberwizards.nl> References: <20060407075301.I21526@gandalf.cyberwizards.nl> <443613D0.80801@rtl.fmailbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 08:23:23 -0000 On Fri, 7 Apr 2006, Robert Leftwich wrote: I found out that without php the mem usages is more or less normaal. no diffs for php4/5 (same big mem usage) ;-( >> Hope someone can shine a light for me on this, > > Sorry, I can't do a lot more than 'me too' > > I reported similar issues on an asus a8n-sli with dual athlon's running > STABLE 6 some time back w/o anyone being able to shed light on it. > > Do you have the ability to run the latest 6.1 beta? If so, and your > experience is like mine, the problem goes away. I'm running the exact same > setup on 6.1b4 as I was on 6 stable and I don't see anywhere near the same > amount of mem usage as I did before - in fact I've been able to triple some > of my Postgres buffer settings with the 4G of ram not even 1/2 fully > utilised. > > I saw very similar memory sizes with httpd as you reported before I switched > to lighttpd (which interestingly did not have the same problem on STABLE 6 - > always using around 17M) but some Python processes I was running regularly > maxed out at over 1.4G, now it's down in the 400M range doing the same > processing on significantly more data. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 08:39:43 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A46B16A406 for ; Fri, 7 Apr 2006 08:39:43 +0000 (UTC) (envelope-from freebsd@rtl.fmailbox.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 873B743D5A for ; Fri, 7 Apr 2006 08:39:36 +0000 (GMT) (envelope-from freebsd@rtl.fmailbox.com) Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id A34A4D46FD4; Fri, 7 Apr 2006 04:39:35 -0400 (EDT) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Fri, 07 Apr 2006 04:39:22 -0400 X-Sasl-enc: ONwcmmTTN8X1yZtQIySJB60PPU4Dro9valriOPLW7syp 1144399159 Received: from [192.168.1.51] (CWPP-p-144-134-229-39.prem.tmns.net.au [144.134.229.39]) by frontend3.messagingengine.com (Postfix) with ESMTP id 700D5311A; Fri, 7 Apr 2006 04:39:16 -0400 (EDT) Message-ID: <4436253F.9080000@rtl.fmailbox.com> Date: Fri, 07 Apr 2006 18:39:27 +1000 From: Robert Leftwich User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: patrick References: <20060407075301.I21526@gandalf.cyberwizards.nl> <443613D0.80801@rtl.fmailbox.com> <20060407101400.R28178@gandalf.cyberwizards.nl> In-Reply-To: <20060407101400.R28178@gandalf.cyberwizards.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 08:39:43 -0000 patrick wrote: > > Even consuring to 'downgrade' to 1386 at this moment. I tried this approach as well, but i386 on that particular asus board with 4G was ram not usable, it wouldn't even complete the install. On another (not so recent?) m/b you might do better. > it this do-able on this amd system, a build world , would i be able to > do a install world/kernels without crashing on the way??? > Sorry, too much of a newbie to help here :-( > I found out that without php the mem usages is more or less normaal. > > no diffs for php4/5 (same big mem usage) > I never tried only having httpd installed and nothing else. Robert From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 09:43:35 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 6384916A402 for ; Fri, 7 Apr 2006 09:43:35 +0000 (UTC) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (217-19-20-65.dsl.cambrium.nl [217.19.20.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF3F343D45 for ; Fri, 7 Apr 2006 09:43:34 +0000 (GMT) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (localhost [127.0.0.1]) by gandalf.cyberwizards.nl (8.13.4/8.13.4) with ESMTP id k379hU4p031924 for ; Fri, 7 Apr 2006 11:43:30 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) Received: from localhost (pbm@localhost) by gandalf.cyberwizards.nl (8.13.4/8.13.4/Submit) with ESMTP id k379hTXx031921 for ; Fri, 7 Apr 2006 11:43:29 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) X-Authentication-Warning: gandalf.cyberwizards.nl: pbm owned process doing -bs Date: Fri, 7 Apr 2006 11:43:29 +0200 (CEST) From: patrick X-X-Sender: pbm@gandalf.cyberwizards.nl To: freebsd-amd64@freebsd.org Message-ID: <20060407114033.J30882@gandalf.cyberwizards.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: safe way to build i386 arch makeworld on amd64 arch? 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, 07 Apr 2006 09:43:35 -0000 hello list, is there a save way to 'downgrade' an amd64 build system by using 'make world' ? e.g. just remove the CPUTYPE=opteron from the make.conf file and do a build world/kernels install world/kernels ? of do we need to do some more for this? thanks in advance Regards patrick From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 09:54:53 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 3DD2E16A402 for ; Fri, 7 Apr 2006 09:54:53 +0000 (UTC) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from svinew.natur.cuni.cz (svinew.natur.cuni.cz [195.113.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81EC943D48 for ; Fri, 7 Apr 2006 09:54:52 +0000 (GMT) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from svinew.natur.cuni.cz (svinew.natur.cuni.cz [127.0.0.1]) by svinew.natur.cuni.cz (8.13.1/8.13.1) with ESMTP id k379sjkT022815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 7 Apr 2006 11:54:50 +0200 Received: from localhost (xdavid@localhost) by svinew.natur.cuni.cz (8.13.1/8.13.1/Submit) with ESMTP id k379sjCI022812 for ; Fri, 7 Apr 2006 11:54:45 +0200 Date: Fri, 7 Apr 2006 11:54:45 +0200 (CEST) From: xdavid@lib-eth.natur.cuni.cz To: freebsd-amd64@freebsd.org In-Reply-To: <200604061133.k36BXTve097808@lurza.secnetix.de> Message-ID: References: <200604061133.k36BXTve097808@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: connection rate limitation for sshd - is it possible ? 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, 07 Apr 2006 09:54:53 -0000 > This is off-topic (not amd64-related), > and you hijacked another thread, but anyway ... The original question was how to set sthg with IPF on my AMD64 box, so I thought it is amd64-related, sorry for my missunderstanding of the purpose of this list. > > please, is there a way to limit the number of connections to openssh > > daemon per time period per source ip address ? I am using this on linux > > boxes with iptables, but couldn't figure out how to do this with IPF on > > FreeBSD. If it is not possible, is there another way how to do this ? Or > > do you think it is (un)wise to run sshd under inetd with "-C" switch or > > "max-connections-per-ip-per-minute" parameter ? > > It is unwise, because sshd has to generate the server key > each time it is started -- if started from inetd, that > would be each time a client connection is accepted. Thank you for giving me good reasons not to do it. > Maybe using "MaxStartups" in your sshd_config would be a > better solution (refer to the manpage for details). The problem is it does not track source IPs so there is a DOS risk. I got another advice how to set up PF, so I'll play with, but as the short term solution I probably use inetd while there are only a few people using sshd on that machine now and more users will be added later. Best Regards, David From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 11:00:37 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 CFB8F16A401 for ; Fri, 7 Apr 2006 11:00:37 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6575143D45 for ; Fri, 7 Apr 2006 11:00:37 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FRohf-000B4K-BW; Fri, 07 Apr 2006 14:00:35 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: patrick In-Reply-To: Message from patrick of "Fri, 07 Apr 2006 11:43:29 +0200." <20060407114033.J30882@gandalf.cyberwizards.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Apr 2006 14:00:35 +0300 From: Danny Braniss Message-ID: Cc: freebsd-amd64@freebsd.org Subject: Re: safe way to build i386 arch makeworld on amd64 arch? 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, 07 Apr 2006 11:00:37 -0000 > hello list, > > is there a save way to 'downgrade' an amd64 build system by using 'make world' ? > > e.g. just remove the CPUTYPE=opteron from the make.conf file and do a > build world/kernels install world/kernels ? > > of do we need to do some more for this? > > thanks in advance > > Regards > patrick > you can, i do: export MAKEOBJDIRPREFIX=/somwhersafe-i386 make TARGET_ARCH=i386 buildworld same for buildkernel, installworld/installkernel, and also you can specify a different DESTDIR= danny > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 13:28:31 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 9790B16A407 for ; Fri, 7 Apr 2006 13:28:31 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9328E43D4C for ; Fri, 7 Apr 2006 13:28:30 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so284767nfc for ; Fri, 07 Apr 2006 06:28:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rr6rlq0hAKooj3fWUEA9VaaxQ3KXdwnZld3QHWIiZsH/hLSaK1zVUmorzbHmwClzT4XQK/wtJOv5V3+3xLyd1DK27BzpQGHvikEgrM6/tCT4zsGcaJVk6qT7/QZF5CFo+n5Ojw1IMSsP4tKSSeiQsSLLaOvZmGjrdfumU8AkXA0= Received: by 10.48.243.6 with SMTP id q6mr1411130nfh; Fri, 07 Apr 2006 06:28:26 -0700 (PDT) Received: by 10.49.38.1 with HTTP; Fri, 7 Apr 2006 06:28:26 -0700 (PDT) Message-ID: <2fd864e0604070628m64ecf142gb7dc314721510835@mail.gmail.com> Date: Fri, 7 Apr 2006 21:28:26 +0800 From: Astrodog To: "Robert Leftwich" In-Reply-To: <4436253F.9080000@rtl.fmailbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060407075301.I21526@gandalf.cyberwizards.nl> <443613D0.80801@rtl.fmailbox.com> <20060407101400.R28178@gandalf.cyberwizards.nl> <4436253F.9080000@rtl.fmailbox.com> Cc: patrick , freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 13:28:31 -0000 > > Even consuring to 'downgrade' to 1386 at this moment. I suppose that would work. > > it this do-able on this amd system, a build world , would i be able to > > do a install world/kernels without crashing on the way??? Not really. > > I found out that without php the mem usages is more or less normaal. > > no diffs for php4/5 (same big mem usage) Alright... Please consider what AMD64 is, exactly, and what it means for something to be 64-bit, as opposed to 32-bit. On a 32 bit processor, all ints, and pointers take up 32 bits of memory. So, for every int, and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and pointers take up 64-bits of memory. So, for every int and pointer, you use 8 bytes. (Assuming its a 64-bit app, of course) That means applications that use a whole lot of ints, and pointers will use way more memory on AMD64, than they will on i386. Here's an example: int main() { int a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z; void *aa, *bb, *cc; return 0; } it will use 104 bytes of memory for ints, and 12 bytes of memory for pointers, on i386. However, on AMD64, the same program will use 208 bytes of memory for ints, and 24 bytes for pointers. This memory usage is significantly compounded in some complex apps. (Yes, PHP is complex) Now that above is the BEST CASE scenario. If an application isn't well written for 64-bit, things can get pretty nasty too. To make up for this memory gobbling, the processor does get to access more information at a time, too, so it all kinda evens out performance-wise. If you have >=3D 4GB of memory though, the pain-in-the-ass-ness of PAE, and how badly it breaks things, makes 64 bit the only choice, for those of us who don't have a thing for pain. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 13:38: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 6B80B16A401 for ; Fri, 7 Apr 2006 13:38:21 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 710AD43D49 for ; Fri, 7 Apr 2006 13:38:20 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so286521nfc for ; Fri, 07 Apr 2006 06:38:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EkVXeYXxsaFsJEcppWQGHqtyH99NKMn/uYkPVPYyIKfOFYGbidOH29PkCMF2KNKT7yCDoRSQL+bqPwyFH5kkEntYEFMVJXcPa2cQzh/y8/yD9AuTtJvhimxlF7EoZCIho0JblDxji2rpyfi/pHbx4ZdCHKIp7T2HLrThKUbTG30= Received: by 10.49.18.15 with SMTP id v15mr1541397nfi; Fri, 07 Apr 2006 06:38:19 -0700 (PDT) Received: by 10.49.38.1 with HTTP; Fri, 7 Apr 2006 06:38:19 -0700 (PDT) Message-ID: <2fd864e0604070638n11ff30f1pa9ad3fe5ac669ea7@mail.gmail.com> Date: Fri, 7 Apr 2006 21:38:19 +0800 From: Astrodog To: "Danny Braniss" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060407114033.J30882@gandalf.cyberwizards.nl> Cc: freebsd-amd64@freebsd.org Subject: Re: safe way to build i386 arch makeworld on amd64 arch? 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, 07 Apr 2006 13:38:21 -0000 On 4/7/06, Danny Braniss wrote: > > hello list, > > > > is there a save way to 'downgrade' an amd64 build system by using 'make= world' ? > > > > e.g. just remove the CPUTYPE=3Dopteron from the make.conf file and do a > > build world/kernels install world/kernels ? > > > > of do we need to do some more for this? > > > > thanks in advance > > > > Regards > > patrick > > To downgrade? Not realistically. > you can, i do: > export MAKEOBJDIRPREFIX=3D/somwhersafe-i386 > make TARGET_ARCH=3Di386 buildworld > same for buildkernel, installworld/installkernel, and also you can specif= y > a different DESTDIR=3D > > danny > That would certainly allow him to crosscompile an i386 kernel, and world, but wouldn't have much effect on downgrading from AMD64 to i386, since you run into a chicken or the egg problem with the kernel, and world. (a 64-bit kernel does not play nice on a 32-bit world, without some hacking around, and a 32-bit kernel does not play nice on a 64-bit world), which makes it impossible to actually do both steps. If you install the 32-bit kernel first, and reboot, the kernel won't be able to run the 64-bit binaries. If you install the 32-bit world first, the 64-bit kernel will become very, very sad, and won't let the installation complete. If you try to install the kernel, then the world without a reboot, you have the same problem as installing the 32-bit world first, since even with a 32-bit kernel installed, you're still RUNNING the 64-bit kernel until you reboot. There are actually ways to do this, but its almost always a bad idea. Not to mention this will break any packages, or ports you're using too, with the exception, perhaps, of Linux Compat. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 14:26:39 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 817D216A404 for ; Fri, 7 Apr 2006 14:26:39 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4477143D68 for ; Fri, 7 Apr 2006 14:26:36 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qfmhmd@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k37EQSsa056989 for ; Fri, 7 Apr 2006 16:26:34 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k37EQSKF056988; Fri, 7 Apr 2006 16:26:28 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Apr 2006 16:26:28 +0200 (CEST) Message-Id: <200604071426.k37EQSKF056988@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 07 Apr 2006 16:26:34 +0200 (CEST) Cc: Subject: Re: connection rate limitation for sshd - is it possible ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 14:26:39 -0000 xdavid@svinew.natur.cuni.cz wrote: > The original question was how to set sthg with IPF on my AMD64 box, so I > thought it is amd64-related, sorry for my missunderstanding of the purpose > of this list. It is my understanding that this list is for amd64-specific things. IPF and ssh are not amd64-specific. > > It is unwise, because sshd has to generate the server key > > each time it is started -- if started from inetd, that > > would be each time a client connection is accepted. > > Thank you for giving me good reasons not to do it. Hm. I might have been mistaken (I'm sorry for that). If I recall correctly, the server key is only required for SSH protocol version 1. Version 2 doesn't generate a server key at all, but uses Diffie-Hellman for a shared session key. Therefore, if you limit your sshd to protocol 2 _only_, then doesn't have to generate a server key each time it starts, and running it via inetd might be feasible. I have not actually tried that, so I might be wrong. > > Maybe using "MaxStartups" in your sshd_config would be a > > better solution (refer to the manpage for details). > > The problem is it does not track source IPs so there is a DOS risk. Unfortunately, it's not that easy. It depends what kind of DoS attack you would like to prevent. Someone who has sufficient bandwidth can always flood your link, no matter whether your packet filter drops the stuff or not. So you cannot prevent that kind of DoS attack at all. However, the packet filter will prevent those packets from reaching the daemon program (sshd, in this case). Whether that has any significant effect depends on the software. In the case of sshd, creating the session key is probably not neglegible. And that has to happen before the client authenticates, i.e. no matter whether it can successfully log in or not. But: If you try to solve the problem on packet filter level (i.e. with IPFW, IPF or PF) by limiting the "setup" packets per source IP, it is very easy to run a DoS attack against you by simply sending a sufficient number of such SYN,!ACK packets with your own (spoofed) source IP. Then you're locked out. In fact, that kind of DoS is _very_ easy to perform. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 14:36: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 BF38816A401 for ; Fri, 7 Apr 2006 14:36:21 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CA8843D46 for ; Fri, 7 Apr 2006 14:36:20 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (nefezk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k37Ea931057748 for ; Fri, 7 Apr 2006 16:36:20 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k37Ea9mA057746; Fri, 7 Apr 2006 16:36:09 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Apr 2006 16:36:09 +0200 (CEST) Message-Id: <200604071436.k37Ea9mA057746@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <2fd864e0604070628m64ecf142gb7dc314721510835@mail.gmail.com> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 07 Apr 2006 16:36:20 +0200 (CEST) Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 14:36:21 -0000 Astrodog wrote: > Please consider what AMD64 is, exactly, and what it means for > something to be 64-bit, as opposed to 32-bit. On a 32 bit processor, > all ints, and pointers take up 32 bits of memory. So, for every int, > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > pointers take up 64-bits of memory. No. You're right with the pointers, but ints are always 4 bytes on both i386 and amd64. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 14:40:32 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E821C16A402 for ; Fri, 7 Apr 2006 14:40:32 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E82843D53 for ; Fri, 7 Apr 2006 14:40:31 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so298271nfc for ; Fri, 07 Apr 2006 07:40:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mxTsTcsxxVvLqqMwKFzPuyzG24fg9UA4HuQyKaJ2s+gYpI/XB8Qyj2/zD+uc2Czlo7/Yru/uoVnGlO3W1U/a5YierZeyXzAcVBXCT4/M/qGJlR3IRHku/XLxppwol0IYLDpZENmxvTFpjyzdMRrQL8EDwF5TaLyVBhoFnFu2+V8= Received: by 10.49.31.8 with SMTP id i8mr1564075nfj; Fri, 07 Apr 2006 07:40:30 -0700 (PDT) Received: by 10.49.38.1 with HTTP; Fri, 7 Apr 2006 07:40:30 -0700 (PDT) Message-ID: <2fd864e0604070740s59f12148lfda0b237a3e869aa@mail.gmail.com> Date: Fri, 7 Apr 2006 14:40:30 +0000 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <200604071436.k37Ea9mA057746@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2fd864e0604070628m64ecf142gb7dc314721510835@mail.gmail.com> <200604071436.k37Ea9mA057746@lurza.secnetix.de> Subject: Re: extreme mem usage under amd64 arch ? 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, 07 Apr 2006 14:40:33 -0000 On 4/7/06, Oliver Fromme wrote: > Astrodog wrote: > > Please consider what AMD64 is, exactly, and what it means for > > something to be 64-bit, as opposed to 32-bit. On a 32 bit processor, > > all ints, and pointers take up 32 bits of memory. So, for every int, > > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > > pointers take up 64-bits of memory. > > No. You're right with the pointers, but ints are always > 4 bytes on both i386 and amd64. > D'oh. Stupid i386, getting me used to sizeof(int) =3D=3D sizeof(*). I blame Intel. Projection is a wonderful thing, --- Harrison Grundy > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "A language that doesn't have everything is actually easier > to program in than some that do." > -- Dennis M. Ritchie > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 17:26: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 5066A16A402 for ; Fri, 7 Apr 2006 17:26:26 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4DA143D46 for ; Fri, 7 Apr 2006 17:26:25 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (r380rr9rjwth57ci@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k37HQJ6B087903; Fri, 7 Apr 2006 10:26:20 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k37HQI4K087902; Fri, 7 Apr 2006 10:26:18 -0700 (PDT) (envelope-from jmg) Date: Fri, 7 Apr 2006 10:26:18 -0700 From: John-Mark Gurney To: Astrodog Message-ID: <20060407172618.GC72485@funkthat.com> Mail-Followup-To: Astrodog , Robert Leftwich , patrick , freebsd-amd64@freebsd.org References: <20060407075301.I21526@gandalf.cyberwizards.nl> <443613D0.80801@rtl.fmailbox.com> <20060407101400.R28178@gandalf.cyberwizards.nl> <4436253F.9080000@rtl.fmailbox.com> <2fd864e0604070628m64ecf142gb7dc314721510835@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e0604070628m64ecf142gb7dc314721510835@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: patrick , freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 17:26:26 -0000 Astrodog wrote this message on Fri, Apr 07, 2006 at 21:28 +0800: > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > pointers take up 64-bits of memory. So, for every int and pointer, you > use 8 bytes. (Assuming its a 64-bit app, of course) That means Not quite... FreeBSD/amd64 like all? the other arches are LP64... that means longs and pointers are 64bits, while ints remain at 32bits... This was primarily done because too many people assumed ints were 32bits for things like disk structures and network protocol layout, and to break less code, LP64 was decided upon... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 21:16:40 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 4728216A401 for ; Fri, 7 Apr 2006 21:16:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AEB443D45 for ; Fri, 7 Apr 2006 21:16:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wdixgp@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k37LGWv5071638; Fri, 7 Apr 2006 23:16:37 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k37LGQhQ071637; Fri, 7 Apr 2006 23:16:26 +0200 (CEST) (envelope-from olli) Date: Fri, 7 Apr 2006 23:16:26 +0200 (CEST) Message-Id: <200604072116.k37LGQhQ071637@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, John-Mark Gurney In-Reply-To: <20060407172618.GC72485@funkthat.com> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 07 Apr 2006 23:16:38 +0200 (CEST) Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG, John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 21:16:40 -0000 John-Mark Gurney wrote: > Astrodog wrote this message on Fri, Apr 07, 2006 at 21:28 +0800: > > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > > pointers take up 64-bits of memory. So, for every int and pointer, you > > use 8 bytes. (Assuming its a 64-bit app, of course) That means > > Not quite... FreeBSD/amd64 like all? the other arches are LP64... > that means longs and pointers are 64bits, while ints remain at 32bits... I think longs are 32 bits on /i386, and 64 bits on /amd64 (On /i386, "long longs" are 64 bits.) A programmer should not rely on specific sizes of longs, ints etc. anyway. In particular, he should not assume that a long is larger than an int, that a pointer has the same size as an int or a long, and similar things. If a specific size is needed, then one of the standard types int64_t, int32_t etc. should be used which are defined appropriately by the OS. Or, or course, use a higher-level programming language where you don't have to care about integer sizes at all, such as Python ("print 999**999" will fill the screen nicely). ;-) > This was primarily done because too many people assumed ints were > 32bits for things like disk structures and network protocol layout, > and to break less code, LP64 was decided upon... I guess this is the most important reason: If ints were 64 bits, there would be no easy way to handle 32 bit entities. Not being able to handle 32 bit objects with a native data type whould be a major problem, especially for an OS kernel, I think. Best regards Oliver PS: The random quote in my signature below fits pretty well. It really is random, I swear. :-) -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C is quirky, flawed, and an enormous success." -- Dennis M. Ritchie. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 21:22:56 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 DF80716A400 for ; Fri, 7 Apr 2006 21:22:56 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7680A43D45 for ; Fri, 7 Apr 2006 21:22:56 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gzb087vwtpp8vcsh@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k37LMtAX093404 for ; Fri, 7 Apr 2006 14:22:55 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k37LMsAP093403 for freebsd-amd64@FreeBSD.ORG; Fri, 7 Apr 2006 14:22:54 -0700 (PDT) (envelope-from jmg) Date: Fri, 7 Apr 2006 14:22:54 -0700 From: John-Mark Gurney To: freebsd-amd64@FreeBSD.ORG Message-ID: <20060407212254.GE72485@funkthat.com> Mail-Followup-To: freebsd-amd64@FreeBSD.ORG References: <20060407172618.GC72485@funkthat.com> <200604072116.k37LGQhQ071637@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604072116.k37LGQhQ071637@lurza.secnetix.de> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 21:22:57 -0000 Oliver Fromme wrote this message on Fri, Apr 07, 2006 at 23:16 +0200: > John-Mark Gurney wrote: > > Astrodog wrote this message on Fri, Apr 07, 2006 at 21:28 +0800: > > > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > > > pointers take up 64-bits of memory. So, for every int and pointer, you > > > use 8 bytes. (Assuming its a 64-bit app, of course) That means > > > > Not quite... FreeBSD/amd64 like all? the other arches are LP64... > > that means longs and pointers are 64bits, while ints remain at 32bits... > > I think longs are 32 bits on /i386, and 64 bits on /amd64 > (On /i386, "long longs" are 64 bits.) Sorry, I ment to write like all the other 64bit arches.... ^^^^^ since i386 isn't 32bit, it isn't LP64, the same way arm or powerpc isn't LP64... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 7 22:04: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 7043E16A402 for ; Fri, 7 Apr 2006 22:04:01 +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 F3DB843D48 for ; Fri, 7 Apr 2006 22:04:00 +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 <0IXD000L9HAOM330@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 08 Apr 2006 00:04:00 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.172.162]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IXD008C8HANI2C0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 08 Apr 2006 00:04:00 +0200 (CEST) Date: Sat, 08 Apr 2006 00:03:59 +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 To: freebsd-amd64@freebsd.org Message-id: <20060408000359.2f829260.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.16; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Gigabyte K8-NF-9: FreeBSD hangs / freezes when I attach a firewire disk 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, 07 Apr 2006 22:04:01 -0000 Hi, I'm running FreeBSD / amd64 on a Gigabyte K8-NF-9 mainboard: FreeBSD 6.1-PRERELEASE #6: Fri Apr 7 23:19:06 CEST 2006 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL60 This board has the following firewire "stuff" inside: fwohci0: mem 0xf4004000-0xf40047ff,0xf4000000-0xf4003fff irq 18 at device 10.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:14:85:56:00:8a:69:c1 fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:14:85:8a:69:c1 fwe0: Ethernet address: 02:14:85:8a:69:c1 fwe0: if_start running deferred for Giant fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode fwohci0: phy int When FreeBSD is up, and I attach a (external) firewire disk, FreeBSD freezes or hangs. It is totally unresponsive, even the console. If I turn off / on the power to the firewire disk, nothing happens. If I keep firewire disk power on, and detach the firewire cable, the following message(s) appear on the console: fwochi0: BUS reset fwochi0: node_id=0xc800ffc0, gen=103, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager (me) fwohci0: phy int If I re-attach the firewire cable, nothing happens. If I detach the firewire cable after that, I get a new message as above, but with a different 'gen=' number. I have to remove the firewire cable and reset the machine to get it going again. If the firewire disk is attached when the machine boot, the boot hangs and never finishes (well, not for 15 mins at least). -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 05:02:11 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502B416A400 for ; Sat, 8 Apr 2006 05:02:11 +0000 (UTC) (envelope-from cdjones-freebsd-amd64@novusordo.net) Received: from correo.novusordo.net (cdjj.org [216.194.85.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id D611E43D46 for ; Sat, 8 Apr 2006 05:02:10 +0000 (GMT) (envelope-from cdjones-freebsd-amd64@novusordo.net) Received: from [192.168.2.100] (S010600c049bda6b5.ed.shawcable.net [68.149.198.157]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by correo.novusordo.net (Postfix) with ESMTP id 70FD511A40 for ; Fri, 7 Apr 2006 23:02:09 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <67611F0F-D849-46A8-BFBB-C1BE54C5F46E@novusordo.net> References: <67611F0F-D849-46A8-BFBB-C1BE54C5F46E@novusordo.net> Content-Type: multipart/mixed; boundary=Apple-Mail-3-809085739 Message-Id: From: Chris Jones Date: Fri, 7 Apr 2006 23:02:06 -0600 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.749.3) Subject: Re: amd64/94989: BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5.4-RELEASE (x86) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 05:02:11 -0000 --Apple-Mail-3-809085739 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On 28-Mar-06, at 2:43 AM, Chris Jones wrote: [... Sun Fire X2100 won't boot under FreeBSD etc.] Further update for the archives: FreeBSD 6.1-BETA4 is quite happy to do PXE booting and installation, and boots from the hard drive (dmesg attached). Sadly, even with the most recent BIOS (v. 1.09), booting from CD fails with the BTX halt. With that said, that's perfectly adequate for my purposes. Now, to burn it in and try it out.... Cheers, Chris --Apple-Mail-3-809085739 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="x2100.dmesg" Content-Disposition: attachment; filename=x2100.dmesg Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-BETA4 #0: Mon Mar 13 19:16:58 UTC 2006 root@x64.samsco.home:/usr/obj/usr/src/sys/SMP ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 146 (2010.31-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f71 Stepping = 1 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1072562176 (1022 MB) avail memory = 1023680512 (976 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered umass0: LaCie LaCie DVDRW USB, rev 2.00/0.00, addr 2 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe800-0xe80f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd400-0xd40f mem 0xfe02c000-0xfe02cfff irq 23 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc000-0xc00f mem 0xfe02b000-0xfe02bfff irq 21 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 9.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) nve0: port 0xbc00-0xbc07 mem 0xfe02a000-0xfe02afff irq 22 at device 10.0 on pci0 nve0: Ethernet address 00:e0:81:5a:1b:76 miibus0: on nve0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:e0:81:5a:1b:76 pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 bge0: mem 0xfdaf0000-0xfdafffff irq 19 at device 0.0 on pci4 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:5a:1b:77 pcib5: at device 14.0 on pci0 pci5: on pcib5 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xc7fff,0xca000-0xcb7ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: Darfon USB Combo Keyboard, rev 1.10/2.02, addr 2, iclass 3/1 kbd0 at ukbd0 uhid0: Darfon USB Combo Keyboard, rev 1.10/2.02, addr 2, iclass 3/1 Timecounter "TSC" frequency 2010312422 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff805fae00, 0) error 6 ad4: 239372MB at ata2-master SATA300 ad6: 239372MB at ata3-master SATA300 ar0: 239372MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Incompatible medium installed Trying to mount root from ufs:/dev/ad4s1a --Apple-Mail-3-809085739-- From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 05:36:17 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24D3D16A400 for ; Sat, 8 Apr 2006 05:36:17 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B86943D53 for ; Sat, 8 Apr 2006 05:36:16 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so400412nfc for ; Fri, 07 Apr 2006 22:36:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=psNoKGAnO0adp6EXgwG38OFsuvrpOXHKfdfopVbOoCQiRBveiZQsSXt4GfSL7KiUh8AUVQLUqeArqoOiiLfeZ94LpOxV5jai9LFh9ILcmTvSrZEDuseYc2eRBKY5Lorcvvom14rO64pFdbgGPPz7duzHi222sei/X8zH99y3v40= Received: by 10.49.18.15 with SMTP id v15mr2268093nfi; Fri, 07 Apr 2006 22:36:15 -0700 (PDT) Received: by 10.49.38.1 with HTTP; Fri, 7 Apr 2006 22:36:15 -0700 (PDT) Message-ID: <2fd864e0604072236p2ee54649ld9d328f429005d6a@mail.gmail.com> Date: Sat, 8 Apr 2006 13:36:15 +0800 From: Astrodog To: freebsd-amd64@freebsd.org, "John-Mark Gurney" In-Reply-To: <200604072116.k37LGQhQ071637@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060407172618.GC72485@funkthat.com> <200604072116.k37LGQhQ071637@lurza.secnetix.de> Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 05:36:17 -0000 On 4/8/06, Oliver Fromme wrote: > John-Mark Gurney wrote: > > Astrodog wrote this message on Fri, Apr 07, 2006 at 21:28 +0800: > > > and pointer, you use 4 Bytes. On a 64-bit processor, all ints, and > > > pointers take up 64-bits of memory. So, for every int and pointer, y= ou > > > use 8 bytes. (Assuming its a 64-bit app, of course) That means > > > > Not quite... FreeBSD/amd64 like all? the other arches are LP64... > > that means longs and pointers are 64bits, while ints remain at 32bits.= .. > Gotcha > I think longs are 32 bits on /i386, and 64 bits on /amd64 > (On /i386, "long longs" are 64 bits.) > > A programmer should not rely on specific sizes of longs, > ints etc. anyway. In particular, he should not assume > that a long is larger than an int, that a pointer has > the same size as an int or a long, and similar things. > Heh. Shouldn't and won't are different, sadly. Myself included. > If a specific size is needed, then one of the standard > types int64_t, int32_t etc. should be used which are > defined appropriately by the OS. > > Or, or course, use a higher-level programming language > where you don't have to care about integer sizes at all, > such as Python ("print 999**999" will fill the screen > nicely). ;-) > I suspect a python kernel would be painfully slow....... > > This was primarily done because too many people assumed ints were > > 32bits for things like disk structures and network protocol layout, > > and to break less code, LP64 was decided upon... > Glad to know I'm not the only one... > I guess this is the most important reason: If ints were 64 > bits, there would be no easy way to handle 32 bit entities. > Not being able to handle 32 bit objects with a native data > type whould be a major problem, especially for an OS kernel, > I think. > Can an AMD64 processor actually handle 32 bits of data natively, or does it just knock off the last 32 bits of a 64-bit version, when its not in long mode? > Best regards > Oliver > > PS: The random quote in my signature below fits pretty well. > It really is random, I swear. :-) > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "C is quirky, flawed, and an enormous success." > -- Dennis M. Ritchie. > _______________________________________________ > 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 Sat Apr 8 06:05:59 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F330A16A401 for ; Sat, 8 Apr 2006 06:05:58 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E1A43D53 for ; Sat, 8 Apr 2006 06:05:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (4ipc6fsnj1hs9kri@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k3865seq005150; Fri, 7 Apr 2006 23:05:54 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k3865qUp005149; Fri, 7 Apr 2006 23:05:52 -0700 (PDT) (envelope-from jmg) Date: Fri, 7 Apr 2006 23:05:52 -0700 From: John-Mark Gurney To: Astrodog Message-ID: <20060408060552.GG72485@funkthat.com> Mail-Followup-To: Astrodog , freebsd-amd64@freebsd.org References: <20060407172618.GC72485@funkthat.com> <200604072116.k37LGQhQ071637@lurza.secnetix.de> <2fd864e0604072236p2ee54649ld9d328f429005d6a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e0604072236p2ee54649ld9d328f429005d6a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 06:05:59 -0000 Astrodog wrote this message on Sat, Apr 08, 2006 at 13:36 +0800: > On 4/8/06, Oliver Fromme wrote: > > I guess this is the most important reason: If ints were 64 > > bits, there would be no easy way to handle 32 bit entities. > > Not being able to handle 32 bit objects with a native data > > type whould be a major problem, especially for an OS kernel, > > I think. > > > Can an AMD64 processor actually handle 32 bits of data natively, or > does it just knock off the last 32 bits of a 64-bit version, when its > not in long mode? yes, it can... infact it defaults to 32bits unless a prefix is provided to access 64bit registers... (assuming a mode that 64bit registers are accessable).. Though as w/ most processors, the upper 32bits are still around, just on 32bit operations they are ignored... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 08:15:17 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E4B416A400 for ; Sat, 8 Apr 2006 08:15:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F1143D55 for ; Sat, 8 Apr 2006 08:15:16 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FS8bD-000OjG-2i; Sat, 08 Apr 2006 11:15:15 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Astrodog In-Reply-To: Message from Astrodog of "Fri, 07 Apr 2006 21:38:19 +0800." <2fd864e0604070638n11ff30f1pa9ad3fe5ac669ea7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 08 Apr 2006 11:15:15 +0300 From: Danny Braniss Message-ID: Cc: freebsd-amd64@freebsd.org Subject: Re: safe way to build i386 arch makeworld on amd64 arch? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 08:15:17 -0000 > On 4/7/06, Danny Braniss wrote: > > > hello list, > > > > > > is there a save way to 'downgrade' an amd64 build system by using '= make world' ? > > > > > > e.g. just remove the CPUTYPE=3Dopteron from the make.conf file and = do a > > > build world/kernels install world/kernels ? > > > > > > of do we need to do some more for this? > > > > > > thanks in advance > > > > > > Regards > > > patrick > > > > = > To downgrade? Not realistically. > = > > you can, i do: > > export MAKEOBJDIRPREFIX=3D/somwhersafe-i386 > > make TARGET_ARCH=3Di386 buildworld > > same for buildkernel, installworld/installkernel, and also you can sp= ecify > > a different DESTDIR=3D > > > > danny > > > = > That would certainly allow him to crosscompile an i386 kernel, and > world, but wouldn't have much effect on downgrading from AMD64 to > i386, since you run into a chicken or the egg problem with the kernel, > and world. (a 64-bit kernel does not play nice on a 32-bit world, > without some hacking around, and a 32-bit kernel does not play nice on > a 64-bit world), which makes it impossible to actually do both steps. > = > If you install the 32-bit kernel first, and reboot, the kernel won't > be able to run the 64-bit binaries. If you install the 32-bit world > first, the 64-bit kernel will become very, very sad, and won't let the > installation complete. > = > If you try to install the kernel, then the world without a reboot, you > have the same problem as installing the 32-bit world first, since even > with a 32-bit kernel installed, you're still RUNNING the 64-bit kernel > until you reboot. > = > There are actually ways to do this, but its almost always a bad idea. > Not to mention this will break any packages, or ports you're using > too, with the exception, perhaps, of Linux Compat. You are of course correct, but then again, I did mention DESTDIR=3D and MAKEOBJDIRPREFIX. personaly, machines that are not diskless, i tend to have 2 root slices (it only needs some 500 Mgb), and install on a non active slice/partition= , then i do 'boot0cfg -sn device'. When that fails i do have to go to the consol= e and reboot from the old partition :-(, this is nice if the console is walking distance away ... danny From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 08:23: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 0E30016A403 for ; Sat, 8 Apr 2006 08:23:33 +0000 (UTC) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (217-19-20-65.dsl.cambrium.nl [217.19.20.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA3643D49 for ; Sat, 8 Apr 2006 08:23:31 +0000 (GMT) (envelope-from patrick@cyberwizards.nl) Received: from gandalf.cyberwizards.nl (localhost [127.0.0.1]) by gandalf.cyberwizards.nl (8.13.4/8.13.4) with ESMTP id k388NRYF094499 for ; Sat, 8 Apr 2006 10:23:27 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) Received: from localhost (pbm@localhost) by gandalf.cyberwizards.nl (8.13.4/8.13.4/Submit) with ESMTP id k388NQt8094496 for ; Sat, 8 Apr 2006 10:23:27 +0200 (CEST) (envelope-from patrick@cyberwizards.nl) X-Authentication-Warning: gandalf.cyberwizards.nl: pbm owned process doing -bs Date: Sat, 8 Apr 2006 10:23:26 +0200 (CEST) From: patrick X-X-Sender: pbm@gandalf.cyberwizards.nl To: freebsd-amd64@freebsd.org In-Reply-To: Message-ID: <20060408102045.F94334@gandalf.cyberwizards.nl> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: safe way to build i386 arch makeworld on amd64 arch? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 08:23:33 -0000 Thanks all for feedback. i did some tresstesting on apache and it seems like 'perfoming well' I guess the best option for me is just add some more memory ;) Enjoy! grtz patrick >>>> is there a save way to 'downgrade' an amd64 build system by using 'make world' ? >>>> >>>> e.g. just remove the CPUTYPE=opteron from the make.conf file and do a >>>> build world/kernels install world/kernels ? >> >> To downgrade? Not realistically. >> >> That would certainly allow him to crosscompile an i386 kernel, and >> world, but wouldn't have much effect on downgrading from AMD64 to >> i386, since you run into a chicken or the egg problem with the kernel, >> and world. (a 64-bit kernel does not play nice on a 32-bit world, >> without some hacking around, and a 32-bit kernel does not play nice on >> a 64-bit world), which makes it impossible to actually do both steps. >> >> If you install the 32-bit kernel first, and reboot, the kernel won't >> be able to run the 64-bit binaries. If you install the 32-bit world >> first, the 64-bit kernel will become very, very sad, and won't let the >> installation complete. >> >> If you try to install the kernel, then the world without a reboot, you >> have the same problem as installing the 32-bit world first, since even >> with a 32-bit kernel installed, you're still RUNNING the 64-bit kernel >> until you reboot. >> >> There are actually ways to do this, but its almost always a bad idea. >> Not to mention this will break any packages, or ports you're using >> too, with the exception, perhaps, of Linux Compat. > You are of course correct, but then again, I did mention DESTDIR= > and MAKEOBJDIRPREFIX. > > personaly, machines that are not diskless, i tend to have 2 root slices > (it only needs some 500 Mgb), and install on a non active slice/partition, then > i do 'boot0cfg -sn device'. When that fails i do have to go to the console > and reboot from the old partition :-(, this is nice if the console is > walking distance away ... From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 10:09:35 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 73A1716A401 for ; Sat, 8 Apr 2006 10:09:35 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3395F43D4C for ; Sat, 8 Apr 2006 10:09:27 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ejqdov@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k38A9Kuc094513; Sat, 8 Apr 2006 12:09:26 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k38A9FwJ094512; Sat, 8 Apr 2006 12:09:15 +0200 (CEST) (envelope-from olli) Date: Sat, 8 Apr 2006 12:09:15 +0200 (CEST) Message-Id: <200604081009.k38A9FwJ094512@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, John-Mark Gurney In-Reply-To: <20060407212254.GE72485@funkthat.com> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sat, 08 Apr 2006 12:09:26 +0200 (CEST) Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG, John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 10:09:35 -0000 John-Mark Gurney wrote: > Oliver Fromme wrote this message on Fri, Apr 07, 2006 at 23:16 +0200: > > John-Mark Gurney wrote: > > > Not quite... FreeBSD/amd64 like all? the other arches are LP64... > > > that means longs and pointers are 64bits, while ints remain at 32bits... > > > > I think longs are 32 bits on /i386, and 64 bits on /amd64 > > (On /i386, "long longs" are 64 bits.) > > Sorry, I ment to write like all the other 64bit arches.... > ^^^^^ > > since i386 isn't 32bit, it isn't LP64, the same way arm or powerpc > isn't LP64... Oh, I see. Yes of course, you're right. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "When your hammer is C++, everything begins to look like a thumb." -- Steve Haflich, in comp.lang.c++ From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 10:21:53 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 AE7E116A401 for ; Sat, 8 Apr 2006 10:21:53 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E26AF43D45 for ; Sat, 8 Apr 2006 10:21:52 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (kdapat@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k38ALkFG094734 for ; Sat, 8 Apr 2006 12:21:51 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k38ALkR1094733; Sat, 8 Apr 2006 12:21:46 +0200 (CEST) (envelope-from olli) Date: Sat, 8 Apr 2006 12:21:46 +0200 (CEST) Message-Id: <200604081021.k38ALkR1094733@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <2fd864e0604072236p2ee54649ld9d328f429005d6a@mail.gmail.com> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sat, 08 Apr 2006 12:21:51 +0200 (CEST) Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 10:21:53 -0000 Astrodog wrote: > Oliver Fromme wrote: > > If a specific size is needed, then one of the standard > > types int64_t, int32_t etc. should be used which are > > defined appropriately by the OS. > > > > Or, or course, use a higher-level programming language > > where you don't have to care about integer sizes at all, > > such as Python ("print 999**999" will fill the screen > > nicely). ;-) > > I suspect a python kernel would be painfully slow....... Certainly. I wasn't implying that Python would be well- suited to write an OS kernel in. Unless someone builds a processor that executes Python bytecode natively. > > I guess this is the most important reason: If ints were 64 > > bits, there would be no easy way to handle 32 bit entities. > > Not being able to handle 32 bit objects with a native data > > type whould be a major problem, especially for an OS kernel, > > I think. > > Can an AMD64 processor actually handle 32 bits of data natively, or > does it just knock off the last 32 bits of a 64-bit version, when its > not in long mode? Yes, it can do both natively. It's actually quite similar to the way the 32bit registers are extensions of the 16bit registers on the i386 platform, e.g. the %ax register (16bit) just becomes the lower half of the %eax register (32bit). Both variantes are handled with exactly the same opcodes, but special prefix bytes are used to select between the two data modes (16bit vs. 32bit). On the amd64 platform, it's somewhat similar, except that you get a further level: The %eax register (32bit) becomes the lower half of the %rax register (64bit). The processor can still handle both data types natively. Best regards Oliver (right now busy writing a boot manager in assembler) -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is to C as Lung Cancer is to Lung." -- Thomas Funke From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 10:43: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 4484716A400 for ; Sat, 8 Apr 2006 10:43:46 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 975BF43D45 for ; Sat, 8 Apr 2006 10:43:45 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail07.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k38Ahhc5029821 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 8 Apr 2006 20:43:44 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k38Ahhsi005203 for ; Sat, 8 Apr 2006 20:43:43 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k38AhhrJ005202 for freebsd-amd64@freebsd.org; Sat, 8 Apr 2006 20:43:43 +1000 (EST) (envelope-from peter) Date: Sat, 8 Apr 2006 20:43:42 +1000 From: Peter Jeremy To: freebsd-amd64@freebsd.org Message-ID: <20060408104342.GA720@turion.vk2pj.dyndns.org> References: <2fd864e0604072236p2ee54649ld9d328f429005d6a@mail.gmail.com> <200604081021.k38ALkR1094733@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604081021.k38ALkR1094733@lurza.secnetix.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 10:43:46 -0000 On Sat, 2006-Apr-08 12:21:46 +0200, Oliver Fromme wrote: > > I suspect a python kernel would be painfully slow....... > >Certainly. I wasn't implying that Python would be well- >suited to write an OS kernel in. Unless someone builds >a processor that executes Python bytecode natively. Squeak (a smalltalk dialect) has its kernel written in a subset of squeak which can be either interpreted or compiled into assembler. The former maintains the development/testing advantages of an interpreter and the latter makes it run at a decent speed. You may be able to do the same with Python. Alternatively, JIT techniques have received an enormous amount of effort over the past decade (thanks to Java) and a JIT Python may be reasonable. > Oliver (right now busy writing a boot manager in assembler) Not Python?? :-) -- Peter Jeremy From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 8 12:05: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 B8CCE16A401 for ; Sat, 8 Apr 2006 12:05:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1686643D64 for ; Sat, 8 Apr 2006 12:05:21 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mjktux@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k38C5Cox097206 for ; Sat, 8 Apr 2006 14:05:17 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k38C5CWp097205; Sat, 8 Apr 2006 14:05:12 +0200 (CEST) (envelope-from olli) Date: Sat, 8 Apr 2006 14:05:12 +0200 (CEST) Message-Id: <200604081205.k38C5CWp097205@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20060408104342.GA720@turion.vk2pj.dyndns.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sat, 08 Apr 2006 14:05:17 +0200 (CEST) Cc: Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 12:05:33 -0000 Peter Jeremy wrote: > On Sat, 2006-Apr-08 12:21:46 +0200, Oliver Fromme wrote: > > > I suspect a python kernel would be painfully slow....... > > > > Certainly. I wasn't implying that Python would be well- > > suited to write an OS kernel in. Unless someone builds > > a processor that executes Python bytecode natively. > > Squeak (a smalltalk dialect) has its kernel written in a subset of > squeak which can be either interpreted or compiled into assembler. > The former maintains the development/testing advantages of an > interpreter and the latter makes it run at a decent speed. You may be > able to do the same with Python. In fact, that's already possible. This is one of the advantages of the Python grammar being relatively simple and well-designed: It's easy to write independent implementations of it. Besides the standard Python implementation (which comes with an interactive interpreter and a bytecode generator) there are several other implementations of the Python language, including compilers such as "Pyrex" that create C code which can be compiled into native binaries (and is easy to interface with other C programs). > Alternatively, JIT techniques have > received an enormous amount of effort over the past decade (thanks to > Java) and a JIT Python may be reasonable. In fact, that's already possible. :-) For example, using "Psyco" (a JIT compiler for Python): http://psyco.sourceforge.net/introduction.html or "Jython" (a Python implementation in Java that creates Java bytecode): http://www.jython.org/docs/whatis.html > > Oliver (right now busy writing a boot manager in assembler) > > Not Python?? :-) Well, that would have been an option if there were no space concerns. That or O'Caml. :-) However, it must be able to run from an ISO9660 sector, using ElTorito "no emulation mode", so it must fit in 2048 bytes. The Python runtime library is a little bit larger than that. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible." -- John William Chambless