From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 20 01:05:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2972D16A4CE for ; Sun, 20 Mar 2005 01:05:58 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC6E843D1D; Sun, 20 Mar 2005 01:05:57 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2K15uUr067258; Sun, 20 Mar 2005 01:05:57 GMT (envelope-from davidxu@freebsd.org) Message-ID: <423CCC7C.60408@freebsd.org> Date: Sun, 20 Mar 2005 09:06:04 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.2) Gecko/20041004 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andy Fawcett References: <200503200019.39083.andy@athame.co.uk> In-Reply-To: <200503200019.39083.andy@athame.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Does anyone have any experience of the Abit KV-80 board? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 01:05:58 -0000 Andy Fawcett wrote: >Hi, > >I've looked through the archives, and googled a fair bit, without success. > >Does anyone here have any experience (good or bad) of running FreeBSD/amd64 on >an Abit KV-80 board? > >http://www2.abit.com.tw/page/en/motherboard/motherboard_detail.php?pMODEL_NAME=KV-80&fMTYPE=Socket%20754 > >A. > > > I haven't used kv8, but used av8, av8 has lots of bugs in ACPI script, also FreeBSD can boot and all devices seem be probed right, but kernel will keep printing annoying messages, vty0 is unusable if you press backspace and cause console to bell. ACPI is really failure technology. David Xu From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 20 07:28:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2251C16A4D0; Sun, 20 Mar 2005 07:28:53 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id B583943D1D; Sun, 20 Mar 2005 07:28:51 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j2K7QhQT004764; Sun, 20 Mar 2005 08:26:43 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j2K7Qorq092659; Sun, 20 Mar 2005 08:26:50 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j2K7Qnef092658; Sun, 20 Mar 2005 08:26:49 +0100 (CET) (envelope-from ftigeot) Date: Sun, 20 Mar 2005 08:26:49 +0100 From: Francois Tigeot To: David Wolfskill Message-ID: <20050320072649.GB73141@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050320014701.GC41509@bunrab.catwhisker.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Qt applications hang X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 07:28:53 -0000 On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: > There's a recent entry in /usr/ports/UPDATING that may be relevant. Thanks, but I fail to see what is relevant in this case. I suspected at one time the system compiler to be busted, but I recompiled everything with -O -pipe and the problem remains. Cc to -amd64 to see if there may be something architecture specific. [For the record, every QT application hang immediately when some menu options are selected. The system is 5.4-PRERELEASE/amd64] -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 20 09:30:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92E9616A4CE; Sun, 20 Mar 2005 09:30:04 +0000 (GMT) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id E403B43D3F; Sun, 20 Mar 2005 09:30:03 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from vimes.int.athame.co.uk ([192.168.1.3]) by hex.athame.co.uk with esmtp (Exim 4.50 (FreeBSD)) id 1DCwkz-000HYs-Vf; Sun, 20 Mar 2005 11:30:02 +0200 From: Andy Fawcett Organization: Being Lazy At Home (BLAH!) To: freebsd-stable@freebsd.org Date: Sun, 20 Mar 2005 11:30:29 +0200 User-Agent: KMail/1.8 References: <20050320072649.GB73141@aoi.wolfpond.org> In-Reply-To: <20050320072649.GB73141@aoi.wolfpond.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503201130.32507.andy@athame.co.uk> cc: freebsd-ports@freebsd.org cc: freebsd-amd64@freebsd.org cc: David Wolfskill Subject: Re: Qt applications hang X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 09:30:04 -0000 On Sunday 20 March 2005 09:26, Francois Tigeot wrote: > On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: > > There's a recent entry in /usr/ports/UPDATING that may be relevant. > > Thanks, but I fail to see what is relevant in this case. > > I suspected at one time the system compiler to be busted, but I recompiled > everything with -O -pipe and the problem remains. > > Cc to -amd64 to see if there may be something architecture specific. > > [For the record, every QT application hang immediately when some menu > options are selected. The system is 5.4-PRERELEASE/amd64] I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and I'm running KDE from ports in it without apparent problems. A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 20 09:46:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3775316A4CE; Sun, 20 Mar 2005 09:46:40 +0000 (GMT) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88B3943D46; Sun, 20 Mar 2005 09:46:38 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from vimes.int.athame.co.uk ([192.168.1.3]) by hex.athame.co.uk with esmtp (Exim 4.50 (FreeBSD)) id 1DCx0z-000Hk8-PK; Sun, 20 Mar 2005 11:46:33 +0200 From: Andy Fawcett Organization: Being Lazy At Home (BLAH!) To: David Xu Date: Sun, 20 Mar 2005 11:47:03 +0200 User-Agent: KMail/1.8 References: <200503200019.39083.andy@athame.co.uk> <423CCC7C.60408@freebsd.org> In-Reply-To: <423CCC7C.60408@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503201147.05006.andy@athame.co.uk> cc: freebsd-amd64@freebsd.org Subject: Re: Does anyone have any experience of the Abit KV-80 board? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 09:46:40 -0000 Hi David, On Sunday 20 March 2005 03:06, David Xu wrote: > Andy Fawcett wrote: > >Hi, > > > >I've looked through the archives, and googled a fair bit, without success. > > > >Does anyone here have any experience (good or bad) of running > > FreeBSD/amd64 on an Abit KV-80 board? > > > >http://www2.abit.com.tw/page/en/motherboard/motherboard_detail.php?pMODEL_ > >NAME=KV-80&fMTYPE=Socket%20754 > > > >A. > > I haven't used kv8, but used av8, av8 has lots of bugs in ACPI script, also > FreeBSD can boot and all devices seem be probed right, but kernel will keep > printing annoying messages, vty0 is unusable if you press backspace and > cause > console to bell. ACPI is really failure technology. Thanks for these comments. These points, together with some I received off-list, have been enough to convince me to avoid this particular board. A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 20 11:15:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6247416A4CE; Sun, 20 Mar 2005 11:15:06 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A560A43D58; Sun, 20 Mar 2005 11:15:04 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j2KBET8i007734; Sun, 20 Mar 2005 12:14:29 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j2KBEbqP094556; Sun, 20 Mar 2005 12:14:37 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j2KBEbKa094555; Sun, 20 Mar 2005 12:14:37 +0100 (CET) (envelope-from ftigeot) Date: Sun, 20 Mar 2005 12:14:36 +0100 From: Francois Tigeot To: Andy Fawcett Message-ID: <20050320111436.GA93111@aoi.wolfpond.org> References: <20050320072649.GB73141@aoi.wolfpond.org> <200503201130.32507.andy@athame.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503201130.32507.andy@athame.co.uk> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Qt applications hang X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 11:15:06 -0000 On Sun, Mar 20, 2005 at 11:30:29AM +0200, Andy Fawcett wrote: > On Sunday 20 March 2005 09:26, Francois Tigeot wrote: > > On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote: > > > There's a recent entry in /usr/ports/UPDATING that may be relevant. > > > > I suspected at one time the system compiler to be busted, but I recompiled > > everything with -O -pipe and the problem remains. > > > > Cc to -amd64 to see if there may be something architecture specific. > > > > [For the record, every QT application hang immediately when some menu > > options are selected. The system is 5.4-PRERELEASE/amd64] > > I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and > I'm running KDE from ports in it without apparent problems. The strange thing is, most of the things work (I have a user running kde from an X terminal and not complaining). Trying to open a file dialog (Location/Open Location in Konqueror) will howewer result in a freezed gui. There must be something locally broken, but so far I was unable to find it. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 08:52:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8520A16A4CE for ; Mon, 21 Mar 2005 08:52:09 +0000 (GMT) Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5316F43D48 for ; Mon, 21 Mar 2005 08:52:09 +0000 (GMT) (envelope-from frank.w@hushmail.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id BA3B7A33B6 for ; Mon, 21 Mar 2005 00:52:08 -0800 (PST) Received: from mailserver5.hushmail.com (mailserver5.hushmail.com [65.39.178.19]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Mon, 21 Mar 2005 00:52:08 -0800 (PST) Received: by mailserver5.hushmail.com (Postfix, from userid 65534) id 204D733C73; Mon, 21 Mar 2005 00:52:08 -0800 (PST) Date: Mon, 21 Mar 2005 00:52:06 -0800 To: freebsd-amd64@freebsd.org Cc: From: Message-Id: <20050321085208.204D733C73@mailserver5.hushmail.com> Subject: sis network card driver (was: Ethernet address ff:ff:ff:ff:ff:ff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 08:52:09 -0000 Hello! I noticed the same effect as Ilia, namely that the Ethernet card was not correctly recognized. The first sign of this is the incorrect Ethernet address (in my case 00:00:00:00:00:00). This problem occurs in all FreeBSD/amd64 versions, that is, FreeBSD-5.3_RELEASE, FreeBSD-5-STABLE, and FreeBSD-current. BUT: The network card is correctly recognized under FreeBSD/i386 (checked with FreeBSD-5.3_RELEASE) !!! The hardware in my case is an asrock upgrade board with the network card on board. Regards, Frank Concerned about your privacy? Follow this link to get secure FREE email: http://www.hushmail.com/?l=2 Free, ultra-private instant messaging with Hush Messenger http://www.hushmail.com/services-messenger?l=434 Promote security and make money with the Hushmail Affiliate Program: http://www.hushmail.com/about-affiliate?l=427 From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 11:01:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED6E016A4CE for ; Mon, 21 Mar 2005 11:01:22 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F4B143D66 for ; Mon, 21 Mar 2005 11:01:22 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2LB1MWF013481 for ; Mon, 21 Mar 2005 11:01:22 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2LB1Lnj013475 for freebsd-amd64@freebsd.org; Mon, 21 Mar 2005 11:01:21 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 21 Mar 2005 11:01:21 GMT Message-Id: <200503211101.j2LB1Lnj013475@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 11:01:23 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/03/10] amd64/78677 amd64 IPSEC causes panic on AMD64 FreeBSD >5.2. o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o 3 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation 21 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 o [2005/02/13] amd64/77470 amd64 Using of cyrillic filenames conversion le o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build 10 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 01:32:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC87F16A4CE for ; Mon, 21 Mar 2005 01:32:44 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id C35B943D2D for ; Mon, 21 Mar 2005 01:32:44 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 95820555DF for ; Mon, 21 Mar 2005 01:32:44 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91B8D16A4CE for ; Mon, 21 Mar 2005 01:32:44 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2AF843D2D for ; Mon, 21 Mar 2005 01:32:43 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id BA25478C79; Sun, 20 Mar 2005 20:34:27 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36068-04; Sun, 20 Mar 2005 20:34:21 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id DE2B978C64; Sun, 20 Mar 2005 20:34:20 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 5D4AA28DEF; Sun, 20 Mar 2005 16:59:59 -0500 (EST) Date: Sun, 20 Mar 2005 16:59:59 -0500 From: Damian Gerow To: vjordana@t-online.de Message-ID: <20050320215959.GA697@afflictions.org> References: <20050319021654.GD27012@afflictions.org> <423CAAE5.4080101@shih.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <423CAAE5.4080101@shih.be> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org X-Mailman-Approved-At: Mon, 21 Mar 2005 12:49:17 +0000 cc: amd64@lists.freebsd.org Subject: Re: java/jdk15 help X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 01:32:45 -0000 Thus spake vjordana@t-online.de (vjordana@t-online.de) [19/03/05 17:44]: : >I've noticed that a few people here have successfully gotten a native : >java/jdk15 built. Can one of those people lend me a hand, please? : > : >I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky : >problem : >thrown by the jdk15 build. But afterwards, all I seem to get is hung javac : >processes, each consuming 100% of CPU. : : cd /usr/ports/java/jdk15 : make build 2>&1 | tee build.out (or make build |& tee build.out, : depending on your shell) : and when the compilation breaks with an error, compile directly the long : line between if/then : See the mailing lists Yep, I've already worked past that stage. The problem I'm having is just afterwards, and I get hung javac processes. i.e. the build doesn't fail with an error, it just hangs. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 13:36:05 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28DF116A4CE for ; Mon, 21 Mar 2005 13:36:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6FA743D39 for ; Mon, 21 Mar 2005 13:36:04 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1220767wra for ; Mon, 21 Mar 2005 05:36:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=WpAs+s85RiwLjq3HZbyAJonRMyjae2hy8zDD6zjyogXmeRB5w5HQrbES74QZmLRXK7vfElANdAiQ2JKKraTqxw5klz+XDY9JNzuwVLT55v82u7lBp5f+LMNDUeqlfV01JFzmsEdZ/WdgJXY+Q+d7tUC1WFppDY2ZbFy9VF453mY= Received: by 10.54.68.17 with SMTP id q17mr1335025wra; Mon, 21 Mar 2005 05:36:03 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 05:36:03 -0800 (PST) Message-ID: <2fd864e05032105366eaf8b2c@mail.gmail.com> Date: Mon, 21 Mar 2005 05:36:03 -0800 From: Astrodog To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 13:36:05 -0000 I was wondering if the R3000Z fixes have been committed to the RELENG_5 branch, I don't see anything on the lists about it. Should I expect 5.4 to work with the R3000 line? --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 13:07:26 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C71AD16A4CE for ; Mon, 21 Mar 2005 13:07:26 +0000 (GMT) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96FA543D39 for ; Mon, 21 Mar 2005 13:07:26 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 87AD55586E for ; Mon, 21 Mar 2005 13:07:26 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83EF816A4CE for ; Mon, 21 Mar 2005 13:07:26 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 063E443D2D for ; Mon, 21 Mar 2005 13:07:26 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so985539wri for ; Mon, 21 Mar 2005 05:07:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=V2ZyCWNHedi1jqE7xG6tizd9cPxAubno4Ei962c498t17U+3YkRoI+cNXZJ3w4NOhSeGr9m+jnY4ciuk+svGxsAHOpIvviJfphy2IctdVNUx5DzXZz+uh4L4LHYh2uuUTDRyxo8zpK9rkFgpWDALzWIuoCWBXcWyRzsmW+tqxtU= Received: by 10.54.78.16 with SMTP id a16mr3101162wrb; Mon, 21 Mar 2005 05:07:24 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 05:07:22 -0800 (PST) Message-ID: <2fd864e050321050772a3cbd4@mail.gmail.com> Date: Mon, 21 Mar 2005 05:07:22 -0800 From: Astrodog To: Damian Gerow In-Reply-To: <20050320215959.GA697@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050319021654.GD27012@afflictions.org> <423CAAE5.4080101@shih.be> <20050320215959.GA697@afflictions.org> X-Mailman-Approved-At: Mon, 21 Mar 2005 13:51:30 +0000 cc: amd64@lists.freebsd.org cc: vjordana@t-online.de Subject: Re: java/jdk15 help X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 13:07:26 -0000 On Sun, 20 Mar 2005 16:59:59 -0500, Damian Gerow wrote: > Thus spake vjordana@t-online.de (vjordana@t-online.de) [19/03/05 17:44]: > : >I've noticed that a few people here have successfully gotten a native > : >java/jdk15 built. Can one of those people lend me a hand, please? > : > > : >I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky > : >problem > : >thrown by the jdk15 build. But afterwards, all I seem to get is hung javac > : >processes, each consuming 100% of CPU. > : > : cd /usr/ports/java/jdk15 > : make build 2>&1 | tee build.out (or make build |& tee build.out, > : depending on your shell) > : and when the compilation breaks with an error, compile directly the long > : line between if/then > : See the mailing lists > > Yep, I've already worked past that stage. The problem I'm having is just > afterwards, and I get hung javac processes. i.e. the build doesn't fail > with an error, it just hangs. > _______________________________________________ > 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" > Have you tried just waiting? From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 15:40:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C73EC16A4CE for ; Mon, 21 Mar 2005 15:40:12 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id F004B43D4C for ; Mon, 21 Mar 2005 15:40:11 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 78D4D78C7F; Mon, 21 Mar 2005 10:41:57 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08095-08; Mon, 21 Mar 2005 10:41:48 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 80CA378C7D; Mon, 21 Mar 2005 10:41:47 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 600F128DF1; Mon, 21 Mar 2005 10:40:01 -0500 (EST) Date: Mon, 21 Mar 2005 10:40:01 -0500 From: Damian Gerow To: Astrodog Message-ID: <20050321154001.GF697@afflictions.org> Mail-Followup-To: Astrodog , freebsd-amd64@freebsd.org References: <20050319021654.GD27012@afflictions.org> <423CAAE5.4080101@shih.be> <20050320215959.GA697@afflictions.org> <2fd864e050321050772a3cbd4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e050321050772a3cbd4@mail.gmail.com> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org cc: freebsd-amd64@freebsd.org Subject: Re: java/jdk15 help X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 15:40:12 -0000 Thus spake Astrodog (astrodog@gmail.com) [21/03/05 08:09]: : > Yep, I've already worked past that stage. The problem I'm having is just : > afterwards, and I get hung javac processes. i.e. the build doesn't fail : > with an error, it just hangs. : : Have you tried just waiting? Unless a given javac requires >24h to complete, yes I have. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 15:49:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4898316A4CE for ; Mon, 21 Mar 2005 15:49:21 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7358F43D5F for ; Mon, 21 Mar 2005 15:49:18 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LFnGDK004159; Mon, 21 Mar 2005 10:49:17 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, Astrodog Date: Mon, 21 Mar 2005 10:49:11 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> In-Reply-To: <2fd864e05032105366eaf8b2c@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211049.11110.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/774/Fri Mar 18 20:04:06 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 15:49:21 -0000 On Monday 21 March 2005 08:36 am, Astrodog wrote: > I was wondering if the R3000Z fixes have been committed to the > RELENG_5 branch, I don't see anything on the lists about it. Should > I expect 5.4 to work with the R3000 line? Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest snapshot and let us know. Thanks, Jung-uk Kim > --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:10:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60CD416A4CE for ; Mon, 21 Mar 2005 16:10:11 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED55D43D2D for ; Mon, 21 Mar 2005 16:10:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2LG98Q1056703; Mon, 21 Mar 2005 09:09:09 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <423EF13B.2040008@samsco.org> Date: Mon, 21 Mar 2005 09:07:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> In-Reply-To: <200503211049.11110.jkim@niksun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:10:11 -0000 Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > >>I was wondering if the R3000Z fixes have been committed to the >>RELENG_5 branch, I don't see anything on the lists about it. Should >>I expect 5.4 to work with the R3000 line? > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest > snapshot and let us know. > > Thanks, > > Jung-uk Kim > > Is there any way that these systems can be detected at runtime and have the work-arounds be automatically activated? Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:12:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6547316A4CE for ; Mon, 21 Mar 2005 16:12:58 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0A8B43D49 for ; Mon, 21 Mar 2005 16:12:57 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so1113505wra for ; Mon, 21 Mar 2005 08:12:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=eCLrUYJnWpe17v41KYz363RNU4NfoDzPr6ZOovseDTS0aIzkQDj8oc+kKGjUZmcZ/ESWGNnKEtes5iUuE+Nds0BVr1gYvDfGh5K9B6AVQE5Lufa2Zv9emNqw65l8/9ZRgmzS9InDp3x7Tosia/u1jLSSkeT9UtCG0ty030KCXBY= Received: by 10.54.33.64 with SMTP id g64mr3394492wrg; Mon, 21 Mar 2005 08:12:56 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 08:12:56 -0800 (PST) Message-ID: <2fd864e05032108127248ddc6@mail.gmail.com> Date: Mon, 21 Mar 2005 08:12:56 -0800 From: Astrodog To: Scott Long In-Reply-To: <423EF13B.2040008@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <423EF13B.2040008@samsco.org> cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:12:58 -0000 On Mon, 21 Mar 2005 09:07:23 -0700, Scott Long wrote: > Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > >>I was wondering if the R3000Z fixes have been committed to the > >>RELENG_5 branch, I don't see anything on the lists about it. Should > >>I expect 5.4 to work with the R3000 line? > > > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest > > snapshot and let us know. > > > > Thanks, > > > > Jung-uk Kim > > > > > > Is there any way that these systems can be detected at runtime and have > the work-arounds be automatically activated? > > Scott > I'm not sure on the keyboard thing, Effectively, the laptop freezes up, then turns off whenever you try to test the keyboard and aux ports. The old fix was to just patch those functions to always return no error, without actually testing. I've gotten it to boot now, with the hint, but it appears that the keyboard is unusable. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:14:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 153A816A4CE for ; Mon, 21 Mar 2005 16:14:00 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80CA743D39 for ; Mon, 21 Mar 2005 16:13:59 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LGDwjl004993; Mon, 21 Mar 2005 11:13:58 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Scott Long Date: Mon, 21 Mar 2005 11:13:52 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <423EF13B.2040008@samsco.org> In-Reply-To: <423EF13B.2040008@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211113.52233.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:14:00 -0000 On Monday 21 March 2005 11:07 am, Scott Long wrote: > Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > >>I was wondering if the R3000Z fixes have been committed to the > >>RELENG_5 branch, I don't see anything on the lists about it. > >> Should I expect 5.4 to work with the R3000 line? > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > latest snapshot and let us know. > > > > Thanks, > > > > Jung-uk Kim > > Is there any way that these systems can be detected at runtime and > have the work-arounds be automatically activated? I believe DMI-based quirk table is the only way but we don't want to do that, right? Jung-uk Kim > Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:19:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53E4F16A4CE for ; Mon, 21 Mar 2005 16:19:39 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A881843D55 for ; Mon, 21 Mar 2005 16:19:38 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LGJaOn005220; Mon, 21 Mar 2005 11:19:38 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Astrodog Date: Mon, 21 Mar 2005 11:19:30 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <423EF13B.2040008@samsco.org> <2fd864e05032108127248ddc6@mail.gmail.com> In-Reply-To: <2fd864e05032108127248ddc6@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211119.30585.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:19:39 -0000 On Monday 21 March 2005 11:12 am, Astrodog wrote: > On Mon, 21 Mar 2005 09:07:23 -0700, Scott Long wrote: > > Jung-uk Kim wrote: > > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > >>I was wondering if the R3000Z fixes have been committed to the > > >>RELENG_5 branch, I don't see anything on the lists about it. > > >> Should I expect 5.4 to work with the R3000 line? > > > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > > latest snapshot and let us know. > > > > > > Thanks, > > > > > > Jung-uk Kim > > > > Is there any way that these systems can be detected at runtime > > and have the work-arounds be automatically activated? > > > > Scott > > I'm not sure on the keyboard thing, Effectively, the laptop freezes > up, then turns off whenever you try to test the keyboard and aux > ports. The old fix was to just patch those functions to always > return no error, without actually testing. I've gotten it to boot > now, with the hint, but it appears that the keyboard is unusable. If you enabled ACPI, that's expected. That is because there's resource allocation problem with current ASL. If you want to enable ACPI, ASL patch is here: http://docs.freebsd.org/cgi/mid.cgi?200501192214.27401.jkim Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:21:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BA1F16A4CE for ; Mon, 21 Mar 2005 16:21:10 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13F5743D2D for ; Mon, 21 Mar 2005 16:21:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2LGKAus056784; Mon, 21 Mar 2005 09:20:11 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <423EF3D2.9050205@samsco.org> Date: Mon, 21 Mar 2005 09:18:26 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <423EF13B.2040008@samsco.org> <200503211113.52233.jkim@niksun.com> In-Reply-To: <200503211113.52233.jkim@niksun.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:21:10 -0000 Jung-uk Kim wrote: > On Monday 21 March 2005 11:07 am, Scott Long wrote: > >>Jung-uk Kim wrote: >> >>>On Monday 21 March 2005 08:36 am, Astrodog wrote: >>> >>>>I was wondering if the R3000Z fixes have been committed to the >>>>RELENG_5 branch, I don't see anything on the lists about it. >>>>Should I expect 5.4 to work with the R3000 line? >>> >>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the >>>latest snapshot and let us know. >>> >>>Thanks, >>> >>>Jung-uk Kim >> >>Is there any way that these systems can be detected at runtime and >>have the work-arounds be automatically activated? > > > I believe DMI-based quirk table is the only way but we don't want to > do that, right? > > Jung-uk Kim > > >>Scott Well, it's gross, but it's not impossible to do. Is there a technical reason why we wouldn't want this? Are there any alternatives, like detecting a signature in ACPI, either a text string or a certain bit of ASL bytecode? Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 16:41:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7187416A4CE for ; Mon, 21 Mar 2005 16:41:48 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BB5A43D46 for ; Mon, 21 Mar 2005 16:41:48 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LGfkw3006091; Mon, 21 Mar 2005 11:41:47 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: Scott Long Date: Mon, 21 Mar 2005 11:41:40 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211113.52233.jkim@niksun.com> <423EF3D2.9050205@samsco.org> In-Reply-To: <423EF3D2.9050205@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211141.40409.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 16:41:48 -0000 On Monday 21 March 2005 11:18 am, Scott Long wrote: > Jung-uk Kim wrote: > > On Monday 21 March 2005 11:07 am, Scott Long wrote: > >>Jung-uk Kim wrote: > >>>On Monday 21 March 2005 08:36 am, Astrodog wrote: > >>>>I was wondering if the R3000Z fixes have been committed to the > >>>>RELENG_5 branch, I don't see anything on the lists about it. > >>>>Should I expect 5.4 to work with the R3000 line? > >>> > >>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > >>>latest snapshot and let us know. > >>> > >>>Thanks, > >>> > >>>Jung-uk Kim > >> > >>Is there any way that these systems can be detected at runtime > >> and have the work-arounds be automatically activated? > > > > I believe DMI-based quirk table is the only way but we don't want > > to do that, right? > > > > Jung-uk Kim > > > >>Scott > > Well, it's gross, but it's not impossible to do. Is there a > technical reason why we wouldn't want this? The only technical reason that I can think of is some systems (e. g., IBM e345 and e346 Opteron servers) have DMI structures in ACPI NVS area, which is not accessible from early stage. If you want to do something like that, you will have to add gross hack in pmap.c to temporarily map it, I think. > Are there any alternatives, like detecting a signature in ACPI, > either a text string or a certain bit of ASL bytecode? We already have the quirk for this broken BIOS. However, keyboard probing happens way earlier to use this quirk. :-( Jung-uk Kim > Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 17:30:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4429816A4CE for ; Mon, 21 Mar 2005 17:30:27 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB62E43D4C for ; Mon, 21 Mar 2005 17:30:26 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so1157711wri for ; Mon, 21 Mar 2005 09:30:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=nGD6L5B70wDv4XzWu9pPIDtE9M5/ksyV43epxYCo+OhEp6GdGPE69cLm0ZKGrlBLAJQJALYcq1aOp/Q/aW0hKbTU8p5NE9q42Ej/cNVaJMDVs+LLHjywjRyZf2Djhf4mAOjbp2AO7yYbsMplotcHff7VBUGxu7ccvpDOC7RbXdM= Received: by 10.54.51.78 with SMTP id y78mr3347119wry; Mon, 21 Mar 2005 09:30:25 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 09:30:25 -0800 (PST) Message-ID: <2fd864e05032109304c2ad323@mail.gmail.com> Date: Mon, 21 Mar 2005 09:30:25 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <200503211141.40409.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211113.52233.jkim@niksun.com> <423EF3D2.9050205@samsco.org> <200503211141.40409.jkim@niksun.com> Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 17:30:27 -0000 > > >>>>I was wondering if the R3000Z fixes have been committed to the > > >>>>RELENG_5 branch, I don't see anything on the lists about it. > > >>>>Should I expect 5.4 to work with the R3000 line? > > >>> > > >>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > >>>latest snapshot and let us know. > > >>> > > >>>Thanks, > > >>> > > >>>Jung-uk Kim > > >> > > >>Is there any way that these systems can be detected at runtime > > >> and have the work-arounds be automatically activated? > > > > > > I believe DMI-based quirk table is the only way but we don't want > > > to do that, right? > > > > > > Jung-uk Kim > > > > > >>Scott > > > > Well, it's gross, but it's not impossible to do. Is there a > > technical reason why we wouldn't want this? > > The only technical reason that I can think of is some systems (e. g., > IBM e345 and e346 Opteron servers) have DMI structures in ACPI NVS > area, which is not accessible from early stage. If you want to do > something like that, you will have to add gross hack in pmap.c to > temporarily map it, I think. > > > Are there any alternatives, like detecting a signature in ACPI, > > either a text string or a certain bit of ASL bytecode? > > We already have the quirk for this broken BIOS. However, keyboard > probing happens way earlier to use this quirk. :-( > > Jung-uk Kim > > > Scott > Something that came up originally, when this issue was first noticed, was trying to figure out what, if any platforms, would have problems if this was made to apply to all AMD64 machines, and use the flag to drive an opt-out. In as far as I'm aware, no AMD64-based machines are effected if you just "break" the keyboard test functionality, though I'm not certain this is a path worth looking at, since its still a bit ugly. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 18:31:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 150EF16A4CE for ; Mon, 21 Mar 2005 18:31:00 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B5B443D49 for ; Mon, 21 Mar 2005 18:30:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2LITokD057359; Mon, 21 Mar 2005 11:29:54 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <423F1236.4000401@samsco.org> Date: Mon, 21 Mar 2005 11:28:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211113.52233.jkim@niksun.com> <423EF3D2.9050205@samsco.org> <200503211141.40409.jkim@niksun.com> <2fd864e05032109304c2ad323@mail.gmail.com> In-Reply-To: <2fd864e05032109304c2ad323@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.3 required=3.8 tests=ALL_TRUSTED,OPTING_OUT autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 18:31:00 -0000 Astrodog wrote: >>>>>>>I was wondering if the R3000Z fixes have been committed to the >>>>>>>RELENG_5 branch, I don't see anything on the lists about it. >>>>>>>Should I expect 5.4 to work with the R3000 line? >>>>>> >>>>>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the >>>>>>latest snapshot and let us know. >>>>>> >>>>>>Thanks, >>>>>> >>>>>>Jung-uk Kim >>>>> >>>>>Is there any way that these systems can be detected at runtime >>>>>and have the work-arounds be automatically activated? >>>> >>>>I believe DMI-based quirk table is the only way but we don't want >>>>to do that, right? >>>> >>>>Jung-uk Kim >>>> >>>> >>>>>Scott >>> >>>Well, it's gross, but it's not impossible to do. Is there a >>>technical reason why we wouldn't want this? >> >>The only technical reason that I can think of is some systems (e. g., >>IBM e345 and e346 Opteron servers) have DMI structures in ACPI NVS >>area, which is not accessible from early stage. If you want to do >>something like that, you will have to add gross hack in pmap.c to >>temporarily map it, I think. >> >> >>>Are there any alternatives, like detecting a signature in ACPI, >>>either a text string or a certain bit of ASL bytecode? >> >>We already have the quirk for this broken BIOS. However, keyboard >>probing happens way earlier to use this quirk. :-( >> >>Jung-uk Kim >> >> >>>Scott >> > > Something that came up originally, when this issue was first noticed, > was trying to figure out what, if any platforms, would have problems > if this was made to apply to all AMD64 machines, and use the flag to > drive an opt-out. In as far as I'm aware, no AMD64-based machines are > effected if you just "break" the keyboard test functionality, though > I'm not certain this is a path worth looking at, since its still a bit > ugly. My number 1 concern is that 5.4-RELEASE 'Just Works' when you load it onto a machine. Undocumented and under-documented work-arounds are very hard to manage and don't help users that aren't intimately familiar with the problem. This is a place where ("Alert! Don the asbestos skivvies now!") adding an option to ("I'm warning you! Prepare for flamage!") beastie.4th might be a good idea. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 18:38:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFBC916A4CE for ; Mon, 21 Mar 2005 18:38:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BE2743D4C for ; Mon, 21 Mar 2005 18:38:48 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1352448wra for ; Mon, 21 Mar 2005 10:38:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=UcpUSxZviNoKX5qLpbF0wggJz3a9HG07A8z0s6JhwlWhK8K9WzqvykKd+bfqMZw97Tkhq2KJFSJYhGg3pbXVx/MKt14ttSPWykPpYtMjt79lSKXvnPDFsrSq8NmclJvmCQ3gaWNjNsp4YJ3JX0qlzEosH96H87VZ3QInIgdXc5Y= Received: by 10.54.77.17 with SMTP id z17mr457415wra; Mon, 21 Mar 2005 10:38:47 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 10:38:46 -0800 (PST) Message-ID: <2fd864e05032110387af56562@mail.gmail.com> Date: Mon, 21 Mar 2005 10:38:46 -0800 From: Astrodog To: Scott Long In-Reply-To: <423F1236.4000401@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211113.52233.jkim@niksun.com> <423EF3D2.9050205@samsco.org> <200503211141.40409.jkim@niksun.com> <2fd864e05032109304c2ad323@mail.gmail.com> <423F1236.4000401@samsco.org> cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 18:38:49 -0000 On Mon, 21 Mar 2005 11:28:06 -0700, Scott Long wrote: > Astrodog wrote: > >>>>>>>I was wondering if the R3000Z fixes have been committed to the > >>>>>>>RELENG_5 branch, I don't see anything on the lists about it. > >>>>>>>Should I expect 5.4 to work with the R3000 line? > >>>>>> > >>>>>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > >>>>>>latest snapshot and let us know. > >>>>>> > >>>>>>Thanks, > >>>>>> > >>>>>>Jung-uk Kim > >>>>> > >>>>>Is there any way that these systems can be detected at runtime > >>>>>and have the work-arounds be automatically activated? > >>>> > >>>>I believe DMI-based quirk table is the only way but we don't want > >>>>to do that, right? > >>>> > >>>>Jung-uk Kim > >>>> > >>>> > >>>>>Scott > >>> > >>>Well, it's gross, but it's not impossible to do. Is there a > >>>technical reason why we wouldn't want this? > >> > >>The only technical reason that I can think of is some systems (e. g., > >>IBM e345 and e346 Opteron servers) have DMI structures in ACPI NVS > >>area, which is not accessible from early stage. If you want to do > >>something like that, you will have to add gross hack in pmap.c to > >>temporarily map it, I think. > >> > >> > >>>Are there any alternatives, like detecting a signature in ACPI, > >>>either a text string or a certain bit of ASL bytecode? > >> > >>We already have the quirk for this broken BIOS. However, keyboard > >>probing happens way earlier to use this quirk. :-( > >> > >>Jung-uk Kim > >> > >> > >>>Scott > >> > > > > Something that came up originally, when this issue was first noticed, > > was trying to figure out what, if any platforms, would have problems > > if this was made to apply to all AMD64 machines, and use the flag to > > drive an opt-out. In as far as I'm aware, no AMD64-based machines are > > effected if you just "break" the keyboard test functionality, though > > I'm not certain this is a path worth looking at, since its still a bit > > ugly. > > My number 1 concern is that 5.4-RELEASE 'Just Works' when you load it > onto a machine. Undocumented and under-documented work-arounds are very > hard to manage and don't help users that aren't intimately familiar with > the problem. This is a place where ("Alert! Don the asbestos skivvies > now!") adding an option to ("I'm warning you! Prepare for flamage!") > beastie.4th might be a good idea. > > Scott > Perhaps all of these kinds of things, could be rolled into one very ugly loader option, that enables pretty much every bugfix out there to atleast get things installed, a "If all else fails" option. The big problem with the R3000Zs was that you couldn't even boot the thing to start fixing it, and I think fixes like that would be the most critical. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 19:12:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8161F16A4CE for ; Mon, 21 Mar 2005 19:12:07 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B287F43D2F for ; Mon, 21 Mar 2005 19:12:06 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LJC4Y8011410; Mon, 21 Mar 2005 14:12:06 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 21 Mar 2005 14:11:58 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <2fd864e05032109304c2ad323@mail.gmail.com> <423F1236.4000401@samsco.org> In-Reply-To: <423F1236.4000401@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211411.58425.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 19:12:07 -0000 On Monday 21 March 2005 01:28 pm, Scott Long wrote: > Astrodog wrote: > >>>>>>>I was wondering if the R3000Z fixes have been committed to > >>>>>>> the RELENG_5 branch, I don't see anything on the lists > >>>>>>> about it. Should I expect 5.4 to work with the R3000 line? > >>>>>> > >>>>>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > >>>>>>latest snapshot and let us know. > >>>>>> > >>>>>>Thanks, > >>>>>> > >>>>>>Jung-uk Kim > >>>>> > >>>>>Is there any way that these systems can be detected at runtime > >>>>>and have the work-arounds be automatically activated? > >>>> > >>>>I believe DMI-based quirk table is the only way but we don't > >>>> want to do that, right? > >>>> > >>>>Jung-uk Kim > >>>> > >>>>>Scott > >>> > >>>Well, it's gross, but it's not impossible to do. Is there a > >>>technical reason why we wouldn't want this? > >> > >>The only technical reason that I can think of is some systems (e. > >> g., IBM e345 and e346 Opteron servers) have DMI structures in > >> ACPI NVS area, which is not accessible from early stage. If you > >> want to do something like that, you will have to add gross hack > >> in pmap.c to temporarily map it, I think. > >> > >>>Are there any alternatives, like detecting a signature in ACPI, > >>>either a text string or a certain bit of ASL bytecode? > >> > >>We already have the quirk for this broken BIOS. However, > >> keyboard probing happens way earlier to use this quirk. :-( > >> > >>Jung-uk Kim > >> > >>>Scott > > > > Something that came up originally, when this issue was first > > noticed, was trying to figure out what, if any platforms, would > > have problems if this was made to apply to all AMD64 machines, > > and use the flag to drive an opt-out. In as far as I'm aware, no > > AMD64-based machines are effected if you just "break" the > > keyboard test functionality, though I'm not certain this is a > > path worth looking at, since its still a bit ugly. > > My number 1 concern is that 5.4-RELEASE 'Just Works' when you load > it onto a machine. Undocumented and under-documented work-arounds > are very hard to manage and don't help users that aren't intimately > familiar with the problem. This is a place where ("Alert! Don the > asbestos skivvies now!") adding an option to ("I'm warning you! > Prepare for flamage!") beastie.4th might be a good idea. One possibility is adding DMI scan code in loader and passing BIOS ID strings to kernel because loader can easily call BIOS function calls. This won't require ugly hack in kernel space. Jung-uk Kim > Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 19:44:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FE1516A4CE for ; Mon, 21 Mar 2005 19:44:45 +0000 (GMT) Received: from web31005.mail.mud.yahoo.com (web31005.mail.mud.yahoo.com [68.142.200.168]) by mx1.FreeBSD.org (Postfix) with SMTP id B759643D39 for ; Mon, 21 Mar 2005 19:44:44 +0000 (GMT) (envelope-from yuval_levy@yahoo.com) Received: (qmail 12443 invoked by uid 60001); 21 Mar 2005 19:44:42 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=m/RW7+jlX4mDzTPku5BuSTxqEET/Dj3lJPDfsoEdfZn0vrDdDrmvW7oidx0e79VKq2dYqLmNuH7+1IMtl90auXVUFEFu+aip8jGna0Wy6EyjHc6AUzg7rNZlzoHOpvVjcgTr9Tn0XXF0ttI2CVEakDqggIsOEw+eTb+sEkJu18w= ; Message-ID: <20050321194442.12440.qmail@web31005.mail.mud.yahoo.com> Received: from [207.134.50.228] by web31005.mail.mud.yahoo.com via HTTP; Mon, 21 Mar 2005 11:44:41 PST Date: Mon, 21 Mar 2005 11:44:41 -0800 (PST) From: yuval levy To: freebsd-amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 19:44:45 -0000 Hello, has anybody had experience running FreeBSD on SuperMicro 6014P-8R? Is the Adaptec 2010S ZCR supported by FreeBSD? Thanks Yuv __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 19:57:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FFD816A4CE for ; Mon, 21 Mar 2005 19:57:50 +0000 (GMT) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 5ABCE43D41 for ; Mon, 21 Mar 2005 19:57:49 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 21 Mar 2005 19:57:48 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Mon, 21 Mar 2005 14:57:47 -0500 (EST) Message-ID: <3059.172.16.0.199.1111435067.squirrel@wettoast.dyndns.org> In-Reply-To: <20050321194442.12440.qmail@web31005.mail.mud.yahoo.com> References: <20050321194442.12440.qmail@web31005.mail.mud.yahoo.com> Date: Mon, 21 Mar 2005 14:57:47 -0500 (EST) From: "Mike Jakubik" To: "yuval levy" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 19:57:50 -0000 On Mon, March 21, 2005 2:44 pm, yuval levy said: > has anybody had experience running FreeBSD on SuperMicro 6014P-8R? > > Is the Adaptec 2010S ZCR supported by FreeBSD? Not using that board, but i do have a supermicro system with the Adaptec 2010S ZCR, it works great. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 20:08:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8FFC16A4CE for ; Mon, 21 Mar 2005 20:08:25 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8156243D4C for ; Mon, 21 Mar 2005 20:08:25 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so1219864wra for ; Mon, 21 Mar 2005 12:08:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=g9Ra1ZUFobI9sTZgJbwqc78fAWZ29hJGy9PGYfQAFzStb9Vg4JZFRP8dGICnt17Fc2HZzEVbcsJMuuSwG4so2cLRbX/CU3wUdsWr+w9xvLLSXdYBRN0B3/VQtG86I0m1iIrez4SjtD97z998aZgDJ5WJgx7GR4Eem6QPkT9lYN4= Received: by 10.54.37.72 with SMTP id k72mr3482868wrk; Mon, 21 Mar 2005 12:08:25 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 12:08:25 -0800 (PST) Message-ID: <2fd864e0503211208491d0307@mail.gmail.com> Date: Mon, 21 Mar 2005 12:08:25 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <423F1236.4000401@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211113.52233.jkim@niksun.com> <423EF3D2.9050205@samsco.org> <200503211141.40409.jkim@niksun.com> <2fd864e05032109304c2ad323@mail.gmail.com> <423F1236.4000401@samsco.org> Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 20:08:26 -0000 Something that has struck me over the past few hours, as I've worked on this machine, outside of the ACPI issue, and the keyboard issue, which are both pretty trivial fixes at this point, this is one of the better supported mobile FreeBSD platforms out there. Internal NIC was detected fine, PCMCIA works great, sound works, USB works, Firewire works, hell, the cardreader seems to work.... Not too many laptops can make that claim. If there was a way to automate those 2 problems away, this would be a great example for FreeBSD on mobile platforms. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 20:21:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AE0516A511 for ; Mon, 21 Mar 2005 20:21:25 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A3E43D55 for ; Mon, 21 Mar 2005 20:21:24 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LKLMNC013962; Mon, 21 Mar 2005 15:21:24 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, Astrodog Date: Mon, 21 Mar 2005 15:21:16 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <423F1236.4000401@samsco.org> <2fd864e0503211208491d0307@mail.gmail.com> In-Reply-To: <2fd864e0503211208491d0307@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211521.16318.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 20:21:25 -0000 On Monday 21 March 2005 03:08 pm, Astrodog wrote: > Something that has struck me over the past few hours, as I've > worked on this machine, outside of the ACPI issue, and the keyboard > issue, which are both pretty trivial fixes at this point, this is > one of the better supported mobile FreeBSD platforms out there. > Internal NIC was detected fine, PCMCIA works great, sound works, > USB works, Firewire works, hell, the cardreader seems to work.... > Not too many laptops can make that claim. If there was a way to > automate those 2 problems away, this would be a great example for > FreeBSD on mobile platforms. IMO, Acer Ferrari series laptops are pretty good with FreeBSD. Broadcom gigabit NIC, wireless (with NDISulator), Bluetooth, card reader, PCCard, audio, Xorg, etc. work out of the box. Jung-uk Kim > --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 21:18:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A5F216A4D3 for ; Mon, 21 Mar 2005 21:18:40 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0158E43D39 for ; Mon, 21 Mar 2005 21:18:40 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1488 invoked from network); 21 Mar 2005 21:18:39 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 21 Mar 2005 21:18:39 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2LLIPeT048944; Mon, 21 Mar 2005 16:18:33 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 21 Mar 2005 14:40:21 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <423F1236.4000401@samsco.org> <200503211411.58425.jkim@niksun.com> In-Reply-To: <200503211411.58425.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211440.21752.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.3 required=4.2 tests=ALL_TRUSTED,OPTING_OUT, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 21:18:40 -0000 On Monday 21 March 2005 02:11 pm, Jung-uk Kim wrote: > On Monday 21 March 2005 01:28 pm, Scott Long wrote: > > Astrodog wrote: > > >>>>>>>I was wondering if the R3000Z fixes have been committed to > > >>>>>>> the RELENG_5 branch, I don't see anything on the lists > > >>>>>>> about it. Should I expect 5.4 to work with the R3000 line? > > >>>>>> > > >>>>>>Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > >>>>>>latest snapshot and let us know. > > >>>>>> > > >>>>>>Thanks, > > >>>>>> > > >>>>>>Jung-uk Kim > > >>>>> > > >>>>>Is there any way that these systems can be detected at runtime > > >>>>>and have the work-arounds be automatically activated? > > >>>> > > >>>>I believe DMI-based quirk table is the only way but we don't > > >>>> want to do that, right? > > >>>> > > >>>>Jung-uk Kim > > >>>> > > >>>>>Scott > > >>> > > >>>Well, it's gross, but it's not impossible to do. Is there a > > >>>technical reason why we wouldn't want this? > > >> > > >>The only technical reason that I can think of is some systems (e. > > >> g., IBM e345 and e346 Opteron servers) have DMI structures in > > >> ACPI NVS area, which is not accessible from early stage. If you > > >> want to do something like that, you will have to add gross hack > > >> in pmap.c to temporarily map it, I think. > > >> > > >>>Are there any alternatives, like detecting a signature in ACPI, > > >>>either a text string or a certain bit of ASL bytecode? > > >> > > >>We already have the quirk for this broken BIOS. However, > > >> keyboard probing happens way earlier to use this quirk. :-( > > >> > > >>Jung-uk Kim > > >> > > >>>Scott > > > > > > Something that came up originally, when this issue was first > > > noticed, was trying to figure out what, if any platforms, would > > > have problems if this was made to apply to all AMD64 machines, > > > and use the flag to drive an opt-out. In as far as I'm aware, no > > > AMD64-based machines are effected if you just "break" the > > > keyboard test functionality, though I'm not certain this is a > > > path worth looking at, since its still a bit ugly. > > > > My number 1 concern is that 5.4-RELEASE 'Just Works' when you load > > it onto a machine. Undocumented and under-documented work-arounds > > are very hard to manage and don't help users that aren't intimately > > familiar with the problem. This is a place where ("Alert! Don the > > asbestos skivvies now!") adding an option to ("I'm warning you! > > Prepare for flamage!") beastie.4th might be a good idea. > > One possibility is adding DMI scan code in loader and passing BIOS ID > strings to kernel because loader can easily call BIOS function calls. > This won't require ugly hack in kernel space. I like this approach better. We already provide hints to ACPI via the loader. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 22:48:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 716B016A4CE for ; Mon, 21 Mar 2005 22:48:46 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E9C043D31 for ; Mon, 21 Mar 2005 22:48:46 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IDQ006S14OBEP@VL-MO-MR007.ip.videotron.ca> for freebsd-amd64@freebsd.org; Mon, 21 Mar 2005 17:48:12 -0500 (EST) Date: Mon, 21 Mar 2005 17:48:12 -0500 From: Nicolas Blais In-reply-to: <200503211049.11110.jkim@niksun.com> To: freebsd-amd64@freebsd.org Message-id: <200503211748.12817.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 22:48:46 -0000 What about the PowerNow! kernel module? Is that still required? Thanks, Nicolas. On March 21, 2005 10:49, Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > I was wondering if the R3000Z fixes have been committed to the > > RELENG_5 branch, I don't see anything on the lists about it. Should > > I expect 5.4 to work with the R3000 line? > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest > snapshot and let us know. > > Thanks, > > Jung-uk Kim > > > --- Harrison Grundy > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 22:53:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FEAC16A4CF for ; Mon, 21 Mar 2005 22:53:39 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE5A43D4C for ; Mon, 21 Mar 2005 22:53:38 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2LMraVJ019607; Mon, 21 Mar 2005 17:53:38 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 21 Mar 2005 17:53:29 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <200503211748.12817.nb_root@videotron.ca> In-Reply-To: <200503211748.12817.nb_root@videotron.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503211753.29889.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/778/Mon Mar 21 05:48:43 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 22:53:39 -0000 On Monday 21 March 2005 05:48 pm, Nicolas Blais wrote: > What about the PowerNow! kernel module? Is that still required? If you are okay with 800MHz, no. ;-) You can grab the latest powernow-k8 driver from: http://www.poupinou.org/cpufreq/bsd/powernow.tar.gz Jung-uk Kim > Thanks, > Nicolas. > > On March 21, 2005 10:49, Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > I was wondering if the R3000Z fixes have been committed to the > > > RELENG_5 branch, I don't see anything on the lists about it. > > > Should I expect 5.4 to work with the R3000 line? > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > latest snapshot and let us know. > > > > Thanks, > > > > Jung-uk Kim > > > > > --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 23:28:33 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7448316A4CE for ; Mon, 21 Mar 2005 23:28:33 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0244C43D46 for ; Mon, 21 Mar 2005 23:28:33 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so1318184wri for ; Mon, 21 Mar 2005 15:28:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=d1bqQgGZVM5CXLOdnJlstKsRmu0gaeflMOZtsN8ArANN+LceERIpZI+qWzGpucj6jyqoX3Gq7ereCOw1jVWVBjOOki79LFrFaQovzN9fYb0sRMwKhVW0pZMx+YZXaSTouFVK4KM7SNoBEp4kD+kTo1+wAwFPnAFrp3tJeIVT+vs= Received: by 10.54.23.3 with SMTP id 3mr3527556wrw; Mon, 21 Mar 2005 15:28:32 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 15:28:32 -0800 (PST) Message-ID: <2fd864e05032115283dc09da7@mail.gmail.com> Date: Mon, 21 Mar 2005 15:28:32 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <200503211753.29889.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <200503211748.12817.nb_root@videotron.ca> <200503211753.29889.jkim@niksun.com> Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 23:28:33 -0000 On Mon, 21 Mar 2005 17:53:29 -0500, Jung-uk Kim wrote: > On Monday 21 March 2005 05:48 pm, Nicolas Blais wrote: > > What about the PowerNow! kernel module? Is that still required? > > If you are okay with 800MHz, no. ;-) You can grab the latest > powernow-k8 driver from: > > http://www.poupinou.org/cpufreq/bsd/powernow.tar.gz > > Jung-uk Kim > > > Thanks, > > Nicolas. > > > > On March 21, 2005 10:49, Jung-uk Kim wrote: > > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > > I was wondering if the R3000Z fixes have been committed to the > > > > RELENG_5 branch, I don't see anything on the lists about it. > > > > Should I expect 5.4 to work with the R3000 line? > > > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > > latest snapshot and let us know. > > > > > > Thanks, > > > > > > Jung-uk Kim > > > > > > > --- Harrison Grundy > _______________________________________________ > 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" > Powernow works great, by the way. I'm upgrading to 6-CURRENT now because I need the ath driver for AMD64 for a wireless card I have, but I tested things out in 5.4-PRERELEASE, and it works great once these few, relatively easy to fix issues are resolved. From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 21 23:34:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D92D16A4CE for ; Mon, 21 Mar 2005 23:34:02 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 727C543D48 for ; Mon, 21 Mar 2005 23:33:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2LNWt1m058739; Mon, 21 Mar 2005 16:32:55 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <423F5941.5090707@samsco.org> Date: Mon, 21 Mar 2005 16:31:13 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: yuval levy References: <20050321194442.12440.qmail@web31005.mail.mud.yahoo.com> In-Reply-To: <20050321194442.12440.qmail@web31005.mail.mud.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 23:34:02 -0000 yuval levy wrote: > Hello, > has anybody had experience running FreeBSD on > SuperMicro 6014P-8R? > No, but I see no reason why it wouldn't work. > Is the Adaptec 2010S ZCR supported by FreeBSD? Yes. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 02:50:22 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 054B316A4CE for ; Tue, 22 Mar 2005 02:50:22 +0000 (GMT) Received: from mxsf34.cluster1.charter.net (mxsf34.cluster1.charter.net [209.225.28.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 966EA43D3F for ; Tue, 22 Mar 2005 02:50:21 +0000 (GMT) (envelope-from lankfordandrew@charter.net) Received: from mxip17.cluster1.charter.net (mxip17a.cluster1.charter.net [209.225.28.147])j2M2oKWW010714 for ; Mon, 21 Mar 2005 21:50:20 -0500 Received: from cpe-24-181-244-212.san.nc.charter.com (HELO [192.168.15.105]) (24.181.244.212) by mxip17.cluster1.charter.net with ESMTP; 21 Mar 2005 21:50:16 -0500 X-Ironport-AV: i="3.91,108,1110171600"; d="scan'208"; a="842824452:sNHT403101592" Message-ID: <423F87EE.6000605@charter.net> Date: Mon, 21 Mar 2005 21:50:22 -0500 From: Andrew Lankford User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Broadcom wireless NIC on R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 02:50:22 -0000 After getting ACPI working with Kim's hints on this list and waiting for several useful commits to -STABLE, ACPI works and my parallel port along with it. That leaves the onboard Wifi capability as the only thing I can't use on FreeBSD. The realtek NIC has always worked fine, but I only recently got the kernel to recognize the Broadcom wireless NIC. Using the 64-bit ndisulator and a downloaded windows driver that was linked to on this list a month or two ago, I can load the right modules and get the right device probe messages, etc. The interface shows up in ifconfig too, but it's always "no-carrier", no matter what settings I try, and the little blue WiFi indicator light doesn't go on like it does in Windows. According to the manual, the antenna is turned on and off by the toggle button right next to the indicator light. I take that to mean that there's some sort of interface that physically controls signals to/from the antenna, and that it's set to "off" by default in FreeBSD. Ergo no connection to the antenna --> no carrier --> no joy. Has anyone tackled this problem before? Google hasn't given me any leads. Andrew Lankford From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 02:57:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 325F916A4CE for ; Tue, 22 Mar 2005 02:57:38 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4E1E43D48 for ; Tue, 22 Mar 2005 02:57:37 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1544858wra for ; Mon, 21 Mar 2005 18:57:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iNECvWgRMCRAd3Rj6CwUWP5Uxh2kNyqqQJ2IzcUTe2o/SwgYXV1PKR3seu5zuKnAi8tLR81hCBd1W6CRcEpety7Yp+AzVunVMza4jjgYcvoVOGCWjK8XS1K1gTWpaQ4o/Ut16Vwhic916DAElaCNwHqzMGn0NvUfg3Wd61c4WfY= Received: by 10.54.23.69 with SMTP id 69mr834168wrw; Mon, 21 Mar 2005 18:57:37 -0800 (PST) Received: by 10.54.40.69 with HTTP; Mon, 21 Mar 2005 18:57:37 -0800 (PST) Message-ID: <2fd864e050321185711297839@mail.gmail.com> Date: Mon, 21 Mar 2005 18:57:37 -0800 From: Astrodog To: Andrew Lankford In-Reply-To: <423F87EE.6000605@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <423F87EE.6000605@charter.net> cc: freebsd-amd64@freebsd.org Subject: Re: Broadcom wireless NIC on R3000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 02:57:38 -0000 On Mon, 21 Mar 2005 21:50:22 -0500, Andrew Lankford wrote: > > After getting ACPI working with Kim's hints on this list and waiting for > several useful commits to -STABLE, ACPI works and my parallel port along > with it. That leaves the onboard Wifi capability as the only thing I > can't use on FreeBSD. > > The realtek NIC has always worked fine, but I only recently got the > kernel to recognize the Broadcom wireless NIC. Using the 64-bit > ndisulator and a downloaded windows driver that was linked to on this > list a month or two ago, I can load the right modules and get the right > device probe messages, etc. The interface shows up in ifconfig too, > but it's always "no-carrier", no matter what settings I try, and the > little blue WiFi indicator light doesn't go on like it does in Windows. > > According to the manual, the antenna is turned on and off by the toggle > button right next to the indicator light. I take that to mean that > there's some sort of interface that physically controls signals to/from > the antenna, and that it's set to "off" by default in FreeBSD. Ergo no > connection to the antenna --> no carrier --> no joy. > > Has anyone tackled this problem before? Google hasn't given me any leads. > > Andrew Lankford > I suspect its trivial stuff if that's your stopping point. I can confirm that ath (Proxim card) and a wi (Netgear) work great. Perhaps in the files NDIS generates it mentions something, a tunable, perhaps? From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 08:02:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2679416A4CE; Tue, 22 Mar 2005 08:02:43 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA89E43D54; Tue, 22 Mar 2005 08:02:41 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.13.3/8.13.3) with ESMTP id j2M82cuD018938 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 22 Mar 2005 09:02:38 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.3/8.13.3/Submit) id j2M82Yif018930; Tue, 22 Mar 2005 09:02:34 +0100 (CET) Date: Tue, 22 Mar 2005 09:02:34 +0100 From: Divacky Roman To: Jung-uk Kim Message-ID: <20050322080234.GA18572@stud.fit.vutbr.cz> References: <20050316093956.GA32442@stud.fit.vutbr.cz> <200503161154.04555.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503161154.04555.jkim@niksun.com> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 cc: amd64@freebsd.org cc: current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: amd64 irq assigning related problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 08:02:43 -0000 On Wed, Mar 16, 2005 at 11:54:03AM -0500, Jung-uk Kim wrote: > On Wednesday 16 March 2005 04:39 am, Divacky Roman wrote: > > Hi, > > > > my amd64 box with nforce3 chipset doesnt boot with acpi enabled. > > when I boot with acpi disabled my atkbd (attached to ps/2) runs > > VERY slow (about 1cps), I think its caused by atkbdc not having irq > > assigned... > > Turn on ACPI and do this from loader: > > set debug.acpi.quirks=4 > > or add the following line in /boot/loader.conf: > > debug.acpi.quirks=4 when I set this... it proceeds further in booting but ata probe routine time outs ie. I am not able to mount / (its on sata disk) typing on keyboard seems to be "normal" (its at slow keyrate but I think its ok now) any other suggest? should I provide any info? (I am able to boot without acpi so I can provide some I think) roman From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 08:02:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2679416A4CE; Tue, 22 Mar 2005 08:02:43 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA89E43D54; Tue, 22 Mar 2005 08:02:41 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.13.3/8.13.3) with ESMTP id j2M82cuD018938 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 22 Mar 2005 09:02:38 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.3/8.13.3/Submit) id j2M82Yif018930; Tue, 22 Mar 2005 09:02:34 +0100 (CET) Date: Tue, 22 Mar 2005 09:02:34 +0100 From: Divacky Roman To: Jung-uk Kim Message-ID: <20050322080234.GA18572@stud.fit.vutbr.cz> References: <20050316093956.GA32442@stud.fit.vutbr.cz> <200503161154.04555.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503161154.04555.jkim@niksun.com> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 cc: amd64@freebsd.org cc: current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: amd64 irq assigning related problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 08:02:43 -0000 On Wed, Mar 16, 2005 at 11:54:03AM -0500, Jung-uk Kim wrote: > On Wednesday 16 March 2005 04:39 am, Divacky Roman wrote: > > Hi, > > > > my amd64 box with nforce3 chipset doesnt boot with acpi enabled. > > when I boot with acpi disabled my atkbd (attached to ps/2) runs > > VERY slow (about 1cps), I think its caused by atkbdc not having irq > > assigned... > > Turn on ACPI and do this from loader: > > set debug.acpi.quirks=4 > > or add the following line in /boot/loader.conf: > > debug.acpi.quirks=4 when I set this... it proceeds further in booting but ata probe routine time outs ie. I am not able to mount / (its on sata disk) typing on keyboard seems to be "normal" (its at slow keyrate but I think its ok now) any other suggest? should I provide any info? (I am able to boot without acpi so I can provide some I think) roman From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 13:37:26 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9E1516A4CE for ; Tue, 22 Mar 2005 13:37:26 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1176743D5E for ; Tue, 22 Mar 2005 13:37:26 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 13B7078C7D for ; Tue, 22 Mar 2005 08:39:15 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74780-08 for ; Tue, 22 Mar 2005 08:39:02 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 178DB78C79 for ; Tue, 22 Mar 2005 08:39:01 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 33F3128DFA; Tue, 22 Mar 2005 08:37:19 -0500 (EST) Date: Tue, 22 Mar 2005 08:37:19 -0500 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050322133719.GX697@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20050319021654.GD27012@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050319021654.GD27012@afflictions.org> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: java/jdk15 help [SOLVED?] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 13:37:27 -0000 Thus spake Damian Gerow (dgerow@afflictions.org) [19/03/05 08:44]: : I've noticed that a few people here have successfully gotten a native : java/jdk15 built. Can one of those people lend me a hand, please? : : I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky problem : thrown by the jdk15 build. But afterwards, all I seem to get is hung javac : processes, each consuming 100% of CPU. By some ridiculous fluke, I tried a build with WITH_IPV6 defined. It built without any issue whatsoever, and has now been installed. So I at least have a JDK at this point; now to try to figure out how/why it's failing when I don't want IPV6 support. From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 19:05:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EC2C16A4CE for ; Tue, 22 Mar 2005 19:05:30 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AA5943D1F for ; Tue, 22 Mar 2005 19:05:30 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so1732810wri for ; Tue, 22 Mar 2005 11:05:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=osYSh91z/by/8X9z43FqcVQbGdxBUVDJGVFpom6ViuvPbL5EUA7zuDLwSusLO0ep60Jxoux4enYRuUw+vKQGsKi5HY4NlV7AIbuYEignJubOPQAnybz3b3YUc84g2TlABkJ6v+m0BsBUtAVeio+nYPb2HXuEMd7cmcCden7K5S0= Received: by 10.54.51.78 with SMTP id y78mr4484576wry; Tue, 22 Mar 2005 11:05:29 -0800 (PST) Received: by 10.54.40.69 with HTTP; Tue, 22 Mar 2005 11:05:29 -0800 (PST) Message-ID: <2fd864e050322110515c67d29@mail.gmail.com> Date: Tue, 22 Mar 2005 19:05:29 +0000 From: Astrodog To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: AMD64 and nVidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 19:05:30 -0000 Is there any word on an nVidia AMD64 FreeBSD driver? From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 20:11:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18DCB16A4CF for ; Tue, 22 Mar 2005 20:11:46 +0000 (GMT) Received: from styx.aic.net (styx.aic.net [195.250.64.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4393543D49 for ; Tue, 22 Mar 2005 20:11:45 +0000 (GMT) (envelope-from ran@styx.aic.net) Received: from ran by styx.aic.net with local (Exim 4.44 (FreeBSD)) id 1DDpj0-000J38-0O; Wed, 23 Mar 2005 00:11:38 +0400 In-Reply-To: <423F5941.5090707@samsco.org> To: Scott Long Date: Wed, 23 Mar 2005 00:11:38 +0400 (AMT) X-PGP: http://styx.aic.net/pgpkeys/ran.asc X-NCC-Regid: am.nic X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: From: Hrant Dadivanyan cc: yuval levy cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 20:11:46 -0000 > yuval levy wrote: > > Hello, > > has anybody had experience running FreeBSD on > > SuperMicro 6014P-8R? > > > > No, but I see no reason why it wouldn't work. > > > Is the Adaptec 2010S ZCR supported by FreeBSD? > > Yes. > Is the Adaptec 2010S ZCR supported by amd64 port ? Thank you, hrant > Scott > _______________________________________________ > 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" > -- Hrant Dadivanyan (aka Ran d'Adi) ran(at)amnic.net /* "Feci quod potui, faciant meliora potentes." */ ran(at)styx.aic.net From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 20:16:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D33D16A4CF for ; Tue, 22 Mar 2005 20:16:59 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 470FF43D3F for ; Tue, 22 Mar 2005 20:16:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2MKFiCI063831; Tue, 22 Mar 2005 13:15:44 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42407D36.7050109@samsco.org> Date: Tue, 22 Mar 2005 13:16:54 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hrant Dadivanyan References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: yuval levy cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 20:16:59 -0000 Hrant Dadivanyan wrote: >>yuval levy wrote: >> >>>Hello, >>>has anybody had experience running FreeBSD on >>>SuperMicro 6014P-8R? >>> >> >>No, but I see no reason why it wouldn't work. >> >> >>>Is the Adaptec 2010S ZCR supported by FreeBSD? >> >>Yes. >> > > > Is the Adaptec 2010S ZCR supported by amd64 port ? > > Thank you, > hrant > The asr driver for the all of these cards is not very 64-bit clean. It _might_ work if you don't excede 4GB of RAM, but I really can't say how reliable it would be. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 20:21:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8040E16A4CE for ; Tue, 22 Mar 2005 20:21:09 +0000 (GMT) Received: from styx.aic.net (styx.aic.net [195.250.64.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B771A43D53 for ; Tue, 22 Mar 2005 20:21:08 +0000 (GMT) (envelope-from ran@styx.aic.net) Received: from ran by styx.aic.net with local (Exim 4.44 (FreeBSD)) id 1DDps7-000K0H-HW; Wed, 23 Mar 2005 00:21:03 +0400 In-Reply-To: <42407D36.7050109@samsco.org> To: Scott Long Date: Wed, 23 Mar 2005 00:21:03 +0400 (AMT) X-PGP: http://styx.aic.net/pgpkeys/ran.asc X-NCC-RegID: am.nic X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: From: Hrant Dadivanyan cc: yuval levy cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on SuperMicro 6014P-8R X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 20:21:09 -0000 > Hrant Dadivanyan wrote: > > > > > > Is the Adaptec 2010S ZCR supported by amd64 port ? > > > > Thank you, > > hrant > > > > The asr driver for the all of these cards is not very 64-bit > clean. It _might_ work if you don't excede 4GB of RAM, but I > really can't say how reliable it would be. > > Scott > Thanks! Last time I tried with 5.3-RELEASE, it paniced as soon as asr was probed. Will try again with 5.4 . Thank you, hrant -- Hrant Dadivanyan (aka Ran d'Adi) ran(at)amnic.net /* "Feci quod potui, faciant meliora potentes." */ ran(at)styx.aic.net From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 22 23:30:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0830016A4CE for ; Tue, 22 Mar 2005 23:30:13 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55B7943D5C for ; Tue, 22 Mar 2005 23:30:12 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so13641rng for ; Tue, 22 Mar 2005 15:30:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=eG5FvXcYOFuF86WRbIyT2nGlWm5mubaBmdbA2dEFpEEOAkuCcRogIGUaKM26L6u4zCCOzGS72v/xvu01cNhxUf0SLmgNeCZ3d2sWl3qNWHacoFlvfM/Z3daKKptPxqEg2ox01sz1dgs7QPgn0qut9Z1pSGbtgmfeQEQGPt+oXKI= Received: by 10.38.165.79 with SMTP id n79mr40157rne; Tue, 22 Mar 2005 15:30:11 -0800 (PST) Received: by 10.38.74.23 with HTTP; Tue, 22 Mar 2005 15:30:11 -0800 (PST) Message-ID: Date: Wed, 23 Mar 2005 00:30:11 +0100 From: Gert Cuykens To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: nvidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 23:30:13 -0000 Do the nvidia display drivers work on amd64 ? From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 01:31:22 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 116D116A4CE for ; Wed, 23 Mar 2005 01:31:22 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D77743D4C for ; Wed, 23 Mar 2005 01:31:21 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 24A8578C64 for ; Tue, 22 Mar 2005 20:31:20 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32438-10 for ; Tue, 22 Mar 2005 20:31:16 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 33BDA78C62 for ; Tue, 22 Mar 2005 20:31:16 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 556EB28DFA; Tue, 22 Mar 2005 20:31:26 -0500 (EST) Date: Tue, 22 Mar 2005 20:31:26 -0500 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050323013126.GH53316@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: nvidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 01:31:22 -0000 Thus spake Gert Cuykens (gert.cuykens@gmail.com) [22/03/05 18:30]: : Do the nvidia display drivers work on amd64 ? Quite well, actually. Just not with the binary driver supplied by nVidia. In the meantime, you can use the open-source 'nv' driver with neither issue, nor hardware-accelerrated 3D. I have no clue when nVidia will be releasing a driver, so don't ask. - Damian From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 19:34:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1387016A4CF for ; Wed, 23 Mar 2005 19:34:41 +0000 (GMT) Received: from web41804.mail.yahoo.com (web41804.mail.yahoo.com [66.218.93.138]) by mx1.FreeBSD.org (Postfix) with SMTP id 99A3F43D46 for ; Wed, 23 Mar 2005 19:34:40 +0000 (GMT) (envelope-from drumslayer2@yahoo.com) Received: (qmail 84861 invoked by uid 60001); 23 Mar 2005 19:34:39 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=UrQJoL63mL62orEyPpsDT9ijWUSt/L0rz40iyjPZDSA+NSKvIESj/8xyxOuOPgjRLFBU7a+C/3z+ei+REMD0QO8gblcE99MRi4Q32R4VpY9lRcVdX4m0Dv82HKjbzDxOJ22Tm6CwZqdjTi4ollJMLz6GrW1TQUsR7FYIDybsQAg= ; Message-ID: <20050323193439.84859.qmail@web41804.mail.yahoo.com> Received: from [67.112.21.27] by web41804.mail.yahoo.com via HTTP; Wed, 23 Mar 2005 11:34:38 PST Date: Wed, 23 Mar 2005 11:34:38 -0800 (PST) From: NMH To: questions , amd MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Panic With MPT driver on Opteron System X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 19:34:41 -0000 Hello I am having a odd problem I hope someone can help with. I have a TYAN 2882 board with 4 gigs of memory and a single Opteron 248 Processor. I am using an Infortrend RAID controller that won't play nice with Adaptec at 320 speeds so I am using an LSI 1030 based PCI-X SCSI card instead of the built in Adaptec. Hence the mpt driver. The system is FreeBSD 5.4-PRERELEASE from March 2nd. The system runs very fast but when testing under somewhat heavy load the system will panic and freeze with: Panic: mpt_get_request: corrupted request free list (ccb) It was also reported that when trying to do a ps auxw it would sometimes (never happened to me) report that it was out of inodes. Which is insane. A screen capture of the frozen console can be seen at: http://pic2.picturetrail.com/VOL965/3391974/6964630/90153559.jpg This seems similiar to reports on both FreeBSD and NetBSD like: http://mail-index.netbsd.org/netbsd-bugs/2004/03/03/0004.html And http://mail-index.netbsd.org/netbsd-bugs/2004/02/12/0003.html And: http://lists.freebsd.org/pipermail/freebsd-scsi/2003-April/000058.html Any assistance would be appreciatted. Thanks! N. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 19:42:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0612816A4D0 for ; Wed, 23 Mar 2005 19:42:19 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id C45A243D5E for ; Wed, 23 Mar 2005 19:42:18 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 7FB31F3EC3 for ; Wed, 23 Mar 2005 11:42:18 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00633-06 for ; Wed, 23 Mar 2005 11:42:17 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 82EFCF1855 for ; Wed, 23 Mar 2005 11:42:17 -0800 (PST) From: Sean McNeil To: amd64@freebsd.org Content-Type: text/plain Date: Wed, 23 Mar 2005 11:42:17 -0800 Message-Id: <1111606937.71972.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: Abiword crashes on save X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 19:42:19 -0000 Can anyone else test this on an amd64 system to verify my results: Open Abiword. File->"New using template..." select Fax-coversheet.awt hit the save button. Any feedback would be appreciated. Thanks, Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 19:50:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84CF816A4CE; Wed, 23 Mar 2005 19:50:50 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 056FC43D1F; Wed, 23 Mar 2005 19:50:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2NJnPsQ069508; Wed, 23 Mar 2005 12:49:25 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4241C7F0.4030108@samsco.org> Date: Wed, 23 Mar 2005 12:48:00 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: NMH References: <20050323193439.84859.qmail@web41804.mail.yahoo.com> In-Reply-To: <20050323193439.84859.qmail@web41804.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: questions cc: amd Subject: Re: Panic With MPT driver on Opteron System X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 19:50:50 -0000 NMH wrote: > Hello > I am having a odd problem I hope someone can help > with. > > I have a TYAN 2882 board with 4 gigs of memory and a > single Opteron 248 Processor. I am using an Infortrend > RAID controller that won't play nice with Adaptec at > 320 speeds so I am using an LSI 1030 based PCI-X SCSI > card instead of the built in Adaptec. Hence the mpt > driver. The system is FreeBSD 5.4-PRERELEASE from > March 2nd. > > The system runs very fast but when testing under > somewhat heavy load the system will panic and freeze > with: > Panic: mpt_get_request: corrupted request free list > (ccb) > It was also reported that when trying to do a ps auxw > it would sometimes (never happened to me) report that > it was out of inodes. Which is insane. > > A screen capture of the frozen console can be seen > at: > > http://pic2.picturetrail.com/VOL965/3391974/6964630/90153559.jpg > > This seems similiar to reports on both FreeBSD and > NetBSD like: > > http://mail-index.netbsd.org/netbsd-bugs/2004/03/03/0004.html > And > http://mail-index.netbsd.org/netbsd-bugs/2004/02/12/0003.html > And: > http://lists.freebsd.org/pipermail/freebsd-scsi/2003-April/000058.html > > Any assistance would be appreciatted. > > Thanks! > > N. > I think that you're seeing the effects of the driver having extremely broken error recovery. This is a known problem, and a fix will likely be going into the tree soon. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 21:06:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6920616A4CF for ; Wed, 23 Mar 2005 21:06:12 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0BC043D2D for ; Wed, 23 Mar 2005 21:06:11 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so288066rng for ; Wed, 23 Mar 2005 13:06:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=lKbRFj2BoEmM7bfgEhPpQqgWzFqPgDurWd2ElavqjdByvEI5F5PX3+1AUgzh8DL7y4olpN0xRIB1TaTADHADiZwZmw7LMBwBWKLg7BUoBEh+9Bmp2+I1j4M0jq7Y4acTmJ5jEUOatOd+Ga9Yn4siZWGDPGhaPfDWmHJdE6FB26w= Received: by 10.38.59.6 with SMTP id h6mr711946rna; Wed, 23 Mar 2005 13:06:11 -0800 (PST) Received: by 10.38.74.23 with HTTP; Wed, 23 Mar 2005 13:06:11 -0800 (PST) Message-ID: Date: Wed, 23 Mar 2005 22:06:11 +0100 From: Gert Cuykens To: freebsd-amd64@freebsd.org In-Reply-To: <20050323013126.GH53316@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050323013126.GH53316@afflictions.org> Subject: Re: nvidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 21:06:12 -0000 On Tue, 22 Mar 2005 20:31:26 -0500, Damian Gerow wrote: > Thus spake Gert Cuykens (gert.cuykens@gmail.com) [22/03/05 18:30]: > : Do the nvidia display drivers work on amd64 ? > > Quite well, actually. Just not with the binary driver supplied by nVidia. > In the meantime, you can use the open-source 'nv' driver with neither issue, > nor hardware-accelerrated 3D. > > I have no clue when nVidia will be releasing a driver, so don't ask. > At least the support is better then ATI :( From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 21:31:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DC6516A4CE for ; Wed, 23 Mar 2005 21:31:25 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBE9643D39 for ; Wed, 23 Mar 2005 21:31:24 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so293471rng for ; Wed, 23 Mar 2005 13:31:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=snO1R+tHhz8/ikym7qTY1JSdSRR5z41qt/MJZ02kmO+QJ5QkP4iSuiNt1FnajUN3GoKheHea8YujoD/2XAxs0JmbRiZFs0slAXtcoqElKR2Iqo6pVWQkxcNXVtCgNbWEONmv2FhxP+pfclMTmoQLc46/fnEv6nI7bN8Kwok9gYg= Received: by 10.38.72.59 with SMTP id u59mr934974rna; Wed, 23 Mar 2005 13:31:24 -0800 (PST) Received: by 10.38.74.23 with HTTP; Wed, 23 Mar 2005 13:31:23 -0800 (PST) Message-ID: Date: Wed, 23 Mar 2005 22:31:23 +0100 From: Gert Cuykens To: Astrodog In-Reply-To: <2fd864e050322110515c67d29@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e050322110515c67d29@mail.gmail.com> cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 and nVidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 21:31:25 -0000 On Tue, 22 Mar 2005 19:05:29 +0000, Astrodog wrote: > Is there any word on an nVidia AMD64 FreeBSD driver? Yes, that i does not excist :) From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 21:45:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0FD616A4CE for ; Wed, 23 Mar 2005 21:45:39 +0000 (GMT) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14A1B43D5A for ; Wed, 23 Mar 2005 21:45:39 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by smtp-gw-cl-d.dmv.com (8.12.10/8.12.10) with ESMTP id j2NM2tWa089442 for ; Wed, 23 Mar 2005 17:02:55 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: freebsd-amd64@freebsd.org In-Reply-To: <1110895353.4291.16.camel@lanshark.dmv.com> References: <1110847561.3412.38.camel@lanshark.dmv.com> <1110895353.4291.16.camel@lanshark.dmv.com> Content-Type: text/plain Date: Wed, 23 Mar 2005 16:45:40 -0500 Message-Id: <1111614340.10569.22.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 Subject: Re: amr performance woes and a bright side [UPDATE] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 21:45:39 -0000 On Tue, 2005-03-15 at 09:02 -0500, Sven Willenberger wrote: > On Mon, 2005-03-14 at 21:59 -0700, Scott Long wrote: > > Sven Willenberger wrote: > > > I have been testing a new box for utlimate use as a postgresql server: > > > dual opteron (2.2GHz), 8G RAM, LSI 320-2x megaraid (battery-backed > > > memory) with 2 single 73 GB drives and an 8x146GB RAID 0+1 array > > > (hitachi U320 10k RPM). In doing so I have also tested the amd64 > > > 5.3-stable release againt gentoo x86_64 and Fedora FC3/x86_64. > > > > > > First the bad news: > > > > > > The linux boxen were configured with the postgres data drives on the > > > raid 0+1 using XFS with a separate pg_xlog on a different drive. Both > > > gentoo and FC3 were using 2.6.x kernels using the x86_64 distro. > > > pgbench was initialized using no scaling factor (1 mill rows), scaling > > > 10 (10 million) and 100. > > > With no scaling the linux boxen hit about 160 tps using 10 connections > > > and 1000 -2000 transactions. > > > The BSD system hit 100-120 tps. This is a difference I could potentially > > > live with. Now enter the scaled tables: > > > Linux systems hit marks of 450+ tps when pgbenching againt millions of > > > rows while the BSD box stayed at 100 tps or worse .. dipping as low as > > > 90 tps. > > > > > > Bonnie benchmarks: > > > Linux: > > > Sequential output: Per Char = 65000 K/sec, Block = 658782 K/sec, Rewrite > > > = 639654 K/sec > > > Sequential input: Per Char = 66240 K/sec, Block = 1278993 K/sec > > > Sequential create: create 641/sec , read n/a, delete 205/sec > > > Random create: create 735/sec, read n/a, delete 126/sec > > > > > > BSD: > > > Sequential output: Per Char = 370K/sec (!!), block = 132281 K/sec, > > > Rewrite = 124070 K/sec > > > Sequential input: Per Char = 756 K/sec, block = 700402 K/sec > > > Sequential create: create 139/sec, read 6308/seec, delete n/a > > > Random create: create 137/sec, read 5877/sec, delete n/a > > > > > > the bonnie tests were run several times with similar results. > > > > > > It would seem to me that the pgbench marks and tests are being hampered > > > by comparatively poor I/O to the raid array and disks under the amr > > > driver control. I am hoping there are some tweaks that I could do or > > > perhaps some patches to the driver in -CURRENT that could be > > > applied/backported/MFC'ed to try and improve this performance. > > > > > > Oh, the "bright" side? FreeBSD is the only OS here that didn't kernel > > > Oops due to memory allocation issues, or whatever caused them (the > > > backtrace showed kmalloc). That may be because of the XFS file system (I > > > didn't try EXT3 or its kin) or because of issues with LSI and the linux > > > kernel or who knows what. I am hoping to get the stability and OS > > > performance of FreeBSD and the raw disk performance witnessed in the > > > Linux systems all rolled up into one. Help? > > > > > > Sven > > > > > > > First of all, are you using the same hardware and just switching the OS? > > Are you sure that the RAID and disk cache settings are identical? > > Second, some of the Linux numbers are very hard to believe; PCI-X has a > > theoretical bandwidth of 1066MB/sec, so it's highly unlikely that you're > > going to get 1249MB/sec out of it in the block read test. bonnie is an > > excellent tool for testing the randomness of cache effects and memory > > bandwidth, it's not so good at testing actual I/O performance =-) > > > > So setting aside the bonnie tests, the PQSQL stats do indeed show a > > problem. Is PGSQL threaded? If so, you might be running into some of > > the threading performance problems that are well known and are being > > worked on. I don't know a whole lot about PGSQL or the tests that you > > are talking about, but if you had an easy recipe for duplicating your > > test environment, I'd like to experiment some myself. > > > > Scott > > Yes, these tests were done on the same hardware, with the same hardware > raid configuration with fresh OS installs for each battery of tests. The > bonnie numbers do seem a bit out of whack upon closer scrutiny. > > As far as setting up PGSQL, in each case it was set up from packages > (FreeBSD ports, Gentoo emerge, FC3 yum) and the postgresql.conf file was > adjusted to use the same set of values for memory, etc. > > pgbench (postgresql-contrib) was run as follows for testing: > pgbench -i -U postgres/pgsql pgtest (where the User is either postgres > or pgsql depending on platform and pgtest is the test db set up using > createdb) > pgbench -c 10 -t 1000 -U pgsql pgtest > pgbench -c 10 -t 4000 -U pgsql pgtest > pgbench -c 10 -t 10000 -U pgsql pgtest > pgbench -i -s 10 -U pgsql pgtest (scaling factor of 10 to increase the > table sizes for benchmarking) > pgbench -c 10 -t 1000 etc ...... > pgbench -i -s 100 -U pgsql pgtest > > Sven > Just thought I would share this: After moving around to a few more OSes (including Solaris 10 which witnessed performance numbers simlar to those of FreeBSD) one of the hard drives in the array failed; I suspect it was a factory defective drive as it was brand new -- not sure if that impacted performance or not (in the original tests) but it may have as the controller tried to keep skipping past bad sectors. Anyway, now with a battery backed raid controller in place and 6 functioning drives (raid striped across 3 pairs of mirrors) and write-back enabled I am seeing the pgbench give me readings of 650+ tps!! :-) These numbers would indicate to me (as did the odd bonnie++ numbers) that the 2.6 linux kernel with xfs was using some heavy duty write caching. I suspect the kernel panics I was seeing were the result of poor handling of the defective drive when trying to fsync or memory mismanagement of the cacched write data. At any rate, I am glad I can stay with the FreeBSD option now. Sven From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 21:49:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC4D416A4CE; Wed, 23 Mar 2005 21:49:03 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E16443D41; Wed, 23 Mar 2005 21:49:03 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDTR9T00.LMF; Wed, 23 Mar 2005 13:49:05 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032313524120160 ; Wed, 23 Mar 2005 13:52:41 -0800 From: "Vinod Kashyap" To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org Date: Wed, 23 Mar 2005 13:48:04 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: Subject: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 21:49:04 -0000 If any kernel module has the following, or a similar line in it: ----- char x[100] =3D {0}; ----- building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 as of 03/19/05, fails with the following message at the time of linking: "undefined reference to `memset'". The same problem is not seen on i386. The problem goes away if the above line is changed to: ----- char x[100]; memset(x, 0, 100); ----- Adding CFLAGS+=3D-fbuiltin, or CFLAGS+=3D-fno-builtin to /sys/conf/Makefile= .amd64 does not help. Anyone knows what's happening? Thanks, Vinod. From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 22:00:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFFA816A4CE for ; Wed, 23 Mar 2005 22:00:50 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71BD643D2F for ; Wed, 23 Mar 2005 22:00:50 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id CF60F97057; Wed, 23 Mar 2005 14:00:49 -0800 (PST) Message-Id: <3.0.1.32.20050323140104.00a76cb8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 23 Mar 2005 14:01:04 -0800 To: Sven Willenberger , freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <1111614340.10569.22.camel@lanshark.dmv.com> References: <1110895353.4291.16.camel@lanshark.dmv.com> <1110847561.3412.38.camel@lanshark.dmv.com> <1110895353.4291.16.camel@lanshark.dmv.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: amr performance woes and a bright side [UPDATE] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 22:00:51 -0000 | At any rate, I am glad I can stay with the FreeBSD option now. | | Sven Hi Sven, I was following along with your e-mail there - is there any reason you are using postgress over MySQL? I use FreeBSD with MySQL here and have very good luck with it. I did use postgress years ago, but moved to MySQL and had better luck. Also, in your testing, are you using a generic FreeBSD kernel or have you done any tuning, tweaking to it and/or the OS settings? I recently completed some tweaking with FreeBSD/apache and PHP and from start to finish, ended up with a 750% increase in TPS. So tweaking and fine tuning (and being open to changing apps/versions of software) can have a big impact. Thanks! Ray From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 22:20:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D82316A4CE for ; Wed, 23 Mar 2005 22:20:48 +0000 (GMT) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92EF443D2D for ; Wed, 23 Mar 2005 22:20:47 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) j2NMc3Wa090809; Wed, 23 Mar 2005 17:38:03 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: ray@redshift.com In-Reply-To: <3.0.1.32.20050323140104.00a76cb8@pop.redshift.com> References: <1110895353.4291.16.camel@lanshark.dmv.com> <1110847561.3412.38.camel@lanshark.dmv.com> <1110895353.4291.16.camel@lanshark.dmv.com> <3.0.1.32.20050323140104.00a76cb8@pop.redshift.com> Content-Type: text/plain Date: Wed, 23 Mar 2005 17:20:48 -0500 Message-Id: <1111616448.10576.34.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 cc: freebsd-amd64@freebsd.org Subject: Re: amr performance woes and a bright side [UPDATE] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 22:20:48 -0000 On Wed, 2005-03-23 at 14:01 -0800, ray@redshift.com wrote: > | At any rate, I am glad I can stay with the FreeBSD option now. > | > | Sven > > Hi Sven, > > I was following along with your e-mail there - is there any reason you are > using postgress over MySQL? I use FreeBSD with MySQL here and have very good > luck with it. I did use postgress years ago, but moved to MySQL and had better > luck. > > Also, in your testing, are you using a generic FreeBSD kernel or have you done > any tuning, tweaking to it and/or the OS settings? > > I recently completed some tweaking with FreeBSD/apache and PHP and from start > to finish, ended up with a 750% increase in TPS. So tweaking and fine tuning > (and being open to changing apps/versions of software) can have a big impact. > > Thanks! > > Ray We are using PostgreSQL for its stored procedures, stability, SQL-compliance, and ability to handle 100G+ tables without flinching. It has been only recently that mysql has even added subqueries much less the higher functionality that we are seeking from a database; after evaluation, PostgreSQL was the enterprise-grade solution that we were seeking, and, with proper tweaking, does perform quite well. After one too many experiences with corrupt mysql tables, workarounds to implementing basic SQL compliant queries, and seeming lack of functionality, the switch to PostgreSQL was almost a no-brainer. Not trying to get into a db shootout as each system has its merits and drawbacks; for what we needed, PostgreSQL provided the solution. I am running a modified kernel that adds plenty of memory for use by the shared memory system PostgreSQL enjoys. Sven From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 22:27:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0D9016A4CE for ; Wed, 23 Mar 2005 22:27:54 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DBF43D54 for ; Wed, 23 Mar 2005 22:27:54 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id E610597055; Wed, 23 Mar 2005 14:27:53 -0800 (PST) Message-Id: <3.0.1.32.20050323142809.00a7bdb0@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 23 Mar 2005 14:28:09 -0800 To: Sven Willenberger From: ray@redshift.com In-Reply-To: <1111616448.10576.34.camel@lanshark.dmv.com> References: <3.0.1.32.20050323140104.00a76cb8@pop.redshift.com> <1110895353.4291.16.camel@lanshark.dmv.com> <1110847561.3412.38.camel@lanshark.dmv.com> <1110895353.4291.16.camel@lanshark.dmv.com> <3.0.1.32.20050323140104.00a76cb8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: freebsd-amd64@freebsd.org Subject: Re: amr performance woes and a bright side [UPDATE] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 22:27:54 -0000 | We are using PostgreSQL for its stored procedures, stability, | SQL-compliance, and ability to handle 100G+ tables without flinching. It | has been only recently that mysql has even added subqueries much less | the higher functionality that we are seeking from a database; after | evaluation, PostgreSQL was the enterprise-grade solution that we were | seeking, and, with proper tweaking, does perform quite well. After one | too many experiences with corrupt mysql tables, workarounds to | implementing basic SQL compliant queries, and seeming lack of | functionality, the switch to PostgreSQL was almost a no-brainer. | Not trying to get into a db shootout as each system has its merits and | drawbacks; for what we needed, PostgreSQL provided the solution. Always good to hear from different perspectives :-) | I am running a modified kernel that adds plenty of memory for use by the | shared memory system PostgreSQL enjoys. 10/4 Ray From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 23 22:35:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77FE316A4CE for ; Wed, 23 Mar 2005 22:35:08 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1314843D46 for ; Wed, 23 Mar 2005 22:35:06 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDT00CJ6T5BNU70@bgo1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 23 Mar 2005 23:29:35 +0100 (CET) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDT0085UTH8UMCF@bgo1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 23 Mar 2005 23:36:44 +0100 (CET) Received: by dsa.des.no (Pony Express, from userid 666) id C675BBDC4B; Wed, 23 Mar 2005 23:35:04 +0100 (CET) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 5EE07BDC37; Wed, 23 Mar 2005 23:35:00 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id EB85F33C1B; Wed, 23 Mar 2005 23:34:59 +0100 (CET) Date: Wed, 23 Mar 2005 23:34:59 +0100 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: To: Gert Cuykens Message-id: <86ll8ehtyk.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <2fd864e050322110515c67d29@mail.gmail.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 and nVidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2005 22:35:08 -0000 Gert Cuykens writes: > On Tue, 22 Mar 2005 19:05:29 +0000, Astrodog wrote: > > Is there any word on an nVidia AMD64 FreeBSD driver? > Yes, that i does not excist :) It's been in -CURRENT for a week or two. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 00:49:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72AC616A4CE for ; Thu, 24 Mar 2005 00:49:45 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1240B43D1D for ; Thu, 24 Mar 2005 00:49:45 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so334423wra for ; Wed, 23 Mar 2005 16:49:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=VH1/rfS4gpWr23ucalfo82NsI6p8ZidAfq+r5ZxXMweR69BNzu1PJGEe3/hBNUWdexs9/ZxJQ1nTiJxQvInkEEY9V3Jik+mD475/Zt30MYSioFNiR0Nu0Tk66Ecz1JVotydeoC8F4WxwSMAk+4PwiEYBwWJatsdIEhKNN9YOzqs= Received: by 10.54.93.5 with SMTP id q5mr217772wrb; Wed, 23 Mar 2005 16:49:42 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 23 Mar 2005 16:49:41 -0800 (PST) Message-ID: <2fd864e05032316492d805751@mail.gmail.com> Date: Wed, 23 Mar 2005 16:49:41 -0800 From: Astrodog To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 00:49:45 -0000 I'm finding a huge number of ports that claim to be i386-only, but that seem to work fine on AMD64, even moreso on the Linux compat side. Are there any thoughts on how to resolve this? From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 01:04:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5A8216A4CE for ; Thu, 24 Mar 2005 01:04:04 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 851C543D31 for ; Thu, 24 Mar 2005 01:04:04 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id A180C97061; Wed, 23 Mar 2005 17:04:03 -0800 (PST) Message-Id: <3.0.1.32.20050323170419.00a904a0@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 23 Mar 2005 17:04:19 -0800 To: Astrodog , freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <2fd864e05032316492d805751@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 01:04:04 -0000 Can't you pretty much compile anything you want on AMD64 and run it? I'm sure some of the code is i386 specific and some is AMD64 specific, but in general doesn't the AMD emulate the 386's instruction set? I have an AMD eval machine on the way, so I haven't done much testing first hand yet as far as ports go. Should be doing more next week. Ray At 04:49 PM 3/23/2005 -0800, Astrodog wrote: | I'm finding a huge number of ports that claim to be i386-only, but | that seem to work fine on AMD64, even moreso on the Linux compat side. | Are there any thoughts on how to resolve this? | _______________________________________________ | freebsd-amd64@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 | To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" | | From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 01:12:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5258B16A4CF for ; Thu, 24 Mar 2005 01:12:25 +0000 (GMT) Received: from isis.sigpipe.cz (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2719543D55 for ; Thu, 24 Mar 2005 01:12:22 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 2375F1F87BEF; Thu, 24 Mar 2005 02:12:20 +0100 (CET) Date: Thu, 24 Mar 2005 02:12:20 +0100 From: Roman Neuhauser To: Astrodog Message-ID: <20050324011220.GA81046@isis.sigpipe.cz> References: <2fd864e05032316492d805751@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032316492d805751@mail.gmail.com> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 01:12:25 -0000 # astrodog@gmail.com / 2005-03-23 16:49:41 -0800: > I'm finding a huge number of ports that claim to be i386-only, but > that seem to work fine on AMD64, even moreso on the Linux compat side. > Are there any thoughts on how to resolve this? Find out in cvs why they have been marked i386-only, and if it doesn't seem to be the case (anymore), file a PR with a patch. One for each port. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 02:24:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9463216A4CE for ; Thu, 24 Mar 2005 02:24:25 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1251243D53 for ; Thu, 24 Mar 2005 02:24:25 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so348053wra for ; Wed, 23 Mar 2005 18:24:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=fFDKaMyoSgiN1NKeOWuc6KDiHIw0uxOJ2hABDIVjrL0mPM+hLcwknHmsBXso7p+WtQtqtlUPXVAE5uU7hcYfWBMW6zk+tP2lvhoQGQyNrRbcKsg+eODuqpcNyAjBM3DtZhzHZ7fK9jgF6mTj6b/3yFa0xMXTSlmT72afBRssgGs= Received: by 10.54.22.30 with SMTP id 30mr216905wrv; Wed, 23 Mar 2005 18:24:24 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 23 Mar 2005 18:24:24 -0800 (PST) Message-ID: <2fd864e050323182432f78eaa@mail.gmail.com> Date: Wed, 23 Mar 2005 18:24:24 -0800 From: Astrodog To: Roman Neuhauser In-Reply-To: <20050324011220.GA81046@isis.sigpipe.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 02:24:25 -0000 On Thu, 24 Mar 2005 02:12:20 +0100, Roman Neuhauser wrote: > # astrodog@gmail.com / 2005-03-23 16:49:41 -0800: > > I'm finding a huge number of ports that claim to be i386-only, but > > that seem to work fine on AMD64, even moreso on the Linux compat side. > > Are there any thoughts on how to resolve this? > > Find out in cvs why they have been marked i386-only, and if it > doesn't seem to be the case (anymore), file a PR with a patch. > One for each port. > > -- > How many Vietnam vets does it take to screw in a light bulb? > You don't know, man. You don't KNOW. > Cause you weren't THERE. http://bash.org/?255991 > How could we denote a linux32 dependancy? From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 03:54:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B12416A4CE for ; Thu, 24 Mar 2005 03:54:07 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40CB643D2D for ; Thu, 24 Mar 2005 03:54:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1721 invoked from network); 24 Mar 2005 03:54:07 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 24 Mar 2005 03:54:06 -0000 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2O3s0EF065987; Wed, 23 Mar 2005 22:54:00 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <86ll8ehtyk.fsf@xps.des.no> References: <2fd864e050322110515c67d29@mail.gmail.com> <86ll8ehtyk.fsf@xps.des.no> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <055ab1357440e4a3e4a03198b00e84df@FreeBSD.org> Content-Transfer-Encoding: quoted-printable From: John Baldwin Date: Wed, 23 Mar 2005 22:54:00 -0500 To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) X-Mailer: Apple Mail (2.619.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: freebsd-amd64@FreeBSD.org Subject: Re: AMD64 and nVidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 03:54:07 -0000 On Mar 23, 2005, at 5:34 PM, Dag-Erling Sm=F8rgrav wrote: > Gert Cuykens writes: >> On Tue, 22 Mar 2005 19:05:29 +0000, Astrodog =20 >> wrote: >>> Is there any word on an nVidia AMD64 FreeBSD driver? >> Yes, that i does not excist :) > > It's been in -CURRENT for a week or two. I think they are asking about X drivers rather than the onboard=20 ethernet in the nVidia chipsets. --=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org= From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 04:21:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECCAE16A4CE for ; Thu, 24 Mar 2005 04:21:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 008C043D49 for ; Thu, 24 Mar 2005 04:21:56 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so365679wra for ; Wed, 23 Mar 2005 20:21:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rIORAOi0oZ7Hl9m+N+TCFkzAUb0CAtH/LqlILW50XeLd3csdvXsSJwH1Xf/DDoWWiXKhZgcyQoZo7PR5RHDsugKjfqj9jD9uEJs1/+8HZaIyOQzIphAdwcfGDzNbpoXpxhRdZaZS3kTDkXfj4mQ1eKZCOo2g17gxc3ihvy9Vivs= Received: by 10.54.98.11 with SMTP id v11mr289070wrb; Wed, 23 Mar 2005 20:21:54 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 23 Mar 2005 20:21:54 -0800 (PST) Message-ID: <2fd864e05032320215e17247e@mail.gmail.com> Date: Wed, 23 Mar 2005 20:21:54 -0800 From: Astrodog To: John Baldwin In-Reply-To: <055ab1357440e4a3e4a03198b00e84df@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <2fd864e050322110515c67d29@mail.gmail.com> <86ll8ehtyk.fsf@xps.des.no> <055ab1357440e4a3e4a03198b00e84df@FreeBSD.org> cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 and nVidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 04:21:57 -0000 On Wed, 23 Mar 2005 22:54:00 -0500, John Baldwin wrote: >=20 > On Mar 23, 2005, at 5:34 PM, Dag-Erling Sm=F8rgrav wrote: >=20 > > Gert Cuykens writes: > >> On Tue, 22 Mar 2005 19:05:29 +0000, Astrodog > >> wrote: > >>> Is there any word on an nVidia AMD64 FreeBSD driver? > >> Yes, that i does not excist :) > > > > It's been in -CURRENT for a week or two. >=20 > I think they are asking about X drivers rather than the onboard > ethernet in the nVidia chipsets. >=20 > -- >=20 > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >=20 Sadly, yes. I sent an e-mail off nvidia's way.... somehow, I doubt it will be very helpful, but I guess we'll see. Thanks for the help though. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 04:42:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6832716A4CE for ; Thu, 24 Mar 2005 04:42:38 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 833F243D5D for ; Thu, 24 Mar 2005 04:42:37 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id A94AD78C7F for ; Wed, 23 Mar 2005 23:42:40 -0500 (EST) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08037-07 for ; Wed, 23 Mar 2005 23:42:35 -0500 (EST) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 25DF178C7D for ; Wed, 23 Mar 2005 23:42:34 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 4433028E21; Wed, 23 Mar 2005 23:42:49 -0500 (EST) Date: Wed, 23 Mar 2005 23:42:49 -0500 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050324044249.GZ53316@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <1111606937.71972.2.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1111606937.71972.2.camel@server.mcneil.com> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: Abiword crashes on save X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 04:42:38 -0000 Thus spake Sean McNeil (sean@mcneil.com) [23/03/05 14:43]: : Can anyone else test this on an amd64 system to verify my results: : : Open Abiword. : File->"New using template..." : select Fax-coversheet.awt : hit the save button. : : Any feedback would be appreciated. I can't get it to open a document... Hitting the 'open' button causes a core dump. It seems to be somewhere in threading, but depending on how I go about debugging it, I get a different location for the crash. I'm still meaning to re-compile world with debugging support, then re-compile all required ports as well, to help debug this a bit more. - Damian From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 05:22:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A8FB16A4CE; Thu, 24 Mar 2005 05:22:03 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA3F43D2F; Thu, 24 Mar 2005 05:22:03 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id E41212A8F3; Wed, 23 Mar 2005 21:22:02 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id BC3C7E2B5; Wed, 23 Mar 2005 21:22:01 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id j2O5M26w019336; Wed, 23 Mar 2005 21:22:02 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id j2O5M2pg019335; Wed, 23 Mar 2005 21:22:02 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 23 Mar 2005 21:22:01 -0800 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503232122.01937.peter@wemm.org> cc: freebsd-stable@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 05:22:03 -0000 On Wednesday 23 March 2005 01:48 pm, Vinod Kashyap wrote: > If any kernel module has the following, or a similar line in it: > ----- > char x[100] = {0}; > ----- > building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > as of 03/19/05, fails with the following message at the time of > linking: "undefined reference to `memset'". > > The same problem is not seen on i386. > > The problem goes away if the above line is changed to: > ----- > char x[100]; > memset(x, 0, 100); > ----- > > Adding CFLAGS+=-fbuiltin, or CFLAGS+=-fno-builtin to > /sys/conf/Makefile.amd64 does not help. > > Anyone knows what's happening? Something fishy is going on. I've tried this on both 5.x and 6.0 and both systems created a bss object called 'x', not something that called memset. For example: peter@fb5-amd64[9:17pm]/home/src/sys/modules/twe-21# nm obj/twe.ko | grep x U busdma_lock_mutex U sysctl_ctx_free U sysctl_ctx_init 0000000000000080 b x peter@fb5-amd64[9:17pm]/home/src/sys/modules/twe-22# nm obj/twe.ko | grep memset peter@fb5-amd64[9:17pm]/home/src/sys/modules/twe-23# I wondered if it might be because of something like -O2 (don't do that) or no -O at all, but I couldn't make it happen even then. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 06:46:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B2D816A4CE for ; Thu, 24 Mar 2005 06:46:25 +0000 (GMT) Received: from web30703.mail.mud.yahoo.com (web30703.mail.mud.yahoo.com [68.142.200.136]) by mx1.FreeBSD.org (Postfix) with SMTP id CB03B43D54 for ; Thu, 24 Mar 2005 06:46:24 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 68541 invoked by uid 60001); 24 Mar 2005 06:46:24 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=dO/T+pGfvWcISKNYYGaGGic0Meq86VpiHZqhz468ZfYDRMutLqEwyxyZ5KYsnJIL331SbU0LHgEOtSC0dnxjEtT9Q95FX19thOiNjT6MY7D0kkdyIcqNCqZ2oLyZ7JIzmPnPnaw7Zs4jmwM0y9ZKpkcgMXJtC1EydXLDW3tgjro= ; Message-ID: <20050324064624.68539.qmail@web30703.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30703.mail.mud.yahoo.com via HTTP; Wed, 23 Mar 2005 22:46:23 PST Date: Wed, 23 Mar 2005 22:46:23 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 06:46:25 -0000 --- Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > I was wondering if the R3000Z fixes have been > committed to the > > RELENG_5 branch, I don't see anything on the lists > about it. Should > > I expect 5.4 to work with the R3000 line? > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Apparently, there is something more that I need to know. I am not clear on what I'm supposed to do with this line - where I'm supposed to use it. Is there an explanation somewhere that I missed? __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 06:55:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ECA016A4CE for ; Thu, 24 Mar 2005 06:55:59 +0000 (GMT) Received: from web30707.mail.mud.yahoo.com (web30707.mail.mud.yahoo.com [68.142.200.140]) by mx1.FreeBSD.org (Postfix) with SMTP id DE40243D54 for ; Thu, 24 Mar 2005 06:55:58 +0000 (GMT) (envelope-from neshort@yahoo.com) Received: (qmail 87378 invoked by uid 60001); 24 Mar 2005 06:55:58 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=PVzwrXHZGShJj/TDqhHCd9aEP90MpVcprfa3gT4EUVNcMuxKz5sgkRi8byO3fV+uPSVVQqPeRobCUaVZ+1U7QNEXGMTgnfB81/5IcP+72ptGz57qT2nxz9Xk+fjZt1cZz2DtsG5b7PgWXgw2OA16x3N34ZVhI4wPGmVg/mwXVnA= ; Message-ID: <20050324065558.87376.qmail@web30707.mail.mud.yahoo.com> Received: from [208.240.243.170] by web30707.mail.mud.yahoo.com via HTTP; Wed, 23 Mar 2005 22:55:58 PST Date: Wed, 23 Mar 2005 22:55:58 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: hint.atkbd.0.flags="0x9" (was Re: R3000Z Laptop Status) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 06:55:59 -0000 > > Yes. hint.atkbd.0.flags="0x9" is all you need > now. > > Apparently, there is something more that I need to > know. I am not clear on what I'm supposed to do with > this line - where I'm supposed to use it. Is there > an > explanation somewhere that I missed? > > > I just figured it out -- moments after the above message. (blush). But just in case there are any other people using this nice equipment but can't boot the install CD, here's what you do with the line: At the Boot menu, select option 6. Escape to loader prompt. Then type: set hint.atkbd.0.flags="0x9" and then: boot. Here's what I noticed: the CD will now boot but the keyboard is completely disabled. (Wondering if that's useful or if there is something else I should do.) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 07:05:24 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B9D16A4CE; Thu, 24 Mar 2005 07:05:24 +0000 (GMT) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 275BE43D46; Thu, 24 Mar 2005 07:05:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j2O75Jer026071 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Mar 2005 18:05:20 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j2O75I7l043183; Thu, 24 Mar 2005 18:05:18 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j2O75HjZ043182; Thu, 24 Mar 2005 18:05:17 +1100 (EST) (envelope-from pjeremy) Date: Thu, 24 Mar 2005 18:05:17 +1100 From: Peter Jeremy To: Vinod Kashyap Message-ID: <20050324070516.GA43123@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 07:05:25 -0000 On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: >If any kernel module has the following, or a similar line in it: >----- >char x[100] = {0}; >----- >building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 >as of 03/19/05, fails with the following message at the time of linking: >"undefined reference to `memset'". > >The same problem is not seen on i386. > >The problem goes away if the above line is changed to: >----- >char x[100]; >memset(x, 0, 100); >----- Can you post a complete (compilable) example please. Based on your second example, I suspect that you are putting the variable declaration inside a function definition - the second example doesn't make sense outside a function. If I add "char x[100] = {0};" into a function on i386 and compile it as a kernel module on 5.3, a static memset symbol is generated - it's possible that the amd64 compiler gets confused about the implicit reference to memset that this code needs. -- Peter Jeremy From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 07:13:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FE7A16A4CE for ; Thu, 24 Mar 2005 07:13:32 +0000 (GMT) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFCBC43D5A for ; Thu, 24 Mar 2005 07:13:31 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.3/8.13.1) with ESMTP id j2O7DUDW001166; Wed, 23 Mar 2005 23:13:31 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.3/8.13.1/Submit) id j2O7DUr4001165; Wed, 23 Mar 2005 23:13:30 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Gert Cuykens In-Reply-To: References: <20050323013126.GH53316@afflictions.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 23 Mar 2005 23:13:29 -0800 Message-Id: <1111648409.995.4.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.2.0 FreeBSD GNOME Team Port cc: freebsd-amd64@freebsd.org Subject: Re: nvidia X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 07:13:32 -0000 On Wed, 2005-03-23 at 22:06 +0100, Gert Cuykens wrote: > On Tue, 22 Mar 2005 20:31:26 -0500, Damian Gerow wrote: > > Thus spake Gert Cuykens (gert.cuykens@gmail.com) [22/03/05 18:30]: > > : Do the nvidia display drivers work on amd64 ? > > > > Quite well, actually. Just not with the binary driver supplied by nVidia. > > In the meantime, you can use the open-source 'nv' driver with neither issue, > > nor hardware-accelerrated 3D. > > > > I have no clue when nVidia will be releasing a driver, so don't ask. > > > > At least the support is better then ATI :( On AMD64? Definitely not -- you've still got 3d acceleration for Rage 128 through R200 on AMD64. Sure, the latest cards aren't supported, but that's still unfortunately the best there is for FreeBSD/amd64. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 07:17:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A594F16A4CE for ; Thu, 24 Mar 2005 07:17:08 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B22243D62 for ; Thu, 24 Mar 2005 07:17:08 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so391160wra for ; Wed, 23 Mar 2005 23:17:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=U+RDlb34FMHdcLgEuoCqfeN/BM883GV6J8vTyZhUlHTJYrg9FYrloGR8G0QDqBU8a/WCwZO0RGJ/715gjmhT2h9/puNEq//wcabNP+kq5orMaq+aeXr0AOks6wN94dFgCmlgF035pruP75xIPTOxzTqZuLh/KY6otQD803Xtyq0= Received: by 10.54.98.18 with SMTP id v18mr591469wrb; Wed, 23 Mar 2005 23:17:07 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 23 Mar 2005 23:17:07 -0800 (PST) Message-ID: <2fd864e050323231774aa75cc@mail.gmail.com> Date: Wed, 23 Mar 2005 23:17:07 -0800 From: Astrodog To: Neil Short , freebsd-amd64@freebsd.org In-Reply-To: <20050324071008.64912.qmail@web30706.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <20050324071008.64912.qmail@web30706.mail.mud.yahoo.com> Subject: Re: hint.atkbd.0.flags="0x9" (was Re: R3000Z Laptop Status) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 07:17:08 -0000 On Wed, 23 Mar 2005 23:10:08 -0800 (PST), Neil Short wrote: > thanks! > That's a real good map for me to follow. > Seriously. I finally think I'm walking down a road > that goes somewhere. > -N > > Do this: > > > > Escape to loader. > > set hint.acpi.0.disabled="1" > > set hint.atkbd.0.flags="0x9" > > boot > > > > For ACPI support, you'll need to install the DSDT > > fix... I think thats > > still on the lists. > > I also suggest building and installing the > > powernow.ko module for K8. > > Reposting to main list, so its on here. I can confirm, that the R3000Zs are supported great under 5.4 and 6-CURRENT, however. Onboard ethernet is caught by rl, sound is snd_ich. You'll want the powernow kernel module for powernow support, which then allows you to select 800 Mhz, 1600 Mhz, and 1800 Mhz, (On the Athlon64 3000 line). From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 08:28:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CDD016A4CE for ; Thu, 24 Mar 2005 08:28:06 +0000 (GMT) Received: from isis.sigpipe.cz (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 823DD43D48 for ; Thu, 24 Mar 2005 08:28:05 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 61D1A1F87BEF; Thu, 24 Mar 2005 09:28:04 +0100 (CET) Date: Thu, 24 Mar 2005 09:28:04 +0100 From: Roman Neuhauser To: Astrodog Message-ID: <20050324082804.GA83746@isis.sigpipe.cz> References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e050323182432f78eaa@mail.gmail.com> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 08:28:06 -0000 # astrodog@gmail.com / 2005-03-23 18:24:24 -0800: > On Thu, 24 Mar 2005 02:12:20 +0100, Roman Neuhauser > wrote: > > # astrodog@gmail.com / 2005-03-23 16:49:41 -0800: > > > I'm finding a huge number of ports that claim to be i386-only, but > > > that seem to work fine on AMD64, even moreso on the Linux compat side. > > > Are there any thoughts on how to resolve this? > > > > Find out in cvs why they have been marked i386-only, and if it > > doesn't seem to be the case (anymore), file a PR with a patch. > > One for each port. > > How could we denote a linux32 dependancy? No idea. But I thought you said that a huge number of ports works on amd64 without the compat layer, and an even larger number works *with* it. That looks like a good deal of low hanging fruit. But I must admit that I'm not all that interested in linux compatibility, perhaps except for the Sun JDK. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 08:31:29 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D86E16A4CE; Thu, 24 Mar 2005 08:31:29 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CA0243D1F; Thu, 24 Mar 2005 08:31:28 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])j2O8VJA6006225; Thu, 24 Mar 2005 19:31:19 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j2O8VGMq023657; Thu, 24 Mar 2005 19:31:17 +1100 Date: Thu, 24 Mar 2005 19:31:14 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Vinod Kashyap In-Reply-To: Message-ID: <20050324182524.J97436@delplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 08:31:29 -0000 On Wed, 23 Mar 2005, Vinod Kashyap wrote: > If any kernel module has the following, or a similar line in it: > ----- > char x[100] = {0}; > ----- I think you mean: ----- auto char x[100] = {0}; ----- or after fixing some style bugs: ----- char x[100] = { 0 }; ----- > building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > as of 03/19/05, fails with the following message at the time of linking: > "undefined reference to `memset'". > > The same problem is not seen on i386. > > The problem goes away if the above line is changed to: > ----- > char x[100]; > memset(x, 0, 100); > ----- This version makes the pessimizations and potential bugs clear: - clearing 100 bytes on every entry to the function is wasteful. C90's auto initializers hide pessimizations like this. They should be used very rarely, especially in kernels. But they are often misused, even in kernels, even for read-only data that should be static. gcc doesn't optimize even "auto const x[100] = { 0 };" to a static initialization -- the programmer must declare the object as static to prevent gcc laboriously clearing it on every entry to the function. - 100 bytes may be too much to put on the kernel stack. Objects just a little larger than this must be dynamically allocated unless they can be read-only. > Adding CFLAGS+=-fbuiltin, or CFLAGS+=-fno-builtin to /sys/conf/Makefile.amd64 > does not help. -fno-builtin is already in CFLAGS, and if it has any effect on this then it should be to cause gcc to generate a call to memset() instead of doing the memory clearing inline. I think gcc has a builtin memset() which is turned off by -fno-builtin, but -fno-builtin doesn't affect cases where memset() is not referenced in the source code. -ffreestanding should prevent gcc generating calls to library functions like memset(). However, -ffreestanding is already in CFLAGS too, and there is a problem: certain initializations like the one in your example need to use an interface like memset(), and struct copies need to use and interface like memcpy(), so what is gcc to do when -fno-builtin tells it to turn off its builtins and -ffreestanding tells it that the relevant interfaces might not exist in the library? > Anyone knows what's happening? gcc is expecting that memset() is in the library, but the FreeBSD kernel is freestanding and happens not to have memset() in its library. Related bugs: - the FreeBSD kernel shouldn't have memset() at all. The kernel interface for clearing memory is bzero(). A few files misspelled bzero() as memset() and provided a macro to convert from memset() to bzero(), and instead of fixing them a low-quality memset() was added to . This gives an inline memset() so it doesn't help here. memset() is of some use for setting to nonzero, but this is rarely needed and can easily be repeated as necessary. The support for the nonzero case in is of particularly low quality -- e.g., it crashes if asked to set a length of 0. - memset() to zero and/or gcc methods for initialization to 0 might be much slower than the library's methods for clearing memory. This is not a problem in practice, although bzero() is much faster than gcc's methods in some cases, because: (a) -fno-builtin turns off builtin memset(). (b) the inline memset() just uses bzero() in the fill_byte = 0 case, so using it instead of bzero() is only a tiny pessimization. (c) large copies that bzero() can handle better than gcc's inline method (which is stosl on i386's for your example) cannot because the data would be too large to fit on the kernel statck. - there are slightly different problems for memcpy(): (a) memcpy() is in the library and is not inline, so there is no linkage problem if gcc generates a call to memcpy() for a struct copy. (b) the library memcpy() never uses bcopy(), so it is much slower than bcopy() in much cases. (c) the reason that memcpy() is in the library is to let gcc inline memcpy() for efficiency, but this reason was turned into nonsense by adding -fno-builtin to CFLAGS, and all calls to memcpy() are style bugs and ask for inefficiency. (The inefficiency is small or negative in practice because bzero() has optimizations for large copies that are small pessimizations for non-large copies.) - the FreeBSD kernel shouldn't have memcmp(). It has an inline one that has even lower quality than the inline memset(). memcmp() cannot be implemented using bcmp() since memcmp() is tri-state but bcmp() is boolean, but the inline memcmp() just calls bcmp(). This works, if at all, because nothing actually needs memcmp() and memcmp() is just a misspelling of bcmp(). Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 08:54:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3974116A4D1 for ; Thu, 24 Mar 2005 08:54:11 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A80B43D2D for ; Thu, 24 Mar 2005 08:54:10 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j2O8s9kH042667; Thu, 24 Mar 2005 09:54:09 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j2O8sGts095545; Thu, 24 Mar 2005 09:54:16 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j2O8sG3Q095544; Thu, 24 Mar 2005 09:54:16 +0100 (CET) (envelope-from ftigeot) Date: Thu, 24 Mar 2005 09:54:16 +0100 From: Francois Tigeot To: Astrodog Message-ID: <20050324085416.GB95396@aoi.wolfpond.org> References: <2fd864e05032316492d805751@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032316492d805751@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 08:54:11 -0000 On Wed, Mar 23, 2005 at 04:49:41PM -0800, Astrodog wrote: > I'm finding a huge number of ports that claim to be i386-only, but > that seem to work fine on AMD64, even moreso on the Linux compat side. > Are there any thoughts on how to resolve this? I have recently submitted a PR for some Linux ports: http://www.freebsd.org/cgi/query-pr.cgi?pr=79009 It should be enough to run the new Acrobat reader. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 09:46:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27CEC16A4CE; Thu, 24 Mar 2005 09:46:00 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C30B43D39; Thu, 24 Mar 2005 09:45:59 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j2O9juHn003434; Thu, 24 Mar 2005 20:45:56 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j2O9jrS5014057; Thu, 24 Mar 2005 20:45:54 +1100 Date: Thu, 24 Mar 2005 20:45:53 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Vinod Kashyap In-Reply-To: <20050324182524.J97436@delplex.bde.org> Message-ID: <20050324194817.N97600@delplex.bde.org> References: <20050324182524.J97436@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 09:46:00 -0000 On Thu, 24 Mar 2005, Bruce Evans wrote: > On Wed, 23 Mar 2005, Vinod Kashyap wrote: > >> If any kernel module has the following, or a similar line in it: >> ----- >> char x[100] = {0}; >> ----- >> building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 >> as of 03/19/05, fails with the following message at the time of linking: >> "undefined reference to `memset'". >> ... > ... >> Anyone knows what's happening? > > gcc is expecting that memset() is in the library, but the FreeBSD kernel > is freestanding and happens not to have memset() in its library. As to why gcc calls memset() on amd64's but not on i386's: - gcc-3.3.3 doesn't call memset() on amd64's either. - gcc-3.4.2 on amd64's calls memset() starting with an array size of 65. It uses mov[qlwb] for sizes up to 16, then stos[qlwb] up to size 64. gcc-3.3.3 on i386's uses mov[lwb] for sizes up to 8, then stos[lwb] for all larger sizes. - the relevant change seems to be: % Index: i386.c % =================================================================== % RCS file: /home/ncvs/src/contrib/gcc/config/i386/i386.c,v % retrieving revision 1.20 % retrieving revision 1.21 % diff -u -2 -r1.20 -r1.21 % --- i386.c 19 Jun 2004 20:40:00 -0000 1.20 % +++ i386.c 28 Jul 2004 04:47:35 -0000 1.21 % @@ -437,26 +502,36 @@ % ... % +const int x86_rep_movl_optimal = m_386 | m_PENT | m_PPRO | m_K6; % ... Note that rep_movl is considered optimal on i386's but not on amd64's. % @@ -10701,6 +11427,10 @@ % /* In case we don't know anything about the alignment, default to % library version, since it is usually equally fast and result in % - shorter code. */ % - if (!TARGET_INLINE_ALL_STRINGOPS && align < UNITS_PER_WORD) % + shorter code. % + % + Also emit call when we know that the count is large and call overhead % + will not be important. */ % + if (!TARGET_INLINE_ALL_STRINGOPS % + && (align < UNITS_PER_WORD || !TARGET_REP_MOVL_OPTIMAL)) % return 0; % TARGET_REP_MOVL_OPTIMAL is x86_rep_movl_optimal modulo a mask. It is zero for amd64's, so 0 is returned for amd64's here unless you use -mfoo to set TARGET_INLINE_ALL_STRINGOPS. Returning 0 gives the library call instead of a stringop. This is in i386_expand_clrstr(). There is an identical change in i386_expand_movstr() that gives library calls to memcpy() for (at least) copying structs. Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 10:36:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DB8816A4CE; Thu, 24 Mar 2005 10:36:17 +0000 (GMT) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.82.131.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46E7043D3F; Thu, 24 Mar 2005 10:36:16 +0000 (GMT) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.112.141.145]) j2OAa7uo093387; Thu, 24 Mar 2005 10:36:07 GMT (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) j2OAa5rB090610; Thu, 24 Mar 2005 10:36:06 GMT (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: Bruce Evans In-Reply-To: <20050324182524.J97436@delplex.bde.org> from Bruce Evans of "Thu, 24 Mar 2005 19:31:14 +1100" Date: Thu, 24 Mar 2005 10:36:05 +0000 Message-ID: <90609.1111660565@thrush.ravenbrook.com> Sender: nb@ravenbrook.com cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 10:36:17 -0000 At 2005-03-24 08:31:14+0000, Bruce Evans writes: > what is gcc to do when -fno-builtin tells it to turn off its > builtins and -ffreestanding tells it that the relevant interfaces > might not exist in the library? Plainly, GCC should generate code which fills the array with zeroes. It's not obliged to generate code which calls memset (either builtin or in a library). If it knows that it can do so, then fine. Otherwise it must do it the Old Fashioned Way. So this is surely a bug in GCC. Nick B, who used to write compilers for a living From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 13:43:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DB3516A4CE for ; Thu, 24 Mar 2005 13:43:10 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF7443D46 for ; Thu, 24 Mar 2005 13:43:09 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDU00FA4Z6QBW50@bgo1smout1.broadpark.no> for amd64@freebsd.org; Thu, 24 Mar 2005 14:37:38 +0100 (CET) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDU00II5ZINLMT0@bgo1sminn1.broadpark.no> for amd64@freebsd.org; Thu, 24 Mar 2005 14:44:47 +0100 (CET) Received: by dsa.des.no (Pony Express, from userid 666) id 9921DBDC4B; Thu, 24 Mar 2005 14:43:08 +0100 (CET) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 27900BDC5E for ; Thu, 24 Mar 2005 14:43:04 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 2065033C1B; Thu, 24 Mar 2005 14:43:04 +0100 (CET) Date: Thu, 24 Mar 2005 14:43:04 +0100 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: amd64@freebsd.org Message-id: <86ll8dgnx3.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: Subject: testers wanted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 13:43:10 -0000 I need someone with an nForce3-based Opteron box running -CURRENT to do the following: - upgrade to a recent -CURRENT, verify that a GENERIC kernel with NO_MIXED_MODE removed works properly *with apic enabled* - build an unmodified GENERIC (*with* NO_MIXED_MODE) from the same sources and boot it *with apic enabled* Please provide verbose dmesg for both cases, as well as the contents of /boot/loader.conf and /boot/device.hints. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 15:45:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DD4916A4CE for ; Thu, 24 Mar 2005 15:45:10 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3B2743D55 for ; Thu, 24 Mar 2005 15:45:09 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 691 invoked from network); 24 Mar 2005 15:45:09 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 24 Mar 2005 15:45:08 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j2OFigNC069879; Thu, 24 Mar 2005 10:44:53 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Thu, 24 Mar 2005 09:34:21 -0500 User-Agent: KMail/1.6.2 References: <20050324064624.68539.qmail@web30703.mail.mud.yahoo.com> In-Reply-To: <20050324064624.68539.qmail@web30703.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503240934.21911.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 15:45:10 -0000 On Thursday 24 March 2005 01:46 am, Neil Short wrote: > --- Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > I was wondering if the R3000Z fixes have been > > > > committed to the > > > > > RELENG_5 branch, I don't see anything on the lists > > > > about it. Should > > > > > I expect 5.4 to work with the R3000 line? > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. > > Apparently, there is something more that I need to > know. I am not clear on what I'm supposed to do with > this line - where I'm supposed to use it. Is there an > explanation somewhere that I missed? You need to set it in the loader by breaking into the loader and typing 'set hint.atkbd.0.flags=0x9'. You can make it permament after installation by editing /boot/device.hints and adding a line of just 'hint.atkbd.0.flags=0x9'. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 16:33:46 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C6E516A4CE for ; Thu, 24 Mar 2005 16:33:46 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC9F343D41 for ; Thu, 24 Mar 2005 16:33:45 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1DEVH7-0000n0-00; Thu, 24 Mar 2005 17:33:37 +0100 Date: Thu, 24 Mar 2005 17:33:36 +0100 To: Astrodog Message-ID: <20050324163336.GU2298@poupinou.org> References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <200503211748.12817.nb_root@videotron.ca> <200503211753.29889.jkim@niksun.com> <2fd864e05032115283dc09da7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032115283dc09da7@mail.gmail.com> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 16:33:46 -0000 On Mon, Mar 21, 2005 at 03:28:32PM -0800, Astrodog wrote: > On Mon, 21 Mar 2005 17:53:29 -0500, Jung-uk Kim wrote: > > On Monday 21 March 2005 05:48 pm, Nicolas Blais wrote: > > > What about the PowerNow! kernel module? Is that still required? > > > > If you are okay with 800MHz, no. ;-) You can grab the latest > > powernow-k8 driver from: > > > > http://www.poupinou.org/cpufreq/bsd/powernow.tar.gz > > > > Jung-uk Kim > > > > > Thanks, > > > Nicolas. > > > > > > On March 21, 2005 10:49, Jung-uk Kim wrote: > > > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > > > I was wondering if the R3000Z fixes have been committed to the > > > > > RELENG_5 branch, I don't see anything on the lists about it. > > > > > Should I expect 5.4 to work with the R3000 line? > > > > > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the > > > > latest snapshot and let us know. > > > > > > > > Thanks, > > > > > > > > Jung-uk Kim > > > > > > > > > --- Harrison Grundy > > _______________________________________________ > > 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" > > > > Powernow works great, by the way. I'm upgrading to 6-CURRENT now > because I need the ath driver for AMD64 for a wireless card I have, > but I tested things out in 5.4-PRERELEASE, and it works great once > these few, relatively easy to fix issues are resolved. The powernow driver have just been updated btw, would be fine if I got some feedback. It's close to be committed I believe. There is though an unlikely situation where a kernel panic happens if using acpi_perf driver at kldload time (it happens due to known BIOS bugs), and since acpi_perf is compiled now statically, the ACPI path will be taken at first in the powernow driver (this should not be an issue for releng_5 and powernow alone). The below patch (which maybe already committed, who knows) fix this. Index: acpi_perf.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_perf.c,v retrieving revision 1.16 diff -u -p -r1.16 acpi_perf.c --- acpi_perf.c 20 Mar 2005 03:51:18 -0000 1.16 +++ acpi_perf.c 24 Mar 2005 12:52:17 -0000 @@ -244,6 +244,7 @@ acpi_perf_evaluate(device_t dev) ACPI_OBJECT *pkg, *res; ACPI_STATUS status; int error, i, j; + int count; uint32_t *p; /* Get the control values and parameters for each state. */ @@ -272,27 +273,31 @@ acpi_perf_evaluate(device_t dev) * BusMasterLatency, ControlVal, StatusVal}, sorted from highest * performance to lowest. */ - for (i = 0; i < sc->px_count; i++) { + for (count = 0, i = 0; i < sc->px_count; i++) { res = &pkg->Package.Elements[i]; if (!ACPI_PKG_VALID(res, 6)) { device_printf(dev, "invalid _PSS package\n"); continue; } - /* - * Check for some impossible frequencies that some systems - * use to indicate they don't actually support Px states. - */ p = &sc->px_states[i].core_freq; - if (*p == 9999 || *p == 0xffff) - goto out; - /* Parse the rest of the package into the struct. */ for (j = 0; j < 6; j++, p++) acpi_PkgInt32(res, j, p); + + /* + * Check for some impossible frequencies that some systems + * use to indicate they don't actually support this Px state. + */ + if (sc->px_states[i].core_freq == 9999 || + sc->px_states[i].core_freq == 0xffff) + continue; + count++; } AcpiOsFree(buf.Pointer); + sc->px_count = count; + /* Get the control and status registers (one of each). */ buf.Pointer = NULL; buf.Length = ACPI_ALLOCATE_BUFFER; Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 18:21:34 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2051E16A4CE; Thu, 24 Mar 2005 18:21:34 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E41A43D31; Thu, 24 Mar 2005 18:21:33 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDV00FCCC2POO90@bgo1smout1.broadpark.no>; Thu, 24 Mar 2005 19:16:01 +0100 (CET) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IDV00IEECEMLCI1@bgo1sminn1.broadpark.no>; Thu, 24 Mar 2005 19:23:10 +0100 (CET) Received: by dsa.des.no (Pony Express, from userid 666) id B6718BDC5E; Thu, 24 Mar 2005 19:21:31 +0100 (CET) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 42A9BBDC3E; Thu, 24 Mar 2005 19:21:27 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 327D533C3E; Thu, 24 Mar 2005 19:21:27 +0100 (CET) Date: Thu, 24 Mar 2005 19:21:27 +0100 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: <200503232122.01937.peter@wemm.org> To: Peter Wemm Message-id: <86acosykew.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <200503232122.01937.peter@wemm.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 18:21:34 -0000 Peter Wemm writes: > I wondered if it might be because of something like -O2 (don't do that)=20 Peter, stop that. The kernel builds and runs fine with -O2, and has for a long time. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 19:57:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BACD16A4CE for ; Thu, 24 Mar 2005 19:57:41 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC8AD43D49 for ; Thu, 24 Mar 2005 19:57:40 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OJveJA096571; Thu, 24 Mar 2005 11:57:40 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OJvcei096570; Thu, 24 Mar 2005 11:57:38 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 11:57:38 -0800 From: "David O'Brien" To: Jung-uk Kim Message-ID: <20050324195738.GA60666@dragon.NUXI.org> References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503211049.11110.jkim@niksun.com> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 19:57:41 -0000 On Mon, Mar 21, 2005 at 10:49:11AM -0500, Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > I was wondering if the R3000Z fixes have been committed to the > > RELENG_5 branch, I don't see anything on the lists about it. Should > > I expect 5.4 to work with the R3000 line? > > Yes. hint.atkbd.0.flags="0x9" is all you need now. What the implications be of changing the USB boot option in the Beastie menu with atkbd flags 0x9 vs. 0x1? Meaning we could have a "safe kbd" option instead of just a USB one. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:04:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 595C616A4CE; Thu, 24 Mar 2005 20:04:19 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA36D43D2F; Thu, 24 Mar 2005 20:04:18 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDVH3802.ESF; Thu, 24 Mar 2005 12:04:20 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032412073715466 ; Thu, 24 Mar 2005 12:07:37 -0800 From: "Vinod Kashyap" To: Bruce Evans Date: Thu, 24 Mar 2005 12:03:19 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:04:19 -0000 > This version makes the pessimizations and potential bugs clear: > - clearing 100 bytes on every entry to the function is = > wasteful. C90's > auto initializers hide pessimizations like this. They should be > used very rarely, especially in kernels. But they are = > often misused, > even in kernels, even for read-only data that should be = > static. gcc > doesn't optimize even "auto const x[100] =3D { 0 };" to a static > initialization -- the programmer must declare the object = > as static to > prevent gcc laboriously clearing it on every entry to the function. > - 100 bytes may be too much to put on the kernel stack. Objects just > a little larger than this must be dynamically allocated unless they > can be read-only. > = A statement like this (auto and not static) is necessary if you are dealing with re-entrancy. Whatever the issues with wastage or bad performance, a programmer should definitely be able to do it, if he so desires. Also, the line I mentioned earlier was only an example. Something like this also fails (your response already explains this): ----- struct x_type x =3D {0}; ----- > > Adding CFLAGS+=3D-fbuiltin, or CFLAGS+=3D-fno-builtin to = > /sys/conf/Makefile.amd64 > > does not help. > = > -fno-builtin is already in CFLAGS, and if it has any effect = > on this then > it should be to cause gcc to generate a call to memset() = > instead of doing > the memory clearing inline. I think gcc has a builtin = > memset() which is > turned off by -fno-builtin, but -fno-builtin doesn't affect = > cases where > memset() is not referenced in the source code. > = > -ffreestanding should prevent gcc generating calls to library = > functions > like memset(). However, -ffreestanding is already in CFLAGS too, and > there is a problem: certain initializations like the one in = > your example > need to use an interface like memset(), and struct copies = > need to use and > interface like memcpy(), so what is gcc to do when = > -fno-builtin tells it > to turn off its builtins and -ffreestanding tells it that the relevant > interfaces might not exist in the library? > = > > Anyone knows what's happening? > = > gcc is expecting that memset() is in the library, but the = > FreeBSD kernel > is freestanding and happens not to have memset() in its library. > = How is it then, that an explicit call to memset (like in my example) works?= As about other questions in the thread: 1. Yes, the example code is within a function, 2. I should have mentioned that I don't see the problem if I am building only the kernel module. It happens only when I am building the kernel integrating the module containing the example code. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:08:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CB16A4CE for ; Thu, 24 Mar 2005 20:08:45 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA44743D2D for ; Thu, 24 Mar 2005 20:08:44 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OK8iRB096861; Thu, 24 Mar 2005 12:08:44 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OK8iLJ096860; Thu, 24 Mar 2005 12:08:44 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 12:08:43 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050324200843.GE60666@dragon.NUXI.org> References: <2fd864e05032316492d805751@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032316492d805751@mail.gmail.com> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:08:45 -0000 On Wed, Mar 23, 2005 at 04:49:41PM -0800, Astrodog wrote: > I'm finding a huge number of ports that claim to be i386-only, but > that seem to work fine on AMD64, even moreso on the Linux compat side. > Are there any thoughts on how to resolve this? Yes, if you find that a "i386-only" port works fine on AMD64 send a patch to the port using 'send-pr'. Or email the ports@freebsd.org mailing list with the information. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:10:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C47516A4CE for ; Thu, 24 Mar 2005 20:10:25 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419F843D49 for ; Thu, 24 Mar 2005 20:10:22 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2OKAL3g003822 for ; Thu, 24 Mar 2005 15:10:21 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 15:10:17 -0500 User-Agent: KMail/1.6.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> <20050324195738.GA60666@dragon.NUXI.org> In-Reply-To: <20050324195738.GA60666@dragon.NUXI.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503241510.18194.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 07:29:35 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:10:25 -0000 On Thursday 24 March 2005 02:57 pm, David O'Brien wrote: > On Mon, Mar 21, 2005 at 10:49:11AM -0500, Jung-uk Kim wrote: > > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > > I was wondering if the R3000Z fixes have been committed to the > > > RELENG_5 branch, I don't see anything on the lists about it. > > > Should I expect 5.4 to work with the R3000 line? > > > > Yes. hint.atkbd.0.flags="0x9" is all you need now. > > What the implications be of changing the USB boot option in the > Beastie menu with atkbd flags 0x9 vs. 0x1? Meaning we could have a > "safe kbd" option instead of just a USB one. I like the idea. Adding DMI scanning in loader is too late for 5.4 release any way. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:10:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C9F816A4CE for ; Thu, 24 Mar 2005 20:10:37 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5281043D58 for ; Thu, 24 Mar 2005 20:10:37 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OKAa4I096899; Thu, 24 Mar 2005 12:10:36 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OKAabX096898; Thu, 24 Mar 2005 12:10:36 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 12:10:36 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050324201036.GF60666@dragon.NUXI.org> References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e050323182432f78eaa@mail.gmail.com> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:10:37 -0000 On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote: > How could we denote a linux32 dependancy? I don't follow. The current idea is that the linux_base port when installed for FreeBSD will install both 32-bit and 64-bit[*] bits. [*] When 64-bit Linux support is later added. We have enough polishing to do to just support all the things we've already got to the standards people expect of FreeBSD. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:17:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2937716A4CE; Thu, 24 Mar 2005 20:17:13 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AECF143D31; Thu, 24 Mar 2005 20:17:12 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2OKFaYr075675; Thu, 24 Mar 2005 13:15:37 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42431F9D.5080906@samsco.org> Date: Thu, 24 Mar 2005 13:14:21 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <200503232122.01937.peter@wemm.org> <86acosykew.fsf@xps.des.no> In-Reply-To: <86acosykew.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:17:13 -0000 Dag-Erling Smørgrav wrote: > Peter Wemm writes: > >>I wondered if it might be because of something like -O2 (don't do that) > > > Peter, stop that. The kernel builds and runs fine with -O2, and has > for a long time. > > DES No it doesn't. See the gymnastics that Bill Paul had to do recently in the iee80211 code to get around the insane inlining that gcc does with -O2. I'm not saying that gcc produces incorrect code, but I am saying that there is very strong evidence that it produces code that is incompatible with the restrictions inherent to the kernel, mainly that stack space is not infinite. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:20:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id E207416A4CF; Thu, 24 Mar 2005 20:20:42 +0000 (GMT) Date: Thu, 24 Mar 2005 20:20:42 +0000 From: David O'Brien To: Vinod Kashyap Message-ID: <20050324202042.GA8469@hub.freebsd.org> References: <20050324070516.GA43123@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050324070516.GA43123@cirb503493.alcatel.com.au> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:20:43 -0000 On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > >If any kernel module has the following, or a similar line in it: > >----- > >char x[100] = {0}; > >----- > >building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > >as of 03/19/05, fails with the following message at the time of linking: > >"undefined reference to `memset'". > > > >The same problem is not seen on i386. > > > >The problem goes away if the above line is changed to: > >----- > >char x[100]; > >memset(x, 0, 100); > >----- > > Can you post a complete (compilable) example please. Vinod can you please post a complete compilable example? It is impossible to get anything done about your issue without stand alone test code. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:25:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F03E16A4CE; Thu, 24 Mar 2005 20:25:35 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7D0843D49; Thu, 24 Mar 2005 20:25:34 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2OKPWup046326; Thu, 24 Mar 2005 22:25:32 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 06989-07; Thu, 24 Mar 2005 22:25:47 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2OKPVAN046323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Mar 2005 22:25:32 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2OKPqRp043562; Thu, 24 Mar 2005 22:25:52 +0200 (EET) (envelope-from ru) Date: Thu, 24 Mar 2005 22:25:52 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20050324202552.GA40329@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org Subject: amd64/packages-6-current linked with libc.so.5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:25:35 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Kris, Can you please explain how this happened that some current packages for amd64 are linked with libc.so.5? I noticed this when trying to bootstrap my current amd64 box with: ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All/cvsup-= without-gui-16.1h.tbz Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQyJQqRfpzJluFF4RAq45AJ0Uvg5ELJ1aHQYV4D7xmd98ZMzuAQCffRcN raI6565fH7uzZHXmpgIXM+8= =8J73 -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:32:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B157B16A4CE; Thu, 24 Mar 2005 20:32:04 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C78643D55; Thu, 24 Mar 2005 20:32:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5E8A9511F0; Thu, 24 Mar 2005 12:32:03 -0800 (PST) Date: Thu, 24 Mar 2005 12:32:03 -0800 From: Kris Kennaway To: Ruslan Ermilov Message-ID: <20050324203203.GA10600@xor.obsecurity.org> References: <20050324202552.GA40329@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20050324202552.GA40329@ip.net.ua> User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: amd64/packages-6-current linked with libc.so.5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:32:04 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 10:25:52PM +0200, Ruslan Ermilov wrote: > Hi Kris, >=20 > Can you please explain how this happened that some current > packages for amd64 are linked with libc.so.5? >=20 > I noticed this when trying to bootstrap my current amd64 > box with: >=20 > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All/cvsu= p-without-gui-16.1h.tbz AFAIK, that port just installs a precompiled binary on amd64. Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQyPDWry0BWjoQKURAhzpAJ9bhBJ7D4nzwNc9CHTzq/8v6qzXFACfaN9b 2KCaBvKduhqzW23W80uazFU= =7oKo -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:42:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A13D16A4CE for ; Thu, 24 Mar 2005 20:42:28 +0000 (GMT) Received: from mail.celeritystorm.com (mail.celeritystorm.com [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id A071F43D48 for ; Thu, 24 Mar 2005 20:42:27 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: from [192.168.0.1] (unknown [81.84.174.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id B2AD83D85D7 for ; Thu, 24 Mar 2005 21:49:29 +0100 (CET) Message-ID: <4243259C.1050906@celeritystorm.com> Date: Thu, 24 Mar 2005 20:39:56 +0000 From: Hugo Silva User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: First time experience with AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:42:28 -0000 Hey all, I've just had my first experience with FreeBSD/AMD64. Perhaps naively, I've built the world using the usual command sequence. After installing the world, however, I've noticed all the system binaries are 32 bits. I think this shouldn't be the case! Also, make buildkernel KERNCONF=name doesn't work (always says it cannot find the kernel). I've placed my kernel config on /usr/src/sys/amd64/conf/ , this is the right directory to place it on a 64 bits machine, right ? Perhaps I need an extra switch to the make buildkernel command, instructing a 64 bits architecture. Last but not the least, building my kernel "the old way" (config NAME, cd.. /compile/NAME && make depend && make && make install) gives out a bunch of errors right at the start and fails. I don't have the error messages right now. The system is 5.3-STABLE as of last thursday. Any insight on this would be very much welcomed! Thanks. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:44:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6460416A4CE; Thu, 24 Mar 2005 20:44:03 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 775D143D2D; Thu, 24 Mar 2005 20:44:02 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2OKi15a048485; Thu, 24 Mar 2005 22:44:01 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 08066-02; Thu, 24 Mar 2005 22:44:15 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2OKi0tZ048480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Mar 2005 22:44:00 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2OKiLi3077593; Thu, 24 Mar 2005 22:44:21 +0200 (EET) (envelope-from ru) Date: Thu, 24 Mar 2005 22:44:20 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20050324204420.GB40329@ip.net.ua> References: <20050324202552.GA40329@ip.net.ua> <20050324203203.GA10600@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline In-Reply-To: <20050324203203.GA10600@xor.obsecurity.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: amd64/packages-6-current linked with libc.so.5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:44:03 -0000 --TRYliJ5NKNqkz5bu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 12:32:03PM -0800, Kris Kennaway wrote: > On Thu, Mar 24, 2005 at 10:25:52PM +0200, Ruslan Ermilov wrote: > > Hi Kris, > >=20 > > Can you please explain how this happened that some current > > packages for amd64 are linked with libc.so.5? > >=20 > > I noticed this when trying to bootstrap my current amd64 > > box with: > >=20 > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All/cv= sup-without-gui-16.1h.tbz >=20 > AFAIK, that port just installs a precompiled binary on amd64. >=20 Thanks, that explains it. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQyakqRfpzJluFF4RAigwAJ91YwjIkVQk7Yb02tHJspit8eqF+gCeM8Jy YfEjn5MDw/O7434O4cvUckM= =Z1T2 -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:47:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 802DE16A4CE; Thu, 24 Mar 2005 20:47:41 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id E929043D1F; Thu, 24 Mar 2005 20:47:38 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDVJ3H01.CW0; Thu, 24 Mar 2005 12:47:41 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032412510115974 ; Thu, 24 Mar 2005 12:51:01 -0800 From: "Vinod Kashyap" To: obrien@freebsd.org Date: Thu, 24 Mar 2005 12:46:41 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:47:41 -0000 Ok, make sure you have 'device twa' in your kernel configuration file, and apply these patches to /sys/dev/twa/twa.c. This patch causes the problem: --- twa.c.org Wed Mar 23 11:13:49 2005 +++ twa.c Thu Mar 24 12:42:23 2005 @@ -366,9 +366,12 @@ int8_t fw_flashed =3D FALSE; int8_t fw_flash_failed =3D FALSE; #endif /* TWA_FLASH_FIRMWARE */ + int8_t tw_expt[100] =3D {0}; + int8_t *tw_expt_ptr; = twa_dbg_dprint_enter(3, sc); = + tw_expt_ptr =3D &(tw_expt[0]); /* Wait for the controller to become ready. */ if (twa_wait_status(sc, TWA_STATUS_MICROCONTROLLER_READY, TWA_REQUEST_TIMEOUT_PERIOD)) { This patch does not cause the problem: --- twa.c.org Wed Mar 23 11:13:49 2005 +++ twa.c Thu Mar 24 12:36:10 2005 @@ -366,9 +366,13 @@ int8_t fw_flashed =3D FALSE; int8_t fw_flash_failed =3D FALSE; #endif /* TWA_FLASH_FIRMWARE */ + int8_t tw_expt[100]/* =3D {0}*/; + int8_t *tw_expt_ptr; = twa_dbg_dprint_enter(3, sc); = + memset(tw_expt, 0, 100); + tw_expt_ptr =3D &(tw_expt[0]); /* Wait for the controller to become ready. */ if (twa_wait_status(sc, TWA_STATUS_MICROCONTROLLER_READY, TWA_REQUEST_TIMEOUT_PERIOD)) { > -----Original Message----- > From: David O'Brien [mailto:obrien@FreeBSD.ORG] > Sent: Thursday, March 24, 2005 12:21 PM > To: Vinod Kashyap > Cc: freebsd-amd64@freebsd.org > Subject: Re: undefined reference to `memset' > = > = > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > >If any kernel module has the following, or a similar line in it: > > >----- > > >char x[100] =3D {0}; > > >----- > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > > >as of 03/19/05, fails with the following message at the = > time of linking: > > >"undefined reference to `memset'". > > > > > >The same problem is not seen on i386. > > > > > >The problem goes away if the above line is changed to: > > >----- > > >char x[100]; > > >memset(x, 0, 100); > > >----- > > = > > Can you post a complete (compilable) example please. > = > Vinod can you please post a complete compilable example? > It is impossible to get anything done about your issue without stand > alone test code. > = > -- = > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 20:50:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D510F16A4CE for ; Thu, 24 Mar 2005 20:50:14 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71FC543D49 for ; Thu, 24 Mar 2005 20:50:14 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so611834wra for ; Thu, 24 Mar 2005 12:50:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=LXwoGvkvsrHg5vh6V8V2Kxxr0aZfv7Lxc0XEhiqlu+TKHzWH+tluzDKxONWQqgKqAT4SSKXyJzB8Cv6yHjVl5KR6/qv1QBZX+tx9dCXoxST1oD0RIo8ZyD8aKJxgzU5V5At2Ts2c6GdYTw+lI4CEVXAJqOtFH77v3TEMUpae+BY= Received: by 10.54.99.6 with SMTP id w6mr500897wrb; Thu, 24 Mar 2005 12:50:13 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 24 Mar 2005 12:50:13 -0800 (PST) Message-ID: <2fd864e05032412501c001a5d@mail.gmail.com> Date: Thu, 24 Mar 2005 12:50:13 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050324201036.GF60666@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org> Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 20:50:15 -0000 On Thu, 24 Mar 2005 12:10:36 -0800, David O'Brien wrote: > On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote: > > How could we denote a linux32 dependancy? > > I don't follow. The current idea is that the linux_base port when > installed for FreeBSD will install both 32-bit and 64-bit[*] bits. > > [*] When 64-bit Linux support is later added. We have enough polishing > to do to just support all the things we've already got to the standards > people expect of FreeBSD. > -- > -- David (obrien@FreeBSD.org) > We have 2 problems, that I see. #1. Linux32 doesn't appear to be addressed for dependancies at all, almost every linux-something port I've found, calls itsself i386 only, and sometimes has minor RPM issues. #2. With IA32 Compatibility, it should be possible to install i386-only ports, and packages in quite a few cases, because of the binary compatibility stuff. I'm not sure how this could be handled either, since it would require a specific kernel option be enabled.... much like Linux32, I suppose. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 21:07:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E28A16A4CF for ; Thu, 24 Mar 2005 21:07:07 +0000 (GMT) Received: from mail.celeritystorm.com (mail.celeritystorm.com [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0F1A43D39 for ; Thu, 24 Mar 2005 21:07:06 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: from [192.168.0.1] (unknown [81.84.174.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id 02DF63D85D7 for ; Thu, 24 Mar 2005 22:14:09 +0100 (CET) Message-ID: <42432B64.2010808@celeritystorm.com> Date: Thu, 24 Mar 2005 21:04:37 +0000 From: Hugo Silva User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <4243259C.1050906@celeritystorm.com> <2fd864e050324125953d5aea3@mail.gmail.com> In-Reply-To: <2fd864e050324125953d5aea3@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: First time experience with AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 21:07:07 -0000 LOL point well taken ;) I burned the ISO from my laptop, totally forgot about that. :) Astrodog wrote: >On Thu, 24 Mar 2005 20:39:56 +0000, Hugo Silva wrote: > > >>Hey all, >> >>I've just had my first experience with FreeBSD/AMD64. Perhaps naively, >>I've built the world using the usual command sequence. After installing >>the world, however, I've noticed all the system binaries are 32 bits. I >>think this shouldn't be the case! >> >>Also, make buildkernel KERNCONF=name doesn't work (always says it cannot >>find the kernel). I've placed my kernel config on >>/usr/src/sys/amd64/conf/ , this is the right directory to place it on a >>64 bits machine, right ? Perhaps I need an extra switch to the make >>buildkernel command, instructing a 64 bits architecture. >> >>Last but not the least, building my kernel "the old way" (config NAME, >>cd.. /compile/NAME && make depend && make && make install) gives out a >>bunch of errors right at the start and fails. I don't have the error >>messages right now. >> >>The system is 5.3-STABLE as of last thursday. >> >>Any insight on this would be very much welcomed! >> >>Thanks. >>_______________________________________________ >>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" >> >> >> > >It is somewhat important that you start with the amd64 ISOs. :) > > > From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 21:50:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F94016A4CE for ; Thu, 24 Mar 2005 21:50:00 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E59E43D31 for ; Thu, 24 Mar 2005 21:50:00 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OLnvqS099146; Thu, 24 Mar 2005 13:49:57 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OLnuof099145; Thu, 24 Mar 2005 13:49:56 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 13:49:56 -0800 From: "David O'Brien" To: Vinod Kashyap Message-ID: <20050324214956.GA99087@dragon.NUXI.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 21:50:00 -0000 Please don't top-post -- it destroys context. [Format recovered] On Thu, Mar 24, 2005 at 12:46:41PM -0800, Vinod Kashyap wrote: > > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > > >If any kernel module has the following, or a similar line in it: > > > >----- > > > >char x[100] = {0}; > > > >----- > > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > > > >as of 03/19/05, fails with the following message at the > > time of linking: > > > >"undefined reference to `memset'". > > > > > > > >The same problem is not seen on i386. > > > > > > > >The problem goes away if the above line is changed to: > > > >----- > > > >char x[100]; > > > >memset(x, 0, 100); > > > >----- > > > > > > Can you post a complete (compilable) example please. > > > > Vinod can you please post a complete compilable example? > > It is impossible to get anything done about your issue without stand > > alone test code. > Ok, make sure you have 'device twa' in your kernel configuration > file, and apply these patches to /sys/dev/twa/twa.c. > This patch causes the problem: "stand alone" means a single foo.c file that shows the problem you want fixed. I cannot submit a GCC bug report with a tarball of the entire FreeBSD kernel. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 21:51:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53FB116A4CE; Thu, 24 Mar 2005 21:51:14 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29A8343D3F; Thu, 24 Mar 2005 21:51:14 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OLpDZC099231; Thu, 24 Mar 2005 13:51:13 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OLpDYt099230; Thu, 24 Mar 2005 13:51:13 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 13:51:13 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20050324215113.GA99206@dragon.NUXI.org> References: <20050324202552.GA40329@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050324202552.GA40329@ip.net.ua> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: Kris Kennaway cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/packages-6-current linked with libc.so.5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 21:51:14 -0000 On Thu, Mar 24, 2005 at 10:25:52PM +0200, Ruslan Ermilov wrote: > Hi Kris, > > Can you please explain how this happened that some current > packages for amd64 are linked with libc.so.5? > > I noticed this when trying to bootstrap my current amd64 > box with: > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All/cvsup-without-gui-16.1h.tbz It isn't built from source. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 21:54:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C04116A4CE for ; Thu, 24 Mar 2005 21:54:49 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D57843D5E for ; Thu, 24 Mar 2005 21:54:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2OLsjdc099315; Thu, 24 Mar 2005 13:54:45 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2OLsjVG099314; Thu, 24 Mar 2005 13:54:45 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 13:54:45 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050324215445.GB99206@dragon.NUXI.org> References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org> <2fd864e05032412501c001a5d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032412501c001a5d@mail.gmail.com> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 21:54:49 -0000 On Thu, Mar 24, 2005 at 12:50:13PM -0800, Astrodog wrote: > On Thu, 24 Mar 2005 12:10:36 -0800, David O'Brien wrote: > > On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote: > > > How could we denote a linux32 dependancy? > > > > I don't follow. The current idea is that the linux_base port when > > installed for FreeBSD will install both 32-bit and 64-bit[*] bits. > > > > [*] When 64-bit Linux support is later added. We have enough polishing > > to do to just support all the things we've already got to the standards > > people expect of FreeBSD. > > -- > > -- David (obrien@FreeBSD.org) > > > > We have 2 problems, that I see. > > #1. Linux32 doesn't appear to be addressed for dependancies at all, > almost every linux-something port I've found, calls itsself i386 only, > and sometimes has minor RPM issues. What are the minor RPM issues? I knew there are some (see archives for the arguments over the way we currently igngore them). But a summary of current issues would be good. 'amd64# cd /usr/ports/print/acroread ; make install' worked for me at work. > #2. With IA32 Compatibility, it should be possible to install > i386-only ports, and packages in quite a few cases, because of the > binary compatibility stuff. I'm not sure how this could be handled > either, since it would require a specific kernel option be enabled.... > much like Linux32, I suppose. Assume that if someone goes out of their way to install a 32-bit port, they have not removed the IA32 support from their kernel. This is now in the default GENERIC config for 5.4. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 22:02:24 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C5A16A4CE; Thu, 24 Mar 2005 22:02:24 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02BBC43D55; Thu, 24 Mar 2005 22:02:24 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (pD9E69236.dip.t-dialin.net [217.230.146.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 4A50632380; Thu, 24 Mar 2005 23:02:14 +0100 (CET) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j2OM3A0x002162; Thu, 24 Mar 2005 23:03:16 +0100 (CET) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j2OM2x0t002161; Thu, 24 Mar 2005 23:02:59 +0100 (CET) (envelope-from mkb) Date: Thu, 24 Mar 2005 23:02:59 +0100 From: Matthias Buelow To: Scott Long Message-ID: <20050324220259.GA770@drjekyll.mkbuelow.net> References: <200503232122.01937.peter@wemm.org> <86acosykew.fsf@xps.des.no> <42431F9D.5080906@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42431F9D.5080906@samsco.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 22:02:24 -0000 Scott Long writes: >No it doesn't. See the gymnastics that Bill Paul had to do recently in >the iee80211 code to get around the insane inlining that gcc does with >-O2. I'm not saying that gcc produces incorrect code, but I am saying >that there is very strong evidence that it produces code that is >incompatible with the restrictions inherent to the kernel, mainly that >stack space is not infinite. I wonder how this is being done elsewhere, on NetBSD, everything is built with -O2 and has been for several years afair. Not that I care much about it but apparently it doesn't seem to be such a big problem everywhere? mkb. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 22:02:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A71616A4CE for ; Thu, 24 Mar 2005 22:02:54 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 067C543D41 for ; Thu, 24 Mar 2005 22:02:54 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDVMKW00.1RS for ; Thu, 24 Mar 2005 14:02:56 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032414062116909 for ; Thu, 24 Mar 2005 14:06:21 -0800 From: "Vinod Kashyap" To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 14:01:56 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 22:02:54 -0000 > > > Vinod can you please post a complete compilable example? > > > It is impossible to get anything done about your issue = > without stand > > > alone test code. > > Ok, make sure you have 'device twa' in your kernel configuration > > file, and apply these patches to /sys/dev/twa/twa.c. > > This patch causes the problem: > = > "stand alone" means a single foo.c file that shows the = > problem you want > fixed. > I cannot submit a GCC bug report with a tarball of the entire FreeBSD > kernel. > = Can you not submit it with the patch I sent? A "stand alone" foo.c will have to be a new module under a new directory (/sys/dev/foo), with its own Makefile, with changes to /sys/conf/files, and an entry in GENERIC. From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 22:10:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67CFC16A4CE for ; Thu, 24 Mar 2005 22:10:35 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23B4043D4C for ; Thu, 24 Mar 2005 22:10:35 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C3D64F3EE9; Thu, 24 Mar 2005 14:10:32 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02642-03; Thu, 24 Mar 2005 14:10:31 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id A626FF3EB8; Thu, 24 Mar 2005 14:10:31 -0800 (PST) From: Sean McNeil To: freebsd-amd64@freebsd.org In-Reply-To: <20050324214956.GA99087@dragon.NUXI.org> References: <20050324214956.GA99087@dragon.NUXI.org> Content-Type: multipart/mixed; boundary="=-wLOup4CYUrnuKOU6OdqB" Date: Thu, 24 Mar 2005 14:10:31 -0800 Message-Id: <1111702231.2655.6.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 22:10:35 -0000 --=-wLOup4CYUrnuKOU6OdqB Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 2005-03-24 at 13:49 -0800, David O'Brien wrote: > Please don't top-post -- it destroys context. [Format recovered] > > On Thu, Mar 24, 2005 at 12:46:41PM -0800, Vinod Kashyap wrote: > > > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > > > >If any kernel module has the following, or a similar line in it: > > > > >----- > > > > >char x[100] = {0}; > > > > >----- > > > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64 > > > > >as of 03/19/05, fails with the following message at the > > > time of linking: > > > > >"undefined reference to `memset'". > > > > > > > > > >The same problem is not seen on i386. > > > > > > > > > >The problem goes away if the above line is changed to: > > > > >----- > > > > >char x[100]; > > > > >memset(x, 0, 100); > > > > >----- > > > > > > > > Can you post a complete (compilable) example please. > > > > > > Vinod can you please post a complete compilable example? > > > It is impossible to get anything done about your issue without stand > > > alone test code. > > Ok, make sure you have 'device twa' in your kernel configuration > > file, and apply these patches to /sys/dev/twa/twa.c. > > This patch causes the problem: > > "stand alone" means a single foo.c file that shows the problem you want > fixed. > I cannot submit a GCC bug report with a tarball of the entire FreeBSD > kernel. I've taken the liberty to write up an example here. Not sure if this is a bug or not: cc -O -pipe -c -fno-builtin -ffreestanding memset_bug.c Take a look at what is generated: objdump --disassemble memset_bug.o You'll see that instead of performing the inline code generation for memset, the compiler generates a call to memset in the case of the assignment of {0}. memset_bug.c: #include static __inline void * memset(void *b, int c, size_t len) { char *bb; if (c == 0) bzero(b, len); else for (bb = (char *)b; len--; ) *bb++ = c; return (b); } void bug (void) { int buf[100] = { 0 }; memset (buf, sizeof(buf), 0); printf ("%d\n", buf[0]); } Attached as well. Cheers, Sean --=-wLOup4CYUrnuKOU6OdqB-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 22:46:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28BA016A4CE; Thu, 24 Mar 2005 22:46:09 +0000 (GMT) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE4043D54; Thu, 24 Mar 2005 22:46:08 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j2OMk3vV006966 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Mar 2005 09:46:04 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j2OMk27l048346; Fri, 25 Mar 2005 09:46:03 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j2OMk2np048345; Fri, 25 Mar 2005 09:46:02 +1100 (EST) (envelope-from pjeremy) Date: Fri, 25 Mar 2005 09:46:02 +1100 From: Peter Jeremy To: Vinod Kashyap Message-ID: <20050324224602.GC43123@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 22:46:09 -0000 On Thu, 2005-Mar-24 12:03:19 -0800, Vinod Kashyap wrote: [ char x[100] = { 0 }; ] >A statement like this (auto and not static) I'd point out that this is the first time that you've mentioned that the variable is auto. Leaving out critical information will not encourage people to help you. > is necessary if you >are dealing with re-entrancy. This isn't completely true. The preferred approach is: char *x; x = malloc(100, MEM_POOL_xxx, M_ZERO | M_WAITOK); (with a matching free() later). > Whatever the issues with wastage or >bad performance, a programmer should definitely be able to do it, >if he so desires. Again, untrue. The FreeBSD kernel is not a standard C environment. Kernel stack is a relatively small, fixed size and using excessive kernel stack will lead to panics. Increasing the kernel stack size is undesirable because it's expensive in RAM consumption. >How is it then, that an explicit call to memset (like in my example) works? The code auto char x[100] = {0}; is equivalent to auto char x[100]; memset(x, 0, sizeof(x)); but memset only exists as a static inline function (defined in libkern.h). If an explicit call to memset works then the problem would appear to be that the compiler's implicit expansion is failing to detect the static inline definition, and generating an external reference which can't be satisfied. This would seem to be a gcc bug. >2. I should have mentioned that I don't see the problem if I am > building only the kernel module. It happens only when I am building > the kernel integrating the module containing the example code. This is the opposite of what you implied previously. There are some differences in how kernel modules are built so this How about posting a (short) compilable piece of C code that shows the problem. I would expect that an "nm" of the resultant object would show "U memset" when the code was compiled for linking into the kernel and " t memset" or not reference memset at all when compiled as a module. -- Peter Jeremy From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:16:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B86816A4CE; Thu, 24 Mar 2005 23:16:04 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D16443D2D; Thu, 24 Mar 2005 23:16:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2ONEPva076526; Thu, 24 Mar 2005 16:14:25 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <42434984.3050807@samsco.org> Date: Thu, 24 Mar 2005 16:13:08 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <200503232122.01937.peter@wemm.org> <86acosykew.fsf@xps.des.no> <42431F9D.5080906@samsco.org> <20050324220259.GA770@drjekyll.mkbuelow.net> In-Reply-To: <20050324220259.GA770@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:16:04 -0000 Matthias Buelow wrote: > Scott Long writes: > > >>No it doesn't. See the gymnastics that Bill Paul had to do recently in >>the iee80211 code to get around the insane inlining that gcc does with >>-O2. I'm not saying that gcc produces incorrect code, but I am saying >>that there is very strong evidence that it produces code that is >>incompatible with the restrictions inherent to the kernel, mainly that >>stack space is not infinite. > > > I wonder how this is being done elsewhere, on NetBSD, everything is > built with -O2 and has been for several years afair. > Not that I care much about it but apparently it doesn't seem to be > such a big problem everywhere? > > mkb. > I'm sure that it's highly dependent on the version of gcc in use and the other -f flags that are passed to it, neither of which I'm familiar with in NetBSD. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:22:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 431B416A4CE for ; Thu, 24 Mar 2005 23:22:11 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9254843D5C for ; Thu, 24 Mar 2005 23:22:10 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2ONM2X4010291; Thu, 24 Mar 2005 18:22:03 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 18:22:00 -0500 User-Agent: KMail/1.6.2 References: <20050324214956.GA99087@dragon.NUXI.org> <1111702231.2655.6.camel@server.mcneil.com> In-Reply-To: <1111702231.2655.6.camel@server.mcneil.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200503241822.00480.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 07:29:35 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:22:11 -0000 On Thursday 24 March 2005 05:10 pm, Sean McNeil wrote: > On Thu, 2005-03-24 at 13:49 -0800, David O'Brien wrote: > > Please don't top-post -- it destroys context. [Format recovered] > > > > On Thu, Mar 24, 2005 at 12:46:41PM -0800, Vinod Kashyap wrote: > > > > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > > > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > > > > >If any kernel module has the following, or a similar line > > > > > > in it: ----- > > > > > >char x[100] = {0}; > > > > > >----- > > > > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for > > > > > > amd64 as of 03/19/05, fails with the following message at > > > > > > the > > > > > > > > time of linking: > > > > > >"undefined reference to `memset'". > > > > > > > > > > > >The same problem is not seen on i386. > > > > > > > > > > > >The problem goes away if the above line is changed to: > > > > > >----- > > > > > >char x[100]; > > > > > >memset(x, 0, 100); > > > > > >----- > > > > > > > > > > Can you post a complete (compilable) example please. > > > > > > > > Vinod can you please post a complete compilable example? > > > > It is impossible to get anything done about your issue > > > > without stand alone test code. > > > > > > Ok, make sure you have 'device twa' in your kernel > > > configuration file, and apply these patches to > > > /sys/dev/twa/twa.c. > > > This patch causes the problem: > > > > "stand alone" means a single foo.c file that shows the problem > > you want fixed. > > I cannot submit a GCC bug report with a tarball of the entire > > FreeBSD kernel. > > I've taken the liberty to write up an example here. Not sure if > this is a bug or not: > > cc -O -pipe -c -fno-builtin -ffreestanding memset_bug.c > > Take a look at what is generated: > > objdump --disassemble memset_bug.o > > You'll see that instead of performing the inline code generation > for memset, the compiler generates a call to memset in the case of > the assignment of {0}. Have you tried -minline-all-stringops/-mno-inline-all-stringops? Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:26:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBB1B16A4CE for ; Thu, 24 Mar 2005 23:26:50 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7072B43D1D for ; Thu, 24 Mar 2005 23:26:50 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2ONQmjj010408; Thu, 24 Mar 2005 18:26:50 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 18:26:46 -0500 User-Agent: KMail/1.6.2 References: <20050324214956.GA99087@dragon.NUXI.org> <1111702231.2655.6.camel@server.mcneil.com> In-Reply-To: <1111702231.2655.6.camel@server.mcneil.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200503241826.46663.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 07:29:35 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:26:51 -0000 On Thursday 24 March 2005 05:10 pm, Sean McNeil wrote: --- >8 --- SNIP!!! --- >8 --- > void bug (void) > { > int buf[100] = { 0 }; > > memset (buf, sizeof(buf), 0); ^^^^^^^^^^^^^^ memset (buf, 0, sizeof(buf)); Right? ;-) Jung-uk Kim > printf ("%d\n", buf[0]); > } --- >8 --- SNIP!!! --- >8 --- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:44:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20B7C16A4CE for ; Thu, 24 Mar 2005 23:44:25 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B982643D2D for ; Thu, 24 Mar 2005 23:44:24 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 6C9FEF3F2B; Thu, 24 Mar 2005 15:44:24 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02642-08; Thu, 24 Mar 2005 15:44:23 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 38132F3EE8; Thu, 24 Mar 2005 15:44:23 -0800 (PST) From: Sean McNeil To: Jung-uk Kim In-Reply-To: <200503241822.00480.jkim@niksun.com> References: <20050324214956.GA99087@dragon.NUXI.org> <1111702231.2655.6.camel@server.mcneil.com> <200503241822.00480.jkim@niksun.com> Content-Type: text/plain Date: Thu, 24 Mar 2005 15:44:22 -0800 Message-Id: <1111707862.37802.14.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:44:25 -0000 On Thu, 2005-03-24 at 18:22 -0500, Jung-uk Kim wrote: > On Thursday 24 March 2005 05:10 pm, Sean McNeil wrote: > > On Thu, 2005-03-24 at 13:49 -0800, David O'Brien wrote: > > > Please don't top-post -- it destroys context. [Format recovered] > > > > > > On Thu, Mar 24, 2005 at 12:46:41PM -0800, Vinod Kashyap wrote: > > > > > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > > > > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > > > > > >If any kernel module has the following, or a similar line > > > > > > > in it: ----- > > > > > > >char x[100] = {0}; > > > > > > >----- > > > > > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for > > > > > > > amd64 as of 03/19/05, fails with the following message at > > > > > > > the > > > > > > > > > > time of linking: > > > > > > >"undefined reference to `memset'". > > > > > > > > > > > > > >The same problem is not seen on i386. > > > > > > > > > > > > > >The problem goes away if the above line is changed to: > > > > > > >----- > > > > > > >char x[100]; > > > > > > >memset(x, 0, 100); > > > > > > >----- > > > > > > > > > > > > Can you post a complete (compilable) example please. > > > > > > > > > > Vinod can you please post a complete compilable example? > > > > > It is impossible to get anything done about your issue > > > > > without stand alone test code. > > > > > > > > Ok, make sure you have 'device twa' in your kernel > > > > configuration file, and apply these patches to > > > > /sys/dev/twa/twa.c. > > > > This patch causes the problem: > > > > > > "stand alone" means a single foo.c file that shows the problem > > > you want fixed. > > > I cannot submit a GCC bug report with a tarball of the entire > > > FreeBSD kernel. > > > > I've taken the liberty to write up an example here. Not sure if > > this is a bug or not: > > > > cc -O -pipe -c -fno-builtin -ffreestanding memset_bug.c > > > > Take a look at what is generated: > > > > objdump --disassemble memset_bug.o > > > > You'll see that instead of performing the inline code generation > > for memset, the compiler generates a call to memset in the case of > > the assignment of {0}. > > Have you tried -minline-all-stringops/-mno-inline-all-stringops? No, I was just trying to be helpful. Anyone can take the example I provided and do whatever they wish with it. I honestly do not have the time to fiddle with this much more than I already have. Sorry. The only concern I have with this is if gcc is doing the right thing here. Should memset be checked and expanded as an inline function when used within the initializer? IMHO, yes. All that being said, testing took less time that writing this email :) so..... with -mno-inline-all-stringops, no difference. with -minline-all-stringops, wow! memset inline function is gone and the code is way smaller: Disassembly of section .text: 0000000000000000 : 0: 48 81 ec 98 01 00 00 sub $0x198,%rsp 7: 48 89 e7 mov %rsp,%rdi a: fc cld b: b9 32 00 00 00 mov $0x32,%ecx 10: b8 00 00 00 00 mov $0x0,%eax 15: f3 48 ab repz stos %rax,%es:(%rdi) 18: 8b 34 24 mov (%rsp),%esi 1b: bf 00 00 00 00 mov $0x0,%edi 20: e8 00 00 00 00 callq 25 25: 48 81 c4 98 01 00 00 add $0x198,%rsp 2c: c3 retq as opposed to (with -O): Disassembly of section .text: 0000000000000000 : 0: 48 81 ec 98 01 00 00 sub $0x198,%rsp 7: 48 89 e7 mov %rsp,%rdi a: ba 90 01 00 00 mov $0x190,%edx f: be 00 00 00 00 mov $0x0,%esi 14: e8 27 00 00 00 callq 40 19: 8b 34 24 mov (%rsp),%esi 1c: bf 00 00 00 00 mov $0x0,%edi 21: b8 00 00 00 00 mov $0x0,%eax 26: e8 00 00 00 00 callq 2b 2b: 48 81 c4 98 01 00 00 add $0x198,%rsp 32: c3 retq 33: 66 data16 34: 66 data16 35: 66 data16 36: 90 nop 37: 66 data16 38: 66 data16 39: 90 nop 3a: 66 data16 3b: 66 data16 3c: 90 nop 3d: 66 data16 3e: 66 data16 3f: 90 nop 0000000000000040 : 40: 53 push %rbx 41: 48 89 fb mov %rdi,%rbx 44: 85 f6 test %esi,%esi 46: 75 0f jne 57 48: 48 89 d6 mov %rdx,%rsi 4b: b8 00 00 00 00 mov $0x0,%eax 50: e8 00 00 00 00 callq 55 55: eb 1b jmp 72 57: 48 89 f8 mov %rdi,%rax 5a: 48 ff ca dec %rdx 5d: 48 83 fa ff cmp $0xffffffffffffffff,%rdx 61: 74 0f je 72 63: 40 88 30 mov %sil,(%rax) 66: 48 ff c0 inc %rax 69: 48 ff ca dec %rdx 6c: 48 83 fa ff cmp $0xffffffffffffffff,%rdx 70: 75 f1 jne 63 72: 48 89 d8 mov %rbx,%rax 75: 5b pop %rbx 76: c3 retq Note, with -O (default for 5.x), a local version of memset is created, so all is well. As you can see with nm, 0000000000000000 T bug U bzero 0000000000000040 t memset U printf With -O2 (default for -current), there is no local version of memset. This could be considered a bug as well. nm shows 0000000000000000 T bug U memset U printf Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:45:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3314416A4CE for ; Thu, 24 Mar 2005 23:45:14 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id D088C43D39 for ; Thu, 24 Mar 2005 23:45:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DD11B511D2; Thu, 24 Mar 2005 15:45:12 -0800 (PST) Date: Thu, 24 Mar 2005 15:45:12 -0800 From: Kris Kennaway To: amd64@FreeBSD.org Message-ID: <20050324234511.GA59281@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:45:14 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I get this consistently when trying to cross-build amd64 RELENG_5 world on i386: ===> csu/i386-elf cc -m32 -march=athlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT -I/usr/obj/amd64/a/portbuild/amd64/5/src/lib32/u sr/include -L/usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/lib32 -B/usr/obj/amd64/a/portbuild/amd64/5/src/li b32/usr/lib32 -O -pipe -I/a/portbuild/amd64/5/src/lib/csu/i386-elf/../common -I/a/portbuild/amd64/5/src/lib/csu/ i386-elf/../../libc/include -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prot otypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-al ign -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c crt1.c In file included from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/sys/types.h:44, from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/sys/param.h:61, from /a/portbuild/amd64/5/src/lib/csu/i386-elf/../common/crtbrand.c:29, from crt1.c:36: /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h: In function `__bswap64': /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: right shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: right shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: left shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: left shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: left shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: left shift count >= width of type /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:158: warning: left shift count >= width of type *** Error code 1 Any ideas? I need to get this to work for 5.4-RELEASE package builds. Kris --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ1EGWry0BWjoQKURAoWcAJ9M2CB+SszASyNV/AOBcAT1j6KbJACbB5fb AxaQxeKJnyAXIdjKmJAGKeM= =icYc -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:45:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9B7D16A4CE for ; Thu, 24 Mar 2005 23:45:51 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A9A843D2F for ; Thu, 24 Mar 2005 23:45:51 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so649742wra for ; Thu, 24 Mar 2005 15:45:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=c4UL9N0njyGLGaosqixrzQYxW0VTQa8/JCM+UfYLBxtXK2sHxGgfOmK9WiSdVRRC3WwJAO7pzHOQUCW73as5dGMDQPucoXdE+SQfX9Od2wYOFzepF4W7Jq45Y4u12hWTxFy7PK5SpY117UBpanO9PBWkqpIAjlS8Dot/A250lH0= Received: by 10.54.98.8 with SMTP id v8mr615768wrb; Thu, 24 Mar 2005 15:45:50 -0800 (PST) Received: by 10.54.40.69 with HTTP; Thu, 24 Mar 2005 15:45:50 -0800 (PST) Message-ID: <2fd864e05032415452721de81@mail.gmail.com> Date: Thu, 24 Mar 2005 15:45:50 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050324215445.GB99206@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org> <2fd864e05032412501c001a5d@mail.gmail.com> <20050324215445.GB99206@dragon.NUXI.org> Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:45:51 -0000 On Thu, 24 Mar 2005 13:54:45 -0800, David O'Brien wrote: > On Thu, Mar 24, 2005 at 12:50:13PM -0800, Astrodog wrote: > > On Thu, 24 Mar 2005 12:10:36 -0800, David O'Brien wrote: > > > On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote: > > > > How could we denote a linux32 dependancy? > > > > > > I don't follow. The current idea is that the linux_base port when > > > installed for FreeBSD will install both 32-bit and 64-bit[*] bits. > > > > > > [*] When 64-bit Linux support is later added. We have enough polishing > > > to do to just support all the things we've already got to the standards > > > people expect of FreeBSD. > > > -- > > > -- David (obrien@FreeBSD.org) > > > > > > > We have 2 problems, that I see. > > > > #1. Linux32 doesn't appear to be addressed for dependancies at all, > > almost every linux-something port I've found, calls itsself i386 only, > > and sometimes has minor RPM issues. > > What are the minor RPM issues? I knew there are some (see archives for > the arguments over the way we currently igngore them). But a summary of > current issues would be good. > The two that come up, that I've seen, Most all of the ports that rely on Linux compat, linux-jdk, linux-mozilla, etc, don't use the RPM properly, they're labeled ONLY FOT ARCHS i386. These are fixed with just adding amd64 to that list. Also, any port that attempts to use system RPM seems to have problems, when RPM tells it that its on the wrong arch. > 'amd64# cd /usr/ports/print/acroread ; make install' > worked for me at work. > > > #2. With IA32 Compatibility, it should be possible to install > > i386-only ports, and packages in quite a few cases, because of the > > binary compatibility stuff. I'm not sure how this could be handled > > either, since it would require a specific kernel option be enabled.... > > much like Linux32, I suppose. > > Assume that if someone goes out of their way to install a 32-bit port, > they have not removed the IA32 support from their kernel. This is now in > the default GENERIC config for 5.4. > Currently, without manual fetching and whatnot, you cannot easily install i386 packages. With IA32 support included, it should be possible to install 32-bit packages, and if the crosscompile is viable, 32-bit only ports. --- Harrison Grundy > -- > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:47:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3696D16A4CE for ; Thu, 24 Mar 2005 23:47:58 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 140F943D1F for ; Thu, 24 Mar 2005 23:47:58 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C0A3CF3F30; Thu, 24 Mar 2005 15:47:57 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83374-10; Thu, 24 Mar 2005 15:47:56 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id D356EF3EE8; Thu, 24 Mar 2005 15:47:56 -0800 (PST) From: Sean McNeil To: Jung-uk Kim In-Reply-To: <200503241826.46663.jkim@niksun.com> References: <20050324214956.GA99087@dragon.NUXI.org> <1111702231.2655.6.camel@server.mcneil.com> <200503241826.46663.jkim@niksun.com> Content-Type: text/plain Date: Thu, 24 Mar 2005 15:47:56 -0800 Message-Id: <1111708076.37802.15.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 23:47:58 -0000 On Thu, 2005-03-24 at 18:26 -0500, Jung-uk Kim wrote: > On Thursday 24 March 2005 05:10 pm, Sean McNeil wrote: > --- >8 --- SNIP!!! --- >8 --- > > void bug (void) > > { > > int buf[100] = { 0 }; > > > > memset (buf, sizeof(buf), 0); > ^^^^^^^^^^^^^^ > memset (buf, 0, sizeof(buf)); > > Right? ;-) Right :) Same results, though. Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 02:28:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B45F16A4CE; Fri, 25 Mar 2005 02:28:27 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7C7F43D31; Fri, 25 Mar 2005 02:28:26 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j2P2SIHn019703; Fri, 25 Mar 2005 13:28:18 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j2P2SES5017665; Fri, 25 Mar 2005 13:28:15 +1100 Date: Fri, 25 Mar 2005 13:28:13 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Nick Barnes In-Reply-To: <90609.1111660565@thrush.ravenbrook.com> Message-ID: <20050325131358.T215@delplex.bde.org> References: <90609.1111660565@thrush.ravenbrook.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 02:28:27 -0000 On Thu, 24 Mar 2005, Nick Barnes wrote: > At 2005-03-24 08:31:14+0000, Bruce Evans writes: > >> what is gcc to do when -fno-builtin tells it to turn off its >> builtins and -ffreestanding tells it that the relevant interfaces >> might not exist in the library? > > Plainly, GCC should generate code which fills the array with zeroes. > It's not obliged to generate code which calls memset (either builtin > or in a library). If it knows that it can do so, then fine. > Otherwise it must do it the Old Fashioned Way. So this is surely a > bug in GCC. > > Nick B, who used to write compilers for a living But the compiler can require the Old Fashioned Way to be in the library. libgcc.a is probably part of gcc even in the freestanding case. The current implementation of libgcc.a won't all work in the freestanding case, since parts of it call stdio, but some parts of it are needed and work (e.g., __divdi3() on i386's at least). The kernel doesn't use libgcc.a, but it knows that __divdi3() and friends are needed and implements them in its libkern. Strictly, it should do something similar for memset(). I think the only bugs in gcc here are that the function it calls is in the application namespace in the freestanding case, and that the requirements for freestanding implementations are not all documented. The requirement for memset() and friends _is_ documented (in gcc.info), but the requirement for __divdi3() and friends are only documented indirectly by the presence of these functions in libgcc.a. Bruce From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 03:00:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6061616A4CE; Fri, 25 Mar 2005 03:00:13 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2B5243D1F; Fri, 25 Mar 2005 03:00:12 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j2P309Hn024372; Fri, 25 Mar 2005 14:00:09 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j2P306S5023286; Fri, 25 Mar 2005 14:00:07 +1100 Date: Fri, 25 Mar 2005 14:00:05 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Peter Jeremy In-Reply-To: <20050324224602.GC43123@cirb503493.alcatel.com.au> Message-ID: <20050325133228.S215@delplex.bde.org> References: <20050324224602.GC43123@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-stable@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 03:00:13 -0000 On Fri, 25 Mar 2005, Peter Jeremy wrote: > On Thu, 2005-Mar-24 12:03:19 -0800, Vinod Kashyap wrote: > [ char x[100] = { 0 }; ] >> A statement like this (auto and not static) > > I'd point out that this is the first time that you've mentioned that > the variable is auto. Leaving out critical information will not > encourage people to help you. It was obviously auto, since memset() would not have been called for a global variable. >> is necessary if you >> are dealing with re-entrancy. > > This isn't completely true. The preferred approach is: > char *x; > x = malloc(100, MEM_POOL_xxx, M_ZERO | M_WAITOK); > (with a matching free() later). This is also preferred to alloca() and C99's dynamic arrays. BTW, the kernel has had some dubious examples of dynamic arrays in very important code since long before C99 existed. vm uses some dynamic arrays, and this is only safe since the size of the arrays is bounded and small. But when the size of an array is bounded and small, dynamic allocation is just a pessimization -- it is more efficient to always allocate an array with the maximum size that might be needed. >> How is it then, that an explicit call to memset (like in my example) works? > > The code > auto char x[100] = {0}; > is equivalent to > auto char x[100]; > memset(x, 0, sizeof(x)); > but memset only exists as a static inline function (defined in libkern.h). > If an explicit call to memset works then the problem would appear to be > that the compiler's implicit expansion is failing to detect the static > inline definition, and generating an external reference which can't be > satisfied. This would seem to be a gcc bug. No, it is a feature :-). See my earlier reply. >> 2. I should have mentioned that I don't see the problem if I am >> building only the kernel module. It happens only when I am building >> the kernel integrating the module containing the example code. > > This is the opposite of what you implied previously. There are some > differences in how kernel modules are built so this > > How about posting a (short) compilable piece of C code that shows the > problem. I would expect that an "nm" of the resultant object would > show "U memset" when the code was compiled for linking into the kernel > and " t memset" or not reference memset at all when > compiled as a module. I deleted the actual example. Most likely it would fail at load time do to using memset(). Another possibility is for the code that needs memset to be unreachable in the module since it is inside an ifdef. Bruce From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 03:02:20 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0D7916A4CE; Fri, 25 Mar 2005 03:02:20 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0118343D2D; Fri, 25 Mar 2005 03:02:19 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDW0FY04.5SV; Thu, 24 Mar 2005 19:02:22 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032419051019735 ; Thu, 24 Mar 2005 19:05:11 -0800 From: "Vinod Kashyap" To: Peter Jeremy Date: Thu, 24 Mar 2005 19:01:17 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 03:02:21 -0000 > -----Original Message----- > From: Peter Jeremy [mailto:PeterJeremy@optushome.com.au] > Sent: Thursday, March 24, 2005 2:46 PM > To: Vinod Kashyap > Cc: freebsd-stable@freebsd.org; freebsd-amd64@freebsd.org > Subject: Re: undefined reference to `memset' > = > = > On Thu, 2005-Mar-24 12:03:19 -0800, Vinod Kashyap wrote: > [ char x[100] =3D { 0 }; ] > >A statement like this (auto and not static) > = > I'd point out that this is the first time that you've mentioned that > the variable is auto. Leaving out critical information will not > encourage people to help you. > = It is "char x[100] =3D {0};" and that's it. Doesn't it make it auto? Isn't auto the default? > > is necessary if you > >are dealing with re-entrancy. > = > This isn't completely true. The preferred approach is: > char *x; > x =3D malloc(100, MEM_POOL_xxx, M_ZERO | M_WAITOK); > (with a matching free() later). > = Well, I am in a function that is OS-independent, and cannot assume malloc (or a wrapper to it) is available. > > Whatever the issues with wastage or > >bad performance, a programmer should definitely be able to do it, > >if he so desires. > = > Again, untrue. The FreeBSD kernel is not a standard C environment. > Kernel stack is a relatively small, fixed size and using excessive > kernel stack will lead to panics. Increasing the kernel stack size is > undesirable because it's expensive in RAM consumption. > = Whatever that may be, I don't think the compiler should be stopping me from doing standard C stuff. I could be having this statement in my module with full knowledge that it would not cause a kernel stack overflow.= > >How is it then, that an explicit call to memset (like in my = > example) works? > = > The code > auto char x[100] =3D {0}; > is equivalent to > auto char x[100]; > memset(x, 0, sizeof(x)); > but memset only exists as a static inline function (defined = > in libkern.h). > If an explicit call to memset works then the problem would = > appear to be > that the compiler's implicit expansion is failing to detect the static > inline definition, and generating an external reference which can't be > satisfied. This would seem to be a gcc bug. > = > >2. I should have mentioned that I don't see the problem if I am > > building only the kernel module. It happens only when I = > am building > > the kernel integrating the module containing the example code. > = > This is the opposite of what you implied previously. There are some > differences in how kernel modules are built so this = > = No, it's not. This is what I wrote in my first e-mail: "building of the GENERIC kernel on FreeBSD 5 -STABLE for amd64". I just forgot to mention that the problem did not occur when I build only the module. This is possibly due to different gcc flags being used in the 2 cases. > How about posting a (short) compilable piece of C code that shows the > problem. I would expect that an "nm" of the resultant object would > show "U memset" when the code was compiled for linking into the kernel > and " t memset" or not reference memset at all when > compiled as a module. > = Just like the problem is not seen when I build only the module, it's not seen if I simply write a foo.c (with the example code) and compile it. That's the reason I posted the patch to /sys/dev/twa/twa.c, which would cause the problem if applied, and then followed with a kernel build. I can send the result of running nm on twa.o tomorrow. From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 03:15:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0E1D16A4CE; Fri, 25 Mar 2005 03:15:03 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B021143D1D; Fri, 25 Mar 2005 03:15:03 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 67BF3F3F44; Thu, 24 Mar 2005 19:15:03 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42082-03; Thu, 24 Mar 2005 19:15:02 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 70735F3F0E; Thu, 24 Mar 2005 19:15:02 -0800 (PST) From: Sean McNeil To: Vinod Kashyap In-Reply-To: References: Content-Type: text/plain Date: Thu, 24 Mar 2005 19:15:02 -0800 Message-Id: <1111720502.42823.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Peter Jeremy cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 03:15:04 -0000 Vinod, On Thu, 2005-03-24 at 19:01 -0800, Vinod Kashyap wrote: > Just like the problem is not seen when I build only the module, it's > not seen if I simply write a foo.c (with the example code) and compile it. > That's the reason I posted the patch to /sys/dev/twa/twa.c, which would > cause the problem if applied, and then followed with a kernel build. > I can send the result of running nm on twa.o tomorrow. Please take a look at other messages in this thread, like some of the ones I have posted. They clearly show your problem in a small example and how it is happening in the -O2 case as memset is being optimized away. -O would appear to do the right thing and adding -minline-all-stringops (at either optimization level) would produce even better code. Cheers, Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 03:52:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17CAB16A4CE; Fri, 25 Mar 2005 03:52:48 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C5943D41; Fri, 25 Mar 2005 03:52:47 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDW2S101.STY; Thu, 24 Mar 2005 19:52:49 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032419554319947 ; Thu, 24 Mar 2005 19:55:43 -0800 From: "Vinod Kashyap" To: Sean McNeil Date: Thu, 24 Mar 2005 19:51:49 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: cc: Peter Jeremy cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 03:52:48 -0000 > -----Original Message----- > From: Sean McNeil [mailto:sean@mcneil.com] > Sent: Thursday, March 24, 2005 7:15 PM > To: Vinod Kashyap > Cc: Peter Jeremy; freebsd-stable@freebsd.org; = > freebsd-amd64@freebsd.org > Subject: RE: undefined reference to `memset' > = > = > Vinod, > = > On Thu, 2005-03-24 at 19:01 -0800, Vinod Kashyap wrote: > > Just like the problem is not seen when I build only the module, it's > > not seen if I simply write a foo.c (with the example code) = > and compile it. > > That's the reason I posted the patch to /sys/dev/twa/twa.c, = > which would > > cause the problem if applied, and then followed with a kernel build. > > I can send the result of running nm on twa.o tomorrow. > = > Please take a look at other messages in this thread, like some of the > ones I have posted. They clearly show your problem in a small example > and how it is happening in the -O2 case as memset is being optimized > away. -O would appear to do the right thing and adding > -minline-all-stringops (at either optimization level) would = > produce even > better code. > = I did look at your posting Sean, thanks. But did you see the "undefined reference to `memset'" linker error when you built it? It's obvious that a reference to memset is being generated by the initialization of an array of 100 bytes to 0. The linker is getting the needed memset if you build a stand alone program, or even build a stand= alone kernel module, but is not being able to find it when building the kernel itself. This implies to me that it is a difference in the use of flags, or linking/not linking with particular libraries that's causing the problem. I am also confused as to how an explicit call to memset works, when compiler generated call doesn't! Are we talking 2 different memset's here? Maybe a memset and an __memset? From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 04:09:24 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F76616A4CE; Fri, 25 Mar 2005 04:09:24 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C5B943D1F; Fri, 25 Mar 2005 04:09:24 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id EF48AF3F44; Thu, 24 Mar 2005 20:09:23 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42082-06; Thu, 24 Mar 2005 20:09:22 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B4B79F3EDB; Thu, 24 Mar 2005 20:09:22 -0800 (PST) From: Sean McNeil To: Vinod Kashyap In-Reply-To: References: Content-Type: text/plain Date: Thu, 24 Mar 2005 20:09:22 -0800 Message-Id: <1111723762.43056.15.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Peter Jeremy cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 04:09:24 -0000 On Thu, 2005-03-24 at 19:51 -0800, Vinod Kashyap wrote: > I did look at your posting Sean, thanks. But did you see the > "undefined reference to `memset'" linker error when you built it? > It's obvious that a reference to memset is being generated by > the initialization of an array of 100 bytes to 0. The linker is getting > the needed memset if you build a stand alone program, or even build a stand > alone kernel module, but is not being able to find it when building > the kernel itself. This implies to me that it is a difference in > the use of flags, or linking/not linking with particular libraries > that's causing the problem. Here is what I believe is happening: There exists an inline function called memset. This inline function _should_ replace any uses of memset within the function when compiled with optimization (-O or -O2). In any event that a call is not inlined, a local copy of memset should be emitted and used. This is what happens with -O, but not with -O2. This is clearly seen by an objdump at each optimization. For -O, a local copy of memset is emitted and used. For -O2, memset is still called, but the memset code is optimized away. This is a bug, IMHO, in various ways. 1) -O2 is being too agressive and eliminating memset when it shouldn't. 2) both optimized versions are not replacing the call to memset with the inline code. Here is one of several issues with the amd64 compiler used at -O2 vs. -O. There are others as well. Note: this comment inserted for the sole purpose of adding flame-bait :) You do not need to link to show this. In fact, since this is a standard program and memset is available in libc, you will not see the problem in a link. You need to look at the nm output and objdump to understand what is happening. > I am also confused as to how an explicit call to memset works, > when compiler generated call doesn't! Are we talking 2 different > memset's here? Maybe a memset and an __memset? The problem is that the compiler is inserting the memset call. Either it is happening too late for inlining to occur or it is done in some fashion that doesn't lend to inlining by the compiler. The call inside the function is handled like all other code and is properly identified and inlined. We are not talking about 2 different memset functions, no. We are talking about 2 different mechanisms for using memset where one is not properly inlined and the other is. HTH, Sean From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 06:20:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 919F116A4CE for ; Fri, 25 Mar 2005 06:20:35 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C0A343D1D for ; Fri, 25 Mar 2005 06:20:35 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2P6KY2G007692; Thu, 24 Mar 2005 22:20:34 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2P6KXJK007691; Thu, 24 Mar 2005 22:20:33 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 22:20:33 -0800 From: "David O'Brien" To: Kris Kennaway Message-ID: <20050325062033.GA7662@dragon.NUXI.org> References: <20050324234511.GA59281@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050324234511.GA59281@xor.obsecurity.org> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@FreeBSD.org Subject: Re: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 06:20:35 -0000 On Thu, Mar 24, 2005 at 03:45:12PM -0800, Kris Kennaway wrote: > I get this consistently when trying to cross-build amd64 RELENG_5 world on i386: Which OS version on the i386 machine? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 06:23:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40DB216A4CE for ; Fri, 25 Mar 2005 06:23:18 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BFE43D48 for ; Fri, 25 Mar 2005 06:23:18 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2P6NHUs007768; Thu, 24 Mar 2005 22:23:17 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2P6NHsT007767; Thu, 24 Mar 2005 22:23:17 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 22:23:17 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20050325062317.GB7662@dragon.NUXI.org> References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org> <2fd864e05032412501c001a5d@mail.gmail.com> <20050324215445.GB99206@dragon.NUXI.org> <2fd864e05032415452721de81@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e05032415452721de81@mail.gmail.com> X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 06:23:18 -0000 On Thu, Mar 24, 2005 at 03:45:50PM -0800, Astrodog wrote: > On Thu, 24 Mar 2005 13:54:45 -0800, David O'Brien wrote: > > On Thu, Mar 24, 2005 at 12:50:13PM -0800, Astrodog wrote: > > > We have 2 problems, that I see. > > > #1. Linux32 doesn't appear to be addressed for dependancies at all, > > > almost every linux-something port I've found, calls itsself i386 only, > > > and sometimes has minor RPM issues. > > > > What are the minor RPM issues? I knew there are some (see archives for > > the arguments over the way we currently igngore them). But a summary of > > current issues would be good. > > The two that come up, that I've seen, > Most all of the ports that rely on Linux compat, linux-jdk, > linux-mozilla, etc, don't use the RPM properly, they're labeled ONLY > FOT ARCHS i386. These are fixed with just adding amd64 to that list. Please post a typescript clearly showing the problem; or explain the situation in detail. The working Acroread on my amd64 desktop says things are working tolerably well. > Currently, without manual fetching and whatnot, you cannot easily > install i386 packages. With IA32 support included, it should be > possible to install 32-bit packages, and if the crosscompile is > viable, 32-bit only ports. This needs some architectural work that no one has wrapped their heads around. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 06:25:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44A9116A4CE for ; Fri, 25 Mar 2005 06:25:30 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1175B43D58 for ; Fri, 25 Mar 2005 06:25:30 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j2P6PS6f007836; Thu, 24 Mar 2005 22:25:28 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j2P6PSak007835; Thu, 24 Mar 2005 22:25:28 -0800 (PST) (envelope-from obrien) Date: Thu, 24 Mar 2005 22:25:28 -0800 From: "David O'Brien" To: Vinod Kashyap Message-ID: <20050325062528.GC7662@dragon.NUXI.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 06:25:30 -0000 On Thu, Mar 24, 2005 at 02:01:56PM -0800, Vinod Kashyap wrote: > > > > Vinod can you please post a complete compilable example? > > > > It is impossible to get anything done about your issue > > without stand > > > > alone test code. > > > Ok, make sure you have 'device twa' in your kernel configuration > > > file, and apply these patches to /sys/dev/twa/twa.c. > > > This patch causes the problem: > > > > "stand alone" means a single foo.c file that shows the > > problem you want > > fixed. > > I cannot submit a GCC bug report with a tarball of the entire FreeBSD > > kernel. > > > > Can you not submit it with the patch I sent? Submit the entire /usr/src/sys kernel source?? > A "stand alone" foo.c will have to be a new module under a new > directory (/sys/dev/foo), with its own Makefile, with changes to > /sys/conf/files, and an entry in GENERIC. A module would still depend on files in /usr/share/mk, /usr/src/sys/conf, /usr/src/sys/modules, /usr/src/sys/dev/foo. NO! nothing other than a single file -- foo.c in my home directory that shows the problem is a "stand alone" example. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 06:59:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F3216A4CE for ; Fri, 25 Mar 2005 06:59:39 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 886E043D1F for ; Fri, 25 Mar 2005 06:59:38 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P6xbIM005124; Fri, 25 Mar 2005 08:59:37 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 27915-04; Fri, 25 Mar 2005 08:59:54 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P6xaFG005121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 08:59:36 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2P6xvnW076004; Fri, 25 Mar 2005 08:59:57 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 08:59:57 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20050325065957.GC75626@ip.net.ua> References: <20050324234511.GA59281@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2JFBq9zoW8cOFH7v" Content-Disposition: inline In-Reply-To: <20050324234511.GA59281@xor.obsecurity.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org Subject: Re: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 06:59:39 -0000 --2JFBq9zoW8cOFH7v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 03:45:12PM -0800, Kris Kennaway wrote: > I get this consistently when trying to cross-build amd64 RELENG_5 world o= n i386: >=20 > =3D=3D=3D> csu/i386-elf > cc -m32 -march=3Dathlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT -I/usr= /obj/amd64/a/portbuild/amd64/5/src/lib32/u > sr/include -L/usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/lib32 -B/= usr/obj/amd64/a/portbuild/amd64/5/src/li > b32/usr/lib32 -O -pipe -I/a/portbuild/amd64/5/src/lib/csu/i386-elf/../com= mon -I/a/portbuild/amd64/5/src/lib/csu/ > i386-elf/../../libc/include -Wsystem-headers -Werror -Wall -Wno-format-y2= k -W -Wno-unused-parameter -Wstrict-prot > otypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Ww= rite-strings -Wswitch -Wshadow -Wcast-al > ign -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredu= ndant-decls -c crt1.c > In file included from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/inc= lude/sys/types.h:44, > from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/inc= lude/sys/param.h:61, > from /a/portbuild/amd64/5/src/lib/csu/i386-elf/../common= /crtbrand.c:29, > from crt1.c:36: > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= In function `__bswap64': > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: right shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: right shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > *** Error code 1 >=20 > Any ideas? I need to get this to work for 5.4-RELEASE package builds. >=20 As Peter warned, this part wasn't tested at all in a cross-build environmen= t. Before we fix it, you can consider cross-building with NO_LIB32. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --2JFBq9zoW8cOFH7v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ7bsqRfpzJluFF4RAtGGAJ4xojU/aqPbq1EHIH2kmXdp5DpEgACfe39V 9dC8rm4W/BhHM3W3ccnPCOI= =GP1J -----END PGP SIGNATURE----- --2JFBq9zoW8cOFH7v-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 07:24:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9EC916A4CE for ; Fri, 25 Mar 2005 07:24:18 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2729F43D5A for ; Fri, 25 Mar 2005 07:24:18 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P7OHCl007922; Fri, 25 Mar 2005 09:24:17 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 28792-02; Fri, 25 Mar 2005 09:24:34 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P7OFxt007917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 09:24:16 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2P7OalQ076156; Fri, 25 Mar 2005 09:24:36 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 09:24:36 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20050325072436.GD75626@ip.net.ua> References: <20050324234511.GA59281@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1sNVjLsmu1MXqwQ/" Content-Disposition: inline In-Reply-To: <20050324234511.GA59281@xor.obsecurity.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org Subject: Re: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 07:24:19 -0000 --1sNVjLsmu1MXqwQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 03:45:12PM -0800, Kris Kennaway wrote: > I get this consistently when trying to cross-build amd64 RELENG_5 world o= n i386: >=20 > =3D=3D=3D> csu/i386-elf > cc -m32 -march=3Dathlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT -I/usr= /obj/amd64/a/portbuild/amd64/5/src/lib32/u > sr/include -L/usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/lib32 -B/= usr/obj/amd64/a/portbuild/amd64/5/src/li > b32/usr/lib32 -O -pipe -I/a/portbuild/amd64/5/src/lib/csu/i386-elf/../com= mon -I/a/portbuild/amd64/5/src/lib/csu/ > i386-elf/../../libc/include -Wsystem-headers -Werror -Wall -Wno-format-y2= k -W -Wno-unused-parameter -Wstrict-prot > otypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Ww= rite-strings -Wswitch -Wshadow -Wcast-al > ign -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredu= ndant-decls -c crt1.c > In file included from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/inc= lude/sys/types.h:44, > from /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/inc= lude/sys/param.h:61, > from /a/portbuild/amd64/5/src/lib/csu/i386-elf/../common= /crtbrand.c:29, > from crt1.c:36: > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= In function `__bswap64': > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: right shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: right shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h:= 158: warning: left shift count >=3D width of type > *** Error code 1 >=20 > Any ideas? I need to get this to work for 5.4-RELEASE package builds. >=20 It looks like the wrong version of endian.h header is used here: /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h which is the AMD64 version, rather than an i386 versopm from /usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/include/machine/endian.h I will look into this today (on HEAD). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --1sNVjLsmu1MXqwQ/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ7y0qRfpzJluFF4RArCyAJ9vJGpo9QHqruiyu98SpZWLnM150QCfaTpf 4qrathxm8dhrWAwBV++OMxQ= =SC27 -----END PGP SIGNATURE----- --1sNVjLsmu1MXqwQ/-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 07:47:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A091B16A4CE for ; Fri, 25 Mar 2005 07:47:42 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD81943D39 for ; Fri, 25 Mar 2005 07:47:41 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P7lekE009357; Fri, 25 Mar 2005 09:47:40 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 30017-10; Fri, 25 Mar 2005 09:47:57 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P7lchS009352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 09:47:39 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2P7lx1l076254; Fri, 25 Mar 2005 09:47:59 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 09:47:59 +0200 From: Ruslan Ermilov To: Dag-Erling Sm?rgrav Message-ID: <20050325074759.GE75626@ip.net.ua> References: <86ll8dgnx3.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EXKGNeO8l0xGFBjy" Content-Disposition: inline In-Reply-To: <86ll8dgnx3.fsf@xps.des.no> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@freebsd.org Subject: Re: testers wanted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 07:47:42 -0000 --EXKGNeO8l0xGFBjy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 02:43:04PM +0100, Dag-Erling Sm?rgrav wrote: > I need someone with an nForce3-based Opteron box running -CURRENT to > do the following: >=20 > - upgrade to a recent -CURRENT, verify that a GENERIC kernel with > NO_MIXED_MODE removed works properly *with apic enabled* >=20 > - build an unmodified GENERIC (*with* NO_MIXED_MODE) from the same > sources and boot it *with apic enabled* >=20 > Please provide verbose dmesg for both cases, as well as the contents > of /boot/loader.conf and /boot/device.hints. >=20 I will do it. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --EXKGNeO8l0xGFBjy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ8IvqRfpzJluFF4RAnHcAKCQlXITH+LjzJC0uUCOhamHAIZfQQCgmifx iwViluiwS4y8nK6UueurpCM= =YXJE -----END PGP SIGNATURE----- --EXKGNeO8l0xGFBjy-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 07:50:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 188DE16A4CE for ; Fri, 25 Mar 2005 07:50:00 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BADEC43D1D for ; Fri, 25 Mar 2005 07:49:59 +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 1DEjZu-0007MN-RR for amd64@freebsd.org; Fri, 25 Mar 2005 09:49:58 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Mar 2005 09:49:58 +0200 From: Danny Braniss Message-ID: Subject: INCLUDE_CONFIG_FILE broken? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 07:50:00 -0000 it seems that options INCLUDE_CONFIG_FILE in the kernel conf. file does not work: strings -n 3 /boot/kernel/kernel | sed -n 's/^___//p' _````QQQQ _ From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 08:51:15 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F93616A4CE for ; Fri, 25 Mar 2005 08:51:15 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCA5C43D46 for ; Fri, 25 Mar 2005 08:51:13 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id j2P8pAAG087846 for ; Fri, 25 Mar 2005 10:51:11 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <4243D111.1020904@he.iki.fi> Date: Fri, 25 Mar 2005 10:51:29 +0200 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: syscall sysret X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 08:51:15 -0000 Does amd64 freebsd always utilize syscall / sysret opcodes? Pete From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 09:46:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D51BF16A4CE for ; Fri, 25 Mar 2005 09:46:10 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE8F43D1D for ; Fri, 25 Mar 2005 09:46:09 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P9k5U6016572; Fri, 25 Mar 2005 11:46:05 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 40160-01; Fri, 25 Mar 2005 11:46:21 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2P9k2UP016559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 11:46:03 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2P9kNmb076790; Fri, 25 Mar 2005 11:46:23 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 11:46:18 +0200 From: Ruslan Ermilov To: Dag-Erling Sm?rgrav Message-ID: <20050325094618.GA76747@ip.net.ua> References: <86ll8dgnx3.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX" Content-Disposition: inline In-Reply-To: <86ll8dgnx3.fsf@xps.des.no> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@freebsd.org Subject: Re: testers wanted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 09:46:10 -0000 --yNb1oOkm5a9FJOVX Content-Type: multipart/mixed; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi DES, On Thu, Mar 24, 2005 at 02:43:04PM +0100, Dag-Erling Sm?rgrav wrote: > I need someone with an nForce3-based Opteron box running -CURRENT to > do the following: >=20 > - upgrade to a recent -CURRENT, verify that a GENERIC kernel with > NO_MIXED_MODE removed works properly *with apic enabled* >=20 Looks like it works, though I got one TIMEOUT - WRITE_DMA with it. I just used a stripped down GENERIC kernel with hw.apic.mixed_mode=3D1 set in /boot/loader.conf, which has the same effect as above. > - build an unmodified GENERIC (*with* NO_MIXED_MODE) from the same > sources and boot it *with apic enabled* >=20 Booted the same kernel with hw.apic.mixed_mode=3D0. It stalls (see the attached logs). > Please provide verbose dmesg for both cases, as well as the contents > of /boot/loader.conf and /boot/device.hints. >=20 /boot/loader.conf has some uninteresting stuff to load network and sound modules I need, and device.hints equals GENERIC.hints. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot.mixed_mode" Copyright (c) 1992-2005 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.0-CURRENT #3: Fri Mar 25 10:44:58 EET 2005 ru@hammer.runet:/usr/obj/usr/src/sys/HAMMER WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8068b000. Preloaded elf obj module "/boot/kernel/if_em.ko" at 0xffffffff8068b1d0. Preloaded elf obj module "/boot/kernel/if_xl.ko" at 0xffffffff8068b6f8. Preloaded elf obj module "/boot/kernel/miibus.ko" at 0xffffffff8068bc20. Preloaded elf obj module "/boot/kernel/snd_ich.ko" at 0xffffffff8068c148. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff8068c6b0. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193171 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1470007451 Hz CPU: AMD Opteron(tm) Processor 240 (1470.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 1073479680 (1023 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000789000 - 0x000000003e189fff, 1033900032 bytes (252417 pages) avail memory = 1028120576 (980 MB) APIC: CPU 0 has ACPI ID 1 MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high MADT: Interrupt override: source 14, irq 14 ioapic0: intpin 14 trigger: edge ioapic0: intpin 14 polarity: high MADT: Interrupt override: source 15, irq 15 ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000000 err: 0x0001000f pcm: 0x00010000 random: io: mem: null: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80015004 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=00d110de) AcpiOsDerivePciId: bus 0 dev 1 func 0 acpi0: Power Button (fixed) ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link0: irq 0 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link1: irq 11 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 20 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link2: irq 5 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 21 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: irq 0 on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link4: irq 5 on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 20 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link5: irq 10 on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 20 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link6: irq 11 on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 16 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link7: irq 0 on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base f0000000, size 27, enabled found-> vendor=0x10de, dev=0x00d1, revid=0xa4 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x00d0, revid=0xf6 bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00005000, size 6, enabled map[24]: type 4, range 32, base 00005040, size 6, enabled found-> vendor=0x10de, dev=0x00d4, revid=0xa4 bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base febfd000, size 12, enabled pcib0: matched entry for 0.2.INTA (src \\_SB_.LUS0:0) pci_link1: Picked IRQ 20 with weight 0 ioapic0: Changing polarity for pin 20 to high pcib0: slot 2 INTA routed to irq 20 via \\_SB_.LUS0 found-> vendor=0x10de, dev=0x00d7, revid=0xa5 bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base febfe000, size 12, enabled pcib0: matched entry for 0.2.INTB (src \\_SB_.LUS1:0) pci_link4: Picked IRQ 20 with weight 1 pcib0: slot 2 INTB routed to irq 20 via \\_SB_.LUS1 found-> vendor=0x10de, dev=0x00d7, revid=0xa5 bus=0, slot=2, func=1 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base febffc00, size 8, enabled pcib0: matched entry for 0.2.INTC (src \\_SB_.LUS2:0) pci_link5: Picked IRQ 20 with weight 2 pcib0: slot 2 INTC routed to irq 20 via \\_SB_.LUS2 found-> vendor=0x10de, dev=0x00d8, revid=0xa2 bus=0, slot=2, func=2 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=c, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 4, range 32, base 0000ec00, size 7, enabled map[18]: type 1, range 32, base febfb000, size 12, enabled pcib0: matched entry for 0.6.INTA (src \\_SB_.LAUI:0) pci_link2: Picked IRQ 21 with weight 0 ioapic0: Changing polarity for pin 21 to high pcib0: slot 6 INTA routed to irq 21 via \\_SB_.LAUI found-> vendor=0x10de, dev=0x00da, revid=0xa2 bus=0, slot=6, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=21 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x10de, dev=0x00d5, revid=0xa5 bus=0, slot=8, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x10de, dev=0x00dd, revid=0xa2 bus=0, slot=10, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x00d2, revid=0xa4 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x0b (2750 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0:1:1: Transition from D0 to D3 ohci0: mem 0xfebfd000-0xfebfdfff irq 20 at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfd000 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: 3 ports with 3 removable, self powered ohci1: mem 0xfebfe000-0xfebfefff irq 20 at device 2.1 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfe000 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: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfebffc00-0xfebffcff irq 20 at device 2.2 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfebffc00 ehci0: [GIANT-LOCKED] usb2: waiting for BIOS to give up control usb2: timed out waiting for BIOS usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered pcm0: port 0xe800-0xe8ff,0xec00-0xec7f mem 0xfebfb000-0xfebfbfff irq 21 at device 6.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe800 pcm0: Reserved 0x80 bytes for rid 0x14 type 4 at 0xec00 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features 20 bit DAC, 18 bit ADC, 5 bit master volume, Realtek 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, double rate PCM, reserved 1, center DAC, surround DAC, LFE DAC, reserved 4 pcm0: sndbuf_setmap 3db86000, 4000; 0xffffffffa5446000 -> 3db86000 pcm0: sndbuf_setmap 3db78000, 4000; 0xffffffffa544a000 -> 3db78000 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=7f ostat1=50 ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-slave: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=ff stat1=10 devices=0x8 ata1: [MPSAFE] pcib1: at device 10.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xc000-0xdfff pcib1: memory decode 0xfc800000-0xfc9fffff pcib1: prefetched decode 0xfff00000-0xfffff pci_link8: irq 11 on acpi0 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 17 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link9: irq 0 on acpi0 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link10: irq 10 on acpi0 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 19 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link11: irq 0 on acpi0 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 ACPI: Found matching pin for 0.6.INTA at func 0: 21 pci_link11: BIOS IRQ 21 for 0.6.INTA is invalid pci1: on pcib1 pci1: physical bus=1 map[10]: type 4, range 32, base 0000dc00, size 7, enabled pcib1: (null) requested I/O range 0xdc00-0xdc7f: in range map[14]: type 1, range 32, base fc9ffc00, size 7, enabled pcib1: (null) requested memory range 0xfc9ffc00-0xfc9ffc7f: good pcib1: matched entry for 1.5.INTA (src \\_SB_.LNKC:0) pci_link10: Picked IRQ 19 with weight 0 ioapic0: Changing polarity for pin 19 to high pcib1: slot 5 INTA routed to irq 19 via \\_SB_.LNKC found-> vendor=0x10b7, dev=0x9200, revid=0x74 bus=1, slot=5, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=19 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fc9a0000, size 17, enabled pcib1: (null) requested memory range 0xfc9a0000-0xfc9bffff: good map[14]: type 1, range 32, base fc980000, size 17, enabled pcib1: (null) requested memory range 0xfc980000-0xfc99ffff: good map[18]: type 4, range 32, base 0000d800, size 6, enabled pcib1: (null) requested I/O range 0xd800-0xd83f: in range pcib1: matched entry for 1.7.INTA (src \\_SB_.LNKA:0) pci_link8: Picked IRQ 17 with weight 0 ioapic0: Changing polarity for pin 17 to high pcib1: slot 7 INTA routed to irq 17 via \\_SB_.LNKA found-> vendor=0x8086, dev=0x1076, revid=0x00 bus=1, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=17 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 0000d400, size 6, enabled pcib1: (null) requested I/O range 0xd400-0xd43f: in range map[14]: type 4, range 32, base 0000d000, size 4, enabled pcib1: (null) requested I/O range 0xd000-0xd00f: in range map[18]: type 4, range 32, base 0000cc00, size 7, enabled pcib1: (null) requested I/O range 0xcc00-0xcc7f: in range map[1c]: type 1, range 32, base fc9fe000, size 12, enabled pcib1: (null) requested memory range 0xfc9fe000-0xfc9fefff: good map[20]: type 1, range 32, base fc940000, size 17, enabled pcib1: (null) requested memory range 0xfc940000-0xfc95ffff: good pcib1: matched entry for 1.8.INTA (src \\_SB_.LNKC:0) pcib1: slot 8 INTA routed to irq 19 via \\_SB_.LNKC found-> vendor=0x105a, dev=0x3373, revid=0x02 bus=1, slot=8, func=0 class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=145 (dwords) lattimer=0x60 (2880 ns), mingnt=0x04 (1000 ns), maxlat=0x12 (4500 ns) intpin=a, irq=19 powerspec 2 supports D0 D1 D3 current D0 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xfc9ffc00-0xfc9ffc7f irq 19 at device 5.0 on pci1 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xfc9ffc00 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:50:da:42:6e:8e xl0: [MPSAFE] em0: port 0xd800-0xd83f mem 0xfc9a0000-0xfc9bffff,0xfc980000-0xfc99ffff irq 17 at device 7.0 on pci1 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfc9a0000 em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xd800 em0: [MPSAFE] em0: bpf attached em0: Ethernet address: 00:0e:0c:37:c2:82 em0: Speed:N/A Duplex:N/A atapci1: port 0xd400-0xd43f,0xd000-0xd00f,0xcc00-0xcc7f mem 0xfc9fe000-0xfc9fefff,0xfc940000-0xfc95ffff irq 19 at device 8.0 on pci1 atapci1: failed: rid 0x20 is memory, requested 4 atapci1: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xfc940000 atapci1: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xfc9fe000 atapci1: [MPSAFE] ata2: channel #0 on atapci1 ata2: reset tp1 mask=01 ostat0=7f ostat1=7f ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=ff stat1=00 devices=0x0 ata2: [MPSAFE] ata3: channel #1 on atapci1 ata3: reset tp1 mask=01 ostat0=7f ostat1=7f ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=ff stat1=00 devices=0x0 ata3: [MPSAFE] ata4: channel #2 on atapci1 ata4: reset tp1 mask=03 ostat0=50 ostat1=00 ata4-master: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ata4-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata4-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata4: reset tp2 stat0=50 stat1=00 devices=0x1 ata4: [MPSAFE] pcib2: at device 11.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xfca00000-0xfeafffff pcib2: prefetched decode 0xe4700000-0xec6fffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 - AE_NOT_FOUND pci2: on pcib2 pci2: physical bus=2 map[10]: type 1, range 32, base fd000000, size 24, enabled pcib2: (null) requested memory range 0xfd000000-0xfdffffff: good map[14]: type 3, range 32, base e8000000, size 26, enabled pcib2: (null) requested memory range 0xe8000000-0xebffffff: good pcib0: matched entry for 0.11.INTA (src \\_SB_.LNKE:0) pci_link6: Picked IRQ 16 with weight 0 ioapic0: Changing polarity for pin 16 to high pcib0: slot 11 INTA routed to irq 16 via \\_SB_.LNKE pcib2: slot 0 INTA is routed to irq 16 found-> vendor=0x10de, dev=0x0181, revid=0xc1 bus=2, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x05 (1250 ns), maxlat=0x01 (250 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 pci2: at device 0.0 (no driver attached) acpi_button0: on acpi0 pci_link12: irq 0 on acpi0 pci_link12: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link12: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link13: irq 14 on acpi0 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 14 N 0 22 pci_link13: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link13: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 sio0: irq maps: 0xc21 0xc31 0xc21 0xc21 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: irq maps: 0xc21 0xc29 0xc21 0xc21 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it vga: vga0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xcf7ff,0xcf800-0xcffff,0xd0000-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) ppc0 failed to probe at irq 7 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. Timecounter "TSC" frequency 1470007451 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on nVidia nForce3 chip ata0-master: setting UDMA100 on nVidia nForce3 chip ad0: ATA-6 disk at ata0-master ad0: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 ata1-slave: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ata1-slave: setting PIO4 on nVidia nForce3 chip ata1-slave: DMA limited to UDMA33, non-ATA66 cable or device ata1-slave: setting UDMA33 on nVidia nForce3 chip acd0: CDRW drive at ata1 as slave acd0: read 345KB/s (8251KB/s) write 8251KB/s (8251KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata4-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad8: ATA-6 disk at ata4-master ad8: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B ad8: 16 secs/int, 1 depth queue, UDMA100 pcm0: measured ac97 link rate at 47996 Hz, will use 48000 Hz ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 3 (ISA IRQ 3) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 19 (PCI IRQ 19) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 GEOM: new disk ad0 GEOM: new disk ad8 Trying to mount root from ufs:/dev/ad0a start_init: trying /sbin/init ipfw2 initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled WARNING: attempt to net_add_domain(netgraph) after domainfinalize() em0: Link is up 100 Mbps Full Duplex --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot.no_mixed_mode" Copyright (c) 1992-2005 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.0-CURRENT #3: Fri Mar 25 10:44:58 EET 2005 ru@hammer.runet:/usr/obj/usr/src/sys/HAMMER WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8068b000. Preloaded elf obj module "/boot/kernel/if_em.ko" at 0xffffffff8068b1d0. Preloaded elf obj module "/boot/kernel/if_xl.ko" at 0xffffffff8068b6f8. Preloaded elf obj module "/boot/kernel/miibus.ko" at 0xffffffff8068bc20. Preloaded elf obj module "/boot/kernel/snd_ich.ko" at 0xffffffff8068c148. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff8068c6b0. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193169 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1470007358 Hz CPU: AMD Opteron(tm) Processor 240 (1470.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 1073479680 (1023 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000789000 - 0x000000003e189fff, 1033900032 bytes (252417 pages) avail memory = 1028120576 (980 MB) APIC: CPU 0 has ACPI ID 1 MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high MADT: Interrupt override: source 14, irq 14 ioapic0: intpin 14 trigger: edge ioapic0: intpin 14 polarity: high MADT: Interrupt override: source 15, irq 15 ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000000 err: 0x0001000f pcm: 0x00010000 random: io: mem: null: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80015004 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=00d110de) AcpiOsDerivePciId: bus 0 dev 1 func 0 acpi0: Power Button (fixed) ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link0: irq 0 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link1: irq 11 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 20 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link2: irq 5 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 21 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: irq 0 on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link4: irq 5 on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 20 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link5: irq 10 on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 20 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link6: irq 11 on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 16 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link7: irq 0 on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base f0000000, size 27, enabled found-> vendor=0x10de, dev=0x00d1, revid=0xa4 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x00d0, revid=0xf6 bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00005000, size 6, enabled map[24]: type 4, range 32, base 00005040, size 6, enabled found-> vendor=0x10de, dev=0x00d4, revid=0xa4 bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base febfd000, size 12, enabled pcib0: matched entry for 0.2.INTA (src \\_SB_.LUS0:0) pci_link1: Picked IRQ 20 with weight 0 ioapic0: Changing polarity for pin 20 to high pcib0: slot 2 INTA routed to irq 20 via \\_SB_.LUS0 found-> vendor=0x10de, dev=0x00d7, revid=0xa5 bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base febfe000, size 12, enabled pcib0: matched entry for 0.2.INTB (src \\_SB_.LUS1:0) pci_link4: Picked IRQ 20 with weight 1 pcib0: slot 2 INTB routed to irq 20 via \\_SB_.LUS1 found-> vendor=0x10de, dev=0x00d7, revid=0xa5 bus=0, slot=2, func=1 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base febffc00, size 8, enabled pcib0: matched entry for 0.2.INTC (src \\_SB_.LUS2:0) pci_link5: Picked IRQ 20 with weight 2 pcib0: slot 2 INTC routed to irq 20 via \\_SB_.LUS2 found-> vendor=0x10de, dev=0x00d8, revid=0xa2 bus=0, slot=2, func=2 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=c, irq=20 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 4, range 32, base 0000ec00, size 7, enabled map[18]: type 1, range 32, base febfb000, size 12, enabled pcib0: matched entry for 0.6.INTA (src \\_SB_.LAUI:0) pci_link2: Picked IRQ 21 with weight 0 ioapic0: Changing polarity for pin 21 to high pcib0: slot 6 INTA routed to irq 21 via \\_SB_.LAUI found-> vendor=0x10de, dev=0x00da, revid=0xa2 bus=0, slot=6, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=21 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x10de, dev=0x00d5, revid=0xa5 bus=0, slot=8, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x10de, dev=0x00dd, revid=0xa2 bus=0, slot=10, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x00d2, revid=0xa4 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x0b (2750 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0:1:1: Transition from D0 to D3 ohci0: mem 0xfebfd000-0xfebfdfff irq 20 at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfd000 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: 3 ports with 3 removable, self powered ohci1: mem 0xfebfe000-0xfebfefff irq 20 at device 2.1 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfe000 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: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfebffc00-0xfebffcff irq 20 at device 2.2 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfebffc00 ehci0: [GIANT-LOCKED] usb2: waiting for BIOS to give up control usb2: timed out waiting for BIOS usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered pcm0: port 0xe800-0xe8ff,0xec00-0xec7f mem 0xfebfb000-0xfebfbfff irq 21 at device 6.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe800 pcm0: Reserved 0x80 bytes for rid 0x14 type 4 at 0xec00 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features 20 bit DAC, 18 bit ADC, 5 bit master volume, Realtek 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, double rate PCM, reserved 1, center DAC, surround DAC, LFE DAC, reserved 4 pcm0: sndbuf_setmap 3db86000, 4000; 0xffffffffa5446000 -> 3db86000 pcm0: sndbuf_setmap 3db78000, 4000; 0xffffffffa544a000 -> 3db78000 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=7f ostat1=50 ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-slave: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=ff stat1=10 devices=0x8 ata1: [MPSAFE] pcib1: at device 10.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xc000-0xdfff pcib1: memory decode 0xfc800000-0xfc9fffff pcib1: prefetched decode 0xfff00000-0xfffff pci_link8: irq 11 on acpi0 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 17 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link9: irq 0 on acpi0 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link10: irq 10 on acpi0 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 19 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link11: irq 0 on acpi0 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 ACPI: Found matching pin for 0.6.INTA at func 0: 21 pci_link11: BIOS IRQ 21 for 0.6.INTA is invalid pci1: on pcib1 pci1: physical bus=1 map[10]: type 4, range 32, base 0000dc00, size 7, enabled pcib1: (null) requested I/O range 0xdc00-0xdc7f: in range map[14]: type 1, range 32, base fc9ffc00, size 7, enabled pcib1: (null) requested memory range 0xfc9ffc00-0xfc9ffc7f: good pcib1: matched entry for 1.5.INTA (src \\_SB_.LNKC:0) pci_link10: Picked IRQ 19 with weight 0 ioapic0: Changing polarity for pin 19 to high pcib1: slot 5 INTA routed to irq 19 via \\_SB_.LNKC found-> vendor=0x10b7, dev=0x9200, revid=0x74 bus=1, slot=5, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=19 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fc9a0000, size 17, enabled pcib1: (null) requested memory range 0xfc9a0000-0xfc9bffff: good map[14]: type 1, range 32, base fc980000, size 17, enabled pcib1: (null) requested memory range 0xfc980000-0xfc99ffff: good map[18]: type 4, range 32, base 0000d800, size 6, enabled pcib1: (null) requested I/O range 0xd800-0xd83f: in range pcib1: matched entry for 1.7.INTA (src \\_SB_.LNKA:0) pci_link8: Picked IRQ 17 with weight 0 ioapic0: Changing polarity for pin 17 to high pcib1: slot 7 INTA routed to irq 17 via \\_SB_.LNKA found-> vendor=0x8086, dev=0x1076, revid=0x00 bus=1, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=17 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 0000d400, size 6, enabled pcib1: (null) requested I/O range 0xd400-0xd43f: in range map[14]: type 4, range 32, base 0000d000, size 4, enabled pcib1: (null) requested I/O range 0xd000-0xd00f: in range map[18]: type 4, range 32, base 0000cc00, size 7, enabled pcib1: (null) requested I/O range 0xcc00-0xcc7f: in range map[1c]: type 1, range 32, base fc9fe000, size 12, enabled pcib1: (null) requested memory range 0xfc9fe000-0xfc9fefff: good map[20]: type 1, range 32, base fc940000, size 17, enabled pcib1: (null) requested memory range 0xfc940000-0xfc95ffff: good pcib1: matched entry for 1.8.INTA (src \\_SB_.LNKC:0) pcib1: slot 8 INTA routed to irq 19 via \\_SB_.LNKC found-> vendor=0x105a, dev=0x3373, revid=0x02 bus=1, slot=8, func=0 class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=145 (dwords) lattimer=0x60 (2880 ns), mingnt=0x04 (1000 ns), maxlat=0x12 (4500 ns) intpin=a, irq=19 powerspec 2 supports D0 D1 D3 current D0 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xfc9ffc00-0xfc9ffc7f irq 19 at device 5.0 on pci1 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xfc9ffc00 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:50:da:42:6e:8e xl0: [MPSAFE] em0: port 0xd800-0xd83f mem 0xfc9a0000-0xfc9bffff,0xfc980000-0xfc99ffff irq 17 at device 7.0 on pci1 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfc9a0000 em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xd800 em0: [MPSAFE] em0: bpf attached em0: Ethernet address: 00:0e:0c:37:c2:82 em0: Speed:N/A Duplex:N/A atapci1: port 0xd400-0xd43f,0xd000-0xd00f,0xcc00-0xcc7f mem 0xfc9fe000-0xfc9fefff,0xfc940000-0xfc95ffff irq 19 at device 8.0 on pci1 atapci1: failed: rid 0x20 is memory, requested 4 atapci1: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xfc940000 atapci1: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xfc9fe000 atapci1: [MPSAFE] ata2: channel #0 on atapci1 ata2: reset tp1 mask=01 ostat0=7f ostat1=7f ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=ff stat1=00 devices=0x0 ata2: [MPSAFE] ata3: channel #1 on atapci1 ata3: reset tp1 mask=01 ostat0=7f ostat1=7f ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=ff stat1=00 devices=0x0 ata3: [MPSAFE] ata4: channel #2 on atapci1 ata4: reset tp1 mask=03 ostat0=50 ostat1=00 ata4-master: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ata4-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata4-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata4: reset tp2 stat0=50 stat1=00 devices=0x1 ata4: [MPSAFE] pcib2: at device 11.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xfca00000-0xfeafffff pcib2: prefetched decode 0xe4700000-0xec6fffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 - AE_NOT_FOUND pci2: on pcib2 pci2: physical bus=2 map[10]: type 1, range 32, base fd000000, size 24, enabled pcib2: (null) requested memory range 0xfd000000-0xfdffffff: good map[14]: type 3, range 32, base e8000000, size 26, enabled pcib2: (null) requested memory range 0xe8000000-0xebffffff: good pcib0: matched entry for 0.11.INTA (src \\_SB_.LNKE:0) pci_link6: Picked IRQ 16 with weight 0 ioapic0: Changing polarity for pin 16 to high pcib0: slot 11 INTA routed to irq 16 via \\_SB_.LNKE pcib2: slot 0 INTA is routed to irq 16 found-> vendor=0x10de, dev=0x0181, revid=0xc1 bus=2, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x05 (1250 ns), maxlat=0x01 (250 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 pci2: at device 0.0 (no driver attached) acpi_button0: on acpi0 pci_link12: irq 0 on acpi0 pci_link12: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link12: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link13: irq 14 on acpi0 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 14 N 0 22 pci_link13: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link13: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 sio0: irq maps: 0xc21 0xc31 0xc21 0xc21 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: irq maps: 0xc21 0xc29 0xc21 0xc21 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it vga: vga0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xcf7ff,0xcf800-0xcffff,0xd0000-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) ppc0 failed to probe at irq 7 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. Timecounter "TSC" frequency 1470007358 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on nVidia nForce3 chip ata0-master: setting UDMA100 on nVidia nForce3 chip ad0: ATA-6 disk at ata0-master ad0: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 ata1-slave: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ata1-slave: setting PIO4 on nVidia nForce3 chip ata1-slave: DMA limited to UDMA33, non-ATA66 cable or device ata1-slave: setting UDMA33 on nVidia nForce3 chip acd0: CDRW drive at ata1 as slave acd0: read 345KB/s (8251KB/s) write 8251KB/s (8251KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata4-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad8: ATA-6 disk at ata4-master ad8: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B ad8: 16 secs/int, 1 depth queue, UDMA100 pcm0: measured ac97 link rate at 17112 Hz ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 2 (ISA IRQ 0) to cluster 0 ioapic0: routing intpin 3 (ISA IRQ 3) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 19 (PCI IRQ 19) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 --8t9RHnE3ZwKMSgU+-- --yNb1oOkm5a9FJOVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ93qqRfpzJluFF4RArvZAJ0XF3nk3ix1SJMe4BolZ8AdvC/KIgCeJpgY VIvb/+emJM0ihcBsLuFOLKM= =P3eJ -----END PGP SIGNATURE----- --yNb1oOkm5a9FJOVX-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 09:52:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7468016A4CE for ; Fri, 25 Mar 2005 09:52:44 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1E6F43D3F for ; Fri, 25 Mar 2005 09:52:43 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so184451wri for ; Fri, 25 Mar 2005 01:52:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YYc0D3gfzYkg/elzjCRdxOCGtKY79rxfnU31QbaFjp4ozkUwQEG359XqpSFuQXuuK2xIeJqoA7O7kXJPdR+AraGhpk8nfswndCKp8dg6RmkejezqljqBP9Cm31fl0QEYmpFJs/Td9Sah6YzNf/6PdqRPYlj8We6m30eH3VoORvE= Received: by 10.54.99.8 with SMTP id w8mr936286wrb; Fri, 25 Mar 2005 01:52:43 -0800 (PST) Received: by 10.54.40.69 with HTTP; Fri, 25 Mar 2005 01:52:43 -0800 (PST) Message-ID: <2fd864e05032501525fd3dbe6@mail.gmail.com> Date: Fri, 25 Mar 2005 01:52:43 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050325062317.GB7662@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org> <2fd864e05032412501c001a5d@mail.gmail.com> <20050324215445.GB99206@dragon.NUXI.org> <2fd864e05032415452721de81@mail.gmail.com> <20050325062317.GB7662@dragon.NUXI.org> Subject: Re: AMD64 Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 09:52:44 -0000 On Thu, 24 Mar 2005 22:23:17 -0800, David O'Brien wrote: > On Thu, Mar 24, 2005 at 03:45:50PM -0800, Astrodog wrote: > > On Thu, 24 Mar 2005 13:54:45 -0800, David O'Brien wrote: > > > On Thu, Mar 24, 2005 at 12:50:13PM -0800, Astrodog wrote: > > > > We have 2 problems, that I see. > > > > #1. Linux32 doesn't appear to be addressed for dependancies at all, > > > > almost every linux-something port I've found, calls itsself i386 only, > > > > and sometimes has minor RPM issues. > > > > > > What are the minor RPM issues? I knew there are some (see archives for > > > the arguments over the way we currently igngore them). But a summary of > > > current issues would be good. > > > > The two that come up, that I've seen, > > Most all of the ports that rely on Linux compat, linux-jdk, > > linux-mozilla, etc, don't use the RPM properly, they're labeled ONLY > > FOT ARCHS i386. These are fixed with just adding amd64 to that list. > > Please post a typescript clearly showing the problem; or explain the > situation in detail. The working Acroread on my amd64 desktop says > things are working tolerably well. > Alright. > > Currently, without manual fetching and whatnot, you cannot easily > > install i386 packages. With IA32 support included, it should be > > possible to install 32-bit packages, and if the crosscompile is > > viable, 32-bit only ports. > > This needs some architectural work that no one has wrapped their heads > around. > How complete is the IA32 support? And... I guess there should be a compat/ia32, or somesuch? > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 10:13:04 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41BA116A4CE; Fri, 25 Mar 2005 10:13:04 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE48643D48; Fri, 25 Mar 2005 10:13:03 +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 1DEloM-0009mS-M8; Fri, 25 Mar 2005 12:13:02 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Ruslan Ermilov In-Reply-To: Message from Ruslan Ermilov of "Fri, 25 Mar 2005 11:46:18 +0200." <20050325094618.GA76747@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Mar 2005 12:13:02 +0200 From: Danny Braniss Message-ID: cc: amd64@freebsd.org Subject: Re: testers wanted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 10:13:04 -0000 > Hi DES, > > On Thu, Mar 24, 2005 at 02:43:04PM +0100, Dag-Erling Sm?rgrav wrote: > > I need someone with an nForce3-based Opteron box running -CURRENT to > > do the following: > >=20 > > - upgrade to a recent -CURRENT, verify that a GENERIC kernel with > > NO_MIXED_MODE removed works properly *with apic enabled* > >=20 > Looks like it works, though I got one TIMEOUT - WRITE_DMA with it. > I just used a stripped down GENERIC kernel with hw.apic.mixed_mode=3D1 > set in /boot/loader.conf, which has the same effect as above. > > > - build an unmodified GENERIC (*with* NO_MIXED_MODE) from the same > > sources and boot it *with apic enabled* > >=20 > Booted the same kernel with hw.apic.mixed_mode=3D0. It stalls > (see the attached logs). same here, but there seems to be a problem with the network: Trying to mount root from nfs: NFS ROOT: 132.65.16.100:/d/9 em0: Link is up 100 Mbps Full Duplex em0: link state changed to UP em0: Link is up 100 Mbps Full Duplex usb_new_device: set address 2 failed - trying a port reset em0: Link is up 100 Mbps Full Duplex usb_new_device: set address 2 failed - trying a port reset usb_new_device: set address 2 failed - trying a port reset em0: Link is up 100 Mbps Full Duplex usb_new_device: set address 2 failed uhub_explore: usb_new_device failed, error=SET_ADDR_FAILED uhub1: device problem (SET_ADDR_FAILED), disabling port 1 em0: Link is up 100 Mbps Full Duplex i'll disconnect the usb stuff now ... danny From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 10:20:11 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A7E416A4CE for ; Fri, 25 Mar 2005 10:20:11 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47EEE43D5A for ; Fri, 25 Mar 2005 10:20:10 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2PAK7x0018471; Fri, 25 Mar 2005 12:20:07 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 42561-05; Fri, 25 Mar 2005 12:20:25 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2PAK6Yh018468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 12:20:06 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2PAKRdR077125; Fri, 25 Mar 2005 12:20:27 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 12:20:26 +0200 From: Ruslan Ermilov To: Dag-Erling Sm?rgrav Message-ID: <20050325102026.GA77092@ip.net.ua> References: <86ll8dgnx3.fsf@xps.des.no> <20050325094618.GA76747@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <20050325094618.GA76747@ip.net.ua> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@freebsd.org Subject: Re: testers wanted X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 10:20:11 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 25, 2005 at 11:46:18AM +0200, Ruslan Ermilov wrote: > Hi DES, >=20 > On Thu, Mar 24, 2005 at 02:43:04PM +0100, Dag-Erling Sm?rgrav wrote: > > I need someone with an nForce3-based Opteron box running -CURRENT to > > do the following: > >=20 > > - upgrade to a recent -CURRENT, verify that a GENERIC kernel with > > NO_MIXED_MODE removed works properly *with apic enabled* > >=20 > Looks like it works, though I got one TIMEOUT - WRITE_DMA with it. > I just used a stripped down GENERIC kernel with hw.apic.mixed_mode=3D1 > set in /boot/loader.conf, which has the same effect as above. >=20 Hmm, I get a lot of these timeouts under a moderate load, so I reverted to running without APIC. ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D78348992 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D76137492 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D40718060 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D75041976 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D42997008 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D70133884 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D43351984 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D43735084 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D43745116 > > - build an unmodified GENERIC (*with* NO_MIXED_MODE) from the same > > sources and boot it *with apic enabled* > >=20 > Booted the same kernel with hw.apic.mixed_mode=3D0. It stalls > (see the attached logs). >=20 > > Please provide verbose dmesg for both cases, as well as the contents > > of /boot/loader.conf and /boot/device.hints. > >=20 > /boot/loader.conf has some uninteresting stuff to load network > and sound modules I need, and device.hints equals GENERIC.hints. >=20 That said, the situation didn't imrpove in any way since I first tried it a few months ago. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCQ+XqqRfpzJluFF4RAteqAJ9Pz0s/Bkm7M3/BV3/l8666sUwmpQCfVU5y 2VL5UkUx6qhkBu8MHTAn+O4= =MxbP -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 13:05:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87FA716A4CE for ; Fri, 25 Mar 2005 13:05:53 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31AF743D2F for ; Fri, 25 Mar 2005 13:05:53 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so1073421rne for ; Fri, 25 Mar 2005 05:05:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iwRSOA9+9Nc2P17/xfGmBWoKYxlM/8iubZyrOus1cYDJ+31oueavIqKMsGSMHfx5V4doJUWJMOftGGYmJfean4C/LMES7TScgXVkQz/YRROhBpHN/W1CApXwFK/ACV01HPH6sL8OFLoEjaWzgfed/5XyAZuAHdwYJ3HydEwAcjk= Received: by 10.38.75.80 with SMTP id x80mr2501848rna; Fri, 25 Mar 2005 05:05:52 -0800 (PST) Received: by 10.38.209.22 with HTTP; Fri, 25 Mar 2005 05:05:52 -0800 (PST) Message-ID: <84dead7205032505051c1eb879@mail.gmail.com> Date: Fri, 25 Mar 2005 13:05:52 +0000 From: Joseph Koshy To: Petri Helenius In-Reply-To: <4243D111.1020904@he.iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <4243D111.1020904@he.iki.fi> cc: freebsd-amd64@freebsd.org Subject: Re: syscall sysret X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 13:05:53 -0000 > Does amd64 freebsd always utilize syscall / sysret opcodes? See: src/lib/libc/amd64/SYS.h ... 66 #define KERNCALL movq %rcx, %r10; syscall ... So the answer appears to be yes for native binaries. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 13:38:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE59616A4CE; Fri, 25 Mar 2005 13:38:01 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AE7B43D39; Fri, 25 Mar 2005 13:38:01 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E907C511CB; Fri, 25 Mar 2005 05:38:00 -0800 (PST) Date: Fri, 25 Mar 2005 05:38:00 -0800 From: Kris Kennaway To: Ruslan Ermilov Message-ID: <20050325133800.GA52791@xor.obsecurity.org> References: <20050324234511.GA59281@xor.obsecurity.org> <20050325072436.GD75626@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <20050325072436.GD75626@ip.net.ua> User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 13:38:01 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 25, 2005 at 09:24:36AM +0200, Ruslan Ermilov wrote: > > Any ideas? I need to get this to work for 5.4-RELEASE package builds. > >=20 > It looks like the wrong version of endian.h header is used here: > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h > which is the AMD64 version, rather than an i386 versopm from > /usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/include/machine/endian.h >=20 > I will look into this today (on HEAD). Thanks. Kris --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRBQ4Wry0BWjoQKURAosvAKDbVo3xWMsp5k8vlcK3pmONHrTx7QCgwjt9 /tmutYQV7qrqNmU6sKwfiWs= =Tyno -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 14:51:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 363D816A4CE for ; Fri, 25 Mar 2005 14:51:39 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C421143D2D for ; Fri, 25 Mar 2005 14:51:37 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2PEpZZk035396; Fri, 25 Mar 2005 16:51:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 68519-10; Fri, 25 Mar 2005 16:51:54 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j2PEpYW3035393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Mar 2005 16:51:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id j2PEpt6K078539; Fri, 25 Mar 2005 16:51:55 +0200 (EET) (envelope-from ru) Date: Fri, 25 Mar 2005 16:51:55 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20050325145155.GA78455@ip.net.ua> References: <20050324234511.GA59281@xor.obsecurity.org> <20050325072436.GD75626@ip.net.ua> <20050325133800.GA52791@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <20050325133800.GA52791@xor.obsecurity.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@freebsd.org Subject: Re: buildworld error while cross-building X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 14:51:39 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Kris, On Fri, Mar 25, 2005 at 05:38:00AM -0800, Kris Kennaway wrote: > On Fri, Mar 25, 2005 at 09:24:36AM +0200, Ruslan Ermilov wrote: >=20 > > > Any ideas? I need to get this to work for 5.4-RELEASE package builds. > > >=20 > > It looks like the wrong version of endian.h header is used here: > > /usr/obj/amd64/a/portbuild/amd64/5/src/i386/usr/include/machine/endian.h > > which is the AMD64 version, rather than an i386 versopm from > > /usr/obj/amd64/a/portbuild/amd64/5/src/lib32/usr/include/machine/endian= =2Eh > >=20 > > I will look into this today (on HEAD). >=20 > Thanks. >=20 I cannot reproduce this problem on HEAD, and at a glance RELENG_5 should be OK too. I mean, the .depend file correctly references the i386 version of endian.h. Can you provide me with a shell access to this box, so I could look into the contents of /usr/obj/amd64/a/portbuild/amd64/5/? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRCWLqRfpzJluFF4RAhFdAKCINmocDIDvFs+9McQxyWsVd1g5MACeKKg5 SQONmxAEM0giiCNzGYdKLS8= =RkCI -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 25 22:38:17 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01AA616A4CE; Fri, 25 Mar 2005 22:38:17 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84F4E43D49; Fri, 25 Mar 2005 22:38:16 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IDXIVU00.7WB; Fri, 25 Mar 2005 14:38:18 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005032514414416809 ; Fri, 25 Mar 2005 14:41:44 -0800 From: "Vinod Kashyap" To: obrien@freebsd.org Date: Fri, 25 Mar 2005 14:37:19 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=-------64c2860764c28607 Message-ID: cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: RE: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 22:38:17 -0000 This is a multi-part message in MIME format ---------64c2860764c28607 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > > Can you not submit it with the patch I sent? > = > Submit the entire /usr/src/sys kernel source?? > = > > A "stand alone" foo.c will have to be a new module under a new > > directory (/sys/dev/foo), with its own Makefile, with changes to > > /sys/conf/files, and an entry in GENERIC. > = > A module would still depend on files in /usr/share/mk, = > /usr/src/sys/conf, > /usr/src/sys/modules, /usr/src/sys/dev/foo. > = > NO! nothing other than a single file -- foo.c in my home = > directory that > shows the problem is a "stand alone" example. Here is memset_issue.c (also attached). But note that you cannot reproduce the "undefined reference to `memset'" issue with this (that's what I have been trying to explain). You could also use the earlier posting from Sean McNeil. #include main() { char a[100] =3D {0}; char *ap; ap =3D &(a[0]); printf("a[0] =3D %d\n", a[0]); } With the patch that I sent earlier applied to /sys/dev/twa/twa.c, 'nm twa.o' shows this when twa is built as a stand alone module: 00000000000003f0 t memset 'nm twa.o' shows this when twa is built as part of the kernel: U memset And now, moving to the important thing... in kern.pre.mk, I changed COPTFLAGS from -O2 to -O for amd64 (just like i386), and the problem is gone!! ---------64c2860764c28607 Content-Type: text/plain; name="memset_issue.c" Content-Disposition: attachment; filename="memset_issue.c" Content-Transfer-Encoding: quoted-printable #include main() { char a[100] =3D {0}; char *ap; ap =3D &(a[0]); printf("a[0] =3D %d\n", a[0]); } ---------64c2860764c28607-- From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 08:50:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 655CE16A4CE; Sat, 26 Mar 2005 08:50:13 +0000 (GMT) Received: from peedub.jennejohn.org (J844b.j.pppool.de [85.74.132.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 849FF43D1F; Sat, 26 Mar 2005 08:50:12 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.3/8.11.6) with ESMTP id j2Q8o6ov001415; Sat, 26 Mar 2005 09:50:07 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200503260850.j2Q8o6ov001415@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: "Vinod Kashyap" In-Reply-To: Message from "Vinod Kashyap" of "Fri, 25 Mar 2005 14:37:19 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Mar 2005 09:50:06 +0100 From: Gary Jennejohn cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 08:50:13 -0000 "Vinod Kashyap" writes: > > And now, moving to the important thing... in kern.pre.mk, I changed > COPTFLAGS from -O2 to -O for amd64 (just like i386), and the problem > is gone!! > Better to do it in /etc/make.conf. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 11:32:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05B0516A505 for ; Sat, 26 Mar 2005 11:32:30 +0000 (GMT) Received: from c2bapps18.btconnect.com (dswu195.btconnect.com [193.113.154.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 1501E43D1D for ; Sat, 26 Mar 2005 11:32:29 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from AJDELL9200 (actually host 114.74.198.83.in-addr.arpa) by dswu195.btconnect.com with SMTP (XT-PP) with ESMTP; Sat, 26 Mar 2005 11:32:21 +0000 From: "Alan Jay" To: Date: Sat, 26 Mar 2005 11:32:19 -0000 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcUmCYIl8qHLKXCqQS+cgzz8EZLHLwH9Xz5QAP2O38A= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20050326113229.1501E43D1D@mx1.FreeBSD.org> Subject: BroadcomBCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin[Alan Jay] Operteron X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 11:32:30 -0000 > -----Original Message----- > From: Doug White [mailto:dwhite@gumbysoft.com] > Sent: Friday, March 11, 2005 7:11 AM > To: Alan Jay > Cc: freebsd-amd64@freebsd.org > Subject: RE: BroadcomBCM5704C 10/100/1000 on TyanThunder K8S pro S2882 > twin[Alan Jay] Operteron > > On Thu, 10 Mar 2005, Alan Jay wrote: > > > > > > From: Doug White > > > > > > On Mon, 7 Mar 2005, Alan Jay wrote: > > > > > > > Well after upgrading to the latest -STABLE via cvsup and makeworld > > > makekernel > > > > etc we have been doing some more tests over the weekend. > > > > > > When did you run this cvsup? > > > > [Alan Jay] March 2nd. > > Being that its been a week you might give this another spin. [Alan Jay] Did so this weekend. CVSUP'd to the latest version > > [Alan Jay] We have done that but the serial terminal is attached to a > terminal > > concentrator and it seems to timeout before logging any useful > information. > > When we succeeded there was nothing on the serial console in the way of a > > panic message. Sorry not sure how to do a backtrace or crashdump? > > See the section on kernel debugging in the Developer's Handbook. You > activate crashdumps by nominating a partition that is at least as large as > memory with the 'dumpdev' rc.conf variable (and can be enabled at runtime > with the 'dumpon' command). Once the machine panics and creates the > crashdump, on the ensuing reboot savecore will automatically run and > extract the crashdump. With the crashdump in hand you can use kgdb and a > debugging kernel image to figure out what happened. [Alan Jay] I tried to understand this but may have missed something in how to do it as not sure if it is working or not. > > > > By the way over the weekend the latest -STABLE which is marked 5.4- > > > PRERELEASE > > > > 2 seemed much better than 5.3 had and the initial problems took much > > > longer to > > > > appear. Though once the problems started to appear, they repeated > > > themselves > > > > rebooting every 1-2hrs until we removed the tests data. > > Right, but a failed fan keeps that nice cool air from getting to the > burning hot parts. :) [Alan Jay] Well the fans all see m fine and having reinstalled we thought we would do some more tests. As a first step we decided to use the option to set the memory to be limited to 4Gb. Unfortunately the computer crashed shortly after starting the test and I didn't manage to get anything useful out of the above commands which I must not have fully understood. Unfortunately no additional information on why it crashed but even with only 4Gb of RAM in play it fell over quite quickly Anyway the report back is that the latest version Prerelase 3 still have this problem. Regards ALan > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 13:20:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A989616A4CE for ; Sat, 26 Mar 2005 13:20:44 +0000 (GMT) Received: from smtp813.mail.sc5.yahoo.com (smtp813.mail.sc5.yahoo.com [66.163.170.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 6AB2D43D1D for ; Sat, 26 Mar 2005 13:20:44 +0000 (GMT) (envelope-from rwideman@sbcglobal.net) Received: from unknown (HELO ?192.168.0.102?) (rwideman@sbcglobal.net@66.143.142.211 with plain) by smtp813.mail.sc5.yahoo.com with SMTP; 26 Mar 2005 13:20:44 -0000 Message-ID: <42456274.70308@sbcglobal.net> Date: Sat, 26 Mar 2005 07:24:04 -0600 From: Robert Wideman User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050325) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: amd64 freebsd mailing lists X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 13:20:44 -0000 i would like to subscribe to the amd64/freebsd mailing list. thank you. Robert Wideman From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 13:31:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F14B16A4CE for ; Sat, 26 Mar 2005 13:31:07 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C157043D2D for ; Sat, 26 Mar 2005 13:31:06 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-a071.otenet.gr [212.205.215.71]) j2QDUN60001432; Sat, 26 Mar 2005 15:30:24 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.3/8.13.3) with ESMTP id j2QDV3L9066290; Sat, 26 Mar 2005 15:31:03 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.3/8.13.3/Submit) id j2QDV3UE066289; Sat, 26 Mar 2005 15:31:03 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Sat, 26 Mar 2005 15:31:02 +0200 From: Giorgos Keramidas To: Robert Wideman Message-ID: <20050326133102.GA66262@gothmog.gr> References: <42456274.70308@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42456274.70308@sbcglobal.net> cc: freebsd-amd64@freebsd.org Subject: Re: amd64 freebsd mailing lists X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 13:31:07 -0000 On 2005-03-26 07:24, Robert Wideman wrote: > i would like to subscribe to the amd64/freebsd mailing list. thank you. You're looking for this web page then: http://lists.freebsd.org/mailman/listinfo From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 15:55:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B7C716A4CE for ; Sat, 26 Mar 2005 15:55:09 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5472E43D41 for ; Sat, 26 Mar 2005 15:55:09 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IDY00ER8UUKCU@VL-MO-MR010.ip.videotron.ca> for freebsd-amd64@freebsd.org; Sat, 26 Mar 2005 10:54:21 -0500 (EST) Date: Sat, 26 Mar 2005 10:54:12 -0500 From: Nicolas Blais In-reply-to: <200503211049.11110.jkim@niksun.com> To: freebsd-amd64@freebsd.org Message-id: <200503261054.14614.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <2fd864e05032105366eaf8b2c@mail.gmail.com> <200503211049.11110.jkim@niksun.com> Subject: Re: R3000Z Laptop Status X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 15:55:09 -0000 On March 21, 2005 10:49, Jung-uk Kim wrote: > On Monday 21 March 2005 08:36 am, Astrodog wrote: > > I was wondering if the R3000Z fixes have been committed to the > > RELENG_5 branch, I don't see anything on the lists about it. Should > > I expect 5.4 to work with the R3000 line? > > Yes. hint.atkbd.0.flags="0x9" is all you need now. Try the latest > snapshot and let us know. > > Thanks, > > Jung-uk Kim > > > --- Harrison Grundy With an update from acpi_ppc kernel module to the new powernow module, my cpu speed stays fixed at approx 800 mhz, even during the complete kde 3.4 build. I see that the module loaded successfully at boot, and kldstat shows that it loaded. Is there anything else I must do appart from "make install" and kldload the module at boot ? Also, I kept the old chkfreq from the acpi_ppc package as it isn't available in the newer powernow package. Running on 5.4-PRE Thanks, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 16:17:31 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C5F816A4CE for ; Sat, 26 Mar 2005 16:17:31 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 365DC43D5C for ; Sat, 26 Mar 2005 16:17:31 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0IDY00H6DVX6QH@VL-MO-MR011.ip.videotron.ca> for freebsd-amd64@freebsd.org; Sat, 26 Mar 2005 11:17:30 -0500 (EST) Date: Sat, 26 Mar 2005 11:17:29 -0500 From: Nicolas Blais In-reply-to: <200502081156.51114.nb_root@videotron.ca> To: freebsd-amd64@freebsd.org Message-id: <200503261117.29939.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <20050208163758.GA1086@NitroPhys.welchsmnet.net> <200502081156.51114.nb_root@videotron.ca> Subject: Compaq R3000Z keyboard doesn't work without DSDT patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 16:17:31 -0000 Hi, Without the following lines in loader.conf: acpi_dsdt_load="YES" acpi_dsdt_name="/boot/DSDT.aml" and of course in device.hints: hint.atkbd.0.flags="0x9" and Jung-uk Kim's r3000z-asl.diff found on this list, my keyboard not work at all but the booting process is fine and I can move my mouse, log on thru ssh etc... I was under the impression that 5.4 would be "R3000 friendly" and that the only things needed were hint.atkbd.0.flags="0x9" in device.hints and the powernow module (which stays at 800mhz while acpi_ppc works). Is there something I'm doing wrong? Thanks, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 18:44:26 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 968F416A4CE; Sat, 26 Mar 2005 18:44:26 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CBA943D31; Sat, 26 Mar 2005 18:44:26 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 13F4FF3F9D; Sat, 26 Mar 2005 10:44:24 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96657-10; Sat, 26 Mar 2005 10:44:22 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B944FF3F97; Sat, 26 Mar 2005 10:44:22 -0800 (PST) From: Sean McNeil To: jdp@FreeBSD.org Content-Type: text/plain Date: Sat, 26 Mar 2005 10:44:22 -0800 Message-Id: <1111862662.3953.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: amd64@freebsd.org Subject: cvsup now broken for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 18:44:26 -0000 With the introduction of a patch to net/cvsup, it will no longer work for amd64: ---> Upgrading 'cvsup-without-gui-16.1h' to 'cvsup-without-gui-16.1h_1' (net/cvsup-without-gui) ---> Building '/usr/ports/net/cvsup-without-gui' ===> Cleaning for cvsup-without-gui-16.1h_1 ===> Vulnerability check disabled, database not found ===> Extracting for cvsup-without-gui-16.1h_1 => Checksum OK for cvsup-without-gui.amd64.tar.bz2. ===> Patching for cvsup-without-gui-16.1h_1 ===> Applying FreeBSD patches for cvsup-without-gui-16.1h_1 File to patch: Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 26 21:32:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27F1316A4CE for ; Sat, 26 Mar 2005 21:32:27 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81D1743D31 for ; Sat, 26 Mar 2005 21:32:26 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 444C030003EE for ; Sat, 26 Mar 2005 22:32:25 +0100 (CET) Message-ID: <4245D504.9040004@mail.uni-mainz.de> Date: Sat, 26 Mar 2005 22:32:52 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050317 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: ASUS A8N-SLI Deluxe FreeBSD 5.4-Beta problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 21:32:27 -0000 Dear Sirs. I just tried to install a most recent set of FreeBSD 5.4-PRERELEASE/5.4-BETA1 on an ASUS A8N-SLI Deluxe mobo. The system has a Maxtor 6B200M0 200GB harddisk attached to the nForce4 SATA connector (due to NCQ) and a NEC 3500AG DVD+RW attached to the nForce4 ATA133 connector. Booting from installation CDROM is not possible until acpi gets disabled and this stays so when already did make world / new kernel with a most recent CTM set of the kernel stuff. It seems that FreeBSD does not know much about the SATA/SATA2 controller (it shows up as ATA Generic). The harddisk shows up as UDMA33 drive (like the DVDRW). Performance is crude, copying from DVD while compiling makes the system hang for some seconds on console. Sorry, I'm not connected to the net with that machine so I lack in dmesg-output. I read some time ago about nVidia nForce3/4 issues and I wonder that this is still status quo. Compiling kernel without "atpic" seems to leave the operating system inoperable, ACPI seems not to work. My question is whether FreeBSD 5.4 will support this type of hardware or maybe 5.5 or will FreeBSD not support this? Sorry bothering somebody around here, maybe this has been completely discussed here but I do not read regularily this mailing list. Can someone send me hints/tips for a fast kerl config and say something about the trapdoors? Thanks, Oliver