From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 9 00:43:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7E6116A4CE; Sun, 9 Jan 2005 00:43:32 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75EB943D2D; Sun, 9 Jan 2005 00:43:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j090hVIC088810; Sat, 8 Jan 2005 19:43:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id j090hVei062463; Sat, 8 Jan 2005 19:43:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 914C37306E; Sat, 8 Jan 2005 19:43:31 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050109004331.914C37306E@freebsd-current.sentex.ca> Date: Sat, 8 Jan 2005 19:43:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/640/Thu Dec 23 13:48:27 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 00:43:33 -0000 TB --- 2005-01-08 23:44:33 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-08 23:44:33 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-01-08 23:44:33 - checking out the source tree TB --- 2005-01-08 23:44:33 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-01-08 23:44:33 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-08 23:50:22 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-08 23:50:22 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-01-08 23:50:22 - /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 [...] cc -O2 -pipe -I/tinderbox/CURRENT/amd64/amd64/src/sbin/atm/ilmid/../../../sys -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/sbin/atm/ilmid/ilmid.c (cd /tinderbox/CURRENT/amd64/amd64/src/rescue/rescue/../../sbin/ping6 && /home/tinderbox/CURRENT/amd64/amd64/obj/tinderbox/CURRENT/amd64/amd64/src/make.i386/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/ping6/ depend && /home/tinderbox/CURRENT/amd64/amd64/obj/tinderbox/CURRENT/amd64/amd64/src/make.i386/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/ping6/ ping6.o) rm -f .depend mkdep -f .depend -a -DINET6 -DIPSEC -DKAME_SCOPEID -DUSE_RFC2292BIS -DHAVE_POLL_H -DHAVE_ARC4RANDOM -DRESCUE /tinderbox/CURRENT/amd64/amd64/src/sbin/ping6/ping6.c echo ping6: /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libc.a /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libipsec.a /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libm.a /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libmd.a >> .depend cc -O2 -pipe -DINET6 -DIPSEC -DKAME_SCOPEID -DUSE_RFC2292BIS -DHAVE_POLL_H -DHAVE_ARC4RANDOM -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/CURRENT/amd64/amd64/src/sbin/ping6/ping6.c /tinderbox/CURRENT/amd64/amd64/src/sbin/ping6/ping6.c: In function `pr_ip6opt': /tinderbox/CURRENT/amd64/amd64/src/sbin/ping6/ping6.c:1786: warning: passing arg 5 of `inet6_opt_next' from incompatible pointer type *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sbin/ping6. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-01-09 00:43:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-09 00:43:31 - ERROR: failed to build world TB --- 2005-01-09 00:43:31 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 9 04:06:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA57816A4CF for ; Sun, 9 Jan 2005 04:06:30 +0000 (GMT) Received: from mail.fearthepenguin.net (h-68-165-82-164.dllatx37.covad.net [68.165.82.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39CAA43D2F for ; Sun, 9 Jan 2005 04:06:30 +0000 (GMT) (envelope-from doubletwist@fearthepenguin.net) Received: from localhost (localhost [127.0.0.1]) by fearthepenguin.net (Postfix) with ESMTP id 0AF1C3BC94 for ; Sat, 8 Jan 2005 23:10:59 -0600 (CST) Received: from mail.fearthepenguin.net ([127.0.0.1]) by localhost (rerun [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30049-02 for ; Sat, 8 Jan 2005 23:10:58 -0600 (CST) Received: from [192.168.0.16] (h-68-165-82-162.dllatx37.covad.net [68.165.82.162]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.fearthepenguin.net (Postfix) with ESMTP id 8583E3BA63 for ; Sat, 8 Jan 2005 23:10:58 -0600 (CST) Message-ID: <41E0ADC1.6080808@fearthepenguin.net> Date: Sat, 08 Jan 2005 22:06:25 -0600 From: Doubletwist User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at fearthepenguin.net Subject: Abit K8V-MAX3 nic doesn't function during install X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 04:06:30 -0000 I have an Abit K8V-MAX3 motherboard with gig Ethernet on it. [It's branded a 3com, but uses the sk98 module in Linux]. The install correctly detects it [using sk0 I believe], but it does not function during the install. If I try to use DHCP, it never sends the request out [the dhcp server sees no request]. If I try to set the ip manually, it accepts the address but still doesn't work. I then installed from the cd without using the network. Once it was installed and booted, dhcp worked, and I was able to use the nic just fine. I had this same problem with an earlier version of Freebsd 5.something. I'm not sure why it would work after it is set up ,but not during the install even though the nic is detected. Just thought I'd put that out there in case someone else is thinking of using this motherboard. Doubletwist aka. Jim From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 9 06:54:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC4B16A4CE for ; Sun, 9 Jan 2005 06:54:02 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA45143D39 for ; Sun, 9 Jan 2005 06:54:01 +0000 (GMT) (envelope-from ccnp.bsd@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so320862rnf for ; Sat, 08 Jan 2005 22:54:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=bn7zpp8uzEcqhbT5S5YyzjdwOmoF6ludodFW0QMLACfZ6FWWygLN4jn6XaioYtkzEVlWcuY7AQxTQ/8MtYDPkeAwBHffGjsRsJzrn5EGqcx5rj/NM3YRli1CMlYU3/tU0lWWzezav99aT3q4ggthmUGX9GeWJkmgWlTX/5MkJ9c= Received: by 10.39.2.32 with SMTP id e32mr271125rni; Sat, 08 Jan 2005 22:54:01 -0800 (PST) Received: by 10.38.208.42 with HTTP; Sat, 8 Jan 2005 22:54:01 -0800 (PST) Message-ID: Date: Sun, 9 Jan 2005 00:54:01 -0600 From: Nick Lozinsky To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Dlink DWL-AG660 WiFi A/B/G PCCARD card not loading in 5.3-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nick Lozinsky List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 06:54:02 -0000 Hello, I have made sure that my kernel config had: device wlan device an device awi device wi After rebooting with new kernel, I have attempted to: # kldload bridge without the PC card being inserted, then inserting it, I receive: cardbus0: at device 0.0 (no driver loaded) cbb0: CardBus card activation failed Also, device cardbus, device pccard, device cbb are also included in the kernel. Is this Dlink card compatible with FreeBSD-5.4-STABLE? Thank you in advance. Nick From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 9 11:10:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A49C16A4CE for ; Sun, 9 Jan 2005 11:10:08 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D9A43D2F for ; Sun, 9 Jan 2005 11:10:08 +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 555D51FFACD; Sun, 9 Jan 2005 12:10:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 6155A1FFACA; Sun, 9 Jan 2005 12:10:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 4AD9D1550C; Sun, 9 Jan 2005 11:08:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 403B715384; Sun, 9 Jan 2005 11:08:46 +0000 (UTC) Date: Sun, 9 Jan 2005 11:08:46 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Doubletwist In-Reply-To: <41E0ADC1.6080808@fearthepenguin.net> Message-ID: References: <41E0ADC1.6080808@fearthepenguin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-amd64@freebsd.org Subject: Re: Abit K8V-MAX3 nic doesn't function during install X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 11:10:08 -0000 On Sat, 8 Jan 2005, Doubletwist wrote: > I have an Abit K8V-MAX3 motherboard with gig Ethernet on it. [It's > branded a 3com, but uses the sk98 module in Linux]. see the archives or http://www.freebsd.org/releases/5.3R/errata.htm for well known problems with sk(4). Some of them got already corrected. You might want to update to RELENG_5 (5-STABLE) to get the latest version of the driver. There still is a DHCP problem on bootup but I think there is a fix out there and I will look into this next week. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 9 11:50:24 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 348BF16A4CE for ; Sun, 9 Jan 2005 11:50:24 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A9A43D3F for ; Sun, 9 Jan 2005 11:50:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j09BoNMh075730 for ; Sun, 9 Jan 2005 11:50:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j09BoN8P075729; Sun, 9 Jan 2005 11:50:23 GMT (envelope-from gnats) Date: Sun, 9 Jan 2005 11:50:23 GMT Message-Id: <200501091150.j09BoN8P075729@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Tomaz Borstnar Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tomaz Borstnar List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 11:50:24 -0000 The following reply was made to PR amd64/71471; it has been noted by GNATS. From: Tomaz Borstnar To: freebsd-gnats-submit@FreeBSD.org, tomaz.borstnar@over.net Cc: Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M Date: Sun, 09 Jan 2005 12:38:31 +0100 Nothing new with 5.3 release. It stops installing (copying) files to volumes with I/O error. Source upgrade from 5.2.x might work, but 5.2.x does not know about Adaptec IDs for ServeRAID 6M :( From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 10 11:02:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40B5D16A4D2 for ; Mon, 10 Jan 2005 11:02:59 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0612143D58 for ; Mon, 10 Jan 2005 11:02:59 +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.1/8.13.1) with ESMTP id j0AB2wXf095441 for ; Mon, 10 Jan 2005 11:02:58 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0AB2wRR095435 for freebsd-amd64@freebsd.org; Mon, 10 Jan 2005 11:02:58 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 10 Jan 2005 11:02:58 GMT Message-Id: <200501101102.j0AB2wRR095435@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 11:02:59 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk 13 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 10 19:11:52 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C78D816A4CE for ; Mon, 10 Jan 2005 19:11:52 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947E743D1D for ; Mon, 10 Jan 2005 19:11:52 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0AJEOGY023912; Mon, 10 Jan 2005 11:14:24 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0AJENw7023911; Mon, 10 Jan 2005 11:14:23 -0800 Date: Mon, 10 Jan 2005 11:14:23 -0800 From: Brooks Davis To: Nick Lozinsky Message-ID: <20050110191423.GB15907@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: Dlink DWL-AG660 WiFi A/B/G PCCARD card not loading in 5.3-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 19:11:52 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 09, 2005 at 12:54:01AM -0600, Nick Lozinsky wrote: > Hello, >=20 > I have made sure that my kernel config had: >=20 > device wlan > device an > device awi > device wi >=20 > After rebooting with new kernel, I have attempted to: >=20 > # kldload bridge >=20 > without the PC card being inserted, then inserting it, I receive: >=20 > cardbus0: at device 0.0 (no driver loaded) > cbb0: CardBus card activation failed >=20 > Also, device cardbus, device pccard, device cbb are also included in the = kernel. > Is this Dlink card compatible with FreeBSD-5.4-STABLE? You'll need the ath(4) driver or the ndisulator. This card should work in 6.x, I'm not sure if the device ids are in 5-STABLE or not. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9zSXsLTf0vkW971A Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB4tQPXY6L6fI4GtQRAsvNAKDc//y915TRAnb54Fjso9Asg41xZACfdowd gx4apaMzPvVpN7+/YA4+Czo= =q2y0 -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A-- From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 10 23:34:34 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73B8516A4CE for ; Mon, 10 Jan 2005 23:34:34 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2306D43D45 for ; Mon, 10 Jan 2005 23:34:34 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1Co93Q-000Lcr-Ve for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:32 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1Co93O-000Lck-Cy for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:32 +0100 Received: from localhost ([127.0.0.1]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1Co93O-000Lch-6m for freebsd-amd64@freebsd.org; Tue, 11 Jan 2005 00:34:30 +0100 Message-ID: <41E31103.1040003@anduin.net> Date: Tue, 11 Jan 2005 00:34:27 +0100 From: =?ISO-8859-1?Q?Eirik_=D8verby?= User-Agent: Mozilla Thunderbird 1.0RC1 (Macintosh/20041201) 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-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-5.9 required=7.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 Subject: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 23:34:34 -0000 [Trying again, first attempt didn't come through, it seems. Otherwise excuse the dup.] Hi! Daring as I am, here's another attempt at having someone look into the asr driver and why it doesn't work on amd64. I have such a Zero-Channel RAID card laying around collecting dust, whereas it was planned installed in a server here long time ago. I know Scott Long looked into it long ago, and he seems to have been the last one to touch the driver. He indicated a few months ago that he had little time; perhaps things look brighter now that 5.3 is out? I'll cross-post to -current/-stable in a few days if I don't hear anything.. Thanks, /Eirik From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 01:31:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 975C616A4CE for ; Tue, 11 Jan 2005 01:31:43 +0000 (GMT) Received: from smtp.uol.com.br (smtpout1.uol.com.br [200.221.4.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B853543D46 for ; Tue, 11 Jan 2005 01:31:42 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from [200.141.91.218] (200141091218.user.veloxzone.com.br [200.141.91.218]) by scorpion1.uol.com.br (Postfix) with ESMTP id EDF608FEE for ; Mon, 10 Jan 2005 23:31:40 -0200 (BRST) Message-ID: <41E32C81.8090608@jonny.eng.br> Date: Mon, 10 Jan 2005 23:31:45 -0200 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Athlon 64 2800+ on ASUS K8V SE freezing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 01:31:43 -0000 Hi, I've been running a test machine with FreeBSD-amd64 5.3-stable since 5.3-beta. It's a Athlon 64 2800+ on ASUS K8V SE, 512M DDR400 and 2 Seagate SATA 200 on Promise RAID1. In the test setup, no problem was found, except for the onboard sk(4), which has been "replaced" by an Intel fxp(4). Then, after migrating for production work, this same machine is now freezing (no panics, just full freeze) after some time. I could not yet find a repeatable procedure to freeze this machine. I have removed almost every non-essencial driver from the kernel and non-essencial daemons from running, but it still freezes. Could somebody please help me on how to seek the source of these problems? I've seen some reports of problems with the Promise RAID Controler, the firewire controller (which I am not using) and the ACPI subsystem (which I don't know if I can disable). But all of these are now more than six months old, and I thought they have been fixed. Here is the current dmesg.boot. Note the DMA failure on ad0. This disk is not being used here, it is installed just for copying of previous i386 system data, but this disk is pretty new and had no problems before. Anyway, the freeze was happening before it has been installed here. Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Mon Jan 10 18:48:24 BRST 2005 jonny@roma.coe.ufrj.br:/usr/cvsup/RELENG_5/src/sys/amd64/compile/ROMA64 WARNING: DIAGNOSTIC option enabled, expect reduced performance. WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 2800+ (1802.32-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 536018944 (511 MB) avail memory = 508870656 (485 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) atapci0: port 0xbc00-0xbc7f,0xcc00-0xcc0f,0xdc00-0xdc3f mem 0xf7700000-0xf771ffff,0xf7800000-0xf7800fff irq 18 at device 8.0 on pci0 atapci0: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 fxp0: port 0xec00-0xec1f mem 0xf7e00000-0xf7efffff,0xf5200000-0xf5200fff irq 16 at device 9.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:a0:c9:cc:52:b3 fxp0: [GIANT-LOCKED] puc0: port 0xb000-0xb007 irq 19 at device 14.0 on pci0 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode atapci1: port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 20 at device 15.0 on pci0 ata5: channel #0 on atapci1 ata6: channel #1 on atapci1 atapci2: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci2 ata1: channel #1 on atapci2 pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 16.2 (no driver attached) pci0: at device 16.3 (no driver attached) pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A orm0: at iomem 0xc0000-0xcafff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1802318426 Hz quality 800 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging unlimited ad0: 114473MB [232581/16/63] at ata0-master UDMA100 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=234441585 ad0: FAILURE - READ_DMA timed out acd0: CDROM at ata1-master PIO4 ad4: 190782MB [387621/16/63] at ata2-master SATA150 ad6: 190782MB [387621/16/63] at ata3-master SATA150 ar0: 190782MB [24321/255/63] status: READY subdisks: disk0 READY on ad6 at ata3-master disk1 READY on ad4 at ata2-master Mounting root from ufs:/dev/ar0s1a Accounting enabled Heres the kernel config file: machine amd64 cpu HAMMER ident ROMA maxusers 0 options INCLUDE_CONFIG_FILE options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options IPSEC # IP security options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options QUOTA # enable disk quotas options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options NULLFS # NULL filesystem options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device atpic # 8259A compatability options NO_MIXED_MODE # Don't penalize working chipsets device acpi options ACPI_DEBUG device isa device pci device agp device fdc device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device sc options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso15 options SC_HISTORY_SIZE=1000 # number of history buffer lines device sio # 8250, 16[45]50 based serial ports device puc device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device rl # RealTek 8129/8139 device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device bpf # Berkeley packet filter device snp # Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 Jonny -- João Carlos Mendes Luís - Networking Engineer - jonny@jonny.eng.br From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 01:33:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B06A16A4CE for ; Tue, 11 Jan 2005 01:33:35 +0000 (GMT) Received: from smtp.uol.com.br (smtpout3.uol.com.br [200.221.4.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C975A43D1D for ; Tue, 11 Jan 2005 01:33:34 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from [200.141.91.218] (200141091218.user.veloxzone.com.br [200.141.91.218]) by scorpion3.uol.com.br (Postfix) with ESMTP id 5F70D90ED for ; Mon, 10 Jan 2005 23:33:33 -0200 (BRST) Message-ID: <41E32CF2.4070005@jonny.eng.br> Date: Mon, 10 Jan 2005 23:33:38 -0200 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: atacontrol rebuild ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 01:33:35 -0000 Hi, Is atacontrol rebuild working? I had a mirror configuration needing a rebuild on a freebsd-amd64, and nothing happened after running atacontrol rebuild 0. Not even an error message. Should I avoid ataraid and go for gmirror or gvinum instead? Jonny -- João Carlos Mendes Luís - Networking Engineer - jonny@jonny.eng.br From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 04:51:31 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30BB516A4CE for ; Tue, 11 Jan 2005 04:51:31 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56F6B43D49 for ; Tue, 11 Jan 2005 04:51:30 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id 020AC8A for ; Tue, 11 Jan 2005 13:51:28 +0900 (JST) Date: Tue, 11 Jan 2005 13:51:29 +0900 From: Shunsuke SHINOMIYA To: freebsd-amd64@freebsd.org Message-Id: <20050111132101.84B1.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Mailer: Becky! ver. 2.12.01 [ja] Subject: thread with 32bit compatible binary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 04:51:31 -0000 Hello, I try to run FreeBSD 32bit native JDK 1.4.2 with FreeBSD/amd64 5-stable, but ld-elf.so.1 says `/usr/lib32/libpthread.so.1: Undefined symbol "i386_set_ldt"'. > ~> java > /libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol "i386_= set_ldt" I set /etc/libmap32.conf to use lib32/libthr or libc_r instead of lib32/libpthread, but java did not run too. In case of lib32/libthr. ~> java /libexec/ld-elf.so.1: /usr/lib32/libthr.so.1: Undefined symbol "i386_set_ld= t" In case of lib32/libc_r. ~> java yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: 67155= 7860 yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: -1 yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: -1 yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: -1 yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: -1 yp_match: clnt_call: RPC: Unable to receive; errno =3D Unknown error: -1 =2E.. Are there any ways to use 32bit compatible thread library with 5-stable? Is this problem corrected with 6-current? Thank you in advance. --=20 Shunsuke SHINOMIYA From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 08:48:05 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D0F416A4CE for ; Tue, 11 Jan 2005 08:48:05 +0000 (GMT) Received: from mta1.siol.net (pegasus.siol.net [193.189.160.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF24243D5F for ; Tue, 11 Jan 2005 08:48:03 +0000 (GMT) (envelope-from tomaz.borstnar@over.net) Received: from edge1.siol.net ([10.10.10.210]) by mta1.siol.net with ESMTP id <20050111084802.QEIM9346.mta1.siol.net@edge1.siol.net>; Tue, 11 Jan 2005 09:48:02 +0100 Received: from zvezek1.over.net ([193.77.70.7]) by edge1.siol.net with ESMTP id <20050111084801.TOER11496.edge1.siol.net@zvezek1.over.net>; Tue, 11 Jan 2005 09:48:01 +0100 Message-Id: <6.2.0.14.0.20050111094509.06758a70@193.189.169.9> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 11 Jan 2005 09:48:07 +0100 To: =?iso-8859-1?Q?Jo=E3o?= Carlos Mendes =?iso-8859-1?Q?Lu=EDs?= From: Tomaz Borstnar In-Reply-To: <41E32C81.8090608@jonny.eng.br> References: <41E32C81.8090608@jonny.eng.br> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable cc: freebsd-amd64@freebsd.org Subject: Re: Athlon 64 2800+ on ASUS K8V SE freezing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 08:48:05 -0000 At 02:31 11.1.2005, Jo=E3o Carlos Mendes Lu=EDs wrote: >Hi, > > I've been running a test machine with FreeBSD-amd64 5.3-stable since= =20 > 5.3-beta. It's a Athlon 64 2800+ on ASUS K8V SE, 512M DDR400 and 2=20 > Seagate SATA 200 on Promise RAID1. In the test setup, no problem was=20 > found, except for the onboard sk(4), which has been "replaced" by an=20 > Intel fxp(4). I added fxp next to builtin re (realtek gig eth)... > Then, after migrating for production work, this same machine is now=20 > freezing (no panics, just full freeze) after some time. I could not yet= =20 > find a repeatable procedure to freeze this machine. I have removed=20 > almost every non-essencial driver from the kernel and non-essencial=20 > daemons from running, but it still freezes. According to my experiences fxp could be the reason. Had the same problems= =20 until I switched back to re card. Try with another card. Tomaz=20 From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 11:55:09 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28F3716A4CE for ; Tue, 11 Jan 2005 11:55:09 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52EE943D41 for ; Tue, 11 Jan 2005 11:55:08 +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 5210F1FF91D; Tue, 11 Jan 2005 12:55:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 506361FF90C; Tue, 11 Jan 2005 12:55:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id C31561550C; Tue, 11 Jan 2005 11:51:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id C03371550B; Tue, 11 Jan 2005 11:51:02 +0000 (UTC) Date: Tue, 11 Jan 2005 11:51:02 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Tomaz Borstnar In-Reply-To: <6.2.0.14.0.20050111094509.06758a70@193.189.169.9> Message-ID: References: <41E32C81.8090608@jonny.eng.br> <6.2.0.14.0.20050111094509.06758a70@193.189.169.9> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-amd64@freebsd.org Subject: Re: Athlon 64 2800+ on ASUS K8V SE freezing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 11:55:09 -0000 On Tue, 11 Jan 2005, Tomaz Borstnar wrote: > At 02:31 11.1.2005, Jo=E3o Carlos Mendes Lu=EDs wrote: > >Hi, > > > > I've been running a test machine with FreeBSD-amd64 5.3-stable sinc= e > > 5.3-beta. It's a Athlon 64 2800+ on ASUS K8V SE, 512M DDR400 and 2 > > Seagate SATA 200 on Promise RAID1. In the test setup, no problem was > > found, except for the onboard sk(4), which has been "replaced" by an > > Intel fxp(4). > > I added fxp next to builtin re (realtek gig eth)... when updating to latest RELENG_5 sk(4) should be usable again. --=20 Bjoern A. Zeeb=09=09=09=09bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 12:06:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24A7B16A4CE for ; Tue, 11 Jan 2005 12:06:32 +0000 (GMT) Received: from hal.btw23.de (reverse-213-146-119-155.dialin.kamp-dsl.de [213.146.119.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5843943D3F for ; Tue, 11 Jan 2005 12:06:31 +0000 (GMT) (envelope-from flo@btw23.de) Received: by hal.btw23.de (Postfix, from userid 1004) id 4C63A256F3; Tue, 11 Jan 2005 13:10:38 +0100 (CET) Date: Tue, 11 Jan 2005 13:10:38 +0100 From: usenet04@rootofallevil.net To: freebsd-amd64@freebsd.org Message-ID: <20050111121038.GA1827@hal.btw23.de> Mail-Followup-To: freebsd-amd64@freebsd.org References: <41E32C81.8090608@jonny.eng.br> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <41E32C81.8090608@jonny.eng.br> X-Operating-System: Linux 2.6.9 i586 X-Homepage: http://rootofallevil.net X-GPG-Key: FE3A7C44 X-Phone: +49-9231-702360 X-Phone2: +49-921-1612118 X-Mobile: +49-176-23534542 User-Agent: Mutt/1.5.6i Subject: Re: Athlon 64 2800+ on ASUS K8V SE freezing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 12:06:32 -0000 On Mon, Jan 10, 2005 at 11:31:45PM -0200, João Carlos Mendes Luís wrote: > Hi, > > I've been running a test machine with FreeBSD-amd64 5.3-stable > since 5.3-beta. It's a Athlon 64 2800+ on ASUS K8V SE, 512M DDR400 and > 2 Seagate SATA 200 on Promise RAID1. In the test setup, no problem was > found, except for the onboard sk(4), which has been "replaced" by an > Intel fxp(4). > > Then, after migrating for production work, this same machine is now > freezing (no panics, just full freeze) after some time. I could not yet > find a repeatable procedure to freeze this machine. I have removed > almost every non-essencial driver from the kernel and non-essencial > daemons from running, but it still freezes. I had the same problem with an 3000+ and same mainboard. I replaced my 360W power supply with a new 500W and things are working now. Maybe that solves your problem. -- Florian Unglaub GnuPG Key ID: FE3A7C44 http://rootofallevil.net/files/flo.pub.asc No ePatents: From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 14:31:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 123E016A4D1; Tue, 11 Jan 2005 14:31:51 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F13B43D31; Tue, 11 Jan 2005 14:31:50 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0BEVoiH062421; Tue, 11 Jan 2005 09:31:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0BEVo8n063278; Tue, 11 Jan 2005 09:31:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C22E57306E; Tue, 11 Jan 2005 09:31:49 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050111143149.C22E57306E@freebsd-current.sentex.ca> Date: Tue, 11 Jan 2005 09:31:49 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/640/Thu Dec 23 13:48:27 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 14:31:51 -0000 TB --- 2005-01-11 13:53:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-11 13:53:09 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-01-11 13:53:09 - checking out the source tree TB --- 2005-01-11 13:53:09 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-01-11 13:53:09 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-11 13:58:58 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-11 13:58:58 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-01-11 13:58:58 - /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 [...] mkdep -f .depend -a /tinderbox/CURRENT/amd64/amd64/src/sbin/kldstat/kldstat.c echo kldstat: /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libc.a >> .depend ===> sbin/kldunload (depend) rm -f .depend mkdep -f .depend -a /tinderbox/CURRENT/amd64/amd64/src/sbin/kldunload/kldunload.c echo kldunload: /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libc.a >> .depend ===> sbin/ldconfig (depend) make: don't know how to make shlib.c. Stop *** Error code 2 Stop in /tinderbox/CURRENT/amd64/amd64/src/sbin. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-01-11 14:31:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-11 14:31:49 - ERROR: failed to build world TB --- 2005-01-11 14:31:49 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 11 14:53:58 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E24416A4CE for ; Tue, 11 Jan 2005 14:53:58 +0000 (GMT) Received: from minerva.int.gov.br (nat.int.gov.br [200.20.196.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 346A743D54 for ; Tue, 11 Jan 2005 14:53:57 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from [10.0.8.17] (dinf-02 [10.0.8.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by minerva.int.gov.br (Postfix) with ESMTP id 1762FBE517 for ; Tue, 11 Jan 2005 12:53:55 -0200 (BRDT) Message-ID: <41E3E882.3060407@jonny.eng.br> Date: Tue, 11 Jan 2005 12:53:54 -0200 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <41E32C81.8090608@jonny.eng.br> <20050111121038.GA1827@hal.btw23.de> In-Reply-To: <20050111121038.GA1827@hal.btw23.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Athlon 64 2800+ on ASUS K8V SE freezing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 14:53:58 -0000 usenet04@rootofallevil.net wrote: > On Mon, Jan 10, 2005 at 11:31:45PM -0200, João Carlos Mendes Luís wrote: > >>Hi, >> >> I've been running a test machine with FreeBSD-amd64 5.3-stable >>since 5.3-beta. It's a Athlon 64 2800+ on ASUS K8V SE, 512M DDR400 and >>2 Seagate SATA 200 on Promise RAID1. In the test setup, no problem was >>found, except for the onboard sk(4), which has been "replaced" by an >>Intel fxp(4). >> >> Then, after migrating for production work, this same machine is now >>freezing (no panics, just full freeze) after some time. I could not yet >>find a repeatable procedure to freeze this machine. I have removed >>almost every non-essencial driver from the kernel and non-essencial >>daemons from running, but it still freezes. > > > I had the same problem with an 3000+ and same mainboard. I replaced my > 360W power supply with a new 500W and things are working now. > Maybe that solves your problem. I also thought this was the problem, but now we have a SevenTeam 550W PFC power source and the system still freezes. :-( Just wondering: Could there be a counter on ataraid that had some conversion problem when migrated to 64 bit? I've read another report of an user having the same problem, repeatable after lots of disk access. -- João Carlos Mendes Luís From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 00:13:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF5516A4CE; Wed, 12 Jan 2005 00:13:13 +0000 (GMT) Received: from mail.monkeytower.net (mail.monkeytower.net [195.49.173.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F3143D39; Wed, 12 Jan 2005 00:13:12 +0000 (GMT) (envelope-from root@mail.monkeytower.net) Received: from root by mail.monkeytower.net with local Exim id 1CoW9v-0006zN-0Z; Wed, 12 Jan 2005 01:14:47 +0100 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.monkeytower.net with esmtp Exim id 1CnFID-000Lzd-SX for mailinglists@suntsu.org; Sat, 08 Jan 2005 13:02:06 +0100 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 5C9FC561AE; Sat, 8 Jan 2005 11:57:24 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8EFC216A4FD; Sat, 8 Jan 2005 11:57:22 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24CA216A4CE; Sat, 8 Jan 2005 11:57:18 +0000 (GMT) Received: from graf.pompo.net (graf.pompo.net [81.56.186.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84E8943D4C; Sat, 8 Jan 2005 11:57:17 +0000 (GMT) (envelope-from thierry@pompo.net) Received: by graf.pompo.net (Postfix, from userid 1001) id 17A1B763F; Sat, 8 Jan 2005 12:56:07 +0100 (CET) Date: Sat, 8 Jan 2005 12:56:07 +0100 From: Thierry Thomas To: Francois Tigeot Message-ID: <20050108115606.GC53172@graf.pompo.net> Mail-Followup-To: Francois Tigeot , freebsd-emulation@freebsd.org, freebsd-ports@freebsd.org, freebsd-amd64@freebsd.org References: <20050107150038.044adcb7@dolphin.local.net> <20050108095217.GA765@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oLBj+sq0vYjzfsbl" Content-Disposition: inline In-Reply-To: <20050108095217.GA765@aoi.wolfpond.org> X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.10-STABLE i386 Organization: Kabbale Eros X-PGP: 0xC71405A2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-ports@freebsd.org Errors-To: owner-freebsd-ports@freebsd.org X-MailScanner-Information: contact information at http://www.monkeytower.net X-MailScanner: Found to be clean X-MailScanner-From: root@mail.monkeytower.net cc: freebsd-emulation@freebsd.org cc: freebsd-ports@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Many linux ports needing update to support amd64 X-BeenThere: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 00:13:13 -0000 --oLBj+sq0vYjzfsbl Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le Sam 8 jan 05 =E0 10:52:17 +0100, Francois Tigeot =E9crivait=A0: > I have filled ports/75852 a few days ago to allow java/linux-sun-jdk14 to > install on amd64. It also fixes some other ports such as print/acroread. >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/75852 >=20 > Even though it is a port issue it got assigned to java@ :-/ The category is still "ports", but java@ maintains this port. --=20 Th. Thomas. --oLBj+sq0vYjzfsbl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB38pWc95pjMcUBaIRAgb3AKC6Fvu6l3kibHy53J2juy/Y2nDrmgCeIpQ7 9U/mB6Jpz2tQyVt/HREGWrk= =ZCEW -----END PGP SIGNATURE----- --oLBj+sq0vYjzfsbl-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 11:20:36 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC0EF16A4D2 for ; Wed, 12 Jan 2005 11:20:35 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B3C943D46 for ; Wed, 12 Jan 2005 11:20:35 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0CBKZXl030681 for ; Wed, 12 Jan 2005 11:20:35 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0CBKZEl030680; Wed, 12 Jan 2005 11:20:35 GMT (envelope-from gnats) Resent-Date: Wed, 12 Jan 2005 11:20:35 GMT Resent-Message-Id: <200501121120.j0CBKZEl030680@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, Ulrich Roemer Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E0B16A4CE for ; Wed, 12 Jan 2005 11:16:42 +0000 (GMT) Received: from bis.bonn.org (f-1.bis.bonn.org [217.110.117.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDDD143D45 for ; Wed, 12 Jan 2005 11:16:38 +0000 (GMT) (envelope-from roemer@city-1.wetteronline.de) Received: from city-1.wetteronline.de ([213.148.151.87] verified) by bis.bonn.org (CommuniGate Pro SMTP 4.2) with ESMTP-TLS id 385446 for FreeBSD-gnats-submit@freebsd.org; Wed, 12 Jan 2005 12:16:36 +0100 Received: from city-1.wetteronline.de (localhost [127.0.0.1]) j0CBGXnO001922 for ; Wed, 12 Jan 2005 12:16:33 +0100 (CET) (envelope-from roemer@city-1.wetteronline.de) Received: (from roemer@localhost) by city-1.wetteronline.de (8.13.1/8.13.1/Submit) id j0CBGXEZ001921; Wed, 12 Jan 2005 12:16:33 +0100 (CET) (envelope-from roemer) Message-Id: <200501121116.j0CBGXEZ001921@city-1.wetteronline.de> Date: Wed, 12 Jan 2005 12:16:33 +0100 (CET) From: Ulrich Roemer To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/76136: system halts before reboot X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ulrich Roemer List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 11:20:36 -0000 >Number: 76136 >Category: amd64 >Synopsis: system halts before reboot >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 12 11:20:35 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Ulrich Roemer >Release: FreeBSD 5.3-STABLE amd64 >Organization: >Environment: System: FreeBSD city-1.wetteronline.de 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Jan 10 12:45:30 CET 2005 root@city-1.wetteronline.de:/space/obj/space/src/sys/CITY-1 amd64 amd64, freebsd 5.3 >Description: system halts before reboot: error: cpu_reset called on cpu#0 cpu_rest: stopping other cpus /var/run/dmesg.boot ----- Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #4: Mon Jan 10 12:45:30 CET 2005 root@city-1.wetteronline.de:/space/obj/space/src/sys/CITY-1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x659d,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,> AMD Features=0x20000800 Hyperthreading: 2 logical CPUs real memory = 1073610752 (1023 MB) avail memory = 1027170304 (979 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 iir0: mem 0xfa0fc000-0xfa0fffff irq 24 at device 3.0 on pci2 iir0: [GIANT-LOCKED] mpt0: port 0x9400-0x94ff mem 0xfa7c0000-0xfa7cffff,0xfa7d0000-0xfa7dffff irq 26 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt1: port 0x9800-0x98ff mem 0xfa7e0000-0xfa7effff,0xfa7f0000-0xfa7fffff irq 25 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] pci1: at device 0.1 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 pci1: at device 0.3 (no driver attached) pcib4: irq 16 at device 4.0 on pci0 pci4: on pcib4 pcib5: irq 16 at device 5.0 on pci0 pci5: on pcib5 pci5: at device 0.0 (no driver attached) pcib6: irq 16 at device 6.0 on pci0 pci6: on pcib6 uhci0: port 0xd000-0xd01f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd400-0xd41f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd800-0xd81f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib7: at device 30.0 on pci0 pci7: on pcib7 em0: port 0xcc00-0xcc3f mem 0xfea40000-0xfea5ffff irq 16 at device 4.0 on pci7 em0: Ethernet address: 00:0e:0c:4e:99:6e em0: Speed:N/A Duplex:N/A pci7: at device 6.0 (no driver attached) pci7: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] orm0: at iomem 0xd3000-0xd3fff,0xcd800-0xcdfff,0xc0000-0xcd7ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: DVDROM at ata0-master UDMA33 Waiting 3 seconds for SCSI devices to settle em0: Link is up 100 Mbps Full Duplex Interrupt storm detected on "irq16: em0 uhci0"; throttling interrupt source ses0 at iir0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device ses1 at iir0 bus 1 target 8 lun 0 ses1: Fixed Processor SCSI-2 device ses1: SAF-TE Compliant Device da0 at iir0 bus 2 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 279992MB (573424110 512 byte sectors: 255H 63S/T 35694C) SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Mounting root from ufs:/dev/da0s1a ----- >How-To-Repeat: reboot >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 18:20:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80CD116A4CE for ; Wed, 12 Jan 2005 18:20:23 +0000 (GMT) Received: from smtp2.enst.fr (revol1.enst.fr [137.194.32.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1D7A43D2D for ; Wed, 12 Jan 2005 18:20:22 +0000 (GMT) (envelope-from beyssac@bofh.enst.fr) Received: from localhost (localhost.enst.fr [127.0.0.1]) by smtp2.enst.fr (Postfix) with ESMTP id 0D1A9164CEE for ; Wed, 12 Jan 2005 19:20:22 +0100 (CET) Received: from smtp2.enst.fr ([127.0.0.1]) by localhost (revol1.enst.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81603-08 for ; Wed, 12 Jan 2005 19:20:18 +0100 (CET) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bofh.enst.fr", Issuer "ENST CA" (not verified)) by smtp2.enst.fr (Postfix) with ESMTP id 9FE25164CDF for ; Wed, 12 Jan 2005 19:20:18 +0100 (CET) Received: from bofh.enst.fr (localhost [127.0.0.1]) by bofh.enst.fr (8.13.1/8.13.1) with ESMTP id j0CIKIDh058989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 12 Jan 2005 19:20:18 +0100 (CET) (envelope-from beyssac@bofh.enst.fr) Received: (from beyssac@localhost) by bofh.enst.fr (8.13.1/8.13.1/Submit) id j0CIKI1W058988 for freebsd-amd64@freebsd.org; Wed, 12 Jan 2005 19:20:18 +0100 (CET) (envelope-from beyssac) Date: Wed, 12 Jan 2005 19:20:18 +0100 From: Pierre Beyssac To: freebsd-amd64@freebsd.org Message-ID: <20050112182018.GA58924@bofh.enst.fr> References: <20050105194836.GA85467@bofh.enst.fr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <20050105194836.GA85467@bofh.enst.fr> User-Agent: Mutt/1.4.2.1i X-message-flag: Warning! Use of Microsoft Outlook makes your system susceptible to worms and viruses X-Virus-Scanned: amavisd-new at enst.fr Subject: Re: RELENG_5 panic: page fault while in kernel mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 18:20:23 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 05, 2005 at 08:48:36PM +0100, Pierre Beyssac wrote: > I have the following reproductible panic (during a make release, > oddly enough when creating README.html for each port) on a Xeon box > (Dell PowerEdge 2850, double Xeon 2.8GHz, 4GB RAM) in amd64 mode. > It's a up-to-date RELENG_5. As a followup, here's a simple script that crashes my box every time (it takes a few seconds). Can someone try it on a test box and tell me if they see the same result? -- A: Yes. Pierre Beyssac pb@enst.fr >Q: Are you sure? >>A: Because it reverses the logical flow of conversation. >>>Q: Why is top posting annoying in email? --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=crashme #!/bin/sh while true; do make -V COMMENT -f - << 'EOF' COMMENT= Crash test GREP?= /usr/bin/grep TRUE?= true ECHO_CMD?= echo . for AJ in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 \ 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 \ 40 41 42 43 44 45 46 47 48 49 50 A!= ${ECHO_CMD} "${J}" | ${GREP} -q "${J}" \ && ${ECHO_CMD} "${J}" | ${GREP} -q "${J}" \ && ${ECHO_CMD} "${J}" | ${GREP} -q "${J}" \ && ${ECHO_CMD} "${J}" \ || ${TRUE} . endfor EOF done --3MwIy2ne0vdjdPXF-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 20:30:20 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4439E16A4CE for ; Wed, 12 Jan 2005 20:30:20 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0888043D5D for ; Wed, 12 Jan 2005 20:30:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0CKUJIx096799 for ; Wed, 12 Jan 2005 20:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0CKUJlu096798; Wed, 12 Jan 2005 20:30:19 GMT (envelope-from gnats) Resent-Date: Wed, 12 Jan 2005 20:30:19 GMT Resent-Message-Id: <200501122030.j0CKUJlu096798@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, Jonathan Dama Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F5EB16A4CE for ; Wed, 12 Jan 2005 20:27:28 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0C1643D54 for ; Wed, 12 Jan 2005 20:27:27 +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 j0CKRRRB039561 for ; Wed, 12 Jan 2005 20:27:27 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j0CKRRTw039560; Wed, 12 Jan 2005 20:27:27 GMT (envelope-from nobody) Message-Id: <200501122027.j0CKRRTw039560@www.freebsd.org> Date: Wed, 12 Jan 2005 20:27:27 GMT From: Jonathan Dama To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/76176: misc/compat4x are mismarked unsupported on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 20:30:20 -0000 >Number: 76176 >Category: amd64 >Synopsis: misc/compat4x are mismarked unsupported on amd64 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 12 20:30:19 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Jonathan Dama >Release: FreeBSD-5.3/amd64 >Organization: Caltech VLSI Engineering >Environment: FreeBSD carbon.async.caltech.edu 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Jan 10 11 :53:44 PST 2005 root@carbon.async.caltech.edu:/usr/obj/usr/src/sys/CRUNCHER amd64 >Description: misc/compat4x reports "unsupported" because 4.x did not run amd64. However, amd64 supports running i386 binaries and libraries. Obviously, 4.x-i386 binaries should be able to run. >How-To-Repeat: cd /usr/ports/misc/compat4x && make install >Fix: Port should be adjusted to download the packages for the i386 architecture and install them in /usr/local/lib32/compat >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 22:37:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2561916A4CF for ; Wed, 12 Jan 2005 22:37:25 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id A00FA43D2F for ; Wed, 12 Jan 2005 22:37:24 +0000 (GMT) (envelope-from will@exomi.com) Received: from [192.168.1.29] (ZMCXLI.dsl.saunalahti.fi [85.76.70.242]) by will.iki.fi (Postfix) with ESMTP id 1D343138; Thu, 13 Jan 2005 00:37:23 +0200 (EET) From: Ville-Pertti Keinonen To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Thu, 13 Jan 2005 00:37:17 +0200 Message-Id: <1105569437.670.45.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: wpaul@windriver.com Subject: RFC: if_ndis on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 22:37:25 -0000 Now that 64-bit Windows WLAN drivers are actually available, I decided to see if it would be relatively simple to get a 64-bit driver to work on FreeBSD/amd64. It turns out Microsoft doesn't even use the same calling conventions as everybody else, so it ended up requiring some fairly intrusive changes, such as making everything in the HAL, NDIS and ntoskrnl tables point to assembly language wrappers, and making the symbols for the actual functions visible for linking. To get it to work, I used the very ugly trick of #defining away the static keyword for code where those functions were being defined... Before I start cleaning things up I'd like some comments on what kind of solution to this would be preferred and have a chance of actually being committed (e.g. having an ndis_static that is empty on amd64). A patch against a recent -current is available at http://will.iki.fi/patches/ndis-amd64-20050112.diff It seems reasonably functional; I'm writing this on my Ferrari 3200 running FreeBSD/amd64, and my main route to the outside world is through: ndis0: mem 0xd0014000-0xd0015fff irq 19 at device 9.0 on pci0 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:0b:6b:4a:7e:76 I found the 64-bit Windows driver I'm using through a link on http://www.linuxant.com/driverloader/drivers.php The .inf file needed some editing for ndiscvt to do anything useful with it (asciification and getting rid of the NTamd64 strings). Although ndis.ko builds on amd64, for some reason if_ndis.ko can't find symbols that it defines, so currently "option NDISAPI" needs to be in the kernel. From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 23:33:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EEE116A4CE for ; Wed, 12 Jan 2005 23:33:32 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0952943D3F for ; Wed, 12 Jan 2005 23:33:32 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0CNXOPa032835; Wed, 12 Jan 2005 15:33:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0CNXNle032834; Wed, 12 Jan 2005 15:33:23 -0800 (PST) (envelope-from obrien) Date: Wed, 12 Jan 2005 15:33:23 -0800 From: "David O'Brien" To: Ville-Pertti Keinonen Message-ID: <20050112233323.GA29445@dragon.nuxi.com> References: <1105569437.670.45.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1105569437.670.45.camel@localhost> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: wpaul@windriver.com cc: freebsd-amd64@freebsd.org Subject: Re: RFC: if_ndis on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 23:33:32 -0000 On Thu, Jan 13, 2005 at 12:37:17AM +0200, Ville-Pertti Keinonen wrote: > Now that 64-bit Windows WLAN drivers are actually available, I decided > to see if it would be relatively simple to get a 64-bit driver to work > on FreeBSD/amd64. > > It turns out Microsoft doesn't even use the same calling conventions as > everybody else, What are "calling conventions that everyone else uses"?? Such things really don't exist as x86 CPU's don't force a particular way. It is up to the compiler writer to do what he wants. On the i386 there are three types available with MS and Borland C compilers: (1) pass thru registers, (2) pass on the stack in reverse order with the caller cleaning up the stack, (3) pass parameters on the stack (typically in order) with the callee cleaning up the stack. In the MSwin world, these are "FASTCALL", "CDECL", and "PASCAL". Both the AMD64 ELF and AMD64 PE (mswin) ABI's specify that the first X parameters are passed in registers (beyond that on the stack). So both ELF (ie, FreeBSD) and MSwin passes parameters differently on 32-bit "i386" vs. 64-bit AMD64. > Before I start cleaning things up I'd like some comments on what kind of > solution to this would be preferred and have a chance of actually being > committed (e.g. having an ndis_static that is empty on amd64). > > A patch against a recent -current is available at > http://will.iki.fi/patches/ndis-amd64-20050112.diff It is good to see NDIS progress on AMD64. I'll take a look at this patch and see how it matches the approach I was initially working on. > The .inf file needed some editing for ndiscvt to do anything useful with > it (asciification and getting rid of the NTamd64 strings). We should probably make ndiscvt accept the NTamd64 string as all MSwin64 drivers are required to have this now. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 12 23:34:35 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9819216A4CE; Wed, 12 Jan 2005 23:34:35 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 711E943D45; Wed, 12 Jan 2005 23:34:35 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0CNYZcG029495; Wed, 12 Jan 2005 23:34:35 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0CNYZq3029491; Wed, 12 Jan 2005 23:34:35 GMT (envelope-from obrien) Date: Wed, 12 Jan 2005 23:34:35 GMT From: "David E. O'Brien" Message-Id: <200501122334.j0CNYZq3029491@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, obrien@FreeBSD.org Subject: Re: amd64/76176: misc/compat4x are mismarked unsupported on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 23:34:35 -0000 Synopsis: misc/compat4x are mismarked unsupported on amd64 Responsible-Changed-From-To: freebsd-amd64->obrien Responsible-Changed-By: obrien Responsible-Changed-When: Wed Jan 12 23:33:48 GMT 2005 Responsible-Changed-Why: While compat4x can be installed by hand; we need to be careful to create compat convension that will allow both 32-bit and 64-bit compat5x to exist on the same FreeBSD/AMD64 system. http://www.freebsd.org/cgi/query-pr.cgi?pr=76176 From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 13 05:46:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3653516A4CE for ; Thu, 13 Jan 2005 05:46:02 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8795A43D48 for ; Thu, 13 Jan 2005 05:46:01 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id ED38E7C005 for ; Thu, 13 Jan 2005 00:46:00 -0500 (EST) Message-ID: <41E60A45.8010200@michaelmeltzer.com> Date: Thu, 13 Jan 2005 00:42:29 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: [Fwd: twa breakage on AMD64 with 9.1.5.2 3ware version and2005-01-11 03:00:49 UTC RELENG_5 commit] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 05:46:02 -0000 -------- Original Message -------- Subject: twa breakage on AMD64 with 9.1.5.2 3ware version and 2005-01-11 03:00:49 UTC RELENG_5 commit Date: Thu, 13 Jan 2005 00:18:35 -0500 From: Michael Meltzer To: freebsd stable The new 3ware twa drive does not seem to work after the 2005-01-11 03:00:49 UTC RELENG_5 commit. Basically the device da is not visible to complete the boot and the system stopped asking for the root path (if their was an error message it scrolled to fast for me to see) Backed off to 5_3_0_RELEASE code to /usr/src/sys/dev/twa/* to get the system backup. FWIW the 3ware support page does NOT list amd64 freebsd support for this driver( 9.1.5.2) and 3ware seem to define the downloadable driver firmware feather in their makefile, the -D rule does not seem to have made it to the build. I tried to rebuild the code with the correct define but the firmware try to load but still had the problem. Took a look at the CVS diffs but it a large/complex change set and someone smarter than myself needs to take a look. -mjm From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 13 05:50:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6A2416A4CE for ; Thu, 13 Jan 2005 05:50:19 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C13143D1D for ; Thu, 13 Jan 2005 05:50:19 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 3CBF22A8FC; Wed, 12 Jan 2005 21:50:19 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (dhcp55.wemm.org [10.0.0.55]) by fw.wemm.org (Postfix) with ESMTP id C42BAE2B5; Wed, 12 Jan 2005 21:50:18 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by peter-laptop.wemm.org (8.12.11/8.12.11) id j0D5nnXl017036; Wed, 12 Jan 2005 21:49:49 -0800 (PST) (envelope-from peter) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 12 Jan 2005 21:49:49 -0800 User-Agent: KMail/1.6.2 References: <20050111132101.84B1.SHINO@fornext.org> In-Reply-To: <20050111132101.84B1.SHINO@fornext.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501122149.49712.peter@wemm.org> Subject: Re: thread with 32bit compatible binary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 05:50:19 -0000 On Monday 10 January 2005 08:51 pm, Shunsuke SHINOMIYA wrote: > Hello, > > I try to run FreeBSD 32bit native JDK 1.4.2 with FreeBSD/amd64 5-stable, > but ld-elf.so.1 says `/usr/lib32/libpthread.so.1: Undefined symbol > "i386_set_ldt"'. > > > ~> java > > /libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol > > "i386_set_ldt" > > I set /etc/libmap32.conf to use lib32/libthr or libc_r instead of > lib32/libpthread, but java did not run too. Unfortunately, there is zero chance of getting this binary to work with libpthread because the 32bit mailbox interface is layed out differently on the 64 bit kernel due to differences in pointer sizes, alignment etc. The chances of getting kse apps to run in any form is pretty remote at the moment. > In case of lib32/libthr. > ~> java > /libexec/ld-elf.so.1: /usr/lib32/libthr.so.1: Undefined symbol > "i386_set_ldt" > > In case of lib32/libc_r. > ~> java > yp_match: clnt_call: RPC: Unable to receive; errno = Unknown error: > 671557860 yp_match: clnt_call: RPC: Unable to receive; errno = Unknown > error: -1 yp_match: clnt_call: RPC: Unable to receive; errno = Unknown > error: -1 yp_match: clnt_call: RPC: Unable to receive; errno = Unknown > error: -1 yp_match: clnt_call: RPC: Unable to receive; errno = Unknown > error: -1 yp_match: clnt_call: RPC: Unable to receive; errno = Unknown > error: -1 ... > > Are there any ways to use 32bit compatible thread library with 5-stable? > Is this problem corrected with 6-current? Finding out what the problem is with libc_r is the best short-term chance of success for running threaded apps. libthr and libpthread are out of reach for now because we don't have ldt support. I think I MFC'ed patches to make the compat shim libraries use _amd64_set_gsbase() etc, but that won't make the kernel thread stuff work. > Thank you in advance. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 13 07:16:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D352216A4CE for ; Thu, 13 Jan 2005 07:16:07 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AE7D43D45 for ; Thu, 13 Jan 2005 07:16:07 +0000 (GMT) (envelope-from will@exomi.com) Received: from [192.168.1.29] (ZMCXLI.dsl.saunalahti.fi [85.76.70.242]) by will.iki.fi (Postfix) with ESMTP id 25BE6C3; Thu, 13 Jan 2005 09:16:06 +0200 (EET) From: Ville-Pertti Keinonen To: freebsd-amd64@freebsd.org In-Reply-To: <20050112233323.GA29445@dragon.nuxi.com> References: <1105569437.670.45.camel@localhost> <20050112233323.GA29445@dragon.nuxi.com> Content-Type: text/plain Date: Thu, 13 Jan 2005 09:15:59 +0200 Message-Id: <1105600559.662.56.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: wpaul@windriver.com Subject: Re: RFC: if_ndis on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 07:16:07 -0000 On Wed, 2005-01-12 at 15:33 -0800, David O'Brien wrote: > What are "calling conventions that everyone else uses"?? Such things > really don't exist as x86 CPU's don't force a particular way. It is up > to the compiler writer to do what he wants. Note that I didn't even try to claim "standard" calling conventions; however AFAIK all of the released operating systems that run on amd64 (*BSD, Linux, Solaris) use the same C ABI (SysV (ELF) ABI). Often at least the basic C calling conventions are compatible across ABIs. > Both the AMD64 ELF and AMD64 PE (mswin) ABI's specify that the first X > parameters are passed in registers (beyond that on the stack). So both > ELF (ie, FreeBSD) and MSwin passes parameters differently on 32-bit > "i386" vs. 64-bit AMD64. The different i386 conventions are at least partly to historical reasons. Since 64-bit mode is inevitably incompatible with 32-bit mode, I was hoping 64-bit mode would be somewhat more consistent. Anyhow, having to create wrappers isn't that bad, and should be possible to be coerced to work correctly. The varargs kludge I used should be possible to eliminate by transforming the arguments into a va_list instead of trying to preserve it as a varargs call. Something like: ENTRY(sprintf_x64) subq $40,%rsp mov %rdi,32(%rsp) mov %rsi,24(%rsp) mov %r8,40+8+16(%rsp) mov %r9,40+8+24(%rsp) movl $48,(%rsp) movl $0,4(%rsp) lea 40+8+16(%rsp),%rax mov %rax,8(%rsp) mov %rax,16(%rsp) mov %rcx,%rdi mov %rdx,%rsi mov %rsp,%rdx call vsprintf mov 32(%rsp),%rdi mov 24(%rsp),%rsi addq $40,%rsp ret From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 13 19:47:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5019A16A4CE for ; Thu, 13 Jan 2005 19:47:45 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09AB643D39 for ; Thu, 13 Jan 2005 19:47:45 +0000 (GMT) (envelope-from will@exomi.com) Received: from ZMXLVII.dsl.saunalahti.fi (ZMXLVII.dsl.saunalahti.fi [85.76.70.148]) by will.iki.fi (Postfix) with ESMTP id ED294C3; Thu, 13 Jan 2005 21:47:43 +0200 (EET) From: Ville-Pertti Keinonen To: william paul In-Reply-To: <200501131842.KAA02977@huisne.wrs.com> References: <200501131842.KAA02977@huisne.wrs.com> Content-Type: text/plain Date: Thu, 13 Jan 2005 21:47:33 +0200 Message-Id: <1105645653.684.15.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: RFC: if_ndis on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 19:47:45 -0000 On Thu, 2005-01-13 at 10:42 -0800, william paul wrote: > I have to sit down and do a bit of research on the amd64 calling > conventions first. Right at the moment I don't have any better ideas, > but I'll see what I can come up with. Just for a quick reference, the ELF/Unix conventions are available at (among other places): http://www.x86-64.org/documentation The Microsoft conventions can be found at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/64bitAMD_6ec00b51-bf75-41bf-8635-caa8653c8bd9.xml.asp (If the link doesn't work, try googling for "x64 calling conventions"). In any case, thank you for the excellent implementation of the NDIS API! I was genuinely impressed by how everything seemed to work so easily after I had fixed the few minor amd64 issues. With no knowledge of any NDIS or Windows programming, in two evenings I managed to get things working, just by trying things out and figuring out (mostly by disassembling, googling and educated guesses) what was going wrong. ;) If you're ever in Finland, I'd be happy to buy you a drink or ten. :) The same applies to other FreeBSD contributors, as well! From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 13 22:30:58 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5378316A4EC for ; Thu, 13 Jan 2005 22:30:36 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 882BE43D45 for ; Thu, 13 Jan 2005 22:30:36 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0DMUaFl037130 for ; Thu, 13 Jan 2005 22:30:36 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0DMUaah037122; Thu, 13 Jan 2005 22:30:36 GMT (envelope-from gnats) Resent-Date: Thu, 13 Jan 2005 22:30:36 GMT Resent-Message-Id: <200501132230.j0DMUaah037122@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, Jonathan Dama Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EF2716A4CE for ; Thu, 13 Jan 2005 22:26:12 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 044C343D1D for ; Thu, 13 Jan 2005 22:26:12 +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 j0DMQBqj075950 for ; Thu, 13 Jan 2005 22:26:11 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j0DMQBdx075949; Thu, 13 Jan 2005 22:26:11 GMT (envelope-from nobody) Message-Id: <200501132226.j0DMQBdx075949@www.freebsd.org> Date: Thu, 13 Jan 2005 22:26:11 GMT From: Jonathan Dama To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/76224: gcc fails to invoke ld properly, ld fails to examine ldconfig -32's libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 22:30:59 -0000 >Number: 76224 >Category: amd64 >Synopsis: gcc fails to invoke ld properly, ld fails to examine ldconfig -32's libraries >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 13 22:30:35 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Jonathan Dama >Release: FreeBSD-5.3/amd64 >Organization: Caltech VLSI Group >Environment: FreeBSD carbon.async.caltech.edu 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Jan 10 11:53:44 PST 2005 root@carbon.async.caltech.edu:/usr/obj/usr/src/sys/CRUNCHER amd64 >Description: Though /usr/bin/ld reports that it can make elf_i386_fbsd, cc -m32 simple-c-file.c does not properly build gcc does not translate -m32 to mean that ld must be envoked with /usr/lib32 bits instead of /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o also mistakenly gives: -dynamic-linker /libexec/ld-elf.so.1 and -L/usr/lib instead of -dynamic-linker /libexec/ld-elf32.so.1 and -L/usr/lib32 >How-To-Repeat: Following simple test program (main.c): #include int main() { printf("Hello world\n"); return 0; } Run: jd@carbon:~/tmp/cdemo>cc -m32 -v -o test main.c Result: Using built-in specs. Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 /usr/libexec/cc1 -quiet -v -D_LONGLONG main.c -quiet -dumpbase main.c -m32 -aux base main -version -o /var/tmp//ccGKzqtl.s ignoring duplicate directory "/usr/include" #include "..." search starts here: #include <...> search starts here: /usr/include End of search list. GNU C version 3.4.2 [FreeBSD] 20040728 (amd64-fbsdproj-freebsd) compiled by GNU C version 3.4.2 [FreeBSD] 20040728. GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 /usr/bin/as -V -Qy --32 -o /var/tmp//ccdmrhyt.o /var/tmp//ccGKzqtl.s GNU assembler version 2.15 [FreeBSD] 2004-05-23 (x86_64-obrien-freebsd) using BF D version 2.15 [FreeBSD] 2004-05-23 /usr/bin/ld -m elf_i386_fbsd -V -dynamic-linker /libexec/ld-elf.so.1 -o test /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/lib -melf_i386_fbsd /var/tmp//ccdmrhyt.o -lgcc -lc -lgcc /usr/lib/crtend.o /usr/lib/crtn.o GNU ld version 2.15 [FreeBSD] 2004-05-23 Supported emulations: elf_i386_fbsd elf_x86_64_fbsd /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 00:20:19 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D4B516A4CE; Fri, 14 Jan 2005 00:20:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43DF843D1F; Fri, 14 Jan 2005 00:20:19 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0E0KJCv052612; Fri, 14 Jan 2005 00:20:19 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0E0KIeo052608; Fri, 14 Jan 2005 00:20:18 GMT (envelope-from obrien) Date: Fri, 14 Jan 2005 00:20:18 GMT From: "David E. O'Brien" Message-Id: <200501140020.j0E0KIeo052608@freefall.freebsd.org> To: jd@caltech.edu, obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/76224: gcc fails to invoke ld properly, ld fails to examine ldconfig -32's libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 00:20:19 -0000 Synopsis: gcc fails to invoke ld properly, ld fails to examine ldconfig -32's libraries State-Changed-From-To: open->closed State-Changed-By: obrien State-Changed-When: Fri Jan 14 00:19:46 GMT 2005 State-Changed-Why: Know issue. We don't yet support building 32-bit apps on a a 64-bit system. We only barely support *running* them at this point. http://www.freebsd.org/cgi/query-pr.cgi?pr=76224 From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 00:23:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34C1616A4CE for ; Fri, 14 Jan 2005 00:23:00 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 064D043D1F for ; Fri, 14 Jan 2005 00:23:00 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0E0MulU052588; Thu, 13 Jan 2005 16:22:56 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0E0MtP1052587; Thu, 13 Jan 2005 16:22:55 -0800 (PST) (envelope-from obrien) Date: Thu, 13 Jan 2005 16:22:54 -0800 From: "David O'Brien" To: Eirik ?verby Message-ID: <20050114002254.GC29445@dragon.nuxi.com> References: <41E31103.1040003@anduin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E31103.1040003@anduin.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 00:23:00 -0000 On Tue, Jan 11, 2005 at 12:34:27AM +0100, Eirik ?verby wrote: > [Trying again, first attempt didn't come through, it seems. Otherwise > excuse the dup.] > > Hi! > > Daring as I am, here's another attempt at having someone look into the > asr driver and why it doesn't work on amd64. > I have such a Zero-Channel RAID card laying around collecting dust, > whereas it was planned installed in a server here long time ago. > > I know Scott Long looked into it long ago, and he seems to have been the > last one to touch the driver. He indicated a few months ago that he had > little time; perhaps things look brighter now that 5.3 is out? > > I'll cross-post to -current/-stable in a few days if I don't hear anything.. NO need to cross post. Unless you see a statement otherwise -- nothing has changed. eBay a *real* RAID controller. ;-)) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 05:09:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D59C216A4CE for ; Fri, 14 Jan 2005 05:09:08 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5CC543D49 for ; Fri, 14 Jan 2005 05:09:08 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0E596CV017473; Thu, 13 Jan 2005 21:09:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0E596lm017406; Thu, 13 Jan 2005 21:09:06 -0800 (PST) (envelope-from obrien) Date: Thu, 13 Jan 2005 21:09:06 -0800 From: "David O'Brien" To: Paul Allen Message-ID: <20050114050906.GE29445@dragon.nuxi.com> References: <20050103231847.GJ22456@philemon.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050103231847.GJ22456@philemon.caltech.edu> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: 5-STABLE or -CURRENT? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 05:09:08 -0000 On Mon, Jan 03, 2005 at 03:18:47PM -0800, Paul Allen wrote: > I had experienced some issues with 5.3-Release vis-a-vis bad > bounce buffer panics. > > Am I correct in my read of the mailing list that 5.3-Stable > Resolves these issues? Yes. > Additionally, I was wondering if it was regarded as better > to run some snapshot of current. You should only run 6-CURRENT if you're really prepaired to deal with what -CURRENT is. > I've heard some off hand > remarks along the lines of "everyone who is running on amd64 > should be running -CURRENT." Is this true? No it is not true. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 08:20:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D8CE16A4CE for ; Fri, 14 Jan 2005 08:20:06 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9B4943D31 for ; Fri, 14 Jan 2005 08:20:04 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id 7694D4D; Fri, 14 Jan 2005 17:20:03 +0900 (JST) Date: Fri, 14 Jan 2005 17:20:03 +0900 From: Shunsuke SHINOMIYA To: Peter Wemm In-Reply-To: <200501122149.49712.peter@wemm.org> References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> Message-Id: <20050114171031.F520.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12.01 [ja] cc: freebsd-amd64@freebsd.org Subject: Re[2]: thread with 32bit compatible binary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 08:20:06 -0000 Thank you, Peter. > Finding out what the problem is with libc_r is the best short-term chance of > success for running threaded apps. libthr and libpthread are out of reach I see. I will try to find out the cause of this problem. And, I look forward to JDK15 running on FreeBSD/amd64. -- Shunsuke SHINOMIYA From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 09:25:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B630316A4CE for ; Fri, 14 Jan 2005 09:25:51 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id C150343D1F for ; Fri, 14 Jan 2005 09:25:50 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.0.61] (elrond.private.hydrix.com [192.168.0.61]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0E9PsNs001261 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Fri, 14 Jan 2005 20:25:55 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041221053638.33947b3a@dolphin.local.net> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041220192745.0e941442@dolphin.local.net> <20041221021702.GB83892@dragon.nuxi.com> <20041221053638.33947b3a@dolphin.local.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <39D80F62-660E-11D9-82BD-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Fri, 14 Jan 2005 20:25:27 +1100 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Subject: 5.3-RELEASE hangs as of 14/01/2005 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 09:25:51 -0000 Hello I Just performed a make update (with tag RELENG_5) installed the kernel, reboot: it hangs right after detecting my 3ware 9500-8S card. Reverting to the kernel build the same way on November 28th and it works fine... Any changes made on the twa0 driver lately? Regards Jean-Yves From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 13:28:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B3A16A4CE; Fri, 14 Jan 2005 13:28:30 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B9043D31; Fri, 14 Jan 2005 13:28:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 57822513CE; Fri, 14 Jan 2005 05:28:29 -0800 (PST) Date: Fri, 14 Jan 2005 05:28:29 -0800 From: Kris Kennaway To: Kris Kennaway , src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG Message-ID: <20050114132829.GA42958@xor.obsecurity.org> References: <200501140709.j0E79NTA046894@repoman.freebsd.org> <20050114131536.GA41709@xor.obsecurity.org> <20050114132433.GA97735@VARK.MIT.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <20050114132433.GA97735@VARK.MIT.EDU> User-Agent: Mutt/1.4.2.1i cc: amd64@FreeBSD.org Subject: Re: cvs commit: src/lib/msun/alpha fenv.h src/lib/msun/amd64 fenv.h src/lib/msun/arm fenv.h src/lib/msun/i387 fenv.h src/lib/msun/ia64 fenv.h src/lib/msun/powerpc fenv.h src/lib/msun/sparc64 fenv.h X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 13:28:30 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 14, 2005 at 08:24:33AM -0500, David Schultz wrote: > On Fri, Jan 14, 2005, Kris Kennaway wrote: > > On Fri, Jan 14, 2005 at 07:09:23AM +0000, David Schultz wrote: > > > das 2005-01-14 07:09:23 UTC > > >=20 > > > FreeBSD src repository > > >=20 > > > Modified files: > > > lib/msun/alpha fenv.h=20 > > > lib/msun/amd64 fenv.h=20 > > > lib/msun/arm fenv.h=20 > > > lib/msun/i387 fenv.h=20 > > > lib/msun/ia64 fenv.h=20 > > > lib/msun/powerpc fenv.h=20 > > > lib/msun/sparc64 fenv.h=20 > > > Log: > > > Mark all inline asms that read the floating-point control or status > > > registers as volatile. Instructions that *wrote* to FP state were > > > already marked volatile, but apparently gcc has license to move > > > non-volatile asms past volatile asms. This broke amd64's feupdatee= nv > > > at -O2 due to a WAR conflict between fnstsw and fldenv there. > >=20 > > Do you think this is likely to the cause of the build failures > > reported with a number of ports when world is compiled with -O2 > > (i.e. does the feupdateenv failure cascade to other commonly-used > > parts of the code)? >=20 > No, this would lead to a runtime failure, and I would be surprised > if very many ports use fenv.h anyway. OK :-( Someone needs to revert amd64 back to using -O in the meantime, then. Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB58j9Wry0BWjoQKURAujtAKDEY/GK83bMoFUVqRS9rvFwSSFaigCeINV3 1kUtm2an2QXE1THaKSWLUwI= =7XcG -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 14:31:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D39DA16A4CE for ; Fri, 14 Jan 2005 14:31:16 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2047843D2F for ; Fri, 14 Jan 2005 14:31:15 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1CpSTp-00033n-Th for freebsd-amd64@freebsd.org; Fri, 14 Jan 2005 15:31:13 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1CpSTn-00033W-Mx for freebsd-amd64@freebsd.org; Fri, 14 Jan 2005 15:31:13 +0100 Received: from eirik.unicore.no ([213.225.74.166] helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CpSTn-00033T-2z for freebsd-amd64@freebsd.org; Fri, 14 Jan 2005 15:31:11 +0100 Message-ID: <41E7D834.7080505@anduin.net> Date: Fri, 14 Jan 2005 15:33:24 +0100 From: =?ISO-8859-1?Q?Eirik_=D8verby?= User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <41E31103.1040003@anduin.net> <20050114002254.GC29445@dragon.nuxi.com> In-Reply-To: <20050114002254.GC29445@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-2.6 required=7.5 tests=BAYES_00 autolearn=ham version=3.0.1 Subject: Re: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 14:31:16 -0000 David O'Brien wrote: > On Tue, Jan 11, 2005 at 12:34:27AM +0100, Eirik ?verby wrote: > >>[Trying again, first attempt didn't come through, it seems. Otherwise >>excuse the dup.] >> >>Hi! >> >>Daring as I am, here's another attempt at having someone look into the >>asr driver and why it doesn't work on amd64. >>I have such a Zero-Channel RAID card laying around collecting dust, >>whereas it was planned installed in a server here long time ago. >> >>I know Scott Long looked into it long ago, and he seems to have been the >>last one to touch the driver. He indicated a few months ago that he had >>little time; perhaps things look brighter now that 5.3 is out? >> >>I'll cross-post to -current/-stable in a few days if I don't hear anything.. > > > NO need to cross post. Unless you see a statement otherwise -- nothing > has changed. eBay a *real* RAID controller. ;-)) Sorry. Already done.. And for the record, this *is* a "real" RAID controller; it's a real pity noone cares about upgrading the driver. It's a Ultra320 SCSI RAID controller card, used by many Tyan high-end Opteron motherboards. /Eirik From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 14:46:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1850A16A4CE for ; Fri, 14 Jan 2005 14:46:38 +0000 (GMT) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 741CF43D1F for ; Fri, 14 Jan 2005 14:46:37 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com) (mikej@69.193.222.195 with login) by smtp103.rog.mail.re2.yahoo.com with SMTP; 14 Jan 2005 14:46:33 -0000 Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Fri, 14 Jan 2005 09:46:34 -0500 (EST) Message-ID: <11291.207.219.213.163.1105713994.squirrel@207.219.213.163> In-Reply-To: <41E7D834.7080505@anduin.net> References: <41E31103.1040003@anduin.net> <20050114002254.GC29445@dragon.nuxi.com> <41E7D834.7080505@anduin.net> Date: Fri, 14 Jan 2005 09:46:34 -0500 (EST) From: "Mike Jakubik" To: Eirik =?iso-8859-1?Q?=D8verby?= User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-amd64@freebsd.org Subject: Re: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 14:46:38 -0000 Eirik Øverby said: > Sorry. Already done.. And for the record, this *is* a "real" RAID > controller; it's a real pity noone cares about upgrading the driver. > It's a Ultra320 SCSI RAID controller card, used by many Tyan high-end > Opteron motherboards. It's also a pity that most of of the drivers for high end RAID controllers are still Giant locked, while crappy ATA is not. From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 17:52:47 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D5F816A4CE for ; Fri, 14 Jan 2005 17:52:47 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA0D43D1F for ; Fri, 14 Jan 2005 17:52:47 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0EHuFLF026330; Fri, 14 Jan 2005 12:56:15 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Fri, 14 Jan 2005 12:56:15 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: =?ISO-8859-1?Q?Eirik_=D8verby?= In-Reply-To: <41E7D834.7080505@anduin.net> Message-ID: <20050114123408.P13189@bahre.achedra.org> References: <41E31103.1040003@anduin.net> <20050114002254.GC29445@dragon.nuxi.com> <41E7D834.7080505@anduin.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1162557361-1105724270=:13189" Content-ID: <20050114123903.S13189@bahre.achedra.org> X-Virus-Scanned: ClamAV 0.80/631/Wed Dec 15 09:01:14 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 17:52:47 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1162557361-1105724270=:13189 Content-Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; FORMAT=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: <20050114123903.U13189@bahre.achedra.org> On Fri, 14 Jan 2005, [ISO-8859-1] Eirik =D8verby wrote: >> NO need to cross post. Unless you see a statement otherwise -- nothing >> has changed. eBay a *real* RAID controller. ;-)) > > Sorry. Already done.. And for the record, this *is* a "real" RAID control= ler;=20 > it's a real pity noone cares about upgrading the driver. It's a Ultra320 = SCSI=20 > RAID controller card, used by many Tyan high-end Opteron motherboards. (On three, cue the users..) Ah, no. The 2105S is definitely not in the real RAID class. If it was reall= y all that good, other folks would be using it. For that matter, if it was an= y good, Tyan would be using it on the S4882 instead of the LSI 53c1030 mpt(4) with PCI-X Ultra320-0 amr(4) ZCR. Either way, I recall Scott saying not too long ago, "asr(4) needs fixed on amd64. Can anyone step up to fix it?" and being greeted with a chorus of crickets. In other words, there is a shortage of people with the time and/o= r resources to get this done, and I wouldn't expect to see any change in that any time soon. -Ketrien I. Saihr-Kenchedra Ozzy pages, "Our cafeteria posts its menu weekly on the internal web. The page is marked 'CISCO CONFIDENTIAL'." to you. Ozzy pages, "Competitors and customers must not find out what goes on in Cisco's s3kr1t f00d labz!!!1!!11!!" to you. --0-1162557361-1105724270=:13189-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:05:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AA1116A4CE for ; Fri, 14 Jan 2005 18:05:39 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08CBF43D39 for ; Fri, 14 Jan 2005 18:05:39 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0EI5ath025205; Fri, 14 Jan 2005 10:05:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0EI5Y5P025204; Fri, 14 Jan 2005 10:05:34 -0800 (PST) (envelope-from obrien) Date: Fri, 14 Jan 2005 10:05:34 -0800 From: "David O'Brien" To: Eirik ?verby Message-ID: <20050114180534.GA12260@dragon.nuxi.com> References: <41E31103.1040003@anduin.net> <20050114002254.GC29445@dragon.nuxi.com> <41E7D834.7080505@anduin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E7D834.7080505@anduin.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: asr on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:05:39 -0000 On Fri, Jan 14, 2005 at 03:33:24PM +0100, Eirik ?verby wrote: > David O'Brien wrote: > >On Tue, Jan 11, 2005 at 12:34:27AM +0100, Eirik ?verby wrote: > >>Daring as I am, here's another attempt at having someone look into the > >>asr driver and why it doesn't work on amd64. > >>I have such a Zero-Channel RAID card laying around collecting dust, > >>whereas it was planned installed in a server here long time ago. > >> > >>I know Scott Long looked into it long ago, and he seems to have been the > >>last one to touch the driver. He indicated a few months ago that he had > >>little time; perhaps things look brighter now that 5.3 is out? > >> > >>I'll cross-post to -current/-stable in a few days if I don't hear > >>anything.. > > > >NO need to cross post. Unless you see a statement otherwise -- nothing > >has changed. eBay a *real* RAID controller. ;-)) > > Sorry. Already done.. And for the record, this *is* a "real" RAID > controller; .. > It's a Ultra320 SCSI RAID controller card, used by many Tyan high-end > Opteron motherboards. Zero-channel RAID controllers perform below a full-fledged RAID controllers. > it's a real pity noone cares about upgrading the driver. Its not a "don't care" issue -- if you investigated the driver you'd realize how difficult it is. It wasn't until just reciently that Linux managed to support these RAID cards in the 64-bit kernel. That's over 2 years since the first AMD64 Linux was released (much less beta's etc...) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:09:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42A0D16A4CE; Fri, 14 Jan 2005 18:09:41 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B86BF43D1D; Fri, 14 Jan 2005 18:09:40 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0EI9dR4025293; Fri, 14 Jan 2005 10:09:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0EI9doL025291; Fri, 14 Jan 2005 10:09:39 -0800 (PST) (envelope-from obrien) Date: Fri, 14 Jan 2005 10:09:39 -0800 From: "David O'Brien" To: Kris Kennaway Message-ID: <20050114180939.GB12260@dragon.nuxi.com> References: <200501140709.j0E79NTA046894@repoman.freebsd.org> <20050114131536.GA41709@xor.obsecurity.org> <20050114132433.GA97735@VARK.MIT.EDU> <20050114132829.GA42958@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050114132829.GA42958@xor.obsecurity.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: freebsd-amd64@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/msun/alpha fenv.h src/lib/msun/amd64 fenv.h src/lib/msun/arm fenv.h src/lib/msun/i387 fenv.h src/lib/msun/ia64 fenv.h src/lib/msun/powerpc fenv.h src/lib/msun/sparc64 fenv.h X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:09:41 -0000 On Fri, Jan 14, 2005 at 05:28:29AM -0800, Kris Kennaway wrote: > On Fri, Jan 14, 2005 at 08:24:33AM -0500, David Schultz wrote: > > On Fri, Jan 14, 2005, Kris Kennaway wrote: > > > On Fri, Jan 14, 2005 at 07:09:23AM +0000, David Schultz wrote: > > > > das 2005-01-14 07:09:23 UTC ... > > > > Log: > > > > Mark all inline asms that read the floating-point control or status > > > > registers as volatile. Instructions that *wrote* to FP state were > > > > already marked volatile, but apparently gcc has license to move > > > > non-volatile asms past volatile asms. This broke amd64's feupdateenv > > > > at -O2 due to a WAR conflict between fnstsw and fldenv there. > > > > > > Do you think this is likely to the cause of the build failures > > > reported with a number of ports when world is compiled with -O2 > > > (i.e. does the feupdateenv failure cascade to other commonly-used > > > parts of the code)? > > > > No, this would lead to a runtime failure, and I would be surprised > > if very many ports use fenv.h anyway. > > OK :-( > > Someone needs to revert amd64 back to using -O in the meantime, then. I can't tell if you're talking about a need to move back to -O is for /usr/ports or /usr/src? If for /usr/ports, we should just change ports/Mk/bsd.port.mk to s/-O2/-O/ on AMD64? If we move back to -O in /usr/src we'll never get all the issues found and ironed out. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:33:36 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 963DB16A4CE; Fri, 14 Jan 2005 18:33:36 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A45543D54; Fri, 14 Jan 2005 18:33:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3F80551462; Fri, 14 Jan 2005 10:33:35 -0800 (PST) Date: Fri, 14 Jan 2005 10:33:35 -0800 From: Kris Kennaway To: freebsd-amd64@FreeBSD.ORG Message-ID: <20050114183335.GA22659@xor.obsecurity.org> References: <200501140709.j0E79NTA046894@repoman.freebsd.org> <20050114131536.GA41709@xor.obsecurity.org> <20050114132433.GA97735@VARK.MIT.EDU> <20050114132829.GA42958@xor.obsecurity.org> <20050114180939.GB12260@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <20050114180939.GB12260@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG cc: Kris Kennaway Subject: Re: cvs commit: src/lib/msun/alpha fenv.h src/lib/msun/amd64 fenv.h src/lib/msun/arm fenv.h src/lib/msun/i387 fenv.h src/lib/msun/ia64 fenv.h src/lib/msun/powerpc fenv.h src/lib/msun/sparc64 fenv.h X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:33:36 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 14, 2005 at 10:09:39AM -0800, David O'Brien wrote: > On Fri, Jan 14, 2005 at 05:28:29AM -0800, Kris Kennaway wrote: > > On Fri, Jan 14, 2005 at 08:24:33AM -0500, David Schultz wrote: > > > On Fri, Jan 14, 2005, Kris Kennaway wrote: > > > > On Fri, Jan 14, 2005 at 07:09:23AM +0000, David Schultz wrote: > > > > > das 2005-01-14 07:09:23 UTC > ... > > > > > Log: > > > > > Mark all inline asms that read the floating-point control or st= atus > > > > > registers as volatile. Instructions that *wrote* to FP state w= ere > > > > > already marked volatile, but apparently gcc has license to move > > > > > non-volatile asms past volatile asms. This broke amd64's feupd= ateenv > > > > > at -O2 due to a WAR conflict between fnstsw and fldenv there. > > > >=20 > > > > Do you think this is likely to the cause of the build failures > > > > reported with a number of ports when world is compiled with -O2 > > > > (i.e. does the feupdateenv failure cascade to other commonly-used > > > > parts of the code)? > > >=20 > > > No, this would lead to a runtime failure, and I would be surprised > > > if very many ports use fenv.h anyway. > >=20 > > OK :-( > >=20 > > Someone needs to revert amd64 back to using -O in the meantime, then. >=20 > I can't tell if you're talking about a need to move back to -O is for > /usr/ports or /usr/src? src. This was discussed on current@ in December; some amd64 ports do not build when world is compiled with -O2 (even if the port itself is built with -O), but build when world is recompiled with -O. There was some analysis of the problem cause in the mailing list thread (which you were CC'ed on), but no conclusion. > If for /usr/ports, we should just change ports/Mk/bsd.port.mk to > s/-O2/-O/ on AMD64? If we move back to -O in /usr/src we'll never > get all the issues found and ironed out. The issues have been reported, so someone either needs to fix them or apply the workaround of reverting src to -O until the former can take place. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6BB+Wry0BWjoQKURAsdzAJ9kLkQ/y9GfBNLUrkNTwLxDUfE/+gCgxL5S 7fkH1m0BFjzw5rXFbEiUQXA= =p12H -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:41:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D48AD16A4CE; Fri, 14 Jan 2005 18:41:21 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A16ED43D1F; Fri, 14 Jan 2005 18:41:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0EIfKXB001529; Fri, 14 Jan 2005 10:41:20 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0EIfJ0Z001528; Fri, 14 Jan 2005 10:41:19 -0800 (PST) (envelope-from obrien) Date: Fri, 14 Jan 2005 10:41:19 -0800 From: "David O'Brien" To: Kris Kennaway Message-ID: <20050114184119.GA1414@dragon.nuxi.com> References: <200501140709.j0E79NTA046894@repoman.freebsd.org> <20050114131536.GA41709@xor.obsecurity.org> <20050114132433.GA97735@VARK.MIT.EDU> <20050114132829.GA42958@xor.obsecurity.org> <20050114180939.GB12260@dragon.nuxi.com> <20050114183335.GA22659@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050114183335.GA22659@xor.obsecurity.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG cc: freebsd-amd64@FreeBSD.ORG Subject: Re: cvs commit: src/lib/msun/alpha fenv.h src/lib/msun/amd64 fenv.h src/lib/msun/arm fenv.h src/lib/msun/i387 fenv.h src/lib/msun/ia64 fenv.h src/lib/msun/powerpc fenv.h src/lib/msun/sparc64 fenv.h X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:41:22 -0000 On Fri, Jan 14, 2005 at 10:33:35AM -0800, Kris Kennaway wrote: > On Fri, Jan 14, 2005 at 10:09:39AM -0800, David O'Brien wrote: > > On Fri, Jan 14, 2005 at 05:28:29AM -0800, Kris Kennaway wrote: > > > Someone needs to revert amd64 back to using -O in the meantime, then. > > > > I can't tell if you're talking about a need to move back to -O is for > > /usr/ports or /usr/src? > > src. This was discussed on current@ in December; some amd64 ports do > not build when world is compiled with -O2 (even if the port itself is > built with -O), but build when world is recompiled with -O. > > There was some analysis of the problem cause in the mailing list > thread (which you were CC'ed on), but no conclusion. That thread got cross-posted and then so hijacked I couldn't follow it at all. Is this something you could summerize. Or start a fresh tread to freebsd-amd64? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:42:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67C7116A4CE; Fri, 14 Jan 2005 18:42:56 +0000 (GMT) Received: from mail.jrv.org (adsl-70-243-84-14.dsl.austtx.swbell.net [70.243.84.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9979E43D46; Fri, 14 Jan 2005 18:42:53 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) by fearless.housenet.jrv (8.13.1/8.13.1) with ESMTP id j0E8W7uU010779; Fri, 14 Jan 2005 02:32:07 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41E78387.2090808@jrv.org> Date: Fri, 14 Jan 2005 02:32:07 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050103231847.GJ22456@philemon.caltech.edu> <20050114050906.GE29445@dragon.nuxi.com> In-Reply-To: <20050114050906.GE29445@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org cc: Paul Allen Subject: Re: 5-STABLE or -CURRENT? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:42:56 -0000 David O'Brien wrote: >On Mon, Jan 03, 2005 at 03:18:47PM -0800, Paul Allen wrote: > > >>I had experienced some issues with 5.3-Release vis-a-vis bad >>bounce buffer panics. >> >>Am I correct in my read of the mailing list that 5.3-Stable >>Resolves these issues? >> >> > >Yes. > > I have never succeeded in getting the bge NIC on the Tyan K8W to work with more than 4GB of RAM in 5-stable (5.2.1 worked OK). The system seems fine booting single-user with 8 GB of RAM using the twa disk driver, but the system locks up as soon as I do "sh /etc/netstart", at the point that the bge driver should print that the Ethernet link is established. From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 18:46:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCE2516A4CE for ; Fri, 14 Jan 2005 18:46:19 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B4F943D2F for ; Fri, 14 Jan 2005 18:46:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D3629513CE; Fri, 14 Jan 2005 10:46:18 -0800 (PST) Date: Fri, 14 Jan 2005 10:46:18 -0800 From: Kris Kennaway To: freebsd-amd64@FreeBSD.ORG Message-ID: <20050114184618.GA22896@xor.obsecurity.org> References: <200501140709.j0E79NTA046894@repoman.freebsd.org> <20050114131536.GA41709@xor.obsecurity.org> <20050114132433.GA97735@VARK.MIT.EDU> <20050114132829.GA42958@xor.obsecurity.org> <20050114180939.GB12260@dragon.nuxi.com> <20050114183335.GA22659@xor.obsecurity.org> <20050114184119.GA1414@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <20050114184119.GA1414@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i Subject: Ports broken with -O2 world (Re: cvs commit: src/lib/msun/alpha fenv.h src/lib/msun/amd64 fenv.h src/lib/msun/arm fenv.h src/lib/msun/i387 fenv.h src/lib/msun/ia64 fenv.h src/lib/msun/powerpc fenv.h src/lib/msun/sparc64 fenv.h) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:46:20 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 14, 2005 at 10:41:19AM -0800, David O'Brien wrote: > On Fri, Jan 14, 2005 at 10:33:35AM -0800, Kris Kennaway wrote: > > On Fri, Jan 14, 2005 at 10:09:39AM -0800, David O'Brien wrote: > > > On Fri, Jan 14, 2005 at 05:28:29AM -0800, Kris Kennaway wrote: > > > > Someone needs to revert amd64 back to using -O in the meantime, the= n. > > >=20 > > > I can't tell if you're talking about a need to move back to -O is for > > > /usr/ports or /usr/src? > >=20 > > src. This was discussed on current@ in December; some amd64 ports do > > not build when world is compiled with -O2 (even if the port itself is > > built with -O), but build when world is recompiled with -O. > >=20 > > There was some analysis of the problem cause in the mailing list > > thread (which you were CC'ed on), but no conclusion. >=20 > That thread got cross-posted and then so hijacked I couldn't follow it at > all. Is this something you could summerize. Or start a fresh tread to > freebsd-amd64? The relevant messages are: Message-ID: <20041214062738.GA78138@xor.obsecurity.org> Message-ID: <20041210161650.I63382@carver.gumbysoft.com> Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6BN6Wry0BWjoQKURAiUZAJ4zGO6PpB+jM7vaI3lcCiKGlLaQWgCdF4WO gvsEhdDCEr6pcpAB0BiTxEI= =0huY -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 14 21:39:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 845EA16A4CE; Fri, 14 Jan 2005 21:39:08 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 072A943D46; Fri, 14 Jan 2005 21:39:08 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0ELd7Jp069178; Fri, 14 Jan 2005 16:39:07 -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.1/8.13.1) with ESMTP id j0ELd6UG059936; Fri, 14 Jan 2005 16:39:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5602C7306E; Fri, 14 Jan 2005 16:39:07 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050114213907.5602C7306E@freebsd-current.sentex.ca> Date: Fri, 14 Jan 2005 16:39:07 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/649/Sun Jan 2 18:02:22 2005 clamav-milter version 0.80j on clamscanner3 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 21:39:08 -0000 TB --- 2005-01-14 21:04:26 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-14 21:04:26 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-01-14 21:04:26 - checking out the source tree TB --- 2005-01-14 21:04:26 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-01-14 21:04:26 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-14 21:10:03 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-14 21:10:03 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-01-14 21:10:03 - /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 [...] building static telnet library ranlib libtelnet.a ===> lib/libthr (all) cc -O2 -pipe -DPTHREAD_KERNEL -D_THREAD_SAFE -I/tinderbox/CURRENT/amd64/amd64/src/lib/libthr/../libc/include -I/tinderbox/CURRENT/amd64/amd64/src/lib/libthr/thread -I/tinderbox/CURRENT/amd64/amd64/src/lib/libthr/../../include -I/tinderbox/CURRENT/amd64/amd64/src/lib/libthr/../../libexec/rtld-elf -D_PTHREADS_INVARIANTS -g -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/CURRENT/amd64/amd64/src/lib/libthr/thread/thr_atfork.c In file included from /tinderbox/CURRENT/amd64/amd64/src/lib/libthr/thread/thr_private.h:72, from /tinderbox/CURRENT/amd64/amd64/src/lib/libthr/thread/thr_atfork.c:36: /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/sys/umtx.h: In function `umtx_wait': /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/sys/umtx.h:118: warning: passing arg 5 of `_umtx_op' discards qualifiers from pointer target type *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libthr. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-01-14 21:39:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-14 21:39:07 - ERROR: failed to build world TB --- 2005-01-14 21:39:07 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 01:40:18 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05E5416A4CE; Sat, 15 Jan 2005 01:40:18 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3AE243D3F; Sat, 15 Jan 2005 01:40:17 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IAC4NA03.RB8; Fri, 14 Jan 2005 17:40:22 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005011417434424492 ; Fri, 14 Jan 2005 17:43:44 -0800 From: "Vinod Kashyap" To: Michael Meltzer Date: Fri, 14 Jan 2005 17:40:12 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=-------39f297439f2974 Message-ID: cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: RE: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 01:40:18 -0000 This is a multi-part message in MIME format ---------39f297439f2974 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I tried reproducing the problem on both i386 and amd64, but could not. I installed 5.3 RELEASE, cvsuped to the tip of RELENG_5, re-built the kernel with twa integrated, and rebooted. The test systems booted just fine (off of 3ware controlled da0). I even tried replacing just the twa sources of 5.3 RELEASE with the twa sources from the tip of RELENG_5, and that worked fine too. All this, without even upgrading the firmware from 2.02.00.008 (which is bundled into 5.3 RELEASE sources). So, I am confused as to what might be happening. Could you give the attached patch a try? Just a hunch... > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer > Sent: Friday, January 14, 2005 6:03 AM > To: Vinod Kashyap > Cc: freebsd stable > Subject: Re: twa breakage on AMD64 with 9.1.5.2 > 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit > = > = > = > >Could you see if the driver is getting loaded? The driver prints > >the message: "3ware device driver for 9000 series storage = > controllers...". > > > >Did the new firmware get flashed? You can download the firmware > >from the 3ware website and flash it on the card using a DOS floppy. > >Alternatively, you can add 'options TWA_FLASH_FIRMWARE' to your > >kernel configuration file and rebuild the kernel. This should build > >the kernel/driver with the firmware bundled, and the firmware should > >automatically get downloaded the next time you reboot. > > > > > > > > > > = > > > I reloaded the new driver and rebuilt the kernel last night with the = > TWA_FLASH_FIRMWARE, Did not see the -D on the command line for the = > rebuild, the new firmware was not requested to load. I got the new = > firmware from 3ware and flashed it in, Still does not work. I = > also build = > a straight GENERIC Kernel, still no luck. Their is no error = > message that = > I saw and the versions number for the pieces did change so it = > the "new" = > stuff. I need to setup a serial console to capture the full messages, = > should have that on monday night. Thank You -mjm > = > = > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = > "freebsd-stable-unsubscribe@freebsd.org" > ---------39f297439f2974 Content-Type: application/octet-stream; name="twa_r5.diff" Content-Disposition: attachment; filename="twa_r5.diff" Content-Transfer-Encoding: base64 SW5kZXg6IHR3YV9mcmVlYnNkLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2hvbWUvbmN2 cy9zcmMvc3lzL2Rldi90d2EvdHdhX2ZyZWVic2QuYyx2CnJldHJpZXZpbmcgcmV2aXNpb24g MS43LjIuMgpkaWZmIC11IC1yMS43LjIuMiB0d2FfZnJlZWJzZC5jCi0tLSB0d2FfZnJlZWJz ZC5jCTExIEphbiAyMDA1IDAzOjAwOjQ4IC0wMDAwCTEuNy4yLjIKKysrIHR3YV9mcmVlYnNk LmMJMTUgSmFuIDIwMDUgMDE6MzM6NTYgLTAwMDAKQEAgLTI2MSwxNSArMjYxLDYgQEAKIAlz Yy0+dHdhX2J1c190YWcgPSBybWFuX2dldF9idXN0YWcoc2MtPnR3YV9pb19yZXMpOwogCXNj LT50d2FfYnVzX2hhbmRsZSA9IHJtYW5fZ2V0X2J1c2hhbmRsZShzYy0+dHdhX2lvX3Jlcyk7 CiAKLQkvKiBJbml0aWFsaXplIHRoZSBkcml2ZXIgZm9yIHRoaXMgY29udHJvbGxlci4gKi8K LQlpZiAoKGVycm9yID0gdHdhX3NldHVwKHNjKSkpIHsKLQkJdHdhX2ZyZWUoc2MpOwotCQly ZXR1cm4oZXJyb3IpOwotCX0KLQotCS8qIFByaW50IHNvbWUgaW5mb3JtYXRpb24gYWJvdXQg dGhlIGNvbnRyb2xsZXIgYW5kIGNvbmZpZ3VyYXRpb24uICovCi0JdHdhX2Rlc2NyaWJlX2Nv bnRyb2xsZXIoc2MpOwotCiAJLyogQWxsb2NhdGUgYW5kIGNvbm5lY3Qgb3VyIGludGVycnVw dC4gKi8KIAlyZXNfaWQgPSAwOwogCWlmICgoc2MtPnR3YV9pcnFfcmVzID0gYnVzX2FsbG9j X3Jlc291cmNlKHNjLT50d2FfYnVzX2RldiwgU1lTX1JFU19JUlEsCkBAIC0yODYsNiArMjc3 LDE1IEBACiAJCXJldHVybihFTlhJTyk7CiAJfQogCisJLyogSW5pdGlhbGl6ZSB0aGUgZHJp dmVyIGZvciB0aGlzIGNvbnRyb2xsZXIuICovCisJaWYgKChlcnJvciA9IHR3YV9zZXR1cChz YykpKSB7CisJCXR3YV9mcmVlKHNjKTsKKwkJcmV0dXJuKGVycm9yKTsKKwl9CisKKwkvKiBQ cmludCBzb21lIGluZm9ybWF0aW9uIGFib3V0IHRoZSBjb250cm9sbGVyIGFuZCBjb25maWd1 cmF0aW9uLiAqLworCXR3YV9kZXNjcmliZV9jb250cm9sbGVyKHNjKTsKKwogCS8qIENyZWF0 ZSB0aGUgY29udHJvbCBkZXZpY2UuICovCiAJc2MtPnR3YV9jdHJsX2RldiA9IG1ha2VfZGV2 KCZ0d2FfY2RldnN3LCBkZXZpY2VfZ2V0X3VuaXQoc2MtPnR3YV9idXNfZGV2KSwKIAkJCQkJ VUlEX1JPT1QsIEdJRF9PUEVSQVRPUiwgU19JUlVTUiB8IFNfSVdVU1IsCg== ---------39f297439f2974-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 02:29:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 186D016A4CE for ; Sat, 15 Jan 2005 02:29:45 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C376E43D2F for ; Sat, 15 Jan 2005 02:29:44 +0000 (GMT) (envelope-from mmontaseri@amcc.com) Received: from [10.66.12.100] (medi.amcc.com [10.66.12.100]) by hadar.amcc.com (Netscape Messaging Server 4.15) with ESMTP id IAC6XO01.XA6; Fri, 14 Jan 2005 18:29:48 -0800 Message-ID: <41E8800A.70005@amcc.com> Date: Fri, 14 Jan 2005 18:29:30 -0800 From: "Medi Montaseri" User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: amd64 and FreeBSD 5.2.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 02:29:45 -0000 Hi....I am having some problem porting my app to FreeBSD 5.2.1 on a amd64 and am wondering about the state of 5.2.1 before I dive into debugging.... FYI...my app works fine on 64 bit linux. My concerns are: 1- http://www.freebsd.org/releng/#schedule describes 5.2.1 as "FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported)." What do you mean by "not supported"....should I use 5.3 2- I do'nt see gdb(1) on the 5.2.1 ISOs. Was this never ported ? I have found gdb-6 but that requires libm.so.3 which is not available on 5.2.1.... stopped there as I was getting into pre-req recursive rat hole... If gdb was not made available, should I interpret this as 5.2.1 is not a formal release? 3- I don't see any traces of 5.2.1 on FreeBSD mirror sites... as though it was there and now its not... This is worring me....was there something about 5.2.1 that has disappeared from the face of Internet. Or is it the FreeBSD.org practice of pulling down previous releases....maybe a minor issue...right now I'm over reading too much. 4- My motherboard is actually a dual CPU using Intel EM64T (Extended Memory) but uname -m shows amd64.....I hope this ok... 5- My app is failing consistingly as follows... (gdb) bt #0 0x00000002007014d8 in find_symdef () from /libexec/ld-elf.so.1 #1 0x0000000200700d1b in _rtld_bind () from /libexec/ld-elf.so.1 #2 0x0000000200700755 in _rtld_bind_start () from /libexec/ld-elf.so.1 #3 0x0000000000000247 in ?? () #4 0x0000000000000004 in ?? () #5 0x0000000000000002 in ?? () #6 0x0000000200b73960 in RC5_version () from /lib/libcrypto.so.3 #7 0x0000000000000002 in ?? () #8 0x0000000000000206 in ?? () #9 0x0000000200718600 in ?? () #10 0x00000000000001d3 in ?? () #11 0x0000000200b30453 in ERR_get_state () from /lib/libcrypto.so.3 #12 0x0000000200b2fbe1 in ERR_put_error () from /lib/libcrypto.so.3 #13 0x0000000200b40192 in BIO_new_file () from /lib/libcrypto.so.3 #14 0x0000000200ae3277 in X509_load_cert_crl_file () from /lib/libcrypto.so.3 #15 0x0000000200ae2e9d in X509_LOOKUP_file () from /lib/libcrypto.so.3 I've seen some conversations on ld-elf.so.1 available at http://lists.freebsd.org/pipermail/freebsd-current/2004-February/021414.html Where Kenneth Merry at FreeBSD org concludes... So, it looks like find_symdef() is returning a bogus value for def, and NULL for defobj, which causes a NULL pointer deference at line 197. Does this look familiar to anyone? Since I've got a core dump, I can look at more things if anyone has anything they'd like to see. Ken -- So...anyone knows anything about this ld-elf.so.1 problem.... Thank you From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 03:00:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E792416A4CE for ; Sat, 15 Jan 2005 03:00:25 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B49F343D3F for ; Sat, 15 Jan 2005 03:00:25 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j0F30I66052240; Fri, 14 Jan 2005 19:00:18 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j0F30IG9052239; Fri, 14 Jan 2005 19:00:18 -0800 (PST) (envelope-from sgk) Date: Fri, 14 Jan 2005 19:00:18 -0800 From: Steve Kargl To: Medi Montaseri Message-ID: <20050115030018.GA52185@troutmask.apl.washington.edu> References: <41E8800A.70005@amcc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E8800A.70005@amcc.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: amd64 and FreeBSD 5.2.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 03:00:26 -0000 On Fri, Jan 14, 2005 at 06:29:30PM -0800, Medi Montaseri wrote: > > Hi....I am having some problem porting my app to FreeBSD 5.2.1 on a > amd64 and am wondering about the state of 5.2.1 before I dive into > debugging.... > FYI...my app works fine on 64 bit linux. > > My concerns are: > > 1- http://www.freebsd.org/releng/#schedule describes 5.2.1 as > "FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported)." > What do you mean by "not supported"....should I use 5.3 "not supported" means that if you have problems, then update to 5.3; otherwise don't expect help. > > 2- I do'nt see gdb(1) on the 5.2.1 ISOs. Was this never ported ? gdb is the debugger in 5.3. > I have found gdb-6 but that requires libm.so.3 which is not available on > 5.2.1.... Install 5.3. > stopped there as I was getting into pre-req recursive rat hole... > If gdb was not made available, should I interpret this as 5.2.1 is not a > formal release? Yes. > 4- My motherboard is actually a dual CPU using Intel EM64T (Extended > Memory) but uname -m shows amd64.....I hope this ok... Yes. > I've seen some conversations on ld-elf.so.1 available at > http://lists.freebsd.org/pipermail/freebsd-current/2004-February/021414.html > Where Kenneth Merry at FreeBSD org concludes... A year old discussion is probably not relevant here. Do yourself a big favor and upgrade to 5.3. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 04:13:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E29D16A4CF for ; Sat, 15 Jan 2005 04:13:06 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B459043D31 for ; Sat, 15 Jan 2005 04:13:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9507A5145A; Fri, 14 Jan 2005 20:13:04 -0800 (PST) Date: Fri, 14 Jan 2005 20:13:04 -0800 From: Kris Kennaway To: Medi Montaseri Message-ID: <20050115041304.GA78790@xor.obsecurity.org> References: <41E8800A.70005@amcc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <41E8800A.70005@amcc.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: amd64 and FreeBSD 5.2.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 04:13:06 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 14, 2005 at 06:29:30PM -0800, Medi Montaseri wrote: >=20 > Hi....I am having some problem porting my app to FreeBSD 5.2.1 on a=20 > amd64 and am wondering about the state of 5.2.1 before I dive into=20 > debugging.... > FYI...my app works fine on 64 bit linux. >=20 > My concerns are: >=20 > 1- http://www.freebsd.org/releng/#schedule describes 5.2.1 as > "FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported)." > What do you mean by "not supported"....should I use 5.3 Absolutely, yes. There's no good reason to run 5.2.1 on amd64. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6JhQWry0BWjoQKURAvPaAJ9WPTp/vZjr+MTS/FfIu5pDx9kaHACgvOkL rkmK1kjmsOy9JdZ27V7pM1Q= =ua2z -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 08:20:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19E7516A4CE; Sat, 15 Jan 2005 08:20:00 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFE0343D1D; Sat, 15 Jan 2005 08:19:58 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0F8JkhF012722 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sat, 15 Jan 2005 19:19:47 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <282504B0-66CE-11D9-82BD-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Sat, 15 Jan 2005 19:19:20 +1100 To: "Vinod Kashyap" X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.2 required=6.5 tests=ALL_TRUSTED,J_CHICKENPOX_34 autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with 9.1.5.2 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 08:20:00 -0000 Hello On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: > > I tried reproducing the problem on both i386 and amd64, > but could not. I installed 5.3 RELEASE, cvsuped to the > tip of RELENG_5, re-built the kernel with twa integrated, > and rebooted. The test systems booted just fine (off of > 3ware controlled da0). I even tried replacing just the > twa sources of 5.3 RELEASE with the twa sources from the > tip of RELENG_5, and that worked fine too. All this, > without even upgrading the firmware from 2.02.00.008 (which > is bundled into 5.3 RELEASE sources). So, I am confused as > to what might be happening. > > Could you give the attached patch a try? Just a hunch... > Here is what the screen look like: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #2: Sun Nov 28 13:39:08 EST 2004 avenardj@server3.private.hydrix.com:/usr/obj/usr/src/sys/AMD64 ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2190.63-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1073676288 (1023 MB) avail memory = 1025294336 (977 MB) MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci3: at device 6.0 (no driver attached) fxp0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:29:c0:30 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:29:c0:b0 bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 miibus2: on bge1 brgphy1: on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:29:c0:b1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.00.000 twa0: <3ware 9000 series Storage Controller> port 0x9800-0x98ff mem 0xfb800000-0xfbffffff,0xfc6ffc00-0xfc6ffcff irq 29 at device 1.0 on pci1 From there it just hangs... The drive activity LED will be lit for about 10s and after that goes off. The more it goes, the more I'm thinking of reverting to i386 mode, the amd64 just keeps crashing about once a fortnight. Jean-Yves --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 15:12:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B11416A4CE for ; Sat, 15 Jan 2005 15:12:16 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC34943D1D for ; Sat, 15 Jan 2005 15:12:15 +0000 (GMT) (envelope-from archive.it@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so160232rne for ; Sat, 15 Jan 2005 07:12:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=J6/zt7aGLzIzSVn50UtXBVe6lx6z+Tcl34A3zcPVCHYOym01ys9MfjKiDXy73jlrJyi5pILBuYbeG5Zc0Hrk8aJxNOTOg7XK0/sO45VFB8QCrF6+qRrLuStCKcjWHxh1WQh3fkjAmEUtcecL9ZAgix8cyF2F1FVkhcqKGfHYbzc= Received: by 10.38.99.58 with SMTP id w58mr101758rnb; Sat, 15 Jan 2005 07:12:15 -0800 (PST) Received: by 10.39.2.26 with HTTP; Sat, 15 Jan 2005 07:12:15 -0800 (PST) Message-ID: <64559708050115071264c3754@mail.gmail.com> Date: Sat, 15 Jan 2005 23:12:15 +0800 From: YEDIrk To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Please help about AIC-7902W on TYan S2882. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: YEDIrk List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 15:12:16 -0000 We buyed a dual Opteron 246 server used TYan S2882 integrated Adaptec AIC7902W Dual Channel U320 SCSI controller. When we install FreeBSD/AMD64 5.3 release on this machine, FreeBSD will DUMP CARD STATUS while probe SCSI device. Is there anyone use TYan S2882 or AIC7902W ? Thanks very much. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 17:22:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2231616A4CE; Sat, 15 Jan 2005 17:22:01 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7798143D58; Sat, 15 Jan 2005 17:22:00 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IADC8S00.IFP; Sat, 15 Jan 2005 09:22:04 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005011509244606266 ; Sat, 15 Jan 2005 09:24:46 -0800 From: "Vinod Kashyap" To: Jean-Yves Avenard Date: Sat, 15 Jan 2005 09:21:56 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: RE: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 17:22:01 -0000 You seem to running twa version 2.50.00.000. This is the driver prior to the recent update. Do you see the hang even with this? The latest version is 2.50.02.011. > -----Original Message----- > From: Jean-Yves Avenard [mailto:jean-yves.avenard@hydrix.com] > Sent: Saturday, January 15, 2005 12:19 AM > To: Vinod Kashyap > Cc: freebsd-amd64@FreeBSD.ORG; freebsd stable; Michael Meltzer > Subject: Re: twa breakage on AMD64 with 9.1.5.2 > 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit > = > = > Hello > = > On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: > = > > > > I tried reproducing the problem on both i386 and amd64, > > but could not. I installed 5.3 RELEASE, cvsuped to the > > tip of RELENG_5, re-built the kernel with twa integrated, > > and rebooted. The test systems booted just fine (off of > > 3ware controlled da0). I even tried replacing just the > > twa sources of 5.3 RELEASE with the twa sources from the > > tip of RELENG_5, and that worked fine too. All this, > > without even upgrading the firmware from 2.02.00.008 (which > > is bundled into 5.3 RELEASE sources). So, I am confused as > > to what might be happening. > > > > Could you give the attached patch a try? Just a hunch... > > > = > Here is what the screen look like: > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, = > 1993, 1994 > The Regents of the University of California. All rights = > reserved. > FreeBSD 5.3-STABLE #2: Sun Nov 28 13:39:08 EST 2004 > avenardj@server3.private.hydrix.com:/usr/obj/usr/src/sys/AMD64 > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 248 (2190.63-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0xf5a Stepping =3D 10 > = > Features=3D0x78bfbff ,MTRR,PGE, > MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=3D0xe0500800 > real memory =3D 1073676288 (1023 MB) > avail memory =3D 1025294336 (977 MB) > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 6.0 on pci0 > pci3: on pcib1 > ohci0: mem = > 0xfeafc000-0xfeafcfff irq 19 > at device 0.0 on pci3 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem = > 0xfeafd000-0xfeafdfff irq 19 > at device 0.1 on pci3 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > pci3: at device 6.0 (no driver attached) > fxp0: port 0xbc00-0xbc3f mem > 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on > pci3 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:e0:81:29:c0:30 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port > 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.2 (no driver attached) > pci0: at device 7.3 (no driver attached) > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > ahd0: port > 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device > 6.0 on pci2 > ahd0: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel A, SCSI Id=3D7, PCI-X 67-100Mhz, 512 SCBs > ahd1: port > 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device > 6.1 on pci2 > ahd1: [GIANT-LOCKED] > aic7902: Ultra320 Wide Channel B, SCSI Id=3D7, PCI-X 67-100Mhz, 512 SCBs > bge0: mem > 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on > pci2 > miibus1: on bge0 > brgphy0: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:e0:81:29:c0:b0 > bge1: mem > 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on > pci2 > miibus2: on bge1 > brgphy1: on miibus2 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:e0:81:29:c0:b1 > pci0: at device 10.1 = > (no driver > attached) > pcib3: at device 11.0 on pci0 > pci1: on pcib3 > 3ware device driver for 9000 series storage controllers, version: > 2.50.00.000 > twa0: <3ware 9000 series Storage Controller> port 0x9800-0x98ff mem > 0xfb800000-0xfbffffff,0xfc6ffc00-0xfc6ffcff irq 29 at device 1.0 on > pci1 > = > = > From there it just hangs... > The drive activity LED will be lit for about 10s and after that goes > off. > = > The more it goes, the more I'm thinking of reverting to i386 mode, the > amd64 just keeps crashing about once a fortnight. > = > Jean-Yves > = > = > --- > Jean-Yves Avenard > Hydrix Pty Ltd - Embedding the net > www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 > VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com > = > From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 20:41:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DF8416A4CE; Sat, 15 Jan 2005 20:41:19 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B4DC43D49; Sat, 15 Jan 2005 20:41:18 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0FKf6VN018166 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 16 Jan 2005 07:41:08 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Sun, 16 Jan 2005 07:40:41 +1100 To: Vinod Kashyap X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with 9.1.5.2 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 20:41:19 -0000 On 16/01/2005, at 4:21 AM, Vinod Kashyap wrote: > > You seem to running twa version 2.50.00.000. This is the > driver prior to the recent update. Do you see the hang > even with this? The latest version is 2.50.02.011. > What do you mean even with this? Oops I see ; sorry. I just wanted to point where the hang was, the dump I posted was made with a Kernel compiled back in November (still from RELENG_5). Obviously I can't give you a dump of the new kernel has when booting the kernel compiler last Friday I lost the access to it I haven't had the chance to try your patch yet; i don't have physical access to the server until Monday and i don't want to take the risk of starting a kernel that will hang. --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 22:41:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B0B616A4E3 for ; Sat, 15 Jan 2005 22:41:13 +0000 (GMT) Received: from macrbg.com (macrbg.com [64.62.240.79]) by mx1.FreeBSD.org (Postfix) with SMTP id 2785C43D39 for ; Sat, 15 Jan 2005 22:41:13 +0000 (GMT) (envelope-from rbg@macrbg.com) Received: from 70.112.64.143 ([70.112.64.143]) by macrbg.com for ; Sat, 15 Jan 2005 14:41:04 -0800 Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <8B0A5827-6746-11D9-8923-000A956F2DD2@macrbg.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@FreeBSD.ORG From: Robert Gordon Date: Sat, 15 Jan 2005 16:41:06 -0600 X-Mailer: Apple Mail (2.619) Subject: iWill ZMAXDP. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 22:41:13 -0000 does anyone have this working yet? (http://www.iwill.net/product_2.asp?p_id=36) -- If i disable ACPI it boots the amd64 kernel however sysctl only shows one CPU. any pointers would be cool. Robert.. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 15 22:52:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C2F916A4CE for ; Sat, 15 Jan 2005 22:52:00 +0000 (GMT) Received: from macrbg.com (macrbg.com [64.62.240.79]) by mx1.FreeBSD.org (Postfix) with SMTP id CC27A43D2D for ; Sat, 15 Jan 2005 22:51:59 +0000 (GMT) (envelope-from rbg@macrbg.com) Received: from 70.112.64.143 ([70.112.64.143]) by macrbg.com for ; Sat, 15 Jan 2005 14:51:48 -0800 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <8B0A5827-6746-11D9-8923-000A956F2DD2@macrbg.com> References: <8B0A5827-6746-11D9-8923-000A956F2DD2@macrbg.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0B8AB157-6748-11D9-8923-000A956F2DD2@macrbg.com> Content-Transfer-Encoding: 7bit From: Robert Gordon Date: Sat, 15 Jan 2005 16:51:51 -0600 To: freebsd-amd64@FreeBSD.ORG X-Mailer: Apple Mail (2.619) Subject: Re: iWill ZMAXDP. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 22:52:00 -0000 how about some more info ? This is stock FreeBSD 5.3 with SMP turned on. It hangs after the GEOM: messages.. On Jan 15, 2005, at 4:41 PM, Robert Gordon wrote: > > does anyone have this working yet? > (http://www.iwill.net/product_2.asp?p_id=36) > > -- > > If i disable ACPI it boots the amd64 kernel however > sysctl only shows one CPU. > > any pointers would be cool. > > Robert.. > > _______________________________________________ > 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" >