From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 18:18:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A98B16A444 for ; Sun, 13 Nov 2005 18:18:36 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0F4C43D46 for ; Sun, 13 Nov 2005 18:18:34 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id E4513F820 for ; Sun, 13 Nov 2005 11:18:31 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id ABF58F7C5 for ; Sun, 13 Nov 2005 11:18:31 -0700 (MST) Date: Sun, 13 Nov 2005 11:18:30 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051113111830.4ce6563e.kgunders@teamcool.net> In-Reply-To: References: Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: FreeBSD 5.4 or 6.0 as postgresql-server X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 18:18:36 -0000 On Fri, 11 Nov 2005 10:18:10 -0500 Vivek Khera wrote: > > On Nov 9, 2005, at 5:47 PM, Claus Guttesen wrote: > > > Since 6.0 just came out the door it may be premature to ask whether I > > should go for RELENG_6_0 or 5.4 (RELENG_5). The server will only be > > doing postgresql 7.4.9. Is anyone running postgresql with 8 GB RAM or > > more on 6.0? > > > > Our current (and slightly smaller hardware-wise) db-server is running > > RELENG_5_4 but I'd like to get the improved smp-, disk- and > > network-related improvements in 6.0. > > I'm running 5.4-REL on Tyan K8SR boards with dual opterons at 4GB, > LSI 320-2X RAID cards configured with a 2 disk RAID1 for system + PG > log and 6 disk RAID10 for data. > > However, I do not run the onboard BGE nics. I use a plug-in Intel > dual gigabit nic. We had some lockups with the bge onboard until we > switched to the Intels. > > Postgres 8.0.4 runs non-stop and with great speed. > > I just took delivery (and will be putting into full-load pre- > production testing today) a similar system (it has more disks is the > major difference) with FreeBSD 6.0-REL. So far my experience with a > couple of other 6.0/amd64 systems (one in production) has been > positive. I don't anticipate any problems, but do expect some > improvements in concurrency to the disk. > > I've been avoiding > 4GB RAM because of issues I hear others have > been having, such as yours... One of these days I'll try it I'm sure. Vivek: I'd be interested in your experiences w/6.0. Would you mind testing the onboard bge nics at the kind of loads that was causing them to puke under 5.4? I've got same system and as of yet not encountered issues w/ the onboard bge nics. The machine is also at the latest BIOS, however, so that may contribute as well. TIA-- -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 19:39:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 358FE16A41F for ; Sun, 13 Nov 2005 19:39:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A70343D49 for ; Sun, 13 Nov 2005 19:39:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 316FF1A3C24; Sun, 13 Nov 2005 11:39:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9C31B5138F; Sun, 13 Nov 2005 14:39:24 -0500 (EST) Date: Sun, 13 Nov 2005 14:39:24 -0500 From: Kris Kennaway To: Sean McNeil Message-ID: <20051113193924.GA63606@xor.obsecurity.org> References: <43743466.2050909@gmail.com> <43743CC5.9070801@freebsd.org> <200511111131.36948.peter@wemm.org> <20051111200558.GA64077@troutmask.apl.washington.edu> <20051111202334.GA64218@troutmask.apl.washington.edu> <43750645.1040906@gmail.com> <20051111233800.GA16215@xor.obsecurity.org> <1131752430.84095.5.camel@triton.mcneil.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <1131752430.84095.5.camel@triton.mcneil.com> User-Agent: Mutt/1.4.2.1i Cc: Kris Moore , freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: Question about x64 and running x86 programs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 19:39:31 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 11, 2005 at 03:40:30PM -0800, Sean McNeil wrote: > On Fri, 2005-11-11 at 18:38 -0500, Kris Kennaway wrote: > > On Fri, Nov 11, 2005 at 12:59:49PM -0800, Kris Moore wrote: > > >=20 > > > Figured I'd give you guys an update on this also. I got all the=20 > > > libraries loaded, and everything into place, but it seems the suppot = is=20 > > > only "so-so" at best. About every other binary crashes, or segfaults= =20 > > > with varying errors. I have quite a few QT programs, and they are all= =20 > > > compiled on the same machine, with the same libs and such, but its=20 > > > really hit-n-miss on which ones work. Anybody know if the 32bit binar= y /=20 > > > shared library support is really still this shaky? > >=20 > > It's a work-in-progress, and you're doing something pretty extreme > > with it.. >=20 > Will this work be MFCd to 6, or will it stay only in 7? I'm sure whatever can be merged will be. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDd5ZsWry0BWjoQKURAqMlAKD+FciyGTWo5mt4UTarzD+rdefZEACfV/AC 6ZaDhUMuFwOxSzSFfnFcquI= =yN8K -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 19:40:27 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C5916A420; Sun, 13 Nov 2005 19:40:27 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62F1243D46; Sun, 13 Nov 2005 19:40:27 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jADJeR61032324; Sun, 13 Nov 2005 19:40:27 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jADJeQej032308; Sun, 13 Nov 2005 19:40:26 GMT (envelope-from kris) Date: Sun, 13 Nov 2005 19:40:26 GMT From: Kris Kennaway Message-Id: <200511131940.jADJeQej032308@freefall.freebsd.org> To: apn@bepolytech.be, kris@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/88746: Buffer problem with SSH2 under amd64 arch. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 19:40:27 -0000 Synopsis: Buffer problem with SSH2 under amd64 arch. State-Changed-From-To: open->feedback State-Changed-By: kris State-Changed-When: Sun Nov 13 19:39:59 GMT 2005 State-Changed-Why: I answered this question when you asked it on Usenet, but didn't yet see your response. http://www.freebsd.org/cgi/query-pr.cgi?pr=88746 From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 19:43:16 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CF4216A420; Sun, 13 Nov 2005 19:43:16 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B1C43D46; Sun, 13 Nov 2005 19:43:16 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jADJhGsD032453; Sun, 13 Nov 2005 19:43:16 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jADJhFO0032449; Sun, 13 Nov 2005 19:43:15 GMT (envelope-from kris) Date: Sun, 13 Nov 2005 19:43:15 GMT From: Kris Kennaway Message-Id: <200511131943.jADJhFO0032449@freefall.freebsd.org> To: fernando@schapachnik.com.ar, kris@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 19:43:16 -0000 Synopsis: Reproducable panic running OO/linux on 6.0/AMD64 State-Changed-From-To: open->analyzed State-Changed-By: kris State-Changed-When: Sun Nov 13 19:42:54 GMT 2005 State-Changed-Why: This is believed to be fixed in 6.0-STABLE, can you please update and confirm? http://www.freebsd.org/cgi/query-pr.cgi?pr=88884 From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 20:40:16 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F11CF16A420 for ; Sun, 13 Nov 2005 20:40:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C077843D45 for ; Sun, 13 Nov 2005 20:40:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jADKeG8Y041378 for ; Sun, 13 Nov 2005 20:40:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jADKeGqo041377; Sun, 13 Nov 2005 20:40:16 GMT (envelope-from gnats) Date: Sun, 13 Nov 2005 20:40:16 GMT Message-Id: <200511132040.jADKeGqo041377@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Ilya Sher Cc: Subject: Re: amd64/87316: [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ilya Sher List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 20:40:17 -0000 The following reply was made to PR amd64/87316; it has been noted by GNATS. From: Ilya Sher To: bug-followup@FreeBSD.org, ilya79@actcom.net.il Cc: Subject: Re: amd64/87316: [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd64 Date: Sun, 13 Nov 2005 22:38:16 +0200 > if_vge does work on the same system it only worked for 2 reboots * loading if_vge later does not help * the problem narrowed down to if_vge.c: vge_miibus_readreg(): /* Wait for the read command bit to self-clear. */ for (i = 0; i < VGE_TIMEOUT; i++) { DELAY(1); if ((CSR_READ_1(sc, VGE_MIICMD) & VGE_MIICMD_RCMD) == 0) break; } Looks like the bit is not automagically cleared. From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 22:03:23 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD9B16A421; Sun, 13 Nov 2005 22:03:23 +0000 (GMT) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (www.cursosvirtuales.com.ar [200.59.46.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E244D43D5A; Sun, 13 Nov 2005 22:03:16 +0000 (GMT) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (localhost [127.0.0.1]) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11) with ESMTP id jADM3AVf005990; Sun, 13 Nov 2005 19:03:11 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from schapachnik.com.ar (uucp@localhost) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11/Submit) with UUCP id jADM3Alr005989; Sun, 13 Nov 2005 19:03:10 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from funes.schapachnik.com.ar (localhost [127.0.0.1]) by funes.schapachnik.com.ar (8.13.4/8.13.4) with ESMTP id jADM2w3U000865; Sun, 13 Nov 2005 19:02:58 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: (from fpscha@localhost) by funes.schapachnik.com.ar (8.13.4/8.13.4/Submit) id jADM2we0000864; Sun, 13 Nov 2005 19:02:58 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) X-Authentication-Warning: funes.schapachnik.com.ar: fpscha set sender to fernando@schapachnik.com.ar using -f Date: Sun, 13 Nov 2005 19:02:58 -0300 From: Fernando Schapachnik To: Kris Kennaway Message-ID: <20051113220258.GA833@funes.schapachnik.com.ar> References: <200511131943.jADJhFO0032449@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200511131943.jADJhFO0032449@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i X-OS: FreeBSD 6.0 - http://www.freebsd.org Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 22:03:23 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit En un mensaje anterior, Kris Kennaway escribió: > Synopsis: Reproducable panic running OO/linux on 6.0/AMD64 > > State-Changed-From-To: open->analyzed > State-Changed-By: kris > State-Changed-When: Sun Nov 13 19:42:54 GMT 2005 > State-Changed-Why: > This is believed to be fixed in 6.0-STABLE, can you please > update and confirm? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=88884 CVSup yesterday. Find attached the kernel bt. What's strange is that if I run it from the shell, it is Ok. The problem is when I click on the kicker icon (KDE 3.4.2). It's strange because it calls the same shell script to lauch OO. Fernando P. Schapachnik fernando@schapachnik.com.ar --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=typescript [247]funes:/var/crash>kgdb -n 3 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: panic: kmem_malloc(1335996416): kmem_map too small: 5197824 total allocated Uptime: 2h6m48s Dumping 991 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 991MB (253648 pages) 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff803b74d7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #3 0xffffffff803b7b56 in panic (fmt=0xffffff0029f434c0 "@\023\005+") at /usr/src/sys/kern/kern_shutdown.c:555 #4 0xffffffff80553e62 in kmem_malloc (map=0xffffff003c270160, size=1335996416, flags=258) at /usr/src/sys/vm/vm_kern.c:299 #5 0xffffffff8054cae3 in uma_large_malloc (size=1335996416, wait=258) at /usr/src/sys/vm/uma_core.c:2715 #6 0xffffffff803ab42b in malloc (size=0, mtp=0xffffffff807b3620, flags=258) at /usr/src/sys/kern/kern_malloc.c:330 #7 0xffffffff80420a43 in vfs_read_dirent (ap=0xffffffffa6c3d8a0, dp=0x0, off=0) at /usr/src/sys/kern/vfs_subr.c:3877 #8 0xffffffff80359e74 in devfs_readdir (ap=0xffffffffa6c3d8a0) at /usr/src/sys/fs/devfs/devfs_vnops.c:828 #9 0xffffffff805dd83d in VOP_READDIR_APV (vop=0x0, a=0x0) at vnode_if.c:1427 #10 0xffffffff805d25ff in getdents_common (td=0xffffff0029f434c0, args=0xffffffffa6c3dba0, is64bit=1) at vnode_if.h:746 #11 0xffffffff805cb06a in ia32_syscall (frame= {tf_rdi = 3, tf_rsi = 6, tf_rdx = 4096, tf_rcx = 135168056, tf_r8 = 0, tf_r9 = 0, tf_rax = 220, tf_rbx = 3, tf_rbp = 4294956648, tf_r10 = 0, tf_r11 = 0, tf_r12 = 0, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = 135172152, tf_flags = 0, tf_err = 2, tf_rip = 672771129, tf_cs = 27, tf_rflags = 58 2, tf_rsp = 4294956572, tf_ss = 35}) at /usr/src/sys/amd64/ia32/ia32_syscall.c:186 #12 0xffffffff8057e74d in Xint0x80_syscall () at ia32_exception.S:64 #13 0x000000002819ac39 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) [248]funes:/var/crash>uname -a FreeBSD funes.schapachnik.com.ar 6.0-STABLE FreeBSD 6.0-STABLE #19: Sun Nov 13 12:29:44 ART 2005 root@funes.schapachnik.com.ar:/usr/obj/usr/src/sys/FUNES2 amd64 Script done on Sun Nov 13 18:56:59 2005 --7AUc2qLy4jB3hD7Z-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 22:15:57 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2AC316A41F; Sun, 13 Nov 2005 22:15:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61AF143D46; Sun, 13 Nov 2005 22:15:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 35AB91A3C19; Sun, 13 Nov 2005 14:15:57 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 080AD513BA; Sun, 13 Nov 2005 17:15:55 -0500 (EST) Date: Sun, 13 Nov 2005 17:15:55 -0500 From: Kris Kennaway To: Fernando Schapachnik Message-ID: <20051113221555.GA10425@xor.obsecurity.org> References: <200511131943.jADJhFO0032449@freefall.freebsd.org> <20051113220258.GA833@funes.schapachnik.com.ar> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <20051113220258.GA833@funes.schapachnik.com.ar> User-Agent: Mutt/1.4.2.1i Cc: Kris Kennaway , freebsd-amd64@FreeBSD.org Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 22:15:57 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 13, 2005 at 07:02:58PM -0300, Fernando Schapachnik wrote: > En un mensaje anterior, Kris Kennaway escribi?: > > Synopsis: Reproducable panic running OO/linux on 6.0/AMD64 > >=20 > > State-Changed-From-To: open->analyzed > > State-Changed-By: kris > > State-Changed-When: Sun Nov 13 19:42:54 GMT 2005 > > State-Changed-Why:=20 > > This is believed to be fixed in 6.0-STABLE, can you please > > update and confirm? > >=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D88884 >=20 > CVSup yesterday. Find attached the kernel bt. I think it was only merged yesterday, so you may not yet have the fix. Please try again. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDd7saWry0BWjoQKURAr3nAJ0a6vwFLu4nS/I4R9TzM91HsdK/mwCgxIXn HLQakEF9mvm/6tq5oIRFhoY= =BsuH -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 23:30:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E04116A41F for ; Sun, 13 Nov 2005 23:30:35 +0000 (GMT) (envelope-from rschi@rsmba.biz) Received: from admin.cablespeed.com (admin.cablespeed.com [216.15.205.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4123543D46 for ; Sun, 13 Nov 2005 23:30:34 +0000 (GMT) (envelope-from rschi@rsmba.biz) Received: from [66.235.9.146] (account schilling@cablespeed.com HELO [192.168.2.2]) by admin.cablespeed.com (CommuniGate Pro SMTP 4.2.10) with ESMTP id 61496102 for freebsd-amd64@freebsd.org; Sun, 13 Nov 2005 17:30:34 -0600 Message-ID: <4377CD61.1040700@rsmba.biz> Date: Sun, 13 Nov 2005 15:33:53 -0800 From: Richard Schilling Organization: Richard Schilling, MBA User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050318 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: buildworld failing on libalias, amd64, RELENG_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 23:30:35 -0000 Still having problems running make buildworld. It crashes when trying to build libalias. Any information how libalias is generated and built would be helpful. There are no files at all in the directory /usr/src/lib/libalias. Not sure why they aren't generated. uname -a output: FreeBSD newbox.cognitiongroup.biz 6.0-STABLE FreeBSD 6.0-STABLE #3: Fri Nov 4 23:36:56 PST 2005 rschilling@newbox.cognitiongroup.biz:/usr/obj/usr/src/sys/PRODUCTION amd64 Here's the error ===> lib/libalias (all) make: don't know how to make /usr/src/lib/libalias/alias.c. Stop *** Error code 2 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 13 23:59:33 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85A2516A422; Sun, 13 Nov 2005 23:59:33 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2225643D75; Sun, 13 Nov 2005 23:59:30 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 0B97172DD4; Sun, 13 Nov 2005 15:59:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 05E2572DCB; Sun, 13 Nov 2005 15:59:30 -0800 (PST) Date: Sun, 13 Nov 2005 15:59:29 -0800 (PST) From: Doug White To: Fernando Schapachnik In-Reply-To: <20051113220258.GA833@funes.schapachnik.com.ar> Message-ID: <20051113155908.U7337@carver.gumbysoft.com> References: <200511131943.jADJhFO0032449@freefall.freebsd.org> <20051113220258.GA833@funes.schapachnik.com.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Kris Kennaway , freebsd-amd64@FreeBSD.org Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 23:59:33 -0000 On Sun, 13 Nov 2005, Fernando Schapachnik wrote: > CVSup yesterday. Find attached the kernel bt. > > What's strange is that if I run it from the shell, it is Ok. The problem > is when I click on the kicker icon (KDE 3.4.2). It's strange because > it calls the same shell script to lauch OO. For the record, this is a duplicate of kern/88249. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 02:35:55 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3307916A422; Mon, 14 Nov 2005 02:35:55 +0000 (GMT) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (www.cursosvirtuales.com.ar [200.59.46.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71DD443D46; Mon, 14 Nov 2005 02:35:50 +0000 (GMT) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (localhost [127.0.0.1]) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11) with ESMTP id jAE2ZhDD012453; Sun, 13 Nov 2005 23:35:43 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from schapachnik.com.ar (uucp@localhost) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11/Submit) with UUCP id jAE2Zhgg012452; Sun, 13 Nov 2005 23:35:43 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from funes.schapachnik.com.ar (localhost [127.0.0.1]) by funes.schapachnik.com.ar (8.13.4/8.13.4) with ESMTP id jAE2ZbcA001028; Sun, 13 Nov 2005 23:35:37 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: (from fpscha@localhost) by funes.schapachnik.com.ar (8.13.4/8.13.4/Submit) id jAE2ZaRO001027; Sun, 13 Nov 2005 23:35:36 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) X-Authentication-Warning: funes.schapachnik.com.ar: fpscha set sender to fernando@schapachnik.com.ar using -f Date: Sun, 13 Nov 2005 23:35:36 -0300 From: Fernando Schapachnik To: Kris Kennaway Message-ID: <20051114023536.GA1015@funes.schapachnik.com.ar> References: <200511131943.jADJhFO0032449@freefall.freebsd.org> <20051113220258.GA833@funes.schapachnik.com.ar> <20051113221555.GA10425@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20051113221555.GA10425@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i X-OS: FreeBSD 6.0 - http://www.freebsd.org Cc: Kris Kennaway , freebsd-amd64@FreeBSD.org Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 02:35:55 -0000 En un mensaje anterior, Kris Kennaway escribió: > I think it was only merged yesterday, so you may not yet have the fix. > Please try again. That solved it. Please close the bug report. Fernando P. Schapachnik fernando@schapachnik.com.ar From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 02:52:53 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2604F16A420; Mon, 14 Nov 2005 02:52:53 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D61CF43D4C; Mon, 14 Nov 2005 02:52:52 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAE2qqjP096621; Mon, 14 Nov 2005 02:52:52 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAE2qqFJ096617; Mon, 14 Nov 2005 02:52:52 GMT (envelope-from kris) Date: Mon, 14 Nov 2005 02:52:52 GMT From: Kris Kennaway Message-Id: <200511140252.jAE2qqFJ096617@freefall.freebsd.org> To: fernando@schapachnik.com.ar, kris@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/88884: Reproducable panic running OO/linux on 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 02:52:53 -0000 Synopsis: Reproducable panic running OO/linux on 6.0/AMD64 State-Changed-From-To: analyzed->closed State-Changed-By: kris State-Changed-When: Mon Nov 14 02:52:38 GMT 2005 State-Changed-Why: Submitter reports problem resolved http://www.freebsd.org/cgi/query-pr.cgi?pr=88884 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 10:50:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32FE616A41F; Mon, 14 Nov 2005 10:50:58 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B97343D4C; Mon, 14 Nov 2005 10:50:57 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 3DDA5208E; Mon, 14 Nov 2005 11:50:52 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 2477B2083; Mon, 14 Nov 2005 11:50:52 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id F112633C3E; Mon, 14 Nov 2005 11:50:51 +0100 (CET) To: John Baldwin References: <20051103112655.A264C7302F@freebsd-current.sentex.ca> <200511031545.05339.jkim@FreeBSD.org> <200511031600.01220.jhb@freebsd.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 14 Nov 2005 11:50:51 +0100 In-Reply-To: <200511031600.01220.jhb@freebsd.org> (John Baldwin's message of "Thu, 3 Nov 2005 15:59:58 -0500") Message-ID: <86zmo7h59w.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Jung-uk Kim , freebsd-current@freebsd.org, FreeBSD Tinderbox , freebsd-amd64@freebsd.org, freebsd-i386@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 10:50:58 -0000 John Baldwin writes: > The tinderbox runs with -O2 just for fun I think. The tinderbox runs with -O2 because -O2 reveals bugs. Sweeping them under the carpet with -fno-strict-aliasing does nobody favors. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 10:58:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D77A16A423 for ; Mon, 14 Nov 2005 10:58:02 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id B342D43D53 for ; Mon, 14 Nov 2005 10:57:59 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR004.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IPX00G0WYGNSXF0@VL-MO-MR004.ip.videotron.ca> for freebsd-amd64@freebsd.org; Mon, 14 Nov 2005 05:57:59 -0500 (EST) Date: Mon, 14 Nov 2005 05:57:52 -0500 From: Nicolas Blais In-reply-to: <20051105174055.34700.qmail@web30201.mail.mud.yahoo.com> To: freebsd-amd64@freebsd.org Message-id: <200511140557.58737.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart2346160.xZXNqgQp9g; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <20051105174055.34700.qmail@web30201.mail.mud.yahoo.com> User-Agent: KMail/1.8.3 Cc: Subject: Re: System powers off after selecting boot option X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 10:58:02 -0000 --nextPart2346160.xZXNqgQp9g Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On November 5, 2005 12:40 pm, Aaron Job Andrus wrote: > I'm trying to install 6.0 64bit on my Compaq Presario > R3000 (AMD Athlon 64 3400+). When I boot to the disk1 > cd I get to the boot menu where I am presented with > the options to boot default, no acpi, safemode, single > user mode etc. However, no matter which boot option I > choose my laptop powers off after a few seconds of > churning (/-\-/). I can "escape to the boot console". > Are there any special variables I need to set in order > to proceed from the boot console? > > Thanks, > > Aaron before it boots into FreeBSD (at the 10 second countdown), press 6 to go to= =20 the boot loader. =20 When there, type: set hint.atkbd.0.flags=3D0x9 Nicolas. =20 =2D-=20 =46reeBSD 7.0-CURRENT #0: Sat Nov 5 12:12:36 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? : http://www.clkroot.net/security/nb_root.asc --nextPart2346160.xZXNqgQp9g Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDeG22z38ton5LGeIRAts4AJ9XZlc7z7rjAcrrBqO2aT1WKBt17wCfWuxD KpYI9fW5USx9N+rp31LRMow= =1fN5 -----END PGP SIGNATURE----- --nextPart2346160.xZXNqgQp9g-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 11:02:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7AAE16A41F for ; Mon, 14 Nov 2005 11:02:20 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E2E43D64 for ; Mon, 14 Nov 2005 11:02:20 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAEB2KX8073630 for ; Mon, 14 Nov 2005 11:02:20 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAEB2J9R073624 for freebsd-amd64@freebsd.org; Mon, 14 Nov 2005 11:02:19 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 14 Nov 2005 11:02:19 GMT Message-Id: <200511141102.jAEB2J9R073624@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 11:02:21 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 fxp0: device timeout, fxp interface dies o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/18] amd64/85081 amd64 TeamSpeak o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 6.0-BETA3 lockups on AMD64 with PREEMPTIO o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/16] amd64/86199 amd64 Missed AMD64 motherboard o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing a [2005/10/14] amd64/87436 amd64 gui does not start on the ATI RS480 M2-IL o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/20] amd64/87748 amd64 can't initialize X o [2005/10/24] amd64/87898 amd64 Failt to init X: can't open device/io o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre 58 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 [bge] bge driver for 3Com 3C996B on amd64 o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 [bge] [patch] FreeBSD 5.4 released versio o [2005/06/12] amd64/82178 amd64 missing 32bit subsystem o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported f [2005/07/20] amd64/83806 amd64 Can not comple /usr/src/lib/msun/amd64/fe o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/02] amd64/85626 amd64 java/jdk15 compile error o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins 20 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 11:14:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0A0616A41F for ; Mon, 14 Nov 2005 11:14:37 +0000 (GMT) (envelope-from savrus@mexmat.net) Received: from gulipin.mexmat.net (gulipin.mexmat.net [217.67.124.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1455743D46 for ; Mon, 14 Nov 2005 11:14:36 +0000 (GMT) (envelope-from savrus@mexmat.net) Received: from mail@gulipin by gulipin.mexmat.net (8.13.4/8.13.4) with ESMTP id jAEBEarT000658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 14:14:36 +0300 (MSK) Received: from localhost (localhost. [127.0.0.1]) by savrus.fds. (8.13.4/8.13.3) with ESMTP id jAEBHxYA049841; Mon, 14 Nov 2005 14:18:03 +0300 (MSK) (envelope-from savrus@mexmat.net) Date: Mon, 14 Nov 2005 14:17:59 +0300 (MSK) Message-Id: <20051114.141759.-1233336878.savrus@mexmat.net> To: rschi@rsmba.biz From: Ruslan Savchenko In-Reply-To: <4377CD61.1040700@rsmba.biz> References: <4377CD61.1040700@rsmba.biz> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1169/Sat Nov 12 00:28:05 2005 on gulipin.mexmat.net X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=5.0 tests=ALL_TRUSTED, BAYES_00, BIZ_TLD autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on gulipin.mexmat.net Cc: freebsd-amd64@freebsd.org Subject: Re: buildworld failing on libalias, amd64, RELENG_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 11:14:37 -0000 Sun, 13 Nov 2005 15:33:53 -0800 Richard Schilling : > Still having problems running make buildworld. It crashes when trying > to build libalias. try rm -rf /usr/obj/* before doing buildworld Ruslan Savchenko From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 19:17:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6418F16A41F for ; Mon, 14 Nov 2005 19:17:50 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B5343D55 for ; Mon, 14 Nov 2005 19:17:49 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 88418B80A for ; Mon, 14 Nov 2005 14:17:48 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20051113111830.4ce6563e.kgunders@teamcool.net> References: <20051113111830.4ce6563e.kgunders@teamcool.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <09618041-B227-4A27-8507-656CDBAD77E7@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 14 Nov 2005 14:17:47 -0500 To: freebsd-amd64 List X-Mailer: Apple Mail (2.746.2) Subject: Re: FreeBSD 5.4 or 6.0 as postgresql-server X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 19:17:50 -0000 On Nov 13, 2005, at 1:18 PM, Ken Gunderson wrote: > I'd be interested in your experiences w/6.0. Would you mind testing > the onboard bge nics at the kind of loads that was causing them to > puke under 5.4? I've got same system and as of yet not encountered > issues w/ the onboard bge nics. The machine is also at the latest > BIOS, however, so that may contribute as well. normally I would but right now I need to get this server up and running ASAP. and switching cables at the data center is a 2+ hour operation given the horrid traffic on the DC beltway. i can't generate that kind of load easily at the office :-) From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 22:00:25 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6351216A41F; Mon, 14 Nov 2005 22:00:25 +0000 (GMT) (envelope-from magus@dlrow.dyndns.org) Received: from dlrow.dyndns.org (h219-110-239-144.catv02.itscom.jp [219.110.239.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1452043D45; Mon, 14 Nov 2005 22:00:25 +0000 (GMT) (envelope-from magus@dlrow.dyndns.org) Received: by dlrow.dyndns.org (Postfix, from userid 999) id 3C84F1FFC3B; Tue, 15 Nov 2005 07:00:24 +0900 (JST) Date: Tue, 15 Nov 2005 07:00:24 +0900 From: KOBAYASHI Hidenobu To: Mark Linimon Message-ID: <20051114220024.GA2485%kobayasi@pp.iij4u.or.jp> References: <200511121717.jACHHSUo089197@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511121717.jACHHSUo089197@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/83806: Can not comple /usr/src/lib/msun/amd64/fenv.c at make buildworld. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 22:00:25 -0000 > Is this still a problem with the latest 6-STABLE tree? Yes. I tried to make buildworld and installworld without NO_LIB32=yes. "/usr/include/fenv.h" was still overwritten with "/usr/src/lib/msun/i387/fenv.h". Best Regards, -- KOBAYASHI Hidenobu kobayasi@pp.iij4u.or.jp From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 14 23:10:02 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC8F16A420; Mon, 14 Nov 2005 23:10:02 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CA9243D6A; Mon, 14 Nov 2005 23:10:02 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAENA2K7097215; Mon, 14 Nov 2005 23:10:02 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAENA1j2097211; Mon, 14 Nov 2005 23:10:01 GMT (envelope-from linimon) Date: Mon, 14 Nov 2005 23:10:01 GMT From: Mark Linimon Message-Id: <200511142310.jAENA1j2097211@freefall.freebsd.org> To: kobayasi@pp.iij4u.or.jp, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/83806: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 23:10:02 -0000 Old Synopsis: Can not comple /usr/src/lib/msun/amd64/fenv.c at make buildworld. New Synopsis: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. State-Changed-From-To: feedback->open State-Changed-By: linimon State-Changed-When: Mon Nov 14 23:09:33 GMT 2005 State-Changed-Why: Feedback received. http://www.freebsd.org/cgi/query-pr.cgi?pr=83806 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 18:08:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E794216A41F for ; Tue, 15 Nov 2005 18:08:34 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (66-23-216-219.clients.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6016A43D45 for ; Tue, 15 Nov 2005 18:08:34 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2011085 for multiple; Tue, 15 Nov 2005 13:08:38 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAFI8L2f087883; Tue, 15 Nov 2005 13:08:21 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Tue, 15 Nov 2005 13:08:24 -0500 User-Agent: KMail/1.8.2 References: <1131641262.99700.3.camel@triton.mcneil.com> <200511101420.04967.jhb@freebsd.org> In-Reply-To: <200511101420.04967.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_ZQieDd8YNe9kuRO" Message-Id: <200511151308.25729.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Roman Neuhauser Subject: Re: problems booting recompiled 5.4-kernel (Was: amd64 does not see all 4 GB RAM on tyan GT24) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 18:08:35 -0000 --Boundary-00=_ZQieDd8YNe9kuRO Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thursday 10 November 2005 02:20 pm, John Baldwin wrote: > On Thursday 10 November 2005 11:47 am, Sean McNeil wrote: > > On Thu, 2005-11-10 at 11:11 -0500, John Baldwin wrote: > > > On Wednesday 09 November 2005 04:12 pm, Sean McNeil wrote: > > > > On Wed, 2005-11-09 at 16:04 -0500, John Baldwin wrote: > > > > > On Wednesday 09 November 2005 02:47 pm, Roman Neuhauser wrote: > > > > > > # jhb@freebsd.org / 2005-11-09 10:22:07 -0500: > > > > > > > On Wednesday 09 November 2005 04:22 am, Claus Guttesen wrote: > > > > > > > > I tried FreeBSD 6.0 a few days ago and I seem to recall that > > > > > > > > the above mentioned line is not needed in FreeBSD 6.0, but my > > > > > > > > (own) memory is probably corrupt :-) > > > > > > > > > > > > > > That's correct. > > > > > > > > > > > > EAMBIGUOUS. > > > > > > > > > > > > Which part is correct? "mentioned line is not needed in > > > > > > FreeBSD 6.0" or "my (own) memory is probably corrupt"? > > > > > > > > > > You don't need atpic on 6.0. > > > > > > > > Not true. My Athlon 2x Gigabyte K8 Triton (GA-K8NSC-939) requires > > > > atpic or it will not boot. This is an nVidia nForce3-Pro250 board. > > > > > > You need to post a problem report about it then since we are probably > > > going to remove atpic in 7.0. When atpic was taken out of GENERIC in > > > HEAD recently no one said it broke for them. What problems do you see > > > with atpic taken out on 6.0? > > > > Again, not true. When it was asked in email subject > > > > Re: [PATCH] remove 'device atpic' > > > > I responded at that time with: > > > > On Thu, 2005-10-20 at 10:40 -0400, John Baldwin wrote: > > > On Wednesday 19 October 2005 05:28 pm, Sean McNeil wrote: > > > > Just recently fried my MSI MB and got a new one with an Athlon 64x2. > > > > The following setup still requires the 'device atpic' or it will > > > > fault > > > > > > with an unknown/reserved trap of 30: > > > > > > > > GigaByte K8 Triton Series GA-K8NSC-939 BIOS rev. F5 > > > > AMD Athlon 64 X2 Dual-Core Processor 3800+ > > > > > > > > It works perfectly fine as a single core without the atpic device > > > > and as > > > > > > a dual-cpu with the atpic device. This board has the nForce3 250Gb > > > > chipset. > > > > > > What version(s) of FreeBSD does it fail on? > > > > This was/is 6-current RC1. > > Ok, can you get a stack trace? The only time I've seen these recently was > when the 8259A wasn't truly shut down correctly during boot and it fired an > interrupt before it was shut up. Hmm, I thought Peter had added some hack > code to just shut the 8259As up during boot, but now I can't find it. Ah, > it's earlier in that function. It might be that his hack is incomplete as > it assumes the 8259As are in a certain state, and if they aren't then his > hack won't work. I'll try to flesh it out some more. Here's a patch you can test. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org --Boundary-00=_ZQieDd8YNe9kuRO Content-Type: text/x-diff; charset="iso-8859-6"; name="amd64_atpic.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="amd64_atpic.patch" --- //depot/vendor/freebsd/src/sys/amd64/amd64/machdep.c 2005/10/26 22:21:00 +++ //depot/user/jhb/acpipci/amd64/amd64/machdep.c 2005/11/15 16:41:07 @@ -124,6 +124,7 @@ #include #endif +#include #include #include @@ -1126,9 +1127,22 @@ char *env; #ifdef DEV_ISA - /* Preemptively mask the atpics and leave them shut down */ +#if !defined(DEV_ATPIC) + /* Preemptively reset and mask the atpics and leave them shut down */ + outb(IO_ICU1, ICW1_RESET | ICW1_IC4); + outb(IO_ICU1 + ICU_IMR_OFFSET, IDT_IO_INTS); + outb(IO_ICU1 + ICU_IMR_OFFSET, 1 << 2); + outb(IO_ICU1 + ICU_IMR_OFFSET, ICW4_8086); outb(IO_ICU1 + ICU_IMR_OFFSET, 0xff); + outb(IO_ICU1, OCW3_SEL | OCW3_RR); + + outb(IO_ICU2, ICW1_RESET | ICW1_IC4); + outb(IO_ICU2 + ICU_IMR_OFFSET, IDT_IO_INTS + 8); + outb(IO_ICU2 + ICU_IMR_OFFSET, 2); + outb(IO_ICU2 + ICU_IMR_OFFSET, ICW4_8086); outb(IO_ICU2 + ICU_IMR_OFFSET, 0xff); + outb(IO_ICU2, OCW3_SEL | OCW3_RR); +#endif #else #error "have you forgotten the isa device?"; #endif --Boundary-00=_ZQieDd8YNe9kuRO-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 19:13:15 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8EA016A420; Tue, 15 Nov 2005 19:13:15 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1A543D45; Tue, 15 Nov 2005 19:13:14 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 72E6CF24E0; Tue, 15 Nov 2005 11:13:14 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00821-01; Tue, 15 Nov 2005 11:13:12 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id AB6CAF24B4; Tue, 15 Nov 2005 11:13:12 -0800 (PST) From: Sean McNeil To: John Baldwin In-Reply-To: <200511151308.25729.jhb@freebsd.org> References: <1131641262.99700.3.camel@triton.mcneil.com> <200511101420.04967.jhb@freebsd.org> <200511151308.25729.jhb@freebsd.org> Content-Type: text/plain Date: Tue, 15 Nov 2005 11:13:12 -0800 Message-Id: <1132081992.1334.7.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Cc: Roman Neuhauser , freebsd-amd64@freebsd.org Subject: Re: problems booting recompiled 5.4-kernel (Was: amd64 does not see all 4 GB RAM on tyan GT24) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 19:13:15 -0000 On Tue, 2005-11-15 at 13:08 -0500, John Baldwin wrote: > On Thursday 10 November 2005 02:20 pm, John Baldwin wrote: > > On Thursday 10 November 2005 11:47 am, Sean McNeil wrote: > > > On Thu, 2005-11-10 at 11:11 -0500, John Baldwin wrote: > > > > On Wednesday 09 November 2005 04:12 pm, Sean McNeil wrote: > > > > > On Wed, 2005-11-09 at 16:04 -0500, John Baldwin wrote: > > > > > > On Wednesday 09 November 2005 02:47 pm, Roman Neuhauser wrote: > > > > > > > # jhb@freebsd.org / 2005-11-09 10:22:07 -0500: > > > > > > > > On Wednesday 09 November 2005 04:22 am, Claus Guttesen wrote: > > > > > > > > > I tried FreeBSD 6.0 a few days ago and I seem to recall that > > > > > > > > > the above mentioned line is not needed in FreeBSD 6.0, but my > > > > > > > > > (own) memory is probably corrupt :-) > > > > > > > > > > > > > > > > That's correct. > > > > > > > > > > > > > > EAMBIGUOUS. > > > > > > > > > > > > > > Which part is correct? "mentioned line is not needed in > > > > > > > FreeBSD 6.0" or "my (own) memory is probably corrupt"? > > > > > > > > > > > > You don't need atpic on 6.0. > > > > > > > > > > Not true. My Athlon 2x Gigabyte K8 Triton (GA-K8NSC-939) requires > > > > > atpic or it will not boot. This is an nVidia nForce3-Pro250 board. > > > > > > > > You need to post a problem report about it then since we are probably > > > > going to remove atpic in 7.0. When atpic was taken out of GENERIC in > > > > HEAD recently no one said it broke for them. What problems do you see > > > > with atpic taken out on 6.0? > > > > > > Again, not true. When it was asked in email subject > > > > > > Re: [PATCH] remove 'device atpic' > > > > > > I responded at that time with: > > > > > > On Thu, 2005-10-20 at 10:40 -0400, John Baldwin wrote: > > > > On Wednesday 19 October 2005 05:28 pm, Sean McNeil wrote: > > > > > Just recently fried my MSI MB and got a new one with an Athlon 64x2. > > > > > The following setup still requires the 'device atpic' or it will > > > > > > fault > > > > > > > > with an unknown/reserved trap of 30: > > > > > > > > > > GigaByte K8 Triton Series GA-K8NSC-939 BIOS rev. F5 > > > > > AMD Athlon 64 X2 Dual-Core Processor 3800+ > > > > > > > > > > It works perfectly fine as a single core without the atpic device > > > > > > and as > > > > > > > > a dual-cpu with the atpic device. This board has the nForce3 250Gb > > > > > chipset. > > > > > > > > What version(s) of FreeBSD does it fail on? > > > > > > This was/is 6-current RC1. > > > > Ok, can you get a stack trace? The only time I've seen these recently was > > when the 8259A wasn't truly shut down correctly during boot and it fired an > > interrupt before it was shut up. Hmm, I thought Peter had added some hack > > code to just shut the 8259As up during boot, but now I can't find it. Ah, > > it's earlier in that function. It might be that his hack is incomplete as > > it assumes the 8259As are in a certain state, and if they aren't then his > > hack won't work. I'll try to flesh it out some more. > > Here's a patch you can test. Tried the patch and it looks like things fail earlier. I haven't been able to make the time yet to build a kernel with debug and get you a backtrace. I will try to do so as soon as possible. For me, I think it has to do with the second CPU settings as it works when SMP is not enabled. This is what I see when things work: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: on acpi0 pci_link1: irq 5 on acpi0 pci_link2: on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 7 on acpi0 pci_link5: irq 11 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: on acpi0 pci_link8: on acpi0 pci_link9: irq 9 on acpi0 pci_link10: on acpi0 pci_link11: irq 10 on acpi0 pci_link12: irq 11 on acpi0 pci_link13: on acpi0 pci_link14: on acpi0 pci_link15: on acpi0 pci_link16: on acpi0 pci_link17: irq 11 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 0 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 16 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 23 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 0 on acpi0 pci_link32: irq 0 on acpi0 pci_link33: irq 0 on acpi0 pci_link34: irq 0 on acpi0 pci_link35: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci_link29: BIOS IRQ 10 for -2145892088.1.INTA is invalid pci_link23: BIOS IRQ 11 for -2145892088.2.INTA is invalid pci_link24: BIOS IRQ 11 for -2145892088.2.INTB is invalid pci_link30: BIOS IRQ 11 for -2145892088.2.INTC is invalid pci_link27: BIOS IRQ 9 for -2145892088.6.INTA is invalid pci_link35: BIOS IRQ 11 for -2145892088.10.INTA is invalid pci0: on pcib0 Sean From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 21:50:44 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3320416A41F for ; Tue, 15 Nov 2005 21:50:44 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCA9243D45 for ; Tue, 15 Nov 2005 21:50:43 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1496460nzo for ; Tue, 15 Nov 2005 13:50:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=I2yiJQvJrb2pgrJ8FeSrakkVCBmL0w5omedrfB+i7sRAUaVFU3uW2cIk8mFCj1ucrYGQNEvziqTK7lpiXI4cTHoCm8F0F8icGl1I0DvB+o5NsmKD5BbrcPSmhJyz6syDSnNrIkB/OrXFe3gTHxc6mjG2xbNgXfBq3+4630fJGmc= Received: by 10.36.13.10 with SMTP id 10mr5614206nzm; Tue, 15 Nov 2005 13:50:42 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 13:50:42 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 00:50:42 +0300 From: "Andrew P." To: amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 21:50:44 -0000 I'm gravely sorry to annoy. I've googled for a little while and found out that IPSec panics are a known issue on amd64. Is it still so? I was surprised that setkey -D causes panic and a memory dump on my 6-Stable box. Come on, it's _FreeBSD_ for crying out loud. We can't live with that. I'm willing to help debugging this nasty thing if help's needed. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 21:55:20 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D02AE16A41F for ; Tue, 15 Nov 2005 21:55:20 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D63E43D68 for ; Tue, 15 Nov 2005 21:55:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0DEF91A3C25; Tue, 15 Nov 2005 13:55:18 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 551E951516; Tue, 15 Nov 2005 16:55:17 -0500 (EST) Date: Tue, 15 Nov 2005 16:55:17 -0500 From: Kris Kennaway To: "Andrew P." Message-ID: <20051115215517.GA47583@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 21:55:20 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 16, 2005 at 12:50:42AM +0300, Andrew P. wrote: > I'm gravely sorry to annoy. I've googled for a little > while and found out that IPSec panics are a known > issue on amd64. Is it still so? >=20 > I was surprised that setkey -D causes panic and > a memory dump on my 6-Stable box. Come on, > it's _FreeBSD_ for crying out loud. We can't live > with that. >=20 > I'm willing to help debugging this nasty thing if > help's needed. Start by determining whether an adequately documented PR (with backtrace, etc) is filed on this issue, and if not, then file one. Kris --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDellEWry0BWjoQKURAhjCAKCLKxVjdXPdqBqKqwrjwZLdI43+1wCgmey7 +Axw6zSLbpF5BTQtyheFBF4= =Jy0V -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:09:43 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D458C16A41F for ; Tue, 15 Nov 2005 22:09:43 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A4443D72 for ; Tue, 15 Nov 2005 22:09:34 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1500256nzo for ; Tue, 15 Nov 2005 14:09:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CxuXAmT/ve+ZhUJzg4+MyI0OnJ3CBc1BbgHQg8gqZAGn+e4fPCBM0cuovaflJeugqrnLok4YZraX5zGZq+Vjpv86D/WDrZBL6XRfg3hLihLTRTDNQAbDRaaYVDqsUQlukvFS5ozXNCOzKspbDe8ymMLFQkTDpq1+Hdroj0bAjBI= Received: by 10.36.216.6 with SMTP id o6mr2699782nzg; Tue, 15 Nov 2005 14:09:33 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 14:09:33 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 01:09:33 +0300 From: "Andrew P." To: Kris Kennaway In-Reply-To: <20051115215517.GA47583@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051115215517.GA47583@xor.obsecurity.org> Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:09:44 -0000 On 11/16/05, Kris Kennaway wrote: > On Wed, Nov 16, 2005 at 12:50:42AM +0300, Andrew P. wrote: > > I'm gravely sorry to annoy. I've googled for a little > > while and found out that IPSec panics are a known > > issue on amd64. Is it still so? > > > > I was surprised that setkey -D causes panic and > > a memory dump on my 6-Stable box. Come on, > > it's _FreeBSD_ for crying out loud. We can't live > > with that. > > > > I'm willing to help debugging this nasty thing if > > help's needed. > > Start by determining whether an adequately documented PR (with > backtrace, etc) is filed on this issue, and if not, then file one. It's a relief that you don't know about it. I have to hope that I've done something wrong. I'm compiling latest stable world/kernel now, then I might want to try 6.0-release. Well, there are some PR's: http://www.freebsd.org/cgi/query-pr-summary.cgi?text=3Dipsec Some are close to what I see, none are exactly similar, but they are all very outdated. Actually, I've never sent a proper bug-related PR, so I'll need some hand-holding support from a kind soul. I can cvsup to anything, recompile to anything and I might be able to get a serial console. root access is not impossible to provide. Still, give me some time so I can rule out some very simple mistakes. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:20:13 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB32F16A41F for ; Tue, 15 Nov 2005 22:20:13 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F9CB43D60 for ; Tue, 15 Nov 2005 22:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9275F1FFAD5; Tue, 15 Nov 2005 23:20:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 224401FFAD2; Tue, 15 Nov 2005 23:20:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 2AEA215823; Tue, 15 Nov 2005 22:18:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 20791155EB; Tue, 15 Nov 2005 22:18:11 +0000 (UTC) Date: Tue, 15 Nov 2005 22:18:11 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Andrew P." In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:20:14 -0000 On Wed, 16 Nov 2005, Andrew P. wrote: > I'm gravely sorry to annoy. I've googled for a little > while and found out that IPSec panics are a known > issue on amd64. Is it still so? > > I was surprised that setkey -D causes panic and > a memory dump on my 6-Stable box. Come on, > it's _FreeBSD_ for crying out loud. We can't live > with that. > > I'm willing to help debugging this nasty thing if > help's needed. is it fast_ispec? best place to contriubte might be: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211 I just gave it a try w/o any policy loaded and the bt looks like this: y2k# setkey -D [thread pid 471 tid 100057 ] Stopped at kdebug_sockaddr+0xb0: decl 0xffffffffffffff8d(%rax) db> where Tracing pid 471 tid 100057 td 0xffffff010bfc7750 kdebug_sockaddr() at kdebug_sockaddr+0xb0 raw_usend() at raw_usend+0x74 key_send() at key_send+0xa sosend() at sosend+0x726 kern_sendit() at kern_sendit+0x12f sendit() at sendit+0x1d3 sendto() at sendto+0x52 syscall() at syscall+0x350 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x8007e9a6c, rsp = 0x7fffffff6b98, rbp = 0x2 --- db> show alllocks db> -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:20:44 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 231FF16A420 for ; Tue, 15 Nov 2005 22:20:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 827B143D5D for ; Tue, 15 Nov 2005 22:20:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 552B11A3C25; Tue, 15 Nov 2005 14:20:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 78C7D533D0; Tue, 15 Nov 2005 17:20:39 -0500 (EST) Date: Tue, 15 Nov 2005 17:20:39 -0500 From: Kris Kennaway To: "Andrew P." Message-ID: <20051115222039.GA63863@xor.obsecurity.org> References: <20051115215517.GA47583@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Kris Kennaway Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:20:44 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 16, 2005 at 01:09:33AM +0300, Andrew P. wrote: > On 11/16/05, Kris Kennaway wrote: > > On Wed, Nov 16, 2005 at 12:50:42AM +0300, Andrew P. wrote: > > > I'm gravely sorry to annoy. I've googled for a little > > > while and found out that IPSec panics are a known > > > issue on amd64. Is it still so? > > > > > > I was surprised that setkey -D causes panic and > > > a memory dump on my 6-Stable box. Come on, > > > it's _FreeBSD_ for crying out loud. We can't live > > > with that. > > > > > > I'm willing to help debugging this nasty thing if > > > help's needed. > > > > Start by determining whether an adequately documented PR (with > > backtrace, etc) is filed on this issue, and if not, then file one. >=20 >=20 > It's a relief that you don't know about it. I wouldn't read too much into it :) > Actually, I've never sent a proper bug-related PR, > so I'll need some hand-holding support from a > kind soul. I can cvsup to anything, recompile to > anything and I might be able to get a serial console. > root access is not impossible to provide. The main thing is to follow the directions in the developers handbook chapter on kernel debugging, which explains how to obtain the necessary debugging backtrace. Kris --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDel82Wry0BWjoQKURArgDAKD5OEzA32xzNBexgRjfa3ufplmv7ACgklEn Pac2XKMSF7mkyCUxN3KcL+c= =pP7i -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:24:49 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB2DA16A41F; Tue, 15 Nov 2005 22:24:49 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B57FD43D46; Tue, 15 Nov 2005 22:24:49 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (bz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAFMOn27018872; Tue, 15 Nov 2005 22:24:49 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAFMOnRB018868; Tue, 15 Nov 2005 22:24:49 GMT (envelope-from bz) Date: Tue, 15 Nov 2005 22:24:49 GMT From: "Bjoern A. Zeeb" Message-Id: <200511152224.jAFMOnRB018868@freefall.freebsd.org> To: bz@FreeBSD.org, freebsd-amd64@FreeBSD.org, bz@FreeBSD.org Cc: Subject: Re: amd64/73211: FAST_IPSEC broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:24:50 -0000 Synopsis: FAST_IPSEC broken on amd64 Responsible-Changed-From-To: freebsd-amd64->bz Responsible-Changed-By: bz Responsible-Changed-When: Tue Nov 15 22:22:19 GMT 2005 Responsible-Changed-Why: gnn and me will work on fast_ipsec so take this PR. I have an amd64 machine here and could reproduce a panic even w/o a policy loaded. y2k# setkey -D [thread pid 471 tid 100057 ] Stopped at kdebug_sockaddr+0xb0: decl 0xffffffffffffff8d(%rax) db> where Tracing pid 471 tid 100057 td 0xffffff010bfc7750 kdebug_sockaddr() at kdebug_sockaddr+0xb0 raw_usend() at raw_usend+0x74 key_send() at key_send+0xa sosend() at sosend+0x726 kern_sendit() at kern_sendit+0x12f sendit() at sendit+0x1d3 sendto() at sendto+0x52 syscall() at syscall+0x350 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x8007e9a6c, rsp = 0x7fffffff6b98, rbp = 0x2 --- db> show alllocks db> http://www.freebsd.org/cgi/query-pr.cgi?pr=73211 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:25:04 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA22816A41F for ; Tue, 15 Nov 2005 22:25:04 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 524CA43D45 for ; Tue, 15 Nov 2005 22:25:04 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1503030nzo for ; Tue, 15 Nov 2005 14:25:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CWXXov5dAfdMaI0Pr1lLtjhzVzM35MNEhYqRfatJ0WMYLDRTqQg4DcACR3MvbDaEAlKJfBjd0cY8OrjRsZyMbNZhjygqDBABmv4petULftDQsZLk1K3H7b2sjzNN1mBTMkZ/T6BJ+ruBBViyPeMzY6oIblaZIc3qu9nUOea8L1U= Received: by 10.36.13.10 with SMTP id 10mr5641339nzm; Tue, 15 Nov 2005 14:25:03 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 14:25:03 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 01:25:03 +0300 From: "Andrew P." To: "Bjoern A. Zeeb" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:25:04 -0000 On 11/16/05, Bjoern A. Zeeb wrote: > On Wed, 16 Nov 2005, Andrew P. wrote: > > > I'm gravely sorry to annoy. I've googled for a little > > while and found out that IPSec panics are a known > > issue on amd64. Is it still so? > > > > I was surprised that setkey -D causes panic and > > a memory dump on my 6-Stable box. Come on, > > it's _FreeBSD_ for crying out loud. We can't live > > with that. > > > > I'm willing to help debugging this nasty thing if > > help's needed. > > is it fast_ispec? > > best place to contriubte might be: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Damd64/73211 > > I just gave it a try w/o any policy loaded and the bt looks like this: > > y2k# setkey -D > [thread pid 471 tid 100057 ] > Stopped at kdebug_sockaddr+0xb0: decl 0xffffffffffffff8d(%rax) > db> where > Tracing pid 471 tid 100057 td 0xffffff010bfc7750 > kdebug_sockaddr() at kdebug_sockaddr+0xb0 > raw_usend() at raw_usend+0x74 > key_send() at key_send+0xa > sosend() at sosend+0x726 > kern_sendit() at kern_sendit+0x12f > sendit() at sendit+0x1d3 > sendto() at sendto+0x52 > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (133, FreeBSD ELF64, sendto), rip =3D 0x8007e9a6c, rsp =3D 0x= 7fffffff6b98, rbp =3D 0x2 --- > db> show alllocks > db> No, it's just options IPSEC (without IPSEC_ESP). Can you please remove all IPSEC options except for IPSEC itself and try setkey -D? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:26:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B4B416A420 for ; Tue, 15 Nov 2005 22:26:48 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5DC343D49 for ; Tue, 15 Nov 2005 22:26:47 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1503349nzo for ; Tue, 15 Nov 2005 14:26:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aXVYfWmpz5FjQTXp+k+4dpicdEOosWg/a8PXVyAs7YI8/DU8pSb0z9Qd0+DQpQSW6ry7tiOj8tMYIwmxprFXtdvXRIz8FHLQ4SengK6xbCfsNBt9fLNX2bL5ToEiMYC15PAs3eK+3e9JlxB2nNgExZ3OyGiabEpdq80+nztm+8Y= Received: by 10.37.2.48 with SMTP id e48mr5644694nzi; Tue, 15 Nov 2005 14:26:47 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 14:26:47 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 01:26:47 +0300 From: "Andrew P." To: Kris Kennaway In-Reply-To: <20051115222039.GA63863@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051115215517.GA47583@xor.obsecurity.org> <20051115222039.GA63863@xor.obsecurity.org> Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:26:48 -0000 On 11/16/05, Kris Kennaway wrote: > On Wed, Nov 16, 2005 at 01:09:33AM +0300, Andrew P. wrote: > > On 11/16/05, Kris Kennaway wrote: > > > On Wed, Nov 16, 2005 at 12:50:42AM +0300, Andrew P. wrote: > > > > I'm gravely sorry to annoy. I've googled for a little > > > > while and found out that IPSec panics are a known > > > > issue on amd64. Is it still so? > > > > > > > > I was surprised that setkey -D causes panic and > > > > a memory dump on my 6-Stable box. Come on, > > > > it's _FreeBSD_ for crying out loud. We can't live > > > > with that. > > > > > > > > I'm willing to help debugging this nasty thing if > > > > help's needed. > > > > > > Start by determining whether an adequately documented PR (with > > > backtrace, etc) is filed on this issue, and if not, then file one. > > > > > > It's a relief that you don't know about it. > > I wouldn't read too much into it :) > > > Actually, I've never sent a proper bug-related PR, > > so I'll need some hand-holding support from a > > kind soul. I can cvsup to anything, recompile to > > anything and I might be able to get a serial console. > > root access is not impossible to provide. > > The main thing is to follow the directions in the developers handbook > chapter on kernel debugging, which explains how to obtain the > necessary debugging backtrace. Great, it's high time I read it. Will do if the problem stays. Thanks, Andrew P. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 00:58:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D584B16A41F for ; Wed, 16 Nov 2005 00:58:29 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 416E943D73 for ; Wed, 16 Nov 2005 00:58:28 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.10]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id jAG0wPOn051008 for ; Tue, 15 Nov 2005 16:58:26 -0800 (PST) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <000c01c5ea48$d7366ba0$0a00a8c0@rodan> From: "Jeff D. Hamann" To: Date: Tue, 15 Nov 2005 16:58:16 -0800 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Subject: safe and sane way to 6? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 00:58:30 -0000 I've installed FreeBSD 6BETA4 a few months ago and have been waiting until the first release (non-beta) came out to get the machine moving. I went to upgrade my system by performing a cvsup after setting the cvsupfile to the following: *default host=cvsup18.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6_0 *default delete use-rel-suffix *default compress src-all ports-all doc-all www cvsroot-all I then tried to run a make buildworld and got the following error message: mkmagic: could not find any magic files! *** Error code 1 Stop in /usr/src/lib/libmagic. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. bobby# bobby# Now what? Would it be smarter to simply install a clean version of FreeBSD 6.0? or can I upgrade without having to go through all that again? Jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 02:28:16 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4569116A41F for ; Wed, 16 Nov 2005 02:28:16 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958E143D4C for ; Wed, 16 Nov 2005 02:28:15 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 941A74CC86; Wed, 16 Nov 2005 02:28:27 +0000 (GMT) Received: from [192.168.46.52] (ppp166-27.static.internode.on.net [150.101.166.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id BB3364CC6C; Wed, 16 Nov 2005 02:28:26 +0000 (GMT) Message-ID: <437A993B.8080204@roq.com> Date: Wed, 16 Nov 2005 13:28:11 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051110 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Andrew P." References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 02:28:16 -0000 Andrew P. wrote: >I'm gravely sorry to annoy. I've googled for a little >while and found out that IPSec panics are a known >issue on amd64. Is it still so? > >I was surprised that setkey -D causes panic and >a memory dump on my 6-Stable box. Come on, >it's _FreeBSD_ for crying out loud. We can't live >with that. > >I'm willing to help debugging this nasty thing if >help's needed. >_______________________________________________ > > FAST_IPSEC broken on amd64 is still broken. As far as I know VANHULLEBUS Yvan appears to be the most active IPSEC guy in FreeBSD and he has talked about fixing it but probably hasn't got the time, probably only money is a viable motivator if you wanted this problem fixed soon. Mike From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 03:44:38 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB91B16A41F for ; Wed, 16 Nov 2005 03:44:38 +0000 (GMT) (envelope-from jimmyblim@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A09D43D49 for ; Wed, 16 Nov 2005 03:44:38 +0000 (GMT) (envelope-from jimmyblim@gmail.com) Received: by zproxy.gmail.com with SMTP id m22so1581206nzf for ; Tue, 15 Nov 2005 19:44:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Fodvd9MyYK339XMfXCKHlaF0wh+DhkdPPebSCP7XUUYdCle8iRAOM7HqnAzqePEwJZo7JAFw2kGZ+o1cjJpNTTRYYoybDCDsRLSbtcqjB++cpZT9S+CYbJhneX5cEK3zd1UkbR6m2GL9FIiGhjqeai60HEH7CcgEBtufOcMHbv4= Received: by 10.65.158.6 with SMTP id k6mr5347145qbo; Tue, 15 Nov 2005 19:44:37 -0800 (PST) Received: by 10.65.52.3 with HTTP; Tue, 15 Nov 2005 19:44:37 -0800 (PST) Message-ID: <127fb190511151944l39e47eah96b89fb3ac5e8d96@mail.gmail.com> Date: Wed, 16 Nov 2005 11:44:37 +0800 From: Jimmy Lim To: amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: firebirdsql-server on FreeBSD-6.0R/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 03:44:38 -0000 Hi, I've installed firebirdsql-server(32-bit) on my DL145 opteron, I've ldconfi= g -32 the libs and I can use the firebird-clients, but when I tried to enable the server, and try to connect to it, it gives me these errors: Statement failed, SQLCODE =3D -902 operating system directive semctl failed -Bad address I tried to remove the active semaphors on it and I learned that fb_lock_mgr is not running. Any work around to use firebirdsql on FreeBSD-6.0/amd64? TIA -- Jimmy B. Lim j i m m y b l i m @ g m a i l . c o m From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 07:43:23 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C6D316A41F for ; Wed, 16 Nov 2005 07:43:23 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FDD043D45 for ; Wed, 16 Nov 2005 07:43:23 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [83.242.63.242] (242-63-242-83.dip.h-tel.de [83.242.63.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id C352830004B7; Wed, 16 Nov 2005 08:43:20 +0100 (CET) Message-ID: <437AE312.4090709@mail.uni-mainz.de> Date: Wed, 16 Nov 2005 08:43:14 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <437A993B.8080204@roq.com> In-Reply-To: <437A993B.8080204@roq.com> Content-Type: multipart/mixed; boundary="------------040801010705030006020706" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 07:43:23 -0000 This is a multi-part message in MIME format. --------------040801010705030006020706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Michael Vince wrote: > Andrew P. wrote: > >> I'm gravely sorry to annoy. I've googled for a little >> while and found out that IPSec panics are a known >> issue on amd64. Is it still so? >> >> I was surprised that setkey -D causes panic and >> a memory dump on my 6-Stable box. Come on, >> it's _FreeBSD_ for crying out loud. We can't live >> with that. >> >> I'm willing to help debugging this nasty thing if >> help's needed. >> _______________________________________________ >> >> > FAST_IPSEC broken on amd64 is still broken. As far as I know > VANHULLEBUS Yvan appears to be the most active IPSEC guy in FreeBSD > and he has talked about fixing it but probably hasn't got the time, > probably only money is a viable motivator if you wanted this problem > fixed soon. > > Mike Indeed, but IPSEC seems also to be broken. With IPSEC or FAST_IPSEC it is possible to force a crash as described further below in this thread. O. --------------040801010705030006020706-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 10:18:35 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47EDF16A420; Wed, 16 Nov 2005 10:18:35 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B220543D49; Wed, 16 Nov 2005 10:18:34 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jAGAIXgJ081275; Wed, 16 Nov 2005 05:18:33 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAGAIX2i050616; Wed, 16 Nov 2005 05:18:33 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 575B37302F; Wed, 16 Nov 2005 05:18:32 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051116101832.575B37302F@freebsd-current.sentex.ca> Date: Wed, 16 Nov 2005 05:18:32 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 10:18:35 -0000 TB --- 2005-11-16 09:08:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-16 09:08:52 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-16 09:08:52 - cleaning the object tree TB --- 2005-11-16 09:09:30 - checking out the source tree TB --- 2005-11-16 09:09:30 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-16 09:09:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-16 09:16:05 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-16 09:16:05 - cd /src TB --- 2005-11-16 09:16:05 - /usr/bin/make -B buildworld >>> 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 >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] mount_portalfs.o(.text+0x14a): In function `main': : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() gzip -cn /src/usr.sbin/mount_portalfs/mount_portalfs.8 > mount_portalfs.8.gz ===> usr.sbin/mount_smbfs (all) cc -O2 -pipe -DSMBFS -I/src/usr.sbin/mount_smbfs/../../sbin/mount -I/src/usr.sbin/mount_smbfs/../../contrib/smbfs/include -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /src/usr.sbin/mount_smbfs/../../contrib/smbfs/mount_smbfs/mount_smbfs.c /src/usr.sbin/mount_smbfs/../../contrib/smbfs/mount_smbfs/mount_smbfs.c: In function `main': /src/usr.sbin/mount_smbfs/../../contrib/smbfs/mount_smbfs/mount_smbfs.c:234: warning: comparison is always false due to limited range of data type /src/usr.sbin/mount_smbfs/../../contrib/smbfs/mount_smbfs/mount_smbfs.c:236: warning: comparison is always false due to limited range of data type *** Error code 1 Stop in /src/usr.sbin/mount_smbfs. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-16 10:18:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-16 10:18:32 - ERROR: failed to build world TB --- 2005-11-16 10:18:32 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 15:13:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 193B916A41F for ; Wed, 16 Nov 2005 15:13:58 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83C8743D45 for ; Wed, 16 Nov 2005 15:13:57 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id D05A9564C2 for ; Wed, 16 Nov 2005 16:13:55 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 55392-02-2 for ; Wed, 16 Nov 2005 16:13:54 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 8BEDE564C1 for ; Wed, 16 Nov 2005 16:13:54 +0100 (CET) Received: from 145.248.192.30 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Wed, 16 Nov 2005 16:13:54 +0100 (CET) Message-ID: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> Date: Wed, 16 Nov 2005 16:13:54 +0100 (CET) From: "Julien Gabel" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Subject: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 15:13:58 -0000 Hello, I am currently looking for feedback on using a Sun Ultra 20 Workstation. I didn't found anything on freebsd-amd64@, nor in the list of supported motherboards (http://www.freebsd.org/platforms/amd64/motherboards.html). Only the Sun Fire V20z seems ok. * Sun Ultra 20 Workstation -- Hardware Specifications: http://sunsolve.sun.com/handbook_private/Systems/Ultra20/spec.html * Sun Ultra 20 Workstation -- Full Components List: http://sunsolve.sun.com/handbook_private/Systems/Ultra20/components.html Any chance to get it working using FreeBSD? Many thanks in advance for reply(ies) and feedback(s). -- -jpeg. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 15:30:25 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E59BE16A41F for ; Wed, 16 Nov 2005 15:30:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B40443D45 for ; Wed, 16 Nov 2005 15:30:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAGFUPEN092382 for ; Wed, 16 Nov 2005 15:30:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAGFUOmr092377; Wed, 16 Nov 2005 15:30:24 GMT (envelope-from gnats) Date: Wed, 16 Nov 2005 15:30:24 GMT Message-Id: <200511161530.jAGFUOmr092377@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "D. J. Bernstein" Cc: Subject: Re: amd64/87348: amd64+smp+startkde always crashing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "D. J. Bernstein" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 15:30:26 -0000 The following reply was made to PR amd64/87348; it has been noted by GNATS. From: "D. J. Bernstein" To: bug-followup@freebsd.org Cc: Subject: Re: amd64/87348: amd64+smp+startkde always crashing Date: 16 Nov 2005 15:29:18 -0000 I think I've successfully tracked this one down: it's a serious X server bug, applicable to both BSD and Linux. Specifically, everything I've seen is fully explained by ATI Radeon DRI freezing the OS (no keyboard lights, no ping response, etc.) under AMD64 SMP. I've had no freezes after removing the ``Load "dri"'' line from the X configuration. ---D. J. Bernstein, Professor, Mathematics, Statistics, and Computer Science, University of Illinois at Chicago From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 16:27:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB50D16A41F for ; Wed, 16 Nov 2005 16:27:49 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74E1F43D68 for ; Wed, 16 Nov 2005 16:27:48 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IQ2006KP38O2760@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 16 Nov 2005 17:31:36 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IQ200JYS3730UB0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 16 Nov 2005 17:30:40 +0100 (CET) Date: Wed, 16 Nov 2005 17:24:45 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> To: freebsd-amd64@freebsd.org Message-id: <20051116172445.20613a0e.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:27:49 -0000 On Wed, 16 Nov 2005 16:13:54 +0100 (CET) Julien Gabel wrote: > * Sun Ultra 20 Workstation -- Hardware Specifications: > http://sunsolve.sun.com/handbook_private/Systems/Ultra20/spec.html > * Sun Ultra 20 Workstation -- Full Components List: > http://sunsolve.sun.com/handbook_private/Systems/Ultra20/components.html I don't know anything about this machine vs FreeBSD, but this is a better link: http://sunsolve.sun.com/handbook_pub/Systems/Ultra20/Ultra20.html -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 16:32:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 282A016A421 for ; Wed, 16 Nov 2005 16:32:57 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4004F43D5A for ; Wed, 16 Nov 2005 16:32:47 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 40A5E564C2; Wed, 16 Nov 2005 17:32:46 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57700-02-9; Wed, 16 Nov 2005 17:32:45 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 0F5F0564C1; Wed, 16 Nov 2005 17:32:45 +0100 (CET) Received: from 145.248.192.30 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Wed, 16 Nov 2005 17:32:45 +0100 (CET) Message-ID: <24221.145.248.192.30.1132158765.squirrel@webmail.thilelli.net> In-Reply-To: <20051116172445.20613a0e.torfinn.ingolfsen@broadpark.no> References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <20051116172445.20613a0e.torfinn.ingolfsen@broadpark.no> Date: Wed, 16 Nov 2005 17:32:45 +0100 (CET) From: "Julien Gabel" To: "Torfinn Ingolfsen" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:32:57 -0000 >> * Sun Ultra 20 Workstation -- Hardware Specifications: >> http://sunsolve.sun.com/handbook_private/Systems/Ultra20/spec.html >> * Sun Ultra 20 Workstation -- Full Components List: >> http://sunsolve.sun.com/handbook_private/Systems/Ultra20/components.html > I don't know anything about this machine vs FreeBSD, but this is a > better link: > http://sunsolve.sun.com/handbook_pub/Systems/Ultra20/Ultra20.html Yes, sorry for the private (registered) link and thanks for the public url. -- -jpeg. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 17:06:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6592A16A420 for ; Wed, 16 Nov 2005 17:06:22 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34C7243D6B for ; Wed, 16 Nov 2005 17:06:13 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.3/8.13.3) with ESMTP id jAGH6BN9092139; Wed, 16 Nov 2005 18:06:11 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 4CCD3B824; Wed, 16 Nov 2005 18:06:11 +0100 (CET) Date: Wed, 16 Nov 2005 18:06:11 +0100 From: Roland Smith To: Julien Gabel Message-ID: <20051116170611.GC33710@slackbox.xs4all.nl> Mail-Followup-To: Julien Gabel , freebsd-amd64@freebsd.org References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XWOWbaMNXpFDWE00" Content-Disposition: inline In-Reply-To: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 17:06:22 -0000 --XWOWbaMNXpFDWE00 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 16, 2005 at 04:13:54PM +0100, Julien Gabel wrote: > Hello, >=20 > I am currently looking for feedback on using a Sun Ultra 20 Workstation. >=20 > * Sun Ultra 20 Workstation -- Hardware Specifications: > http://sunsolve.sun.com/handbook_private/Systems/Ultra20/spec.html > Any chance to get it working using FreeBSD? Many thanks in advance for > reply(ies) and feedback(s). It seems to run Linux, so I'd _guess_ that most things would work. Not sure if Xorg supports PCI-express yet. But I bet you can have a no-name amd64 PC built to your specs for less. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --XWOWbaMNXpFDWE00 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDe2cDEnfvsMMhpyURAhI9AJwIZJAYNPushEAJ3TQYR3YY0IhGhwCfeVAu ACcGtlqf+bOvEgv9TlxHz8c= =pHg3 -----END PGP SIGNATURE----- --XWOWbaMNXpFDWE00-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 17:48:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45BA316A41F for ; Wed, 16 Nov 2005 17:48:03 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C32943D53 for ; Wed, 16 Nov 2005 17:48:02 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id AF189564C2 for ; Wed, 16 Nov 2005 18:48:00 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 62659-03 for ; Wed, 16 Nov 2005 18:47:59 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 4C24B564C1 for ; Wed, 16 Nov 2005 18:47:59 +0100 (CET) Received: from 145.248.192.30 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Wed, 16 Nov 2005 18:47:59 +0100 (CET) Message-ID: <50693.145.248.192.30.1132163279.squirrel@webmail.thilelli.net> In-Reply-To: <20051116170611.GC33710@slackbox.xs4all.nl> References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <20051116170611.GC33710@slackbox.xs4all.nl> Date: Wed, 16 Nov 2005 18:47:59 +0100 (CET) From: "Julien Gabel" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 17:48:03 -0000 >> I am currently looking for feedback on using a Sun Ultra 20 Workstation. >> [...] >> Any chance to get it working using FreeBSD? Many thanks in advance for >> reply(ies) and feedback(s). > It seems to run Linux, so I'd _guess_ that most things would work. Not > sure if Xorg supports PCI-express yet. This is what i would gess too at first, but since some additional "Driver and Diagnostics updates" are also provided[1], i am not sure anymore this kink of hardware (especially the motherboard and the SATA controller) may be supported "out of the box", based on the assumption of generic hardware or similar Linux support. On the other side, Windows is also supported and if i can imagine Sun to provide some binary driver(s) for Linux, i don't think it may be the case for Windows. So, i don't really know what to think... and ask the list ;) I think that PCI-Express is -- at least partially -- supported by Xorg via the 'Option "BusType" "PCIE"' configuration entry. The problem is more to know if a driver is provided by Xorg or in the binary updates on the downloadable ISO from Sun: i am pretty sure this one is a problem (i can't see any reference for the proposed cards on the release notes for Xorg 8.6.2...). > But I bet you can have a no-name amd64 PC built to your specs for less. Since this one is provided at work, it isn't an issue. -- -jpeg. [1] http://www.sun.com/desktop/workstation/ultra20/downloads.html From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 19:12:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 351A616A41F for ; Wed, 16 Nov 2005 19:12:58 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id A606A43D49 for ; Wed, 16 Nov 2005 19:12:57 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr12.xs4all.nl (8.13.3/8.13.3) with ESMTP id jAGJCtMC023999; Wed, 16 Nov 2005 20:12:55 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 4DE22B822; Wed, 16 Nov 2005 20:12:55 +0100 (CET) Date: Wed, 16 Nov 2005 20:12:55 +0100 From: Roland Smith To: Julien Gabel Message-ID: <20051116191255.GD33710@slackbox.xs4all.nl> Mail-Followup-To: Julien Gabel , freebsd-amd64@freebsd.org References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <20051116170611.GC33710@slackbox.xs4all.nl> <50693.145.248.192.30.1132163279.squirrel@webmail.thilelli.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W5WqUoFLvi1M7tJE" Content-Disposition: inline In-Reply-To: <50693.145.248.192.30.1132163279.squirrel@webmail.thilelli.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 19:12:58 -0000 --W5WqUoFLvi1M7tJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 16, 2005 at 06:47:59PM +0100, Julien Gabel wrote: > >> I am currently looking for feedback on using a Sun Ultra 20 Workstatio= n. > >> [...] > >> Any chance to get it working using FreeBSD? Many thanks in advance for > >> reply(ies) and feedback(s). >=20 > > It seems to run Linux, so I'd _guess_ that most things would work. Not > > sure if Xorg supports PCI-express yet. >=20 > This is what i would gess too at first, but since some additional "Driver > and Diagnostics updates" are also provided[1], i am not sure anymore this > kink of hardware (especially the motherboard and the SATA controller) may > be supported "out of the box", based on the assumption of generic hardware > or similar Linux support. On the other side, Windows is also supported > and if i can imagine Sun to provide some binary driver(s) for Linux, i > don't think it may be the case for Windows. So, i don't really know what > to think... and ask the list ;) Well, the thing comes with UNIX ((Open?)Solaris) installed, so unless there is some functionality in FreeBSD that you can't do without, you can always fall back on that. > I think that PCI-Express is -- at least partially -- supported by Xorg > via the 'Option "BusType" "PCIE"' configuration entry. The problem is > more to know if a driver is provided by Xorg or in the binary updates > on the downloadable ISO from Sun: i am pretty sure this one is a problem > (i can't see any reference for the proposed cards on the release notes > for Xorg 8.6.2...). Most of the cards listed use NVidia chips. Most nvidia cards will work in 2D in Xorg, but might not use much of the accelleration features provided by the card. Hardware OpenGL will probably not work. > > But I bet you can have a no-name amd64 PC built to your specs for less. >=20 > Since this one is provided at work, it isn't an issue. If there is already a machine in the house, just try booting the FreeBSD install CD, and look at the dmesg output. That should give you an idea what works and what doesn't. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --W5WqUoFLvi1M7tJE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDe4S3EnfvsMMhpyURAtLlAJ9uqBGSPmeJd0xdsOqVDMwHaKD8OACgmkyi rc/trZAVD6bK9fLrWk6VBqY= =zBFt -----END PGP SIGNATURE----- --W5WqUoFLvi1M7tJE-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 20:54:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 608BA16A41F for ; Wed, 16 Nov 2005 20:54:42 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id A64F643D46 for ; Wed, 16 Nov 2005 20:54:40 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 9FD20564C2 for ; Wed, 16 Nov 2005 21:54:39 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 70848-06-3 for ; Wed, 16 Nov 2005 21:54:38 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 48667564C1 for ; Wed, 16 Nov 2005 21:54:38 +0100 (CET) Received: from 192.168.1.20 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Wed, 16 Nov 2005 21:54:38 +0100 (CET) Message-ID: <58155.192.168.1.20.1132174478.squirrel@webmail.thilelli.net> In-Reply-To: <20051116191255.GD33710@slackbox.xs4all.nl> References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <20051116170611.GC33710@slackbox.xs4all.nl> <50693.145.248.192.30.1132163279.squirrel@webmail.thilelli.net> <20051116191255.GD33710@slackbox.xs4all.nl> Date: Wed, 16 Nov 2005 21:54:38 +0100 (CET) From: "Julien Gabel" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 20:54:42 -0000 >>>> I am currently looking for feedback on using a Sun U20 Workstation. >>>> [...] >>>> Any chance to get it working using FreeBSD? Many thanks in advance >>>> for reply(ies) and feedback(s). >>> It seems to run Linux, so I'd _guess_ that most things would work. Not >>> sure if Xorg supports PCI-express yet. >> This is what i would gess too at first, but since some additional >> "Driver and Diagnostics updates" are also provided[1], i am not sure >> anymore this kink of hardware (especially the motherboard and the SATA >> controller) may be supported "out of the box", based on the assumption >> of generic hardware or similar Linux support. On the other side, >> Windows is also supported and if i can imagine Sun to provide some >> binary driver(s) for Linux, i don't think it may be the case for >> Windows. So, i don't really know what to think... and ask the list ;) > Well, the thing comes with UNIX ((Open?)Solaris) installed, so unless > there is some functionality in FreeBSD that you can't do without, you > can always fall back on that. For sure! I just wanted to use FreeBSD on this kind of machine, but falling back to Solaris 10 will be the answer if that is not (yet?) an option. >> I think that PCI-Express is -- at least partially -- supported by Xorg >> via the 'Option "BusType" "PCIE"' configuration entry. The problem is >> more to know if a driver is provided by Xorg or in the binary updates >> on the downloadable ISO from Sun: i am pretty sure this one is a problem >> (i can't see any reference for the proposed cards on the release notes >> for Xorg 8.6.2...). > Most of the cards listed use NVidia chips. Most nvidia cards will work > in 2D in Xorg, but might not use much of the accelleration features > provided by the card. Hardware OpenGL will probably not work. I am not interesting in gaming here, so lack of 3D support isn't a problem. But because i had problem running an U10 (sparc64) in the past with a Creator graphic card, i am suspicious here -- maybe without reason (but nothing say the opposite). >>> But I bet you can have a no-name amd64 PC built to your specs for >>> less. >> Since this one is provided at work, it isn't an issue. > If there is already a machine in the house, just try booting the FreeBSD > install CD, and look at the dmesg output. That should give you an idea > what works and what doesn't. Right, unless it is just _planned_ to acquire some of this kind of machine, hence my questioning. -- -jpeg. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 21:42:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F5DE16A41F for ; Wed, 16 Nov 2005 21:42:10 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4CA543D4C for ; Wed, 16 Nov 2005 21:42:07 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5F59C.dip.t-dialin.net [84.165.245.156]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAGLfvuW017321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 22:42:04 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAGLflQG071757; Wed, 16 Nov 2005 22:41:47 +0100 (CET) Message-ID: <437BA7B1.5060200@deadcafe.de> Date: Wed, 16 Nov 2005 22:42:09 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: jpeg@thilelli.net References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> In-Reply-To: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 21:42:10 -0000 Julien Gabel schrieb: > Hello, > > I am currently looking for feedback on using a Sun Ultra 20 Workstation. > > I didn't found anything on freebsd-amd64@, nor in the list of supported > motherboards (http://www.freebsd.org/platforms/amd64/motherboards.html). > Only the Sun Fire V20z seems ok. The Ultra-20 contains just an ordinary Tyan Tomcat K8E (S2865) mainboard with some components stripped off (just like the X2100 server BTW). I see no reason why it shouldn't run FreeBSD. The following components from a normal S2865 are missing on the U-20: - no PS/2 mouse/keyboard ports - USB should work though - no serial port - no bge ethernet, only nve The last one should be really annoying since the nve driver on FreeBSD is still quite buggy. Daniel From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 01:34:41 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDF2816A420 for ; Thu, 17 Nov 2005 01:34:41 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C7243D58 for ; Thu, 17 Nov 2005 01:34:37 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1810498nzo for ; Wed, 16 Nov 2005 17:34:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=alAM57kb0GbPfkYznicD/jXhYvmwXkeMhm0KkTKs4FTE78wOG0Zo7+EgSC44OygRPbYWZM1Y4tQnWZ3P08Krv9+Iw1WtDodD+aLCNS17r/KaClYWpyAzsrwhVJ49Mw32MnEqLX9CMEYuh9Mu48b3n/KG2P/typGQ1UXskRP5mDk= Received: by 10.36.3.15 with SMTP id 15mr7097843nzc; Wed, 16 Nov 2005 17:34:37 -0800 (PST) Received: by 10.37.20.33 with HTTP; Wed, 16 Nov 2005 17:34:37 -0800 (PST) Message-ID: Date: Thu, 17 Nov 2005 04:34:37 +0300 From: "Andrew P." To: "O. Hartmann" In-Reply-To: <437AE312.4090709@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <437A993B.8080204@roq.com> <437AE312.4090709@mail.uni-mainz.de> Cc: amd64@freebsd.org, re-amd64@FreeBSD.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 01:34:42 -0000 Just to confirm it: I tried 5.4-RELEASE, 6.0-RELEASE and 6.0-STABLE - every one panicked with just "options IPSEC" added to generic kernel and "setkey -D" command typed. I'll be conducting basic kernel debugging as soon as I learn how to do it. As far as I am concerned, this issue is dead serious and very highly critical. Networking is the single most powerful strength of *BSD and we can't live with such core functionality as IPSec broken on a Tier-1 platform. From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 01:53:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 471B116A41F for ; Thu, 17 Nov 2005 01:53:06 +0000 (GMT) (envelope-from nicca64@srt.com) Received: from hilda.srt.com (hilda.srt.com [216.221.96.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id D917D43D6E for ; Thu, 17 Nov 2005 01:53:01 +0000 (GMT) (envelope-from nicca64@srt.com) Received: from [192.168.1.102] (dsl-119-235.srtnet.com [216.221.119.235]) (authenticated bits=0) by hilda.srt.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jAH1qsTJ025171 for ; Wed, 16 Nov 2005 19:52:55 -0600 Message-ID: <437BE280.5080304@srt.com> Date: Wed, 16 Nov 2005 19:53:04 -0600 From: Christopher Thomas User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: DFI Lanparty NF4 Ultra-D AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 01:53:06 -0000 Hello, first time poster, long time user. System: DFI Lanparty NF4 ultra-D AMD64 3500+ 1GB GeIL DDR400 Dual Channel Maxtor 12GB 5400RM Lite-ON CDRW Problem: Can install FBSD 6.0-Release/amd64 and i386 just fine, but upon first reboot I get. Fatal Trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xffffffff8022b99a stack pointer = 0x10:0xfffffff809769f0 frame pointer = 0x10:0xfffff003b8af800 code segment = base 0x0, limit 0xfffff, type 0x1b = DBL 0, pres 1, long 1, def32 0, gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 18 panic: integer divide fault Uptime: 1s Cannot dump. No dump device defined. (hand typed on my WinXP box (same mobo)) My plea: I have been using FBSD for about 5 years, but I've never had a panic, never had a problem installing, so I've had limited experience and need to troubleshoot a system. Luckily, I found a problem, and I want to learn from it. But still fix my problem. So, if possible, can some one help me? I've disabled what I could, removed everyting but HDD, tried every boot option in the boot menu. I have a suspicion that the problem might lay in the nf4/nvidia chipset? Maybe the ataraid? But thats just based off of the current nf4 problems I've seen. Doing a search for trap 18 only brings up trap 12, (with two instances of trap 18 that have no solutions.) Thank you very much, it is communitis, and lists like this that make my mind up about FreeBSD and lets me know why I chose such a wonderful OS. ---Christopher Thomas From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 11:02:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7454E16A41F for ; Thu, 17 Nov 2005 11:02:31 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE69D43D49 for ; Thu, 17 Nov 2005 11:02:30 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so422298wxc for ; Thu, 17 Nov 2005 03:02:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=roRlJb7Daf4vd1e8dZJI+r53ETnS4/NgyBUetH2V9UIeELmfgIqlx4DVvC33ztkGYf02/nQGZkn8t8Azb5HgjPz9BYYQtUxBRZGizPZ40zJdTv7jX4Yiuo99wZBoPHBVolJFE0pZhyQFwGBqamvOpJHpku+dhh7XFZexfA5rmEA= Received: by 10.70.37.13 with SMTP id k13mr4753916wxk; Thu, 17 Nov 2005 03:02:29 -0800 (PST) Received: by 10.70.32.20 with HTTP; Thu, 17 Nov 2005 03:02:29 -0800 (PST) Message-ID: <27dbfc8c0511170302v407fb4fbvd83d02b244b20bc0@mail.gmail.com> Date: Thu, 17 Nov 2005 12:02:29 +0100 From: Valerio daelli To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with bash ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 11:02:31 -0000 Hello everybody I am trying to install a bash on a FreeBSD 5.4 amd64. I cvsupped the sources and ports and just recompiled everything. When I go to /usr/ports/shells/bash and try to compile it, I get this error= : ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------- peter# make CONFIGURE_ARGS=3D"--without-bash-malloc --disable-rpath --enable-disabled-builtins --enable-static-link --disable-nls" =3D=3D=3D> bash-3.0.16_1 depends on shared library: intl - not found =3D=3D=3D> Verifying install for intl in /usr/ports/devel/gettext =3D=3D=3D> gettext-0.14.5 depends on file: /usr/local/bin/libtool15 - not f= ound =3D=3D=3D> Verifying install for /usr/local/bin/libtool15 in /usr/ports/devel/libtool15 =3D=3D=3D> Returning to build of gettext-0.14.5 =3D=3D=3D> gettext-0.14.5 depends on shared library: iconv.3 - not found =3D=3D=3D> Verifying install for iconv.3 in /usr/ports/converters/libiconv =3D=3D=3D> Building for libiconv-1.9.2_1 builddir=3D"`pwd`"; cd libcharset && make all && make install-lib libdir=3D"$builddir/lib" includedir=3D"$builddir/lib" cd lib && make all /bin/sh /usr/local/bin/libtool15 --mode=3Dcompile cc -I. -I. -I.. -I./.. -I../include -O -pipe -march=3Dopteron -DLIBDIR=3D\"/usr/local/lib\" -DENABLE_RELOCATABLE=3D1 -DIN_LIBRARY -DINSTALLDIR=3D\"/usr/local/lib\" -DNO_XMALLOC -Dset_relocation_prefix=3Dlibcharset_set_relocation_prefix -Drelocate=3Dlibcharset_relocate -DHAVE_CONFIG_H -DLIBDIR=3D\"/usr/local/libdata\" -c ./localcharset.c /usr/local/bin/libtool15: Can't open /usr/local/bin/libtool15: No such file or directory *** Error code 2 Stop in /usr/ports/converters/libiconv/work/libiconv-1.9.2/libcharset/lib. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.9.2/libcharset. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.9.2. *** Error code 1 Stop in /usr/ports/converters/libiconv. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/shells/bash. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------- which I circumvent installing by hand libtool15 and gettext. Should I open a PR on this? Thanks Valerio Daelli From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 12:22:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EC2516A41F for ; Thu, 17 Nov 2005 12:22:29 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id CED6243D45 for ; Thu, 17 Nov 2005 12:22:28 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 01E39564C2; Thu, 17 Nov 2005 13:22:27 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57826-04; Thu, 17 Nov 2005 13:22:25 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id A9DB3564C1; Thu, 17 Nov 2005 13:22:25 +0100 (CET) Received: from 145.248.192.30 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Thu, 17 Nov 2005 13:22:25 +0100 (CET) Message-ID: <14668.145.248.192.30.1132230145.squirrel@webmail.thilelli.net> In-Reply-To: <437BA7B1.5060200@deadcafe.de> References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <437BA7B1.5060200@deadcafe.de> Date: Thu, 17 Nov 2005 13:22:25 +0100 (CET) From: "Julien Gabel" To: "Daniel Rock" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 12:22:29 -0000 >> I am currently looking for feedback on using a Sun Ultra 20 Workstation. >> >> I didn't found anything on freebsd-amd64@, nor in the list of supported >> motherboards (http://www.freebsd.org/platforms/amd64/motherboards.html). >> Only the Sun Fire V20z seems ok. > The Ultra-20 contains just an ordinary Tyan Tomcat K8E (S2865) mainboard > with some components stripped off (just like the X2100 server BTW). I see > no reason why it shouldn't run FreeBSD. Certainly, even if the FreeBSD report's feedback is not very optimist on this particular mainboard (mainly because some of the main components are not _yet_ tested, as PCI-E or onboard Gig-E). > The following components from a normal S2865 are missing on the U-20: > - no PS/2 mouse/keyboard ports - USB should work though > - no serial port Not having a serial port may be a problem. Is it possible to use the USB port to act a serial for console access? > - no bge ethernet, only nve > > The last one should be really annoying since the nve driver on FreeBSD > is still quite buggy. Since we certainly will use an other ethernet card on bus PCI, the last point is annoying but not for the moment (we doesn't use Gig-E yet, just 100Mbps (as with nve(4), it seems)). Thank you. -- -jpeg. From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 13:34:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 080C616A41F for ; Thu, 17 Nov 2005 13:34:19 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA20D43D75 for ; Thu, 17 Nov 2005 13:34:10 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1915096nzo for ; Thu, 17 Nov 2005 05:34:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CYVZjf1yZgoDYT9oK6Ge7Vrgqc1vOJf9d4ThijHW5fx1YuvfDzYXD6W1w7WnKM3L3o9B8cJcEmysRvhcA0fjMBSy+FdomVEzXSsk8vod0D4NpN/gmjUYGE155Dxd3CaFSC7UM49oIH3hTGh7BThwRGJKIIDzhrQP4+ROCC7xteU= Received: by 10.36.177.11 with SMTP id z11mr7525518nze; Thu, 17 Nov 2005 05:34:09 -0800 (PST) Received: by 10.36.71.10 with HTTP; Thu, 17 Nov 2005 05:34:09 -0800 (PST) Message-ID: <28edec3c0511170534n14586426vd7cee0115e45b58c@mail.gmail.com> Date: Thu, 17 Nov 2005 21:34:09 +0800 From: "Mars G. Miro" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: nasty amd64 date bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 13:34:19 -0000 Hiya list! Earlier today, one of my cow-orkers inadvertently did a: # date 190000000000 and his FreeBSD/amd64 box hung and dead on the water :-( I tried to reproduce it and can confirm that it only happens on FreeBSD/amd64, on 5.4R and in 6.0RC1 (6.0R might be affected). In i386 it just gives an 'incorrect date' message or something if you type in something not w/in 190300000000->203800000000 range. Also this requires root privs so not really something to panic. Any case, I wanted to break to debugger but ran out of time (mebe tomorrow when I'm back at work), or perhaps somebody else here who can risk crash-testing their amd64 boxen can try it. Thanks and FYI. cheers mars From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 13:35:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BC6E16A41F for ; Thu, 17 Nov 2005 13:35:11 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BBDB43D6D for ; Thu, 17 Nov 2005 13:35:07 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1915281nzo for ; Thu, 17 Nov 2005 05:35:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fm+EriRy1y40I8Cz81zMkQTRRtzE+P0zW+zzt4SugTnMbpFow7jeJvmlwxUt0keClIBsrVrT5iC0PWxwC6hb3Fb6ytGDVpCMRcWdXFz1Vb6f0GaavzOBXnsrDrtMmeU4kJj64MWRJjDLXO9R39bdR9dadRGzHyiDIlic1mpknB4= Received: by 10.37.12.41 with SMTP id p41mr6615600nzi; Thu, 17 Nov 2005 05:35:07 -0800 (PST) Received: by 10.37.20.33 with HTTP; Thu, 17 Nov 2005 05:35:07 -0800 (PST) Message-ID: Date: Thu, 17 Nov 2005 16:35:07 +0300 From: "Andrew P." To: Valerio daelli In-Reply-To: <27dbfc8c0511170302v407fb4fbvd83d02b244b20bc0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <27dbfc8c0511170302v407fb4fbvd83d02b244b20bc0@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: Problem with bash ports on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 13:35:11 -0000 On 11/17/05, Valerio daelli wrote: > Hello everybody > I am trying to install a bash on a FreeBSD 5.4 amd64. > I cvsupped the sources and ports and just recompiled everything. > When I go to /usr/ports/shells/bash and try to compile it, I get this err= or: > > > > which I circumvent installing by hand libtool15 and gettext. > Should I open a PR on this? Just repeat your mail to ports@ and cc it to the port's maintainer. Ports PR's without fixes are not very welcome. Still if nobody answers your complaint, file a PR - or better yet, provide a fix (I think something like USE_LIBTOOL, but it requires some attention). Thanks From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 16:26:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A086416A41F for ; Thu, 17 Nov 2005 16:26:16 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 627A343D49 for ; Thu, 17 Nov 2005 16:26:16 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from dsl-200-95-47-79.prod-infinitum.com.mx (dsl-200-95-47-79.prod-infinitum.com.mx [200.95.47.79]) by sophia3.e-shell.net (Postfix) with ESMTP id B8EA4656826 for ; Thu, 17 Nov 2005 10:26:15 -0600 (CST) From: Axel Gonzalez To: freebsd-amd64@freebsd.org Date: Thu, 17 Nov 2005 10:26:07 -0600 User-Agent: KMail/1.8.3 References: <28edec3c0511170534n14586426vd7cee0115e45b58c@mail.gmail.com> In-Reply-To: <28edec3c0511170534n14586426vd7cee0115e45b58c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171026.08194.loox@e-shell.net> Subject: Re: nasty amd64 date bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:26:16 -0000 $ date -r 190300000000 Sun May 14 01:06:40 CST 8000 This is probably a bios error, that can't handle dates so much in the future This happens only on amd64, because it uses 64 bits utimes. On i386, with 32 bits utimes, the maximun date is about 2032, so the bios shouldn't have problems with that date (remember the *nix version of the y2k problem ??) So this is not really a bug, is a feature ;) On Thursday 17 November 2005 07:34, Mars G. Miro wrote: > Hiya list! > > Earlier today, one of my cow-orkers inadvertently did a: > # date 190000000000 > and his FreeBSD/amd64 box hung and dead on the water :-( > > I tried to reproduce it and can confirm that it only happens on > FreeBSD/amd64, on 5.4R and in 6.0RC1 (6.0R might be affected). In i386 > it just gives an 'incorrect date' message or something if you type in > something not w/in 190300000000->203800000000 range. Also this > requires root privs so not really something to panic. > Any case, I wanted to break to debugger but ran out of time (mebe > tomorrow when I'm back at work), or perhaps somebody else here who can > risk crash-testing their amd64 boxen can try it. > > Thanks and FYI. > > cheers > mars > _______________________________________________ > 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 Nov 17 16:42:07 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C742516A41F; Thu, 17 Nov 2005 16:42:07 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31D7A43D70; Thu, 17 Nov 2005 16:42:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2124645 for multiple; Thu, 17 Nov 2005 11:42:07 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAHGfvtL023178; Thu, 17 Nov 2005 11:42:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Thu, 17 Nov 2005 11:42:04 -0500 User-Agent: KMail/1.8.2 References: <437BE280.5080304@srt.com> In-Reply-To: <437BE280.5080304@srt.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171142.05886.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: sos@freebsd.org, Christopher Thomas Subject: Re: DFI Lanparty NF4 Ultra-D AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:42:07 -0000 On Wednesday 16 November 2005 08:53 pm, Christopher Thomas wrote: > Hello, > > first time poster, long time user. > > System: > DFI Lanparty NF4 ultra-D > AMD64 3500+ > 1GB GeIL DDR400 Dual Channel > Maxtor 12GB 5400RM > Lite-ON CDRW > > Problem: > Can install FBSD 6.0-Release/amd64 and i386 just fine, but upon first > reboot I get. > > Fatal Trap 18: integer divide fault while in kernel mode > instruction pointer = 0x8:0xffffffff8022b99a > stack pointer = 0x10:0xfffffff809769f0 > frame pointer = 0x10:0xfffff003b8af800 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DBL 0, pres 1, long 1, def32 0, gran 1 > processor flags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > trap number = 18 > panic: integer divide fault > Uptime: 1s > Cannot dump. No dump device defined. > (hand typed on my WinXP box (same mobo)) It does seem related to ataraid. I just ran gdb on the kernel.debug on the 6.0 install CD and that instruction pointer comes out to: (gdb) l *0xffffffff8022b99a 0xffffffff8022b99a is in ata_raid_promise_read_meta (/usr/src/sys/dev/ata/ata-raid.c:2497). Which corresponds to the line: if (ata_raid_rw(parent, PR_LBA(parent), meta, sizeof(struct promise_raid_conf), ATA_R_READ)) { It looks like it probably died in the PR_LBA macro. Perhaps the ata-raid code isn't checking for a 'heads' value of 0 and it needs to? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 17:10:26 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.ORG Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9713116A41F; Thu, 17 Nov 2005 17:10:26 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB12743D73; Thu, 17 Nov 2005 17:10:25 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id jAHHAK8i042444; Thu, 17 Nov 2005 18:10:20 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <437CB97B.8050009@deepcore.dk> Date: Thu, 17 Nov 2005 18:10:19 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <437BE280.5080304@srt.com> <200511171142.05886.jhb@freebsd.org> In-Reply-To: <200511171142.05886.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-amd64@FreeBSD.ORG, Christopher Thomas Subject: Re: DFI Lanparty NF4 Ultra-D AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:10:26 -0000 John Baldwin wrote: > On Wednesday 16 November 2005 08:53 pm, Christopher Thomas wrote: > >>Hello, >> >>first time poster, long time user. >> >>System: >>DFI Lanparty NF4 ultra-D >>AMD64 3500+ >>1GB GeIL DDR400 Dual Channel >>Maxtor 12GB 5400RM >>Lite-ON CDRW >> >>Problem: >>Can install FBSD 6.0-Release/amd64 and i386 just fine, but upon first >>reboot I get. >> >>Fatal Trap 18: integer divide fault while in kernel mode >>instruction pointer = 0x8:0xffffffff8022b99a >>stack pointer = 0x10:0xfffffff809769f0 >>frame pointer = 0x10:0xfffff003b8af800 >>code segment = base 0x0, limit 0xfffff, type 0x1b >> = DBL 0, pres 1, long 1, def32 0, gran 1 >>processor flags = interrupt enabled, resume, IOPL = 0 >>current process = 0 (swapper) >>trap number = 18 >>panic: integer divide fault >>Uptime: 1s >>Cannot dump. No dump device defined. >>(hand typed on my WinXP box (same mobo)) > > > It does seem related to ataraid. I just ran gdb on the kernel.debug on the > 6.0 install CD and that instruction pointer comes out to: > > (gdb) l *0xffffffff8022b99a > 0xffffffff8022b99a is in ata_raid_promise_read_meta > (/usr/src/sys/dev/ata/ata-raid.c:2497). > > Which corresponds to the line: > > > if (ata_raid_rw(parent, PR_LBA(parent), > meta, sizeof(struct promise_raid_conf), ATA_R_READ)) { > > It looks like it probably died in the PR_LBA macro. Perhaps the ata-raid code > isn't checking for a 'heads' value of 0 and it needs to? Hmm heads and sectors cannot be null or at least then something else has gone wrong before this. Is the disk found and reported correctly (boot verbose) or does the geometry etc look strange ? -Søren From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 17:20:23 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEAF716A440 for ; Thu, 17 Nov 2005 17:20:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F34543D45 for ; Thu, 17 Nov 2005 17:20:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAHHKLSR037229 for ; Thu, 17 Nov 2005 17:20:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAHHKLuh037228; Thu, 17 Nov 2005 17:20:21 GMT (envelope-from gnats) Resent-Date: Thu, 17 Nov 2005 17:20:21 GMT Resent-Message-Id: <200511171720.jAHHKLuh037228@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, Ivo Janssen Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB02416A420 for ; Thu, 17 Nov 2005 17:11:54 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0654443D5C for ; Thu, 17 Nov 2005 17:11:54 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAHHBris058765 for ; Thu, 17 Nov 2005 17:11:53 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAHHBr7j058763; Thu, 17 Nov 2005 17:11:53 GMT (envelope-from nobody) Message-Id: <200511171711.jAHHBr7j058763@www.freebsd.org> Date: Thu, 17 Nov 2005 17:11:53 GMT From: Ivo Janssen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:20:24 -0000 >Number: 89202 >Category: amd64 >Synopsis: Kernel crash when accessing filesystem >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 17 17:20:21 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Ivo Janssen >Release: FreeBSD 6.0-STABLE >Organization: DCTI >Environment: FreeBSD fritz.distributed.net 6.0-STABLE FreeBSD 6.0-STABLE #3: Thu Nov 17 16:13:18 UTC 2005 root@fritz.distributed.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When copying larger trees to a newly created raid10 partition on a 3ware card, e.g: cp -Rp /usr/obj /usr/local/raid10 we get a consistent kernel panic. These are the options to create the filesystem. # newfs -U -O2 -b 8192 -f 1024 -g 1073741824 /dev/twed1s1d and also a tunefs -e 20480 fritz# tunefs -p /dev/twed1s1d tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 20480 tunefs: average file size: (-f) 1073741824 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) This partition is our data partition. The system partitions, which was created with an FBSD5 doesn't exhibit the bug: fritz# tunefs -p /dev/twed0s1a tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time Now follows the kernel dump. Note that we're running on amd64. We still have the vmcore, if you need more information, we can probably provide that. ivo@fritz: / > sudo kgdb /usr/obj/usr/src/sys/GENERIC/kernel.debug /var/crash/vmcore.2 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xffffffff8051f9cf stack pointer = 0x10:0xffffffffacff66f0 frame pointer = 0x10:0xffffff00c14e0400 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 = 786 (cp) trap number = 18 panic: integer divide fault Uptime: 7m39s Dumping 3999 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3999MB (1023728 pages) 3983 3967 3951 3935 3919 3903 3887 3871 3855 3839 3823 3807 3791 3775 3759 3743 3727 3711 3695 3679 3663 3647 3631 3615 3599 3583 3567 3551 3535 3519 3503 3487 3471 3455 3439 3423 3407 3391 3375 3359 3343 3327 3311 3295 3279 3263 3247 3231 3215 3199 3183 3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959 2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 9 11 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff803b7993 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #3 0xffffffff803b7f96 in panic (fmt=0xffffff00b9ada000 "ÀÙ\035¹") at /usr/src/sys/kern/kern_shutdown.c:555 #4 0xffffffff8058f53f in trap_fatal (frame=0xffffff00b9ada000, eva=18446742977303665088) at /usr/src/sys/amd64/amd64/trap.c:655 #5 0xffffffff8058f9e2 in trap (frame= {tf_rdi = 0, tf_rsi = 0, tf_rdx = 0, tf_rcx = 44228608, tf_r8 = 64, tf_r9 = 12682, tf_rax = 44228608, tf_rbx = -1096272840704, tf_rbp = -1096268512256, tf_r10 = 11584, tf_r11 = 8688, tf_r12 = -1096396636160, tf_r13 = 11583, tf_r14 = -1096272840704, tf_r15 = 255, tf_trapno = 18, tf_addr = 0, tf_flags = 2147483648012, tf_err = 0, tf_rip = -2142111281, tf_cs = 8, tf_rflags = 66118, tf_rsp = -1392548096, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:467 #6 0xffffffff8057f06b in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #7 0xffffffff8051f9cf in ffs_valloc (pvp=0xffffff00b908e1f0, mode=16877, cred=0x0, vpp=0xffffffffacff6798) at libkern.h:56 #8 0xffffffff8054413e in ufs_mkdir (ap=0xffffffffacff69a0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1333 #9 0xffffffff805dfe55 in VOP_MKDIR_APV (vop=0x2a2e000, a=0xffffffffacff69a0) at vnode_if.c:1251 #10 0xffffffff80428bd6 in kern_mkdir (td=0xffffff00b908e1f0, path=0xffffff00c0335c00 "¨\\3À", segflg=4, mode=16877) at vnode_if.h:653 #11 0xffffffff80590351 in syscall (frame= {tf_rdi = 5256368, tf_rsi = 16877, tf_rdx = -1, tf_rcx = 2, tf_r8 = -2138905248, tf_r9 = 1, tf_rax = 136, tf_rbx = 5341440, tf_rbp = 1, tf_r10 = 0, tf_r11 = 0, tf_r12 = 0, tf_r13 = 5328896, tf_r14 = 0, tf_r15 = 1, tf_trapno = 12, tf_addr = 34366781936, tf_flags = 0, tf_err = 2, tf_rip = 34366970428, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488349640, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:787 #12 0xffffffff8057f208 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #13 0x00000008006e5a3c in ?? () Previous frame inner to this frame (corrupt stack?) >How-To-Repeat: When copying larger trees to that partition, e.g: cp -Rp /usr/obj /usr/local/raid10 we get a consistent kernel panic. >Fix: unknown fix >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 17:49:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1216316A41F for ; Thu, 17 Nov 2005 17:49:45 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66EFA43D49 for ; Thu, 17 Nov 2005 17:49:44 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5F1E9.dip.t-dialin.net [84.165.241.233]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAHHnZ1o018584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 18:49:37 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAHHnOYr004611; Thu, 17 Nov 2005 18:49:24 +0100 (CET) Message-ID: <437CC2A0.4010006@deadcafe.de> Date: Thu, 17 Nov 2005 18:49:20 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: jpeg@thilelli.net References: <44611.145.248.192.30.1132154034.squirrel@webmail.thilelli.net> <437BA7B1.5060200@deadcafe.de> <14668.145.248.192.30.1132230145.squirrel@webmail.thilelli.net> In-Reply-To: <14668.145.248.192.30.1132230145.squirrel@webmail.thilelli.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Cc: freebsd-amd64@freebsd.org Subject: Re: Sun U20 supported, fully/partially working... or not at all? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:49:45 -0000 Julien Gabel schrieb: > Certainly, even if the FreeBSD report's feedback is not very optimist > on this particular mainboard (mainly because some of the main components > are not _yet_ tested, as PCI-E or onboard Gig-E). Onboard Ethernet should work. It is just plain NForce4 Ethernet. I haven't tested it on this mobo, but on a Tyan S2895. On this machine nve does work - as long I don't have memory beneath 4GB. I have to clip the kernel to a maximum of 4GB (via MAXMEM config variable), otherwise nve doesn't work at all. With this workaround I can usually transfer some 100 GBytes before nve problems come up again. > Not having a serial port may be a problem. Is it possible to use the > USB port to act a serial for console access? I don't think so. But I don't know if and how Sun customized the standard S2865 BIOS. > Since we certainly will use an other ethernet card on bus PCI, the last > point is annoying but not for the moment (we doesn't use Gig-E yet, just > 100Mbps (as with nve(4), it seems)). nve is unstable not only with GigE, but (at least for me) also with only 100Mb Daniel From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 18:20:19 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED3E816A41F for ; Thu, 17 Nov 2005 18:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C255143D49 for ; Thu, 17 Nov 2005 18:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAHIKJN4046200 for ; Thu, 17 Nov 2005 18:20:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAHIKJef046199; Thu, 17 Nov 2005 18:20:19 GMT (envelope-from gnats) Date: Thu, 17 Nov 2005 18:20:19 GMT Message-Id: <200511171820.jAHIKJef046199@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Ivo Janssen Cc: Subject: Re: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ivo Janssen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 18:20:20 -0000 The following reply was made to PR amd64/89202; it has been noted by GNATS. From: Ivo Janssen To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/89202: Kernel crash when accessing filesystem Date: Thu, 17 Nov 2005 12:11:12 -0600 (CST) More information: I recreated the filesystem without the huge -f (avg filesize) option, which we had initially set to 1Gb: # newfs -U -O2 -b 8192 -f 1024 # tunefs -e 20480 (10x the default) With the defaults of avg filesize of 16384, we don't see a crash. I then started playing with tunefs. Increasing the avg filesize to -f 16777216 (16Mb), we don't see a crash. Increasing the avg filesize to -f 33554432 (32Mb), we repro the crash. By the way, cvsup was performed at around Nov16 23:00 UTC, I can probably find the exact timestamp if needed. Ivo From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 18:40:18 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12A3F16A41F for ; Thu, 17 Nov 2005 18:40:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B522C43D58 for ; Thu, 17 Nov 2005 18:40:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAHIeHue048677 for ; Thu, 17 Nov 2005 18:40:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAHIeHbm048676; Thu, 17 Nov 2005 18:40:17 GMT (envelope-from gnats) Date: Thu, 17 Nov 2005 18:40:17 GMT Message-Id: <200511171840.jAHIeHbm048676@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Ivo Janssen Cc: Subject: Re: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ivo Janssen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 18:40:18 -0000 The following reply was made to PR amd64/89202; it has been noted by GNATS. From: Ivo Janssen To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/89202: Kernel crash when accessing filesystem Date: Thu, 17 Nov 2005 12:35:20 -0600 (CST) More information: In sys/ufs/ffs/ffs_alloc.c we find: dirsize = fs->fs_avgfilesize * fs->fs_avgfpdir dirsize is int, so it's an overflow our crash happened in a mkdir operation indeed our tunefs reports: > tunefs: average number of files in a directory: (-s) 64 64 * 64 Mb == 2^32 So if a directory size can only be 4 gb, if we specify that the avg filesize is 64Mb and the avg number of files is 64, we overflow... From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 20:01:47 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 606B316A41F for ; Thu, 17 Nov 2005 20:01:47 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9024443D46 for ; Thu, 17 Nov 2005 20:01:46 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHK1gVp005392; Fri, 18 Nov 2005 07:01:42 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHK1elw023114; Fri, 18 Nov 2005 07:01:41 +1100 Date: Fri, 18 Nov 2005 07:01:40 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Axel Gonzalez In-Reply-To: <200511171026.08194.loox@e-shell.net> Message-ID: <20051118055837.W96399@delplex.bde.org> References: <28edec3c0511170534n14586426vd7cee0115e45b58c@mail.gmail.com> <200511171026.08194.loox@e-shell.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: nasty amd64 date bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 20:01:47 -0000 On Thu, 17 Nov 2005, Axel Gonzalez wrote: > $ date -r 190300000000 > Sun May 14 01:06:40 CST 8000 > > This is probably a bios error, that can't handle dates so much in the future > > This happens only on amd64, because it uses 64 bits utimes. amd64 has 64 bit time_t's. There are no utimes here. > On i386, with 32 bits utimes, the maximun date is about 2032, so the bios > shouldn't have problems with that date (remember the *nix version of the y2k > problem ??) This shows that 64-bit time_t's don't actually work. Probably something is looping about 190000000000 times. There used to be such a loop in kern_tc.c. This loop still has overflow bugs in its sanity checking (see rev.1.156) but these only reduce the amount of looping for steps larger than INT_MAX and increase it from 0 iterations to at most LARGE_STEP = 200 iterations for steps smaller than INT_MAX. > So this is not really a bug, is a feature ;) Nah. [Context lost to top posting.] Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 20:31:02 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 474B816A41F for ; Thu, 17 Nov 2005 20:31:02 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D32C43D45 for ; Thu, 17 Nov 2005 20:31:01 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHKUwcx026099; Fri, 18 Nov 2005 07:30:58 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHKUunk008519; Fri, 18 Nov 2005 07:30:57 +1100 Date: Fri, 18 Nov 2005 07:30:56 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Ivo Janssen In-Reply-To: <200511171820.jAHIKJef046199@freefall.freebsd.org> Message-ID: <20051118071624.V96570@delplex.bde.org> References: <200511171820.jAHIKJef046199@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 20:31:02 -0000 On Thu, 17 Nov 2005, Ivo Janssen wrote: > I recreated the filesystem without the huge -f (avg filesize) option, > which we had initially set to 1Gb: > # newfs -U -O2 -b 8192 -f 1024 > # tunefs -e 20480 (10x the default) > > With the defaults of avg filesize of 16384, we don't see a crash. I > then started playing with tunefs. > Increasing the avg filesize to -f 16777216 (16Mb), we don't see a crash. > Increasing the avg filesize to -f 33554432 (32Mb), we repro the crash. I have had the following comment about this bug (but haven't fixed it) for many years % Index: ffs_alloc.c % =================================================================== % RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_alloc.c,v % retrieving revision 1.121 % diff -u -2 -r1.121 ffs_alloc.c % --- ffs_alloc.c 16 Jun 2004 09:47:25 -0000 1.121 % +++ ffs_alloc.c 28 Oct 2004 15:12:47 -0000 % @@ -964,4 +991,11 @@ % minbfree = 1; % cgsize = fs->fs_fsize * fs->fs_fpg; % + /* % + * XXX the following multiplication can overflow, since newfs can % + * be abused to set fs_avgfilesize and fs_avgfpdir to preposterous % + * values. For the particular preposterous values of (64M, 16), % + * the multiplication overflows to 0 and then dirsize = 0 sometimes % + * causes division by 0. % + */ % dirsize = fs->fs_avgfilesize * fs->fs_avgfpdir; % curdirsize = avgndir ? (cgsize - avgbfree * fs->fs_bsize) / avgndir : 0; This bug is easy to work around by not changing fs->fs_avgfilesize or fs->fs_avgfpdir. Tuning them has limited useful effects. Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 21:06:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 711B316A41F; Thu, 17 Nov 2005 21:06:48 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8943043D53; Thu, 17 Nov 2005 21:06:47 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAHL6krN064390; Thu, 17 Nov 2005 16:06:46 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <437CF0E5.5030405@wmptl.com> Date: Thu, 17 Nov 2005 16:06:45 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Sun x2100 Server Compatability X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 21:06:48 -0000 Any known issues running FreeBSD/amd64 on a Sun x2100 server? Single opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: http://www.sun.com/servers/entry/x2100/ -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 21:31:05 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 125DE16A41F for ; Thu, 17 Nov 2005 21:31:05 +0000 (GMT) (envelope-from ivo@distributed.net) Received: from mentat.ivo.nu (mentat.ivo.nu [63.149.157.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED94843D67 for ; Thu, 17 Nov 2005 21:31:01 +0000 (GMT) (envelope-from ivo@distributed.net) Received: from mentat.ivo.nu (localhost [127.0.0.1]) by mentat.ivo.nu (Postfix) with ESMTP id 1DEB96EEE6; Thu, 17 Nov 2005 15:31:01 -0600 (CST) Received: from localhost (ivo@localhost) by mentat.ivo.nu (8.12.9p2/8.12.9/Submit) with ESMTP id jAHLUoG3025043; Thu, 17 Nov 2005 15:31:00 -0600 (CST) (envelope-from ivo@distributed.net) X-Authentication-Warning: mentat.ivo.nu: ivo owned process doing -bs Date: Thu, 17 Nov 2005 15:30:50 -0600 (CST) From: Ivo Janssen X-X-Sender: ivo@mentat.ivo.nu To: Bruce Evans In-Reply-To: <20051118071624.V96570@delplex.bde.org> Message-ID: <20051117143605.N364@mentat.ivo.nu> References: <200511171820.jAHIKJef046199@freefall.freebsd.org> <20051118071624.V96570@delplex.bde.org> X-Personal-GUID: 0EA26052-DB50-4609-A9BE-8B282A615B35 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 21:31:05 -0000 I'm sure you've thought about this, but I can see the following improvements to be made: - make dirsize 64bit - add checks to the multiplication operation to make sure it doesn't overflow at runtime - add logic tunefs and newfs so that user cannot set values that will lead to kernel panics - add at the very least huge warnings to the newfs and tunefs manpages, or mention why their usefulness is limited. This particular partition is used for a huge postgres database, which typically use files holding the actual tables. We assumed tuning the fs would gain us some improvements... -Ivo On Fri, 18 Nov 2005, Bruce Evans wrote: > On Thu, 17 Nov 2005, Ivo Janssen wrote: > >> I recreated the filesystem without the huge -f (avg filesize) option, >> which we had initially set to 1Gb: >> # newfs -U -O2 -b 8192 -f 1024 >> # tunefs -e 20480 (10x the default) >> >> With the defaults of avg filesize of 16384, we don't see a crash. I >> then started playing with tunefs. >> Increasing the avg filesize to -f 16777216 (16Mb), we don't see a crash. >> Increasing the avg filesize to -f 33554432 (32Mb), we repro the crash. > > I have had the following comment about this bug (but haven't fixed it) for > many years > > % Index: ffs_alloc.c > % =================================================================== > % RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_alloc.c,v > % retrieving revision 1.121 > % diff -u -2 -r1.121 ffs_alloc.c > % --- ffs_alloc.c 16 Jun 2004 09:47:25 -0000 1.121 > % +++ ffs_alloc.c 28 Oct 2004 15:12:47 -0000 > % @@ -964,4 +991,11 @@ > % minbfree = 1; > % cgsize = fs->fs_fsize * fs->fs_fpg; > % + /* > % + * XXX the following multiplication can overflow, since newfs can > % + * be abused to set fs_avgfilesize and fs_avgfpdir to preposterous > % + * values. For the particular preposterous values of (64M, 16), > % + * the multiplication overflows to 0 and then dirsize = 0 sometimes > % + * causes division by 0. > % + */ > % dirsize = fs->fs_avgfilesize * fs->fs_avgfpdir; > % curdirsize = avgndir ? (cgsize - avgbfree * fs->fs_bsize) / avgndir : > 0; > > This bug is easy to work around by not changing fs->fs_avgfilesize or > fs->fs_avgfpdir. Tuning them has limited useful effects. > > Bruce > > Ivo -- +--------------------------------------------------------------------- | IVO JANSSEN - ivo at ivo.nu - http://ivo.nu/ | finger ivo at finger.ivo.nu for PGP and more info | Part of the world's largest computer: http://www.distributed.net/ From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 23:19:21 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3741716A41F; Thu, 17 Nov 2005 23:19:21 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9963043D46; Thu, 17 Nov 2005 23:19:20 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5F1E9.dip.t-dialin.net [84.165.241.233]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAHNJEMq018942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 18 Nov 2005 00:19:17 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAHNJ8oA010472; Fri, 18 Nov 2005 00:19:08 +0100 (CET) Message-ID: <437D0FF6.20009@deadcafe.de> Date: Fri, 18 Nov 2005 00:19:18 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Nathan Vidican References: <437CF0E5.5030405@wmptl.com> In-Reply-To: <437CF0E5.5030405@wmptl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Cc: amd64@freebsd.org, questions@freebsd.org Subject: Re: Sun x2100 Server Compatability X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 23:19:21 -0000 Nathan Vidican schrieb: > Any known issues running FreeBSD/amd64 on a Sun x2100 server? Single > opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without PS/2 mouse and keyboard ports. So you should look at success reports for this board. In contrast to the Ultra-20, the Broadcom network has been left on the board. It should be much more stable than the NForce ethernet. Daniel From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 23:32:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F60716A420 for ; Thu, 17 Nov 2005 23:32:14 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0167043D46 for ; Thu, 17 Nov 2005 23:32:13 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHNVg2k012578; Fri, 18 Nov 2005 10:31:42 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAHNVe1h007246; Fri, 18 Nov 2005 10:31:40 +1100 Date: Fri, 18 Nov 2005 10:31:39 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Ivo Janssen In-Reply-To: <20051117143605.N364@mentat.ivo.nu> Message-ID: <20051118094317.N96862@delplex.bde.org> References: <200511171820.jAHIKJef046199@freefall.freebsd.org> <20051118071624.V96570@delplex.bde.org> <20051117143605.N364@mentat.ivo.nu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/89202: Kernel crash when accessing filesystem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 23:32:14 -0000 On Thu, 17 Nov 2005, Ivo Janssen wrote: > I'm sure you've thought about this, but I can see the following > improvements to be made: > > - make dirsize 64bit - add checks to the multiplication operation to make > sure it doesn't > overflow at runtime > - add logic tunefs and newfs so that user cannot set values > that will lead to kernel panics > - add at the very least huge warnings to the newfs and tunefs > manpages, or mention why their usefulness is limited. I prefer just adding limits to newfs. newfs already enforces other limits. ffs does very little runtime checking except via fsck, and if it ever does more directly it should start with more important parameters. > This particular partition is used for a huge postgres database, which > typically use files holding the actual tables. We assumed tuning the > fs would gain us some improvements... It would be interesting to know if these parameters actually do give improvements. The came with the dirpref changes, and were initially undocumented except in the log message. The log message still documents them much better than the man page. From the log for ffs_alloc 1.55: % The maxcontigdirs is a maximum number of directories which may be created % without an intervening file creation. I found in my tests that the best % performance occurs when I restrict the number of directories in one cylinder % group such that all its files may be located in the same cylinder group. % There may be some deterioration in performance if all the file inodes % are in the same cylinder group as its containing directory, but their % data partially resides in a different cylinder group. The maxcontigdirs % value is calculated to try to prevent this condition. Since there is % no way to know how many files and directories will be allocated later % I added two optimization parameters in superblock/tunefs. They are: % % int32_t fs_avgfilesize; /* expected average file size */ % int32_t fs_avgfpdir; /* expected # of files per directory */ % % These parameters have reasonable defaults but may be tweeked for special % uses of a filesystem. They are only necessary in rare cases like better % tuning a filesystem being used to store a squid cache. So the usefulness of these parameters is limited to cases where there are largish files with frequent inode updates, where tuning prevents the inodes being in different cylinder groups than the data, and where the reduction in seeks from this is actually significant, i.e., where the cylinder groups aren't so large that seeks within them aren't almost as slow as inter-cg seeks and where the working set consists of only 1 cg. I doubt that there are many such cases. You either have a small working set which is fast enough to access because it is small, or a larger one which will require large seeks to access. Also, settings with the product larger than the size of a cylinder group are not useful; the size of a cg is also int32_t so newfs just needs to check that the size of the produce doesn't exceed the size of a cg. Bruce From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 06:19:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 651A216A41F for ; Fri, 18 Nov 2005 06:19:51 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from smtpclu-1.eunet.yu (smtpclu-1.eunet.yu [194.247.192.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id B430543D49 for ; Fri, 18 Nov 2005 06:19:49 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from mycenae.net (P-15.22.EUnet.yu [213.240.15.22]) by smtpclu-1.eunet.yu (8.13.4/8.13.4) with ESMTP id jAI6Jej8001810 for ; Fri, 18 Nov 2005 07:19:41 +0100 Received: by mycenae.net (Postfix, from userid 1001) id 2E96C60DA; Fri, 18 Nov 2005 07:18:15 +0100 (CET) Date: Fri, 18 Nov 2005 07:18:15 +0100 From: Zoran Kolic To: freebsd-amd64@freebsd.org Message-ID: <20051118061815.GA541@mycenae.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scan: EUnet-AVAS-Milter X-AVAS-Virus-Status: clean X-Spam-Checker: EUnet-AVAS-Milter X-AVAS-Spam-Score: -1.8 X-AVAS-Spam-Symbols: AWL BAYES_05 NO_RELAYS Subject: acpi_perf error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 06:19:51 -0000 This error is from early boot and the line is some 300 times the same: acpi_perf0: invalid _PSS package Sysctl shows that option is: dev.acpi_perf.0.%driver: acpi_perf System is amd64 on nforce3 250, with cpufreq and powerd in rc.conf. In bios I've turned off acpi apic, since on 5.4 I had a lot of errors in acpi implementation. Is there something to put into sysctl? Or comes a time to give apic new chance? Error is just that. Machine boots and works fine. Zoran From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 08:34:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E79B416A41F for ; Fri, 18 Nov 2005 08:34:21 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D2BB44010 for ; Fri, 18 Nov 2005 08:34:21 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ed1hL-0007iL-00 for ; Fri, 18 Nov 2005 09:34:19 +0100 Message-ID: <437D920A.4050805@axis.nl> Date: Fri, 18 Nov 2005 09:34:18 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: Some quick -yet important- questions for AMD-64 as DB server OS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 08:34:22 -0000 Hi all, I have just been asked for my opinion/experiences in setting up a high-end MySQL DB server. Now.... I know some of the main things to look at, but I'm not 100% certain about some of the other things, and based on what I'll say they'll make their hardware decisions as well (and I'll be the one who will then most likely have to tune the OS and DB). Unfortunately they didn't ask me this any time sooner, and if possible they would like to make their hardware choices today or on Monday, so I have precious little time to do the typical Googling and reading on forums etc. Instead, I have a few basic questions, and based on the input I hope I can at least give them a hardware suggestion, and then I'll figure out the details when the machine is in... :) Their questions basically come down to the following, and I hope someone can answer them for me: 1-What would be the most ideal selection of processor(s)? Would that be Dual AMD-64 (Athlon?), Dual Xenon, or Dual core AMD-64? Also, generally spoken what is better: two AMD-64s or one Dual core AMD-64? 2-Does anyone know if the MySQL versions that appear in the amd64 ports are specifically tuned for the AMD-64 architectures, or are they not a whole lot different from the normal -say- i386 ports versions? IOW, just "how 64-bits" is the amd64 version of MySQL? 3-Which MySQL version (generally spoken) nowadays has the edge for performance (under the amd64 version of FBSD), would that be 4.0.x, 4.1.x or is 3.23.x better for speed? 4-Does MySQL have explicit tuning options (e.g. in my.cnf) in order to specify the amount of processors to use, or is that automatically handled by the OS? 5-The people who asked me this are very W*nd*ws minded, and I am not. I told them that IMO it would be far better and easier to tune a MySQL DB under Unix than under W*nd*ws. Can someone please give me a good edge, for this such that indeed they will NOT want to opt for W*nd*ws, or am I totally off-base here and can the W*nd*ws versions of MySQL be equally well tuned as the Unix versions for a high-end (!) DB system? 6-Any pitfalls you may be aware of when using the amd64 FBSD version for a high-end DB server? Thanks heaps in advance, and cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 13:39:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C298C16A41F for ; Fri, 18 Nov 2005 13:39:47 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6619343D45 for ; Fri, 18 Nov 2005 13:39:47 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ed6Sw-00089w-00 for ; Fri, 18 Nov 2005 14:39:46 +0100 Message-ID: <437DD9A0.5060706@axis.nl> Date: Fri, 18 Nov 2005 14:39:44 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 13:39:47 -0000 Hi all, In addition to the questions posed in the message I sent earlier today, I would like to know which SATA hardware controllers incl. RAID 10 support are working well with FreeBSD 5.4 or 6 amd64... Note: the motherboard of the machine that will be used will most likely not have 64-bit PCI slots, but rather only normal 32-bit PCI and PCI-express slots. Can anyone recommend me some good solutions? Also: the motherboard featured a built in Silicon RAID controller. I've previously tried to get FreeBSD to recognise such a controller, but it didn't recognise the RAID array properly and simply identified the drives individually instead of as 1 RAID-1 array. On: http://www.freebsd.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.0-RELEASE it looks like this might work better under v6 but I'm not certain... Does anyone have any suggestions? I know what to do SCSI wise (which is what I have myself), but these guys really want to use SATA.... Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 13:40:28 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF59B16A41F for ; Fri, 18 Nov 2005 13:40:27 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8542543D45 for ; Fri, 18 Nov 2005 13:40:27 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAIDeFZL084699; Fri, 18 Nov 2005 08:40:15 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <437DD9BF.30102@wmptl.com> Date: Fri, 18 Nov 2005 08:40:15 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <437D920A.4050805@axis.nl> In-Reply-To: <437D920A.4050805@axis.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Some quick -yet important- questions for AMD-64 as DB server OS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 13:40:28 -0000 Olaf Greve wrote: > Hi all, > > I have just been asked for my opinion/experiences in setting up a > high-end MySQL DB server. Now.... I know some of the main things to look > at, but I'm not 100% certain about some of the other things, and based > on what I'll say they'll make their hardware decisions as well (and I'll > be the one who will then most likely have to tune the OS and DB). > > Unfortunately they didn't ask me this any time sooner, and if possible > they would like to make their hardware choices today or on Monday, so I > have precious little time to do the typical Googling and reading on > forums etc. > > Instead, I have a few basic questions, and based on the input I hope I > can at least give them a hardware suggestion, and then I'll figure out > the details when the machine is in... :) > > Their questions basically come down to the following, and I hope someone > can answer them for me: > > 1-What would be the most ideal selection of processor(s)? Would that be > Dual AMD-64 (Athlon?), Dual Xenon, or Dual core AMD-64? Also, generally > spoken what is better: two AMD-64s or one Dual core AMD-64? > go with AMD Opteron, hands-down better choice. Single or dual cpu's with single or dual cores, your choice... personally, considering the price I'd go with dual (single core) cpus, like two AMD Opteron 246 cpu's. Also, I'd reccomend using ECC registered memory if cost is not the ultimate issue. > 2-Does anyone know if the MySQL versions that appear in the amd64 ports > are specifically tuned for the AMD-64 architectures, or are they not a > whole lot different from the normal -say- i386 ports versions? IOW, just > "how 64-bits" is the amd64 version of MySQL? > Not entirely sure, built mysql/64 from the source myself - will say it runs GREAT so far. > 3-Which MySQL version (generally spoken) nowadays has the edge for > performance (under the amd64 version of FBSD), would that be 4.0.x, > 4.1.x or is 3.23.x better for speed? > Not have any definitive benchmarks, but will vouch for the stability. Hardware wise, the AMD Opteron runs faster than most anything else in it's price-range anyhow - on that alone one can assume better results. > 4-Does MySQL have explicit tuning options (e.g. in my.cnf) in order to > specify the amount of processors to use, or is that automatically > handled by the OS? > Yes - check http://www.mysql.com/ > 5-The people who asked me this are very W*nd*ws minded, and I am not. I > told them that IMO it would be far better and easier to tune a MySQL DB > under Unix than under W*nd*ws. Can someone please give me a good edge, > for this such that indeed they will NOT want to opt for W*nd*ws, or am I > totally off-base here and can the W*nd*ws versions of MySQL be equally > well tuned as the Unix versions for a high-end (!) DB system? > Don't know much myself about tuning/performance on windows. Do know however, that administation on windows for mysql is a pain. Lack of Perl, lack of a shell, etc make the scripts that come with myself virtually useless. You can always consider the downfall to the windows O/S wasting cpu/ram resources on running a full GUI that you don't need too. > 6-Any pitfalls you may be aware of when using the amd64 FBSD version for > a high-end DB server? > None I've encountered, been running for a year now almost with freebsd/amd64 and mysql - using transactional innodb tables. > Thanks heaps in advance, and cheers! > Olafo > _______________________________________________ > 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" > > hope it helps... -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 13:47:38 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 415F116A41F for ; Fri, 18 Nov 2005 13:47:38 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D0643D46 for ; Fri, 18 Nov 2005 13:47:37 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAIDlZwR084887; Fri, 18 Nov 2005 08:47:35 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <437DDB77.9000001@wmptl.com> Date: Fri, 18 Nov 2005 08:47:35 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <437DD9A0.5060706@axis.nl> In-Reply-To: <437DD9A0.5060706@axis.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 13:47:38 -0000 Olaf Greve wrote: > Hi all, > > In addition to the questions posed in the message I sent earlier today, > I would like to know which SATA hardware controllers incl. RAID 10 > support are working well with FreeBSD 5.4 or 6 amd64... > > Note: the motherboard of the machine that will be used will most likely > not have 64-bit PCI slots, but rather only normal 32-bit PCI and > PCI-express slots. > > Can anyone recommend me some good solutions? > > Also: the motherboard featured a built in Silicon RAID controller. I've > previously tried to get FreeBSD to recognise such a controller, but it > didn't recognise the RAID array properly and simply identified the > drives individually instead of as 1 RAID-1 array. > > On: > http://www.freebsd.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.0-RELEASE > > it looks like this might work better under v6 but I'm not certain... > > Does anyone have any suggestions? I know what to do SCSI wise (which is > what I have myself), but these guys really want to use SATA.... > > Cheers! > Olafo > _______________________________________________ > 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" > > HANDS-DOWN, the 3-Ware Escalade 9000 Series... rock solid performance, stability, they support the FreeBSD community 'officially', AND they won't cost you an arm and a leg either. We're running Dual AMD Opteron 246's plugged into a MSI K8D-Master-FA4R, has room for 24GB ECC registered memory, on-board S-ATA raid (which we don't use), dual on-board Gig ethernet, on-board video/usb1.1. We're using 3Ware Escalade 9000-series 8-port controllers with Western Digital RAID Edition 7200RPM 250GB S-ATA drives... knock-on-woood, these systems have been GREAT for us, running LDAP directories - including central authentication for all unix boxen via pam_ldap/nss_ldap and windows domain control via samba using the same user database. Also running apache with mod_perl and Apache::DBI attached to various databases run from mysql. Performance has been great, and stability even better, all hardware was supported and no weird kwirks required to get system up and running. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 13:58:27 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C73C416A420 for ; Fri, 18 Nov 2005 13:58:27 +0000 (GMT) (envelope-from ray@redshift.com) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B174D43D49 for ; Fri, 18 Nov 2005 13:58:26 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id F0C8497BFA; Fri, 18 Nov 2005 05:58:25 -0800 (PST) Message-Id: <3.0.1.32.20051118055823.00d655b8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 18 Nov 2005 05:58:23 -0800 To: Nathan Vidican ,Olaf Greve From: ray@redshift.com In-Reply-To: <437DD9BF.30102@wmptl.com> References: <437D920A.4050805@axis.nl> <437D920A.4050805@axis.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: Some quick -yet important- questions for AMD-64 as DB server OS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 13:58:27 -0000 At 08:40 AM 11/18/2005 -0500, Nathan Vidican wrote: | Olaf Greve wrote: | > Hi all, | > | > I have just been asked for my opinion/experiences in setting up a | > high-end MySQL DB server. Now.... I know some of the main things to look | > at, but I'm not 100% certain about some of the other things, and based | > on what I'll say they'll make their hardware decisions as well (and I'll | > be the one who will then most likely have to tune the OS and DB). | > | > Unfortunately they didn't ask me this any time sooner, and if possible | > they would like to make their hardware choices today or on Monday, so I | > have precious little time to do the typical Googling and reading on | > forums etc. | > | > Instead, I have a few basic questions, and based on the input I hope I | > can at least give them a hardware suggestion, and then I'll figure out | > the details when the machine is in... :) | > | > Their questions basically come down to the following, and I hope someone | > can answer them for me: | > | > 1-What would be the most ideal selection of processor(s)? Would that be | > Dual AMD-64 (Athlon?), Dual Xenon, or Dual core AMD-64? Also, generally | > spoken what is better: two AMD-64s or one Dual core AMD-64? | > | go with AMD Opteron, hands-down better choice. Single or dual cpu's with single | or dual cores, your choice... personally, considering the price I'd go with dual | (single core) cpus, like two AMD Opteron 246 cpu's. Also, I'd reccomend using | ECC registered memory if cost is not the ultimate issue. | | > 2-Does anyone know if the MySQL versions that appear in the amd64 ports | > are specifically tuned for the AMD-64 architectures, or are they not a | > whole lot different from the normal -say- i386 ports versions? IOW, just | > "how 64-bits" is the amd64 version of MySQL? | > | | Not entirely sure, built mysql/64 from the source myself - will say it runs | GREAT so far. | | > 3-Which MySQL version (generally spoken) nowadays has the edge for | > performance (under the amd64 version of FBSD), would that be 4.0.x, | > 4.1.x or is 3.23.x better for speed? | > | | Not have any definitive benchmarks, but will vouch for the stability. Hardware | wise, the AMD Opteron runs faster than most anything else in it's price-range | anyhow - on that alone one can assume better results. | | > 4-Does MySQL have explicit tuning options (e.g. in my.cnf) in order to | > specify the amount of processors to use, or is that automatically | > handled by the OS? | > | | Yes - check http://www.mysql.com/ | | > 5-The people who asked me this are very W*nd*ws minded, and I am not. I | > told them that IMO it would be far better and easier to tune a MySQL DB | > under Unix than under W*nd*ws. Can someone please give me a good edge, | > for this such that indeed they will NOT want to opt for W*nd*ws, or am I | > totally off-base here and can the W*nd*ws versions of MySQL be equally | > well tuned as the Unix versions for a high-end (!) DB system? | > | Don't know much myself about tuning/performance on windows. Do know however, | that administation on windows for mysql is a pain. Lack of Perl, lack of a | shell, etc make the scripts that come with myself virtually useless. You can | always consider the downfall to the windows O/S wasting cpu/ram resources on | running a full GUI that you don't need too. | | > 6-Any pitfalls you may be aware of when using the amd64 FBSD version for | > a high-end DB server? | > | None I've encountered, been running for a year now almost with freebsd/amd64 and | mysql - using transactional innodb tables. | | > Thanks heaps in advance, and cheers! | > Olafo | > _______________________________________________ | > 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" | > | > | | hope it helps... For production database servers, I use Dual AMD 246 machines, running on Tyan S2881 motherboards. The AMD CPU's are much faster than the Xeon machines in my benchmarking tests. You can also gain considerable speed by using a properly configured RAID 1+0 on the database server. I personally use the 3Ware RAID cards (specifically the 9500S line). With 4 or 8 SATA 10K RPM drives on it, it runs really well/fast under FreeBSD 5.4 AMD64. Just make sure to compile the SMP kernel :) If you are interested, I have some benchmarks I've done that I can send along. I've always used MySQL 4.1.xx (built from source) on the machines with very good luck - all with Innodb tables and then interfaced via the with_mysql lib in PHP. Works like a dream. As far as trying to use Windows over FreeBSD for a high end database server, that sounds about as fun as firing a nail gun through the top of your foot. Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 14:07:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6143316A41F for ; Fri, 18 Nov 2005 14:07:23 +0000 (GMT) (envelope-from ray@redshift.com) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B8C843D45 for ; Fri, 18 Nov 2005 14:07:23 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id 0D4F2979C9; Fri, 18 Nov 2005 06:07:22 -0800 (PST) Message-Id: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 18 Nov 2005 06:07:18 -0800 To: Olaf Greve ,freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <437DD9A0.5060706@axis.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 14:07:23 -0000 At 02:39 PM 11/18/2005 +0100, Olaf Greve wrote: | Hi all, | | In addition to the questions posed in the message I sent earlier today, | I would like to know which SATA hardware controllers incl. RAID 10 | support are working well with FreeBSD 5.4 or 6 amd64... | | Note: the motherboard of the machine that will be used will most likely | not have 64-bit PCI slots, but rather only normal 32-bit PCI and | PCI-express slots. | | Can anyone recommend me some good solutions? | | Also: the motherboard featured a built in Silicon RAID controller. I've | previously tried to get FreeBSD to recognise such a controller, but it | didn't recognise the RAID array properly and simply identified the | drives individually instead of as 1 RAID-1 array. | | On: | http://www.freebsd.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+6.0-RELEASE | it looks like this might work better under v6 but I'm not certain... | | Does anyone have any suggestions? I know what to do SCSI wise (which is | what I have myself), but these guys really want to use SATA.... | | Cheers! | Olafo | Hi Olafo, 3Ware is very well supported under FreeBSD. I've used several of their RAID cards with very good luck. The one I like the best so far is the 9500S-12 (or the 9500S-8 is good also). It works really well with 4 or 8 WD 36 or 74GB Raptor drives and the performance is outstanding. FreeBSD supports this RAID card in the kernel, so you don't have to do anything crazy. Basically, you just install the card, boot into the RAID bios using Alt+3 and then you follow a simple menu to build whatever type of raid you want. Once that's done, FreeBSD installs on the RAID volume like it was a normal old single SATA drive. Of course, for maintenance, FreeBSD can still access the individual drives in the raid - but for the most part the day to day OS sees the RAID volume just like a single drive. I've had far better luck using SATA over SCSI in the recent couple of years. We have several machines setup using FreeBSD and 3Ware RAID 0+1 that routinely run with no problems and uptimes of 200 to 300 days at a time. Hope that helps. Feel free to e-mail me directly with any questions if you wish. Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 14:29:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99ED816A41F for ; Fri, 18 Nov 2005 14:29:25 +0000 (GMT) (envelope-from dan@langille.org) Received: from m21.unixathome.org (m21.unixathome.org [205.150.199.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39CAF43D45 for ; Fri, 18 Nov 2005 14:29:25 +0000 (GMT) (envelope-from dan@langille.org) Received: from localhost (localhost [205.150.199.217]) by m21.unixathome.org (Postfix) with ESMTP id BEDC8BF58; Fri, 18 Nov 2005 09:29:23 -0500 (EST) Received: from m21.unixathome.org ([205.150.199.217]) by localhost (m21.unixathome.org [205.150.199.217]) (amavisd-new, port 10024) with ESMTP id 10154-06; Fri, 18 Nov 2005 09:29:20 -0500 (EST) Received: from bast.unixathome.org (bast.unixathome.org [70.26.229.230]) by m21.unixathome.org (Postfix) with ESMTP id B77AEBF57; Fri, 18 Nov 2005 09:29:20 -0500 (EST) Received: from wocker (wocker.unixathome.org [10.55.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 45FCA3D3B; Fri, 18 Nov 2005 09:29:20 -0500 (EST) From: "Dan Langille" To: Olaf Greve Date: Fri, 18 Nov 2005 09:29:19 -0500 MIME-Version: 1.0 Message-ID: <437D9EEF.13094.2B9BB220@localhost> Priority: normal In-reply-to: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> References: <437DD9A0.5060706@axis.nl> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at unixathome.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 14:29:25 -0000 On 18 Nov 2005 at 6:07, ray@redshift.com wrote: > 3Ware is very well supported under FreeBSD. I've used several of their RAID > cards with very good luck. I've used only their 7006-2 cards to do RAID-1, under FreeBSD 4, FreeBSD 6, and Windows XP. No concerns. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 14:42:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C598916A41F for ; Fri, 18 Nov 2005 14:42:35 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3582C43D45 for ; Fri, 18 Nov 2005 14:42:35 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ed7Rf-0000GX-00; Fri, 18 Nov 2005 15:42:31 +0100 Message-ID: <437DE855.4010006@axis.nl> Date: Fri, 18 Nov 2005 15:42:29 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 14:42:35 -0000 Hi Ray, Nathan (and others via cc per list), First off: thanks a lot for your answers, they're definitly very helpful! I have forwarded the messages to the person who'll have to make the final call for ordering the hardware. I'm trying to get him towards ordering a 3Ware-Escalade 9500S-4 RAID controller (or possibly the -8 or -12 one). One thing which is of importance is that their budget may not allow for a really high end server, so they may have to decide to buy a semi high-end server. This then may result in them taking Athlons instead of Opterons, and it may result in a MoBo with 32-bits PCI slots instead of 64-bits PCI slots. Judging from the pictures of the 9500S it has a 64-bits PCI slot, but it looks like it might be compatible with the 32-bits slots as well (at a performance penalty, of course). Would you happen to know if that's indeed possible, or whether they'd better choose a different RAID controller? Regarding the MySQL versions and their settings: tnx for giving me enough comfort to indeed give heavy preference for the FreeBSD amd64 version. Will (source) installing the version from the ports do, or do you mean something else when you say that you compiled MySQL yourself? Regarding the benchmark results: I'd love to receive them. Can you perhaps send them off-list to me? Regarding W*nd*ws vs. FreeBSD: I love your remark; I wonder if the person I forwarded it to can laugh as loudly about it as I did. :D Finally regarding SCSI vs. SATA: > I've had far better luck using SATA over SCSI in the recent couple of years. > We have several machines setup using FreeBSD and 3Ware RAID 0+1 that routinely > run with no problems and uptimes of 200 to 300 days at a time. Very interesting to know. At present, I myself have a 754 socket AMD Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB drives attached to it in RAID-10 mode. So far it works a charm (though I too had to effectively downgrade it to U160 due to the lack of 64-bits PCI slots, grrr). I hope it'll keep performing well (so far uptimes in the order magnitude you mention have been working fine for me as well on SCSI - Adaptec 2100S RAID set-ups in my (now) fall-back server, and ever after installing the AMD-64 one 34 days ago I haven't had to restart it so far)... Yet, it'll be interesting to keep an eye on the SATA RAID performance and costs. With such uptimes SATA will surely become (if it hasn't already become so, that is) a very good alternative for SCSI. Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 14:56:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D7916A41F for ; Fri, 18 Nov 2005 14:56:48 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A71643D69 for ; Fri, 18 Nov 2005 14:56:38 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAIEua9T087359; Fri, 18 Nov 2005 09:56:36 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <437DEBA3.7060308@wmptl.com> Date: Fri, 18 Nov 2005 09:56:35 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <437DE855.4010006@axis.nl> In-Reply-To: <437DE855.4010006@axis.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 14:56:48 -0000 Olaf Greve wrote: > Hi Ray, Nathan (and others via cc per list), > > First off: thanks a lot for your answers, they're definitly very helpful! > > I have forwarded the messages to the person who'll have to make the > final call for ordering the hardware. > > I'm trying to get him towards ordering a 3Ware-Escalade 9500S-4 RAID > controller (or possibly the -8 or -12 one). > I have a 9500S-4 here, with 5 250GB RAID edition drives attached to it. - Works VERY well, have never had any issues with it at all, running RAID 5 array on it. > One thing which is of importance is that their budget may not allow for > a really high end server, so they may have to decide to buy a semi > high-end server. This then may result in them taking Athlons instead of > Opterons, and it may result in a MoBo with 32-bits PCI slots instead of > 64-bits PCI slots. Judging from the pictures of the 9500S it has a > 64-bits PCI slot, but it looks like it might be compatible with the > 32-bits slots as well (at a performance penalty, of course). > Would you happen to know if that's indeed possible, or whether they'd > better choose a different RAID controller? > 3Ware cards all work 64/32-bit PCI slots. Also... Cheap Opteron's can be had, even new hardware; look at Sun x2100's, starting at like $750 complete... or eBay a clone ;) You should be able to put together what you're looking for under $1000, plus the cost of your disks.... you didn't really mention what kinda load you'll be anticipating, connections/bandwidth capabilities/etc... but if you'd like to provide more specific requirements, (ie: 70 clients connecting from Windows machines to SQL for entry/updates, plus 3 webservers querying average of say 5-10 users each...) then we (the list) may better be able to guide you. > Regarding the MySQL versions and their settings: tnx for giving me > enough comfort to indeed give heavy preference for the FreeBSD amd64 > version. Will (source) installing the version from the ports do, or do > you mean something else when you say that you compiled MySQL yourself? > Personally, looking into Sun's new x2100 for a pure mysql server setup over here, (cost $745 single Opteron 146/1GB ecc/80gb s-ata)... it'll be an upgrade to a dual PIII proliant box doing the job right now, (10800 connections per day, cascading updates accross 4 tables/180 fields of data about 3 times every 8 seconds). Currently mysql takes about 35-40% CPU utilization; to further add to your 'windows vs freebsd' - if used solely for mysql, this same machine couldn't handle this load under windows - period. > Regarding the benchmark results: I'd love to receive them. Can you > perhaps send them off-list to me? > > Regarding W*nd*ws vs. FreeBSD: I love your remark; I wonder if the > person I forwarded it to can laugh as loudly about it as I did. :D > > Finally regarding SCSI vs. SATA: > >> I've had far better luck using SATA over SCSI in the recent couple >> of years. >> We have several machines setup using FreeBSD and 3Ware RAID 0+1 that >> routinely >> run with no problems and uptimes of 200 to 300 days at a time. > Hands down, SCSI is a stable and solid performer... but compare cost per meg, both in terms of storage amounts, and bandwidth - and S-ATA takes it. > > Very interesting to know. At present, I myself have a 754 socket AMD > Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an > Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB > drives attached to it in RAID-10 mode. So far it works a charm (though I > too had to effectively downgrade it to U160 due to the lack of 64-bits > PCI slots, grrr). I hope it'll keep performing well (so far uptimes in > the order magnitude you mention have been working fine for me as well on > SCSI - Adaptec 2100S RAID set-ups in my (now) fall-back server, and ever > after installing the AMD-64 one 34 days ago I haven't had to restart it > so far)... > > Yet, it'll be interesting to keep an eye on the SATA RAID performance > and costs. With such uptimes SATA will surely become (if it hasn't > already become so, that is) a very good alternative for SCSI. > > Cheers! > Olafo > > -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 15:11:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74DB816A41F for ; Fri, 18 Nov 2005 15:11:36 +0000 (GMT) (envelope-from ray@redshift.com) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA3D743D49 for ; Fri, 18 Nov 2005 15:11:35 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id EB56D97C0A; Fri, 18 Nov 2005 07:11:34 -0800 (PST) Message-Id: <3.0.1.32.20051118071132.00d655b8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 18 Nov 2005 07:11:32 -0800 To: Olaf Greve From: ray@redshift.com In-Reply-To: <437DE855.4010006@axis.nl> References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 15:11:36 -0000 | I'm trying to get him towards ordering a 3Ware-Escalade 9500S-4 RAID | controller (or possibly the -8 or -12 one). The 9500S line is a good choice. You can also sometimes find them used/NIB on ebay at a fair price ($300 to $400). BTW, in my testing, you don't get much additional performance from having 8 vs 4 drives (if you want to save costs). Although you do get more space :) | One thing which is of importance is that their budget may not allow for | a really high end server, so they may have to decide to buy a semi | high-end server. This then may result in them taking Athlons instead of | Opterons, and it may result in a MoBo with 32-bits PCI slots instead of | 64-bits PCI slots. Judging from the pictures of the 9500S it has a | 64-bits PCI slot, but it looks like it might be compatible with the | 32-bits slots as well (at a performance penalty, of course). | Would you happen to know if that's indeed possible, or whether they'd | better choose a different RAID controller? You'd have to check the 3ware website to be sure, but a lot of times those cards are backwards compatible with the 32 bit slots. I just checked the manuals I have for the 9000 series and it says 3Ware cards will run properly in any PCI or PCI-X slot, but you'll get better performance in a 64 bit slot - here is the text from the manual: -------------------------------------------------------- Selecting the Slot in Which to Install the Controller Consider these factors when deciding on the slot in which to insert the controller: .. While the 3ware RAID Controller runs properly in any PCI or PCI-X slot, not all slots give equal performance due to the architecture of the PCI bus. These slots typically give the best performance: .. Slots closest to the Accelerated Graphics Port (AGP), if included. .. 64-bit PCI slots Although the controller fits in both 32-bit and 64-bit PCI or PCI-X slots with 5V as well as with 3.3V, install it in a 64- bit slot to take full advantage of the controller’s performance. -------------------------------------------------------- | Regarding the MySQL versions and their settings: tnx for giving me | enough comfort to indeed give heavy preference for the FreeBSD amd64 | version. Will (source) installing the version from the ports do, or do | you mean something else when you say that you compiled MySQL yourself? from the tar.gz off the mysql site. E-mail me privately for a full run down on the install I use, but here is the basic idea: as root do this: ------------------------------------------------------ tar -xzf mysql-4.1.15.tar.gz cd mysql-4.1.15 pw groupadd mysql adduser {user you are creating is mysql} CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static --without-debug make make install make clean ln -s /usr/local/mysql/share/mysql/mysql.server /usr/local/bin/mysql.server ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql ln -s /usr/local/mysql/bin/mysqld_safe /usr/local/bin/mysqld_safe ------------------------------------------------------ There is more too it, but that's the basic idea. Check the readme/install files with the tar.gz - I will also send you my entire run down privately in a second. | Regarding the benchmark results: I'd love to receive them. Can you | perhaps send them off-list to me? Actually, I forgot that I put them on-line a while back. Here you go: http://www.redshift.com/~ray/mysql_bench/ | Regarding W*nd*ws vs. FreeBSD: I love your remark; I wonder if the | person I forwarded it to can laugh as loudly about it as I did. :D :) | Finally regarding SCSI vs. SATA: | >I've had far better luck using SATA over SCSI in the recent couple of years. | > We have several machines setup using FreeBSD and 3Ware RAID 0+1 that | > routinely run with no problems and uptimes of 200 to 300 days at a time. | | Very interesting to know. At present, I myself have a 754 socket AMD | Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an | Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB | drives attached to it in RAID-10 mode. So far it works a charm (though I | too had to effectively downgrade it to U160 due to the lack of 64-bits | PCI slots, grrr). I hope it'll keep performing well (so far uptimes in | the order magnitude you mention have been working fine for me as well on | SCSI - Adaptec 2100S RAID set-ups in my (now) fall-back server, and ever | after installing the AMD-64 one 34 days ago I haven't had to restart it | so far)... The file will send you with the benchmarks includes the PHP files to run the benchmarks, so if you feel like adding your #'s to the mix, just let me know. Or feel free to run the code and send me the results. I'll e-mail you privately in a second here. | Yet, it'll be interesting to keep an eye on the SATA RAID performance | and costs. With such uptimes SATA will surely become (if it hasn't | already become so, that is) a very good alternative for SCSI. SATA is built on top of SCSI I think (not sure exactly how it all sorts out, but I think some of the SATA stuff is tied into some of the SCSI stuff in the kernel or something). If I recall correctly, you have to leave some SCSI drivers in the kernel when you setup SATA on FreeBSD. I may be off, but I think that's what we had to do. Maybe someone more familiar with the kernel stuff can comment further on that count. I will e-mail you the install run down in a sec. Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 16:34:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D5DB16A41F for ; Fri, 18 Nov 2005 16:34:20 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7BB443D46 for ; Fri, 18 Nov 2005 16:34:19 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id jAIGYMMx014568; Fri, 18 Nov 2005 17:34:22 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.1/Submit) id jAIGYM4t014567; Fri, 18 Nov 2005 17:34:22 +0100 (CET) (envelope-from ftigeot) Date: Fri, 18 Nov 2005 17:34:22 +0100 From: Francois Tigeot To: Olaf Greve Message-ID: <20051118163422.GA14537@aoi.wolfpond.org> References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <437DE855.4010006@axis.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <437DE855.4010006@axis.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 16:34:20 -0000 On Fri, Nov 18, 2005 at 03:42:29PM +0100, Olaf Greve wrote: [...] > Judging from the pictures of the 9500S it has a > 64-bits PCI slot, but it looks like it might be compatible with the > 32-bits slots as well (at a performance penalty, of course). > Would you happen to know if that's indeed possible, or whether they'd > better choose a different RAID controller? It is possible, and it works nicely. I built such a box no later than two weeks ago with an Asus A8V/Athlon 64 combo. So far, so good. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 16:49:52 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DB9716A41F for ; Fri, 18 Nov 2005 16:49:52 +0000 (GMT) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [83.136.81.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 876D343D45 for ; Fri, 18 Nov 2005 16:49:51 +0000 (GMT) (envelope-from lehmann@ans-netz.de) Received: (qmail 54398 invoked by uid 89); 18 Nov 2005 16:49:21 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (83.136.81.185) by avocado.salatschuessel.net with SMTP; 18 Nov 2005 16:49:21 -0000 Date: Fri, 18 Nov 2005 17:49:48 +0100 From: Oliver Lehmann To: Olaf Greve Message-Id: <20051118174948.39100812.lehmann@ans-netz.de> In-Reply-To: <437DE855.4010006@axis.nl> References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <437DE855.4010006@axis.nl> X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.6; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 16:49:52 -0000 Olaf Greve wrote: > Judging from the pictures of the 9500S it has a > 64-bits PCI slot, but it looks like it might be compatible with the > 32-bits slots as well They are working in a 32Bit slot without problems. I've running a 9500S-4LP in a 32bit slot and it works like a charm with a 4*250GB RAID-5+BBU;) 3ware device driver for 9000 series storage controllers, version: 3.60.00.017 twa0: <3ware 9000 series Storage Controller> port 0x3400-0x34ff mem 0xf4102800-0xf41028ff,0xf4800000-0xf4ffffff irq 17 at device 13.0 on pci0 twa0: [FAST] twa0: DEBUG: (0x04: 0x0054): Charge termination voltage is at high level: 0x0 twa0: INFO: (0x15: 0x1300): Controller details:: 4 ports, Firmware FE9X 2.08.00.005, BIOS BE9X 2.03.01.052 da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 100.000MB/s transfers da0: 715224MB (1464778752 512 byte sectors: 255H 63S/T 91178C) -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 18 19:00:21 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F94616A420 for ; Fri, 18 Nov 2005 19:00:21 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06BE643D5C for ; Fri, 18 Nov 2005 19:00:19 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAIJ0EJI096174; Fri, 18 Nov 2005 14:00:15 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <437E24BE.90008@wmptl.com> Date: Fri, 18 Nov 2005 14:00:14 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <3.0.1.32.20051118071132.00d655b8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051118071132.00d655b8@pop.redshift.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 0.6 () J_CHICKENPOX_33 X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 19:00:21 -0000 ray@redshift.com wrote: > | I'm trying to get him towards ordering a 3Ware-Escalade 9500S-4 RAID > | controller (or possibly the -8 or -12 one). > > The 9500S line is a good choice. You can also sometimes find them used/NIB on > ebay at a fair price ($300 to $400). BTW, in my testing, you don't get much > additional performance from having 8 vs 4 drives (if you want to save costs). > Although you do get more space :) > > | One thing which is of importance is that their budget may not allow for > | a really high end server, so they may have to decide to buy a semi > | high-end server. This then may result in them taking Athlons instead of > | Opterons, and it may result in a MoBo with 32-bits PCI slots instead of > | 64-bits PCI slots. Judging from the pictures of the 9500S it has a > | 64-bits PCI slot, but it looks like it might be compatible with the > | 32-bits slots as well (at a performance penalty, of course). > | Would you happen to know if that's indeed possible, or whether they'd > | better choose a different RAID controller? > > You'd have to check the 3ware website to be sure, but a lot of times those cards > are backwards compatible with the 32 bit slots. I just checked the manuals I > have for the 9000 series and it says 3Ware cards will run properly in any PCI or > PCI-X slot, but you'll get better performance in a 64 bit slot - here is the > text from the manual: > > -------------------------------------------------------- > Selecting the Slot in Which to Install the Controller > Consider these factors when deciding on the slot in which to insert the controller: > .. While the 3ware RAID Controller runs properly in any PCI or > PCI-X slot, not all slots give equal performance due to the > architecture of the PCI bus. > These slots typically give the best performance: > .. Slots closest to the Accelerated Graphics Port (AGP), if > included. > .. 64-bit PCI slots > Although the controller fits in both 32-bit and 64-bit PCI or > PCI-X slots with 5V as well as with 3.3V, install it in a 64- > bit slot to take full advantage of the controller’s > performance. > -------------------------------------------------------- > > | Regarding the MySQL versions and their settings: tnx for giving me > | enough comfort to indeed give heavy preference for the FreeBSD amd64 > | version. Will (source) installing the version from the ports do, or do > | you mean something else when you say that you compiled MySQL yourself? > > from the tar.gz off the mysql site. E-mail me privately for a full run down on > the install I use, but here is the basic idea: > > as root do this: > ------------------------------------------------------ > tar -xzf mysql-4.1.15.tar.gz > cd mysql-4.1.15 > pw groupadd mysql > adduser {user you are creating is mysql} > > CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions > -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler > --with-mysqld-ldflags=-all-static --without-debug > > make > make install > make clean > > ln -s /usr/local/mysql/share/mysql/mysql.server /usr/local/bin/mysql.server > ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql > ln -s /usr/local/mysql/bin/mysqld_safe /usr/local/bin/mysqld_safe > ------------------------------------------------------ > > There is more too it, but that's the basic idea. Check the readme/install files > with the tar.gz - I will also send you my entire run down privately in a second. > > | Regarding the benchmark results: I'd love to receive them. Can you > | perhaps send them off-list to me? > > Actually, I forgot that I put them on-line a while back. Here you go: > > http://www.redshift.com/~ray/mysql_bench/ > > | Regarding W*nd*ws vs. FreeBSD: I love your remark; I wonder if the > | person I forwarded it to can laugh as loudly about it as I did. :D > > :) > > | Finally regarding SCSI vs. SATA: > | >I've had far better luck using SATA over SCSI in the recent couple of years. > | > We have several machines setup using FreeBSD and 3Ware RAID 0+1 that > | > routinely run with no problems and uptimes of 200 to 300 days at a time. > | > | Very interesting to know. At present, I myself have a 754 socket AMD > | Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an > | Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB > | drives attached to it in RAID-10 mode. So far it works a charm (though I > | too had to effectively downgrade it to U160 due to the lack of 64-bits > | PCI slots, grrr). I hope it'll keep performing well (so far uptimes in > | the order magnitude you mention have been working fine for me as well on > | SCSI - Adaptec 2100S RAID set-ups in my (now) fall-back server, and ever > | after installing the AMD-64 one 34 days ago I haven't had to restart it > | so far)... > > The file will send you with the benchmarks includes the PHP files to run the > benchmarks, so if you feel like adding your #'s to the mix, just let me know. > Or feel free to run the code and send me the results. I'll e-mail you privately > in a second here. > > | Yet, it'll be interesting to keep an eye on the SATA RAID performance > | and costs. With such uptimes SATA will surely become (if it hasn't > | already become so, that is) a very good alternative for SCSI. > > SATA is built on top of SCSI I think (not sure exactly how it all sorts out, but > I think some of the SATA stuff is tied into some of the SCSI stuff in the kernel > or something). If I recall correctly, you have to leave some SCSI drivers in > the kernel when you setup SATA on FreeBSD. I may be off, but I think that's > what we had to do. Maybe someone more familiar with the kernel stuff can > comment further on that count. > > I will e-mail you the install run down in a sec. > > Ray > > > Actually, that's quite wrong. S-ATA is ATA, not SCSI-like... S-ATA in fact is almost the same as ATA (EIDE) from a code/kernel standpoint. The physical hardware interface differs slightly and offers greater stability and performance than standard ATA (EIDE). However, you are correct if not confusing when you state that you must 'leave some SCSI drivers in the kernel', this is not for ATA so much as it is for the use of the RAID card. If you're using plain old S-ATA, no SCSI disk devices are required, but with the 3Ware Escalades, you will need: device scbus device da device twa Anyhow, long story short - the only 'real' difference from S-ATA to P-ATA (Parallel ATA aka 'ATA' or 'EIDE'), is the interface - the drive internals and functionality are the same - but both differ from SCSI. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 19 00:10:30 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 833C916A41F for ; Sat, 19 Nov 2005 00:10:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0309543D46 for ; Sat, 19 Nov 2005 00:10:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAJ0ARo9012679 for ; Sat, 19 Nov 2005 00:10:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAJ0ARm9012678; Sat, 19 Nov 2005 00:10:27 GMT (envelope-from gnats) Resent-Date: Sat, 19 Nov 2005 00:10:27 GMT Resent-Message-Id: <200511190010.jAJ0ARm9012678@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, infofarmer@gmail.com Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CA2716A41F for ; Sat, 19 Nov 2005 00:04:34 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from proxy.gubkin.ru (proxy.gubkin.ru [193.233.78.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7D3743D45 for ; Sat, 19 Nov 2005 00:04:33 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from proxy.gubkin.ru (localhost [127.0.0.1]) by proxy.gubkin.ru (8.13.4/8.13.4) with ESMTP id jAJ04TZN068039 for ; Sat, 19 Nov 2005 03:04:29 +0300 (MSK) (envelope-from infofarmer@gmail.com) Received: (from sat@localhost) by proxy.gubkin.ru (8.13.4/8.13.3/Submit) id jAJ04SvS068038; Sat, 19 Nov 2005 03:04:28 +0300 (MSK) (envelope-from infofarmer@gmail.com) Message-Id: <200511190004.jAJ04SvS068038@proxy.gubkin.ru> Date: Sat, 19 Nov 2005 03:04:28 +0300 (MSK) From: infofarmer@gmail.com To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/89261: IPSec always causes panics on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: infofarmer@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 00:10:30 -0000 >Number: 89261 >Category: amd64 >Synopsis: IPSec always causes panics on amd64 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 19 00:10:27 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Andrew Pantyukhin >Release: FreeBSD 6.0-RELEASE i386 >Organization: >Environment: This bug has been reproduced on 5.4-RELEASE, 6.0-RELEASE and 6.0-STABLE. >Description: IPSec key management (setkey) always causes kernel panics >How-To-Repeat: Add "options IPSEC" to GENERIC kernel and run "setkey -D" Adding other IPSEC options does not help at all. >Fix: Sorry about the acid formatting. I've done this with script(1) --- ipsec.1.debug begins here --- Script started on Sat Nov 19 02:43:19 2005 satsmb# kgdb kernel.debug /var/crsash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xffffffff804c5d4c stack pointer = 0x10:0xffffffff967808a0 frame pointer = 0x10:0xa0 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 = 641 (setkey) trap number = 9 panic: general protection fault Uptime: 3m11s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff803ba433 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #3 0xffffffff803baa36 in panic (fmt=0xffffff00152be720 "@\023°\025") at /usr/src/sys/kern/kern_shutdown.c:555 #4 0xffffffff805af57f in trap_fatal (frame=0xffffff00152be720, eva=18446742974561784640) at /usr/src/sys/amd64/amd64/trap.c:655 #5 0xffffffff805afa22 in trap (frame= {tf_rdi = -1099013703168, tf_rsi = 4351, tf_rdx = 4351, tf_rcx = -281373226712833, tf_r8 = 0, tf_r9 = -1099156429024, tf_rax = -1770518320, tf_rbx = -1770518145, tf_rbp = 160, tf_r10 = -2139144832, tf_r11 = 1, tf_r12 = 0, tf_r13 = -1099151977264, tf_r14 = 0, tf_r15 = 0, tf_trapno = 9, tf_addr = 0, tf_flags = 4, tf_err = 0, tf_rip = -2142479028, tf_cs = 8, tf_rflags = 66051, tf_rsp = -1770518352, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:467 #6 0xffffffff8059f0ab in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #7 0xffffffff804c5d4c in keydb_newsecasvar () at /usr/src/sys/netkey/keydb.c:177 #8 0x0000000000001041 in ?? () #9 0xffffff00178dc9b0 in ?? () #10 0xffffff00156fd4d0 in ?? () #11 0xffffff001dadba00 in ?? () #12 0x0000000000000000 in ?? () Previous frame identical to this frame (corrupt stack?) (kgdb) up 7 #7 0xffffffff804c5d4c in keydb_newsecasvar () at /usr/src/sys/netkey/keydb.c:177 177 if (q->id < said && said < TAILQ_NEXT(q, tailq)->id) (kgdb) list 172 said++; 173 TAILQ_FOREACH(q, &satailq, tailq) { 174 if (q->id == said) 175 goto again; 176 if (TAILQ_NEXT(q, tailq)) { 177 if (q->id < said && said < TAILQ_NEXT(q, tailq)->id) 178 break; 179 if (q->id + 1 < TAILQ_NEXT(q, tailq)->id) { 180 said = q->id + 1; 181 break; (kgdb) pirnt    rint q $1 = (struct secasvar *) 0xffffffff9678097f (kgdb) print q->id $2 = 4351 (kgdb) print q->id     said $3 = 0 (kgdb) print said    tailq No symbol "tailq" in current context. (kgdb) yo  up #8 0x0000000000001041 in ?? () (kgdb) up #9 0xffffff00178dc9b0 in ?? () (kgdb) up #10 0xffffff00156fd4d0 in ?? () (kgdb) up #11 0xffffff001dadba00 in ?? () (kgdb) up #12 0x0000000000000000 in ?? () (kgdb) up Initial frame selected; you cannot go up. (kgdb) quit satsmb# ^Dexit Script done on Sat Nov 19 02:48:28 2005 --- ipsec.1.debug ends here --- I will welcome any requests for further investigations. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 19 01:04:59 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AB1A16A41F for ; Sat, 19 Nov 2005 01:04:59 +0000 (GMT) (envelope-from ray@redshift.com) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1017543D45 for ; Sat, 19 Nov 2005 01:04:59 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id 4F14C98529; Fri, 18 Nov 2005 17:04:55 -0800 (PST) Message-Id: <3.0.1.32.20051118170452.00a8ca08@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 18 Nov 2005 17:04:52 -0800 To: Nathan Vidican From: ray@redshift.com In-Reply-To: <437E24BE.90008@wmptl.com> References: <3.0.1.32.20051118071132.00d655b8@pop.redshift.com> <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <3.0.1.32.20051118060718.00d655b8@pop.redshift.com> <3.0.1.32.20051118071132.00d655b8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 01:04:59 -0000 At 02:00 PM 11/18/2005 -0500, Nathan Vidican wrote: | ray@redshift.com wrote: | > | I'm trying to get him towards ordering a 3Ware-Escalade 9500S-4 RAID | > | controller (or possibly the -8 or -12 one). | > | > The 9500S line is a good choice. You can also sometimes find them used/NIB on | > ebay at a fair price ($300 to $400). BTW, in my testing, you don't get much | > additional performance from having 8 vs 4 drives (if you want to save costs). | > Although you do get more space :) | > | > | One thing which is of importance is that their budget may not allow for | > | a really high end server, so they may have to decide to buy a semi | > | high-end server. This then may result in them taking Athlons instead of | > | Opterons, and it may result in a MoBo with 32-bits PCI slots instead of | > | 64-bits PCI slots. Judging from the pictures of the 9500S it has a | > | 64-bits PCI slot, but it looks like it might be compatible with the | > | 32-bits slots as well (at a performance penalty, of course). | > | Would you happen to know if that's indeed possible, or whether they'd | > | better choose a different RAID controller? | > | > You'd have to check the 3ware website to be sure, but a lot of times those cards | > are backwards compatible with the 32 bit slots. I just checked the manuals I | > have for the 9000 series and it says 3Ware cards will run properly in any PCI or | > PCI-X slot, but you'll get better performance in a 64 bit slot - here is the | > text from the manual: | > | > -------------------------------------------------------- | > Selecting the Slot in Which to Install the Controller | > Consider these factors when deciding on the slot in which to insert the controller: | > .. While the 3ware RAID Controller runs properly in any PCI or | > PCI-X slot, not all slots give equal performance due to the | > architecture of the PCI bus. | > These slots typically give the best performance: | > .. Slots closest to the Accelerated Graphics Port (AGP), if | > included. | > .. 64-bit PCI slots | > Although the controller fits in both 32-bit and 64-bit PCI or | > PCI-X slots with 5V as well as with 3.3V, install it in a 64- | > bit slot to take full advantage of the controller’s | > performance. | > -------------------------------------------------------- | > | > | Regarding the MySQL versions and their settings: tnx for giving me | > | enough comfort to indeed give heavy preference for the FreeBSD amd64 | > | version. Will (source) installing the version from the ports do, or do | > | you mean something else when you say that you compiled MySQL yourself? | > | > from the tar.gz off the mysql site. E-mail me privately for a full run down on | > the install I use, but here is the basic idea: | > | > as root do this: | > ------------------------------------------------------ | > tar -xzf mysql-4.1.15.tar.gz | > cd mysql-4.1.15 | > pw groupadd mysql | > adduser {user you are creating is mysql} | > | > CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions | > -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler | > --with-mysqld-ldflags=-all-static --without-debug | > | > make | > make install | > make clean | > | > ln -s /usr/local/mysql/share/mysql/mysql.server /usr/local/bin/mysql.server | > ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql | > ln -s /usr/local/mysql/bin/mysqld_safe /usr/local/bin/mysqld_safe | > ------------------------------------------------------ | > | > There is more too it, but that's the basic idea. Check the readme/install files | > with the tar.gz - I will also send you my entire run down privately in a second. | > | > | Regarding the benchmark results: I'd love to receive them. Can you | > | perhaps send them off-list to me? | > | > Actually, I forgot that I put them on-line a while back. Here you go: | > | > http://www.redshift.com/~ray/mysql_bench/ | > | > | Regarding W*nd*ws vs. FreeBSD: I love your remark; I wonder if the | > | person I forwarded it to can laugh as loudly about it as I did. :D | > | > :) | > | > | Finally regarding SCSI vs. SATA: | > | >I've had far better luck using SATA over SCSI in the recent couple of years. | > | > We have several machines setup using FreeBSD and 3Ware RAID 0+1 that | > | > routinely run with no problems and uptimes of 200 to 300 days at a time. | > | | > | Very interesting to know. At present, I myself have a 754 socket AMD | > | Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an | > | Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB | > | drives attached to it in RAID-10 mode. So far it works a charm (though I | > | too had to effectively downgrade it to U160 due to the lack of 64-bits | > | PCI slots, grrr). I hope it'll keep performing well (so far uptimes in | > | the order magnitude you mention have been working fine for me as well on | > | SCSI - Adaptec 2100S RAID set-ups in my (now) fall-back server, and ever | > | after installing the AMD-64 one 34 days ago I haven't had to restart it | > | so far)... | > | > The file will send you with the benchmarks includes the PHP files to run the | > benchmarks, so if you feel like adding your #'s to the mix, just let me know. | > Or feel free to run the code and send me the results. I'll e-mail you privately | > in a second here. | > | > | Yet, it'll be interesting to keep an eye on the SATA RAID performance | > | and costs. With such uptimes SATA will surely become (if it hasn't | > | already become so, that is) a very good alternative for SCSI. | > | > SATA is built on top of SCSI I think (not sure exactly how it all sorts out, but | > I think some of the SATA stuff is tied into some of the SCSI stuff in the kernel | > or something). If I recall correctly, you have to leave some SCSI drivers in | > the kernel when you setup SATA on FreeBSD. I may be off, but I think that's | > what we had to do. Maybe someone more familiar with the kernel stuff can | > comment further on that count. | > | > I will e-mail you the install run down in a sec. | > | > Ray | > | > | > | Actually, that's quite wrong. S-ATA is ATA, not SCSI-like... S-ATA in fact is | almost the same as ATA (EIDE) from a code/kernel standpoint. The physical | hardware interface differs slightly and offers greater stability and performance | than standard ATA (EIDE). However, you are correct if not confusing when you | state that you must 'leave some SCSI drivers in the kernel', this is not for ATA | so much as it is for the use of the RAID card. If you're using plain old S-ATA, | no SCSI disk devices are required, but with the 3Ware Escalades, you will need: | | device scbus | device da | device twa | | | Anyhow, long story short - the only 'real' difference from S-ATA to P-ATA | (Parallel ATA aka 'ATA' or 'EIDE'), is the interface - the drive internals and | functionality are the same - but both differ from SCSI. Hi Nathan, Thanks for the run down. I was refering mainly to the drivers (specifically the ones you mention above, scbus and da, etc), not so much the hardware per se. Ray From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 19 03:07:09 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F5EB16A41F; Sat, 19 Nov 2005 03:07:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6196D43D46; Sat, 19 Nov 2005 03:07:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2258813 for multiple; Fri, 18 Nov 2005 22:07:00 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAJ36oKN042486; Fri, 18 Nov 2005 22:06:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 18 Nov 2005 22:06:47 -0500 User-Agent: KMail/1.8.3 References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> In-Reply-To: <200511190018.jAJ0ItTe013855@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511182206.49195.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: amd64@freebsd.org, Matthew Dillon , Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 03:07:09 -0000 On Friday 18 November 2005 07:18 pm, Matthew Dillon wrote: > :So the amd64 snapshot didn't boot but the i386 one did? Interesting. > :Thanks a lot for investigating this. > : > :Scott > > Yup. My guess is that the 64-bit boot issue that early in the boot > sequence is something stupid simple. It looks it from the consistency > of the crash. Actually, your comments about the stray ICU interrupts led me to it on the = way=20 home tonight. Peter has a hack in amd64 that if you don't include 'device= =20 atpic' in your kernel config (not in GENERIC amd64 by default in HEAD) he=20 just masks the PICs. However, he doesn't setup handlers for the spurious=20 interrupts that can still occur (since they are unmaskable). Couple that=20 with the fact that HEAD (until a few hours ago) didn't print the trap messa= ge=20 for a T_RESERVED trap, and you'll see that your panic on amd64 was caused b= y=20 a spurious ICU interrupt. I have part of peter's hack expanded to do a ful= l=20 reset of the ICUs, and I'll update it for Monday to adjust the base interru= pt=20 such that the spurious ICU vectors get sent to the APIC spurious interrupt= =20 vector. That should fix your issue as well as the same issue reported by=20 someone else on the amd64@ list recently. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 19 07:33:51 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A989C16A420; Sat, 19 Nov 2005 07:33:51 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB6643D45; Sat, 19 Nov 2005 07:33:51 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (ru@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAJ7XpsG071110; Sat, 19 Nov 2005 07:33:51 GMT (envelope-from ru@freefall.freebsd.org) Received: (from ru@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAJ7XpMm071106; Sat, 19 Nov 2005 07:33:51 GMT (envelope-from ru) Date: Sat, 19 Nov 2005 07:33:51 GMT From: Ruslan Ermilov Message-Id: <200511190733.jAJ7XpMm071106@freefall.freebsd.org> To: kobayasi@pp.iij4u.or.jp, ru@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/83806: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 07:33:51 -0000 Synopsis: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. State-Changed-From-To: open->patched State-Changed-By: ru State-Changed-When: Sat Nov 19 07:33:26 GMT 2005 State-Changed-Why: Fixed in 7.0-CURRENT, MFC in 1 week. http://www.freebsd.org/cgi/query-pr.cgi?pr=83806 From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 19 12:41:32 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C9FD16A41F; Sat, 19 Nov 2005 12:41:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A47C243D46; Sat, 19 Nov 2005 12:41:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jAJCfUhZ021194; Sat, 19 Nov 2005 07:41:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAJCfUKE056750; Sat, 19 Nov 2005 07:41:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4E4EE7302F; Sat, 19 Nov 2005 07:41:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051119124130.4E4EE7302F@freebsd-current.sentex.ca> Date: Sat, 19 Nov 2005 07:41:30 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 12:41:32 -0000 TB --- 2005-11-19 11:43:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-19 11:43:12 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-19 11:43:12 - cleaning the object tree TB --- 2005-11-19 11:43:48 - checking out the source tree TB --- 2005-11-19 11:43:48 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-19 11:43:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-19 11:50:20 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-19 11:50:20 - cd /src TB --- 2005-11-19 11:50:20 - /usr/bin/make -B buildworld >>> 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 >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/sbin/ping/ping.c: In function `main': /src/sbin/ping/ping.c:240: error: `MAX_IPOPTLEN' undeclared (first use in this function) /src/sbin/ping/ping.c:240: error: (Each undeclared identifier is reported only once /src/sbin/ping/ping.c:240: error: for each function it appears in.) /src/sbin/ping/ping.c:240: warning: unused variable `rspace' /src/sbin/ping/ping.c: In function `pr_pack': /src/sbin/ping/ping.c:1016: error: `MAX_IPOPTLEN' undeclared (first use in this function) /src/sbin/ping/ping.c:1016: warning: unused variable `old_rr' *** Error code 1 Stop in /src/sbin/ping. *** Error code 1 Stop in /obj/amd64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-19 12:41:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-19 12:41:30 - ERROR: failed to build world TB --- 2005-11-19 12:41:30 - tinderbox aborted