From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 5 23:10:25 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBE3616A554 for ; Sun, 5 Dec 2004 23:10:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99B7D43D6B for ; Sun, 5 Dec 2004 23:10:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB5NAPlI016975 for ; Sun, 5 Dec 2004 23:10:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB5NAPru016974; Sun, 5 Dec 2004 23:10:25 GMT (envelope-from gnats) Resent-Date: Sun, 5 Dec 2004 23:10:25 GMT Resent-Message-Id: <200412052310.iB5NAPru016974@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Sean McNeil Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE46816A4D7 for ; Sun, 5 Dec 2004 23:07:00 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1C6543D2D for ; Sun, 5 Dec 2004 23:07:00 +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 iB5N6wjU015886 for ; Sun, 5 Dec 2004 23:06:58 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id iB5N6wWs015885; Sun, 5 Dec 2004 23:06:58 GMT (envelope-from nobody) Message-Id: <200412052306.iB5N6wWs015885@www.freebsd.org> Date: Sun, 5 Dec 2004 23:06:58 GMT From: Sean McNeil To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/74747: System panic on shutdown when process will not die 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, 05 Dec 2004 23:10:26 -0000 >Number: 74747 >Category: amd64 >Synopsis: System panic on shutdown when process will not die >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 05 23:10:25 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Sean McNeil >Release: 6.0-CURRENT >Organization: Sean McNeil Consulting >Environment: FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #19: Sun Dec 5 13:42:35 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 >Description: slapd will not properly shutdown /usr/local/etc/rc.d/slapd.sh stop. During shutdown (ctrl-alt-delete), this causes the pid to be displayed many times, then a long pause, then a panic. The following is output: Dec 5 14:43:31 server syslogd: kernel boot file is /boot/kernel/kernel Dec 5 14:43:31 server kernel: interrupt total Dec 5 14:43:31 server kernel: irq1: atkbd0 203 Dec 5 14:43:31 server kernel: irq0: clk 486756 Dec 5 14:43:31 server kernel: irq4: sio0 6 Dec 5 14:43:31 server kernel: irq8: rtc 31172 Dec 5 14:43:31 server kernel: irq14: ata0 777 Dec 5 14:43:31 server kernel: irq15: ata1 172 Dec 5 14:43:31 server kernel: irq16: re0 628 Dec 5 14:43:31 server kernel: irq17: fwohci0 1 Dec 5 14:43:31 server kernel: irq19: dc0 2 Dec 5 14:43:31 server kernel: irq20: atapci0 11332 Dec 5 14:43:31 server kernel: irq21: uhci0 uhci1+ 56 Dec 5 14:43:31 server kernel: Total 531105 Dec 5 14:43:31 server kernel: KDB: stack backtrace: Dec 5 14:43:31 server kernel: hardclock() at hardclock+0x21b Dec 5 14:43:31 server kernel: intr_execute_handlers() at intr_execute_handlers+0x102 Dec 5 14:43:31 server kernel: lapic_handle_intr() at lapic_handle_intr+0x21 Dec 5 14:43:31 server kernel: Xapic_isr1() at Xapic_isr1+0x7d Dec 5 14:43:31 server kernel: --- interrupt, rip = 0xffffffff80486616, rsp = 0xffffffffb188dba0, rbp = 0xffffffffb188dbb0 --- Dec 5 14:43:31 server kernel: acpi_cpu_c1() at acpi_cpu_c1+0x6 Dec 5 14:43:31 server kernel: acpi_cpu_idle() at acpi_cpu_idle+0x178 Dec 5 14:43:31 server kernel: idle_proc() at idle_proc+0x9d Dec 5 14:43:31 server kernel: fork_exit() at fork_exit+0x8f Dec 5 14:43:31 server kernel: fork_trampoline() at fork_trampoline+0xe Dec 5 14:43:31 server kernel: --- trap 0, rip = 0, rsp = 0xffffffffb188dd00, rbp = 0 --- Dec 5 14:43:31 server kernel: KDB: enter: watchdog timeout >How-To-Repeat: Install openldap22-sasl-server and start it. Perform a ctrl-alt-delete. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 11:02:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A651016A4CE for ; Mon, 6 Dec 2004 11:02:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 630E043D1F for ; Mon, 6 Dec 2004 11:02:19 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB6B2Jkh027312 for ; Mon, 6 Dec 2004 11:02:19 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB6B2ISG027306 for freebsd-amd64@freebsd.org; Mon, 6 Dec 2004 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Dec 2004 11:02:18 GMT Message-Id: <200412061102.iB6B2ISG027306@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, 06 Dec 2004 11:02:19 -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/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/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 12 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/04] amd64/74669 amd64 The port math/octave is marked BROKEN on 9 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 13:15:46 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F1A316A4CE; Mon, 6 Dec 2004 13:15:46 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A51C43D6A; Mon, 6 Dec 2004 13:15:46 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB6DFkds048741; Mon, 6 Dec 2004 13:15:46 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB6DFkTZ048737; Mon, 6 Dec 2004 13:15:46 GMT (envelope-from ceri) Date: Mon, 6 Dec 2004 13:15:46 GMT From: Ceri Davies Message-Id: <200412061315.iB6DFkTZ048737@freefall.freebsd.org> To: ceri@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 13:15:46 -0000 Synopsis: The port math/octave is marked BROKEN on amd64 Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: ceri Responsible-Changed-When: Mon Dec 6 13:14:49 GMT 2004 Responsible-Changed-Why: This is a ports PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=74669 From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 13:50:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4528616A4CE for ; Mon, 6 Dec 2004 13:50:43 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDA5243D48 for ; Mon, 6 Dec 2004 13:50:42 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (jose.freesurf.fr [212.43.206.13]) by fidel.freesurf.fr (Postfix) with SMTP id 619D52A6DAB for ; Mon, 6 Dec 2004 14:50:41 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by jose.freesurf.fr with HTTP; Mon, 6 Dec 2004 14:50:41 +0100 (CET) Message-ID: <59730.134.214.201.98.1102341041.squirrel@jose.freesurf.fr> Date: Mon, 6 Dec 2004 14:50:41 +0100 (CET) From: To: "amd64 " X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Kernel compilation problem 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, 06 Dec 2004 13:50:43 -0000 Hi all! I'm very new to FreeBSD (indeed I ran it since one week) and I need to compile my kernel so that some patches will apply correctly. So I made all the process I type make depends && make and I've got sth like this: ../../../i386/i386/genassym.c:216:error: storage size of BC32SELw0 isn't known I've got that for all BC32 and furthermore on line 214 for KSPEL :( So the compilation stops on an error code. Does anyone got a clue? Many thx :) From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 14:23:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94F5316A4CF for ; Mon, 6 Dec 2004 14:23:55 +0000 (GMT) Received: from ns3.bsn.com (ns3.bsn.com [194.221.32.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4ACD43D5E for ; Mon, 6 Dec 2004 14:23:54 +0000 (GMT) (envelope-from ewwinter@ns3.bsn.com) Received: from ns3.bsn.com (localhost [127.0.0.1]) by ns3.bsn.com (8.12.10/8.12.10) with ESMTP id iB6ENrpm004232 for ; Mon, 6 Dec 2004 15:23:53 +0100 (CET) (envelope-from ewwinter@ns3.bsn.com) Received: (from ewwinter@localhost) by ns3.bsn.com (8.12.10/8.12.10/Submit) id iB6ENqUt004231 for freebsd-amd64@freebsd.org; Mon, 6 Dec 2004 15:23:52 +0100 (CET) (envelope-from ewwinter) Date: Mon, 6 Dec 2004 15:23:52 +0100 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20041206152352.A4053@ns3.bsn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Phone: + 49-89-3075-6800 Organization: BSn -- Basis Systeme netzwerk X-Operating-System: FreeBSD ns3.bsn.com 4.9-STABLE FreeBSD 4.9-STABLE Subject: network card X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 14:23:55 -0000 Well I would like to ask "what ntwork card" is working with amd64 FreeBSD, that is without any hassles. I try the sk one and it still has the problem of putting out the same message: sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) it is a ASUS A8V Deluxe board with the lan omboard. 5.3_STABLE is the version I'm running. I tried the Netgear Gigabyte PCI-Adapter GA311 but it will hang at times and so there is no other solution as to use the three finger salute (alt-ctrl-del) to reboot. Funny is that it ran for a few days and then all of a sudden it hung. Any sugestions what card would work with this MB and amd64? Ernst -- Ernst W. Winter Basis Systeme netzwerk phone: +49 89 692 8120 Brecherspitzstr. 8/Rgb. fax: +49 89 692 8150 D-81541 Muenchen, Germany http://www.bsn.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 15:02:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B31316A4CE for ; Mon, 6 Dec 2004 15:02:32 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C65643D41 for ; Mon, 6 Dec 2004 15:02:31 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (arlette.freesurf.fr [212.43.206.12]) by fidel.freesurf.fr (Postfix) with SMTP id CC9C42A6FF2 for ; Mon, 6 Dec 2004 16:02:30 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by arlette.freesurf.fr with HTTP; Mon, 6 Dec 2004 16:02:30 +0100 (CET) Message-ID: <24642.134.214.201.98.1102345350.squirrel@arlette.freesurf.fr> Date: Mon, 6 Dec 2004 16:02:30 +0100 (CET) From: To: X-Priority: 3 In-Reply-To: <20041206152352.A4053@ns3.bsn.com> References: <20041206152352.A4053@ns3.bsn.com> Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: network card 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, 06 Dec 2004 15:02:32 -0000 > Well I would like to ask "what ntwork card" is working with amd64 > FreeBSD, that is without any hassles. I try the sk one and it still has > the problem of putting out the same message: > > sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) > > it is a ASUS A8V Deluxe board with the lan omboard. > 5.3_STABLE is the version I'm running. > Hello I've myself got some problem with sk0 (my card is a Yukon Marvell Gigabit Ethernet) sth like sk0:watchdog timeout (it's real pain!!) But u could find some clue here: http://sources.zabbadoz.net/freebsd/if_sk.html I think such a card could work (but not easily tough :/) From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 15:05:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBAAD16A4CE for ; Mon, 6 Dec 2004 15:05:47 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D42C43D62 for ; Mon, 6 Dec 2004 15:05:47 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iB6F5jtN013165; Mon, 6 Dec 2004 16:05:45 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org, "Ernst W. Winter" Date: Mon, 6 Dec 2004 16:05:57 +0100 User-Agent: KMail/1.7.50 References: <20041206152352.A4053@ns3.bsn.com> In-Reply-To: <20041206152352.A4053@ns3.bsn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412061605.57407.groot@kde.org> Subject: Re: network card 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, 06 Dec 2004 15:05:48 -0000 On Monday 06 December 2004 15:23, Ernst W. Winter wrote: > Well I would like to ask "what ntwork card" is working with amd64 > FreeBSD, that is without any hassles. I try the sk one and it still has > the problem of putting out the same message: > > sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) > > it is a ASUS A8V Deluxe board with the lan omboard. > 5.3_STABLE is the version I'm running. 5-CURRENT has had patches applied by Bjoern (or others? In any case, mentioned often and recently on this list) for sk0; that works normally for me on a K8V. > Any sugestions what card would work with this MB and amd64? 3c905 (xl)? rtl8139 (rl)? I ran my K8V with xl0 and rl0 for months until the sk issues were resolved. It depends, of course, on what you want to do with the machine -- perhaps a cheap-ass $5 rl card isn't what you want. -- Don't worry, 't ain't no shame to be stupid - ol' mouse. GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 15:45:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D763D16A4CE for ; Mon, 6 Dec 2004 15:45:38 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C45343D39 for ; Mon, 6 Dec 2004 15:45:38 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (arlette.freesurf.fr [212.43.206.12]) by fidel.freesurf.fr (Postfix) with SMTP id BED322A6EB1; Mon, 6 Dec 2004 16:45:37 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by arlette.freesurf.fr with HTTP; Mon, 6 Dec 2004 16:45:37 +0100 (CET) Message-ID: <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> Date: Mon, 6 Dec 2004 16:45:37 +0100 (CET) From: "Guillaume R." To: X-Priority: 3 In-Reply-To: <200412061605.57407.groot@kde.org> References: <200412061605.57407.groot@kde.org> Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: network card 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, 06 Dec 2004 15:45:39 -0000 > On Monday 06 December 2004 15:23, Ernst W. Winter wrote: >> Well I would like to ask "what ntwork card" is working with amd64 >> FreeBSD, that is without any hassles. I try the sk one and it still >> has the problem of putting out the same message: >> >> sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) >> >> it is a ASUS A8V Deluxe board with the lan omboard. >> 5.3_STABLE is the version I'm running. > > 5-CURRENT has had patches applied by Bjoern (or others? In any case, > mentioned often and recently on this list) for sk0; that works > normally for me on a K8V. I'm interested here :) What patches have u applied to get this card working? As for me this card does not perfectly work on a fresh 5.3 installation. You got some clue? > >> Any sugestions what card would work with this MB and amd64? > > 3c905 (xl)? rtl8139 (rl)? I ran my K8V with xl0 and rl0 for months > until the sk issues were resolved. It depends, of course, on what you > want to do with the machine -- perhaps a cheap-ass $5 rl card isn't > what you want. Personnaly will be happy to get a cheap ass card that works fine under freebsd :) > > -- > Don't worry, 't ain't no shame to be stupid - ol' mouse. > GPG: FEA2 A3FE Adriaan de Groot > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to > "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 15:56:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6C5916A4CE for ; Mon, 6 Dec 2004 15:56:44 +0000 (GMT) Received: from ns3.bsn.com (ns3.bsn.com [194.221.32.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D75043D5E for ; Mon, 6 Dec 2004 15:56:44 +0000 (GMT) (envelope-from ewwinter@ns3.bsn.com) Received: from ns3.bsn.com (localhost [127.0.0.1]) by ns3.bsn.com (8.12.10/8.12.10) with ESMTP id iB6Fuhpm006196; Mon, 6 Dec 2004 16:56:43 +0100 (CET) (envelope-from ewwinter@ns3.bsn.com) Received: (from ewwinter@localhost) by ns3.bsn.com (8.12.10/8.12.10/Submit) id iB6FuhDM006195; Mon, 6 Dec 2004 16:56:43 +0100 (CET) (envelope-from ewwinter) Date: Mon, 6 Dec 2004 16:56:43 +0100 From: "Ernst W. Winter" To: Adriaan de Groot Message-ID: <20041206165643.A5894@ns3.bsn.com> References: <20041206152352.A4053@ns3.bsn.com> <200412061605.57407.groot@kde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200412061605.57407.groot@kde.org>; from groot@kde.org on Mon, Dec 06, 2004 at 04:05:57PM +0100 X-Phone: + 49-89-3075-6800 Organization: BSn -- Basis Systeme netzwerk X-Operating-System: FreeBSD ns3.bsn.com 4.9-STABLE FreeBSD 4.9-STABLE cc: freebsd-amd64@freebsd.org Subject: Re: network card X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 15:56:45 -0000 On Mon, 06 Dec 2004, Adriaan de Groot wrote: > On Monday 06 December 2004 15:23, Ernst W. Winter wrote: > > Well I would like to ask "what ntwork card" is working with amd64 > > FreeBSD, that is without any hassles. I try the sk one and it still has > > the problem of putting out the same message: > > > > sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) > > > > it is a ASUS A8V Deluxe board with the lan omboard. > > 5.3_STABLE is the version I'm running. > > 5-CURRENT has had patches applied by Bjoern (or others? In any case, mentioned > often and recently on this list) for sk0; that works normally for me on a > K8V. > > > Any sugestions what card would work with this MB and amd64? > > 3c905 (xl)? rtl8139 (rl)? I ran my K8V with xl0 and rl0 for months until the > sk issues were resolved. It depends, of course, on what you want to do with > the machine -- perhaps a cheap-ass $5 rl card isn't what you want. > Thanks, I came to the same conclusion as I have the same machine at home and since I just wanted to wait, until the problem is fixed I use a (xl?) as well and it works fine without problem. Just recompiled the kernel with a (rl?) and see what happen as I think it will run fine. The machine wouldn't use any Gigabyte line and so it is mute to have the card. Probably by the time it is ready I will use it, but it is a production machine and so need to be stable. eww -- Ernst W. Winter Basis Systeme netzwerk phone: +49 89 692 8120 Brecherspitzstr. 8/Rgb. fax: +49 89 692 8150 D-81541 Muenchen, Germany http://www.bsn.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 16:43:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39E3716A4CE for ; Mon, 6 Dec 2004 16:43:12 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id E75FB43D4C for ; Mon, 6 Dec 2004 16:43:11 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id E94BC803 for ; Mon, 6 Dec 2004 11:43:08 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 8AFA77A0; Mon, 6 Dec 2004 11:42:50 -0500 (EST) Date: Mon, 6 Dec 2004 11:42:50 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041206164250.GC28404@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mJm6k4Vb/yFcL9ZU" Content-Disposition: inline X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: sgs_public_dcc_server: phoenix.gargantuan.com 1199; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. Subject: amd64 laptop recommendations 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, 06 Dec 2004 16:43:12 -0000 --mJm6k4Vb/yFcL9ZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good morning folks! I am in the market for an AMD64-based laptop, and am currently leaning toward the Acer Ferrari 3400, but would like to borrow a few minutes of your time to ask for suggestions on something better. I just spoke to someone at Acer, and they gave me these specs: o CPU - AMD64 3200+ (2.0 Ghz) o LAN - Broadcom BCM5788M o Wireless - Broadcom BCM4306KFB (mini-PCI, maybe replaceable with atheros-based a/b/g card????) o bluetooth / modem - CSR BC212615BEN-E4 (agere scorpio) o Via K8T800 chipset, Via VT8235CE o Phoenix BIOS (hoping for hw.acpi.s4bios=3D1) Thanks for your time and consideration, I appreciate it! (The reason that I am moving from i386 toward AMD64 is a belief that 64 bit computing is the future, and that the AMD64 will be around for a (relatively) long time, and since I can't spend thousands of $$ very often for a new PC, this (it would seem) holds the most long-term value. If you think I am way off base on that assumption, please school me!) --=20 Michael W. Oliver [see complete headers for contact information] --mJm6k4Vb/yFcL9ZU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtIwKsWv7q8X6o8kRAuf/AJ9rZ9MGXXqI+KVI1oisfvZyCJ8LRQCffiEk pCFNTIs2OYpSngMdATXSKQI= =6tiU -----END PGP SIGNATURE----- --mJm6k4Vb/yFcL9ZU-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 17:16:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EBBC16A4CE for ; Mon, 6 Dec 2004 17:16:37 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E24043D5E for ; Mon, 6 Dec 2004 17:16:37 +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 iB6HGZGm032871; Mon, 6 Dec 2004 09:16:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB6HGZ43032869; Mon, 6 Dec 2004 09:16:35 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Dec 2004 09:16:34 -0800 From: "David O'Brien" To: "Michael W. Oliver" Message-ID: <20041206171634.GA32801@dragon.nuxi.com> References: <20041206164250.GC28404@gargantuan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041206164250.GC28404@gargantuan.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: amd64 laptop recommendations 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: Mon, 06 Dec 2004 17:16:37 -0000 On Mon, Dec 06, 2004 at 11:42:50AM -0500, Michael W. Oliver wrote: > I am in the market for an AMD64-based laptop, and am currently leaning > toward the Acer Ferrari 3400, but would like to borrow a few minutes of > your time to ask for suggestions on something better. This is in my opinion the best shipping AMD64 laptop. The only other one to consider is the high-end HP one (model number escapes me), which you'd only get over the Acer 3400 if you wanted a huge screen and work horse. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 17:25:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDD7816A4CE for ; Mon, 6 Dec 2004 17:25:40 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D3EC43D69 for ; Mon, 6 Dec 2004 17:25: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 iB6HPdpI033271; Mon, 6 Dec 2004 09:25: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 iB6HPdFc033270; Mon, 6 Dec 2004 09:25:39 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Dec 2004 09:25:38 -0800 From: "David O'Brien" To: "Guillaume R." Message-ID: <20041206172538.GC32801@dragon.nuxi.com> References: <200412061605.57407.groot@kde.org> <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> 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: network card 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: Mon, 06 Dec 2004 17:25:40 -0000 On Mon, Dec 06, 2004 at 04:45:37PM +0100, Guillaume R. wrote: > > On Monday 06 December 2004 15:23, Ernst W. Winter wrote: > >> Well I would like to ask "what ntwork card" is working with amd64 > >> FreeBSD, that is without any hassles. I try the sk one and it still > >> has the problem of putting out the same message: > >> > >> sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) > >> > >> it is a ASUS A8V Deluxe board with the lan omboard. > >> 5.3_STABLE is the version I'm running. > > > > 5-CURRENT has had patches applied by Bjoern (or others? In any case, > > mentioned often and recently on this list) for sk0; that works > > normally for me on a K8V. > I'm interested here :) > What patches have u applied to get this card working? > As for me this card does not perfectly work on a fresh 5.3 installation. > You got some clue? Can you update to RELENG_5 and try again? There was a MAJOR bug fixed after 5.3 (diff attached). -- -- David (obrien@FreeBSD.org) Index: if_sk.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_sk.c,v retrieving revision 1.83.2.2 retrieving revision 1.83.2.3 diff -u -r1.83.2.2 -r1.83.2.3 --- if_sk.c 25 Aug 2004 21:19:06 -0000 1.83.2.2 +++ if_sk.c 20 Nov 2004 17:41:43 -0000 1.83.2.3 @@ -48,7 +48,7 @@ */ #include -__FBSDID("$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.2 2004/08/25 21:19:06 jmg Exp $"); +__FBSDID("$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.3 2004/11/20 17:41:43 bz Exp $"); /* * SysKonnect SK-NET gigabit ethernet driver for FreeBSD. Supports @@ -136,7 +136,7 @@ #ifndef lint static const char rcsid[] = - "$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.2 2004/08/25 21:19:06 jmg Exp $"; + "$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.3 2004/11/20 17:41:43 bz Exp $"; #endif static struct sk_type sk_devs[] = { @@ -1501,6 +1501,7 @@ { struct sk_softc *sc; int unit, error = 0, rid, *port; + uint8_t skrs; sc = device_get_softc(dev); unit = device_get_unit(dev); @@ -1561,9 +1562,10 @@ /* Read and save vital product data from EEPROM. */ sk_vpd_read(sc); + skrs = sk_win_read_1(sc, SK_EPROM0); if (sc->sk_type == SK_GENESIS) { /* Read and save RAM size and RAMbuffer offset */ - switch(sk_win_read_1(sc, SK_EPROM0)) { + switch(skrs) { case SK_RAMSIZE_512K_64: sc->sk_ramsize = 0x80000; sc->sk_rboff = SK_RBOFF_0; @@ -1586,8 +1588,11 @@ error = ENXIO; goto fail; } - } else { - sc->sk_ramsize = 0x20000; + } else { /* SK_YUKON */ + if (skrs == 0x00) + sc->sk_ramsize = 0x20000; + else + sc->sk_ramsize = skrs * (1<<12); sc->sk_rboff = SK_RBOFF_0; } From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 19:30:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5096416A4CE; Mon, 6 Dec 2004 19:30:37 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8F2E43D48; Mon, 6 Dec 2004 19:30:36 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (jose.freesurf.fr [212.43.206.13]) by fidel.freesurf.fr (Postfix) with SMTP id 0F6CE2A5EDB; Mon, 6 Dec 2004 20:30:36 +0100 (CET) Received: from 134.214.103.196 (proxying for 134.214.228.213) (SquirrelMail authenticated user freebsd2) by jose.freesurf.fr with HTTP; Mon, 6 Dec 2004 20:30:35 +0100 (CET) Message-ID: <33363.134.214.103.196.1102361435.squirrel@jose.freesurf.fr> Date: Mon, 6 Dec 2004 20:30:35 +0100 (CET) From: "Guillaume R." To: X-Priority: 3 In-Reply-To: <20041206172538.GC32801@dragon.nuxi.com> References: <20041206172538.GC32801@dragon.nuxi.com> Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: obrien@FreeBSD.org Subject: Re: network card 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, 06 Dec 2004 19:30:37 -0000 > On Mon, Dec 06, 2004 at 04:45:37PM +0100, Guillaume R. wrote: >> > On Monday 06 December 2004 15:23, Ernst W. Winter wrote: >> >> Well I would like to ask "what ntwork card" is working with amd64 >> >> FreeBSD, that is without any hassles. I try the sk one and it still >> >> has the problem of putting out the same message: >> >> >> >> sk0 discard frame w/o leading ethernet header (len 10 pkt len 10) >> >> >> >> it is a ASUS A8V Deluxe board with the lan omboard. >> >> 5.3_STABLE is the version I'm running. >> > >> > 5-CURRENT has had patches applied by Bjoern (or others? In any case, >> > mentioned often and recently on this list) for sk0; that works >> > normally for me on a K8V. >> I'm interested here :) >> What patches have u applied to get this card working? >> As for me this card does not perfectly work on a fresh 5.3 >> installation. You got some clue? > > Can you update to RELENG_5 and try again? There was a MAJOR bug fixed > after 5.3 (diff attached). Lo Will do it with pleasure :) Hope it will work and thx for the diff (I think I already apply it will check that and tell the results) Thx :) > > -- > -- David (obrien@FreeBSD.org) > > > Index: if_sk.c > =================================================================== RCS > file: /home/ncvs/src/sys/pci/if_sk.c,v > retrieving revision 1.83.2.2 > retrieving revision 1.83.2.3 > diff -u -r1.83.2.2 -r1.83.2.3 > --- if_sk.c 25 Aug 2004 21:19:06 -0000 1.83.2.2 > +++ if_sk.c 20 Nov 2004 17:41:43 -0000 1.83.2.3 > @@ -48,7 +48,7 @@ > */ > > #include > -__FBSDID("$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.2 2004/08/25 21:19:06 > jmg Exp $"); +__FBSDID("$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.3 > 2004/11/20 17:41:43 bz Exp $"); > > /* > * SysKonnect SK-NET gigabit ethernet driver for FreeBSD. Supports > @@ -136,7 +136,7 @@ > > #ifndef lint > static const char rcsid[] = > - "$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.2 2004/08/25 21:19:06 jmg > Exp $"; + "$FreeBSD: src/sys/pci/if_sk.c,v 1.83.2.3 2004/11/20 > 17:41:43 bz Exp $"; > #endif > > static struct sk_type sk_devs[] = { > @@ -1501,6 +1501,7 @@ > { > struct sk_softc *sc; > int unit, error = 0, rid, *port; > + uint8_t skrs; > > sc = device_get_softc(dev); > unit = device_get_unit(dev); > @@ -1561,9 +1562,10 @@ > /* Read and save vital product data from EEPROM. */ > sk_vpd_read(sc); > > + skrs = sk_win_read_1(sc, SK_EPROM0); > if (sc->sk_type == SK_GENESIS) { > /* Read and save RAM size and RAMbuffer offset */ > - switch(sk_win_read_1(sc, SK_EPROM0)) { > + switch(skrs) { > case SK_RAMSIZE_512K_64: > sc->sk_ramsize = 0x80000; > sc->sk_rboff = SK_RBOFF_0; > @@ -1586,8 +1588,11 @@ > error = ENXIO; > goto fail; > } > - } else { > - sc->sk_ramsize = 0x20000; > + } else { /* SK_YUKON */ > + if (skrs == 0x00) > + sc->sk_ramsize = 0x20000; > + else > + sc->sk_ramsize = skrs * (1<<12); > sc->sk_rboff = SK_RBOFF_0; > } > From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 20:55:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A76016A4CE for ; Mon, 6 Dec 2004 20:55:41 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F4E243D1D for ; Mon, 6 Dec 2004 20:55:41 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so178398wra for ; Mon, 06 Dec 2004 12:55:35 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=WXfXBdYWpfTZLEoh5L5gPYfrSL3z2QmeIX9rUYDTthcMTFgY2/t56amtmV6sDh1idi/oOVGdutAFq1aqMQ+6jbODrO/Vdjyc7zXGNZVFjh1Oa5MoZ3Livo08HqhRc1FrbBgXGikkHtk9N7nwmrSjEnmkajYZRXK+ayBjGKpMFsY= Received: by 10.54.32.22 with SMTP id f22mr449164wrf; Mon, 06 Dec 2004 12:46:33 -0800 (PST) Received: by 10.54.40.6 with HTTP; Mon, 6 Dec 2004 12:46:32 -0800 (PST) Message-ID: <2fd864e0412061246eeb0cc6@mail.gmail.com> Date: Mon, 6 Dec 2004 12:46:32 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20041206171634.GA32801@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041206164250.GC28404@gargantuan.com> <20041206171634.GA32801@dragon.nuxi.com> Subject: Re: amd64 laptop recommendations X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 20:55:41 -0000 On Mon, 6 Dec 2004 09:16:34 -0800, David O'Brien wrote: > On Mon, Dec 06, 2004 at 11:42:50AM -0500, Michael W. Oliver wrote: > > I am in the market for an AMD64-based laptop, and am currently leaning > > toward the Acer Ferrari 3400, but would like to borrow a few minutes of > > your time to ask for suggestions on something better. > > This is in my opinion the best shipping AMD64 laptop. The only other one > to consider is the high-end HP one (model number escapes me), which you'd > only get over the Acer 3400 if you wanted a huge screen and work horse. > > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > 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" > The high end HP AMD64s share the R3000Z Laptop bug if I'm not mistaken. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 21:00:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D1016A4CE for ; Mon, 6 Dec 2004 21:00:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C3AE43D55 for ; Mon, 6 Dec 2004 21:00:48 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so179178wra for ; Mon, 06 Dec 2004 13:00:48 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=DzUq0D8CJkuHB4T6A4X3jC1DMhZWs6oDrTZiPfFhdXsFBDtPs7hfJ/3x9oAejvXbP1vvxaeiVCtsPEyiMVM5i23wpOou7o9p6vuj38gF8PsLkPqv1gcamm0iGfr7JbzeO6EydWmDO3pKzOqcnL8atyxk4tJ5Eayia/ZfFA+WBQA= Received: by 10.54.51.7 with SMTP id y7mr723810wry; Mon, 06 Dec 2004 12:48:25 -0800 (PST) Received: by 10.54.40.6 with HTTP; Mon, 6 Dec 2004 12:48:23 -0800 (PST) Message-ID: <2fd864e04120612481ae2de47@mail.gmail.com> Date: Mon, 6 Dec 2004 12:48:23 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <2fd864e0412061246eeb0cc6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041206164250.GC28404@gargantuan.com> <20041206171634.GA32801@dragon.nuxi.com> <2fd864e0412061246eeb0cc6@mail.gmail.com> Subject: Re: amd64 laptop recommendations X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 21:00:48 -0000 > > The high end HP AMD64s share the R3000Z Laptop bug if I'm not mistaken. > Ack, forgot something else. Avoid All laptops that use the mobile NForce3 chipset. I'm working on getting atleast some functionality out of it for ACPI.... but I don't expect that to be done any time soon. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 21:15:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85D0A16A4CE; Mon, 6 Dec 2004 21:15:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79FB43D46; Mon, 6 Dec 2004 21:15:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 6E2D61FF91D; Mon, 6 Dec 2004 22:15:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 6A8B71FF90C; Mon, 6 Dec 2004 22:15:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 2ED981560B; Mon, 6 Dec 2004 21:12:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 241361539E; Mon, 6 Dec 2004 21:12:10 +0000 (UTC) Date: Mon, 6 Dec 2004 21:12:10 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Guillaume R." In-Reply-To: <33363.134.214.103.196.1102361435.squirrel@jose.freesurf.fr> Message-ID: References: <20041206172538.GC32801@dragon.nuxi.com> <33363.134.214.103.196.1102361435.squirrel@jose.freesurf.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: obrien@FreeBSD.org cc: freebsd-amd64@freebsd.org Subject: Re: network card 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, 06 Dec 2004 21:15:10 -0000 On Mon, 6 Dec 2004, Guillaume R. wrote: Hi, > > Can you update to RELENG_5 and try again? There was a MAJOR bug fixed > > after 5.3 (diff attached). > Lo > Will do it with pleasure :) > Hope it will work and thx for the diff (I think I already apply it will > check that and tell the results) the formerly attached patch isn't the com/lete fix. there are more patches committed to 6-CURRENT by jmg@. I will MFC them within the next days when I find the time (somewhat under load). you may want to fetch if_sk.c and if_skreg.h from HEAD and copy them over your RELENG_5 tree in the mean time. fetch -o if_sk.c-1.92 \ 'http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/pci/if_sk.c?rev=1.92&content-type=text/plain' fetch -o if_skreg.h-1.24 \ 'http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/pci/if_skreg.h?rev=1.24&content-type=text/plain' will do the trick for now to fetch the up-to-date version. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 21:55:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A6B516A4CE for ; Mon, 6 Dec 2004 21:55:52 +0000 (GMT) Received: from eagle4.cc.GeorgiaSouthern.edu (eagle4.cc.GeorgiaSouthern.edu [141.165.4.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1DD43D1F for ; Mon, 6 Dec 2004 21:55:51 +0000 (GMT) (envelope-from sdodson@sdodson.com) Received: from [141.165.208.115] (vl208-115.vl208.GeorgiaSouthern.edu [141.165.208.115])iB6LtmjS007423 for ; Mon, 6 Dec 2004 16:55:49 -0500 (EST) Message-ID: <41B4D564.2090006@sdodson.com> Date: Mon, 06 Dec 2004 16:55:48 -0500 From: Scott Dodson User-Agent: Mozilla Thunderbird 1.0RC1 (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: nForce woes? 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, 06 Dec 2004 21:55:52 -0000 Do we expect the nForce 4 chipset to alleviate many of the problems found in nForce 3 or should I steer clear of products using this chipset as well? -- Scott Dodson From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 22:09:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E55016A4CE for ; Mon, 6 Dec 2004 22:09:50 +0000 (GMT) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9125D43D72 for ; Mon, 6 Dec 2004 22:09:49 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d199-126-50-174.abhsia.telus.net ([199.126.50.174]) by priv-edtnes51.telusplanet.netESMTP <20041206220918.ZUUO19238.priv-edtnes51.telusplanet.net@d199-126-50-174.abhsia.telus.net> for ; Mon, 6 Dec 2004 15:09:18 -0700 From: James Earl To: freebsd-amd64@freebsd.org In-Reply-To: <20041206172538.GC32801@dragon.nuxi.com> References: <200412061605.57407.groot@kde.org> <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> <20041206172538.GC32801@dragon.nuxi.com> Content-Type: text/plain Date: Mon, 06 Dec 2004 15:09:10 -0700 Message-Id: <1102370950.660.4.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: network card 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, 06 Dec 2004 22:09:50 -0000 On Mon, 2004-12-06 at 09:25 -0800, David O'Brien wrote: > Can you update to RELENG_5 and try again? There was a MAJOR bug fixed > after 5.3 (diff attached). I've patched to 1.83.2.3, as well as the latest if_sk.c, and if_skreg.h in CVS but am still having problems with the sk device. It seems I only have problems when trying to obtain a dhcp lease. I am usually able to kill dhclient, bring down and back up sk0, and then try obtaining a dhcp lease again. This usually works, but sometimes it doesn't and I have to try for up to 30 minutes (rebooting, etc) to obtain a lease. I'm running an Asus A8V Deluxe (rev 2.0). James From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 22:20:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7E5916A4CE for ; Mon, 6 Dec 2004 22:20:09 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 105E943D5F for ; Mon, 6 Dec 2004 22:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 1DE771FF91D; Mon, 6 Dec 2004 23:20:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 1CF3D1FF90C; Mon, 6 Dec 2004 23:20:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 613091560B; Mon, 6 Dec 2004 22:18:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 568691539E; Mon, 6 Dec 2004 22:18:36 +0000 (UTC) Date: Mon, 6 Dec 2004 22:18:36 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: James Earl In-Reply-To: <1102370950.660.4.camel@serious.ab.hsia.telus.net> Message-ID: References: <200412061605.57407.groot@kde.org> <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> <1102370950.660.4.camel@serious.ab.hsia.telus.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: network card 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, 06 Dec 2004 22:20:09 -0000 On Mon, 6 Dec 2004, James Earl wrote: > On Mon, 2004-12-06 at 09:25 -0800, David O'Brien wrote: > > Can you update to RELENG_5 and try again? There was a MAJOR bug fixed > > after 5.3 (diff attached). > > I've patched to 1.83.2.3, as well as the latest if_sk.c, and if_skreg.h > in CVS but am still having problems with the sk device. > > It seems I only have problems when trying to obtain a dhcp lease. I am this is one of the last open issues. See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/61296 I will investigate this once the other things got MFCed. Hans Lambermont told me that a media "media 10baseT/UTP"; in dhclient.conf seems to be a workaround though this is really very very unsupported and you might see some "funny" state in ifconfig media line. If you really need DHCP on your interface you might want ot give it a try in the meantime. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 23:13:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAB5A16A4CE for ; Mon, 6 Dec 2004 23:13:57 +0000 (GMT) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661A943D48 for ; Mon, 6 Dec 2004 23:13:57 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d199-126-50-174.abhsia.telus.net ([199.126.50.174]) by priv-edtnes51.telusplanet.netESMTP <20041206231356.DRBJ19238.priv-edtnes51.telusplanet.net@d199-126-50-174.abhsia.telus.net>; Mon, 6 Dec 2004 16:13:56 -0700 From: James Earl To: "Bjoern A. Zeeb" In-Reply-To: References: <200412061605.57407.groot@kde.org> <33305.134.214.201.98.1102347937.squirrel@arlette.freesurf.fr> <20041206172538.GC32801@dragon.nuxi.com> <1102370950.660.4.camel@serious.ab.hsia.telus.net> Content-Type: text/plain Date: Mon, 06 Dec 2004 16:13:46 -0700 Message-Id: <1102374826.660.14.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: network card 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, 06 Dec 2004 23:13:58 -0000 On Mon, 2004-12-06 at 22:18 +0000, Bjoern A. Zeeb wrote: > On Mon, 6 Dec 2004, James Earl wrote: > > > On Mon, 2004-12-06 at 09:25 -0800, David O'Brien wrote: > > > Can you update to RELENG_5 and try again? There was a MAJOR bug fixed > > > after 5.3 (diff attached). > > > > I've patched to 1.83.2.3, as well as the latest if_sk.c, and if_skreg.h > > in CVS but am still having problems with the sk device. > > > > It seems I only have problems when trying to obtain a dhcp lease. I am > > this is one of the last open issues. See > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/61296 > > I will investigate this once the other things got MFCed. > > Hans Lambermont told me that a > media "media 10baseT/UTP"; > in dhclient.conf seems to be a workaround though this is really > very very unsupported and you might see some "funny" state in > ifconfig media line. > If you really need DHCP on your interface you might want ot give > it a try in the meantime. > Thank you. I'm okay living with it for the time being. I usually only turn my system on once a day, so it's definitely not a huge problem for me. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 00:09:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DEC316A4CE for ; Tue, 7 Dec 2004 00:09:56 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ABE543D1D for ; Tue, 7 Dec 2004 00:09:56 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 3053B1975F; Mon, 6 Dec 2004 16:09:56 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 6 Dec 2004 16:09:55 -0800 User-Agent: KMail/1.7.1 References: <59730.134.214.201.98.1102341041.squirrel@jose.freesurf.fr> In-Reply-To: <59730.134.214.201.98.1102341041.squirrel@jose.freesurf.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412061609.55733.peter@wemm.org> Subject: Re: Kernel compilation problem 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, 07 Dec 2004 00:09:56 -0000 On Monday 06 December 2004 05:50 am, freebsd2@freesurf.fr wrote: > Hi all! > I'm very new to FreeBSD (indeed I ran it since one week) and I need > to compile my kernel so that some patches will apply correctly. So I > made all the process I type make depends && make and I've got sth > like this: > ../../../i386/i386/genassym.c:216:error: storage size of BC32SELw0 > isn't known > I've got that for all BC32 and furthermore on line 214 for KSPEL :( > So the compilation stops on an error code. > Does anyone got a clue? > Many thx :) It means you're in the wrong directory and as a result, trying to build an i386 kernel on an amd64 machine with an amd64 compiler. You probably want to do your thing in /usr/src/sys/amd64/conf and /usr/src/sys/amd64/compile/... -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 00:17:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 787AF16A4CE for ; Tue, 7 Dec 2004 00:17:41 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53AE743D60 for ; Tue, 7 Dec 2004 00:17:41 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 478DC1975F; Mon, 6 Dec 2004 16:17:41 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 6 Dec 2004 16:17:40 -0800 User-Agent: KMail/1.7.1 References: <41B4D564.2090006@sdodson.com> In-Reply-To: <41B4D564.2090006@sdodson.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412061617.40804.peter@wemm.org> Subject: Re: nForce woes? 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, 07 Dec 2004 00:17:41 -0000 On Monday 06 December 2004 01:55 pm, Scott Dodson wrote: > Do we expect the nForce 4 chipset to alleviate many of the problems > found in nForce 3 or should I steer clear of products using this > chipset as well? My experience is with the nForce3-Pro150 and the reference bioses for it. The nForce3-Pro250 might be better. The same goes for the nForce4. There were two problems on the Pro150 boards, possibly one was an artifact of the other. 1) the bioses were really shoddy. If I understand things correctly, this is because the reference bioses were shoddy and few motherboard makers bothered to do anything about it. 2) the APIC subsystem was very unreliable under FreeBSD. It is distinctly possible that this was bugs/races in our code, but I believe it far more likely that it was genuine chipset bugs or malfunctions due to bad bios setup of the hardware. The problems should exist on FreeBSD/i386 as well. I verified that the easiest ones to reproduce on my boards do show up in 32 bit mode as well. I was so gun-shy over the whole thing that I've avoided them like the plague. Since I was buying them myself and not using sample boards or the like, I didn't want to risk wasting money on more junk. For all I know, they've fixed bugs in the chipset. But I'm not going to be the one to fork out $ to find out, I've already lost enough sleep over them. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 01:33:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2835016A4CE for ; Tue, 7 Dec 2004 01:33:40 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id B775143D1F for ; Tue, 7 Dec 2004 01:33:39 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so29195wri for ; Mon, 06 Dec 2004 17:33:39 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iOgPGL5DJxRZiNStC5AuHgVOHFtY9SUxeycKR87Xd8r72DrgJqUjYIWX0JNLwty4U/9uY0nRFL8NkrwfFg1Fc9bC+4Nse/htlPv19/ua7LVW0EOi4BJ9gw8kCtHXsumE03uCOE9WEpG0kIS+/JBezwr8/IUGu18droXFYEf5lS4= Received: by 10.54.13.78 with SMTP id 78mr773750wrm; Mon, 06 Dec 2004 17:28:49 -0800 (PST) Received: by 10.54.40.6 with HTTP; Mon, 6 Dec 2004 17:28:48 -0800 (PST) Message-ID: <2fd864e041206172840f48d35@mail.gmail.com> Date: Mon, 6 Dec 2004 17:28:48 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <2fd864e041206172824bb791@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41B4D564.2090006@sdodson.com> <200412061617.40804.peter@wemm.org> <2fd864e041206172824bb791@mail.gmail.com> Subject: Fwd: nForce woes? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 01:33:40 -0000 Oops. Only sent this to Peter. Sorry if it reposts. ---------- Forwarded message ---------- From: Astrodog Date: Mon, 6 Dec 2004 17:28:06 -0800 Subject: Re: nForce woes? To: Peter Wemm On Mon, 6 Dec 2004 16:17:40 -0800, Peter Wemm wrote: > On Monday 06 December 2004 01:55 pm, Scott Dodson wrote: > > Do we expect the nForce 4 chipset to alleviate many of the problems > > found in nForce 3 or should I steer clear of products using this > > chipset as well? > > My experience is with the nForce3-Pro150 and the reference bioses for > it. The nForce3-Pro250 might be better. The same goes for the > nForce4. > > There were two problems on the Pro150 boards, possibly one was an > artifact of the other. > > 1) the bioses were really shoddy. If I understand things correctly, > this is because the reference bioses were shoddy and few motherboard > makers bothered to do anything about it. > > 2) the APIC subsystem was very unreliable under FreeBSD. It is > distinctly possible that this was bugs/races in our code, but I believe > it far more likely that it was genuine chipset bugs or malfunctions due > to bad bios setup of the hardware. The problems should exist on > FreeBSD/i386 as well. I verified that the easiest ones to reproduce on > my boards do show up in 32 bit mode as well. > > I was so gun-shy over the whole thing that I've avoided them like the > plague. Since I was buying them myself and not using sample boards or > the like, I didn't want to risk wasting money on more junk. For all I > know, they've fixed bugs in the chipset. But I'm not going to be the > one to fork out $ to find out, I've already lost enough sleep over > them. > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > _______________________________________________ > 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" > NForce3 150 is what's on all the R3000 AMD64 compaq notebooks. Without ACPI enabled, the notebooks crash on any power management feature, and with ACPI, they just lock up mid-boot. I'm working on resolving the ACPI stuff, so if anyone has docs on how they've implemented ACPI on the NForce3s for notebooks that'd be great. On a sidenote, the ACPI blacklist does not correctly determine the board in these machines. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 10:11:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDE4516A4CE for ; Tue, 7 Dec 2004 10:11:35 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CB7143D60 for ; Tue, 7 Dec 2004 10:11:35 +0000 (GMT) (envelope-from will@exomi.com) Received: from acerf.exomi.com (fa-3-0-0.fw.exomi.com [217.169.64.99]) by will.iki.fi (Postfix) with ESMTP id 93C531E; Tue, 7 Dec 2004 12:11:33 +0200 (EET) From: Ville-Pertti Keinonen To: "Michael W. Oliver" In-Reply-To: <20041206164250.GC28404@gargantuan.com> References: <20041206164250.GC28404@gargantuan.com> Content-Type: text/plain Date: Tue, 07 Dec 2004 12:11:14 +0200 Message-Id: <1102414274.671.33.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: amd64 laptop recommendations 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, 07 Dec 2004 10:11:35 -0000 On Mon, 2004-12-06 at 11:42 -0500, Michael W. Oliver wrote: > Good morning folks! > > I am in the market for an AMD64-based laptop, and am currently leaning > toward the Acer Ferrari 3400, but would like to borrow a few minutes of > your time to ask for suggestions on something better. The Ferrari 3400 is probably a decent choice. I have a Ferrari 3200 myself, which is mostly the same except for the slower processor, and it works well with FreeBSD. I've been using it for almost 6 months now. FreeBSD/amd64 works well - X (except for 3D accel.), built-in ethernet, audio, bluetooth, even the built-in card reader. Under FreeBSD/i386, the builtin wireless interface also works (with if_ndis). There are some cons, though - the viewing angle isn't particularly good, colors are bluish, and battery life is non-existent (it should be improved for the 3400 according to specs, though). The design and build quality are ok for a PC laptop, but compared to my previous laptop (a PowerBook), it seems big, ugly and cheap. I mainly bought it for the amd64 processor and the decent screen resolution. > o CPU - AMD64 3200+ (2.0 Ghz) The specs on Acer's web page claim Mobile AMD64 3000+ (that could be 2GHz, though, depending on the cache size). From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 12:00:56 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E002B16A502 for ; Tue, 7 Dec 2004 12:00:56 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A038943D72 for ; Tue, 7 Dec 2004 12:00:55 +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 iB7C0tuX041659 for ; Tue, 7 Dec 2004 12:00:55 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB7C0th2041652; Tue, 7 Dec 2004 12:00:55 GMT (envelope-from gnats) Resent-Date: Tue, 7 Dec 2004 12:00:55 GMT Resent-Message-Id: <200412071200.iB7C0th2041652@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, Palle Girgensohn Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 556D416A4CE for ; Tue, 7 Dec 2004 11:56:16 +0000 (GMT) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F33643D31 for ; Tue, 7 Dec 2004 11:56:15 +0000 (GMT) (envelope-from girgen@rambutan.pingpong.net) Received: from rambutan.pingpong.net (localhost [127.0.0.1]) iB7BuDhY077346 for ; Tue, 7 Dec 2004 12:56:13 +0100 (CET) (envelope-from girgen@rambutan.pingpong.net) Received: (from girgen@localhost) by rambutan.pingpong.net (8.12.11/8.12.11/Submit) id iB7BuDHE077345; Tue, 7 Dec 2004 12:56:13 +0100 (CET) (envelope-from girgen) Message-Id: <200412071156.iB7BuDHE077345@rambutan.pingpong.net> Date: Tue, 7 Dec 2004 12:56:13 +0100 (CET) From: Palle Girgensohn To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/74811: df, nfs mount, negative Avail -> 32/64-bit confusion X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Palle Girgensohn List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 12:00:57 -0000 >Number: 74811 >Category: amd64 >Synopsis: df, nfs mount, negative Avail -> 32/64-bit confusion >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 07 12:00:54 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Palle Girgensohn >Release: FreeBSD 5.3-RELEASE amd64 >Organization: >Environment: System: FreeBSD rambutan.pingpong.net 4.10-RELEASE FreeBSD 4.10-RELEASE #2: Mon Jun 21 17:45:46 CEST 2004 girgen@banan.pingpong.net:/usr/obj/usr/src/sys/WORKSTATION i386 >Description: using FreeBSD 5.3 amd64 as nfs client FreeBSD 4.10 i386 as nfs server when a disk is filled up over 100%, Avail becomes negative on the server, but hugely postive on the 64-bit platform. Not very surprising, but still a bug... :) 4.10 i386 server: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da6s1f 17388202 16153532 -156386 101% /dumps/0 5.3 amd64 client: Filesystem 1K-blocks Used Avail Capacity Mounted on banan:/dumps/0 17388202 16153532 18014398509325598 0% /mnt >How-To-Repeat: 1. fill up a volume on FreeBSD 4.10 i386 to 101% 2. nfs mount this system on a FreeBSD 5.3 amd64 system 3. df on the 5.3 amd64 system reveals LOTS of space on the volume. :) >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 15:33:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7386B16A4CE; Tue, 7 Dec 2004 15:33:01 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8815C43D70; Tue, 7 Dec 2004 15:33:00 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7FWxHp090419; Tue, 7 Dec 2004 17:32:59 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 99552-13; Tue, 7 Dec 2004 17:32:58 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7FWwWk090416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 17:32:58 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB7FWw9R002028; Tue, 7 Dec 2004 17:32:58 +0200 (EET) (envelope-from ru) Date: Tue, 7 Dec 2004 17:32:57 +0200 From: Ruslan Ermilov To: current@FreeBSD.org, stable@FreeBSD.org Message-ID: <20041207153257.GE1336@ip.net.ua> Mail-Followup-To: Ruslan Ermilov , current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3oCie2+XPXTnK5a5" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org Subject: [TEST] Updated port net/nvnet 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, 07 Dec 2004 15:33:01 -0000 --3oCie2+XPXTnK5a5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm the lucky owner of the ASUS SK8N (amd64) motherboard with the onboard NVIDIA MCP Ethernet. With this patch, http://people.freebsd.org/~ru/patches/port_net_nvnet.patch I'm happily running it for three days without any glitches noticed so far: : nv0: port 0xec00-0xec07 mem 0xfeb= fc000-0xfebfcfff irq 5 at device 5.0 on pci0 : nv0: Ethernet address 00:0e:a6:54:dc:67 : miibus0: on nv0 : rlphy0: on miibus0 : rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto : nv0: Ethernet address: 00:0e:a6:54:dc:67 : nv0: [GIANT-LOCKED] I'd be grateful if someone could test this update on i386. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --3oCie2+XPXTnK5a5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtc0pqRfpzJluFF4RAkxCAJ91k1u3NhuMZOMIAhcRZhPlS6UTbgCeKIPq 1kwZrEJ4W8Jj3lk8ZLlkYpM= =p0Ey -----END PGP SIGNATURE----- --3oCie2+XPXTnK5a5-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 15:33:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B72B416A4CF for ; Tue, 7 Dec 2004 15:33:01 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 481E343D76 for ; Tue, 7 Dec 2004 15:33:01 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (arlette.freesurf.fr [212.43.206.12]) by fidel.freesurf.fr (Postfix) with SMTP id D2B0B2A508A for ; Tue, 7 Dec 2004 16:32:59 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by arlette.freesurf.fr with HTTP; Tue, 7 Dec 2004 16:32:59 +0100 (CET) Message-ID: <57594.134.214.201.98.1102433579.squirrel@arlette.freesurf.fr> Date: Tue, 7 Dec 2004 16:32:59 +0100 (CET) From: "Guillaume R." To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: sk0:watchdog timeout 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, 07 Dec 2004 15:33:01 -0000 Hello As we are numerous to get this problem I decide to open a dedicate thread. Here is what I've done today: First after dhclient hangs up; i restart dhclient again and finally get connected :) First I use cvsup to upgrade my freebsd thx to the stable-supfile and the ports supfile. Then strange phenomenon appears: no host resolution but i was always connected.Look at my logs and see the famous: sk0 watchdog timeout Reboot Call of dhclient three times, get connected finally (I've got a error message: can't bind DHCP address: address already in use etc..) Finish my upgrade thx to cvsup Then make buildworld etc...(in multi user mode) Then reboot (again...) First of all:i've always a GENERIC i386 kernel though I compiled a proper GNUX64 which was a copy of the GENERIC for amd64 modified (no compile errors :)) Dhclient hangs as usually finally get connected always the sk0 in my logs But now I can't use mozilla or even use the ports system:I've always got sth like "An older version of xxx is already installed, u may wish to make deinstall etc..." portupgrade doesn't work. So I've only succeed in broken my ports tree today and the problem of the sk0 is not solved: it's a little better (coz connection is up, but no resolution host I've got to do a ifconfig sk0 down and then up and then it works) Sorry for the confusion of this post but I'm a little tired :'( From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 17:06:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4204216A4CE for ; Tue, 7 Dec 2004 17:06:23 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id D114843D62 for ; Tue, 7 Dec 2004 17:06:22 +0000 (GMT) (envelope-from freebsd2@freesurf.fr) Received: from freesurf.fr (jose.freesurf.fr [212.43.206.13]) by fidel.freesurf.fr (Postfix) with SMTP id D552F2A6B13 for ; Tue, 7 Dec 2004 18:06:21 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by jose.freesurf.fr with HTTP; Tue, 7 Dec 2004 18:06:21 +0100 (CET) Message-ID: <29119.134.214.201.98.1102439181.squirrel@jose.freesurf.fr> Date: Tue, 7 Dec 2004 18:06:21 +0100 (CET) From: "Guillaume R." To: X-Priority: 3 In-Reply-To: <200412061609.55733.peter@wemm.org> References: <200412061609.55733.peter@wemm.org> Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Kernel compilation problem 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, 07 Dec 2004 17:06:23 -0000 > On Monday 06 December 2004 05:50 am, freebsd2@freesurf.fr wrote: >> Hi all! >> I'm very new to FreeBSD (indeed I ran it since one week) and I need to >> compile my kernel so that some patches will apply correctly. So I made >> all the process I type make depends && make and I've got sth like >> this: >> ../../../i386/i386/genassym.c:216:error: storage size of BC32SELw0 >> isn't known >> I've got that for all BC32 and furthermore on line 214 for KSPEL :( So >> the compilation stops on an error code. >> Does anyone got a clue? >> Many thx :) > > It means you're in the wrong directory and as a result, trying to build > an i386 kernel on an amd64 machine with an amd64 compiler. > > You probably want to do your thing in /usr/src/sys/amd64/conf > and /usr/src/sys/amd64/compile/... I am in those directories I try again and pay attention to this. Do u think it's a bug or sth like that? I don't understand this error :s Thx if u could help > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 17:51:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36BF916A4CE; Tue, 7 Dec 2004 17:51:59 +0000 (GMT) Received: from ns.yar.post.ru (ns.yar.post.ru [213.187.102.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EC2A43D69; Tue, 7 Dec 2004 17:51:58 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from gate-corbina.km.vibrators.ru (km.yar.post.ru [213.187.105.186]) by ns.yar.post.ru (8.12.9p2/8.12.9) with ESMTP id iB7Hptql031008; Tue, 7 Dec 2004 20:51:56 +0300 (MSK) (envelope-from liettneff@bk.ru) Received: from 192.168.1.100 ([192.168.1.100])iB7HplUE044942; Tue, 7 Dec 2004 20:51:49 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Tue, 7 Dec 2004 20:49:31 +0300 From: Michael Lednev X-Mailer: The Bat! (v2.01) Business Organization: none X-Priority: 3 (Normal) Message-ID: <172432578.20041207204931@bk.ru> To: Ruslan Ermilov In-Reply-To: <20041207153257.GE1336@ip.net.ua> References: <20041207153257.GE1336@ip.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@FreeBSD.org Subject: Re: [TEST] Updated port net/nvnet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: liettneff List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 17:51:59 -0000 Hello, Ruslan. 7 Dec 2004 ã., 18:32:57: RE> With this patch, RE> http://people.freebsd.org/~ru/patches/port_net_nvnet.patch RE> I'd be grateful if someone could test this update on i386. no luck on nforce3-250gb: root@reaper:~# kldload if_nv agp0: mem 0xc0000000-0xcfffffff at device 0.0 on pci0 agp0: Unable to find NVIDIA Memory Controller 1. device_attach: agp0 attach returned 19 i assume that none of my devices were recognized as nforce nic, after applying Masahiko KIMOTO's october patch the device was recognized as MCP7 with cicada chip, but after ifconfig i've got kernel page fault :) -- Regards, Michael mailto:liettneff@bk.ru From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 18:45:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81EBB16A4CE for ; Tue, 7 Dec 2004 18:45:52 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA5943D4C for ; Tue, 7 Dec 2004 18:45:51 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7IjiwM003205; Tue, 7 Dec 2004 20:45:44 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 25142-07; Tue, 7 Dec 2004 20:45:43 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7IjhlE003202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 20:45:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB7Ijhqe003343; Tue, 7 Dec 2004 20:45:43 +0200 (EET) (envelope-from ru) Date: Tue, 7 Dec 2004 20:45:43 +0200 From: Ruslan Ermilov To: Michael Lednev Message-ID: <20041207184543.GA3312@ip.net.ua> References: <20041207153257.GE1336@ip.net.ua> <172432578.20041207204931@bk.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: <172432578.20041207204931@bk.ru> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@freebsd.org Subject: Re: [TEST] Updated port net/nvnet 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, 07 Dec 2004 18:45:52 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 07, 2004 at 08:49:31PM +0300, Michael Lednev wrote: > Hello, Ruslan. >=20 > 7 Dec 2004 ?., 18:32:57: >=20 > RE> With this patch, >=20 > RE> http://people.freebsd.org/~ru/patches/port_net_nvnet.patch >=20 > RE> I'd be grateful if someone could test this update on i386. >=20 > no luck on nforce3-250gb: >=20 > root@reaper:~# kldload if_nv > agp0: mem 0xc0000000-0xcfffffff at > device 0.0 on pci0 > agp0: Unable to find NVIDIA Memory Controller 1. > device_attach: agp0 attach returned 19 >=20 > i assume that none of my devices were recognized as nforce nic, after > applying Masahiko KIMOTO's october patch the device was recognized as > MCP7 with cicada chip, but after ifconfig i've got kernel page fault > :) >=20 This has nothing to do with AGP. Also, at least on AMD64, kldloading this and some other modules doesn't work -- you need to pre-load it from loader(8). Add this line to /boot/loader.conf: if_nv_load=3D"YES" If you still don't have it running after this, send me the output of "pciconf -lv" off the list. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtfpXqRfpzJluFF4RAhbPAJ0TfrCqvq3SPs7Uvf+efzdjulb91QCeJWbt DMQJrFDzITgDOHxFbAyqGSM= =O7e4 -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 19:01:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D1B16A4CE for ; Tue, 7 Dec 2004 19:01:47 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EB8843D58 for ; Tue, 7 Dec 2004 19:01:46 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7J1jE1004123 for ; Tue, 7 Dec 2004 21:01:45 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 26400-08 for ; Tue, 7 Dec 2004 21:01:44 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7J1i1W004119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Dec 2004 21:01:44 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB7J1hMp003543 for amd64@FreeBSD.org; Tue, 7 Dec 2004 21:01:43 +0200 (EET) (envelope-from ru) Date: Tue, 7 Dec 2004 21:01:43 +0200 From: Ruslan Ermilov To: amd64@FreeBSD.org Message-ID: <20041207190143.GC3312@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5QAgd0e35j3NYeGe" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua Subject: Looking for chipset specs for NVIDIA nForce3 Pro 150 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, 07 Dec 2004 19:01:47 -0000 --5QAgd0e35j3NYeGe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm looking for the chipset specs for NVIDIA nForce3 (Pro 150), in order to add SMBus support for it. Googled two hours, and still didn't find anything. :-( Anyone has a clue where can I get the chipset manuals? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --5QAgd0e35j3NYeGe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtf4XqRfpzJluFF4RAtUKAJ9imvfP2UHYA27jGs0cIkY2OLtaVACcDstc i8rNAkOP6sBRj35H2Y0iDwc= =9BTW -----END PGP SIGNATURE----- --5QAgd0e35j3NYeGe-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 21:03:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82AE516A4CE; Tue, 7 Dec 2004 21:03:00 +0000 (GMT) Received: from f29.mail.ru (f29.mail.ru [194.67.57.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 028C843D73; Tue, 7 Dec 2004 21:03:00 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from mail by f29.mail.ru with local id 1CbmU6-000JtA-00; Wed, 08 Dec 2004 00:02:58 +0300 Received: from [193.233.48.103] by win.mail.ru with HTTP; Wed, 08 Dec 2004 00:02:58 +0300 From: =?koi8-r?Q?=EE=C9=CB=CF=CC=C1=CA=20=E2=CF=CB=CF=D7=20?= To: Ruslan Ermilov Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [193.233.48.103] Date: Wed, 08 Dec 2004 00:02:58 +0300 In-Reply-To: <20041207184543.GA3312@ip.net.ua> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: cc: freebsd-amd64@freebsd.org Subject: Re[2]: [TEST] Updated port net/nvnet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?koi8-r?Q?=EE=C9=CB=CF=CC=C1=CA=20=E2=CF=CB=CF=D7?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 21:03:00 -0000 -----Original Message----- From: Ruslan Ermilov To: Michael Lednev Date: Tue, 7 Dec 2004 20:45:43 +0200 Subject: Re: [TEST] Updated port net/nvnet > This has nothing to do with AGP. Also, at least on AMD64, > kldloading this and some other modules doesn't work -- you > need to pre-load it from loader(8). Add this line to > /boot/loader.conf: > > if_nv_load="YES" > > If you still don't have it running after this, send me the > output of "pciconf -lv" off the list. no, you dont understand, module is loading fine, but there is no line in if_nvreg.h referring to my nic. after adding something like #define NFORCE_MCPNET7_DEVICEID 0x00DF in it and recompiling nic is detected but cannot work read archive for october, original message from Masahiko Kimoto was posted on Oct 10 20:29:11 PDT 2004. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 22:23:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9A5D16A4CE for ; Tue, 7 Dec 2004 22:23:47 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD02E43D39 for ; Tue, 7 Dec 2004 22:23:47 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB7MNlL23929 for freebsd-amd64@freebsd.org; Tue, 7 Dec 2004 14:23:47 -0800 (PST) Date: Tue, 7 Dec 2004 14:23:47 -0800 From: Mike Hunter To: freebsd-amd64@freebsd.org Message-ID: <20041207222347.GA23656@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: problems compiling perl 5.8.5 w/ fbsd 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: Tue, 07 Dec 2004 22:23:47 -0000 Hi, I'm new to amd64 as of this nice new dual opteron box I've just received...I may be seeing a lot of you guys in the coming weeks :) I'm trying to build perl 5.8.5 but I'm having some problems. I got this funny-looking "ok" message after doing a make (in /usr/ports/lang/perl5.8) Making Errno (nonxs) Writing Makefile for Errno ../../miniperl "-I../../lib" "-I../../lib" "-I../../lib" "-I../../lib" Errno_pm.PL Errno.pm cp Errno.pm ../../lib/Errno.pm *** Error code 1 (ignored) Everything is up to date. Type 'make test' to run test suite. So then I tried to run make test but I got some more funny stuff: bash-2.05b# make test lib/Class/ISA/test........................ok lib/Class/Struct..........................ok lib/Config................................Out of memory during "large" request for 2147487744 bytes, total sbrk() is 4024666112 bytes at ../lib/Config.t line 15. # Looks like you planned 47 tests but ran 1. FAILED at test 2 lib/constant..............................ok lib/CPAN/t/loadme.........................ok lib/CPAN/t/mirroredby.....................ok lib/CPAN/t/Nox............................ok lib/CPAN/t/signature......................ok Any suggestions? Thanks! Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 22:32:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3E8716A4CE for ; Tue, 7 Dec 2004 22:32:11 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9769743D46 for ; Tue, 7 Dec 2004 22:32:11 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com (localhost [127.0.0.1])with ESMTP id BA637295437; Tue, 7 Dec 2004 17:32:04 -0500 (EST) Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Tue, 7 Dec 2004 17:32:04 -0500 (EST) Message-ID: <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> In-Reply-To: <20041207222347.GA23656@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> Date: Tue, 7 Dec 2004 17:32:04 -0500 (EST) From: "Mike Jakubik" To: "Mike Hunter" 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 X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: freebsd-amd64@freebsd.org Subject: Re: problems compiling perl 5.8.5 w/ fbsd 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: Tue, 07 Dec 2004 22:32:12 -0000 Mike Hunter said: > Hi, > > I'm new to amd64 as of this nice new dual opteron box I've just > received...I may be seeing a lot of you guys in the coming weeks :) Any reason why you installed 5.2.1 (Its an old pre-release version)? If this is a fresh box, then i highly recommend you install 5.3 instead. Perl 5.8.5 is packaged with 5.3 too. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 23:31:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADC8516A4CE for ; Tue, 7 Dec 2004 23:31:02 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DB4C43D2F for ; Tue, 7 Dec 2004 23:31:02 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB7NV1B29913; Tue, 7 Dec 2004 15:31:01 -0800 (PST) Date: Tue, 7 Dec 2004 15:31:01 -0800 From: Mike Hunter To: Mike Jakubik Message-ID: <20041207233101.GA29595@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: problems compiling perl 5.8.5 w/ fbsd 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: Tue, 07 Dec 2004 23:31:02 -0000 On Dec 07, "Mike Jakubik" wrote: > Mike Hunter said: > > Hi, > > > > I'm new to amd64 as of this nice new dual opteron box I've just > > received...I may be seeing a lot of you guys in the coming weeks :) > > Any reason why you installed 5.2.1 (Its an old pre-release version)? If > this is a fresh box, then i highly recommend you install 5.3 instead. Perl > 5.8.5 is packaged with 5.3 too. Actually I did 5.2.1 because that was the install media I had handy :) I'm building a RELENG_5 world/kernel as we speak...I'll be back if it doesn't work out :) Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 23:38:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52EAC16A4D5 for ; Tue, 7 Dec 2004 23:38:46 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07FA443D31 for ; Tue, 7 Dec 2004 23:38:46 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id EEC7619773; Tue, 7 Dec 2004 15:38:45 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 7 Dec 2004 15:38:45 -0800 User-Agent: KMail/1.7.1 References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> In-Reply-To: <20041207233101.GA29595@ack.Berkeley.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412071538.45627.peter@wemm.org> Subject: Re: problems compiling perl 5.8.5 w/ fbsd 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: Tue, 07 Dec 2004 23:38:46 -0000 On Tuesday 07 December 2004 03:31 pm, Mike Hunter wrote: > On Dec 07, "Mike Jakubik" wrote: > > Mike Hunter said: > > > Hi, > > > > > > I'm new to amd64 as of this nice new dual opteron box I've just > > > received...I may be seeing a lot of you guys in the coming weeks > > > :) > > > > Any reason why you installed 5.2.1 (Its an old pre-release > > version)? If this is a fresh box, then i highly recommend you > > install 5.3 instead. Perl 5.8.5 is packaged with 5.3 too. > > Actually I did 5.2.1 because that was the install media I had handy > :) I'm building a RELENG_5 world/kernel as we speak...I'll be back if > it doesn't work out :) There was some distinct brokenness with brk() and family in 5.2 for amd64, FYI. The known problems were fixed a while ago. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 00:38:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB46616A4CE for ; Wed, 8 Dec 2004 00:38:58 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F5043D5D for ; Wed, 8 Dec 2004 00:38:58 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from 172.16.0.1 (localhost [127.0.0.1]) with ESMTP id C80712957CF; Tue, 7 Dec 2004 19:38:50 -0500 (EST) Received: from 172.16.0.200 (SquirrelMail authenticated user mikej); by 172.16.0.1 with HTTP; Tue, 7 Dec 2004 19:38:50 -0500 (EST) Message-ID: <2501.172.16.0.200.1102466330.squirrel@172.16.0.200> In-Reply-To: <20041207233101.GA29595@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> Date: Tue, 7 Dec 2004 19:38:50 -0500 (EST) From: "Mike Jakubik" To: "Mike Hunter" 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 X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: freebsd-amd64@freebsd.org Subject: Re: problems compiling perl 5.8.5 w/ fbsd 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: Wed, 08 Dec 2004 00:38:58 -0000 Mike Hunter said: > On Dec 07, "Mike Jakubik" wrote: > >> Mike Hunter said: >> > Hi, >> > >> > I'm new to amd64 as of this nice new dual opteron box I've just >> > received...I may be seeing a lot of you guys in the coming weeks :) >> >> Any reason why you installed 5.2.1 (Its an old pre-release version)? If >> this is a fresh box, then i highly recommend you install 5.3 instead. >> Perl >> 5.8.5 is packaged with 5.3 too. > > Actually I did 5.2.1 because that was the install media I had handy :) > I'm building a RELENG_5 world/kernel as we speak...I'll be back if it > doesn't work out :) Well, don't make a habbit of installing old releases. I would still recommend you install 5.3 from scratch instead. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 01:37:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA8D516A4CE for ; Wed, 8 Dec 2004 01:37:16 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9262943D4C for ; Wed, 8 Dec 2004 01:37:16 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB81bGX11742 for freebsd-amd64@freebsd.org; Tue, 7 Dec 2004 17:37:16 -0800 (PST) Date: Tue, 7 Dec 2004 17:37:16 -0800 From: Mike Hunter To: freebsd-amd64@freebsd.org Message-ID: <20041208013716.GA10869@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: device apic? 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, 08 Dec 2004 01:37:17 -0000 Hi, I'm successfully up to 5.3-STABLE / RELENG_5 as of today :) In order to build my kernel I had to leave out apic, even though I had options SMP...has something changed? # make buildkernel KERNCONF=mybox config: Error: device "apic" is unknown config: 1 errors *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. mybox# grep apic sys/amd64/conf/NOTES # The apic device enables the use of the I/O APIC for interrupt delivery. # The apic device can be used in both UP and SMP kernels, but is required # for SMP kernels. Thus, the apic device is not strictly an SMP option, Did smp successfully make it into my kernel? mybox# uname -a FreeBSD mybox 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Dec 7 15:35:28 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 mybox# sysctl -a | grep -i smp kern.timecounter.smp_tsc: 0 kern.smp.forward_roundrobin_enabled: 1 kern.smp.forward_signal_enabled: 1 kern.smp.cpus: 2 kern.smp.disabled: 0 kern.smp.active: 1 kern.smp.maxcpus: 8 debug.psmpkterrthresh: 2 Thanks for any help, Mike From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 07:41:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A55016A4CE; Wed, 8 Dec 2004 07:41:30 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DA8943D2F; Wed, 8 Dec 2004 07:41:29 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB87fC3E046204; Wed, 8 Dec 2004 09:41:12 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 66235-10; Wed, 8 Dec 2004 09:41:11 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB87fAgg046201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 09:41:11 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB87fAgG038479; Wed, 8 Dec 2004 09:41:10 +0200 (EET) (envelope-from ru) Date: Wed, 8 Dec 2004 09:41:10 +0200 From: Ruslan Ermilov To: Mike Hunter , Peter Wemm Message-ID: <20041208074109.GB35079@ip.net.ua> References: <20041208013716.GA10869@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline In-Reply-To: <20041208013716.GA10869@ack.Berkeley.EDU> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@FreeBSD.org Subject: Re: device apic? 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, 08 Dec 2004 07:41:30 -0000 --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 07, 2004 at 05:37:16PM -0800, Mike Hunter wrote: > Hi, >=20 > I'm successfully up to 5.3-STABLE / RELENG_5 as of today :) >=20 > In order to build my kernel I had to leave out apic, even though I had > options SMP...has something changed? >=20 > # make buildkernel KERNCONF=3Dmybox >=20 > config: Error: device "apic" is unknown > config: 1 errors > *** Error code 1 >=20 There's no separate "device apic" on amd64, it's standard part of any kernel. It order to turn it off, you either need to do it in your machine's BIOS, or set hint.apic.0.disabled=3D1 in /boot/loader.conf. Peter, can you tweak amd64/NOTES to *not* mention "device apic", as it's confusing? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtrAVqRfpzJluFF4RApsGAKCaq9EiAg91YIV5veZuoIaZjxciwQCZAW1C iPSA5T1RRmoYyh+1xBP5u4c= =KL4O -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 08:06:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75CE916A4CE for ; Wed, 8 Dec 2004 08:06:29 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5673D43D4C for ; Wed, 8 Dec 2004 08:06:28 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB886MSb047564; Wed, 8 Dec 2004 10:06:23 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 68232-08; Wed, 8 Dec 2004 10:06:21 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB886Loi047561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 10:06:21 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB886K39038694; Wed, 8 Dec 2004 10:06:20 +0200 (EET) (envelope-from ru) Date: Wed, 8 Dec 2004 10:06:20 +0200 From: Ruslan Ermilov To: =?koi8-r?B?7snLz8zByiDiz8vP1w==?= Message-ID: <20041208080620.GD35079@ip.net.ua> References: <20041207184543.GA3312@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jL2BoiuKMElzg3CS" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@FreeBSD.org Subject: Re: [TEST] Updated port net/nvnet 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, 08 Dec 2004 08:06:29 -0000 --jL2BoiuKMElzg3CS Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 08, 2004 at 12:02:58AM +0300, =EE=C9=CB=CF=CC=C1=CA =E2=CF=CB= =CF=D7 wrote: > -----Original Message----- > From: Ruslan Ermilov > To: Michael Lednev > Date: Tue, 7 Dec 2004 20:45:43 +0200 > Subject: Re: [TEST] Updated port net/nvnet >=20 > > This has nothing to do with AGP. Also, at least on AMD64, > > kldloading this and some other modules doesn't work -- you > > need to pre-load it from loader(8). Add this line to > > /boot/loader.conf: > >=20 > > if_nv_load=3D"YES" > >=20 > > If you still don't have it running after this, send me the > > output of "pciconf -lv" off the list. >=20 > no, you dont understand, module is loading fine, but there is > no line in if_nvreg.h referring to my nic. after adding=20 > something like #define NFORCE_MCPNET7_DEVICEID 0x00DF in it and > recompiling nic is detected but cannot work >=20 > read archive for october, original message from Masahiko Kimoto > was posted on Oct 10 20:29:11 PDT 2004. >=20 Your device is not supported by this version of the driver. Newer version 1.0-0292 has support for it: $ pwd /usr/home/ru/NFORCE-Linux-x86_64-1.0-0292-pkg1/nvnet $ grep -i 00df * nvenet.h:#define PCI_DEVICE_ID_NVIDIA_NVENET_7 0x00DF Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --jL2BoiuKMElzg3CS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtrX8qRfpzJluFF4RAjUQAJ95N/W9of03CTDniEoSZ5WKEc55CwCfee6l GHQxWlXM9rwkbxIK8ufuPLs= =wVTL -----END PGP SIGNATURE----- --jL2BoiuKMElzg3CS-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 08:28:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6F2216A4CF for ; Wed, 8 Dec 2004 08:28:44 +0000 (GMT) Received: from koganei-server.ohnolab.org (koganei-server.ohnolab.org [202.249.37.99]) by mx1.FreeBSD.org (Postfix) with SMTP id 1DF4D43D55 for ; Wed, 8 Dec 2004 08:28:43 +0000 (GMT) (envelope-from kimoto@ohnolab.org) Received: (qmail 22747 invoked from network); 8 Dec 2004 08:28:37 -0000 Received: from localhost (kimoto@127.0.0.1) by localhost with SMTP; 8 Dec 2004 08:28:37 -0000 Date: Wed, 08 Dec 2004 17:27:52 +0900 (JST) Message-Id: <20041208.172752.85419182.kimoto@ohnolab.org> To: ru@FreeBSD.org From: Masahiko KIMOTO In-Reply-To: <20041208080620.GD35079@ip.net.ua> References: <20041207184543.GA3312@ip.net.ua> <20041208080620.GD35079@ip.net.ua> X-fingerprint: DA 63 E3 AD 3F 30 98 05 EB CF 3C 06 2D FF 07 7F X-PGP-Public-Key: http://www.ohnolab.org/~kimoto/kimoto.pubkey.asc X-URL: http://www.ohnolab.org/~kimoto/ X-Mailer: Mew version 4.0.69 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: [TEST] Updated port net/nvnet 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, 08 Dec 2004 08:28:45 -0000 > Your device is not supported by this version of the driver. > Newer version 1.0-0292 has support for it: > > $ pwd > /usr/home/ru/NFORCE-Linux-x86_64-1.0-0292-pkg1/nvnet > $ grep -i 00df * > nvenet.h:#define PCI_DEVICE_ID_NVIDIA_NVENET_7 0x00DF Even using newer version, I've received reports that GbE doesn't work. Some more modification should be needed to nvnet-src, e.g. supporting GbE media types. Maybe diffs of linux drivers between old and new help me, but I've not checked yet. ---------------------------------------------------------------------- Masahiko KIMOTO, Ph. D. E-mail: kimoto@ohnolab.org URL: http://www.ohnolab.org/~kimoto From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 7 22:22:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02B6616A4CE for ; Tue, 7 Dec 2004 22:22:48 +0000 (GMT) Received: from webmail.thai.com (webmail.thai.com [203.151.178.212]) by mx1.FreeBSD.org (Postfix) with SMTP id E22ED43D53 for ; Tue, 7 Dec 2004 22:22:46 +0000 (GMT) (envelope-from virek@thai.com) Received: (qmail 51429 invoked by uid 89); 7 Dec 2004 22:22:42 -0000 Message-ID: <20041207222242.51423.qmail@webmail.thai.com> From: "virek" To: freebsd-amd64@freebsd.org Date: Tue, 07 Dec 2004 22:22:42 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 08 Dec 2004 12:50:40 +0000 Subject: asus a2000k ? 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, 07 Dec 2004 22:22:48 -0000 Hello. Anyone been able to try 5.3 on the Asus A2000K? thanks.. . be yourself@thai.com! Shop all amazing products and get our special offers! From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 16:33:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48D0B16A4CE; Wed, 8 Dec 2004 16:33:36 +0000 (GMT) Received: from mailgate.csie.nctu.edu.tw (mailgate.csie.nctu.edu.tw [140.113.209.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3814A43D73; Wed, 8 Dec 2004 16:33:35 +0000 (GMT) (envelope-from wkwu@csie.nctu.edu.tw) Received: from mailgate.csie.nctu.edu.tw (wkwu@localhost [127.0.0.1]) iB8GXPlG073023; Thu, 9 Dec 2004 00:33:25 +0800 (CST) Received: (from wkwu@localhost) by mailgate.csie.nctu.edu.tw (8.13.1/8.13.1/Submit) id iB8GXEhX072965; Thu, 9 Dec 2004 00:33:14 +0800 (CST) Date: Thu, 9 Dec 2004 00:33:14 +0800 From: Wei-Kai Wu To: Xin LI Message-ID: <20041208163314.GA72697@mailgate.csie.nctu.edu.tw> References: <200412020817.iB28HxZP038814@mailgate.csie.nctu.edu.tw> <20041202082459.GA767@frontfree.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202082459.GA767@frontfree.net> User-Agent: Mutt/1.5.4i cc: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/74608: mpt hangs 5 minutes when booting 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, 08 Dec 2004 16:33:36 -0000 is there (id=74601022) AcpiOsDerivePciId: bus 0 dev 7 func 3 acpi0: Power Button (fixed) AcpiOsDerivePciId: bus 0 dev 10 func 0 ACPI timer: 1/2 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc008-0xc00b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pcib0: could not get PCI interrupt routing table for \\_SB_.PCI0 - AE_NOT_FOUND pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1022, dev=0x7460, revid=0x07 bus=0, slot=6, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x73 (3450 ns), mingnt=0x0e (3500 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7468, revid=0x05 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001000, size 4, enabled found-> vendor=0x1022, dev=0x7469, revid=0x03 bus=0, slot=7, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x746b, revid=0x05 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=0, slot=10, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 64, base fc000000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=0, slot=10, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 64, base fc001000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=0, slot=11, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=25, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=25, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=25, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=25, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=26, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=26, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=26, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=26, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=27, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=27, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=27, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=27, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib1: at device 6.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x2000-0x2fff pcib1: memory decode 0xfc100000-0xfdffffff pcib1: prefetched decode 0xfff00000-0xfffff ACPI PCI link initial configuration: pci1: on pcib1 pci1: physical bus=1 map[10]: type 1, range 32, base fd000000, size 24, enabled pcib1: device (null) requested decoded memory range 0xfd000000-0xfdffffff map[14]: type 4, range 32, base 00002000, size 8, enabled pcib1: device (null) requested decoded I/O range 0x2000-0x20ff map[18]: type 1, range 32, base fc100000, size 12, enabled pcib1: device (null) requested decoded memory range 0xfc100000-0xfc100fff pcib1: matched entry for 1.6.INTA pcib1: slot 6 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4752, revid=0x27 bus=1, slot=6, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=18 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x3000-0x3fff pcib2: memory decode 0xfe000000-0xfe0fffff pcib2: prefetched decode 0xfff00000-0xfffff ACPI PCI link initial configuration: pci2: on pcib2 pci2: physical bus=2 map[10]: type 4, range 32, base 00003000, size 8, enabled pcib2: device (null) requested decoded I/O range 0x3000-0x30ff map[14]: type 1, range 64, base fe010000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe010000-0xfe01ffff map[1c]: type 1, range 64, base fe000000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe000000-0xfe00ffff pcib2: matched entry for 2.4.INTA pcib2: slot 4 INTA hardwired to IRQ 24 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=2, slot=4, func=0 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=a, irq=24 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 00003400, size 8, enabled pcib2: device (null) requested decoded I/O range 0x3400-0x34ff map[14]: type 1, range 64, base fe030000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe030000-0xfe03ffff map[1c]: type 1, range 64, base fe020000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe020000-0xfe02ffff pcib2: matched entry for 2.4.INTB pcib2: slot 4 INTB hardwired to IRQ 25 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=2, slot=4, func=1 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=b, irq=25 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base fe050000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe050000-0xfe05ffff map[18]: type 1, range 64, base fe040000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe040000-0xfe04ffff pcib2: matched entry for 2.9.INTA pcib2: slot 9 INTA hardwired to IRQ 24 found-> vendor=0x14e4, dev=0x1648, revid=0x03 bus=2, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0016, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=24 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base fe070000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe070000-0xfe07ffff map[18]: type 1, range 64, base fe060000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe060000-0xfe06ffff pcib2: matched entry for 2.9.INTB pcib2: slot 9 INTB hardwired to IRQ 25 found-> vendor=0x14e4, dev=0x1648, revid=0x03 bus=2, slot=9, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0016, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=b, irq=25 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit mpt0: port 0x3000-0x30ff mem 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 4.0 on pci2 mpt0: Reserved 0x10000 bytes for rid 0x14 type 3 at 0xfe010000 mpt0: [GIANT-LOCKED] mpt0: soft reset mpt1: port 0x3400-0x34ff mem 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at device 4.1 on pci2 mpt1: linking with peer (mpt0) mpt1: Reserved 0x10000 bytes for rid 0x14 type 3 at 0xfe030000 mpt1: [GIANT-LOCKED] mpt1: soft reset bge0: mem 0xfe040000-0xfe04ffff,0xfe050000-0xfe05ffff irq 24 at device 9.0 on pci2 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe050000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:e0:81:63:4f:2e bge0: [MPSAFE] bge1: mem 0xfe060000-0xfe06ffff,0xfe070000-0xfe07ffff irq 25 at device 9.1 on pci2 bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe070000 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: bpf attached bge1: Ethernet address: 00:e0:81:63:4f:2d bge1: [MPSAFE] pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0x4000-0x4fff pcib3: memory decode 0xfe100000-0xfe1fffff pcib3: prefetched decode 0xfff00000-0xfffff AcpiOsDerivePciId: bus 0 dev 11 func 0 ACPI PCI link initial configuration: pci3: on pcib3 pci3: physical bus=3 map[10]: type 4, range 32, base 00004000, size 8, enabled pcib3: device (null) requested decoded I/O range 0x4000-0x40ff map[14]: type 1, range 64, base fe100000, size 12, enabled pcib3: device (null) requested decoded memory range 0xfe100000-0xfe100fff pcib3: matched entry for 3.3.INTA pcib3: slot 3 INTA hardwired to IRQ 28 found-> vendor=0x9005, dev=0x0080, revid=0x02 bus=3, slot=3, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=a, irq=28 powerspec 2 supports D0 D3 current D0 ahc0: port 0x4000-0x40ff mem 0xfe100000-0xfe100fff irq 28 at device 3.0 on pci3 ahc0: Defaulting to MEMIO on ahc0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xfe100000 ahc0: Enabling 39Bit Addressing ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 433 instructions downloaded ahc0: Features 0x1def6, Bugs 0x40, Flags 0x21485560 ahc0: [GIANT-LOCKED] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pci0: at device 11.1 (no driver attached) psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) atkbdc: atkbdc0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ahc_isa_probe 0: ioport 0xc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0 failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0 failed to probe at port 0x3f8 irq 4 on isa0 sio1 failed to probe at port 0x2f8 irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xffffffff800b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 238312 -> 100000 Timecounter "TSC" frequency 1804102097 Hz quality -100 Timecounters tick every 0.976 msec lo0: bpf attached ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging disabled Waiting 3 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe1:mpt0:0:1:0): error 22 (probe1:mpt0:0:1:0): Unretryable Error (probe2:mpt0:0:2:0): error 22 (probe2:mpt0:0:2:0): Unretryable Error (probe3:mpt0:0:3:0): error 22 (probe3:mpt0:0:3:0): Unretryable Error (probe4:mpt0:0:4:0): error 22 (probe4:mpt0:0:4:0): Unretryable Error (probe5:mpt0:0:5:0): error 22 (probe5:mpt0:0:5:0): Unretryable Error (probe7:mpt0:0:8:0): error 22 (probe7:mpt0:0:8:0): Unretryable Error ahc0: Selection Timeout on A:4. 0 SCBs aborted (probe8:mpt0:0:9:0): error 22 (probe8:mpt0:0:9:0): Unretryable Error (probe17:mpt1:0:2:0): error 22 (probe17:mpt1:0:2:0): Unretryable Error (probe9:mpt0:0:10:0): error 22 (probe9:mpt0:0:10:0): Unretryable Error ahc0: Selection Timeout on A:12. 0 SCBs aborted (probe18:mpt1:0:3:0): error 22 (probe18:mpt1:0:3:0): Unretryable Error (probe10:mpt0:0:11:0): error 22 (probe10:mpt0:0:11:0): Unretryable Error ahc0: Selection Timeout on A:13. 0 SCBs aborted (probe25:mpt1:0:11:0): error 22 (probe25:mpt1:0:11:0): Unretryable Error (probe11:mpt0:0:12:0): error 22 (probe11:mpt0:0:12:0): Unretryable Error ahc0: Selection Timeout on A:1. 0 SCBs aborted (probe15:mpt1:0:0:0): error 22 (probe15:mpt1:0:0:0): Unretryable Error (probe12:mpt0:0:13:0): error 22 (probe12:mpt0:0:13:0): Unretryable Error ahc0: Selection Timeout on A:2. 0 SCBs aborted (probe16:mpt1:0:1:0): error 22 (probe16:mpt1:0:1:0): Unretryable Error (probe13:mpt0:0:14:0): error 22 (probe13:mpt0:0:14:0): Unretryable Error ahc0: Selection Timeout on A:3. 0 SCBs aborted (probe19:mpt1:0:4:0): error 22 (probe19:mpt1:0:4:0): Unretryable Error (probe14:mpt0:0:15:0): error 22 (probe14:mpt0:0:15:0): Unretryable Error ahc0: Selection Timeout on A:5. 0 SCBs aborted (probe20:mpt1:0:5:0): error 22 (probe20:mpt1:0:5:0): Unretryable Error ahc0: Selection Timeout on A:6. 0 SCBs aborted (probe21:mpt1:0:6:0): error 22 (probe21:mpt1:0:6:0): Unretryable Error ahc0: Selection Timeout on A:8. 0 SCBs aborted (probe22:mpt1:0:8:0): error 22 (probe22:mpt1:0:8:0): Unretryable Error (probe0:mpt0:0:0:0): Retrying Command ahc0: Selection Timeout on A:9. 0 SCBs aborted (probe23:mpt1:0:9:0): error 22 (probe23:mpt1:0:9:0): Unretryable Error ahc0: Selection Timeout on A:10. 0 SCBs aborted (probe24:mpt1:0:10:0): error 22 (probe24:mpt1:0:10:0): Unretryable Error ahc0: Selection Timeout on A:11. 0 SCBs aborted (probe26:mpt1:0:12:0): error 22 (probe26:mpt1:0:12:0): Unretryable Error ahc0: Selection Timeout on A:14. 0 SCBs aborted (probe27:mpt1:0:13:0): error 22 (probe27:mpt1:0:13:0): Unretryable Error ahc0: Selection Timeout on A:15. 0 SCBs aborted (probe30:ahc0:0:0:0): Retrying Command (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 80.0MHz DT, offset = 0x3e (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (probe0:ahc0:0:0:1): Retrying Command (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (probe28:mpt1:0:14:0): error 22 (probe28:mpt1:0:14:0): Unretryable Error (probe29:mpt1:0:15:0): error 22 (probe29:mpt1:0:15:0): Unretryable Error pass0 at mpt0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-3 device pass0: Serial Number 3FP00LZB000022070857 pass0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled pass1 at mpt0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device pass1: Serial Number 1 pass1: 3.300MB/s transfers pass2 at ahc0 bus 0 target 0 lun 0 pass2: Fixed Direct Access SCSI-4 device pass2: Serial Number 3367957 pass2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled pass3 at ahc0 bus 0 target 0 lun 1 pass3: Fixed Direct Access SCSI-4 device pass3: Serial Number 3367957 pass3: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled pass1 at mpt0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device pass1: Serial Number 1 pass1: 3.300MB/s transfers da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 3FP00LZB000022070857 da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687371 512 byte sectors: 255H 63S/T 4462C) da1 at ahc0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-4 device da1: Serial Number 3367957 da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da1: 1000000MB (2048000000 512 byte sectors: 255H 63S/T 127482C) da2 at ahc0 bus 0 target 0 lun 1 da2: Fixed Direct Access SCSI-4 device da2: Serial Number 3367957 da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da2: 673784MB (1379909632 512 byte sectors: 255H 63S/T 85895C) GEOM: new disk da0 GEOM: new disk da1 GEOM: new disk da2 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00040010 LDR: 0x02000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00040010 LDR: 0x04000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00040010 LDR: 0x08000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 2 (ISA IRQ 0) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic1: routing intpin 0 (PCI IRQ 24) to cluster 0 ioapic1: routing intpin 1 (PCI IRQ 25) to cluster 0 ioapic2: routing intpin 0 (PCI IRQ 28) to cluster 0 [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:71681967 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da0s1, start 32256 length 36701167104 end 36701199359 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/26/32 s:63 l:2047999937 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da1s1, start 32256 length 1048575967744 end 1048575999999 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:1379903112 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da2s1, start 32256 length 706510393344 end 706510425599 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da0s1a, start 0 length 35433480192 end 35433480191 GEOM: Configure da0s1b, start 35433480192 length 1267686912 end 36701167103 GEOM: Configure da0s1c, start 0 length 36701167104 end 36701167103 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da1s1a, start 0 length 107374182400 end 107374182399 GEOM: Configure da1s1b, start 214748364800 length 34359738368 end 249108103167 GEOM: Configure da1s1c, start 0 length 1048575967744 end 1048575967743 GEOM: Configure da1s1f, start 107374182400 length 107374182400 end 214748364799 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da2s1b, start 107374182400 length 5368709120 end 112742891519 GEOM: Configure da2s1c, start 0 length 706510393344 end 706510393343 GEOM: Configure da2s1e, start 0 length 107374182400 end 107374182399 GEOM: Configure da2s1f, start 112742891520 length 593767501824 end 706510393343 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 Mounting root from ufs:/dev/da0s1a start_init: trying /sbin/init From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 16:40:25 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3FC516A4D6 for ; Wed, 8 Dec 2004 16:40:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF0F43D2D for ; Wed, 8 Dec 2004 16:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB8GePXQ070795 for ; Wed, 8 Dec 2004 16:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB8GePQl070794; Wed, 8 Dec 2004 16:40:25 GMT (envelope-from gnats) Date: Wed, 8 Dec 2004 16:40:25 GMT Message-Id: <200412081640.iB8GePQl070794@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Wei-Kai Wu Subject: Re: amd64/74608: mpt hangs 5 minutes when booting X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Wei-Kai Wu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 16:40:26 -0000 The following reply was made to PR amd64/74608; it has been noted by GNATS. From: Wei-Kai Wu To: Xin LI Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/74608: mpt hangs 5 minutes when booting Date: Thu, 9 Dec 2004 00:33:14 +0800 is there (id=74601022) AcpiOsDerivePciId: bus 0 dev 7 func 3 acpi0: Power Button (fixed) AcpiOsDerivePciId: bus 0 dev 10 func 0 ACPI timer: 1/2 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc008-0xc00b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pcib0: could not get PCI interrupt routing table for \\_SB_.PCI0 - AE_NOT_FOUND pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1022, dev=0x7460, revid=0x07 bus=0, slot=6, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x73 (3450 ns), mingnt=0x0e (3500 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7468, revid=0x05 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001000, size 4, enabled found-> vendor=0x1022, dev=0x7469, revid=0x03 bus=0, slot=7, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x746b, revid=0x05 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=0, slot=10, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 64, base fc000000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=0, slot=10, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 64, base fc001000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=0, slot=11, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=25, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=25, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=25, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=25, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=26, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=26, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=26, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=26, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=27, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=27, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=27, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=27, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib1: at device 6.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x2000-0x2fff pcib1: memory decode 0xfc100000-0xfdffffff pcib1: prefetched decode 0xfff00000-0xfffff ACPI PCI link initial configuration: pci1: on pcib1 pci1: physical bus=1 map[10]: type 1, range 32, base fd000000, size 24, enabled pcib1: device (null) requested decoded memory range 0xfd000000-0xfdffffff map[14]: type 4, range 32, base 00002000, size 8, enabled pcib1: device (null) requested decoded I/O range 0x2000-0x20ff map[18]: type 1, range 32, base fc100000, size 12, enabled pcib1: device (null) requested decoded memory range 0xfc100000-0xfc100fff pcib1: matched entry for 1.6.INTA pcib1: slot 6 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4752, revid=0x27 bus=1, slot=6, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=18 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x3000-0x3fff pcib2: memory decode 0xfe000000-0xfe0fffff pcib2: prefetched decode 0xfff00000-0xfffff ACPI PCI link initial configuration: pci2: on pcib2 pci2: physical bus=2 map[10]: type 4, range 32, base 00003000, size 8, enabled pcib2: device (null) requested decoded I/O range 0x3000-0x30ff map[14]: type 1, range 64, base fe010000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe010000-0xfe01ffff map[1c]: type 1, range 64, base fe000000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe000000-0xfe00ffff pcib2: matched entry for 2.4.INTA pcib2: slot 4 INTA hardwired to IRQ 24 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=2, slot=4, func=0 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=a, irq=24 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 00003400, size 8, enabled pcib2: device (null) requested decoded I/O range 0x3400-0x34ff map[14]: type 1, range 64, base fe030000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe030000-0xfe03ffff map[1c]: type 1, range 64, base fe020000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe020000-0xfe02ffff pcib2: matched entry for 2.4.INTB pcib2: slot 4 INTB hardwired to IRQ 25 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=2, slot=4, func=1 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=b, irq=25 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base fe050000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe050000-0xfe05ffff map[18]: type 1, range 64, base fe040000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe040000-0xfe04ffff pcib2: matched entry for 2.9.INTA pcib2: slot 9 INTA hardwired to IRQ 24 found-> vendor=0x14e4, dev=0x1648, revid=0x03 bus=2, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0016, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=24 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base fe070000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe070000-0xfe07ffff map[18]: type 1, range 64, base fe060000, size 16, enabled pcib2: device (null) requested decoded memory range 0xfe060000-0xfe06ffff pcib2: matched entry for 2.9.INTB pcib2: slot 9 INTB hardwired to IRQ 25 found-> vendor=0x14e4, dev=0x1648, revid=0x03 bus=2, slot=9, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0016, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=b, irq=25 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit mpt0: port 0x3000-0x30ff mem 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 4.0 on pci2 mpt0: Reserved 0x10000 bytes for rid 0x14 type 3 at 0xfe010000 mpt0: [GIANT-LOCKED] mpt0: soft reset mpt1: port 0x3400-0x34ff mem 0xfe020000-0xfe02ffff,0xfe030000-0xfe03ffff irq 25 at device 4.1 on pci2 mpt1: linking with peer (mpt0) mpt1: Reserved 0x10000 bytes for rid 0x14 type 3 at 0xfe030000 mpt1: [GIANT-LOCKED] mpt1: soft reset bge0: mem 0xfe040000-0xfe04ffff,0xfe050000-0xfe05ffff irq 24 at device 9.0 on pci2 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe050000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:e0:81:63:4f:2e bge0: [MPSAFE] bge1: mem 0xfe060000-0xfe06ffff,0xfe070000-0xfe07ffff irq 25 at device 9.1 on pci2 bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe070000 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: bpf attached bge1: Ethernet address: 00:e0:81:63:4f:2d bge1: [MPSAFE] pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0x4000-0x4fff pcib3: memory decode 0xfe100000-0xfe1fffff pcib3: prefetched decode 0xfff00000-0xfffff AcpiOsDerivePciId: bus 0 dev 11 func 0 ACPI PCI link initial configuration: pci3: on pcib3 pci3: physical bus=3 map[10]: type 4, range 32, base 00004000, size 8, enabled pcib3: device (null) requested decoded I/O range 0x4000-0x40ff map[14]: type 1, range 64, base fe100000, size 12, enabled pcib3: device (null) requested decoded memory range 0xfe100000-0xfe100fff pcib3: matched entry for 3.3.INTA pcib3: slot 3 INTA hardwired to IRQ 28 found-> vendor=0x9005, dev=0x0080, revid=0x02 bus=3, slot=3, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=a, irq=28 powerspec 2 supports D0 D3 current D0 ahc0: port 0x4000-0x40ff mem 0xfe100000-0xfe100fff irq 28 at device 3.0 on pci3 ahc0: Defaulting to MEMIO on ahc0: Reserved 0x1000 bytes for rid 0x14 type 3 at 0xfe100000 ahc0: Enabling 39Bit Addressing ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 433 instructions downloaded ahc0: Features 0x1def6, Bugs 0x40, Flags 0x21485560 ahc0: [GIANT-LOCKED] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pci0: at device 11.1 (no driver attached) psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) atkbdc: atkbdc0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ahc_isa_probe 0: ioport 0xc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0 failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0 failed to probe at port 0x3f8 irq 4 on isa0 sio1 failed to probe at port 0x2f8 irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xffffffff800b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 238312 -> 100000 Timecounter "TSC" frequency 1804102097 Hz quality -100 Timecounters tick every 0.976 msec lo0: bpf attached ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging disabled Waiting 3 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe1:mpt0:0:1:0): error 22 (probe1:mpt0:0:1:0): Unretryable Error (probe2:mpt0:0:2:0): error 22 (probe2:mpt0:0:2:0): Unretryable Error (probe3:mpt0:0:3:0): error 22 (probe3:mpt0:0:3:0): Unretryable Error (probe4:mpt0:0:4:0): error 22 (probe4:mpt0:0:4:0): Unretryable Error (probe5:mpt0:0:5:0): error 22 (probe5:mpt0:0:5:0): Unretryable Error (probe7:mpt0:0:8:0): error 22 (probe7:mpt0:0:8:0): Unretryable Error ahc0: Selection Timeout on A:4. 0 SCBs aborted (probe8:mpt0:0:9:0): error 22 (probe8:mpt0:0:9:0): Unretryable Error (probe17:mpt1:0:2:0): error 22 (probe17:mpt1:0:2:0): Unretryable Error (probe9:mpt0:0:10:0): error 22 (probe9:mpt0:0:10:0): Unretryable Error ahc0: Selection Timeout on A:12. 0 SCBs aborted (probe18:mpt1:0:3:0): error 22 (probe18:mpt1:0:3:0): Unretryable Error (probe10:mpt0:0:11:0): error 22 (probe10:mpt0:0:11:0): Unretryable Error ahc0: Selection Timeout on A:13. 0 SCBs aborted (probe25:mpt1:0:11:0): error 22 (probe25:mpt1:0:11:0): Unretryable Error (probe11:mpt0:0:12:0): error 22 (probe11:mpt0:0:12:0): Unretryable Error ahc0: Selection Timeout on A:1. 0 SCBs aborted (probe15:mpt1:0:0:0): error 22 (probe15:mpt1:0:0:0): Unretryable Error (probe12:mpt0:0:13:0): error 22 (probe12:mpt0:0:13:0): Unretryable Error ahc0: Selection Timeout on A:2. 0 SCBs aborted (probe16:mpt1:0:1:0): error 22 (probe16:mpt1:0:1:0): Unretryable Error (probe13:mpt0:0:14:0): error 22 (probe13:mpt0:0:14:0): Unretryable Error ahc0: Selection Timeout on A:3. 0 SCBs aborted (probe19:mpt1:0:4:0): error 22 (probe19:mpt1:0:4:0): Unretryable Error (probe14:mpt0:0:15:0): error 22 (probe14:mpt0:0:15:0): Unretryable Error ahc0: Selection Timeout on A:5. 0 SCBs aborted (probe20:mpt1:0:5:0): error 22 (probe20:mpt1:0:5:0): Unretryable Error ahc0: Selection Timeout on A:6. 0 SCBs aborted (probe21:mpt1:0:6:0): error 22 (probe21:mpt1:0:6:0): Unretryable Error ahc0: Selection Timeout on A:8. 0 SCBs aborted (probe22:mpt1:0:8:0): error 22 (probe22:mpt1:0:8:0): Unretryable Error (probe0:mpt0:0:0:0): Retrying Command ahc0: Selection Timeout on A:9. 0 SCBs aborted (probe23:mpt1:0:9:0): error 22 (probe23:mpt1:0:9:0): Unretryable Error ahc0: Selection Timeout on A:10. 0 SCBs aborted (probe24:mpt1:0:10:0): error 22 (probe24:mpt1:0:10:0): Unretryable Error ahc0: Selection Timeout on A:11. 0 SCBs aborted (probe26:mpt1:0:12:0): error 22 (probe26:mpt1:0:12:0): Unretryable Error ahc0: Selection Timeout on A:14. 0 SCBs aborted (probe27:mpt1:0:13:0): error 22 (probe27:mpt1:0:13:0): Unretryable Error ahc0: Selection Timeout on A:15. 0 SCBs aborted (probe30:ahc0:0:0:0): Retrying Command (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 80.0MHz DT, offset = 0x3e (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (probe0:ahc0:0:0:1): Retrying Command (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (probe28:mpt1:0:14:0): error 22 (probe28:mpt1:0:14:0): Unretryable Error (probe29:mpt1:0:15:0): error 22 (probe29:mpt1:0:15:0): Unretryable Error pass0 at mpt0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-3 device pass0: Serial Number 3FP00LZB000022070857 pass0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled pass1 at mpt0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device pass1: Serial Number 1 pass1: 3.300MB/s transfers pass2 at ahc0 bus 0 target 0 lun 0 pass2: Fixed Direct Access SCSI-4 device pass2: Serial Number 3367957 pass2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled pass3 at ahc0 bus 0 target 0 lun 1 pass3: Fixed Direct Access SCSI-4 device pass3: Serial Number 3367957 pass3: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled pass1 at mpt0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device pass1: Serial Number 1 pass1: 3.300MB/s transfers da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 3FP00LZB000022070857 da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687371 512 byte sectors: 255H 63S/T 4462C) da1 at ahc0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-4 device da1: Serial Number 3367957 da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da1: 1000000MB (2048000000 512 byte sectors: 255H 63S/T 127482C) da2 at ahc0 bus 0 target 0 lun 1 da2: Fixed Direct Access SCSI-4 device da2: Serial Number 3367957 da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da2: 673784MB (1379909632 512 byte sectors: 255H 63S/T 85895C) GEOM: new disk da0 GEOM: new disk da1 GEOM: new disk da2 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00040010 LDR: 0x02000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x02000000 VER: 0x00040010 LDR: 0x04000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x03000000 VER: 0x00040010 LDR: 0x08000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x000001ff ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 2 (ISA IRQ 0) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic1: routing intpin 0 (PCI IRQ 24) to cluster 0 ioapic1: routing intpin 1 (PCI IRQ 25) to cluster 0 ioapic2: routing intpin 0 (PCI IRQ 28) to cluster 0 [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:71681967 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da0s1, start 32256 length 36701167104 end 36701199359 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/26/32 s:63 l:2047999937 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da1s1, start 32256 length 1048575967744 end 1048575999999 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:1379903112 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da2s1, start 32256 length 706510393344 end 706510425599 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da0s1a, start 0 length 35433480192 end 35433480191 GEOM: Configure da0s1b, start 35433480192 length 1267686912 end 36701167103 GEOM: Configure da0s1c, start 0 length 36701167104 end 36701167103 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da1s1a, start 0 length 107374182400 end 107374182399 GEOM: Configure da1s1b, start 214748364800 length 34359738368 end 249108103167 GEOM: Configure da1s1c, start 0 length 1048575967744 end 1048575967743 GEOM: Configure da1s1f, start 107374182400 length 107374182400 end 214748364799 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 GEOM: Configure da2s1b, start 107374182400 length 5368709120 end 112742891519 GEOM: Configure da2s1c, start 0 length 706510393344 end 706510393343 GEOM: Configure da2s1e, start 0 length 107374182400 end 107374182399 GEOM: Configure da2s1f, start 112742891520 length 593767501824 end 706510393343 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:0): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 (ahc0:A:0:1): Sending PPR bus_width 1, period 9, offset 3e, ppr_options 2 (ahc0:A:0:1): Received PPR width 1, period 9, offset 3e,options 2 Filtered to width 1, period 9, offset 3e, options 2 Mounting root from ufs:/dev/da0s1a start_init: trying /sbin/init From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 17:05:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33E5E16A4CE; Wed, 8 Dec 2004 17:05:58 +0000 (GMT) Received: from harik.murex.com (mail.murex.com [194.98.239.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id A19F843D46; Wed, 8 Dec 2004 17:05:57 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from interscan.fr.murex.com (iscan.murex.fr [172.21.17.207] (may be forged)) by harik.murex.com with ESMTP id iB8Gw7ka006209; Wed, 8 Dec 2004 17:58:07 +0100 (CET) Received: from mxmail.murex.com (interscan.murex.fr [127.0.0.1]) by interscan.fr.murex.com (8.11.6/8.11.6) with ESMTP id iB8HTTs28276; Wed, 8 Dec 2004 18:29:29 +0100 Received: from mteterin.us.murex.com ([172.21.130.86]) by mxmail.murex.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 8 Dec 2004 18:05:30 +0100 From: Mikhail Teterin Organization: Virtual Estates, Inc. Date: Wed, 8 Dec 2004 12:05:38 -0500 User-Agent: KMail/1.7.1 To: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081205.39354.mi+mx@aldan.algebra.com> X-OriginalArrivalTime: 08 Dec 2004 17:05:31.0028 (UTC) FILETIME=[1F924540:01C4DD48] cc: ade@FreeBSD.org cc: Kris Kennaway Subject: new TCL vs. current-6 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, 08 Dec 2004 17:05:58 -0000 Three of my TCL-based ports fail now on amd64 running current-6. All failures occur, when an attempt is made to use the TCL-interpreter -- either to run the port's self-tests, or to generate the manual pages. The failures are either "Floating point exceptions" or "Segmentation faults" and appear to only happen on amd64 (may be, on ia64 as well): http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html Can anyone confirm being able to use freshly built TCL on amd64 _at all_? My ports did not change in months -- what could be wrong with TCL and/or amd64? Thanks! -mi From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 17:13:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA75E16A4E9; Wed, 8 Dec 2004 17:13:22 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD0443D60; Wed, 8 Dec 2004 17:13:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 52F455141A; Wed, 8 Dec 2004 09:19:47 -0800 (PST) Date: Wed, 8 Dec 2004 09:19:47 -0800 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20041208171947.GA46271@xor.obsecurity.org> References: <200412081205.39354.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org cc: ade@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 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, 08 Dec 2004 17:13:23 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 08, 2004 at 12:05:38PM -0500, Mikhail Teterin wrote: > Three of my TCL-based ports fail now on amd64 running current-6. All fail= ures=20 > occur, when an attempt is made to use the TCL-interpreter -- either to ru= n=20 > the port's self-tests, or to generate the manual pages. The failures are= =20 > either "Floating point exceptions" or "Segmentation faults" and appear to= =20 > only happen on amd64 (may be, on ia64 as well): >=20 > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html >=20 > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? >=20 > My ports did not change in months -- what could be wrong with TCL and/or= =20 > amd64? Peter speculated a problem when the world is built with -O2 (with or without -fno-strict-aliasing). I haven't been able to confirm this by testing with a world built with -O, because I only have one working amd64 package builder. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtzezWry0BWjoQKURAgNWAKDkKLJ2A8O/20nlScYHDdvpqvMr1gCdH0fe Mg8vbrXTRD0BWCrspYw/6cY= =uNBu -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 17:29:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31E9216A4CE; Wed, 8 Dec 2004 17:29:07 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2225443D55; Wed, 8 Dec 2004 17:29:07 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 66-169-240-6.or.charter.com ([66.169.240.6] helo=[10.21.91.101]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1Cc5cg-0008y9-Vm; Wed, 08 Dec 2004 17:29:07 +0000 Message-ID: <41B739E1.8080304@FreeBSD.org> Date: Wed, 08 Dec 2004 09:29:05 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mikhail Teterin References: <200412081205.39354.mi+mx@aldan.algebra.com> In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 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, 08 Dec 2004 17:29:07 -0000 Mikhail Teterin wrote: > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > My ports did not change in months -- what could be wrong with TCL and/or > amd64? No idea. My one and only working amd64 box (the other is a presario r3000z laptop, don't laugh :P) is running 5.3-STABLE and attempting to do GNOME package building. Sorry. -aDe From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 17:29:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B52A816A4CE; Wed, 8 Dec 2004 17:29:34 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F5F643D55; Wed, 8 Dec 2004 17:29:34 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB8HTYF09966; Wed, 8 Dec 2004 09:29:34 -0800 (PST) Date: Wed, 8 Dec 2004 09:29:34 -0800 From: Mike Hunter To: Ruslan Ermilov Message-ID: <20041208172934.GB9252@ack.Berkeley.EDU> References: <20041208013716.GA10869@ack.Berkeley.EDU> <20041208074109.GB35079@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041208074109.GB35079@ip.net.ua> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@FreeBSD.org cc: Peter Wemm Subject: Re: device apic? 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, 08 Dec 2004 17:29:34 -0000 On Dec 08, "Ruslan Ermilov" wrote: > On Tue, Dec 07, 2004 at 05:37:16PM -0800, Mike Hunter wrote: > > Hi, > > > > I'm successfully up to 5.3-STABLE / RELENG_5 as of today :) > > > > In order to build my kernel I had to leave out apic, even though I had > > options SMP...has something changed? > > > > # make buildkernel KERNCONF=mybox > > > > config: Error: device "apic" is unknown > > config: 1 errors > > *** Error code 1 > > > There's no separate "device apic" on amd64, it's standard part > of any kernel. It order to turn it off, you either need to do > it in your machine's BIOS, or set hint.apic.0.disabled=1 in > /boot/loader.conf. > > Peter, can you tweak amd64/NOTES to *not* mention "device apic", > as it's confusing? I do want it, I was just confused about the kernel config. Thanks very much for clearing it up! Mike From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 18:08:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1A5816A4CE for ; Wed, 8 Dec 2004 18:08:59 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97A1A43D3F for ; Wed, 8 Dec 2004 18:08:59 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB8I8wN17345; Wed, 8 Dec 2004 10:08:58 -0800 (PST) Date: Wed, 8 Dec 2004 10:08:58 -0800 From: Mike Hunter To: Mike Jakubik Message-ID: <20041208180858.GA10932@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041207233101.GA29595@ack.Berkeley.EDU> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Same problem w/ 5.3 (Was: problems compiling perl 5.8.5 w/ fbsd 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: Wed, 08 Dec 2004 18:08:59 -0000 On Dec 07, "To Mike Jakubik" wrote: Hi, > On Dec 07, "Mike Jakubik" wrote: > > > I'm new to amd64 as of this nice new dual opteron box I've just > > > received...I may be seeing a lot of you guys in the coming weeks :) > > > > Any reason why you installed 5.2.1 (Its an old pre-release version)? If > > this is a fresh box, then i highly recommend you install 5.3 instead. Perl > > 5.8.5 is packaged with 5.3 too. > > Actually I did 5.2.1 because that was the install media I had handy :) > I'm building a RELENG_5 world/kernel as we speak...I'll be back if it > doesn't work out :) I upgraded to 5.3, but I still am having the same problem: #uname -a FreeBSD mybox 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Dec 7 15:35:28 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 `WITH_GDBM=1 make` works fine, but `make test` still fails. It hangs for a long time on lib/Config................................ And...and I was going to copy and paste the same error message as I sent yesterday, but instead ssh hung up on me, and the console has the following bad news: swap_pager: out of swap space swap_pager_getwwapspace(16): failed ...sshd was killed ...out of swap space Top says it was a very big boy indeed while it was running: 17771 root 130 0 10732M 2470M CPU0 0 13:41 103.17% 103.17% perl I'm willing to do a binary package as a last resort, but I'm planning on building code on this box so it'd be better to get this resolved properly :) I'm going to try changing the perl MALLOC options. This machine has 8G of ram, are there still problems with large memory on amd64? Thanks for any help, Mike From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 18:13:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28C3E16A4CE for ; Wed, 8 Dec 2004 18:13:12 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id F153A43D4C for ; Wed, 8 Dec 2004 18:13:11 +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 iB8IFW2J001054; Wed, 8 Dec 2004 10:15:32 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iB8IFW3Z001053; Wed, 8 Dec 2004 10:15:32 -0800 Date: Wed, 8 Dec 2004 10:15:32 -0800 From: Brooks Davis To: Mike Hunter Message-ID: <20041208181532.GA638@odin.ac.hmc.edu> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> <20041208180858.GA10932@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <20041208180858.GA10932@ack.Berkeley.EDU> 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: Same problem w/ 5.3 (Was: problems compiling perl 5.8.5 w/ fbsd 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: Wed, 08 Dec 2004 18:13:12 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 08, 2004 at 10:08:58AM -0800, Mike Hunter wrote: > On Dec 07, "To Mike Jakubik" wrote: >=20 > Hi, >=20 > > On Dec 07, "Mike Jakubik" wrote: >=20 > > > > I'm new to amd64 as of this nice new dual opteron box I've just > > > > received...I may be seeing a lot of you guys in the coming weeks :) > > >=20 > > > Any reason why you installed 5.2.1 (Its an old pre-release version)? = If > > > this is a fresh box, then i highly recommend you install 5.3 instead.= Perl > > > 5.8.5 is packaged with 5.3 too. > >=20 > > Actually I did 5.2.1 because that was the install media I had handy :) > > I'm building a RELENG_5 world/kernel as we speak...I'll be back if it > > doesn't work out :) >=20 > I upgraded to 5.3, but I still am having the same problem: >=20 > #uname -a=20 > FreeBSD mybox 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Dec 7 15:35:28 PST 2= 004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 >=20 > `WITH_GDBM=3D1 make` works fine, but `make test` still fails. It hangs f= or > a long time on=20 >=20 > lib/Config................................ >=20 > And...and I was going to copy and paste the same error message as I sent > yesterday, but instead ssh hung up on me, and the console has the > following bad news: >=20 > swap_pager: out of swap space > swap_pager_getwwapspace(16): failed > ...sshd was killed ...out of swap space >=20 > Top says it was a very big boy indeed while it was running: >=20 > 17771 root 130 0 10732M 2470M CPU0 0 13:41 103.17% 103.17% perl >=20 > I'm willing to do a binary package as a last resort, but I'm planning on > building code on this box so it'd be better to get this resolved properly > :) >=20 > I'm going to try changing the perl MALLOC options. This machine has 8G of > ram, are there still problems with large memory on amd64? A fix for mmap's larger then 2GB was committed to HEAD yesterday so it's possiable that's your issue. -- 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 --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBt0TDXY6L6fI4GtQRAg+dAJ93iugxtOWxtXiPsdK5eJBDHJ3X2ACg4IA+ 5/dub0zjFFR12bpxHv1x+4w= =mwFK -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 18:54:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F7AD16A4CE for ; Wed, 8 Dec 2004 18:54:25 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B64943D49 for ; Wed, 8 Dec 2004 18:54:25 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB8IsNT20062; Wed, 8 Dec 2004 10:54:23 -0800 (PST) Date: Wed, 8 Dec 2004 10:54:23 -0800 From: Mike Hunter To: Brooks Davis Message-ID: <20041208185423.GA19687@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> <20041208180858.GA10932@ack.Berkeley.EDU> <20041208181532.GA638@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041208181532.GA638@odin.ac.hmc.edu> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: Same problem w/ 5.3 (Was: problems compiling perl 5.8.5 w/ fbsd 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: Wed, 08 Dec 2004 18:54:25 -0000 On Dec 08, "Brooks Davis" wrote: > > I'm willing to do a binary package as a last resort, but I'm planning on > > building code on this box so it'd be better to get this resolved properly > > :) > > > > I'm going to try changing the perl MALLOC options. This machine has 8G of > > ram, are there still problems with large memory on amd64? > > A fix for mmap's larger then 2GB was committed to HEAD yesterday so it's > possiable that's your issue. Thanks. Do you know if there are plans to MFC that fix to 5-STABLE? I know beggers can't be choosers, but I'm not sure I have the heart for current on this server. Thanks, Mike From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 22:30:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E208916A4CE for ; Wed, 8 Dec 2004 22:30:22 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A14C43D54 for ; Wed, 8 Dec 2004 22:30:22 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 78921744 for ; Wed, 8 Dec 2004 17:30:21 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 5A6EE532; Wed, 8 Dec 2004 17:29:50 -0500 (EST) Date: Wed, 8 Dec 2004 17:29:50 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041208222950.GB21601@gargantuan.com> References: <20041206164250.GC28404@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa" Content-Disposition: inline In-Reply-To: <20041206164250.GC28404@gargantuan.com> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: MC: phoenix.gargantuan.com 1128; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. Subject: Re: amd64 laptop recommendations 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, 08 Dec 2004 22:30:23 -0000 --5I6of5zJg18YgZEa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-06T11:42:50-0500, Michael W. Oliver wrote: > I am in the market for an AMD64-based laptop, and am currently leaning > toward the Acer Ferrari 3400, but would like to borrow a few minutes of > your time to ask for suggestions on something better. OK, following up to myself here, and to supplement the below information on the Ferrari with what I found on another site, once again to get your input/advice before buying. I found a new machine at abscomputer.com called the 'Mayhem G3', which has a few notable differences from the Acer Ferrari 3400, such as: > o CPU - AMD64 3200+ (2.0 Ghz) This is actually a AMD64 3000+ (2.0GHz) CPU, with 512k L2 cache, on the Ferrari. On the Mayhem, I have the option of a AMD64 3700+ CPU (2.4 GHz) with 1MB L2 cache. > o LAN - Broadcom BCM5788M The Mayhem has a RTL8201CL, which doesn't look to be supported by either the re(4) or rl(4) drivers :( > o Wireless - Broadcom BCM4306KFB (mini-PCI, maybe replaceable with > atheros-based a/b/g card????) The Mayhem comes with an Engenius-branded Atheros card, 802.11 b/g, model NI-3054MP (Aries2). The Mini-PCI card actually has the model number "NL-5354MP+ARIES2(F)-1.00" on it. Noting Sam's posts to current@ today about the updated ath hal and such, this is tempting. > o bluetooth / modem - CSR BC212615BEN-E4 (agere scorpio) no integrated bluetooth on the Mayhem :-/ > o Via K8T800 chipset, Via VT8235CE SiS 755 + SiS SB 963L on the Mayhem. Ho hum, don't know enough about either to care one way or the other. > o Phoenix BIOS (hoping for hw.acpi.s4bios=3D1) Nobody could tell me about the BIOS of the Mayhem. Both laptops have the ATI Radeon 9700 w/128MB. The Ferrari comes with 512MB DRAM, while the Mayhem comes with 1GB. The Ferrari has 4 USB ports, while the Mayhem has 3. With the above noted options for the Mayhem, the price is within a few dollars of the Ferrari, so price is only significant in that I will get (mostly) more for my money from an off-brand manufacturer. If you have an opinion, I would very much like to hear it. Indecision sucks. Thanks. --=20 Michael W. Oliver [see complete headers for contact information] --5I6of5zJg18YgZEa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt4BesWv7q8X6o8kRAsrYAJ93/5A0OEFgTSkmyA9UXy1zGNwqZgCgnHPZ 0XrAsGWVUgmhSXweXL1MD28= =BoPS -----END PGP SIGNATURE----- --5I6of5zJg18YgZEa-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 23:02:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82A4016A4CE for ; Wed, 8 Dec 2004 23:02:26 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FED643D5A for ; Wed, 8 Dec 2004 23:02:25 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.208] [213.112.167.208]) by mxfep01.bredband.com with ESMTP <20041208230223.XPHO18879.mxfep01.bredband.com@[192.168.245.231]>; Thu, 9 Dec 2004 00:02:23 +0100 Message-ID: <41B787C2.9010107@bredband.net> Date: Thu, 09 Dec 2004 00:01:22 +0100 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael W. Oliver" References: <20041206164250.GC28404@gargantuan.com> <20041208222950.GB21601@gargantuan.com> In-Reply-To: <20041208222950.GB21601@gargantuan.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: amd64 laptop recommendations 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, 08 Dec 2004 23:02:26 -0000 Michael W. Oliver wrote: > On 2004-12-06T11:42:50-0500, Michael W. Oliver wrote: > > > Both laptops have the ATI Radeon 9700 w/128MB. The Ferrari comes with > 512MB DRAM, while the Mayhem comes with 1GB. The Ferrari has 4 USB > ports, while the Mayhem has 3. > The Max RAM on the G3 seems to be 1 GB whilst the Ferarri can can have 2 GB RAM. My AMD64 PC did use about 800 MB RAM while compiling/building Ports in 64 bit mode. Most of that was probably buffer cache. But if you want to run VMWare or similar and an additional OS concurrently I dont like the 1 GB limit. //Lars From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 23:02:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B47F16A4CE for ; Wed, 8 Dec 2004 23:02:56 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id D327F43D60 for ; Wed, 8 Dec 2004 23:02:50 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from [192.168.1.102] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <2004120823024401500ed973e>; Wed, 8 Dec 2004 23:02:45 +0000 Message-ID: <41B78815.9060504@pythonemproject.com> Date: Wed, 08 Dec 2004 15:02:45 -0800 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael W. Oliver" References: <20041206164250.GC28404@gargantuan.com> <20041208222950.GB21601@gargantuan.com> In-Reply-To: <20041208222950.GB21601@gargantuan.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: amd64 laptop recommendations 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, 08 Dec 2004 23:02:56 -0000 Michael W. Oliver wrote: >On 2004-12-06T11:42:50-0500, Michael W. Oliver wrote: > > >>I am in the market for an AMD64-based laptop, and am currently leaning >>toward the Acer Ferrari 3400, but would like to borrow a few minutes of >>your time to ask for suggestions on something better. >> >> > >OK, following up to myself here, and to supplement the below information >on the Ferrari with what I found on another site, once again to get your >input/advice before buying. > >I found a new machine at abscomputer.com called the 'Mayhem G3', which >has a few notable differences from the Acer Ferrari 3400, such as: > > > >>o CPU - AMD64 3200+ (2.0 Ghz) >> >> > >This is actually a AMD64 3000+ (2.0GHz) CPU, with 512k L2 cache, on the >Ferrari. On the Mayhem, I have the option of a AMD64 3700+ CPU (2.4 >GHz) with 1MB L2 cache. > > > >>o LAN - Broadcom BCM5788M >> >> > >The Mayhem has a RTL8201CL, which doesn't look to be supported by either >the re(4) or rl(4) drivers :( > > > >>o Wireless - Broadcom BCM4306KFB (mini-PCI, maybe replaceable with >> atheros-based a/b/g card????) >> >> > >The Mayhem comes with an Engenius-branded Atheros card, 802.11 b/g, >model NI-3054MP (Aries2). The Mini-PCI card actually has the model >number "NL-5354MP+ARIES2(F)-1.00" on it. Noting Sam's posts to current@ >today about the updated ath hal and such, this is tempting. > > > >>o bluetooth / modem - CSR BC212615BEN-E4 (agere scorpio) >> >> > >no integrated bluetooth on the Mayhem :-/ > > > >>o Via K8T800 chipset, Via VT8235CE >> >> > >SiS 755 + SiS SB 963L on the Mayhem. Ho hum, don't know enough about >either to care one way or the other. > > > >>o Phoenix BIOS (hoping for hw.acpi.s4bios=1) >> >> > >Nobody could tell me about the BIOS of the Mayhem. > >Both laptops have the ATI Radeon 9700 w/128MB. The Ferrari comes with >512MB DRAM, while the Mayhem comes with 1GB. The Ferrari has 4 USB >ports, while the Mayhem has 3. > >With the above noted options for the Mayhem, the price is within a few >dollars of the Ferrari, so price is only significant in that I will get >(mostly) more for my money from an off-brand manufacturer. > >If you have an opinion, I would very much like to hear it. Indecision >sucks. > >Thanks. > > > Oh jeez, you guys got my mouth watering with this discussion. I have an AMD64 + 3800 on an Abit AV8, (socket 939) The idea of a AMD64 laptop being available has gotten my attention. However, I have had big problems trying to load a Windoze application that I really love, IVisit, which is a video chat application. I found that no 32 bit Windoze video driver would load on AMD64. For Windoze, I'm using the XP-64 bit beta. So I guess I'll need to wait. But FBSD works fine. Rob. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 8 23:37:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36C2A16A4CE for ; Wed, 8 Dec 2004 23:37:04 +0000 (GMT) Received: from mail.cisnet.com (mail.cisnet.com [68.22.80.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B835B43D53 for ; Wed, 8 Dec 2004 23:37:03 +0000 (GMT) (envelope-from klowther@cisnet.com) Received: from [68.254.146.229] (unverified [68.254.146.229]) by mail.cisnet.comfor ; Wed, 8 Dec 2004 18:37:03 -0500 Message-ID: <41B7901E.9050908@cisnet.com> Date: Wed, 08 Dec 2004 18:37:02 -0500 From: Ken Lowther User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 32 bit compatability 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, 08 Dec 2004 23:37:04 -0000 I have been reading the archives on this issue and am getting some info bit by bit. I am running 5.3 Release amd64 I have edited /etc/make.conf and added: WITH_LIB32=YES I have edited my version of MYKERNEL to include : options SMP options QUOTA options COMPAT_IA32 # Compatible with i386 binaries (last one in by default) Did make depend, make, and make insall. Rebooted. Kernel looks like it installed because quotas now work: hostserv1# quota -v Disk quotas for user root (uid 0): Filesystem usage quota limit grace files quota limit grace /home 130108 0 0 3660 0 0 /usr 1054978 0 0 67161 0 0 /var 6580 0 0 1031 0 0 I gather this means the kernel suports the 32 bit compat mode from the posts I have seen so far: hostserv1# sysctl kern.elf32 kern.elf32.fallback_brand: -1 hostserv1# After this I seem to be lost. I have seen references to various things, but bottom line, where do I go from here. The script under tools is obsolete now? install32.sh? I get the impression that this stuff was supposed to compile with the kernel but Google doesn't help me find any one place that is a step by step walk through. Thanks Ken From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 00:11:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 201E716A4CE; Thu, 9 Dec 2004 00:11:13 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id D084D43D1D; Thu, 9 Dec 2004 00:11:12 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])iB909JHY029515; Wed, 8 Dec 2004 18:09:19 -0600 (CST) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)iB909Gu6029512; Wed, 8 Dec 2004 18:09:18 -0600 (CST) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Wed, 8 Dec 2004 18:09:16 -0600 (CST) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: Mikhail Teterin In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> Message-ID: <20041208180601.T29045@area51.capnet.state.tx.us> References: <200412081205.39354.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: ade@freebsd.org cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:11:13 -0000 On Wed, 8 Dec 2004, Mikhail Teterin wrote: > Three of my TCL-based ports fail now on amd64 running current-6. All failures > occur, when an attempt is made to use the TCL-interpreter -- either to run > the port's self-tests, or to generate the manual pages. The failures are > either "Floating point exceptions" or "Segmentation faults" and appear to > only happen on amd64 (may be, on ia64 as well): > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > My ports did not change in months -- what could be wrong with TCL and/or > amd64? I just build expect a few minutes ago on: FreeBSD rc.capnet.state.tx.us 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Wed Dec 8 11:39:15 CST 2004 stu@rc.capnet.state.tx.us:/usr/obj/usr/src/sys/SMP amd64 and it seems to work fine, though I haven't pushed it. Let me know if you need specific tests. I can do a -current tomorrow, possibly. stu From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 00:32:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68C2716A4CE for ; Thu, 9 Dec 2004 00:32:35 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4752D43D7F for ; Thu, 9 Dec 2004 00:32:35 +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 F194C2A8E0 for ; Wed, 8 Dec 2004 16:31:58 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id A4CEEE2B5 for ; Wed, 8 Dec 2004 16:31:58 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iB90Vv0h083468; Wed, 8 Dec 2004 16:31:57 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iB90VvCB083467; Wed, 8 Dec 2004 16:31:57 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 8 Dec 2004 16:31:57 -0800 User-Agent: KMail/1.7.1 References: <41B7901E.9050908@cisnet.com> In-Reply-To: <41B7901E.9050908@cisnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081631.57451.peter@wemm.org> Subject: Re: 32 bit compatability 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, 09 Dec 2004 00:32:35 -0000 On Wednesday 08 December 2004 03:37 pm, Ken Lowther wrote: > I have been reading the archives on this issue and am getting some > info bit by bit. > > I am running 5.3 Release amd64 > > I have edited /etc/make.conf and added: > WITH_LIB32=YES > > I have edited my version of MYKERNEL to include : > options SMP > options QUOTA > options COMPAT_IA32 # Compatible with i386 > binaries (last one in by default) > > Did make depend, make, and make insall. > > Rebooted. Kernel looks like it installed because quotas now work: > > hostserv1# quota -v > Disk quotas for user root (uid 0): > Filesystem usage quota limit grace files quota > limit grace > /home 130108 0 0 3660 0 > 0 /usr 1054978 0 0 67161 0 0 > /var 6580 0 0 1031 0 0 > > I gather this means the kernel suports the 32 bit compat mode from > the posts I have seen so far: > > hostserv1# sysctl kern.elf32 > kern.elf32.fallback_brand: -1 > hostserv1# > > After this I seem to be lost. I have seen references to various > things, but bottom line, where do I go from here. The script under > tools is obsolete now? install32.sh? I get the impression that this > stuff was supposed to compile with the kernel but Google doesn't help > me find any one place that is a step by step walk through. The 32 bit libraries are built as part of buildworld/installworld. However, if you still have a fresh world laying around, you might be able to build just the libraries part like this: cd /usr/src; make build32 make install32 If you have any trouble, then do a full buildworld etc and they will be included with it. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 01:11:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A605616A4CE for ; Thu, 9 Dec 2004 01:11:44 +0000 (GMT) Received: from mail.cisnet.com (mail.cisnet.com [68.22.80.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F15243D53 for ; Thu, 9 Dec 2004 01:11:44 +0000 (GMT) (envelope-from klowther@cisnet.com) Received: from [68.254.146.229] (unverified [68.254.146.229]) by mail.cisnet.comfor ; Wed, 8 Dec 2004 20:11:43 -0500 Message-ID: <41B7A64F.8080402@cisnet.com> Date: Wed, 08 Dec 2004 20:11:43 -0500 From: Ken Lowther User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-amd64@freebsd.org References: <41B7901E.9050908@cisnet.com> <200412081631.57451.peter@wemm.org> In-Reply-To: <200412081631.57451.peter@wemm.org> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 32 bit compatability 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, 09 Dec 2004 01:11:44 -0000 Peter Wemm wrote >The 32 bit libraries are built as part of buildworld/installworld. >However, if you still have a fresh world laying around, you might be >able to build just the libraries part like this: >cd /usr/src; >make build32 >make install32 > >If you have any trouble, then do a full buildworld etc and they will be >included with it. > > > OK. This may be where I am going wrong. I did an install kernel sources during the install, but some of the commands will not work for me. Mergemaster is not on my machine and "make buildworld" does not seem to work. I have tried to issue it from /usr/src and /usr/src/sys. I was under the impression from the Handbook that I only needed to do these after an upgrade any how. Off list some one suggested I would have to upgrade from Release to Stable. Ken From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 01:55:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B25B16A4CE for ; Thu, 9 Dec 2004 01:55:38 +0000 (GMT) Received: from frodo.anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39D443D4C for ; Thu, 9 Dec 2004 01:55:37 +0000 (GMT) (envelope-from c@nu.org) Received: from elrond.anembo.nu.org (elrond.anembo.nu.org [10.5.1.3]) by frodo.anembo.nu.org (8.13.1/8.13.1) with SMTP id iB91tarw008958 for ; Thu, 9 Dec 2004 12:55:36 +1100 (EST) Received: by elrond.anembo.nu.org (sSMTP sendmail emulation); Thu, 9 Dec 2004 12:55:36 +1100 Date: Thu, 9 Dec 2004 12:55:36 +1100 From: Christopher Vance To: freebsd-amd64@freebsd.org Message-ID: <20041209015536.GH3041@nu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Subject: install questions 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, 09 Dec 2004 01:55:38 -0000 I have been a happy user of FreeBSD/i386 since 2.2.6. I have always tracked stable, and often had current on another partition. I have i386 install CDs for 5.2, and have successfully used them to install /i386 on my amd64. I am considering upgrading to /amd64 on the same machine. Can I use the sysinstall I already have to do a network install of /amd64 stuff from a server somewhere, or do I need a 64-bit sysinstall to do this from? I'm happy to newfs the partition if that's appropriate - it has nothing valuable on it. I've seen suggestions that I can run /i386 stuff on /amd64 provided the kernel emulation is included and the 32-bit libraries are present. Are these 32-bit libraries identical to the i386 ones, or have they been tweaked to know they are emulating on /amd64? The SATA controller is a VIA, not the SiI 3512A &^%$ which made me abandon FreeBSD on a different machine. Any other things I need to know? (I've made a brief foray into Gentoo on this machine, and I'd rather do FreeBSD, where things are the way I'm used to.) -- Christopher Vance From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 12:33:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A336416A4CE for ; Thu, 9 Dec 2004 12:33:45 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id A434143D53 for ; Thu, 9 Dec 2004 12:33:44 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] ([144.133.92.247]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id iB9CXcWZ016178 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Thu, 9 Dec 2004 23:33:40 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <1102414274.671.33.camel@localhost> References: <20041206164250.GC28404@gargantuan.com> <1102414274.671.33.camel@localhost> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <75074CF1-49DE-11D9-80BD-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Thu, 9 Dec 2004 23:32:57 +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/622/Thu Dec 9 00:36:53 2004 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Subject: Kernel panic 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, 09 Dec 2004 12:33:45 -0000 Hello everybody 3 times in the past two weeks I had a kernel panic. Is there a way to get the panic message so I can report the problem... Thank you Jean-Yves From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 15:37:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E33D516A4CE for ; Thu, 9 Dec 2004 15:37:25 +0000 (GMT) Received: from enggate.uwi.tt (enggate.uwi.tt [196.3.139.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id F387E43D2F for ; Thu, 9 Dec 2004 15:37:24 +0000 (GMT) (envelope-from feisal@uwi.tt) Received: from localhost (localhost [127.0.0.1]) by enggate.uwi.tt (Postfix) with ESMTP id 1B44C1044B for ; Thu, 9 Dec 2004 11:35:33 -0400 (AST) Received: from enggate.uwi.tt ([127.0.0.1]) by localhost (bsd.eng.uwi.tt [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 88931-07 for ; Thu, 9 Dec 2004 11:35:32 -0400 (AST) Received: from ldc.eng.uwi.tt (ldc.eng.uwi.tt [192.168.20.31]) by enggate.uwi.tt (Postfix) with ESMTP id 85DD910452 for ; Thu, 9 Dec 2004 11:35:32 -0400 (AST) Received: from router.eng.uwi.tt (router.eng.uwi.tt [192.168.20.195]) by ldc.eng.uwi.tt (8.9.1/8.9.1) with SMTP id LAA11513 for ; Thu, 9 Dec 2004 11:16:48 +0400 (GMT) Date: Thu, 9 Dec 2004 11:37:48 -0400 From: Feisal Mohammed To: freebsd-amd64@freebsd.org Message-Id: <20041209113748.0fdff2c5.feisal@uwi.tt> In-Reply-To: <200412081631.57451.peter@wemm.org> References: <41B7901E.9050908@cisnet.com> <200412081631.57451.peter@wemm.org> Organization: University of the West Indies X-Mailer: Sylpheed version 1.0.0beta4 (GTK+ 1.2.10; amd64-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uwi.tt Subject: Re: 32 bit compatability 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, 09 Dec 2004 15:37:26 -0000 On Wed, 8 Dec 2004 16:31:57 -0800 Peter Wemm wrote: > On Wednesday 08 December 2004 03:37 pm, Ken Lowther wrote: > > I have been reading the archives on this issue and am getting some > > info bit by bit. > > > > I am running 5.3 Release amd64 > > > > I have edited /etc/make.conf and added: > > WITH_LIB32=YES > > > > I have edited my version of MYKERNEL to include : > > options SMP > > options QUOTA > > options COMPAT_IA32 # Compatible with i386 > > binaries (last one in by default) > > > > Did make depend, make, and make insall. > > > > Rebooted. Kernel looks like it installed because quotas now work: > > > > hostserv1# quota -v > > Disk quotas for user root (uid 0): > > Filesystem usage quota limit grace files quota > > limit grace > > /home 130108 0 0 3660 0 > > 0 /usr 1054978 0 0 67161 0 0 > > /var 6580 0 0 1031 0 0 > > > > I gather this means the kernel suports the 32 bit compat mode from > > the posts I have seen so far: > > > > hostserv1# sysctl kern.elf32 > > kern.elf32.fallback_brand: -1 > > hostserv1# > > > > After this I seem to be lost. I have seen references to various > > things, but bottom line, where do I go from here. The script under > > tools is obsolete now? install32.sh? I get the impression that this > > stuff was supposed to compile with the kernel but Google doesn't help > > me find any one place that is a step by step walk through. > > The 32 bit libraries are built as part of buildworld/installworld. > However, if you still have a fresh world laying around, you might be > able to build just the libraries part like this: > cd /usr/src; > make build32 > make install32 > > If you have any trouble, then do a full buildworld etc and they will be > included with it. > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 I've just installed 5.3 and cvsupped to stable, make build32 says don't know how to make build32. make.conf has WITH_LIB32=yes and the kernel has IA32 support. What can I be doing wrong? -Feisal From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 20:30:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D35D16A4CE for ; Thu, 9 Dec 2004 20:30:31 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id D206543D46 for ; Thu, 9 Dec 2004 20:30:30 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from [127.0.0.1] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (sccrmhc11) with ESMTP id <2004120920302901100dhbine>; Thu, 9 Dec 2004 20:30:29 +0000 Message-ID: <41B8B5E4.1070906@pythonemproject.com> Date: Thu, 09 Dec 2004 12:30:28 -0800 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael R. Wayne" , freebsd-amd64@freebsd.org References: <20041206164250.GC28404@gargantuan.com> <20041208222950.GB21601@gargantuan.com> <41B78815.9060504@pythonemproject.com> <20041209174601.GJ803@manor.msen.com> In-Reply-To: <20041209174601.GJ803@manor.msen.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: amd64 laptop recommendations 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, 09 Dec 2004 20:30:31 -0000 Michael R. Wayne wrote: >On Wed, Dec 08, 2004 at 03:02:45PM -0800, Rob wrote: > > >>Oh jeez, you guys got my mouth watering with this discussion. I have an >>AMD64 + 3800 on an Abit AV8, (socket 939) >> >> > >I'm looking at putting a box together based on that motherboard, >got any pointers? I'm planning on going with the dual video cards >(unsure which at this point) so that I can drive 4 displays at times >as well as convert to SLI mode for one real fast display. Am also planning on >spending extra cash to make it quiet. > >/\/\ \/\/ > > > > Hi Michael, LOL, quiet. My box with a Coolermaster case, 460W power supply, giant cpu fan (Zalman), and two scsci 160 drives sounds like a jet engine starting up. Unfortunately, the Abit "Guru" fan fan speed control doesn't work, and the Abit "PC Guru" utility will not load, I get an error message. This Guru tool looks fantastic. You can set trip points for cpu voltage, temps,etc, and get an audible alarm or shutdown if they are exceeded. I t was designed for the overclocker. I know better than do that stuff LOL. It will, if working, also automatically download bios and flash install it. Very cool. (if working :( My main problems have been with Windoze XP-64 beta. FreeBSD just appears to be working, although I have to admit, I really haven't put it thru its paces yet. I have one app on Windoze that I use all the time IVisit video chat, and I've been pulling out my hair and concentrating on getting that working on my laptop. Its taking 100% of my time right now. As an aside, I have no video capture drivers that will work with any cam for the Windoze 64 bit OS.. I guess I am too far ahead of my time. I was able to cvsup to 5.3-RELEASE on the FBSD side, and that is where I am currenty at. However I get lots of bogus error messages saying that almost all the config params in rc.conf are misconfigured. Yet the computer works fine. This is my own fault as I merge /etc by hand and probably missed something. I occasionally have tried to compile a port and have gotten the error message, paraphrasing, "this is a 32 bit application and can't be run on a 64 bit OS" or something like that. It seems totally bogus. (please no lectures about mergemaster, I know the drill) Right now I am stuck on both OS's trying to install a brand new beautiful Plextor PX-712SA SATA DVD+/- RW drive. It doesn't seem to be recognized by either FBSD or Windoze. So that is my 64 bit story.. I hope some of the info helps. Sincerely, Rob. ps. I will copy the AMD list on this as I or they might be able to exchange some info or tips From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 22:00:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 795C816A4CE for ; Thu, 9 Dec 2004 22:00:43 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1516A43D2F for ; Thu, 9 Dec 2004 22:00:36 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB9M0YW06198; Thu, 9 Dec 2004 14:00:34 -0800 (PST) Date: Thu, 9 Dec 2004 14:00:34 -0800 From: Mike Hunter To: Mike Jakubik Message-ID: <20041209220034.GA2250@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> <20041208180858.GA10932@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041208180858.GA10932@ack.Berkeley.EDU> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Same problem w/ 6.0 (Was: problems compiling perl 5.8.5 w/ fbsd 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: Thu, 09 Dec 2004 22:00:43 -0000 On Dec 08, "To Mike Jakubik" wrote: > I upgraded to 5.3, but I still am having the same problem: > > #uname -a > FreeBSD mybox 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Dec 7 15:35:28 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 > > `WITH_GDBM=1 make` works fine, but `make test` still fails. It hangs for > a long time on > > lib/Config................................ > > And...and I was going to copy and paste the same error message as I sent > yesterday, but instead ssh hung up on me, and the console has the > following bad news: > > swap_pager: out of swap space > swap_pager_getwwapspace(16): failed > ...sshd was killed ...out of swap space > > Top says it was a very big boy indeed while it was running: > > 17771 root 130 0 10732M 2470M CPU0 0 13:41 103.17% 103.17% perl > > I'm willing to do a binary package as a last resort, but I'm planning on > building code on this box so it'd be better to get this resolved properly > :) > > I'm going to try changing the perl MALLOC options. This machine has 8G of > ram, are there still problems with large memory on amd64? More bad news: It's still doing the same thing :( 12400 root 118 0 2871M 2698M CPU0 1 3:02 98.94% 98.93% perl uname -a FreeBSD mybox 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Dec 9 12:09:07 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 I'm ready to help; any guidance? Thanks, Mike From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 22:06:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAF7D16A4CE for ; Thu, 9 Dec 2004 22:06:17 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E48843D55 for ; Thu, 9 Dec 2004 22:06:17 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com (localhost [127.0.0.1])with ESMTP id 14352295416 for ; Thu, 9 Dec 2004 17:06:04 -0500 (EST) Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Thu, 9 Dec 2004 17:06:04 -0500 (EST) Message-ID: <54008.207.219.213.163.1102629964.squirrel@207.219.213.163> Date: Thu, 9 Dec 2004 17:06:04 -0500 (EST) From: "Mike Jakubik" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com Subject: Can't compile jabberd on AMD64 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: Thu, 09 Dec 2004 22:06:18 -0000 I am getting a lot of warnings and finally a stop error when trying to compile /usr/ports/net/jabberd/ on an AMD64, 5.3-STABLE box. The port compiles OK on an x86 6-CURRENT box. No answers from the port maintanier or the ports list. All my installed ports and ports tree are up to date. Here is the compiling process: --- source='main.c' object='main.o' libtool=no depfile='.deps/main.Po' tmpdepfile='.deps/main.TPo' depmode=gcc3 /bin/sh ../depcomp cc -DHAVE_CONFIG_H -I. -I. -I.. -DCONFIG_DIR=\"/usr/local/etc/jabberd\" -I/usr/local/include/mysql -I/usr/local/include -O -pipe -c `test -f 'main.c' || echo './'`main.c In file included from ../sx/sx.h:30, from c2s.h:26, from main.c:21: ../expat/expat.h:216: warning: `cdecl' attribute ignored ../expat/expat.h:220: warning: `cdecl' attribute ignored ../expat/expat.h:236: warning: `cdecl' attribute ignored ../expat/expat.h:240: warning: `cdecl' attribute ignored ../expat/expat.h:253: warning: `cdecl' attribute ignored ../expat/expat.h:257: warning: `cdecl' attribute ignored ../expat/expat.h:261: warning: `cdecl' attribute ignored ../expat/expat.h:262: warning: `cdecl' attribute ignored ../expat/expat.h:263: warning: `cdecl' attribute ignored ../expat/expat.h:270: warning: `cdecl' attribute ignored ../expat/expat.h:284: warning: `cdecl' attribute ignored ../expat/expat.h:299: warning: `cdecl' attribute ignored ../expat/expat.h:311: warning: `cdecl' attribute ignored ../expat/expat.h:318: warning: `cdecl' attribute ignored ../expat/expat.h:321: warning: `cdecl' attribute ignored ../expat/expat.h:327: warning: `cdecl' attribute ignored ../expat/expat.h:333: warning: `cdecl' attribute ignored ../expat/expat.h:337: warning: `cdecl' attribute ignored ../expat/expat.h:339: warning: `cdecl' attribute ignored ../expat/expat.h:340: warning: `cdecl' attribute ignored ../expat/expat.h:357: warning: `cdecl' attribute ignored ../expat/expat.h:367: warning: `cdecl' attribute ignored ../expat/expat.h:373: warning: `cdecl' attribute ignored ../expat/expat.h:402: warning: `cdecl' attribute ignored ../expat/expat.h:406: warning: `cdecl' attribute ignored ../expat/expat.h:423: warning: `cdecl' attribute ignored ../expat/expat.h:434: warning: `cdecl' attribute ignored ../expat/expat.h:445: warning: `cdecl' attribute ignored ../expat/expat.h:449: warning: `cdecl' attribute ignored ../expat/expat.h:460: warning: `cdecl' attribute ignored ../expat/expat.h:501: warning: `cdecl' attribute ignored ../expat/expat.h:516: warning: `cdecl' attribute ignored ../expat/expat.h:573: warning: `cdecl' attribute ignored ../expat/expat.h:574: warning: `cdecl' attribute ignored ../expat/expat.h:595: warning: `cdecl' attribute ignored ../expat/expat.h:600: warning: `cdecl' attribute ignored ../expat/expat.h:603: warning: `cdecl' attribute ignored ../expat/expat.h:606: warning: `cdecl' attribute ignored ../expat/expat.h:610: warning: `cdecl' attribute ignored ../expat/expat.h:614: warning: `cdecl' attribute ignored ../expat/expat.h:617: warning: `cdecl' attribute ignored ../expat/expat.h:622: warning: `cdecl' attribute ignored ../expat/expat.h:626: warning: `cdecl' attribute ignored ../expat/expat.h:630: warning: `cdecl' attribute ignored ../expat/expat.h:638: warning: `cdecl' attribute ignored ../expat/expat.h:646: warning: `cdecl' attribute ignored ../expat/expat.h:651: warning: `cdecl' attribute ignored ../expat/expat.h:655: warning: `cdecl' attribute ignored ../expat/expat.h:659: warning: `cdecl' attribute ignored ../expat/expat.h:663: warning: `cdecl' attribute ignored ../expat/expat.h:667: warning: `cdecl' attribute ignored ../expat/expat.h:672: warning: `cdecl' attribute ignored ../expat/expat.h:676: warning: `cdecl' attribute ignored ../expat/expat.h:680: warning: `cdecl' attribute ignored ../expat/expat.h:684: warning: `cdecl' attribute ignored ../expat/expat.h:688: warning: `cdecl' attribute ignored ../expat/expat.h:695: warning: `cdecl' attribute ignored ../expat/expat.h:699: warning: `cdecl' attribute ignored ../expat/expat.h:704: warning: `cdecl' attribute ignored ../expat/expat.h:711: warning: `cdecl' attribute ignored ../expat/expat.h:728: warning: `cdecl' attribute ignored ../expat/expat.h:732: warning: `cdecl' attribute ignored ../expat/expat.h:744: warning: `cdecl' attribute ignored ../expat/expat.h:751: warning: `cdecl' attribute ignored ../expat/expat.h:769: warning: `cdecl' attribute ignored ../expat/expat.h:781: warning: `cdecl' attribute ignored ../expat/expat.h:784: warning: `cdecl' attribute ignored ../expat/expat.h:793: warning: `cdecl' attribute ignored ../expat/expat.h:801: warning: `cdecl' attribute ignored ../expat/expat.h:813: warning: `cdecl' attribute ignored ../expat/expat.h:816: warning: `cdecl' attribute ignored ../expat/expat.h:819: warning: `cdecl' attribute ignored ../expat/expat.h:840: warning: `cdecl' attribute ignored ../expat/expat.h:873: warning: `cdecl' attribute ignored ../expat/expat.h:879: warning: `cdecl' attribute ignored ../expat/expat.h:897: warning: `cdecl' attribute ignored ../expat/expat.h:898: warning: `cdecl' attribute ignored ../expat/expat.h:899: warning: `cdecl' attribute ignored ../expat/expat.h:905: warning: `cdecl' attribute ignored ../expat/expat.h:920: warning: `cdecl' attribute ignored ../expat/expat.h:929: warning: `cdecl' attribute ignored ../expat/expat.h:933: warning: `cdecl' attribute ignored ../expat/expat.h:936: warning: `cdecl' attribute ignored ../expat/expat.h:939: warning: `cdecl' attribute ignored ../expat/expat.h:943: warning: `cdecl' attribute ignored ../expat/expat.h:947: warning: `cdecl' attribute ignored ../expat/expat.h:951: warning: `cdecl' attribute ignored ../expat/expat.h:963: warning: `cdecl' attribute ignored ../expat/expat.h:985: warning: `cdecl' attribute ignored main.c:24: error: conflicting types for 'c2s_lost_router' c2s.h:210: error: previous declaration of 'c2s_lost_router' was here main.c:24: error: conflicting types for 'c2s_lost_router' c2s.h:210: error: previous declaration of 'c2s_lost_router' was here *** Error code 1 Stop in /usr/ports/net/jabberd/work/jabberd-2.0s5/c2s. *** Error code 1 --- Thanks. From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 9 22:16:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB01216A4CE for ; Thu, 9 Dec 2004 22:16:06 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6DBB43D48 for ; Thu, 9 Dec 2004 22:16:06 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB9MG5D06940; Thu, 9 Dec 2004 14:16:05 -0800 (PST) Date: Thu, 9 Dec 2004 14:16:05 -0800 From: Mike Hunter To: Mike Jakubik Message-ID: <20041209221605.GA6906@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> <20041208180858.GA10932@ack.Berkeley.EDU> <20041209220034.GA2250@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209220034.GA2250@ack.Berkeley.EDU> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: Same problem w/ 6.0 (Was: problems compiling perl 5.8.5 w/ fbsd 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: Thu, 09 Dec 2004 22:16:07 -0000 > More bad news: It's still doing the same thing :( > > 12400 root 118 0 2871M 2698M CPU0 1 3:02 98.94% 98.93% perl > > uname -a > > FreeBSD mybox 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Dec 9 12:09:07 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 > > I'm ready to help; any guidance? I grabbed the perl 5.8.6 source and it gets stuck in the same place. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 00:25:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBFC416A4CE; Fri, 10 Dec 2004 00:25:46 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16F4B43D5F; Fri, 10 Dec 2004 00:25:46 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])iBA0PiGx014873; Fri, 10 Dec 2004 11:25:44 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) iBA0PgcH015638; Fri, 10 Dec 2004 11:25:43 +1100 Date: Fri, 10 Dec 2004 11:25:42 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Palle Girgensohn In-Reply-To: <200412071156.iB7BuDHE077345@rambutan.pingpong.net> Message-ID: <20041210092445.Y28756@delplex.bde.org> References: <200412071156.iB7BuDHE077345@rambutan.pingpong.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-gnats-submit@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: amd64/74811: df, nfs mount, negative Avail -> 32/64-bit confusion 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, 10 Dec 2004 00:25:46 -0000 On Tue, 7 Dec 2004, Palle Girgensohn wrote: > >Description: > > using FreeBSD 5.3 amd64 as nfs client > FreeBSD 4.10 i386 as nfs server The combination of client and server is critical for demonstrating this bug. Broken servers don't implement negative avail counts. FreeBSD-5's server was broken in rev.1.140 of nfs_serv.c to "fix" the problem reported in this PR. FreeBSD-4's server remains unbroken. > when a disk is filled up over 100%, Avail becomes negative on the > server, but hugely postive on the 64-bit platform. Not very > surprising, but still a bug... :) > > 4.10 i386 server: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da6s1f 17388202 16153532 -156386 101% /dumps/0 > > 5.3 amd64 client: > Filesystem 1K-blocks Used Avail Capacity Mounted on > banan:/dumps/0 17388202 16153532 18014398509325598 0% /mnt This is caused by sign extension/overflow bugs in nfs_vfsops.c. From the version in FreeBSD-5.3 (rev.1.158): % u_quad_t tquad; % ... % tquad = fxdr_hyper(&sfp->sf_abytes); % if (((long)(tquad / bsize) > LONG_MAX) || ^^^^^^^^^^^^^^^^^^^^^ % ((long)(tquad / bsize) < LONG_MIN)) ^^^^^^^^^^^^^^^^^^^^^ % continue; % sbp->f_bavail = tquad / bsize; % ^^^^^^^^^^^^^ -156386 1K-blocks is passed by the server as (uint64_t)(-156386 * 1024) = (2**64 - 156386 * 1024). It needs to be converted back to a signed quantity before dividing it by bsize, but this is not done. tquad is still (2**64 - 156386 * 1024). bsize is always 512 in FreeBSD-5.3 (**). The division gives the wrong value (2**55 - 156386 * 2). This is passed back to userland. It is a block count in 512-blocks, so df divides it by 2 to convert to 1K-blocks. The final value printed is (2**54 - 156386) = 18014398509325598. The magic number 18014398509325598 is easy to recognize. 2**64 is 1844..., so huge values starting with the digits 18 are often misrepresentations of small negative values converted to uint64_t. Here the value is 1801... instead of 1844..., and on closer examination has 3 fewer digits. It is just the corresponding 1844... value divided by 2**10 = 1024 to convert to 1K-blocks. Applications like df could recognize such magic numbers (not so) similarly and fix them up, but shouldn't have to. (*) Other aspects of this bug include the code that doubles bsize actually being executed in some versions of FreeBSD on some machines, including -current on i386's. It is broken and gives a kernel panic for division by bsize = 0 for about half of all possible values for negative available space, including all values that are likely to occur (small negative ones). See PR 56606 for more details of older aspects of this bug suite. There are many newer ones. Bruce From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 00:30:30 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AD6116A4CE for ; Fri, 10 Dec 2004 00:30:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39F9A43D4C for ; Fri, 10 Dec 2004 00:30:30 +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 iBA0UTOA041696 for ; Fri, 10 Dec 2004 00:30:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBA0UTLW041695; Fri, 10 Dec 2004 00:30:29 GMT (envelope-from gnats) Date: Fri, 10 Dec 2004 00:30:29 GMT Message-Id: <200412100030.iBA0UTLW041695@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Bruce Evans Subject: Re: amd64/74811: df, nfs mount, negative Avail -> 32/64-bit confusion X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce Evans List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:30:30 -0000 The following reply was made to PR amd64/74811; it has been noted by GNATS. From: Bruce Evans To: Palle Girgensohn Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/74811: df, nfs mount, negative Avail -> 32/64-bit confusion Date: Fri, 10 Dec 2004 11:25:42 +1100 (EST) On Tue, 7 Dec 2004, Palle Girgensohn wrote: > >Description: > > using FreeBSD 5.3 amd64 as nfs client > FreeBSD 4.10 i386 as nfs server The combination of client and server is critical for demonstrating this bug. Broken servers don't implement negative avail counts. FreeBSD-5's server was broken in rev.1.140 of nfs_serv.c to "fix" the problem reported in this PR. FreeBSD-4's server remains unbroken. > when a disk is filled up over 100%, Avail becomes negative on the > server, but hugely postive on the 64-bit platform. Not very > surprising, but still a bug... :) > > 4.10 i386 server: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da6s1f 17388202 16153532 -156386 101% /dumps/0 > > 5.3 amd64 client: > Filesystem 1K-blocks Used Avail Capacity Mounted on > banan:/dumps/0 17388202 16153532 18014398509325598 0% /mnt This is caused by sign extension/overflow bugs in nfs_vfsops.c. From the version in FreeBSD-5.3 (rev.1.158): % u_quad_t tquad; % ... % tquad = fxdr_hyper(&sfp->sf_abytes); % if (((long)(tquad / bsize) > LONG_MAX) || ^^^^^^^^^^^^^^^^^^^^^ % ((long)(tquad / bsize) < LONG_MIN)) ^^^^^^^^^^^^^^^^^^^^^ % continue; % sbp->f_bavail = tquad / bsize; % ^^^^^^^^^^^^^ -156386 1K-blocks is passed by the server as (uint64_t)(-156386 * 1024) = (2**64 - 156386 * 1024). It needs to be converted back to a signed quantity before dividing it by bsize, but this is not done. tquad is still (2**64 - 156386 * 1024). bsize is always 512 in FreeBSD-5.3 (**). The division gives the wrong value (2**55 - 156386 * 2). This is passed back to userland. It is a block count in 512-blocks, so df divides it by 2 to convert to 1K-blocks. The final value printed is (2**54 - 156386) = 18014398509325598. The magic number 18014398509325598 is easy to recognize. 2**64 is 1844..., so huge values starting with the digits 18 are often misrepresentations of small negative values converted to uint64_t. Here the value is 1801... instead of 1844..., and on closer examination has 3 fewer digits. It is just the corresponding 1844... value divided by 2**10 = 1024 to convert to 1K-blocks. Applications like df could recognize such magic numbers (not so) similarly and fix them up, but shouldn't have to. (*) Other aspects of this bug include the code that doubles bsize actually being executed in some versions of FreeBSD on some machines, including -current on i386's. It is broken and gives a kernel panic for division by bsize = 0 for about half of all possible values for negative available space, including all values that are likely to occur (small negative ones). See PR 56606 for more details of older aspects of this bug suite. There are many newer ones. Bruce From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 10:48:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72E2B16A4CE for ; Fri, 10 Dec 2004 10:48:56 +0000 (GMT) Received: from satie.private.org (qclgw.qcl.t.u-tokyo.ac.jp [133.11.70.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B9843D6A for ; Fri, 10 Dec 2004 10:48:55 +0000 (GMT) (envelope-from chat95@mac.com) Received: from localhost (localhost [IPv6:::1]) by satie.private.org (8.13.1/8.13.1) with ESMTP id iBAAmjvd084942 for ; Fri, 10 Dec 2004 19:48:46 +0900 (JST) (envelope-from chat95@mac.com) Date: Fri, 10 Dec 2004 19:48:45 +0900 (JST) Message-Id: <20041210.194845.653222828.chat95@mac.com> To: freebsd-amd64@freebsd.org From: NAKATA Maho Organization: private X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Tyan Thunder K8W (S2885) with FreeBSD 5.3-RELEASE 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, 10 Dec 2004 10:48:56 -0000 Dear amd64 freaks, Yesterday, I installed 5.3-RELEASE to my Opteron dual box. o Opteron 242 (1.6MHz) x2 o Memory ECC PC2700 Reg. trancend 2G modules x4 + CenturyMicro 512M x 4 (total 10G) o Tyan Thunder K8W (S2885) I encountered a prolbem, while installtion. As many one pointed out in this ML, if we have >4G of memory, ATA hangs up. so I type o set hw.physmem="3G" at boot time. however, I recompiled and re-installed SMP kernel, FreeBSD never boots even if I type set hw.physmem="3G". So I took different way. There's no problem with 5.2.1-RELEASE and 5.3-BETA4. So CVSup'ing from 5.3-BETA4 to -STABLE seems to be fine, only set hw.physmem="3G" is mandatory at installation, and can omit after recompiling world and kernel. Does anybody here have problems with it? All the best, -- NAKATA, Maho From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 17:21:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7172316A4CE for ; Fri, 10 Dec 2004 17:21:13 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53AF543D1D for ; Fri, 10 Dec 2004 17:21:13 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iBAHLBi11193; Fri, 10 Dec 2004 09:21:11 -0800 (PST) Date: Fri, 10 Dec 2004 09:21:11 -0800 From: Mike Hunter To: NAKATA Maho Message-ID: <20041210172111.GB10811@ack.Berkeley.EDU> References: <20041210.194845.653222828.chat95@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041210.194845.653222828.chat95@mac.com> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: Tyan Thunder K8W (S2885) with FreeBSD 5.3-RELEASE 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, 10 Dec 2004 17:21:13 -0000 On Dec 10, "NAKATA Maho" wrote: Nakata-san, > Yesterday, I installed 5.3-RELEASE to my Opteron dual box. > > o Opteron 242 (1.6MHz) x2 > o Memory ECC PC2700 Reg. trancend 2G modules x4 > + CenturyMicro 512M x 4 > (total 10G) > o Tyan Thunder K8W (S2885) > > I encountered a prolbem, while installtion. As many one pointed out > in this ML, if we have >4G of memory, ATA hangs up. > so I type > o set hw.physmem="3G" > at boot time. > however, I recompiled and re-installed SMP kernel, > FreeBSD never boots even if I type set hw.physmem="3G". > > So I took different way. There's no problem with 5.2.1-RELEASE > and 5.3-BETA4. So CVSup'ing from 5.3-BETA4 to -STABLE > seems to be fine, only set hw.physmem="3G" is mandatory at > installation, and can omit after recompiling world and kernel. > > Does anybody here have problems with it? I have a similar story. 5.2.1 loaded fine, 5.3-RELEASE would cause instant reboots. I was able to cvsup to RELENG_5 and run that kernel. At the time I blamed bad 5.3 CD Media, but perhaps there was something actually wrong. I have a Tyan K8S with 8G of ram. Mike From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 20:20:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE24A16A4CE for ; Fri, 10 Dec 2004 20:20:38 +0000 (GMT) Received: from flash.atmos.colostate.edu (flash.atmos.colostate.edu [129.82.48.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9811F43D5C for ; Fri, 10 Dec 2004 20:20:38 +0000 (GMT) (envelope-from tarcieri@flash.atmos.colostate.edu) Received: from flash.atmos.colostate.edu (localhost [127.0.0.1]) iBAKKbse012435 for ; Fri, 10 Dec 2004 13:20:37 -0700 (MST) (envelope-from tarcieri@flash.atmos.colostate.edu) Received: (from tarcieri@localhost) by flash.atmos.colostate.edu (8.13.1/8.13.1/Submit) id iBAKKbvk012434 for freebsd-amd64@FreeBSD.org; Fri, 10 Dec 2004 13:20:37 -0700 (MST) (envelope-from tarcieri) Date: Fri, 10 Dec 2004 13:20:37 -0700 From: Tony Arcieri To: freebsd-amd64@FreeBSD.org Message-ID: <20041210202037.GA12369@flash.atmos.colostate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Issuing rebuild instruction to 3Ware 7000 series TwinStor array 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, 10 Dec 2004 20:20:39 -0000 I have a 3Ware 7000 series controller on a FreeBSD 5.3/amd64 system. Unfortunately, after stability problems the array is in the degraded state: twed0: on twe0 As there is currently no version of the 3Ware CLI for FreeBSD/AMD64, I was wondering how hard it would be to set up the ioctl() calls to issue the rebuild command to the controller directly. Looking in twe_tables.h, I see the following memeber of the twe_table_opcode array: {"REBUILDUNIT", 0x17}, Is this the command I need to send to the device and if so, what parameters does it need? Tony Arcieri From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 20:54:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3155816A4CE for ; Fri, 10 Dec 2004 20:54:02 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB8843D2D for ; Fri, 10 Dec 2004 20:54:01 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iBAKrhdQ077501; Fri, 10 Dec 2004 14:53:44 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41BA0CD7.4080309@jrv.org> Date: Fri, 10 Dec 2004 14:53:43 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <20041210.194845.653222828.chat95@mac.com> <20041210172111.GB10811@ack.Berkeley.EDU> In-Reply-To: <20041210172111.GB10811@ack.Berkeley.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Tyan Thunder K8W (S2885) with FreeBSD 5.3-RELEASE 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, 10 Dec 2004 20:54:02 -0000 5.3-release has a known bug with more than 4GB of RAM. You need 5.3-stable. But even that may not work: I have a Tan S2885 also with two Opteron 248s and 8GB, two DIMMs on each CPU. This ran FreeBSD/amd64 5.2.1 since spring with no problems using ATA and bge(4) NIC. I've now switched to a twa(4) 3ware 9500S disk controller, which doesn't need bounce-buffers. bge(4) does need bounce-buffers. FreeBSD/amd64 5-stable hangs right after the bge(4) NIC is enabled if 8GB of RAM is present. I can boot single user and do disk I/O with no problem, but it hangs - no panic - as soon as I try to bring up the NIC. If I add the line "set hw.physmem=4g" to the top of /boot/loader.rc then everything works fine - no bge(4) hang. I think the em(4) NIC doesn't need bounce-buffers and I'm trying to track one down for testing. I think drivers had to be changed for the bounce buffer changes in 5.3. Perhaps there is a bug in the bge(4) change? Is anyone using a bge(4) NIC with more than 4GB of RAM? Mike Hunter wrote: >On Dec 10, "NAKATA Maho" wrote: > >Nakata-san, > > > >>Yesterday, I installed 5.3-RELEASE to my Opteron dual box. >> >>o Opteron 242 (1.6MHz) x2 >>o Memory ECC PC2700 Reg. trancend 2G modules x4 >> + CenturyMicro 512M x 4 >> (total 10G) >>o Tyan Thunder K8W (S2885) >> >>I encountered a prolbem, while installtion. As many one pointed out >>in this ML, if we have >4G of memory, ATA hangs up. >>so I type >>o set hw.physmem="3G" >>at boot time. >>however, I recompiled and re-installed SMP kernel, >>FreeBSD never boots even if I type set hw.physmem="3G". >> >>So I took different way. There's no problem with 5.2.1-RELEASE >>and 5.3-BETA4. So CVSup'ing from 5.3-BETA4 to -STABLE >>seems to be fine, only set hw.physmem="3G" is mandatory at >>installation, and can omit after recompiling world and kernel. >> >>Does anybody here have problems with it? >> >> > >I have a similar story. 5.2.1 loaded fine, 5.3-RELEASE would cause >instant reboots. I was able to cvsup to RELENG_5 and run that kernel. At >the time I blamed bad 5.3 CD Media, but perhaps there was something >actually wrong. I have a Tyan K8S with 8G of ram. > > From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 21:31:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E05616A4CE for ; Fri, 10 Dec 2004 21:31:54 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEA2F43D39 for ; Fri, 10 Dec 2004 21:31:53 +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 iBALWujn011706; Fri, 10 Dec 2004 16:32:56 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Fri, 10 Dec 2004 16:32:56 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: "James R. Van Artsalen" In-Reply-To: <41BA0CD7.4080309@jrv.org> Message-ID: <20041210163106.C88450@bahre.achedra.org> References: <20041210.194845.653222828.chat95@mac.com> <20041210172111.GB10811@ack.Berkeley.EDU> <41BA0CD7.4080309@jrv.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: Mike Hunter cc: freebsd-amd64@freebsd.org Subject: Re: Tyan Thunder K8W (S2885) with FreeBSD 5.3-RELEASE 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, 10 Dec 2004 21:31:54 -0000 On Fri, 10 Dec 2004, James R. Van Artsalen wrote: > I think drivers had to be changed for the bounce buffer changes in 5.3. > Perhaps there is a bug in the bge(4) change? Is anyone using a bge(4) NIC > with more than 4GB of RAM? Despite my best efforts not to, since the thing has it's own share of problems. bge(4) was working fine with 8GB _before_ the busdma fixes, so I think you can safely rule it out. I don't think you get much better testing than PXE+nfsroot. -ksaihr From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 10 21:37:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21C6D16A4D0 for ; Fri, 10 Dec 2004 21:37:55 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id F21AE43D41 for ; Fri, 10 Dec 2004 21:37:54 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iBALbq826854; Fri, 10 Dec 2004 13:37:52 -0800 (PST) Date: Fri, 10 Dec 2004 13:37:52 -0800 From: Mike Hunter To: "James R. Van Artsalen" Message-ID: <20041210213752.GB25659@ack.Berkeley.EDU> References: <20041210.194845.653222828.chat95@mac.com> <20041210172111.GB10811@ack.Berkeley.EDU> <41BA0CD7.4080309@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41BA0CD7.4080309@jrv.org> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: Tyan Thunder K8W (S2885) with FreeBSD 5.3-RELEASE 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, 10 Dec 2004 21:37:55 -0000 On Dec 10, "James R. Van Artsalen" wrote: > 5.3-release has a known bug with more than 4GB of RAM. You need > 5.3-stable. But even that may not work: > > I have a Tan S2885 also with two Opteron 248s and 8GB, two DIMMs on each > CPU. This ran FreeBSD/amd64 5.2.1 since spring with no problems using > ATA and bge(4) NIC. > > I've now switched to a twa(4) 3ware 9500S disk controller, which doesn't > need bounce-buffers. bge(4) does need bounce-buffers. > > FreeBSD/amd64 5-stable hangs right after the bge(4) NIC is enabled if > 8GB of RAM is present. I can boot single user and do disk I/O with no > problem, but it hangs - no panic - as soon as I try to bring up the NIC. > > If I add the line "set hw.physmem=4g" to the top of /boot/loader.rc then > everything works fine - no bge(4) hang. > > I think the em(4) NIC doesn't need bounce-buffers and I'm trying to > track one down for testing. > > I think drivers had to be changed for the bounce buffer changes in 5.3. > Perhaps there is a bug in the bge(4) change? Is anyone using a bge(4) > NIC with more than 4GB of RAM? mybox# uname -a FreeBSD mybox 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Dec 9 12:09:07 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 mybox# ifconfig bge0 bge0: flags=8802 mtu 1500 options=1a ether 00:e0:81:2b:4b:12 media: Ethernet autoselect (none) status: no carrier mybox# dmesg | grep -i bge bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 miibus1: on bge0 bge0: Ethernet address: 00:e0:81:2b:4b:12 bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 miibus2: on bge1 bge1: Ethernet address: 00:e0:81:2b:4b:13 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 00:19:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0906316A4CE for ; Sat, 11 Dec 2004 00:19:04 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCC5B43D39 for ; Sat, 11 Dec 2004 00:19:03 +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 813A82A904 for ; Fri, 10 Dec 2004 16:19:03 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 16FEFE2B7 for ; Fri, 10 Dec 2004 16:19:02 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iBB0J2Nt013107; Fri, 10 Dec 2004 16:19:02 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iBB0J113013106; Fri, 10 Dec 2004 16:19:01 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Fri, 10 Dec 2004 16:19:01 -0800 User-Agent: KMail/1.7.1 References: <20041210202037.GA12369@flash.atmos.colostate.edu> In-Reply-To: <20041210202037.GA12369@flash.atmos.colostate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412101619.01488.peter@wemm.org> cc: Tony Arcieri Subject: Re: Issuing rebuild instruction to 3Ware 7000 series TwinStor array 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, 11 Dec 2004 00:19:04 -0000 On Friday 10 December 2004 12:20 pm, Tony Arcieri wrote: > I have a 3Ware 7000 series controller on a FreeBSD 5.3/amd64 system. > Unfortunately, after stability problems the array is in the degraded > state: > > twed0: on twe0 > > As there is currently no version of the 3Ware CLI for FreeBSD/AMD64, > I was wondering how hard it would be to set up the ioctl() calls to > issue the rebuild command to the controller directly. Looking in > twe_tables.h, I see the following memeber of the twe_table_opcode > array: > > {"REBUILDUNIT", 0x17}, > > Is this the command I need to send to the device and if so, what > parameters does it need? I have a horrible hack to the twe driver to enable it to understand the 32 bit binary ioctl's. It was enough for me to run the CLI. I was thinking about committing it, but I've been meaning to ask the 3ware folks for a native build, which would be much better. Maybe they do a build so I won't have to commit this. I've given this diff to all the people that have asked. Their management stuff generally passes opaque data blobs through from the cli/3dm to the firmware. We don't need to see what it is. Anyway, the diff: http://people.freebsd.org/~peter/twe.diff Index: sys/dev/twe/twe.c =========================================================================== --- sys/dev/twe/twe.c 2004/12/11 00:10:34 #14 +++ sys/dev/twe/twe.c 2004/12/11 00:10:34 @@ -500,9 +500,25 @@ struct twe_request *tr; u_int8_t srid; int s, error; +#ifdef __amd64__ + struct twe_paramcommand32 *tp32 = (struct twe_paramcommand32 *)addr; + struct twe_usercommand32 *tu32 = (struct twe_usercommand32 *)addr; + struct twe_paramcommand tp_swab; + struct twe_usercommand tu_swab; +#endif error = 0; switch(ioctlcmd) { + +#ifdef __amd64__ + case TWEIO_COMMAND32: + tu_swab.tu_command = tu32->tu_command; + tu_swab.tu_data = (void *)(uintptr_t)tu32->tu_data; + tu_swab.tu_size = tu32->tu_size; + tu = &tu_swab; + /* FALLTHROUGH */ +#endif + /* handle a command from userspace */ case TWEIO_COMMAND: /* get a request */ @@ -588,6 +604,16 @@ splx(s); break; +#ifdef __amd64__ + case TWEIO_GET_PARAM32: + tp_swab.tp_table_id = tp32->tp_table_id; + tp_swab.tp_param_id = tp32->tp_param_id; + tp_swab.tp_data = (void *)(uintptr_t)tp32->tp_data; + tp_swab.tp_size = tp32->tp_size; + tp = &tp_swab; + /* FALLTHROUGH */ +#endif + case TWEIO_GET_PARAM: if ((param = twe_get_param(sc, tp->tp_table_id, tp->tp_param_id, tp->tp_size, NULL)) == NULL) { twe_printf(sc, "TWEIO_GET_PARAM failed for 0x%x/0x%x/%d\n", @@ -605,6 +631,16 @@ } break; +#ifdef __amd64__ + case TWEIO_SET_PARAM32: + tp_swab.tp_table_id = tp32->tp_table_id; + tp_swab.tp_param_id = tp32->tp_param_id; + tp_swab.tp_data = (void *)(uintptr_t)tp32->tp_data; + tp_swab.tp_size = tp32->tp_size; + tp = &tp_swab; + /* FALLTHROUGH */ +#endif + case TWEIO_SET_PARAM: if ((data = malloc(tp->tp_size, M_DEVBUF, M_WAITOK)) == NULL) { error = ENOMEM; Index: sys/dev/twe/tweio.h =========================================================================== --- sys/dev/twe/tweio.h 2004/12/11 00:10:34 #3 +++ sys/dev/twe/tweio.h 2004/12/11 00:10:34 @@ -44,6 +44,17 @@ #define TWEIO_COMMAND _IOWR('T', 100, struct twe_usercommand) +#ifdef __amd64__ +struct twe_usercommand32 { + TWE_Command tu_command; /* command ready for the controller */ + uint32_t tu_data; /* pointer to data in userspace */ + uint32_t tu_size; /* userspace data length */ +}; + +#define TWEIO_COMMAND32 _IOWR('T', 100, struct twe_usercommand32) +#endif + + /* * Command queue statistics */ @@ -89,6 +100,18 @@ #define TWEIO_SET_PARAM _IOW ('T', 104, struct twe_paramcommand) #define TWEIO_GET_PARAM _IOW ('T', 105, struct twe_paramcommand) +#ifdef __amd64__ +struct twe_paramcommand32 { + u_int16_t tp_table_id; + u_int8_t tp_param_id; + u_int32_t tp_data; + u_int8_t tp_size; +}; + +#define TWEIO_SET_PARAM32 _IOW ('T', 104, struct twe_paramcommand32) +#define TWEIO_GET_PARAM32 _IOW ('T', 105, struct twe_paramcommand32) +#endif + /* * Request a controller soft-reset */ -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 00:23:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2248716A4CE; Sat, 11 Dec 2004 00:23:58 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A8F143D46; Sat, 11 Dec 2004 00:23:58 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id EB17372DD4; Fri, 10 Dec 2004 16:23:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E6B1C72DCB; Fri, 10 Dec 2004 16:23:57 -0800 (PST) Date: Fri, 10 Dec 2004 16:23:57 -0800 (PST) From: Doug White To: Kris Kennaway In-Reply-To: <20041208171947.GA46271@xor.obsecurity.org> Message-ID: <20041210161650.I63382@carver.gumbysoft.com> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208171947.GA46271@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mikhail Teterin cc: freebsd-current@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: ade@FreeBSD.org Subject: Re: new TCL vs. current-6 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, 11 Dec 2004 00:23:58 -0000 On Wed, 8 Dec 2004, Kris Kennaway wrote: > On Wed, Dec 08, 2004 at 12:05:38PM -0500, Mikhail Teterin wrote: > > Three of my TCL-based ports fail now on amd64 running current-6. All failures > > occur, when an attempt is made to use the TCL-interpreter -- either to run > > the port's self-tests, or to generate the manual pages. The failures are > > either "Floating point exceptions" or "Segmentation faults" and appear to > > only happen on amd64 (may be, on ia64 as well): > > > > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > > > > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > > > My ports did not change in months -- what could be wrong with TCL and/or > > amd64? > > Peter speculated a problem when the world is built with -O2 (with or > without -fno-strict-aliasing). I haven't been able to confirm this by > testing with a world built with -O, because I only have one working > amd64 package builder. A quick Makefile look and gdb run finds it taking SIGFPE in strtod(). The tcl build is also very odd since it seems to apply CFLAGS twice like: cc $CFLAGS -O $CFLAGS ... I haven't gone looking for why, just noticed it during the build. This is on a machine built with -O2. I'll kick off an -O build now and see what happens. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 00:34:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6560A16A4CE for ; Sat, 11 Dec 2004 00:34:36 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F2843D1D for ; Sat, 11 Dec 2004 00:34:36 +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 iBB0YZ2H051387; Fri, 10 Dec 2004 16:34:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBB0YZR5051386; Fri, 10 Dec 2004 16:34:35 -0800 (PST) (envelope-from obrien) Date: Fri, 10 Dec 2004 16:34:34 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20041211003434.GB50516@dragon.nuxi.com> References: <41B4D564.2090006@sdodson.com> <200412061617.40804.peter@wemm.org> <2fd864e041206172824bb791@mail.gmail.com> <2fd864e041206172840f48d35@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e041206172840f48d35@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Fwd: nForce woes? 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: Sat, 11 Dec 2004 00:34:36 -0000 On Mon, Dec 06, 2004 at 05:28:48PM -0800, Astrodog wrote: > I'm working on resolving the > ACPI stuff, so if anyone has docs on how they've implemented ACPI on > the NForce3s for notebooks that'd be great. What docs are you looking for? I've never seen per-motherboard docs on ACPI usage before; so I wonder what you're looking for -- other than an iasl(8) disassembly. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 00:43:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B82216A4CE for ; Sat, 11 Dec 2004 00:43:02 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC8BA43D54 for ; Sat, 11 Dec 2004 00:43:01 +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 iBB0gwGW051541; Fri, 10 Dec 2004 16:42:58 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBB0gvkx051540; Fri, 10 Dec 2004 16:42:57 -0800 (PST) (envelope-from obrien) Date: Fri, 10 Dec 2004 16:42:57 -0800 From: "David O'Brien" To: "Guillaume R." Message-ID: <20041211004257.GD50516@dragon.nuxi.com> References: <200412061609.55733.peter@wemm.org> <29119.134.214.201.98.1102439181.squirrel@jose.freesurf.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29119.134.214.201.98.1102439181.squirrel@jose.freesurf.fr> 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: Kernel compilation problem 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: Sat, 11 Dec 2004 00:43:02 -0000 On Tue, Dec 07, 2004 at 06:06:21PM +0100, Guillaume R. wrote: > > On Monday 06 December 2004 05:50 am, freebsd2@freesurf.fr wrote: > >> Hi all! > >> I'm very new to FreeBSD (indeed I ran it since one week) and I need to > >> compile my kernel so that some patches will apply correctly. So I made > >> all the process I type make depends && make and I've got sth like > >> this: > >> ../../../i386/i386/genassym.c:216:error: storage size of BC32SELw0 > >> isn't known > >> I've got that for all BC32 and furthermore on line 214 for KSPEL :( So > >> the compilation stops on an error code. > >> Does anyone got a clue? > >> Many thx :) > > > > It means you're in the wrong directory and as a result, trying to build > > an i386 kernel on an amd64 machine with an amd64 compiler. > > > > You probably want to do your thing in /usr/src/sys/amd64/conf > > and /usr/src/sys/amd64/compile/... > I am in those directories I try again and pay attention to this. > Do u think it's a bug or sth like that? You can't be doing this in /usr/src/sys/amd64/conf otherwise you would never try to compile i386/i386/genassym.c. Exactly what are the commands and steps you are taking in trying to build a kernel? From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 05:26:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E91CD16A4CE for ; Sat, 11 Dec 2004 05:26:39 +0000 (GMT) Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9F7643D39 for ; Sat, 11 Dec 2004 05:26:39 +0000 (GMT) (envelope-from bluestateblues@hushmail.com) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id BA0A7A3618 for ; Fri, 10 Dec 2004 21:26:38 -0800 (PST) Received: from mailserver3.hushmail.com (mailserver3.hushmail.com [65.39.178.20]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Fri, 10 Dec 2004 21:26:38 -0800 (PST) Received: (from nobody@localhost) by mailserver3.hushmail.com (8.12.11/8.12.9/Submit) id iBB5Qbc7007440 for freebsd-amd64@FreeBSD.org; Fri, 10 Dec 2004 21:26:37 -0800 (PST) (envelope-from bluestateblues@hushmail.com) Message-Id: <200412110526.iBB5Qbc7007440@mailserver3.hushmail.com> Date: Fri, 10 Dec 2004 21:26:35 -0800 To: freebsd-amd64@FreeBSD.org From: Subject: 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, 11 Dec 2004 05:26:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.4 wkYEARECAAYFAkG6hQgACgkQz7EVtfYVyOdZGQCgmJinRcHsqrtbnf0FEjrmValvtqYA oLAwUExk+Gy5gwiaofJWsjU41pDo =WQsP -----END PGP SIGNATURE----- Concerned about your privacy? Follow this link to get secure FREE email: http://www.hushmail.com/?l=2 Free, ultra-private instant messaging with Hush Messenger http://www.hushmail.com/services-messenger?l=434 Promote security and make money with the Hushmail Affiliate Program: http://www.hushmail.com/about-affiliate?l=427 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 11 19:52:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17B7016A4CE for ; Sat, 11 Dec 2004 19:52:06 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE11643D2D for ; Sat, 11 Dec 2004 19:52:05 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iBBJq4h05147; Sat, 11 Dec 2004 11:52:04 -0800 (PST) Date: Sat, 11 Dec 2004 11:52:04 -0800 From: Mike Hunter To: Mike Jakubik Message-ID: <20041211195204.GB5024@ack.Berkeley.EDU> References: <20041207222347.GA23656@ack.Berkeley.EDU> <60451.207.219.213.163.1102458724.squirrel@207.219.213.163> <20041207233101.GA29595@ack.Berkeley.EDU> <20041208180858.GA10932@ack.Berkeley.EDU> <20041209220034.GA2250@ack.Berkeley.EDU> <20041209221605.GA6906@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209221605.GA6906@ack.Berkeley.EDU> User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: [Solved] Re: Same problem w/ 6.0 (Was: problems compiling perl 5.8.5 w/ fbsd 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, 11 Dec 2004 19:52:06 -0000 On Dec 09, "To Mike Jakubik" wrote: > > More bad news: It's still doing the same thing :( > > > > 12400 root 118 0 2871M 2698M CPU0 1 3:02 98.94% 98.93% perl > > > > uname -a > > > > FreeBSD mybox 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Dec 9 12:09:07 PST 2004 root@mybox:/usr/obj/usr/src/sys/mybox amd64 > > > > I'm ready to help; any guidance? > > I grabbed the perl 5.8.6 source and it gets stuck in the same place. Believe it or not, somebody wrote and suggested that I hadn't run ntpdate. It looks like that did the trick (although looking at the date before I ran ntpdate didn't show it was off by much...maybe it was set for 2004 bc or something.) Thanks and sorry for the noise. Mike