From owner-freebsd-amd64@FreeBSD.ORG Sun Jun 26 04:24:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 408A716A41F; Sun, 26 Jun 2005 04:24:12 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFAED43D48; Sun, 26 Jun 2005 04:24:11 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j5Q4NvuV049566; Sat, 25 Jun 2005 22:23:57 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j5Q4Nue5049565; Sat, 25 Jun 2005 22:23:56 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Sat, 25 Jun 2005 22:23:56 -0600 From: Greg Lewis To: Neo Jia Message-ID: <20050626042355.GA41119@misty.eyesbeyond.com> References: <42BC8310.9040501@cse.unl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42BC8310.9040501@cse.unl.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org, freebsd-java@freebsd.org Subject: Re: How to build JDK15 on AMD64 with FreeBSD? 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, 26 Jun 2005 04:24:12 -0000 On Fri, Jun 24, 2005 at 05:02:56PM -0500, Neo Jia wrote: > These days, I tried to build the JDK15 on AMD64 with Fedora Core 3, but > failed. And I happened to find out that in these two mailing lists, > there were many people who had successfully built it with FreeBSD. I > hope I could get some detailed information about the building procedure. > Do you also use the source code from SUN SCSL or another version > maintained by FreeBSD.org? What is the requirement I should meet to > build it on FreeBSD, such as the version of FreeBSD? Do I still need GCC > 3.2.2? > > Sorry about so many questions at the first time. Your instructions will > be greatly appreciated! We use the Sun SCSL source code as the base for our port. However, many patches are required for it to build on FreeBSD. These are contained in a patchset that you can download at http://www.eyesbeyond.com/freebsddom/java/jdk15.html The easiest way to do this is simply to use the jdk15 port. Simply do the following: cd /usr/ports/java/jdk15 make install and follow the instructions. There is one caveat on amd64 -- one of the build commands will fail strangely (this is a bug in the Linux emulation on amd64 as far as I can determine). Simply execute that command by hand and restart the build. Also, if you have an EM64T rather than an actual amd64 then you will need one patch (just reply to me and I can send it to you or search the mailing list archives and you should find it). -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sun Jun 26 04:24:52 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD25016A41F; Sun, 26 Jun 2005 04:24:52 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52A2643D49; Sun, 26 Jun 2005 04:24:52 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j5Q4OcNc049577; Sat, 25 Jun 2005 22:24:38 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j5Q4ObUJ049576; Sat, 25 Jun 2005 22:24:37 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Sat, 25 Jun 2005 22:24:36 -0600 From: Greg Lewis To: Neo Jia Message-ID: <20050626042436.GB41119@misty.eyesbeyond.com> References: <42BC8310.9040501@cse.unl.edu> <42BDCB62.1030602@cse.unl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42BDCB62.1030602@cse.unl.edu> User-Agent: Mutt/1.4.2.1i Cc: Till Riedel , freebsd-amd64@FreeBSD.org, freebsd-java@FreeBSD.org Subject: Re: How to build JDK15 on AMD64 with FreeBSD? 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, 26 Jun 2005 04:24:52 -0000 On Sat, Jun 25, 2005 at 04:23:46PM -0500, Neo Jia wrote: > Thank you for your information. One question about your build, do you > make any modification on the SUN JAVA SCSL? I am afraid that you cannot > pass the sanity checking with the gcc 3.4.2? And the default GCC used by > 5.4-RELEASE is 3.4.2, right? One of the FreeBSD specific patches changes the sanity check to allow gcc 3.4 to be used. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sun Jun 26 05:33:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3642A16A41C for ; Sun, 26 Jun 2005 05:33:30 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from smtpclu-2.eunet.yu (smtpclu-2.eunet.yu [194.247.192.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2F6343D4C for ; Sun, 26 Jun 2005 05:33:28 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from faust.net (P-14.125.EUnet.yu [213.240.14.125]) by smtpclu-2.eunet.yu (8.12.11/8.12.11) with ESMTP id j5Q5XLif031849 for ; Sun, 26 Jun 2005 07:33:22 +0200 Received: by faust.net (Postfix, from userid 1001) id 5613E4205; Sun, 26 Jun 2005 07:32:47 +0200 (CEST) Date: Sun, 26 Jun 2005 07:32:47 +0200 From: Zoran Kolic To: freebsd-amd64@freebsd.org Message-ID: <20050626053247.GA923@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scan: EUnet-AVAS-Milter X-AVAS-Virus-Status: clean X-Spam-Checker: EUnet-AVAS-Milter X-AVAS-Spam-Score: -0.0 X-AVAS-Spam-Symbols: BAYES_44 Subject: cpufreq enabling 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, 26 Jun 2005 05:33:30 -0000 Hi all! I've tried to include "cpufreq" into kernel and building just failed. There is no device like this. What is the way to do something like that on 5.4 release? Or just ready for current? Best regards Zoran From owner-freebsd-amd64@FreeBSD.ORG Sun Jun 26 22:49:24 2005 Return-Path: X-Original-To: freebsd-amd64@Freebsd.org Delivered-To: freebsd-amd64@Freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A792416A41C for ; Sun, 26 Jun 2005 22:49:24 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BF7143D55 for ; Sun, 26 Jun 2005 22:49:23 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from [66.92.151.194] (june.chuckr.org [66.92.151.194]) by chuckr.org (Postfix) with ESMTP id 9F795114F2 for ; Sun, 26 Jun 2005 18:41:49 -0400 (EDT) Message-ID: <42BF4096.6020609@chuckr.org> Date: Sun, 26 Jun 2005 23:56:06 +0000 From: Chuck Robey User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050524) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@Freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: amd64: building xorg-libraries 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, 26 Jun 2005 22:49:24 -0000 I can't get this built, and the error I see is that the assembler is barfing over certain iincorrect sequences. I'm suspicious, because the directory it's in is the xc/lib/GL/i386 subdirectory (qnd there isn't any obvious amd64 dir to set things to). Is there any workaround, in building xorg-libraries? I should be completely honest, and admit why I need to build this, because it might have some bearing ... I have both a i386 *and* a amd64 system, and I had the PACKAGESITE var set wrong, so that aI had been using pkg_add with the wrong arch, when I last decided to try upgrading kde. Yes, it's dumb, and I've been the last two days slowly recompiling things. The problem I see with the xorg-libraries, it's with both libXau.so.0 and libX11.so.6, they both wont seem to allow ldconfig to work with them ... the exact error is /libexec/ld-elf.so.1: /usr/X11R6/lib/libXau.so.0: unsupported file layout /libexec/ld-elf.so.1: /usr/X11R6/lib/libX11.so.6: unsupported file layout that's it, I'm finished being candid. If you wish, you may address your *LOL* comments to me, offline. I guess I deserve it. Here's the last bit of the actual error listing: cd /raid/ports/x11/xorg-libraries/work/xc/exports/lib && ln -s ../../lib/Xv/libXv.a . making all in lib/GL... making all in lib/GL/mesa... making all in lib/GL/mesa/x86... rm -f common_x86.o unshared/common_x86.o cc -c -ansi -pedantic -Wno-system-headers -Dasm=__asm -Wall -Wpointer-arith -Wundef -I/raid/ports/x11/xorg-libra ries/work/xc/extras/Mesa/src/mesa -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/include -I/raid/ports/x11/xorg-libraries/work/xc/lib/GL/include -I/raid/ports/x11/xorg-libraries/work/xc/ extras/Mesa/src/mesa/main -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/src/mesa/x86 -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/src/mesa/glapi -I/raid/ports/x11/xorg-libraries/work/xc - I/raid/ports/x11/xorg-libraries/work/xc/exports/include -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROW PROTO -DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X8 6_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -O2 -fno-strict-aliasing -pipe common_x86.c -o unshare d/common_x86.oesa/x86 -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/src/mesa/glapi -I/raid/po rts/x11/xorg-libraries/work/xc -I/raid/ports/x11/xorg-libraries/work/xc/exports/include -I/usr/X11R6/include -DCSR G_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE _DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -fPIC common_x86.cbraries/wor k/xc/extras/Mesa/src/mesa/main -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/src/mesa/x86 -I/raid/ports/x11/xorg-libraries/work/xc/extras/Mesa/src/mesa/glapi common_x86_asm.S | grep -v '^\#' > common_x86_asm.i:14: Error: suffix or operands invalid for `push' common_x86_asm.i:15: Error: suffix or operands invalid for `popf' common_x86_asm.i:16: Error: suffix or operands invalid for `pushf' common_x86_asm.i:17: Error: suffix or operands invalid for `pop' common_x86_asm.i:31: Error: `4(%esp)' is not a valid 64 bit base/index expression common_x86_asm.i:32: Error: suffix or operands invalid for `push' common_x86_asm.i:33: Error: suffix or operands invalid for `push' common_x86_asm.i:37: Error: `16(%esp)' is not a valid 64 bit base/index expression common_x86_asm.i:38: Error: `(%edi)' is not a valid 64 bit base/index expression july:root:/usr/ports/x11/xorg-libraries:#163# From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 10:11:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20D3516A41C for ; Mon, 27 Jun 2005 10:11:12 +0000 (GMT) (envelope-from freebsd-amd64@molecon.ru) Received: from amd64.molecon.ru (amd64.molecon.ru [213.219.245.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2BF143D1D for ; Mon, 27 Jun 2005 10:11:11 +0000 (GMT) (envelope-from freebsd-amd64@molecon.ru) Received: from [194.154.84.59] (helo=[10.20.5.22]) by amd64.molecon.ru with esmtp (Exim 4.51 (FreeBSD)) id 1DmqZp-0006yE-QV for freebsd-amd64@freebsd.org; Mon, 27 Jun 2005 14:10:54 +0400 Date: Mon, 27 Jun 2005 14:10:14 +0400 From: Oleg Rusanov X-Mailer: The Bat! (v3.0) Professional Organization: Molecon X-Priority: 3 (Normal) Message-ID: <1525910592.20050627141014@molecon.ru> To: freebsd-amd64 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-PopBeforeSMTPSenders: freebsd-amd64@molecon.ru, freebsd-opennet@molecon.ru, info@molecon.ru, mysql@molecon.ru, oleg@molecon.ru X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - amd64.molecon.ru X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - molecon.ru X-Source: X-Source-Args: X-Source-Dir: Subject: "sh -i" My server was hacked. How can i found hole on my server? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oleg Rusanov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2005 10:11:12 -0000 Hello. My server was hacked. The CPU has been loaded on 99 % by "sh -i" process. I found out that someone has started phpshell through a hole in one of phpbb forums. Also has filled in scripts for flud and spam and "vadim script" in "/tmp". I has made it noexec. Recently has found out the same process. May be i have left again /tmp opened, or other hole may be. What is better to do for clean my system? amd64# ps aux -H USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND nobody 60138 99.0 0.2 12796 4844 ?? RL 7:11AM 739:26.28 sh -i (perl5.8.6) amd64# ps -lp 60138 UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 65534 60138 1 291 114 0 12796 4844 - R ?? 762:55.06 sh -i (perl5.8.6) amd64# (i can not find info about parent process 65534) amd64# sockstat| grep 60138 nobody perl5.8.6 60138 3 tcp4 my_ip:55000 161.53.178.240:9999 amd64# amd64# lsof -p 60138 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME perl5.8.6 60138 nobody cwd VDIR 4,13 512 2 / perl5.8.6 60138 nobody rtd VDIR 4,13 512 2 / perl5.8.6 60138 nobody txt VREG 4,18 13144 6312845 /usr/local/bin/perl5.8.6 perl5.8.6 60138 nobody txt VREG 4,13 173264 616 /libexec/ld-elf.so.1 perl5.8.6 60138 nobody txt VREG 4,18 1272229 6524324 /usr/local/lib/perl5/5.8.6/mach/CORE/libperl.so perl5.8.6 60138 nobody txt VREG 4,13 151160 576 /lib/libm.so.3 perl5.8.6 60138 nobody txt VREG 4,13 33024 339 /lib/libcrypt.so.2 perl5.8.6 60138 nobody txt VREG 4,13 52064 583 /lib/libutil.so.4 perl5.8.6 60138 nobody txt VREG 4,13 1055864 585 /lib/libc.so.5 perl5.8.6 60138 nobody txt VREG 4,18 22226 6901089 /usr/local/lib/perl5/5.8.6/mach/auto/IO/IO.so perl5.8.6 60138 nobody txt VREG 4,18 28921 6901280 /usr/local/lib/perl5/5.8.6/mach/auto/Socket/Socket.so perl5.8.6 60138 nobody 0r VCHR 2,2 0t0 7 /dev/null perl5.8.6 60138 nobody 1u PIPE 0x6f537410 0 ->0xffffff006f5372d0 perl5.8.6 60138 nobody 2w VREG 4,18 47856095 6407163 /usr/local/apache/logs/error_log perl5.8.6 60138 nobody 3u IPv4 0xffffff00168142c0 0t0 TCP my_hostname:55000->zagreb.hr.eu.undernet.org:9999 (ESTABLISHED) perl5.8.6 60138 nobody 4u IPv4 0t0 TCP no PCB, CANTSENDMORE, CANTRCVMORE perl5.8.6 60138 nobody 15w VREG 4,18 47856095 6407163 /usr/local/apache/logs/error_log perl5.8.6 60138 nobody 18w VREG 4,18 84 6406351 /usr/local/apache/domlogs/my_site.ru-bytes_log ... apache logs... perl5.8.6 60138 nobody 61w VREG 4,18 847357 6407164 /usr/local/apache/logs/ssl_engine_log perl5.8.6 60138 nobody 62w VREG 4,16 147300 8310 /var/log/my_site.ru perl5.8.6 60138 nobody 63w VREG 4,18 0 6406441 /usr (/dev/ad4s1f) perl5.8.6 60138 nobody 109w VREG 4,18 0 6406441 /usr (/dev/ad4s1f) amd64# amd64# fstat -p 60138 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W nobody perl5.8.6 60138 root / 2 drwxr-xr-x 512 r nobody perl5.8.6 60138 wd / 2 drwxr-xr-x 512 r nobody perl5.8.6 60138 text /usr 6312845 -rwxr-xr-x 13144 r nobody perl5.8.6 60138 0 /dev 7 crw-rw-rw- null r nobody perl5.8.6 60138 1* pipe ffffff006f537410 <-> ffffff006f5372d0 0 rw nobody perl5.8.6 60138 2 /usr 6407163 -rw-r--r-- 47853541 w nobody perl5.8.6 60138 3* internet stream tcp ffffff00168142c0 nobody perl5.8.6 60138 4* internet stream tcp nobody perl5.8.6 60138 15 /usr 6407163 -rw-r--r-- 47853541 w nobody perl5.8.6 60138 18 /usr 6406351 -rw-r--r-- 84 w nobody perl5.8.6 60138 19 /usr 6406445 -rw-r--r-- 177196 w nobody perl5.8.6 60138 20 /usr 6406367 -rw-r--r-- 273155 w nobody perl5.8.6 60138 21 /usr 6406346 -rw-r--r-- 68 w nobody perl5.8.6 60138 22 /usr 6406340 -rw-r--r-- 219769 w nobody perl5.8.6 60138 23 /usr 6406152 -rw-r--r-- 61985 w nobody perl5.8.6 60138 24 /usr 6406295 -rw-r--r-- 98621 w nobody perl5.8.6 60138 25 /usr 6406287 -rw-r--r-- 2558162 w nobody perl5.8.6 60138 26 /usr 6406284 -rw-r--r-- 32168 w nobody perl5.8.6 60138 27 /usr 6406292 -rw-r--r-- 265964 w nobody perl5.8.6 60138 28 /usr 6406213 -rw-r--r-- 1607 w nobody perl5.8.6 60138 29 /usr 6407351 -rw-r--r-- 347197 w nobody perl5.8.6 60138 30 /usr 6407377 -rw-r--r-- 140832 w nobody perl5.8.6 60138 31 /usr 6407290 -rw-r--r-- 935975 w nobody perl5.8.6 60138 32 /usr 6406393 -rw-r--r-- 5634 w nobody perl5.8.6 60138 33 /usr 6407328 -rw-r--r-- 51239 w nobody perl5.8.6 60138 34 /usr 6406252 -rw-r--r-- 12198 w nobody perl5.8.6 60138 35 /usr 6407325 -rw-r--r-- 13538 w nobody perl5.8.6 60138 36 /usr 6407319 -rw-r--r-- 23151 w nobody perl5.8.6 60138 37 /usr 6407322 -rw-r--r-- 16184 w nobody perl5.8.6 60138 38 /usr 6407341 -rw-r--r-- 146759 w nobody perl5.8.6 60138 39 /usr 6407329 -rw-r--r-- 36336 w nobody perl5.8.6 60138 40 /usr 6406423 -rw-r--r-- 43747 w nobody perl5.8.6 60138 41 /usr 6407330 -rw-r--r-- 95287 w nobody perl5.8.6 60138 42 /usr 6406425 -rw-r--r-- 28586 w nobody perl5.8.6 60138 43 /usr 6406223 -rw-r--r-- 210 w nobody perl5.8.6 60138 44 /usr 6407166 -rw-r--r-- 613177 w nobody perl5.8.6 60138 45 /usr 6406160 -rw-r--r-- 0 w nobody perl5.8.6 60138 46 /usr 6406166 -rw-r--r-- 123158 w nobody perl5.8.6 60138 47 /usr 6407974 -rw-r--r-- 272 w nobody perl5.8.6 60138 48 /usr 6407952 -rw-r--r-- 196 w nobody perl5.8.6 60138 49 /usr 6407915 -rw-r--r-- 49313 w nobody perl5.8.6 60138 50 /usr 6407942 -rw-r--r-- 170924 w nobody perl5.8.6 60138 51 /usr 6407933 -rw-r--r-- 1496129 w nobody perl5.8.6 60138 52 /usr 6407931 -rw-r--r-- 202140 w nobody perl5.8.6 60138 53 /usr 6407924 -rw-r--r-- 342351 w nobody perl5.8.6 60138 54 /usr 6407913 -rw-r--r-- 23547 w nobody perl5.8.6 60138 55 /usr 6407288 -rw-r--r-- 18729 w nobody perl5.8.6 60138 56 /usr 6407289 -rw-r--r-- 377903 w nobody perl5.8.6 60138 57 /usr 6407166 -rw-r--r-- 613177 w nobody perl5.8.6 60138 58 /usr 6407175 -rw-r--r-- 4526 w nobody perl5.8.6 60138 59 /usr 6407171 -rw-r--r-- 373516 w nobody perl5.8.6 60138 60 /usr 6407181 -rw-r--r-- 49888 w nobody perl5.8.6 60138 61 /usr 6407164 -rw-r--r-- 847357 w nobody perl5.8.6 60138 62 /var 8310 -rw-r--r-- 147300 w nobody perl5.8.6 60138 63 /usr 6406441 -rw------- 0 w nobody perl5.8.6 60138 109 /usr 6406441 -rw------- 0 w amd64# then i kill -9 60138 process, its restart with other number - 86717, and i rebooted for kill him. amd64# lsof -i -n | grep 86717 perl5.8.6 86717 nobody 3u IPv4 0xffffff004b465000 0t0 TCP my_ip:53650->161.53.178.240:9999 (ESTABLISHED) perl5.8.6 86717 nobody 4u IPv4 0t0 TCP no PCB, CANTSENDMORE, CANTRCVMORE amd64# How can i found hole on my server? -- Regards, Oleg mailto:freebsd-amd64@molecon.ru From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 11:01:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0196816A426 for ; Mon, 27 Jun 2005 11:01:45 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC3AA43D53 for ; Mon, 27 Jun 2005 11:01:45 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5RB1jmj042981 for ; Mon, 27 Jun 2005 11:01:45 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5RB1iWc042976 for freebsd-amd64@freebsd.org; Mon, 27 Jun 2005 11:01:44 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Jun 2005 11:01:44 GMT Message-Id: <200506271101.j5RB1iWc042976@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2005 11:01:46 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. p [2005/05/19] amd64/81279 amd64 /usr/games/random returns every line o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b f [2005/06/12] amd64/82176 amd64 ehci causes crash on amd64 o [2005/06/19] amd64/82425 amd64 fxp0: device timeout, fxp interface dies 33 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/13] ports/75015 amd64 cvsup on amd64 with runsocks (socks5) cor o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 FreeBSD 5.4 released version can not use o [2005/06/12] amd64/82178 amd64 missing 32bit subsystem o [2005/06/18] amd64/82380 amd64 buildworld error in libc o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/06/24] amd64/82599 amd64 ports/misc/mtx wont compile on amd64 14 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 14:37:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC94016A41C for ; Mon, 27 Jun 2005 14:37:10 +0000 (GMT) (envelope-from dystopianrebel@yahoo.com) Received: from web52306.mail.yahoo.com (web52306.mail.yahoo.com [206.190.39.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C99143D1D for ; Mon, 27 Jun 2005 14:37:10 +0000 (GMT) (envelope-from dystopianrebel@yahoo.com) Received: (qmail 49021 invoked by uid 60001); 27 Jun 2005 14:37:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=C+idEu3BmHTK3K8W4DxgfsfZab6JmhX7qtSACnoUGpY3MlYS+1UNqJ6FiT0K4IFPLTk9YxwtdwBR1pcegXTo33ssHE3jI7YC1LwU2IL0U/8H9tTOIiUWsCsgovct7xJif2YewetPNVSbW021+XGUPYMa9mx+ONyYY31QU+lvyzs= ; Message-ID: <20050627143709.49019.qmail@web52306.mail.yahoo.com> Received: from [205.210.232.62] by web52306.mail.yahoo.com via HTTP; Mon, 27 Jun 2005 07:37:09 PDT Date: Mon, 27 Jun 2005 07:37:09 -0700 (PDT) From: dR To: freebsd-amd64@freebsd.org, freebsd-amd64@molecon.ru In-Reply-To: <20050627120006.5A15116A429@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: freebsd-amd64 Digest, Vol 108, Issue 1 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, 27 Jun 2005 14:37:10 -0000 Oleg, stop your Web server, check with the owner of your PHP bulletin-board source for a security update, and apply the patches immediately. Make sure that you use a robots.txt file to protect your site from Google and Yahoo indexing. The script kiddies are using search engines to find vulnerable PHP bulletin-board installations. As for identifying the culprit, I wish you success but I don't know if you will have any. Marko - - - Date: Mon, 27 Jun 2005 14:10:14 +0400 From: Oleg Rusanov Subject: "sh -i" My server was hacked. How can i found hole on my server? To: freebsd-amd64 Message-ID: <1525910592.20050627141014@molecon.ru> Content-Type: text/plain; charset=us-ascii Hello. My server was hacked. The CPU has been loaded on 99 % by "sh -i" process. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 17:32:15 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF93B16A41C; Mon, 27 Jun 2005 17:32:15 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (mail.wmptl.com [216.8.159.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7772543D1D; Mon, 27 Jun 2005 17:32:14 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from r3140ca ([10.0.0.104]) by wmptl.net (8.13.1/8.12.9) with ESMTP id j5RHWB3Q013088; Mon, 27 Jun 2005 13:32:12 -0400 (EDT) From: "Nathan Vidican" To: Date: Mon, 27 Jun 2005 13:32:04 -0400 Message-ID: <002201c57b3e$23548e60$6800000a@r3140ca> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Linux emulation on amd64, possible yet? ... plausible? 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, 27 Jun 2005 17:32:16 -0000 MSG In-short: what is, or where do I find info on, the current status of linux binary compatability on FreeBSD/amd64 platform MSG In-Long(er) Detailed format: ... Hey all - been searching the FAQ, and the release notes trying to find some diffinitive answer as to where linux binary compatability stands at in regards to the FreeBSD/amd64 platform... can't seem to find one, the only thing the release notes state (and 5.3R we're talking here), is that there is limited linux_32 compatability available. I'm (still) running FreeBSD/amd64 5.3R on a couple of dual-opteron boxen. What I'm eventually hoping to accomplish, is to get Sun JDK, Oracle Database (preferably 10g... but who knows), and possibly Sun One Studio to work. I can download all the above mentioned installs, and can even get partway through running some of them... The binaries always seem to fail with error 'ELF binary type "0" not known.' - which is to be expected seeing as how I've not enabled any sort of binary emulation. If going to 5.4R is the only option - I'm open to trying it, but prefer to do so on my laptop - and last known there were still issues with the keyboard probe/chipset of the Compaq 300-series amd64 platform, if anyone knows the status of that fix it'd be great to know too (of course assuming I've got the option of better linux emulation with 5.4R). Ideally, I'd like to be able to run the linux/amd64 binaries... But I really don't know where FreeBSD stands at current for doing this, or if it will even be possible, or if linux/32 is still in development stages... Can anyone provide me with a more authoratative response, either in form of status or in form of url/mailing list towards who is working on this stuff? Much appreciated all, and sorry if posting this to the general list was not the proper place - was unsure of where to ask. Thanks to all who reply. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 18:26:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A5B16A426 for ; Mon, 27 Jun 2005 18:26:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FA0243D1F for ; Mon, 27 Jun 2005 18:26:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.231] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 27 Jun 2005 14:39:53 -0400 From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 27 Jun 2005 13:34:30 -0400 User-Agent: KMail/1.8 References: <20050626053247.GA923@faust.net> In-Reply-To: <20050626053247.GA923@faust.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506271334.31516.jhb@FreeBSD.org> Cc: Zoran Kolic Subject: Re: cpufreq enabling 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, 27 Jun 2005 18:26:20 -0000 On Sunday 26 June 2005 01:32 am, Zoran Kolic wrote: > Hi all! > I've tried to include "cpufreq" > into kernel and building just > failed. There is no device like > this. What is the way to do > something like that on 5.4 release? > Or just ready for current? > Best regards 5.4 only has the infrastructure, it doesn't have any of the actual drivers. 6.0 should have full support, though I don't know if it works ok on FreeBSD/amd64. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 18:26:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86ECF16A45C for ; Mon, 27 Jun 2005 18:26:27 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4010B43D1F for ; Mon, 27 Jun 2005 18:26:27 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.231] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 27 Jun 2005 14:39:53 -0400 From: John Baldwin To: freebsd-amd64@freebsd.org, amd64@cybernetwork.org Date: Mon, 27 Jun 2005 13:33:38 -0400 User-Agent: KMail/1.8 References: <1642.192.168.1.25.1119646769.squirrel@192.168.1.25> In-Reply-To: <1642.192.168.1.25.1119646769.squirrel@192.168.1.25> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506271333.38774.jhb@FreeBSD.org> Cc: Subject: Re: Dell 6850 Dual Intel 64-bit Xeon MP and no SMP 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, 27 Jun 2005 18:26:27 -0000 On Friday 24 June 2005 04:59 pm, SectorONE wrote: > I need some help here. > I=92ve been running FreeBSD for some years now and only i386 platform. Th= is > time I=92ve bought some new Dell PowerEdge servers and need the possibili= ty > to address more than 4GB of ram and use some 64-bit stuff. > > One of them is a Dell PowerEdge 6850 with dual Intel 64-bit Xeon MP > prosessors. > After installing FreeBSD/amd64 5.4-RELEASE, I cvsuped for stable and now > got 5.4-RELEASE-p2. I then added SMP support in my kernel and compiled > world, compiled kernel installed kernel and installed world.(and of course > some mergemaster in between) > > When I reboot the machine the dmesg gives me the following disturbing inf= o: > > --- quote on --- > > SMP: CPU 8 exceeds maximum CPU 7, ignoring > SMP: CPU 14 exceeds maximum CPU 7, ignoring > SMP: CPU 9 exceeds maximum CPU 7, ignoring > SMP: CPU 15 exceeds maximum CPU 7, ignoring Looks like MAXCPU is set to 8 somehow. It should be at least 16. Oh, it's= =20 not. :-P Try this change: Index: amd64/include/param.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/sys/amd64/include/param.h,v retrieving revision 1.17 diff -u -r1.17 param.h =2D-- amd64/include/param.h 21 Jan 2005 05:56:41 -0000 1.17 +++ amd64/include/param.h 27 Jun 2005 17:33:20 -0000 @@ -84,7 +84,7 @@ #endif #ifdef SMP =2D#define MAXCPU 8 +#define MAXCPU 16 #else #define MAXCPU 1 #endif =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 19:06:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1D6216A41C for ; Mon, 27 Jun 2005 19:06:42 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from falcon.loomes.de (smtp.loomes.de [212.40.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8683143D49 for ; Mon, 27 Jun 2005 19:06:42 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from port-212-202-35-78.dynamic.qsc.de ([212.202.35.78] helo=bsd.trippelsdorf.de) by falcon.loomes.de with asmtp (Exim 4.30) id 1DmywK-0006ld-FC; Mon, 27 Jun 2005 21:06:40 +0200 Date: Mon, 27 Jun 2005 21:06:38 +0200 From: Markus Trippelsdorf To: Zoran Kolic Message-ID: <20050627190638.GA1470@bsd.trippelsdorf.de> References: <20050626053247.GA923@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050626053247.GA923@faust.net> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: cpufreq enabling 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, 27 Jun 2005 19:06:42 -0000 On Sun, Jun 26, 2005 at 07:32:47AM +0200, Zoran Kolic wrote: > I've tried to include "cpufreq" > into kernel and building just > failed. There is no device like > this. What is the way to do > something like that on 5.4 release? I've been using the acpi_ppc kernel module from Fukuda-san for five months now without any problems. It works with Current and 5.4.. Here is the link: http://www.spa.is.uec.ac.jp/~nfukuda/software/index.html -- Markus From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 20:58:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA3EE16A41C for ; Mon, 27 Jun 2005 20:58:42 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp105.rog.mail.re2.yahoo.com (smtp105.rog.mail.re2.yahoo.com [206.190.36.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 5A11943D4C for ; Mon, 27 Jun 2005 20:58:42 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 62554 invoked from network); 27 Jun 2005 20:58:41 -0000 Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp105.rog.mail.re2.yahoo.com with SMTP; 27 Jun 2005 20:58:41 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by 172.16.0.1 with HTTP; Mon, 27 Jun 2005 16:58:40 -0400 (EDT) Message-ID: <1952.172.16.0.199.1119905920.squirrel@172.16.0.1> In-Reply-To: <1525910592.20050627141014@molecon.ru> References: <1525910592.20050627141014@molecon.ru> Date: Mon, 27 Jun 2005 16:58:40 -0400 (EDT) From: "Mike Jakubik" To: "Oleg Rusanov" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: 'sh -i' My server was hacked. How can i found hole on my 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, 27 Jun 2005 20:58:42 -0000 On Mon, June 27, 2005 6:10 am, Oleg Rusanov said: > Hello. > > > My server was hacked. The CPU has been loaded on 99 % by "sh -i" process. > I found out that someone has started phpshell through a hole in one of > phpbb forums. Also has filled in scripts for flud and spam and "vadim > script" in "/tmp". I has made it noexec. Recently has found out the same > process. May be i have left again /tmp opened, or other hole may be. > What is better to do for clean my system? And what does this have to do with the amd64 mailing list? Try questions instead. From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 27 22:21:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9790A16A41C for ; Mon, 27 Jun 2005 22:21:56 +0000 (GMT) (envelope-from amd64@cybernetwork.org) Received: from webserver.glupus.net (186.80-203-151.nextgentel.com [80.203.151.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id E811943D48 for ; Mon, 27 Jun 2005 22:21:55 +0000 (GMT) (envelope-from amd64@cybernetwork.org) Received: from webmail.glupus.net (stitch [10.0.1.2]) by webserver.glupus.net (8.13.1/8.13.1) with ESMTP id j5RMLts0084661 for ; Tue, 28 Jun 2005 00:21:55 +0200 (CEST) (envelope-from amd64@cybernetwork.org) Received: from 192.168.1.25 (SquirrelMail authenticated user glupus); by webmail.glupus.net with HTTP; Tue, 28 Jun 2005 00:21:57 +0200 (CEST) Message-ID: <4979.192.168.1.25.1119910917.squirrel@192.168.1.25> In-Reply-To: <200506271333.38774.jhb@FreeBSD.org> References: <1642.192.168.1.25.1119646769.squirrel@192.168.1.25> <200506271333.38774.jhb@FreeBSD.org> Date: Tue, 28 Jun 2005 00:21:57 +0200 (CEST) From: "SectorONE" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Dell 6850 Dual Intel 64-bit Xeon MP and no SMP X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: amd64@cybernetwork.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2005 22:21:56 -0000 > On Friday 24 June 2005 04:59 pm, SectorONE wrote: >> I need some help here. >> I’ve been running FreeBSD for some years now and only i386 platform. >> This >> time I’ve bought some new Dell PowerEdge servers and need the >> possibility >> to address more than 4GB of ram and use some 64-bit stuff. >> >> One of them is a Dell PowerEdge 6850 with dual Intel 64-bit Xeon MP >> prosessors. >> After installing FreeBSD/amd64 5.4-RELEASE, I cvsuped for stable and now >> got 5.4-RELEASE-p2. I then added SMP support in my kernel and compiled >> world, compiled kernel installed kernel and installed world.(and of >> course >> some mergemaster in between) >> >> When I reboot the machine the dmesg gives me the following disturbing >> info: >> >> --- quote on --- >> >> SMP: CPU 8 exceeds maximum CPU 7, ignoring >> SMP: CPU 14 exceeds maximum CPU 7, ignoring >> SMP: CPU 9 exceeds maximum CPU 7, ignoring >> SMP: CPU 15 exceeds maximum CPU 7, ignoring > > Looks like MAXCPU is set to 8 somehow. It should be at least 16. Oh, > it's > not. :-P Try this change: > > Index: amd64/include/param.h > =================================================================== > RCS file: /usr/cvs/src/sys/amd64/include/param.h,v > retrieving revision 1.17 > diff -u -r1.17 param.h > --- amd64/include/param.h 21 Jan 2005 05:56:41 -0000 1.17 > +++ amd64/include/param.h 27 Jun 2005 17:33:20 -0000 > @@ -84,7 +84,7 @@ > #endif > > #ifdef SMP > -#define MAXCPU 8 > +#define MAXCPU 16 > #else > #define MAXCPU 1 > #endif > > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > > *blushing* I tried many times in many different ways to change sysctl: kern.smp.maxcpus from 8 -> 16. Including in /boot/loader.conf. But with no luck.. You are my hero.. tnx a lot.. That helped :D All my CPUs are now in action. Of course I had to change sysctl: machdep.hyperthreading_allowed: 0 -> 1 But that’s another story. Thanks again.. :D From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 28 12:20:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60C616A455; Tue, 28 Jun 2005 12:20:37 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8346743D49; Tue, 28 Jun 2005 12:20:37 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1DnF4t-0007mW-00; Tue, 28 Jun 2005 14:20:35 +0200 Date: Tue, 28 Jun 2005 14:20:35 +0200 To: freebsd-amd64@freebsd.org, Zoran Kolic Message-ID: <20050628122035.GO8899@poupinou.org> References: <20050626053247.GA923@faust.net> <200506271334.31516.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506271334.31516.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot Cc: John Baldwin Subject: Re: cpufreq enabling 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, 28 Jun 2005 12:20:39 -0000 On Mon, Jun 27, 2005 at 01:34:30PM -0400, John Baldwin wrote: > On Sunday 26 June 2005 01:32 am, Zoran Kolic wrote: > > Hi all! > > I've tried to include "cpufreq" > > into kernel and building just > > failed. There is no device like > > this. What is the way to do > > something like that on 5.4 release? > > Or just ready for current? > > Best regards > > 5.4 only has the infrastructure, it doesn't have any of the actual drivers. > 6.0 should have full support, though I don't know if it works ok on > FreeBSD/amd64. > The OP can try http://www.poupinou.org/cpufreq/bsd/cpufreq-mfc.20050608.diff.gz It work on FreeBSD/amd64 -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 28 12:37:45 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.ORG Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C0CD16A41C for ; Tue, 28 Jun 2005 12:37:45 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 968E343D58 for ; Tue, 28 Jun 2005 12:37:44 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qfmhmd@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j5SCbeD1018972; Tue, 28 Jun 2005 14:37:40 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j5SCbdto018971; Tue, 28 Jun 2005 14:37:39 +0200 (CEST) (envelope-from olli) Date: Tue, 28 Jun 2005 14:37:39 +0200 (CEST) Message-Id: <200506281237.j5SCbdto018971@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, Oleg Rusanov In-Reply-To: <1525910592.20050627141014@molecon.ru> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: "sh -i" My server was hacked. How can i found hole on my 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: Tue, 28 Jun 2005 12:37:45 -0000 Oleg Rusanov wrote: > My server was hacked. The CPU has been loaded on 99 % by "sh -i" process. > I found out that someone has started phpshell through a hole in one of phpbb fo > rums. > Also has filled in scripts for flud and spam and "vadim script" in > "/tmp". I has made it noexec. Recently has found out the same process. > May be i have left again /tmp opened, or other hole may be. > What is better to do for clean my system? If a machine has been hacked, the _only_ way to make sure that all holes and backdoors are gone is to newfs and re- install from CD-ROM or other know-to-be-clean media. Better yet, remove the harddisk and keep it for further forensic examinations. Install a new harddisk. After that, be sure to install the latest version of phpbb, which has the problem fixed. Run it inside a jail only. When restoring your backup, only restore user data, no executables. Keep your base system and ports up-to-date. Install portaudit. Subscribe to security mailing lists. There's much more to say, but the above is probably the most important. Best regards Oliver PS: When replying, please do so privately. This issue is not on-topic on the freebsd-amd64 list. -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 08:18:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B182216A41C for ; Wed, 29 Jun 2005 08:18:17 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (J9b3e.j.pppool.de [85.74.155.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14F4743D1F for ; Wed, 29 Jun 2005 08:18:16 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j5T8IELL002348 for ; Wed, 29 Jun 2005 10:18:15 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200506290818.j5T8IELL002348@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: freebsd-amd64@freebsd.org From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jun 2005 10:18:14 +0200 Sender: garyj@jennejohn.org Subject: AMD64 X2 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, 29 Jun 2005 08:18:17 -0000 Has anyone tried using a dual-core AMD65 X2 in an ASUS AV8 Deluxe mobo? For that matter, has anyone on this list tried out an X2 at all? -------- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 10:00:40 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C48216A41C for ; Wed, 29 Jun 2005 10:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D9F543D1F for ; Wed, 29 Jun 2005 10:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5TA0diY005899 for ; Wed, 29 Jun 2005 10:00:39 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5TA0dId005898; Wed, 29 Jun 2005 10:00:39 GMT (envelope-from gnats) Date: Wed, 29 Jun 2005 10:00:39 GMT Message-Id: <200506291000.j5TA0dId005898@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: amd64/82555: Kernel Panic - after i connect to my "amd64" from another network bsd box [ssh session]. "nve0" don't work corectly, system hang up, or message and then hang up X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 10:00:40 -0000 The following reply was made to PR amd64/82555; it has been noted by GNATS. From: Kris Kennaway To: Dmitry Selin Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/82555: Kernel Panic - after i connect to my "amd64" from another network bsd box [ssh session]. "nve0" don't work corectly, system hang up, or message and then hang up Date: Wed, 29 Jun 2005 05:50:52 -0400 --XF85m9dhOBO43t/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 23, 2005 at 01:26:08AM +0000, Dmitry Selin wrote: >=20 > >Number: 82555 > >Category: amd64 > >Synopsis: Kernel Panic - after i connect to my "amd64" from anothe= r network bsd box [ssh session]. "nve0" don't work corectly, system hang up= , or message and then hang up > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-amd64 > >State: open > >Quarter: =20 > >Keywords: =20 > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Jun 23 01:30:18 GMT 2005 > >Closed-Date: > >Last-Modified: > >Originator: Dmitry Selin > >Release: 6-CURRENT (Jun 2005) > >Organization: > Khabarovsk Oil Refinery > >Environment: > # uname -a > FreeBSD prg_1.zup.local 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Mon Jun 20 10= :41:32 > UTC 2005 selin@prg_test.zup.local:/usr/obj/usr/src/sys/K2K amd64 [...] Please see the Developers' Handbook chapter on Kernel Debugging for how to obtain the minimal information needed to proceed further with this bug (i.e. crashdump with gdb traceback). KRis --XF85m9dhOBO43t/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwm77Wry0BWjoQKURApLEAJ9QusxQG4ukBiaW985xZgDlOCKvfwCdGCuD fDZqWkBI6XGkeQO1b9M1ERs= =CLiy -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 10:58:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0596416A41C for ; Wed, 29 Jun 2005 10:58:35 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id B41C943D1D for ; Wed, 29 Jun 2005 10:58:33 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 7219684428 for ; Wed, 29 Jun 2005 12:58:32 +0200 (CEST) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 70439-03-2 for ; Wed, 29 Jun 2005 12:58:27 +0200 (CEST) Received: from [172.16.129.72] (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTP id 4DA4584425 for ; Wed, 29 Jun 2005 12:58:27 +0200 (CEST) Message-ID: <42C27ED3.80103@fsn.hu> Date: Wed, 29 Jun 2005 12:58:27 +0200 From: Attila Nagy User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050628) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> In-Reply-To: <200506290818.j5T8IELL002348@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: Re: AMD64 X2 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, 29 Jun 2005 10:58:35 -0000 Gary Jennejohn wrote: > Has anyone tried using a dual-core AMD65 X2 in an ASUS AV8 Deluxe > mobo? For that matter, has anyone on this list tried out an X2 at > all? Don't know about the ASUS motherboard, but the HP BL45p works with dual core processors: http://www.freebsd.org/platforms/amd64/motherboards.html -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Adopt a directory on our free software phone @work: +361 371 3536 server! http://www.fsn.hu/?f=brick cell.: +3630 306 6758 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 12:15:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EAC516A41C for ; Wed, 29 Jun 2005 12:15:56 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E092543D1F for ; Wed, 29 Jun 2005 12:15:55 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so1994913rna for ; Wed, 29 Jun 2005 05:15:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QH1bd5j03B5sCU87nfRJ8ksa/UNDuPPzvFPzV1Mc+tXO8cQO8JVehqfEGLsQihamCU0vhKefTZMh/gVz9tkS173pp+JLaWmORiCnl1cO/W0YbpCBBtYK52e6b5tYMb5P+mgkWx5VzDMaNSuwsHJasSg+tln68eJdfp7+r6RrmWM= Received: by 10.38.67.2 with SMTP id p2mr2413656rna; Wed, 29 Jun 2005 05:15:55 -0700 (PDT) Received: by 10.38.12.17 with HTTP; Wed, 29 Jun 2005 05:15:55 -0700 (PDT) Message-ID: <1d6d20bc05062905156d427484@mail.gmail.com> Date: Wed, 29 Jun 2005 20:15:55 +0800 From: Jia-Shiun Li To: Gary Jennejohn In-Reply-To: <200506290818.j5T8IELL002348@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 X2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jia-Shiun Li List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 12:15:56 -0000 I suppose you meant A8V Deluxe. Asus have Athlon64 X2 on their list of supported CPUs, all you need is to update BIOS: http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=3Den-us&model= =3DA8V%20Deluxe All Socket 939 boards should be able to use X2 after updating BIOS. Jia-Shiun. On 6/29/05, Gary Jennejohn wrote: > Has anyone tried using a dual-core AMD65 X2 in an ASUS AV8 Deluxe > mobo? For that matter, has anyone on this list tried out an X2 at > all? >=20 > -------- > Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTd= e >=20 > _______________________________________________ > 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 Wed Jun 29 13:11:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70AA716A41C for ; Wed, 29 Jun 2005 13:11:57 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Jb487.j.pppool.de [85.74.180.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id D89BF43D58 for ; Wed, 29 Jun 2005 13:11:56 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j5TDBsGX003783; Wed, 29 Jun 2005 15:11:54 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200506291311.j5TDBsGX003783@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Jia-Shiun Li In-Reply-To: Message from Jia-Shiun Li of "Wed, 29 Jun 2005 20:15:55 +0800." <1d6d20bc05062905156d427484@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jun 2005 15:11:54 +0200 From: Gary Jennejohn Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 X2 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, 29 Jun 2005 13:11:57 -0000 Jia-Shiun Li writes: > I suppose you meant A8V Deluxe. Asus have Athlon64 X2 on their list of > supported CPUs, all you need is to update BIOS: > Thanks for responding. Yes, I did mean A8V Deluxe. > http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us&model=A8V%20Deluxe > > All Socket 939 boards should be able to use X2 after updating BIOS. > Should support and do support are horses of a different color. That's why I inquired on this ML. I don't really want to spend the bucks on an X2 only to find that it doesn't work, even though I'm using the latest BIOS (which I am). But, nothing risked nothing gained. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 15:20:46 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D828216A41F; Wed, 29 Jun 2005 15:20:46 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE73C43D48; Wed, 29 Jun 2005 15:20:46 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (jhb@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5TFKk5B059388; Wed, 29 Jun 2005 15:20:46 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5TFKkCG059384; Wed, 29 Jun 2005 15:20:46 GMT (envelope-from jhb) Date: Wed, 29 Jun 2005 15:20:46 GMT From: John Baldwin Message-Id: <200506291520.j5TFKkCG059384@freefall.freebsd.org> To: vivek@khera.org, jhb@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/81279: /usr/games/random returns every line 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, 29 Jun 2005 15:20:47 -0000 Synopsis: /usr/games/random returns every line State-Changed-From-To: patched->closed State-Changed-By: jhb State-Changed-When: Wed Jun 29 15:20:28 GMT 2005 State-Changed-Why: Fix committed to RELENG_5. http://www.freebsd.org/cgi/query-pr.cgi?pr=81279 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 18:59:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6EAE16A41F; Wed, 29 Jun 2005 18:59:22 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88C7C43D53; Wed, 29 Jun 2005 18:59:22 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 46B312A8DA; Wed, 29 Jun 2005 11:59:22 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id E0F48E2B3; Wed, 29 Jun 2005 11:59:21 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.4/8.13.1) with ESMTP id j5TIxLje079551; Wed, 29 Jun 2005 11:59:21 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.4/8.13.1/Submit) id j5TIxKN9079550; Wed, 29 Jun 2005 11:59:20 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 29 Jun 2005 11:59:20 -0700 User-Agent: KMail/1.8.1 References: <20050520033116.62902.qmail@web30704.mail.mud.yahoo.com> <20050524155924.GE31564@dragon.NUXI.org> In-Reply-To: <20050524155924.GE31564@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506291159.20846.peter@wemm.org> Cc: Subject: Re: device cpufreq 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, 29 Jun 2005 18:59:22 -0000 On Tuesday 24 May 2005 08:59 am, David O'Brien wrote: > On Thu, May 19, 2005 at 08:31:16PM -0700, Neil Short wrote: > > I updated to 6.0-CURRENT to test out the powernow > > drivers on my machine. It's a laptop and the processor > > is AMD Athlon-xpm. > > .. > > > carmen# dmesg > > ... > > CPU: AMD Athlon(tm) XP Processor 3000+ (1595.89-MHz > > 686-class CPU) > > Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 > > I'm surprised by this output - you have a K8 core CPU (754-pin rev. > C0). Your BIOS should say something other than "Athlon(tm) XP". What > laptop do you have? > > > Features=0x78bfbff >,PGE,MCA,CM OV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > AMD Features=0xc0500000 > > ... > > cpu0 on motherboard > > powernow0: on cpu0 > > This is correct. If you'll notice, he's got a '686-class' cpu and there is no LM (long mode) in the AMD Features flag. He's running FreeBSD/i386, not /amd64, on an Athlon-XP mobile, not an Athlon64. It might be a cut-down K8 core, but its not got 64 bit on it. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 21:53:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C280416A41C for ; Wed, 29 Jun 2005 21:53:30 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C58243D1D for ; Wed, 29 Jun 2005 21:53:30 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j5TLrUNh020952; Wed, 29 Jun 2005 14:53:30 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j5TLrTes020951; Wed, 29 Jun 2005 14:53:29 -0700 (PDT) (envelope-from obrien) Date: Wed, 29 Jun 2005 14:53:29 -0700 From: "David O'Brien" To: Peter Wemm Message-ID: <20050629215329.GA20836@dragon.NUXI.org> References: <20050520033116.62902.qmail@web30704.mail.mud.yahoo.com> <20050524155924.GE31564@dragon.NUXI.org> <200506291159.20846.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506291159.20846.peter@wemm.org> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: device cpufreq X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 21:53:30 -0000 On Wed, Jun 29, 2005 at 11:59:20AM -0700, Peter Wemm wrote: > On Tuesday 24 May 2005 08:59 am, David O'Brien wrote: > > On Thu, May 19, 2005 at 08:31:16PM -0700, Neil Short wrote: > > > I updated to 6.0-CURRENT to test out the powernow > > > drivers on my machine. It's a laptop and the processor > > > is AMD Athlon-xpm. > > > carmen# dmesg > > > ... > > > CPU: AMD Athlon(tm) XP Processor 3000+ (1595.89-MHz > > > 686-class CPU) > > > Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 > > > > I'm surprised by this output - you have a K8 core CPU (754-pin rev. > > C0). Your BIOS should say something other than "Athlon(tm) XP". What > > laptop do you have? > > > > > Features=0x78bfbff > >,PGE,MCA,CM OV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > > AMD Features=0xc0500000 > > > ... > > > cpu0 on motherboard > > > powernow0: on cpu0 > > > > This is correct. > > If you'll notice, he's got a '686-class' cpu and there is no LM (long > mode) in the AMD Features flag. He's running FreeBSD/i386, not /amd64, > on an Athlon-XP mobile, not an Athlon64. It might be a cut-down K8 > core, but its not got 64 bit on it. It most likely is a K8-based Sempron laptop, but AFAIK it should identify the CPU as such. That's why I wan't to know the model of laptop to check into this. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 21:59:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D85D416A438; Wed, 29 Jun 2005 21:59:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4A3543D53; Wed, 29 Jun 2005 21:59:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j5TLxKkk021170; Wed, 29 Jun 2005 14:59:20 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j5TLxJSt021157; Wed, 29 Jun 2005 14:59:19 -0700 (PDT) (envelope-from obrien) Date: Wed, 29 Jun 2005 14:59:19 -0700 From: "David O'Brien" To: Nathan Vidican Message-ID: <20050629215919.GB20836@dragon.NUXI.org> References: <002201c57b3e$23548e60$6800000a@r3140ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002201c57b3e$23548e60$6800000a@r3140ca> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Linux emulation on amd64, possible yet? ... plausible? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: questions@freebsd.org, freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 21:59:21 -0000 On Mon, Jun 27, 2005 at 01:32:04PM -0400, Nathan Vidican wrote: > MSG In-short: what is, or where do I find info on, the current status of > linux binary compatability on FreeBSD/amd64 platform 32-bit x86 Linux binaries should run just fine on FreeBSD/AMD64 5.4 or later. You will have to install the linux_base port. For FreeBSD 5.4 you need to install the 32-bit libs thru a 'make world'. Later versions will have them offered by Sysinstall. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 22:10:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56E6816A41C for ; Wed, 29 Jun 2005 22:10:48 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB1943D53 for ; Wed, 29 Jun 2005 22:10:48 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j5TMAlC4021545 for ; Wed, 29 Jun 2005 15:10:47 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j5TMAlaE021544 for freebsd-amd64@freebsd.org; Wed, 29 Jun 2005 15:10:47 -0700 (PDT) (envelope-from obrien) Date: Wed, 29 Jun 2005 15:10:47 -0700 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20050629221047.GC20836@dragon.NUXI.org> References: <42BC8310.9040501@cse.unl.edu> <20050626042355.GA41119@misty.eyesbeyond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050626042355.GA41119@misty.eyesbeyond.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Subject: sript (Perl) test code needed (was: How to build JDK15 on AMD64 with FreeBSD?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 22:10:48 -0000 On Sat, Jun 25, 2005 at 10:23:56PM -0600, Greg Lewis wrote: > and follow the instructions. There is one caveat on amd64 -- one of the > build commands will fail strangely (this is a bug in the Linux emulation > on amd64 as far as I can determine). I know this should be trivial to do in perl and maybe someone here has the time to hack it up. I want a small test script (actually some other scripting language than perl preferred). The script should run the following commands until an error is returned: ls ls . ls ./ ls ./. ls ././ ls ././. ls ./././ etc... and when the error occurs print out the length of the command line. I want to get the bottom of the "command too long" issue that causes too much trouble deploying Java on FreeBSD/AMD64. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 29 22:50:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E565516A41C for ; Wed, 29 Jun 2005 22:50:49 +0000 (GMT) (envelope-from griepent@wias-berlin.de) Received: from smtp1.wias-berlin.de (scan.wias-berlin.de [62.141.177.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3FF843D1D for ; Wed, 29 Jun 2005 22:50:48 +0000 (GMT) (envelope-from griepent@wias-berlin.de) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.wias-berlin.de (Postfix) with ESMTP id A532119C008 for ; Thu, 30 Jun 2005 00:50:47 +0200 (CEST) Received: from localhost (hilbert.wias-berlin.de [62.141.177.108]) by smtp1.wias-berlin.de (Postfix) with ESMTP id 2A64519C003 for ; Thu, 30 Jun 2005 00:50:46 +0200 (CEST) Date: Thu, 30 Jun 2005 00:50:44 +0200 (CEST) Message-Id: <20050630.005044.194102849.griepent@wias-berlin.de> To: freebsd-amd64@freebsd.org From: Jens Andre Griepentrog X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at wias-berlin.de Subject: Stable Opteron configurations with 16GB or more X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: griepent@wias-berlin.de List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 22:50:50 -0000 Dear FreeBSD AMD64 Community, I would like to get an Opteron compute server with a large amount of memory appropriate for three-dimensional numerical simulations. I have got some offer for a system with a Tyan S2882-D or S2892 board with two Opterons 248HE, U320 SCSI disks, and 16GB memory. But after tweaking out more information the same dealer concedes severe BIOS problems with the 90nm Opteron version connected to more than 2GB of memory! So one can feel a little bit irritated having in mind that all 248HE Opterons are manufactured in 90nm process ... It would be nice to hear from experienced BSD users which combinations of Opteron mainboards and processors work stable with 16GB or more of installed memory. Best regards, Jens A. Griepentrog PS: I would like to thank the whole BSD Community for their efforts maintaining that nice operating system which I have been using now for over ten years. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 00:41:50 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6755216A41C; Thu, 30 Jun 2005 00:41:50 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C56A43D55; Thu, 30 Jun 2005 00:41:50 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 093752A8F8; Wed, 29 Jun 2005 17:41:50 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id B254BE2B3; Wed, 29 Jun 2005 17:41:49 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.4/8.13.1) with ESMTP id j5U0fnkq089020; Wed, 29 Jun 2005 17:41:49 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.4/8.13.1/Submit) id j5U0fmWe089019; Wed, 29 Jun 2005 17:41:48 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: current@freebsd.org Date: Wed, 29 Jun 2005 17:41:48 -0700 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506291741.48817.peter@wemm.org> Cc: amd64@freebsd.org, i386@freebsd.org Subject: HEADS UP: crashdumps on -current! Format change for i386 and amd64! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 00:41:50 -0000 Crash dumps on -current for i386 and amd64 are now in ELF format, just like in IA64. There are several reasons for this, including being able to do crashdumps on machines with >4GB ram, or machines with 4GB of ram where some has been relocated above the 4GB mark due to the PCI hole. Anyway, there is a libkvm update that understands the new crash dump format. If you have a new dump, you'll need the updated libkvm. And likewise, old crash dumps will need the old libkvm. My advice is to stash a copy of the old libkvm somewhere safe if you want to be able to examine old crash dumps. gdb6 doesn't care either way, the changes are entirely in libkvm. You should be able to use your saved libkvm by the use of $LD_PRELOAD or $LD_LIBRARY_PATH with an otherwise unmodified gdb6. Building an old libkvm by using a cvs update -D'20050628' and a quick compile is also fairly painless. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 10:06:42 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.ORG Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0707016A41C; Thu, 30 Jun 2005 10:06:42 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57CEC43D58; Thu, 30 Jun 2005 10:06:41 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wtcfqp@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j5UA6auq017309; Thu, 30 Jun 2005 12:06:36 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j5UA6ZV9017308; Thu, 30 Jun 2005 12:06:35 +0200 (CEST) (envelope-from olli) Date: Thu, 30 Jun 2005 12:06:35 +0200 (CEST) Message-Id: <200506301006.j5UA6ZV9017308@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG, obrien@FreeBSD.ORG In-Reply-To: <20050629221047.GC20836@dragon.NUXI.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: sript (Perl) test code needed X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG, obrien@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 10:06:42 -0000 David O'Brien wrote: > I know this should be trivial to do in perl and maybe someone here has the > time to hack it up. I want a small test script (actually some other > scripting language than perl preferred). > > The script should run the following commands until an error is returned: > > ls > ls . > ls ./ > ls ./. > ls ././ > ls ././. > ls ./././ > etc... > > and when the error occurs print out the length of the command line. > I want to get the bottom of the "command too long" issue that causes too > much trouble deploying Java on FreeBSD/AMD64. This is pretty easy to do in plain /bin/sh. CMD="ls " while $CMD >/dev/null; do case "$CMD" in *.) CMD="$CMD/";; *) CMD="$CMD.";; esac done echo "length == ${#CMD}" On my old 4-stable/i386 machine, it reports "File name too long" when the length of the command reaches 1027 chars (i.e. the path is 1024 chars, which is PATH_MAX). When replacing "/" with " ", so that the commands become "ls . . . . " etc., it runs a lot longer, until finally it reports "argument list too long" when the command length reaches 61344 chars. Since my environment is 2079 chars, and the " >/dev/null" is another 12 bytes, that adds up to 65532 bytes. ARG_MAX is 65536. Don't ask me where the remaining 4 chars go. Maybe some safety margins in the implementation, or alignment issues. Best regards Oliver PS: I couldn't help writing the same in Python, too. :-) It reports the same result, of course. import os cmd = "ls " while os.system(cmd + " >/dev/null") == 0: cmd = cmd + "/."[len(cmd) % 2] print "length ==", len(cmd) And in awk ... BEGIN { cmd = "ls " while (system(cmd " >/dev/null") == 0) cmd = cmd substr("/.", length(cmd) % 2 + 1, 1) print "length ==", length(cmd) } -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. (On the statement print "42 monkeys" + "1 snake":) By the way, both perl and Python get this wrong. Perl gives 43 and Python gives "42 monkeys1 snake", when the answer is clearly "41 monkeys and 1 fat snake". -- Jim Fulton From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 10:14:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B0BF16A41C for ; Thu, 30 Jun 2005 10:14:08 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C94A443D53 for ; Thu, 30 Jun 2005 10:14:07 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.12.10/5.2) with ESMTP id j5UADwtn013067 for ; Thu, 30 Jun 2005 12:14:03 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Thu, 30 Jun 2005 12:13:58 +0200 User-Agent: KMail/1.8.50 References: <42BC8310.9040501@cse.unl.edu> <20050626042355.GA41119@misty.eyesbeyond.com> <20050629221047.GC20836@dragon.NUXI.org> In-Reply-To: <20050629221047.GC20836@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506301213.58569.groot@kde.org> X-Spam-Score: -0.464 () BAYES_20,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Subject: Re: sript (Perl) test code needed (was: How to build JDK15 on AMD64 with FreeBSD?) 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, 30 Jun 2005 10:14:08 -0000 On Thursday 30 June 2005 00:10, David O'Brien wrote: > On Sat, Jun 25, 2005 at 10:23:56PM -0600, Greg Lewis wrote: > > and follow the instructions. There is one caveat on amd64 -- one of the > > build commands will fail strangely (this is a bug in the Linux emulation > > on amd64 as far as I can determine). > > I know this should be trivial to do in perl and maybe someone here has the > time to hack it up. I want a small test script (actually some other > scripting language than perl preferred). > The script should run the following commands until an error is returned: > and when the error occurs print out the length of the command line. > I want to get the bottom of the "command too long" issue that causes too > much trouble deploying Java on FreeBSD/AMD64. Well, in the setup you posit here, you run into the maximum file-name length of 1024 well before you run into the length of the maximum command-line (kern.argmax). The following quick test tests the maximum command-line (it's a lot like the autoconf test for maximum command-line length); #! /usr/bin/env perl @what = ( "././././././././" ); while ( 0 == system( "ls",@what) ) { push(@what , @what); print STDERR "Length " . (@what + 0) . "\n"; } It stops after printing Length 4096, so 2+4096*16 bytes of command-line is too much (and indeed, my kern.argmax is 65536) (hm, does a NUL terminating byte count towards argmax?). Doing something more subtle finishes at Length 3776 (* 16 bytes, possibly 17 -- in any case less that 65536). -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 10:29:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34D8416A41C; Thu, 30 Jun 2005 10:29:29 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2BF43D1F; Thu, 30 Jun 2005 10:29:28 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 715A11F87BEE; Thu, 30 Jun 2005 12:29:24 +0200 (CEST) Date: Thu, 30 Jun 2005 12:29:24 +0200 From: Roman Neuhauser To: David O'Brien Message-ID: <20050630102924.GA71895@isis.sigpipe.cz> References: <42BC8310.9040501@cse.unl.edu> <20050626042355.GA41119@misty.eyesbeyond.com> <20050629221047.GC20836@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050629221047.GC20836@dragon.NUXI.org> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: sript (Perl) test code needed (was: How to build JDK15 on AMD64 with FreeBSD?) 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, 30 Jun 2005 10:29:29 -0000 # obrien@freebsd.org / 2005-06-29 15:10:47 -0700: > On Sat, Jun 25, 2005 at 10:23:56PM -0600, Greg Lewis wrote: > > and follow the instructions. There is one caveat on amd64 -- one of the > > build commands will fail strangely (this is a bug in the Linux emulation > > on amd64 as far as I can determine). > > I know this should be trivial to do in perl and maybe someone here has the > time to hack it up. I want a small test script (actually some other > scripting language than perl preferred). > > The script should run the following commands until an error is returned: > > ls > ls . > ls ./ > ls ./. > ls ././ > ls ././. > ls ./././ > etc... > > and when the error occurs print out the length of the command line. > I want to get the bottom of the "command too long" issue that causes too > much trouble deploying Java on FreeBSD/AMD64. This prints the length of the argument (add 3 for "ls "), works in zsh: setopt ksh_arrays p=; i=0; c=(. /); while ls $p; do p=$p${c[i++ % 2]}; done >/dev/null 2>&1; echo $i ${#p} -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 12:05:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFCA816A41C for ; Thu, 30 Jun 2005 12:05:54 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id A498A43D4C for ; Thu, 30 Jun 2005 12:05:54 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so79483wra for ; Thu, 30 Jun 2005 05:05:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TEI6MYwqq4DqhNfvhtov1ldgryukLRyefKnzaWs5NuYHWvUSd5xC+4TsJPpU/IEOYbAieYSkewuWFilO6AgN9js/w/6evw0ru/moucd4WLlrc4gFtT6H+LZuEbUufBpkwOXGAgwVnzCrYVzcRXWVOyoWgEgD+OGMebEZN6JZ1vM= Received: by 10.54.44.58 with SMTP id r58mr346969wrr; Thu, 30 Jun 2005 05:05:53 -0700 (PDT) Received: by 10.54.47.76 with HTTP; Thu, 30 Jun 2005 05:05:53 -0700 (PDT) Message-ID: <27dbfc8c05063005057c230d62@mail.gmail.com> Date: Thu, 30 Jun 2005 14:05:53 +0200 From: Valerio daelli To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Dual Fibre Channel Host Adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Valerio daelli List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 12:05:55 -0000 Hi all we have few amd64 FreeBSD 5.4 boxes and we would like to buy some Dual Fibre Channel Host Adapter. We would like to know which is the best supported by FreeBSD. If you have any reference (another mailing list, some sites etc.) please let us know. We have already visited=20 http://www.freebsd.org/releases/5.4R/hardware-amd64.html#DISK but we would like to hear the users' opinion. Thanks a lot. Valerio Daelli From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 12:52:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836E916A41C for ; Thu, 30 Jun 2005 12:52:31 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40F9B43D1F for ; Thu, 30 Jun 2005 12:52:31 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so86471wra for ; Thu, 30 Jun 2005 05:52:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ap3xKEJ3khydlpssuFE0Up5u7apvVPipAEOR/JxVbD0/U/h6MpD2tX5VDVg6TEt8zRYv0MOjxhhDah3OCd/0Wkoo7FJBtj4K5k+r1HQRsylR0v855ujLIvx+kiowbbasZacqxjG06Z0YGP5jYC86r6GbMK6sEHSClvF8UzlCIGQ= Received: by 10.54.3.16 with SMTP id 16mr371958wrc; Thu, 30 Jun 2005 05:52:30 -0700 (PDT) Received: by 10.54.125.12 with HTTP; Thu, 30 Jun 2005 05:52:30 -0700 (PDT) Message-ID: Date: Thu, 30 Jun 2005 14:52:30 +0200 From: Claus Guttesen To: Valerio daelli In-Reply-To: <27dbfc8c05063005057c230d62@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <27dbfc8c05063005057c230d62@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: Dual Fibre Channel Host Adapter X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Claus Guttesen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 12:52:31 -0000 > we have few amd64 FreeBSD 5.4 boxes and we would like to buy > some Dual Fibre Channel Host Adapter. > We would like to know which is the best supported by FreeBSD. > If you have any reference (another mailing list, some sites etc.) > please let us know. > We have already visited > http://www.freebsd.org/releases/5.4R/hardware-amd64.html#DISK > but we would like to hear the users' opinion. > Thanks a lot. I tried qlogic's 2310 (single port) hba on a Dell 2850 with 4 GB RAM and the amd64-port and the isp-driver. I experienced some panics which did not happen on the i386-port. This may have to do with the amount of RAM. So you probably want to test this in advance. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 13:44:18 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF72316A41C for ; Thu, 30 Jun 2005 13:44:18 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD7643D1F for ; Thu, 30 Jun 2005 13:44:18 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 24061 invoked from network); 30 Jun 2005 13:44:18 -0000 Received: from adsl-211-141-250.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.250]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Jun 2005 13:44:17 -0000 Message-ID: <42C3F72E.9070902@speakeasy.net> Date: Thu, 30 Jun 2005 09:44:14 -0400 From: JM User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Jennejohn References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> In-Reply-To: <200506290818.j5T8IELL002348@peedub.jennejohn.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 30 Jun 2005 13:44:18 -0000 Gary Jennejohn wrote: >Has anyone tried using a dual-core AMD65 X2 in an ASUS AV8 Deluxe >mobo? For that matter, has anyone on this list tried out an X2 at >all? > >-------- >Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde > > > i've never had the pleasure of coming across an AMD65... and unfortunately i haven't experienced an X2 although there are a few articles regarding performance and other info. anandtech.com is my favorite review site and they've tested the X2 in this article: http://anandtech.com/cpuchipsets/showdoc.aspx?i=2410 and here's the dual core opterons just for fun: http://anandtech.com/cpuchipsets/showdoc.aspx?i=2397 and some info on X2 overclocking: http://anandtech.com/cpuchipsets/showdoc.aspx?i=2452 hope this helps. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 15:43:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C09716A41C for ; Thu, 30 Jun 2005 15:43:45 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F2B243D49 for ; Thu, 30 Jun 2005 15:43:44 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j5UFhiLP005996 for ; Thu, 30 Jun 2005 11:43:44 -0400 Date: Thu, 30 Jun 2005 11:43:43 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: FreeBSD amd64 List Message-ID: <20050630114041.W64452@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 15:43:45 -0000 Is there a difference in the behavior of crontab in AMD64 vs i386? I have a crontab 14 22 * * * /usr/home/hank/bin/tozoraida.sh which is not running When I try to research the problem the only thing I see is an error in maillog postfix/sendmail[36590]: fatal: No recipient addresses found in message header Have setup user crontab on several other machines without problems, but they were all i386. Archives came up empty so don't know if this is an issue with the AMD64 branch or something else. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 17:34:39 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E664F16A41C for ; Thu, 30 Jun 2005 17:34:39 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1F0E43D4C for ; Thu, 30 Jun 2005 17:34:39 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 7A8852A8FA for ; Thu, 30 Jun 2005 10:34:39 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 3B8BEE2B3 for ; Thu, 30 Jun 2005 10:34:39 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.4/8.13.1) with ESMTP id j5UHYch9037320; Thu, 30 Jun 2005 10:34:38 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.4/8.13.1/Submit) id j5UHYcgV037319; Thu, 30 Jun 2005 10:34:38 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 30 Jun 2005 10:34:37 -0700 User-Agent: KMail/1.8.1 References: <20050630114041.W64452@zoraida.natserv.net> In-Reply-To: <20050630114041.W64452@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506301034.38233.peter@wemm.org> Cc: Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 17:34:40 -0000 On Thursday 30 June 2005 08:43 am, Francisco Reyes wrote: > Is there a difference in the behavior of crontab in AMD64 vs i386? > > I have a crontab > 14 22 * * * /usr/home/hank/bin/tozoraida.sh > > which is not running > When I try to research the problem the only thing I see is an error > in maillog > postfix/sendmail[36590]: fatal: > No recipient addresses found in message > header > > Have setup user crontab on several other machines without problems, > but they were all i386. > > Archives came up empty so don't know if this is an issue with the > AMD64 branch or something else. I'm afraid its something else. I do a lot of cron work on various amd64 boxes and there's no differences compared to i386. So I'm afraid you're going to need to do a bit of detective work. You might also check /var/log/cron. Also, have you tried restarting cron in case something got messed up in the process's internals? -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 19:51:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 966F116A41C for ; Thu, 30 Jun 2005 19:51:48 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F28143D48 for ; Thu, 30 Jun 2005 19:51:48 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j5UJplRw010027; Thu, 30 Jun 2005 15:51:47 -0400 Date: Thu, 30 Jun 2005 15:51:46 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: Peter Wemm In-Reply-To: <200506301034.38233.peter@wemm.org> Message-ID: <20050630154904.I65748@zoraida.natserv.net> References: <20050630114041.W64452@zoraida.natserv.net> <200506301034.38233.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 19:51:48 -0000 On Thu, 30 Jun 2005, Peter Wemm wrote: > I'm afraid its something else. I do a lot of cron work on various amd64 > boxes and there's no differences compared to i386. Great for the info. At least is one less variable to consider. > So I'm afraid you're going to need to do a bit of detective work. You > might also check /var/log/cron Just did. Lots of other entries/errors that I need to check, but the one related to the program I am trying to get run Jun 30 10:23:00 server05 /usr/sbin/cron[38466]: (hank) CMD (/usr/home/hank/bin/tozoraida.sh) Jun 30 11:05:33 server05 crontab[38566]: (hank) LIST (hank) Jun 30 11:11:21 server05 crontab[38595]: (hank) BEGIN EDIT (hank) Jun 30 11:11:27 server05 crontab[38595]: (hank) END EDIT (hank) Jun 30 13:23:00 server05 /usr/sbin/cron[38869]: (hank) CMD (/usr/home/hank/bin/tozoraida.sh) The program seems like it was called from cron. > Also, have you tried restarting cron > in case something got messed up in the process's internals? Will try that. Thanks again for the pointers. Next, going to see if it's something related to Postfix.. Although it would be pretty bad if a crontab would fail because of a call to the local smtp. From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 20:03:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A908616A41C for ; Thu, 30 Jun 2005 20:03:03 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (167-49.nyc.dsl.access.net [166.84.167.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF6443D1D for ; Thu, 30 Jun 2005 20:03:02 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (localhost.mistermishap.net [127.0.0.1]) by daemon.mistermishap.net (8.12.9/8.12.9) with ESMTP id j5UK32mU038887 for ; Thu, 30 Jun 2005 16:03:02 -0400 (EDT) (envelope-from rob@hudson-trading.com) Received: from localhost (rob@localhost) by daemon.mistermishap.net (8.12.9/8.12.9/Submit) with ESMTP id j5UK32fs038884 for ; Thu, 30 Jun 2005 16:03:02 -0400 (EDT) X-Authentication-Warning: daemon.mistermishap.net: rob owned process doing -bs Date: Thu, 30 Jun 2005 16:03:02 -0400 (EDT) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: freebsd-amd64@freebsd.org Message-ID: <20050630160225.D38285@daemon.mistermishap.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: fatal trap 12 in pagedaemon on dual-core opteron machine 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, 30 Jun 2005 20:03:03 -0000 I've been having stability problems in a new dual-core opteron machine. When it first crashed we were running a number of multicast applications that were listening to, recording, and rebroadcasting data. I have been able to re-simulate the data play upto the crash and can recreate the panic 1 out of every 5 or 6 replays. the hardware is: - 2 275 (2.2Ghz) dual-core processors - tyan 2881 k8sr motherboard (bios 2.05v) - 2 Gb DDR 400Mhz PC3200 Registered ECC memory - SEAGATE ST3146807LC scsi drive - intel dual-port gigabit ethernet card I have experienced the problem in both 5.4-RELEASE and STABLE (stable as-of today). I am running a custom SMP kernel. The most recent panic message was: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x88 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802af0da stack pointer = 0x10:0xffffffffb1c16a60 frame pointer = 0x10:0xffffff005b8cd000 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 63 (pagedaemon) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 1h3m10s Dumping 2047 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 1024 1040 1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312 1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584 1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032 Every time it crashes the current process is pagedaemon, and the instruction pointer points to 'thread_fini'. kgdb shows: host1# kgdb /usr/obj/usr/src/sys/LOCAL/kernel.debug /usr/tmp/crash/vmcore.6 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] This GDB was configured as "amd64-marcel-freebsd". #0 doadump () at pcpu.h:167 167 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:167 #1 0x0000000000000000 in ?? () #2 0xffffffff802a2bd7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410 #3 0xffffffff802a340f in panic (fmt=0xffffff007b78c500 "\uffff\022y{") at /usr/src/sys/kern/kern_shutdown.c:566 #4 0xffffffff80412f8a in trap_fatal (frame=0xffffff007b78c500, eva=18446742976269456104) at /usr/src/sys/amd64/amd64/trap.c:639 #5 0xffffffff804132af in trap_pfault (frame=0xffffffffb1c169b0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:562 #6 0xffffffff80413553 in trap (frame= {tf_rdi = -1097427386128, tf_rsi = -1097440115456, tf_rdx = 99343, tf_rcx = 0, tf_r8 = 0, tf_r9 = 0, tf_rax = 99343, tf_rbx = 0, tf_rbp = -1097975672832, tf_r10 = 4503599627366400, tf_r11 = 3424, tf_r12 = 4, tf_r13 = 4, tf_r14 = -1098264600680, tf_r15 = -1097364252144, tf_trapno = 12, tf_addr = 136, tf_flags = -1098264600680, tf_err = 0, tf_rip = -2144669478, tf_cs = 8, tf_rflags = 66050, tf_rsp = -1312724368, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:341 #7 0xffffffff80400c0b in calltrap () at /usr/src/sys/amd64/amd64/exception.S:171 #8 0xffffff007c3b00f0 in ?? () #9 0xffffff007b78c500 in ?? () #10 0x000000000001840f in ?? () #11 0x0000000000000000 in ?? () #12 0x0000000000000000 in ?? () #13 0x0000000000000000 in ?? () #14 0x000000000001840f in ?? () #15 0x0000000000000000 in ?? () #16 0xffffff005b8cd000 in ?? () #17 0x000ffffffffff000 in ?? () #18 0x0000000000000d60 in ?? () #19 0x0000000000000004 in ?? () #20 0x0000000000000004 in ?? () #21 0xffffff004a541f98 in ?? () #22 0xffffff007ffe5a10 in ?? () #23 0x000000000000000c in ?? () #24 0x0000000000000088 in ?? () #25 0xffffff004a541f98 in ?? () #26 0x0000000000000000 in ?? () #27 0xffffffff802af0da in thread_fini (mem=0x0, size=0) at /usr/src/sys/kern/kern_thread.c:271 #28 0x0000000000000010 in ?? () #29 0x0000000000000001 in ?? () #30 0xffffff007ffe5a00 in ?? () #31 0xffffff005b8cdf98 in ?? () #32 0xffffffff803f67ff in zone_drain (zone=0x8) at /usr/src/sys/vm/uma_core.c:749 #33 0xffffffff803f43b6 in zone_foreach (zfunc=0xffffffff803f6630 ) at /usr/src/sys/vm/uma_core.c:1494 #34 0xffffffff803f7fc9 in uma_reclaim () at /usr/src/sys/vm/uma_core.c:2623 #35 0xffffffff803f1dac in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:674 #36 0xffffffff802898cc in fork_exit (callout=0xffffffff803f17b0 , arg=0x0, frame=0xffffffffb1c16c50) at /usr/src/sys/kern/kern_fork.c:791 #37 0xffffffff80400e0e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:296 #38 0x0000000000000000 in ?? () #39 0x0000000000000000 in ?? () #40 0x0000000000000001 in ?? () #41 0x0000000000000000 in ?? () #42 0x0000000000000000 in ?? () #43 0x0000000000000000 in ?? () #44 0x0000000000000000 in ?? () #45 0x0000000000000000 in ?? () #46 0x0000000000000000 in ?? () #47 0x0000000000000000 in ?? () #48 0x0000000000000000 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x0000000000000000 in ?? () #58 0x0000000000000000 in ?? () #59 0x0000000000000000 in ?? () #60 0x0000000000000000 in ?? () #61 0x0000000000000000 in ?? () #62 0x0000000000000000 in ?? () #63 0x0000000000000000 in ?? () #64 0x0000000000000000 in ?? () #65 0x0000000000000000 in ?? () #66 0x0000000000000000 in ?? () #67 0x0000000000000000 in ?? () #68 0x0000000000000000 in ?? () #69 0x0000000000000000 in ?? () #70 0x00000000007ff000 in ?? () #71 0xffffffff8062fad4 in vm_page_max_wired () #72 0xffffffff8062f1c0 in vm_page_queue_free_mtx () #73 0x0000000000000001 in ?? () #74 0xffffff007b7912e8 in ?? () #75 0xffffff007b7d5000 in ?? () #76 0xffffffffb1c16a08 in ?? () #77 0xffffff007b78c500 in ?? () #78 0xffffffff802b777c in sched_switch (td=0x0, newtd=0x0, flags=1) at /usr/src/sys/kern/sched_4bsd.c:881 #79 0x0000000000000000 in ?? () #80 0x0000000000000000 in ?? () #81 0x0000000000000000 in ?? () #82 0x0000000000000000 in ?? () #83 0x0000000000000000 in ?? () #84 0x0000000000000000 in ?? () #85 0x0000000000000000 in ?? () #86 0x0000000000000000 in ?? () #87 0x0000000000000000 in ?? () #88 0x0000000000000000 in ?? () #89 0x0000000000000000 in ?? () #90 0x0000000000000000 in ?? () #91 0x0000000000000000 in ?? () #92 0x0000000000000000 in ?? () #93 0x0000000000000000 in ?? () #94 0x0000000000000000 in ?? () #95 0x0000000000000000 in ?? () #96 0x0000000000000000 in ?? () #97 0x0000000000000000 in ?? () #98 0x0000000000000000 in ?? () #99 0x0000000000000000 in ?? () #100 0x0000000000000000 in ?? () #101 0x0000000000000000 in ?? () #102 0x0000000000000000 in ?? () #103 0x0000000000000000 in ?? () #104 0x0000000000000000 in ?? () #105 0x0000000000000000 in ?? () #106 0x0000000000000000 in ?? () #107 0x0000000000000000 in ?? () #108 0x0000000000000000 in ?? () #109 0x0000000000000000 in ?? () #110 0x0000000000000000 in ?? () #111 0x0000000000000000 in ?? () #112 0x0000000000000000 in ?? () #113 0x0000000000000000 in ?? () #114 0x0000000000000000 in ?? () #115 0x0000000000000000 in ?? () #116 0x0000000000000000 in ?? () #117 0x0000000000000000 in ?? () #118 0x0000000000000000 in ?? () #119 0x0000000000000000 in ?? () #120 0x0000000000000000 in ?? () #121 0x0000000000000000 in ?? () #122 0x0000000000000000 in ?? () #123 0x0000000000000000 in ?? () #124 0x0000000000000000 in ?? () #125 0x0000000000000000 in ?? () #126 0x0000000000000000 in ?? () #127 0x0000000000000000 in ?? () #128 0x0000000000000000 in ?? () #129 0x0000000000000000 in ?? () #130 0x0000000000000000 in ?? () #131 0x0000000000000000 in ?? () #132 0x0000000000000000 in ?? () #133 0x0000000000000000 in ?? () #134 0x0000000000000000 in ?? () #135 0x0000000000000000 in ?? () #136 0x0000000000000000 in ?? () #137 0x0000000000000000 in ?? () #138 0x0000000000000000 in ?? () #139 0x0000000000000000 in ?? () #140 0x0000000000000000 in ?? () #141 0x0000000000000000 in ?? () #142 0x0000000000000000 in ?? () #143 0x0000000000000000 in ?? () #144 0x0000000000000000 in ?? () #145 0x0000000000000000 in ?? () #146 0x0000000000000000 in ?? () #147 0x0000000000000000 in ?? () #148 0x0000000000000000 in ?? () #149 0x0000000000000000 in ?? () #150 0x0000000000000000 in ?? () Cannot access memory at address 0xffffffffb1c17000 kernel config: machine amd64 cpu HAMMER ident CUSTOM makeoptions DEBUG=-g options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options NTFS # NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Needed by COMPAT_LINUX32 options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_LINUX32 # Compatible with i386 linux binaries options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug options ADAPTIVE_GIANT # Giant mutex is adaptive. options SMP device atpic # 8259A compatability options LINPROCFS # Cannot be a module yet. device acpi device isa device pci device fdc device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support device sc device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device device em # Intel PRO/1000 adapter Gigabit Ethernet Card device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse any thoughts? thanks. - Rob Watt From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 30 20:49:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9392416A41C for ; Thu, 30 Jun 2005 20:49:53 +0000 (GMT) (envelope-from peter@wemm.org) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E5CC43D1D for ; Thu, 30 Jun 2005 20:49:53 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 532701976E; Thu, 30 Jun 2005 13:49:53 -0700 (PDT) From: Peter Wemm To: Francisco Reyes Date: Thu, 30 Jun 2005 13:49:52 -0700 User-Agent: KMail/1.7.2 References: <20050630114041.W64452@zoraida.natserv.net> <200506301034.38233.peter@wemm.org> <20050630154904.I65748@zoraida.natserv.net> In-Reply-To: <20050630154904.I65748@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506301349.52913.peter@wemm.org> Cc: freebsd-amd64@freebsd.org Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 20:49:53 -0000 On Thursday 30 June 2005 12:51 pm, Francisco Reyes wrote: > On Thu, 30 Jun 2005, Peter Wemm wrote: > > I'm afraid its something else. I do a lot of cron work on various > > amd64 boxes and there's no differences compared to i386. > > Great for the info. At least is one less variable to consider. > > > So I'm afraid you're going to need to do a bit of detective work. > > You might also check /var/log/cron > > Just did. > Lots of other entries/errors that I need to check, but the one > related to the program I am trying to get run > > Jun 30 10:23:00 server05 /usr/sbin/cron[38466]: (hank) CMD > (/usr/home/hank/bin/tozoraida.sh) > Jun 30 11:05:33 server05 crontab[38566]: (hank) LIST (hank) > Jun 30 11:11:21 server05 crontab[38595]: (hank) BEGIN EDIT (hank) > Jun 30 11:11:27 server05 crontab[38595]: (hank) END EDIT (hank) > Jun 30 13:23:00 server05 /usr/sbin/cron[38869]: (hank) CMD > (/usr/home/hank/bin/tozoraida.sh) > > > The program seems like it was called from cron. Silly idea. put 'date >> /tmp/tozoraida.log' at the start of your script and make sure that it actually kicked off. > Next, going to see if it's something related to Postfix.. > Although it would be pretty bad if a crontab would fail because of a > call to the local smtp. It shouldn't be anything inherently due to postfix, because that's what I use on most of my amd64 boxes. Of course, something could have been messed up somehow. The only thing I wonder is if perhaps there is a file descriptor leak or resource problem? You could also try this from right before the script is due to run: sysctl kern.ktrace.request_pool=16384 sysctl kern.ktrace.genio_size=128 ktrace -f /tmp/cron.trace -i -p 38869 and then you can use kdump -f /tmp/cron.trace and look for clues. The output will be big though. kdump can be told to look for particular processes in the combined trace file if that helps. Be sure to run 'ktrace -C' to turn off any child processes that inherited trace mode or you'll run out of disk space very quickly. Anyway, you should see exactly what error conditions lead to the problem. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 01:44:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2A0616A41C for ; Fri, 1 Jul 2005 01:44:04 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 752CA43D49 for ; Fri, 1 Jul 2005 01:44:04 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: by wproxy.gmail.com with SMTP id i21so209385wra for ; Thu, 30 Jun 2005 18:44:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PGQp6kja8gbdgPErrJ9wnXuT2Y+9AN8D5hRit0+RCBMjS+tYbtyGaJ9WU7waGCKxMREEW6DElUwjnrPJN95y97T5N/7BPLz6fFS0vrKVXSjcJ1DMNV1CVnA/1s5tazumxh6VV4ZD56ynQMhGfctNrt6B0nCuwUKt+18lPHpBxWk= Received: by 10.54.117.16 with SMTP id p16mr898532wrc; Thu, 30 Jun 2005 18:44:02 -0700 (PDT) Received: by 10.54.31.69 with HTTP; Thu, 30 Jun 2005 18:44:02 -0700 (PDT) Message-ID: <8f55402905063018441217c95a@mail.gmail.com> Date: Fri, 1 Jul 2005 11:44:02 +1000 From: =?WINDOWS-1252?B?lSCV?= To: JM In-Reply-To: <42C3F72E.9070902@speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?WINDOWS-1252?B?lSCV?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 01:44:05 -0000 On 6/30/05, JM wrote: > Gary Jennejohn wrote: >=20 > >Has anyone tried using a dual-core AMD65 X2 in an ASUS AV8 Deluxe > >mobo? For that matter, has anyone on this list tried out an X2 at > >all? > > > >-------- > >Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOT= de > > > > > > > i've never had the pleasure of coming across an AMD65... and > unfortunately i haven't experienced an X2 although there are a few > articles regarding performance and other info. anandtech.com is my > favorite review site and they've tested the X2 in this article: > http://anandtech.com/cpuchipsets/showdoc.aspx?i=3D2410 > and here's the dual core opterons just for fun: > http://anandtech.com/cpuchipsets/showdoc.aspx?i=3D2397 > and some info on X2 overclocking: > http://anandtech.com/cpuchipsets/showdoc.aspx?i=3D2452 > hope this helps. >=20 Page 2 of the second last link has this to say, regarding compatibility of the X2 chips with existing motherboards: http://anandtech.com/cpuchipsets/showdoc.aspx?i=3D2397&p=3D2 "... On the desktop, the Athlon 64 X2 series is fully compatible with all Socket-939 motherboards. All you need is a BIOS update and you're good to go." I'd be truly amazed if this was the case for all motherboards, although it might be in the spec... --cheers gm From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 01:47:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 382F316A41C for ; Fri, 1 Jul 2005 01:47:23 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14F5A43D1D for ; Fri, 1 Jul 2005 01:47:22 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j611lLFU008982; Thu, 30 Jun 2005 18:47:22 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j611lLdt008981; Thu, 30 Jun 2005 18:47:21 -0700 (PDT) (envelope-from obrien) Date: Thu, 30 Jun 2005 18:47:21 -0700 From: "David O'Brien" To: Rob Watt Message-ID: <20050701014721.GA4460@dragon.NUXI.org> References: <20050630160225.D38285@daemon.mistermishap.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050630160225.D38285@daemon.mistermishap.net> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: fatal trap 12 in pagedaemon on dual-core opteron machine X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 01:47:23 -0000 On Thu, Jun 30, 2005 at 04:03:02PM -0400, Rob Watt wrote: > I've been having stability problems in a new dual-core opteron machine. > When it first crashed we were running a number of multicast > applications that were listening to, recording, and rebroadcasting data. I > have been able to re-simulate the data play upto the crash and can > recreate the panic 1 out of every 5 or 6 replays. > > the hardware is: > > - 2 275 (2.2Ghz) dual-core processors > - tyan 2881 k8sr motherboard (bios 2.05v) > - 2 Gb DDR 400Mhz PC3200 Registered ECC memory > - SEAGATE ST3146807LC scsi drive > - intel dual-port gigabit ethernet card There is no inherent issue in your choice of parts. What BIOS settings do you have for your memory configuration? Is software or hardware memory hole turned on? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 01:54:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DF6416A41C; Fri, 1 Jul 2005 01:54:58 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44F2E43D4C; Fri, 1 Jul 2005 01:54:58 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j611svDQ011502; Thu, 30 Jun 2005 18:54:57 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j611svT7011501; Thu, 30 Jun 2005 18:54:57 -0700 (PDT) (envelope-from obrien) Date: Thu, 30 Jun 2005 18:54:57 -0700 From: "David O'Brien" To: =?unknown-8bit?B?lSCV?= Message-ID: <20050701015457.GC4460@dragon.NUXI.org> References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8f55402905063018441217c95a@mail.gmail.com> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hardware@freebsd.org, freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 01:54:58 -0000 On Fri, Jul 01, 2005 at 11:44:02AM +1000, ? ? wrote: > Page 2 of the second last link has this to say, regarding > compatibility of the X2 chips with existing motherboards: > http://anandtech.com/cpuchipsets/showdoc.aspx?i=2397&p=2 > "... > On the desktop, the Athlon 64 X2 series is fully compatible with all > Socket-939 motherboards. All you need is a BIOS update and you're > good to go." > > I'd be truly amazed if this was the case for all motherboards, > although it might be in the spec... It really should be that simple. All the external interfaces and pins are the same for Athlon64-939 and Athlon64 X2. They have the same thermal specifications, etc... -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 09:50:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFF8D16A41C; Fri, 1 Jul 2005 09:50:42 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D40343D1D; Fri, 1 Jul 2005 09:50:41 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 1 Jul 2005 10:51:22 +0100 Message-ID: <42C511EF.70004@dial.pipex.com> Date: Fri, 01 Jul 2005 10:50:39 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: =?windows-1252?Q?=95_=95?= References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> In-Reply-To: <8f55402905063018441217c95a@mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Jul 2005 09:51:22.0896 (UTC) FILETIME=[705B8100:01C57E22] Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 09:50:42 -0000 On 6/30/05, JM wrote >Page 2 of the second last link has this to say, regarding >compatibility of the X2 chips with existing motherboards: > >http://anandtech.com/cpuchipsets/showdoc.aspx?i=2397&p=2 >"... >On the desktop, the Athlon 64 X2 series is fully compatible with all >Socket-939 motherboards. All you need is a BIOS update and you're >good to go." > > The A8V Deluxe the original poster asked about, certainly claims on it's website to support X2 and has numerous recent BIOS updates to "prove" it. Not aware if there are any bootstrapping problems (the board is unlikely to come with latest BIOS). The board itself works OK under FreeBSD i386 (ACPI support poor, but doesn't seem to break anything and the serial ports come out backwards; other than that has been good for me the last month) but I don't have an X2. --Alex From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 10:59:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B375A16A41C; Fri, 1 Jul 2005 10:59:28 +0000 (GMT) (envelope-from guy@crossflight.co.uk) Received: from supermarine.crossflight.co.uk (supermarine.crossflight.co.uk [195.172.72.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B3A43D58; Fri, 1 Jul 2005 10:59:27 +0000 (GMT) (envelope-from guy@crossflight.co.uk) Received: from mailscan0.crossflight.co.uk (mailscan0.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.12.9p2/8.12.9) with ESMTP id j61AxOYt012501; Fri, 1 Jul 2005 11:59:25 +0100 (BST) (envelope-from guy@crossflight.co.uk) Received: from [195.172.72.7] (northrop.crossflight.co.uk) by mailscan0.crossflight.co.uk (Clearswift SMTPRS 5.0.4) with ESMTP id ; Fri, 1 Jul 2005 11:59:24 +0100 Message-ID: <42C5220B.1000203@crossflight.co.uk> Date: Fri, 01 Jul 2005 11:59:23 +0100 From: Guy Dawson Organization: Crossflight Limited User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-amd64@freebsd.org References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> In-Reply-To: <20050701015457.GC4460@dragon.NUXI.org> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63-supermarine_global_rules_20050204a X-Spam-Checker-Version: SpamAssassin 2.63-supermarine_global_rules_20050204a (2004-01-11) on supermarine.crossflight.co.uk Cc: Subject: Re: AMD64 X2 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, 01 Jul 2005 10:59:29 -0000 David O'Brien wrote: > On Fri, Jul 01, 2005 at 11:44:02AM +1000, ? ? wrote: > >>Page 2 of the second last link has this to say, regarding >>compatibility of the X2 chips with existing motherboards: >>http://anandtech.com/cpuchipsets/showdoc.aspx?i=2397&p=2 >>"... >>On the desktop, the Athlon 64 X2 series is fully compatible with all >>Socket-939 motherboards. All you need is a BIOS update and you're >>good to go." >> >>I'd be truly amazed if this was the case for all motherboards, >>although it might be in the spec... > > > It really should be that simple. All the external interfaces and pins > are the same for Athlon64-939 and Athlon64 X2. They have the same > thermal specifications, etc... It's the only way AMD could reasonably do it. To require a different motherboard for X1 (?) and X2 chips would have the mobo makers rioting! Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation oF Crossflight Limited. Crossflight Limited is an international express courier, mailing and logistics service provider, and is authorised and regulated by the Financial Services Authority to conduct General Insurance Business. This communication and any attachments are confidential and may be protected from disclosure. We endorse no advice or opinion contained in this communication that is not the subject of a contract between the recipient and ourselves. If you have received it in error please notify us immediately and note that any storage, use or disclosure is strictly prohibited and may be unlawful. Those communicating with us by electronic mail will be deemed to have accepted the risks associated with interception, amendment, loss and late or incomplete delivery. They will also be deemed to have consented to our intercepting and monitoring such communications. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ********************************************************************** From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 13:17:00 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.ORG Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9C3416A41C for ; Fri, 1 Jul 2005 13:17:00 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5886843D1F for ; Fri, 1 Jul 2005 13:16:59 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tmzebi@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j61DGtnE090437 for ; Fri, 1 Jul 2005 15:16:55 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j61DGsuD090436; Fri, 1 Jul 2005 15:16:54 +0200 (CEST) (envelope-from olli) Date: Fri, 1 Jul 2005 15:16:54 +0200 (CEST) Message-Id: <200507011316.j61DGsuD090436@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20050630114041.W64452@zoraida.natserv.net> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 13:17:01 -0000 Francisco Reyes wrote: > I have a crontab > 14 22 * * * /usr/home/hank/bin/tozoraida.sh > > which is not running > When I try to research the problem the only thing I see is an error in > maillog > postfix/sendmail[36590]: fatal: > No recipient addresses found in message > header Do you happen to use LDAP on that machine, or have some other unusual user-authentication scheme configured? There has been a similar case on the German FreeBSD- question mailing list recently (i.e. cron refusing to send mails, and the same error message from the MTA), and it turned out to be the fault of the local LDAP installation. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 13:44:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64C7C16A41C; Fri, 1 Jul 2005 13:44:23 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (167-49.nyc.dsl.access.net [166.84.167.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id F23D243D1D; Fri, 1 Jul 2005 13:44:22 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (localhost.mistermishap.net [127.0.0.1]) by daemon.mistermishap.net (8.12.9/8.12.9) with ESMTP id j61DiLmU044116; Fri, 1 Jul 2005 09:44:21 -0400 (EDT) (envelope-from rob@hudson-trading.com) Received: from localhost (rob@localhost) by daemon.mistermishap.net (8.12.9/8.12.9/Submit) with ESMTP id j61DiLmm044113; Fri, 1 Jul 2005 09:44:21 -0400 (EDT) X-Authentication-Warning: daemon.mistermishap.net: rob owned process doing -bs Date: Fri, 1 Jul 2005 09:44:21 -0400 (EDT) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: "David O'Brien" In-Reply-To: <20050701014721.GA4460@dragon.NUXI.org> Message-ID: <20050701094317.B43977@daemon.mistermishap.net> References: <20050630160225.D38285@daemon.mistermishap.net> <20050701014721.GA4460@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-amd64@freebsd.org Subject: Re: fatal trap 12 in pagedaemon on dual-core opteron machine 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, 01 Jul 2005 13:44:23 -0000 On Thu, 30 Jun 2005, David O'Brien wrote: > On Thu, Jun 30, 2005 at 04:03:02PM -0400, Rob Watt wrote: > There is no inherent issue in your choice of parts. > What BIOS settings do you have for your memory configuration? Is > software or hardware memory hole turned on? hardware/software memory hole is disabled in bios. Should it be enabled? - Rob Watt From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 13:53:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9CD216A41F for ; Fri, 1 Jul 2005 13:53:28 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BD0F43D5C for ; Fri, 1 Jul 2005 13:53:28 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so263215rna for ; Fri, 01 Jul 2005 06:53:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BXpu0I15kK4VkjB01/JHgtfQIxEb0zE2dr2flIh8HRRLI8+StTqZTnGqdBUWH2BYBJPbRqnmESjUQ/Bu07iF9U9G93DU8iKEy1brwqwjcmRHKeHnrBWU/jDNwFb6NUl22vh0VwoWuHj2O1vm9tw9B8gI//1lBeWd6s/XZW3TjYY= Received: by 10.38.67.12 with SMTP id p12mr284910rna; Fri, 01 Jul 2005 06:53:27 -0700 (PDT) Received: by 10.38.12.17 with HTTP; Fri, 1 Jul 2005 06:53:27 -0700 (PDT) Message-ID: <1d6d20bc050701065367a01e8b@mail.gmail.com> Date: Fri, 1 Jul 2005 21:53:27 +0800 From: Jia-Shiun Li To: Guy Dawson In-Reply-To: <42C5220B.1000203@crossflight.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jia-Shiun Li List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 13:53:28 -0000 On 7/1/05, Guy Dawson wrote: > David O'Brien wrote: > > It really should be that simple. All the external interfaces and pins > > are the same for Athlon64-939 and Athlon64 X2. They have the same > > thermal specifications, etc... >=20 > It's the only way AMD could reasonably do it. To require a different > motherboard for X1 (?) and X2 chips would have the mobo makers rioting! That's what Intel did. Requiring a new i945/i955-based board for their rushed dual-core CPUs. Only use the same socket but varied pin definition. If you put the new CPU on an i915 board, it will shutdown automatically to 'protect'. In contrast Athlon64 claimed to be designed with dual-core capability in mind from the beginning. Jia-Shiun. From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 13:57:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13F3616A41C; Fri, 1 Jul 2005 13:57:20 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (167-49.nyc.dsl.access.net [166.84.167.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id B16B343D66; Fri, 1 Jul 2005 13:57:19 +0000 (GMT) (envelope-from rob@hudson-trading.com) Received: from daemon.mistermishap.net (localhost.mistermishap.net [127.0.0.1]) by daemon.mistermishap.net (8.12.9/8.12.9) with ESMTP id j61DvImU044152; Fri, 1 Jul 2005 09:57:18 -0400 (EDT) (envelope-from rob@hudson-trading.com) Received: from localhost (rob@localhost) by daemon.mistermishap.net (8.12.9/8.12.9/Submit) with ESMTP id j61DvINb044149; Fri, 1 Jul 2005 09:57:18 -0400 (EDT) X-Authentication-Warning: daemon.mistermishap.net: rob owned process doing -bs Date: Fri, 1 Jul 2005 09:57:18 -0400 (EDT) From: Rob Watt X-X-Sender: rob@daemon.mistermishap.net To: "David O'Brien" In-Reply-To: <20050701014721.GA4460@dragon.NUXI.org> Message-ID: <20050701095505.D43977@daemon.mistermishap.net> References: <20050630160225.D38285@daemon.mistermishap.net> <20050701014721.GA4460@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-amd64@freebsd.org Subject: Re: fatal trap 12 in pagedaemon on dual-core opteron machine 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, 01 Jul 2005 13:57:20 -0000 On Thu, 30 Jun 2005, David O'Brien wrote: > On Thu, Jun 30, 2005 at 04:03:02PM -0400, Rob Watt wrote: > > the hardware is: > > > > - 2 275 (2.2Ghz) dual-core processors > > - tyan 2881 k8sr motherboard (bios 2.05v) > > - 2 Gb DDR 400Mhz PC3200 Registered ECC memory > > - SEAGATE ST3146807LC scsi drive > > - intel dual-port gigabit ethernet card > > There is no inherent issue in your choice of parts. > What BIOS settings do you have for your memory configuration? Is > software or hardware memory hole turned on? The BIOS setting for memory are: Memory Clock Mode Auto MCT Timing Mode Auto User Config Mode Auto Bank Interleaving Auto Burst Length 8 Beats Enable Clock to All Dimms Disabled Hardware Memory Hole Disabled Node Interleaving Disabled DRAM ECC Enabled IOMMU Mode Disabled - Rob Watt From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 15:30:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADBF616A41C for ; Fri, 1 Jul 2005 15:30:17 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F56643D1D for ; Fri, 1 Jul 2005 15:30:17 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j61FUGfS025053 for ; Fri, 1 Jul 2005 11:30:16 -0400 Date: Fri, 1 Jul 2005 11:30:16 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: freebsd-amd64@freebsd.org In-Reply-To: <200507011316.j61DGsuD090436@lurza.secnetix.de> Message-ID: <20050701112803.N2991@zoraida.natserv.net> References: <200507011316.j61DGsuD090436@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 15:30:17 -0000 On Fri, 1 Jul 2005, Oliver Fromme wrote: > Do you happen to use LDAP on that machine, or have some > other unusual user-authentication scheme configured? No. > There has been a similar case on the German FreeBSD- > question mailing list recently (i.e. cron refusing to > send mails, and the same error message from the MTA), > and it turned out to be the fault of the local LDAP > installation. I am still trying to figure it out. What I find disconcerting is that it seems the cron job fails because the email fails. The program I call in cron runs fine if called from the command line. Never had this problem on a i386 machine, that's why I thought maybe it was AMD64.. but most likely it's a Postfix setting. From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 16:27:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80E1116A41C for ; Fri, 1 Jul 2005 16:27:21 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5749643D1D for ; Fri, 1 Jul 2005 16:27:21 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 27855 invoked from network); 1 Jul 2005 16:27:20 -0000 Received: from adsl-211-141-250.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.250]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Jul 2005 16:27:20 -0000 Message-ID: <42C56EE5.3010608@speakeasy.net> Date: Fri, 01 Jul 2005 12:27:17 -0400 From: JM User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jia-Shiun Li References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> In-Reply-To: <1d6d20bc050701065367a01e8b@mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Guy Dawson , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 16:27:21 -0000 Jia-Shiun Li wrote: >On 7/1/05, Guy Dawson wrote: > > >>David O'Brien wrote: >> >> >>>It really should be that simple. All the external interfaces and pins >>>are the same for Athlon64-939 and Athlon64 X2. They have the same >>>thermal specifications, etc... >>> >>> >>It's the only way AMD could reasonably do it. To require a different >>motherboard for X1 (?) and X2 chips would have the mobo makers rioting! >> >> > >That's what Intel did. Requiring a new i945/i955-based board for their >rushed dual-core CPUs. Only use the same socket but varied pin >definition. If you put the new CPU on an i915 board, it will shutdown >automatically to 'protect'. In contrast Athlon64 claimed to be >designed with dual-core capability in mind from the beginning. > >Jia-Shiun. >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > first of all, Intel claims to have had the original idea of dual core which any educated hardware expert knows to be false. AMD touted support for multiple cores months ahead of intel and it's apparent by the hyper transport technology white paper that AMD was planning this route when the Athlon XP was released long ago. Intel only recently scrapped their processor roadmap. rather than attempt to hit the 4GHz mark they re-wrote the roadmap, fabbed up a quick and dirty dual core solution and released it before AMD claiming that the idea was theirs... i hate that company... From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 16:33:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF7EB16A41C for ; Fri, 1 Jul 2005 16:33:48 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D0B743D49 for ; Fri, 1 Jul 2005 16:33:48 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 31689 invoked from network); 1 Jul 2005 16:33:48 -0000 Received: from adsl-211-141-250.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.250]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Jul 2005 16:33:47 -0000 Message-ID: <42C57069.9080102@speakeasy.net> Date: Fri, 01 Jul 2005 12:33:45 -0400 From: JM User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Francisco Reyes References: <20050630114041.W64452@zoraida.natserv.net> In-Reply-To: <20050630114041.W64452@zoraida.natserv.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD amd64 List Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 16:33:48 -0000 Francisco Reyes wrote: > Is there a difference in the behavior of crontab in AMD64 vs i386? > > I have a crontab > 14 22 * * * /usr/home/hank/bin/tozoraida.sh > > which is not running > When I try to research the problem the only thing I see is an error in > maillog > postfix/sendmail[36590]: fatal: > No recipient addresses found in message > header > > Have setup user crontab on several other machines without problems, > but they were all i386. > > Archives came up empty so don't know if this is an issue with the > AMD64 branch or something else. i know it seems simple but make sure your script has +x permissions. a lot of times i've forgotten to do this and overlooking this sometimes causes me some headaches. it's one of those things you forget and slap yourself about later. From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 16:54:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3541716A41C for ; Fri, 1 Jul 2005 16:54:58 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id DACD043D4C for ; Fri, 1 Jul 2005 16:54:57 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j61GsuVj030508; Fri, 1 Jul 2005 12:54:57 -0400 Date: Fri, 1 Jul 2005 12:54:56 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: JM In-Reply-To: <42C57069.9080102@speakeasy.net> Message-ID: <20050701125231.F3559@zoraida.natserv.net> References: <20050630114041.W64452@zoraida.natserv.net> <42C57069.9080102@speakeasy.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD amd64 List Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 16:54:58 -0000 On Fri, 1 Jul 2005, JM wrote: > i know it seems simple but make sure your script has +x permissions. a lot of > times i've forgotten to do this and overlooking this sometimes causes me some > headaches. it's one of those things you forget and slap yourself about later. Found the problem. Will put complete details on a reply to a post I did in questions.. for the archives. Short version.. A file called /etc/nsswitch.conf needed to be changed because I compiled the kernel without NIS. However I still think that cron failing because it can not send an email is a strange "feature". :-) From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 17:21:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8625B16A41C; Fri, 1 Jul 2005 17:21:49 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F3DA43D1F; Fri, 1 Jul 2005 17:21:49 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j61HLdtQ029263; Fri, 1 Jul 2005 10:21:39 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j61HLdHS029262; Fri, 1 Jul 2005 10:21:39 -0700 Date: Fri, 1 Jul 2005 10:21:39 -0700 From: Brooks Davis To: Jia-Shiun Li Message-ID: <20050701172139.GA25916@odin.ac.hmc.edu> References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <1d6d20bc050701065367a01e8b@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Guy Dawson , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 17:21:49 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 01, 2005 at 09:53:27PM +0800, Jia-Shiun Li wrote: > On 7/1/05, Guy Dawson wrote: > > David O'Brien wrote: > > > It really should be that simple. All the external interfaces and pins > > > are the same for Athlon64-939 and Athlon64 X2. They have the same > > > thermal specifications, etc... > >=20 > > It's the only way AMD could reasonably do it. To require a different > > motherboard for X1 (?) and X2 chips would have the mobo makers rioting! >=20 > That's what Intel did. Requiring a new i945/i955-based board for their > rushed dual-core CPUs. Only use the same socket but varied pin > definition. If you put the new CPU on an i915 board, it will shutdown > automatically to 'protect'. In contrast Athlon64 claimed to be > designed with dual-core capability in mind from the beginning. It is worth noting that some motherboard manufactures did produce boards that don't work with dual core opterons. In particular the Tyan K8SR prior to rev-D doesn't work because they proview a couple too few watts to the CPU sockets. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCxXuiXY6L6fI4GtQRAt/XAKCfJobiSWfzOi9M1Yoe1zjeipn5vACgxUzU eyyZn6nArzjgBh2C6UvHF98= =HTE6 -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 18:02:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2F6F16A41C for ; Fri, 1 Jul 2005 18:02:43 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97D0A43D48 for ; Fri, 1 Jul 2005 18:02:40 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id E8C261F87BEE; Fri, 1 Jul 2005 20:02:38 +0200 (CEST) Date: Fri, 1 Jul 2005 20:02:38 +0200 From: Roman Neuhauser To: Francisco Reyes Message-ID: <20050701180238.GB85960@isis.sigpipe.cz> References: <200507011316.j61DGsuD090436@lurza.secnetix.de> <20050701112803.N2991@zoraida.natserv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050701112803.N2991@zoraida.natserv.net> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 18:02:44 -0000 # lists@natserv.com / 2005-07-01 11:30:16 -0400: > On Fri, 1 Jul 2005, Oliver Fromme wrote: > >There has been a similar case on the German FreeBSD- > >question mailing list recently (i.e. cron refusing to > >send mails, and the same error message from the MTA), > >and it turned out to be the fault of the local LDAP > >installation. > > I am still trying to figure it out. What I find disconcerting is that it > seems the cron job fails because the email fails. What exactly does crond feed into the sendmail? You can quite easily find out by putting a suitable script in /etc/mail/mailer.conf. Something that writes "$@" and its STDIN in a file will do. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 18:17:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A85E416A41F; Fri, 1 Jul 2005 18:17:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E5EA43D5F; Fri, 1 Jul 2005 18:17:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j61IORBi087945; Fri, 1 Jul 2005 12:24:28 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42C587EC.7030203@samsco.org> Date: Fri, 01 Jul 2005 12:14:04 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> <20050701172139.GA25916@odin.ac.hmc.edu> In-Reply-To: <20050701172139.GA25916@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Guy Dawson , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 18:17:11 -0000 Brooks Davis wrote: > On Fri, Jul 01, 2005 at 09:53:27PM +0800, Jia-Shiun Li wrote: > >>On 7/1/05, Guy Dawson wrote: >> >>>David O'Brien wrote: >>> >>>>It really should be that simple. All the external interfaces and pins >>>>are the same for Athlon64-939 and Athlon64 X2. They have the same >>>>thermal specifications, etc... >>> >>>It's the only way AMD could reasonably do it. To require a different >>>motherboard for X1 (?) and X2 chips would have the mobo makers rioting! >> >>That's what Intel did. Requiring a new i945/i955-based board for their >>rushed dual-core CPUs. Only use the same socket but varied pin >>definition. If you put the new CPU on an i915 board, it will shutdown >>automatically to 'protect'. In contrast Athlon64 claimed to be >>designed with dual-core capability in mind from the beginning. > > > It is worth noting that some motherboard manufactures did produce boards > that don't work with dual core opterons. In particular the Tyan K8SR > prior to rev-D doesn't work because they proview a couple too few watts > to the CPU sockets. > > -- Brooks > The Asus A8V-E series also does not work. Asus claims that it's a limitation of the Via K8T890 chipset, which is highly unfortunate since it's otherwise a good motherboard. Not sure whether to be upset at Asus or Via here, but either way I guess both suck =-) Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 18:17:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10F4216A41C for ; Fri, 1 Jul 2005 18:17:56 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id B031F43D6A for ; Fri, 1 Jul 2005 18:17:55 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j61IHsuQ028525; Fri, 1 Jul 2005 14:17:54 -0400 Date: Fri, 1 Jul 2005 14:17:54 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: Roman Neuhauser In-Reply-To: <20050701180238.GB85960@isis.sigpipe.cz> Message-ID: <20050701141651.P3559@zoraida.natserv.net> References: <200507011316.j61DGsuD090436@lurza.secnetix.de> <20050701112803.N2991@zoraida.natserv.net> <20050701180238.GB85960@isis.sigpipe.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: Crontab behavior in AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 18:17:56 -0000 On Fri, 1 Jul 2005, Roman Neuhauser wrote: >> I am still trying to figure it out. What I find disconcerting is that it >> seems the cron job fails because the email fails. > > What exactly does crond feed into the sendmail? You can quite easily > find out by putting a suitable script in /etc/mail/mailer.conf. > Something that writes "$@" and its STDIN in a file will do. Already found the problem.. posted to this list. It had to do with a file called /etc/nsswitch.conf and not having NIS anymore in the machine. will post full story on questions for the archives.. but basically if one compiles without NIS one needs to change /etc/nsswitch.conf From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 21:20:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BCB316A41C; Fri, 1 Jul 2005 21:20:25 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B111343D48; Fri, 1 Jul 2005 21:20:23 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 1 Jul 2005 22:21:05 +0100 Message-ID: <42C5B396.9000500@dial.pipex.com> Date: Fri, 01 Jul 2005 22:20:22 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Scott Long References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> <20050701172139.GA25916@odin.ac.hmc.edu> <42C587EC.7030203@samsco.org> In-Reply-To: <42C587EC.7030203@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Jul 2005 21:21:05.0413 (UTC) FILETIME=[CA427B50:01C57E82] Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 21:20:25 -0000 Scott Long wrote: > The Asus A8V-E series also does not work. Asus claims that it's a > limitation of the Via K8T890 chipset, which is highly unfortunate > since it's otherwise a good motherboard. Not sure whether to be > upset at Asus or Via here, but either way I guess both suck =-) Off topic a bit, but what would be your criteria for judging it a good motherboard? --Alex From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 21:27:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39C9716A41C; Fri, 1 Jul 2005 21:27:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C860243D1F; Fri, 1 Jul 2005 21:27:26 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j61LYfkP089260; Fri, 1 Jul 2005 15:34:41 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42C5B531.9040202@samsco.org> Date: Fri, 01 Jul 2005 15:27:13 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Zbyslaw References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> <20050701172139.GA25916@odin.ac.hmc.edu> <42C587EC.7030203@samsco.org> <42C5B396.9000500@dial.pipex.com> In-Reply-To: <42C5B396.9000500@dial.pipex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 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, 01 Jul 2005 21:27:27 -0000 Alex Zbyslaw wrote: > Scott Long wrote: > >> The Asus A8V-E series also does not work. Asus claims that it's a >> limitation of the Via K8T890 chipset, which is highly unfortunate >> since it's otherwise a good motherboard. Not sure whether to be >> upset at Asus or Via here, but either way I guess both suck =-) > > > Off topic a bit, but what would be your criteria for judging it a good > motherboard? > > --Alex > 1) Boots FreeBSD 2) Has a COM1 header 3) Has good perihperals (this one even has wifi built in, though there is no driver yet). Scott