From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 24 09:04:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6801B16A4CE; Sun, 24 Oct 2004 09:04:58 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id F20F243D41; Sun, 24 Oct 2004 09:04:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id i9O7XH8b088728; Sun, 24 Oct 2004 03:33:17 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id i9O7XCda030153; Sun, 24 Oct 2004 03:33:17 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 75DE57306E; Sun, 24 Oct 2004 03:33:12 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041024073312.75DE57306E@freebsd-current.sentex.ca> Date: Sun, 24 Oct 2004 03:33:12 -0400 (EDT) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 09:04:58 -0000 TB --- 2004-10-24 06:53:51 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-10-24 06:53:51 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-10-24 06:53:51 - checking out the source tree TB --- 2004-10-24 06:53:51 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-10-24 06:53:51 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-10-24 06:59:29 - building world (CFLAGS=-O2 -pipe) TB --- 2004-10-24 06:59:29 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-10-24 06:59:29 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c: In function `mb_put_uint32be': /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c:254: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c: In function `mb_put_uint32le': /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c:262: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c: In function `mb_put_int64be': /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c:270: warning: dereferencing type-punned pointer will break strict-aliasing rules /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c: In function `mb_put_int64le': /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb/../../contrib/smbfs/lib/smb/mbuf.c:278: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libsmb. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-10-24 07:33:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-10-24 07:33:12 - ERROR: failed to build world TB --- 2004-10-24 07:33:12 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 24 12:27:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC57816A4CE for ; Sun, 24 Oct 2004 12:27:55 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FFB543D3F for ; Sun, 24 Oct 2004 12:27:54 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.92] [213.112.167.92]) by mxfep01.bredband.com with ESMTP id <20041024122753.VVAO4883.mxfep01.bredband.com@[192.168.245.231]> for ; Sun, 24 Oct 2004 14:27:53 +0200 Message-ID: <417B9F35.7050705@bredband.net> Date: Sun, 24 Oct 2004 14:25:25 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-amd64@freebsd.org References: <20041022031145.23130.qmail@web61110.mail.yahoo.com> <20041022093439.GA15304@cat.robbins.dropbear.id.au> <417A462D.5060109@bredband.net> In-Reply-To: <417A462D.5060109@bredband.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: HOW TO to get linux emulation going on AMD64 5.3-RC1 ! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 12:27:55 -0000 This is a step by step guide to get linux emulation to run on AMD64 5.3-RC1 using the standard emulators/linux_base port. This is pulled together from the previous work done by Tim Robbins and Francois Tigeot. Do we need to feed this back to a certain authority ? If the "authority" reads this please respond, if not I'll mail it to the maintainer of linux_base in a few days. 1.) Put these varaiables in the Kernel config file: /usr/src/sys/amd64/conf/your_kernel_config_file options LINPROCFS options COMPAT_43 options COMPAT_LINUX32 Rebuild the kernel and install it ! 2.) Edited /etc/fstab for linprocfs , add the line: none /compat/linux/proc linprocfs rw 0 0 3.) Edit /etc/rc.conf and add the line: linux_enabled="YES" 4.) Reboot. 5.) Patch /usr/ports/emulators/linux_base/Makefile with Francois Tigeot's patch. Put the patch below in /usr/ports/emulators/linux_base/patchfile run: # patch -p0 < patchfile --------------------------------- --- Makefile.orig Wed Oct 6 15:13:33 2004 +++ Makefile Wed Oct 6 16:05:51 2004 @@ -110,6 +110,9 @@ RPM= LC_ALL=C rpm RPMFLAGS= --root ${LINUXBASE} --dbpath ${DBPATH} --nodeps \ --replacepkgs --ignoreos --ignorearch +.if (${ARCH} == "amd64") +RPMFLAGS+= --noscripts +.endif RPMDIR= ${DISTDIR}/${DIST_SUBDIR} REMOVE_DIRS= boot dev home root tmp var/tmp usr/local usr/tmp @@ -118,7 +121,7 @@ etc/protocols BRAND_FILES= bin/rpm sbin/ldconfig sbin/sln -FALLBACK_ELF_MIB= kern.fallback_elf_brand +FALLBACK_ELF_MIB= kern.elf32.fallback_brand LINUX_ELF= 3 PREVIOUS_ELF!= /sbin/sysctl -n ${FALLBACK_ELF_MIB} --------------------------------------------- 6.) Install linux_base # cd /usr/ports/emulators/linux_base # make install 7.) Fix the library searchpath for the linux Emulator to find the linux X libraries. Brand some binaries as Linux binaries, ( this is done in linux_base makefile for i386 ) # cd /usr/compat/linux # echo '/usr/X11R6/lib' > etc/ld.so.conf # brandelf -t Linux sbin/ldconfig # brandelf -t Linux sbin/sln # brandelf -t Linux sbin/rpm # sbin/ldconfig 8.) Reboot again. Install desired Linux apps and run. Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 24 13:01:49 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7029C16A4CE for ; Sun, 24 Oct 2004 13:01:49 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B85543D1D for ; Sun, 24 Oct 2004 13:01:48 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.92] [213.112.167.92]) by mxfep01.bredband.com with ESMTP id <20041024130147.WAMF4883.mxfep01.bredband.com@[192.168.245.231]>; Sun, 24 Oct 2004 15:01:47 +0200 Message-ID: <417BA728.30305@bredband.net> Date: Sun, 24 Oct 2004 14:59:20 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Goran Gajic References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@www.freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemenes CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 13:01:49 -0000 Goran Gajic wrote: > > Hi, > > I have installed FreeBSD 5.3RC1 on Fujitsu Siemenes Celsius. First > problem I had was with sk0. It stops responding and all I can do is > ifconfig sk0 down and then ifconfig sk0 up to reset it. Second, server > reboots without reason. What can I do to provide more information about > spontanious reboots. I'm also sending pciconf -vl as attachment. I > didn't compiled kernel I'm using GENERIC. The technical Overview for Celsius V accessible from this URL: http://www.fujitsu-siemens.com/products/deskbound/workstations/celsius_v.html Says that its supposed to have a Broadcom gigabit Ethernet i/F bge0 which is also found in the pciconf list you supplied. Have you installed an extra syskonnekt pci card in the machine ? As this is a DUAL Opteron machine with AMD8000 chipset its either a Tyan board or something Fujitsu built themselves. From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 24 19:59:47 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F33716A4CE for ; Sun, 24 Oct 2004 19:59:47 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 415CD43D1D for ; Sun, 24 Oct 2004 19:59:46 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id i9OJxbsF039484; Sun, 24 Oct 2004 21:59:37 +0200 (CEST) Date: Sun, 24 Oct 2004 21:59:37 +0200 (CEST) From: Goran Gajic To: Lars Tunkrans In-Reply-To: <417BA728.30305@bredband.net> Message-ID: References: <417BA728.30305@bredband.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean cc: freebsd-amd64@www.freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemens CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 19:59:47 -0000 You are right. It has Fujitsu-Siemens motherboard. It has only one NIC, integrated Broadcom. Since I need two NIC, second one is sk, pci card, not integrated. On 5.2.1 problem with sk was solvied by inseting fxp and using it instead. I have expected that problem with sk will be gone with 5.3 but it is still present - and machine is even rebooting for no reason. Regards, Goran Gajic On Sun, 24 Oct 2004, Lars Tunkrans wrote: > Goran Gajic wrote: >> >> Hi, >> >> I have installed FreeBSD 5.3RC1 on Fujitsu Siemenes Celsius. First problem >> I had was with sk0. It stops responding and all I can do is ifconfig sk0 >> down and then ifconfig sk0 up to reset it. Second, server reboots without >> reason. What can I do to provide more information about spontanious >> reboots. I'm also sending pciconf -vl as attachment. I didn't compiled >> kernel I'm using GENERIC. > > The technical Overview for Celsius V accessible from this URL: > > http://www.fujitsu-siemens.com/products/deskbound/workstations/celsius_v.html > > Says that its supposed to have a Broadcom gigabit Ethernet i/F bge0 which is > also found in the pciconf list you supplied. > Have you installed an extra syskonnekt pci card in the machine ? > > As this is a DUAL Opteron machine with AMD8000 chipset its either a Tyan > board > or something Fujitsu built themselves. > From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 24 20:08:41 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F6AE16A4CE for ; Sun, 24 Oct 2004 20:08:41 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CAD143D41 for ; Sun, 24 Oct 2004 20:08:41 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 10827 invoked from network); 24 Oct 2004 20:08:40 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Oct 2004 20:08:40 -0000 Received: from hydrogen.funkthat.com (vkbczg@localhost.funkthat.com [127.0.0.1])i9OK8dlb044166; Sun, 24 Oct 2004 13:08:39 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i9OK8bJT044165; Sun, 24 Oct 2004 13:08:37 -0700 (PDT) Date: Sun, 24 Oct 2004 13:08:37 -0700 From: John-Mark Gurney To: Goran Gajic Message-ID: <20041024200837.GA22681@funkthat.com> Mail-Followup-To: Goran Gajic , Lars Tunkrans , freebsd-amd64@www.freebsd.org References: <417BA728.30305@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-amd64@www.freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemens CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 20:08:41 -0000 Goran Gajic wrote this message on Sun, Oct 24, 2004 at 21:59 +0200: > You are right. It has Fujitsu-Siemens motherboard. It has only one NIC, > integrated Broadcom. Since I need two NIC, second one is sk, pci card, not > integrated. On 5.2.1 problem with sk was solvied by inseting fxp and using > it instead. I have expected that problem with sk will be gone with 5.3 but > it is still present - and machine is even rebooting for no reason. The sk driver in FreeBSD is less than ideal, and the vendor is not interested in providing information for better support. I would highly recommend you get a different card, or try to use the drivers SysKonnect provide on their web site (though they are only for 5.1-R and 5.2-R, I'm not sure if they support amd64 or not)... I have a card, and due to these considerations, will not be using it in any of my FreeBSD boxes... > On Sun, 24 Oct 2004, Lars Tunkrans wrote: > > >Goran Gajic wrote: > >> > >>Hi, > >> > >>I have installed FreeBSD 5.3RC1 on Fujitsu Siemenes Celsius. First > >>problem I had was with sk0. It stops responding and all I can do is > >>ifconfig sk0 down and then ifconfig sk0 up to reset it. Second, server > >>reboots without reason. What can I do to provide more information about > >>spontanious reboots. I'm also sending pciconf -vl as attachment. I didn't > >>compiled kernel I'm using GENERIC. > > > >The technical Overview for Celsius V accessible from this URL: > > > >http://www.fujitsu-siemens.com/products/deskbound/workstations/celsius_v.html > > > >Says that its supposed to have a Broadcom gigabit Ethernet i/F bge0 which > >is > >also found in the pciconf list you supplied. > >Have you installed an extra syskonnekt pci card in the machine ? > > > >As this is a DUAL Opteron machine with AMD8000 chipset its either a Tyan > >board > >or something Fujitsu built themselves. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 09:56:57 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6660216A4CE for ; Mon, 25 Oct 2004 09:56:57 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A494F43D39 for ; Mon, 25 Oct 2004 09:56:56 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id i9P9uqsF024615 for ; Mon, 25 Oct 2004 11:56:52 +0200 (CEST) Date: Mon, 25 Oct 2004 11:56:52 +0200 (CEST) From: Goran Gajic To: freebsd-amd64@www.freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean Subject: Re: FBSD 5.3RC1 on Fujitsu Siemens CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 09:56:57 -0000 It is sk driver that is causing system to reboot. I just did ifconfig sk0 down and ifconfig sk0 up and system rebooted with kernel panic message. Regards, Goran Gajic From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 11:02:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD3F916A4CE for ; Mon, 25 Oct 2004 11:02:02 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE13E43D49 for ; Mon, 25 Oct 2004 11:02:02 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i9PB22VB078209 for ; Mon, 25 Oct 2004 11:02:02 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9PB21eB078200 for freebsd-amd64@freebsd.org; Mon, 25 Oct 2004 11:02:01 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 25 Oct 2004 11:02:01 GMT Message-Id: <200410251102.i9PB21eB078200@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 11:02:02 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z 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/04] amd64/72333 amd64 vinum doesn't scan for drives on slices o 6 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/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/09/12] amd64/71674 amd64 static libraries cannot be linked when bu o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 o [2004/09/30] amd64/72213 amd64 No vesa device o [2004/10/10] amd64/72493 amd64 CD-Image of amd64-5.3-BETA6 missing files o [2004/10/11] amd64/72517 amd64 Minor Bug in /etc/login.access 11 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 12:00:57 2004 Return-Path: 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 6E4E316A517 for ; Mon, 25 Oct 2004 12:00:57 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E9F643D48 for ; Mon, 25 Oct 2004 12:00:57 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9PC0vhe087183 for ; Mon, 25 Oct 2004 12:00:57 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9PC0v0h087177; Mon, 25 Oct 2004 12:00:57 GMT (envelope-from gnats) Resent-Date: Mon, 25 Oct 2004 12:00:57 GMT Resent-Message-Id: <200410251200.i9PC0v0h087177@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ville-Pertti Keinonen Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C51516A4CE for ; Mon, 25 Oct 2004 11:53:25 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 408F643D48 for ; Mon, 25 Oct 2004 11:53:25 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i9PBrPnU026370 for ; Mon, 25 Oct 2004 11:53:25 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i9PBrPUf026369; Mon, 25 Oct 2004 11:53:25 GMT (envelope-from nobody) Message-Id: <200410251153.i9PBrPUf026369@www.freebsd.org> Date: Mon, 25 Oct 2004 11:53:25 GMT From: Ville-Pertti Keinonen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73111: Optimized libc string functions missing for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 12:00:57 -0000 >Number: 73111 >Category: amd64 >Synopsis: Optimized libc string functions missing for amd64 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Oct 25 12:00:56 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Ville-Pertti Keinonen >Release: 6.0-current >Organization: >Environment: >Description: Using optimized assembly language versions of string functions on amd64 (this is already done on other architectures) would probably be a good idea. Functions adapted from NetBSD (which can be extracted into /usr/src for inclusion in a buildworld) are available at the following URL: http://will.iki.fi/patches/libc-amd64-string.tar.gz I mentioned the issue on -current, but this didn't result in any discussion. The NetBSD functions may or may not all be desirable in their current form; some of the functions have extensive unrolling and may produce a performance penalty for short strings (but a huge advantage for longer ones). >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 17:00:28 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1865B16A4CF for ; Mon, 25 Oct 2004 17:00:28 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E478743D31 for ; Mon, 25 Oct 2004 17:00:27 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 6052 invoked from network); 25 Oct 2004 17:00:27 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Oct 2004 17:00:27 -0000 Received: from hydrogen.funkthat.com (dixgpk@localhost.funkthat.com [127.0.0.1])i9PH0Plb069484; Mon, 25 Oct 2004 10:00:26 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i9PH0PjA069483; Mon, 25 Oct 2004 10:00:25 -0700 (PDT) Date: Mon, 25 Oct 2004 10:00:25 -0700 From: John-Mark Gurney To: Goran Gajic Message-ID: <20041025170025.GC22681@funkthat.com> Mail-Followup-To: Goran Gajic , freebsd-amd64@www.freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-amd64@www.freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemens CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 17:00:28 -0000 Goran Gajic wrote this message on Mon, Oct 25, 2004 at 11:56 +0200: > It is sk driver that is causing system to reboot. I just did ifconfig sk0 > down and ifconfig sk0 up and system rebooted with kernel panic message. Well, it's good to here that you know what triggers the problem.. unless you provide us with the panic message, there is nothing we can do to help you... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 17:10:21 2004 Return-Path: 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 BAEE016A4CE for ; Mon, 25 Oct 2004 17:10:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A2043D31 for ; Mon, 25 Oct 2004 17:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9PHALR6027883 for ; Mon, 25 Oct 2004 17:10:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9PHALGX027882; Mon, 25 Oct 2004 17:10:21 GMT (envelope-from gnats) Date: Mon, 25 Oct 2004 17:10:21 GMT Message-Id: <200410251710.i9PHALGX027882@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John-Mark Gurney Subject: Re: amd64/73111: Optimized libc string functions missing for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 17:10:21 -0000 The following reply was made to PR amd64/73111; it has been noted by GNATS. From: John-Mark Gurney To: Ville-Pertti Keinonen Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/73111: Optimized libc string functions missing for amd64 Date: Mon, 25 Oct 2004 10:03:20 -0700 Ville-Pertti Keinonen wrote this message on Mon, Oct 25, 2004 at 11:53 +0000: > >Description: > Using optimized assembly language versions of string functions on amd64 (this is already done on other architectures) would probably be a good idea. > > Functions adapted from NetBSD (which can be extracted into /usr/src for inclusion in a buildworld) are available at the following URL: > http://will.iki.fi/patches/libc-amd64-string.tar.gz > > I mentioned the issue on -current, but this didn't result in any discussion. > > The NetBSD functions may or may not all be desirable in their current form; some of the functions have extensive unrolling and may produce a performance penalty for short strings (but a huge advantage for longer ones). Have you run some benchmarks to validate that the assembly optimized code is faster than the c generated? if you need help analyzing the benchmark numbers, look at ministat in src/tools/tools/ministat... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 18:39:28 2004 Return-Path: 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 C39A816A4CE; Mon, 25 Oct 2004 18:39:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A476643D46; Mon, 25 Oct 2004 18:39:28 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) i9PIdSON035400; Mon, 25 Oct 2004 18:39:28 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9PIdSjx035396; Mon, 25 Oct 2004 18:39:28 GMT (envelope-from obrien) Date: Mon, 25 Oct 2004 18:39:28 GMT From: "David E. O'Brien" Message-Id: <200410251839.i9PIdSjx035396@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, obrien@FreeBSD.org Subject: Re: amd64/73111: Optimized libc string functions missing for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 18:39:28 -0000 Synopsis: Optimized libc string functions missing for amd64 Responsible-Changed-From-To: freebsd-amd64->obrien Responsible-Changed-By: obrien Responsible-Changed-When: Mon Oct 25 18:39:12 GMT 2004 Responsible-Changed-Why: I've got some input from AMD on these. http://www.freebsd.org/cgi/query-pr.cgi?pr=73111 From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 25 18:51:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F7E016A4CE for ; Mon, 25 Oct 2004 18:51:40 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37F3543D41 for ; Mon, 25 Oct 2004 18:51:40 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9PIpdir034225; Mon, 25 Oct 2004 11:51:39 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9PIpcW0034223; Mon, 25 Oct 2004 11:51:38 -0700 (PDT) (envelope-from obrien) Date: Mon, 25 Oct 2004 11:51:38 -0700 From: "David O'Brien" To: Adriaan de Groot Message-ID: <20041025185138.GA34116@dragon.nuxi.com> References: <200410232339.02777.groot@kde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410232339.02777.groot@kde.org> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemenes CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 18:51:40 -0000 On Sat, Oct 23, 2004 at 11:39:02PM +0200, Adriaan de Groot wrote: > On Saturday 23 October 2004 23:13, Goran Gajic wrote: > > I have installed FreeBSD 5.3RC1 on Fujitsu Siemenes Celsius. First problem > > I had was with sk0. It stops responding and all I can do is ifconfig sk0 > > down and then ifconfig sk0 up to reset it. Second, server reboots without > > Have you any idea what motherboard is in there? It is a Tyan K8W (s2885) motherboard with a custom Phoenix-based BIOS (vs. the Tyan channel boards which have AMI BIOS). -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 11:50:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CB5916A4CE; Tue, 26 Oct 2004 11:50:19 +0000 (GMT) Received: from cannabis.dataforce.net (cannabis.dataforce.net [195.42.160.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CB2243D3F; Tue, 26 Oct 2004 11:50:16 +0000 (GMT) (envelope-from georgi@cannabis.dataforce.net) Received: (from georgi@localhost) by cannabis.dataforce.net (8.11.6p2-DF11/8.8.8) id i9QBo9M04691; Tue, 26 Oct 2004 15:50:09 +0400 Date: Tue, 26 Oct 2004 14:50:41 +0300 From: Georgi Guninski To: freebsd-amd64@FreeBSD.org Message-ID: <20041026115041.GE2841@sivokote.iziade.m$> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline header: best read with a sniffer User-Agent: Mutt/1.5.5.1i cc: roam@FreeBSD.org Subject: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 11:50:19 -0000 on a freebsd amd64 box with more than 8GB swap i experience the following: amdkotef64# uname -a FreeBSD amdkotef64.localdomain 5.3-BETA6 FreeBSD 5.3-BETA6 #0: Sat Sep 25 21:49:38 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC amd64 amdkotef64# amdkotef64# cat test.c #include int main(int ac, char **av) { char *a, *b; size_t siz; siz=4L*1024L*1024L*1024L; printf("%lx\n",siz); a=malloc(siz); printf("%lx\n",a); b=malloc(siz); printf("%lx\n",b); } amdkotef64# gcc test.c amdkotef64# ./a.out 100000000 503000 /: write failed, filesystem is full Segmentation fault amdkotef64# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s3a 3.8G 3.7G -236M 107% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s3d 4.7G 34K 4.3G 0% /home amdkotef64# du -h a.out.core 2.5G a.out.core amdkotef64# From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 12:47:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C259B16A4CE; Tue, 26 Oct 2004 12:47:11 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DEB843D39; Tue, 26 Oct 2004 12:47:10 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QCl79S027088; Tue, 26 Oct 2004 14:47:08 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E474A.1000401@withagen.nl> Date: Tue, 26 Oct 2004 14:47:06 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Georgi Guninski References: <20041026115041.GE2841@sivokote.iziade.m$> In-Reply-To: <20041026115041.GE2841@sivokote.iziade.m$> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: roam@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 12:47:11 -0000 Georgi Guninski wrote: > on a freebsd amd64 box with more than 8GB swap i experience the following: > > amdkotef64# uname -a > FreeBSD amdkotef64.localdomain 5.3-BETA6 FreeBSD 5.3-BETA6 #0: Sat Sep 25 > 21:49:38 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC > amd64 > amdkotef64# > > amdkotef64# cat test.c > #include > > int main(int ac, char **av) > { > char *a, *b; > size_t siz; > siz=4L*1024L*1024L*1024L; > printf("%lx\n",siz); > a=malloc(siz); > printf("%lx\n",a); > b=malloc(siz); > printf("%lx\n",b); > } > amdkotef64# gcc test.c > amdkotef64# ./a.out > 100000000 > 503000 > /: write failed, filesystem is full > Segmentation fault These 2 lines stem from the fact that the program is being dumped and there is not enough space to dump the full size core of that program. what does swapinfo tell you during the the run of the program??? I ran malloc tests in 4Gb with 5Gb of swap, which it nicely completely filled, and then in faulted, because there was no more space. This behaviour can be set, I think. Check man 5 malloc.conf, and check /etc/malloc.conf to see if you've got the X-flag on. I have malloc.conf-> aj, and the program terminates in 3 seconds because it does not zero the memory. So pick and choose the behaviour you want. --WjW > amdkotef64# df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s3a 3.8G 3.7G -236M 107% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/ad0s3d 4.7G 34K 4.3G 0% /home > amdkotef64# du -h a.out.core > 2.5G a.out.core > amdkotef64# From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:13:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0F6D16A4CE for ; Tue, 26 Oct 2004 13:13:41 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 827F743D45 for ; Tue, 26 Oct 2004 13:13:36 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QDDG9S027974; Tue, 26 Oct 2004 15:13:27 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E4D6C.4040508@withagen.nl> Date: Tue, 26 Oct 2004 15:13:16 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Pentchev References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> In-Reply-To: <20041026125709.GF1003@straylight.m.ringlet.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Georgi Guninski cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:13:42 -0000 Peter Pentchev wrote: > On Tue, Oct 26, 2004 at 02:47:06PM +0200, Willem Jan Withagen wrote: > >>Georgi Guninski wrote: >> >> >>>on a freebsd amd64 box with more than 8GB swap i experience the following: > > [snip] > >>>amdkotef64# cat test.c > > [snip 2 * 4GB malloc] > >>>amdkotef64# gcc test.c >>>amdkotef64# ./a.out >>>100000000 >>>503000 >> >>>/: write failed, filesystem is full >>>Segmentation fault >> >>These 2 lines stem from the fact that the program is being dumped and there >>is not enough space to dump the full size core of that program. >> >>what does swapinfo tell you during the the run of the program??? >> >>I ran malloc tests in 4Gb with 5Gb of swap, which it nicely completely >>filled, and then in faulted, because there was no more space. >>This behaviour can be set, I think. Check man 5 malloc.conf, and check >>/etc/malloc.conf to see if you've got the X-flag on. > > > But shouldn't malloc() write out an 'out of memory' message before the > core dump then? There's no such message in Georgi's output. That depends on the flags set with malloc.conf. The X-flag tells you how errors are handled. But you are right, it is strange: malloc should either return 0, or give a warning. I think that std-malloc settings were AX for anything before -STABLE. > It's true that when he asked me on Saturday about this, I completely > forgot about malloc's X flag, but I don't think he's using it, and even > if he were, there ought to be a message there. That's why I send him to the man-page. He could even force the settings in the testprogram. And check the link!!! it is probably set to something, or something is assumed. So better be safe and force it one-selves. Could be that the message does not arrive because the out-of-mem trap killed it first.... ??? Perhaps also check /var/log/messages. I remember seeing things there as well. >>I have malloc.conf-> aj, and the program terminates in 3 seconds because it >>does not zero the memory. >> >>So pick and choose the behaviour you want. > > > Sure, the question is if this is the result of 'X' or something else :) Well given the fact that there are not yet that many big boxes, let alone people really wanting to allocate a 4Gb blob, I'm not going to bet the usual case of beer on it. :~) --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:36:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 969EB16A4CE for ; Tue, 26 Oct 2004 13:36:25 +0000 (GMT) Received: from cannabis.dataforce.net (cannabis.dataforce.net [195.42.160.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8790643D48 for ; Tue, 26 Oct 2004 13:36:24 +0000 (GMT) (envelope-from georgi@cannabis.dataforce.net) Received: (from georgi@localhost) by cannabis.dataforce.net (8.11.6p2-DF11/8.8.8) id i9QDaI027892; Tue, 26 Oct 2004 17:36:18 +0400 Date: Tue, 26 Oct 2004 16:36:51 +0300 From: Georgi Guninski To: Peter Pentchev Message-ID: <20041026133651.GF2841@sivokote.iziade.m$> References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026133002.GG1003@straylight.m.ringlet.net> header: best read with a sniffer User-Agent: Mutt/1.5.5.1i cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:36:25 -0000 On Tue, Oct 26, 2004 at 04:30:02PM +0300, Peter Pentchev wrote: > > Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or > a /etc/malloc.conf symlink? > don't have neither. default install. iirc the problem is also in 5.2. georgi From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:42:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22B8416A4CE for ; Tue, 26 Oct 2004 13:42:13 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 714EE43D3F for ; Tue, 26 Oct 2004 13:42:12 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QDgA9S029045; Tue, 26 Oct 2004 15:42:11 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E5432.1070004@withagen.nl> Date: Tue, 26 Oct 2004 15:42:10 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Pentchev References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> In-Reply-To: <20041026133002.GG1003@straylight.m.ringlet.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Georgi Guninski cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:42:13 -0000 Peter Pentchev wrote: [snip] >>>>>on a freebsd amd64 box with more than 8GB swap i experience the >>>>>following: This is of course where strange things start. This should not be possible when al things are as suggested. 2*4G allocs should work. [more snip] >>>>what does swapinfo tell you during the the run of the program??? So what that tell you... BTW. I ran the program with 3*2Gb alloc (I got 4GB and 5Gb swap) malloc.conf -> XZ => Give text warnings, and zero everything But still I get: [/tmp] root@opteron> ./a.out 80000000 503000 80503000 100503000 And no further text. So this is consistent with previous findings that the text gets lost somewhere... But it does not dump core??? where X would tell it to do so. > I looked at the source before posting that - src/lib/libc/stdlib/malloc.c, > and the handling of malloc_xmalloc invokes wrterror(), which writes to > stderr before aborting. Oke, should be correct then? >>I think that std-malloc settings were AX for anything before -STABLE. > Actually they were 'AJ', not 'AX', and they were turned off on Sep 7 for > RELENG_5. Georgi's uname shows 5.3-BETA6, which was cut about Sep 23, > so neither 'J' nor 'X' ought to be set by default. could very well be so. > Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or > a /etc/malloc.conf symlink? I've found that settings not always worked the way I fully expected them. Still got a test for 0xdeaddead in a program which explicitly sets Z in its malloc-settings --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:45:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60F3516A4D0 for ; Tue, 26 Oct 2004 13:45:40 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6F4E43D54 for ; Tue, 26 Oct 2004 13:45:39 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QDjc9S029208; Tue, 26 Oct 2004 15:45:38 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E5501.2090909@withagen.nl> Date: Tue, 26 Oct 2004 15:45:37 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Georgi Guninski References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> <20041026133651.GF2841@sivokote.iziade.m$> In-Reply-To: <20041026133651.GF2841@sivokote.iziade.m$> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Peter Pentchev cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:45:40 -0000 Georgi Guninski wrote: > On Tue, Oct 26, 2004 at 04:30:02PM +0300, Peter Pentchev wrote: > >>Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or >>a /etc/malloc.conf symlink? >> > > > don't have neither. > default install. > iirc the problem is also in 5.2. Running it on a small box: [/tmp] root@files> ln -s AXZ /etc/malloc.conf [/tmp] root@files> ./a.out 80000000 a.out in malloc(): error: out of memory Abort (core dumped) [/tmp] root@files> uname -a FreeBSD files.digiware.nl 5.1-RELEASE-p11 FreeBSD 5.1-RELEASE-p11 #3: Sat Dec 20 16:16:35 CET 2003 root@freebee.digiware.nl:/mnt2/obj/u sr/src51/src/sys/GENERIC i386 so there it works as expected... --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:51:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06C7A16A4CE for ; Tue, 26 Oct 2004 13:51:26 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 076BC43D45 for ; Tue, 26 Oct 2004 13:51:25 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QDpN9S029412; Tue, 26 Oct 2004 15:51:23 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E565A.5010009@withagen.nl> Date: Tue, 26 Oct 2004 15:51:22 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Georgi Guninski References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> <20041026133651.GF2841@sivokote.iziade.m$> In-Reply-To: <20041026133651.GF2841@sivokote.iziade.m$> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Peter Pentchev cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:51:26 -0000 Georgi Guninski wrote: > On Tue, Oct 26, 2004 at 04:30:02PM +0300, Peter Pentchev wrote: > >>Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or >>a /etc/malloc.conf symlink? >> > > > don't have neither. > default install. > iirc the problem is also in 5.2. And again on a 5.2 i386 box: [/tmp] root@freebee> a.out 80000000 a.out in malloc(): error: allocation failed Abort (core dumped) [/tmp] root@freebee> ll /etc/malloc.conf ls: /etc/malloc.conf: No such file or directory [/tmp] root@freebee> ln -s AXZ /etc/malloc.conf [/tmp] root@freebee> a.out 80000000 a.out in malloc(): error: allocation failed Abort (core dumped) [/tmp] root@freebee> uname -a FreeBSD freebee.digiware.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Fri Jul 9 18:44:14 CEST 2004 root@freebee.digiware.nl:/usr/obj/usr/src5/src/sys/FREEBEE i386 Which is all as expected. But I don't have i386-CURRENT other AMD64 releases around. --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 14:11:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61B2216A4D1 for ; Tue, 26 Oct 2004 14:11:13 +0000 (GMT) Received: from cannabis.dataforce.net (cannabis.dataforce.net [195.42.160.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6456243D45 for ; Tue, 26 Oct 2004 14:11:12 +0000 (GMT) (envelope-from georgi@cannabis.dataforce.net) Received: (from georgi@localhost) by cannabis.dataforce.net (8.11.6p2-DF11/8.8.8) id i9QEB7514277; Tue, 26 Oct 2004 18:11:07 +0400 Date: Tue, 26 Oct 2004 17:11:38 +0300 From: Georgi Guninski To: Willem Jan Withagen Message-ID: <20041026141138.GG2841@sivokote.iziade.m$> References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> <20041026133651.GF2841@sivokote.iziade.m$> <417E565A.5010009@withagen.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417E565A.5010009@withagen.nl> header: best read with a sniffer User-Agent: Mutt/1.5.5.1i cc: Peter Pentchev cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 14:11:13 -0000 when i try to malloc a block more than the swap, malloc just returns 0 and i don't segfault. On Tue, Oct 26, 2004 at 03:51:22PM +0200, Willem Jan Withagen wrote: From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 14:28:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE39A16A4CE for ; Tue, 26 Oct 2004 14:28:16 +0000 (GMT) Received: from cannabis.dataforce.net (cannabis.dataforce.net [195.42.160.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D096E43D49 for ; Tue, 26 Oct 2004 14:28:15 +0000 (GMT) (envelope-from georgi@cannabis.dataforce.net) Received: (from georgi@localhost) by cannabis.dataforce.net (8.11.6p2-DF11/8.8.8) id i9QESAb16228; Tue, 26 Oct 2004 18:28:10 +0400 Date: Tue, 26 Oct 2004 17:28:43 +0300 From: Georgi Guninski To: Willem Jan Withagen Message-ID: <20041026142843.GH2841@sivokote.iziade.m$> References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> <20041026133651.GF2841@sivokote.iziade.m$> <417E565A.5010009@withagen.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417E565A.5010009@withagen.nl> header: best read with a sniffer User-Agent: Mutt/1.5.5.1i cc: Peter Pentchev cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 14:28:16 -0000 On Tue, Oct 26, 2004 at 03:51:22PM +0200, Willem Jan Withagen wrote: > > And again on a 5.2 i386 box: > [/tmp] root@freebee> a.out > 80000000 actually on i386 linux i get 0 and i don't crash at all. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 14:47:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B42516A4CE for ; Tue, 26 Oct 2004 14:47:21 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id A08CF43D31 for ; Tue, 26 Oct 2004 14:47:20 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QElE9S031269; Tue, 26 Oct 2004 16:47:14 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E6372.4080006@withagen.nl> Date: Tue, 26 Oct 2004 16:47:14 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Georgi Guninski References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> <20041026133651.GF2841@sivokote.iziade.m$> <417E565A.5010009@withagen.nl> <20041026142843.GH2841@sivokote.iziade.m$> In-Reply-To: <20041026142843.GH2841@sivokote.iziade.m$> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Peter Pentchev cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 14:47:21 -0000 Georgi Guninski wrote: > On Tue, Oct 26, 2004 at 03:51:22PM +0200, Willem Jan Withagen wrote: > >>And again on a 5.2 i386 box: >>[/tmp] root@freebee> a.out >>80000000 > > > actually on i386 linux i get 0 and i don't crash at all. facinating, but true... Willest compiling I get a warning of a overflow that 2G gives a wrap in long, but things are interpreted unsigned as far as I see. And that is because I changed your 4G to 2G, 'cause I only had 2Gb of mem and 5Gb of swap. Yours just really overflows to 0, I guess. eg. if the optimizer (or the code) calculates the expression from right to left, and *4 is done 'by shiftleft 2' you're left with an all-zeros... --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 17:28:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61EED16A4D0 for ; Tue, 26 Oct 2004 17:28:44 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 8DB1743D53 for ; Tue, 26 Oct 2004 17:28:43 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 26660 invoked by uid 513); 26 Oct 2004 17:28:48 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.59.39):. Processed in 0.307061 secs); 26 Oct 2004 17:28:48 -0000 Received: from unknown (HELO lobo.homeunix.org) (82.141.59.39) by dsl-mail.kamp.net with SMTP; 26 Oct 2004 17:28:47 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9QHUOjE001119 for ; Tue, 26 Oct 2004 19:30:26 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9QHUOQ8001118 for freebsd-amd64@freebsd.org; Tue, 26 Oct 2004 19:30:24 +0200 (CEST) (envelope-from ewinter) Date: Tue, 26 Oct 2004 19:30:24 +0200 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20041026173024.GB879@lobo.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i Subject: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:28:44 -0000 Hi there, how are MB's from Asus going with amd64, for example: ASUS K8V SE Deluxe 754 ATX ASUS K8N-E Deluxe 754 ATX that is with Lan card and sound, are they better then Gigabyte with Nvidea3 250? Any findings would be appreceated. Ernst From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 17:30:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BD3216A4CE; Tue, 26 Oct 2004 17:30:10 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4B9D43D5A; Tue, 26 Oct 2004 17:30:09 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9QHU8X8003228; Tue, 26 Oct 2004 10:30:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9QHU6uu003227; Tue, 26 Oct 2004 10:30:06 -0700 (PDT) (envelope-from obrien) Date: Tue, 26 Oct 2004 10:30:05 -0700 From: "David O'Brien" To: Georgi Guninski Message-ID: <20041026173005.GA2984@dragon.nuxi.com> References: <20041026115041.GE2841@sivokote.iziade.m$> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026115041.GE2841@sivokote.iziade.m$> User-Agent: Mutt/1.4.1i 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 cc: roam@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:30:10 -0000 On Tue, Oct 26, 2004 at 02:50:41PM +0300, Georgi Guninski wrote: > amdkotef64# cat test.c > #include > > int main(int ac, char **av) > { > char *a, *b; > size_t siz; > siz=4L*1024L*1024L*1024L; > printf("%lx\n",siz); > a=malloc(siz); > printf("%lx\n",a); > b=malloc(siz); > printf("%lx\n",b); > } > amdkotef64# gcc test.c > amdkotef64# ./a.out > 100000000 > 503000 > /: write failed, filesystem is full > Segmentation fault I don't know why you didn't take this to the next step to try to figure out what was going on.... # cc -g test.c # gdb a.out (gdb) run Starting program: /var/tmp/a.out 100000000 503000 Program received signal SIGSEGV, Segmentation fault. 0x0000000200503002 in ?? () from /libexec/ld-elf.so.1 (gdb) where now the output you get isn't but so helpful because you wind up in the middle of libc. So if you build libc with -g and don't strip the lib when installing it you get: (gdb) run Starting program: /var/tmp/a.out 4294967296 5255168 Program received signal SIGILL, Illegal instruction. 0x0000000200503000 in ?? () from /libexec/ld-elf.so.1 (gdb) where #0 0x0000000200503000 in ?? () from /libexec/ld-elf.so.1 #1 0x000000020069579d in map_pages (pages=8595189760) at /usr/src/lib/libc/stdlib/malloc.c:338 #2 0x0000000200695c19 in malloc_pages (size=1048576) at /usr/src/lib/libc/stdlib/malloc.c:572 #3 0x0000000200695f77 in imalloc (size=4294967296) at /usr/src/lib/libc/stdlib/malloc.c:740 #4 0x00000002006968ed in pubrealloc (ptr=0x0, size=4294967296, func=0x2006f8c88 " in malloc():") at /usr/src/lib/libc/stdlib/malloc.c:1128 #5 0x00000002006969d8 in malloc (size=8595189760) at /usr/src/lib/libc/stdlib/malloc.c:1152 #6 0x00000000004007b4 in main (ac=1, av=0x7fffffffe900) at test.c:11 malloc.c:map_pages() calls brk(2) and this is where it goes to la-la land. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 17:36:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2929A16A4CE for ; Tue, 26 Oct 2004 17:36:01 +0000 (GMT) Received: from beer.ux6.net (beer.ux6.net [64.62.253.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1345143D31 for ; Tue, 26 Oct 2004 17:36:01 +0000 (GMT) (envelope-from miha@ghuug.org) Received: from [64.62.253.84] (helo=m) by beer.ux6.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CMVEf-000Pks-VM; Tue, 26 Oct 2004 10:35:54 -0700 From: "Mikhail P." To: freebsd-amd64@freebsd.org, "Ernst W. Winter" Date: Tue, 26 Oct 2004 17:35:49 +0000 User-Agent: KMail/1.7 References: <20041026173024.GB879@lobo.homeunix.org> In-Reply-To: <20041026173024.GB879@lobo.homeunix.org> Organization: Ghana Unix Users Group MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410261735.49338.miha@ghuug.org> X-Spam-Score: -4.9 (----) X-Spam-Report: Spam detection software, running on the system "beer.ux6.net", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Tuesday 26 October 2004 17:30, Ernst W. Winter wrote: > Hi there, > > how are MB's from Asus going with amd64, for example: > > ASUS K8V SE Deluxe 754 ATX > > ASUS K8N-E Deluxe 754 ATX for the sk NIC.. [...] Content analysis details: (-4.9 points, 6.0 required) pts rule name description --------------------------------------------------1% [score: 0.0000] 0.0 UPPERCASE_25_50 message body is 25-50% uppercase Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: miha@ghuug.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:36:01 -0000 On Tuesday 26 October 2004 17:30, Ernst W. Winter wrote: > Hi there, > > how are MB's from Asus going with amd64, for example: > > ASUS K8V SE Deluxe 754 ATX > > ASUS K8N-E Deluxe 754 ATX I'm using ASUS K8V SE Deluxe. Works great for ~3 months now, except for the sk NIC.. regards, M. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 17:55:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E362616A4CE; Tue, 26 Oct 2004 17:55:07 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64FFA43D53; Tue, 26 Oct 2004 17:55:07 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.jrv.org [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id i9QHt62e029341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Oct 2004 12:55:06 -0500 (CDT) (envelope-from james@jrv.org) Message-ID: <417E8F7A.70009@jrv.org> Date: Tue, 26 Oct 2004 12:55:06 -0500 From: "James R. Van Artsalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20041026115041.GE2841@sivokote.iziade.m$> <20041026173005.GA2984@dragon.nuxi.com> In-Reply-To: <20041026173005.GA2984@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Georgi Guninski cc: roam@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:55:08 -0000 David O'Brien wrote: >malloc.c:map_pages() calls brk(2) and this is where it goes to la-la land. > > > The brk() kernel call is probably failing due to ulimit being exceeded and not anything mysterious. A few months ago I posted this bug in the libc brk(2) code - the stack is not balanced if the kernel returns an error. I'm not running current code at the moment but see if you brk.S has a stack issue at the err: label. Stick in this pop if so and report if malloc(3c) then returns NULL instead of crashing, then up your ulimit and try again and see if all works without error. --- lib/libc/amd64/sys/brk.S.~1~ Sat May 24 12:35:23 2003 +++ lib/libc/amd64/sys/brk.S Fri Apr 9 02:02:22 2004 @@ -78,6 +78,7 @@ popq %rdi ret err: + popq %rdi #ifdef PIC movq PIC_GOT(HIDENAME(cerror)),%rdx jmp *%rdx From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 18:03:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8233816A4CE; Tue, 26 Oct 2004 18:03:33 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F4A343D48; Tue, 26 Oct 2004 18:03:32 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QI3U9S038025; Tue, 26 Oct 2004 20:03:31 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E9173.90406@withagen.nl> Date: Tue, 26 Oct 2004 20:03:31 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20041026115041.GE2841@sivokote.iziade.m$> <20041026173005.GA2984@dragon.nuxi.com> In-Reply-To: <20041026173005.GA2984@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Georgi Guninski cc: roam@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 18:03:33 -0000 David O'Brien wrote: > On Tue, Oct 26, 2004 at 02:50:41PM +0300, Georgi Guninski wrote: > >>amdkotef64# cat test.c >>#include >> >>int main(int ac, char **av) >>{ >>char *a, *b; >>size_t siz; >>siz=4L*1024L*1024L*1024L; >>printf("%lx\n",siz); >>a=malloc(siz); >>printf("%lx\n",a); >>b=malloc(siz); >>printf("%lx\n",b); >>} >>amdkotef64# gcc test.c >>amdkotef64# ./a.out >>100000000 >>503000 >>/: write failed, filesystem is full >>Segmentation fault > > > I don't know why you didn't take this to the next step to try to figure > out what was going on.... > > # cc -g test.c > # gdb a.out > (gdb) run > Starting program: /var/tmp/a.out > 100000000 > 503000 > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000200503002 in ?? () from /libexec/ld-elf.so.1 > (gdb) where > > now the output you get isn't but so helpful because you wind up in the > middle of libc. So if you build libc with -g and don't strip the lib > when installing it you get: A man is never too old to learn.... Thanx for the education, perhaps too simple to think of. --WjW From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 18:08:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94D2A16A4D0 for ; Tue, 26 Oct 2004 18:08:23 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CE5A43D2F for ; Tue, 26 Oct 2004 18:08:23 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9QI84ev004439; Tue, 26 Oct 2004 11:08:04 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9QI83ef004436; Tue, 26 Oct 2004 11:08:03 -0700 (PDT) (envelope-from obrien) Date: Tue, 26 Oct 2004 11:08:03 -0700 From: "David O'Brien" To: "Ernst W. Winter" Message-ID: <20041026180803.GA4202@dragon.nuxi.com> References: <20041026173024.GB879@lobo.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026173024.GB879@lobo.homeunix.org> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 18:08:23 -0000 On Tue, Oct 26, 2004 at 07:30:24PM +0200, Ernst W. Winter wrote: > Hi there, > > how are MB's from Asus going with amd64, for example: > > ASUS K8V SE Deluxe 754 ATX > ASUS K8N-E Deluxe 754 ATX > > that is with Lan card and sound, are they better then Gigabyte with > Nvidea3 250? What chipset does these boards use? The rule of thumb is don't use the nVidia nForce3 chipet. I don't see so much different between board manufacturers as the chipsets used. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 18:14:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F4C616A4CE for ; Tue, 26 Oct 2004 18:14:11 +0000 (GMT) Received: from enggate.uwi.tt (enggate.uwi.tt [196.3.139.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id C235643D41 for ; Tue, 26 Oct 2004 18:14:10 +0000 (GMT) (envelope-from feisal@uwi.tt) Received: from localhost (localhost [127.0.0.1]) by enggate.uwi.tt (Postfix) with ESMTP id 8261C103F3 for ; Tue, 26 Oct 2004 14:13:04 -0400 (AST) Received: from enggate.uwi.tt ([127.0.0.1]) by localhost (bsd.eng.uwi.tt [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02123-03 for ; Tue, 26 Oct 2004 14:13:04 -0400 (AST) Received: from ldc.eng.uwi.tt (ldc.eng.uwi.tt [192.168.20.31]) by enggate.uwi.tt (Postfix) with ESMTP id 44818103EC for ; Tue, 26 Oct 2004 14:13:04 -0400 (AST) Received: from router.eng.uwi.tt (router.eng.uwi.tt [192.168.20.195]) by ldc.eng.uwi.tt (8.9.1/8.9.1) with ESMTP id NAA11416 for ; Tue, 26 Oct 2004 13:54:11 +0400 (GMT) Received: from router.eng.uwi.tt (localhost [127.0.0.1]) by router.eng.uwi.tt (Postfix) with SMTP id 3D8C15D for ; Tue, 26 Oct 2004 14:14:07 -0400 (AST) Date: Tue, 26 Oct 2004 14:14:07 -0400 From: Feisal Mohammed To: freebsd-amd64@freebsd.org Message-Id: <20041026141407.481d4f17.feisal@uwi.tt> In-Reply-To: <20041026180803.GA4202@dragon.nuxi.com> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> Organization: University of the West Indies X-Mailer: Sylpheed version 0.9.99 (GTK+ 1.2.10; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uwi.tt Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 18:14:11 -0000 On Tue, 26 Oct 2004 11:08:03 -0700 "David O'Brien" wrote: > On Tue, Oct 26, 2004 at 07:30:24PM +0200, Ernst W. Winter wrote: > > Hi there, > > > > how are MB's from Asus going with amd64, for example: > > > > ASUS K8V SE Deluxe 754 ATX > > ASUS K8N-E Deluxe 754 ATX > > > > that is with Lan card and sound, are they better then Gigabyte with > > Nvidea3 250? > > What chipset does these boards use? The rule of thumb is don't use the > nVidia nForce3 chipet. I don't see so much different between board > manufacturers as the chipsets used. > > -- > -- David (obrien@FreeBSD.org) Check the list archives, there was some discussion about the K8V SE Deluxe board. AFIK the only problem was with the onboard LAN card. -Feisal From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 18:17:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC7F516A4CE for ; Tue, 26 Oct 2004 18:17:44 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id D4FB643D3F for ; Tue, 26 Oct 2004 18:17:43 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 32054 invoked by uid 513); 26 Oct 2004 18:17:48 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.59.39):SA:0(-4.9/5.0):. Processed in 0.651179 secs); 26 Oct 2004 18:17:48 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.59.39) by dsl-mail.kamp.net with SMTP; 26 Oct 2004 18:17:48 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9QIJPqe001358; Tue, 26 Oct 2004 20:19:25 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9QIJPMd001357; Tue, 26 Oct 2004 20:19:25 +0200 (CEST) (envelope-from ewinter) Date: Tue, 26 Oct 2004 20:19:25 +0200 From: "Ernst W. Winter" To: "David O'Brien" Message-ID: <20041026181925.GA1234@lobo.homeunix.org> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026180803.GA4202@dragon.nuxi.com> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 18:17:44 -0000 On Tue, 26 Oct 2004, David O'Brien wrote: > On Tue, Oct 26, 2004 at 07:30:24PM +0200, Ernst W. Winter wrote: > > how are MB's from Asus going with amd64, for example: > > > > ASUS K8V SE Deluxe 754 ATX > > What chipset does these boards use? The rule of thumb is don't use > the nVidia nForce3 chipet. I don't see so much different between > board manufacturers as the chipsets used. > Well the above has a VIA K8T800 and that is why I think I might use it next. I have a Gigabyte GA-K8NS and running 5.3-STABLE. I bought it on the spur of the moment. Also I have a company that want a AMD64 754 and so I will use rather the ASUS then the Nvidea3 that is on the Gigabyte. At least I will keep away from it. Ernst From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 18:23:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE03816A4CE for ; Tue, 26 Oct 2004 18:23:49 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id F057F43D49 for ; Tue, 26 Oct 2004 18:23:48 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 4178 invoked by uid 513); 26 Oct 2004 18:23:53 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.59.39):SA:0(-4.9/5.0):. Processed in 0.711498 secs); 26 Oct 2004 18:23:53 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.59.39) by dsl-mail.kamp.net with SMTP; 26 Oct 2004 18:23:52 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9QIPPCq001414; Tue, 26 Oct 2004 20:25:25 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9QIPO8j001413; Tue, 26 Oct 2004 20:25:24 +0200 (CEST) (envelope-from ewinter) Date: Tue, 26 Oct 2004 20:25:24 +0200 From: "Ernst W. Winter" To: Feisal Mohammed Message-ID: <20041026182524.GB1234@lobo.homeunix.org> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026141407.481d4f17.feisal@uwi.tt> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 18:23:49 -0000 On Tue, 26 Oct 2004, Feisal Mohammed wrote: > On Tue, 26 Oct 2004 11:08:03 -0700 > "David O'Brien" wrote: > > > On Tue, Oct 26, 2004 at 07:30:24PM +0200, Ernst W. Winter wrote: > > > Hi there, > > > > > > how are MB's from Asus going with amd64, for example: > > > > > > ASUS K8V SE Deluxe 754 ATX > > > ASUS K8N-E Deluxe 754 ATX > > > > > > that is with Lan card and sound, are they better then Gigabyte with > > > Nvidea3 250? > > > > What chipset does these boards use? The rule of thumb is don't use the > > nVidia nForce3 chipet. I don't see so much different between board > > manufacturers as the chipsets used. > > > > -- > > -- David (obrien@FreeBSD.org) > Check the list archives, there was some discussion about the K8V SE > Deluxe board. AFIK the only problem was with the onboard LAN card. > Thanks, the same has happen with the Nvidea3 250 I have here with a Gigabyte MB, so I think I rather will use the ASUS again as I had good experience with them all the time so far as well I will have to put a box together for a customer that want a AMD64/754 with FreeBSD. I have a Lancard in mine now and it works ok, but no sound. Ernst From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 21:32:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A52116A4CE; Tue, 26 Oct 2004 21:32:31 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24CDB43D53; Tue, 26 Oct 2004 21:32:31 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9QLWTUT095078; Tue, 26 Oct 2004 14:32:29 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9QLWRGu095077; Tue, 26 Oct 2004 14:32:27 -0700 (PDT) (envelope-from obrien) Date: Tue, 26 Oct 2004 14:32:27 -0700 From: "David O'Brien" To: "James R. Van Artsalen" Message-ID: <20041026213227.GA95016@dragon.nuxi.com> References: <20041026115041.GE2841@sivokote.iziade.m$> <20041026173005.GA2984@dragon.nuxi.com> <417E8F7A.70009@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417E8F7A.70009@jrv.org> User-Agent: Mutt/1.4.1i 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 cc: Georgi Guninski cc: roam@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 21:32:31 -0000 On Tue, Oct 26, 2004 at 12:55:06PM -0500, James R. Van Artsalen wrote: > David O'Brien wrote: > > >malloc.c:map_pages() calls brk(2) and this is where it goes to la-la land. > > > > > > > The brk() kernel call is probably failing due to ulimit being exceeded > and not anything mysterious. # ulimit -a | grep virt virtual memory (kbytes, -v) unlimited BTW, a statically built binary (ie, using libc.a) just hangs in the brk(2) call. > A few months ago I posted this bug in the libc brk(2) code - the stack > is not balanced if the kernel returns an error. I'm not running current > code at the moment but see if you brk.S has a stack issue at the err: > label. Stick in this pop if so and report if malloc(3c) then returns > NULL instead of crashing, then up your ulimit and try again and see if > all works without error. > > --- lib/libc/amd64/sys/brk.S.~1~ Sat May 24 12:35:23 2003 > +++ lib/libc/amd64/sys/brk.S Fri Apr 9 02:02:22 2004 > @@ -78,6 +78,7 @@ > popq %rdi > ret > err: > + popq %rdi > #ifdef PIC > movq PIC_GOT(HIDENAME(cerror)),%rdx > jmp *%rdx Today's code has: err: addq $8, %rsp #ifdef PIC movq PIC_GOT(HIDENAME(cerror)),%rdx jmp *%rdx so the stack should be OK. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 21:50:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9895116A4CE for ; Tue, 26 Oct 2004 21:50:52 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 347C243D5C for ; Tue, 26 Oct 2004 21:50:51 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.92] [213.112.167.92]) by mxfep02.bredband.com with ESMTP id <20041026215050.WLSM44.mxfep02.bredband.com@[192.168.245.231]>; Tue, 26 Oct 2004 23:50:50 +0200 Message-ID: <417EC623.6090900@bredband.net> Date: Tue, 26 Oct 2004 23:48:19 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ernst W. Winter" References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> <20041026182524.GB1234@lobo.homeunix.org> In-Reply-To: <20041026182524.GB1234@lobo.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 21:50:52 -0000 Ernst W. Winter wrote: > Thanks, the same has happen with the Nvidea3 250 I have here with a > Gigabyte MB, so I think I rather will use the ASUS again as I had > good experience with them all the time so far as well I will have to > put a box together for a customer that want a AMD64/754 with FreeBSD. > I have a Lancard in mine now and it works ok, but no sound. Hi, The advice I usually give these days is : Forget socket 754 - buy socket 939. Its faster with it's DUAL DIMM 128 bit memorybus. Its also the future, the New AMD Athlon64 4000+ and the FX-55 are both socket 939. Avoid the current batch of ASUS boards for FreeBSD. Most of them have Either or Both of the NVIDIA Nforce3 chipsets and the Marvel Yukon sk0 Ethernet chip. I bought the MSI K8T Neo2 FIR. with K8T800-PRO chipset and Realtek re0 Gigabit chip. works beautifully . Does a seti@home workunit in 2 hours and 15 minutes, with the Athlon64 3800+ CPU. Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 21:52:59 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69C2E16A4CE for ; Tue, 26 Oct 2004 21:52:59 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2F8043D1F for ; Tue, 26 Oct 2004 21:52:58 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id i9QLqrgD061153 for ; Tue, 26 Oct 2004 23:52:53 +0200 (CEST) Date: Tue, 26 Oct 2004 23:52:53 +0200 (CEST) From: Goran Gajic To: freebsd-amd64@www.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean Subject: FBSD 5.3RC1 on Fujitsu Siemenes CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 21:52:59 -0000 Kernel is GENERIC. This is message I got from serial console. Sorry it took so much time to post it. Hope this helps. Regards, Goran Gajic p.s. until I haven't used sk everything was ok. since I have switched to sk0 and few times did ifconfig sk0 down; ifconfig sk0 up system crashed Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff803a0d73 stack pointer = 0x10:0xffffffffb2ee37e0 frame pointer = 0x10:0x0 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 = 44 (swi1: net) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 11h20m35s Dumping 3327 MB From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 22:04:30 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58E7B16A4CE for ; Tue, 26 Oct 2004 22:04:30 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D6643D1D for ; Tue, 26 Oct 2004 22:04:29 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id i9QM47gD003057 for ; Wed, 27 Oct 2004 00:04:07 +0200 (CEST) Date: Wed, 27 Oct 2004 00:04:06 +0200 (CEST) From: Goran Gajic To: freebsd-amd64@www.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean Subject: FBSD 5.3RC1 on Fujitsu Siemenes CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 22:04:30 -0000 Why kernel was unable to dump to swap partition? I have hoped that I could use dump to debug and send report to mailing list as described in developers handbook. I have 4096 MB RAM and 4096MB swap partition. This in /etc/rc.conf: dumpdev="/dev/aacd0s1b" dumpdir="/var/crash" and this is my /etc/fstab: # Device Mountpoint FStype Options Dump Pass# /dev/aacd0s1b none swap sw 0 0 /dev/aacd0s1a / ufs rw 1 1 /dev/aacd0s1g /home ufs rw 2 2 /dev/aacd0s1f /tmp ufs rw 2 2 /dev/aacd0s1d /usr ufs rw 2 2 /dev/aacd0s1e /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/aacd0s1b is 4MB. Regards, Goran Gajic Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff803a0d73 stack pointer = 0x10:0xffffffffb2ee37e0 frame pointer = 0x10:0x0 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 = 44 (swi1: net) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 11h20m35s Dumping 3327 MB 16 32Error dumping block 0x0 Dump failed writing data (5) Dump complete aac0: shutting down controller...done Shutting down ACPI Akernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kerneul mode cpuid = 0; apic id = 00 fault virtual address = 0x98 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff8018240e stack pointer = 0x10:0xffffffffb2df9b30 frame pointer = 0x10:0x1 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (idle: ctomatpu0) trap number = 12 ic reboot in 15 seconds - press a key on the console to abort Rebooting... From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 01:53:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 741C016A4CE for ; Wed, 27 Oct 2004 01:53:28 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 196A243D49 for ; Wed, 27 Oct 2004 01:53:21 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CMd2Y-000HHc-6L for freebsd-amd64@freebsd.org; Wed, 27 Oct 2004 09:55:55 +0800 Message-Id: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Wed, 27 Oct 2004 09:52:58 +0900 To: freebsd-amd64@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Subject: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 01:53:28 -0000 Hi, I still have problem running FreeBSD 5.3 with 8GB RAM on Dual amd64 2.2GHz (IBM @server 325, ServeRAID 6M) with 8GB RAM. I did cvsup and updated (made world, kernel) to latest using RELENG_5_3 tag. It was working ok with 4 GB RAM. Afterwards I added another 4GB RAM and=20 tried to boot FreeBSD with 8GB RAM. However it showed various errors and login didn't work. You=20 can see serial console messages at the end of my email. What should I do? I really want to run this machine with 8GB RAM. Any ideas? Errors were something like: --------------------------------------------------------------------- Starting sshd /libexec/ld.elf.so.1: Cannot fstat "/usr/lib/libssh.so.2" Starting inetd /libexec/ld.elf.so.1: Cannot fstat "/usr/lib/libwrap.so.3" login: root Oct 14:31:25 amd getty[428]: /usr/bin/login: Permission denied --------------------------------------------------------------------- I built and installed latest kernel of RELENG_5_3 tag with following=20 debugging options in kernel config file. ----------------------------------------------------------------------------= ---------------------------------- makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug= symbols options WITNESS options WITNESS_KDB options WITNESS_SKIPSPIN options KDB options KDB_TRACE options DDB options DDB_NUMSYM options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC ----------------------------------------------------------------------------= ------------------------------------------ Following is the messages I got from serial console, first part is with 4GB= =20 RAM, second part is with 8GB RAM: ############################################################################= ################# Console: serial port BIOS drive C: is disk0 BIOS 614kB/4127168kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (tsgan@amd.micom.mng.net, Mon Oct 25 18:56:14 ULAT 2004) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=3D0x30e580 -data=3D0x7ec58+0x77db8=20 -syms=3D[0x8+0x5c538+0x8+0x4e56d-] KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #4: Tue Oct 26 13:39:47 ULAT 2004 tsgan@amd.micom.mng.net:/usr/obj/usr/src/sys/AMD WARNING: WITNESS option enabled, expect reduced performance. WARNING: DIAGNOSTIC option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.18-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf58 Stepping =3D 8 = Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 4227268608 (4031 MB) avail memory =3D 4082835456 (3893 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff= =20 iomem 0xd8000-0xdbfff on acpi0 pcib0: could not get PCI interrupt routing table for \_SB_.PCI0 -= AE_NOT_FOUND pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfc100000-0xfc100fff irq 19 at= =20 device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfc101000-0xfc101fff irq 19 at= =20 device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ukbd0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 uhid0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port=20 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem=20 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge0: Ethernet address: 00:0d:60:14:cc:9e bge1: mem=20 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at device 1.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge1: Ethernet address: 00:0d:60:14:cc:9f pci2: at device 2.0 (no driver attached) pci0: at device 10.1 (no driver=20 attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 3.0 on pci3 pci4: on pcib4 ips0: mem 0xfe100000-0xfe100fff irq 28 at=20 device 8.0 on pci4 ips0: [GIANT-LOCKED] pci0: at device 11.1 (no driver=20 attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on= acpi0 sio0: type 16550A, console orm0: at iomem=20 0xcb000-0xcb7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec acd0: CDROM at ata1-master UDMA33 ips0: adapter type: ServeRAID 6M (marco) ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 355481600, state OK ipsd0: on ips0 ipsd0: Logical Drive (173575MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ipsd0s1b as swap device Starting file system checks: /dev/ipsd0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1a: clean, 479984 free (704 frags, 59910 blocks, 0.1%= fragmentation) /dev/ipsd0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1f: clean, 1003939 free (59 frags, 125485 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1d: clean, 8989787 free (49579 frags, 1117526 blocks, 0.5%=20 fragmentation) /dev/ipsd0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1e: clean, 4997667 free (275 frags, 624674 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1g: clean, 65656968 free (392 frags, 8207072 blocks, 0.0%=20 fragmentation) Setting hostname: amd.micom.mng.net. bge0: flags=3D8843 mtu 1500 options=3D1a inet 192.168.0.50 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:0d:60:14:cc:9e media: Ethernet 100baseTX status: no carrier lo0: flags=3D8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 192.168.0.1 Additional routing options:. Starting devd. kbdcontrol: cannot open /dev/kbd1: Device busy Mounting NFS file systems:. Starting syslogd. Oct 26 14:15:10 amd syslogd: kernel boot file is /boot/kernel/kernel ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib= /usr/local/lib Starting usbd. Starting local daemons:. Updating motd. Configuring syscons: font8x16 font8x8 blanktime=20 screensavermodule_register_init: MOD_LOAD (logo_saver, 0xffffffffb63c1430,= =20 0) error 19 . Starting sshd. Oct 26 14:15:11 amd kernel: logo_saver: the console does not support=20 M_VGA_CG320 Initial amd64 initialization:. Additional ABI support:. Starting cron. Local package initialization:Expensive timeout(9) function:=20 0xffffffff801a91e0(0xffffffff80825000) 0.002224584 s mysqld. Additional TCP options:. Starting inetd. Starting background file system checks in 60 seconds. Tue Oct 26 14:15:12 ULAT 2004 =E0Stopping inetd. Shutting down daemon processes: mysqld. Stopping cron. Shutting down local daemons:. Writing entropy file:. . Oct 26 14:16:52 amd syslogd: exiting on signal 15 boot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...2 2 2 2 0 0 done No buffers busy after final sync Uptime: 1m56s ips0: flushing cache Shutting down ACPI The operating system has halted. Please press any key to reboot. ############################################################################= ################# Console: serial port BIOS drive C: is disk0 BIOS 614kB/4127168kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (tsgan@amd.micom.mng.net, Mon Oct 25 18:56:14 ULAT 2004) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=3D0x30e580 -data=3D0x7ec58+0x77db8=20 --=08syms=3D[0x8+0x5c538+0x8+0x4e56d-] KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #4: Tue Oct 26 13:39:47 ULAT 2004 tsgan@amd.micom.mng.net:/usr/obj/usr/src/sys/AMD WARNING: WITNESS option enabled, expect reduced performance. WARNING: DIAGNOSTIC option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.18-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf58 Stepping =3D 8 = Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 8589934592 (8192 MB) avail memory =3D 8249974784 (7867 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff= =20 iomem 0xd8000-0xdbfff on acpi0 pcib0: could not get PCI interrupt routing table for \_SB_.PCI0 -= AE_NOT_FOUND pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfc100000-0xfc100fff irq 19 at= =20 device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfc101000-0xfc101fff irq 19 at= =20 device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ukbd0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 uhid0: Silitek IBM USB Keyboard, rev 1.10/1.00, addr 2, iclass 3/1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port=20 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem=20 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge0: Ethernet address: 00:0d:60:14:cc:9e bge1: mem=20 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at device 1.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,=20 1000baseTX-FDX, auto bge1: Ethernet address: 00:0d:60:14:cc:9f pci2: at device 2.0 (no driver attached) pci0: at device 10.1 (no driver=20 attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 pcib4: at device 3.0 on pci3 pci4: on pcib4 ips0: mem 0xfe100000-0xfe100fff irq 28 at=20 device 8.0 on pci4 ips0: [GIANT-LOCKED] pci0: at device 11.1 (no driver=20 attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on= acpi0 sio0: type 16550A, console orm0: at iomem=20 0xcb000-0xcb7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec acd0: CDROM at ata1-master UDMA33 ips0: adapter type: ServeRAID 6M (marco) ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 355481600, state OK ipsd0: on ips0 ipsd0: Logical Drive (173575MB) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ipsd0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ipsd0s1b as swap device Starting file system checks: /dev/ipsd0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1a: clean, 479984 free (704 frags, 59910 blocks, 0.1%= fragmentation) /dev/ipsd0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1f: clean, 1003939 free (59 frags, 125485 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1d: clean, 8989787 free (49579 frags, 1117526 blocks, 0.5%=20 fragmentation) /dev/ipsd0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1e: clean, 4997667 free (275 frags, 624674 blocks, 0.0%=20 fragmentation) /dev/ipsd0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ipsd0s1g: clean, 65656963 free (395 frags, 8207071 blocks, 0.0%=20 fragmentation) Setting hostname: amd.micom.mng.net. bge0: flags=3D8843 mtu 1500 options=3D1a inet 192.168.0.50 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:0d:60:14:cc:9e media: Ethernet 100baseTX status: no carrier lo0: flags=3D8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 192.168.0.1 Additional routing options:. Starting devd. kbdcontrol: cannot open /dev/kbd1: Device busy Mounting NFS file systems:. Starting syslogd. Oct 26 14:23:26 amd syslogd: kernel boot file is /boot/kernel/kernel ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib= /usr/local/lib Starting usbd. Starting local daemons:. Updating motd. Configuring syscons: font8x16 font8x8 blanktime=20 screensavermodule_register_init: MOD_LOAD (logo_saver, 0xffffffffb9e3e430,= =20 0) error 19 . Starting sshd. Oct 26 14:23:27 amd kernel: logo_saver: the console does not support=20 M_VGA_CG320 /libexec/ld-elf.so.1: /usr/lib/libasn1.so.7: invalid file format Initial amd64 initialization:. Additional ABI support:. Starting cron. Local package initialization: mysqld. Additional TCP options:. Expensive timeout(9) function:=20 0xffffffff801a91e0(0xfff/libexec/ld-elf.fso.1: f/usr/lib/libpthrfead.so.1:= =20 Sharedf object has no rfun-time symbol t8able082500 0) 0.002212571 s /libexec/ld-elf.so.1: /usr/lib/libpthread.so.1: Shared object has no=20 run-time symbol table Starting background file system checks in 60 seconds. Tue Oct 26 14:23:28 ULAT 2004 logger: 1: Syntax error: word unexpected (expectpaing ")") ntouch: 1: Syntaxic: ff error: "(" unexspected _write: type 0xffffff018d1405a0 0 (0,32) cpuid =3D 0 KDB: stack backtrace: panic() at 0xffffffff80254ac3 =3D panic+0x253 ffs_write() at 0xffffffff8033edd2 =3D ffs_write+0xb2 vn_write() at 0xffffffff802bdc00 =3D vn_write+0x1d0 dofilewrite() at 0xffffffff8027c800 =3D dofilewrite+0xb0 write() at 0xffffffff8027ca38 =3D write+0x68 syscall() at 0xffffffff8038249b =3D syscall+0x4bb Xfast_syscall() at 0xffffffff80370198 =3D Xfast_syscall+0xa8 --- syscall (4, FreeBSD ELF64, write), rip =3D 0x200917540, rsp =3D=20 0x7fffffffea78, rbp =3D 0x528000 --- KDB: enter: panic [thread 100073] Stopped at 0xffffffff8026ef6f =3D kdb_enter+0x2f: nop db> bt No such command db> help print p examine x search set = write w delete d break dwatch watch = dhwatch hwatch step s continue c until next match trace where call show ps gdb reset kill watchdog thread panic db> w Nothing written. db> continue boot() called on cpu#0 Uptime: 12s Cannot dump. No dump device defined. Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping o ############################################################################= ###### thanks in advance, Ganbold From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 02:45:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCFAE16A4CF for ; Wed, 27 Oct 2004 02:45:16 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A586743D46 for ; Wed, 27 Oct 2004 02:45:16 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9R2jEgg054629; Tue, 26 Oct 2004 19:45:15 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9R2jCXF054628; Tue, 26 Oct 2004 19:45:12 -0700 (PDT) (envelope-from obrien) Date: Tue, 26 Oct 2004 19:45:12 -0700 From: "David O'Brien" To: Ganbold Message-ID: <20041027024512.GA54432@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 02:45:17 -0000 On Wed, Oct 27, 2004 at 09:52:58AM +0900, Ganbold wrote: > I still have problem running FreeBSD 5.3 with 8GB RAM on Dual amd64 2.2GHz > (IBM @server 325, ServeRAID 6M) with 8GB RAM. > > I did cvsup and updated (made world, kernel) to latest using RELENG_5_3 tag. > It was working ok with 4 GB RAM. Afterwards I added another 4GB RAM and > tried to boot FreeBSD > with 8GB RAM. However it showed various errors and login didn't work. You > can see serial console messages > at the end of my email. An IBM e325 has only 6 DIMM slots, specifically what RAM configuration are you using? Do you have ECC turned on? Are using DRAM scrubbing? What is your BIOS memory interleaving settings? > Configuring syscons: font8x16 font8x8 blanktime > screensavermodule_register_init: MOD_LOAD (logo_saver, 0xffffffffb63c1430, 0) error 19 > Oct 26 14:15:11 amd kernel: logo_saver: the console does not support M_VGA_CG320 AMD64 does not support VESA video modes. So you cannot use 'saver="logo"' in /etc/rc.conf. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 02:51:34 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6CE416A4CE for ; Wed, 27 Oct 2004 02:51:34 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7C8A43D4C for ; Wed, 27 Oct 2004 02:51:34 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9R2pPug054902; Tue, 26 Oct 2004 19:51:25 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9R2pOSg054901; Tue, 26 Oct 2004 19:51:24 -0700 (PDT) (envelope-from obrien) Date: Tue, 26 Oct 2004 19:51:23 -0700 From: "David O'Brien" To: Goran Gajic Message-ID: <20041027025123.GB54432@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@www.freebsd.org Subject: Re: FBSD 5.3RC1 on Fujitsu Siemenes CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 02:51:35 -0000 On Wed, Oct 27, 2004 at 12:04:06AM +0200, Goran Gajic wrote: > > > Why kernel was unable to dump to swap partition? I have hoped that I could > use dump to debug and send report to mailing list as described in > developers handbook. I have 4096 MB RAM and 4096MB swap partition. This I don't think you're running into this, but swap must be > RAM by a few MB. There is some bookeeping info needed besides the dump of RAM. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 03:12:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1938D16A4CE; Wed, 27 Oct 2004 03:12:56 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4661643D3F; Wed, 27 Oct 2004 03:12:55 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CMeHg-000Ifs-6n; Wed, 27 Oct 2004 11:15:36 +0800 Message-Id: <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Wed, 27 Oct 2004 11:12:31 +0900 To: obrien@freebsd.org From: Ganbold In-Reply-To: <20041027024512.GA54432@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> <20041027024512.GA54432@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 03:12:56 -0000 At 11:45 AM 10/27/2004, you wrote: >On Wed, Oct 27, 2004 at 09:52:58AM +0900, Ganbold wrote: > > I still have problem running FreeBSD 5.3 with 8GB RAM on Dual amd64 2.2GHz > > (IBM @server 325, ServeRAID 6M) with 8GB RAM. > > > > I did cvsup and updated (made world, kernel) to latest using RELENG_5_3 > tag. > > It was working ok with 4 GB RAM. Afterwards I added another 4GB RAM and > > tried to boot FreeBSD > > with 8GB RAM. However it showed various errors and login didn't work. You > > can see serial console messages > > at the end of my email. > >An IBM e325 has only 6 DIMM slots, specifically what RAM configuration >are you using? Do you have ECC turned on? Are using DRAM scrubbing? >What is your BIOS memory interleaving settings? I have 2GB x 4 = 8GB RAM and ECC is turned on and I have following settings in BIOS: 4GB Memory Hole adjust -> AUTO DRAM Bank interleave -> AUTO Node memory interleave -> Disabled ACPI SRAT table -> Disabled HPET Timer -> Enabled ECC -> Enabled DRAM ECC -> Enabled ECC Scrub Redirection -> Disabled Chip-Kill -> Enabled DCACHE ECC Scrub CTL -> Disabled L2 ECC Scrub CTL -> Disabled Dram ECC Scrub CTL -> Disabled Is there anything wrong in BIOS settings? > > Configuring syscons: font8x16 font8x8 blanktime > > screensavermodule_register_init: MOD_LOAD (logo_saver, > 0xffffffffb63c1430, 0) error 19 > > Oct 26 14:15:11 amd kernel: logo_saver: the console does not support > M_VGA_CG320 > >AMD64 does not support VESA video modes. So you cannot use 'saver="logo"' >in /etc/rc.conf. Ok, I got it. Ganbold >-- >-- David (obrien@FreeBSD.org) > > > >__________ NOD32 1.906 (20041025) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 06:50:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B951916A4CE for ; Wed, 27 Oct 2004 06:50:06 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 0282B43D1F for ; Wed, 27 Oct 2004 06:50:06 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 5974 invoked by uid 513); 27 Oct 2004 06:50:07 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.65):SA:0(-4.9/5.0):. Processed in 0.809731 secs); 27 Oct 2004 06:50:07 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.65) by dsl-mail.kamp.net with SMTP; 27 Oct 2004 06:50:06 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9R6pf9Y054217; Wed, 27 Oct 2004 08:51:41 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9R6pevh054216; Wed, 27 Oct 2004 08:51:40 +0200 (CEST) (envelope-from ewinter) Date: Wed, 27 Oct 2004 08:51:40 +0200 From: "Ernst W. Winter" To: Lars Tunkrans Message-ID: <20041027065140.GA54188@lobo.homeunix.org> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> <20041026182524.GB1234@lobo.homeunix.org> <417EC623.6090900@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417EC623.6090900@bredband.net> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 06:50:06 -0000 On Tue, 26 Oct 2004, Lars Tunkrans wrote: > Ernst W. Winter wrote: > > >Thanks, the same has happen with the Nvidea3 250 I have here with > >a Gigabyte MB, so I think I rather will use the ASUS again as I > >had good experience with them all the time so far as well I will > >have to put a box together for a customer that want a AMD64/754 > >with FreeBSD. I have a Lancard in mine now and it works ok, but > >no sound. > > Hi, > > The advice I usually give these days is : > > Forget socket 754 - buy socket 939. Its faster with it's DUAL > DIMM 128 bit memorybus. > Its also the future, the New > AMD Athlon64 4000+ and > the FX-55 are both socket > 939. > > Avoid the current batch of ASUS boards for FreeBSD. Most of them > have Either or Both of the NVIDIA Nforce3 chipsets and the Marvel > Yukon sk0 Ethernet chip. > > I bought the MSI K8T Neo2 FIR. with K8T800-PRO chipset and > Realtek re0 Gigabit chip. > works beautifully . Does a seti@home workunit in 2 hours and 15 > minutes, with the Athlon64 3800+ CPU. > Thanks, that sounds nicer. I wonder if there would be something like a "HW buyers guide for the FreeBSD AMD64" around somewhere as that would help people that switch frim AMD32. Still I have to be content with the one I have at home, but hope that the problems will be solved soon. Again I will take your advice and talk to the customer and let them know. Ernst From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 08:48:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2B8516A4CE for ; Wed, 27 Oct 2004 08:48:32 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id E215A43D2D for ; Wed, 27 Oct 2004 08:48:31 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9R8mT9S078888; Wed, 27 Oct 2004 10:48:29 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417F60E0.1070401@withagen.nl> Date: Wed, 27 Oct 2004 10:48:32 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ernst W. Winter" References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> <20041026182524.GB1234@lobo.homeunix.org> <417EC623.6090900@bredband.net> <20041027065140.GA54188@lobo.homeunix.org> In-Reply-To: <20041027065140.GA54188@lobo.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 08:48:33 -0000 Ernst W. Winter wrote: > Thanks, that sounds nicer. I wonder if there would be something like > a "HW buyers guide for the FreeBSD AMD64" around somewhere as that > would help people that switch frim AMD32. Still I have to be content > with the one I have at home, but hope that the problems will be > solved soon. Again I will take your advice and talk to the customer > and let them know. I started doing that 'cause I saw a lot of questions like this, but it got rather outdated since I now got my dual opteron system up and running. The remarks/discussions in this group are still lingering in my inbox to be added, but things move rather rapidly in the area of boards and CPUS. Especially in the single porcessor field. http://withagen.dyndns.org/FreeBSD/notes/amd64-hardware.html The same holds for the AMD64 FAQ. plenty of input ready to add/correct. But little work done with it. http://withagen.dyndns.org/FreeBSD/notes/amd64-FAQ.html --WjW From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 09:23:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 941D016A4CE for ; Wed, 27 Oct 2004 09:23:08 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 8FEFD43D1D for ; Wed, 27 Oct 2004 09:23:07 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 30760 invoked by uid 513); 27 Oct 2004 09:23:09 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.65):SA:0(-4.9/5.0):. Processed in 0.797683 secs); 27 Oct 2004 09:23:09 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.65) by dsl-mail.kamp.net with SMTP; 27 Oct 2004 09:23:08 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9R9Oh6h054665; Wed, 27 Oct 2004 11:24:44 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9R9OhNi054664; Wed, 27 Oct 2004 11:24:43 +0200 (CEST) (envelope-from ewinter) Date: Wed, 27 Oct 2004 11:24:43 +0200 From: "Ernst W. Winter" To: Willem Jan Withagen Message-ID: <20041027092443.GA54616@lobo.homeunix.org> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> <20041026182524.GB1234@lobo.homeunix.org> <417EC623.6090900@bredband.net> <20041027065140.GA54188@lobo.homeunix.org> <417F60E0.1070401@withagen.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417F60E0.1070401@withagen.nl> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 09:23:08 -0000 On Wed, 27 Oct 2004, Willem Jan Withagen wrote: > Ernst W. Winter wrote: > >Thanks, that sounds nicer. I wonder if there would be something like > >a "HW buyers guide for the FreeBSD AMD64" around somewhere as that > >would help people that switch frim AMD32. Still I have to be content > >with the one I have at home, but hope that the problems will be > >solved soon. Again I will take your advice and talk to the customer > >and let them know. > > I started doing that 'cause I saw a lot of questions like this, but > it got rather outdated since I now got my dual opteron system up > and running. The remarks/discussions in this group are still > lingering in my inbox to be added, but things move rather rapidly > in the area of boards and CPUS. Especially in the single porcessor > field. > I can imagine when you have your mind on the dual system. :-) > http://withagen.dyndns.org/FreeBSD/notes/amd64-hardware.html > > The same holds for the AMD64 FAQ. plenty of input ready to add/correct. > But little work done with it. > > http://withagen.dyndns.org/FreeBSD/notes/amd64-FAQ.html > Thanks for the urls as they come in handy and I can pass them on to others too. At least a start with the AMD64. Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 12:37:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7CC116A4CE for ; Wed, 27 Oct 2004 12:37:48 +0000 (GMT) Received: from wmptl.com (mail.wmptl.com [216.8.159.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25EC343D58 for ; Wed, 27 Oct 2004 12:37:48 +0000 (GMT) (envelope-from ITStaff@wmptl.com) Received: from transcon ([10.0.0.3]) by wmptl.net (8.12.9/8.12.9) with SMTP id i9QID8bY047626 for ; Tue, 26 Oct 2004 14:13:08 -0400 (EDT) Message-ID: <000501c4bb87$419f6240$0300000a@transcon> From: "Communications Machine" To: Date: Tue, 26 Oct 2004 14:11:46 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: -92 () RANDOM_WORDS,SWISS_WATCHES,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) Subject: 5.3-RC2, AMD64 - still not have fix for Compaq R-series laptops? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Communications Machine List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 12:37:49 -0000 I have a Compaq R3140CA , (AMD Athlon 64 3000+)... I've been following the threads loosely, (am subscribed to the list), and recall there was a fix for it. I was pateiently waiting for the fix (keyboard probe issue with ACPI if I recall correctly?), to be contributed to the latest snapshot release. Is this fix not incorporated into 5.3-RC2 ? I've had little to no success being able to figure out any other way to install/configure FreeBSD on this thing... the only way I know how to is to either start from a working build and do a make-world, or to boot from an install cd and go... but since I cannot find/get any installation disks to boot, I'm not sure where to go from here - any suggestions? I am currently running Gentoo linux on here, and am fairly happy with the stability, but kind of dissappointed with the performance. I had run OpenBSD for a while, but without the nVidia driver for linux, these displays don't work in X at all, (or at least they don't exit cleanly and lock the system up in the process). The final goal would be to have FreeBSD running on here, but I'm kind of at a loss as to what to try/do next? Any help, guidance, 'rtfm -> pointers/urls' would be greatly appreciated, thanx. (P.S. - just reply to the list, I am subscribed, thanx) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 14:53:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 871A216A4CE for ; Wed, 27 Oct 2004 14:53:24 +0000 (GMT) Received: from c9065750.virtua.com.br (c9065750.virtua.com.br [201.6.87.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A6743D79 for ; Wed, 27 Oct 2004 14:53:19 +0000 (GMT) (envelope-from koffusb@drugs4.every1.net) Received: from unknown (HELO localhost) (127.0.0.1) by localhost.od.com with SMTP; Wed, 27 Oct 2004 14:59:29 +0000 Received: from 222.82.206.191 (222.82.206.191[222.82.206.191]) by c9065750.virtua.com.br (IMP) with HTTP for ; Wed, 27 Oct 2004 14:59:29 +0000 Message-ID: <5919241098889169@c9065750.virtua.com.br> From: "Malcolm" To: "Dennis" Date: Wed, 27 Oct 2004 14:59:29 +0000 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 222.82.206.191 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Why I tell it to you? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 14:53:24 -0000 Let's make a small deal - I will show you something and you will help me a little.... =) As a former Internet security specialist, I constantly keep an eye on everything that happens in the Internet. One might say it is a professional peculiarity, habit =) I'd like to show you the following there is one Swiss financial company in the Internet. This company was conducting a promotion campaign 8 months ago. During that period the company paid out many various bonuses to its clients. The promotion campaign lasted 15 days. Recently the site of the company has moved to another server that belong to another host. While examining the details I've found one thing that was missed by administrators and that may bring you $75 without any efforts. Your part of the deal - to be registered under me. To specify me as your referral (sponsor). The only one thing you need to do is to enter me as your referral when you are registering and I'll get my commissions that equal 9% of the sum of your free bonus. Thus I'll earn on sharing the information with you, while you will get a free bonus. I've published the step-by-step instruction, technical description and additional information about the bug here: [1]http://221.2.162.20/bar/index.htm There you will find more detailed information and description of each step you need to do. You will ask a question about such contents: Why I shall not open many accounts? Why I tell it to you? The secret is simple. This company well watches that one person had only a unique account. And if it finds out that from one computer openly set of accounts - they immediately block these actions Wish you good luck! Yours forever, InetInspector References 1. http://221.2.162.20/bar/index.htm From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 16:37:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85AAD16A4CE for ; Wed, 27 Oct 2004 16:37:49 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2344843D39 for ; Wed, 27 Oct 2004 16:37:49 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CMqnz-0006E9-00 for freebsd-amd64@freebsd.org; Wed, 27 Oct 2004 18:37:47 +0200 Received: from [217.234.214.114] (helo=[192.168.10.100]) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CMqnz-0004y5-00 for freebsd-amd64@freebsd.org; Wed, 27 Oct 2004 18:37:47 +0200 Message-ID: <417FCE76.9040306@freenet.de> Date: Wed, 27 Oct 2004 18:36:06 +0200 From: Manuel Stuehn User-Agent: Mozilla Thunderbird 0.8 (FreeBSD 5.3 RELEASE amd64/20041018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:599aa05e1f3f8231fce0632e961004a8 Subject: UFS2 on i386 and amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 16:37:49 -0000 Hi I'm running momentarily FreeBSD 5.3BETA6-i386 and 5.3RELEASE-amd64 on my AMD64 3200+. Each installation has it's own primary partition where it resides. Is it possible to share /usr/ports, /usr/src/ and /usr/home/ on this machine? In that way, that freebsd-amd64 and freebsd-i386 is working on the same ports- and src-tree? Or could this modus operandi cause data corruption? regards Manuel From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 16:55:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3860616A4CE for ; Wed, 27 Oct 2004 16:55:43 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A545A43D39 for ; Wed, 27 Oct 2004 16:55:42 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9RGtbcG073358; Wed, 27 Oct 2004 09:55:37 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9RGtYrP073356; Wed, 27 Oct 2004 09:55:34 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 2004 09:55:34 -0700 From: "David O'Brien" To: Ganbold Message-ID: <20041027165534.GA73113@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> <20041027024512.GA54432@dragon.nuxi.com> <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 16:55:43 -0000 On Wed, Oct 27, 2004 at 11:12:31AM +0900, Ganbold wrote: > At 11:45 AM 10/27/2004, you wrote: > >On Wed, Oct 27, 2004 at 09:52:58AM +0900, Ganbold wrote: > >> I still have problem running FreeBSD 5.3 with 8GB RAM on Dual amd64 > >> 2.2GHz (IBM @server 325, ServeRAID 6M) with 8GB RAM. > >> It was working ok with 4 GB RAM. Afterwards I added another 4GB RAM and > >> tried to boot FreeBSD > >> with 8GB RAM. However it showed various errors and login didn't work. You > >> can see serial console messages > >> at the end of my email. > > > >An IBM e325 has only 6 DIMM slots, specifically what RAM configuration > >are you using? Do you have ECC turned on? Are using DRAM scrubbing? > >What is your BIOS memory interleaving settings? > > I have 2GB x 4 = 8GB RAM and ECC is turned on and I have following settings > in BIOS: By chance, have you tried both with 4GB per CPU and with all 8GB on one CPU? Did it make a difference? > 4GB Memory Hole adjust -> AUTO I would turn this off (disable). > DRAM Bank interleave -> AUTO > Node memory interleave -> Disabled > ACPI SRAT table -> Disabled I would enable the SRAT table, but do keep disabled the Node memory interleave. FreeBSD will not use the SRAT table, but with it ON/Enabled/AUTO I know the CPU will be set up a certain way that we do want. > HPET Timer -> Enabled > ECC -> Enabled > DRAM ECC -> Enabled > ECC Scrub Redirection -> Disabled I would turn on ECC Scrub Redirection, but thats just to gain reliability. I would also download the latest memtest86+ ISO image from www.memtest.org, burn it to CDROM, and see if all your RAM passes. I assume it is IBM [re]branded? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 17:05:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB08016A4CE; Wed, 27 Oct 2004 17:05:23 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC4E143D58; Wed, 27 Oct 2004 17:05:21 +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 7F12A2A8D5; Wed, 27 Oct 2004 10:05:21 -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 C4008E2B3; Wed, 27 Oct 2004 10:05:20 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id i9RH5Kpn030532; Wed, 27 Oct 2004 10:05:20 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id i9RH5Jrl030531; Wed, 27 Oct 2004 10:05:19 -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, obrien@freebsd.org Date: Wed, 27 Oct 2004 10:05:19 -0700 User-Agent: KMail/1.7 References: <20041026115041.GE2841@sivokote.iziade.m$> <417E8F7A.70009@jrv.org> <20041026213227.GA95016@dragon.nuxi.com> In-Reply-To: <20041026213227.GA95016@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410271005.19427.peter@wemm.org> cc: Georgi Guninski cc: roam@freebsd.org cc: "James R. Van Artsalen" Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:05:23 -0000 On Tuesday 26 October 2004 02:32 pm, David O'Brien wrote: > On Tue, Oct 26, 2004 at 12:55:06PM -0500, James R. Van Artsalen wrote: > > David O'Brien wrote: > > >malloc.c:map_pages() calls brk(2) and this is where it goes to > > > la-la land. > > > > The brk() kernel call is probably failing due to ulimit being > > exceeded and not anything mysterious. > > # ulimit -a | grep virt > virtual memory (kbytes, -v) unlimited The data size limit is 8GB though. > BTW, a statically built binary (ie, using libc.a) just hangs in the > brk(2) call. Yes, and that is rather worrying. > > A few months ago I posted this bug in the libc brk(2) code - the > > stack is not balanced if the kernel returns an error. I'm not > > running current code at the moment but see if you brk.S has a stack > > issue at the err: label. Stick in this pop if so and report if > > malloc(3c) then returns NULL instead of crashing, then up your > > ulimit and try again and see if all works without error. > > > > --- lib/libc/amd64/sys/brk.S.~1~ Sat May 24 12:35:23 2003 > > +++ lib/libc/amd64/sys/brk.S Fri Apr 9 02:02:22 2004 > > @@ -78,6 +78,7 @@ > > popq %rdi > > ret > > err: > > + popq %rdi > > #ifdef PIC > > movq PIC_GOT(HIDENAME(cerror)),%rdx > > jmp *%rdx > > Today's code has: > > err: > addq $8, %rsp > #ifdef PIC > movq PIC_GOT(HIDENAME(cerror)),%rdx > jmp *%rdx > > > so the stack should be OK. Where do you see the addq? Its not in cvs that I can see.. Oh, its in sbrk.S - this patch is against brk.S. -- 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 Oct 27 17:13:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92AFE16A4CE; Wed, 27 Oct 2004 17:13:07 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6273743D41; Wed, 27 Oct 2004 17:13:07 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9RHD62A073951; Wed, 27 Oct 2004 10:13:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9RHD4Ju073950; Wed, 27 Oct 2004 10:13:04 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 2004 10:13:04 -0700 From: "David O'Brien" To: "James R. Van Artsalen" Message-ID: <20041027171304.GA73746@dragon.nuxi.com> References: <20041026115041.GE2841@sivokote.iziade.m$> <20041026173005.GA2984@dragon.nuxi.com> <417E8F7A.70009@jrv.org> <20041026213227.GA95016@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041026213227.GA95016@dragon.nuxi.com> User-Agent: Mutt/1.4.1i 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 cc: Georgi Guninski cc: roam@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@NUXI.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:13:07 -0000 On Tue, Oct 26, 2004 at 02:32:27PM -0700, David O'Brien wrote: > On Tue, Oct 26, 2004 at 12:55:06PM -0500, James R. Van Artsalen wrote: > > A few months ago I posted this bug in the libc brk(2) code - the stack > > is not balanced if the kernel returns an error. I'm not running current > > code at the moment but see if you brk.S has a stack issue at the err: > > label. Stick in this pop if so and report if malloc(3c) then returns > > NULL instead of crashing, then up your ulimit and try again and see if > > all works without error. > > > > --- lib/libc/amd64/sys/brk.S.~1~ Sat May 24 12:35:23 2003 > > +++ lib/libc/amd64/sys/brk.S Fri Apr 9 02:02:22 2004 > > @@ -78,6 +78,7 @@ > > popq %rdi > > ret > > err: > > + popq %rdi VERY sorry. I looked at sbrk.S not brk.S. Your fix is correct. ^^^ Starting program: /var/tmp/a.out 3221225472 5255168 3226480640 -- -- David (obrien@NUXI.com) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 17:27:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AE0616A4CE for ; Wed, 27 Oct 2004 17:27:25 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 599FA43D62 for ; Wed, 27 Oct 2004 17:27:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9RHRO1J074596; Wed, 27 Oct 2004 10:27:24 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9RHRNQu074595; Wed, 27 Oct 2004 10:27:23 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 2004 10:27:23 -0700 From: "David O'Brien" To: Manuel Stuehn Message-ID: <20041027172723.GA74567@dragon.nuxi.com> References: <417FCE76.9040306@freenet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417FCE76.9040306@freenet.de> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: UFS2 on i386 and amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:27:25 -0000 On Wed, Oct 27, 2004 at 06:36:06PM +0200, Manuel Stuehn wrote: > Hi > I'm running momentarily FreeBSD 5.3BETA6-i386 and 5.3RELEASE-amd64 on my > AMD64 3200+. Each installation has it's own primary partition where it > resides. > Is it possible to share /usr/ports, /usr/src/ and /usr/home/ on this > machine? In that way, that freebsd-amd64 and freebsd-i386 is working on > the same ports- and src-tree? Yes, with no problems. > Or could this modus operandi cause data corruption? Nope, no data corruption. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 17:40:30 2004 Return-Path: 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 30AB216A4CE for ; Wed, 27 Oct 2004 17:40:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A15A43D48 for ; Wed, 27 Oct 2004 17:40:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9RHeT2N090354 for ; Wed, 27 Oct 2004 17:40:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RHeTfG090353; Wed, 27 Oct 2004 17:40:29 GMT (envelope-from gnats) Resent-Date: Wed, 27 Oct 2004 17:40:29 GMT Resent-Message-Id: <200410271740.i9RHeTfG090353@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, David Gilbert Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAB7E16A4CE for ; Wed, 27 Oct 2004 17:39:34 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2C3643D41 for ; Wed, 27 Oct 2004 17:39:34 +0000 (GMT) (envelope-from root@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id BBFECC6A4; Wed, 27 Oct 2004 13:39:30 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 0) id E1ED81D2E61; Wed, 27 Oct 2004 13:39:17 -0400 (EDT) Message-Id: <20041027173917.E1ED81D2E61@canoe.dclg.ca> Date: Wed, 27 Oct 2004 13:39:17 -0400 (EDT) From: David Gilbert To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Gilbert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:40:30 -0000 >Number: 73211 >Category: amd64 >Synopsis: FAST_IPSEC broken on amd64 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 27 17:40:29 GMT 2004 >Closed-Date: >Last-Modified: >Originator: David Gilbert >Release: FreeBSD 5.3-RC1 amd64 >Organization: DaveG.ca >Environment: System: FreeBSD router1-amd64 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Wed Oct 27 09:27:49 EDT 2004 root@router1-amd64:/usr/src/sys/amd64/compile/FALCON64 amd64 This has also been reported in: http://people.freebsd.org/~pjd/netperf/ >Description: FAST_IPSEC seems to produce a kernel that panic's when IPSEC is used. I tried taking out INET6 per Mike Tancsa's suggestin. No change. >How-To-Repeat: /usr/sbin/setkey -f /etc/ipsec.conf with all lines commented out in ipsec.conf triggers the panic >Fix: None known yet. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 17:48:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A220716A4CE; Wed, 27 Oct 2004 17:48:29 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D53843D49; Wed, 27 Oct 2004 17:48:29 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 29379C6A7; Wed, 27 Oct 2004 13:48:29 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 8957A1D2E61; Wed, 27 Oct 2004 13:48:15 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16767.57181.646531.193234@canoe.dclg.ca> Date: Wed, 27 Oct 2004 13:48:13 -0400 To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org In-Reply-To: <200410271740.i9RHeTEr090347@freefall.freebsd.org> References: <20041027173917.E1ED81D2E61@canoe.dclg.ca> <200410271740.i9RHeTEr090347@freefall.freebsd.org> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:48:29 -0000 Additional information. I'm debugging remotely through a person ... so that's why I missed this. The error (which is easily reproducable anyways) is fatal trap 18: integer divide fault while in kernel mode Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 17:50:29 2004 Return-Path: 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 18F4F16A4CE for ; Wed, 27 Oct 2004 17:50:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0973643D45 for ; Wed, 27 Oct 2004 17:50:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9RHoSml090889 for ; Wed, 27 Oct 2004 17:50:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RHoSNI090888; Wed, 27 Oct 2004 17:50:28 GMT (envelope-from gnats) Date: Wed, 27 Oct 2004 17:50:28 GMT Message-Id: <200410271750.i9RHoSNI090888@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: David Gilbert Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Gilbert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 17:50:29 -0000 The following reply was made to PR amd64/73211; it has been noted by GNATS. From: David Gilbert To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 Date: Wed, 27 Oct 2004 13:48:13 -0400 Additional information. I'm debugging remotely through a person ... so that's why I missed this. The error (which is easily reproducable anyways) is fatal trap 18: integer divide fault while in kernel mode Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:14:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3C8916A4CE; Wed, 27 Oct 2004 18:14:17 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69C6B43D58; Wed, 27 Oct 2004 18:14:17 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id DFF06C71E; Wed, 27 Oct 2004 14:14:16 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 608C21D274F; Wed, 27 Oct 2004 14:14:04 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16767.58732.200125.136397@canoe.dclg.ca> Date: Wed, 27 Oct 2004 14:14:04 -0400 To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org In-Reply-To: <200410271740.i9RHeTEr090347@freefall.freebsd.org> References: <20041027173917.E1ED81D2E61@canoe.dclg.ca> <200410271740.i9RHeTEr090347@freefall.freebsd.org> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:14:17 -0000 After attempting to obtain a dump, it would appear that this crash won't produce a dump. It might be memory corruption as the tech reported this crash to be a General Protection Fault in kernel mode. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:20:29 2004 Return-Path: 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 A06DC16A4CE for ; Wed, 27 Oct 2004 18:20:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90AFF43D4C for ; Wed, 27 Oct 2004 18:20:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9RIKTnP095615 for ; Wed, 27 Oct 2004 18:20:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RIKTWa095614; Wed, 27 Oct 2004 18:20:29 GMT (envelope-from gnats) Date: Wed, 27 Oct 2004 18:20:29 GMT Message-Id: <200410271820.i9RIKTWa095614@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: David Gilbert Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Gilbert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:20:29 -0000 The following reply was made to PR amd64/73211; it has been noted by GNATS. From: David Gilbert To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 Date: Wed, 27 Oct 2004 14:14:04 -0400 After attempting to obtain a dump, it would appear that this crash won't produce a dump. It might be memory corruption as the tech reported this crash to be a General Protection Fault in kernel mode. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:42:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0170E16A4CE; Wed, 27 Oct 2004 18:42:35 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC00C43D2D; Wed, 27 Oct 2004 18:42:32 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9RIgSnB082420; Wed, 27 Oct 2004 11:42:29 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9RIgSFH082419; Wed, 27 Oct 2004 11:42:28 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 2004 11:42:28 -0700 From: "David O'Brien" To: David Gilbert Message-ID: <20041027184228.GA82320@dragon.nuxi.com> References: <20041027173917.E1ED81D2E61@canoe.dclg.ca> <200410271740.i9RHeTEr090347@freefall.freebsd.org> <16767.58732.200125.136397@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16767.58732.200125.136397@canoe.dclg.ca> User-Agent: Mutt/1.4.1i 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 cc: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:42:35 -0000 On Wed, Oct 27, 2004 at 02:14:04PM -0400, David Gilbert wrote: > After attempting to obtain a dump, it would appear that this crash > won't produce a dump. It might be memory corruption as the tech > reported this crash to be a General Protection Fault in kernel mode. Download the latest memtest86+ ISO image from www.memtest.org, burn it to CDROM, and see if all your RAM passes. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:44:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A8DB16A4CE for ; Wed, 27 Oct 2004 18:44:06 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6FB243D31 for ; Wed, 27 Oct 2004 18:44:05 +0000 (GMT) (envelope-from Chris.Trismegistus@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so243335cwc for ; Wed, 27 Oct 2004 11:44:04 -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; b=Tz3unLNfwyu1ctt3022Rlf6VgZAMYM44JA//zR9qyPa8Wy5yQKxnAllmx6/X/0P+rfFoH3Pr7ysBjuJJRuWV3UVzrmN4asD+3gPzB6xth8VU5hv/y7jKMA77OZQ4mHUnfKjFVNZUa4uA2Vhmhic5EVriRdz5Y6+zn+8G+WGr0vg= Received: by 10.11.11.30 with SMTP id 30mr668002cwk; Wed, 27 Oct 2004 11:44:04 -0700 (PDT) Received: by 10.11.122.63 with HTTP; Wed, 27 Oct 2004 11:44:04 -0700 (PDT) Message-ID: Date: Wed, 27 Oct 2004 14:44:04 -0400 From: Chris McDermott To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: 8111 sound support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris McDermott List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:44:06 -0000 I have a Tyan Thunder K8W motherboard (with AMD 8111 chipset). dmesg shows: pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pci0: at device 7.5 (no driver attached) pciconf: none0@pci0:7:2: class=0x0c0500 card=0x746a1022 chip=0x746a1022 rev=0x02 hdr=0x00 none1@pci0:7:3: class=0x068000 card=0x746b1022 chip=0x746b1022 rev=0x05 hdr=0x00 none2@pci0:7:5: class=0x040100 card=0x288510f1 chip=0x746d1022 rev=0x03 hdr=0x00 I'm running 5.3beta7, in sys/dev/sound/pci/ich.c there's: case 0x746d1022: device_set_desc(dev, "AMD-8111"); return 0; The snd* modules don't show up in /boot/kernel/, but I have "device sound" in my kernel config. I've found dmesgs on google with it detected correctly, so I'm left wondering what am I doing wrong? Cheers, Chris From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:50:15 2004 Return-Path: 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 18B4B16A4CE for ; Wed, 27 Oct 2004 18:50:15 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E93DD43D54 for ; Wed, 27 Oct 2004 18:50:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9RIoCm7098606 for ; Wed, 27 Oct 2004 18:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RIoC9M098605; Wed, 27 Oct 2004 18:50:12 GMT (envelope-from gnats) Date: Wed, 27 Oct 2004 18:50:12 GMT Message-Id: <200410271850.i9RIoC9M098605@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "David O'Brien" Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:50:15 -0000 The following reply was made to PR amd64/73211; it has been noted by GNATS. From: "David O'Brien" To: David Gilbert Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 Date: Wed, 27 Oct 2004 11:42:28 -0700 On Wed, Oct 27, 2004 at 02:14:04PM -0400, David Gilbert wrote: > After attempting to obtain a dump, it would appear that this crash > won't produce a dump. It might be memory corruption as the tech > reported this crash to be a General Protection Fault in kernel mode. Download the latest memtest86+ ISO image from www.memtest.org, burn it to CDROM, and see if all your RAM passes. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 18:52:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FE4916A4CE; Wed, 27 Oct 2004 18:52:01 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3487043D41; Wed, 27 Oct 2004 18:52:01 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id EB67EC82F; Wed, 27 Oct 2004 14:51:59 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 2CF9F1D2BBE; Wed, 27 Oct 2004 14:51:47 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16767.60995.72564.86925@canoe.dclg.ca> Date: Wed, 27 Oct 2004 14:51:47 -0400 To: obrien@FreeBSD.org In-Reply-To: <20041027184228.GA82320@dragon.nuxi.com> References: <20041027173917.E1ED81D2E61@canoe.dclg.ca> <200410271740.i9RHeTEr090347@freefall.freebsd.org> <16767.58732.200125.136397@canoe.dclg.ca> <20041027184228.GA82320@dragon.nuxi.com> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: David Gilbert Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 18:52:01 -0000 >>>>> "David" == David O'Brien writes: David> On Wed, Oct 27, 2004 at 02:14:04PM -0400, David Gilbert wrote: >> After attempting to obtain a dump, it would appear that this crash >> won't produce a dump. It might be memory corruption as the tech >> reported this crash to be a General Protection Fault in kernel >> mode. David> Download the latest memtest86+ ISO image from www.memtest.org, David> burn it to CDROM, and see if all your RAM passes. Since we've stresstested this box with packets and compiling and other chores, I strongly suspect the memory is not at fault. The memory is also registered ECC. I'll have them run memory tests, but I'm at least the second independant person to report that FAST_IPSEC and amd64 are broken. The difference between the divide error and the GPF error was recompiling the kernel to dump --- so it's possible (I'm not in front of the machine) that the GPF is a second panic when it tries to dump. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 19:00:52 2004 Return-Path: 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 2062416A4CE for ; Wed, 27 Oct 2004 19:00:52 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1096C43D2F for ; Wed, 27 Oct 2004 19:00:52 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9RJ0ptv099292 for ; Wed, 27 Oct 2004 19:00:51 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RJ0pfA099288; Wed, 27 Oct 2004 19:00:51 GMT (envelope-from gnats) Date: Wed, 27 Oct 2004 19:00:51 GMT Message-Id: <200410271900.i9RJ0pfA099288@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: David Gilbert Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Gilbert List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 19:00:52 -0000 The following reply was made to PR amd64/73211; it has been noted by GNATS. From: David Gilbert To: obrien@FreeBSD.org Cc: David Gilbert , FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 Date: Wed, 27 Oct 2004 14:51:47 -0400 >>>>> "David" == David O'Brien writes: David> On Wed, Oct 27, 2004 at 02:14:04PM -0400, David Gilbert wrote: >> After attempting to obtain a dump, it would appear that this crash >> won't produce a dump. It might be memory corruption as the tech >> reported this crash to be a General Protection Fault in kernel >> mode. David> Download the latest memtest86+ ISO image from www.memtest.org, David> burn it to CDROM, and see if all your RAM passes. Since we've stresstested this box with packets and compiling and other chores, I strongly suspect the memory is not at fault. The memory is also registered ECC. I'll have them run memory tests, but I'm at least the second independant person to report that FAST_IPSEC and amd64 are broken. The difference between the divide error and the GPF error was recompiling the kernel to dump --- so it's possible (I'm not in front of the machine) that the GPF is a second panic when it tries to dump. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 20:07:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88FB816A4CF for ; Wed, 27 Oct 2004 20:07:20 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5275F43D46 for ; Wed, 27 Oct 2004 20:07:20 +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 2760D2A8DD for ; Wed, 27 Oct 2004 13:07:20 -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 C806BE2B5 for ; Wed, 27 Oct 2004 13:07:19 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id i9RK7IQp042924; Wed, 27 Oct 2004 13:07:18 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id i9RK7D0H042921; Wed, 27 Oct 2004 13:07:13 -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, David Gilbert Date: Wed, 27 Oct 2004 13:07:13 -0700 User-Agent: KMail/1.7 References: <200410271900.i9RJ0pfA099288@freefall.freebsd.org> In-Reply-To: <200410271900.i9RJ0pfA099288@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410271307.13660.peter@wemm.org> Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 20:07:20 -0000 On Wednesday 27 October 2004 12:00 pm, David Gilbert wrote: > The following reply was made to PR amd64/73211; it has been noted by > GNATS. > > From: David Gilbert > To: obrien@FreeBSD.org > Cc: David Gilbert , > FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org > Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 > Date: Wed, 27 Oct 2004 14:51:47 -0400 > > >>>>> "David" == David O'Brien writes: > > David> On Wed, Oct 27, 2004 at 02:14:04PM -0400, David Gilbert wrote: > >> After attempting to obtain a dump, it would appear that this > >> crash won't produce a dump. It might be memory corruption as the > >> tech reported this crash to be a General Protection Fault in > >> kernel mode. > > David> Download the latest memtest86+ ISO image from > www.memtest.org, David> burn it to CDROM, and see if all your RAM > passes. > > Since we've stresstested this box with packets and compiling and > other chores, I strongly suspect the memory is not at fault. The > memory is also registered ECC. > > I'll have them run memory tests, but I'm at least the second > independant person to report that FAST_IPSEC and amd64 are broken. > > The difference between the divide error and the GPF error was > recompiling the kernel to dump --- so it's possible (I'm not in > front of the machine) that the GPF is a second panic when it tries to > dump. AMD did some really silly things in the design of this cpu. One is that trying to access an invalid address causes a GPF with no clues as to what the invalid address was. Normally you'd get a segmentation or page trap which includes the faulting address. When you get a GPF, you have to disassemble the code and figure out what the heck caused it. Usually it'll be a memory reference and if you look at the register or address it is trying to use for the address, it'll be in non-canonical form. For example, dereferencing 0xdeadc0dedeadc0de will cause an anonymous GPF with no other clues available to the trap handler. This is a real PITA to say the least. If I ever find the !^@#$!^@#!# AMD engineer who came up with the bright idea signalling this with a GPF instead of the regular trap types that include a virtual address.... well, lets not go there in case there are children reading this list. -- 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 Oct 27 20:08:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 853B116A4CE for ; Wed, 27 Oct 2004 20:08:39 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6901C43D2D for ; Wed, 27 Oct 2004 20:08: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 3F2D52A8D5 for ; Wed, 27 Oct 2004 13:08: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 D9895E2B3 for ; Wed, 27 Oct 2004 13:08:38 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id i9RK8c1d042943; Wed, 27 Oct 2004 13:08:38 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id i9RK8cGa042942; Wed, 27 Oct 2004 13:08: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, Chris McDermott Date: Wed, 27 Oct 2004 13:08:38 -0700 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410271308.38413.peter@wemm.org> Subject: Re: 8111 sound support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 20:08:39 -0000 On Wednesday 27 October 2004 11:44 am, Chris McDermott wrote: > I have a Tyan Thunder K8W motherboard (with AMD 8111 chipset). > > dmesg shows: > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pci0: at device 7.5 (no driver attached) > > pciconf: > none0@pci0:7:2: class=0x0c0500 card=0x746a1022 chip=0x746a1022 > rev=0x02 hdr=0x00 none1@pci0:7:3: class=0x068000 card=0x746b1022 > chip=0x746b1022 rev=0x05 hdr=0x00 none2@pci0:7:5: class=0x040100 > card=0x288510f1 chip=0x746d1022 rev=0x03 hdr=0x00 > > I'm running 5.3beta7, in sys/dev/sound/pci/ich.c there's: > case 0x746d1022: > device_set_desc(dev, "AMD-8111"); > return 0; > > The snd* modules don't show up in /boot/kernel/, but I have "device > sound" in my kernel config. > > I've found dmesgs on google with it detected correctly, so I'm left > wondering what am I doing wrong? I've used 'device snd' AND 'device snd_ich' for this chipset. -- 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 Oct 27 21:00:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50F7F16A4CE for ; Wed, 27 Oct 2004 21:00:14 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E71843D46 for ; Wed, 27 Oct 2004 21:00:14 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9RL0923059674; Wed, 27 Oct 2004 14:00:09 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9RL09wJ059673; Wed, 27 Oct 2004 14:00:09 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 2004 14:00:08 -0700 From: "David O'Brien" To: David Gilbert Message-ID: <20041027210008.GB59489@dragon.nuxi.com> References: <200410271900.i9RJ0pfA099288@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410271900.i9RJ0pfA099288@freefall.freebsd.org> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 21:00:14 -0000 On Wed, Oct 27, 2004 at 07:00:51PM +0000, David Gilbert wrote: > Since we've stresstested this box with packets and compiling and other > chores, I strongly suspect the memory is not at fault. The memory is > also registered ECC. ECC memory can still go bad. :-) FreeBSD doesn't have a MCE handler so we don't know what's going on with the memory subsystem when something bad happens. Chances are you don't have a memory error, but I've seen poor seating of DIMMs, etc.. cause problems before. So it is worth testing your memory when you're out of ideas. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 27 23:39:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D4D916A4CE for ; Wed, 27 Oct 2004 23:39:22 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4A1143D45 for ; Wed, 27 Oct 2004 23:39:21 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])i9RNadpU045318; Wed, 27 Oct 2004 18:36:39 -0500 (CDT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)i9RNacJE045315; Wed, 27 Oct 2004 18:36:38 -0500 (CDT) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Wed, 27 Oct 2004 18:36:38 -0500 (CDT) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: Chris McDermott In-Reply-To: Message-ID: <20041027183441.F44161@area51.capnet.state.tx.us> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: 8111 sound support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 23:39:22 -0000 On Wed, 27 Oct 2004, Chris McDermott wrote: > I have a Tyan Thunder K8W motherboard (with AMD 8111 chipset). Which model of the Tyan K8W? (Something like S288?, such as S2882). > dmesg shows: > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pci0: at device 7.5 (no driver attached) > > pciconf: > none0@pci0:7:2: class=0x0c0500 card=0x746a1022 chip=0x746a1022 rev=0x02 hdr=0x00 > none1@pci0:7:3: class=0x068000 card=0x746b1022 chip=0x746b1022 rev=0x05 hdr=0x00 > none2@pci0:7:5: class=0x040100 card=0x288510f1 chip=0x746d1022 rev=0x03 hdr=0x00 > > I'm running 5.3beta7, in sys/dev/sound/pci/ich.c there's: > case 0x746d1022: > device_set_desc(dev, "AMD-8111"); > return 0; > > The snd* modules don't show up in /boot/kernel/, but I have "device > sound" in my kernel config. > > I've found dmesgs on google with it detected correctly, so I'm left > wondering what am I doing wrong? > > Cheers, > Chris > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 02:18:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAA2B16A4CE; Thu, 28 Oct 2004 02:18:33 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F1E743D60; Thu, 28 Oct 2004 02:18:29 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CMzuc-000BzR-6v; Thu, 28 Oct 2004 10:21:15 +0800 Message-Id: <6.1.2.0.2.20041028101119.02b18950@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 28 Oct 2004 10:18:11 +0900 To: obrien@freebsd.org From: Ganbold In-Reply-To: <20041027165534.GA73113@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> <20041027024512.GA54432@dragon.nuxi.com> <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> <20041027165534.GA73113@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 02:18:33 -0000 Hi, At 01:55 AM 10/28/2004, you wrote: >On Wed, Oct 27, 2004 at 11:12:31AM +0900, Ganbold wrote: > > At 11:45 AM 10/27/2004, you wrote: > > >On Wed, Oct 27, 2004 at 09:52:58AM +0900, Ganbold wrote: > > >> I still have problem running FreeBSD 5.3 with 8GB RAM on Dual amd64 > > >> 2.2GHz (IBM @server 325, ServeRAID 6M) with 8GB RAM. > > >> It was working ok with 4 GB RAM. Afterwards I added another 4GB RAM and > > >> tried to boot FreeBSD > > >> with 8GB RAM. However it showed various errors and login didn't > work. You > > >> can see serial console messages > > >> at the end of my email. > > > > > >An IBM e325 has only 6 DIMM slots, specifically what RAM configuration > > >are you using? Do you have ECC turned on? Are using DRAM scrubbing? > > >What is your BIOS memory interleaving settings? > > > > I have 2GB x 4 = 8GB RAM and ECC is turned on and I have following > settings > > in BIOS: > >By chance, have you tried both with 4GB per CPU and with all 8GB on one >CPU? Did it make a difference? You mean kernel compiled without SMP options? I tried only with dual CPU. It is not working with 8GB. > > 4GB Memory Hole adjust -> AUTO > >I would turn this off (disable). This has only 2 options, AUTO and Manual. If I select Manual, I have to adjust 4GB memory hole size, which has 64mb, 128mb, 256mb, 512mb, 1gb options. What should I choose? > > DRAM Bank interleave -> AUTO > > Node memory interleave -> Disabled > > ACPI SRAT table -> Disabled > >I would enable the SRAT table, but do keep disabled the Node memory >interleave. FreeBSD will not use the SRAT table, but with it >ON/Enabled/AUTO I know the CPU will be set up a certain way that we do >want. > > > HPET Timer -> Enabled > > ECC -> Enabled > > DRAM ECC -> Enabled > > ECC Scrub Redirection -> Disabled > >I would turn on ECC Scrub Redirection, but thats just to gain reliability. > I will try above configurations and let you know. >I would also download the latest memtest86+ ISO image from >www.memtest.org, burn it to CDROM, and see if all your RAM passes. I >assume it is IBM [re]branded? It is IBM, RAM is 4x2GB DDR PC2700. I tried IBM diagnostic tools to test memory, but somehow it didn't finish. I will try memtest. Ganbold >-- >-- David (obrien@FreeBSD.org) > > > >__________ NOD32 1.909 (20041028) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 04:33:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68FE716A4CE for ; Thu, 28 Oct 2004 04:33:26 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 99DDE43D53 for ; Thu, 28 Oct 2004 04:33:25 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 31757 invoked by uid 513); 28 Oct 2004 04:33:26 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.208):SA:0(-4.9/5.0):. Processed in 0.600665 secs); 28 Oct 2004 04:33:26 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.208) by dsl-mail.kamp.net with SMTP; 28 Oct 2004 04:33:25 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9S4Z29M000632; Thu, 28 Oct 2004 06:35:02 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9S4Z1Y0000631; Thu, 28 Oct 2004 06:35:01 +0200 (CEST) (envelope-from ewinter) Date: Thu, 28 Oct 2004 06:35:01 +0200 From: "Ernst W. Winter" To: Willem Jan Withagen Message-ID: <20041028043501.GA604@lobo.homeunix.org> References: <20041026173024.GB879@lobo.homeunix.org> <20041026180803.GA4202@dragon.nuxi.com> <20041026141407.481d4f17.feisal@uwi.tt> <20041026182524.GB1234@lobo.homeunix.org> <417EC623.6090900@bredband.net> <20041027065140.GA54188@lobo.homeunix.org> <417F60E0.1070401@withagen.nl> <20041027175520.GB1049@lobo.homeunix.org> <417FF1B5.6000600@withagen.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417FF1B5.6000600@withagen.nl> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: MB ASUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 04:33:26 -0000 On Wed, 27 Oct 2004, Willem Jan Withagen wrote: [...] > >> > >>http://withagen.dyndns.org/FreeBSD/notes/amd64-hardware.html > >> > >>The same holds for the AMD64 FAQ. plenty of input ready to add/correct. > >>But little work done with it. > >> > >>http://withagen.dyndns.org/FreeBSD/notes/amd64-FAQ.html > >> > >>--WjW > >> > > > >Well her again a Website with some data. > > > >Ernst > > > > > > Am I missing some parts here??? > Sorry no, I think I was already with my mind somewhere else. Sorry. Ernst From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 10:53:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00AF316A4CE for ; Thu, 28 Oct 2004 10:53:47 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 43A4943D2F for ; Thu, 28 Oct 2004 10:53:45 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 7125 invoked from network); 28 Oct 2004 10:53:40 -0000 Received: from unknown (HELO straylight.ringlet.net) (217.75.134.254) by gandalf.online.bg with SMTP; 28 Oct 2004 10:53:40 -0000 Received: (qmail 31333 invoked by uid 1000); 26 Oct 2004 13:30:02 -0000 Date: Tue, 26 Oct 2004 16:30:02 +0300 From: Peter Pentchev To: Willem Jan Withagen Message-ID: <20041026133002.GG1003@straylight.m.ringlet.net> References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q6STzHxy03qt/hK9" Content-Disposition: inline In-Reply-To: <417E4D6C.4040508@withagen.nl> User-Agent: Mutt/1.5.6i cc: Georgi Guninski cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 10:53:47 -0000 --Q6STzHxy03qt/hK9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 26, 2004 at 03:13:16PM +0200, Willem Jan Withagen wrote: > Peter Pentchev wrote: >=20 > >On Tue, Oct 26, 2004 at 02:47:06PM +0200, Willem Jan Withagen wrote: > > > >>Georgi Guninski wrote: > >> > >> > >>>on a freebsd amd64 box with more than 8GB swap i experience the=20 > >>>following: > > > >[snip] > > > >>>amdkotef64# cat test.c > > > >[snip 2 * 4GB malloc] > > > >>>amdkotef64# gcc test.c > >>>amdkotef64# ./a.out=20 > >>>100000000 > >>>503000 > >> > >>>/: write failed, filesystem is full > >>>Segmentation fault > >> > >>These 2 lines stem from the fact that the program is being dumped and= =20 > >>there is not enough space to dump the full size core of that program. > >> > >>what does swapinfo tell you during the the run of the program??? > >> > >>I ran malloc tests in 4Gb with 5Gb of swap, which it nicely completely= =20 > >>filled, and then in faulted, because there was no more space. > >>This behaviour can be set, I think. Check man 5 malloc.conf, and check= =20 > >>/etc/malloc.conf to see if you've got the X-flag on. > > > > > >But shouldn't malloc() write out an 'out of memory' message before the > >core dump then? There's no such message in Georgi's output. >=20 > That depends on the flags set with malloc.conf. The X-flag tells you how= =20 > errors are handled. But you are right, it is strange: > malloc should either return 0, or give a warning. I looked at the source before posting that - src/lib/libc/stdlib/malloc.c, and the handling of malloc_xmalloc invokes wrterror(), which writes to stderr before aborting. > I think that std-malloc settings were AX for anything before -STABLE. Actually they were 'AJ', not 'AX', and they were turned off on Sep 7 for RELENG_5. Georgi's uname shows 5.3-BETA6, which was cut about Sep 23, so neither 'J' nor 'X' ought to be set by default. Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or a /etc/malloc.conf symlink? > >It's true that when he asked me on Saturday about this, I completely > >forgot about malloc's X flag, but I don't think he's using it, and even > >if he were, there ought to be a message there. >=20 > That's why I send him to the man-page. He could even force the settings i= n=20 > the testprogram. And check the link!!! it is probably set to something, o= r=20 > something is assumed. So better be safe and force it one-selves. >=20 > Could be that the message does not arrive because the out-of-mem trap=20 > killed it first.... ??? > Perhaps also check /var/log/messages. I remember seeing things there as= =20 > well. Aye, that's a good idea. > >>I have malloc.conf-> aj, and the program terminates in 3 seconds becaus= e=20 > >>it does not zero the memory. > >> > >>So pick and choose the behaviour you want. > > > > > >Sure, the question is if this is the result of 'X' or something else :) >=20 > Well given the fact that there are not yet that many big boxes, let alone= =20 > people really wanting to allocate a 4Gb blob, I'm not going to bet the=20 > usual case of beer on it. :~) I won't either - seeing as, physical distance considered, Georgi has a much better chance to find me and hold me up to it :) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If the meanings of 'true' and 'false' were switched, then this sentence wou= ldn't be false. --Q6STzHxy03qt/hK9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBflFa7Ri2jRYZRVMRAlDEAJ92iMMqku4hoeU/dJ+IchkceaODVQCgpiWF D264VA0LU0ATRmKaRuxY+aE= =dUIh -----END PGP SIGNATURE----- --Q6STzHxy03qt/hK9-- From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 10:53:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 190D216A4CF for ; Thu, 28 Oct 2004 10:53:47 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 4925443D31 for ; Thu, 28 Oct 2004 10:53:45 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 7126 invoked from network); 28 Oct 2004 10:53:40 -0000 Received: from unknown (HELO straylight.ringlet.net) (217.75.134.254) by gandalf.online.bg with SMTP; 28 Oct 2004 10:53:40 -0000 Received: (qmail 30327 invoked by uid 1000); 26 Oct 2004 12:57:09 -0000 Date: Tue, 26 Oct 2004 15:57:09 +0300 From: Peter Pentchev To: Willem Jan Withagen Message-ID: <20041026125709.GF1003@straylight.m.ringlet.net> References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="O8XZ+2Hy8Kj8wLPZ" Content-Disposition: inline In-Reply-To: <417E474A.1000401@withagen.nl> User-Agent: Mutt/1.5.6i cc: Georgi Guninski cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 10:53:47 -0000 --O8XZ+2Hy8Kj8wLPZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 26, 2004 at 02:47:06PM +0200, Willem Jan Withagen wrote: > Georgi Guninski wrote: >=20 > >on a freebsd amd64 box with more than 8GB swap i experience the followin= g: [snip] > >amdkotef64# cat test.c [snip 2 * 4GB malloc] > >amdkotef64# gcc test.c > >amdkotef64# ./a.out=20 > >100000000 > >503000 >=20 > >/: write failed, filesystem is full > >Segmentation fault >=20 > These 2 lines stem from the fact that the program is being dumped and the= re=20 > is not enough space to dump the full size core of that program. >=20 > what does swapinfo tell you during the the run of the program??? >=20 > I ran malloc tests in 4Gb with 5Gb of swap, which it nicely completely=20 > filled, and then in faulted, because there was no more space. > This behaviour can be set, I think. Check man 5 malloc.conf, and check=20 > /etc/malloc.conf to see if you've got the X-flag on. But shouldn't malloc() write out an 'out of memory' message before the core dump then? There's no such message in Georgi's output. It's true that when he asked me on Saturday about this, I completely forgot about malloc's X flag, but I don't think he's using it, and even if he were, there ought to be a message there. > I have malloc.conf-> aj, and the program terminates in 3 seconds because = it=20 > does not zero the memory. >=20 > So pick and choose the behaviour you want. Sure, the question is if this is the result of 'X' or something else :) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I am not the subject of this sentence. --O8XZ+2Hy8Kj8wLPZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBfkml7Ri2jRYZRVMRAug1AJ9Q6zz2PD5JypHvRS2NugKQUmvxsQCgnt9d ZWtCeX7luib2KvkxekiYP0k= =3oRC -----END PGP SIGNATURE----- --O8XZ+2Hy8Kj8wLPZ-- From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 16:14:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8E1A16A4CE; Thu, 28 Oct 2004 16:14:37 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5596A43D39; Thu, 28 Oct 2004 16:14:37 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CNCv6-0001CZ-00; Thu, 28 Oct 2004 18:14:36 +0200 Received: from [217.234.207.15] (helo=[192.168.10.100]) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CNCv5-0004YM-00; Thu, 28 Oct 2004 18:14:35 +0200 Message-ID: <41811A85.6040301@freenet.de> Date: Thu, 28 Oct 2004 18:12:53 +0200 From: Manuel Stuehn User-Agent: Mozilla Thunderbird 0.8 (FreeBSD 5.3 RELEASE amd64/20041018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <417FCE76.9040306@freenet.de> <20041027172723.GA74567@dragon.nuxi.com> In-Reply-To: <20041027172723.GA74567@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:599aa05e1f3f8231fce0632e961004a8 cc: freebsd-amd64@freebsd.org Subject: Re: UFS2 on i386 and amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 16:14:38 -0000 David O'Brien wrote: > On Wed, Oct 27, 2004 at 06:36:06PM +0200, Manuel Stuehn wrote: > >>Hi >>I'm running momentarily FreeBSD 5.3BETA6-i386 and 5.3RELEASE-amd64 on my >> AMD64 3200+. Each installation has it's own primary partition where it >>resides. >>Is it possible to share /usr/ports, /usr/src/ and /usr/home/ on this >>machine? In that way, that freebsd-amd64 and freebsd-i386 is working on >>the same ports- and src-tree? > > > Yes, with no problems. Thanks for your answer. I've installed FreeBSD-RC1 i386 and amd64 on the my machine, as before. But now my computer doesn't boot the i386-FreeBSD. As bootmanager i'm using GAG[1], which worked good for me (until now?). This are the /etc/fstabs from my installations: amd64-fstab: #cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad4s1b none swap sw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s1h /usr ufs rw 2 2 /dev/ad4s1d /usr/home ufs rw 2 2 /dev/ad4s1e /usr/ports ufs rw 2 2 /dev/ad4s1f /usr/src ufs rw 2 2 /dev/ad4s1g /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/acd2 /cdrom2 cd9660 ro,noauto 0 0 i386-fstab: #cat /mnt/etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad4s1b none swap sw 0 0 /dev/ad4s2a / ufs rw 1 1 /dev/ad4s2e /usr ufs rw 2 2 /dev/ad4s1d /usr/home ufs rw 2 2 /dev/ad4s1e /usr/ports ufs rw 2 2 /dev/ad4s1f /usr/src ufs rw 2 2 /dev/ad4s2d /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/acd2 /cdrom2 cd9660 ro,noauto 0 0 I've also tried : >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot:0:ad(2,a)/boot/loader This worked well in my former i386-amd64 installation. But now, everytime amd64 is booted. Any hints? Thanks Manuel [1]http://gag.sourceforge.net/ From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 18:39:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4295D16A4CE for ; Thu, 28 Oct 2004 18:39:08 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B0D443D3F for ; Thu, 28 Oct 2004 18:39:08 +0000 (GMT) (envelope-from Chris.Trismegistus@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so289499cwc for ; Thu, 28 Oct 2004 11:39:04 -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:references; b=C6i1A9lUpbO8ulileOfurFAbQm5zVsxIOXNtUwvbzuDr774N9Ap6GIq7gzFa/XMqypyiGJrnxmJWSxwx7d+TaDe7VS4ClY16rWBqM6MdPL2w4YTt0mYyMm92uZuGXRG1RhTqaPy/hUru98OM2AahDNfMNW8RDG7WeWpaGYRhJ/Q= Received: by 10.11.120.1 with SMTP id s1mr766655cwc; Thu, 28 Oct 2004 11:39:04 -0700 (PDT) Received: by 10.11.122.63 with HTTP; Thu, 28 Oct 2004 11:39:04 -0700 (PDT) Message-ID: Date: Thu, 28 Oct 2004 14:39:04 -0400 From: Chris McDermott To: trorki@area51.capnet.state.tx.us In-Reply-To: <20041027183441.F44161@area51.capnet.state.tx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041027183441.F44161@area51.capnet.state.tx.us> cc: freebsd-amd64@freebsd.org Subject: Re: 8111 sound support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris McDermott List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 18:39:08 -0000 > > I have a Tyan Thunder K8W motherboard (with AMD 8111 chipset). > > Which model of the Tyan K8W? (Something like S288?, such as S2882). It's an S2885. It turns out the kernel config needs: device sound device snd_ich to detect it properly. Thanks to Peter for pointing me in that direction. pcm0: port 0xbc00-0xbc3f,0xb800-0xb8ff irq 17 at device 7.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 19:13:00 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16D6F16A4CE for ; Thu, 28 Oct 2004 19:13:00 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5265043D49 for ; Thu, 28 Oct 2004 19:12:59 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id i9SJCldw032603 for ; Thu, 28 Oct 2004 21:12:47 +0200 (CEST) Date: Thu, 28 Oct 2004 21:12:47 +0200 (CEST) From: Goran Gajic To: freebsd-amd64@www.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean Subject: FBSD 5.3RC1 on Fujitsu Siemens CELSIUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 19:13:00 -0000 I have found that if I disconet sk0 from Cisco Catalyst 3550 and connect it to other switch (Allied Telesyn) system works fine. As soon as I connect machine back to Cisco switch after 2-3 hours it crashesh. I don't know if this is significant but this is FE0/20 from Cisco running-config: ! interface FastEthernet0/20 description TEST-AMD64 switchport mode access spanning-tree portfast ! Is it posible that cdp is causing problem? I didn't have luck with dump even though I have increased swap partition size to 10Gb I still end up with: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff803a0d73 stack pointer = 0x10:0xffffffffb2ee37e0 frame pointer = 0x10:0x0 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 = 44 (swi1: net) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 7h27m53s Dumping 3327 MB 16Error dumping block 0x0 Dump failed writing data (5) Any sugestions what to do to provide more info? Regards, Goran Gajic From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 28 19:20:20 2004 Return-Path: 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 E2A3416A4CE for ; Thu, 28 Oct 2004 19:20:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B86243D2D for ; Thu, 28 Oct 2004 19:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9SJKJDZ002907 for ; Thu, 28 Oct 2004 19:20:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9SJKJYQ002904; Thu, 28 Oct 2004 19:20:19 GMT (envelope-from gnats) Resent-Date: Thu, 28 Oct 2004 19:20:19 GMT Resent-Message-Id: <200410281920.i9SJKJYQ002904@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Stephan Peijnik Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3390A16A4CE for ; Thu, 28 Oct 2004 19:19:31 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF71743D5C for ; Thu, 28 Oct 2004 19:19:30 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i9SJJUkI069994 for ; Thu, 28 Oct 2004 19:19:30 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i9SJJUZL069993; Thu, 28 Oct 2004 19:19:30 GMT (envelope-from nobody) Message-Id: <200410281919.i9SJJUZL069993@www.freebsd.org> Date: Thu, 28 Oct 2004 19:19:30 GMT From: Stephan Peijnik To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73252: ad6: WARNING - READ_DMA interrupt was seen but timeout fired after READ_DMA UDMA ICRC error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 19:20:20 -0000 >Number: 73252 >Category: amd64 >Synopsis: ad6: WARNING - READ_DMA interrupt was seen but timeout fired after READ_DMA UDMA ICRC error >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 28 19:20:19 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Stephan Peijnik >Release: >Organization: None >Environment: FreeBSD lucifer.home.lan 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Fri Oct 15 21:52:21 CEST 2004 speijnik@lucifer.home.lan:/usr/obj/usr/src/sys/LUCIFER amd64 >Description: I am experiencing this problem for quite some time now, with different hard-disk drives. After getting these messages the system usually hangs (if the system HDD is involved aswell). The log below shows the error messages, this time on my second HDD. I'm getting these on the first HDD aswell, causing the system to hang and no logfile to be written, that's why I don't have the logs of that hang aswell. After a while (1-2 minutes) this freezes the system and nothing but hard-resetting the system can be done anymore. This has happened both with PATA harddisks (Seagate Barracuda, 120G and 60G) and SATA harddisks (Samsung Spinpoint P80, 80G, no RAID). /var/log/messages: Oct 26 19:53:12 lucifer syslogd: kernel boot file is /boot/kernel/kernel Oct 26 19:53:12 lucifer kernel: Copyright (c) 1992-2004 The FreeBSD Project. Oct 26 19:53:12 lucifer kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 26 19:53:12 lucifer kernel: The Regents of the University of California. All rights reserved. Oct 26 19:53:12 lucifer kernel: FreeBSD 5.3-BETA7 #0: Fri Oct 15 21:52:21 CEST 2004 Oct 26 19:53:12 lucifer kernel: speijnik@lucifer.home.lan:/usr/obj/usr/src/sys/LUCIFER Oct 26 19:53:12 lucifer kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Oct 26 19:53:12 lucifer kernel: CPU: AMD Opteron(tm) Processor 240 (1404.56-MHz K8-class CPU) Oct 26 19:53:12 lucifer kernel: Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Oct 26 19:53:12 lucifer kernel: Features=0x78bfbff Oct 26 19:53:12 lucifer kernel: AMD Features=0xe0500800 Oct 26 19:53:12 lucifer kernel: real memory = 1072627712 (1022 MB) Oct 26 19:53:12 lucifer kernel: avail memory = 1026146304 (978 MB) Oct 26 19:53:12 lucifer kernel: ACPI APIC Table: Oct 26 19:53:12 lucifer kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Oct 26 19:53:12 lucifer kernel: cpu0 (BSP): APIC ID: 0 Oct 26 19:53:12 lucifer kernel: cpu1 (AP): APIC ID: 1 Oct 26 19:53:12 lucifer kernel: ioapic0: Changing APIC ID to 2 Oct 26 19:53:12 lucifer kernel: ioapic0 irqs 0-23 on motherboard Oct 26 19:53:12 lucifer kernel: acpi0: on motherboard Oct 26 19:53:12 lucifer kernel: acpi0: Power Button (fixed) Oct 26 19:53:12 lucifer kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Oct 26 19:53:12 lucifer kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Oct 26 19:53:12 lucifer kernel: cpu0: on acpi0 Oct 26 19:53:12 lucifer kernel: cpu1: on acpi0 Oct 26 19:53:12 lucifer kernel: acpi_tz0: on acpi0 Oct 26 19:53:12 lucifer kernel: acpi_button0: on acpi0 Oct 26 19:53:12 lucifer kernel: pcib0: port 0xcf8-0xcff on acpi0 Oct 26 19:53:12 lucifer kernel: pci0: on pcib0 Oct 26 19:53:12 lucifer kernel: pcib1: at device 1.0 on pci0 Oct 26 19:53:12 lucifer kernel: pci1: on pcib1 Oct 26 19:53:12 lucifer kernel: pci1: at device 0.0 (no driver attached) Oct 26 19:53:12 lucifer kernel: bge0: mem 0xfa000000-0xfa00ffff irq 16 at device 11.0 on pci0 Oct 26 19:53:12 lucifer kernel: miibus0: on bge0 Oct 26 19:53:12 lucifer kernel: brgphy0: on miibus0 Oct 26 19:53:12 lucifer kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Oct 26 19:53:12 lucifer kernel: bge0: Ethernet address: 00:0c:76:7f:f1:be Oct 26 19:53:12 lucifer kernel: atapci0: port 0xd400-0xd4ff,0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 irq 20 at device 15.0 on pci0 Oct 26 19:53:12 lucifer kernel: ata2: channel #0 on atapci0 Oct 26 19:53:12 lucifer kernel: ata3: channel #1 on atapci0 Oct 26 19:53:12 lucifer kernel: atapci1: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 Oct 26 19:53:12 lucifer kernel: ata0: channel #0 on atapci1 Oct 26 19:53:12 lucifer kernel: ata1: channel #1 on atapci1 Oct 26 19:53:12 lucifer kernel: uhci0: port 0xdc00-0xdc1f irq 21 at device 16.0 on pci0 Oct 26 19:53:12 lucifer kernel: uhci0: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: usb0: on uhci0 Oct 26 19:53:12 lucifer kernel: usb0: USB revision 1.0 Oct 26 19:53:12 lucifer kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 26 19:53:12 lucifer kernel: uhub0: 2 ports with 2 removable, self powered Oct 26 19:53:12 lucifer kernel: uhci1: port 0xe000-0xe01f irq 21 at device 16.1 on pci0 Oct 26 19:53:12 lucifer kernel: uhci1: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: usb1: on uhci1 Oct 26 19:53:12 lucifer kernel: usb1: USB revision 1.0 Oct 26 19:53:12 lucifer kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 26 19:53:12 lucifer kernel: uhub1: 2 ports with 2 removable, self powered Oct 26 19:53:12 lucifer kernel: uhci2: port 0xe400-0xe41f irq 21 at device 16.2 on pci0 Oct 26 19:53:12 lucifer kernel: uhci2: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: usb2: on uhci2 Oct 26 19:53:12 lucifer kernel: usb2: USB revision 1.0 Oct 26 19:53:12 lucifer kernel: uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 26 19:53:12 lucifer kernel: uhub2: 2 ports with 2 removable, self powered Oct 26 19:53:12 lucifer kernel: pci0: at device 16.4 (no driver attached) Oct 26 19:53:12 lucifer kernel: isab0: at device 17.0 on pci0 Oct 26 19:53:12 lucifer kernel: isa0: on isab0 Oct 26 19:53:12 lucifer kernel: pcm0: port 0xec00-0xecff irq 22 at device 17.5 on pci0 Oct 26 19:53:12 lucifer kernel: pcm0: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: pcm0: Oct 26 19:53:12 lucifer kernel: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 Oct 26 19:53:12 lucifer kernel: fdc0: [FAST] Oct 26 19:53:12 lucifer kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Oct 26 19:53:12 lucifer kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Oct 26 19:53:12 lucifer kernel: sio0: port may not be enabled Oct 26 19:53:12 lucifer kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Oct 26 19:53:12 lucifer kernel: sio0: type 16550A Oct 26 19:53:12 lucifer kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 Oct 26 19:53:12 lucifer kernel: sio1: type 16550A Oct 26 19:53:12 lucifer kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Oct 26 19:53:12 lucifer kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Oct 26 19:53:12 lucifer kernel: kbd0 at atkbd0 Oct 26 19:53:12 lucifer kernel: atkbd0: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: psm0: irq 12 on atkbdc0 Oct 26 19:53:12 lucifer kernel: psm0: [GIANT-LOCKED] Oct 26 19:53:12 lucifer kernel: psm0: model IntelliMouse Explorer, device ID 4 Oct 26 19:53:12 lucifer kernel: orm0: at iomem 0xd0000-0xd3fff,0xc0000-0xcefff on isa0 Oct 26 19:53:12 lucifer kernel: ppc0: cannot reserve I/O port range Oct 26 19:53:12 lucifer kernel: sc0: at flags 0x100 on isa0 Oct 26 19:53:12 lucifer kernel: sc0: VGA <16 virtual consoles, flags=0x300> Oct 26 19:53:12 lucifer kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Oct 26 19:53:12 lucifer kernel: Timecounters tick every 0.976 msec Oct 26 19:53:12 lucifer kernel: acd0: DVDROM at ata1-master UDMA33 Oct 26 19:53:12 lucifer kernel: ad4: 76351MB [155127/16/63] at ata2-master SATA150 Oct 26 19:53:12 lucifer kernel: ad6: 76351MB [155127/16/63] at ata3-master SATA150 Oct 26 19:53:12 lucifer kernel: SMP: AP CPU #1 Launched! Oct 26 19:53:12 lucifer kernel: Mounting root from ufs:/dev/ad4s1a Oct 26 19:55:31 lucifer su: speijnik to root on /dev/ttyp0 Oct 26 22:01:28 lucifer kernel: ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=147152363 Oct 26 22:01:28 lucifer kernel: ntfs_procfixups: magic doesn't match: 00000000 != 454c4946 Oct 26 22:01:28 lucifer kernel: ntfs_loadntnode: BAD MFT RECORD 2404 Oct 26 22:01:28 lucifer kernel: ntfs_findvattr: FAILED TO LOAD INO: 2404 Oct 26 22:01:28 lucifer kernel: ntfs_strategy: ntfs_readattr failed Oct 26 22:01:28 lucifer kernel: vnode_pager_getpages: I/O read error Oct 26 22:01:28 lucifer kernel: vm_fault: pager read error, pid 1312 (cp) Oct 26 22:01:28 lucifer kernel: ntfs_procfixups: magic doesn't match: 00000000 != 454c4946 Oct 26 22:01:28 lucifer kernel: ntfs_loadntnode: BAD MFT RECORD 2405 Oct 26 22:01:28 lucifer kernel: ntfs_findvattr: FAILED TO LOAD INO: 2405 Oct 26 22:01:28 lucifer kernel: ntfs_strategy: ntfs_readattr failed Oct 26 22:01:28 lucifer kernel: vnode_pager_getpages: I/O read error Oct 26 22:01:28 lucifer kernel: vm_fault: pager read error, pid 1312 (cp) Oct 26 22:01:28 lucifer kernel: ntfs_procfixups: magic doesn't match: 00000000 != 454c4946 Oct 26 22:01:28 lucifer kernel: ntfs_loadntnode: BAD MFT RECORD 2406 Oct 26 22:01:28 lucifer kernel: ntfs_findvattr: FAILED TO LOAD INO: 2406 Oct 26 22:01:28 lucifer kernel: ntfs_strategy: ntfs_readattr failed Oct 26 22:01:28 lucifer kernel: vnode_pager_getpages: I/O read error Oct 26 22:01:28 lucifer kernel: vm_fault: pager read error, pid 1312 (cp) Oct 26 22:01:29 lucifer kernel: ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=147166427 Oct 26 22:01:34 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:02:09 lucifer last message repeated 7 times Oct 26 22:03:59 lucifer last message repeated 22 times Oct 26 22:04:04 lucifer su: speijnik to root on /dev/ttyp4 Oct 26 22:04:04 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:04:39 lucifer last message repeated 7 times Oct 26 22:04:54 lucifer last message repeated 3 times Oct 26 22:04:56 lucifer su: speijnik to root on /dev/ttyp0 Oct 26 22:04:59 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:05:34 lucifer last message repeated 7 times Oct 26 22:07:39 lucifer last message repeated 25 times Oct 26 22:07:43 lucifer su: speijnik to root on /dev/ttyp2 Oct 26 22:07:44 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:08:14 lucifer last message repeated 6 times Oct 26 22:10:14 lucifer last message repeated 24 times Oct 26 22:16:39 lucifer last message repeated 77 times Oct 26 22:16:39 lucifer su: speijnik to root on /dev/ttyp3 Oct 26 22:16:44 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:17:14 lucifer last message repeated 6 times Oct 26 22:17:14 lucifer su: speijnik to root on /dev/ttyp0 Oct 26 22:17:19 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 26 22:17:54 lucifer last message repeated 7 times Oct 26 22:19:59 lucifer last message repeated 25 times Oct 26 22:30:03 lucifer last message repeated 121 times Oct 26 22:40:08 lucifer last message repeated 121 times Oct 26 22:50:13 lucifer last message repeated 121 times Oct 26 23:00:13 lucifer last message repeated 120 times Oct 26 23:10:13 lucifer last message repeated 120 times Oct 26 23:20:13 lucifer last message repeated 120 times Oct 26 23:30:13 lucifer last message repeated 120 times Oct 26 23:40:18 lucifer last message repeated 121 times Oct 26 23:50:18 lucifer last message repeated 120 times Oct 26 23:59:58 lucifer last message repeated 116 times Oct 27 00:00:03 lucifer kernel: ad6: WARNING - READ_DMA interrupt was seen but timeout fired LBA=147166427 Oct 27 00:00:37 lucifer last message repeated 7 times Oct 27 00:02:38 lucifer last message repeated 24 times Oct 27 00:12:42 lucifer last message repeated 121 times Oct 27 00:22:47 lucifer last message repeated 121 times Oct 27 00:32:47 lucifer last message repeated 120 times Oct 27 00:42:47 lucifer last message repeated 120 times Oct 27 00:52:47 lucifer last message repeated 120 times Oct 27 01:02:47 lucifer last message repeated 120 times Oct 27 01:12:47 lucifer last message repeated 120 times Oct 27 01:22:47 lucifer last message repeated 120 times Oct 27 01:32:47 lucifer last message repeated 120 times Oct 27 01:42:46 lucifer last message repeated 120 times Oct 27 01:52:51 lucifer last message repeated 121 times Oct 27 02:02:51 lucifer last message repeated 120 times Oct 27 02:12:51 lucifer last message repeated 120 times Oct 27 02:22:51 lucifer last message repeated 120 times Oct 27 02:32:51 lucifer last message repeated 120 times Oct 27 02:42:51 lucifer last message repeated 120 times Oct 27 02:52:51 lucifer last message repeated 120 times Oct 27 03:02:50 lucifer last message repeated 120 times Oct 27 03:12:50 lucifer last message repeated 120 times Oct 27 03:22:50 lucifer last message repeated 120 times Oct 27 03:32:50 lucifer last message repeated 120 times Oct 27 03:42:50 lucifer last message repeated 120 times Oct 27 03:52:50 lucifer last message repeated 120 times Oct 27 04:02:50 lucifer last message repeated 120 times Oct 27 04:12:55 lucifer last message repeated 121 times Oct 27 04:22:55 lucifer last message repeated 120 times Oct 27 04:32:55 lucifer last message repeated 120 times Oct 27 04:42:54 lucifer last message repeated 120 times Oct 27 04:52:54 lucifer last message repeated 120 times Oct 27 05:02:54 lucifer last message repeated 120 times Oct 27 05:12:54 lucifer last message repeated 120 times Oct 27 05:22:54 lucifer last message repeated 120 times Oct 27 05:32:54 lucifer last message repeated 120 times Oct 27 05:42:54 lucifer last message repeated 120 times Oct 27 05:52:54 lucifer last message repeated 120 times Oct 27 06:02:53 lucifer last message repeated 120 times Oct 27 06:12:53 lucifer last message repeated 120 times Oct 27 06:22:58 lucifer last message repeated 121 times Oct 27 06:32:58 lucifer last message repeated 120 times Oct 27 06:42:58 lucifer last message repeated 120 times Oct 27 06:52:58 lucifer last message repeated 120 times As I wrote, if that doesn't happen on the system hdd the only problem it causes is a slowdown of the system in gernal and it makes you unable to unmount the problem drive/partition. This means it is not a NTFS-only problem, as it happens to UFS partitions aswell. I am sure this is not a hardware problem as everything is working fine under other Operating Systems (including Fedora Core2 x86_64, FreeBSD 5.x i386 and Windows XP 32/64bit). >How-To-Repeat: Unknown, randomly happens after some time. However, it tends to happen under rather high CPU load (>50%) and/or when heavily accessing the HDD. I got the errors above while copying about 20 files with a size of 3-4M each. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 02:25:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7292516A4CE; Fri, 29 Oct 2004 02:25:36 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C1ED43D55; Fri, 29 Oct 2004 02:25:32 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CNMUy-0005Vk-CE; Fri, 29 Oct 2004 10:28:18 +0800 Message-Id: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Fri, 29 Oct 2004 10:25:07 +0900 To: obrien@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM continues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 02:25:36 -0000 Hi, >By chance, have you tried both with 4GB per CPU and with all 8GB on one >CPU? Did it make a difference? With 4GB RAM I compiled kernel without ATA support and tried new kernel with 8GB RAM. Still same result, not working. Next I will try to compile kernel without SMP support and let's see. I have to make binary update again, since after putting 8GB RAM file system was corrupted. If kernel without SMP will not work I don't know what to do. I will be desperate. Please let me know if there is anything I can try. >I would enable the SRAT table, but do keep disabled the Node memory >interleave. FreeBSD will not use the SRAT table, but with it >ON/Enabled/AUTO I know the CPU will be set up a certain way that we do >want. > > > HPET Timer -> Enabled > > ECC -> Enabled > > DRAM ECC -> Enabled > > ECC Scrub Redirection -> Disabled > >I would turn on ECC Scrub Redirection, but thats just to gain reliability. I tried settings in BIOS setup as you suggested. No difference. >I would also download the latest memtest86+ ISO image from >www.memtest.org, burn it to CDROM, and see if all your RAM passes. I >assume it is IBM [re]branded? I checked memory with memtest. No errors, passed everything. Ganbold >-- >-- David (obrien@FreeBSD.org) > > > >__________ NOD32 1.909 (20041028) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 03:19:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B1B516A4CE; Fri, 29 Oct 2004 03:19:55 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BBA543D2F; Fri, 29 Oct 2004 03:19:55 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9T3Jsr3014087; Thu, 28 Oct 2004 20:19:54 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9T3JpSi014086; Thu, 28 Oct 2004 20:19:51 -0700 (PDT) (envelope-from obrien) Date: Thu, 28 Oct 2004 20:19:51 -0700 From: "David O'Brien" To: Ganbold Message-ID: <20041029031951.GA13963@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> <20041027024512.GA54432@dragon.nuxi.com> <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> <20041027165534.GA73113@dragon.nuxi.com> <6.1.2.0.2.20041028101119.02b18950@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.2.0.2.20041028101119.02b18950@202.179.0.80> User-Agent: Mutt/1.4.1i 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 cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 03:19:55 -0000 On Thu, Oct 28, 2004 at 10:18:11AM +0900, Ganbold wrote: > >> >An IBM e325 has only 6 DIMM slots, specifically what RAM configuration > >> >are you using? Do you have ECC turned on? Are using DRAM scrubbing? > >> >What is your BIOS memory interleaving settings? > >> > >> I have 2GB x 4 = 8GB RAM and ECC is turned on and I have following > >> settings in BIOS: > > > >By chance, have you tried both with 4GB per CPU and with all 8GB on one > >CPU? Did it make a difference? > > You mean kernel compiled without SMP options? No. You have 6 DIMM slots and 4 DIMM's. So there are two ways to install the memory -- CPU0 gets all 4 DIMM's; or CPU0 gets 2 DIMM's and CPU1 gets 2 DIMM's. > >> 4GB Memory Hole adjust -> AUTO > > > >I would turn this off (disable). > > This has only 2 options, AUTO and Manual. If I select Manual, I have to > adjust 4GB memory hole size, which > has 64mb, 128mb, 256mb, 512mb, 1gb options. What should I choose? Go with AUTO then. You don't want anything special happening. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 03:34:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FDCB16A4CE; Fri, 29 Oct 2004 03:34:19 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F1843D5F; Fri, 29 Oct 2004 03:34:19 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9T3YIqJ014406; Thu, 28 Oct 2004 20:34:18 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9T3YGe4014404; Thu, 28 Oct 2004 20:34:16 -0700 (PDT) (envelope-from obrien) Date: Thu, 28 Oct 2004 20:34:16 -0700 From: "David O'Brien" To: Ganbold Message-ID: <20041029033416.GC13963@dragon.nuxi.com> References: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> User-Agent: Mutt/1.4.1i 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 cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM continues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 03:34:19 -0000 On Fri, Oct 29, 2004 at 10:25:07AM +0900, Ganbold wrote: > >By chance, have you tried both with 4GB per CPU and with all 8GB on one > >CPU? Did it make a difference? > > With 4GB RAM I compiled kernel without ATA support and tried new kernel > with 8GB RAM. You definately don't want to use ATA, so it is good you compiled it out. It is felt by several of us that there is a problem with ATA in >4GB systems right now. Correct me if I'm wrong -- Scott Long verified that the driver for the IBM RAID controller you are using is 64-bit clean and has no known issues on >4GB systems? > I checked memory with memtest. No errors, passed everything. That is a good sign. :-) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 03:53:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF2C616A4CE; Fri, 29 Oct 2004 03:53:41 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1A9943D2F; Fri, 29 Oct 2004 03:53:40 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CNNsL-0006Bi-Nx; Fri, 29 Oct 2004 11:56:30 +0800 Message-Id: <6.1.2.0.2.20041029115154.02b43300@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Fri, 29 Oct 2004 11:53:17 +0900 To: obrien@freebsd.org From: Ganbold In-Reply-To: <20041029031951.GA13963@dragon.nuxi.com> References: <6.1.2.0.2.20041027095212.02b38560@202.179.0.80> <20041027024512.GA54432@dragon.nuxi.com> <6.1.2.0.2.20041027111122.02b3cc20@202.179.0.80> <20041027165534.GA73113@dragon.nuxi.com> <6.1.2.0.2.20041028101119.02b18950@202.179.0.80> <20041029031951.GA13963@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 03:53:42 -0000 Hi, At 12:19 PM 10/29/2004, you wrote: >On Thu, Oct 28, 2004 at 10:18:11AM +0900, Ganbold wrote: > > >By chance, have you tried both with 4GB per CPU and with all 8GB on one > > >CPU? Did it make a difference? > > > > You mean kernel compiled without SMP options? > >No. You have 6 DIMM slots and 4 DIMM's. So there are two ways to >install the memory -- CPU0 gets all 4 DIMM's; or CPU0 gets 2 DIMM's and >CPU1 gets 2 DIMM's. OK, I got it. I tried both. Same result, no difference. > > >> 4GB Memory Hole adjust -> AUTO > > > > > >I would turn this off (disable). > > > > This has only 2 options, AUTO and Manual. If I select Manual, I have to > > adjust 4GB memory hole size, which > > has 64mb, 128mb, 256mb, 512mb, 1gb options. What should I choose? > >Go with AUTO then. You don't want anything special happening. I did so. >-- >-- David (obrien@FreeBSD.org) > > > >__________ NOD32 1.910 (20041028) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 03:55:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DCD816A4CE; Fri, 29 Oct 2004 03:55:42 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C8C843D54; Fri, 29 Oct 2004 03:55:41 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CNNuL-0006Cm-A8; Fri, 29 Oct 2004 11:58:33 +0800 Message-Id: <6.1.2.0.2.20041029115322.02b43510@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Fri, 29 Oct 2004 11:55:29 +0900 To: obrien@freebsd.org From: Ganbold In-Reply-To: <20041029033416.GC13963@dragon.nuxi.com> References: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> <20041029033416.GC13963@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: scottl@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM continues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 03:55:42 -0000 At 12:34 PM 10/29/2004, you wrote: > > With 4GB RAM I compiled kernel without ATA support and tried new kernel > > with 8GB RAM. > >You definately don't want to use ATA, so it is good you compiled it out. >It is felt by several of us that there is a problem with ATA in >4GB >systems right now. > >Correct me if I'm wrong -- Scott Long verified that the driver for the >IBM RAID controller you are using is 64-bit clean and has no known issues >on >4GB systems? Scott didn't tell me. So I thought it is clean. Maybe now he will confirm it. I'm cc-ing to him. Ganbold > > I checked memory with memtest. No errors, passed everything. > >That is a good sign. :-) > >-- >-- David (obrien@FreeBSD.org) > > > >__________ NOD32 1.910 (20041028) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 05:23:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B1816A4CE for ; Fri, 29 Oct 2004 05:23:47 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 97B4943D55 for ; Fri, 29 Oct 2004 05:23:46 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 11329 invoked by uid 513); 29 Oct 2004 05:23:47 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.59.219):SA:0(-4.9/5.0):. Processed in 6.28494 secs); 29 Oct 2004 05:23:47 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.59.219) by dsl-mail.kamp.net with SMTP; 29 Oct 2004 05:23:40 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id i9T5PNvl000704; Fri, 29 Oct 2004 07:25:24 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id i9T5PNhh000703; Fri, 29 Oct 2004 07:25:23 +0200 (CEST) (envelope-from ewinter) Date: Fri, 29 Oct 2004 07:25:23 +0200 From: "Ernst W. Winter" To: Manuel Stuehn Message-ID: <20041029052523.GA603@lobo.homeunix.org> References: <417FCE76.9040306@freenet.de> <20041027172723.GA74567@dragon.nuxi.com> <41811A85.6040301@freenet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41811A85.6040301@freenet.de> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: UFS2 on i386 and amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 05:23:47 -0000 On Thu, 28 Oct 2004, Manuel Stuehn wrote: > I've installed FreeBSD-RC1 i386 and amd64 on the my machine, as > before. But now my computer doesn't boot the i386-FreeBSD. As > bootmanager i'm using GAG[1], which worked good for me (until > now?). This are the /etc/fstabs from my installations: > > amd64-fstab: > #cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > /dev/ad4s1b none swap sw 0 0 > /dev/ad4s1a / ufs rw 1 1 > /dev/ad4s1h /usr ufs rw 2 2 > /dev/ad4s1d /usr/home ufs rw 2 2 > /dev/ad4s1e /usr/ports ufs rw 2 2 > /dev/ad4s1f /usr/src ufs rw 2 2 > /dev/ad4s1g /var ufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 > /dev/acd2 /cdrom2 cd9660 ro,noauto 0 0 > > i386-fstab: > #cat /mnt/etc/fstab > # Device Mountpoint FStype Options Dump Pass# > /dev/ad4s1b none swap sw 0 0 > /dev/ad4s2a / ufs rw 1 1 > /dev/ad4s2e /usr ufs rw 2 2 > /dev/ad4s1d /usr/home ufs rw 2 2 > /dev/ad4s1e /usr/ports ufs rw 2 2 > /dev/ad4s1f /usr/src ufs rw 2 2 > /dev/ad4s2d /var ufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 > /dev/acd2 /cdrom2 cd9660 ro,noauto 0 0 > >From a gues and my own experience I would say since both do have the same in fstab it might not be right. I had the same here and the second drive was/had a different configuraten and once I booted booted with the live CD and corrected it then it wrked fine. > I've also tried : > >> FreeBSD/i386 BOOT > Default: 0:ad(0,a)/boot/loader > boot:0:ad(2,a)/boot/loader > This worked well in my former i386-amd64 installation. But now, > everytime amd64 is booted. > > Any hints? > Again have a look when you boot form a live cd and then what your machine will tell you what they really are. Ernst From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 08:02:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from [IPv6:::1] (hub.freebsd.org [216.136.204.18]) by hub.freebsd.org (Postfix) with ESMTP id EBEDF16A4CE; Fri, 29 Oct 2004 08:02:36 +0000 (GMT) Message-ID: <4181F8AF.8030800@freebsd.org> Date: Fri, 29 Oct 2004 02:00:47 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ganbold References: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> <20041029033416.GC13963@dragon.nuxi.com> <6.1.2.0.2.20041029115322.02b43510@202.179.0.80> In-Reply-To: <6.1.2.0.2.20041029115322.02b43510@202.179.0.80> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM continues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 08:02:38 -0000 Ganbold wrote: > At 12:34 PM 10/29/2004, you wrote: > >> > With 4GB RAM I compiled kernel without ATA support and tried new kernel >> > with 8GB RAM. >> >> You definately don't want to use ATA, so it is good you compiled it out. >> It is felt by several of us that there is a problem with ATA in >4GB >> systems right now. >> >> Correct me if I'm wrong -- Scott Long verified that the driver for the >> IBM RAID controller you are using is 64-bit clean and has no known issues >> on >4GB systems? > > > Scott didn't tell me. So I thought it is clean. Maybe now he will > confirm it. > I'm cc-ing to him. > > Ganbold The ips driver looks like it will fail under heavy load when more than 4GB of RAM is present. I tries to force busdma to not defer requests when the bounce page reserve is low, but that looks to be broken and will result in corrupted commands. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 29 08:21:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C83416A4CE; Fri, 29 Oct 2004 08:21:49 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D5643D45; Fri, 29 Oct 2004 08:21:46 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CNS3p-000803-5B; Fri, 29 Oct 2004 16:24:37 +0800 Message-Id: <6.1.2.0.2.20041029161024.02b5c460@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Fri, 29 Oct 2004 16:20:04 +0900 To: Scott Long From: Ganbold In-Reply-To: <4181F8AF.8030800@freebsd.org> References: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> <20041029033416.GC13963@dragon.nuxi.com> <6.1.2.0.2.20041029115322.02b43510@202.179.0.80> <4181F8AF.8030800@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM continues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 08:21:49 -0000 At 05:00 PM 10/29/2004, you wrote: >>>Correct me if I'm wrong -- Scott Long verified that the driver for the >>>IBM RAID controller you are using is 64-bit clean and has no known issues >>>on >4GB systems? >> >>Scott didn't tell me. So I thought it is clean. Maybe now he will confirm it. >>I'm cc-ing to him. >>Ganbold > > >The ips driver looks like it will fail under heavy load when more than 4GB >of RAM is present. I tries to force busdma to not defer requests >when the bounce page reserve is low, but that looks to be broken and >will result in corrupted commands. Thanks Scott. I tried to compile kernel several different way, tried different RAM configurations and no result. With 8GB file system gets corrupted and after several boot file system becomes in unusable state. Scott, when ips driver will be fixed? Will it be ready when 5.3 release comes out? Please let me know. I'm ready to test. thanks, Ganbold >Scott > > > >__________ NOD32 1.911 (20041029) Information __________ > >This message was checked by NOD32 antivirus system. >http://www.nod32.com > From owner-freebsd-amd64@FreeBSD.ORG Sat Oct 30 19:30:19 2004 Return-Path: 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 0A0D816A4CE for ; Sat, 30 Oct 2004 19:30:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0D5943D3F for ; Sat, 30 Oct 2004 19:30:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9UJUI1s080031 for ; Sat, 30 Oct 2004 19:30:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9UJUI3Z080030; Sat, 30 Oct 2004 19:30:18 GMT (envelope-from gnats) Resent-Date: Sat, 30 Oct 2004 19:30:18 GMT Resent-Message-Id: <200410301930.i9UJUI3Z080030@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Sean McNeil Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A97BB16A4CE for ; Sat, 30 Oct 2004 19:25:52 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CE7E43D31 for ; Sat, 30 Oct 2004 19:25:52 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i9UJPoa8038930 for ; Sat, 30 Oct 2004 19:25:50 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i9UJPoNr038928; Sat, 30 Oct 2004 19:25:50 GMT (envelope-from nobody) Message-Id: <200410301925.i9UJPoNr038928@www.freebsd.org> Date: Sat, 30 Oct 2004 19:25:50 GMT From: Sean McNeil To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73322: unarchiving /etc to msdos fs locks up amd64 system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 19:30:19 -0000 >Number: 73322 >Category: amd64 >Synopsis: unarchiving /etc to msdos fs locks up amd64 system >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 30 19:30:18 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Sean McNeil >Release: 6.0-CURRENT >Organization: Sean McNeil Consulting >Environment: FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #46: Fri Oct 29 14:37:40 PDT 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 >Description: Certain functionality appears to be broken with the msdos filesystem. With a usb pen drive (either uhci or ehci) I can read and write files but if I attempt to unarchive /etc it will cause my system to lock up without a trace or going to debug. This could be an issue with USB. I do not have another type of device with an msdos filesystem to verify. >How-To-Repeat: /etc/malloc.conf is a symlink to "aj" mount an msdos filesystem to /mnt cd / tar cf - etc | (cd /mnt; tar xvf -) system locks up on me every time. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Oct 30 19:40:30 2004 Return-Path: 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 2B40016A4CE for ; Sat, 30 Oct 2004 19:40:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F23D943D49 for ; Sat, 30 Oct 2004 19:40:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9UJeTtQ081143 for ; Sat, 30 Oct 2004 19:40:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9UJeTkY081142; Sat, 30 Oct 2004 19:40:29 GMT (envelope-from gnats) Date: Sat, 30 Oct 2004 19:40:29 GMT Message-Id: <200410301940.i9UJeTkY081142@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Nicolas Blais Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nicolas Blais List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 19:40:30 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Nicolas Blais To: freebsd-gnats-submit@freebsd.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Sat, 30 Oct 2004 15:35:54 -0400 How come the patch exists.... works perfectly.... and isn't being commited? Nicolas.