From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 06:52:20 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8567616A430; Sun, 11 Sep 2005 06:52:18 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 166C943D46; Sun, 11 Sep 2005 06:52:17 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j8B6qGZm082400; Sun, 11 Sep 2005 02:52:17 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id j8B6qGL2092990; Sun, 11 Sep 2005 02:52:16 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7A9EA7302F; Sun, 11 Sep 2005 02:52:16 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050911065216.7A9EA7302F@freebsd-current.sentex.ca> Date: Sun, 11 Sep 2005 02:52:16 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 06:52:20 -0000 TB --- 2005-09-11 04:53:37 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-09-11 04:53:37 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-09-11 04:53:37 - cleaning the object tree TB --- 2005-09-11 04:54:26 - checking out the source tree TB --- 2005-09-11 04:54:26 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-09-11 04:54:26 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-09-11 05:04:46 - building world (CFLAGS=-O2 -pipe) TB --- 2005-09-11 05:04:46 - cd /src TB --- 2005-09-11 05:04:46 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-09-11 06:51:08 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-09-11 06:51:08 - cd /src TB --- 2005-09-11 06:51:08 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Sep 11 06:51:08 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] /src/sys/dev/twa/tw_cl_misc.c:42:26: tw_osl_share.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:43:25: tw_cl_share.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:44:24: tw_cl_fwif.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:45:25: tw_cl_ioctl.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:46:19: tw_cl.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:47:27: tw_cl_externs.h: No such file or directory /src/sys/dev/twa/tw_cl_misc.c:48:26: tw_osl_ioctl.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-09-11 06:52:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-09-11 06:52:16 - ERROR: failed to build generic kernel TB --- 2005-09-11 06:52:16 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 13:10:21 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D57116A420 for ; Sun, 11 Sep 2005 13:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A68E843D72 for ; Sun, 11 Sep 2005 13:10:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8BDACl3062337 for ; Sun, 11 Sep 2005 13:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8BDACAa062336; Sun, 11 Sep 2005 13:10:12 GMT (envelope-from gnats) Resent-Date: Sun, 11 Sep 2005 13:10:12 GMT Resent-Message-Id: <200509111310.j8BDACAa062336@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, Petr Janda Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D930716A41F for ; Sun, 11 Sep 2005 13:06:57 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB60F43D45 for ; Sun, 11 Sep 2005 13:06:57 +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 j8BD6vOQ062615 for ; Sun, 11 Sep 2005 13:06:57 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j8BD6vbN062614; Sun, 11 Sep 2005 13:06:57 GMT (envelope-from nobody) Message-Id: <200509111306.j8BD6vbN062614@www.freebsd.org> Date: Sun, 11 Sep 2005 13:06:57 GMT From: Petr Janda To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/85972: Movement of USB mouse in CLI causes freeze X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 13:10:21 -0000 >Number: 85972 >Category: amd64 >Synopsis: Movement of USB mouse in CLI causes freeze >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 11 13:10:11 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Petr Janda >Release: 6.0 Beta4 >Organization: >Environment: >Description: Logitech Cordless Desktop LX700 USB. Movement of the cordless mouse in CLI causes a full input freeze. This is a fresh install. The bug has been existing in FreeBSD 5.4 also. Cant speak of earlier versions because I only got the cordless desktop recently. Works while using a USB -> PS/2 adapter, but no scrolling is possible. >How-To-Repeat: Get the same cordless desktop, make a fresh install, start typing in CLI and then move your mouse. Nomore keyboard or mouse input possible. >Fix: Disable USBD. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 14:40:37 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37FFC16A41F for ; Sun, 11 Sep 2005 14:40:37 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85EFC43D46 for ; Sun, 11 Sep 2005 14:40:36 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 5667821848; Sun, 11 Sep 2005 14:40:36 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23192-05-2; Sun, 11 Sep 2005 14:40:35 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id E68DB21840; Sun, 11 Sep 2005 14:40:34 +0000 (GMT) Message-ID: <432441E3.2020004@jetnet.co.uk> Date: Sun, 11 Sep 2005 15:40:35 +0100 From: David Reid User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050908) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Neil Short , FreeBSD AMD64 Mailing List References: <20050904015940.77319.qmail@web30715.mail.mud.yahoo.com> In-Reply-To: <20050904015940.77319.qmail@web30715.mail.mud.yahoo.com> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Subject: Re: Mounting cd-rom X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 14:40:37 -0000 Neil Short wrote: > does it matter which cdrom? I.e., if you use a > different disc, is the behavior the same? Sorry for the delay, but I finally got round to trying this a bit more. Basically if I try and mount a "data" CD then it's fine. Mounting a music CD and it reboots - with nothing at all in /var/log/messages :-( I've confirmed this with at least 3 different music CD's. Kernel has WITNESS and debugger compiled in, so anything else I can do try and debug what's going on? david From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 15:37:05 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A52416A41F for ; Sun, 11 Sep 2005 15:37:05 +0000 (GMT) (envelope-from webmaster@machowto.com) Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [204.127.198.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ED6A43D46 for ; Sun, 11 Sep 2005 15:37:04 +0000 (GMT) (envelope-from webmaster@machowto.com) Received: from [192.168.0.4] (c-67-177-44-144.hsd1.ut.comcast.net[67.177.44.144]) by comcast.net (rwcrmhc14) with SMTP id <2005091115370401400fccu5e>; Sun, 11 Sep 2005 15:37:04 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Sun, 11 Sep 2005 09:37:02 -0600 From: "David S. Besade" To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 15:37:05 -0000 Hey Guys, I have a Dual Xeon (With EM64T) system running FreeBSD 5.4 AMD64 - Release (with a -stable kernel). I can't get the kernel to see my second CPU. I have recompiled and retuned and done everything I could to get it to see the second CPU. The guys on IRC (##Freebsd on freenode) told me to post this to this list. I do have the ACPI disabled as it doesn't work right yet. The Motherboard is a Tyan S5350 ( http://tyan.com/products/html/tigeri7320.html ) running with 2 Dual Nacona Core Xeons. I had the datacenter check the BIOS and everything is as it should be. I have Registered ECC RAM on it as well. Both CPU's were recogized by Centos 4.1 X86-64, however I prefer FBSD to anything Linux. So if you guys could help me out I would appreciate it. I think I have given you all the relevant information I Hope but if not just ask me I will get it. Thanks in advance -Dave From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 15:52:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16A5616A41F for ; Sun, 11 Sep 2005 15:52:31 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.28]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E70143D45 for ; Sun, 11 Sep 2005 15:52:29 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 425 invoked from network); 11 Sep 2005 15:52:28 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate2.pacific.net.sg with SMTP; 11 Sep 2005 15:52:28 -0000 Received: from [192.168.0.107] ([210.24.246.71]) by maxwell2.pacific.net.sg with ESMTP id <20050911155228.RNLX28012.maxwell2.pacific.net.sg@[192.168.0.107]>; Sun, 11 Sep 2005 23:52:28 +0800 Message-ID: <43245280.3040405@pacific.net.sg> Date: Sun, 11 Sep 2005 23:51:28 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050906) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "David S. Besade" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 15:52:31 -0000 Hi, David S. Besade wrote: > > I do have the ACPI disabled as it doesn't work right yet. The Motherboard is doesn't it have to be enabled for SMP to work? Erich From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 16:34:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0C9416A41F for ; Sun, 11 Sep 2005 16:34:40 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44D3143D45 for ; Sun, 11 Sep 2005 16:34:40 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.102] (tardiss.hsd1.ma.comcast.net[66.30.82.93]) by comcast.net (sccrmhc11) with ESMTP id <2005091116343801100bdhhne>; Sun, 11 Sep 2005 16:34:39 +0000 Message-ID: <43245C91.1090904@comcast.net> Date: Sun, 11 Sep 2005 12:34:25 -0400 From: Sean User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050907) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "David S. Besade" References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 16:34:40 -0000 David S. Besade wrote: > Hey Guys, > > I have a Dual Xeon (With EM64T) system running FreeBSD 5.4 AMD64 - Release > (with a -stable kernel). I can't get the kernel to see my second CPU. I have > recompiled and retuned and done everything I could to get it to see the > second CPU. The guys on IRC (##Freebsd on freenode) told me to post this to > this list. > > I do have the ACPI disabled as it doesn't work right yet. The Motherboard is > a Tyan S5350 ( http://tyan.com/products/html/tigeri7320.html ) running with > 2 Dual Nacona Core Xeons. I had the datacenter check the BIOS and everything > is as it should be. I have Registered ECC RAM on it as well. > > Both CPU's were recogized by Centos 4.1 X86-64, however I prefer FBSD to > anything Linux. So if you guys could help me out I would appreciate it. I > think I have given you all the relevant information I Hope but if not just > ask me I will get it. > > Thanks in advance > -Dave > > > _______________________________________________ > 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" > You said you did a kernel recompile, so did you include 'device acpi' 'options SMP' in your custom kernel before you recompiled? That is what did it for me. Do a 'dmesg | less' and near the top portion you should see a statement like 'FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs' and then after showing the cpu info. Like someone else mentioned, I also thought ACPI had to be enabled. Sean From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 17:29:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BFE216A41F for ; Sun, 11 Sep 2005 17:29:34 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9893743D45 for ; Sun, 11 Sep 2005 17:29:33 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j8BHTP4B058310; Sun, 11 Sep 2005 11:29:25 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4324697A.40301@samsco.org> Date: Sun, 11 Sep 2005 11:29:30 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rsh.lists@comcast.net References: <43245C91.1090904@comcast.net> In-Reply-To: <43245C91.1090904@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 17:29:34 -0000 Sean wrote: > David S. Besade wrote: > >> Hey Guys, >> >> I have a Dual Xeon (With EM64T) system running FreeBSD 5.4 AMD64 - >> Release >> (with a -stable kernel). I can't get the kernel to see my second CPU. >> I have >> recompiled and retuned and done everything I could to get it to see the >> second CPU. The guys on IRC (##Freebsd on freenode) told me to post >> this to >> this list. >> >> I do have the ACPI disabled as it doesn't work right yet. The >> Motherboard is >> a Tyan S5350 ( http://tyan.com/products/html/tigeri7320.html ) running >> with >> 2 Dual Nacona Core Xeons. I had the datacenter check the BIOS and >> everything >> is as it should be. I have Registered ECC RAM on it as well. >> >> Both CPU's were recogized by Centos 4.1 X86-64, however I prefer FBSD to >> anything Linux. So if you guys could help me out I would appreciate it. I >> think I have given you all the relevant information I Hope but if not >> just >> ask me I will get it. >> >> Thanks in advance >> -Dave >> >> >> _______________________________________________ >> 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" >> > You said you did a kernel recompile, so did you include > 'device acpi' ^^^^ You need 'device apic' here also. There is a difference between 'acpi' and 'apic. For SMP amd64 machines, you should have both. Simply put, the apic is what allows the first CPU to start up the other CPUs during boot. Scott From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 19:12:19 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D21EC16A41F; Sun, 11 Sep 2005 19:12:19 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DFA343D48; Sun, 11 Sep 2005 19:12:18 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j8BJBuMG018279; Sun, 11 Sep 2005 12:11:56 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j8BJBt9Y018190; Sun, 11 Sep 2005 12:11:55 -0700 (PDT) (envelope-from obrien) Date: Sun, 11 Sep 2005 12:11:55 -0700 From: "David O'Brien" To: "Mikhail T." Message-ID: <20050911191155.GA16393@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, "Mikhail T." , freebsd-amd64@FreeBSD.org, current@FreeBSD.org, gerald@FreeBSD.org References: <200509102303.j8AN3ZO9073021@blue.virtual-estates.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200509102303.j8AN3ZO9073021@blue.virtual-estates.net> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: gerald@FreeBSD.org, current@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: another case of Arithmetic exception on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 19:12:20 -0000 On Sat, Sep 10, 2005 at 07:03:35PM -0400, Mikhail T. wrote: > I built and installed audio/timidity the stock compiler with my usual > CFLAGS: > > -O2 -fno-strict-aliasing -pipe -march=opteron > > It dies on startup from SIGFPE. I turned on "-Wall -Werror" and patched > the port to compile cleanly without any warning. That did not help... How are you using the port? Can you give me an input file and the proper commandline invocation? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 20:15:57 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8C3416A41F for ; Sun, 11 Sep 2005 20:15:57 +0000 (GMT) (envelope-from alexander.okunevich@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6E0243D58 for ; Sun, 11 Sep 2005 20:15:56 +0000 (GMT) (envelope-from alexander.okunevich@gmail.com) Received: by zproxy.gmail.com with SMTP id l1so183885nzf for ; Sun, 11 Sep 2005 13:15:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ShbBaywKBqAcszib8YNTuUK2FvUDewq1hI8OuHd6d/KPmpjmiX8usn/z0dl4F6zoeRQlPiY5+3jLMgza/MwaIw6eN2ZaDRZvPmZ7RwXcWuTqRvIA343yx553yG46hwrb2c8mNHoqGVkdSgIF56+7TDbuDRtY8nl8HB0vVSAC56A= Received: by 10.36.251.12 with SMTP id y12mr2238967nzh; Sun, 11 Sep 2005 13:15:56 -0700 (PDT) Received: by 10.37.2.66 with HTTP; Sun, 11 Sep 2005 13:15:56 -0700 (PDT) Message-ID: <1621a35105091113156dc4abe4@mail.gmail.com> Date: Sun, 11 Sep 2005 23:15:56 +0300 From: Alexander Okunevich To: freebsd-amd64@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: (no subject) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alexander.okunevich@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 20:15:57 -0000 From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 20:19:33 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43D4316A41F for ; Sun, 11 Sep 2005 20:19:33 +0000 (GMT) (envelope-from alexander.okunevich@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D27943D5C for ; Sun, 11 Sep 2005 20:19:26 +0000 (GMT) (envelope-from alexander.okunevich@gmail.com) Received: by zproxy.gmail.com with SMTP id l1so184247nzf for ; Sun, 11 Sep 2005 13:19:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PAUzbGHlBS4Iv3kDL3s3IG6xpBzrnSMspsjXKZf3Oy52+WGIn+n5y4wxfB6hvmVFCE3oFjQ7fIQ5sLMIlvg8V+Z1sqWrKL1si5cwZPI+EqTzSKauuXgKSjos4CBEQ3ge4WSBRAgk7M0r+sJ/bS8AodzVmAJhMjQQiKDV+2uj/KQ= Received: by 10.36.215.14 with SMTP id n14mr2270398nzg; Sun, 11 Sep 2005 13:19:26 -0700 (PDT) Received: by 10.37.2.66 with HTTP; Sun, 11 Sep 2005 13:19:25 -0700 (PDT) Message-ID: <1621a351050911131951859269@mail.gmail.com> Date: Sun, 11 Sep 2005 23:19:26 +0300 From: Alexander Okunevich To: freebsd-amd64@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: subcribe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alexander.okunevich@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 20:19:33 -0000 subcribe From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 22:39:03 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD02E16A41F for ; Sun, 11 Sep 2005 22:39:03 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7775A43D45 for ; Sun, 11 Sep 2005 22:39:03 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 1C1F821088 for ; Sun, 11 Sep 2005 22:39:03 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27384-02 for ; Sun, 11 Sep 2005 22:39:00 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 4E15C20A81 for ; Sun, 11 Sep 2005 22:39:00 +0000 (GMT) Message-ID: <4324B202.3040908@jetnet.co.uk> Date: Sun, 11 Sep 2005 23:38:58 +0100 From: David Reid User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050908) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD AMD64 Mailing List X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Subject: reboots X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 22:39:04 -0000 Following a recent commit to the sound driver my system (-CURRENT) started rebooting when gnome started. The eventual cause turned out be as (seemingly) innocent as the following call snd_mtxassert(d->lock); [line 169 sys/dev/sound/pcm/sound.c] defined as void snd_mtxassert(void *m) { #ifdef USING_MUTEX #ifdef INVARIANTS struct mtx *mtx = m; mtx_assert(mtx, MA_OWNED); #endif #endif } This code runs OK on i386 (the developer who tested and committed said that's what he was running), so given that it didn't cause problems there, but does on my system I wondered if it might be somehow related to the issues I see when mounting music CD's? When the system reboots there is nothing written to the syslog and no sign of a kernel panic. I'm open to suggestions on how to further debug this :-) david From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 11 22:58:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B1CB16A420 for ; Sun, 11 Sep 2005 22:58:06 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0634043D68 for ; Sun, 11 Sep 2005 22:58:01 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: (qmail 8279 invoked from network); 11 Sep 2005 22:58:01 -0000 Received: from aldan.algebra.com (HELO blue.virtual-estates.net) ([216.254.65.224]) (envelope-sender ) by mail26.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 11 Sep 2005 22:58:01 -0000 Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j8BMvxIl000196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Sep 2005 18:57:59 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by blue.virtual-estates.net (8.13.4/8.13.3/Submit) id j8BMvx4A000195; Sun, 11 Sep 2005 18:57:59 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) X-Authentication-Warning: blue.virtual-estates.net: mi set sender to mi+kde@aldan.algebra.com using -f From: Mikhail Teterin To: obrien@freebsd.org, freebsd-amd64@freebsd.org, current@freebsd.org, gerald@freebsd.org Date: Sun, 11 Sep 2005 18:57:58 -0400 User-Agent: KMail/1.8.1 References: <200509102303.j8AN3ZO9073021@blue.virtual-estates.net> <20050911191155.GA16393@dragon.NUXI.org> In-Reply-To: <20050911191155.GA16393@dragon.NUXI.org> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Subject: Re: another case of Arithmetic exception on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 22:58:06 -0000 On Sunday 11 September 2005 03:11 pm, David O'Brien wrote: = On Sat, Sep 10, 2005 at 07:03:35PM -0400, Mikhail T. wrote: = > I built and installed audio/timidity the stock compiler with my usual = > CFLAGS: = > = > -O2 -fno-strict-aliasing -pipe -march=opteron = > = > It dies on startup from SIGFPE. I turned on "-Wall -Werror" and patched = > the port to compile cleanly without any warning. That did not help... = = How are you using the port? Can you give me an input file and the proper = commandline invocation? Install audio/eawpats (it run-depends on timidity++) and try: timidity something.mid Here is a good example of a MIDI file: http://www.discoverynet.com/~ajsnead/theme/midi/ppanther_37.mid Thanks. -mi From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 01:57:01 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 108C216A41F for ; Mon, 12 Sep 2005 01:57:01 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87F3243D4C for ; Mon, 12 Sep 2005 01:57:00 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 229D48A037 for ; Mon, 12 Sep 2005 11:55:54 +1000 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 084698A035 for ; Mon, 12 Sep 2005 11:55:54 +1000 (EST) Message-ID: <4324E06A.4090400@roq.com> Date: Mon, 12 Sep 2005 11:56:58 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.11) Gecko/20050907 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: FAST_IPSEC on EMT64 / AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 01:57:01 -0000 Hi guys, I am getting a Intel Xeon based EMT64 server as a gateway that may in the future do some VPN, I wondered if the EMT64 servers could run FAST_IPSEC under AMD64 FreeBSD. With these options below compiled into the kernel I was able to boot FreeBSD with no panics if I booted into single user mode and then just did 'exit' to go back to regular boot, otherwise it would panic as if it was an AMD64 CPU. device crypto device cryptodev options FAST_IPSEC I read on one post earlier back that this problem with AMD64 and FAST_IPSEC isn't with the code but with a bug in the AMD64 CPU so I figured maybe such a bug doesn't exist on Intels EMT64. Has any one else tried this? I was wondering if I would have more luck if I tried 6.0 Otherwise might put i386 FreeBSD on instead or test with regular 'options IPSEC', but its a shame I can't get that extra bit of speed out of the machine running AMD64. Cheers, Mike From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 05:49:00 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E127E16A41F for ; Mon, 12 Sep 2005 05:49:00 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77FAD43D45 for ; Mon, 12 Sep 2005 05:49:00 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j8C5mx0r010484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 01:49:00 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j8C5mx6P032444; Mon, 12 Sep 2005 01:48:59 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 093D651233; Mon, 12 Sep 2005 01:48:58 -0400 (EDT) Date: Mon, 12 Sep 2005 01:48:58 -0400 From: Kris Kennaway To: Michael VInce Message-ID: <20050912054858.GA28647@xor.obsecurity.org> References: <4324E06A.4090400@roq.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <4324E06A.4090400@roq.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@FreeBSD.org Subject: Re: FAST_IPSEC on EMT64 / AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 05:49:01 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote: > Hi guys, > I am getting a Intel Xeon based EMT64 server as a gateway that may in=20 > the future do some VPN, > I wondered if the EMT64 servers could run FAST_IPSEC under AMD64 FreeBSD. > With these options below compiled into the kernel I was able to boot=20 > FreeBSD with no panics if I booted into single user mode and then just=20 > did 'exit' to go back to regular boot, otherwise it would panic as if=20 > it was an AMD64 CPU. You forgot to include details of the panic. Kris --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDJRbKWry0BWjoQKURAraeAKD/IefklyLeav1ERa7gtQUpUur6FgCdEuPw Nhi0mSimkSAJNWVcNO+WUxM= =ivnS -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 07:20:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5BDF16A420 for ; Mon, 12 Sep 2005 07:20:13 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6858543D48 for ; Mon, 12 Sep 2005 07:20:12 +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 9D7F11FFE8F; Mon, 12 Sep 2005 09:20:10 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 4CE1A1FFE82; Mon, 12 Sep 2005 09:20:08 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id A8502157F3; Mon, 12 Sep 2005 07:20:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 9DDFF157C4; Mon, 12 Sep 2005 07:20:03 +0000 (UTC) Date: Mon, 12 Sep 2005 07:20:03 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Kris Kennaway In-Reply-To: <20050912054858.GA28647@xor.obsecurity.org> Message-ID: References: <4324E06A.4090400@roq.com> <20050912054858.GA28647@xor.obsecurity.org> 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: FAST_IPSEC on EMT64 / AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 07:20:13 -0000 On Mon, 12 Sep 2005, Kris Kennaway wrote: > > On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote: > > Hi guys, > > I am getting a Intel Xeon based EMT64 server as a gateway that may in > > the future do some VPN, > > I wondered if the EMT64 servers could run FAST_IPSEC under AMD64 FreeBSD. > > With these options below compiled into the kernel I was able to boot > > FreeBSD with no panics if I booted into single user mode and then just > > did 'exit' to go back to regular boot, otherwise it would panic as if > > it was an AMD64 CPU. > > You forgot to include details of the panic. That would be really good to know. Then we'd finally know more than was given in http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 11:01:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E83F816A41F for ; Mon, 12 Sep 2005 11:01:57 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0C6B43D46 for ; Mon, 12 Sep 2005 11:01:57 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8CB1vFI025357 for ; Mon, 12 Sep 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8CB1uN3025351 for freebsd-amd64@freebsd.org; Mon, 12 Sep 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Sep 2005 11:01:56 GMT Message-Id: <200509121101.j8CB1uN3025351@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 11:01:58 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 fxp0: device timeout, fxp interface dies o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/07/25] amd64/84027 amd64 if_nve gets stuck o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/18] amd64/85081 amd64 TeamSpeak o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 6.0-BETA3 lockups on AMD64 o [2005/09/11] amd64/85972 amd64 Movement of USB mouse in CLI causes freez 40 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 FreeBSD 5.4 released version can not use o [2005/06/12] amd64/82178 amd64 missing 32bit subsystem o [2005/06/18] amd64/82380 amd64 buildworld error in libc o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/07/20] amd64/83806 amd64 Can not comple /usr/src/lib/msun/amd64/fe o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/09/02] amd64/85626 amd64 java/jdk15 compile error o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/09/07] amd64/85852 amd64 Typo in amd64 machine/specialreg.h 19 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 11:35:25 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEBC616A41F for ; Mon, 12 Sep 2005 11:35:24 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F0443D46 for ; Mon, 12 Sep 2005 11:35:24 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 76A1B4CD32; Mon, 12 Sep 2005 11:35:53 +0000 (GMT) Received: from [10.0.1.8] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 2ACDA4CD31; Mon, 12 Sep 2005 11:35:51 +0000 (GMT) Message-ID: <432567EF.2060800@roq.com> Date: Mon, 12 Sep 2005 21:35:11 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.11) Gecko/20050907 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4324E06A.4090400@roq.com> <20050912054858.GA28647@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@FreeBSD.org, Kris Kennaway Subject: Re: FAST_IPSEC on EMT64 / AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 11:35:25 -0000 Bjoern A. Zeeb wrote: >On Mon, 12 Sep 2005, Kris Kennaway wrote: > > > >>On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote: >> >> >>>Hi guys, >>>I am getting a Intel Xeon based EMT64 server as a gateway that may in >>>the future do some VPN, >>>I wondered if the EMT64 servers could run FAST_IPSEC under AMD64 FreeBSD. >>>With these options below compiled into the kernel I was able to boot >>>FreeBSD with no panics if I booted into single user mode and then just >>>did 'exit' to go back to regular boot, otherwise it would panic as if >>>it was an AMD64 CPU. >>> >>> >>You forgot to include details of the panic. >> >> > >That would be really good to know. > >Then we'd finally know more than was given in >http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211 > > Sorry instead of getting a core dump I grabbed a FreeBSD AMD64 beta4 6.0 ISO and put it on this server. But I do have some good news in what I found. Recompiled FAST_IPSEC into the kernel and rebooted it, it came up fine.. So then put in some ipsec security policies into /etc/ipsec.conf ipsec_enable="YES" and ran /etc/rc.d/ipsec start and it ran fine. I then installed ipsec-tools and loaded up the racoon daemon this also triggers a panic on my FreeBSD AMD64 6.0 laptop with out FAST_IPSEC being compiled into the kernel and its loaded up fine. This looks all completely solid. I haven't been able to panic the server with a full VPN configuration activated. The only thing I haven't done is tested if the IPSEC VPN actually can work. This is no mistake this is AMD64 kernel FreeBSD with FAST_IPSEC I just cheated using the Intel EMT64 Regards, Mike beast# /sbin/sysctl -a | grep ipsec ipsecpolicy 16 4K - 520 256 ipsecrequest 2 1K - 4 256 ipsec-reg 3 1K - 24 32 net.inet.ipsec.def_policy: 1 net.inet.ipsec.esp_trans_deflev: 1 net.inet.ipsec.esp_net_deflev: 1 net.inet.ipsec.ah_trans_deflev: 1 net.inet.ipsec.ah_net_deflev: 1 net.inet.ipsec.ah_cleartos: 1 net.inet.ipsec.ah_offsetmask: 0 net.inet.ipsec.dfbit: 0 net.inet.ipsec.ecn: 0 net.inet.ipsec.debug: 0 net.inet.ipsec.esp_randpad: -1 net.inet.ipsec.crypto_support: 0 net.inet6.ipsec6.def_policy: 1 net.inet6.ipsec6.esp_trans_deflev: 1 net.inet6.ipsec6.esp_net_deflev: 1 net.inet6.ipsec6.ah_trans_deflev: 1 net.inet6.ipsec6.ah_net_deflev: 1 net.inet6.ipsec6.ecn: 0 net.inet6.ipsec6.debug: 0 net.inet6.ipsec6.esp_randpad: -1 beast# uname -a FreeBSD beast 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Mon Sep 12 20:40:05 UTC 2005 root@beast:/usr/obj/usr/src/sys/GENERIC_IPSEC amd64 From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 12:57:15 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A40016A41F for ; Mon, 12 Sep 2005 12:57:15 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3031243D48 for ; Mon, 12 Sep 2005 12:57:15 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 7F44B21A01 for ; Mon, 12 Sep 2005 12:57:14 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 33777-02 for ; Mon, 12 Sep 2005 12:57:10 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 9C414219FB for ; Mon, 12 Sep 2005 12:57:10 +0000 (GMT) Message-ID: <43257B26.20809@jetnet.co.uk> Date: Mon, 12 Sep 2005 13:57:10 +0100 From: David Reid User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050908) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD AMD64 Mailing List References: <4324B202.3040908@jetnet.co.uk> In-Reply-To: <4324B202.3040908@jetnet.co.uk> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Subject: Re: reboots X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 12:57:15 -0000 David Reid wrote: > Following a recent commit to the sound driver my system (-CURRENT) > started rebooting when gnome started. The eventual cause turned out be > as (seemingly) innocent as the following call > > snd_mtxassert(d->lock); > [line 169 sys/dev/sound/pcm/sound.c] > > defined as > > void > snd_mtxassert(void *m) > { > #ifdef USING_MUTEX > #ifdef INVARIANTS > struct mtx *mtx = m; > > mtx_assert(mtx, MA_OWNED); > #endif > #endif > } > > This code runs OK on i386 (the developer who tested and committed said > that's what he was running), so given that it didn't cause problems > there, but does on my system I wondered if it might be somehow related > to the issues I see when mounting music CD's? When the system reboots > there is nothing written to the syslog and no sign of a kernel panic. > > I'm open to suggestions on how to further debug this :-) Added a DVD-rom to the machine today, and the simple action of opening the drawer, inserting a dvd and closing the drawer results in a reboot! Again, no panics and nothing in the logs :-( david From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 18:25:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E45416A41F for ; Mon, 12 Sep 2005 18:25:54 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C50343D45 for ; Mon, 12 Sep 2005 18:25:50 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 655DB1F87BF1; Mon, 12 Sep 2005 20:25:49 +0200 (CEST) Date: Mon, 12 Sep 2005 20:25:49 +0200 From: Roman Neuhauser To: Kris Kennaway Message-ID: <20050912182549.GB90492@isis.sigpipe.cz> References: <20050805225309.GA99941@luke.immure.com> <20050810034707.GA49313@dragon.NUXI.org> <20050810061322.GA91774@troutmask.apl.washington.edu> <20050810230238.GA3571@xor.obsecurity.org> <20050810232819.GA1035@troutmask.apl.washington.edu> <20050811005508.GA35453@xor.obsecurity.org> <20050811051125.GA8733@troutmask.apl.washington.edu> <20050811130805.GA48042@xor.obsecurity.org> <20050811145238.GA11289@troutmask.apl.washington.edu> <20050811145942.GA80118@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050811145942.GA80118@xor.obsecurity.org> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: Griping about the ports collection (Re: OpenOffice2.0 64Bit ready?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 18:25:54 -0000 # kris@obsecurity.org / 2005-08-11 10:59:42 -0400: > To repeat: what, *precisely*, is missing from the Porters' Handbook > that makes it "useless"? You're a ("foreign", non-@freebsd.org) port maintainer, and received a notification that a PR has been posted for your port. That PR includes a patch. Identify the part of PH that describes how to get the patch onto your machine from GNATS. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 19:34:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3ED6016A41F for ; Mon, 12 Sep 2005 19:34:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADED743D46 for ; Mon, 12 Sep 2005 19:34:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j8CJYb0r029375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 15:34:37 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j8CJYa6P010482; Mon, 12 Sep 2005 15:34:36 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 303BF511FD; Mon, 12 Sep 2005 15:34:36 -0400 (EDT) Date: Mon, 12 Sep 2005 15:34:36 -0400 From: Kris Kennaway To: Roman Neuhauser Message-ID: <20050912193436.GA63345@xor.obsecurity.org> References: <20050810034707.GA49313@dragon.NUXI.org> <20050810061322.GA91774@troutmask.apl.washington.edu> <20050810230238.GA3571@xor.obsecurity.org> <20050810232819.GA1035@troutmask.apl.washington.edu> <20050811005508.GA35453@xor.obsecurity.org> <20050811051125.GA8733@troutmask.apl.washington.edu> <20050811130805.GA48042@xor.obsecurity.org> <20050811145238.GA11289@troutmask.apl.washington.edu> <20050811145942.GA80118@xor.obsecurity.org> <20050912182549.GB90492@isis.sigpipe.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <20050912182549.GB90492@isis.sigpipe.cz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: Griping about the ports collection (Re: OpenOffice2.0 64Bit ready?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 19:34:38 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2005 at 08:25:49PM +0200, Roman Neuhauser wrote: > # kris@obsecurity.org / 2005-08-11 10:59:42 -0400: > > To repeat: what, *precisely*, is missing from the Porters' Handbook > > that makes it "useless"? >=20 > You're a ("foreign", non-@freebsd.org) port maintainer, and received > a notification that a PR has been posted for your port. That PR > includes a patch. Identify the part of PH that describes how to get > the patch onto your machine from GNATS. Is this really a problem? The main www.freebsd.org webpage has a link for 'view a bug report'. Also, when you received the notification that the PR has been posted (e.g. by someone assigning the PR to your non-freebsd.org address, or forwarding the mail), it will have included an explicit URL to view the PR. Kris --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDJdhLWry0BWjoQKURAtBgAKCsb9M6DCBe27lEnR4qkE623ISGRQCgoQl2 BwbugKfcNrA+rctoeVo1lKk= =dImW -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 19:35:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A12D16A41F for ; Mon, 12 Sep 2005 19:35:24 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from hotmail.com (bay20-f21.bay20.hotmail.com [64.4.54.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB87943D45 for ; Mon, 12 Sep 2005 19:35:23 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 12 Sep 2005 12:34:15 -0700 Message-ID: Received: from 201.1.184.167 by by20fd.bay20.hotmail.msn.com with HTTP; Mon, 12 Sep 2005 19:34:15 GMT X-Originating-IP: [201.1.184.167] X-Originating-Email: [thebluesgnr@hotmail.com] X-Sender: thebluesgnr@hotmail.com From: "theblues gnr" To: freebsd-amd64@freebsd.org Date: Mon, 12 Sep 2005 16:34:15 -0300 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 12 Sep 2005 19:34:15.0477 (UTC) FILETIME=[F5CB9E50:01C5B7D0] Subject: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 19:35:24 -0000 Hello everyone! I'm having trouble setting up networking on the ABIT AV8 motherboard using the onboard NIC. From: http://www.freebsd.org/platforms/amd64/motherboards.html "On-board ethernet controller (vge(4)) does not work unless statically compiled into kernel." I do know how to compile a kernel (from the Handbook) but I do not know how to compile a module statically. Could anyone please point me to the right documentation on doing that? I swear I looked almost everywhere (that is, everywhere but the right place). Also, I found on google that an alternative is to stop the module from being loaded at boot, and loading it only after the system boots. I tried to disable the module (disable-module if_vge on the console prompt) but I still get a kernel panic related to vge when booting. Is there a correct way to stop the module from being loaded? And how would I go about loading it manually, later? In case you're wondering, I had to disable the onboard NIC to install FreeBSD, or I get a kernel panic. Thanks in advance. :) _________________________________________________________________ Chegou o que faltava: MSN Acesso Grátis. Instale Já! http://www.msn.com.br/discador From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 19:40:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9CEA16A41F for ; Mon, 12 Sep 2005 19:40:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C51E43D46 for ; Mon, 12 Sep 2005 19:40:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j8CJeR0r029962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 15:40:27 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j8CJeR6P010947; Mon, 12 Sep 2005 15:40:27 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 11BA4511FD; Mon, 12 Sep 2005 15:40:27 -0400 (EDT) Date: Mon, 12 Sep 2005 15:40:26 -0400 From: Kris Kennaway To: theblues gnr Message-ID: <20050912194026.GA63524@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 19:40:28 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2005 at 04:34:15PM -0300, theblues gnr wrote: > Hello everyone! >=20 > I'm having trouble setting up networking on the ABIT AV8 motherboard usin= g=20 > the onboard NIC. From: > http://www.freebsd.org/platforms/amd64/motherboards.html >=20 > "On-board ethernet controller (vge(4)) does not work unless statically=20 > compiled into kernel." >=20 > I do know how to compile a kernel (from the Handbook) but I do not know h= ow=20 > to compile a module statically. Could anyone please point me to the right= =20 > documentation on doing that? It means "do not use a (dynamic) module, compile the driver into your (static) kernel." Kris --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDJdmqWry0BWjoQKURAgpDAKDMbXqaw/Fzjyte73136jk1ddG3IgCeKCwZ 5x9aqjZHGvZ7ujKqFfYLyIY= =7sqG -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 20:32:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C55E16A41F for ; Mon, 12 Sep 2005 20:32:46 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16EFA43D48 for ; Mon, 12 Sep 2005 20:32:45 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (localhost [127.0.0.1]) by malcolm.berkeley.edu (8.13.3/8.13.3) with ESMTP id j8CKWil9053646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 13:32:45 -0700 (PDT) (envelope-from mhunter@malcolm.berkeley.edu) Received: (from mhunter@localhost) by malcolm.berkeley.edu (8.13.3/8.13.3/Submit) id j8CKWgha053645; Mon, 12 Sep 2005 13:32:42 -0700 (PDT) (envelope-from mhunter) Date: Mon, 12 Sep 2005 13:32:42 -0700 From: Mike Hunter To: Scott Long Message-ID: <20050912203242.GA53403@malcolm.berkeley.edu> References: <43245C91.1090904@comcast.net> <4324697A.40301@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4324697A.40301@samsco.org> User-Agent: Mutt/1.5.6i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [127.0.0.1]); Mon, 12 Sep 2005 13:32:45 -0700 (PDT) Cc: freebsd-amd64@freebsd.org Subject: Re: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 20:32:46 -0000 On Sep 11, "Scott Long" wrote: > Sean wrote: > >David S. Besade wrote: > >>I have a Dual Xeon (With EM64T) system running FreeBSD 5.4 AMD64 - > >>Release (with a -stable kernel). I can't get the kernel to see my > >>second CPU. I have recompiled and retuned and done everything I could > >>to get it to see the second CPU. The guys on IRC (##Freebsd on > >>freenode) told me to post this to this list. > >>I do have the ACPI disabled as it doesn't work right yet. The > >>Motherboard is a Tyan S5350 ( > >>http://tyan.com/products/html/tigeri7320.html ) running with 2 Dual > >>Nacona Core Xeons. I had the datacenter check the BIOS and everything > >>is as it should be. I have Registered ECC RAM on it as well. > >>Both CPU's were recogized by Centos 4.1 X86-64, however I prefer FBSD > >>to anything Linux. So if you guys could help me out I would appreciate > >>it. I think I have given you all the relevant information I Hope but > >>if not just ask me I will get it. > >You said you did a kernel recompile, so did you include > >'device acpi' > > ^^^^ > You need 'device apic' here also. There is a difference between 'acpi' > and 'apic. For SMP amd64 machines, you should have both. Simply put, > the apic is what allows the first CPU to start up the other CPUs during > boot. I thought apic was "built in" to amd64...? http://docs.freebsd.org/cgi/mid.cgi?20041208074109.GB35079 From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 20:37:18 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B353716A41F for ; Mon, 12 Sep 2005 20:37:18 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 237CC43D45 for ; Mon, 12 Sep 2005 20:37:17 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j8CKbCVV066960; Mon, 12 Sep 2005 14:37:12 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4325E6F9.3020108@samsco.org> Date: Mon, 12 Sep 2005 14:37:13 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hunter References: <43245C91.1090904@comcast.net> <4324697A.40301@samsco.org> <20050912203242.GA53403@malcolm.berkeley.edu> In-Reply-To: <20050912203242.GA53403@malcolm.berkeley.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Problems with Nacona Xeons X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 20:37:18 -0000 Mike Hunter wrote: > On Sep 11, "Scott Long" wrote: > > >>Sean wrote: >> >>>David S. Besade wrote: > > >>>>I have a Dual Xeon (With EM64T) system running FreeBSD 5.4 AMD64 - >>>>Release (with a -stable kernel). I can't get the kernel to see my >>>>second CPU. I have recompiled and retuned and done everything I could >>>>to get it to see the second CPU. The guys on IRC (##Freebsd on >>>>freenode) told me to post this to this list. > > >>>>I do have the ACPI disabled as it doesn't work right yet. The >>>>Motherboard is a Tyan S5350 ( >>>>http://tyan.com/products/html/tigeri7320.html ) running with 2 Dual >>>>Nacona Core Xeons. I had the datacenter check the BIOS and everything >>>>is as it should be. I have Registered ECC RAM on it as well. > > >>>>Both CPU's were recogized by Centos 4.1 X86-64, however I prefer FBSD >>>>to anything Linux. So if you guys could help me out I would appreciate >>>>it. I think I have given you all the relevant information I Hope but >>>>if not just ask me I will get it. > > >>>You said you did a kernel recompile, so did you include >>>'device acpi' >> >> ^^^^ >>You need 'device apic' here also. There is a difference between 'acpi' >>and 'apic. For SMP amd64 machines, you should have both. Simply put, >>the apic is what allows the first CPU to start up the other CPUs during >>boot. > > > I thought apic was "built in" to amd64...? > > http://docs.freebsd.org/cgi/mid.cgi?20041208074109.GB35079 Gah! You're right. It's atpic that has to be explicitely included. Sorry for the bad info. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 21:37:07 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8063416A41F for ; Mon, 12 Sep 2005 21:37:07 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from hotmail.com (bay20-f3.bay20.hotmail.com [64.4.54.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C2243D53 for ; Mon, 12 Sep 2005 21:37:06 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 12 Sep 2005 14:37:06 -0700 Message-ID: Received: from 201.1.184.167 by by20fd.bay20.hotmail.msn.com with HTTP; Mon, 12 Sep 2005 21:37:06 GMT X-Originating-IP: [201.1.184.167] X-Originating-Email: [thebluesgnr@hotmail.com] X-Sender: thebluesgnr@hotmail.com In-Reply-To: <20050912194026.GA63524@xor.obsecurity.org> From: "theblues gnr" To: freebsd-amd64@freebsd.org Date: Mon, 12 Sep 2005 18:37:06 -0300 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 12 Sep 2005 21:37:06.0882 (UTC) FILETIME=[1F7EC220:01C5B7E2] Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 21:37:07 -0000 First of all, thank you for your reply. Mon, Sep 12, 2005 at 04:34:15PM -0300, theblues gnr wrote: > > Hello everyone! > > > > I'm having trouble setting up networking on the ABIT AV8 motherboard >using > > the onboard NIC. From: > > http://www.freebsd.org/platforms/amd64/motherboards.html > > > > "On-board ethernet controller (vge(4)) does not work unless statically > > compiled into kernel." > > > > I do know how to compile a kernel (from the Handbook) but I do not know >how > > to compile a module statically. Could anyone please point me to the >right > > documentation on doing that? > >It means "do not use a (dynamic) module, compile the driver into your >(static) kernel." > >Kris I didn't word my problem correctly; what I wanted to know is how to compile the driver statically. When I follow the instructions on building a custom kernel the vge driver gets built as a module. Thank you, _________________________________________________________________ Chegou o que faltava: MSN Acesso Grátis. Instale Já! http://www.msn.com.br/discador From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 22:27:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E66616A41F for ; Mon, 12 Sep 2005 22:27:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2E8043D45 for ; Mon, 12 Sep 2005 22:27:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j8CMRn0r012408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 18:27:49 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j8CMRm6P024591; Mon, 12 Sep 2005 18:27:48 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 489A8511FC; Mon, 12 Sep 2005 18:27:48 -0400 (EDT) Date: Mon, 12 Sep 2005 18:27:48 -0400 From: Kris Kennaway To: theblues gnr Message-ID: <20050912222748.GA12943@xor.obsecurity.org> References: <20050912194026.GA63524@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 22:27:50 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2005 at 06:37:06PM -0300, theblues gnr wrote: >=20 >=20 > First of all, thank you for your reply. >=20 > Mon, Sep 12, 2005 at 04:34:15PM -0300, theblues gnr wrote: > >> Hello everyone! > >> > >> I'm having trouble setting up networking on the ABIT AV8 motherboard= =20 > >using > >> the onboard NIC. From: > >> http://www.freebsd.org/platforms/amd64/motherboards.html > >> > >> "On-board ethernet controller (vge(4)) does not work unless statically > >> compiled into kernel." > >> > >> I do know how to compile a kernel (from the Handbook) but I do not kno= w=20 > >how > >> to compile a module statically. Could anyone please point me to the=20 > >right > >> documentation on doing that? > > > >It means "do not use a (dynamic) module, compile the driver into your > >(static) kernel." > > > >Kris >=20 > I didn't word my problem correctly; what I wanted to know is how to compi= le=20 > the driver statically. When I follow the instructions on building a custo= m=20 > kernel the vge driver gets built as a module. Edit the kernel configuration file and add the appropriate entry (cf GENERIC or NOTES). This is surely described in the handbook. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDJgDjWry0BWjoQKURAoD6AKC/RoregfpOVwMkGUMk/XBip62k6wCgyOj3 mCpGlHvWp9vNTeDAdsRvtWQ= =HyWY -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 22:49:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B9B216A41F for ; Mon, 12 Sep 2005 22:49:32 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: from web81803.mail.mud.yahoo.com (web81803.mail.mud.yahoo.com [68.142.207.168]) by mx1.FreeBSD.org (Postfix) with SMTP id 01CDF43D48 for ; Mon, 12 Sep 2005 22:49:31 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: (qmail 94062 invoked by uid 60001); 12 Sep 2005 22:49:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MnKqJngbXUeRDa3JidMHqokEi5jCXQ3ADaes6MYfScZ9PqSLxu64QZ9FyThyt5/ParEoVfeLdh6ng91WZZmIDUrq6ViIInI/YykSWbCMi1YWb40Qow0/pvOGrfETAUy6sluRKLLOuCFC2GmkUxslwPnnACYHMxypLoe6xX0tsh0= ; Message-ID: <20050912224931.94060.qmail@web81803.mail.mud.yahoo.com> Received: from [71.130.151.221] by web81803.mail.mud.yahoo.com via HTTP; Mon, 12 Sep 2005 15:49:31 PDT Date: Mon, 12 Sep 2005 15:49:31 -0700 (PDT) From: Patrick Lehner To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: linux_glide X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 22:49:32 -0000 Has anyone gotten linux_glide to work? I know, the Makefile sez i386 only, but that hasn't stopped other apps to install by either modifying the Makefile or setting the environment variable for *ARCH to i386 One problem that immediately comes to mind is that linux glide was built with XFree libs, while FreeBSD uses xorg. Thanks From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 22:55:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8FE916A420 for ; Mon, 12 Sep 2005 22:55:04 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: from web81804.mail.mud.yahoo.com (web81804.mail.mud.yahoo.com [68.142.207.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C8DA43D58 for ; Mon, 12 Sep 2005 22:55:03 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: (qmail 93177 invoked by uid 60001); 12 Sep 2005 22:55:03 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=p9N0BUN1cTwcoERGQFqXYJTxj0Ja9UXJYnBjAZzoX6NVGsfILMpNkr27UPnx+yhq+2wwOPjoTfAkIM1oAmgrIDoU61Pfi6WvfrqUxSXlr3h9grcIP7Ds7AVhcvJpjjY1EejMeC8R+x08LTseyDiqLsN1Vbs+5nYVToVTxXCLi6c= ; Message-ID: <20050912225503.93175.qmail@web81804.mail.mud.yahoo.com> Received: from [71.130.151.221] by web81804.mail.mud.yahoo.com via HTTP; Mon, 12 Sep 2005 15:55:03 PDT Date: Mon, 12 Sep 2005 15:55:03 -0700 (PDT) From: Patrick Lehner To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Correction: I meant linux_dri X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 22:55:04 -0000 Has anyone gotten linux_dri to work? I know, the Makefile sez i386 only, but that hasn't stopped other apps to install by either modifying the Makefile or setting the environment variable for *ARCH to i386 One problem that immediately comes to mind is that linux dri was built with XFree libs, while FreeBSD uses xorg. Thanks From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 12 23:52:05 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C17F16A41F for ; Mon, 12 Sep 2005 23:52:05 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E927F43D45 for ; Mon, 12 Sep 2005 23:52:04 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id j8CNq3Cf068141; Mon, 12 Sep 2005 16:52:04 -0700 (PDT) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id j8CNq3J7068140; Mon, 12 Sep 2005 16:52:03 -0700 (PDT) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Patrick Lehner In-Reply-To: <20050912225503.93175.qmail@web81804.mail.mud.yahoo.com> References: <20050912225503.93175.qmail@web81804.mail.mud.yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-3aDI6IuwkiX0GchGWOe3" Date: Mon, 12 Sep 2005 16:52:02 -0700 Message-Id: <1126569122.34672.37.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.3.8 FreeBSD GNOME Team Port Cc: freebsd-amd64@freebsd.org Subject: Re: Correction: I meant linux_dri X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 23:52:05 -0000 --=-3aDI6IuwkiX0GchGWOe3 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2005-09-12 at 15:55 -0700, Patrick Lehner wrote: > Has anyone gotten linux_dri to work? I know, the > Makefile sez i386 only, but that hasn't stopped other > apps to install by either modifying the Makefile or > setting the environment variable for *ARCH to i386 >=20 > One problem that immediately comes to mind is that > linux dri was built with XFree libs, while FreeBSD > uses xorg. linux_dri is really really stale. Someone needs to update it, and I haven't ever got around to it. Someone also needs to build amd64 binaries for it. And someone needs to build a compat ioctl layer so we can do both 32-bit and 64-bit clients in the DRM (32 should not work currently). --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-3aDI6IuwkiX0GchGWOe3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDJhSiHUdvYGzw6vcRAmpCAKCM657S5KK2/VWMHCmL1sRscg3lPwCgidFy mN1wRIpH0s0UZKRwYwbZC+E= =1j0/ -----END PGP SIGNATURE----- --=-3aDI6IuwkiX0GchGWOe3-- From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 01:43:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C8316A41F for ; Tue, 13 Sep 2005 01:43:11 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84A5143D46 for ; Tue, 13 Sep 2005 01:43:06 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id i31so2576115wxd for ; Mon, 12 Sep 2005 18:43:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JJ+294D69EElbG5Fi8Pv2wyWFR6RUwFPtn64du1Anq5od9uCKPJI6xtjy/8tn/Ikn+o11Dm7rC/qyFnPwLtpieWN1uoLiOm1eYQTXOGfa9H122ewTLpQtWO387L0xZVZFVqGQTabjtdKuZimqCVuJl591s4VczMJHHrxpaHGEy4= Received: by 10.70.60.6 with SMTP id i6mr13956wxa; Mon, 12 Sep 2005 18:43:05 -0700 (PDT) Received: by 10.70.115.15 with HTTP; Mon, 12 Sep 2005 18:43:05 -0700 (PDT) Message-ID: <84dead7205091218434516ab6d@mail.gmail.com> Date: Tue, 13 Sep 2005 07:13:05 +0530 From: Joseph Koshy To: theblues gnr In-Reply-To: <20050912222748.GA12943@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050912194026.GA63524@xor.obsecurity.org> <20050912222748.GA12943@xor.obsecurity.org> Cc: freebsd-amd64@freebsd.org Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: joseph.koshy@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 01:43:11 -0000 theblues> the driver statically. When I follow the instructions=20 theblues> on building a custom kernel the vge driver gets built=20 theblues> as a module. Modules will get built even if the relevant driver is already statically linked into the kernel. No-one has got around to integrating config(8) with the kernel module build system. --=20 FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 08:05:39 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6321716A41F for ; Tue, 13 Sep 2005 08:05:39 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Jb9d8.j.pppool.de [85.74.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF30443D4C for ; Tue, 13 Sep 2005 08:05:38 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j8D85axE006180; Tue, 13 Sep 2005 10:05:36 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200509130805.j8D85axE006180@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: joseph.koshy@gmail.com In-Reply-To: Message from Joseph Koshy of "Tue, 13 Sep 2005 07:13:05 +0530." <84dead7205091218434516ab6d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Sep 2005 10:05:36 +0200 From: Gary Jennejohn Cc: freebsd-amd64@freebsd.org Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 08:05:39 -0000 Joseph Koshy writes: > theblues> the driver statically. When I follow the instructions=20 > theblues> on building a custom kernel the vge driver gets built=20 > theblues> as a module. > > Modules will get built even if the relevant driver is already > statically linked into the kernel. No-one has got around to > integrating config(8) with the kernel module build system. > Of course, one can specify which modules to build using ``makeoptions MODULES_OVERRIDE''. I build only linux, linprocfs, msdosfs, pseudofs, netgraph/ether and geom/geom_concat as modules. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 09:08:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1222016A41F for ; Tue, 13 Sep 2005 09:08:40 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 938FE43D46 for ; Tue, 13 Sep 2005 09:08:38 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id B6BD81F87BEF; Tue, 13 Sep 2005 11:08:37 +0200 (CEST) Date: Tue, 13 Sep 2005 11:08:37 +0200 From: Roman Neuhauser To: Kris Kennaway Message-ID: <20050913090837.GA563@isis.sigpipe.cz> References: <20050810061322.GA91774@troutmask.apl.washington.edu> <20050810230238.GA3571@xor.obsecurity.org> <20050810232819.GA1035@troutmask.apl.washington.edu> <20050811005508.GA35453@xor.obsecurity.org> <20050811051125.GA8733@troutmask.apl.washington.edu> <20050811130805.GA48042@xor.obsecurity.org> <20050811145238.GA11289@troutmask.apl.washington.edu> <20050811145942.GA80118@xor.obsecurity.org> <20050912182549.GB90492@isis.sigpipe.cz> <20050912193436.GA63345@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050912193436.GA63345@xor.obsecurity.org> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: Griping about the ports collection (Re: OpenOffice2.0 64Bit ready?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 09:08:40 -0000 # kris@obsecurity.org / 2005-09-12 15:34:36 -0400: > On Mon, Sep 12, 2005 at 08:25:49PM +0200, Roman Neuhauser wrote: > > # kris@obsecurity.org / 2005-08-11 10:59:42 -0400: > > > To repeat: what, *precisely*, is missing from the Porters' Handbook > > > that makes it "useless"? > > > > You're a ("foreign", non-@freebsd.org) port maintainer, and received > > a notification that a PR has been posted for your port. That PR > > includes a patch. Identify the part of PH that describes how to get > > the patch onto your machine from GNATS. > > Is this really a problem? The main www.freebsd.org webpage has a link > for 'view a bug report'. Also, when you received the notification > that the PR has been posted (e.g. by someone assigning the PR to your > non-freebsd.org address, or forwarding the mail), it will have > included an explicit URL to view the PR. First, this omission doesn't make the PH useless, but including a bit of text would make it better. Second, while you can certainly fetch(1) the url (don't forget to add &f=raw), and if the PR contains a single diff, patch(1) will do quite a good job of surgeoning it from the blob, it gets bothersome in more complicated cases. How do *you* handle this? Third, the PH isn't as organized as it could be, especially the "Dos and Don'ts" section, which, with its FAQy nature, is a heap of useful information whose utility is hampered /because/ it's a heap. But I haven't put any xml (yet) where my mouth is, so I'll get off my soap box. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 10:56:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5B8516A41F for ; Tue, 13 Sep 2005 10:56:50 +0000 (GMT) (envelope-from wolfgang.keller.nospam@gmx.de) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 67CAA43D48 for ; Tue, 13 Sep 2005 10:56:49 +0000 (GMT) (envelope-from wolfgang.keller.nospam@gmx.de) Received: (qmail invoked by alias); 13 Sep 2005 10:56:48 -0000 Received: from p54B77249.dip.t-dialin.net (EHLO localhost) [84.183.114.73] by mail.gmx.net (mp035) with SMTP; 13 Sep 2005 12:56:48 +0200 X-Authenticated: #645711 Date: Tue, 13 Sep 2005 12:56:44 +0200 From: Wolfgang Keller X-Mailer: The Bat! (v3.5.30) Home X-Priority: 3 (Normal) Message-ID: <162312088.20050913125644@gmx.de> To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: FreeBSD on Acer Ferrari 4000? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Wolfgang Keller List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 10:56:51 -0000 Hello, has someone tried to run FreeBSD on the Acer Ferrari 4000 notebook? The FreeBSD WWW site doesn't mention notebooks or at least I couldn't find it... TIA, Sincerely, Wolfgang Keller -- P.S.: My From-address is correct From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 17:44:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E57C116A41F for ; Tue, 13 Sep 2005 17:44:40 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from hotmail.com (bay20-f20.bay20.hotmail.com [64.4.54.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id B339843D46 for ; Tue, 13 Sep 2005 17:44:40 +0000 (GMT) (envelope-from thebluesgnr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 13 Sep 2005 10:44:40 -0700 Message-ID: Received: from 201.26.64.42 by by20fd.bay20.hotmail.msn.com with HTTP; Tue, 13 Sep 2005 17:44:40 GMT X-Originating-IP: [201.26.64.42] X-Originating-Email: [thebluesgnr@hotmail.com] X-Sender: thebluesgnr@hotmail.com In-Reply-To: <20050912222748.GA12943@xor.obsecurity.org> From: "theblues gnr" To: freebsd-amd64@freebsd.org Date: Tue, 13 Sep 2005 14:44:40 -0300 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 13 Sep 2005 17:44:40.0614 (UTC) FILETIME=[D148E460:01C5B88A] Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 17:44:41 -0000 > >Edit the kernel configuration file and add the appropriate entry (cf >GENERIC or NOTES). This is surely described in the handbook. > >Kris I built my own kernel, and I made sure to include the options: device miibus # MII bus support device vge # VIA VT612x gigabit ethernet I built twice, using each method (I named them FBSD001 and FBSD002). In both cases the custom kernel was installed, but still I got the panic when booting with the onboard VIA Velocity enabled. I also tried loading the kernel from the boot prompt, with the following options: unload (to unload all modules) disable-module if_vge boot And still the same kernel panic. :( Thanks everyone for the help so far. _________________________________________________________________ Chegou o que faltava: MSN Acesso Grátis. Instale Já! http://www.msn.com.br/discador From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 17:57:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7207216A41F for ; Tue, 13 Sep 2005 17:57:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03A1343D46 for ; Tue, 13 Sep 2005 17:57:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j8DHv30r017888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Sep 2005 13:57:03 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j8DHv36P027700; Tue, 13 Sep 2005 13:57:03 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DDFF0511FD; Tue, 13 Sep 2005 13:57:02 -0400 (EDT) Date: Tue, 13 Sep 2005 13:57:02 -0400 From: Kris Kennaway To: theblues gnr Message-ID: <20050913175702.GA32612@xor.obsecurity.org> References: <20050912222748.GA12943@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Compiling modules statically X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 17:57:04 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 13, 2005 at 02:44:40PM -0300, theblues gnr wrote: > > > >Edit the kernel configuration file and add the appropriate entry (cf > >GENERIC or NOTES). This is surely described in the handbook. > > > >Kris >=20 > I built my own kernel, and I made sure to include the options: >=20 > device miibus # MII bus support > device vge # VIA VT612x gigabit ethernet >=20 > I built twice, using each method (I named them FBSD001 and FBSD002). In= =20 > both cases the custom kernel was installed, but still I got the panic whe= n=20 > booting with the onboard VIA Velocity enabled. >=20 > I also tried loading the kernel from the boot prompt, with the following= =20 > options: >=20 > unload (to unload all modules) > disable-module if_vge > boot >=20 > And still the same kernel panic. :( >=20 > Thanks everyone for the help so far. Sounds like the advice was incorrect then. Did you obtain a dump from the panic (see the developers' handbook chapter on kernel debugging)? Kris --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDJxLuWry0BWjoQKURAseCAKD12+kC2A5Rmckh/jybgVtfDqAoDACeMMHp OLmhNrmrygjLdNdvRMYXRmU= =Eke0 -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 18:00:40 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A5F216A41F for ; Tue, 13 Sep 2005 18:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B30C943D48 for ; Tue, 13 Sep 2005 18:00:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8DI0c7M067513 for ; Tue, 13 Sep 2005 18:00:38 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8DI0ckQ067510; Tue, 13 Sep 2005 18:00:38 GMT (envelope-from gnats) Resent-Date: Tue, 13 Sep 2005 18:00:38 GMT Resent-Message-Id: <200509131800.j8DI0ckQ067510@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, Lukasz Gryglicki Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4775116A41F for ; Tue, 13 Sep 2005 17:54:46 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 055F143D46 for ; Tue, 13 Sep 2005 17:54:46 +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 j8DHsjQR004287 for ; Tue, 13 Sep 2005 17:54:45 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j8DHsi2W004284; Tue, 13 Sep 2005 17:54:44 GMT (envelope-from nobody) Message-Id: <200509131754.j8DHsi2W004284@www.freebsd.org> Date: Tue, 13 Sep 2005 17:54:44 GMT From: Lukasz Gryglicki To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/86080: radeon DRI causes system hang on amd64 using mplayer -vo xv X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 18:00:40 -0000 >Number: 86080 >Category: amd64 >Synopsis: radeon DRI causes system hang on amd64 using mplayer -vo xv >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 13 18:00:38 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Lukasz Gryglicki >Release: FreeBSD-6.0-BETA4 >Organization: student >Environment: FreeBSD 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Tue Sep 13 15:19:54 CEST 2005 root@:/usr/src/sys/amd64/compile/STARLIGHT amd64 gcc (GCC) 3.4.4 [FreeBSD] 20050518 Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE >Description: When I use radeon.ko with Xorg with glx and dri enabled: glxinfo gives Direct Rendering Enables: YES. OpenGL applications works fine, but using mplayer 1.0pre5, 1.0pre6, 1.0pre7try2 causes system to hung, my radeon is: GeCube Radeon 9200 SE Game buster >How-To-Repeat: kldload radeon.ko, enable dri and glx in xorg.conf, startx, mplayer -vo xv somefile.avi >Fix: ? >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 13 23:18:47 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A071B16A41F; Tue, 13 Sep 2005 23:18:47 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E9143D45; Tue, 13 Sep 2005 23:18:47 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8DNIl3W015098; Tue, 13 Sep 2005 23:18:47 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8DNIlhK015094; Tue, 13 Sep 2005 23:18:47 GMT (envelope-from linimon) Date: Tue, 13 Sep 2005 23:18:47 GMT From: Mark Linimon Message-Id: <200509132318.j8DNIlhK015094@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: kern/82380: [libc] [patch] buildworld error in libc X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 23:18:47 -0000 Synopsis: [libc] [patch] buildworld error in libc Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Sep 13 23:18:15 GMT 2005 Responsible-Changed-Why: Yes, it's about amd64, but this is really a problem in libc. http://www.freebsd.org/cgi/query-pr.cgi?pr=82380 From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 14 16:55:39 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CBC316A443 for ; Wed, 14 Sep 2005 16:55:39 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02CAA43D48 for ; Wed, 14 Sep 2005 16:55:38 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id E1B5E3000277 for ; Wed, 14 Sep 2005 18:55:37 +0200 (CEST) Message-ID: <432855C8.20304@mail.uni-mainz.de> Date: Wed, 14 Sep 2005 18:54:32 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050908) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: java/jdk15: build failure on FBSD 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 16:55:39 -0000 Hello. Since my last posting about failing to build a working JDK I tried again with all the recommendations I got from this list. On FreeBSD/i386, build process still dies due to a sanity check error (watch out my previous posting about this error). One possible cause should be a missing Linuxulator - but that's not the trueth. Linux was enabled either as kernel module and loaded when system boots or staticaly built into the kernel. In both cases I receive the same error :-( On FreeBSD/AMD64 everything seems to build perfectly since this error occurs (and it seemes to be at the end of the build process): Force the Client VM when dumping the shared archive since you can't dump the archive with the Server VM. I feel confused, I read about this error but no solutions or workaround. It confuses me a bit that I still run into harsh trouble although I do exactly all the steps the port repository recommends! On the other hand, I ran into trouble fetching some essential ports needed by the jdk15-build process on an AMD64 architecture, but they are i386 and I needed fetching them on another i386-based machine (I remember myself it was a XFree86 library for Linux and not available for amd64, but fetching ports from FreeBSD 6.0/amd64 let me get ports only for amd64!). Within the last 4 years I belong to the 'small' (?) group of FreeBSD users who never had success compiling a working JAVA environment. So neither OpenOffice is fully working, nor FireFox or Mozilla are capable of working with JAVA under FBSD 5/6. Mmmmmmhhhh ... May there are some hidden hints and tricks? Oliver From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 14 18:47:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72B2F16A41F for ; Wed, 14 Sep 2005 18:47:48 +0000 (GMT) (envelope-from ralph@zitz.dk) Received: from camilla.zitz.dk (ip30.ds1-od.adsl.cybercity.dk [217.157.208.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id C31BB43D46 for ; Wed, 14 Sep 2005 18:47:46 +0000 (GMT) (envelope-from ralph@zitz.dk) Received: from localhost (localhost.zitz.dk [127.0.0.1]) by camilla.zitz.dk (8.13.4/8.13.3) with ESMTP id j8EIlimL013244 for ; Wed, 14 Sep 2005 20:47:44 +0200 (CEST) (envelope-from ralph@zitz.dk) Received: from camilla.zitz.dk ([127.0.0.1]) by localhost (camilla.zitz.dk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 95824-07 for ; Wed, 14 Sep 2005 20:47:27 +0200 (CEST) Received: from [10.0.0.2] ([10.0.0.2]) (authenticated bits=0) by camilla.zitz.dk (8.13.4/8.13.3) with ESMTP id j8EIlPvm013237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 14 Sep 2005 20:47:25 +0200 (CEST) (envelope-from ralph@zitz.dk) Message-ID: <4328703B.4020203@zitz.dk> Date: Wed, 14 Sep 2005 20:47:23 +0200 From: Ralph Zitz User-Agent: Thunderbird 1.6a1 (Windows/20050907) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at zitz.dk Subject: Building world X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 18:47:48 -0000 Hello. I'm currently running FreeBSD 6.0/AMD64 beta4 on my dual xeon nocona system. In /etc/make.conf I have CPUTYPE=nocona. Every time I do a cvsup to "update world" I have to manually change /usr/src/Makefile.inc1 LIB32PREFLAGS= -m32 -march=athlon-xp ........ to LIB32PREFLAGS= -m32 -march=prescott ........ Obviously it makes sense to have it set to athlon-xp for the AMD64 arch, but since I'm running on Nocona it would be nice to have it look at what CPUTYPE is set to. I guess the question is: Would it be possible to add this check ? Regards, Ralph. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 14 19:46:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBC3E16A41F for ; Wed, 14 Sep 2005 19:46:23 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D87243D53 for ; Wed, 14 Sep 2005 19:46:23 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.12.11/8.12.11) with ESMTP id j8EJkInF074901; Wed, 14 Sep 2005 14:46:18 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <43287E0A.8000001@palisadesys.com> Date: Wed, 14 Sep 2005 14:46:18 -0500 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" References: <432855C8.20304@mail.uni-mainz.de> In-Reply-To: <432855C8.20304@mail.uni-mainz.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-amd64@freebsd.org Subject: Re: java/jdk15: build failure on FBSD 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 19:46:24 -0000 O. Hartmann wrote: > Hello. > Since my last posting about failing to build a working JDK I tried > again with all the recommendations I got from this list. > > On FreeBSD/i386, build process still dies due to a sanity check error > (watch out my previous posting about this error). One possible cause > should be a missing Linuxulator - but that's not the trueth. Linux was > enabled either as kernel module and loaded when system boots or > staticaly built into the kernel. In both cases I receive the same > error :-( But was linprocfs mounted as /compat/linux/proc? > On FreeBSD/AMD64 everything seems to build perfectly since this error > occurs (and it seemes to be at the end of the build process): > > Force the Client VM when dumping the shared archive since you can't > dump the archive with the Server VM. I applied Greg Lewis' jdk15 patch he sent yesterday (at http://lists.freebsd.org/pipermail/freebsd-java/2005-September/004329.html) to the java/jdk15 port and I've successfully built the port on amd64 with it today. I tried building and installing it earlier today before I applied the patch, and it failed during the install with the "can't dump" error... > I feel confused, I read about this error but no solutions or > workaround. It confuses me a bit that I still run into harsh trouble > although I do exactly all the steps the port repository recommends! On > the other hand, I ran into trouble fetching some essential ports > needed by the jdk15-build process on an AMD64 architecture, but they > are i386 and I needed fetching them on another i386-based machine (I > remember myself it was a XFree86 library for Linux and not available > for amd64, but fetching ports from FreeBSD 6.0/amd64 let me get ports > only for amd64!). IIRC, I was able to fetch and install all the amd64 packages for Linux compatibility on my new amd64 machine installed from 6.0BETA2, and the Linux JDK worked just fine for me... I used portinstall, and I explicitly set PACKAGESITE to retrieve the binary packages from ftp://ftp2.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All... > Within the last 4 years I belong to the 'small' (?) group of FreeBSD > users who never had success compiling a working JAVA environment. So > neither OpenOffice is fully working, nor FireFox or Mozilla are > capable of working with JAVA under FBSD 5/6. Mmmmmmhhhh ... Good luck! Guy Helmer -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 14 23:15:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AC1216A41F for ; Wed, 14 Sep 2005 23:15:08 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id B07FF43D4C for ; Wed, 14 Sep 2005 23:15:04 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 228A03000681; Thu, 15 Sep 2005 01:15:03 +0200 (CEST) Message-ID: <4328AEB3.6060903@mail.uni-mainz.de> Date: Thu, 15 Sep 2005 01:13:55 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050908) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guy Helmer References: <432855C8.20304@mail.uni-mainz.de> <43287E0A.8000001@palisadesys.com> In-Reply-To: <43287E0A.8000001@palisadesys.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-amd64@freebsd.org Subject: Re: java/jdk15: build failure on FBSD 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 23:15:08 -0000 Guy Helmer wrote: > O. Hartmann wrote: > >> Hello. >> Since my last posting about failing to build a working JDK I tried >> again with all the recommendations I got from this list. >> >> On FreeBSD/i386, build process still dies due to a sanity check error >> (watch out my previous posting about this error). One possible cause >> should be a missing Linuxulator - but that's not the trueth. Linux was >> enabled either as kernel module and loaded when system boots or >> staticaly built into the kernel. In both cases I receive the same >> error :-( > > > But was linprocfs mounted as /compat/linux/proc? Yes, it was, I explicitely checked this. > >> On FreeBSD/AMD64 everything seems to build perfectly since this error >> occurs (and it seemes to be at the end of the build process): >> >> Force the Client VM when dumping the shared archive since you can't >> dump the archive with the Server VM. > > > I applied Greg Lewis' jdk15 patch he sent yesterday (at > http://lists.freebsd.org/pipermail/freebsd-java/2005-September/004329.html) > to the java/jdk15 port and I've successfully built the port on amd64 > with it today. I tried building and installing it earlier today before > I applied the patch, and it failed during the install with the "can't > dump" error... All right, this sounds to me to take a further shot. Maybe JDK is on FBSD 6/AMD64 to new and just a 'job in progress'. I will try it again. > >> I feel confused, I read about this error but no solutions or >> workaround. It confuses me a bit that I still run into harsh trouble >> although I do exactly all the steps the port repository recommends! On >> the other hand, I ran into trouble fetching some essential ports >> needed by the jdk15-build process on an AMD64 architecture, but they >> are i386 and I needed fetching them on another i386-based machine (I >> remember myself it was a XFree86 library for Linux and not available >> for amd64, but fetching ports from FreeBSD 6.0/amd64 let me get ports >> only for amd64!). > > > IIRC, I was able to fetch and install all the amd64 packages for Linux > compatibility on my new amd64 machine installed from 6.0BETA2, and the > Linux JDK worked just fine for me... I used portinstall, and I > explicitly set PACKAGESITE to retrieve the binary packages from > ftp://ftp2.freebsd.org/pub/FreeBSD/ports/amd64/packages-6-current/All... I just fetch the ports collection via cvsup and its brothers and sisters. On amd64-based hosts I very often see a set ARCH-variable and errors not being capable fetching tarballs due to be i386-tarballs. This seems to be especially for Linux files, where some '.amd64.xxx' type files are looked for. > >> Within the last 4 years I belong to the 'small' (?) group of FreeBSD >> users who never had success compiling a working JAVA environment. So >> neither OpenOffice is fully working, nor FireFox or Mozilla are >> capable of working with JAVA under FBSD 5/6. Mmmmmmhhhh ... > > I will try it again on i386 and amd64. Hope it will work then ... Thank you for your answer, Oliver From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 04:23:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12FD716A41F for ; Thu, 15 Sep 2005 04:23:47 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84CDE43D45 for ; Thu, 15 Sep 2005 04:23:46 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.10]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8F4NhMc090958 for ; Wed, 14 Sep 2005 21:23:43 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <002f01c5b9ad$415e5870$0a00a8c0@rodan> From: "Jeff D. Hamann" To: Date: Wed, 14 Sep 2005 21:23:36 -0700 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Subject: where's the cvsupfile? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 04:23:47 -0000 I've installed FreeBSD-6.0BETA4 and I'm having a bit of a time. I can't get the usb drive to mount... anywhere. The floppy drive won't mount when I type, # mount -v -t msdos /dev/fd0 /mnt so I can't even transfer files to a floppy drive to help post the error messages from the machine! I finally had to install an additional NIC (the on-board sis965L chipset -- I've verified that the device sis is in the GENERIC kernel config file, but that was just taking a guess since the sis device is ) to try to cvsup to the latest ports. There's no /etc/cvsupfile present. I would simply create one by hand, but I don't know what values to put in there now (RELEG_6 or BETA_6 or what). The machine is an asus vintage ae-1 (I'm not sure if that has anything to do with the other problems described below or not) and so far I haven't been successful in doing any of the following: 1) getting the on-board nic to light up 2) mounting a usb flash drive and now, 3) running cvsup When I created a /etc/cvsupfile by hand: bobby# cat cvsupfile *default host=cvsup5.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6 *default delete use-rel-suffix *default compress src-src ports-all doc-all bobby# my response was: bobby# /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile Parsing supfile "/etc/cvsupfile" Parse error in "/etc/cvsupfile": Missing Field value And now I'm stuck... And frustrated.... Ideas? I went to 6.0BETA4 becuase of an initial problem with getting my hard drive past the boot process (I think BSD was detecting the incorrect disk geometry?) in 5.4 and I'm starting to wonder if I sould focus on that version rather than spend more time with 6.0BETAX... Or when is the next beta release? Jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 04:50:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 074C216A41F for ; Thu, 15 Sep 2005 04:50:06 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF8F943D46 for ; Thu, 15 Sep 2005 04:50:05 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j8F4ntQV004332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 21:49:56 -0700 X-MailKey: purple frogs are falling from the sky Message-Id: <6.2.3.4.2.20050914214612.07437a30@cobalt.antimatter.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 14 Sep 2005 21:49:22 -0700 To: "Jeff D. Hamann" , From: Glenn Dawson In-Reply-To: <002f01c5b9ad$415e5870$0a00a8c0@rodan> References: <002f01c5b9ad$415e5870$0a00a8c0@rodan> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: where's the cvsupfile? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 04:50:06 -0000 At 09:23 PM 9/14/2005, Jeff D. Hamann wrote: >I've installed FreeBSD-6.0BETA4 and I'm having a bit of a time. I >can't get the usb drive to mount... anywhere. The floppy drive won't >mount when I type, > ># mount -v -t msdos /dev/fd0 /mnt > >so I can't even transfer files to a floppy drive to help post the >error messages from the machine! I finally had to install an >additional NIC (the on-board sis965L chipset -- I've verified that >the device sis is in the GENERIC kernel config file, but that was >just taking a guess since the sis device is ) to try to cvsup to the >latest ports. There's no /etc/cvsupfile present. I would simply >create one by hand, but I don't know what values to put in there now >(RELEG_6 or BETA_6 or what). The machine is an asus vintage ae-1 >(I'm not sure if that has anything to do with the other problems >described below or not) and so far I haven't been successful in >doing any of the following: > >1) getting the on-board nic to light up >2) mounting a usb flash drive > >and now, > >3) running cvsup > >When I created a /etc/cvsupfile by hand: > >bobby# cat cvsupfile >*default host=cvsup5.FreeBSD.org >*default base=/usr >*default prefix=/usr >*default release=cvs >*default tag=RELENG_6 >*default delete use-rel-suffix >*default compress >src-src There is no "src-src". Did you mean src-sys? or src-all? The sample sup files are in /usr/share/examples/cvsup >ports-all >doc-all >bobby# > >my response was: > >bobby# /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile >Parsing supfile "/etc/cvsupfile" >Parse error in "/etc/cvsupfile": Missing Field value > >And now I'm stuck... And frustrated.... > >Ideas? > >I went to 6.0BETA4 becuase of an initial problem with getting my >hard drive past the boot process (I think BSD was detecting the >incorrect disk geometry?) in 5.4 and I'm starting to wonder if I >sould focus on that version rather than spend more time with 6.0BETAX... > >Or when is the next beta release? > >Jeff. > >--- >Jeff D. Hamann >Forest Informatics, Inc. >PO Box 1421 >Corvallis, Oregon USA 97339-1421 >541-754-1428 >jeff.hamann@forestinformatics.com >www.forestinformatics.com > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 14:23:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D5CB16A41F for ; Thu, 15 Sep 2005 14:23:17 +0000 (GMT) (envelope-from wieland.k@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7451E43D45 for ; Thu, 15 Sep 2005 14:23:16 +0000 (GMT) (envelope-from wieland.k@gmail.com) Received: by xproxy.gmail.com with SMTP id i27so25865wxd for ; Thu, 15 Sep 2005 07:23:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=Y1WXjdHAa9caIcP7rgrXpA7Ijtwu3su9n53XKPqWRSOnSU9mGW2/iog+vyMSumiJXgOVQuHdZf0sijyLnXW3eObC6yUHaTqI70rw3ovJLSV1vhabW+khlU87kpnlZcQIEdm94bSxKDnby7wkaNnXpE3H9UMWG865lIwej1dBUaw= Received: by 10.70.132.13 with SMTP id f13mr408277wxd; Thu, 15 Sep 2005 07:23:15 -0700 (PDT) Received: from ?128.252.125.191? ( [128.252.125.191]) by mx.gmail.com with ESMTP id h7sm255663wxd.2005.09.15.07.23.14; Thu, 15 Sep 2005 07:23:14 -0700 (PDT) In-Reply-To: <200509131240.45207.jkim@FreeBSD.org> References: <200509131117.10960.jkim@FreeBSD.org> <777362bd663bbe40600d195b7cecf30c@wustl.edu> <200509131240.45207.jkim@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4efa8eff718166b299f7d6a317011a37@gmail.com> Content-Transfer-Encoding: 7bit From: K. Wieland Date: Thu, 15 Sep 2005 09:22:26 -0500 To: Jung-uk Kim X-Mailer: Apple Mail (2.622) Cc: freebsd-amd64@freebsd.org Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 14:23:17 -0000 Jung-uk and fellow amd64 subscribers, I tried upgrading to 6.0B4 last night, after spending several nights reading the documentation. I have been reading and am subscribed to the amd64 list, so I figure I might as well try it! First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the sysinstall that way as outlined in the docs (I don't remember where, but I can get the reference). sysinstall (v6.0 B4) would not run, complaining about some libraries not being present (I had a previous version of the libraries it was looking for, so I made sym links (bad, I know!) but it failed looking for the next library, so I deleted the symlink, and decided to reboot with the CD. I rebooted, went into fixit and did a dmesg. AGP was there, and the device /dev/agpart existed. I was happy, and decided to upgrade to 6.0 beta4 using the upgrade option in sysinstall. I didn't remember the mount points for the various file systems so I had to boot back into 5.4 and write it all down (it would be nice if this was in the documentation)! Anyway, I upgraded and rebooted. The first thing I noticed was the generic kernel detected my com port, but didn't create a /dev/cuaa0 (I dial up for internet). And, because I want sound and my TV card (bktr) I decided to customize the kernel like I had done in 5.4. So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and found that it was basically the same (MYKERNEL had the sound, bktr, and agp with several extraneous things commented out). I built the new kernel, installed it and rebooted. AGP was gone! I thought, well maybe you don't need "device agp" in the kernel (I didn't see it in the GENERIC, and agp loaded with that), so I tried that...still no AGP. Then, I decided to use the GENERIC and see if that worked---still no AGP. But, if I boot up with the CD, AGP is back! The confusing part to me is that the uname -a still gives me RELENG5.4 -p7. That seems strange to me. The ps command also didn't work as expected (just prints the headers, none of the processes). I read that if your sources don't match your kernel, you can get weird stuff like this, so I went to cvsup to the most recent. BUT, in the /usr/share/examples/standard-cvsup files it still had RELENG 5.4. I went ahead and cvsup'ed anyway. I don't have anything critical on the drive, so I am tempted to wipe it clean and reinstall (ala windows style) but I would really like to understand what is going on here. I am CCing the freebsd-amd64 list in case they have some insights, too. Thanks, Kristopher Wieland Graduate Student Washington University in St. Louis Dept. of Physics- Compton Hall On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote: > On Tuesday 13 September 2005 12:19 pm, K Wieland wrote: >> Thanks again for the quick reply. > > No problem. > >> Is there a "best method" for installing another version? I would >> rather not loose the kernel config, etc. Is it best to just wipe >> everything and start over? > > cvsup, buildworld, installworld, mergemaster... But it's quite a > hassle for new users. First of all, if the only problem for you is > the agp, try booting from the ISO, select Fixit, select CD/DVD, then > you will get shell. You can see if agp is probed/attached from > there. If that's there, you have two choices: > > 1. Upgrade. > 2. Patch kernel to add support for the AGP device. > > If you choose option 2, the only thing you really need is this: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff? > r1=1.6&r2=1.7 > > Good luck, > > JK > >> I'll give it a try and see how it goes! >> >> Kristopher >> >> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote: >>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote: >>>> Thank you for your quick reply! >>>> >>>> Yes, I am using 5.4 Release. I guess since I was just starting >>>> out with Freebsd, I'd go with "release" vs. stable or current. >>>> >>>> Do you know an ftp site for getting the images for 6.0 beta4? >>>> Or should I just cvsup to it? You can tell I am new, new new! >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/ >>> >>> JK >>> >>>> Thanks, >>>> >>>> Kristopher >>>> >>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote: >>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote: >>>>>> Hello Jung-uk! >>>>>> >>>>>> I was reading through the archives of the freebsd-amd64 >>>>>> archives (I am a new Freebsd user) and I have the exact same >>>>>> problem that you and Geneal talked about. >>>>>> >>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does >>>>>> not detect the agp, even though it is in the kernel. >>>>>> >>>>>> Did you ever get this issue resolved? >>>>> >>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It >>>>> should be fine. >>>>> >>>>> JK >>>>> >>>>>> Thank you, >>>>>> >>>>>> Kristopher Wieland > From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 15:49:05 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BC4C16A41F; Thu, 15 Sep 2005 15:49:05 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from mail.martymac.com (martymac.com [82.224.94.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA7C43D46; Thu, 15 Sep 2005 15:49:04 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from martymac.com (localhost [127.0.0.1]) by mail.martymac.com (Postfix) with ESMTP id E4FB9229; Thu, 15 Sep 2005 17:53:13 +0200 (CEST) From: "Ganael Laplanche" To: K.Wieland , Jung-uk Kim Date: Thu, 15 Sep 2005 15:53:13 +0000 Message-Id: <20050915155131.M39844@martymac.com> In-Reply-To: <4efa8eff718166b299f7d6a317011a37@gmail.com> References: <200509131117.10960.jkim@FreeBSD.org> <777362bd663bbe40600d195b7cecf30c@wustl.edu> <200509131240.45207.jkim@FreeBSD.org> <4efa8eff718166b299f7d6a317011a37@gmail.com> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 81.57.27.189 (martymac) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 15:49:05 -0000 Hi all, I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system hangs during X bootup. I had to go back to the goold old driver from 5.x :( The PR is here : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015 Any clue ? Ganaël LAPLANCHE ganael.laplanche@martymac.com http://www.martymac.com Tel : (+33)6.84.03.57.24. ---------- Original Message ----------- From: K.Wieland To: Jung-uk Kim Cc: freebsd-amd64@freebsd.org Sent: Thu, 15 Sep 2005 09:22:26 -0500 Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No > Jung-uk and fellow amd64 subscribers, > > I tried upgrading to 6.0B4 last night, after spending several nights > reading the documentation. I have been reading and am subscribed to > the amd64 list, so I figure I might as well try it! > > First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the > sysinstall that way as outlined in the docs (I don't remember where, > but I can get the reference). sysinstall (v6.0 B4) would not run, > complaining about some libraries not being present (I had a previous > version of the libraries it was looking for, so I made sym links (bad, > I know!) but it failed looking for the next library, so I deleted the > symlink, and decided to reboot with the CD. > > I rebooted, went into fixit and did a dmesg. AGP was there, and the > device /dev/agpart existed. I was happy, and decided to upgrade to > 6.0 beta4 using the upgrade option in sysinstall. I didn't remember > the mount points for the various file systems so I had to boot back > into > 5.4 and write it all down (it would be nice if this was in the > documentation)! > > Anyway, I upgraded and rebooted. The first thing I noticed was the > generic kernel detected my com port, but didn't create a /dev/cuaa0 (I > dial up for internet). And, because I want sound and my TV card > (bktr) I decided to customize the kernel like I had done in 5.4. > > So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and > found that it was basically the same (MYKERNEL had the sound, bktr, > and agp with several extraneous things commented out). I built the > new kernel, installed it and rebooted. AGP was gone! I thought, > well maybe you don't need "device agp" in the kernel (I didn't see it > in the GENERIC, and agp loaded with that), so I tried that...still no > AGP. Then, I decided to use the GENERIC and see if that worked--- > still no AGP. But, if I boot up with the CD, AGP is back! > > The confusing part to me is that the uname -a still gives me RELENG5.4 > -p7. That seems strange to me. The ps command also didn't work as > expected (just prints the headers, none of the processes). > > I read that if your sources don't match your kernel, you can get weird > stuff like this, so I went to cvsup to the most recent. BUT, in the > /usr/share/examples/standard-cvsup files it still had RELENG 5.4. I > went ahead and cvsup'ed anyway. > > I don't have anything critical on the drive, so I am tempted to wipe > it clean and reinstall (ala windows style) but I would really like to > understand what is going on here. > > I am CCing the freebsd-amd64 list in case they have some insights, too. > > Thanks, > > Kristopher Wieland > Graduate Student > Washington University in St. Louis > Dept. of Physics- Compton Hall > On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote: > > > On Tuesday 13 September 2005 12:19 pm, K Wieland wrote: > >> Thanks again for the quick reply. > > > > No problem. > > > >> Is there a "best method" for installing another version? I would > >> rather not loose the kernel config, etc. Is it best to just wipe > >> everything and start over? > > > > cvsup, buildworld, installworld, mergemaster... But it's quite a > > hassle for new users. First of all, if the only problem for you is > > the agp, try booting from the ISO, select Fixit, select CD/DVD, then > > you will get shell. You can see if agp is probed/attached from > > there. If that's there, you have two choices: > > > > 1. Upgrade. > > 2. Patch kernel to add support for the AGP device. > > > > If you choose option 2, the only thing you really need is this: > > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff? > > r1=1.6&r2=1.7 > > > > Good luck, > > > > JK > > > >> I'll give it a try and see how it goes! > >> > >> Kristopher > >> > >> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote: > >>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote: > >>>> Thank you for your quick reply! > >>>> > >>>> Yes, I am using 5.4 Release. I guess since I was just starting > >>>> out with Freebsd, I'd go with "release" vs. stable or current. > >>>> > >>>> Do you know an ftp site for getting the images for 6.0 beta4? > >>>> Or should I just cvsup to it? You can tell I am new, new new! > >>> > >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/ > >>> > >>> JK > >>> > >>>> Thanks, > >>>> > >>>> Kristopher > >>>> > >>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote: > >>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote: > >>>>>> Hello Jung-uk! > >>>>>> > >>>>>> I was reading through the archives of the freebsd-amd64 > >>>>>> archives (I am a new Freebsd user) and I have the exact same > >>>>>> problem that you and Geneal talked about. > >>>>>> > >>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does > >>>>>> not detect the agp, even though it is in the kernel. > >>>>>> > >>>>>> Did you ever get this issue resolved? > >>>>> > >>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It > >>>>> should be fine. > >>>>> > >>>>> JK > >>>>> > >>>>>> Thank you, > >>>>>> > >>>>>> Kristopher Wieland > > > > _______________________________________________ > 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" ------- End of Original Message ------- From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 16:20:14 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F93D16A41F for ; Thu, 15 Sep 2005 16:20:14 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E4E43D53 for ; Thu, 15 Sep 2005 16:20:13 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j8FGPq1p011304; Thu, 15 Sep 2005 12:25:52 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "Ganael Laplanche" Date: Thu, 15 Sep 2005 12:19:53 -0400 User-Agent: KMail/1.6.2 References: <4efa8eff718166b299f7d6a317011a37@gmail.com> <20050915155131.M39844@martymac.com> In-Reply-To: <20050915155131.M39844@martymac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <200509151219.55989.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/1082/Wed Sep 14 11:22:17 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-amd64@FreeBSD.org, "K.Wieland" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 16:20:14 -0000 On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote: > Hi all, > > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system > hangs during X bootup. I had to go back to the goold old driver > from 5.x :( The 'good old' driver uses generic nForce AGP interface. If the driver really works, I will be surprised. I admit agp_amd64.c requires more work (esp. chipset-specific handling including nForce) but I had no time/hardware. Anyway you have to make sure agp(4) really works for you. http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim > The PR is here : > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015 > > Any clue ? Have you tried xorg-server-snap? If it doesn't work, can you try this? http://people.freebsd.org/~jkim/xorg-server-snap.diff Thanks, Jung-uk Kim > Gana�l LAPLANCHE > ganael.laplanche@martymac.com > http://www.martymac.com > Tel : (+33)6.84.03.57.24. From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 16:28:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A326316A41F for ; Thu, 15 Sep 2005 16:28:42 +0000 (GMT) (envelope-from ebola@psychoholics.org) Received: from mail.psychoholics.org (www.psychoholics.org [64.185.102.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4142743D46 for ; Thu, 15 Sep 2005 16:28:41 +0000 (GMT) (envelope-from ebola@psychoholics.org) Received: from S0106c0ffeec0ffee.su.shawcable.net (S0106c0ffeec0ffee.su.shawcable.net [24.109.19.58]) by mail.psychoholics.org (Postfix) with ESMTP id 21C99157173; Thu, 15 Sep 2005 10:29:23 -0700 (PDT) From: Adam Gregoire To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Thu, 15 Sep 2005 12:29:37 -0400 Message-Id: <1126801777.7412.7.camel@S0106c0ffeec0ffee.su.shawcable.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "K.Wieland" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 16:28:42 -0000 Hello, this chipset is not supported for agpgart, the nforce3 250 chipset has the code needed to detect the gart but is missing functionality needed for proper operation. See also, PR amd64/71753 and the following thread http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html Regards, -- Adam Gregoire From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 17:19:06 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EADD16A41F; Thu, 15 Sep 2005 17:19:06 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A2B043D46; Thu, 15 Sep 2005 17:19:05 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j8FHJ5iR034873; Thu, 15 Sep 2005 10:19:05 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j8FHJ4JM034872; Thu, 15 Sep 2005 10:19:04 -0700 (PDT) (envelope-from jmg) Date: Thu, 15 Sep 2005 10:19:04 -0700 From: John-Mark Gurney To: "K. Wieland" Message-ID: <20050915171904.GT793@funkthat.com> Mail-Followup-To: "K. Wieland" , Jung-uk Kim , freebsd-amd64@freebsd.org References: <200509131117.10960.jkim@FreeBSD.org> <777362bd663bbe40600d195b7cecf30c@wustl.edu> <200509131240.45207.jkim@FreeBSD.org> <4efa8eff718166b299f7d6a317011a37@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4efa8eff718166b299f7d6a317011a37@gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-amd64@FreeBSD.org, Jung-uk Kim Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 17:19:06 -0000 K. Wieland wrote this message on Thu, Sep 15, 2005 at 09:22 -0500: > Anyway, I upgraded and rebooted. The first thing I noticed was the > generic kernel detected my com port, but didn't create a /dev/cuaa0 (I > dial up for internet). And, because I want sound and my TV card (bktr) > I decided to customize the kernel like I had done in 5.4. These have been renamed to match the tty versions.. look for /dev/cuad0 instead... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 17:27:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A25B316A41F; Thu, 15 Sep 2005 17:27:29 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF1243D48; Thu, 15 Sep 2005 17:27:28 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.10]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8FHRNMc092779; Thu, 15 Sep 2005 10:27:25 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <001d01c5ba1a$bc83fdd0$0a00a8c0@rodan> From: "Jeff D. Hamann" To: , Date: Thu, 15 Sep 2005 10:27:16 -0700 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Cc: Subject: building/porting linux SIS965L driver X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 17:27:29 -0000 I'm building (or trying to build) an amd64 FreeBSD machine to replace my FreeBSD 4.4 server. I purchased an ASUS Vintage-AE1 MB that uses the following chipsets: Northbridge: SiS760GX Southbridge: SiS965L I've not been able to get the on-board NIC to light up, so I purchased another NIC which works alright. It's bothering me too much that the chipset isn't supported (http://www.freebsd.org/platforms/amd64/motherboards.html) but many of the other ASUS MB chipsets are. This seems like a great machine and I suspect there are plenty more machines that will be using this barebones box as a starting place (of course, I'll be wrong in a year anyways). I've found the linux driver for the on-board NIC and since I've never ported a driver for FreeBSD, I'm trying to figure out how much work it will be to port the driver to FreeBSD-6.0? I've snooped around in the /usr/src/sys/pci/if_sis.c /usr/src/sys/pci/if_sisreg.h 6.0Beta4 files to simply examine the bsd code. To my novice eyes, the files look completely different from the linux drivers and I'm not sure I can takle this myself since I've never done anything like this. Can someone help me through this process, or is this not worth the trouble? Jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 19:41:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E227916A41F for ; Thu, 15 Sep 2005 19:41:50 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9993243D55 for ; Thu, 15 Sep 2005 19:41:41 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.10]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8FJfXMc093081 for ; Thu, 15 Sep 2005 12:41:35 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> From: "Jeff D. Hamann" To: Date: Thu, 15 Sep 2005 12:41:18 -0700 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Subject: acpi/ohci/rsdt wtf? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 19:41:51 -0000 I'm curious what the acpi_perf0: invalid _PSS package messages are all about and why there are so many? I'm also curious about the EHCI stuff. My bios has some settings which state: "stop ehci in ohci handler handover" the comments for the setting stats: "stops the ehci host controller during ohci handvoer call. the is needed for installing Oses that does not support ehci host controllers" and I'm not sure what it means and I don't know if FreeBSD-6beta4 supports it. Also, there's another setting about "acpi apic support" where the hint states: "include acpi apic table pointer to rsdt pointer list" Wha? I've included my dmesg output for diagnostics. $ dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-BETA4 #1: Fri Sep 16 06:41:12 PDT 2005 root@bobby.forestinformatics.com:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1995.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1039400960 (991 MB) avail memory = 991444992 (945 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 0 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 5 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: irq 5 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.5 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 2.7 (no driver attached) ohci0: mem 0xfbefc000-0xfbefcfff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfbefd000-0xfbefdfff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xfbefe000-0xfbefefff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfbeff000-0xfbefffff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered pci0: at device 4.0 (no driver attached) pcib2: at device 6.0 on pci0 pci2: on pcib2 pcib3: at device 7.0 on pci0 pci3: on pcib3 rl0: port 0xa800-0xa8ff mem 0xfbefb800-0xfbefb8ff irq 17 at device 10.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:11:95:24:60:b3 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1995008941 Hz quality 800 Timecounters tick every 1.000 msec ad0: 190782MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA66 Trying to mount root from ufs:/dev/ad0s1a $ jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 19:59:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E416816A420 for ; Thu, 15 Sep 2005 19:59:48 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30FE843D60 for ; Thu, 15 Sep 2005 19:59:47 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.233] (Not Verified[10.50.41.233]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Thu, 15 Sep 2005 16:15:27 -0400 From: John Baldwin To: freebsd-amd64@freebsd.org, "Jeff D. Hamann" Date: Thu, 15 Sep 2005 16:00:49 -0400 User-Agent: KMail/1.8 References: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> In-Reply-To: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509151600.50793.jhb@FreeBSD.org> Cc: Subject: Re: acpi/ohci/rsdt wtf? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 19:59:49 -0000 On Thursday 15 September 2005 03:41 pm, Jeff D. Hamann wrote: > I'm curious what the > > acpi_perf0: invalid _PSS package > > messages are all about and why there are so many? I'm also curious about > the EHCI stuff. My bios has some settings which state: > > "stop ehci in ohci handler handover" > > the comments for the setting stats: > > "stops the ehci host controller during ohci handvoer call. the is needed > for installing Oses that does not support ehci host controllers" Leave it off. FreeBSD 6 includes the ehci(4) driver by default as you can see in your dmesg. > and I'm not sure what it means and I don't know if FreeBSD-6beta4 supports > it. > > Also, there's another setting about "acpi apic support" where the hint > states: > > "include acpi apic table pointer to rsdt pointer list" > > Wha? Leave that on. It looks like it already is. Having this on is what let's us find the ACPI APIC Table as mentioned here: > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 15 23:57:41 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D3616A41F for ; Thu, 15 Sep 2005 23:57:41 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C8D43D46 for ; Thu, 15 Sep 2005 23:57:40 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j8G03LJo025834 for ; Thu, 15 Sep 2005 20:03:21 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-amd64@FreeBSD.org Date: Thu, 15 Sep 2005 19:57:04 -0400 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200509151957.24837.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/1082/Wed Sep 14 11:22:17 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: [PATCH] agp(4) for ULi M1689/nVidia nForce3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 23:57:41 -0000 If you have any of these, please test and let me know. http://people.freebsd.org/~jkim/agp_amd64.diff FYI, agp(4) GART test is here: http://people.freebsd.org/~jkim/testgart.c Thanks, Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 03:50:09 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AFE416A41F for ; Fri, 16 Sep 2005 03:50:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C9643D46 for ; Fri, 16 Sep 2005 03:50:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8G3o84C029824 for ; Fri, 16 Sep 2005 03:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8G3o8W0029823; Fri, 16 Sep 2005 03:50:08 GMT (envelope-from gnats) Resent-Date: Fri, 16 Sep 2005 03:50:08 GMT Resent-Message-Id: <200509160350.j8G3o8W0029823@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, Mike Smith Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9271B16A41F for ; Fri, 16 Sep 2005 03:48:18 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D83243D46 for ; Fri, 16 Sep 2005 03:48:18 +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 j8G3mIJt015715 for ; Fri, 16 Sep 2005 03:48:18 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j8G3mIH5015714; Fri, 16 Sep 2005 03:48:18 GMT (envelope-from nobody) Message-Id: <200509160348.j8G3mIH5015714@www.freebsd.org> Date: Fri, 16 Sep 2005 03:48:18 GMT From: Mike Smith To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/86199: Missed AMD64 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 03:50:09 -0000 >Number: 86199 >Category: amd64 >Synopsis: Missed AMD64 motherboard >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 16 03:50:08 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Mike Smith >Release: FreeBSD 5.4-STABLE >Organization: none >Environment: FreeBSD insomnia.localnet.net 5.4-STABLE FreeBSD 5.4-STABLE #5: Thu Sep 15 15:24:53 CDT 2005 perlfu@insomnia.localnet.net:/usr/obj/usr/src/sys/INSOMNIA amd64 >Description: MSI K8M NEO-V is not listed in the section covering amd64 compatible motherboards. Also there seems to be a lack of support for the VT8237 SATA Raid controller. I can use the drive, but there seems to be some shaky behavior coming from it. I've seen random kernel panics related to the drive, (don't have them to paste currently, but if you give me some time I'm sure it will randomly pop up some time soon). It also defers for background fsck'ing even if the drives were properly unmounted. The onboard sound also results in hard locks, randomly, especially when vchans are enabled. I'm using the VT8237 Audio as well. Any help with this would be greatly appreciated. >How-To-Repeat: Errors occur fairly randomly, and present themselves in different manners each time. The drive can do everything from cause a panic, (same one each time, seems to indicate inconsistancies on the drive). Also shows itself by constantly appearing as improperly dismounted, even when shutdown, or reboot was called. Sound causes hard locks quite frequently and randomly as far as I can tell. It only hard locks when I try to play multiple sounds at once. Have tried with and without hw.snd.maxautovchans=4, tried a few of the patches that came out on the lists to no avail, no error messages, or logs can be found with anything pertaining to the sound issue, apparently it is generally a 100% hard lock, keyboard failure and all. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 05:50:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A1D16A41F for ; Fri, 16 Sep 2005 05:50:10 +0000 (GMT) (envelope-from pierg75@yahoo.it) Received: from host130-93.pool8019.interbusiness.it (host130-93.pool8019.interbusiness.it [80.19.93.130]) by mx1.FreeBSD.org (Postfix) with SMTP id B96E143D46 for ; Fri, 16 Sep 2005 05:50:09 +0000 (GMT) (envelope-from pierg75@yahoo.it) Message-ID: <432A5EEC.9020202@yahoo.it> Date: Fri, 16 Sep 2005 07:58:04 +0200 From: pier MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6949FBFCF16651EA77EDC791" Subject: Problem with hp zv6000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 05:50:10 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6949FBFCF16651EA77EDC791 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hi all. I'm having so many troubles that i have almost gave up to install FreeBSD on this notebook (amd64 3500+, chipset ATI Xpress200). I tried all the releases, from 5.3 to 6.0-BETA4 but no one works. I read something here that could be interesting: http://forums.bit-tech.net/showthread.php?t=94652 I tried to look for this functions in the code, but it looks like in the new releases they don't exist. So...now i can boot with the kernel installed with this personalized boot-cd (http://blackk.union.edu/~black/freebsd/5_3_30Dec2004-amd64-miniinst.iso) but i can't update my kernel with a newer one. What can I do? Thank you Pier --------------enig6949FBFCF16651EA77EDC791 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDKl7x0EvuLV/O0yoRAnhSAKDv1it/9rdEK62/rxWQlCSF/eGw3gCfZMv1 YttTfV6EAw+hdr5Ejd5lEcA= =u1df -----END PGP SIGNATURE----- --------------enig6949FBFCF16651EA77EDC791-- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 08:00:22 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E8EC16A41F; Fri, 16 Sep 2005 08:00:22 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from mail.martymac.com (martymac.com [82.224.94.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03A2D43D49; Fri, 16 Sep 2005 08:00:19 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from martymac.com (localhost [127.0.0.1]) by mail.martymac.com (Postfix) with ESMTP id DF012229; Fri, 16 Sep 2005 10:04:28 +0200 (CEST) From: "Ganael Laplanche" To: Jung-uk Kim Date: Fri, 16 Sep 2005 08:04:28 +0000 Message-Id: <20050916080048.M77239@martymac.com> In-Reply-To: <200509151219.55989.jkim@FreeBSD.org> References: <4efa8eff718166b299f7d6a317011a37@gmail.com> <20050915155131.M39844@martymac.com> <200509151219.55989.jkim@FreeBSD.org> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 81.57.27.189 (martymac) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: freebsd-amd64@FreeBSD.org, "K.Wieland" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 08:00:22 -0000 > On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote: > > Hi all, > > > > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system > > hangs during X bootup. I had to go back to the goold old driver > > from 5.x :( > > The 'good old' driver uses generic nForce AGP interface. If the > driver really works, I will be surprised. I admit agp_amd64.c > requires more work (esp. chipset-specific handling including nForce) > but I had no time/hardware. > > Anyway you have to make sure agp(4) really works for you. > Hi again, No, I have no agp support, but using the old driver allows me to start X... I remember using the new driver made a /dev/agpgart appear, but the system crashes at X startup... > http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim > > > The PR is here : > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015 > > > > Any clue ? > > Have you tried xorg-server-snap? If it doesn't work, can you try > this? No, I didn't, but I think I'll have the same pb since agp code for nforce3-250 is not correct in the kernel :( > http://people.freebsd.org/~jkim/xorg-server-snap.diff > > Thanks, Thanks to you, Regards, Ganael. > Jung-uk Kim > > > [UTF-8?]Gana�l LAPLANCHE > > ganael.laplanche@martymac.com > > http://www.martymac.com > > Tel : (+33)6.84.03.57.24. ------- End of Original Message ------- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 08:04:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 441C316A41F for ; Fri, 16 Sep 2005 08:04:45 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from mail.martymac.com (martymac.com [82.224.94.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D349C43D45 for ; Fri, 16 Sep 2005 08:04:44 +0000 (GMT) (envelope-from ganael.laplanche@martymac.com) Received: from martymac.com (localhost [127.0.0.1]) by mail.martymac.com (Postfix) with ESMTP id 36791229; Fri, 16 Sep 2005 10:08:54 +0200 (CEST) From: "Ganael Laplanche" To: Adam Gregoire , freebsd-amd64@freebsd.org Date: Fri, 16 Sep 2005 08:08:54 +0000 Message-Id: <20050916080443.M8613@martymac.com> In-Reply-To: <1126801777.7412.7.camel@S0106c0ffeec0ffee.su.shawcable.net> References: <1126801777.7412.7.camel@S0106c0ffeec0ffee.su.shawcable.net> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 81.57.27.189 (martymac) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: "K.Wieland" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 08:04:45 -0000 > Hello, this chipset is not supported for agpgart, the nforce3 250 > chipset has the code needed to detect the gart but is missing > functionality needed for proper operation. > > See also, PR amd64/71753 and the following thread > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html I'm the author of this post... I tried to write a small patch to see what's happening with it, but it made my system hang as described here http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004315.html ! And It looks like this code has been included in the 6-0 branch :(, that's why you should use the old 5.x drivers... > Regards, > > -- > Adam Gregoire > > _______________________________________________ > 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" ------- End of Original Message ------- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 09:37:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 919DF16A41F for ; Fri, 16 Sep 2005 09:37:21 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F24143D45 for ; Fri, 16 Sep 2005 09:37:20 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.12.10/5.2) with ESMTP id j8G9bEBR014802 for ; Fri, 16 Sep 2005 11:37:15 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Fri, 16 Sep 2005 11:37:14 +0200 User-Agent: KMail/1.8.91 References: <200509160348.j8G3mIH5015714@www.freebsd.org> In-Reply-To: <200509160348.j8G3mIH5015714@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509161137.14570.groot@kde.org> X-Spam-Score: -1.399 () BAYES_00,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Subject: Re: amd64/86199: Missed AMD64 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 09:37:21 -0000 On Friday 16 September 2005 05:48, Mike Smith wrote: > MSI K8M NEO-V is not listed in the section covering amd64 compatible > motherboards. That's one issue, which should be PR-ed as described on the motherboards page. > Also there seems to be a lack of support for the VT8237 SATA > Raid controller. Er, you mean atapci1@pci0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 VT6410 SATA RAID Controller' class = mass storage subclass = RAID That one? It works just fine on Asus & Gigabyte boards. > onboard sound also results in hard locks, randomly, especially when vchans > are enabled. I'm using the VT8237 Audio as well. Any help with this would > be greatly appreciated. I've managed to lock my Asus board once with mpg123 foo.mp3 & mpg123 foo.mp3, but sound in general is fine as well. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 10:13:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 628E216A41F for ; Fri, 16 Sep 2005 10:13:22 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1224443D49 for ; Fri, 16 Sep 2005 10:13:22 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EGDDF-0007d3-00; Fri, 16 Sep 2005 12:12:57 +0200 Date: Fri, 16 Sep 2005 12:12:57 +0200 To: "Jeff D. Hamann" Message-ID: <20050916101257.GA12562@poupinou.org> References: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-amd64@freebsd.org Subject: Re: acpi/ohci/rsdt wtf? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 10:13:22 -0000 On Thu, Sep 15, 2005 at 12:41:18PM -0700, Jeff D. Hamann wrote: > I'm curious what the > > acpi_perf0: invalid _PSS package > > messages are all about and why there are so many? Could you send to me the output from acpidump -dt It's rather large. Please send it to me privately or better provide some link. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 10:16:40 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DD8A16A41F for ; Fri, 16 Sep 2005 10:16:40 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id D279643D4C for ; Fri, 16 Sep 2005 10:16:39 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 799EA4C970; Fri, 16 Sep 2005 10:17:17 +0000 (GMT) Received: from [192.168.46.52] (ppp166-27.static.internode.on.net [150.101.166.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id B28264C969; Fri, 16 Sep 2005 10:17:14 +0000 (GMT) Message-ID: <432A9B78.8020906@roq.com> Date: Fri, 16 Sep 2005 20:16:24 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.11) Gecko/20050907 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4324E06A.4090400@roq.com> <20050912054858.GA28647@xor.obsecurity.org> <432567EF.2060800@roq.com> In-Reply-To: <432567EF.2060800@roq.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@FreeBSD.org, Kris Kennaway Subject: Re: FAST_IPSEC on EMT64 / AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 10:16:40 -0000 Michael VInce wrote: > Bjoern A. Zeeb wrote: > >> On Mon, 12 Sep 2005, Kris Kennaway wrote: >> >> >> >>> On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote: >>> >>> >>>> Hi guys, >>>> I am getting a Intel Xeon based EMT64 server as a gateway that may in >>>> the future do some VPN, >>>> I wondered if the EMT64 servers could run FAST_IPSEC under AMD64 >>>> FreeBSD. >>>> With these options below compiled into the kernel I was able to boot >>>> FreeBSD with no panics if I booted into single user mode and then just >>>> did 'exit' to go back to regular boot, otherwise it would panic as if >>>> it was an AMD64 CPU. >>>> >>> >>> You forgot to include details of the panic. >>> >> >> >> That would be really good to know. >> >> Then we'd finally know more than was given in >> http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211 >> >> > > Sorry instead of getting a core dump I grabbed a FreeBSD AMD64 beta4 > 6.0 ISO and put it on this server. > But I do have some good news in what I found. > Recompiled FAST_IPSEC into the kernel and rebooted it, it came up fine.. > So then put in some ipsec security policies into /etc/ipsec.conf > ipsec_enable="YES" > and ran /etc/rc.d/ipsec start > and it ran fine. > I then installed ipsec-tools and loaded up the racoon daemon this also > triggers a panic on my FreeBSD AMD64 6.0 laptop with out FAST_IPSEC > being compiled into the kernel and its loaded up fine. > This looks all completely solid. I haven't been able to panic the > server with a full VPN configuration activated. > The only thing I haven't done is tested if the IPSEC VPN actually can > work. > > This is no mistake this is AMD64 kernel FreeBSD with FAST_IPSEC I just > cheated using the Intel EMT64 > > Regards, > Mike > > beast# /sbin/sysctl -a | grep ipsec > ipsecpolicy 16 4K - 520 256 > ipsecrequest 2 1K - 4 256 > ipsec-reg 3 1K - 24 32 > net.inet.ipsec.def_policy: 1 > net.inet.ipsec.esp_trans_deflev: 1 > net.inet.ipsec.esp_net_deflev: 1 > net.inet.ipsec.ah_trans_deflev: 1 > net.inet.ipsec.ah_net_deflev: 1 > net.inet.ipsec.ah_cleartos: 1 > net.inet.ipsec.ah_offsetmask: 0 > net.inet.ipsec.dfbit: 0 > net.inet.ipsec.ecn: 0 > net.inet.ipsec.debug: 0 > net.inet.ipsec.esp_randpad: -1 > net.inet.ipsec.crypto_support: 0 > net.inet6.ipsec6.def_policy: 1 > net.inet6.ipsec6.esp_trans_deflev: 1 > net.inet6.ipsec6.esp_net_deflev: 1 > net.inet6.ipsec6.ah_trans_deflev: 1 > net.inet6.ipsec6.ah_net_deflev: 1 > net.inet6.ipsec6.ecn: 0 > net.inet6.ipsec6.debug: 0 > net.inet6.ipsec6.esp_randpad: -1 > beast# uname -a > FreeBSD beast 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Mon Sep 12 20:40:05 UTC > 2005 root@beast:/usr/obj/usr/src/sys/GENERIC_IPSEC amd64 > > _______________________________________________ > 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" I am back, I still would like to see this bug fixed (and I assume other people do as well :) The server in my above email appears to be working fine using FAST_IPSEC on AMD64 is a Dell 2850 (Beast) But on a Dell 1850 it crashes as usual, here is a dump on AMD64 6.0 Beta4 cvsuped from beta3 ISO install. I still don't know why it appears to be working fine on a 2850 but not on any other machine in the world? This machine below is a Dell 1850 EMT64 with FAST_IPSEC compiled into it with some rules in /etc/ipsec.conf I can get panics from starting ipsec or starting racoon ipsec-tools. The I have listed 2 dumps here the first one is from racoon and the one below is from setkey ( starting ipsec ) I don't really know much about doing this stuff so I have just run some of the commands in the kernel debug handbook example. This dump was triggered from starting racoon. This is from a usb2serial console output from the server. cd /usr/obj/usr/src/sys/GENERIC_IPSEC/ tank# kgdb kernel.debug /usr/crash/vmcore.7 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: 0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 591 (racoon) panic: from debugger cpuid = 0 Uptime: 4m23s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list 167 static __inline struct thread * 168 __curthread(void) 169 { 170 struct thread *td; 171 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); 173 return (td); 174 } 175 #define curthread (__curthread()) 176 (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0xffffffff803b8ccc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xffffffff803b876b in panic (fmt=0xffffffff805faac2 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xffffffff801aa1c2 in db_panic (addr=0, have_addr=0, count=0, modif=0x0) at /usr/src/sys/ddb/db_command.c:435 #4 0xffffffff801aa705 in db_command_loop () at /usr/src/sys/ddb/db_command.c:349 #5 0xffffffff801ac573 in db_trap (type=-1270872608, code=0) at /usr/src/sys/ddb/db_main.c:221 #6 0xffffffff803d5799 in kdb_trap (type=12, code=0, tf=0xffffffffb44007a0) at /usr/src/sys/kern/subr_kdb.c:473 #7 0xffffffff8059bf0e in trap_fatal (frame=0xffffffffb44007a0, eva=18446742975788145024) at /usr/src/sys/amd64/amd64/trap.c:656 #8 0xffffffff8059c2a3 in trap_pfault (frame=0xffffffffb44007a0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:581 #9 0xffffffff8059c4b9 in trap (frame= {tf_rdi = -2140943745, tf_rsi = 256, tf_rdx = -1270871712, tf_rcx = -2142535110, tf_r8 = 64, tf_r9 = -1097921406592, tf_rax = 0, tf_rbx = 2152432187, tf_rbp = -1270871728, tf_r10 = -2139154144, tf_r11 = -1270871552, tf_r12 = 57, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = -3413406822, tf_flags = -2140901446, tf_err = 0, tf_rip = -2142535096, tf_cs = 8, tf_rflags = 66178, tf_rsp = -1270871968, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:360 #10 0xffffffff80589dfb in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #11 0xffffffff8063ca7f in wi_pccard_products () #12 0x0000000000000100 in ?? () #13 0xffffffffb4400960 in ?? () #14 0xffffffff804b823a in kdebug_mbuf (m0=0x0) at /usr/src/sys/netipsec/key_debug.c:670 #15 0xffffffff80442d60 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/net/raw_usrreq.c:263 #16 0xffffffff804b8d2a in key_send (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/netipsec/keysock.c:532 #17 0xffffffff803fdde4 in sosend (so=0xffffff005f41dc08, addr=0x0, uio=0xffffffffb4400a80, top=0xffffff006076e700, control=0x0, flags=0, td=0xffffff005ec8d980) at /usr/src/sys/kern/uipc_socket.c:829 #18 0xffffffff80404d54 in kern_sendit (td=0xffffff005ec8d980, s=5, mp=0xffffffffb4400b50, flags=0, control=0x0, segflg=16) at /usr/src/sys/kern/uipc_syscalls.c:772 #19 0xffffffff80405f16 in sendit (td=0xffffff005ec8d980, s=5, mp=0xffffffffb4400b50, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:712 #20 0xffffffff804062d4 in sendto (td=0x0, uap=0x0) at /usr/src/sys/kern/uipc_syscalls.c:830 #21 0xffffffff8059cc72 in syscall (frame= {tf_rdi = 5, tf_rsi = 5677936, tf_rdx = 16, tf_rcx = 0, tf_r8 = 0, tf_r9 = 0, tf_rax = 133, tf_rbx = 5677952, tf_rbp = 2, tf_r10 = 4, tf_r11 = 582, tf_r12 = 5677936, tf_r13 = 7, tf_r14 = 5, tf_r15 = 0, tf_trapno = 12, tf_addr = 4292816, tf_flags = 0, tf_err = 2, tf_rip = 34372796060, tf_cs = 43, tf_rflags = 582, tf_rsp = 140737488349928, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:797 #22 0xffffffff80589f98 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #23 0x0000000000000005 in ?? () #24 0x000000000056a370 in ?? () #25 0x0000000000000010 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000085 in ?? () #30 0x000000000056a380 in ?? () #31 0x0000000000000002 in ?? () #32 0x0000000000000004 in ?? () #33 0x0000000000000246 in ?? () #34 0x000000000056a370 in ?? () #35 0x0000000000000007 in ?? () #36 0x0000000000000005 in ?? () #37 0x0000000000000000 in ?? () #38 0x000000000000000c in ?? () #39 0x00000000004180d0 in ?? () #40 0x0000000000000000 in ?? () #41 0x0000000000000002 in ?? () #42 0x0000000800c73e9c in ?? () #43 0x000000000000002b in ?? () #44 0x0000000000000246 in ?? () #45 0x00007fffffffeae8 in ?? () #46 0x0000000000000023 in ?? () #47 0x00007fffffff5b50 in ?? () #48 0x0000000000000023 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x000000005f4dd000 in ?? () #58 0x0000000000000001 in ?? () #59 0x0000000000000000 in ?? () #60 0xffffff005e696340 in ?? () #61 0xffffff007b9b74c0 in ?? () #62 0xffffffffb4400260 in ?? () #63 0xffffffffb4400238 in ?? () #64 0xffffff005ec8d980 in ?? () #65 0xffffffff803cd10a in sched_switch (td=0x56a380, newtd=0x56a370, flags=5) at /usr/src/sys/kern/sched_4bsd.c:973 Previous frame inner to this frame (corrupt stack?) Here is the serial console output from doing '/etc/rc.d/ipsec start' with some rules in /etc/ipsec.conf Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xffffffff3489ab9a fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff804b8248 stack pointer = 0x10:0xffffffffb43e2850 frame pointer = 0x10:0xffffffffb43e2950 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 615 (setkey) [thread pid 615 tid 100159 ] Stopped at kdebug_mbuf+0x88: db> panic panic: from debugger cpuid = 0 Uptime: 14m39s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 16k Dump complete tank# kgdb kernel.debug /usr/crash/vmcore.8 kgdb kernel.debug /usr/crash/vmcore.8 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: fff804b8248 stack pointer = 0x10:0xffffffffb43e2850 frame pointer = 0x10:0xffffffffb43e2950 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 615 (setkey) panic: from debugger cpuid = 0 Uptime: 14m39s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list 167 static __inline struct thread * 168 __curthread(void) 169 { 170 struct thread *td; 171 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); 173 return (td); 174 } 175 #define curthread (__curthread()) 176 (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0xffffffff803b8ccc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xffffffff803b876b in panic (fmt=0xffffffff805faac2 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xffffffff801aa1c2 in db_panic (addr=0, have_addr=0, count=0, modif=0x0) at /usr/src/sys/ddb/db_command.c:435 #4 0xffffffff801aa705 in db_command_loop () at /usr/src/sys/ddb/db_command.c:349 #5 0xffffffff801ac573 in db_trap (type=-1270995488, code=0) at /usr/src/sys/ddb/db_main.c:221 #6 0xffffffff803d5799 in kdb_trap (type=12, code=0, tf=0xffffffffb43e27a0) at /usr/src/sys/kern/subr_kdb.c:473 #7 0xffffffff8059bf0e in trap_fatal (frame=0xffffffffb43e27a0, eva=18446742975772514688) at /usr/src/sys/amd64/amd64/trap.c:656 #8 0xffffffff8059c2a3 in trap_pfault (frame=0xffffffffb43e27a0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:581 #9 0xffffffff8059c4b9 in trap (frame= {tf_rdi = -2140943745, tf_rsi = 256, tf_rdx = -1270994592, tf_rcx = -2142535110, tf_r8 = 64, tf_r9 = -1097937036928, tf_rax = 0, tf_rbx = 2152432187, tf_rbp = -1270994608, tf_r10 = -2139154144, tf_r11 = -1270994432, tf_r12 = 57, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = -3413529702, tf_flags = -2140901446, tf_err = 0, tf_rip = -2142535096, tf_cs = 8, tf_rflags = 66178, tf_rsp = -1270994848, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:360 #10 0xffffffff80589dfb in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #11 0xffffffff8063ca7f in wi_pccard_products () #12 0x0000000000000100 in ?? () #13 0xffffffffb43e2960 in ?? () #14 0xffffffff804b823a in kdebug_mbuf (m0=0x0) at /usr/src/sys/netipsec/key_debug.c:670 #15 0xffffffff80442d60 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/net/raw_usrreq.c:263 #16 0xffffffff804b8d2a in key_send (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/netipsec/keysock.c:532 #17 0xffffffff803fdde4 in sosend (so=0xffffff005ef219a0, addr=0x0, uio=0xffffffffb43e2a80, top=0xffffff00608a0e00, control=0x0, flags=0, td=0xffffff005dda5980) at /usr/src/sys/kern/uipc_socket.c:829 #18 0xffffffff80404d54 in kern_sendit (td=0xffffff005dda5980, s=4, mp=0xffffffffb43e2b50, flags=0, control=0x0, segflg=16) at /usr/src/sys/kern/uipc_syscalls.c:772 #19 0xffffffff80405f16 in sendit (td=0xffffff005dda5980, s=4, mp=0xffffffffb43e2b50, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:712 #20 0xffffffff804062d4 in sendto (td=0x0, uap=0x0) at /usr/src/sys/kern/uipc_syscalls.c:830 #21 0xffffffff8059cc72 in syscall (frame= {tf_rdi = 4, tf_rsi = 5320768, tf_rdx = 16, tf_rcx = 0, tf_r8 = 0, tf_r9 = 0, tf_rax = 133, tf_rbx = 5320784, tf_rbp = 0, tf_r10 = 4, tf_r11 = 5320704, tf_r12 = 5320768, tf_r13 = 7, tf_r14 = 4, tf_r15 = 0, tf_trapno = 12, tf_addr = 5320704, tf_flags = 0, tf_err = 2, tf_rip = 34367663772, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488349848, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:797 #22 0xffffffff80589f98 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #23 0x0000000000000004 in ?? () #24 0x0000000000513040 in ?? () #25 0x0000000000000010 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000085 in ?? () #30 0x0000000000513050 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000004 in ?? () #33 0x0000000000513000 in ?? () #34 0x0000000000513040 in ?? () #35 0x0000000000000007 in ?? () #36 0x0000000000000004 in ?? () #37 0x0000000000000000 in ?? () #38 0x000000000000000c in ?? () #39 0x0000000000513000 in ?? () #40 0x0000000000000000 in ?? () ---Type to continue, or q to quit--- #41 0x0000000000000002 in ?? () #42 0x000000080078ee9c in ?? () #43 0x000000000000002b in ?? () #44 0x0000000000000202 in ?? () #45 0x00007fffffffea98 in ?? () #46 0x0000000000000023 in ?? () #47 0x00007fffffffd4d8 in ?? () #48 0x0000000000000023 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x000000005f9ba000 in ?? () #58 0x0000000000000001 in ?? () #59 0x0000000000000000 in ?? () #60 0xffffff005e4aa9c0 in ?? () #61 0xffffff007b9b74c0 in ?? () #62 0xffffffffb43e2260 in ?? () #63 0xffffffffb43e2238 in ?? () #64 0xffffff005dda5980 in ?? () #65 0xffffffff803cd10a in sched_switch (td=0x513050, newtd=0x513040, flags=4) at /usr/src/sys/kern/sched_4bsd.c:973 Previous frame inner to this frame (corrupt stack?) Here is my dmesg for the Dell 1850 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-BETA4 #0: Fri Sep 16 01:52:30 UTC 2005 root@tank:/usr/obj/usr/src/sys/GENERIC_IPSEC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100800 Hyperthreading: 2 logical CPUs real memory = 2147221504 (2047 MB) avail memory = 2062241792 (1966 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 4 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 3 on acpi0 pci_link2: irq 7 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 5 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 amr0: mem 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2 amr0: Firmware 521S, BIOS H430, 256MB RAM pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 4.0 on pci0 pci4: on pcib4 pcib5: at device 0.0 on pci4 pci5: on pcib5 em0: port 0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 16 at device 4.0 on pci5 em0: Ethernet address: 00:0e:0c:73:d4:f2 em0: Speed:N/A Duplex:N/A em1: port 0xec80-0xecbf mem 0xdfac0000-0xdfadffff irq 17 at device 4.1 on pci5 em1: Ethernet address: 00:0e:0c:73:d4:f3 em1: Speed:N/A Duplex:N/A pcib6: at device 0.2 on pci4 pci6: on pcib6 pcib7: at device 5.0 on pci0 pci7: on pcib7 pcib8: at device 0.0 on pci7 pci8: on pcib8 em2: port 0xdcc0-0xdcff mem 0xdf7e0000-0xdf7fffff irq 64 at device 7.0 on pci8 em2: Ethernet address: 00:14:22:15:ff:4b em2: Speed:N/A Duplex:N/A pcib9: at device 0.2 on pci7 pci9: on pcib9 em3: port 0xccc0-0xccff mem 0xdf5e0000-0xdf5fffff irq 65 at device 8.0 on pci9 em3: Ethernet address: 00:14:22:15:ff:4c em3: Speed:N/A Duplex:N/A pcib10: at device 6.0 on pci0 pci10: on pcib10 uhci0: port 0xace0-0xacff irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xacc0-0xacdf irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xaca0-0xacbf irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdff00000-0xdff003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 2 ports with 2 removable, self powered pcib11: at device 30.0 on pci0 pci11: on pcib11 pci11: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console orm0: at iomem 0xc0000-0xcafff,0xcb000-0xcbfff,0xce800-0xcf7ff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 Timecounters tick every 1.000 msec Fast IPsec: Initialized Security Association Processing. acd0: DVDROM at ata0-master UDMA33 amrd0: on amr0 amrd0: 139900MB (286515200 sectors) RAID 1 (optimal) ses0 at amr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/amrd0s1a WARNING: / was not properly dismounted em2: link state changed to UP em3: link state changed to UP Cheers, Mike From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 14:56:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47AE116A41F for ; Fri, 16 Sep 2005 14:56:24 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F68F43D46 for ; Fri, 16 Sep 2005 14:56:23 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr15.xs4all.nl (8.13.3/8.13.3) with ESMTP id j8GEuLIe016854 for ; Fri, 16 Sep 2005 16:56:21 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id A3C9361FA; Fri, 16 Sep 2005 16:56:21 +0200 (CEST) Date: Fri, 16 Sep 2005 16:56:21 +0200 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20050916145621.GA56113@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <200509160348.j8G3mIH5015714@www.freebsd.org> <200509161137.14570.groot@kde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <200509161137.14570.groot@kde.org> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.10i X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: amd64/86199: Missed AMD64 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 14:56:24 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 16, 2005 at 11:37:14AM +0200, Adriaan de Groot wrote: > On Friday 16 September 2005 05:48, Mike Smith wrote: > > MSI K8M NEO-V is not listed in the section covering amd64 compati= ble > > motherboards. =20 >=20 > That's one issue, which should be PR-ed as described on the > motherboards page. >=20 > > Also there seems to be a lack of support for the VT8237 SATA=20 > > Raid controller. =20 >=20 > Er, you mean >=20 > atapci1@pci0:15:0: class=3D0x010400 card=3D0x80ed1043 chip=3D0x31491= 106=20 > rev=3D0x80 hdr=3D0x00 > vendor =3D 'VIA Technologies Inc' > device =3D 'VT8237 VT6410 SATA RAID Controller' > class =3D mass storage > subclass =3D RAID >=20 > That one? It works just fine on Asus & Gigabyte boards. Works fine as a SATA controller on my MSI NEO FSR (MS-6702). Haven't tried the RAID part. =20 > > onboard sound also results in hard locks, randomly, especially when vch= ans > > are enabled. I'm using the VT8237 Audio as well. Any help with this w= ould > > be greatly appreciated. >=20 > I've managed to lock my Asus board once with mpg123 foo.mp3 & mpg123 > foo.mp3, but sound in general is fine as well. No problems here. Sound tested with maplyer and xmms. FreeBSD slackbox.xs4all.nl 5.4-STABLE FreeBSD 5.4-STABLE #1: Sun Aug 28 13:27:26 CEST 2005 rsmith@slackbox.xs4all.nl:/usr/obj/usr/src/sys/RFS amd= 64 Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDKt0VEnfvsMMhpyURAgUcAJ97I2UeLTkyGqzl/QtIpXa+vu99tgCcDWF+ d78IR9k1coryC0i7/0/9uoU= =ygQe -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 16:51:35 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 786D016A41F for ; Fri, 16 Sep 2005 16:51:35 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E93EA43D45 for ; Fri, 16 Sep 2005 16:51:32 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j8GGvBiX046841; Fri, 16 Sep 2005 12:57:16 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "Ganael Laplanche" Date: Fri, 16 Sep 2005 12:51:09 -0400 User-Agent: KMail/1.6.2 References: <200509151219.55989.jkim@FreeBSD.org> <20050916080048.M77239@martymac.com> In-Reply-To: <20050916080048.M77239@martymac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <200509161251.13330.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/1083/Fri Sep 16 05:41:30 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-amd64@FreeBSD.org, "K.Wieland" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 16:51:35 -0000 On Friday 16 September 2005 04:04 am, Ganael Laplanche wrote: > > On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote: > > > Hi all, > > > > > > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but > > > system hangs during X bootup. I had to go back to the goold old > > > driver from 5.x :( > > > > The 'good old' driver uses generic nForce AGP interface. If the > > driver really works, I will be surprised. I admit agp_amd64.c > > requires more work (esp. chipset-specific handling including > > nForce) but I had no time/hardware. > > > > Anyway you have to make sure agp(4) really works for you. > > Hi again, > > No, I have no agp support, but using the old driver allows me to > start X... I remember using the new driver made a /dev/agpgart > appear, but the system crashes at X startup... Ah, so you are using old driver to disable AGP support? :-) You can always turn off DRI from xorg.conf. > > http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim > > > > > The PR is here : > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015 > > > > > > Any clue ? > > > > Have you tried xorg-server-snap? If it doesn't work, can you try > > this? > > No, I didn't, but I think I'll have the same pb since agp code for > nforce3-250 is not correct in the kernel :( As a matter of fact, agp(4) is not usual suspect here. DRM is. So, you need to make sure agpgart is functioning. If so, drm(4) may be at its fault. > > http://people.freebsd.org/~jkim/xorg-server-snap.diff There are many radeon driver fixes in it. If agpgart works but xorg still crashes, you need this. Thanks, JK > > Thanks, > > Thanks to you, > > Regards, > > Ganael. > > > Jung-uk Kim > > > > > [UTF-8?]Ganaå ï¿½l LAPLANCHE > > > ganael.laplanche@martymac.com > > > http://www.martymac.com > > > Tel : (+33)6.84.03.57.24. > > ------- End of Original Message ------- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 18:48:18 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08CC316A41F for ; Fri, 16 Sep 2005 18:48:18 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F9D843D4C for ; Fri, 16 Sep 2005 18:48:17 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from 192.168.0.2 (localhost.forestinformatics.com [127.0.0.1]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8GImCMc096377 for ; Fri, 16 Sep 2005 11:48:12 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Received: from 192.168.0.20 (SquirrelMail authenticated user hamannj) by 192.168.0.2 with HTTP; Fri, 16 Sep 2005 11:48:12 -0700 (PDT) Message-ID: <50988.192.168.0.20.1126896492.squirrel@192.168.0.2> Date: Fri, 16 Sep 2005 11:48:12 -0700 (PDT) From: "Jeff D. Hamann" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Subject: no wine on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jeff.hamann@forestinformatics.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 18:48:18 -0000 bobby# cd /usr/ports/emulators/wine bobby# make install ===> wine-20050830 is only for i386, and you are running amd64 grrrr....... Any chance of finding an emulator that I can run WinXP/MS Office apps on the amd64 machine? -- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon 97339-1421 phone 541-754-1428 fax 541-752-0288 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 21:00:32 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B63116A41F for ; Fri, 16 Sep 2005 21:00:32 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF2043D58 for ; Fri, 16 Sep 2005 21:00: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.3/8.13.3) with ESMTP id j8GL0Uj9071420 for ; Fri, 16 Sep 2005 21:00:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8GL0TnE071419; Fri, 16 Sep 2005 21:00:30 GMT (envelope-from gnats) Resent-Date: Fri, 16 Sep 2005 21:00:30 GMT Resent-Message-Id: <200509162100.j8GL0TnE071419@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, Phil Regnauld Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 741E516A41F for ; Fri, 16 Sep 2005 20:57:36 +0000 (GMT) (envelope-from regnauld@catpipe.net) Received: from moof.catpipe.net (moof.catpipe.net [195.249.214.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB7E43D60 for ; Fri, 16 Sep 2005 20:57:27 +0000 (GMT) (envelope-from regnauld@catpipe.net) Received: from localhost (localhost [127.0.0.1]) by localhost.catpipe.net (Postfix) with ESMTP id 3D89F1B3CA for ; Fri, 16 Sep 2005 22:57:26 +0200 (CEST) Received: from moof.catpipe.net ([127.0.0.1]) by localhost (moof.catpipe.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42009-01 for ; Fri, 16 Sep 2005 22:57:21 +0200 (CEST) Received: from vinyl.catpipe.net (vinyl.catpipe.net [195.249.214.189]) by moof.catpipe.net (Postfix) with ESMTP id AACE11B3AF for ; Fri, 16 Sep 2005 22:57:15 +0200 (CEST) Received: by vinyl.catpipe.net (Postfix, from userid 1006) id AB5B339827; Fri, 16 Sep 2005 22:53:34 +0200 (CEST) Message-Id: <20050916205334.AB5B339827@vinyl.catpipe.net> Date: Fri, 16 Sep 2005 22:53:34 +0200 (CEST) From: Phil Regnauld To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/86229: Missing recvmsg syscall in freebsd32 API causes sshd crash on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Phil Regnauld List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 21:00:32 -0000 >Number: 86229 >Category: amd64 >Synopsis: Missing recvmsg syscall in freebsd32 API causes sshd crash on amd64 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 16 21:00:29 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Phil Regnauld >Release: FreeBSD 5.4-STABLE amd64 >Organization: catpipe Systems ApS >Environment: System: FreeBSD j2 5.4-STABLE FreeBSD 5.4-STABLE #0: Thu Sep 15 21:21:01 CEST 2005 admin@j2:/usr/obj/usr/src/sys/JAIL amd64 >Description: recvmsg(2) is not implemented in the freebsd32 compatibility layer. >From /sys/compat/freebsd32/syscalls.master: ; XXX implement 27 AUE_NULL UNIMPL recvmsg This is a problem when trying to run, among others sshd from i386/4-STABLE or 5-STABLE (for example in a jail): if privilege separation (the default) is used, then recvmsg is called by the child after the fork. The missing syscall causes a termination of sshd with SIGSYS (12): 14143 sshd CALL recvmsg 14143 sshd RET recvmsg -1 errno 78 Function not implemented [...] 14143 sshd PSIG SIGSYS SIG_DFL This is a problem as both i386 and amd64 are Tier 1 platforms, and the non availability of recvmsg() can be a problem for many applications. >How-To-Repeat: Compile the following statically on 5.x/i386 or 4.x/i386 system and execute on an amd64 system with "options COMPAT_IA32" in the kernel. #include #include #include #include int main(void) { fprintf(stderr, "moo1\n"); recvmsg(0, 0, 0); fprintf(stderr, "moo2\n"); err(1, "moo"); return 0; } >Fix: No known fix. In the case of sshd, disable privilege separation in /etc/ssh/sshd_config (not necessary if logging in as root). >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 21:27:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6599216A41F for ; Fri, 16 Sep 2005 21:27:24 +0000 (GMT) (envelope-from sl151@waikato.ac.nz) Received: from newman.its.waikato.ac.nz (newman.its.waikato.ac.nz [130.217.66.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAE4743D46 for ; Fri, 16 Sep 2005 21:27:22 +0000 (GMT) (envelope-from sl151@waikato.ac.nz) Received: from ex4.its.waikato.ac.nz (ex4.its.waikato.ac.nz [130.217.70.144]) by newman.its.waikato.ac.nz (Postfix) with ESMTP id 00CCF1279C8 for ; Sat, 17 Sep 2005 09:27:21 +1200 (NZST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5BB05.6BD48F3A" Date: Sat, 17 Sep 2005 09:27:03 +1200 Message-ID: <53EF8EA01F1F5241BAB680A851B4F03F1E1224@ex4.its.waikato.ac.nz> X-MS-Has-Attach: X-MS-TNEF-Correlator: <53EF8EA01F1F5241BAB680A851B4F03F1E1224@ex4.its.waikato.ac.nz> Thread-Topic: freebsd-amd64 Digest, Vol 119, Issue 5 Thread-Index: AcW6tlvGE/p8DeZDSJ6FhRvTV/dB4QATwXQj From: "Lin, Shih-Min" To: , X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: freebsd-amd64 Digest, Vol 119, Issue 5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 21:27:24 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C5BB05.6BD48F3A Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -----Original Message----- From: owner-freebsd-amd64@freebsd.org on behalf of = freebsd-amd64-request@freebsd.org Sent: Sat 9/17/2005 12:00 AM To: freebsd-amd64@freebsd.org Subject: freebsd-amd64 Digest, Vol 119, Issue 5 =20 Send freebsd-amd64 mailing list submissions to freebsd-amd64@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 or, via email, send a message with subject or body 'help' to freebsd-amd64-request@freebsd.org You can reach the person managing the list at freebsd-amd64-owner@freebsd.org When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-amd64 digest..." Today's Topics: 1. amd64 Radeon 9000 nForce3 250 agp support - Yes and No (K. Wieland) 2. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (Ganael Laplanche) 3. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (Jung-uk Kim) 4. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (Adam Gregoire) 5. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (John-Mark Gurney) 6. building/porting linux SIS965L driver (Jeff D. Hamann) 7. acpi/ohci/rsdt wtf? (Jeff D. Hamann) 8. Re: acpi/ohci/rsdt wtf? (John Baldwin) 9. [PATCH] agp(4) for ULi M1689/nVidia nForce3 (Jung-uk Kim) 10. amd64/86199: Missed AMD64 motherboard (Mike Smith) 11. Problem with hp zv6000 (pier) 12. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (Ganael Laplanche) 13. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No (Ganael Laplanche) 14. Re: amd64/86199: Missed AMD64 motherboard (Adriaan de Groot) 15. Re: acpi/ohci/rsdt wtf? (Bruno Ducrot) 16. Re: FAST_IPSEC on EMT64 / AMD64 (Michael VInce) ---------------------------------------------------------------------- Message: 1 Date: Thu, 15 Sep 2005 09:22:26 -0500 From: K. Wieland Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: Jung-uk Kim Cc: freebsd-amd64@freebsd.org Message-ID: <4efa8eff718166b299f7d6a317011a37@gmail.com> Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; = format=3Dflowed Jung-uk and fellow amd64 subscribers, I tried upgrading to 6.0B4 last night, after spending several nights =20 reading the documentation. I have been reading and am subscribed to =20 the amd64 list, so I figure I might as well try it! First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the =20 sysinstall that way as outlined in the docs (I don't remember where, =20 but I can get the reference). sysinstall (v6.0 B4) would not run, =20 complaining about some libraries not being present (I had a previous =20 version of the libraries it was looking for, so I made sym links (bad, =20 I know!) but it failed looking for the next library, so I deleted the =20 symlink, and decided to reboot with the CD. I rebooted, went into fixit and did a dmesg. AGP was there, and the =20 device /dev/agpart existed. I was happy, and decided to upgrade to 6.0 = beta4 using the upgrade option in sysinstall. I didn't remember the =20 mount points for the various file systems so I had to boot back into =20 5.4 and write it all down (it would be nice if this was in the =20 documentation)! Anyway, I upgraded and rebooted. The first thing I noticed was the =20 generic kernel detected my com port, but didn't create a /dev/cuaa0 (I =20 dial up for internet). And, because I want sound and my TV card (bktr) = I decided to customize the kernel like I had done in 5.4. So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and =20 found that it was basically the same (MYKERNEL had the sound, bktr, and = agp with several extraneous things commented out). I built the new =20 kernel, installed it and rebooted. AGP was gone! I thought, well =20 maybe you don't need "device agp" in the kernel (I didn't see it in the = GENERIC, and agp loaded with that), so I tried that...still no AGP. =20 Then, I decided to use the GENERIC and see if that worked---still no =20 AGP. But, if I boot up with the CD, AGP is back! The confusing part to me is that the uname -a still gives me RELENG5.4 =20 -p7. That seems strange to me. The ps command also didn't work as =20 expected (just prints the headers, none of the processes). I read that if your sources don't match your kernel, you can get weird =20 stuff like this, so I went to cvsup to the most recent. BUT, in the =20 /usr/share/examples/standard-cvsup files it still had RELENG 5.4. I =20 went ahead and cvsup'ed anyway. I don't have anything critical on the drive, so I am tempted to wipe it = clean and reinstall (ala windows style) but I would really like to =20 understand what is going on here. I am CCing the freebsd-amd64 list in case they have some insights, too. Thanks, Kristopher Wieland Graduate Student Washington University in St. Louis Dept. of Physics- Compton Hall On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote: > On Tuesday 13 September 2005 12:19 pm, K Wieland wrote: >> Thanks again for the quick reply. > > No problem. > >> Is there a "best method" for installing another version? I would >> rather not loose the kernel config, etc. Is it best to just wipe >> everything and start over? > > cvsup, buildworld, installworld, mergemaster... But it's quite a > hassle for new users. First of all, if the only problem for you is > the agp, try booting from the ISO, select Fixit, select CD/DVD, then > you will get shell. You can see if agp is probed/attached from > there. If that's there, you have two choices: > > 1. Upgrade. > 2. Patch kernel to add support for the AGP device. > > If you choose option 2, the only thing you really need is this: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?=20 > r1=3D1.6&r2=3D1.7 > > Good luck, > > JK > >> I'll give it a try and see how it goes! >> >> Kristopher >> >> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote: >>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote: >>>> Thank you for your quick reply! >>>> >>>> Yes, I am using 5.4 Release. I guess since I was just starting >>>> out with Freebsd, I'd go with "release" vs. stable or current. >>>> >>>> Do you know an ftp site for getting the images for 6.0 beta4? >>>> Or should I just cvsup to it? You can tell I am new, new new! >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/ >>> >>> JK >>> >>>> Thanks, >>>> >>>> Kristopher >>>> >>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote: >>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote: >>>>>> Hello Jung-uk! >>>>>> >>>>>> I was reading through the archives of the freebsd-amd64 >>>>>> archives (I am a new Freebsd user) and I have the exact same >>>>>> problem that you and Geneal talked about. >>>>>> >>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does >>>>>> not detect the agp, even though it is in the kernel. >>>>>> >>>>>> Did you ever get this issue resolved? >>>>> >>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It >>>>> should be fine. >>>>> >>>>> JK >>>>> >>>>>> Thank you, >>>>>> >>>>>> Kristopher Wieland > ------------------------------ Message: 2 Date: Thu, 15 Sep 2005 15:53:13 +0000 From: "Ganael Laplanche" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: K.Wieland , Jung-uk Kim Cc: freebsd-amd64@freebsd.org Message-ID: <20050915155131.M39844@martymac.com> Content-Type: text/plain; charset=3Diso-8859-1 Hi all, I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system hangs = during X bootup. I had to go back to the goold old driver from 5.x :( The PR is here : http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84015 Any clue ? Gana=EBl LAPLANCHE ganael.laplanche@martymac.com http://www.martymac.com Tel : (+33)6.84.03.57.24. ---------- Original Message ----------- From: K.Wieland To: Jung-uk Kim Cc: freebsd-amd64@freebsd.org Sent: Thu, 15 Sep 2005 09:22:26 -0500 Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No > Jung-uk and fellow amd64 subscribers, >=20 > I tried upgrading to 6.0B4 last night, after spending several nights =20 > reading the documentation. I have been reading and am subscribed to =20 > the amd64 list, so I figure I might as well try it! >=20 > First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the =20 > sysinstall that way as outlined in the docs (I don't remember where, =20 > but I can get the reference). sysinstall (v6.0 B4) would not run, =20 > complaining about some libraries not being present (I had a previous =20 > version of the libraries it was looking for, so I made sym links (bad, = > I know!) but it failed looking for the next library, so I deleted the = > symlink, and decided to reboot with the CD. >=20 > I rebooted, went into fixit and did a dmesg. AGP was there, and the =20 > device /dev/agpart existed. I was happy, and decided to upgrade to=20 > 6.0 beta4 using the upgrade option in sysinstall. I didn't remember=20 > the mount points for the various file systems so I had to boot back=20 > into =20 > 5.4 and write it all down (it would be nice if this was in the=20 > documentation)! >=20 > Anyway, I upgraded and rebooted. The first thing I noticed was the =20 > generic kernel detected my com port, but didn't create a /dev/cuaa0 (I = > dial up for internet). And, because I want sound and my TV card=20 > (bktr) I decided to customize the kernel like I had done in 5.4. >=20 > So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and =20 > found that it was basically the same (MYKERNEL had the sound, bktr, > and agp with several extraneous things commented out). I built the=20 > new kernel, installed it and rebooted. AGP was gone! I thought,=20 > well maybe you don't need "device agp" in the kernel (I didn't see it = > in the GENERIC, and agp loaded with that), so I tried that...still no = > AGP. Then, I decided to use the GENERIC and see if that worked--- > still no AGP. But, if I boot up with the CD, AGP is back! >=20 > The confusing part to me is that the uname -a still gives me RELENG5.4 = > -p7. That seems strange to me. The ps command also didn't work as=20 > expected (just prints the headers, none of the processes). >=20 > I read that if your sources don't match your kernel, you can get weird = > stuff like this, so I went to cvsup to the most recent. BUT, in the = > /usr/share/examples/standard-cvsup files it still had RELENG 5.4. I=20 > went ahead and cvsup'ed anyway. >=20 > I don't have anything critical on the drive, so I am tempted to wipe=20 > it clean and reinstall (ala windows style) but I would really like to = > understand what is going on here. >=20 > I am CCing the freebsd-amd64 list in case they have some insights, = too. >=20 > Thanks, >=20 > Kristopher Wieland > Graduate Student > Washington University in St. Louis > Dept. of Physics- Compton Hall > On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote: >=20 > > On Tuesday 13 September 2005 12:19 pm, K Wieland wrote: > >> Thanks again for the quick reply. > > > > No problem. > > > >> Is there a "best method" for installing another version? I would > >> rather not loose the kernel config, etc. Is it best to just wipe > >> everything and start over? > > > > cvsup, buildworld, installworld, mergemaster... But it's quite a > > hassle for new users. First of all, if the only problem for you is > > the agp, try booting from the ISO, select Fixit, select CD/DVD, then > > you will get shell. You can see if agp is probed/attached from > > there. If that's there, you have two choices: > > > > 1. Upgrade. > > 2. Patch kernel to add support for the AGP device. > > > > If you choose option 2, the only thing you really need is this: > > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?=20 > > r1=3D1.6&r2=3D1.7 > > > > Good luck, > > > > JK > > > >> I'll give it a try and see how it goes! > >> > >> Kristopher > >> > >> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote: > >>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote: > >>>> Thank you for your quick reply! > >>>> > >>>> Yes, I am using 5.4 Release. I guess since I was just starting > >>>> out with Freebsd, I'd go with "release" vs. stable or current. > >>>> > >>>> Do you know an ftp site for getting the images for 6.0 beta4? > >>>> Or should I just cvsup to it? You can tell I am new, new new! > >>> > >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/ > >>> > >>> JK > >>> > >>>> Thanks, > >>>> > >>>> Kristopher > >>>> > >>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote: > >>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote: > >>>>>> Hello Jung-uk! > >>>>>> > >>>>>> I was reading through the archives of the freebsd-amd64 > >>>>>> archives (I am a new Freebsd user) and I have the exact same > >>>>>> problem that you and Geneal talked about. > >>>>>> > >>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does > >>>>>> not detect the agp, even though it is in the kernel. > >>>>>> > >>>>>> Did you ever get this issue resolved? > >>>>> > >>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It > >>>>> should be fine. > >>>>> > >>>>> JK > >>>>> > >>>>>> Thank you, > >>>>>> > >>>>>> Kristopher Wieland > > >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to = "freebsd-amd64-unsubscribe@freebsd.org" ------- End of Original Message ------- ------------------------------ Message: 3 Date: Thu, 15 Sep 2005 12:19:53 -0400 From: Jung-uk Kim Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: "Ganael Laplanche" Cc: freebsd-amd64@FreeBSD.org, "K.Wieland" Message-ID: <200509151219.55989.jkim@FreeBSD.org> Content-Type: text/plain; charset=3D"utf-8" On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote: > Hi all, > > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system > hangs during X bootup. I had to go back to the goold old driver > from 5.x :( The 'good old' driver uses generic nForce AGP interface. If the=20 driver really works, I will be surprised. I admit agp_amd64.c=20 requires more work (esp. chipset-specific handling including nForce)=20 but I had no time/hardware. Anyway you have to make sure agp(4) really works for you. http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim > The PR is here : > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84015 > > Any clue ? Have you tried xorg-server-snap? If it doesn't work, can you try=20 this? http://people.freebsd.org/~jkim/xorg-server-snap.diff Thanks, Jung-uk Kim > Gana=EF=BF=BDl LAPLANCHE > ganael.laplanche@martymac.com > http://www.martymac.com > Tel : (+33)6.84.03.57.24. ------------------------------ Message: 4 Date: Thu, 15 Sep 2005 12:29:37 -0400 From: Adam Gregoire Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: freebsd-amd64@freebsd.org Cc: "K.Wieland" Message-ID: <1126801777.7412.7.camel@S0106c0ffeec0ffee.su.shawcable.net> Content-Type: text/plain Hello, this chipset is not supported for agpgart, the nforce3 250 chipset has the code needed to detect the gart but is missing functionality needed for proper operation. See also, PR amd64/71753 and the following thread http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html Regards, --=20 Adam Gregoire ------------------------------ Message: 5 Date: Thu, 15 Sep 2005 10:19:04 -0700 From: John-Mark Gurney Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: "K. Wieland" Cc: freebsd-amd64@FreeBSD.org, Jung-uk Kim Message-ID: <20050915171904.GT793@funkthat.com> Content-Type: text/plain; charset=3Dus-ascii K. Wieland wrote this message on Thu, Sep 15, 2005 at 09:22 -0500: > Anyway, I upgraded and rebooted. The first thing I noticed was the =20 > generic kernel detected my com port, but didn't create a /dev/cuaa0 (I = =20 > dial up for internet). And, because I want sound and my TV card = (bktr) =20 > I decided to customize the kernel like I had done in 5.4. These have been renamed to match the tty versions.. look for /dev/cuad0 instead... --=20 John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ------------------------------ Message: 6 Date: Thu, 15 Sep 2005 10:27:16 -0700 From: "Jeff D. Hamann" Subject: building/porting linux SIS965L driver To: , Message-ID: <001d01c5ba1a$bc83fdd0$0a00a8c0@rodan> Content-Type: text/plain; format=3Dflowed; charset=3D"iso-8859-1"; reply-type=3Doriginal I'm building (or trying to build) an amd64 FreeBSD machine to replace my = FreeBSD 4.4 server. I purchased an ASUS Vintage-AE1 MB that uses the=20 following chipsets: Northbridge: SiS760GX Southbridge: SiS965L I've not been able to get the on-board NIC to light up, so I purchased=20 another NIC which works alright. It's bothering me too much that the = chipset=20 isn't supported = (http://www.freebsd.org/platforms/amd64/motherboards.html)=20 but many of the other ASUS MB chipsets are. This seems like a great = machine=20 and I suspect there are plenty more machines that will be using this=20 barebones box as a starting place (of course, I'll be wrong in a year=20 anyways). I've found the linux driver for the on-board NIC and since = I've=20 never ported a driver for FreeBSD, I'm trying to figure out how much = work it=20 will be to port the driver to FreeBSD-6.0? I've snooped around in the /usr/src/sys/pci/if_sis.c /usr/src/sys/pci/if_sisreg.h 6.0Beta4 files to simply examine the bsd code. To my novice eyes, the = files=20 look completely different from the linux drivers and I'm not sure I can=20 takle this myself since I've never done anything like this. Can someone = help=20 me through this process, or is this not worth the trouble? Jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com ------------------------------ Message: 7 Date: Thu, 15 Sep 2005 12:41:18 -0700 From: "Jeff D. Hamann" Subject: acpi/ohci/rsdt wtf? To: Message-ID: <000b01c5ba2d$7a6fa940$0a00a8c0@rodan> Content-Type: text/plain; format=3Dflowed; charset=3D"iso-8859-1"; reply-type=3Doriginal I'm curious what the acpi_perf0: invalid _PSS package messages are all about and why there are so many? I'm also curious about = the=20 EHCI stuff. My bios has some settings which state: "stop ehci in ohci handler handover" the comments for the setting stats: "stops the ehci host controller during ohci handvoer call. the is needed = for=20 installing Oses that does not support ehci host controllers" and I'm not sure what it means and I don't know if FreeBSD-6beta4 = supports=20 it. Also, there's another setting about "acpi apic support" where the hint=20 states: "include acpi apic table pointer to rsdt pointer list" Wha? I've included my dmesg output for diagnostics. $ dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 6.0-BETA4 #1: Fri Sep 16 06:41:12 PDT 2005 root@bobby.forestinformatics.com:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1995.01-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf4a Stepping =3D 10 = Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 1039400960 (991 MB) avail memory =3D 991444992 (945 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 0 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 5 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: irq 5 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port=20 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.5 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 2.7 (no driver attached) ohci0: mem 0xfbefc000-0xfbefcfff irq 20 at = device=20 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfbefd000-0xfbefdfff irq 21 at = device=20 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xfbefe000-0xfbefefff irq 22 at = device=20 3.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfbeff000-0xfbefffff irq = 23=20 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered pci0: at device 4.0 (no driver attached) pcib2: at device 6.0 on pci0 pci2: on pcib2 pcib3: at device 7.0 on pci0 pci3: on pcib3 rl0: port 0xa800-0xa8ff mem=20 0xfbefb800-0xfbefb8ff irq 17 at device 10.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:11:95:24:60:b3 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on=20 acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 = on=20 acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq = 3=20 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 Timecounter "TSC" frequency 1995008941 Hz quality 800 Timecounters tick every 1.000 msec ad0: 190782MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA66 Trying to mount root from ufs:/dev/ad0s1a $ jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com ------------------------------ Message: 8 Date: Thu, 15 Sep 2005 16:00:49 -0400 From: John Baldwin Subject: Re: acpi/ohci/rsdt wtf? To: freebsd-amd64@freebsd.org, "Jeff D. Hamann" Message-ID: <200509151600.50793.jhb@FreeBSD.org> Content-Type: text/plain; charset=3D"iso-8859-1" On Thursday 15 September 2005 03:41 pm, Jeff D. Hamann wrote: > I'm curious what the > > acpi_perf0: invalid _PSS package > > messages are all about and why there are so many? I'm also curious = about > the EHCI stuff. My bios has some settings which state: > > "stop ehci in ohci handler handover" > > the comments for the setting stats: > > "stops the ehci host controller during ohci handvoer call. the is = needed > for installing Oses that does not support ehci host controllers" Leave it off. FreeBSD 6 includes the ehci(4) driver by default as you = can see=20 in your dmesg. > and I'm not sure what it means and I don't know if FreeBSD-6beta4 = supports > it. > > Also, there's another setting about "acpi apic support" where the hint > states: > > "include acpi apic table pointer to rsdt pointer list" > > Wha? Leave that on. It looks like it already is. Having this on is what = let's us=20 find the ACPI APIC Table as mentioned here: > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard --=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org ------------------------------ Message: 9 Date: Thu, 15 Sep 2005 19:57:04 -0400 From: Jung-uk Kim Subject: [PATCH] agp(4) for ULi M1689/nVidia nForce3 To: freebsd-amd64@FreeBSD.org Message-ID: <200509151957.24837.jkim@FreeBSD.org> Content-Type: text/plain; charset=3D"us-ascii" If you have any of these, please test and let me know. http://people.freebsd.org/~jkim/agp_amd64.diff FYI, agp(4) GART test is here: http://people.freebsd.org/~jkim/testgart.c Thanks, Jung-uk Kim ------------------------------ Message: 10 Date: Fri, 16 Sep 2005 03:48:18 GMT From: Mike Smith Subject: amd64/86199: Missed AMD64 motherboard To: freebsd-gnats-submit@FreeBSD.org Message-ID: <200509160348.j8G3mIH5015714@www.freebsd.org> >Number: 86199 >Category: amd64 >Synopsis: Missed AMD64 motherboard >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: =20 >Keywords: =20 >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 16 03:50:08 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Mike Smith >Release: FreeBSD 5.4-STABLE >Organization: none >Environment: FreeBSD insomnia.localnet.net 5.4-STABLE FreeBSD 5.4-STABLE #5: Thu Sep = 15 15:24:53 CDT 2005 = perlfu@insomnia.localnet.net:/usr/obj/usr/src/sys/INSOMNIA amd64 >Description: MSI K8M NEO-V is not listed in the section covering amd64 = compatible motherboards. Also there seems to be a lack of support for = the VT8237 SATA Raid controller. I can use the drive, but there seems = to be some shaky behavior coming from it. I've seen random kernel = panics related to the drive, (don't have them to paste currently, but if = you give me some time I'm sure it will randomly pop up some time soon). = It also defers for background fsck'ing even if the drives were properly = unmounted. The onboard sound also results in hard locks, randomly, = especially when vchans are enabled. I'm using the VT8237 Audio as well. = Any help with this would be greatly appreciated. >How-To-Repeat: Errors occur fairly randomly, and present themselves in different = manners each time. The drive can do everything from cause a panic, = (same one each time, seems to indicate inconsistancies on the drive). = Also shows itself by constantly appearing as improperly dismounted, even = when shutdown, or reboot was called. Sound causes hard locks quite = frequently and randomly as far as I can tell. It only hard locks when I = try to play multiple sounds at once. Have tried with and without = hw.snd.maxautovchans=3D4, tried a few of the patches that came out on = the lists to no avail, no error messages, or logs can be found with = anything pertaining to the sound issue, apparently it is generally a = 100% hard lock, keyboard failure and all. >Fix: =20 >Release-Note: >Audit-Trail: >Unformatted: ------------------------------ Message: 11 Date: Fri, 16 Sep 2005 07:58:04 +0200 From: pier Subject: Problem with hp zv6000 To: freebsd-amd64@freebsd.org Message-ID: <432A5EEC.9020202@yahoo.it> Content-Type: text/plain; charset=3D"iso-8859-15" Hi all. I'm having so many troubles that i have almost gave up to install FreeBSD on this notebook (amd64 3500+, chipset ATI Xpress200). I tried all the releases, from 5.3 to 6.0-BETA4 but no one works. I read something here that could be interesting: http://forums.bit-tech.net/showthread.php?t=3D94652 I tried to look for this functions in the code, but it looks like in the new releases they don't exist. So...now i can boot with the kernel installed with this personalized boot-cd (http://blackk.union.edu/~black/freebsd/5_3_30Dec2004-amd64-miniinst.iso)= but i can't update my kernel with a newer one. What can I do? Thank you Pier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature Url : = http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050916/9b8= 58fc7/signature-0001.bin ------------------------------ Message: 12 Date: Fri, 16 Sep 2005 08:04:28 +0000 From: "Ganael Laplanche" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: Jung-uk Kim Cc: freebsd-amd64@FreeBSD.org, "K.Wieland" Message-ID: <20050916080048.M77239@martymac.com> Content-Type: text/plain; charset=3Diso-8859-1 > On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote: > > Hi all, > > > > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system > > hangs during X bootup. I had to go back to the goold old driver > > from 5.x :( >=20 > The 'good old' driver uses generic nForce AGP interface. If the=20 > driver really works, I will be surprised. I admit agp_amd64.c=20 > requires more work (esp. chipset-specific handling including nForce)=20 > but I had no time/hardware. >=20 > Anyway you have to make sure agp(4) really works for you. > Hi again, No, I have no agp support, but using the old driver allows me to start = X... I remember using the new driver made a /dev/agpgart appear, but the system = crashes at X startup... =20 > http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim >=20 > > The PR is here : > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84015 > > > > Any clue ? >=20 > Have you tried xorg-server-snap? If it doesn't work, can you try=20 > this? No, I didn't, but I think I'll have the same pb since agp code for = nforce3-250 is not correct in the kernel :( > http://people.freebsd.org/~jkim/xorg-server-snap.diff >=20 > Thanks, Thanks to you, Regards, Ganael. > Jung-uk Kim >=20 > > [UTF-8?]Gana=EF=BF=BDl LAPLANCHE > > ganael.laplanche@martymac.com > > http://www.martymac.com > > Tel : (+33)6.84.03.57.24. ------- End of Original Message ------- ------------------------------ Message: 13 Date: Fri, 16 Sep 2005 08:08:54 +0000 From: "Ganael Laplanche" Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No To: Adam Gregoire , freebsd-amd64@freebsd.org Cc: "K.Wieland" Message-ID: <20050916080443.M8613@martymac.com> Content-Type: text/plain; charset=3Diso-8859-1 > Hello, this chipset is not supported for agpgart, the nforce3 250 > chipset has the code needed to detect the gart but is missing > functionality needed for proper operation. >=20 > See also, PR amd64/71753 and the following thread > = http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html I'm the author of this post... I tried to write a small patch to see = what's happening with it, but it made my system hang as described here http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004315.html = ! And It looks like this code has been included in the 6-0 branch :(, that's why = you should use the old 5.x drivers... > Regards, >=20 > --=20 > Adam Gregoire >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to = "freebsd-amd64-unsubscribe@freebsd.org" ------- End of Original Message ------- ------------------------------ Message: 14 Date: Fri, 16 Sep 2005 11:37:14 +0200 From: Adriaan de Groot Subject: Re: amd64/86199: Missed AMD64 motherboard To: freebsd-amd64@freebsd.org Message-ID: <200509161137.14570.groot@kde.org> Content-Type: text/plain; charset=3D"iso-8859-1" On Friday 16 September 2005 05:48, Mike Smith wrote: > MSI K8M NEO-V is not listed in the section covering amd64 = compatible > motherboards. =20 That's one issue, which should be PR-ed as described on the motherboards = page. > Also there seems to be a lack of support for the VT8237 SATA=20 > Raid controller. =20 Er, you mean atapci1@pci0:15:0: class=3D0x010400 card=3D0x80ed1043 = chip=3D0x31491106=20 rev=3D0x80 hdr=3D0x00 vendor =3D 'VIA Technologies Inc' device =3D 'VT8237 VT6410 SATA RAID Controller' class =3D mass storage subclass =3D RAID That one? It works just fine on Asus & Gigabyte boards. > onboard sound also results in hard locks, randomly, especially when = vchans > are enabled. I'm using the VT8237 Audio as well. Any help with this = would > be greatly appreciated. I've managed to lock my Asus board once with mpg123 foo.mp3 & mpg123 = foo.mp3,=20 but sound in general is fine as well. --=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot ------------------------------ Message: 15 Date: Fri, 16 Sep 2005 12:12:57 +0200 From: Bruno Ducrot Subject: Re: acpi/ohci/rsdt wtf? To: "Jeff D. Hamann" Cc: freebsd-amd64@freebsd.org Message-ID: <20050916101257.GA12562@poupinou.org> Content-Type: text/plain; charset=3Dus-ascii On Thu, Sep 15, 2005 at 12:41:18PM -0700, Jeff D. Hamann wrote: > I'm curious what the >=20 > acpi_perf0: invalid _PSS package >=20 > messages are all about and why there are so many? Could you send to me the output from acpidump -dt It's rather large. Please send it to me privately or better provide some link. Cheers, --=20 Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ------------------------------ Message: 16 Date: Fri, 16 Sep 2005 20:16:24 +1000 From: Michael VInce Subject: Re: FAST_IPSEC on EMT64 / AMD64 To: "Bjoern A. Zeeb" Cc: freebsd-amd64@FreeBSD.org, Kris Kennaway Message-ID: <432A9B78.8020906@roq.com> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed Michael VInce wrote: > Bjoern A. Zeeb wrote: > >> On Mon, 12 Sep 2005, Kris Kennaway wrote: >> >> =20 >> >>> On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote: >>> =20 >>> >>>> Hi guys, >>>> I am getting a Intel Xeon based EMT64 server as a gateway that may = in >>>> the future do some VPN, >>>> I wondered if the EMT64 servers could run FAST_IPSEC under AMD64=20 >>>> FreeBSD. >>>> With these options below compiled into the kernel I was able to = boot >>>> FreeBSD with no panics if I booted into single user mode and then = just >>>> did 'exit' to go back to regular boot, otherwise it would panic as = if >>>> it was an AMD64 CPU. >>>> =20 >>> >>> You forgot to include details of the panic. >>> =20 >> >> >> That would be really good to know. >> >> Then we'd finally know more than was given in >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Damd64/73211 >> =20 >> > > Sorry instead of getting a core dump I grabbed a FreeBSD AMD64 beta4=20 > 6.0 ISO and put it on this server. > But I do have some good news in what I found. > Recompiled FAST_IPSEC into the kernel and rebooted it, it came up = fine.. > So then put in some ipsec security policies into /etc/ipsec.conf > ipsec_enable=3D"YES" > and ran /etc/rc.d/ipsec start > and it ran fine. > I then installed ipsec-tools and loaded up the racoon daemon this also = > triggers a panic on my FreeBSD AMD64 6.0 laptop with out FAST_IPSEC=20 > being compiled into the kernel and its loaded up fine. > This looks all completely solid. I haven't been able to panic the=20 > server with a full VPN configuration activated. > The only thing I haven't done is tested if the IPSEC VPN actually can=20 > work. > > This is no mistake this is AMD64 kernel FreeBSD with FAST_IPSEC I just = > cheated using the Intel EMT64 > > Regards, > Mike > > beast# /sbin/sysctl -a | grep ipsec > ipsecpolicy 16 4K - 520 256 > ipsecrequest 2 1K - 4 256 > ipsec-reg 3 1K - 24 32 > net.inet.ipsec.def_policy: 1 > net.inet.ipsec.esp_trans_deflev: 1 > net.inet.ipsec.esp_net_deflev: 1 > net.inet.ipsec.ah_trans_deflev: 1 > net.inet.ipsec.ah_net_deflev: 1 > net.inet.ipsec.ah_cleartos: 1 > net.inet.ipsec.ah_offsetmask: 0 > net.inet.ipsec.dfbit: 0 > net.inet.ipsec.ecn: 0 > net.inet.ipsec.debug: 0 > net.inet.ipsec.esp_randpad: -1 > net.inet.ipsec.crypto_support: 0 > net.inet6.ipsec6.def_policy: 1 > net.inet6.ipsec6.esp_trans_deflev: 1 > net.inet6.ipsec6.esp_net_deflev: 1 > net.inet6.ipsec6.ah_trans_deflev: 1 > net.inet6.ipsec6.ah_net_deflev: 1 > net.inet6.ipsec6.ecn: 0 > net.inet6.ipsec6.debug: 0 > net.inet6.ipsec6.esp_randpad: -1 > beast# uname -a > FreeBSD beast 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Mon Sep 12 20:40:05 UTC=20 > 2005 root@beast:/usr/obj/usr/src/sys/GENERIC_IPSEC amd64 > > _______________________________________________ > 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" I am back, I still would like to see this bug fixed (and I assume other people do=20 as well :) The server in my above email appears to be working fine using FAST_IPSEC = on AMD64 is a Dell 2850 (Beast) But on a Dell 1850 it crashes as usual, here is a dump on AMD64 6.0=20 Beta4 cvsuped from beta3 ISO install. I still don't know why it appears=20 to be working fine on a 2850 but not on any other machine in the world? This machine below is a Dell 1850 EMT64 with FAST_IPSEC compiled into it = with some rules in /etc/ipsec.conf I can get panics from starting ipsec or starting racoon ipsec-tools. The = I have listed 2 dumps here the first one is from racoon and the one=20 below is from setkey ( starting ipsec ) I don't really know much about doing this stuff so I have just run some=20 of the commands in the kernel debug handbook example. This dump was=20 triggered from starting racoon. This is from a usb2serial console output from the server. cd /usr/obj/usr/src/sys/GENERIC_IPSEC/ tank# kgdb kernel.debug /usr/crash/vmcore.7 [GDB will not be able to debug user-mode threads:=20 /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain=20 conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: 0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 591 (racoon) panic: from debugger cpuid =3D 0 Uptime: 4m23s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 = 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695=20 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471=20 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247=20 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023=20 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 = 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447=20 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159=20 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); (kgdb) list 167 static __inline struct thread * 168 __curthread(void) 169 { 170 struct thread *td; 171 172 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); 173 return (td); 174 } 175 #define curthread (__curthread()) 176 (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0xffffffff803b8ccc in boot (howto=3D260) at=20 /usr/src/sys/kern/kern_shutdown.c:399 #2 0xffffffff803b876b in panic (fmt=3D0xffffffff805faac2 "from = debugger")=20 at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xffffffff801aa1c2 in db_panic (addr=3D0, have_addr=3D0, count=3D0,=20 modif=3D0x0) at /usr/src/sys/ddb/db_command.c:435 #4 0xffffffff801aa705 in db_command_loop () at=20 /usr/src/sys/ddb/db_command.c:349 #5 0xffffffff801ac573 in db_trap (type=3D-1270872608, code=3D0) at=20 /usr/src/sys/ddb/db_main.c:221 #6 0xffffffff803d5799 in kdb_trap (type=3D12, code=3D0,=20 tf=3D0xffffffffb44007a0) at /usr/src/sys/kern/subr_kdb.c:473 #7 0xffffffff8059bf0e in trap_fatal (frame=3D0xffffffffb44007a0,=20 eva=3D18446742975788145024) at /usr/src/sys/amd64/amd64/trap.c:656 #8 0xffffffff8059c2a3 in trap_pfault (frame=3D0xffffffffb44007a0,=20 usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:581 #9 0xffffffff8059c4b9 in trap (frame=3D {tf_rdi =3D -2140943745, tf_rsi =3D 256, tf_rdx =3D -1270871712, = tf_rcx=20 =3D -2142535110, tf_r8 =3D 64, tf_r9 =3D -1097921406592, tf_rax =3D 0, = tf_rbx =3D=20 2152432187, tf_rbp =3D -1270871728, tf_r10 =3D -2139154144, tf_r11 =3D=20 -1270871552, tf_r12 =3D 57, tf_r13 =3D 0, tf_r14 =3D 0, tf_r15 =3D 0, = tf_trapno=20 =3D 12, tf_addr =3D -3413406822, tf_flags =3D -2140901446, tf_err =3D 0, = tf_rip=20 =3D -2142535096, tf_cs =3D 8, tf_rflags =3D 66178, tf_rsp =3D = -1270871968, tf_ss=20 =3D 16}) at /usr/src/sys/amd64/amd64/trap.c:360 #10 0xffffffff80589dfb in calltrap () at=20 /usr/src/sys/amd64/amd64/exception.S:168 #11 0xffffffff8063ca7f in wi_pccard_products () #12 0x0000000000000100 in ?? () #13 0xffffffffb4400960 in ?? () #14 0xffffffff804b823a in kdebug_mbuf (m0=3D0x0) at=20 /usr/src/sys/netipsec/key_debug.c:670 #15 0xffffffff80442d60 in raw_usend (so=3D0x0, flags=3D0, m=3D0x0, = nam=3D0x0,=20 control=3D0x0, td=3D0x0) at /usr/src/sys/net/raw_usrreq.c:263 #16 0xffffffff804b8d2a in key_send (so=3D0x0, flags=3D0, m=3D0x0, = nam=3D0x0,=20 control=3D0x0, td=3D0x0) at /usr/src/sys/netipsec/keysock.c:532 #17 0xffffffff803fdde4 in sosend (so=3D0xffffff005f41dc08, addr=3D0x0,=20 uio=3D0xffffffffb4400a80, top=3D0xffffff006076e700, control=3D0x0, = flags=3D0, td=3D0xffffff005ec8d980) at /usr/src/sys/kern/uipc_socket.c:829 #18 0xffffffff80404d54 in kern_sendit (td=3D0xffffff005ec8d980, s=3D5,=20 mp=3D0xffffffffb4400b50, flags=3D0, control=3D0x0, segflg=3D16) at /usr/src/sys/kern/uipc_syscalls.c:772 #19 0xffffffff80405f16 in sendit (td=3D0xffffff005ec8d980, s=3D5,=20 mp=3D0xffffffffb4400b50, flags=3D0) at = /usr/src/sys/kern/uipc_syscalls.c:712 #20 0xffffffff804062d4 in sendto (td=3D0x0, uap=3D0x0) at=20 /usr/src/sys/kern/uipc_syscalls.c:830 #21 0xffffffff8059cc72 in syscall (frame=3D {tf_rdi =3D 5, tf_rsi =3D 5677936, tf_rdx =3D 16, tf_rcx =3D 0, = tf_r8 =3D 0,=20 tf_r9 =3D 0, tf_rax =3D 133, tf_rbx =3D 5677952, tf_rbp =3D 2, tf_r10 = =3D 4,=20 tf_r11 =3D 582, tf_r12 =3D 5677936, tf_r13 =3D 7, tf_r14 =3D 5, tf_r15 = =3D 0,=20 tf_trapno =3D 12, tf_addr =3D 4292816, tf_flags =3D 0, tf_err =3D 2, = tf_rip =3D=20 34372796060, tf_cs =3D 43, tf_rflags =3D 582, tf_rsp =3D = 140737488349928,=20 tf_ss =3D 35}) at /usr/src/sys/amd64/amd64/trap.c:797 #22 0xffffffff80589f98 in Xfast_syscall () at=20 /usr/src/sys/amd64/amd64/exception.S:270 #23 0x0000000000000005 in ?? () #24 0x000000000056a370 in ?? () #25 0x0000000000000010 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000085 in ?? () #30 0x000000000056a380 in ?? () #31 0x0000000000000002 in ?? () #32 0x0000000000000004 in ?? () #33 0x0000000000000246 in ?? () #34 0x000000000056a370 in ?? () #35 0x0000000000000007 in ?? () #36 0x0000000000000005 in ?? () #37 0x0000000000000000 in ?? () #38 0x000000000000000c in ?? () #39 0x00000000004180d0 in ?? () #40 0x0000000000000000 in ?? () #41 0x0000000000000002 in ?? () #42 0x0000000800c73e9c in ?? () #43 0x000000000000002b in ?? () #44 0x0000000000000246 in ?? () #45 0x00007fffffffeae8 in ?? () #46 0x0000000000000023 in ?? () #47 0x00007fffffff5b50 in ?? () #48 0x0000000000000023 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x000000005f4dd000 in ?? () #58 0x0000000000000001 in ?? () #59 0x0000000000000000 in ?? () #60 0xffffff005e696340 in ?? () #61 0xffffff007b9b74c0 in ?? () #62 0xffffffffb4400260 in ?? () #63 0xffffffffb4400238 in ?? () #64 0xffffff005ec8d980 in ?? () #65 0xffffffff803cd10a in sched_switch (td=3D0x56a380, newtd=3D0x56a370, = flags=3D5) at /usr/src/sys/kern/sched_4bsd.c:973 Previous frame inner to this frame (corrupt stack?) Here is the serial console output from doing '/etc/rc.d/ipsec start'=20 with some rules in /etc/ipsec.conf Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0xffffffff3489ab9a fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xffffffff804b8248 stack pointer =3D 0x10:0xffffffffb43e2850 frame pointer =3D 0x10:0xffffffffb43e2950 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 615 (setkey) [thread pid 615 tid 100159 ] Stopped at kdebug_mbuf+0x88: db> panic panic: from debugger cpuid =3D 0 Uptime: 14m39s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 = 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695=20 1679 1663 16k Dump complete tank# kgdb kernel.debug /usr/crash/vmcore.8 kgdb kernel.debug /usr/crash/vmcore.8 [GDB will not be able to debug user-mode threads:=20 /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain=20 conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: fff804b8248 stack pointer =3D 0x10:0xffffffffb43e2850 frame pointer =3D 0x10:0xffffffffb43e2950 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 615 (setkey) panic: from debugger cpuid =3D 0 Uptime: 14m39s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919 = 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695=20 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471=20 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247=20 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023=20 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 = 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447=20 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159=20 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); (kgdb) list 167 static __inline struct thread * 168 __curthread(void) 169 { 170 struct thread *td; 171 172 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); 173 return (td); 174 } 175 #define curthread (__curthread()) 176 (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0xffffffff803b8ccc in boot (howto=3D260) at=20 /usr/src/sys/kern/kern_shutdown.c:399 #2 0xffffffff803b876b in panic (fmt=3D0xffffffff805faac2 "from = debugger")=20 at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xffffffff801aa1c2 in db_panic (addr=3D0, have_addr=3D0, count=3D0,=20 modif=3D0x0) at /usr/src/sys/ddb/db_command.c:435 #4 0xffffffff801aa705 in db_command_loop () at=20 /usr/src/sys/ddb/db_command.c:349 #5 0xffffffff801ac573 in db_trap (type=3D-1270995488, code=3D0) at=20 /usr/src/sys/ddb/db_main.c:221 #6 0xffffffff803d5799 in kdb_trap (type=3D12, code=3D0,=20 tf=3D0xffffffffb43e27a0) at /usr/src/sys/kern/subr_kdb.c:473 #7 0xffffffff8059bf0e in trap_fatal (frame=3D0xffffffffb43e27a0,=20 eva=3D18446742975772514688) at /usr/src/sys/amd64/amd64/trap.c:656 #8 0xffffffff8059c2a3 in trap_pfault (frame=3D0xffffffffb43e27a0,=20 usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:581 #9 0xffffffff8059c4b9 in trap (frame=3D {tf_rdi =3D -2140943745, tf_rsi =3D 256, tf_rdx =3D -1270994592, = tf_rcx=20 =3D -2142535110, tf_r8 =3D 64, tf_r9 =3D -1097937036928, tf_rax =3D 0, = tf_rbx =3D=20 2152432187, tf_rbp =3D -1270994608, tf_r10 =3D -2139154144, tf_r11 =3D=20 -1270994432, tf_r12 =3D 57, tf_r13 =3D 0, tf_r14 =3D 0, tf_r15 =3D 0, = tf_trapno=20 =3D 12, tf_addr =3D -3413529702, tf_flags =3D -2140901446, tf_err =3D 0, = tf_rip=20 =3D -2142535096, tf_cs =3D 8, tf_rflags =3D 66178, tf_rsp =3D = -1270994848, tf_ss=20 =3D 16}) at /usr/src/sys/amd64/amd64/trap.c:360 #10 0xffffffff80589dfb in calltrap () at=20 /usr/src/sys/amd64/amd64/exception.S:168 #11 0xffffffff8063ca7f in wi_pccard_products () #12 0x0000000000000100 in ?? () #13 0xffffffffb43e2960 in ?? () #14 0xffffffff804b823a in kdebug_mbuf (m0=3D0x0) at=20 /usr/src/sys/netipsec/key_debug.c:670 #15 0xffffffff80442d60 in raw_usend (so=3D0x0, flags=3D0, m=3D0x0, = nam=3D0x0,=20 control=3D0x0, td=3D0x0) at /usr/src/sys/net/raw_usrreq.c:263 #16 0xffffffff804b8d2a in key_send (so=3D0x0, flags=3D0, m=3D0x0, = nam=3D0x0,=20 control=3D0x0, td=3D0x0) at /usr/src/sys/netipsec/keysock.c:532 #17 0xffffffff803fdde4 in sosend (so=3D0xffffff005ef219a0, addr=3D0x0,=20 uio=3D0xffffffffb43e2a80, top=3D0xffffff00608a0e00, control=3D0x0, = flags=3D0, td=3D0xffffff005dda5980) at /usr/src/sys/kern/uipc_socket.c:829 #18 0xffffffff80404d54 in kern_sendit (td=3D0xffffff005dda5980, s=3D4,=20 mp=3D0xffffffffb43e2b50, flags=3D0, control=3D0x0, segflg=3D16) at /usr/src/sys/kern/uipc_syscalls.c:772 #19 0xffffffff80405f16 in sendit (td=3D0xffffff005dda5980, s=3D4,=20 mp=3D0xffffffffb43e2b50, flags=3D0) at = /usr/src/sys/kern/uipc_syscalls.c:712 #20 0xffffffff804062d4 in sendto (td=3D0x0, uap=3D0x0) at=20 /usr/src/sys/kern/uipc_syscalls.c:830 #21 0xffffffff8059cc72 in syscall (frame=3D {tf_rdi =3D 4, tf_rsi =3D 5320768, tf_rdx =3D 16, tf_rcx =3D 0, = tf_r8 =3D 0,=20 tf_r9 =3D 0, tf_rax =3D 133, tf_rbx =3D 5320784, tf_rbp =3D 0, tf_r10 = =3D 4,=20 tf_r11 =3D 5320704, tf_r12 =3D 5320768, tf_r13 =3D 7, tf_r14 =3D 4, = tf_r15 =3D 0,=20 tf_trapno =3D 12, tf_addr =3D 5320704, tf_flags =3D 0, tf_err =3D 2, = tf_rip =3D=20 34367663772, tf_cs =3D 43, tf_rflags =3D 514, tf_rsp =3D = 140737488349848,=20 tf_ss =3D 35}) at /usr/src/sys/amd64/amd64/trap.c:797 #22 0xffffffff80589f98 in Xfast_syscall () at=20 /usr/src/sys/amd64/amd64/exception.S:270 #23 0x0000000000000004 in ?? () #24 0x0000000000513040 in ?? () #25 0x0000000000000010 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000085 in ?? () #30 0x0000000000513050 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000004 in ?? () #33 0x0000000000513000 in ?? () #34 0x0000000000513040 in ?? () #35 0x0000000000000007 in ?? () #36 0x0000000000000004 in ?? () #37 0x0000000000000000 in ?? () #38 0x000000000000000c in ?? () #39 0x0000000000513000 in ?? () #40 0x0000000000000000 in ?? () ---Type to continue, or q to quit--- #41 0x0000000000000002 in ?? () #42 0x000000080078ee9c in ?? () #43 0x000000000000002b in ?? () #44 0x0000000000000202 in ?? () #45 0x00007fffffffea98 in ?? () #46 0x0000000000000023 in ?? () #47 0x00007fffffffd4d8 in ?? () #48 0x0000000000000023 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x000000005f9ba000 in ?? () #58 0x0000000000000001 in ?? () #59 0x0000000000000000 in ?? () #60 0xffffff005e4aa9c0 in ?? () #61 0xffffff007b9b74c0 in ?? () #62 0xffffffffb43e2260 in ?? () #63 0xffffffffb43e2238 in ?? () #64 0xffffff005dda5980 in ?? () #65 0xffffffff803cd10a in sched_switch (td=3D0x513050, newtd=3D0x513040, = flags=3D4) at /usr/src/sys/kern/sched_4bsd.c:973 Previous frame inner to this frame (corrupt stack?) Here is my dmesg for the Dell 1850 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 6.0-BETA4 #0: Fri Sep 16 01:52:30 UTC 2005 root@tank:/usr/obj/usr/src/sys/GENERIC_IPSEC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf43 Stepping =3D 3 =20 Features=3D0xbfebfbff Features2=3D0x641d> AMD Features=3D0x20100800 Hyperthreading: 2 logical CPUs real memory =3D 2147221504 (2047 MB) avail memory =3D 2062241792 (1966 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic1: WARNING: intbase 32 !=3D expected base 24 ioapic2: Changing APIC ID to 4 ioapic2: WARNING: intbase 64 !=3D expected base 56 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 3 on acpi0 pci_link2: irq 7 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 5 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 amr0: mem=20 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on = pci2 amr0: Firmware 521S, BIOS H430, 256MB RAM pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 4.0 on pci0 pci4: on pcib4 pcib5: at device 0.0 on pci4 pci5: on pcib5 em0: port=20 0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 16 at device 4.0 on pci5 em0: Ethernet address: 00:0e:0c:73:d4:f2 em0: Speed:N/A Duplex:N/A em1: port=20 0xec80-0xecbf mem 0xdfac0000-0xdfadffff irq 17 at device 4.1 on pci5 em1: Ethernet address: 00:0e:0c:73:d4:f3 em1: Speed:N/A Duplex:N/A pcib6: at device 0.2 on pci4 pci6: on pcib6 pcib7: at device 5.0 on pci0 pci7: on pcib7 pcib8: at device 0.0 on pci7 pci8: on pcib8 em2: port=20 0xdcc0-0xdcff mem 0xdf7e0000-0xdf7fffff irq 64 at device 7.0 on pci8 em2: Ethernet address: 00:14:22:15:ff:4b em2: Speed:N/A Duplex:N/A pcib9: at device 0.2 on pci7 pci9: on pcib9 em3: port=20 0xccc0-0xccff mem 0xdf5e0000-0xdf5fffff irq 65 at device 8.0 on pci9 em3: Ethernet address: 00:14:22:15:ff:4c em3: Speed:N/A Duplex:N/A pcib10: at device 6.0 on pci0 pci10: on pcib10 uhci0: port 0xace0-0xacff=20 irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xacc0-0xacdf=20 irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xaca0-0xacbf=20 irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdff00000-0xdff003ff irq = 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 2 ports with 2 removable, self powered pcib11: at device 30.0 on pci0 pci11: on pcib11 pci11: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port=20 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = acpi0 fdc0: [FAST] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on=20 acpi0 sio0: type 16550A, console orm0: at iomem=20 0xc0000-0xcafff,0xcb000-0xcbfff,0xce800-0xcf7ff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, = addr 2 Timecounters tick every 1.000 msec Fast IPsec: Initialized Security Association Processing. acd0: DVDROM at ata0-master UDMA33 amrd0: on amr0 amrd0: 139900MB (286515200 sectors) RAID 1 (optimal) ses0 at amr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/amrd0s1a WARNING: / was not properly dismounted em2: link state changed to UP em3: link state changed to UP Cheers, Mike ------------------------------ _______________________________________________ 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" End of freebsd-amd64 Digest, Vol 119, Issue 5 ********************************************* ------_=_NextPart_001_01C5BB05.6BD48F3A-- From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 21:35:46 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0146C16A41F; Fri, 16 Sep 2005 21:35:46 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86CF643D46; Fri, 16 Sep 2005 21:35:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j8GLZiR9024802; Fri, 16 Sep 2005 17:35:44 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id j8GLZinE089393; Fri, 16 Sep 2005 17:35:44 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id EC3227302F; Fri, 16 Sep 2005 17:35:43 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050916213543.EC3227302F@freebsd-current.sentex.ca> Date: Fri, 16 Sep 2005 17:35:43 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 21:35:46 -0000 TB --- 2005-09-16 19:33:47 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-09-16 19:33:47 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-09-16 19:33:47 - cleaning the object tree TB --- 2005-09-16 19:34:19 - checking out the source tree TB --- 2005-09-16 19:34:19 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-09-16 19:34:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-09-16 19:40:11 - building world (CFLAGS=-O2 -pipe) TB --- 2005-09-16 19:40:11 - cd /src TB --- 2005-09-16 19:40:11 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-09-16 21:11:08 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-09-16 21:11:08 - cd /src TB --- 2005-09-16 21:11:08 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Sep 16 21:11:09 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Sep 16 21:26:56 UTC 2005 TB --- 2005-09-16 21:26:56 - generating LINT kernel config TB --- 2005-09-16 21:26:56 - cd /src/sys/amd64/conf TB --- 2005-09-16 21:26:56 - /usr/bin/make -B LINT TB --- 2005-09-16 21:26:57 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-09-16 21:26:57 - cd /src TB --- 2005-09-16 21:26:57 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Sep 16 21:26:57 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/net/if_spppsubr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/net/if_stf.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/net/if_tun.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/net/if_tap.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/net/if_vlan.c /src/sys/net/if_vlan.c: In function `vlan_start': /src/sys/net/if_vlan.c:540: warning: format argument is not a pointer (arg 2) /src/sys/net/if_vlan.c:540: warning: field width is not type int (arg 3) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-09-16 21:35:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-09-16 21:35:43 - ERROR: failed to build lint kernel TB --- 2005-09-16 21:35:43 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 16 23:39:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B31116A41F; Fri, 16 Sep 2005 23:39:54 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD40143D45; Fri, 16 Sep 2005 23:39:53 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.14]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8GNdjMc096866; Fri, 16 Sep 2005 16:39:45 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <001101c5bb17$e969e3c0$0a00a8c0@rodan> From: "Jeff D. Hamann" To: , Date: Fri, 16 Sep 2005 16:39:36 -0700 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Cc: Subject: mounting usb on fbsd6beta4... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2005 23:39:54 -0000 Okay, I thought I give mounting my usb so I inserted it one of the usb ports. There are 8 total on this machine; six are actually wired to a port. I'm not removing it as it reboots my system and I'm determined to get this thing to work! Sep 17 16:24:46 bobby kernel: umass0: vendor 0x090a product 0x1001, rev 1.10/1.00, addr 2 Sep 17 16:24:46 bobby kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Sep 17 16:24:46 bobby kernel: da0: Removable Direct Access SCSI-0 device Sep 17 16:24:46 bobby kernel: da0: 1.000MB/s transfers Sep 17 16:24:46 bobby kernel: da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) Sep 17 16:24:46 bobby kernel: da1 at umass-sim0 bus 0 target 0 lun 1 Sep 17 16:24:46 bobby kernel: da1: Removable Direct Access SCSI-0 device Sep 17 16:24:46 bobby kernel: da1: 1.000MB/s transfers Sep 17 16:24:46 bobby kernel: da1: 250MB (512000 512 byte sectors: 64H 32S/T 250C) Sep 17 16:24:46 bobby kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 bobby# I don't recall having any da* devices in my /dev so I've included all the listed devices in /dev which are: bobby# ls -la /dev total 4 dr-xr-xr-x 4 root wheel 512 Dec 31 1969 . drwxr-xr-x 22 root wheel 512 Sep 17 14:27 .. crw-r----- 1 root operator 10, 89 Sep 17 14:26 acd0 crw-r--r-- 1 root wheel 10, 19 Sep 17 14:26 acpi crw-r----- 1 root operator 10, 88 Sep 17 14:26 ad0 crw-r----- 1 root operator 10, 90 Sep 17 14:26 ad0s1 crw-r----- 1 root operator 10, 91 Sep 17 07:26 ad0s1a crw-r----- 1 root operator 10, 92 Sep 17 07:26 ad0s1b crw-r----- 1 root operator 10, 93 Sep 17 14:26 ad0s1c crw-r----- 1 root operator 10, 94 Sep 17 07:26 ad0s1d crw-r----- 1 root operator 10, 95 Sep 17 07:26 ad0s1e crw-r----- 1 root operator 10, 80 Sep 17 07:26 ad0s1f crw------- 1 root operator 10, 18 Sep 17 14:26 ata crw------- 1 root wheel 10, 43 Sep 17 14:26 atkbd0 crw-rw-rw- 1 root wheel 10, 46 Sep 17 14:26 bpsm0 crw------- 1 root wheel 10, 4 Sep 17 16:24 console crw------- 1 root wheel 10, 64 Sep 17 14:26 consolectl crw-rw-rw- 1 root wheel 10, 5 Sep 17 14:26 ctty crw-rw---- 1 uucp dialer 10, 34 Sep 17 14:26 cuad0 crw-rw---- 1 uucp dialer 10, 35 Sep 17 14:26 cuad0.init crw-rw---- 1 uucp dialer 10, 36 Sep 17 14:26 cuad0.lock crw-rw---- 1 uucp dialer 10, 56 Sep 17 14:26 cuad1 crw-rw---- 1 uucp dialer 10, 57 Sep 17 14:26 cuad1.init crw-rw---- 1 uucp dialer 10, 58 Sep 17 14:26 cuad1.lock crw------- 1 root wheel 10, 13 Sep 17 14:26 devctl cr-------- 1 root wheel 10, 69 Sep 17 14:26 devstat lrwxr-xr-x 1 root wheel 11 Sep 17 07:26 dumpdev -> /dev/ad0s1b dr-xr-xr-x 2 root wheel 512 Dec 31 1969 fd crw-r----- 1 root operator 10, 71 Sep 17 14:26 fd0 crw------- 1 root wheel 10, 6 Sep 17 14:26 fido crw-r----- 1 root operator 10, 12 Sep 17 14:26 geom.ctl crw------- 1 root wheel 10, 16 Sep 17 14:26 io lrwxr-xr-x 1 root wheel 6 Dec 31 1969 kbd0 -> atkbd0 crw------- 1 root wheel 10, 0 Sep 17 14:26 klog crw-r----- 1 root kmem 10, 31 Sep 17 14:26 kmem lrwxr-xr-x 1 root wheel 12 Sep 17 14:27 log -> /var/run/log crw------- 1 root wheel 10, 61 Sep 17 14:26 lpt0 crw------- 1 root wheel 10, 62 Sep 17 14:26 lpt0.ctl crw------- 1 root wheel 10, 68 Sep 17 14:26 mdctl crw-r----- 1 root kmem 10, 30 Sep 17 14:26 mem dr-xr-xr-x 2 root wheel 512 Dec 31 1969 net lrwxr-xr-x 1 root wheel 7 Dec 31 1969 net1 -> net/rl0 lrwxr-xr-x 1 root wheel 9 Dec 31 1969 net2 -> net/plip0 lrwxr-xr-x 1 root wheel 7 Dec 31 1969 net3 -> net/lo0 crw------- 1 root wheel 10, 11 Sep 17 14:26 network crw------- 1 root wheel 10, 65 Sep 17 14:26 nfs4 crw------- 1 root kmem 10, 7 Sep 17 14:26 nfslock crw-rw-rw- 1 root wheel 10, 14 Sep 17 16:22 null crw------- 1 root operator 10, 83 Sep 17 14:26 pass0 crw------- 1 root operator 10, 84 Sep 17 14:26 pass1 crw-r--r-- 1 root wheel 10, 1 Sep 17 14:26 pci crw------- 1 root wheel 10, 63 Sep 17 14:26 ppi0 crw-rw-rw- 1 root wheel 10, 45 Sep 17 14:26 psm0 crw-rw-rw- 1 root wheel 10, 81 Sep 17 16:27 ptyp0 crw-rw-rw- 1 root wheel 10, 2 Sep 17 07:26 random lrwxr-xr-x 1 root wheel 4 Dec 31 1969 stderr -> fd/2 lrwxr-xr-x 1 root wheel 4 Dec 31 1969 stdin -> fd/0 lrwxr-xr-x 1 root wheel 4 Dec 31 1969 stdout -> fd/1 crw------- 1 root wheel 10, 17 Sep 17 14:26 sysmouse crw------- 1 root wheel 10, 47 Sep 17 14:26 ttyd0 crw------- 1 root wheel 10, 32 Sep 17 14:26 ttyd0.init crw------- 1 root wheel 10, 33 Sep 17 14:26 ttyd0.lock crw------- 1 root wheel 10, 37 Sep 17 14:26 ttyd1 crw------- 1 root wheel 10, 38 Sep 17 14:26 ttyd1.init crw------- 1 root wheel 10, 39 Sep 17 14:26 ttyd1.lock crw--w---- 1 hamannj tty 10, 82 Sep 17 16:27 ttyp0 crw------- 1 root wheel 10, 48 Sep 17 14:27 ttyv0 crw------- 1 root wheel 10, 49 Sep 17 14:27 ttyv1 crw------- 1 root wheel 10, 50 Sep 17 14:27 ttyv2 crw------- 1 root wheel 10, 51 Sep 17 14:27 ttyv3 crw------- 1 root wheel 10, 52 Sep 17 14:27 ttyv4 crw------- 1 root wheel 10, 53 Sep 17 14:27 ttyv5 crw------- 1 root wheel 10, 54 Sep 17 14:27 ttyv6 crw------- 1 root wheel 10, 55 Sep 17 14:27 ttyv7 crw------- 1 root wheel 10, 72 Sep 17 14:26 ttyv8 crw------- 1 root wheel 10, 73 Sep 17 14:26 ttyv9 crw------- 1 root wheel 10, 74 Sep 17 14:26 ttyva crw------- 1 root wheel 10, 75 Sep 17 14:26 ttyvb crw------- 1 root wheel 10, 76 Sep 17 14:26 ttyvc crw------- 1 root wheel 10, 77 Sep 17 14:26 ttyvd crw------- 1 root wheel 10, 78 Sep 17 14:26 ttyve crw------- 1 root wheel 10, 79 Sep 17 14:26 ttyvf lrwxr-xr-x 1 root wheel 6 Dec 31 1969 urandom -> random crw-rw---- 1 root operator 10, 21 Sep 17 14:26 usb crw-rw---- 1 root operator 10, 20 Sep 17 14:26 usb0 crw-rw---- 1 root operator 10, 22 Sep 17 14:26 usb1 crw-rw---- 1 root operator 10, 23 Sep 17 14:26 usb2 crw-rw---- 1 root operator 10, 40 Sep 17 14:26 usb3 crw------- 1 root operator 10, 70 Sep 17 14:26 xpt0 crw-rw-rw- 1 root wheel 10, 15 Sep 17 14:26 zero bobby# and I know that normally to mount drives, I need to type: bobby# mount -v -t msdos /dev/something-something-something /mnt/usb I've tried using the usb0,1,2,3 devices with no success but since I don't see any da*, I'm not sure how to mount this thing. It's a msdos (fat) formatted drive and it's been used most everywhere. I've tried mounting almost every combination of the following: bobby# mount -v -t msdos /dev/da0s1 /mnt/usb mount_msdosfs: /dev/da0s1: No such file or directory bobby# mount -v -t msdos /dev/usb0s1 /mnt/usb mount_msdosfs: /dev/usb0s1: No such file or directory bobby# mount -v -t msdos /dev/usb0 /mnt/usb mount_msdosfs: /dev/usb0: Block device required bobby# and just can't get it to go. This is really getting me down on the beta6 stuff. Will I have this kind of trouble when I attempt to use a usb keyboard and mouse? can I use a wireless usb kb and mouse? should I even try or would spending the $ be a waste? Whoa..... After about six minutes the following popped up on my screen...I checked the /var/log/messages file and found... Sep 17 16:30:21 bobby kernel: Opened disk da0 -> 5 Sep 17 16:35:47 bobby kernel: Opened disk da0 -> 5 so, bobby# mount -v -t msdos /dev/da0 /mnt/usb mount_msdosfs: /dev/da0: Device busy argh..... Jeff. --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 00:32:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0F5F16A41F; Sat, 17 Sep 2005 00:32:53 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49DB843D46; Sat, 17 Sep 2005 00:32:53 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from rodan ([192.168.0.14]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id j8H0WoMc096982; Fri, 16 Sep 2005 17:32:50 -0700 (PDT) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <000d01c5bb1f$53c92a80$0a00a8c0@rodan> From: "Jeff D. Hamann" To: , Date: Fri, 16 Sep 2005 17:32:42 -0700 Organization: Forest Informatics, Inc. MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Cc: Subject: more weirdness with usb... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jeff D. Hamann" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 00:32:54 -0000 I posted a message that contained some output from dmesg... Before when I would simple get fed up, yank out the usb device, the machine would reboot... After letting the machine sit for about 40 mintues with the usb key in the port, the following messages would scroll by every five minutes or so, Sep 17 16:30:21 bobby kernel: Opened disk da0 -> 5 Sep 17 16:35:47 bobby kernel: Opened disk da0 -> 5 Sep 17 16:41:12 bobby kernel: Opened disk da1 -> 5 Sep 17 16:46:37 bobby kernel: Opened disk da1 -> 5 Sep 17 16:52:02 bobby kernel: Opened disk da1 -> 5 Sep 17 16:58:36 bobby kernel: Opened disk da1 -> 5 Sep 17 17:19:58 bobby kernel: Opened disk da0 -> 5 I got fed up (actually I need the usb key) and pulled it out of the port and this time the machine didn't reboot, but gave the following messages: Sep 17 17:27:55 bobby kernel: umass0: at uhub2 port 2 (addr 2) disconnected Sep 17 17:27:55 bobby kernel: (da0:umass-sim0:0:0:0): lost device Sep 17 17:27:55 bobby kernel: (da0:umass-sim0:0:0:0): removing device entry Sep 17 17:27:55 bobby kernel: (da1:umass-sim0:0:0:1): lost device Sep 17 17:27:55 bobby kernel: (da1:umass-sim0:0:0:1): removing device entry Sep 17 17:27:55 bobby kernel: umass0: detached and this is what was printed out on the screen... umass0: vendor 0x090a product 0x1001, rev 1.10/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: 250MB (512000 512 byte sectors: 64H 32S/T 250C) (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Opened disk da0 -> 5 Opened disk da0 -> 5 Opened disk da1 -> 5 Opened disk da1 -> 5 Opened disk da1 -> 5 Opened disk da1 -> 5 Opened disk da0 -> 5 umass0: at uhub2 port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry umass0: detached bobby# Does this help anyone? I still can't figure out what's going on here.... --- Jeff D. Hamann Forest Informatics, Inc. PO Box 1421 Corvallis, Oregon USA 97339-1421 541-754-1428 jeff.hamann@forestinformatics.com www.forestinformatics.com From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 01:20:16 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC4B16A420 for ; Sat, 17 Sep 2005 01:20:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7949E43D4C for ; Sat, 17 Sep 2005 01:20:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8H1KEFo021800 for ; Sat, 17 Sep 2005 01:20:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8H1KERj021799; Sat, 17 Sep 2005 01:20:14 GMT (envelope-from gnats) Resent-Date: Sat, 17 Sep 2005 01:20:14 GMT Resent-Message-Id: <200509170120.j8H1KERj021799@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, ejwalt Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AA3816A41F for ; Sat, 17 Sep 2005 01:14:32 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 363C343D45 for ; Sat, 17 Sep 2005 01:14:32 +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 j8H1EWZD086131 for ; Sat, 17 Sep 2005 01:14:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j8H1EWUD086130; Sat, 17 Sep 2005 01:14:32 GMT (envelope-from nobody) Message-Id: <200509170114.j8H1EWUD086130@www.freebsd.org> Date: Sat, 17 Sep 2005 01:14:32 GMT From: ejwalt To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/86244: dfi nf4 ulta-d X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 01:20:16 -0000 >Number: 86244 >Category: amd64 >Synopsis: dfi nf4 ulta-d >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sat Sep 17 01:20:14 GMT 2005 >Closed-Date: >Last-Modified: >Originator: ejwalt >Release: latest >Organization: ecq >Environment: none yet >Description: Hello I am glad to say that It's been 6months since I had to use Winblows. I have been on osX latly and soon will switch to Bsd. I wanted to know if the DFI lanparty nf4 ultra-d can run bsd it wasnt on the list but it said to ask if my board wasnt there thanks >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 06:14:18 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4034816A420; Sat, 17 Sep 2005 06:14:18 +0000 (GMT) (envelope-from fujita@soum.co.jp) Received: from gate.soum.co.jp (gate.soum.co.jp [202.221.40.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86AE43D46; Sat, 17 Sep 2005 06:14:16 +0000 (GMT) (envelope-from fujita@soum.co.jp) Received: from mail.soum.co.jp (hoth.soum.co.jp [IPv6:2001:240:c4:1:203:baff:fea1:6471]) by gate.soum.co.jp (8.13.3/8.13.3) with ESMTP id j8H6EESM061104; Sat, 17 Sep 2005 15:14:15 +0900 (JST) (envelope-from fujita@soum.co.jp) Received: from localhost (luke.soum.co.jp [172.19.2.3]) by mail.soum.co.jp (8.13.4/8.13.4) with ESMTP id j8H6E9JF014784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 17 Sep 2005 15:14:09 +0900 (JST) Date: Sat, 17 Sep 2005 15:14:08 +0900 (JST) Message-Id: <20050917.151408.46626816.fujita@soum.co.jp> To: freebsd-amd64@freebsd.org, freebsd-current@freebsd.org From: FUJITA Kazutoshi In-Reply-To: <20050902.103259.08238152.fujita@soum.co.jp> <20050902.105311.24457489.fujita@soum.co.jp> References: <17166.21317.705489.47055@grasshopper.cs.duke.edu> <20050902.100210.123568240.fujita@soum.co.jp> <20050902.103259.08238152.fujita@soum.co.jp> X-Face: "; PnIN=f2{%Xj2PnI+zHd.39&Cn1)}br_7:N|2[CbS87Du6#6?|UeqX'&OfyZG-mX#'5T>k/~8X(F,2Mb_pNd8]3Cb1u[kSZjF}J+#`L5(g); List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 06:14:18 -0000 ----Next_Part(Sat_Sep_17_15_14_08_2005_164)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I have AMD64 -CURRENT box. Motherboard is ASUS A8N-E(chipset is nForce4). It has 4GB Memory. There is some trouble with GENERIC kernel, but specifying MAXMEM, such as options MAXMEM=(2*1024*1024) in kernel configuration solve that. What is the problem? [trouble 1] From: FUJITA Kazutoshi Subject: bge problem Date: Fri, 02 Sep 2005 10:32:59 +0900 (JST) > > nve never works on my amd64 box. > > It links up successfully, but... > > > > nve0: device timeout (5) > > nve0: link state changed to DOWN > > nve0: link state changed to UP > > nve0: device timeout (8) > > nve0: link state changed to DOWN > > nve0: link state changed to UP > > > > > > my motherboard is ASUS A8N-E. > > on my amd64 box, bge (at PCI slot) also never works. > it seems same problem as nve. > > > bge0: link state changed to UP > bge0: watchdog timeout -- resetting > bge0: link state changed to DOWN > bge0: link state changed to UP > bge0: watchdog timeout -- resetting > bge0: link state changed to DOWN > bge0: link state changed to UP > bge0: watchdog timeout -- resetting > bge0: link state changed to DOWN > > > bge0: mem 0xd8000000-0xd800ffff irq 16 at device 6.0 on pci5 > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd8000000 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge0: bpf attached > bge0: Ethernet address: 00:09:5b:8e:63:2f > bge0: [MPSAFE] > > > of course, the bge works well on my i386 box. > any suggestions ? [trouble 2] From: FUJITA Kazutoshi Subject: uhub1: device problem (SHORT_XFER), disabling port 1 Date: Fri, 02 Sep 2005 10:53:11 +0900 (JST) > my axe never works on my amd64 box with 7.0-current. > > insert axe to the usb port, following message is out. > > uhub1: device problem (SHORT_XFER), disabling port 1 > > > of course, > the axe works well on my i386 laptop(ThinkPad T43) > with 7.0-current. Regards, ----Next_Part(Sat_Sep_17_15_14_08_2005_164)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT #15: Sat Sep 17 14:16:11 JST 2005 fujita@oscar:/usr/obj/usr/src/sys/OSCAR WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80a62000. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff80a621d0. Preloaded elf obj module "/boot/kernel/snd_ich.ko" at 0xffffffff80a627f8. Preloaded elf obj module "/boot/kernel/smbus.ko" at 0xffffffff80a62d60. Preloaded elf obj module "/boot/kernel/smb.ko" at 0xffffffff80a631c8. Preloaded elf obj module "/boot/kernel/ichsmb.ko" at 0xffffffff80a63630. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193257 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2412374352 Hz CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2412.37-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> Hyperthreading: 2 logical CPUs L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 5368709120 (5120 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000b61000 - 0x00000000b69bffff, 3051745280 bytes (745055 pages) 0x0000000100000000 - 0x000000013ffebfff, 1073659904 bytes (262124 pages) avail memory = 4115156992 (3924 MB) APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 2 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high MADT: Interrupt override: source 14, irq 14 ioapic0: intpin 14 trigger: edge ioapic0: intpin 14 polarity: high MADT: Interrupt override: source 15, irq 15 ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI -> LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 wlan: <802.11 Link Layer> random: nfslock: pseudo-device mem: io: null: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80004004 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=058000] [hdr=00] is there (id=005e10de) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 acpi0: Power Button (fixed) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 pci_link0: on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: irq 3 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: irq 11 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: irq 3 on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: irq 5 on acpi0 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: on acpi0 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: on acpi0 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: on acpi0 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: on acpi0 pci_link12: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: irq 5 on acpi0 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: irq 11 on acpi0 pci_link14: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: on acpi0 pci_link15: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link16: irq 0 on acpi0 pci_link16: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link17: irq 0 on acpi0 pci_link17: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link17: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link17: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link18: irq 0 on acpi0 pci_link18: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link18: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link18: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link19: irq 0 on acpi0 pci_link19: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link20: irq 16 on acpi0 pci_link20: Links after initial probe: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after initial validation: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link21: irq 0 on acpi0 pci_link21: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link21: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link21: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: irq 0 on acpi0 pci_link22: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: irq 0 on acpi0 pci_link23: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: irq 0 on acpi0 pci_link24: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: irq 0 on acpi0 pci_link25: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: irq 0 on acpi0 pci_link26: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: irq 0 on acpi0 pci_link27: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: irq 0 on acpi0 pci_link28: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: irq 0 on acpi0 pci_link29: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: irq 0 on acpi0 pci_link30: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: irq 0 on acpi0 pci_link31: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 ACPI timer: 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x10de, dev=0x005e, revid=0xa3 bus=0, slot=0, func=0 class=05-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0050, revid=0xa3 bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0052, revid=0xa2 bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000e400, size 5, enabled map[20]: type 4, range 32, base 00004c00, size 6, enabled map[24]: type 4, range 32, base 00004c40, size 6, enabled found-> vendor=0x10de, dev=0x005a, revid=0xa2 bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d8104000, size 12, enabled found-> vendor=0x10de, dev=0x005b, revid=0xa3 bus=0, slot=2, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base feb00000, size 8, enabled found-> vendor=0x10de, dev=0x0059, revid=0xa2 bus=0, slot=4, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000dc00, size 8, enabled map[14]: type 4, range 32, base 0000e000, size 8, enabled map[18]: type 1, range 32, base d8103000, size 12, enabled pcib0: matched entry for 0.4.INTA (src \\_SB_.PCI0.APCJ:0) pci_link24: Picked IRQ 20 with weight 0 pcib0: slot 4 INTA routed to irq 20 via \\_SB_.PCI0.APCJ found-> vendor=0x10de, dev=0x0053, revid=0xf2 bus=0, slot=6, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000f000, size 4, enabled found-> vendor=0x10de, dev=0x0054, revid=0xf3 bus=0, slot=7, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 000009f0, size 3, enabled map[14]: type 4, range 32, base 00000bf0, size 2, enabled map[18]: type 4, range 32, base 00000970, size 3, enabled map[1c]: type 4, range 32, base 00000b70, size 2, enabled map[20]: type 4, range 32, base 0000d800, size 4, enabled map[24]: type 1, range 32, base d8102000, size 12, enabled pcib0: matched entry for 0.7.INTA (src \\_SB_.PCI0.APSI:0) pci_link29: Picked IRQ 21 with weight 0 pcib0: slot 7 INTA routed to irq 21 via \\_SB_.PCI0.APSI found-> vendor=0x10de, dev=0x0055, revid=0xf3 bus=0, slot=8, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 000009e0, size 3, enabled map[14]: type 4, range 32, base 00000be0, size 2, enabled map[18]: type 4, range 32, base 00000960, size 3, enabled map[1c]: type 4, range 32, base 00000b60, size 2, enabled map[20]: type 4, range 32, base 0000c400, size 4, enabled map[24]: type 1, range 32, base d8101000, size 12, enabled pcib0: matched entry for 0.8.INTA (src \\_SB_.PCI0.APSJ:0) pci_link30: Picked IRQ 22 with weight 0 pcib0: slot 8 INTA routed to irq 22 via \\_SB_.PCI0.APSJ found-> vendor=0x10de, dev=0x005c, revid=0xa2 bus=0, slot=9, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x0057, revid=0xa3 bus=0, slot=10, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=3 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d8100000, size 12, enabled map[14]: type 4, range 32, base 0000b000, size 3, enabled pcib0: matched entry for 0.10.INTA (src \\_SB_.PCI0.APCH:0) pci_link23: Picked IRQ 23 with weight 0 pcib0: slot 10 INTA routed to irq 23 via \\_SB_.PCI0.APCH found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=12, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=13, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=14, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 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) pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 ichsmb0: port 0xe400-0xe41f,0x4c00-0x4c3f,0x4c40-0x4c7f at device 1.1 on pci0 ichsmb0: Reserved 0x40 bytes for rid 0x20 type 4 at 0x4c00 pcib0: matched entry for 0.1.INTA (src \\_SB_.PCI0.APCS:0) pci_link26: Picked IRQ 20 with weight 1 pcib0: slot 1 INTA routed to irq 20 via \\_SB_.PCI0.APCS ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 ohci0: mem 0xd8104000-0xd8104fff at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd8104000 pcib0: matched entry for 0.2.INTA (src \\_SB_.PCI0.APCF:0) pci_link21: Picked IRQ 21 with weight 1 pcib0: slot 2 INTA routed to irq 21 via \\_SB_.PCI0.APCF ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff at device 2.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfeb00000 pcib0: matched entry for 0.2.INTB (src \\_SB_.PCI0.APCL:0) pci_link27: Picked IRQ 22 with weight 1 pcib0: slot 2 INTB routed to irq 22 via \\_SB_.PCI0.APCL ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered pcm0: port 0xdc00-0xdcff,0xe000-0xe0ff mem 0xd8103000-0xd8103fff irq 20 at device 4.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xdc00 pcm0: Reserved 0x100 bytes for rid 0x14 type 4 at 0xe000 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features 5 bit master volume, no 3D Stereo Enhancement pcm0: Primary codec extended features double rate PCM, reserved 1, center DAC, surround DAC, LFE DAC, reserved 5 pcm0: ac97 codec dac ready count: 0 pcm0: sndbuf_setmap b69aa000, 4000; 0xffffffffb4abf000 -> b69aa000 pcm0: sndbuf_setmap b69a6000, 4000; 0xffffffffb4ac3000 -> b69a6000 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=60 ostat1=70 ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata0: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 ata0: reset tp2 stat0=20 stat1=30 devices=0x0 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: [MPSAFE] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd8102000-0xd8102fff irq 21 at device 7.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd800 atapci1: [MPSAFE] atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xd8102000 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata2: SATA connect status=00000000 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata3: SATA connect status=00000000 ata3: [MPSAFE] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd8101000-0xd8101fff irq 22 at device 8.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc400 atapci2: [MPSAFE] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xd8101000 atapci2: [MPSAFE] ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata4: SATA connect ready time=0ms ata4: sata_connect devices=0x1 ata4: [MPSAFE] ata5: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata5: SATA connect ready time=0ms ata5: sata_connect devices=0x1 ata5: [MPSAFE] pcib1: at device 9.0 on pci0 pcib1: secondary bus 5 pcib1: subordinate bus 5 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xd8000000-0xd80fffff pcib1: prefetched decode 0xfff00000-0xfffff pcib1: Subtractively decoded bridge. ACPI: Found matching pin for 0.7.INTA at func 0: 21 pci_link17: BIOS IRQ 21 for 0.7.INTA is invalid ACPI: Found matching pin for 0.8.INTA at func 0: 22 pci_link18: BIOS IRQ 22 for 0.8.INTA is invalid ACPI: Found matching pin for 0.10.INTA at func 0: 23 pci_link18: BIOS IRQ 23 for 0.10.INTA is invalid pci5: on pcib1 pci5: physical bus=5 found-> vendor=0x173b, dev=0x03ea, revid=0x15 bus=5, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=3 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base d8000000, size 16, enabled pcib1: (null) requested memory range 0xd8000000-0xd800ffff: good pcib1: matched entry for 5.7.INTA (src \\_SB_.PCI0.APC2:0) pci_link17: Picked IRQ 17 with weight 0 pcib1: slot 7 INTA routed to irq 17 via \\_SB_.PCI0.APC2 bge0: mem 0xd8000000-0xd800ffff irq 17 at device 7.0 on pci5 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd8000000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:09:5b:8e:63:2f bge0: [MPSAFE] nve0: port 0xb000-0xb007 mem 0xd8100000-0xd8100fff irq 23 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd8100000 nve0: Ethernet address 00:13:d4:36:79:07 miibus1: on nve0 ukphy0: on miibus1 ukphy0: OUI 0x005043, model 0x000c, rev. 2 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: bpf attached nve0: Ethernet address: 00:13:d4:36:79:07 nve0: [GIANT-LOCKED] pcib2: at device 11.0 on pci0 pcib2: secondary bus 4 pcib2: subordinate bus 4 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xfff00000-0xfffff pcib2: prefetched decode 0xfff00000-0xfffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR3 - AE_NOT_FOUND pci4: on pcib2 pci4: physical bus=4 pcib3: at device 12.0 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: memory decode 0xfff00000-0xfffff pcib3: prefetched decode 0xfff00000-0xfffff pcib3: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR2 - AE_NOT_FOUND pci3: on pcib3 pci3: physical bus=3 pcib4: at device 13.0 on pci0 pcib4: secondary bus 2 pcib4: subordinate bus 2 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xfff00000-0xfffff pcib4: prefetched decode 0xfff00000-0xfffff pcib4: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR1 - AE_NOT_FOUND pci2: on pcib4 pci2: physical bus=2 pcib5: at device 14.0 on pci0 pcib5: secondary bus 1 pcib5: subordinate bus 1 pcib5: I/O decode 0xf000-0xfff pcib5: memory decode 0xd0000000-0xd7ffffff pcib5: prefetched decode 0xc0000000-0xcfffffff pcib5: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR0 - AE_NOT_FOUND pci1: on pcib5 pci1: physical bus=1 found-> vendor=0x10de, dev=0x0141, revid=0xa2 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 32, base d0000000, size 26, enabled pcib5: (null) requested memory range 0xd0000000-0xd3ffffff: good map[14]: type 3, range 64, base c0000000, size 28, enabled pcib5: (null) requested memory range 0xc0000000-0xcfffffff: good map[1c]: type 1, range 64, base d4000000, size 24, enabled pcib5: (null) requested memory range 0xd4000000-0xd4ffffff: good pcib0: matched entry for 0.14.INTA (src \\_SB_.PCI0.APC3:0) pci_link18: Picked IRQ 18 with weight 0 pcib0: slot 14 INTA routed to irq 18 via \\_SB_.PCI0.APC3 pcib5: slot 0 INTA is routed to irq 18 pci1: at device 0.0 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x829 0x839 0x829 0x829 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 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 Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 4: ioport 0x4c00 alloc failed ahc_isa_probe 13: ioport 0xdc00 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 0xc0000-0xcefff,0xd0000-0xd3fff pnpid ORM0000 on isa0 fb: new array size 4 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x8a9 0x8a9 0x8a9 0x8a9 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 233016 -> 100000 procfs registered linprocfs registered lapic: Divisor 2, Frequency 100515309 hz Timecounter "TSC" frequency 2412374352 Hz quality -100 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire acd0: setting PIO4 on nVidia nForce4 chip acd0: setting UDMA66 on nVidia nForce4 chip acd0: DVDR drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 6890KB/s (6890KB/s), 1419KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 286188MB at ata4-master SATA150 ad8: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed ad8: LSI (v2) check1 failed ad8: FreeBSD check1 failed ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad10: 286188MB at ata5-master SATA150 ad10: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue ad10: nVidia check1 failed ad10: Adaptec check1 failed ad10: LSI (v3) check1 failed ad10: LSI (v2) check1 failed ad10: FreeBSD check1 failed pcm0: measured ac97 link rate at 48007 Hz, will use 48000 Hz ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00040010 LDR: 0x02000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0 GEOM: new disk ad8 GEOM: new disk ad10 Trying to mount root from ufs:/dev/ad8s1a start_init: trying /sbin/init bge0: link state changed to DOWN nve0: link state changed to UP splash: image decoder found: daemon_saver bge0: watchdog timeout -- resetting ----Next_Part(Sat_Sep_17_15_14_08_2005_164)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg-MAXMEM=2G.txt" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT #12: Sat Sep 17 08:44:12 JST 2005 fujita@oscar:/usr/obj/usr/src/sys/OSCAR WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80a62000. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff80a621d0. Preloaded elf obj module "/boot/kernel/snd_ich.ko" at 0xffffffff80a627f8. Preloaded elf obj module "/boot/kernel/smbus.ko" at 0xffffffff80a62d60. Preloaded elf obj module "/boot/kernel/smb.ko" at 0xffffffff80a631c8. Preloaded elf obj module "/boot/kernel/ichsmb.ko" at 0xffffffff80a63630. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193257 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2412375335 Hz CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2412.38-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> Hyperthreading: 2 logical CPUs L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 2147483648 (2048 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000b60000 - 0x000000007c3bbfff, 2072363008 bytes (505948 pages) avail memory = 2062155776 (1966 MB) APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 2 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high MADT: Interrupt override: source 14, irq 14 ioapic0: intpin 14 trigger: edge ioapic0: intpin 14 polarity: high MADT: Interrupt override: source 15, irq 15 ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI -> LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 wlan: <802.11 Link Layer> random: nfslock: pseudo-device mem: io: null: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80004004 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=058000] [hdr=00] is there (id=005e10de) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 acpi0: Power Button (fixed) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 1 func 0 pci_link0: on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: irq 3 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: irq 11 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: irq 3 on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 7 9 10 11 12 14 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: irq 5 on acpi0 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: on acpi0 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: on acpi0 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: on acpi0 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: on acpi0 pci_link12: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: irq 5 on acpi0 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 7 9 10 11 12 14 15 pci_link13: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: irq 11 on acpi0 pci_link14: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 7 9 10 11 12 14 15 pci_link14: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: on acpi0 pci_link15: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link15: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 7 9 10 11 12 14 15 pci_link16: irq 0 on acpi0 pci_link16: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link16: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link17: irq 0 on acpi0 pci_link17: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link17: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link17: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link18: irq 0 on acpi0 pci_link18: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link18: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link18: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link19: irq 0 on acpi0 pci_link19: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link19: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link20: irq 16 on acpi0 pci_link20: Links after initial probe: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after initial validation: Index IRQ Rtd Ref IRQs 0 16 N 0 16 pci_link20: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link21: irq 0 on acpi0 pci_link21: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link21: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link21: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: irq 0 on acpi0 pci_link22: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link22: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: irq 0 on acpi0 pci_link23: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link23: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: irq 0 on acpi0 pci_link24: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link24: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: irq 0 on acpi0 pci_link25: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link25: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: irq 0 on acpi0 pci_link26: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link26: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: irq 0 on acpi0 pci_link27: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: irq 0 on acpi0 pci_link28: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: irq 0 on acpi0 pci_link29: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: irq 0 on acpi0 pci_link30: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: irq 0 on acpi0 pci_link31: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 ACPI timer: 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 1/2 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x10de, dev=0x005e, revid=0xa3 bus=0, slot=0, func=0 class=05-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0050, revid=0xa3 bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0052, revid=0xa2 bus=0, slot=1, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000e400, size 5, enabled map[20]: type 4, range 32, base 00004c00, size 6, enabled map[24]: type 4, range 32, base 00004c40, size 6, enabled found-> vendor=0x10de, dev=0x005a, revid=0xa2 bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d8104000, size 12, enabled found-> vendor=0x10de, dev=0x005b, revid=0xa3 bus=0, slot=2, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base feb00000, size 8, enabled found-> vendor=0x10de, dev=0x0059, revid=0xa2 bus=0, slot=4, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000dc00, size 8, enabled map[14]: type 4, range 32, base 0000e000, size 8, enabled map[18]: type 1, range 32, base d8103000, size 12, enabled pcib0: matched entry for 0.4.INTA (src \\_SB_.PCI0.APCJ:0) pci_link24: Picked IRQ 20 with weight 0 pcib0: slot 4 INTA routed to irq 20 via \\_SB_.PCI0.APCJ found-> vendor=0x10de, dev=0x0053, revid=0xf2 bus=0, slot=6, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000f000, size 4, enabled found-> vendor=0x10de, dev=0x0054, revid=0xf3 bus=0, slot=7, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 000009f0, size 3, enabled map[14]: type 4, range 32, base 00000bf0, size 2, enabled map[18]: type 4, range 32, base 00000970, size 3, enabled map[1c]: type 4, range 32, base 00000b70, size 2, enabled map[20]: type 4, range 32, base 0000d800, size 4, enabled map[24]: type 1, range 32, base d8102000, size 12, enabled pcib0: matched entry for 0.7.INTA (src \\_SB_.PCI0.APSI:0) pci_link29: Picked IRQ 21 with weight 0 pcib0: slot 7 INTA routed to irq 21 via \\_SB_.PCI0.APSI found-> vendor=0x10de, dev=0x0055, revid=0xf3 bus=0, slot=8, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 000009e0, size 3, enabled map[14]: type 4, range 32, base 00000be0, size 2, enabled map[18]: type 4, range 32, base 00000960, size 3, enabled map[1c]: type 4, range 32, base 00000b60, size 2, enabled map[20]: type 4, range 32, base 0000c400, size 4, enabled map[24]: type 1, range 32, base d8101000, size 12, enabled pcib0: matched entry for 0.8.INTA (src \\_SB_.PCI0.APSJ:0) pci_link30: Picked IRQ 22 with weight 0 pcib0: slot 8 INTA routed to irq 22 via \\_SB_.PCI0.APSJ found-> vendor=0x10de, dev=0x005c, revid=0xa2 bus=0, slot=9, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x0057, revid=0xa3 bus=0, slot=10, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=3 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d8100000, size 12, enabled map[14]: type 4, range 32, base 0000b000, size 3, enabled pcib0: matched entry for 0.10.INTA (src \\_SB_.PCI0.APCH:0) pci_link23: Picked IRQ 23 with weight 0 pcib0: slot 10 INTA routed to irq 23 via \\_SB_.PCI0.APCH found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=11, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=12, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=13, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x005d, revid=0xa3 bus=0, slot=14, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 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) pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 ichsmb0: port 0xe400-0xe41f,0x4c00-0x4c3f,0x4c40-0x4c7f at device 1.1 on pci0 ichsmb0: Reserved 0x40 bytes for rid 0x20 type 4 at 0x4c00 pcib0: matched entry for 0.1.INTA (src \\_SB_.PCI0.APCS:0) pci_link26: Picked IRQ 20 with weight 1 pcib0: slot 1 INTA routed to irq 20 via \\_SB_.PCI0.APCS ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 ohci0: mem 0xd8104000-0xd8104fff at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd8104000 pcib0: matched entry for 0.2.INTA (src \\_SB_.PCI0.APCF:0) pci_link21: Picked IRQ 21 with weight 1 pcib0: slot 2 INTA routed to irq 21 via \\_SB_.PCI0.APCF ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff at device 2.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfeb00000 pcib0: matched entry for 0.2.INTB (src \\_SB_.PCI0.APCL:0) pci_link27: Picked IRQ 22 with weight 1 pcib0: slot 2 INTB routed to irq 22 via \\_SB_.PCI0.APCL ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered pcm0: port 0xdc00-0xdcff,0xe000-0xe0ff mem 0xd8103000-0xd8103fff irq 20 at device 4.0 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xdc00 pcm0: Reserved 0x100 bytes for rid 0x14 type 4 at 0xe000 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features 5 bit master volume, no 3D Stereo Enhancement pcm0: Primary codec extended features double rate PCM, reserved 1, center DAC, surround DAC, LFE DAC, reserved 5 pcm0: ac97 codec dac ready count: 0 pcm0: sndbuf_setmap 7ba37000, 4000; 0xffffffffb1ea6000 -> 7ba37000 pcm0: sndbuf_setmap 7ba1c000, 4000; 0xffffffffb1eaa000 -> 7ba1c000 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=60 ostat1=70 ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata0: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 ata0: reset tp2 stat0=20 stat1=30 devices=0x0 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: [MPSAFE] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd8102000-0xd8102fff irq 21 at device 7.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd800 atapci1: [MPSAFE] atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xd8102000 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata2: SATA connect status=00000000 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata3: SATA connect status=00000000 ata3: [MPSAFE] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd8101000-0xd8101fff irq 22 at device 8.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc400 atapci2: [MPSAFE] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xd8101000 atapci2: [MPSAFE] ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata4: SATA connect ready time=0ms ata4: sata_connect devices=0x1 ata4: [MPSAFE] ata5: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata5: SATA connect ready time=0ms ata5: sata_connect devices=0x1 ata5: [MPSAFE] pcib1: at device 9.0 on pci0 pcib1: secondary bus 5 pcib1: subordinate bus 5 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xd8000000-0xd80fffff pcib1: prefetched decode 0xfff00000-0xfffff pcib1: Subtractively decoded bridge. ACPI: Found matching pin for 0.7.INTA at func 0: 21 pci_link17: BIOS IRQ 21 for 0.7.INTA is invalid ACPI: Found matching pin for 0.8.INTA at func 0: 22 pci_link18: BIOS IRQ 22 for 0.8.INTA is invalid ACPI: Found matching pin for 0.10.INTA at func 0: 23 pci_link18: BIOS IRQ 23 for 0.10.INTA is invalid pci5: on pcib1 pci5: physical bus=5 found-> vendor=0x173b, dev=0x03ea, revid=0x15 bus=5, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=3 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base d8000000, size 16, enabled pcib1: (null) requested memory range 0xd8000000-0xd800ffff: good pcib1: matched entry for 5.7.INTA (src \\_SB_.PCI0.APC2:0) pci_link17: Picked IRQ 17 with weight 0 pcib1: slot 7 INTA routed to irq 17 via \\_SB_.PCI0.APC2 bge0: mem 0xd8000000-0xd800ffff irq 17 at device 7.0 on pci5 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd8000000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:09:5b:8e:63:2f bge0: [MPSAFE] nve0: port 0xb000-0xb007 mem 0xd8100000-0xd8100fff irq 23 at device 10.0 on pci0 nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd8100000 nve0: Ethernet address 00:13:d4:36:79:07 miibus1: on nve0 ukphy0: on miibus1 ukphy0: OUI 0x005043, model 0x000c, rev. 2 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: bpf attached nve0: Ethernet address: 00:13:d4:36:79:07 nve0: [GIANT-LOCKED] pcib2: at device 11.0 on pci0 pcib2: secondary bus 4 pcib2: subordinate bus 4 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xfff00000-0xfffff pcib2: prefetched decode 0xfff00000-0xfffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR3 - AE_NOT_FOUND pci4: on pcib2 pci4: physical bus=4 pcib3: at device 12.0 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: memory decode 0xfff00000-0xfffff pcib3: prefetched decode 0xfff00000-0xfffff pcib3: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR2 - AE_NOT_FOUND pci3: on pcib3 pci3: physical bus=3 pcib4: at device 13.0 on pci0 pcib4: secondary bus 2 pcib4: subordinate bus 2 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xfff00000-0xfffff pcib4: prefetched decode 0xfff00000-0xfffff pcib4: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR1 - AE_NOT_FOUND pci2: on pcib4 pci2: physical bus=2 pcib5: at device 14.0 on pci0 pcib5: secondary bus 1 pcib5: subordinate bus 1 pcib5: I/O decode 0xf000-0xfff pcib5: memory decode 0xd0000000-0xd7ffffff pcib5: prefetched decode 0xc0000000-0xcfffffff pcib5: could not get PCI interrupt routing table for \\_SB_.PCI0.XVR0 - AE_NOT_FOUND pci1: on pcib5 pci1: physical bus=1 found-> vendor=0x10de, dev=0x0141, revid=0xa2 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 32, base d0000000, size 26, enabled pcib5: (null) requested memory range 0xd0000000-0xd3ffffff: good map[14]: type 3, range 64, base c0000000, size 28, enabled pcib5: (null) requested memory range 0xc0000000-0xcfffffff: good map[1c]: type 1, range 64, base d4000000, size 24, enabled pcib5: (null) requested memory range 0xd4000000-0xd4ffffff: good pcib0: matched entry for 0.14.INTA (src \\_SB_.PCI0.APC3:0) pci_link18: Picked IRQ 18 with weight 0 pcib0: slot 14 INTA routed to irq 18 via \\_SB_.PCI0.APC3 pcib5: slot 0 INTA is routed to irq 18 pci1: at device 0.0 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x829 0x839 0x829 0x829 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 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:0x1d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 4: ioport 0x4c00 alloc failed ahc_isa_probe 13: ioport 0xdc00 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 0xc0000-0xcefff,0xd0000-0xd3fff pnpid ORM0000 on isa0 fb: new array size 4 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x8a9 0x8a9 0x8a9 0x8a9 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 132689 -> 100000 procfs registered linprocfs registered lapic: Divisor 2, Frequency 100515310 hz Timecounter "TSC" frequency 2412375335 Hz quality -100 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire acd0: setting PIO4 on nVidia nForce4 chip acd0: setting UDMA66 on nVidia nForce4 chip acd0: DVDR drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 6890KB/s (6890KB/s), 1419KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad8: 286188MB at ata4-master SATA150 ad8: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue ad8: nVidia check1 failed ad8: Adaptec check1 failed ad8: LSI (v3) check1 failed ad8: LSI (v2) check1 failed ad8: FreeBSD check1 failed ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad10: 286188MB at ata5-master SATA150 ad10: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue ad10: nVidia check1 failed ad10: Adaptec check1 failed ad10: LSI (v3) check1 failed ad10: LSI (v2) check1 failed ad10: FreeBSD check1 failed pcm0: measured ac97 link rate at 47996 Hz, will use 48000 Hz ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00040010 LDR: 0x02000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 12 (ISA IRQ 12) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0 GEOM: new disk ad8 GEOM: new disk ad10 Trying to mount root from ufs:/dev/ad8s1a start_init: trying /sbin/init nve0: link state changed to UP splash: image decoder found: daemon_saver bge0: link state changed to UP ----Next_Part(Sat_Sep_17_15_14_08_2005_164)---- From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 06:17:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1395D16A41F for ; Sat, 17 Sep 2005 06:17:30 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from smtpclu-6.eunet.yu (smtpclu-6.eunet.yu [194.247.192.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 399A943D46 for ; Sat, 17 Sep 2005 06:17:28 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from faust.net (P-13.111.EUnet.yu [213.240.13.111]) by smtpclu-6.eunet.yu (8.12.11/8.12.11) with ESMTP id j8H6HO79029299; Sat, 17 Sep 2005 08:17:24 +0200 Received: by faust.net (Postfix, from userid 1001) id 9E83641E7; Sat, 17 Sep 2005 08:08:30 +0200 (CEST) Date: Sat, 17 Sep 2005 08:08:30 +0200 From: Zoran Kolic To: wieland.k@gmail.com Message-ID: <20050917060830.GA620@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scan: EUnet-AVAS-Milter X-AVAS-Virus-Status: clean X-Spam-Checker: EUnet-AVAS-Milter X-AVAS-Spam-Score: 0.0 X-AVAS-Spam-Symbols: BAYES_50 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 06:17:30 -0000 Hi Kristopher! Just like you, I had issue with this combination. MB looks to me quite good, but it is not fully supported. Ether- net, some infos from mb (temp...). And, when I installed 5.4, radeon made pure result. "Agp" was not choice and I left it off. After changing for nvidia video card (some 9570, whatever it means), I finally have perfect picture. Perfect should be read as sharp , vivid. I don't listen to the music on it, no movies, so your needs could be bigger from the card. If 6.0 gives the same, I'm fine. If it gives better support for mb, hurrah. That on board nic is headache even for Ruslan Ermilov. Pitty as my asus looks like nice hardware. So, my heart has broken for ati card, but it solved the problem. After two days, no one even noticed the difference. Best regards Zoran From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 09:51:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3EDD16A41F; Sat, 17 Sep 2005 09:51:25 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.swip.net [212.247.155.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0F7843D45; Sat, 17 Sep 2005 09:51:24 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-137-127.daxnet.no ([193.217.137.127] verified) by mailfe13.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 21620517; Sat, 17 Sep 2005 11:51:22 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sat, 17 Sep 2005 11:52:22 +0200 User-Agent: KMail/1.7 References: <17166.21317.705489.47055@grasshopper.cs.duke.edu> <20050902.103259.08238152.fujita@soum.co.jp> <20050917.151408.46626816.fujita@soum.co.jp> In-Reply-To: <20050917.151408.46626816.fujita@soum.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509171152.23745.hselasky@c2i.net> Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: MAXMEM ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 09:51:25 -0000 On Saturday 17 September 2005 08:14, FUJITA Kazutoshi wrote: > Hi, > > I have AMD64 -CURRENT box. > Motherboard is ASUS A8N-E(chipset is nForce4). > It has 4GB Memory. This might indicate that your hardware does not support 4GB addressing. In the file "/sys/dev/usb/usb_mem.c", change "BUS_SPACE_MAXADDR_32BIT" into "BUS_SPACE_MAXADDR_32BIT/2". > > There is some trouble with GENERIC kernel, > but specifying MAXMEM, such as > > options MAXMEM=(2*1024*1024) > ^^^ remove this option from your kernel config file. Recompile kernel and see what happens. You might also want to change this in the other drivers in question, and see if it makes any difference. --HPS From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 13:05:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FBA316A41F for ; Sat, 17 Sep 2005 13:05:54 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5E8643D45 for ; Sat, 17 Sep 2005 13:05:53 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.12.10/5.2) with ESMTP id j8HD5cBR007799; Sat, 17 Sep 2005 15:05:38 +0200 (MEST) From: Adriaan de Groot To: "Jeff D. Hamann" Date: Sat, 17 Sep 2005 15:05:37 +0200 User-Agent: KMail/1.8.91 References: <001101c5bb17$e969e3c0$0a00a8c0@rodan> In-Reply-To: <001101c5bb17$e969e3c0$0a00a8c0@rodan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509171505.38263.groot@kde.org> X-Spam-Score: -1.399 () BAYES_00,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: freebsd-amd64@freebsd.org Subject: Re: mounting usb on fbsd6beta4... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 13:05:54 -0000 [Some notes from a user perspective, on 5.4] On Saturday 17 September 2005 01:39, Jeff D. Hamann wrote: > Sep 17 16:24:46 bobby kernel: umass0: vendor 0x090a product 0x1001, rev > 1.10/1.00, addr 2 > Sep 17 16:24:46 bobby kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Sep 17 16:24:46 bobby kernel: da0: Removable Direct > Access SCSI-0 device > Sep 17 16:24:46 bobby kernel: da0: 1.000MB/s transfers > Sep 17 16:24:46 bobby kernel: da0: 250MB (512000 512 byte sectors: 64H > 32S/T 250C) This is largely to be expected -- there's a umass device being found, it's being mapped to a SCSI disk device, it has a lousy transfer rate because you plugged it into a USB1 port, and it's 250MB (a weird size, maybe). I get very similar output with either my USB1 key (64M) or my removeable HDD (12G leftover piece of junk in a generic USB HDD enclosure). > Sep 17 16:24:46 bobby kernel: da1 at umass-sim0 bus 0 target 0 lun 1 That's odd. I don't particularly see why one device would show up as two SCSI disks (though it's not impossible). > Sep 17 16:24:46 bobby kernel: (da0:umass-sim0:0:0:0): Synchronize cache > failed, status == 0x4, scsi status == 0x0 Typicaly missing quirk. There was a quirks table early on in 5.X's life which I believe has been removed by now. The quirks documented weird behavior that specific USB devices have. In fact, I have a 128M USB stick that -- once I had put in the right quirks -- worked fairly well, but now crashes the system hard on removal. So it's not _just_ you, there's more USB devices out there that give trouble -- at least on 5-STABLE still. Whether any of my rambling applies to 6-CURRENT, I don't know. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 23:28:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B7B016A421; Sat, 17 Sep 2005 23:28:37 +0000 (GMT) (envelope-from sev@interhack.net) Received: from rowlf.interhack.net (rowlf.interhack.net [66.148.172.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 010C843D5A; Sat, 17 Sep 2005 23:28:32 +0000 (GMT) (envelope-from sev@interhack.net) Received: from localhost (rowlf.interhack.net [66.148.172.114]) by rowlf.interhack.net (8.12.11/8.12.11) with ESMTP id j8HNSFVg004995; Sat, 17 Sep 2005 19:28:20 -0400 (EDT) (envelope-from sev@interhack.net) Date: Sun, 18 Sep 2005 02:28:17 +0300 From: Eugene Sandulenko To: Jung-uk Kim Message-ID: <20050918022817.171107a7@grover.interhack.net> In-Reply-To: <200509151957.24837.jkim@FreeBSD.org> References: <200509151957.24837.jkim@FreeBSD.org> Organization: Interhack Corp X-Mailer: Sylpheed-Claws 1.9.14cvs33 (GTK+ 2.6.10; i386-unknown-freebsd6.0) X-Face: 1J6x$MCC5,7[S<,\qnH!C@sPEedsc2LwzF1&kO7]!ILFF~T@rQ93SX1(Y?}"Mc5k0jHfr$GDbb.[M/J8`C]cATX]SOKqYu~VspX?CP\Sue`tjE2`8,f79$Zpt+1eQ#mA9DAlW=Z; rd)m.>3DUi1gTG,fys2%{Nr?nOYG>oE+yRnHk"F6mF; 0&5!UY#XyO0T`K"`I?ya=SVH}W\Mb=F&6"-N*bO'y6~VCPWF499&<^)sc|io?j#U!BM~'MX\X Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on rowlf.interhack.net Cc: freebsd-amd64@freebsd.org Subject: Re: [PATCH] agp(4) for ULi M1689/nVidia nForce3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 23:28:37 -0000 On Thu, 15 Sep 2005 19:57:04 -0400 Jung-uk Kim wrote: > If you have any of these, please test and let me know. > > http://people.freebsd.org/~jkim/agp_amd64.diff FreeBSD 6.0-BETA4. nVidia nForce3 250Gb (Motherboard GA-K8NSC-939). Radeon 9100 (aka 8500). i386 kernel. with xorg-server 6.8.2 I got garbled screen and normal cursor with dri enabled and system didn't let me leave X session though it reacted to mouse movements. Just today I upgraded to xorg-server 6.8.99.16. Starting X with dri gave me black screen and major system lockup. After applying your patch I got this on boot: agp0: mem 0xe0000000-0xe1ffffff at device 0. 0 on pci0 drm0: port 0x9000-0x90ff mem 0xd0000000-0xdfffffff,0xe 3000000-0xe300ffff irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xe0000000 32MB info: [drm] Initialized radeon 1.16.0 20050311 on minor 0 (no changes in messages after patch applying) Though X now loads with dri module and works, but I get following messages with GL applications: libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering I could do any further testing if you like. Eugene From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 17 23:31:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9D3C16A41F for ; Sat, 17 Sep 2005 23:31:06 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 103C743D46 for ; Sat, 17 Sep 2005 23:31:05 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EGm8A-0000C0-PR for freebsd-amd64@freebsd.org; Sun, 18 Sep 2005 01:30:02 +0200 Received: from dsl-084-059-077-096.arcor-ip.net ([84.59.77.96]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Sep 2005 01:30:02 +0200 Received: from Andreas_Eder by dsl-084-059-077-096.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Sep 2005 01:30:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-amd64@freebsd.org From: Andreas Eder Date: Sun, 18 Sep 2005 01:01:19 +0200 Lines: 89 Message-ID: <86acibs3i8.fsf@staffa.eder.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dsl-084-059-077-096.arcor-ip.net User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) Cancel-Lock: sha1:Z+9mzPDcrMWawqLXn29siYIUs0M= Sender: news Subject: USB Problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 23:31:06 -0000 Hi, tiday I tried to attach an mp3 player (X4-TECH BogieMan II) to my amd64 box (FreeBSD staffa.eder.de 5.4-STABLE FreeBSD 5.4-STABLE #0: Sat Sep 17 18:24:26 CEST 2005 root@staffa.eder.de:/usr/obj/usr/src/sys/STAFFA amd64) which promptly wedged it and rebooted. Here is what I found in the log: Sep 17 11:40:32 staffa kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Sep 17 11:40:32 staffa kernel: da1: Removable Direct Access SCSI-0 device Sep 17 11:40:32 staffa kernel: da1: 1.000MB/s transfers Sep 17 11:40:32 staffa kernel: da1: 497MB (1019617 512 byte sectors: 64H 32S/T 497C) Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED it goes on for a while like this Sep 17 11:40:33 staffa kernel: Opened disk da1 -> 5 Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:33 staffa kernel: Opened disk da1 -> 5 Sep 17 11:40:33 staffa kernel: umass1: at uhub2 port 1 (addr 2) disconnected Sep 17 11:40:33 staffa kernel: (da1:umass-sim1:1:0:0): lost device Sep 17 11:40:33 staffa kernel: (da1:umass-sim1:1:0:0): removing device entry Sep 17 11:40:33 staffa kernel: umass1: detached Sep 17 11:40:45 staffa kernel: umass1: vendor 0x10d6 USB 2.0(FS) FLASH DISK, rev 1.10/1.00, addr 2 Sep 17 11:40:45 staffa kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Sep 17 11:40:45 staffa kernel: da1: Removable Direct Access SCSI-0 device Sep 17 11:40:45 staffa kernel: da1: 1.000MB/s transfers Sep 17 11:40:45 staffa kernel: da1: 497MB (1019617 512 byte sectors: 64H 32S/T 497C) Sep 17 11:40:46 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:46 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:46 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:46 staffa kernel: (da1:umass-sim1:1:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Sep 17 11:40:46 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:46 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED Sep 17 11:40:46 staffa kernel: umass1: BBB bulk-out clear stall failed, STALLED Sep 17 11:40:47 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:40:47 staffa kernel: umass1: at uhub2 port 1 (addr 2) disconnected Sep 17 11:40:47 staffa kernel: (da1:umass-sim1:1:0:0): lost device Sep 17 11:40:47 staffa kernel: (da1:umass-sim1:1:0:0): removing device entry Sep 17 11:40:47 staffa kernel: Opened disk da1 -> 5 Sep 17 11:40:47 staffa kernel: umass1: detached Sep 17 11:40:58 staffa kernel: umass1: vendor 0x10d6 USB 2.0(FS) FLASH DISK, rev 1.10/1.00, addr 2 Sep 17 11:40:59 staffa kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Sep 17 11:40:59 staffa kernel: da1: Removable Direct Access SCSI-0 device Sep 17 11:40:59 staffa kernel: da1: 1.000MB/s transfers Sep 17 11:40:59 staffa kernel: da1: 497MB (1019617 512 byte sectors: 64H 32S/T 497C) Sep 17 11:41:00 staffa kernel: umass1: BBB reset failed, STALLED Sep 17 11:41:00 staffa kernel: umass1: BBB bulk-in clear stall failed, STALLED adn finally spontaneously reboots. Is this a know problem? I found similar things with google. How can I fix this? Any help would be appreciated. 'Andreas -- Wherever I lay my .emacs, there's my $HOME.