From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 22 11:53:24 2006 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 E4AD216A53C; Sun, 22 Oct 2006 11:53:24 +0000 (UTC) (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 1D57E4428F; Sun, 22 Oct 2006 11:25:38 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k9MBPcSP067469; Sun, 22 Oct 2006 07:25:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.8/8.13.8) with ESMTP id k9MBPcx7048017; Sun, 22 Oct 2006 07:25:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0668373068; Sun, 22 Oct 2006 07:25:37 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061022112538.0668373068@freebsd-current.sentex.ca> Date: Sun, 22 Oct 2006 07:25:37 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner3 X-Virus-Status: Clean 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, 22 Oct 2006 11:53:25 -0000 TB --- 2006-10-22 10:56:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-22 10:56:03 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-22 10:56:03 - cleaning the object tree TB --- 2006-10-22 10:56:28 - checking out the source tree TB --- 2006-10-22 10:56:28 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-22 10:56:28 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-22 11:06:26 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-22 11:06:26 - cd /src TB --- 2006-10-22 11:06:26 - /usr/bin/make -B buildworld >>> World build started on Sun Oct 22 11:06:28 UTC 2006 >>> 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 [...] cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/vwscanf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wbuf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wprintf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wscanf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wsetup.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/xprintf.c /src/lib/libc/stdio/xprintf.c: In function `__v2printf': /src/lib/libc/stdio/xprintf.c:279: warning: passing arg 2 of `__builtin_va_copy' discards qualifiers from pointer target type *** Error code 1 Stop in /src/lib/libc. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-22 11:25:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-22 11:25:37 - ERROR: failed to build world TB --- 2006-10-22 11:25:37 - tinderbox aborted TB --- 0.20 user 0.68 system 1774.42 real http://tinderbox.des.no//tinderbox/logs/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 22 18:53:47 2006 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 BB4F316A40F; Sun, 22 Oct 2006 18:53:47 +0000 (UTC) (envelope-from danolson@visi.com) Received: from cenn.mc.mpls.visi.com (cenn.mc.mpls.visi.com [208.42.156.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BB4A43D62; Sun, 22 Oct 2006 18:53:46 +0000 (GMT) (envelope-from danolson@visi.com) Received: from [192.168.240.221] (danolson.dsl.visi.com [209.98.225.50]) by cenn.mc.mpls.visi.com (Postfix) with ESMTP id 264E1820E; Sun, 22 Oct 2006 13:53:45 -0500 (CDT) Message-ID: <453BBE33.1030501@visi.com> Date: Sun, 22 Oct 2006 13:53:39 -0500 From: Dan Olson User-Agent: Thunderbird 1.5.0.7 (X11/20061014) MIME-Version: 1.0 To: Coleman Kane References: <20061019220349.GA88673@ramen.coleyandcheryl> In-Reply-To: <20061019220349.GA88673@ramen.coleyandcheryl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Upgrading Turion64 X2 Laptop, need input 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, 22 Oct 2006 18:53:47 -0000 Coleman Kane wrote: > Hi, > > I am looking into getting a Turion64 X2 laptop to replace > the Gateway 7422gx that I have. Has anyone had success with > any specific models under -CURRENT ? I have read the mailing > lists and seen some discussion about the APIC/ACPI problems > as well as some trouble with the second core not booting up > all the time? Are there any success stories that can help me > out? > > -- > Coleman Kane I just bought an HP dv6119us laptop with the Turion X2 which does not work right with apic and thus smp with i386. But if I set hint.apic.0.disabled=1 at the loader prompt it boots fine without using the 2nd core. I filed a PR about this to day under kern/104678 http://www.freebsd.org/cgi/query-pr.cgi?pr=104678 I also posted a mail to the SMP list and haven't seen any responses, positive or negative. Sorry Dan From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 22 21:17:53 2006 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 A8D3016A403 for ; Sun, 22 Oct 2006 21:17:53 +0000 (UTC) (envelope-from groot@kde.org) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EB5B43D4C for ; Sun, 22 Oct 2006 21:17:52 +0000 (GMT) (envelope-from groot@kde.org) Received: from adsl-dc-2f63f.adsl.wanadoo.nl [83.116.148.63] (helo=beans.englishbreakfastnetwork.org) (authen=adridg) by smeltpunt.science.ru.nl (8.13.7/5.10) with ESMTP id k9MLHpwF010136 for ; Sun, 22 Oct 2006 23:17:52 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Sun, 22 Oct 2006 23:17:46 +0200 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1568983.1oj4YbUeFe"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200610222317.51177.groot@kde.org> Subject: Socket F experience? 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, 22 Oct 2006 21:17:53 -0000 --nextPart1568983.1oj4YbUeFe Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is there anyone with experience with socket F motherboards? The Tyan Thunde= r=20 3600b (s2927) in particular, but any one will do. Since most of them are=20 nForce-based, I'm vaguely worried about all kinds of compatibility issues. I don't see much new kit showing up in the motherboard compatibility list,= =20 hence my question. I hope to have a Sun X2100 (M2) for new-fangled=20 experimental purposes soon and will put in a report as well. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1568983.1oj4YbUeFe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFO9//dqzuAf6io/4RAoz5AJ9ymjfHhYYJVyDW2bQKKcfA+5Rw+wCcCrSG 4zZxBXc1Xg9Rg8NxtX99tm8= =cQma -----END PGP SIGNATURE----- --nextPart1568983.1oj4YbUeFe-- From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 00:59:10 2006 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 AB7AA16A412; Mon, 23 Oct 2006 00:59:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CFF943D4C; Mon, 23 Oct 2006 00:59:10 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id k9N0x9rl092226; Sun, 22 Oct 2006 20:59:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.8/8.13.8) with ESMTP id k9N0x9GL084230; Sun, 22 Oct 2006 20:59:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3896373068; Sun, 22 Oct 2006 20:59:09 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061023005909.3896373068@freebsd-current.sentex.ca> Date: Sun, 22 Oct 2006 20:59:09 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner2 X-Virus-Status: Clean 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: Mon, 23 Oct 2006 00:59:10 -0000 TB --- 2006-10-23 00:29:27 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-10-23 00:29:27 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-10-23 00:29:27 - cleaning the object tree TB --- 2006-10-23 00:29:51 - checking out the source tree TB --- 2006-10-23 00:29:51 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-10-23 00:29:51 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-10-23 00:39:50 - building world (CFLAGS=-O2 -pipe) TB --- 2006-10-23 00:39:50 - cd /src TB --- 2006-10-23 00:39:50 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 23 00:39:52 UTC 2006 >>> 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 [...] cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/vwscanf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wbuf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wprintf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wscanf.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/wsetup.c cc -O2 -pipe -I/src/lib/libc/include -I/src/lib/libc/../../include -I/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/src/lib/libc/../../contrib/gdtoa -DINET6 -I/obj/amd64/src/lib/libc -I/src/lib/libc/resolv -DPOSIX_MISTAKE -I/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/src/lib/libc/rpc -DYP -DNS_CACHING -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/lib/libc/stdio/xprintf.c /src/lib/libc/stdio/xprintf.c: In function `__v2printf': /src/lib/libc/stdio/xprintf.c:279: warning: passing arg 2 of `__builtin_va_copy' discards qualifiers from pointer target type *** Error code 1 Stop in /src/lib/libc. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-10-23 00:59:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-10-23 00:59:08 - ERROR: failed to build world TB --- 2006-10-23 00:59:08 - tinderbox aborted TB --- 0.29 user 0.58 system 1781.89 real http://tinderbox.des.no//tinderbox/logs/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 10:20:22 2006 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 C4B4F16A40F for ; Mon, 23 Oct 2006 10:20:22 +0000 (UTC) (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 6708443D58 for ; Mon, 23 Oct 2006 10:20:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9NAKMlU022498 for ; Mon, 23 Oct 2006 10:20:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9NAKLVA022497; Mon, 23 Oct 2006 10:20:21 GMT (envelope-from gnats) Date: Mon, 23 Oct 2006 10:20:21 GMT Message-Id: <200610231020.k9NAKLVA022497@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Jiawei Ye" Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jiawei Ye List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 10:20:22 -0000 The following reply was made to PR amd64/88568; it has been noted by GNATS. From: "Jiawei Ye" To: bug-followup@FreeBSD.org, aron@agx.sk Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard Date: Mon, 23 Oct 2006 18:16:25 +0800 My system is a Dell Dimension C512 with nForce 430 chipset. It panics with the USB keyboard plugged in during boot with 6.2-Beta Install CD. Since there is no PS/2 port on this machine, I hope this problem could be fixed before 6.2 Release. -- "If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant." From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 11:08:14 2006 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 799D116A47E for ; Mon, 23 Oct 2006 11:08:14 +0000 (UTC) (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 CF1D943D5F for ; Mon, 23 Oct 2006 11:08:09 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9NB89L3027580 for ; Mon, 23 Oct 2006 11:08:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9NB88WU027576 for freebsd-amd64@FreeBSD.org; Mon, 23 Oct 2006 11:08:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Oct 2006 11:08:08 GMT Message-Id: <200610231108.k9NB88WU027576@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 23 Oct 2006 11:08:14 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/73775 amd64 Kernel panic (trap 12) when booting with (not from!) P o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Trap 12: Page fa o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not work on amd64 o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/84930 amd64 [msdosfs] something wrong with msdosfs on amd64 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on AMD64 archit o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88299 amd64 swapcontext fails with errno 0 f amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. o amd64/104311 amd64 ports/wine should be installable on amd64 60 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/92527 amd64 [ciphy.c] no driver for "CICADA VSC 8201 Gigabit LAN P o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out f amd64/98346 amd64 [kbd] caps lock and other keys are always illuminated o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100348 amd64 No hardware support: Marvell 88E8053 Yukon PCI-E Gigab o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 23 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 15:31:30 2006 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 CA84E16A407; Mon, 23 Oct 2006 15:31:30 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 881CF43D72; Mon, 23 Oct 2006 15:31:30 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 2D522361F9; Mon, 23 Oct 2006 11:31:30 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 425344AC2B; Mon, 23 Oct 2006 11:31:31 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17724.57427.231687.273549@canoe.dclg.ca> Date: Mon, 23 Oct 2006 11:31:31 -0400 To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Cc: Subject: ggate fails on 6.2-RC. 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, 23 Oct 2006 15:31:30 -0000 Has anyone else been testing ggate on amd64? There is an open pr that highlights a datatype problem between the kernel and userland, but even with that patch, I can't get ggate to stay up. I'll post in a more detailed manner about the problem as soon as I get my test-bed system up, but I'm looking for people who also have been testing this with 6.2-RC. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 15:52:31 2006 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 62F4C16A412; Mon, 23 Oct 2006 15:52:31 +0000 (UTC) (envelope-from kaakun@highway.ne.jp) Received: from mx.highway.ne.jp (pip7.gate01.com [61.122.117.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id B868D43D78; Mon, 23 Oct 2006 15:52:21 +0000 (GMT) (envelope-from kaakun@highway.ne.jp) Received: from [219.0.96.106] (helo=[192.168.11.21]) by pop12.isp.us-com.jp with esmtp (Mail 4.20) id 1Gc267-0004RO-V5; Tue, 24 Oct 2006 00:52:20 +0900 Message-ID: <453CE4E0.40301@highway.ne.jp> Date: Tue, 24 Oct 2006 00:50:56 +0900 From: Kazuaki ODA User-Agent: Thunderbird 1.5.0.7 (X11/20061019) MIME-Version: 1.0 To: David Gilbert References: <17724.57427.231687.273549@canoe.dclg.ca> In-Reply-To: <17724.57427.231687.273549@canoe.dclg.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: ggate fails on 6.2-RC. 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, 23 Oct 2006 15:52:31 -0000 David Gilbert wrote: > Has anyone else been testing ggate on amd64? There is an open pr that > highlights a datatype problem between the kernel and userland, but > even with that patch, I can't get ggate to stay up. I'll post in a > more detailed manner about the problem as soon as I get my test-bed > system up, but I'm looking for people who also have been testing this > with 6.2-RC. > > Dave. > I've posted in the problem about ggated to freebsd-stable@. Try to backout sys/kern/uipc_socket2.c rev. 1.147.2.7. This has solved the problem for me. -- Kazuaki ODA From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 16:05:05 2006 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 B048316A403; Mon, 23 Oct 2006 16:05:05 +0000 (UTC) (envelope-from gabriele@sssup.it) Received: from sssup.it (ms01.sssup.it [193.205.80.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1B2A43D7D; Mon, 23 Oct 2006 16:03:38 +0000 (GMT) (envelope-from gabriele@sssup.it) Received: from [193.205.82.27] (HELO [127.0.0.1]) by sssup.it (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 25179374; Mon, 23 Oct 2006 17:55:19 +0200 Message-ID: <453CE7CE.5000206@sssup.it> Date: Mon, 23 Oct 2006 18:03:26 +0200 From: Gabriele Cecchetti User-Agent: Mozilla Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Kazuaki ODA References: <17724.57427.231687.273549@canoe.dclg.ca> <453CE4E0.40301@highway.ne.jp> In-Reply-To: <453CE4E0.40301@highway.ne.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org, David Gilbert Subject: Re: ggate fails on 6.2-RC. 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, 23 Oct 2006 16:05:05 -0000 Kazuaki ODA ha scritto: > David Gilbert wrote: >> Has anyone else been testing ggate on amd64? There is an open pr that >> highlights a datatype problem between the kernel and userland, but >> even with that patch, I can't get ggate to stay up. I'll post in a >> more detailed manner about the problem as soon as I get my test-bed >> system up, but I'm looking for people who also have been testing this >> with 6.2-RC. >> >> Dave. >> > > I've posted in the problem about ggated to freebsd-stable@. Try to > backout sys/kern/uipc_socket2.c rev. 1.147.2.7. This has solved the > problem for me. > > During last days I've tried ggated too, but it did not work for me. I've tried to apply the patch proposed on pr, but it does not solved. I'll try this too. I think that this GEOM_gate need more attention, because it's a critical component when it is used. Gabriele From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 16:12:31 2006 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 1AD8F16A4F5 for ; Mon, 23 Oct 2006 16:12:31 +0000 (UTC) (envelope-from gabriele@sssup.it) Received: from sssup.it (ms01.sssup.it [193.205.80.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC15543D75 for ; Mon, 23 Oct 2006 16:12:25 +0000 (GMT) (envelope-from gabriele@sssup.it) Received: from [193.205.82.27] (HELO [127.0.0.1]) by sssup.it (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 25179578; Mon, 23 Oct 2006 18:04:10 +0200 Message-ID: <453CE9E2.9070704@sssup.it> Date: Mon, 23 Oct 2006 18:12:18 +0200 From: Gabriele Cecchetti User-Agent: Mozilla Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Mike Meyer References: <452C0286.000005.20759@pantene.yandex.ru> <200610111149.k9BBnaxm001133@peedub.jennejohn.org> <17709.9363.443239.897184@bhuda.mired.org> In-Reply-To: <17709.9363.443239.897184@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alecn2002@yandex.ru, freebsd-amd64@freebsd.org Subject: Re: Fw: To amd64 or not to 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, 23 Oct 2006 16:12:31 -0000 I add myself to this thread for a simple question. We use amd64 even on Conroe 2 when we use our PC as Internet servers. Maybe is wrong, but this sounds as 'a little harder' to attack (maybe some known attacks works on i386 code but not on amd64 code). The main drawback I encounter (or I think so), it is with some contrib software that does not work as we wish, or is not available at all. For example we would like to use CODA, but the client side does not work (venus panics as documented by a PR), we would like to use OpenAFS, but we did not find any working distribution (while is available for i386), ggate right now does not work for another documented problem. I know that i386 platform has a lot of open PRs, but the feeling is that with amd64, if you play hard... the things will get harder! :-) _IMHO_ Gabriele Mike Meyer ha scritto: > In <200610111149.k9BBnaxm001133@peedub.jennejohn.org>, Gary Jennejohn typed: >> "alecn2002" writes: >>> The question is: will I have any benefits if I'll move to amd64 system, or it >>> 's safer and better to stay with i386 arch? >> [snip] >>> Problem-free operation and stability have precedense for me over system speed >> The only real advantage of 64-bit over 32-bit is that you can put more than >> 4 GB of RAM into the box. > > Personally, I think the 30% performance improvment I see using amd64 > is a real benefit. The amd64 architecture has twice as many registers > as i386, and they're twice as wide. If you can run code built for > amd64, you win. If you're running mostly i386 apps (as with certain > proprietary systems), you don't. > > It took a little bit of doing, but I got everything I used on my > desktop on i386 working on amd64. The biggest headach was openoffice, > but that was because one of the repositories had a broken tarball; > once I got the right tarball, it built just fine. Two ports required > tweaking to get the code to build on amd64. I wound up installing > another port from the package. The other 400+ ports I use all worked > with no problems. That 1% problem rate sounds about right for i386 > ports as well. > > 32 bit emulation works, and as others have said, is how you run Linux > binaries. The linuxolator works fine. In fact, that may be the best > way to use 32 bit software. Whlle you can run 32 bit freebsd binaries, > the ports system doesn't work for them, because there's no way to > specify that you need the 32-bit version of a library, not the 64-bit > version (if there is, please point me at the docs), so you don't get > the library dependencies installed properly. > > The other gotcha is that, while gcc knows how to build 32 bit > binaries, the system compiler isn't configured to do the right thing > by default. It's probably possible to make this work right, or maybe a > gcc installed from ports will do the right thing. I haven't checked. > > Oh yeah - if you're running the proprietary NVidia driver, it doesn't > exist for amd64 on FreeBSD. The open source driver works fine. > > Personally, I think converting is worth it, and would recommend it if > you can. However, there are things that don't work. The only real way > to tell if everything you need works is to try and see. If you've got > critical things that you *have* to have, you might ask here. But the > answer may not be reliable, because some options that you require may > not work, like the OpenOffice/Mozilla integration. > > Personally, I bought a second disk identical to my system disk, copied > the partition table and set up a dual boot system with /home from the > original system disk on both systems. After I was happy, I moved > everything to one disk and set them up as a RAID 1. > > While you're doing this, check your motherboard specs, and see if it > supports dual channel memory access. If it will, buy another stick of > RAM so that you'll get dual channel mode. That's another relatively > cheap way to improve system performmance. Since amd64 uses a bit more > memory, you may want to do this anyway. > > 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 AA65416A4E7 for ; Mon, 23 Oct 2006 16:20:52 +0000 (UTC) (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 0175A43E33 for ; Mon, 23 Oct 2006 16:20:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9NGKTP6059041 for ; Mon, 23 Oct 2006 16:20:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9NGKTub059040; Mon, 23 Oct 2006 16:20:29 GMT (envelope-from gnats) Date: Mon, 23 Oct 2006 16:20:29 GMT Message-Id: <200610231620.k9NGKTub059040@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Paul Root Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Root List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 16:20:52 -0000 The following reply was made to PR amd64/88568; it has been noted by GNATS. From: Paul Root To: bug-followup@FreeBSD.org, aron@agx.sk Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard Date: Mon, 23 Oct 2006 11:10:23 -0500 --Apple-Mail-2-776513470 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I have the same issue with a Dell Dimension E521 (Athlon 64 x2) with USB only. No PS/2 keyboard. Tried, 6.1 R on x86 and AMD64. And 6.2 Beta 2 on AMD64 Paul Root ptroot@iaces.com --Apple-Mail-2-776513470 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=US-ASCII I have the same issue with a Dell Dimension E521 (Athlon 64 x2) with USB only. No PS/2 keyboard.

Tried, 6.1 R on x86 and AMD64. And 6.2 Beta 2 on AMD64

Paul Root

--Apple-Mail-2-776513470-- From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 21:48:15 2006 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 9FCDB16A4EE for ; Mon, 23 Oct 2006 21:48:15 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-71-117-237-135.ptldor.fios.verizon.net [71.117.237.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19A8943DEA for ; Mon, 23 Oct 2006 21:47:53 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.7/8.13.6) with ESMTP id k9NLlrMe030883 for ; Mon, 23 Oct 2006 14:47:53 -0700 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.7/8.13.4/Submit) with UUCP id k9NLlrAQ030875 for freebsd-amd64@freebsd.org; Mon, 23 Oct 2006 14:47:53 -0700 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id UAA26566; Mon, 23 Oct 2006 20:37:06 GMT Message-Id: <200610232037.UAA26566@sopwith.solgatos.com> To: freebsd-amd64@freebsd.org Date: Mon, 23 Oct 2006 13:37:06 +0100 From: Dieter Subject: Re: video card for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 21:48:15 -0000 So what video card do you recommend for: FreeBSD 6.x AMD64 PCIe drivers with source (no binary security holes) XvMC DVI-I plus s-video no gaming required or desired no eye-candy GUI required or desired can probably live without 3D From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 22:39:17 2006 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 E92B816A40F for ; Mon, 23 Oct 2006 22:39:16 +0000 (UTC) (envelope-from walterbrunswick@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D51543D49 for ; Mon, 23 Oct 2006 22:39:16 +0000 (GMT) (envelope-from walterbrunswick@gmail.com) Received: by nz-out-0102.google.com with SMTP id o37so606919nzf for ; Mon, 23 Oct 2006 15:39:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:thread-index; b=asV8R7B5vRl+lEavgLbkXfiJdo6srGJt6S7i+6hqRaiyiyWuPCmFSvzV+Unb4nKCdJzi10c9T6MDte4DF1pnq+89DpDPvlFGsQaH+PxuxJix0rtJGaBFLkYYWdQZpbgyJNNZuWJcpSF5RzEhaHt9JAr3Ro7MzROC3zLyQ3agHdA= Received: by 10.35.113.12 with SMTP id q12mr7482705pym; Mon, 23 Oct 2006 15:39:15 -0700 (PDT) Received: from walterxp ( [69.158.109.78]) by mx.google.com with ESMTP id 15sm205520nzn.2006.10.23.15.39.14; Mon, 23 Oct 2006 15:39:14 -0700 (PDT) From: "Walter Brunswick" To: Date: Mon, 23 Oct 2006 18:39:31 -0400 Message-ID: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acb29BsxpnPofc0RSCK+9t9ZGGXKow== Subject: FreeBSD/amd64 6.1-RELEASE on AMD Turion64 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, 23 Oct 2006 22:39:17 -0000 I have an issue regarding the installation of FreeBSD/amd64 on an HP notebook computer with an AMD Turion64 single-core uniprocessor. The following conversation took place on ##freebsd on freenode on Oct 23 2006. 16:17.22 < waltz> question: when I tried to install FreeBSD/amd64 on my laptop during the initial boot there were strange hexadecimal characters scrolling on the screen 16:17.33 < runelind> is there a reason why? 16:17.34 < waltz> I've never seen something like that before 16:17.39 < waltz> I don't know what it could be, or why 16:17.48 < runelind> waltz: do you have a compatible laptop? ;p 16:18.57 < waltz> it's an hp dv8000 pavilion 16:19.03 < waltz> top-of-the-line model 16:19.10 < waltz> amd64 chipset 16:19.14 < waltz> should work.. 16:21.24 < runelind> hmm ok 16:21.28 < waltz> does freebsd have support for the AMD Turion64? 16:22.30 < runelind> did you look at the HCL? 16:22.43 < waltz> I am looking at http://www.freebsd.org/releases/6.1R/hardware-amd64.html 16:23.57 = nox- guesses an AMD Turion64 should work 16:24.12 < waltz> odd 16:24.36 < nox-> it doesnt for you? 16:24.38 < appa_x> I did notice a post to questions where someone couldn't get SMP to work on their dual core Turion64 laptop the other day. 16:24.39 < masta> yea, I agree with nox 16:24.42 < masta> should work 16:24.53 < nox-> hmm 16:25.22 < nox-> appa_x, didnt see both cpus? 16:25.45 < appa_x> Actually, I think the issue was it wouldn't boot an SMP kernel at all. 16:25.45 < waltz> I don't know.. 16:25.53 < waltz> nox-: no, actually, it did not 16:26.00 < waltz> which is bizzare 16:26.12 < nox-> waltz, did you try an up kernel? 16:26.58 < waltz> I used ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/6.1/6.1-RELEASE- amd64-disc1.iso 16:27.11 < nox-> well this surly sounds like a bug... 16:27.46 < nox-> waltz, yours didnt boot either? 16:32.06 < waltz> is amd64 a tier1 arch? 16:32.16 < waltz> sorry, no, it didn't nox- 16:33.41 < nox-> i would believe so 16:33.48 < nox-> i guess you should post on -amd64... 16:41.49 < nox-> waltz, did u try a 6.2 beta? or an i386 iso? 16:42.51 < waltz> nox-: i386 failed 16:42.59 < waltz> and no, I didn't try a 6.2 beta 16:43.28 < nox-> would be interesting to know if its fixed in RELENG_6... 16:43.43 < eri--> waltz: it just doesnt boot at all>! 16:43.49 < waltz> nope 16:44.00 < waltz> it starts the btx, then goes berserk 16:44.13 < waltz> spamming millions of lines of hexadecimal chars 16:44.25 < prism> when is the release date for 6.2 16:44.25 < nox-> waltz, so it doesnt even load the kernel? 16:44.33 < waltz> nox-, 'parently not 16:44.48 < eri--> nox-: that's what i was thinking 16:44.49 < nox-> oh so its a loader issue... I really don't know what it is, but I didn't see the Turion64 processor listed anywhere in the supported hardware list. Is this a bug? If not, what could the problem possibly be? From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 23:12:36 2006 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 5419016A403 for ; Mon, 23 Oct 2006 23:12:36 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FCC143D99 for ; Mon, 23 Oct 2006 23:12:03 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nz-out-0102.google.com with SMTP id o37so610064nzf for ; Mon, 23 Oct 2006 16:12:02 -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:references; b=qntHV/A0pkYwGSBmqKj17h2fnmLJfP9bEsqZHpBUDSVCWBVwyl0Bn+ABE1rzb3AhgCmuUPUl1ymCc9Cq20lG16aHcbwkzOlS7iunbvwek1oISuRE7ak7hqdyu39Ii24eojSZRyC9OozqASiBcEiv8RXeI0pOn/Bx4jM6IDkNxHY= Received: by 10.65.193.16 with SMTP id v16mr6273728qbp; Mon, 23 Oct 2006 16:12:02 -0700 (PDT) Received: by 10.64.241.10 with HTTP; Mon, 23 Oct 2006 16:12:02 -0700 (PDT) Message-ID: <346a80220610231612o2bc29336id0d4e9795715b7ca@mail.gmail.com> Date: Mon, 23 Oct 2006 19:12:02 -0400 From: "Coleman Kane" To: freebsd@sopwith.solgatos.com In-Reply-To: <200610232037.UAA26566@sopwith.solgatos.com> MIME-Version: 1.0 References: <200610232037.UAA26566@sopwith.solgatos.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: video card for amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 23:12:36 -0000 On 10/23/06, Dieter wrote: > > So what video card do you recommend for: > > FreeBSD 6.x > AMD64 > PCIe > drivers with source (no binary security holes) > XvMC > DVI-I plus s-video > > no gaming required or desired > no eye-candy GUI required or desired > can probably live without 3D I recommend an ATI card. Something slightly older like the X300 or similar. I have one running dual-head on a 6.1 box with a dual-core EM64T (FreeBSD/amd64) and it works well. I have found that I need to rebuild glib20 and gtk20 with better optimizations in order to get good performance from the box. -- Coleman Kane From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 23 23:20:46 2006 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 53B6416A416 for ; Mon, 23 Oct 2006 23:20:46 +0000 (UTC) (envelope-from mwm-dated-1162509676.d5e40d@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 8FACA43D5C for ; Mon, 23 Oct 2006 23:20:45 +0000 (GMT) (envelope-from mwm-dated-1162509676.d5e40d@mired.org) Received: (qmail 66039 invoked by uid 1001); 23 Oct 2006 23:21:16 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Mon, 23 Oct 2006 19:21:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17725.20075.825546.292134@bhuda.mired.org> Date: Mon, 23 Oct 2006 19:21:15 -0400 To: cokane@cokane.org In-Reply-To: <346a80220610231612o2bc29336id0d4e9795715b7ca@mail.gmail.com> References: <200610232037.UAA26566@sopwith.solgatos.com> <346a80220610231612o2bc29336id0d4e9795715b7ca@mail.gmail.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd@sopwith.solgatos.com, freebsd-amd64@freebsd.org Subject: Re: video card for 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, 23 Oct 2006 23:20:46 -0000 In <346a80220610231612o2bc29336id0d4e9795715b7ca@mail.gmail.com>, Coleman Kane typed: > On 10/23/06, Dieter wrote: > > > > So what video card do you recommend for: > > > > FreeBSD 6.x > > AMD64 > > PCIe > > drivers with source (no binary security holes) > > XvMC > > DVI-I plus s-video > > > > no gaming required or desired > > no eye-candy GUI required or desired > > can probably live without 3D > > > I recommend an ATI card. Something slightly older like the X300 or similar. > I have one running dual-head on a 6.1 box with a dual-core EM64T > (FreeBSD/amd64) and it works well. According to the MythTV page on XvMC, ATI doesn't have hardware support for it. The Intel and Via chipsets do, but you can't get a PCIe card with those on it. The proprietary NVidia driver does as well, but that means no sources and either no FreeBSD or no amd64. Of course, the same page also says that XvMC has problems, and that the easy solution - if you have a fast enough CPU - is to simply turn it off. "Fast enough" depends on what you're trying to play back. I've played back 1080i on an P4 with EM64T enabled, so "fast enough" doesnt' seem like much of a stretch. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 01:59:28 2006 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 838D316A412 for ; Tue, 24 Oct 2006 01:59:28 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from ms-smtp-02.southeast.rr.com (ms-smtp-02.southeast.rr.com [24.25.9.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E8C543D58 for ; Tue, 24 Oct 2006 01:59:27 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-02.southeast.rr.com (8.13.6/8.13.6) with ESMTP id k9O1xQ4Z027838 for ; Mon, 23 Oct 2006 21:59:26 -0400 (EDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.8/8.13.8) with ESMTP id k9O1xPFB044074 for ; Mon, 23 Oct 2006 21:59:25 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 23 Oct 2006 21:59:25 -0400 (EDT) From: Wesley Morgan To: freebsd-amd64@freebsd.org Message-ID: <20061023215541.K43671@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: video trans/encoding 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, 24 Oct 2006 01:59:28 -0000 I was recently playing around with handbrake transcoding dvds to xvid and discovered that when running as amd64 (kernel, world, apps etc) I get half of the fps as the same system using i386. Why would this happen? -- This .signature sanitized for your protection From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 08:18:03 2006 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 79C2E16A4B3 for ; Tue, 24 Oct 2006 08:18:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8860143D67 for ; Tue, 24 Oct 2006 08:17:55 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c58-107-94-118.belrs4.nsw.optusnet.com.au [58.107.94.118]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k9O8HJ2b021989 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Oct 2006 18:17:24 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id k9O82HAp001148; Tue, 24 Oct 2006 18:02:17 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id k9O82HPK001147; Tue, 24 Oct 2006 18:02:17 +1000 (EST) (envelope-from peter) Date: Tue, 24 Oct 2006 18:02:17 +1000 From: Peter Jeremy To: Walter Brunswick Message-ID: <20061024080217.GA916@turion.vk2pj.dyndns.org> References: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64 6.1-RELEASE on AMD Turion64 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, 24 Oct 2006 08:18:03 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Oct-23 18:39:31 -0400, Walter Brunswick wrote: >I have an issue regarding the installation of FreeBSD/amd64 on an HP >notebook computer with an AMD Turion64 single-core uniprocessor. I'm successfully running FreeBSD/amd64 on a HP nx6125 which is also Turion64. Have you tried searching for other people's experiences with the dv8000? >16:42.51 < waltz> nox-: i386 failed This implies it isn't an amd64-specific problem. >16:44.00 < waltz> it starts the btx, then goes berserk >16:44.13 < waltz> spamming millions of lines of hexadecimal chars Is this just a BTX dump - 1/2 screen of hex data or is it really scrolling massive amounts of data? If it's a BTX dump, you could post a transcription (or a link to a photo) to -stable. There are a couple of people who undterstand BTX. >I really don't know what it is, but I didn't see the Turion64 processor >listed anywhere in the supported hardware list. That's a bug in the documentation. FreeBSD should work on any amd64 compatible processor. --=20 Peter Jeremy --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPciJ/opHv/APuIcRAp68AKCPHdCoaRlQoRbxN3s/xaC33mdCLQCgmBzi TYxEKtLgulOT3wbElzS5Y2o= =TZ4o -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 14:50:16 2006 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 B3BE116A40F for ; Tue, 24 Oct 2006 14:50:16 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0B2843D49 for ; Tue, 24 Oct 2006 14:50:15 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so1353233uge for ; Tue, 24 Oct 2006 07:50:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fl9XxUivv2VPR1lzV4lRQ4XMRWSkg9042GcNV7qm6ORIpLAKfiEYzPMe+QCQbNKSIhcR8KRqu8TsApRlcbJUHduVGFtpS89rztqoM3qAxutuAyVr8koGRiBXokoaynvOebc2G3i00upVzfJtJeXm6Jb176sed+MklLax0XKlYUo= Received: by 10.66.221.19 with SMTP id t19mr9020157ugg; Tue, 24 Oct 2006 07:50:14 -0700 (PDT) Received: by 10.67.86.8 with HTTP; Tue, 24 Oct 2006 07:50:14 -0700 (PDT) Message-ID: <790a9fff0610240750u3bc1186fl517c0e8cf733fb3d@mail.gmail.com> Date: Tue, 24 Oct 2006 09:50:14 -0500 From: "Scot Hetzel" To: "Walter Brunswick" In-Reply-To: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64 6.1-RELEASE on AMD Turion64 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, 24 Oct 2006 14:50:16 -0000 On 10/23/06, Walter Brunswick wrote: > I have an issue regarding the installation of FreeBSD/amd64 on an HP > notebook computer with an AMD Turion64 single-core uniprocessor. > > The following conversation took place on ##freebsd on freenode on Oct 23 > 2006. > > 16:17.22 < waltz> question: when I tried to install FreeBSD/amd64 on my > laptop during the initial boot there were strange hexadecimal characters > scrolling on the screen > > I really don't know what it is, but I didn't see the Turion64 processor > listed anywhere in the supported hardware list. > > Is this a bug? If not, what could the problem possibly be? > It's a strange little bug, that I had come across when setting up my dv8000 laptop. I could boot the FreeBSD/i386 CD with no problems, but the screen would dump these hex characters that would continuosly scroll across the screen when booting the FreeBSD/amd64 CD. I'm still seeing the same problem with the FreeBSD/amd64 6.2-Beta2 CD (tested bootonly CD). My solution was to hit the space bar until the speakers beeped for a couple of seconds (when you see /boot/kernel/kernel you can release the space bar), then it loads and executes the kernel and proceeds to sysinstall. On 3/22/06, Scot Hetzel wrote: >Subject: FreeBSD/AMD64 6.1-Beta4: Strange problem with install CDs boot loader > > I recently purchased a HP Pavilion dv8135nr Laptop. > > The strange problem I had was that when the boot loader would load > it would crash if I didn't touch any key on the keyboard. > > The last thing I saw, before it crashed was it reading the > /boot/loader.conf off the CD. Unfortunately, I wasn't able to read > the crash, as the screen at that point was unreadable. I suspect that > the point in which it crashed was when it was loading the kernel, but > before it displayed the message that it was loading > /boot/kernel/kernel. > > This problem occured with both the FreeBSD/AMD64 boot-only and disc1 > install CD-ROMs. > > Thinking that I may need to disable something with acpi, I tried to > break into the boot loader by pressing the space bar repeatedly. But > it wouldn't break into the boot loader, instead it loaded the kernel > and I was able to install FreeBSD/AMD64 6.1-Beta 4. > > Once I had FreeBSD/AMD64 6.1-Beta 4 installed, I was able to > repeatedly boot the system from the Hard Drive without the boot loader > crashing. > Scot P.S. you'll also need to get the 64bit Windows NDIS driver for the Broadcom Wireless adapter, and build the ndis kernel module to use the wireless adapter in the laptop. You'll need to locate the file named 80211g.zip, if you can't find it, I can send you the file. -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 14:52:46 2006 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 B7AFE16A40F for ; Tue, 24 Oct 2006 14:52:46 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31EAA43D46 for ; Tue, 24 Oct 2006 14:52:42 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so1353921uge for ; Tue, 24 Oct 2006 07:52:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ScBNz1KFStJnA0Zrlq1vuFGtvRxesRPHA3ok6Nj06VrF7IKilu9gvtwqpiHVgQnTuamHpnfsklqXQUKHw00DwMRi83SftbcmQ5btpGUijF/KKn2MjLR9T7dR8xZju24QsnUPMpSjAuOH9Ru4M+fVNzFCHzkTIcBpnSuBCb1PLCc= Received: by 10.67.121.15 with SMTP id y15mr8961680ugm; Tue, 24 Oct 2006 07:52:36 -0700 (PDT) Received: by 10.67.86.8 with HTTP; Tue, 24 Oct 2006 07:52:35 -0700 (PDT) Message-ID: <790a9fff0610240752t5afdd5a2w8cddc7acb2933392@mail.gmail.com> Date: Tue, 24 Oct 2006 09:52:35 -0500 From: "Scot Hetzel" To: "Walter Brunswick" In-Reply-To: <790a9fff0610240750u3bc1186fl517c0e8cf733fb3d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <000701c6f6f4$1c6e6d90$0502a8c0@walterxp> <790a9fff0610240750u3bc1186fl517c0e8cf733fb3d@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64 6.1-RELEASE on AMD Turion64 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, 24 Oct 2006 14:52:46 -0000 On 10/24/06, Scot Hetzel wrote: > It's a strange little bug, that I had come across when setting up my > dv8000 laptop. I could boot the FreeBSD/i386 CD with no problems, but > the screen would dump these hex characters that would continuosly > scroll across the screen when booting the FreeBSD/amd64 CD. > > I'm still seeing the same problem with the FreeBSD/amd64 6.2-Beta2 CD > (tested bootonly CD). My solution was to hit the space bar until the > speakers beeped for a couple of seconds (when you see > /boot/kernel/kernel you can release the space bar), then it loads and > executes the kernel and proceeds to sysinstall. > I have also updated the BIOS to version F.44 and still get the same problem. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 17:55:03 2006 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 040D416A40F for ; Tue, 24 Oct 2006 17:55:02 +0000 (UTC) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5939643D5E for ; Tue, 24 Oct 2006 17:55:02 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (gemini.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.8/8.13.8) with ESMTP id k9OHt0tZ068324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 24 Oct 2006 12:55:01 -0500 (CDT) (envelope-from ptroot@iaces.com) Mime-Version: 1.0 (Apple Message framework v752.3) To: freebsd-amd64@freebsd.org Message-Id: <4AC71EE9-38AB-4E41-893E-45405668EF76@iaces.com> From: Paul Root Date: Tue, 24 Oct 2006 12:55:21 -0500 X-Mailer: Apple Mail (2.752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dell Dimension E521 install 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, 24 Oct 2006 17:55:03 -0000 Hi, I just got an e521 (Athlon 64 x@ 3800, 1 gig, ...) and I'm trying to install 6.1, 6.2 Beta 2 on it. I get a panic on the ohci with everything I do. safe mode, single user, no apci, etc. Using i386 and amd64. I tried sending to questions, but got only 1 response, asking if I used safe mode. The e521 has no PS/2 ports, only usb. The errors look like this: (sorry, there may be missing parts), you get 15 seconds to write it down. uhub0: device problem (SET_ADDR_FAILED) disabling port 8 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 at atkbdc0 kbd0 at atkbd0 atkbd0 [GIANT-LOCKED] sc0 .... ... panic: ohci_add_done: addr 0x3bef1ba0 not found So, I'm thinking a couple of things. 1. It's trying to add in the PS/2 keyboard, even though it's not there. 2. kdbmux is not adding the USB keyboard. So I installed the disk on another machine. And made the mistake of not adding ifconfig to the rc.conf. I built a kernel,taking out unneeded stuff. But I left in the atkbd devices, I think that was a mistake. I'm trying to build a new kernel. I'm also unsure as to the fstab, I think it's wrong. I'm trying to create a zip250 drive that will boot, on an old machine. Paul Root ptroot@iaces.com From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 18:48:36 2006 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 2BBE816A4E9 for ; Tue, 24 Oct 2006 18:48:36 +0000 (UTC) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C79543D76 for ; Tue, 24 Oct 2006 18:48:34 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (gemini.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.8/8.13.8) with ESMTP id k9OIe9YL068824 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 24 Oct 2006 13:40:09 -0500 (CDT) (envelope-from ptroot@iaces.com) In-Reply-To: <4AC71EE9-38AB-4E41-893E-45405668EF76@iaces.com> References: <4AC71EE9-38AB-4E41-893E-45405668EF76@iaces.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7F58A7EC-13DC-4675-A046-A0B960B31275@iaces.com> Content-Transfer-Encoding: 7bit From: Paul Root Date: Tue, 24 Oct 2006 13:40:29 -0500 To: Paul Root X-Mailer: Apple Mail (2.752.3) Cc: freebsd-amd64@freebsd.org Subject: Re: Dell Dimension E521 install 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, 24 Oct 2006 18:48:36 -0000 My other thought on the matter is to install a serial port and boot headless. On Oct 24, 2006, at 12:55 PM, Paul Root wrote: > Hi, > I just got an e521 (Athlon 64 x@ 3800, 1 gig, ...) and I'm trying > to install 6.1, > 6.2 Beta 2 on it. I get a panic on the ohci with everything I do. > safe mode, single > user, no apci, etc. Using i386 and amd64. > > I tried sending to questions, but got only 1 response, asking if I > used safe > mode. > > The e521 has no PS/2 ports, only usb. > > The errors look like this: (sorry, there may be missing parts), > you get 15 seconds > to write it down. > > > uhub0: device problem (SET_ADDR_FAILED) disabling port 8 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 at atkbdc0 > kbd0 at atkbd0 > atkbd0 [GIANT-LOCKED] > sc0 .... > ... > panic: ohci_add_done: addr 0x3bef1ba0 not found > > > So, I'm thinking a couple of things. > > 1. It's trying to add in the PS/2 keyboard, even though it's not > there. > 2. kdbmux is not adding the USB keyboard. > > > So I installed the disk on another machine. And made the mistake of > not adding ifconfig > to the rc.conf. I built a kernel,taking out unneeded stuff. But I > left in the atkbd devices, > I think that was a mistake. I'm trying to build a new kernel. I'm > also unsure as to the fstab, > I think it's wrong. > > I'm trying to create a zip250 drive that will boot, on an old machine. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 24 21:50:25 2006 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 784F616A403 for ; Tue, 24 Oct 2006 21:50:25 +0000 (UTC) (envelope-from rondzierwa@comcast.net) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A6B43D68 for ; Tue, 24 Oct 2006 21:50:22 +0000 (GMT) (envelope-from rondzierwa@comcast.net) Received: from rmailcenter78.comcast.net ([204.127.197.178]) by comcast.net (rwcrmhc14) with SMTP id <20061024215022m14003q1eje>; Tue, 24 Oct 2006 21:50:22 +0000 Received: from [209.115.153.68] by rmailcenter78.comcast.net; Tue, 24 Oct 2006 21:50:21 +0000 From: rondzierwa@comcast.net To: freebsd-amd64@freebsd.org Date: Tue, 24 Oct 2006 21:50:21 +0000 Message-Id: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 4 2006) X-Authenticated-Sender: cm9uZHppZXJ3YUBjb21jYXN0Lm5ldA== X-Mailman-Approved-At: Tue, 24 Oct 2006 21:57:11 +0000 Subject: Hardware topology 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, 24 Oct 2006 21:50:25 -0000 Does the amd64 kernel know anything about which memory is attached to which processor, and which i/o bus is attached to which hypertransport link? Can it use this information to do things like allocate pages to a process from the memory that is physically attached to the cpu upon which the process is running? Along these lines, is there any way to set affinity between a process and a cpu (or set of cpu's in the case of multicore)? Likewise with i/o devices, if a process or device driver wants to operate a particular device, can it be set to run on the cpu that owns the hypertransport connection upon which the device is connected? thanks, ron. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 07:57:37 2006 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 11CD416A407 for ; Wed, 25 Oct 2006 07:57:37 +0000 (UTC) (envelope-from amon@sockar.homeip.net) Received: from mallaury.nerim.net (smtp-103-wednesday.noc.nerim.net [62.4.17.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97BF243D5D for ; Wed, 25 Oct 2006 07:57:35 +0000 (GMT) (envelope-from amon@sockar.homeip.net) Received: from sockar.homeip.net (tourist.net8.nerim.net [213.41.176.3]) by mallaury.nerim.net (Postfix) with ESMTP id F26AA4F3CF; Wed, 25 Oct 2006 09:57:28 +0200 (CEST) Received: from ra.aabs (localhost [127.0.0.1]) by sockar.homeip.net (8.13.4/8.13.4) with ESMTP id k9P7sQqx043657; Wed, 25 Oct 2006 09:54:26 +0200 (CEST) (envelope-from amon@ra.aabs) Received: (from amon@localhost) by ra.aabs (8.13.4/8.13.4/Submit) id k9P7sOft043656; Wed, 25 Oct 2006 09:54:24 +0200 (CEST) (envelope-from amon) Date: Wed, 25 Oct 2006 09:54:24 +0200 From: Herve Boulouis To: rondzierwa@comcast.net Message-ID: <20061025075424.GW46550@ra.aabs> References: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware topology 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, 25 Oct 2006 07:57:37 -0000 Le 24/10/2006 21:50, rondzierwa@comcast.net a écrit: > Does the amd64 kernel know anything about which memory is attached to > which processor, and which i/o bus is attached to which hypertransport link? > Can it use this information to do things like allocate pages to a process from > the memory that is physically attached to the cpu upon which the process is > running? Along these lines, is there any way to set affinity between a process > and a cpu (or set of cpu's in the case of multicore)? > > Likewise with i/o devices, if a process or device driver wants to operate a > particular device, can it be set to run on the cpu that owns the hypertransport > connection upon which the device is connected? The freebsd kernel is not NUMA aware, so it doesn't know anything of the underlying hardware topology. -- Herve Boulouis From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 12:13:42 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 13CD116A494; Wed, 25 Oct 2006 12:13:42 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-amd64@freebsd.org Date: Wed, 25 Oct 2006 20:13:38 +0800 User-Agent: KMail/1.8.2 References: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> In-Reply-To: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610252013.38119.davidxu@freebsd.org> Cc: rondzierwa@comcast.net Subject: Re: Hardware topology 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, 25 Oct 2006 12:13:42 -0000 On Wednesday 25 October 2006 05:50, rondzierwa@comcast.net wrote: > Does the amd64 kernel know anything about which memory is attached to > which processor, and which i/o bus is attached to which hypertransport > link? Can it use this information to do things like allocate pages to a > process from the memory that is physically attached to the cpu upon which > the process is running? Along these lines, is there any way to set > affinity between a process and a cpu (or set of cpu's in the case of > multicore)? > > Likewise with i/o devices, if a process or device driver wants to operate a > particular device, can it be set to run on the cpu that owns the > hypertransport connection upon which the device is connected? > > thanks, > ron. There is no unique hardware topology structure in kernel, but scheduler has some APIs can bind thread to a specific CPU, though there is no any syscall can let you do it. David Xu From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 17:30:35 2006 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 D9A5016A47E for ; Wed, 25 Oct 2006 17:30:35 +0000 (UTC) (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 EAB1143D67 for ; Wed, 25 Oct 2006 17:30:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9PHUK7O053660 for ; Wed, 25 Oct 2006 17:30:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9PHUK4X053659; Wed, 25 Oct 2006 17:30:20 GMT (envelope-from gnats) Resent-Date: Wed, 25 Oct 2006 17:30:20 GMT Resent-Message-Id: <200610251730.k9PHUK4X053659@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, Heiko Silbermann Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0A2116A412 for ; Wed, 25 Oct 2006 17:20:43 +0000 (UTC) (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 51FF043D5C for ; Wed, 25 Oct 2006 17:20:34 +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 k9PHKXJB083764 for ; Wed, 25 Oct 2006 17:20:33 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k9PHKXee083763; Wed, 25 Oct 2006 17:20:33 GMT (envelope-from nobody) Message-Id: <200610251720.k9PHKXee083763@www.freebsd.org> Date: Wed, 25 Oct 2006 17:20:33 GMT From: Heiko Silbermann To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/104810: panic: ohci_add_done: addr 0x3fef1ba0 not found 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, 25 Oct 2006 17:30:36 -0000 >Number: 104810 >Category: amd64 >Synopsis: panic: ohci_add_done: addr 0x3fef1ba0 not found >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 25 17:30:20 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Heiko Silbermann >Release: 6.1/6.2beta >Organization: - >Environment: System: Dell Dimension E521 Mainboard: Dell Inc. Model: 0CT103-A02 Chipset: nVidia Geforce6150 Rev. A2 Southbridge nVidia nForce 410/430 MCP Sensor SMSC 830F BIOS: Phoenix Award Workstation BIOS v6.00PG - AMD Athlon 64 X2 Dual Core Prozessor 4200+ (Info from http://www.cpuid.org/cpuz.php - Tool) >Description: If i've tried to install Freebsd 6.1/6.2beta, the System halt on and reboot after 15 seconds by following boot message. 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, addr1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xfe02c000 - 0xfe02eoff irq 22 at device 11.1 on pci0 ehci0: [GIANT - LOCKED] usb1: EHCI version 1.0, legacy support usb1: companion controller, 8 ports each: usb0 usb1: on echi0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr1 uhub1: 8 ports with 8 removable, self powered .. panic: ohci_add_done: addr 0x3fef1ba0 not found Uptime: 1s Cannot dump. No dump device defined If i've tried boot with ACPI disabled, same problem, but with the message uhub0: device problem (SET_ADDR_FAILED), disabling port 4 If i have all USB Devices off in BIOS, i don't have the problem, but now the HD hanging up. ad4: 238418MB at ata2-master SATA300 BISO Menu: Onboard Devices --> USB Controller on/off Rear Dual USB0 on/off Rear Dual USB1 on/off Front USB on/off >How-To-Repeat: - >Fix: - >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 17:38:24 2006 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 0AEF816A416 for ; Wed, 25 Oct 2006 17:38:24 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5021143D8C for ; Wed, 25 Oct 2006 17:38:17 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nf-out-0910.google.com with SMTP id p77so669157nfc for ; Wed, 25 Oct 2006 10:38:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FmcMgBNg3QxHnT/PFE4SHQrAY/oGNsAB+f+sDGYuVJxshne/kvSA4p5AUDk99VT3eAt0TrsSgU/ME0tbwKEq6CJGGAfBWtwD8qj5v8qXuZTcgXIwsos178+rOpKxyOdXIH/PkfMBgiyT9+TqhcrHvJ41EC9XgeQJGVrwEupSY/A= Received: by 10.82.129.5 with SMTP id b5mr207834bud; Wed, 25 Oct 2006 10:38:15 -0700 (PDT) Received: by 10.82.182.11 with HTTP; Wed, 25 Oct 2006 10:38:15 -0700 (PDT) Message-ID: <2fd864e0610251038h46042de8u3712170010b48228@mail.gmail.com> Date: Wed, 25 Oct 2006 12:38:15 -0500 From: Astrodog To: "David Xu" In-Reply-To: <200610252013.38119.davidxu@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> <200610252013.38119.davidxu@freebsd.org> Cc: rondzierwa@comcast.net, freebsd-amd64@freebsd.org Subject: Re: Hardware topology 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, 25 Oct 2006 17:38:24 -0000 On 10/25/06, David Xu wrote: > On Wednesday 25 October 2006 05:50, rondzierwa@comcast.net wrote: > > Does the amd64 kernel know anything about which memory is attached to > > which processor, and which i/o bus is attached to which hypertransport > > link? Can it use this information to do things like allocate pages to a > > process from the memory that is physically attached to the cpu upon which > > the process is running? Along these lines, is there any way to set > > affinity between a process and a cpu (or set of cpu's in the case of > > multicore)? > > > > Likewise with i/o devices, if a process or device driver wants to operate a > > particular device, can it be set to run on the cpu that owns the > > hypertransport connection upon which the device is connected? > > > > thanks, > > ron. > > There is no unique hardware topology structure in kernel, but scheduler > has some APIs can bind thread to a specific CPU, though there is no any > syscall can let you do it. > I'm working on tying this into memory location. Currently slogging through the VM side of things. I'm expecting some usable patches to come out in the next month or so. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 19:11:35 2006 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 58AF716A412; Wed, 25 Oct 2006 19:11:35 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1E9043D5D; Wed, 25 Oct 2006 19:11:34 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (ru@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9PJBYgD064682; Wed, 25 Oct 2006 19:11:34 GMT (envelope-from ru@freefall.freebsd.org) Received: (from ru@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9PJBY0T064678; Wed, 25 Oct 2006 19:11:34 GMT (envelope-from ru) Date: Wed, 25 Oct 2006 19:11:34 GMT From: Ruslan Ermilov Message-Id: <200610251911.k9PJBY0T064678@freefall.freebsd.org> To: adhoniran.gomes@ig.com.br, ru@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated 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, 25 Oct 2006 19:11:35 -0000 Synopsis: [kbd] caps lock and other keys are always illuminated State-Changed-From-To: feedback->closed State-Changed-By: ru State-Changed-When: Wed Oct 25 19:10:36 UTC 2006 State-Changed-Why: I believe this has already been fixed, and my today's changes make CapsLock LED work under X. http://www.freebsd.org/cgi/query-pr.cgi?pr=98346 From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 20:08:07 2006 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 6C81A16A415; Wed, 25 Oct 2006 20:08:07 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49DFB43D5C; Wed, 25 Oct 2006 20:08:06 +0000 (GMT) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.62) with esmtp (envelope-from ) id <1Gcp2i-0004M2-Hy>; Wed, 25 Oct 2006 22:08:04 +0200 Received: from e178053034.adsl.alicedsl.de ([85.178.53.34] helo=[192.168.1.128]) by inpost2.zedat.fu-berlin.de (Exim 4.62) with esmtpsa (envelope-from ) id <1Gcp2i-0003rT-FU>; Wed, 25 Oct 2006 22:08:04 +0200 Message-ID: <453FC420.5050303@mail.zedat.fu-berlin.de> Date: Wed, 25 Oct 2006 22:08:00 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Ruslan Ermilov References: <200610251911.k9PJBY0T064678@freefall.freebsd.org> In-Reply-To: <200610251911.k9PJBY0T064678@freefall.freebsd.org> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.53.34 Cc: freebsd-amd64@FreeBSD.org, adhoniran.gomes@ig.com.br Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated 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, 25 Oct 2006 20:08:07 -0000 Ruslan Ermilov wrote: > Synopsis: [kbd] caps lock and other keys are always illuminated > > State-Changed-From-To: feedback->closed > State-Changed-By: ru > State-Changed-When: Wed Oct 25 19:10:36 UTC 2006 > State-Changed-Why: > I believe this has already been fixed, and my today's changes > make CapsLock LED work under X. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=98346 > _______________________________________________ > 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" > Sorry, mine's does still not(!) under FreeBSD 6.2-PRE/AMD64, but it does under FreeBSD 6.2-PRE/i386. On both boxes I use identical Xorg configs! I changed keyboards, keyboard layouts and, due to a hardware failure of my AMD64 box, hardware , I can exclude harware issues. Regards, Oliver -- From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 20:20:38 2006 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 6A92C16A403 for ; Wed, 25 Oct 2006 20:20:38 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF75343D5C for ; Wed, 25 Oct 2006 20:20:37 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id BD7EB61D3; Thu, 26 Oct 2006 00:20:35 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 90D395EAC; Thu, 26 Oct 2006 00:20:35 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k9PKKYZc005009; Thu, 26 Oct 2006 00:20:34 +0400 (MSD) (envelope-from ru) Date: Thu, 26 Oct 2006 00:20:34 +0400 From: Ruslan Ermilov To: "O. Hartmann" Message-ID: <20061025202034.GA4966@rambler-co.ru> References: <200610251911.k9PJBY0T064678@freefall.freebsd.org> <453FC420.5050303@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <453FC420.5050303@mail.zedat.fu-berlin.de> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-amd64@FreeBSD.org, adhoniran.gomes@ig.com.br Subject: Re: amd64/98346: [kbd] caps lock and other keys are always illuminated 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, 25 Oct 2006 20:20:38 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 25, 2006 at 10:08:00PM +0200, O. Hartmann wrote: > Ruslan Ermilov wrote: > > Synopsis: [kbd] caps lock and other keys are always illuminated > > > > State-Changed-From-To: feedback->closed > > State-Changed-By: ru > > State-Changed-When: Wed Oct 25 19:10:36 UTC 2006 > > State-Changed-Why:=20 > > I believe this has already been fixed, and my today's changes > > make CapsLock LED work under X. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D98346 > > _______________________________________________ > > 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" > > =20 > Sorry, mine's does still not(!) under FreeBSD 6.2-PRE/AMD64, but it does > under FreeBSD 6.2-PRE/i386. On both boxes I use identical Xorg configs! >=20 > I changed keyboards, keyboard layouts and, due to a hardware failure of > my AMD64 box, hardware , I can exclude harware issues. >=20 Please describe in full detail how it doesn't work for you. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFP8cSqRfpzJluFF4RAgGkAJ9L5/CO1DPNv8S9SCsdvv/xsXn+lwCginEB mBnypAxSdJlbxPc/UeiuoW0= =fakd -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 21:02:02 2006 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 350AC16A415; Wed, 25 Oct 2006 21:02:02 +0000 (UTC) (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 DB7BF43D5F; Wed, 25 Oct 2006 21:02:01 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9PL215o075285; Wed, 25 Oct 2006 21:02:01 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9PL21uD075281; Wed, 25 Oct 2006 21:02:01 GMT (envelope-from linimon) Date: Wed, 25 Oct 2006 21:02:01 GMT From: Mark Linimon Message-Id: <200610252102.k9PL21uD075281@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-usb@FreeBSD.org Cc: Subject: Re: usb/104810: [usb] panic: ohci_add_done: addr 0x3fef1ba0 not found 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, 25 Oct 2006 21:02:02 -0000 Old Synopsis: panic: ohci_add_done: addr 0x3fef1ba0 not found New Synopsis: [usb] panic: ohci_add_done: addr 0x3fef1ba0 not found Responsible-Changed-From-To: freebsd-amd64->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Wed Oct 25 21:01:39 UTC 2006 Responsible-Changed-Why: Sounds like this is happening in the usb subsystem. http://www.freebsd.org/cgi/query-pr.cgi?pr=104810 From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 26 00:20:31 2006 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 ED3C016A47B for ; Thu, 26 Oct 2006 00:20:31 +0000 (UTC) (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 1DD0C43D69 for ; Thu, 26 Oct 2006 00:20:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9Q0KMtF093182 for ; Thu, 26 Oct 2006 00:20:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9Q0KMi1093181; Thu, 26 Oct 2006 00:20:22 GMT (envelope-from gnats) Resent-Date: Thu, 26 Oct 2006 00:20:22 GMT Resent-Message-Id: <200610260020.k9Q0KMi1093181@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, FreeBSD Sucks Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0821B16A407 for ; Thu, 26 Oct 2006 00:10:37 +0000 (UTC) (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 CE78A43D49 for ; Thu, 26 Oct 2006 00:10:36 +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 k9Q0Aa5q028831 for ; Thu, 26 Oct 2006 00:10:36 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k9Q0Aa58028830; Thu, 26 Oct 2006 00:10:36 GMT (envelope-from nobody) Message-Id: <200610260010.k9Q0Aa58028830@www.freebsd.org> Date: Thu, 26 Oct 2006 00:10:36 GMT From: FreeBSD Sucks To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/104820: FreeBSD Sucks 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, 26 Oct 2006 00:20:32 -0000 >Number: 104820 >Category: amd64 >Synopsis: FreeBSD Sucks >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 26 00:20:22 GMT 2006 >Closed-Date: >Last-Modified: >Originator: FreeBSD Sucks >Release: 5.4 5.5 6.1 >Organization: FreeBSD Sucks >Environment: i cant .. it wont even install >Description: I have been a strong FreeBSD supporter for some time. Unfortunetly FreeBSD has turned into one of the shitiest unix variants out there today. I had a server that would not run FreeBSD properly forcing me to use Windows or Linux. After having to deal with what I used to consider sub-par operating systems I bought a new workstation so that I could once again run FreeBSD as my workstation. But much to my suprise FreeBSD crashes on install because of various usb / sata / etc issues. Of course Windows and Linux install and run fine. What are you people doing to this operating system? I mean you cant even run on a fuqn Dell? Seriously, Linux used to suck and now they are kicking your ass. Step it up! This is a very sad day for me, I will no longer run freebsd .. as a workstation, server, paper weight. Not by choice either, but because the OS cant handle complicated and cutting edge technology like USB .. ohhhh .. or hard drives .oohhhhh I have defended this operating system long enough. I'm over it, I'm tired of hacking other peoples code just to get shit to compile, let alone actually run. Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Dee Da Dee! (seg fault) >How-To-Repeat: Try using the OS. >Fix: Use another OS. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 26 00:29:29 2006 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 8AD4C16A40F; Thu, 26 Oct 2006 00:29:29 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A8A43D6A; Thu, 26 Oct 2006 00:29:25 +0000 (GMT) (envelope-from brooks@FreeBSD.org) Received: from freefall.freebsd.org (brooks@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9Q0TPGC093785; Thu, 26 Oct 2006 00:29:25 GMT (envelope-from brooks@freefall.freebsd.org) Received: (from brooks@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9Q0TP7J093781; Thu, 26 Oct 2006 00:29:25 GMT (envelope-from brooks) Date: Thu, 26 Oct 2006 00:29:25 GMT From: Brooks Davis Message-Id: <200610260029.k9Q0TP7J093781@freefall.freebsd.org> To: freebsdsucks@hotmail.com, brooks@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/104820: FreeBSD Sucks 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, 26 Oct 2006 00:29:29 -0000 Synopsis: FreeBSD Sucks State-Changed-From-To: open->closed State-Changed-By: brooks State-Changed-When: Thu Oct 26 00:28:51 UTC 2006 State-Changed-Why: Troll. http://www.freebsd.org/cgi/query-pr.cgi?pr=104820 From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 26 07:40:26 2006 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 2890216A50B for ; Thu, 26 Oct 2006 07:40:26 +0000 (UTC) (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 D4F1D43D49 for ; Thu, 26 Oct 2006 07:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9Q7ePqZ039725 for ; Thu, 26 Oct 2006 07:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9Q7ePPC039724; Thu, 26 Oct 2006 07:40:25 GMT (envelope-from gnats) Date: Thu, 26 Oct 2006 07:40:25 GMT Message-Id: <200610260740.k9Q7ePPC039724@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Jiawei Ye" Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jiawei Ye List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 07:40:26 -0000 The following reply was made to PR amd64/88568; it has been noted by GNATS. From: "Jiawei Ye" To: bug-followup@FreeBSD.org, aron@agx.sk Cc: Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard Date: Thu, 26 Oct 2006 15:36:25 +0800 Some follow-ups here: 1. Unplug the keyboard when it is booting, plug it back in when sysinstall appears seems to be a work-around for the install CD in 6.2 Beta. 2. Upgradding to 6.2-PRE-RELEASE fixes the problem for usb keyboards. The system no longer panics, but will panic if a usb mouse is plugged in during boot phase. From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 26 19:23:02 2006 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 8535616A47B for ; Thu, 26 Oct 2006 19:23:02 +0000 (UTC) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE0C443D81 for ; Thu, 26 Oct 2006 19:22:49 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (gemini.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.8/8.13.8) with ESMTP id k9QJMl4s099814 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 26 Oct 2006 14:22:48 -0500 (CDT) (envelope-from ptroot@iaces.com) In-Reply-To: <200610260740.k9Q7ePPC039724@freefall.freebsd.org> References: <200610260740.k9Q7ePPC039724@freefall.freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <04DE95F3-9AED-4F5D-B9B8-334ED06A1845@iaces.com> Content-Transfer-Encoding: 7bit From: Paul Root Date: Thu, 26 Oct 2006 14:23:06 -0500 To: Jiawei Ye X-Mailer: Apple Mail (2.752.3) Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard 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, 26 Oct 2006 19:23:02 -0000 Ok, I'm making some progress with this. I got 6.2 Beta 2 installed with the trick in 1. When I tried plugging in the mouse after I was up, it seemed that some USB ports went away. Not sure what's going on there. A full power off will probably help that. The next thing I did, was try to get my serial ports working. PCI board from CompUSA. 16550 uarts. The dmesg sees them, but won't start them up. The messages are: sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: type 8250 or not respondingdmesg sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled In Knoppix 5.0, the ports come up and I can 'cat' to and from them. You can't alter the inittab on the CD, so I couldn't get a persistent getty on it. I could start a getty, and then when you try to login it, it kicks out and gives you an error message that you don't have a proper login process. On FreeBSD, try to start a getty on the port and the machine hangs. Reboot and have it on in ttys, and it hangs. Even doing a "cat >/dev/ttyd0" makes it hang. I guess that's because it's not properly initialized. I looked in the BIOS, and there is no place to turn on IRQ scanning. What is the dmesg trying to tell me? Paul. On Oct 26, 2006, at 7:40 AM, Jiawei Ye wrote: > The following reply was made to PR amd64/88568; it has been noted > by GNATS. > > From: "Jiawei Ye" > To: bug-followup@FreeBSD.org, aron@agx.sk > Cc: > Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not > boot with usb keyboard > Date: Thu, 26 Oct 2006 15:36:25 +0800 > > Some follow-ups here: > > 1. Unplug the keyboard when it is booting, plug it back in when > sysinstall appears seems to be a work-around for the install CD in > 6.2 > Beta. > > 2. Upgradding to 6.2-PRE-RELEASE fixes the problem for usb keyboards. > The system no longer panics, but will panic if a usb mouse is plugged > in during boot phase. > _______________________________________________ > 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" Paul Root ptroot@iaces.com From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 26 19:58:50 2006 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 CA65116A4AB for ; Thu, 26 Oct 2006 19:58:50 +0000 (UTC) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D1CD43D66 for ; Thu, 26 Oct 2006 19:58:48 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (gemini.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.8/8.13.8) with ESMTP id k9QJwkFH000262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 26 Oct 2006 14:58:47 -0500 (CDT) (envelope-from ptroot@iaces.com) In-Reply-To: <04DE95F3-9AED-4F5D-B9B8-334ED06A1845@iaces.com> References: <200610260740.k9Q7ePPC039724@freefall.freebsd.org> <04DE95F3-9AED-4F5D-B9B8-334ED06A1845@iaces.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Paul Root Date: Thu, 26 Oct 2006 14:59:05 -0500 To: Paul Root X-Mailer: Apple Mail (2.752.3) Cc: Jiawei Ye , freebsd-amd64@freebsd.org Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard 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, 26 Oct 2006 19:58:50 -0000 On Oct 26, 2006, at 2:23 PM, Paul Root wrote: > Ok, > I'm making some progress with this. I got 6.2 Beta 2 installed > with the trick in 1. When I tried plugging in the mouse after I was > up, > it seemed that some USB ports went away. Not sure what's going on > there. > A full power off will probably help that. > > The next thing I did, was try to get my serial ports working. > PCI board from CompUSA. 16550 uarts. The dmesg sees them, but won't > start > them up. > > The messages are: > > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: type 8250 or not respondingdmesg > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > I found the 'puc' device commented out in the GENERIC config. I'm building that. Oh, I failed to mention before. The DVD drive in the e521 is SATA. And it doesn't show up. I had to install via ftp. More, tomorrow. Paul. From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 27 14:08:08 2006 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 BC64316A4FA for ; Fri, 27 Oct 2006 14:08:08 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7C9943DC3 for ; Fri, 27 Oct 2006 14:06:54 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 825195DFA; Fri, 27 Oct 2006 18:06:53 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 5A46B5D6D; Fri, 27 Oct 2006 18:06:53 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k9RE6qSV002513; Fri, 27 Oct 2006 18:06:52 +0400 (MSD) (envelope-from ru) Date: Fri, 27 Oct 2006 18:06:52 +0400 From: Ruslan Ermilov To: Paul Root Message-ID: <20061027140652.GC1354@rambler-co.ru> References: <200610260740.k9Q7ePPC039724@freefall.freebsd.org> <04DE95F3-9AED-4F5D-B9B8-334ED06A1845@iaces.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qbvjkv9qwOGw/5Fx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: Jiawei Ye , freebsd-amd64@freebsd.org Subject: Re: amd64/88568: [panic] 6.0-RELEASE install cd does not boot with usb keyboard 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, 27 Oct 2006 14:08:08 -0000 --Qbvjkv9qwOGw/5Fx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 26, 2006 at 02:59:05PM -0500, Paul Root wrote: >=20 > On Oct 26, 2006, at 2:23 PM, Paul Root wrote: >=20 > >Ok, > > I'm making some progress with this. I got 6.2 Beta 2 installed > >with the trick in 1. When I tried plugging in the mouse after I was =20 > >up, > >it seemed that some USB ports went away. Not sure what's going on =20 > >there. > >A full power off will probably help that. > > > > The next thing I did, was try to get my serial ports working. > >PCI board from CompUSA. 16550 uarts. The dmesg sees them, but won't =20 > >start > >them up. > > > >The messages are: > > > >sio0: configured irq 4 not in bitmap of probed irqs 0 > >sio0: port may not be enabled > >sio0: type 8250 or not respondingdmesg > >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > >sio1: configured irq 3 not in bitmap of probed irqs 0 > >sio1: port may not be enabled > > >=20 > I found the 'puc' device commented out in the GENERIC config. I'm > building that. >=20 Alternatively, you can try the uart(4) driver instead of sio(4). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Qbvjkv9qwOGw/5Fx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFQhJ8qRfpzJluFF4RAnsTAJ4yrt1Kpo2IFRRpwUPMabv9kTTNNQCfcbEx GZf91vk2uDc6IWazG2IGRog= =CPcK -----END PGP SIGNATURE----- --Qbvjkv9qwOGw/5Fx-- From owner-freebsd-amd64@FreeBSD.ORG Sat Oct 28 07:00:35 2006 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 062E516A412 for ; Sat, 28 Oct 2006 07:00:34 +0000 (UTC) (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 8443243D5A for ; Sat, 28 Oct 2006 07:00:34 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9S70YnE005408 for ; Sat, 28 Oct 2006 07:00:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9S70YOC005405; Sat, 28 Oct 2006 07:00:34 GMT (envelope-from gnats) Resent-Date: Sat, 28 Oct 2006 07:00:34 GMT Resent-Message-Id: <200610280700.k9S70YOC005405@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, "Sergey V. Shadrin" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AD7C16A407 for ; Sat, 28 Oct 2006 06:51:32 +0000 (UTC) (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 5621043D45 for ; Sat, 28 Oct 2006 06:51: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 k9S6pV5l025380 for ; Sat, 28 Oct 2006 06:51:31 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k9S6pVMQ025379; Sat, 28 Oct 2006 06:51:31 GMT (envelope-from nobody) Message-Id: <200610280651.k9S6pVMQ025379@www.freebsd.org> Date: Sat, 28 Oct 2006 06:51:31 GMT From: "Sergey V. Shadrin" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/104875: unsupported intel Desktop Board DG965WH 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, 28 Oct 2006 07:00:35 -0000 >Number: 104875 >Category: amd64 >Synopsis: unsupported intel Desktop Board DG965WH >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 28 07:00:33 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Sergey V. Shadrin >Release: freebsd 6.2-betta2 >Organization: >Environment: >Description: This motherboard has sata and pata(ide) interfaces. I use sata disks(hdd) and ide cd-rom. When I install Freebsd system coudln't use ide cd-rom. I must install only from network. After install freebsd I couldn't start xorg. X can't work with build graphic. Can I resolve this problems? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: