From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 1 22:20:13 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C62BC10656A4 for ; Sat, 1 Jan 2011 22:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 89A338FC2D for ; Sat, 1 Jan 2011 22:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01MKDt9006305 for ; Sat, 1 Jan 2011 22:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01MKD8D006304; Sat, 1 Jan 2011 22:20:13 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 22:20:13 GMT Resent-Message-Id: <201101012220.p01MKD8D006304@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Igor Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8211E106566B for ; Sat, 1 Jan 2011 22:13:52 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 66C478FC1D for ; Sat, 1 Jan 2011 22:13:52 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p01MDq6w077880 for ; Sat, 1 Jan 2011 22:13:52 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p01MDqEn077879; Sat, 1 Jan 2011 22:13:52 GMT (envelope-from nobody) Message-Id: <201101012213.p01MDqEn077879@red.freebsd.org> Date: Sat, 1 Jan 2011 22:13:52 GMT From: Igor To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Sun, 02 Jan 2011 04:38:06 +0000 Cc: Subject: amd64/153609: kernel: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 22:20:13 -0000 >Number: 153609 >Category: amd64 >Synopsis: kernel: Fatal trap 12: page fault while in kernel mode >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 22:20:13 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Igor >Release: FreeBSD 8.2-PRERELEASE #9: Fri Dec 31 >Organization: home >Environment: FreeBSD bvgm.org 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #9: Fri Dec 31 17:18:52 MSK 2010 root@bvgm.org:/usr/src/sys/amd64/compile/BVGM amd64 >Description: /etc/rc.conf .. wlans_zyd0="wlan0" ifconfig_wlan0="inet 172.16.0.1 netmask 255.255.255.0 metric 0" .. kernel config .. # Wireless NIC cards device wlan # 802.11 support options IEEE80211_DEBUG # enable debug msgs options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's options IEEE80211_SUPPORT_MESH # enable 802.11s draft support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm ... device usb # USB Bus (required) device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) ... While booting: Jan 2 00:21:51 bvgm kernel: wlan0: Ethernet address: 00:02:72:52:2a:47 Jan 2 00:21:51 bvgm kernel: zyd0: HMAC ZD1211B, FW 47.25, RF AL2230 S0, PA0 LED 0 BE0 NP1 Gain1 F0 Jan 2 00:21:51 bvgm kernel: Jan 2 00:21:51 bvgm kernel: Jan 2 00:21:51 bvgm kernel: Fatal trap 12: page fault while in kernel mode Jan 2 00:21:51 bvgm kernel: cpuid = 0; apic id = 00 Jan 2 00:21:51 bvgm kernel: fault virtual address = 0x0 Jan 2 00:21:51 bvgm kernel: fault code = supervisor read data, page not present Jan 2 00:21:51 bvgm kernel: instruction pointer = 0x20:0xffffffff80475798 Jan 2 00:21:51 bvgm kernel: stack pointer = 0x28:0xffffff8120cb8a80 Jan 2 00:21:51 bvgm kernel: frame pointer = 0x28:0xffffff8120cb8ac0 Jan 2 00:21:51 bvgm kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jan 2 00:21:51 bvgm kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Jan 2 00:21:51 bvgm kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jan 2 00:21:51 bvgm kernel: current process = 15 (usbus4) >How-To-Repeat: 1. Get somewhere ZyDAS USB2.0 WLAN, rev 2.00/48.10, addr 2 2. put folowwing text in the rc.conf /etc/rc.conf .. wlans_zyd0="wlan0" ifconfig_wlan0="inet 172.16.0.1 netmask 255.255.255.0 metric 0" .. 2. Insert device in the usb port. 3. We have crashed OS 4. If i try to reboot Jan 2 00:55:22 bvgm kernel: ugen4.2: at usbus4 Jan 2 00:55:22 bvgm kernel: zyd0: on usbus4 Jan 2 00:55:22 bvgm kernel: wlan0: Ethernet address: 00:02:72:52:2a:47 Jan 2 00:55:22 bvgm kernel: zyd0: HMAC ZD1211B, FW 47.25, RF AL2230 S0, PA0 LED 0 BE0 NP1 Gain1 F0 Jan 2 00:57:25 bvgm syslogd: kernel boot file is /boot/kernel/kernel Jan 2 00:57:25 bvgm kernel: Jan 2 00:57:25 bvgm kernel: Jan 2 00:57:25 bvgm kernel: Fatal trap 12: page fault while in kernel mode Jan 2 00:57:25 bvgm kernel: cpuid = 0; apic id = 00 Jan 2 00:57:25 bvgm kernel: fault virtual address = 0x0 Jan 2 00:57:25 bvgm kernel: fault code = supervisor read data, page not present Jan 2 00:57:25 bvgm kernel: instruction pointer = 0x20:0xffffffff80475798 Jan 2 00:57:25 bvgm kernel: stack pointer = 0x28:0xffffff8120cb8a80 Jan 2 00:57:25 bvgm kernel: frame pointer = 0x28:0xffffff8120cb8ac0 Jan 2 00:57:25 bvgm kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jan 2 00:57:25 bvgm kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Jan 2 00:57:25 bvgm kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jan 2 00:57:25 bvgm kernel: current process = 15 (usbus4) J If i remove string [wlans_zyd0="wlan0"] from rc.conf system boots properly but device is not work at all. >Fix: driver for zyd0 somewhere works improperly. Null ref error I know that Zyxel devices are ^%$&^*&%$$#$#!!! Thank you very much if you really fix this bug! >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 11:41:26 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B20EC106566B for ; Sun, 2 Jan 2011 11:41:26 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 691438FC0A for ; Sun, 2 Jan 2011 11:41:26 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p02BNHri063294 for ; Sun, 2 Jan 2011 03:23:24 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Sun, 2 Jan 2011 03:23:24 -0800 (PST) Message-ID: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> Date: Sun, 2 Jan 2011 03:23:24 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 11:41:26 -0000 Greetings, I installed fresh from the 8.1-RELEASE DVD, and cvsupped 8.1 src && ports-CURRENT 2 days ago. My target wm for this box is x11-wm/icewm But I chose to install x11/gnome2-lite && x11/kde4-lite beforehand because I like some of the applications they provide. So I started with gnome2-lite immediately after finishing cd /usr/ports/x11/xorg make && make install. The gnome2-lite make failed @ devel/libgtop (libgtop-2.28.2) with the following (from config.log): It was created by libgtop configure 2.28.2, which was generated by GNU Autoconf 2.67. Invocation command line was $ ./configure --disable-gtk-doc --with-html-dir=/usr/local/share/doc --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd8.1 ## --------- ## ## Platform. ## ## --------- ## hostname = udns0.ultimateDNS.NET uname -m = amd64 uname -r = 8.1-RELEASE-p2 uname -s = FreeBSD uname -v = FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 19:07:25 PST 2010 root@udns0.ultimateDNS.NET:/usr/obj/usr/src/sys/XII /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /root/bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2607: checking build system type configure:2621: result: amd64-portbld-freebsd8.1 configure:2641: checking host system type configure:2654: result: amd64-portbld-freebsd8.1 configure:2691: checking for a BSD-compatible install configure:2759: result: /usr/bin/install -c -o root -g wheel configure:2770: checking whether build environment is sane configure:2820: result: yes configure:2961: checking for a thread-safe mkdir -p configure:3000: result: ./install-sh -c -d configure:3013: checking for gawk configure:3029: found /usr/local/bin/gawk configure:3040: result: gawk configure:3051: checking whether gmake sets $(MAKE) configure:3073: result: yes configure:3187: checking for style of include used by gmake configure:3215: result: GNU configure:3285: checking for gcc configure:3312: result: cc configure:3541: checking for C compiler version configure:3550: cc --version >&5 cc (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3561: $? = 0 configure:3550: cc -v >&5 Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] configure:3561: $? = 0 configure:3550: cc -V >&5 cc: '-V' option must have argument configure:3561: $? = 1 configure:3550: cc -qversion >&5 cc: unrecognized option '-qversion' cc: No input files specified configure:3561: $? = 1 configure:3581: checking whether the C compiler works configure:3603: cc -O2 -pipe -march=athlon-mp -fno-strict-aliasing -I/usr/local/include -DHAVE_NET_IF_VAR_H -L/usr/local/lib conftest.c >&5 conftest.c:1: error: CPU you selected does not support x86-64 instruction set conftest.c:1: error: CPU you selected does not support x86-64 instruction set configure:3607: $? = 1 configure:3645: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libgtop" | #define PACKAGE_TARNAME "libgtop" | #define PACKAGE_VERSION "2.28.2" | #define PACKAGE_STRING "libgtop 2.28.2" | #define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=libgtop" | #define PACKAGE_URL "" | #define PACKAGE "libgtop" | #define VERSION "2.28.2" | /* end confdefs.h. */ PLEASE NOTE I have no control of your mail readers screen width/ line wrapping As you can see, it complains about amd64 (x86-64). :( Thank you for all your time ans consideration. --Chris -- FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 19:07:25 PST 2010 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2211.34-MHz K8-class CPU) From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 11:51:43 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A954B106564A for ; Sun, 2 Jan 2011 11:51:43 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 37BA28FC1A for ; Sun, 2 Jan 2011 11:51:42 +0000 (UTC) Received: by fxm16 with SMTP id 16so12493899fxm.13 for ; Sun, 02 Jan 2011 03:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:reply-to:x-mailer:mime-version :content-type:content-transfer-encoding; bh=Gg10y+nFPC2oXKHfynpHaMDa6hV6Fe4RydXHSsS6/OQ=; b=A0+Ym9efA19Un0c7sx1lVfFJXSJwuZUL5cX6zFKqe7Giy9WEhHNmItieUAqwkpfz78 gqvfA11G60CR6UB+0C977gTs/mYNL3YOcPBPU9id74AhgkDAV2unMw1yUChGzuTEN5rS AKjrhCkqVWKpYiLUIMRVa5Y464WPzxFVSx3io= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=HrA/SnkGEHI1wizhh2nA2n0XWpxMHO6S9hv+u0r7gT9kksLES8xZS63AnWNu2HbYII aadZd1OhK1g9sTgEyHKgttlE0hxlau21k+VWQTtnoFV3pFbRTjQswF5S+p3liR2PguTu s4NpWw+4MuqCAth4oK9JUMsgcHaNvrhZ+8rHE= Received: by 10.223.71.194 with SMTP id i2mr522927faj.15.1293969100250; Sun, 02 Jan 2011 03:51:40 -0800 (PST) Received: from ernst.jennejohn.org (p578E38B5.dip.t-dialin.net [87.142.56.181]) by mx.google.com with ESMTPS id n2sm4481491fam.4.2011.01.02.03.51.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 03:51:39 -0800 (PST) Date: Sun, 2 Jan 2011 12:51:37 +0100 From: Gary Jennejohn To: fbsdmail@dnswatch.com Message-ID: <20110102125137.4423cb08@ernst.jennejohn.org> In-Reply-To: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 11:51:43 -0000 On Sun, 2 Jan 2011 03:23:24 -0800 (PST) fbsdmail@dnswatch.com wrote: > Greetings, > I installed fresh from the 8.1-RELEASE DVD, and > cvsupped 8.1 src && ports-CURRENT 2 days ago. > My target wm for this box is x11-wm/icewm > But I chose to install x11/gnome2-lite && x11/kde4-lite > beforehand because I like some of the applications they > provide. > So I started with gnome2-lite immediately after finishing > cd /usr/ports/x11/xorg make && make install. > The gnome2-lite make failed @ devel/libgtop (libgtop-2.28.2) > with the following (from config.log): > > It was created by libgtop configure 2.28.2, which was > generated by GNU Autoconf 2.67. Invocation command line was > > $ ./configure --disable-gtk-doc --with-html-dir=/usr/local/share/doc > --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ > --build=amd64-portbld-freebsd8.1 > > ## --------- ## > ## Platform. ## > ## --------- ## > > hostname = udns0.ultimateDNS.NET > uname -m = amd64 > uname -r = 8.1-RELEASE-p2 > uname -s = FreeBSD > uname -v = FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 19:07:25 PST 2010 > root@udns0.ultimateDNS.NET:/usr/obj/usr/src/sys/XII > > /usr/bin/uname -p = amd64 > /bin/uname -X = unknown > > /bin/arch = unknown > /usr/bin/arch -k = unknown > /usr/convex/getsysinfo = unknown > /usr/bin/hostinfo = unknown > /bin/machine = unknown > /usr/bin/oslevel = unknown > /bin/universe = unknown > > PATH: /sbin > PATH: /bin > PATH: /usr/sbin > PATH: /usr/bin > PATH: /usr/games > PATH: /usr/local/sbin > PATH: /usr/local/bin > PATH: /root/bin > > > ## ----------- ## > ## Core tests. ## > ## ----------- ## > > configure:2607: checking build system type > configure:2621: result: amd64-portbld-freebsd8.1 > configure:2641: checking host system type > configure:2654: result: amd64-portbld-freebsd8.1 > configure:2691: checking for a BSD-compatible install > configure:2759: result: /usr/bin/install -c -o root -g wheel > configure:2770: checking whether build environment is sane > configure:2820: result: yes > configure:2961: checking for a thread-safe mkdir -p > configure:3000: result: ./install-sh -c -d > configure:3013: checking for gawk > configure:3029: found /usr/local/bin/gawk > configure:3040: result: gawk > configure:3051: checking whether gmake sets $(MAKE) > configure:3073: result: yes > configure:3187: checking for style of include used by gmake > configure:3215: result: GNU > configure:3285: checking for gcc > configure:3312: result: cc > configure:3541: checking for C compiler version > configure:3550: cc --version >&5 > cc (GCC) 4.2.1 20070719 [FreeBSD] > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > configure:3561: $? = 0 > configure:3550: cc -v >&5 > Using built-in specs. > Target: amd64-undermydesk-freebsd > Configured with: FreeBSD/amd64 system compiler > Thread model: posix > gcc version 4.2.1 20070719 [FreeBSD] > configure:3561: $? = 0 > configure:3550: cc -V >&5 > cc: '-V' option must have argument > configure:3561: $? = 1 > configure:3550: cc -qversion >&5 > cc: unrecognized option '-qversion' > cc: No input files specified > configure:3561: $? = 1 > configure:3581: checking whether the C compiler works > configure:3603: cc -O2 -pipe -march=athlon-mp -fno-strict-aliasing > -I/usr/local/include -DHAVE_NET_IF_VAR_H -L/usr/local/lib conftest.c >&5 > conftest.c:1: error: CPU you selected does not support x86-64 instruction set > conftest.c:1: error: CPU you selected does not support x86-64 instruction set > configure:3607: $? = 1 > configure:3645: result: no > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "libgtop" > | #define PACKAGE_TARNAME "libgtop" > | #define PACKAGE_VERSION "2.28.2" > | #define PACKAGE_STRING "libgtop 2.28.2" > | #define PACKAGE_BUGREPORT > "http://bugzilla.gnome.org/enter_bug.cgi?product=libgtop" > | #define PACKAGE_URL "" > | #define PACKAGE "libgtop" > | #define VERSION "2.28.2" > | /* end confdefs.h. */ > > PLEASE NOTE I have no control of your mail readers screen width/ > line wrapping > > As you can see, it complains about amd64 (x86-64). :( > > Thank you for all your time ans consideration. > > --Chris > The obvious question is whether you set cpu in /etc/make.conf. Don't do that. -- Gary Jennejohn From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 12:02:47 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5718810656A6 for ; Sun, 2 Jan 2011 12:02:47 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7498FC19 for ; Sun, 2 Jan 2011 12:02:46 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p02C2cBd063421; Sun, 2 Jan 2011 04:02:45 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Sun, 2 Jan 2011 04:02:45 -0800 (PST) Message-ID: <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> In-Reply-To: <20110102125137.4423cb08@ernst.jennejohn.org> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> Date: Sun, 2 Jan 2011 04:02:45 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 12:02:47 -0000 On Sun, January 2, 2011 3:51 am, Gary Jennejohn wrote: > On Sun, 2 Jan 2011 03:23:24 -0800 (PST) > fbsdmail@dnswatch.com wrote: > >> Greetings, >> I installed fresh from the 8.1-RELEASE DVD, and >> cvsupped 8.1 src && ports-CURRENT 2 days ago. My target wm for this box >> is x11-wm/icewm But I chose to install x11/gnome2-lite && x11/kde4-lite >> beforehand because I like some of the applications they provide. So I >> started with gnome2-lite immediately after finishing cd >> /usr/ports/x11/xorg make && make install. >> The gnome2-lite make failed @ devel/libgtop (libgtop-2.28.2) >> with the following (from config.log): >> >> It was created by libgtop configure 2.28.2, which was >> generated by GNU Autoconf 2.67. Invocation command line was >> >> $ ./configure --disable-gtk-doc --with-html-dir=/usr/local/share/doc >> --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ >> --build=amd64-portbld-freebsd8.1 >> >> >> ## --------- ## >> ## Platform. ## >> ## --------- ## >> >> >> uname -m = amd64 uname -r = >> 8.1-RELEASE-p2 >> uname -s = FreeBSD uname -v = FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 >> 19:07:25 PST 2010 >> >> >> /usr/bin/uname -p = amd64 >> /bin/uname -X = unknown >> >> >> /bin/arch = unknown >> /usr/bin/arch -k = unknown >> /usr/convex/getsysinfo = unknown >> /usr/bin/hostinfo = unknown >> /bin/machine = unknown >> /usr/bin/oslevel = unknown >> /bin/universe = unknown >> >> >> PATH: /sbin >> PATH: /bin >> PATH: /usr/sbin >> PATH: /usr/bin >> PATH: /usr/games >> PATH: /usr/local/sbin >> PATH: /usr/local/bin >> PATH: /root/bin >> >> >> >> ## ----------- ## >> ## Core tests. ## >> ## ----------- ## >> >> >> configure:2607: checking build system type >> configure:2621: result: amd64-portbld-freebsd8.1 >> configure:2641: checking host system type >> configure:2654: result: amd64-portbld-freebsd8.1 >> configure:2691: checking for a BSD-compatible install >> configure:2759: result: /usr/bin/install -c -o root -g wheel >> configure:2770: checking whether build environment is sane >> configure:2820: result: yes >> configure:2961: checking for a thread-safe mkdir -p >> configure:3000: result: ./install-sh -c -d >> configure:3013: checking for gawk >> configure:3029: found /usr/local/bin/gawk >> configure:3040: result: gawk >> configure:3051: checking whether gmake sets $(MAKE) >> configure:3073: result: yes >> configure:3187: checking for style of include used by gmake >> configure:3215: result: GNU >> configure:3285: checking for gcc >> configure:3312: result: cc >> configure:3541: checking for C compiler version >> configure:3550: cc --version >&5 >> cc (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software >> Foundation, Inc. >> This is free software; see the source for copying conditions. There is >> NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >> >> configure:3561: $? = 0 >> configure:3550: cc -v >&5 >> Using built-in specs. >> Target: amd64-undermydesk-freebsd >> Configured with: FreeBSD/amd64 system compiler >> Thread model: posix >> gcc version 4.2.1 20070719 [FreeBSD] configure:3561: $? = 0 >> configure:3550: cc -V >&5 >> cc: '-V' option must have argument >> configure:3561: $? = 1 >> configure:3550: cc -qversion >&5 >> cc: unrecognized option '-qversion' >> cc: No input files specified >> configure:3561: $? = 1 >> configure:3581: checking whether the C compiler works >> configure:3603: cc -O2 -pipe -march=athlon-mp -fno-strict-aliasing >> -I/usr/local/include -DHAVE_NET_IF_VAR_H -L/usr/local/lib conftest.c >> >&5 >> conftest.c:1: error: CPU you selected does not support x86-64 >> instruction set conftest.c:1: error: CPU you selected does not support >> x86-64 instruction set configure:3607: $? = 1 >> configure:3645: result: no >> configure: failed program was: >> | /* confdefs.h */ >> | #define PACKAGE_NAME "libgtop" >> | #define PACKAGE_TARNAME "libgtop" >> | #define PACKAGE_VERSION "2.28.2" >> | #define PACKAGE_STRING "libgtop 2.28.2" >> | #define PACKAGE_BUGREPORT >> "http://bugzilla.gnome.org/enter_bug.cgi?product=libgtop" >> | #define PACKAGE_URL "" >> | #define PACKAGE "libgtop" >> | #define VERSION "2.28.2" >> | /* end confdefs.h. */ >> >> >> PLEASE NOTE I have no control of your mail readers screen width/ >> line wrapping >> >> As you can see, it complains about amd64 (x86-64). :( >> >> >> Thank you for all your time ans consideration. >> >> >> --Chris >> >> > > The obvious question is whether you set cpu in /etc/make.conf. > > > Don't do that. > > > -- > Gary Jennejohn > > Hello, and thank you for your reply. Interesting you should bring that up. The last 4 installs I've done on the amd64 ARCH all had: CPUTYPE?=athlon-mp in make.conf, and none resulted in error(s). The only 2 differences from those and this one were the time(s) src && ports were cvsupped. Am I to understand 64-bit optimization is undesirable? Thank you again for your thoughtful reply. --Chris -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 14:05:57 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 850AB106564A for ; Sun, 2 Jan 2011 14:05:57 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0FD6D8FC16 for ; Sun, 2 Jan 2011 14:05:56 +0000 (UTC) Received: by fxm16 with SMTP id 16so12529738fxm.13 for ; Sun, 02 Jan 2011 06:05:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:reply-to:x-mailer:mime-version :content-type:content-transfer-encoding; bh=BIiOaHp/Efm1szeH76MFQEabthE27jhjOCP7YoGguwo=; b=eSZElbzlmkc5OLBTBK8kUlQ1y7p8OS3jJNkEBUqm1dLyJvMjgwPcNTwqEi1fsQO+bI pBlqhX5RfLprCOyFjPLzIlt21MIr7M0UzHvERCz7Tz8AmPRL+iU1Ehyja0ep9V3k//n5 cqvqIa4yIx/xPs549eezi/+tLynh7aTzlstiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=noJCzeXmlmEV5RvKtCnz/DAE3uYiVXDHpCy6G8gCH9BSJTaxHhAJj/mCfiO2N3eOuL vEedgSQMMe1O7fZgobsimKPVn94rouL4aKJ0L5eRoB7Hcfxv2aAGcy3UNldYhqDM+1FC mlBqRMPJCi698Lh6PdR8bV1siCYfwU7XrxW3E= Received: by 10.223.70.193 with SMTP id e1mr2848329faj.91.1293977154673; Sun, 02 Jan 2011 06:05:54 -0800 (PST) Received: from ernst.jennejohn.org (p578E38B5.dip.t-dialin.net [87.142.56.181]) by mx.google.com with ESMTPS id y1sm4503768fak.15.2011.01.02.06.05.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 06:05:53 -0800 (PST) Date: Sun, 2 Jan 2011 15:05:51 +0100 From: Gary Jennejohn To: fbsdmail@dnswatch.com Message-ID: <20110102150551.24f5193e@ernst.jennejohn.org> In-Reply-To: <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 14:05:57 -0000 On Sun, 2 Jan 2011 04:02:45 -0800 (PST) fbsdmail@dnswatch.com wrote: > > On Sun, January 2, 2011 3:51 am, Gary Jennejohn wrote: > > On Sun, 2 Jan 2011 03:23:24 -0800 (PST) > > fbsdmail@dnswatch.com wrote: > > > >> Greetings, > >> I installed fresh from the 8.1-RELEASE DVD, and > >> cvsupped 8.1 src && ports-CURRENT 2 days ago. My target wm for this box > >> is x11-wm/icewm But I chose to install x11/gnome2-lite && x11/kde4-lite > >> beforehand because I like some of the applications they provide. So I > >> started with gnome2-lite immediately after finishing cd > >> /usr/ports/x11/xorg make && make install. > >> The gnome2-lite make failed @ devel/libgtop (libgtop-2.28.2) > >> with the following (from config.log): > >> > >> It was created by libgtop configure 2.28.2, which was > >> generated by GNU Autoconf 2.67. Invocation command line was > >> > >> $ ./configure --disable-gtk-doc --with-html-dir=/usr/local/share/doc > >> --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ > >> --build=amd64-portbld-freebsd8.1 > >> > >> > >> ## --------- ## > >> ## Platform. ## > >> ## --------- ## > >> > >> > >> uname -m = amd64 uname -r = > >> 8.1-RELEASE-p2 > >> uname -s = FreeBSD uname -v = FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 > >> 19:07:25 PST 2010 > >> > >> > >> /usr/bin/uname -p = amd64 > >> /bin/uname -X = unknown > >> > >> > >> /bin/arch = unknown > >> /usr/bin/arch -k = unknown > >> /usr/convex/getsysinfo = unknown > >> /usr/bin/hostinfo = unknown > >> /bin/machine = unknown > >> /usr/bin/oslevel = unknown > >> /bin/universe = unknown > >> > >> > >> PATH: /sbin > >> PATH: /bin > >> PATH: /usr/sbin > >> PATH: /usr/bin > >> PATH: /usr/games > >> PATH: /usr/local/sbin > >> PATH: /usr/local/bin > >> PATH: /root/bin > >> > >> > >> > >> ## ----------- ## > >> ## Core tests. ## > >> ## ----------- ## > >> > >> > >> configure:2607: checking build system type > >> configure:2621: result: amd64-portbld-freebsd8.1 > >> configure:2641: checking host system type > >> configure:2654: result: amd64-portbld-freebsd8.1 > >> configure:2691: checking for a BSD-compatible install > >> configure:2759: result: /usr/bin/install -c -o root -g wheel > >> configure:2770: checking whether build environment is sane > >> configure:2820: result: yes > >> configure:2961: checking for a thread-safe mkdir -p > >> configure:3000: result: ./install-sh -c -d > >> configure:3013: checking for gawk > >> configure:3029: found /usr/local/bin/gawk > >> configure:3040: result: gawk > >> configure:3051: checking whether gmake sets $(MAKE) > >> configure:3073: result: yes > >> configure:3187: checking for style of include used by gmake > >> configure:3215: result: GNU > >> configure:3285: checking for gcc > >> configure:3312: result: cc > >> configure:3541: checking for C compiler version > >> configure:3550: cc --version >&5 > >> cc (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software > >> Foundation, Inc. > >> This is free software; see the source for copying conditions. There is > >> NO > >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > >> PURPOSE. > >> > >> > >> configure:3561: $? = 0 > >> configure:3550: cc -v >&5 > >> Using built-in specs. > >> Target: amd64-undermydesk-freebsd > >> Configured with: FreeBSD/amd64 system compiler > >> Thread model: posix > >> gcc version 4.2.1 20070719 [FreeBSD] configure:3561: $? = 0 > >> configure:3550: cc -V >&5 > >> cc: '-V' option must have argument > >> configure:3561: $? = 1 > >> configure:3550: cc -qversion >&5 > >> cc: unrecognized option '-qversion' > >> cc: No input files specified > >> configure:3561: $? = 1 > >> configure:3581: checking whether the C compiler works > >> configure:3603: cc -O2 -pipe -march=athlon-mp -fno-strict-aliasing > >> -I/usr/local/include -DHAVE_NET_IF_VAR_H -L/usr/local/lib conftest.c > >> >&5 > >> conftest.c:1: error: CPU you selected does not support x86-64 > >> instruction set conftest.c:1: error: CPU you selected does not support > >> x86-64 instruction set configure:3607: $? = 1 > >> configure:3645: result: no > >> configure: failed program was: > >> | /* confdefs.h */ > >> | #define PACKAGE_NAME "libgtop" > >> | #define PACKAGE_TARNAME "libgtop" > >> | #define PACKAGE_VERSION "2.28.2" > >> | #define PACKAGE_STRING "libgtop 2.28.2" > >> | #define PACKAGE_BUGREPORT > >> "http://bugzilla.gnome.org/enter_bug.cgi?product=libgtop" > >> | #define PACKAGE_URL "" > >> | #define PACKAGE "libgtop" > >> | #define VERSION "2.28.2" > >> | /* end confdefs.h. */ > >> > >> > >> PLEASE NOTE I have no control of your mail readers screen width/ > >> line wrapping > >> > >> As you can see, it complains about amd64 (x86-64). :( > >> > >> > >> Thank you for all your time ans consideration. > >> > >> > >> --Chris > >> > >> > > > > The obvious question is whether you set cpu in /etc/make.conf. > > > > > > Don't do that. > > > > > > -- > > Gary Jennejohn > > > > > Hello, and thank you for your reply. > Interesting you should bring that up. > The last 4 installs I've done on the amd64 ARCH > all had: > CPUTYPE?=athlon-mp > > in make.conf, and none resulted in error(s). > The only 2 differences from those and this one were > the time(s) src && ports were cvsupped. > > Am I to understand 64-bit optimization is undesirable? > > Thank you again for your thoughtful reply. > I'm running 9.0-CURRENT AMD64 _without cpu_ in /etc/.make.conf and have no problem compiling libgtop. Try commenting it out and see what happens. It isn't really necessary because AFAIK gcc figures out for itself which CPU you have. -- Gary Jennejohn From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 14:42:28 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAF7C106564A for ; Sun, 2 Jan 2011 14:42:28 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 680068FC12 for ; Sun, 2 Jan 2011 14:42:28 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p02EgKr4063799; Sun, 2 Jan 2011 06:42:26 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Sun, 2 Jan 2011 06:42:27 -0800 (PST) Message-ID: <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> In-Reply-To: <20110102150551.24f5193e@ernst.jennejohn.org> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> Date: Sun, 2 Jan 2011 06:42:27 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 14:42:28 -0000 On Sun, January 2, 2011 6:05 am, Gary Jennejohn wrote: > On Sun, 2 Jan 2011 04:02:45 -0800 (PST) > fbsdmail@dnswatch.com wrote: > >> >> On Sun, January 2, 2011 3:51 am, Gary Jennejohn wrote: >> >>> On Sun, 2 Jan 2011 03:23:24 -0800 (PST) >>> fbsdmail@dnswatch.com wrote: >>> >>>> Greetings, >>>> I installed fresh from the 8.1-RELEASE DVD, and >>>> cvsupped 8.1 src && ports-CURRENT 2 days ago. My target wm for this >>>> box is x11-wm/icewm But I chose to install x11/gnome2-lite && >>>> x11/kde4-lite beforehand because I like some of the applications >>>> they provide. So I started with gnome2-lite immediately after >>>> finishing cd /usr/ports/x11/xorg make && make install. >>>> The gnome2-lite make failed @ devel/libgtop (libgtop-2.28.2) >>>> with the following (from config.log): >>>> >>>> It was created by libgtop configure 2.28.2, which was >>>> generated by GNU Autoconf 2.67. Invocation command line was >>>> >>>> $ ./configure --disable-gtk-doc >>>> --with-html-dir=/usr/local/share/doc >>>> --prefix=/usr/local --mandir=/usr/local/man >>>> --infodir=/usr/local/info/ >>>> --build=amd64-portbld-freebsd8.1 >>>> >>>> >>>> >>>> ## --------- ## >>>> ## Platform. ## >>>> ## --------- ## >>>> >>>> >>>> >>>> uname -m = amd64 uname -r = 8.1-RELEASE-p2 >>>> uname -s = FreeBSD uname -v = FreeBSD 8.1-RELEASE-p2 #0: Fri Dec 31 >>>> 19:07:25 PST 2010 >>>> >>>> >>>> >>>> /usr/bin/uname -p = amd64 >>>> /bin/uname -X = unknown >>>> >>>> >>>> >>>> /bin/arch = unknown >>>> /usr/bin/arch -k = unknown >>>> /usr/convex/getsysinfo = unknown >>>> /usr/bin/hostinfo = unknown >>>> /bin/machine = unknown >>>> /usr/bin/oslevel = unknown >>>> /bin/universe = unknown >>>> >>>> >>>> >>>> PATH: /sbin >>>> PATH: /bin >>>> PATH: /usr/sbin >>>> PATH: /usr/bin >>>> PATH: /usr/games >>>> PATH: /usr/local/sbin >>>> PATH: /usr/local/bin >>>> PATH: /root/bin >>>> >>>> >>>> >>>> >>>> ## ----------- ## >>>> ## Core tests. ## >>>> ## ----------- ## >>>> >>>> >>>> >>>> configure:2607: checking build system type >>>> configure:2621: result: amd64-portbld-freebsd8.1 >>>> configure:2641: checking host system type >>>> configure:2654: result: amd64-portbld-freebsd8.1 >>>> configure:2691: checking for a BSD-compatible install >>>> configure:2759: result: /usr/bin/install -c -o root -g wheel >>>> configure:2770: checking whether build environment is sane >>>> configure:2820: result: yes >>>> configure:2961: checking for a thread-safe mkdir -p >>>> configure:3000: result: ./install-sh -c -d >>>> configure:3013: checking for gawk >>>> configure:3029: found /usr/local/bin/gawk >>>> configure:3040: result: gawk >>>> configure:3051: checking whether gmake sets $(MAKE) >>>> configure:3073: result: yes >>>> configure:3187: checking for style of include used by gmake >>>> configure:3215: result: GNU >>>> configure:3285: checking for gcc >>>> configure:3312: result: cc >>>> configure:3541: checking for C compiler version >>>> configure:3550: cc --version >&5 >>>> cc (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software >>>> Foundation, Inc. >>>> This is free software; see the source for copying conditions. There >>>> is NO >>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >>>> PURPOSE. >>>> >>>> >>>> >>>> configure:3561: $? = 0 >>>> configure:3550: cc -v >&5 >>>> Using built-in specs. >>>> Target: amd64-undermydesk-freebsd >>>> Configured with: FreeBSD/amd64 system compiler >>>> Thread model: posix >>>> gcc version 4.2.1 20070719 [FreeBSD] configure:3561: $? = 0 >>>> configure:3550: cc -V >&5 >>>> cc: '-V' option must have argument >>>> configure:3561: $? = 1 >>>> configure:3550: cc -qversion >&5 >>>> cc: unrecognized option '-qversion' >>>> cc: No input files specified >>>> configure:3561: $? = 1 >>>> configure:3581: checking whether the C compiler works >>>> configure:3603: cc -O2 -pipe -march=athlon-mp -fno-strict-aliasing >>>> -I/usr/local/include -DHAVE_NET_IF_VAR_H -L/usr/local/lib conftest.c >>>> >>>>> &5 >>>>> >>>> conftest.c:1: error: CPU you selected does not support x86-64 >>>> instruction set conftest.c:1: error: CPU you selected does not >>>> support x86-64 instruction set configure:3607: $? = 1 configure:3645: >>>> result: no >>>> configure: failed program was: >>>> | /* confdefs.h */ >>>> | #define PACKAGE_NAME "libgtop" >>>> | #define PACKAGE_TARNAME "libgtop" >>>> | #define PACKAGE_VERSION "2.28.2" >>>> | #define PACKAGE_STRING "libgtop 2.28.2" >>>> | #define PACKAGE_BUGREPORT >>>> "http://bugzilla.gnome.org/enter_bug.cgi?product=libgtop" >>>> | #define PACKAGE_URL "" >>>> | #define PACKAGE "libgtop" >>>> | #define VERSION "2.28.2" >>>> | /* end confdefs.h. */ >>>> >>>> >>>> >>>> PLEASE NOTE I have no control of your mail readers screen width/ >>>> line wrapping >>>> >>>> As you can see, it complains about amd64 (x86-64). :( >>>> >>>> >>>> >>>> Thank you for all your time ans consideration. >>>> >>>> >>>> >>>> --Chris >>>> >>>> >>>> >>> >>> The obvious question is whether you set cpu in /etc/make.conf. >>> >>> >>> >>> Don't do that. >>> >>> >>> >>> -- >>> Gary Jennejohn >>> >>> >>> >> Hello, and thank you for your reply. >> Interesting you should bring that up. >> The last 4 installs I've done on the amd64 ARCH >> all had: CPUTYPE?=athlon-mp >> >> >> in make.conf, and none resulted in error(s). The only 2 differences from >> those and this one were the time(s) src && ports were cvsupped. >> >> Am I to understand 64-bit optimization is undesirable? >> >> >> Thank you again for your thoughtful reply. >> >> > > I'm running 9.0-CURRENT AMD64 _without cpu_ in /etc/.make.conf and have > no problem compiling libgtop. > > Try commenting it out and see what happens. It isn't really necessary > because AFAIK gcc figures out for itself which CPU you have. > > -- > Gary Jennejohn > > Hello again, and thanks for your response. I commented it out after responding to your response, and it happily built. I just figured I'd use the CPUTYPE?= option to gain better amd64 profiling, but apparently it's only _really_ available for the i386 CPU's. I say that because I've always used that option when building on those ARCH types, and never ran into a problem. Oh well, hopefully sometime son, it'll be better supported on the amd64 - fingers crossed. :) Thanks again for taking the time to respond. --Chris -- kern: FreeBSD 8.1-PRERELEASE amd64 MB: MSI 880GMA-E45 (socket: AM3) CPU: AMD Phenom X3 440 (3 core) @3.5Ghz RAM: 2 4Gb CORSAIR DDR3 DualChannel PC1600 From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 15:10:05 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCC811065673 for ; Sun, 2 Jan 2011 15:10:05 +0000 (UTC) (envelope-from listreader@lazlarlyricon.com) Received: from mailgw2.surf-town.net (mail14.surf-town.net [212.97.132.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7989B8FC13 for ; Sun, 2 Jan 2011 15:10:05 +0000 (UTC) Received: by mailgw2.surf-town.net (Postfix, from userid 65534) id 9885F38456; Sun, 2 Jan 2011 15:51:51 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailgw2.surf-town.net (Postfix) with ESMTP id 397AF38457; Sun, 2 Jan 2011 15:51:51 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mailgw2.surf-town.net X-Spam-Score: 0.1 X-Spam-Level: X-Spam-Status: No, score=0.1 tagged_above=-999 required=7 tests=[RDNS_DYNAMIC=0.1] Received: from mailgw2.surf-town.net ([127.0.0.1]) by localhost (mailgw2.surf-town.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LP5OYrLzjP2V; Sun, 2 Jan 2011 15:51:45 +0100 (CET) Received: from lazlar.kicks-ass.net (c-4d80e355.09-42-6e6b7010.cust.bredbandsbolaget.se [85.227.128.77]) by mailgw2.surf-town.net (Postfix) with ESMTP id 408AB37BE3; Sun, 2 Jan 2011 15:51:42 +0100 (CET) Message-ID: <4D2090FC.5030409@lazlarlyricon.com> Date: Sun, 02 Jan 2011 15:51:40 +0100 From: Rolf Nielsen User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; sv-SE; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: fbsdmail@dnswatch.com References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> In-Reply-To: <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 15:10:05 -0000 2011-01-02 15:42, fbsdmail@dnswatch.com skrev: <...> > Hello again, and thanks for your response. > I commented it out after responding to your response, and > it happily built. I just figured I'd use the CPUTYPE?= option > to gain better amd64 profiling, but apparently it's only > _really_ available for the i386 CPU's. I say that because > I've always used that option when building on those ARCH types, > and never ran into a problem. Oh well, hopefully sometime son, > it'll be better supported on the amd64 - fingers crossed. :) > > Thanks again for taking the time to respond. > > --Chris > > Hi, I have an Intel CPU that's amd64 compatible, and I use CPUTYPE?=native, which never gave me any problems (I use it for all builds, including kernel and world). I can't say whether it works with AMD CPUs though. Nor can I really say if it makes a difference, because I've never tried without it. /Rolf From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 18:02:47 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37E6E106566B for ; Sun, 2 Jan 2011 18:02:47 +0000 (UTC) (envelope-from luchesar.iliev@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B3EF08FC14 for ; Sun, 2 Jan 2011 18:02:46 +0000 (UTC) Received: by fxm16 with SMTP id 16so12602372fxm.13 for ; Sun, 02 Jan 2011 10:02:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id :disposition-notification-to:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=E8pW9HsswYXTekvBC+vo9dQcjK2QLx+H68VtWQtE7y8=; b=JH47NN8EZRMogUjUPM4iyNU6S2U8qUrlxTgNTXaki8ENYp3Q0SGsmDwNzI8ng5N9rZ Z6mZG599y978xDPaC+GwVpkJhdqwcQKjPfQUSD8jzFTtU1xIjbVxE/pGxFtzu/p1LNey tLT1oKJy1ZhU5mk4OKt3Prrb7BswsQ9OtAR+0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=H/ny/VvWEMXay8ZQIEtop6tOtfcZSCfWV75WDu9Dqnn9Xe6D7mmjQNISIH4CAZagdg KCX8PUHYqpuEh4n5tEfVFs6OXXoPsMGgg/zRIF8xzlT6+noLYGJOsg04YXerYysfzT4X UHmGhSxvqRrd67KR78PVtIjmVOE6fstNgUJg4= Received: by 10.223.83.133 with SMTP id f5mr6437839fal.101.1293989740144; Sun, 02 Jan 2011 09:35:40 -0800 (PST) Received: from [79.124.93.41] ([79.124.93.41]) by mx.google.com with ESMTPS id r24sm4542495fax.27.2011.01.02.09.35.38 (version=SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 09:35:39 -0800 (PST) Message-ID: <4D20B769.5000704@gmail.com> Date: Sun, 02 Jan 2011 19:35:37 +0200 From: "Luchesar V. ILIEV" Organization: Ideaconsult Ltd. User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: fbsdmail@dnswatch.com References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <4D2090FC.5030409@lazlarlyricon.com> In-Reply-To: <4D2090FC.5030409@lazlarlyricon.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=9A1FEEFF; url=https://cert.acad.bg/pgp-keys/ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 18:02:47 -0000 hw.model: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ CPUTYPE?= athlon64 I've never encountered any CPUTYPE specific problems so far, and I have GNOME2 and almost 1000 ports compiled on my desktop, plus the OS itself. I wonder if "athlon-mp" is so different to be causing the problems you've encountered or if there was something else that got fixed coincidentally when you commented out CPUTYPE from make.conf. Cheers, Luchesar On 01/02/11 16:51, Rolf Nielsen wrote: > 2011-01-02 15:42, fbsdmail@dnswatch.com skrev: > <...> >> Hello again, and thanks for your response. >> I commented it out after responding to your response, and >> it happily built. I just figured I'd use the CPUTYPE?= option >> to gain better amd64 profiling, but apparently it's only >> _really_ available for the i386 CPU's. I say that because >> I've always used that option when building on those ARCH types, >> and never ran into a problem. Oh well, hopefully sometime son, >> it'll be better supported on the amd64 - fingers crossed. :) >> >> Thanks again for taking the time to respond. >> >> --Chris >> >> > > Hi, > > I have an Intel CPU that's amd64 compatible, and I use CPUTYPE?=native, > which never gave me any problems (I use it for all builds, including > kernel and world). I can't say whether it works with AMD CPUs though. > Nor can I really say if it makes a difference, because I've never tried > without it. > > /Rolf > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 2 18:55:21 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B88B01065672 for ; Sun, 2 Jan 2011 18:55:21 +0000 (UTC) (envelope-from bunchou@googlemail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3F79E8FC12 for ; Sun, 2 Jan 2011 18:55:20 +0000 (UTC) Received: by bwz12 with SMTP id 12so5932395bwz.13 for ; Sun, 02 Jan 2011 10:55:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type:content-transfer-encoding; bh=e6H6uGx+/QzcK8XHau+KiZ84k8bVRmyp8jHWZSoPb5I=; b=mEZcTKy1ZGqvwOYDAMlpukEj5uvRdIvRwXH2TbK8De9pcycH60Wsd4Otpz+o/M8XAP jZHIrje4b0MguWfpOmFiSlNmrEN0jYlYIuZy4ewK843LEKaShGvTwGJieUqBZ3FgsQh3 DZLbjKH3uq0f0qhkxVgOkA+M7WWXTbv9s468g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; b=Wh9wSqoUS+BCZGh5GJzxIV1VVKCRQv+bdga+uIck2fcH6DbL94qrU0EkG/q19sqgow mWqjHRwWFhaaAlHu8iv/YucrOck3Of/G6MHyYFv8y5EfCgmrgAMdfuqp6RyIQGqaqv/s CZAuqAXq94E5VZ28bKFNFPYMs0P1YxTyoI5/g= Received: by 10.204.116.74 with SMTP id l10mr2271383bkq.77.1293992990292; Sun, 02 Jan 2011 10:29:50 -0800 (PST) Received: from centaur.5550h.net (p5DC271C8.dip.t-dialin.net [93.194.113.200]) by mx.google.com with ESMTPS id j11sm11079563bka.12.2011.01.02.10.29.48 (version=SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 10:29:49 -0800 (PST) Date: Sun, 2 Jan 2011 19:29:46 +0100 From: "=?UTF-8?B?5paH6bOl?=" To: freebsd-amd64@freebsd.org Message-ID: <20110102192946.2ab5429a@centaur.5550h.net> In-Reply-To: <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 18:55:21 -0000 On Sun, 2 Jan 2011 06:42:27 -0800 (PST) fbsdmail@dnswatch.com wrote: > Hello again, and thanks for your response. > I commented it out after responding to your response, and > it happily built. I just figured I'd use the CPUTYPE?= option > to gain better amd64 profiling, but apparently it's only > _really_ available for the i386 CPU's. I say that because > I've always used that option when building on those ARCH types, > and never ran into a problem. Oh well, hopefully sometime son, > it'll be better supported on the amd64 - fingers crossed. :) > > Thanks again for taking the time to respond. > > --Chris > > Please take a look at /usr/share/examples/etc/make.conf It clearly states that athlon-mp is for the Intel x86 arch _only_. Wikipedia tells us the same (http://en.wikipedia.org/wiki/Athlon_mp#Athlon_XP.2FMP). Therefore I assume, that (since you've got amd64 running), your CPU isn't really an "athlon-mp", but rather one of the following (again from the make.conf example): opteron, athlon64, nocona, prescott, core2 PS: I personally use "native", since that gives me the same level of optimization as choosing the correct CPU by hand would. Additionally, you might consider compiling ports with gcc45, since the base cc doesn't support newer CPU features like e.g. SSE4.2. Best regards From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 06:45:22 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32687106566B for ; Mon, 3 Jan 2011 06:45:22 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id DA3028FC08 for ; Mon, 3 Jan 2011 06:45:21 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p036jDYs066046; Sun, 2 Jan 2011 22:45:19 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Sun, 2 Jan 2011 22:45:20 -0800 (PST) Message-ID: <28cdac712efe4eff35e0d775a0270971.dnswclient@www.dnswatch.com> In-Reply-To: <4D20B769.5000704@gmail.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <4D2090FC.5030409@lazlarlyricon.com> <4D20B769.5000704@gmail.com> Date: Sun, 2 Jan 2011 22:45:20 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 06:45:22 -0000 # # # TOP POSTING IS EVIL # # # >> 2011-01-02 15:42, fbsdmail@dnswatch.com skrev: >> <...> >> >>> Hello again, and thanks for your response. >>> I commented it out after responding to your response, and >>> it happily built. I just figured I'd use the CPUTYPE?= option to gain >>> better amd64 profiling, but apparently it's only _really_ available >>> for the i386 CPU's. I say that because I've always used that option >>> when building on those ARCH types, and never ran into a problem. Oh >>> well, hopefully sometime son, it'll be better supported on the amd64 - >>> fingers crossed. :) >>> >>> Thanks again for taking the time to respond. >>> >>> >>> --Chris >>> >>> >>> >> >> Hi, >> >> >> I have an Intel CPU that's amd64 compatible, and I use CPUTYPE?=native, >> which never gave me any problems (I use it for all builds, including >> kernel and world). I can't say whether it works with AMD CPUs though. >> Nor can I really say if it makes a difference, because I've never tried >> without it. >> >> /Rolf >> _______________________________________________ >> 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" >> On Sun, January 2, 2011 9:35 am, Luchesar V. ILIEV wrote: > hw.model: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ > CPUTYPE?= athlon64 > > > I've never encountered any CPUTYPE specific problems so far, and I have > GNOME2 and almost 1000 ports compiled on my desktop, plus the OS itself. > > > I wonder if "athlon-mp" is so different to be causing the problems > you've encountered or if there was something else that got fixed > coincidentally when you commented out CPUTYPE from make.conf. Greetings Luchesar, and thank you for your reply. I've got a couple of other threads on the @stable list, and one other on this one related to this. Last time I researched make(1) and make.conf(5), the common consensus was that (open)ssl, and possibly a couple of others were the only things that ever made use of the flag. However, when I experimented heavily on older CPU's, I discovered that CPUTYPE?= _did_ make a difference. In some cases it simply made the difference for correctly recognizing the CPU, in all cases, it added the "feature set" that that CPU possessed - SSE, SSE2, 3DNow, etc... So, I find myself inclined to make use of CPUTYPE?= whenever possible. Problem is, I don't always keep up on gcc(1)'s changes/additions. Which I think is the case here. My _guess_ is that they changed the name(s) - however slightly, and I found out the "hard way". :-\ Bottom line; I need to take the time, and find the difference(s) from then<--to-->now to use it effectively. Thanks again for your reply. --Chris > > Cheers, > Luchesar > > > > > -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 06:56:19 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C531065673 for ; Mon, 3 Jan 2011 06:56:19 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 56BD28FC17 for ; Mon, 3 Jan 2011 06:56:19 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p036uB0S066088; Sun, 2 Jan 2011 22:56:17 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Sun, 2 Jan 2011 22:56:18 -0800 (PST) Message-ID: <90fd957c01e95dcfd287427792d91351.dnswclient@www.dnswatch.com> In-Reply-To: <20110102192946.2ab5429a@centaur.5550h.net> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <20110102192946.2ab5429a@centaur.5550h.net> Date: Sun, 2 Jan 2011 22:56:18 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 06:56:19 -0000 On Sun, January 2, 2011 10:29 am, 文鳥 wrote: > On Sun, 2 Jan 2011 06:42:27 -0800 (PST) > fbsdmail@dnswatch.com wrote: > > >> Hello again, and thanks for your response. >> I commented it out after responding to your response, and >> it happily built. I just figured I'd use the CPUTYPE?= option to gain >> better amd64 profiling, but apparently it's only _really_ available for >> the i386 CPU's. I say that because I've always used that option when >> building on those ARCH types, and never ran into a problem. Oh well, >> hopefully sometime son, it'll be better supported on the amd64 - fingers >> crossed. :) >> >> Thanks again for taking the time to respond. >> >> >> --Chris >> >> >> > > Please take a look at /usr/share/examples/etc/make.conf > It clearly states that athlon-mp is for the Intel x86 arch _only_. > Wikipedia tells us the same > (http://en.wikipedia.org/wiki/Athlon_mp#Athlon_XP.2FMP). Therefore I > assume, that (since you've got amd64 running), your CPU isn't really an > "athlon-mp", but rather one of the following (again from the make.conf > example): opteron, athlon64, nocona, prescott, core2 > > > PS: I personally use "native", since that gives me the same level of > optimization as choosing the correct CPU by hand would. Additionally, you > might consider compiling ports with gcc45, since the base cc doesn't > support newer CPU features like e.g. SSE4.2. Right you are. :) As I stated to Luchesar, in my last reply, it's been awhile since I actually researched make(1) && make.conf(5). The last amd64 boxes I built using ths CPUTYPE?=athlon-mp were on 8-(PRE)RELEASE. In fact the only reason I chose athlon-mp is because one of the first ports I built echoed that in the config flags during the build. So without any research, I figured that to be (howeer mis- takenly) the correct choice. :) Thank you for your thoughtful reply. --Chris > > Best regards > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 11:06:59 2011 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BFF910656A4 for ; Mon, 3 Jan 2011 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0FEA18FC1A for ; Mon, 3 Jan 2011 11:06:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03B6wt1046422 for ; Mon, 3 Jan 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03B6wrT046420 for freebsd-amd64@FreeBSD.org; Mon, 3 Jan 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Jan 2011 11:06:58 GMT Message-Id: <201101031106.p03B6wrT046420@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/153609 amd64 kernel: Fatal trap 12: page fault while in kernel mode o amd64/153496 amd64 Install on Hyper-V leaves corrupt filesystems (incl ro o amd64/153495 amd64 xf86-video-ati wavy line problem for lenovo g555 o amd64/153403 amd64 BSD can't find SAS RAID on Intel SR2600UR server o amd64/153372 amd64 kernel panic o amd64/153175 amd64 [amd64] Kernel Panic on only FreeBSD 8 amd64 o amd64/152430 amd64 HP ProLiant Microserver n36l cannot boot into installe o amd64/151385 amd64 [boot] Installation hangs on MacBook o amd64/150170 amd64 [patch] [amd64] [headers] SIG_ATOMIC_MIN/SIG_ATOMIC_MA o amd64/148526 amd64 [ahci] ahci driver does not boot on AMD chip o amd64/145991 amd64 [NOTES] [patch] Add a requires line to /sys/amd64/conf o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' o amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/141060 amd64 [install] Can't install 8.0-RELEASE on the server wher o amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit o amd64/140145 amd64 sysinstall(8): Installation boot sequence freezes o amd64/139998 amd64 [panic][net] 7.2 amd64 panic in rtrequest1_fib o amd64/139924 amd64 [boot] cd or dvd not load o amd64/138029 amd64 [panic][bpf] periodically kernel panic and reboot o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu o amd64/135265 amd64 [mpt] Boot from install cd hangs on HP DL160 G5 with L o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/131456 amd64 [acpi] [ata] ACPI & ATA problems s amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [em] amd64 motherboard: Intel DG965WH motherboard comp o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/127640 amd64 [amd64] gcc(1) will not build shared libraries with -f o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c f amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 45 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 11:46:26 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7BB5106564A for ; Mon, 3 Jan 2011 11:46:26 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8AFC88FC16 for ; Mon, 3 Jan 2011 11:46:26 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p03BkHuv067769; Mon, 3 Jan 2011 03:46:24 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns0.ultimatedns.net ([168.103.150.26]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Mon, 3 Jan 2011 03:46:25 -0800 (PST) Message-ID: <99e66981c355ee3e3092b532204f4a4a.dnswclient@www.dnswatch.com> In-Reply-To: <90fd957c01e95dcfd287427792d91351.dnswclient@www.dnswatch.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <20110102192946.2ab5429a@centaur.5550h.net> <90fd957c01e95dcfd287427792d91351.dnswclient@www.dnswatch.com> Date: Mon, 3 Jan 2011 03:46:25 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 11:46:27 -0000 On Sun, January 2, 2011 10:56 pm, fbsdmail@dnswatch.com wrote: > > On Sun, January 2, 2011 10:29 am, 文鳥 wrote: > >> On Sun, 2 Jan 2011 06:42:27 -0800 (PST) >> fbsdmail@dnswatch.com wrote: >> >> >>> Hello again, and thanks for your response. >>> I commented it out after responding to your response, and >>> it happily built. I just figured I'd use the CPUTYPE?= option to gain >>> better amd64 profiling, but apparently it's only _really_ available >>> for the i386 CPU's. I say that because I've always used that option >>> when building on those ARCH types, and never ran into a problem. Oh >>> well, hopefully sometime son, it'll be better supported on the amd64 - >>> fingers crossed. :) >>> >>> Thanks again for taking the time to respond. >>> >>> >>> >>> --Chris >>> >>> >>> >>> >> >> Please take a look at /usr/share/examples/etc/make.conf >> It clearly states that athlon-mp is for the Intel x86 arch _only_. Ahem... Straight from /usr/share/examples/etc/make.conf: # Currently the following CPU types are recognized: # Intel x86 architecture: # (AMD CPUs) opteron athlon64 athlon-mp athlon-xp athlon-4 -----------------------------------------^^^^^^^^^ # athlon-tbird athlon k8 k6-3 k6-2 k6 k5 # (Intel CPUs) core2 core nocona pentium4m pentium4 prescott # pentium3m pentium3 pentium-m pentium2 # pentiumpro pentium-mmx pentium i486 i386 # (Via CPUs) c3 c3-2 # Alpha/AXP architecture: ev67 ev6 pca56 ev56 ev5 ev45 ev4 # AMD64 architecture: opteron, athlon64, nocona, prescott, core2 # Intel ia64 architecture: itanium2, itanium Sorry, couldn't resist. ;) No offense intended. >> Wikipedia tells us the same >> (http://en.wikipedia.org/wiki/Athlon_mp#Athlon_XP.2FMP). Therefore I >> assume, that (since you've got amd64 running), your CPU isn't really an >> "athlon-mp", but rather one of the following (again from the make.conf >> example): opteron, athlon64, nocona, prescott, core2 >> >> >> >> PS: I personally use "native", since that gives me the same level of >> optimization as choosing the correct CPU by hand would. Additionally, >> you might consider compiling ports with gcc45, since the base cc doesn't >> support newer CPU features like e.g. SSE4.2. > > Right you are. :) > As I stated to Luchesar, in my last reply, it's been awhile since > I actually researched make(1) && make.conf(5). The last amd64 boxes > I built using ths CPUTYPE?=athlon-mp were on 8-(PRE)RELEASE. > In fact the only reason I chose athlon-mp is because one of the > first ports I built echoed that in the config flags during the build. So > without any research, I figured that to be (howeer mis- takenly) the > correct choice. :) > > Thank you for your thoughtful reply. > > > --Chris > > >> >> Best regards >> _______________________________________________ >> 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" >> >> >> > > > -- > kern: > FreeBSD 8.1-RELEASE amd64 > > > > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 15:28:03 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 594D9106564A for ; Mon, 3 Jan 2011 15:28:03 +0000 (UTC) (envelope-from luchesar.iliev@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D27928FC21 for ; Mon, 3 Jan 2011 15:28:02 +0000 (UTC) Received: by fxm16 with SMTP id 16so13102574fxm.13 for ; Mon, 03 Jan 2011 07:28:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id :disposition-notification-to:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=8b8iLCYCjFXl++95zBwx2UJ0VRJYYdAUa1WYWd+DaJs=; b=ccTyK+fLD5W8/7DAtfXmKwRhsW2zgPKCw3QjXiU1/OJ6oNlughhMunD07dwoYNNcml amWzToPFKkJYlqneQesOOUhlk6L9tfTTvBHE3EDUpeWggT6bxS0JawnjWAC6dwWYmt71 +zWQgovs0cEOfKFwy5YSGxxUAKEqoOohnje0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=H8g0ykN2ulMscfUy6YOzIQPw8TY5127CMiJTfWLQITvU2cEcL53JT+M0QtwoHcTOxj moycymVYldRjstYqIm4FSzf7FQNcO5sjdFI0sNdG6m/HLq+4P0Zb4+j5Mn+9hUdq0gLo zzbZUYpEwj5jqK0OTztf2+GogAbtPNYOwVyQM= Received: by 10.223.87.14 with SMTP id u14mr4800080fal.116.1294068480078; Mon, 03 Jan 2011 07:28:00 -0800 (PST) Received: from [79.124.93.41] ([79.124.93.41]) by mx.google.com with ESMTPS id 21sm4770947fav.41.2011.01.03.07.27.58 (version=SSLv3 cipher=RC4-MD5); Mon, 03 Jan 2011 07:27:58 -0800 (PST) Message-ID: <4D21EAFD.4020104@gmail.com> Date: Mon, 03 Jan 2011 17:27:57 +0200 From: "Luchesar V. ILIEV" Organization: Ideaconsult Ltd. User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: fbsdmail@dnswatch.com References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <4D2090FC.5030409@lazlarlyricon.com> <4D20B769.5000704@gmail.com> <28cdac712efe4eff35e0d775a0270971.dnswclient@www.dnswatch.com> In-Reply-To: <28cdac712efe4eff35e0d775a0270971.dnswclient@www.dnswatch.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=9A1FEEFF; url=https://cert.acad.bg/pgp-keys/ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 15:28:03 -0000 On 01/03/11 08:45, fbsdmail@dnswatch.com wrote: > # # # TOP POSTING IS EVIL # # # >>> 2011-01-02 15:42, fbsdmail@dnswatch.com skrev: >>> <...> >>> >>>> Hello again, and thanks for your response. >>>> I commented it out after responding to your response, and >>>> it happily built. I just figured I'd use the CPUTYPE?= option to gain >>>> better amd64 profiling, but apparently it's only _really_ available >>>> for the i386 CPU's. I say that because I've always used that option >>>> when building on those ARCH types, and never ran into a problem. Oh >>>> well, hopefully sometime son, it'll be better supported on the amd64 - >>>> fingers crossed. :) >>>> >>>> Thanks again for taking the time to respond. >>>> >>>> >>>> --Chris >>>> >>>> >>>> >>> >>> Hi, >>> >>> >>> I have an Intel CPU that's amd64 compatible, and I use CPUTYPE?=native, >>> which never gave me any problems (I use it for all builds, including >>> kernel and world). I can't say whether it works with AMD CPUs though. >>> Nor can I really say if it makes a difference, because I've never tried >>> without it. >>> >>> /Rolf >>> _______________________________________________ >>> 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" >>> > On Sun, January 2, 2011 9:35 am, Luchesar V. ILIEV wrote: >> hw.model: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ >> CPUTYPE?= athlon64 >> >> >> I've never encountered any CPUTYPE specific problems so far, and I have >> GNOME2 and almost 1000 ports compiled on my desktop, plus the OS itself. >> >> >> I wonder if "athlon-mp" is so different to be causing the problems >> you've encountered or if there was something else that got fixed >> coincidentally when you commented out CPUTYPE from make.conf. > > Greetings Luchesar, and thank you for your reply. > I've got a couple of other threads on the @stable list, and one > other on this one related to this. Last time I researched make(1) > and make.conf(5), the common consensus was that (open)ssl, and > possibly a couple of others were the only things that ever made > use of the flag. However, when I experimented heavily on older > CPU's, I discovered that CPUTYPE?= _did_ make a difference. In > some cases it simply made the difference for correctly recognizing > the CPU, in all cases, it added the "feature set" that that CPU > possessed - SSE, SSE2, 3DNow, etc... > So, I find myself inclined to make use of CPUTYPE?= whenever possible. > Problem is, I don't always keep up on gcc(1)'s changes/additions. > Which I think is the case here. My _guess_ is that they changed the > name(s) - however slightly, and I found out the "hard way". :-\ > Bottom line; I need to take the time, and find the difference(s) > from then<--to-->now to use it effectively. > > Thanks again for your reply. > > --Chris Hi Chris, Indeed, I was going to comment about those notes in the documentation as well. To be honest, I've always been lazy to do my own research in the FreeBSD's code -- it's rather typical for the documentation to lag behind the code, and that's understandable even for commercial projects. BTW, an interesting file to check is also /usr/share/mk/bsd.cpu.mk. And that's why for the moment I'm a bit reluctant (probably naively) about using CPUTYPE=native -- it is understood by GCC itself, but bsd.cpu.mk "knows" nothing about it. Well, on amd64 it really does nothing more than to add "-march=${CPUTYPE}" to CFLAGS, which should be OK with "native", but it also seems to "describe" available CPU capabilities (e.g. mmx, sse, 3dnow) for the other mk files -- and that depends on the correct value, provided by CPUTYPE. I'm not sure this would work as expected with "native", but then again I might be quite wrong. In any case, I (and likely others) will really appreciate if you share your findings with the list -- and thank you for doing it so far. :) Cheers, Luchesar P.S. Oh, and, erm... sorry for that evil top posting... (blush) From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 20:55:17 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54DA6106566C; Mon, 3 Jan 2011 20:55:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B97E8FC0C; Mon, 3 Jan 2011 20:55:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03KtHUQ090376; Mon, 3 Jan 2011 20:55:17 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03KtHvv090372; Mon, 3 Jan 2011 20:55:17 GMT (envelope-from linimon) Date: Mon, 3 Jan 2011 20:55:17 GMT Message-Id: <201101032055.p03KtHvv090372@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-x11@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: ports/153495: x11-drivers/xf86-video-ati wavy line problem for lenovo g555 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 20:55:17 -0000 Old Synopsis: xf86-video-ati wavy line problem for lenovo g555 New Synopsis: x11-drivers/xf86-video-ati wavy line problem for lenovo g555 Responsible-Changed-From-To: freebsd-amd64->freebsd-x11 Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 3 20:54:39 UTC 2011 Responsible-Changed-Why: ports PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=153495 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 21:00:24 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6D98106566B; Mon, 3 Jan 2011 21:00:24 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ACF958FC15; Mon, 3 Jan 2011 21:00:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03L0Oox092981; Mon, 3 Jan 2011 21:00:24 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03L0OAB092968; Mon, 3 Jan 2011 21:00:24 GMT (envelope-from linimon) Date: Mon, 3 Jan 2011 21:00:24 GMT Message-Id: <201101032100.p03L0OAB092968@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-usb@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: usb/153609: [zyd] [panic] kernel: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 21:00:24 -0000 Old Synopsis: kernel: Fatal trap 12: page fault while in kernel mode New Synopsis: [zyd] [panic] kernel: Fatal trap 12: page fault while in kernel mode Responsible-Changed-From-To: freebsd-amd64->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 3 20:59:27 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=153609 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 21:04:38 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07BC31065674; Mon, 3 Jan 2011 21:04:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D18A78FC13; Mon, 3 Jan 2011 21:04:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03L4b6l003658; Mon, 3 Jan 2011 21:04:37 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03L4bOU003653; Mon, 3 Jan 2011 21:04:37 GMT (envelope-from linimon) Date: Mon, 3 Jan 2011 21:04:37 GMT Message-Id: <201101032104.p03L4bOU003653@freefall.freebsd.org> To: tomsk_interface@vtomske.ru, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/153403: [mfi] BSD can't find SAS RAID on Intel SR2600UR server X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 21:04:38 -0000 Old Synopsis: BSD can't find SAS RAID on Intel SR2600UR server New Synopsis: [mfi] BSD can't find SAS RAID on Intel SR2600UR server State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Mon Jan 3 21:04:03 UTC 2011 State-Changed-Why: reclassify, and note that a dmesg was requested. Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 3 21:04:03 UTC 2011 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=153403 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 21:13:16 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F137106566B; Mon, 3 Jan 2011 21:13:16 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 451C58FC0A; Mon, 3 Jan 2011 21:13:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03LDGd9013651; Mon, 3 Jan 2011 21:13:16 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03LDGi4013644; Mon, 3 Jan 2011 21:13:16 GMT (envelope-from linimon) Date: Mon, 3 Jan 2011 21:13:16 GMT Message-Id: <201101032113.p03LDGi4013644@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: amd64/152874: [install] 8.1 install fails where 7.3 works due to lack of choice of CD drive [regression] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 21:13:16 -0000 Old Synopsis: 8.1 install fails where 7.3 works due to lack of choice of CD drive New Synopsis: [install] 8.1 install fails where 7.3 works due to lack of choice of CD drive [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 3 21:12:29 UTC 2011 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=152874 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 20:00:29 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD00C106566B for ; Mon, 3 Jan 2011 20:00:29 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8FF608FC15 for ; Mon, 3 Jan 2011 20:00:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03K0Tlc026190 for ; Mon, 3 Jan 2011 20:00:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03K0TlI026189; Mon, 3 Jan 2011 20:00:29 GMT (envelope-from gnats) Resent-Date: Mon, 3 Jan 2011 20:00:29 GMT Resent-Message-Id: <201101032000.p03K0TlI026189@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Olivier Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE5E3106566B for ; Mon, 3 Jan 2011 19:53:20 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id BDDC48FC15 for ; Mon, 3 Jan 2011 19:53:20 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p03JrKEs023973 for ; Mon, 3 Jan 2011 19:53:20 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p03JrK1w023972; Mon, 3 Jan 2011 19:53:20 GMT (envelope-from nobody) Message-Id: <201101031953.p03JrK1w023972@red.freebsd.org> Date: Mon, 3 Jan 2011 19:53:20 GMT From: Olivier To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Mon, 03 Jan 2011 23:55:39 +0000 Cc: Subject: amd64/153659: awk segfaults when trying to extract a combination of special characters X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 20:00:29 -0000 >Number: 153659 >Category: amd64 >Synopsis: awk segfaults when trying to extract a combination of special characters >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 03 20:00:29 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Olivier >Release: 8.1 >Organization: interfaSys Ltd >Environment: FreeBSD 8.1-STABLE FreeBSD 8.1-STABLE #0 r213396 amd64 >Description: awk seg faults when it has to deal with at least one sequence of characters. This makes it crash: %* I don't know if it happens with other combinations >How-To-Repeat: # edit conf Type this GPG_PW='%*' # edit awk_test.sh Type this awk '/^[ \t]*GPG_PW[ \t=]/{\ sub(/^[ \t]*GPG_PW[ \t]*=*/,"",$0);\ gsub(/^[ \t]*[\047"]|[\047"][ \t]*$/,"",$0);\ printf $0; exit}' "$1" Now try to extract GPG_PW # ./awk_test.sh conf You will get this: ./awk_test.sh: line 4: 18676 Segmentation fault: 11 (core dumped) awk '/^[ \t]*GPG_PW[ \t=]/{\ sub(/^[ \t]*GPG_PW[ \t]*=*/,"",$0);\ gsub(/^[ \t]*[\047"]|[\047"][ \t]*$/,"",$0);\ printf $0; exit}' "$1" >Fix: I'm not aware of any fixes >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 3 22:50:06 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D16041065672 for ; Mon, 3 Jan 2011 22:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 892B48FC18 for ; Mon, 3 Jan 2011 22:50:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03Mo6Dk009751 for ; Mon, 3 Jan 2011 22:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03Mo6rD009750; Mon, 3 Jan 2011 22:50:06 GMT (envelope-from gnats) Resent-Date: Mon, 3 Jan 2011 22:50:06 GMT Resent-Message-Id: <201101032250.p03Mo6rD009750@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Erik Alexander Løkken Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A74C81065673 for ; Mon, 3 Jan 2011 22:46:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 94CDD8FC0C for ; Mon, 3 Jan 2011 22:46:05 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p03Mk5I6040780 for ; Mon, 3 Jan 2011 22:46:05 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p03Mk5ia040779; Mon, 3 Jan 2011 22:46:05 GMT (envelope-from nobody) Message-Id: <201101032246.p03Mk5ia040779@red.freebsd.org> Date: Mon, 3 Jan 2011 22:46:05 GMT From: Erik Alexander Løkken To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Tue, 04 Jan 2011 00:09:48 +0000 Cc: Subject: amd64/153665: AHCI module unconsistent behaviour with SATA3 disk and SATA3 enabled controller X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 22:50:06 -0000 >Number: 153665 >Category: amd64 >Synopsis: AHCI module unconsistent behaviour with SATA3 disk and SATA3 enabled controller >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 03 22:50:06 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Erik Alexander Løkken >Release: FreeBSD 8.2-RC1 >Organization: >Environment: FreeBSD server.bronx.no 8.2-RC1 FreeBSD 8.2-RC1 #2: Thu Dec 30 22:43:15 CET 2010 root@server.bronx.no:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The AHCI module sometimes fails to identify the SATA3 disks (specifically WDC WD1002FAEX-00Z3A0 05.01D05/Western Digital Black 1TB) connected to a HighPoint Rocket 620 2P SATA III in a PCI-express 2x1 slot (identifies as Marvell 88SE912x AHCI SATA controller). I've tested several hardware configurations with inconsistent results. Sometimes the kernel detects the disk and sometimes it does not. I've tested the with two different types of disks (WD Black 1TB SATA3 + WD green 2TB SATA2). BIOS recognizes all disks in both AHCI mode and IDE mode. FreeBSD recognize all drives without the AHCI driver loaded. AHCI recognizes the SATA3 disks when it is connected to a SATA2 controller. AHCI also recognizes SATA2 disks connected to the HighPoint controller. I have to SATA3 disk of the same type with a disk layout consisting of zfs-aware-bootloader, swap partition and zfs-partition. The are configured with as GEOM_MIRROR for swap and zpool mirror for zfs, so I've been able to test several configurations. In all test scenarios described below the AHCI module is loaded from the boot-loader (I'm not aware of any different behavior if the module would have been compiled into the kernel). 1 - Both SATA3 disks connected to HighPoint controller with AHCI loaded - This configuration leads to consistent failure - I've tested this configuration with different BIOS settings including disabling all on board IDE/AHCI/RAID devices - All tests results in zfs boot loader not finding the the zfs root pool 2 - Both SATA3 disks connected to HighPoint controller without AHCI loaded - This results in a working configuration 3 - Both SATA3 disks connected to the built-in controller with/without AHCI loaded - This results in a working configuration - This is my current configuration, so it is easy to provide more information from this setup 4 - The SATA3 disks connected to two different HighPoint controllers - This gives inconsistent results - Sometimes AHCI recognizes one of two disks. Never both disks. - Most of the times tested AHCI does not recognize any disk. - I have a dmesg available from this setup 5 - One SATA3 disk connected to the HighPoint controller and one connected to the builtin controller - This gives inconsistent results - Sometimes the AHCI recognizes both disks and everything is loaded as expected - Sometimes AHCI does not recognize the disk connected to the HighPoint controler - I have dmesg available from this setup 6 - SATA2 disks connected to the HighPoint controller - This results in a working configuration - This is also part of my current setup so more information can be provided Disk connected to SATA2 controller: ada7 at ahcich29 bus 0 scbus29 target 0 lun 0 ada7: ATA-8 SATA 3.x device ada7: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada7: Command Queueing enabled ada7: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) Disk connected to SATA3 controller: ada4 at ahcich19 bus 0 scbus19 target 0 lun 0 ada4: ATA-8 SATA 3.x device ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada4: Command Queueing enabled ada4: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) Reports in dmesg of a disk not correctly identified: (aprobe1:ahcich2:0:0:0): Unexpected signature 0x0062 (aprobe1:ahcich3:0:0:0): Unexpected signature 0x0062 (aprobe1:ahcich9:0:0:0): Unexpected signature 0x0062 If you would like I could do more debugging, but I'm not sure where to go from here. I have three highpoint controllers available in the machine. The current configuration consist of 7 WD Green disks (4 connected to HighPoint controllers + 3 connected to motherboard controller) and 2 WD Black disks (connected to motherboard) with AHCI loaded. Since the SATA3 disks are mirrored, there should not be any problems trying different setups. >How-To-Repeat: Connect to SATA3 (WD Green 2TB) disks to one or to HighPoint 620 controllers. This gives consistent results of a non-working configuration. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 4 02:51:12 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7074F106564A; Tue, 4 Jan 2011 02:51:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 46F9C8FC13; Tue, 4 Jan 2011 02:51:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p042pCXf076221; Tue, 4 Jan 2011 02:51:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p042pCri076217; Tue, 4 Jan 2011 02:51:12 GMT (envelope-from linimon) Date: Tue, 4 Jan 2011 02:51:12 GMT Message-Id: <201101040251.p042pCri076217@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/153659: awk(1) segfaults when trying to extract a combination of special characters X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 02:51:12 -0000 Old Synopsis: awk segfaults when trying to extract a combination of special characters New Synopsis: awk(1) segfaults when trying to extract a combination of special characters Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Jan 4 02:50:50 UTC 2011 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=153659 From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 5 23:51:44 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D305106566B for ; Wed, 5 Jan 2011 23:51:44 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 4EE088FC0A for ; Wed, 5 Jan 2011 23:51:43 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p05NpZeY078938; Wed, 5 Jan 2011 15:51:42 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns0.ultimatedns.net ([168.103.150.26]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Wed, 5 Jan 2011 15:51:42 -0800 (PST) Message-ID: <4e53f2e33d1bccc74df3fc4ceec2ddb8.dnswclient@www.dnswatch.com> In-Reply-To: <4D21EAFD.4020104@gmail.com> References: <9193ef9ae95084284226832557f8c755.dnswclient@www.dnswatch.com> <20110102125137.4423cb08@ernst.jennejohn.org> <15cc929589a6426f0dad97fac66ed328.dnswclient@www.dnswatch.com> <20110102150551.24f5193e@ernst.jennejohn.org> <0cdfb22d89c8f85ec31704c35982e0e2.dnswclient@www.dnswatch.com> <4D2090FC.5030409@lazlarlyricon.com> <4D20B769.5000704@gmail.com> <28cdac712efe4eff35e0d775a0270971.dnswclient@www.dnswatch.com> <4D21EAFD.4020104@gmail.com> Date: Wed, 5 Jan 2011 15:51:42 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Is Gnome2 not supported on the amd64 ARCH? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2011 23:51:44 -0000 On Mon, January 3, 2011 7:27 am, Luchesar V. ILIEV wrote: > On 01/03/11 08:45, fbsdmail@dnswatch.com wrote: > >> # # # TOP POSTING IS EVIL # # # >> >>>> 2011-01-02 15:42, fbsdmail@dnswatch.com skrev: >>>> <...> >>>> >>>> >>>>> Hello again, and thanks for your response. >>>>> I commented it out after responding to your response, and >>>>> it happily built. I just figured I'd use the CPUTYPE?= option to >>>>> gain better amd64 profiling, but apparently it's only _really_ >>>>> available for the i386 CPU's. I say that because I've always used >>>>> that option when building on those ARCH types, and never ran into >>>>> a problem. Oh well, hopefully sometime son, it'll be better >>>>> supported on the amd64 - fingers crossed. :) >>>>> >>>>> Thanks again for taking the time to respond. >>>>> >>>>> >>>>> >>>>> --Chris >>>>> >>>>> >>>>> >>>>> >>>> >>>> Hi, >>>> >>>> >>>> >>>> I have an Intel CPU that's amd64 compatible, and I use >>>> CPUTYPE?=native, >>>> which never gave me any problems (I use it for all builds, including >>>> kernel and world). I can't say whether it works with AMD CPUs >>>> though. Nor can I really say if it makes a difference, because I've >>>> never tried without it. >>>> >>>> /Rolf >>>> _______________________________________________ >>>> 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" >>>> >>>> >> On Sun, January 2, 2011 9:35 am, Luchesar V. ILIEV wrote: >> >>> hw.model: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ >>> CPUTYPE?= athlon64 >>> >>> >>> >>> I've never encountered any CPUTYPE specific problems so far, and I >>> have GNOME2 and almost 1000 ports compiled on my desktop, plus the OS >>> itself. >>> >>> >>> I wonder if "athlon-mp" is so different to be causing the problems >>> you've encountered or if there was something else that got fixed >>> coincidentally when you commented out CPUTYPE from make.conf. >> >> Greetings Luchesar, and thank you for your reply. >> I've got a couple of other threads on the @stable list, and one >> other on this one related to this. Last time I researched make(1) and >> make.conf(5), the common consensus was that (open)ssl, and possibly a >> couple of others were the only things that ever made use of the flag. >> However, when I experimented heavily on older >> CPU's, I discovered that CPUTYPE?= _did_ make a difference. In >> some cases it simply made the difference for correctly recognizing the >> CPU, in all cases, it added the "feature set" that that CPU >> possessed - SSE, SSE2, 3DNow, etc... So, I find myself inclined to make >> use of CPUTYPE?= whenever possible. Problem is, I don't always keep up >> on gcc(1)'s changes/additions. Which I think is the case here. My >> _guess_ is that they changed the >> name(s) - however slightly, and I found out the "hard way". :-\ Bottom >> line; I need to take the time, and find the difference(s) from >> then<--to-->now to use it effectively. >> >> Thanks again for your reply. >> >> >> --Chris >> > > Hi Chris, > > > Indeed, I was going to comment about those notes in the documentation as > well. To be honest, I've always been lazy to do my own research in the > FreeBSD's code -- it's rather typical for the documentation to lag > behind the code, and that's understandable even for commercial projects. > > BTW, an interesting file to check is also /usr/share/mk/bsd.cpu.mk. And > that's why for the moment I'm a bit reluctant (probably naively) about > using CPUTYPE=native -- it is understood by GCC itself, but bsd.cpu.mk > "knows" nothing about it. Well, on amd64 it really does nothing more > than to add "-march=${CPUTYPE}" to CFLAGS, which should be OK with > "native", but it also seems to "describe" available CPU capabilities > (e.g. mmx, sse, 3dnow) for the other mk files -- and that depends on the > correct value, provided by CPUTYPE. I'm not sure this would work as > expected with "native", but then again I might be quite wrong. > > In any case, I (and likely others) will really appreciate if you share > your findings with the list -- and thank you for doing it so far. :) You're correct about bsd.cpu.mk, I researched it in the past, and my final consensus was that it really only applies to building kernel(s), and possibly world. In either of these cases it is usually safer to _not_ use any profiling. So I only consider that file "informational". I've added CPUTYPE?=athlon64 to my make.conf(5) and have since built some 250 ports - all w/o incident. I know it was picked up during the make(1) process, as make(1) echoed (as you already noted) -march=athlon64. So all in all, I think there is no problems (assuming the _correct_ CPUTYPE is declared). ;) So I suppose in the "big picture" /determining/ _which_ CPUTYPE is up to the user, and given that athlon-mp no longer works for me on AM2, or AM3 CPU's, it's not always going to be consistent (YMMV). :) > > Cheers, > Luchesar > > > P.S. Oh, and, erm... sorry for that evil top posting... (blush) LOL No worries. It's an easy thing to do, but sadly, doing so corrupts the thread. Best wishes, and thanks for your reply. --Chris > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 6 22:50:08 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 818951065693 for ; Thu, 6 Jan 2011 22:50:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 440BA8FC0C for ; Thu, 6 Jan 2011 22:50:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06Mo8pE054338 for ; Thu, 6 Jan 2011 22:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06Mo84c054337; Thu, 6 Jan 2011 22:50:08 GMT (envelope-from gnats) Resent-Date: Thu, 6 Jan 2011 22:50:08 GMT Resent-Message-Id: <201101062250.p06Mo84c054337@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Patrick Mackinlay Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6DD41065693 for ; Thu, 6 Jan 2011 22:45:15 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id C62CE8FC13 for ; Thu, 6 Jan 2011 22:45:15 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p06MjFAp019166 for ; Thu, 6 Jan 2011 22:45:15 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p06MjFSW019165; Thu, 6 Jan 2011 22:45:15 GMT (envelope-from nobody) Message-Id: <201101062245.p06MjFSW019165@red.freebsd.org> Date: Thu, 6 Jan 2011 22:45:15 GMT From: Patrick Mackinlay To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Thu, 06 Jan 2011 23:31:38 +0000 Cc: Subject: amd64/153746: kernel crash with 2 X11 sessions on amd64 with radeon drm X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 22:50:08 -0000 >Number: 153746 >Category: amd64 >Synopsis: kernel crash with 2 X11 sessions on amd64 with radeon drm >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 06 22:50:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Patrick Mackinlay >Release: 8.1-RELEASE-p2 (affects 8.0 as well) >Organization: >Environment: FreeBSD patrick.uknet.spacesurfer.com 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #3: Thu Jan 6 21:40:18 GMT 2011 root@patrick.uknet.spacesurfer.com:/usr/obj/usr/src/sys/PATRICK amd64 >Description: If I start 2 X11 sessions (startx and start -- :1). The close the sessions on display :1, when I switch to the session on display :0 the system reboots. I have an amd64 with a ATI radeon card: drm0: on vgapci0 Note that if I never close either X11 session there is no problem with stability (weeks uptime), however the only graphics intensive app I use is mplayer. mplayer is the only reason I need drm, however the bug will be triggered even if I havn't used mplayer in my X11 session. I will attach the output from dmesg with my full system setup and the output from the two xorg log files. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 7 11:40:57 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04787106566B for ; Fri, 7 Jan 2011 11:40:57 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 982C38FC13 for ; Fri, 7 Jan 2011 11:40:56 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id p07BemjW086418; Fri, 7 Jan 2011 03:40:54 -0800 (PST) (envelope-from fbsdmail@dnswatch.com) Received: from udns0.ultimatedns.net ([168.103.150.26]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Fri, 7 Jan 2011 03:40:55 -0800 (PST) Message-ID: In-Reply-To: <201101062245.p06MjFSW019165@red.freebsd.org> References: <201101062245.p06MjFSW019165@red.freebsd.org> Date: Fri, 7 Jan 2011 03:40:55 -0800 (PST) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: patrick@spacesurfer.com Subject: Re: amd64/153746: kernel crash with 2 X11 sessions on amd64 with radeon drm X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 11:40:57 -0000 On Thu, January 6, 2011 2:45 pm, Patrick Mackinlay wrote: > >> Number: 153746 >> Category: amd64 >> Synopsis: kernel crash with 2 X11 sessions on amd64 with radeon >> drm >> Confidential: no >> Severity: non-critical >> Priority: medium >> Responsible: freebsd-amd64 >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: sw-bug >> Submitter-Id: current-users >> Arrival-Date: Thu Jan 06 22:50:07 UTC 2011 >> Closed-Date: >> Last-Modified: >> Originator: Patrick Mackinlay >> Release: 8.1-RELEASE-p2 (affects 8.0 as well) >> Organization: >> Environment: >> > FreeBSD patrick.uknet.spacesurfer.com 8.1-RELEASE-p2 FreeBSD > 8.1-RELEASE-p2 #3: Thu Jan 6 21:40:18 GMT 2011 > root@patrick.uknet.spacesurfer.com:/usr/obj/usr/src/sys/PATRICK amd64 > >> Description: >> > If I start 2 X11 sessions (startx and start -- :1). The close the > sessions on display :1, when I switch to the session on display :0 the > system reboots. I have an amd64 with a ATI radeon card: > > drm0: on vgapci0 > > > Note that if I never close either X11 session there is no problem with > stability (weeks uptime), however the only graphics intensive app I use > is mplayer. mplayer is the only reason I need drm, however the bug will > be triggered even if I havn't used mplayer in my X11 session. Greetings, Fact is, Mplayer has nothing to do with when/how drm is loaded. 2 possibilities exist for loading; @boot via loader.conf(5), or when starting X via xorg.conf(5). If you're loading it via xorg.conf(5), and suspect drm to be the culprit. The easiest solution would be to comment the line that loads it in your xorg.conf(5) file. Then startx(1), and see if there's any difference in behavior. FWIW I haven't been able to use HALd on _any_ 64bit box. So against the suggested entries in rc.conf(8): dbus_enable="YES" hald_enable="YES" I need to use hald_enable="NO" or I have big problems running X. I only mention it, in case this might also apply to your situation. HTH --Chris > > I will attach the output from dmesg with my full system setup and the > output from the two xorg log files. >> How-To-Repeat: >> > >> Fix: >> > > >> Release-Note: >> Audit-Trail: >> Unformatted: >> > _______________________________________________ > 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" > > -- kern: FreeBSD 8.1-RELEASE amd64 From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 7 13:52:47 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B34C71065673 for ; Fri, 7 Jan 2011 13:52:47 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8E68FC0A for ; Fri, 7 Jan 2011 13:52:46 +0000 (UTC) Received: by mail-wy0-f182.google.com with SMTP id 19so17574260wyf.13 for ; Fri, 07 Jan 2011 05:52:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=78iYKx/7+eBBeko9sUkrMjBnReINCmTMx4tJPSyXwb4=; b=eFRRPLRhUAGe6AHrJMm+WEwKHjBJ98gmrZb2CeEZ+GLE7QOp1rddemcwjBx+ZA8vc9 nPHwAiFdPM1gfItbVCW6GAK5kMGDd5n86yZlVhw79XJYpxECeU2wTYk06mrqbxgKe+8w v77Eb1TTpdfYF/hXStmp5lf1Ylk7BYFTbQqCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i63zv1UtBw7QBwsD02zjX7Adg8PEvV+Cd1Z4/Wz02AED6yaezjCv9yQfVnIVY/abvX C5x1XX8bQ6aDPxu+AhGFXYMddXZxGmgmNHtvIorlf5kDrJCrQvDjonJrpNIhAvX6UWY/ zf1+UyfkprUURRXuRsJB0O7G3DsFktzTBi6bk= MIME-Version: 1.0 Received: by 10.227.146.149 with SMTP id h21mr15424184wbv.43.1294406645377; Fri, 07 Jan 2011 05:24:05 -0800 (PST) Received: by 10.227.59.3 with HTTP; Fri, 7 Jan 2011 05:24:05 -0800 (PST) In-Reply-To: References: <201101062245.p06MjFSW019165@red.freebsd.org> Date: Fri, 7 Jan 2011 14:24:05 +0100 Message-ID: From: Oliver Pinter To: fbsdmail@dnswatch.com Content-Type: text/plain; charset=ISO-8859-1 Cc: patrick@spacesurfer.com, freebsd-amd64@freebsd.org Subject: Re: amd64/153746: kernel crash with 2 X11 sessions on amd64 with radeon drm X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 13:52:47 -0000 http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html http://old.nabble.com/freebsd7,-radeon,-xorg-server-->-deadlock-or-so-td27524122.html On 1/7/11, fbsdmail@dnswatch.com wrote: > > On Thu, January 6, 2011 2:45 pm, Patrick Mackinlay wrote: >> > >>> Number: 153746 >>> Category: amd64 >>> Synopsis: kernel crash with 2 X11 sessions on amd64 with radeon >>> drm >>> Confidential: no >>> Severity: non-critical >>> Priority: medium >>> Responsible: freebsd-amd64 >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Thu Jan 06 22:50:07 UTC 2011 >>> Closed-Date: >>> Last-Modified: >>> Originator: Patrick Mackinlay >>> Release: 8.1-RELEASE-p2 (affects 8.0 as well) >>> Organization: >>> Environment: >>> >> FreeBSD patrick.uknet.spacesurfer.com 8.1-RELEASE-p2 FreeBSD >> 8.1-RELEASE-p2 #3: Thu Jan 6 21:40:18 GMT 2011 >> root@patrick.uknet.spacesurfer.com:/usr/obj/usr/src/sys/PATRICK amd64 >> >>> Description: >>> >> If I start 2 X11 sessions (startx and start -- :1). The close the >> sessions on display :1, when I switch to the session on display :0 the >> system reboots. I have an amd64 with a ATI radeon card: >> >> drm0: on vgapci0 >> >> >> Note that if I never close either X11 session there is no problem with >> stability (weeks uptime), however the only graphics intensive app I use >> is mplayer. mplayer is the only reason I need drm, however the bug will >> be triggered even if I havn't used mplayer in my X11 session. > Greetings, > Fact is, Mplayer has nothing to do with when/how drm is loaded. 2 > possibilities exist for loading; @boot via loader.conf(5), or when > starting X via xorg.conf(5). > If you're loading it via xorg.conf(5), and suspect drm to be the culprit. > The easiest solution would be to comment the line that loads it in your > xorg.conf(5) file. Then startx(1), and see if there's any difference in > behavior. FWIW I haven't been able to use HALd on _any_ 64bit box. So > against the suggested entries in rc.conf(8): > dbus_enable="YES" > hald_enable="YES" > > I need to use > > hald_enable="NO" > or I have big problems running X. I only mention it, in case this > might also apply to your situation. > > HTH > > --Chris > >> >> I will attach the output from dmesg with my full system setup and the >> output from the two xorg log files. >>> How-To-Repeat: >>> >> >>> Fix: >>> >> >> >>> Release-Note: >>> Audit-Trail: >>> Unformatted: >>> >> _______________________________________________ >> 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" >> >> > > > -- > kern: > FreeBSD 8.1-RELEASE amd64 > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 7 19:11:16 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5774B1065696 for ; Fri, 7 Jan 2011 19:11:16 +0000 (UTC) (envelope-from patrick@spacesurfer.com) Received: from ws9.spacesurfer.com (ws9.spacesurfer.com [206.71.190.107]) by mx1.freebsd.org (Postfix) with ESMTP id 323598FC08 for ; Fri, 7 Jan 2011 19:11:15 +0000 (UTC) Received: from ws9.spacesurfer.com (localhost.spacesurfer.com [127.0.0.1]) by ws9.spacesurfer.com (Postfix) with ESMTP id 65980118502C; Fri, 7 Jan 2011 19:11:14 +0000 (GMT) X-My-Spf: pass (ws9.spacesurfer.com: domain of patrick@spacesurfer.com designates 206.71.190.107 as permitted sender) X-My-Id: My::PostFix::Filter.336a4b6502ba4d27654f X-My-Id: My::PostFix::Filter.336a4b6602ba4d276550 X-My-Id: My::PostFix::Filter.336a4b6702ba4d276551 Received: from patrick.uknet.spacesurfer.com (82.69.172.105.ip.spacesurfer.com [82.69.172.105]) by ws9.spacesurfer.com (Postfix) with ESMTPA; Fri, 7 Jan 2011 19:11:10 +0000 (GMT) Message-ID: <4D276549.2050105@spacesurfer.com> Date: Fri, 07 Jan 2011 19:11:05 +0000 From: Patrick Mackinlay User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110101 Thunderbird/3.0.11 MIME-Version: 1.0 To: Oliver Pinter References: <201101062245.p06MjFSW019165@red.freebsd.org> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: url=http://patrick.spacesurfer.com/pgp_public_key.html Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFC2221DD4DA520C44E6F67D1" X-Mailman-Approved-At: Fri, 07 Jan 2011 19:43:10 +0000 Cc: fbsdmail@dnswatch.com, freebsd-amd64@freebsd.org Subject: Re: amd64/153746: kernel crash with 2 X11 sessions on amd64 with radeon drm X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2011 19:11:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFC2221DD4DA520C44E6F67D1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, This issue is not about when drm is loaded. The bug happens 100% reliably and it does not matter how drm is loaded. I can load the radeon kernel module at boot, manually before starting X11 or on demand when xorg starts (that is how it is currently loaded) and the results will be the same. I only mentioned mplayer because this is the only app I use that uses any of the DRM functionality and I dont even have to run mplayer for this issue to occur. However, the problem is definitely with DRM because if I do not load the radeon kernel module then the problem goes away (and I cant use mplayer because its too slow!). Regarding hald, I have this disabled it in rc.conf with an interesting comment: # hald causes the mouse to go haywire when x starts hald_enable=3D"NO" So I guess I had problems with this in the past. Either way hald is unrelated to this problem. Regarding the two links about deadlocks and unresponsive behaviour. This also is not the case for me. The machine is 100% fine unless I close an X session. I never experience deadlocks or unresponsive behaviour. The crash always occurs when I have drm enabled, start two x sessions. Close one (returning to a terminal) and exactly when I switch to the other X session (CTRL-ALT-F9) the machine will automatically reboot. It never locks or shows a kernel panic message, it just reboots. Patrick On 01/07/11 13:24, Oliver Pinter wrote: > http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.htm= l > http://old.nabble.com/freebsd7,-radeon,-xorg-server-->-deadlock-or-so-t= d27524122.html >=20 > On 1/7/11, fbsdmail@dnswatch.com wrote: >> >> On Thu, January 6, 2011 2:45 pm, Patrick Mackinlay wrote: >>> >> >>>> Number: 153746 >>>> Category: amd64 >>>> Synopsis: kernel crash with 2 X11 sessions on amd64 with radeo= n >>>> drm >>>> Confidential: no >>>> Severity: non-critical >>>> Priority: medium >>>> Responsible: freebsd-amd64 >>>> State: open >>>> Quarter: >>>> Keywords: >>>> Date-Required: >>>> Class: sw-bug >>>> Submitter-Id: current-users >>>> Arrival-Date: Thu Jan 06 22:50:07 UTC 2011 >>>> Closed-Date: >>>> Last-Modified: >>>> Originator: Patrick Mackinlay >>>> Release: 8.1-RELEASE-p2 (affects 8.0 as well) >>>> Organization: >>>> Environment: >>>> >>> FreeBSD patrick.uknet.spacesurfer.com 8.1-RELEASE-p2 FreeBSD >>> 8.1-RELEASE-p2 #3: Thu Jan 6 21:40:18 GMT 2011 >>> root@patrick.uknet.spacesurfer.com:/usr/obj/usr/src/sys/PATRICK amd6= 4 >>> >>>> Description: >>>> >>> If I start 2 X11 sessions (startx and start -- :1). The close the >>> sessions on display :1, when I switch to the session on display :0 th= e >>> system reboots. I have an amd64 with a ATI radeon card: >>> >>> drm0: on vgapci0 >>> >>> >>> Note that if I never close either X11 session there is no problem wit= h >>> stability (weeks uptime), however the only graphics intensive app I u= se >>> is mplayer. mplayer is the only reason I need drm, however the bug wi= ll >>> be triggered even if I havn't used mplayer in my X11 session. >> Greetings, >> Fact is, Mplayer has nothing to do with when/how drm is loaded. 2 >> possibilities exist for loading; @boot via loader.conf(5), or when >> starting X via xorg.conf(5). >> If you're loading it via xorg.conf(5), and suspect drm to be the culpr= it. >> The easiest solution would be to comment the line that loads it in you= r >> xorg.conf(5) file. Then startx(1), and see if there's any difference i= n >> behavior. FWIW I haven't been able to use HALd on _any_ 64bit box. So >> against the suggested entries in rc.conf(8): >> dbus_enable=3D"YES" >> hald_enable=3D"YES" >> >> I need to use >> >> hald_enable=3D"NO" >> or I have big problems running X. I only mention it, in case this >> might also apply to your situation. >> >> HTH >> >> --Chris >> >>> >>> I will attach the output from dmesg with my full system setup and the= >>> output from the two xorg log files. >>>> How-To-Repeat: >>>> >>> >>>> Fix: >>>> >>> >>> >>>> Release-Note: >>>> Audit-Trail: >>>> Unformatted: >>>> >>> _______________________________________________ >>> freebsd-amd64@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >>> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.o= rg" >>> >>> >> >> >> -- >> kern: >> FreeBSD 8.1-RELEASE amd64 >> >> >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.or= g" >> --=20 Patrick Mackinlay patrick@spacesurfer.com http://patrick.spacesurfer.com/ tel: +44.7050699851 Yahoo messenger: patrick00_uk fax: +44.7050699852 SpaceSurfer Limited http://www.spacereg.com/ --------------enigFC2221DD4DA520C44E6F67D1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFNJ2VND97IpyzY3RIRAvfgAJ9MdaynNei+U8KnvFAi2O8WE+IivwCfaNU7 B6qduzAoSN8A39xFpwEO0zc= =oBs0 -----END PGP SIGNATURE----- --------------enigFC2221DD4DA520C44E6F67D1--