From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 28 04:38:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D1E616A4D6 for ; Sun, 28 Nov 2004 04:38:35 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 504F043D54 for ; Sun, 28 Nov 2004 04:38:34 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.11] (CPE-144-133-92-247.vic.bigpond.net.au [144.133.92.247]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id iAS4cRfv009021 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 28 Nov 2004 15:38:28 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <200411261238.19311.peter@wemm.org> References: <20041116052630.GD49800@manor.msen.com> <20041126184559.GJ49800@manor.msen.com> <200411261117.02622.peter@wemm.org> <200411261238.19311.peter@wemm.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <55848170-40F7-11D9-8892-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Sun, 28 Nov 2004 15:38:21 +1100 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/533/Sun Oct 17 11:09:44 2004 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Subject: Re: How to use older libs in 32bit mode? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 04:38:35 -0000 hello On 27/11/2004, at 7:38 AM, Peter Wemm wrote: > BTW: if you have already done a buildworld, it might be possible to > rebuild just the 32 bit libraries without a full buildworld again. If > you want to try this, then "cd /usr/src; rm -rf /usr/obj/lib32; make > build32; make install32" > > Excellent. now my Hello World program works.. Great job ; thanks! Jean-Yves --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 28 04:47:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E21716A4CE for ; Sun, 28 Nov 2004 04:47:38 +0000 (GMT) Received: from web51002.mail.yahoo.com (web51002.mail.yahoo.com [206.190.38.133]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F0B043D3F for ; Sun, 28 Nov 2004 04:47:37 +0000 (GMT) (envelope-from tfcheng@yahoo.com) Received: (qmail 56125 invoked by uid 60001); 28 Nov 2004 04:47:35 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=3UdDlqewSvI8niz64Oq0bV1kSeQEH0dlbUDEsVM0iHenVhfmEmX9qDTrzjczJpmh6EOe56rsXdhxKGATRVoYGxK/qEjNg9LS40NwItC5tSaJxzgq6CGhdXtOS46rCLS4gZS7SL4Qov4Dg9w95qli8E2c76gejbqsV6C6NeTVGpg= ; Message-ID: <20041128044735.56123.qmail@web51002.mail.yahoo.com> Received: from [69.113.106.60] by web51002.mail.yahoo.com via HTTP; Sun, 28 Nov 2004 12:47:35 CST Date: Sun, 28 Nov 2004 12:47:35 +0800 (CST) From: "T.F. Cheng" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Subject: amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 04:47:38 -0000 Hi there, I am shopping for new hardware because I want to run amd64 of freebsd, but have to say that I am no expert. I have gone through mailing list, several forums and read articles until I can't read anymore... Anyway, I really need some advice about the pieces that I am getting. Here it goes: (1)M-board+CPU combo:Asus A8V Deluxe Via Socket 939 ATX Motherboard and AMD Athlon 64 3400+ Processor, which has: Chipset: VIA K8T800Pro/VT8237 Memory: 4 DIMM sockets using 184-pin DDR AGP Support: one 8X/4X AGP slot LAN:Gigabit LAN chip (Marvell 88E8001) Audio: AC '97 Sound CODEC (Realtek) (2)RAM: Ultra 512MB PC3200 DDR 400MHz Memory (3) Video card: XFX GeForce FX 5200 / 128MB DDR / AGP 8X / VGA / TV Out / Video Card (sorry, I have posted this on some forums as well) What I would like to know is that if all these are supported , as far as I know, the NIC had given trouble but had been solved. And would like to know if I can run 32-bit app on it? I think I will need some options in kernel. And it seems that this version can't be booted from floopy, has to make 3 boot CD, right? Very much appreciated for any advice, thanks!! TFC ===== Best Regards, Tsu-Fan Cheng _________________________________________________________ Do You Yahoo!? 登記免費的 @yahoo.com 中文電子郵件 @ http://chinese.mail.yahoo.com Get your free @yahoo.com address at http://chinese.mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 28 05:34:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7650116A4CE for ; Sun, 28 Nov 2004 05:34:42 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1952843D5F for ; Sun, 28 Nov 2004 05:34:42 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so404005wri for ; Sat, 27 Nov 2004 21:34:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=cx3DaH9nH1zvDOQUFmOFguId+Ci9ZAUcVUj9V+pJ8O5zfkuHLLX2fRRJqlkP5aEgKCzotER+niQCJNFbxE5HnQZ9YCHhHoTXmjMXSfiCil14dX4H77rT0f066pwDoD+54hYtcHZt3v4OrJCd3y3Pj5rr7UB8/cWsME3J2p4x3O0= Received: by 10.54.43.63 with SMTP id q63mr83834wrq; Sat, 27 Nov 2004 21:34:41 -0800 (PST) Received: by 10.54.3.2 with HTTP; Sat, 27 Nov 2004 21:34:40 -0800 (PST) Message-ID: <2fd864e0411272134409d1faa@mail.gmail.com> Date: Sat, 27 Nov 2004 21:34:40 -0800 From: Astrodog To: "T.F. Cheng" In-Reply-To: <20041128044735.56123.qmail@web51002.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <20041128044735.56123.qmail@web51002.mail.yahoo.com> cc: freebsd-amd64@freebsd.org Subject: Re: amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 05:34:42 -0000 You can use the one miniinst ISO to get things started if you want. It appears, at first glance, that that hardware should be alright. On Sun, 28 Nov 2004 12:47:35 +0800 (CST), T.F. Cheng wr= ote: > Hi there, > I am shopping for new hardware because I want to > run amd64 of freebsd, but have to say that I am no > expert. I have gone through mailing list, several > forums and read articles until I can't read anymore... > Anyway, I really need some advice about the pieces > that I am getting. > Here it goes: > (1)M-board+CPU combo:Asus A8V Deluxe Via Socket 939 > ATX Motherboard and AMD Athlon 64 3400+ Processor, > which has: > Chipset: VIA K8T800Pro/VT8237 > Memory: 4 DIMM sockets using 184-pin DDR > AGP Support: one 8X/4X AGP slot > LAN:Gigabit LAN chip (Marvell 88E8001) > Audio: AC '97 Sound CODEC (Realtek) > (2)RAM: Ultra 512MB PC3200 DDR 400MHz Memory > (3) Video card: XFX GeForce FX 5200 / 128MB DDR / AGP > 8X / VGA / TV Out / Video Card > (sorry, I have posted this on some forums as well) > What I would like to know is that if all these > are supported , as far as I know, the NIC had given > trouble but had been solved. And would like to know if > I can run 32-bit app on it? I think I will need some > options in kernel. And it seems that this version > can't be booted from floopy, has to make 3 boot CD, > right? >=20 > Very much appreciated for any advice, thanks!! >=20 > TFC >=20 > =3D=3D=3D=3D=3D > Best Regards, >=20 > Tsu-Fan Cheng >=20 > _________________________________________________________ > Do You Yahoo!? > =E7=99=BB=E8=A8=98=E5=85=8D=E8=B2=BB=E7=9A=84 @yahoo.com =E4=B8=AD=E6=96= =87=E9=9B=BB=E5=AD=90=E9=83=B5=E4=BB=B6 @ http://chinese.mail.yahoo.com > Get your free @yahoo.com address at http://chinese.mail.yahoo.com > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 28 16:34:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D17BB16A4CE for ; Sun, 28 Nov 2004 16:34:42 +0000 (GMT) Received: from web51003.mail.yahoo.com (web51003.mail.yahoo.com [206.190.38.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 6FAEB43D54 for ; Sun, 28 Nov 2004 16:34:42 +0000 (GMT) (envelope-from tfcheng@yahoo.com) Received: (qmail 43499 invoked by uid 60001); 28 Nov 2004 16:34:38 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=iKAi3NnJJkyEJvnbK33mdlb4IgN6VWZPpZ7ULB8XplGWuByiPKJ5mSThwaQYbeLM28bv6nfdIFR+Y1BSVQlBQXqiu+mJhXyfgRxLI/2JThdkcJjyn/DiS68z6+ntuWtA+FSwQIEC7Bq4MQx0Soz3SHkwXPu4HSAbh6S4a9IskcQ= ; Message-ID: <20041128163437.43496.qmail@web51003.mail.yahoo.com> Received: from [129.49.105.250] by web51003.mail.yahoo.com via HTTP; Mon, 29 Nov 2004 00:34:37 CST Date: Mon, 29 Nov 2004 00:34:37 +0800 (CST) From: "T.F. Cheng" To: Astrodog In-Reply-To: <2fd864e0411272134409d1faa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 16:34:42 -0000 thanks dogg :-) another thing is about the memory's "dual channel arch". Which one will be better? should I buy 2 256MB RAM or just one 512MB at the present? thanks!! TFC --- Astrodog 寫道： > You can use the one miniinst ISO to get things > started if you want. It > appears, at first glance, that that hardware should > be alright. > > > On Sun, 28 Nov 2004 12:47:35 +0800 (CST), T.F. Cheng > wrote: > > Hi there, > > I am shopping for new hardware because I want > to > > run amd64 of freebsd, but have to say that I am no > > expert. I have gone through mailing list, several > > forums and read articles until I can't read > anymore... > > Anyway, I really need some advice about the pieces > > that I am getting. > > Here it goes: > > (1)M-board+CPU combo:Asus A8V Deluxe Via Socket > 939 > > ATX Motherboard and AMD Athlon 64 3400+ Processor, > > which has: > > Chipset: VIA K8T800Pro/VT8237 > > Memory: 4 DIMM sockets using 184-pin DDR > > AGP Support: one 8X/4X AGP slot > > LAN:Gigabit LAN chip (Marvell 88E8001) > > Audio: AC '97 Sound CODEC (Realtek) > > (2)RAM: Ultra 512MB PC3200 DDR 400MHz Memory > > (3) Video card: XFX GeForce FX 5200 / 128MB DDR / > AGP > > 8X / VGA / TV Out / Video Card > > (sorry, I have posted this on some forums as well) > > What I would like to know is that if all > these > > are supported , as far as I know, the NIC had > given > > trouble but had been solved. And would like to > know if > > I can run 32-bit app on it? I think I will need > some > > options in kernel. And it seems that this version > > can't be booted from floopy, has to make 3 boot > CD, > > right? > > > > Very much appreciated for any advice, thanks!! > > > > TFC > > > > ===== > > Best Regards, > > > > Tsu-Fan Cheng > > > > > _________________________________________________________ > > Do You Yahoo!? > > 登記免費的 @yahoo.com 中文電子郵件 @ > http://chinese.mail.yahoo.com > > Get your free @yahoo.com address at > http://chinese.mail.yahoo.com > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to > "freebsd-amd64-unsubscribe@freebsd.org" > > > ===== Best Regards, Tsu-Fan Cheng _________________________________________________________ Do You Yahoo!? 登記免費的 @yahoo.com 中文電子郵件 @ http://chinese.mail.yahoo.com Get your free @yahoo.com address at http://chinese.mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 07:24:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0097C16A4CE; Mon, 29 Nov 2004 07:24:32 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8345F43D5C; Mon, 29 Nov 2004 07:24:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAT7OUIj014633; Mon, 29 Nov 2004 02:24:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAT7OUao015182; Mon, 29 Nov 2004 02:24:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A666E7306E; Mon, 29 Nov 2004 02:24:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129072430.A666E7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 02:24:30 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 07:24:32 -0000 TB --- 2004-11-29 05:43:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 05:43:43 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-29 05:43:43 - checking out the source tree TB --- 2004-11-29 05:43:43 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-29 05:43:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 06:01:31 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 06:01:31 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-29 06:01:31 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cp loader.sym loader.bin strip -R .comment -R .note loader.bin btxld -v -f aout -e 0x200000 -o loader -l /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../btx/btxldr/btxldr -b /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../btx/btx/btx loader.bin kernel: ver=1.01 size=780 load=9000 entry=9010 map=16M pgctl=0:33 client: fmt=elf size=39530 text=32cbc data=53cc bss=6114 entry=0 output: fmt=aout size=3c000 text=1000 data=3a000 org=200000 entry=200000 cat /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../common/help.common /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/help.i386 | awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../common/merge_help.awk > loader.help make: don't know how to make /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/loader.rc. Stop *** Error code 2 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/boot. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-29 07:24:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 07:24:30 - ERROR: failed to build world TB --- 2004-11-29 07:24:30 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 07:54:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA90616A4CE for ; Mon, 29 Nov 2004 07:54:12 +0000 (GMT) Received: from web53209.mail.yahoo.com (web53209.mail.yahoo.com [206.190.39.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 6490443D31 for ; Mon, 29 Nov 2004 07:54:12 +0000 (GMT) (envelope-from tommyhadiwibowo@yahoo.com) Received: (qmail 12435 invoked by uid 60001); 29 Nov 2004 07:54:11 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=pGozI9OdratYkxJRx1Woorvm7Sv3lPw5kEGtq4fjRX63CpVmaQco1wwYEhG/e6BjJaIPcTAMKySPf9RYbEOamnHXdXyr07p1cTNNRmRfb4lBNmIRCvHZ+m/LVbIUDAhukXtzHkQdrBM6D0t0D/pW48Im+vZ/TI5nzRBg1C1FWUE= ; Message-ID: <20041129075411.12433.qmail@web53209.mail.yahoo.com> Received: from [202.133.84.3] by web53209.mail.yahoo.com via HTTP; Sun, 28 Nov 2004 23:54:11 PST Date: Sun, 28 Nov 2004 23:54:11 -0800 (PST) From: tommy barabai To: freebsd-AMD64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 07:54:13 -0000 __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 11:01:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DF5016A4D4 for ; Mon, 29 Nov 2004 11:01:59 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DE2243D1F for ; Mon, 29 Nov 2004 11:01:59 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iATB1wxi007989 for ; Mon, 29 Nov 2004 11:01:59 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iATB1wBc007983 for freebsd-amd64@freebsd.org; Mon, 29 Nov 2004 11:01:58 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 29 Nov 2004 11:01:58 GMT Message-Id: <200411291101.iATB1wBc007983@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 11:01:59 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2004/11/06] amd64/73603 amd64 kernel build amd64 fails when device ath 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/04] amd64/72333 amd64 vinum doesn't scan for drives on slices o o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during 12 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve a [2004/09/12] amd64/71674 amd64 static libraries cannot be linked when bu o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 21:13:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37EB616A4CE for ; Mon, 29 Nov 2004 21:13:42 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D21A243D49 for ; Mon, 29 Nov 2004 21:13:41 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iATLDfYq026665 for ; Mon, 29 Nov 2004 13:13:41 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iATLDfqG026664 for freebsd-amd64@freebsd.org; Mon, 29 Nov 2004 13:13:41 -0800 (PST) (envelope-from sgk) Date: Mon, 29 Nov 2004 13:13:41 -0800 From: Steve Kargl To: freebsd-amd64@freebsd.org Message-ID: <20041129211341.GA26548@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:13:42 -0000 kmem_suballoc: bad status return of 3 panic: kmem_suballoc cpuid = 0 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x37 panic() at painc+0x1d1 kmem_suballoc() at kmem_suballoc+0x93 kmeminit() at kmeminit+0x16d mi_startuup() at mi_startup+0xb6 btext90 at btext+0x2c KDB: enter: panic [thread pid 0 tid 0] This is a Tyan K8S Pro motherboard with 16 GB of PC2700 Cosair ECC memory. The BIOS was flashed to the latest available from Tyan. The scheduler is 4BSD. There are no ATA devices in the system and no ATA subsystem in the kernel. This a SCSI only box. World and kernel were rebuilt today with CFLAGS=-O -pipe and COPTFLAGS=-O -pipe. If I set hw.physmem="#G" n /boot/loader.conf where # is less than or equal to 8 the box boots up (see dmesg below). If # > 8, then we have the above panic. Any ideas where to look for the a fix? -- Steve Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #0: Mon Nov 29 12:18:32 PST 2004 root@dhcp-78-96.apl.washington.edu:/home/obj/usr/src/sys/SPEW WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.63-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 8589934592 (8192 MB) avail memory = 8252538880 (7870 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci3: at device 5.0 (no driver attached) pci3: at device 6.0 (no driver attached) fxp0: port 0xa400-0xa43f mem 0xfeaa0000-0xfeabffff,0xfeafb000-0xfeafbfff irq 18 at device 8.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:2a:59:e7 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) amdpm0: port 0xe0-0xff,0xcc00-0xcc1f irq 19 at device 7.2 on pci0 amdpm0: could not map i/o space device_attach: amdpm0 attach returned 6 pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 ahd0: port 0x9c00-0x9cff,0x9000-0x90ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs ahd1: port 0x9400-0x94ff,0x9800-0x98ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs bge0: mem 0xfc8a0000-0xfc8affff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci2 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:2a:da:46 bge1: mem 0xfc8d0000-0xfc8dffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci2 miibus2: on bge1 brgphy1: on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:2a:da:47 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 pci_link0: irq 15 on acpi0 pci_link1: irq 9 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 10 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec Waiting 3 seconds for SCSI devices to settle acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% SMP: AP CPU #1 Launched! cd0 at ahd0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da1 at ahd0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da0 at ahd0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 16 files 8 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 21:39:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77F1E16A4CE for ; Mon, 29 Nov 2004 21:39:18 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8712243D55 for ; Mon, 29 Nov 2004 21:39:17 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id I7YMTM00.WWT for ; Mon, 29 Nov 2004 13:39:22 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004112913414502816 for ; Mon, 29 Nov 2004 13:41:45 -0800 From: "Vinod Kashyap" To: freebsd-amd64@freebsd.org Date: Mon, 29 Nov 2004 13:39:12 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: Subject: FreeBSD 5.3 installation problems on EM64T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:39:18 -0000 I am trying to install FreeBSD 5.3 for amd64/EM64T on a 3ware 9xxx controller, plugged into a Supermicro X6DH8-G motherboard with a single Intel Nocona 800 MHz processor (with EM64T support). Once I boot off the CD (with ACPI disabled -- the system hangs if ACPI is enabled), sysinstall runs fine (the 3ware controller and all its connected devices are detected, and I can do fdisk and disklabel; the CD drive is detected too), until it's time to start copying files from the CD. After the initial "Starting an emergency holographic shell" message, I see the following error: "The disc in your drive looks more like an Audio disc than a FreeBSD releas= e." I have created the installation CD just like I created all my previous ones that worked (downloading the ISO from ftp.freebsd.org and then burning it using Nero). The md5 of the ISO image checks ok. I tried burning the CD on 2 different machines, with the same result. I tried using 2 different CD drives (TSST CDW/DVD TS-H492A/TB02, Sony CD-ROM CDU4821/S0.Q) and it made no difference. On Alt-F2, I see the following: DEBUG: Notify: Copying the boot floppy to /stand on root filesystem /mnt/stand /mnt/stand/etc ... ... ... /mnt/etc/services /mnt/etc/group 23 blocks DEBUG: Generating /etc/fstab file Does anyone know what's going on here? Thanks, Vinod. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 21:41:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DA2F16A4D0 for ; Mon, 29 Nov 2004 21:41:44 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E0FA43D31 for ; Mon, 29 Nov 2004 21:41:43 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iATLff2h023486; Mon, 29 Nov 2004 15:41:42 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41AB9795.7020805@jrv.org> Date: Mon, 29 Nov 2004 15:41:41 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20041129211341.GA26548@troutmask.apl.washington.edu> In-Reply-To: <20041129211341.GA26548@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:41:44 -0000 I'm not convinced that the bounce-buffer scheme works on amd64 at all. I don't think twe, ata or bge work (individually or in combination) with more than 4GB of RAM. Are you using a bge NIC or USB, or any other driver that needs bounce buffer, 1394? Which SCSI driver? Is this 5.3 release? 5.2.1 worked for me. The bounce-buffer code in amd64 has changed since then but I haven't been able to figure it out. I wonder how much memory is in Tinderbox? Steve Kargl wrote: >kmem_suballoc: bad status return of 3 >panic: kmem_suballoc >cpuid = 0 >KDB: stack backtrace: >kdb_backtrace() at kdb_backtrace+0x37 >panic() at painc+0x1d1 >kmem_suballoc() at kmem_suballoc+0x93 >kmeminit() at kmeminit+0x16d >mi_startuup() at mi_startup+0xb6 >btext90 at btext+0x2c >KDB: enter: panic >[thread pid 0 tid 0] > >This is a Tyan K8S Pro motherboard with 16 GB of PC2700 >Cosair ECC memory. The BIOS was flashed to the latest >available from Tyan. The scheduler is 4BSD. There are >no ATA devices in the system and no ATA subsystem in >the kernel. This a SCSI only box. World and kernel >were rebuilt today with CFLAGS=-O -pipe and >COPTFLAGS=-O -pipe. > >If I set hw.physmem="#G" n /boot/loader.conf where # is >less than or equal to 8 the box boots up (see dmesg below). >If # > 8, then we have the above panic. > >Any ideas where to look for the a fix? > > > From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 21:52:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B064B16A4CE for ; Mon, 29 Nov 2004 21:52:32 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60F8743D69 for ; Mon, 29 Nov 2004 21:52:32 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iATLqTs7023863; Mon, 29 Nov 2004 15:52:30 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41AB9A1D.9010501@jrv.org> Date: Mon, 29 Nov 2004 15:52:29 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 5.3 installation problems on EM64T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:52:32 -0000 How much memory do you have? Are those ATAPI CD drives? The firmware that shipped with the twa/9xxx board I bought ~ 2weeks ago would hang under load after a few hours. The firmware version below has been running under load, with 4GB, for about a week: --- Nov 26 23:17:32 kernel: twa0: 12 ports, Firmware FE9X 2.02.00.012, BIOS BE9X 2.02.01.037 Vinod Kashyap wrote: >I am trying to install FreeBSD 5.3 for amd64/EM64T on a >3ware 9xxx controller, plugged into a Supermicro X6DH8-G >motherboard with a single Intel Nocona 800 MHz processor >(with EM64T support). > >Once I boot off the CD (with ACPI disabled -- the system hangs >if ACPI is enabled), sysinstall runs fine (the 3ware controller >and all its connected devices are detected, and I can do fdisk >and disklabel; the CD drive is detected too), until it's time to start >copying files from the CD. After the initial "Starting an emergency >holographic shell" message, I see the following error: >"The disc in your drive looks more like an Audio disc than a FreeBSD release." > >I have created the installation CD just like I created all my previous >ones that worked (downloading the ISO from ftp.freebsd.org and then >burning it using Nero). The md5 of the ISO image checks ok. I tried >burning the CD on 2 different machines, with the same result. I tried >using 2 different CD drives (TSST CDW/DVD TS-H492A/TB02, >Sony CD-ROM CDU4821/S0.Q) and it made no difference. > >On Alt-F2, I see the following: >DEBUG: Notify: Copying the boot floppy to /stand on root filesystem >/mnt/stand >/mnt/stand/etc >... >... >... >/mnt/etc/services >/mnt/etc/group >23 blocks >DEBUG: Generating /etc/fstab file > >Does anyone know what's going on here? > > >Thanks, > >Vinod. > > From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 21:53:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEA5316A4CE for ; Mon, 29 Nov 2004 21:53:22 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 960A843D58 for ; Mon, 29 Nov 2004 21:53:22 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iATLrM2N026892; Mon, 29 Nov 2004 13:53:22 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iATLrMqs026891; Mon, 29 Nov 2004 13:53:22 -0800 (PST) (envelope-from sgk) Date: Mon, 29 Nov 2004 13:53:22 -0800 From: Steve Kargl To: "James R. Van Artsalen" Message-ID: <20041129215322.GA26806@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AB9795.7020805@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AB9795.7020805@jrv.org> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:53:22 -0000 On Mon, Nov 29, 2004 at 03:41:41PM -0600, James R. Van Artsalen wrote: > I'm not convinced that the bounce-buffer scheme works on amd64 at all. > I don't think twe, ata or bge work (individually or in combination) with > more than 4GB of RAM. 8GB of RAM seems to work without a problem. > Are you using a bge NIC or USB, or any other driver that needs bounce > buffer, 1394? Which SCSI driver? The K8S Pro has 2 bge nics on the motherboard. I have the driver in the kernel, but neither nic is currently being used. USB is compiled into the kernel and is only used when I transfer files to a memory stick (ie., it's seldomly used). Two SCSI drives are attached to an Adaptec AIC7902 Ultra320 SCSI adapter that is also on the motherboard. > Is this 5.3 release? 5.2.1 worked for me. The bounce-buffer code in > amd64 has changed since then but I haven't been able to figure it out. 6.0-CURRENT from today's sources, but the problem goes back to at least August. You can find other posts by me about panics with >8GB or ram. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 22:14:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EABE316A4CE for ; Mon, 29 Nov 2004 22:14:14 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01F4743D5D for ; Mon, 29 Nov 2004 22:14:14 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id I7YOFU02.0WQ; Mon, 29 Nov 2004 14:14:18 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004112914164503408 ; Mon, 29 Nov 2004 14:16:46 -0800 From: "Vinod Kashyap" To: "James R. Van Artsalen" Date: Mon, 29 Nov 2004 14:14:08 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: cc: freebsd-amd64@freebsd.org Subject: RE: FreeBSD 5.3 installation problems on EM64T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 22:14:15 -0000 > -----Original Message----- > From: James R. Van Artsalen [mailto:james@jrv.org] > Sent: Monday, November 29, 2004 1:52 PM > To: Vinod Kashyap > Cc: freebsd-amd64@freebsd.org > Subject: Re: FreeBSD 5.3 installation problems on EM64T > = > = > How much memory do you have? Are those ATAPI CD drives? > = I had 6 GB all along, and was just trying 2 GB. Well, the installation went through!! I am surprised that the error resulting out of more memory in the system looks as bizarre as: "The disc in your drive looks more like an Audio disc than a = FreeBSD release." Thanks for the help! ACPI still doesn't work though. And yes, both are ATAPI/IDE CDROM drives. > The firmware that shipped with the twa/9xxx board I bought ~ = > 2weeks ago = > would hang under load after a few hours. The firmware = > version below has = > been running under load, with 4GB, for about a week: > = What versions of the driver/firmware were you using? You might want to contact 3ware support if you have problems. > --- Nov 26 23:17:32 kernel: twa0: 12 ports, Firmware FE9X = > 2.02.00.012, = > BIOS BE9X 2.02.01.037 > = These are the versions I am using... > Vinod Kashyap wrote: > = > >I am trying to install FreeBSD 5.3 for amd64/EM64T on a > >3ware 9xxx controller, plugged into a Supermicro X6DH8-G > >motherboard with a single Intel Nocona 800 MHz processor > >(with EM64T support). > > > >Once I boot off the CD (with ACPI disabled -- the system hangs > >if ACPI is enabled), sysinstall runs fine (the 3ware controller > >and all its connected devices are detected, and I can do fdisk > >and disklabel; the CD drive is detected too), until it's = > time to start > >copying files from the CD. After the initial "Starting an emergency > >holographic shell" message, I see the following error: > >"The disc in your drive looks more like an Audio disc than a = > FreeBSD release." > > > >I have created the installation CD just like I created all = > my previous > >ones that worked (downloading the ISO from ftp.freebsd.org and then > >burning it using Nero). The md5 of the ISO image checks ok. I tried > >burning the CD on 2 different machines, with the same = > result. I tried > >using 2 different CD drives (TSST CDW/DVD TS-H492A/TB02, > >Sony CD-ROM CDU4821/S0.Q) and it made no difference. > > > >On Alt-F2, I see the following: > >DEBUG: Notify: Copying the boot floppy to /stand on root filesystem > >/mnt/stand > >/mnt/stand/etc > >... > >... > >... > >/mnt/etc/services > >/mnt/etc/group > >23 blocks > >DEBUG: Generating /etc/fstab file > > > >Does anyone know what's going on here? > > > > > >Thanks, > > > >Vinod. > > = > > > = > = > From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:15:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3550916A4CE for ; Mon, 29 Nov 2004 23:15:54 +0000 (GMT) Received: from priv-edtnes27.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 948C943D45 for ; Mon, 29 Nov 2004 23:15:53 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-147-63.abhsia.telus.net ([137.186.147.63]) by priv-edtnes27.telusplanet.netESMTP <20041129231553.POJX27698.priv-edtnes27.telusplanet.net@d137-186-147-63.abhsia.telus.net> for ; Mon, 29 Nov 2004 16:15:53 -0700 From: James Earl To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Tue, 30 Nov 2004 07:17:52 -0700 Message-Id: <1101824272.647.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:15:54 -0000 Hi, I just recently setup an Athlon 64 system. I'm using an Asus A8V Deluxe (rev 2.0) motherboard, and a Matrox G550 video card. I got the video card working under FreeBSD i386, but I'm having issues under FreeBSD amd64. I read a previous post that makes me believe the drivers won't work on an amd64 system. However, one additional difference I noticed between booting up FreeBSD amd64 vs. FreeBSD i386, is that my agp device doesn't show up under FreeBSD amd64 (even after adding 'device agp' under FreeBSD amd64 kernel). Does agp work under FreeBSD amd64? If the Matrox drivers are architecture dependent, is it possible to compile a driver using the driver source Matrox provides? James From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:32:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B515A16A4CE; Mon, 29 Nov 2004 23:32:11 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C6C443D5C; Mon, 29 Nov 2004 23:32:11 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iATNWBZ8027472; Mon, 29 Nov 2004 15:32:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iATNWBKo027471; Mon, 29 Nov 2004 15:32:11 -0800 (PST) (envelope-from sgk) Date: Mon, 29 Nov 2004 15:32:11 -0800 From: Steve Kargl To: freebsd-amd64@freebsd.org Message-ID: <20041129233211.GA27426@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041129211341.GA26548@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:32:11 -0000 On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > kmem_suballoc: bad status return of 3 > panic: kmem_suballoc > cpuid = 0 > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x37 > panic() at painc+0x1d1 > kmem_suballoc() at kmem_suballoc+0x93 > kmeminit() at kmeminit+0x16d > mi_startuup() at mi_startup+0xb6 > btext90 at btext+0x2c > KDB: enter: panic > [thread pid 0 tid 0] > > This is a Tyan K8S Pro motherboard with 16 GB of PC2700 > Cosair ECC memory. The BIOS was flashed to the latest > available from Tyan. The scheduler is 4BSD. There are > no ATA devices in the system and no ATA subsystem in > the kernel. This a SCSI only box. World and kernel > were rebuilt today with CFLAGS=-O -pipe and > COPTFLAGS=-O -pipe. > > If I set hw.physmem="#G" n /boot/loader.conf where # is > less than or equal to 8 the box boots up (see dmesg below). > If # > 8, then we have the above panic. > > Any ideas where to look for the a fix? > (dmesg snipped) (CC'd to -current because the may impact any system with >8 GB of ram) As a data point, I've downloaded, burned, and booted the netbsd/amd64 ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB of memory on the system. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:33:51 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1158616A4CE; Mon, 29 Nov 2004 23:33:51 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0DD43D39; Mon, 29 Nov 2004 23:33:50 +0000 (GMT) (envelope-from peter@FreeBSD.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iATNXoQl022758; Mon, 29 Nov 2004 23:33:50 GMT (envelope-from peter@freefall.freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iATNXoSt022754; Mon, 29 Nov 2004 23:33:50 GMT (envelope-from peter) Date: Mon, 29 Nov 2004 23:33:50 GMT From: Peter Wemm Message-Id: <200411292333.iATNXoSt022754@freefall.freebsd.org> To: peter@FreeBSD.org, freebsd-amd64@FreeBSD.org, sam@FreeBSD.org Subject: Re: amd64/73603: kernel build amd64 fails when device ath and device ath_hal included X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:33:51 -0000 Synopsis: kernel build amd64 fails when device ath and device ath_hal included Responsible-Changed-From-To: freebsd-amd64->sam Responsible-Changed-By: peter Responsible-Changed-When: Mon Nov 29 23:32:59 GMT 2004 Responsible-Changed-Why: Sam owns the ath hal module. http://www.freebsd.org/cgi/query-pr.cgi?pr=73603 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:41:18 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12FDB16A4F1; Mon, 29 Nov 2004 23:41:13 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0538F43D5D; Mon, 29 Nov 2004 23:41:06 +0000 (GMT) (envelope-from peter@FreeBSD.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iATNf5RC023027; Mon, 29 Nov 2004 23:41:05 GMT (envelope-from peter@freefall.freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iATNf3o9023019; Mon, 29 Nov 2004 23:41:03 GMT (envelope-from peter) Date: Mon, 29 Nov 2004 23:41:03 GMT From: Peter Wemm Message-Id: <200411292341.iATNf3o9023019@freefall.freebsd.org> To: jramirez@diatel.upm.es, peter@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/72333: vinum doesn't scan for drives on slices on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:41:18 -0000 Synopsis: vinum doesn't scan for drives on slices on amd64 State-Changed-From-To: open->closed State-Changed-By: peter State-Changed-When: Mon Nov 29 23:40:25 GMT 2004 State-Changed-Why: Patch to enable slice scanning for amd64 committed as vinumio.c:1.100.2.1 in RELENG_5 http://www.freebsd.org/cgi/query-pr.cgi?pr=72333 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:44:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9F6916A4CE for ; Mon, 29 Nov 2004 23:44:30 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F7D43D58 for ; Mon, 29 Nov 2004 23:44:27 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iATNiR8U011774; Mon, 29 Nov 2004 18:44:27 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 29 Nov 2004 18:44:14 -0500 User-Agent: KMail/1.6.2 References: <1101824272.647.8.camel@localhost> In-Reply-To: <1101824272.647.8.camel@localhost> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200411291844.14522.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:44:30 -0000 On Tuesday 30 November 2004 09:17 am, James Earl wrote: > Hi, > > I just recently setup an Athlon 64 system. I'm using an Asus A8V > Deluxe (rev 2.0) motherboard, and a Matrox G550 video card. I got > the video card working under FreeBSD i386, but I'm having issues > under FreeBSD amd64. > > I read a previous post that makes me believe the drivers won't work > on an amd64 system. However, one additional difference I noticed > between booting up FreeBSD amd64 vs. FreeBSD i386, is that my agp > device doesn't show up under FreeBSD amd64 (even after adding > 'device agp' under FreeBSD amd64 kernel). I don't know about G550 but agp driver doesn't really matter if you don't want DRI, i. e., 3D acceleration. > Does agp work under FreeBSD amd64? Can you try the following patch? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?r1=1.2&r2=1.3 Jung-uk Kim > If the Matrox drivers are architecture dependent, is it possible to > compile a driver using the driver source Matrox provides? > > James From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 29 23:53:59 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1542216A4CF; Mon, 29 Nov 2004 23:53:59 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3AE643D5D; Mon, 29 Nov 2004 23:53:58 +0000 (GMT) (envelope-from peter@FreeBSD.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iATNrwsJ023382; Mon, 29 Nov 2004 23:53:58 GMT (envelope-from peter@freefall.freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iATNrwZ1023378; Mon, 29 Nov 2004 23:53:58 GMT (envelope-from peter) Date: Mon, 29 Nov 2004 23:53:58 GMT From: Peter Wemm Message-Id: <200411292353.iATNrwZ1023378@freefall.freebsd.org> To: pete@twisted.org.uk, peter@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:53:59 -0000 Synopsis: static libraries cannot be linked when building shared libraries State-Changed-From-To: analyzed->closed State-Changed-By: peter State-Changed-When: Mon Nov 29 23:51:58 GMT 2004 State-Changed-Why: Committed in 6.x some time ago, and now fixed in RELENG_5 as well. The bogus disabling of libobjc.so was reverted for amd64. The reasons for doing it were probably only relevant to i386 back in 1998. http://www.freebsd.org/cgi/query-pr.cgi?pr=71674 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 00:20:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E6C916A4D2 for ; Tue, 30 Nov 2004 00:20:11 +0000 (GMT) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E99B43D31 for ; Tue, 30 Nov 2004 00:20:06 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-147-63.abhsia.telus.net ([137.186.147.63]) by priv-edtnes46.telusplanet.netESMTP <20041130002005.ILMJ25737.priv-edtnes46.telusplanet.net@d137-186-147-63.abhsia.telus.net>; Mon, 29 Nov 2004 17:20:05 -0700 From: James Earl To: Jung-uk Kim In-Reply-To: <200411291844.14522.jkim@niksun.com> References: <1101824272.647.8.camel@localhost> <200411291844.14522.jkim@niksun.com> Content-Type: text/plain Date: Tue, 30 Nov 2004 17:20:41 -0700 Message-Id: <1101860441.603.10.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 00:20:11 -0000 On Mon, 2004-11-29 at 18:44 -0500, Jung-uk Kim wrote: > On Tuesday 30 November 2004 09:17 am, James Earl wrote: > > Hi, > > > > I just recently setup an Athlon 64 system. I'm using an Asus A8V > > Deluxe (rev 2.0) motherboard, and a Matrox G550 video card. I got > > the video card working under FreeBSD i386, but I'm having issues > > under FreeBSD amd64. > > > > I read a previous post that makes me believe the drivers won't work > > on an amd64 system. However, one additional difference I noticed > > between booting up FreeBSD amd64 vs. FreeBSD i386, is that my agp > > device doesn't show up under FreeBSD amd64 (even after adding > > 'device agp' under FreeBSD amd64 kernel). > > I don't know about G550 but agp driver doesn't really matter if you > don't want DRI, i. e., 3D acceleration. > > > Does agp work under FreeBSD amd64? > > Can you try the following patch? > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?r1=1.2&r2=1.3 Thanks! That patch worked. A .rej file was created... I'm not sure if that's important or not? I can provide the contents if you need them. DRI isn't extremely important to me. Getting a working mga_hal_drv.o is much more important however... otherwise I can't use the DVI output on the graphics card. I realize now, that's not really a FreeBSD amd64 problem though. > > Jung-uk Kim > > > If the Matrox drivers are architecture dependent, is it possible to > > compile a driver using the driver source Matrox provides? > > > > James From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 00:53:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E2B716A4CF for ; Tue, 30 Nov 2004 00:53:16 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C14BA43D2D for ; Tue, 30 Nov 2004 00:53:15 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iAU0rD9q013033; Mon, 29 Nov 2004 19:53:15 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: James Earl Date: Mon, 29 Nov 2004 19:52:58 -0500 User-Agent: KMail/1.6.2 References: <1101824272.647.8.camel@localhost> <200411291844.14522.jkim@niksun.com> <1101860441.603.10.camel@localhost> In-Reply-To: <1101860441.603.10.camel@localhost> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200411291952.59151.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 00:53:16 -0000 On Tuesday 30 November 2004 07:20 pm, James Earl wrote: > On Mon, 2004-11-29 at 18:44 -0500, Jung-uk Kim wrote: > > On Tuesday 30 November 2004 09:17 am, James Earl wrote: > > > Hi, > > > > > > I just recently setup an Athlon 64 system. I'm using an Asus > > > A8V Deluxe (rev 2.0) motherboard, and a Matrox G550 video card. > > > I got the video card working under FreeBSD i386, but I'm > > > having issues under FreeBSD amd64. > > > > > > I read a previous post that makes me believe the drivers won't > > > work on an amd64 system. However, one additional difference I > > > noticed between booting up FreeBSD amd64 vs. FreeBSD i386, is > > > that my agp device doesn't show up under FreeBSD amd64 (even > > > after adding 'device agp' under FreeBSD amd64 kernel). > > > > I don't know about G550 but agp driver doesn't really matter if > > you don't want DRI, i. e., 3D acceleration. > > > > > Does agp work under FreeBSD amd64? > > > > Can you try the following patch? > > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.dif > >f?r1=1.2&r2=1.3 > > Thanks! That patch worked. A .rej file was created... I'm not > sure if that's important or not? I can provide the contents if you > need them. If that worked, agp_amd64.c.rej is probably FreeBSD ID line and it's okay. > DRI isn't extremely important to me. Getting a working > mga_hal_drv.o is much more important however... otherwise I can't > use the DVI output on the graphics card. I realize now, that's not > really a FreeBSD amd64 problem though. Ah, I see. mga_hal_drv.o is closed source and only available for i386 AFAIK. Jung-uk Kim > > Jung-uk Kim > > > > > If the Matrox drivers are architecture dependent, is it > > > possible to compile a driver using the driver source Matrox > > > provides? > > > > > > James From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 01:05:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3365116A4CE; Tue, 30 Nov 2004 01:05:48 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id F361743D3F; Tue, 30 Nov 2004 01:05:47 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 6572CC747; Mon, 29 Nov 2004 20:05:47 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 0FFE66819; Mon, 29 Nov 2004 20:05:40 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16811.51043.987275.174410@canoe.dclg.ca> Date: Mon, 29 Nov 2004 20:05:39 -0500 To: freebsd-amd64@freebsd.org, freebsd-hackers@freebsd.org From: freebsd-list@dclg.ca X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid Subject: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 01:05:48 -0000 After a bunch of frustrating debugging, I've tenatively come to the conclusion that the isp(4) driver is not 64 bit safe --- at the very least insofar as the amd64 platform is concerned. The test setup was a quad opteron 248 system connected via two isp 2340 cards to switches which interconnect to an EMC^2 disk array. I've made a couple of interim posts on this subject. The message from scsi_da.c indicates the correct probe is received from the disk. In the test, it was a 131 gig disk of 512 byte sectors. However, by the time we get to cam_calc_geometry() in cam.c, the structure is corrupt --- containing bad values for both volume_size and sector_size. The data is bogus enough at this point, that it can't be repaired ... and I gave up on the "quick fix" effort. Origionally, it manifested as a divide by zero error (the block size was so huge, it brought the denominator in the first few lines to zero). But both the block_size and the volume_size are bogus making efforts by geom to taste the last sector fail. The isp driver is quite complex. I havn't encountered much of the SCSI or CAM stack before. It would seem a brief overview of where things go from the momment when scsi_da prints out the correct size to the point at which cam_calc_geometry() receives corrupt data would help greately. Our hardware vendor is going to try to obtain test hardware for the LSI logic HBA and an Adaptec HBA --- so we can test them. The test machine remains somewhat available, but it looks like the production machines will be linux (unless I can solve this problem this week). Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 02:39:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F38C416A4CE; Tue, 30 Nov 2004 02:39:49 +0000 (GMT) Received: from skippyii.compar.com (skippyii.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF4943D55; Tue, 30 Nov 2004 02:39:49 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [69.193.82.185])iAU2l4K2022765; Mon, 29 Nov 2004 21:47:05 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <003801c4d685$81192640$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: , , References: <16811.51043.987275.174410@canoe.dclg.ca> Date: Mon, 29 Nov 2004 21:37:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 02:39:50 -0000 Dave, > After a bunch of frustrating debugging, I've tenatively come to the > conclusion that the isp(4) driver is not 64 bit safe --- at the very > least insofar as the amd64 platform is concerned. > > The test setup was a quad opteron 248 system connected via two isp > 2340 cards to switches which interconnect to an EMC^2 disk array. > I've made a couple of interim posts on this subject. > > The message from scsi_da.c indicates the correct probe is received > from the disk. In the test, it was a 131 gig disk of 512 byte > sectors. However, by the time we get to cam_calc_geometry() in > cam.c, the structure is corrupt --- containing bad values for both > volume_size and sector_size. Here's what I found by walking through the code. Mind you, given that I'm no expert on this code either, I may be missing things. 1) cam/scsi/scsi_da.c::dadone() function DA_CCB_PROBE2 probes the device for capacity information. 2) cam/scsi/scsi_da.c::dadone() function DA_CCB_PROBE2 then calls dasetgeom(). The parameters to dasetgeom() are obtained from 1), are updated in softc->params and later the ccg. All variables involved in these assignments have matching types, so there should be no truncation. 3) dasetgeom() then calls xpt_action() [ which I'm assuming is redirected to dev/isp/isp_freebsd.c::isp_action() ] with a function id of XPT_CALC_GEOMETRY, which ultimately calls cam_calc_geometry(). 4) cam/scsi/scsi_da.c::dadone() function DA_CCB_PROBE2 then prints out a probe of the device size. You indicate that this probe is done properly. >From what I see, cam_calc_geometry() is called *before* the device probe prints out the device size, so I'm unsure of how what you are describing can occur. Have you built & run a kernel compiled with "options CAMDEBUG" ? This may provide more insight into where things are going wrong. -- Matt Emmerton From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 03:03:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D48D016A4CE; Tue, 30 Nov 2004 03:03:52 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C6A143D4C; Tue, 30 Nov 2004 03:03:52 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 6AC0BCE6B; Mon, 29 Nov 2004 22:03:51 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id C8056681A; Mon, 29 Nov 2004 22:03:43 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16811.58127.759026.560570@canoe.dclg.ca> Date: Mon, 29 Nov 2004 22:03:43 -0500 To: "Matt Emmerton" In-Reply-To: <003801c4d685$81192640$1200a8c0@gsicomp.on.ca> References: <16811.51043.987275.174410@canoe.dclg.ca> <003801c4d685$81192640$1200a8c0@gsicomp.on.ca> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 03:03:53 -0000 >>>>> "Matt" == Matt Emmerton writes: Matt> You indicate that this probe is done properly. >> From what I see, cam_calc_geometry() is called *before* the device >> probe Matt> prints out the device size, so I'm unsure of how what you are Matt> describing can occur. Well... cam_calc_geometry seems to get called quite a bit. Almost everytime you touch the disk, in fact. fsck'ing a partition calls it, for instance. Console access is personally expensive (much driving, for instance), but from memory the debugging I put in cam_calc_geometry() would print before the correct output from dadone(). Your description reminds me of this --- but it's no less vexing that the output from dadone() has the correct sector and volume size and the ccg in cam_calc_geometry() has bogus data. I don't know if it's significant, but the correct numbers were: 279353684 sectors of 512 bytes The ccg structure comes up with: 3737169375 sectors of 3737169374 bytes Not entirely sensible. Interesting that they're close values. However, with different things on the stack, the values changed. Matt> Have you built & run a kernel compiled with "options CAMDEBUG" ? Matt> This may provide more insight into where things are going wrong. I put CAMDEBUG in the kernel, but it didn't seem to change the output that much. It seemed to dump the control block showing when geom tried to access the high block number --- and failed, but nothing else particularly useful. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 05:16:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 692B116A4CE for ; Tue, 30 Nov 2004 05:16:31 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1A2743D48 for ; Tue, 30 Nov 2004 05:16:30 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from 172.16.0.1 (localhost [127.0.0.1]) with ESMTP id DF20A29544F for ; Tue, 30 Nov 2004 00:16:24 -0500 (EST) Received: from 172.16.0.200 (SquirrelMail authenticated user mikej); by 172.16.0.1 with HTTP; Tue, 30 Nov 2004 00:16:24 -0500 (EST) Message-ID: <4162.172.16.0.200.1101791784.squirrel@172.16.0.200> Date: Tue, 30 Nov 2004 00:16:24 -0500 (EST) From: "Mike Jakubik" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com Subject: ACPI errors on GigaByte GA-K8VM800M X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 05:16:31 -0000 Hi, I am getting the following errors on the GigaByte GA-K8VM800M Motherboard. The system seems to run fine however. Latest BIOS installed. --- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 2800+ (1799.95-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 Features=0x78bfbff AMD Features=0xe0500800 real memory = 469696512 (447 MB) avail memory = 442269696 (421 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.MEM_._CRS] (Node 0xffffff00009b0cc0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.MEM_._CRS] (Node 0xffffff00009b0cc0), AE_AML_ALIGNMENT can't fetch resources for \\_SB_.MEM_ - AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT can't fetch resources for \\_SB_.PCI0 - AE_AML_ALIGNMENT Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: on acpi0 pci0: on pcib0 ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0502: *** Error: Handler for [SystemMemory] returned AE_AML_ALIGNMENT ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT ACPI-0239: *** Error: Method execution failed [\\_SB_.PCI0._CRS] (Node 0xffffff00009b09c0), AE_AML_ALIGNMENT pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) atapci0: port 0xe400-0xe4ff,0xe000-0xe00f,0xdc00-0xdc03,0xd800-0xd807,0xd400-0xd403,0xd000-0xd007 irq 20 at device 15.0 on pci0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: port 0xe800-0xe80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 isab0: at device 17.0 on pci0 isa0: on isab0 rl0: port 0xec00-0xecff mem 0xea000000-0xea0000ff irq 18 at device 19.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0f:ea:31:2d:71 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1799954748 Hz quality 800 Timecounters tick every 0.976 msec ad4: 190782MB [387621/16/63] at ata2-master SATA150 ad6: 190782MB [387621/16/63] at ata3-master SATA150 Mounting root from ufs:/dev/ad4s1a Thanks. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 05:56:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B28016A4CE; Tue, 30 Nov 2004 05:56:13 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C99D43D1F; Tue, 30 Nov 2004 05:56:13 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAU5uBr9074047; Mon, 29 Nov 2004 23:56:11 -0600 (CST) (envelope-from dan) Date: Mon, 29 Nov 2004 23:56:11 -0600 From: Dan Nelson To: David Gilbert Message-ID: <20041130055611.GN5518@dan.emsphone.com> References: <16811.51043.987275.174410@canoe.dclg.ca> <003801c4d685$81192640$1200a8c0@gsicomp.on.ca> <16811.58127.759026.560570@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16811.58127.759026.560570@canoe.dclg.ca> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org cc: Matt Emmerton Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 05:56:13 -0000 In the last episode (Nov 29), David Gilbert said: > Well... cam_calc_geometry seems to get called quite a bit. Almost > everytime you touch the disk, in fact. fsck'ing a partition calls > it, for instance. > > Console access is personally expensive (much driving, for instance), > but from memory the debugging I put in cam_calc_geometry() would > print before the correct output from dadone(). Your description > reminds me of this --- but it's no less vexing that the output from > dadone() has the correct sector and volume size and the ccg in > cam_calc_geometry() has bogus data. > > I don't know if it's significant, but the correct numbers were: > > 279353684 sectors of 512 bytes > > The ccg structure comes up with: > > 3737169375 sectors of 3737169374 bytes > > Not entirely sensible. Interesting that they're close values. > However, with different things on the stack, the values changed. Even more interesting is their hex values: DEC0ADDF and DEC0ADDE, aka 0xDEADC0DE. Something's reading memory after the kernel freed it. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 07:30:29 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DCC216A4D8 for ; Tue, 30 Nov 2004 07:30:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E47F43D1D for ; Tue, 30 Nov 2004 07:30:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iAU7UQqJ013895 for ; Tue, 30 Nov 2004 07:30:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iAU7UPFC013891; Tue, 30 Nov 2004 07:30:25 GMT (envelope-from gnats) Date: Tue, 30 Nov 2004 07:30:25 GMT Message-Id: <200411300730.iAU7UPFC013891@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Pascal Hofstee Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pascal Hofstee List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 07:30:29 -0000 The following reply was made to PR amd64/71674; it has been noted by GNATS. From: Pascal Hofstee To: freebsd-gnats-submit@FreeBSD.org, pete@twisted.org.uk Cc: Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries Date: Mon, 29 Nov 2004 21:37:40 -0800 As i am occasionally toying around with GNUstep as well ... and noticed that originally the FreeBSD ports-version of GNUstep essentially required an actual libobjc.so (and hence required to build a gcc-3.3.5 iirc and get its libobjc.so from there) .... i have since noticed that it is indeed possible to build GNUstep on FreeBSD/i386 using just our static libobjc.a I am wondering though if there is any specific reason for Not reverting this "bogus" disabling of libobjc.so for i386 as well ? i recall reading somewhere that certain elements of the Objective-C runtime would require a dynamic libobjc ... though i don't recall where i read this at the moment ... and it seems not to really impact GNUstep's functioning. But if there is no real reason (besides apprently so called performance impact .. which i hope may have been improved on since 1998) ... i would definately appreciate this change reverted on i386 as well ... (if only for consistency's sake concerning the libraries provided by the base system between different FreeBSD architectures) With kind regards, Pascal Hofstee From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 10:48:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6866516A4CE for ; Tue, 30 Nov 2004 10:48:28 +0000 (GMT) Received: from peedub.jennejohn.org (J9f75.j.pppool.de [85.74.159.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E7043D41 for ; Tue, 30 Nov 2004 10:48:27 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id iAUAmPSJ034940; Tue, 30 Nov 2004 11:48:25 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200411301048.iAUAmPSJ034940@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: James Earl In-reply-to: Your message of "Tue, 30 Nov 2004 17:20:41 MST." <1101860441.603.10.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Nov 2004 11:48:25 +0100 From: Gary Jennejohn cc: freebsd-amd64@freebsd.org Subject: Re: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Jennejohn List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 10:48:28 -0000 James Earl writes: > DRI isn't extremely important to me. Getting a working mga_hal_drv.o is > much more important however... otherwise I can't use the DVI output on > the graphics card. I realize now, that's not really a FreeBSD amd64 > problem though. > Yes, that's a problem. I was forced to give up my G550 because MATROX didn't have any 64-bit drivers at that time. The situation may have changed since then, it was several months ago. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 13:04:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55EF516A4CE; Tue, 30 Nov 2004 13:04:31 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17D743D1D; Tue, 30 Nov 2004 13:04:30 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAUD81ai006963; Tue, 30 Nov 2004 06:08:01 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AC6FF8.40501@freebsd.org> Date: Tue, 30 Nov 2004 06:04:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> In-Reply-To: <20041129233211.GA27426@troutmask.apl.washington.edu> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 13:04:31 -0000 Steve Kargl wrote: > On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > >>kmem_suballoc: bad status return of 3 >>panic: kmem_suballoc >>cpuid = 0 >>KDB: stack backtrace: >>kdb_backtrace() at kdb_backtrace+0x37 >>panic() at painc+0x1d1 >>kmem_suballoc() at kmem_suballoc+0x93 >>kmeminit() at kmeminit+0x16d >>mi_startuup() at mi_startup+0xb6 >>btext90 at btext+0x2c >>KDB: enter: panic >>[thread pid 0 tid 0] >> >>This is a Tyan K8S Pro motherboard with 16 GB of PC2700 >>Cosair ECC memory. The BIOS was flashed to the latest >>available from Tyan. The scheduler is 4BSD. There are >>no ATA devices in the system and no ATA subsystem in >>the kernel. This a SCSI only box. World and kernel >>were rebuilt today with CFLAGS=-O -pipe and >>COPTFLAGS=-O -pipe. >> >>If I set hw.physmem="#G" n /boot/loader.conf where # is >>less than or equal to 8 the box boots up (see dmesg below). >>If # > 8, then we have the above panic. >> >>Any ideas where to look for the a fix? >> > > > (dmesg snipped) > (CC'd to -current because the may impact any system with >8 GB of ram) > > As a data point, I've downloaded, burned, and booted the netbsd/amd64 > ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB > of memory on the system. > I fixed this on i386 a few months ago, and I applied a similar fix to amd64 on the advice of Peter Wemm. Go beat him up on this one =-) Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 13:08:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4946816A4CE for ; Tue, 30 Nov 2004 13:08:01 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB4A43D58 for ; Tue, 30 Nov 2004 13:08:00 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAUDBU2P006978; Tue, 30 Nov 2004 06:11:31 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AC70CA.4090805@freebsd.org> Date: Tue, 30 Nov 2004 06:08:26 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "James R. Van Artsalen" X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 13:08:01 -0000 > I'm not convinced that the bounce-buffer scheme works on amd64 at all. > I don't think twe, ata or bge work (individually or in combination) > with more than 4GB of RAM. Bounce buffers with >4GB were indeed broken in 5.3-RELEASE. I fixed them about a week ago in 5-STABLE and 6-CURRENT. You can work around the breakage in 5.3-R by setting the following in /boot/loader.conf: vm.old_contigmalloc=1 Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 13:14:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1226316A4CE for ; Tue, 30 Nov 2004 13:14:15 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABF8643D58 for ; Tue, 30 Nov 2004 13:14:14 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAUDHiKp006999; Tue, 30 Nov 2004 06:17:44 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AC723F.8000607@freebsd.org> Date: Tue, 30 Nov 2004 06:14:39 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Vinod Kashyap" X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "James R. Van Artsalen" cc: freebsd-amd64@freebsd.org Subject: RE: FreeBSD 5.3 installation problems on EM64T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 13:14:15 -0000 > > How much memory do you have? Are those ATAPI CD drives? > > > I had 6 GB all along, and was just trying 2 GB. Well, the > installation went through!! I am surprised that the error > resulting out of more memory in the system looks as bizarre as: > "The disc in your drive looks more like an Audio disc than a > FreeBSD release." Thanks for the help! ACPI still doesn't work > though. > > And yes, both are ATAPI/IDE CDROM drives. FreeBSD 5.3-R has bounce buffer problems on both amd64 and i386 with >4GB of RAM. This will definitely cause strange data corruption on ATA. I fixed 5-STABLE and 6-CURRENT last week, so you should update. ACPI works ok on my EM64T system (a pre-release Intel 7520BD2 board). Not sure what to say except to see if there are BIOS updates for your board. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 18:35:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59D8016A4CE; Tue, 30 Nov 2004 18:35:56 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D0EE43D3F; Tue, 30 Nov 2004 18:35:56 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAUIZtvr032286; Tue, 30 Nov 2004 10:35:55 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAUIZteg032285; Tue, 30 Nov 2004 10:35:55 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 10:35:55 -0800 From: Steve Kargl To: Scott Long Message-ID: <20041130183555.GA32237@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AC6FF8.40501@freebsd.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 18:35:56 -0000 On Tue, Nov 30, 2004 at 06:04:56AM -0700, Scott Long wrote: > Steve Kargl wrote: > >On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > > > >>kmem_suballoc: bad status return of 3 > >>panic: kmem_suballoc > >>cpuid = 0 > >>KDB: stack backtrace: > >>kdb_backtrace() at kdb_backtrace+0x37 > >>panic() at painc+0x1d1 > >>kmem_suballoc() at kmem_suballoc+0x93 > >>kmeminit() at kmeminit+0x16d > >>mi_startuup() at mi_startup+0xb6 > >>btext90 at btext+0x2c > >>KDB: enter: panic > >>[thread pid 0 tid 0] > >> > >>This is a Tyan K8S Pro motherboard with 16 GB of PC2700 > >>Cosair ECC memory. The BIOS was flashed to the latest > >>available from Tyan. The scheduler is 4BSD. There are > >>no ATA devices in the system and no ATA subsystem in > >>the kernel. This a SCSI only box. World and kernel > >>were rebuilt today with CFLAGS=-O -pipe and > >>COPTFLAGS=-O -pipe. > >> > >>If I set hw.physmem="#G" n /boot/loader.conf where # is > >>less than or equal to 8 the box boots up (see dmesg below). > >>If # > 8, then we have the above panic. > >> > >>Any ideas where to look for the a fix? > >> > > > >(dmesg snipped) > >(CC'd to -current because the may impact any system with >8 GB of ram) > > > >As a data point, I've downloaded, burned, and booted the netbsd/amd64 > >ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB > >of memory on the system. > > > > I fixed this on i386 a few months ago, and I applied a similar fix to > amd64 on the advice of Peter Wemm. Go beat him up on this one =-) > Well, I have more data and Peter advice may have been correct. >From the beastie menu :-O, I dropped to the loader prompt. If I do set hint.acpi.0.disabled="1" set hw.phymem="6G" The system boots up fine (although I thought AMD64 required acpi). Next, if I do set hint.acpi.0.disabled="1" set hw.phymem="16G" The system starts to boot and dmesg reports the 16 GB of memory, but I rapidly get this panic. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffffffff80af6a80 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802a5814 stack pointer = 0x10:0xffffffff80728a30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0] Stopped at isitmychild+0x4: decl %eax db> trace isitmychild() at isitmychild+0x4 isitmydescendant() at isitmydescendant+0x16 witness_checkorder() at witness_checkorder+0x44a _mtx_lock_flags() at _mtx_lock_flags+0x7a lim_hold() at lim_hold+0x29 fork1() at fork1+0xaa0 kthread_create() at kthread_create+0xa3 ktrace_init() at ktrace_init+0xe4 mi_startup() at mi_startup+0xb6 So, it looks like ACPI on this Tyan motherboard is restricting the memory to 8G. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 19:36:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 551C216A4CE; Tue, 30 Nov 2004 19:36:27 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE4A743D72; Tue, 30 Nov 2004 19:36:26 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUJaP0n083806; Tue, 30 Nov 2004 14:36:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUJaOKF066314; Tue, 30 Nov 2004 14:36:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 230797306E; Tue, 30 Nov 2004 14:36:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130193625.230797306E@freebsd-current.sentex.ca> Date: Tue, 30 Nov 2004 14:36:25 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:36:27 -0000 TB --- 2004-11-30 18:14:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 18:14:59 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-30 18:14:59 - checking out the source tree TB --- 2004-11-30 18:14:59 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-30 18:14:59 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 18:21:40 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 18:21:40 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-30 18:21:40 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 19:28:37 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 19:28:37 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-30 19:28:37 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 19:28:37 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/sys_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/trap.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/tsc.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/uio_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/uma_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/vm_machdep.c /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/amd64/vm_machdep.c: In function `cpu_reset': /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/amd64/vm_machdep.c:339: warning: unused variable `cnt' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-30 19:36:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 19:36:24 - ERROR: failed to build generic kernel TB --- 2004-11-30 19:36:24 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 19:39:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1330716A4CE; Tue, 30 Nov 2004 19:39:41 +0000 (GMT) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4874843D76; Tue, 30 Nov 2004 19:39:40 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) iAUJdWKu062087; Tue, 30 Nov 2004 20:39:37 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iAUJdWt2014426; Tue, 30 Nov 2004 20:39:32 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iAUJdWmQ014425; Tue, 30 Nov 2004 20:39:32 +0100 (CET) (envelope-from wb) Date: Tue, 30 Nov 2004 20:39:32 +0100 From: Wilko Bulte To: freebsd-list@dclg.ca Message-ID: <20041130193932.GI14039@freebie.xs4all.nl> References: <16811.51043.987275.174410@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="mYYhpFXgKVw71fwr" Content-Disposition: inline In-Reply-To: <16811.51043.987275.174410@canoe.dclg.ca> X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-hackers@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:39:41 -0000 --mYYhpFXgKVw71fwr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca wrote.. > After a bunch of frustrating debugging, I've tenatively come to the > conclusion that the isp(4) driver is not 64 bit safe --- at the very > least insofar as the amd64 platform is concerned. Side note: isp(4) has been in use for years on Alpha, and I do not recall having seen problems like yours on it. Mind you, not much FC connections I ever used on it. The only thing critical for success on Alpha is loading ispfw.ko *always*. Matt (mjacob) has noted that multiple times, and he is absolutely right. Wilko --=20 Wilko Bulte wilko@FreeBSD.org --mYYhpFXgKVw71fwr Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIOfwYJKoZIhvcNAQcCoIIOcDCCDmwCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC C+swggSmMIICjqADAgECAgMAxq4wDQYJKoZIhvcNAQEEBQAweTEQMA4GA1UEChMHUm9vdCBD QTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNp Z25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwHhcN MDQxMTA2MjI0MzE2WhcNMDUxMTA2MjI0MzE2WjAlMSMwIQYJKoZIhvcNAQkBFhR3YkBmcmVl YmllLnhzNGFsbC5ubDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANtHavP0Bn9g xcTO+rGscZxb/+LZcFdERZcV6d358KOHsrysbvvpElwbTgSL4QpviV9a5ju+3dze7YRi0iB7 3JzWbl1G29Q45nydX58eWX++w+RAFlHI0kAwTY612bIqhP+MmRon7W70lw45gQfUzGz/DqdR M/FRNNYhOVYp2wbp6f2ytEaierTv8p201+mLB4SjVJ1vQtu3oVfYZVZeJDoxYn49SrjVejuA yq/lDEO9ykNTp4l7rGJcK+FRAdag5Oi7Tev6cq5DzJiON74W9MR5aqvOLtYo/bh3zKXf5ygy sN8+hJnkAwlaAJ38SnsxKfpy3aFLUuZEn+Ul3oUcarkCAwEAAaOBijCBhzAMBgNVHRMBAf8E AjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAfBgNVHREEGDAWgRR3YkBm cmVlYmllLnhzNGFsbC5ubDANBgkqhkiG9w0BAQQFAAOCAgEAlKQNnSd8Jdt58NFTEaY202Qb XEdESmsRBaydVid6K956unv0rtp3GhkegEJEjhSKoN0K0rIIoYeHgiArmZu2wtMoNvKJG7kN bXQ+R8uWJ5CLMbQ8HbEommF2ptrkR72GrXwOnDyjInEB/1lTtLjoBGmk7A+sTpvaB/gUpvRZ ydr7h8XhNwTcYdBEUXBeKkR7N+FzzSHfmYH288i65fmKQX91F/ewoaB627sDLKH/Vt/M8Z/I NcqyPlmGuFSKlR184PKWY78VaA8RtHSsQrr97eSRIa6MOWlvYQyq8fUfcPUfxl45qLlH8s2n FP0O7ZMAHhbypjnRWNg/r+HGsUqUh6EKFRdp70MmSSWYnM3ZzxGBIb9UV1n4+nPUCUx9r1fa DIAc/1LEvcjLSlW6vHus48VAOJelNGfMsdr8VlVafJE0F0nIXRiUdoe5sO45RKCSefqgRSW/ 7nLb7mvBg8u9q5+7VLuCsXEkpgc65dIIUD+2FTXpA2Zb0LSeey5zKC+RYdCYYvLAl9sQwx5E 6FMCkHOMDu5MEJLI0oyjrHjDbt/aE+fUQlJrFmfIUUX4CeQCdvFqrHDRjOT7JVSQB6EqA8VZ zBFLYUlTKdunvFcwR+2gJyHOTqLbM8b+Qb972jaBE6bGPWbK6t9PSdUsf2g1B9CpDSMiuWe7 Ek/XJFe6NY0wggc9MIIFJaADAgECAgEAMA0GCSqGSIb3DQEBBAUAMHkxEDAOBgNVBAoTB1Jv b3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2Vy dCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn MB4XDTAzMDMzMDEyMjk0OVoXDTMzMDMyOTEyMjk0OVoweTEQMA4GA1UEChMHUm9vdCBDQTEe MBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25p bmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwggIiMA0G CSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDOIsDiRn3sNigHUJbyoDNAjEvxO2Y/MeVrAjbb 1nz28YiPTnc2BUGV+QnwEs9GhnNgt25+6MBYZK7NsK1FFwxj+mcK6NbSvz7nmMTwTPrgA7s1 XWwh3p4g2brNZjI3cvr3CPXHzVjJjucOXuo+/hyhFAoVbIaEW2RmKnqpS1N59Yiie+4vCmEr jbJ+TValE+zq2pKerERBHlhgZQVm+MBEvcuU90J+C/dlaJhRBfDzBZEEHRsXguzIV7vDa3qI 8bByzCVbIJHsFgISjzLpFxhI0McFLgIwQrglnAVrP6o6p+tTSPfo0rYHmNwbxjR/f8kcgnoF WCsIW/M4oqsXXWbJmNeeEIui0t10mvdxDHJg381vmDOdljR2PiR6krAOlR5v5qBFOEeq10Ht SrcS9tcbg4oPLtgJtlnXqgT/0pN9aC7di0urWLovjeqVp6DDVIml+9uLUSKdssO+Eb4skYaL lnitINOKLxo/xtBRZYchsRkBZX9FHIf1fNBBTE8pmCH9Mx91DARR+hl329QUHO6Bwx31mLdp BpEi3QBQzIExrBIHezjaaFvmK9R+yV+t6OtyTPMB5Usgv5qmV8qRAAGLoXUhN7VjDWc+Rk9w IGfOxdZZ2wLg8NLLzbpit5BB6N0g5Cm8ZClCyCLceJr/Q+yYGwlRS1pawnHxxMtzqeWhCwID AQABo4IBzjCCAcowHQYDVR0OBBYEFBa1MhvUx/Pg5o7zvdKwOu6yORjRMIGjBgNVHSMEgZsw gZiAFBa1MhvUx/Pg5o7zvdKwOu6yORjRoX2kezB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZ4IBADAPBgNVHRMB Af8EBTADAQH/MDIGA1UdHwQrMCkwJ6AloCOGIWh0dHBzOi8vd3d3LmNhY2VydC5vcmcvcmV2 b2tlLmNybDAwBglghkgBhvhCAQQEIxYhaHR0cHM6Ly93d3cuY2FjZXJ0Lm9yZy9yZXZva2Uu Y3JsMDQGCWCGSAGG+EIBCAQnFiVodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lk PTEwMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzANBgkqhkiG9w0BAQQFAAOC AgEAKMfunIICulyAEso1Ch2Bb4lqmczyaA9/p+GNWJU+vfIGw5BarLVg9plDAaOIcJydYp2k h69nWA0wNjvmrUjTy3QChnE+4isDaPE0YkBGO1PqKPSs+2aVU4pNXf072WDXynlpO7FlkqbG gYJcnM3rTQGKpd8RVaoVyh83wIKYcGHbanyWo44uVD5PIamQ79yCv9zoRa1NkHMIPJRlsASZ dn/ivMJqFaqXBDck2B6UTm0OUb7WxI/Klm33Q9/oMGUnO3u7Q0NjxEP3suxozOEZjiL7mOF7 Wj4BNzuLCLCi85VOGsubzZqx27Jw8C1K29iw429FSDMS//48MipU98T3ivCII8JH/mR6ccDR HqZjsAd+pC/TAY/cnyu2xgipD5NIJfwS/Z9C3PPEPvZXsNfdadEGdzQKS9LKoP8cxozJFr7E zDI3aHNfCPtR90lTNgUKlQJM8nkaEPbYOnWc8x3xog1wZ4Ybsxb1L+Wk63mG+T0LwnMLpZms b/xnuOUvC6YYJI170Ug1KRhArJNg4ZaGULR6WdiPIQufz4KRxju/a9wHkbmXViOqtmyUxkgG POTOTqrk9i8J3FNvLvx06zpjmcKmrIm8p7JEoA2KEONs8iTL+pufcEcu3hSL1LIgCZaiZPEk HNyhNZwVstS8VS59BvWcDlX0WtaT2natJXNMxUMxggJcMIICWAIBATCBgDB5MRAwDgYDVQQK EwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNB IENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0 Lm9yZwIDAMauMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDQxMTMwMTkzOTMxWjAjBgkqhkiG9w0BCQQxFgQUEMTCVQNJB4ItBId9 DgMn7nK/F7wwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAE ggEAxqcDAxXx40JT2U/z9regNoDHahporxY4wUxmFZxdgYeUVOJEUYAzeYbA+/I8jYTgZsIC mLrggR8VPM75IYE18HApkwdOpN41azFr3zXZo2Ge2dBKT9uwyP/GpbhrWye1NzII+TRbZ6rd 4k7TPgCXS4/JUKz/jMcjpeFJm8pgptDgvgeFup5pWmvM46aQZjaarGwCadDp+aKoRWIOKTxX OYuWfjo082iTAA3hX1hkj3N2Oz5qrOfyqdqG5fYErRv0tLKnMWLTRqaYJUKv7frh1rxSNcQS h8O022x3BjN+fUYoI+WD8AYSsQGmGvZkHg6oWnC8HHgL2+7pzyY2wNUjdQ== --mYYhpFXgKVw71fwr-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 19:42:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C9CA16A4CE; Tue, 30 Nov 2004 19:42:29 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id E19A443D5A; Tue, 30 Nov 2004 19:42:28 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAUJgR46032675; Tue, 30 Nov 2004 11:42:27 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAUJgRZs032674; Tue, 30 Nov 2004 11:42:27 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 11:42:27 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041130194227.GA32604@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130142652.A59122@bahre.achedra.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:42:29 -0000 On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Tue, 30 Nov 2004, Steve Kargl wrote: > > > >The system starts to boot and dmesg reports the 16 GB of memory, but > >I rapidly get this panic. > > >So, it looks like ACPI on this Tyan motherboard is restricting > >the memory to 8G. > > I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB > ECC Reg'd.) Yes. > More importantly, which BIOS version? You have to run the 2.03 BIOS on > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > in the BIOS as well - this was a never-ending source of fun on both the > S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on > with the S4882 and S288x's is a never-ending font of panic()s. But the > 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. > At least it's not an S4882 1.02: > "DDR 400MHz Memmory Detected" > The BIOS is at 2.03. I haven't tried turning off the ccNUMA support. I'll give it a shot in a moment. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 20:22:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 915D816A4CE; Tue, 30 Nov 2004 20:22:31 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7273C43D3F; Tue, 30 Nov 2004 20:22:31 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 486E12A8E0; Tue, 30 Nov 2004 12:22:31 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 00B33E2B3; Tue, 30 Nov 2004 12:22:30 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iAUKMT3M016587; Tue, 30 Nov 2004 12:22:29 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAUKMO0k016584; Tue, 30 Nov 2004 12:22:24 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 30 Nov 2004 12:22:23 -0800 User-Agent: KMail/1.7.1 References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> In-Reply-To: <20041130193932.GI14039@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411301222.24062.peter@wemm.org> cc: Wilko Bulte cc: freebsd-list@dclg.ca cc: freebsd-hackers@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:22:31 -0000 On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote: > On Mon, Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca > wrote.. > > > After a bunch of frustrating debugging, I've tenatively come to the > > conclusion that the isp(4) driver is not 64 bit safe --- at the > > very least insofar as the amd64 platform is concerned. > > Side note: isp(4) has been in use for years on Alpha, and I do not > recall having seen problems like yours on it. Mind you, not much FC > connections I ever used on it. The only thing critical for success > on Alpha is loading ispfw.ko *always*. Matt (mjacob) has noted that > multiple times, and he is absolutely right. > > Wilko I haven't seen an alpha with more than 2G of ram that we booted on. Is it possible that isp has never been tested with >4G ram? Secondly.. what release is this on? I'm wondering if the horrific busdma bugs in 5.3-RELEASE might be a problem if the machine does have >4G ram. Third, is this a machine ram size problem or a disk volume size problem? The original post was about a 131G FC volume and calculating the wrong number of sectors and the wrong sector size... -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 20:26:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11EAE16A4CE; Tue, 30 Nov 2004 20:26:43 +0000 (GMT) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32D4643D46; Tue, 30 Nov 2004 20:26:42 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr4.xs4all.nl (8.12.11/8.12.11) with ESMTP id iAUKQYHr074601; Tue, 30 Nov 2004 21:26:34 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iAUKQXFs015202; Tue, 30 Nov 2004 21:26:33 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iAUKQXxr015201; Tue, 30 Nov 2004 21:26:33 +0100 (CET) (envelope-from wb) Date: Tue, 30 Nov 2004 21:26:33 +0100 From: Wilko Bulte To: Peter Wemm Message-ID: <20041130202633.GA15157@freebie.xs4all.nl> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> <200411301222.24062.peter@wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <200411301222.24062.peter@wemm.org> X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:26:43 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 30, 2004 at 12:22:23PM -0800, Peter Wemm wrote.. > On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote: > > On Mon, Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca > > wrote.. > > > > > After a bunch of frustrating debugging, I've tenatively come to the > > > conclusion that the isp(4) driver is not 64 bit safe --- at the > > > very least insofar as the amd64 platform is concerned. > > > > Side note: isp(4) has been in use for years on Alpha, and I do not > > recall having seen problems like yours on it. Mind you, not much FC > > connections I ever used on it. The only thing critical for success > > on Alpha is loading ispfw.ko *always*. Matt (mjacob) has noted that > > multiple times, and he is absolutely right. > > > > Wilko >=20 > I haven't seen an alpha with more than 2G of ram that we booted on. Is= =20 > it possible that isp has never been tested with >4G ram? Quite possible as far as Alpha is concerned. You are correct about the 2G, on a lot of Alpha models it is less than that (IIRC..) > Third, is this a machine ram size problem or a disk volume size problem? = =20 > The original post was about a 131G FC volume and calculating the wrong=20 > number of sectors and the wrong sector size... Given time (....) I could test up to 2TB volumes using FC / isp(4) at work. But not on amd64 as we do not currently have such a machine :) W/ --=20 Wilko Bulte wilko@FreeBSD.org --DocE+STaALJfprDB Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIOfwYJKoZIhvcNAQcCoIIOcDCCDmwCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC C+swggSmMIICjqADAgECAgMAxq4wDQYJKoZIhvcNAQEEBQAweTEQMA4GA1UEChMHUm9vdCBD QTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNp Z25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwHhcN MDQxMTA2MjI0MzE2WhcNMDUxMTA2MjI0MzE2WjAlMSMwIQYJKoZIhvcNAQkBFhR3YkBmcmVl YmllLnhzNGFsbC5ubDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANtHavP0Bn9g xcTO+rGscZxb/+LZcFdERZcV6d358KOHsrysbvvpElwbTgSL4QpviV9a5ju+3dze7YRi0iB7 3JzWbl1G29Q45nydX58eWX++w+RAFlHI0kAwTY612bIqhP+MmRon7W70lw45gQfUzGz/DqdR M/FRNNYhOVYp2wbp6f2ytEaierTv8p201+mLB4SjVJ1vQtu3oVfYZVZeJDoxYn49SrjVejuA yq/lDEO9ykNTp4l7rGJcK+FRAdag5Oi7Tev6cq5DzJiON74W9MR5aqvOLtYo/bh3zKXf5ygy sN8+hJnkAwlaAJ38SnsxKfpy3aFLUuZEn+Ul3oUcarkCAwEAAaOBijCBhzAMBgNVHRMBAf8E AjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAfBgNVHREEGDAWgRR3YkBm cmVlYmllLnhzNGFsbC5ubDANBgkqhkiG9w0BAQQFAAOCAgEAlKQNnSd8Jdt58NFTEaY202Qb XEdESmsRBaydVid6K956unv0rtp3GhkegEJEjhSKoN0K0rIIoYeHgiArmZu2wtMoNvKJG7kN bXQ+R8uWJ5CLMbQ8HbEommF2ptrkR72GrXwOnDyjInEB/1lTtLjoBGmk7A+sTpvaB/gUpvRZ ydr7h8XhNwTcYdBEUXBeKkR7N+FzzSHfmYH288i65fmKQX91F/ewoaB627sDLKH/Vt/M8Z/I NcqyPlmGuFSKlR184PKWY78VaA8RtHSsQrr97eSRIa6MOWlvYQyq8fUfcPUfxl45qLlH8s2n FP0O7ZMAHhbypjnRWNg/r+HGsUqUh6EKFRdp70MmSSWYnM3ZzxGBIb9UV1n4+nPUCUx9r1fa DIAc/1LEvcjLSlW6vHus48VAOJelNGfMsdr8VlVafJE0F0nIXRiUdoe5sO45RKCSefqgRSW/ 7nLb7mvBg8u9q5+7VLuCsXEkpgc65dIIUD+2FTXpA2Zb0LSeey5zKC+RYdCYYvLAl9sQwx5E 6FMCkHOMDu5MEJLI0oyjrHjDbt/aE+fUQlJrFmfIUUX4CeQCdvFqrHDRjOT7JVSQB6EqA8VZ zBFLYUlTKdunvFcwR+2gJyHOTqLbM8b+Qb972jaBE6bGPWbK6t9PSdUsf2g1B9CpDSMiuWe7 Ek/XJFe6NY0wggc9MIIFJaADAgECAgEAMA0GCSqGSIb3DQEBBAUAMHkxEDAOBgNVBAoTB1Jv b3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2Vy dCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn MB4XDTAzMDMzMDEyMjk0OVoXDTMzMDMyOTEyMjk0OVoweTEQMA4GA1UEChMHUm9vdCBDQTEe MBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25p bmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwggIiMA0G CSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDOIsDiRn3sNigHUJbyoDNAjEvxO2Y/MeVrAjbb 1nz28YiPTnc2BUGV+QnwEs9GhnNgt25+6MBYZK7NsK1FFwxj+mcK6NbSvz7nmMTwTPrgA7s1 XWwh3p4g2brNZjI3cvr3CPXHzVjJjucOXuo+/hyhFAoVbIaEW2RmKnqpS1N59Yiie+4vCmEr jbJ+TValE+zq2pKerERBHlhgZQVm+MBEvcuU90J+C/dlaJhRBfDzBZEEHRsXguzIV7vDa3qI 8bByzCVbIJHsFgISjzLpFxhI0McFLgIwQrglnAVrP6o6p+tTSPfo0rYHmNwbxjR/f8kcgnoF WCsIW/M4oqsXXWbJmNeeEIui0t10mvdxDHJg381vmDOdljR2PiR6krAOlR5v5qBFOEeq10Ht SrcS9tcbg4oPLtgJtlnXqgT/0pN9aC7di0urWLovjeqVp6DDVIml+9uLUSKdssO+Eb4skYaL lnitINOKLxo/xtBRZYchsRkBZX9FHIf1fNBBTE8pmCH9Mx91DARR+hl329QUHO6Bwx31mLdp BpEi3QBQzIExrBIHezjaaFvmK9R+yV+t6OtyTPMB5Usgv5qmV8qRAAGLoXUhN7VjDWc+Rk9w IGfOxdZZ2wLg8NLLzbpit5BB6N0g5Cm8ZClCyCLceJr/Q+yYGwlRS1pawnHxxMtzqeWhCwID AQABo4IBzjCCAcowHQYDVR0OBBYEFBa1MhvUx/Pg5o7zvdKwOu6yORjRMIGjBgNVHSMEgZsw gZiAFBa1MhvUx/Pg5o7zvdKwOu6yORjRoX2kezB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZ4IBADAPBgNVHRMB Af8EBTADAQH/MDIGA1UdHwQrMCkwJ6AloCOGIWh0dHBzOi8vd3d3LmNhY2VydC5vcmcvcmV2 b2tlLmNybDAwBglghkgBhvhCAQQEIxYhaHR0cHM6Ly93d3cuY2FjZXJ0Lm9yZy9yZXZva2Uu Y3JsMDQGCWCGSAGG+EIBCAQnFiVodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lk PTEwMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzANBgkqhkiG9w0BAQQFAAOC AgEAKMfunIICulyAEso1Ch2Bb4lqmczyaA9/p+GNWJU+vfIGw5BarLVg9plDAaOIcJydYp2k h69nWA0wNjvmrUjTy3QChnE+4isDaPE0YkBGO1PqKPSs+2aVU4pNXf072WDXynlpO7FlkqbG gYJcnM3rTQGKpd8RVaoVyh83wIKYcGHbanyWo44uVD5PIamQ79yCv9zoRa1NkHMIPJRlsASZ dn/ivMJqFaqXBDck2B6UTm0OUb7WxI/Klm33Q9/oMGUnO3u7Q0NjxEP3suxozOEZjiL7mOF7 Wj4BNzuLCLCi85VOGsubzZqx27Jw8C1K29iw429FSDMS//48MipU98T3ivCII8JH/mR6ccDR HqZjsAd+pC/TAY/cnyu2xgipD5NIJfwS/Z9C3PPEPvZXsNfdadEGdzQKS9LKoP8cxozJFr7E zDI3aHNfCPtR90lTNgUKlQJM8nkaEPbYOnWc8x3xog1wZ4Ybsxb1L+Wk63mG+T0LwnMLpZms b/xnuOUvC6YYJI170Ug1KRhArJNg4ZaGULR6WdiPIQufz4KRxju/a9wHkbmXViOqtmyUxkgG POTOTqrk9i8J3FNvLvx06zpjmcKmrIm8p7JEoA2KEONs8iTL+pufcEcu3hSL1LIgCZaiZPEk HNyhNZwVstS8VS59BvWcDlX0WtaT2natJXNMxUMxggJcMIICWAIBATCBgDB5MRAwDgYDVQQK EwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNB IENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0 Lm9yZwIDAMauMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDQxMTMwMjAyNjMzWjAjBgkqhkiG9w0BCQQxFgQUg77f3RJZOfJrRq/E 1HeMFrhyUCMwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAE ggEASi+UOADTpW2C2KtttiIKvo9xoZTCN1pmpWldioPXQ+eiZ9JEnNk01KKziTBlClnNlxo0 Xay1SJvrFUfedrpMmcQuSWL6P4o0R6cxiGN9/Rfmg8zJwFds332iHDMHeqyEEb7Tfd9YCkds rths0FKKZpP3iuu9hQGO7kuXqgqSB5zkRx7SNH3JTT5g1RYmzuovby6kDkGokCQyNTBa0o6O OjeH3GuRbLp1YapqNh5Td4M5Nt8KgOPR/R0pVPaQXjtJNSHn/4EnxT3v8Wg9oczMDsjWg5Ps b0lUf7qWUffQ7VjqRL6OsIdjmKNbcYClbCCzNdYRmoWpAsOJAbcsB88MTw== --DocE+STaALJfprDB-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 20:43:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7C9916A4CE; Tue, 30 Nov 2004 20:43:02 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC9743D39; Tue, 30 Nov 2004 20:43:02 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 3F477CDA3; Tue, 30 Nov 2004 15:43:01 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 1FFB7681B; Tue, 30 Nov 2004 15:42:55 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16812.56143.60199.332283@canoe.dclg.ca> Date: Tue, 30 Nov 2004 15:42:55 -0500 To: Wilko Bulte In-Reply-To: <20041130202633.GA15157@freebie.xs4all.nl> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> <200411301222.24062.peter@wemm.org> <20041130202633.GA15157@freebie.xs4all.nl> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:43:03 -0000 >>>>> "Wilko" == Wilko Bulte writes: Wilko> On Tue, Nov 30, 2004 at 12:22:23PM -0800, Peter Wemm wrote.. >> On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote: > On Mon, >> Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca > wrote.. >> > >> > > After a bunch of frustrating debugging, I've tenatively come to >> the > > conclusion that the isp(4) driver is not 64 bit safe --- at >> the > > very least insofar as the amd64 platform is concerned. >> > >> > Side note: isp(4) has been in use for years on Alpha, and I do >> not > recall having seen problems like yours on it. Mind you, not >> much FC > connections I ever used on it. The only thing critical >> for success > on Alpha is loading ispfw.ko *always*. Matt (mjacob) >> has noted that > multiple times, and he is absolutely right. >> > >> > Wilko >> >> I haven't seen an alpha with more than 2G of ram that we booted on. >> Is it possible that isp has never been tested with >4G ram? Wilko> Quite possible as far as Alpha is concerned. You are correct Wilko> about the 2G, on a lot of Alpha models it is less than that Wilko> (IIRC..) >> Third, is this a machine ram size problem or a disk volume size >> problem? The original post was about a 131G FC volume and >> calculating the wrong number of sectors and the wrong sector >> size... Wilko> Given time (....) I could test up to 2TB volumes using FC / Wilko> isp(4) at work. But not on amd64 as we do not currently have Wilko> such a machine :) I just heard back from some people still onsite. The ISP driver booted with everything the same except hw.physmem=2g works. It's a memory issue. I didn't ever think it was a volume size issue as the volume was 131 gig ... and that's not big these days. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 20:46:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68E3616A4D0; Tue, 30 Nov 2004 20:46:04 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B24F43D54; Tue, 30 Nov 2004 20:46:04 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 99055CD9C; Tue, 30 Nov 2004 15:46:03 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id DA249681B; Tue, 30 Nov 2004 15:45:55 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16812.56323.806726.688109@canoe.dclg.ca> Date: Tue, 30 Nov 2004 15:45:55 -0500 To: Peter Wemm In-Reply-To: <200411301222.24062.peter@wemm.org> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> <200411301222.24062.peter@wemm.org> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: Wilko Bulte cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:46:04 -0000 >>>>> "Peter" == Peter Wemm writes: Peter> On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote: >> On Mon, Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca >> wrote.. >> >> > After a bunch of frustrating debugging, I've tenatively come to >> the > conclusion that the isp(4) driver is not 64 bit safe --- at >> the > very least insofar as the amd64 platform is concerned. >> >> Side note: isp(4) has been in use for years on Alpha, and I do not >> recall having seen problems like yours on it. Mind you, not much >> FC connections I ever used on it. The only thing critical for >> success on Alpha is loading ispfw.ko *always*. Matt (mjacob) has >> noted that multiple times, and he is absolutely right. >> >> Wilko Peter> I haven't seen an alpha with more than 2G of ram that we booted Peter> on. Is it possible that isp has never been tested with >4G Peter> ram? I had the machine tested with hw.physmem=2g and it works. Peter> Secondly.. what release is this on? I'm wondering if the Peter> horrific busdma bugs in 5.3-RELEASE might be a problem if the Peter> machine does have >> 4G ram. I updated to -STABLE as of yesterday morning and it changed the nature of the panic somewhat, but did not fix it. Peter> Third, is this a machine ram size problem or a disk volume size Peter> problem? The original post was about a 131G FC volume and Peter> calculating the wrong number of sectors and the wrong sector Peter> size... Someone pointed out to me that my integer was 0xDEADBEEF ... which somewhat squared with my use of 'options INVARIANTS' on the kernel. Note that the scsi_da.c size printf shows the correct size. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 20:47:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87B7216A4CE; Tue, 30 Nov 2004 20:47:15 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F99543D45; Tue, 30 Nov 2004 20:47:15 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id BBE14CE70; Tue, 30 Nov 2004 15:47:14 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id E298A681B; Tue, 30 Nov 2004 15:47:08 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16812.56396.857963.233756@canoe.dclg.ca> Date: Tue, 30 Nov 2004 15:47:08 -0500 To: Wilko Bulte In-Reply-To: <20041130193932.GI14039@freebie.xs4all.nl> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:47:15 -0000 >>>>> "Wilko" == Wilko Bulte writes: Wilko> On Mon, Nov 29, 2004 at 08:05:39PM -0500, freebsd-list@dclg.ca Wilko> wrote.. >> After a bunch of frustrating debugging, I've tenatively come to the >> conclusion that the isp(4) driver is not 64 bit safe --- at the >> very least insofar as the amd64 platform is concerned. Wilko> Side note: isp(4) has been in use for years on Alpha, and I do Wilko> not recall having seen problems like yours on it. Mind you, Wilko> not much FC connections I ever used on it. The only thing Wilko> critical for success on Alpha is loading ispfw.ko *always*. Wilko> Matt (mjacob) has noted that multiple times, and he is Wilko> absolutely right. I did have device ispfw in the kernel, but this card may be new enough not to require it --- ispfw didn't change the behaviour or spit out any boot messages. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 21:30:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C30EC16A4D8; Tue, 30 Nov 2004 21:30:09 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7408343D60; Tue, 30 Nov 2004 21:30:07 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAULU6Z4001134; Tue, 30 Nov 2004 13:30:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAULU6nP001133; Tue, 30 Nov 2004 13:30:06 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 13:30:06 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041130213006.GA1079@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041130194227.GA32604@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130194227.GA32604@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 21:30:10 -0000 On Tue, Nov 30, 2004 at 11:42:27AM -0800, Steve Kargl wrote: > On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > > > More importantly, which BIOS version? You have to run the 2.03 BIOS on > > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > > in the BIOS as well - this was a never-ending source of fun on both the > > S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on > > with the S4882 and S288x's is a never-ending font of panic()s. But the > > 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. > > At least it's not an S4882 1.02: > > "DDR 400MHz Memmory Detected" > > The BIOS is at 2.03. I haven't tried turning off the ccNUMA support. > I'll give it a shot in a moment. > I disabled the only thing in the BIOS that mentions NUMA (under Advanced ACPI Configuration). FreeBSD now sees the 16 GB, but she still panics. A verbose boot shows real memory = 17179869184 (16384 MB) Physical memory chuck(s): 0x0000000000001000 - 0000000000009bfff, 634880 bytes (155 pages) 0x000000000082d000 - 000000000fbfeffff, 4219219968 bytes (1030083 pages) 0x0000000100000000 - 000000003e1fcffff, 12381388800 bytes (3022800 pages) panic: vm_page_insert: page already inserted cpuid = 0 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x1d1 vm_page_insert() at vm_page_insert+0x4e vm_page_alloc() at vm_page_alloc+0x315 vm_page_grab() at vm_page_grab+0x141 kmem_alloc() at kmem_alloc+0x10c vm_ksubmap_init() at vm_ksubmap_init+0x7d cpu_startup() at cpu_startup+0xbc mi_statup() at mi_startup+0xb6 btext() at btext+0x2c -- Steve From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 22:54:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 149AF16A4CF; Tue, 30 Nov 2004 22:54:12 +0000 (GMT) Date: Tue, 30 Nov 2004 22:54:12 +0000 From: David O'Brien To: David Gilbert Message-ID: <20041130225412.GA26088@hub.freebsd.org> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> <200411301222.24062.peter@wemm.org> <20041130202633.GA15157@freebie.xs4all.nl> <16812.56143.60199.332283@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16812.56143.60199.332283@canoe.dclg.ca> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.10-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Wilko Bulte cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 22:54:12 -0000 On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote: > I just heard back from some people still onsite. The ISP driver > booted with everything the same except hw.physmem=2g works. It's a > memory issue. Try hw.physmem=4g. It should be the 4GB boundary, not 2GB boundary that is causing you trouble. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 30 23:57:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C42E16A4CE; Tue, 30 Nov 2004 23:57:54 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39DDB43D55; Tue, 30 Nov 2004 23:57:54 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by bahre.achedra.org (8.13.1/8.13.1) with ESMTP id iAUJZUl1087734; Tue, 30 Nov 2004 14:35:30 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Tue, 30 Nov 2004 14:35:30 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Steve Kargl In-Reply-To: <20041130183555.GA32237@troutmask.apl.washington.edu> Message-ID: <20041130142652.A59122@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 23:57:54 -0000 On Tue, 30 Nov 2004, Steve Kargl wrote: > The system starts to boot and dmesg reports the 16 GB of memory, but > I rapidly get this panic. > So, it looks like ACPI on this Tyan motherboard is restricting > the memory to 8G. I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB ECC Reg'd.) More importantly, which BIOS version? You have to run the 2.03 BIOS on the K8SPro if you're running 16GB. Make sure that ccNUMA support is off in the BIOS as well - this was a never-ending source of fun on both the S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on with the S4882 and S288x's is a never-ending font of panic()s. But the 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. At least it's not an S4882 1.02: "DDR 400MHz Memmory Detected" -Ketrien I. Saihr-Kenchedra From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 00:18:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B25916A4CE; Wed, 1 Dec 2004 00:18:41 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 229FF43D53; Wed, 1 Dec 2004 00:18:41 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 04F211977A; Tue, 30 Nov 2004 16:18:41 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org, obrien@freebsd.org Date: Tue, 30 Nov 2004 16:18:40 -0800 User-Agent: KMail/1.7.1 References: <16811.51043.987275.174410@canoe.dclg.ca> <16812.56143.60199.332283@canoe.dclg.ca> <20041130225412.GA26088@hub.freebsd.org> In-Reply-To: <20041130225412.GA26088@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411301618.40651.peter@wemm.org> cc: Wilko Bulte cc: freebsd-list@dclg.ca cc: freebsd-hackers@freebsd.org cc: David Gilbert Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 00:18:41 -0000 On Tuesday 30 November 2004 02:54 pm, David O'Brien wrote: > On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote: > > I just heard back from some people still onsite. The ISP driver > > booted with everything the same except hw.physmem=2g works. It's a > > memory issue. > > Try hw.physmem=4g. It should be the 4GB boundary, not 2GB boundary > that is causing you trouble. I wonder if the isp driver is using 32 bit signed addressing for its dma control blocks or something.. I have an ISP-something scsi controller that I could probably extract from an itanic box, but I've got to get more ram in my test machine.. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 02:29:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D042A16A4CF for ; Wed, 1 Dec 2004 02:29:08 +0000 (GMT) Received: from hotmail.com (bay13-f26.bay13.hotmail.com [64.4.31.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B03AD43D45 for ; Wed, 1 Dec 2004 02:29:08 +0000 (GMT) (envelope-from martarese@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 30 Nov 2004 18:29:08 -0800 Message-ID: Received: from 213.22.141.12 by by13fd.bay13.hotmail.msn.com with HTTP; Wed, 01 Dec 2004 02:28:39 GMT X-Originating-IP: [213.22.141.12] X-Originating-Email: [martarese@hotmail.com] X-Sender: martarese@hotmail.com From: "Marta Resende" To: freebsd-amd64@freebsd.org Date: Wed, 01 Dec 2004 02:28:39 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 01 Dec 2004 02:29:08.0173 (UTC) FILETIME=[88DB17D0:01C4D74D] Subject: Dimm difference ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 02:29:08 -0000 Hey, i adquire 2 dimm blocks, to put it runnind in amd64, the 2 are 512MB DDR PC3200 CL3 (samsung), although, one is 30331-B2 and another is 30331-Z, they are a little bit thifference (dont know where), so they wont wwork as dual channel right ?? thks _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 02:40:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0493616A4CE for ; Wed, 1 Dec 2004 02:40:16 +0000 (GMT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C45E43D46 for ; Wed, 1 Dec 2004 02:40:15 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-177-227.abhsia.telus.net ([137.186.177.227]) by priv-edtnes28.telusplanet.netESMTP <20041201024014.XMAZ24672.priv-edtnes28.telusplanet.net@d137-186-177-227.abhsia.telus.net>; Tue, 30 Nov 2004 19:40:14 -0700 From: James Earl To: Gary Jennejohn In-Reply-To: <200411301048.iAUAmPSJ034940@peedub.jennejohn.org> References: <200411301048.iAUAmPSJ034940@peedub.jennejohn.org> Content-Type: text/plain Date: Wed, 01 Dec 2004 19:40:48 -0700 Message-Id: <1101955248.622.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Matrox G550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 02:40:16 -0000 On Tue, 2004-11-30 at 11:48 +0100, Gary Jennejohn wrote: > James Earl writes: > > DRI isn't extremely important to me. Getting a working mga_hal_drv.o is > > much more important however... otherwise I can't use the DVI output on > > the graphics card. I realize now, that's not really a FreeBSD amd64 > > problem though. > > > > Yes, that's a problem. I was forced to give up my G550 because MATROX > didn't have any 64-bit drivers at that time. The situation may have > changed since then, it was several months ago. It doesn't seem to look anymore promising at this time either. There doesn't seem to be any added hope expressed by the tech support staff's posts on the Matrox support forums. Luckily returning my card was fairly painless. Now I just have to wait a couple days to receive my ATI Radeon 9250. It ships out tomorrow, so if there's any last words of advice/general info... please speak now! :) James From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 04:52:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3393916A4CE; Wed, 1 Dec 2004 04:52:32 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id F242143D49; Wed, 1 Dec 2004 04:52:31 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 5BCF5CD72; Tue, 30 Nov 2004 23:52:31 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 7A22E6807; Tue, 30 Nov 2004 23:52:30 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16813.19982.377480.293323@canoe.dclg.ca> Date: Tue, 30 Nov 2004 23:52:30 -0500 To: obrien@freebsd.org In-Reply-To: <20041130225412.GA26088@hub.freebsd.org> References: <16811.51043.987275.174410@canoe.dclg.ca> <20041130193932.GI14039@freebie.xs4all.nl> <200411301222.24062.peter@wemm.org> <20041130202633.GA15157@freebie.xs4all.nl> <16812.56143.60199.332283@canoe.dclg.ca> <20041130225412.GA26088@hub.freebsd.org> X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid cc: Wilko Bulte cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org cc: freebsd-hackers@freebsd.org cc: David Gilbert Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 04:52:32 -0000 >>>>> "David" == David O'Brien writes: David> On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote: >> I just heard back from some people still onsite. The ISP driver >> booted with everything the same except hw.physmem=2g works. It's a >> memory issue. David> Try hw.physmem=4g. It should be the 4GB boundary, not 2GB David> boundary that is causing you trouble. They will likely do that, but that result is slightly less important. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 07:33:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3980E16A4CE for ; Wed, 1 Dec 2004 07:33:56 +0000 (GMT) Received: from kogut.o2.pl (kogut.o2.pl [212.126.20.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id C171043D41 for ; Wed, 1 Dec 2004 07:33:55 +0000 (GMT) (envelope-from morgothdbma@o2.pl) Received: from p22111 (p22111.mini.pw.edu.pl [194.29.178.42]) by kogut.o2.pl (o2.pl Mailer 2.0.1) with SMTP id AF9332EE8A1 for ; Wed, 1 Dec 2004 08:33:53 +0100 (CET) Message-ID: <000601c4d778$1cf25f30$2ab21dc2@p22111> From: "Lukasz Gryglicki" To: Date: Wed, 1 Dec 2004 08:33:47 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: xmms problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 07:33:56 -0000 Is there anybody who got xmms working with FreeBSD 5.3 amd64? If so please contact me or send me some instructions Thanks. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 08:39:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E328A16A4CE for ; Wed, 1 Dec 2004 08:39:58 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98F7A43D5A for ; Wed, 1 Dec 2004 08:39:58 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1CZQ1l-0004JG-Os for freebsd-amd64@freebsd.org; Wed, 01 Dec 2004 10:39:57 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Dec 2004 10:39:57 +0200 From: Danny Braniss Message-Id: <20041201083958.98F7A43D5A@mx1.FreeBSD.org> Subject: acpi related failure - again X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:39:59 -0000 hi, Funny how things reappear, i submitted a PR almost a year ago, and now with the latest -current it resurfaced :-) http://www.freebsd.org/cgi/query-pr.cgi?pr=59732 this is a shuttle FN85/AMD64/NForce. disabling acpi in the bios had me working till now, including latest 5.3 with latest current: with acpi enabled in bios it hangs: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/shuttle+acpi.log with acpi disabled in bios it hangs: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/shuttle-acpi.log anything i can help? danny From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 08:45:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2048016A4CE; Wed, 1 Dec 2004 08:45:44 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAF0043D2F; Wed, 1 Dec 2004 08:45:41 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB18jci8036414; Wed, 1 Dec 2004 00:45:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB18jc8j036413; Wed, 1 Dec 2004 00:45:38 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 00:45:37 -0800 From: "David O'Brien" To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201084537.GA1621@dragon.nuxi.com> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130142652.A59122@bahre.achedra.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:45:44 -0000 On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Tue, 30 Nov 2004, Steve Kargl wrote: > > > >The system starts to boot and dmesg reports the 16 GB of memory, but > >I rapidly get this panic. > > >So, it looks like ACPI on this Tyan motherboard is restricting > >the memory to 8G. > > I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB > ECC Reg'd.) > More importantly, which BIOS version? You have to run the 2.03 BIOS on > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > in the BIOS as well - this was a never-ending source of fun on both the > S2882 and S4882's. There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a NUMA architecture machine regardless of any BIOS settings. I.E. there is no way to disable that a MP Opteron is a NUMA machine. The setting of interest is should the BIOS round-robin interleave physical addresses across the NUMA nodes[*]. The reference AMI BIOS refers to this as "Node Interleaving". It should be "DISABLED". Or if the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on the SRAT turns off node interleaving. There is a CPU errata for older CPU's that can cause problems if you have both memory interleaving turned on and ECC turned enabled in the BIOS. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 08:50:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AEAE16A4CE for ; Wed, 1 Dec 2004 08:50:39 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id D56E043D4C for ; Wed, 1 Dec 2004 08:50:38 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB18ocOE036687; Wed, 1 Dec 2004 00:50:38 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB18ocVJ036686; Wed, 1 Dec 2004 00:50:38 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 00:50:37 -0800 From: "David O'Brien" To: "T.F. Cheng" Message-ID: <20041201085037.GB1621@dragon.nuxi.com> References: <2fd864e0411272134409d1faa@mail.gmail.com> <20041128163437.43496.qmail@web51003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041128163437.43496.qmail@web51003.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:50:39 -0000 On Mon, Nov 29, 2004 at 12:34:37AM +0800, T.F. Cheng wrote: > another thing is about the memory's "dual channel > arch". Which one will be better? should I buy 2 256MB > RAM or just one 512MB at the present? You want to install DIMM's in pairs, other wise you could have saved $$ and bought a 754-pin system. So buy 2x 256MB. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 08:59:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CA4D16A4CE for ; Wed, 1 Dec 2004 08:59:03 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id D2C8943D5F for ; Wed, 1 Dec 2004 08:59:01 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 9112 invoked by uid 513); 1 Dec 2004 08:59:03 -0000 Received: from 82.141.58.98 by dsl-mail (envelope-from , uid 89) with qmail-scanner-1.24 (clamdscan: 0.80/609. spamassassin: 2.60. Clear:RC:1(82.141.58.98):SA:0(-1.6/5.0):. Processed in 0.953101 secs); 01 Dec 2004 08:59:03 -0000 X-Spam-Status: No, hits=-1.6 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.98) by dsl-mail.kamp.net with SMTP; 1 Dec 2004 08:59:02 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id iB191nwI014160; Wed, 1 Dec 2004 10:01:49 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id iB191mkZ014159; Wed, 1 Dec 2004 10:01:48 +0100 (CET) (envelope-from ewinter) Date: Wed, 1 Dec 2004 10:01:48 +0100 From: "Ernst W. Winter" To: Lukasz Gryglicki Message-ID: <20041201090148.GA13790@lobo.homeunix.org> References: <000601c4d778$1cf25f30$2ab21dc2@p22111> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c4d778$1cf25f30$2ab21dc2@p22111> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: xmms problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:59:03 -0000 On Wed, 01 Dec 2004, Lukasz "i8254" frequency 1193182 Hz quality 0 wrote: > Is there anybody who got xmms working with FreeBSD 5.3 amd64? > If so please contact me or send me some instructions > > Thanks. Yes here it works with: ----------------------------------------------------------------------- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #23: Wed Nov 24 10:09:37 igin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 2004 ewinter@lobo.homeunix.org:/usr/es=0x78bfbff,LM,3DNow+,3DNow>,CX8,APIC,SEP,MTRR,PGE,MCA,CM/usr/src/sys/lobo ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1802.32-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073414144 (1023 MB) avail memory = 1026928640 (979 MB) ----------------------------------------------------------------------' no problems so far, what would you like to know or what can I hlep with. Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 09:01:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A85416A4CE for ; Wed, 1 Dec 2004 09:01:01 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 584C243D46 for ; Wed, 1 Dec 2004 09:01:01 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB190RaO036898; Wed, 1 Dec 2004 01:00:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB190O7a036897; Wed, 1 Dec 2004 01:00:24 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 01:00:24 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20041201090024.GC1621@dragon.nuxi.com> References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> <41A80A0F.9030502@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A80A0F.9030502@gmail.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Page fault on Tyan K8S Pro (S2882) board X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:01:01 -0000 On Fri, Nov 26, 2004 at 09:01:03PM -0800, Astrodog wrote: > Running 1 DIMM in this kind of setup is > shooting yourself in the foot. If CPU #1 requests something through CPU > #0, and we're using 1 bank of memory the whole setup..... performance is > gonna be crap. Both CPUs will be blocked from processing instructions > while the request is fulfilled. That is not at all true -- CPU0 is not blocked because CPU1 is accessing memory directly attached to CPU0. The memory controller in an Opteron operates independently of the CPU cache unit and central processing unit ("core"). All of the the HyperTransport connections (3 of them), the memory controller, cache unit (2 for dual-core) all attach together thru a cross-bar switch. > There are known performance issues with the 4+0 memory config... but > they're still good if you use 2 or 4 DIMMs. There aren't performance issues with 4+0 memory configurations -- unless you also consider it a "performance issue" if one is using DDR333 or DDR266 memory vs. DDR400. CPU1 has a higher latency to memory than CPU0, 105ns vs. 70ns; BUT 105ns is still lower than the latency of going thru a traditional northbridge. So its all a trade off of where you want to be on the performance curve. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 09:08:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA0D516A4CE for ; Wed, 1 Dec 2004 09:08:53 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A9343D1F for ; Wed, 1 Dec 2004 09:08:53 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB198nhC037147; Wed, 1 Dec 2004 01:08:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB198n3G037146; Wed, 1 Dec 2004 01:08:49 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 01:08:49 -0800 From: "David O'Brien" To: Chuck Robey Message-ID: <20041201090849.GD1621@dragon.nuxi.com> References: <20041124145143.O4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124145143.O4002@april.chuckr.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:08:53 -0000 On Wed, Nov 24, 2004 at 02:57:07PM -0500, Chuck Robey wrote: > I noticed that acroread is marked as being only for the i386 ... I have a > question about that ... I'm a little new at running the amd64, but I > thought that it was compatible (if it had the 32 bit libraries installed > to support it) with i386, so I would have expected my amd64 machine to be > ablel to run acroread with little trouble. The port being marked > as"ONLY_FOR_ARCHS", well, I considered, *possibly*, that the port author > hadn't had the testing capability, and maybe it did too work on the amd64. The problem is that running i386 Linux binaries on FreeBSD/amd64 is still a hack job in that none of the /usr/ports framework was made to actually support this. None of the linux_base* ports will install on FreeBSD/amd64, and that is a requirement of acroread. You can install Slackware i386 libs by hand and get acroread to run. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 09:17:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C2DA16A4CE for ; Wed, 1 Dec 2004 09:17:32 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5441643D48 for ; Wed, 1 Dec 2004 09:17:32 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB19HVx6037321; Wed, 1 Dec 2004 01:17:31 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB19HUIT037320; Wed, 1 Dec 2004 01:17:30 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 01:17:30 -0800 From: "David O'Brien" To: a.degroot@science.ru.nl Message-ID: <20041201091730.GE1621@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Cross-compiling on x86 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:17:32 -0000 On Tue, Nov 23, 2004 at 12:45:05PM +0100, a.degroot@science.ru.nl wrote: > For various large compiles (KDE, mostly), I'm looking into setting up a > compile farm to produce amd64 inaries. A basic distcc setup, to start with > (icecream, the teambuilder-alike with some pretty neat features, is still > horribly linux-specific and I need to fix that some time), but I'm > somewhat lacking on the number-of-amd64 machines front, as in I've got 1. > > So I got to thinking: why should the x86 machines in the house get a > break? They should be able to produce amd64 code at the least. > > The system gcc on 5.3-R on x86 doesn't like -m64: > > -bash-2.05b$ g++ -c -m64 t.cc > t.cc:1: sorry, unimplemented: 64-bit mode not compiled in > > which is unfortunate, because if I understand correctly, that's the only > flag I would really need to use to make gcc on x86en produce code for > amd64 (ie. > > x86box$ g++ -m64 t.cc > amd64box$ g++ t.cc Nope, you need a lot more than 'gcc -m64' to be accepted. You also need a 64-bit capable 'as' and 'ld'. You also need 64-bit libs (matching what's in /lib and /usr/lib), and 64-bit /usr/include/machine headers. We're no where near ready to support cross building for 64-bits on a 32-bit machine and vice-versa. I've got a WIP patch set for GCC on FreeBSD/amd64 to enable one to build 32-bit binaries, provided 32-bit libs are available. But it will be a little while longer until things are ready for use. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 09:47:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EBD316A4CE; Wed, 1 Dec 2004 09:47:37 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81BC843D31; Wed, 1 Dec 2004 09:47:36 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB19lpqj090971; Wed, 1 Dec 2004 04:47:51 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Wed, 1 Dec 2004 04:47:51 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: "David O'Brien" In-Reply-To: <20041201084537.GA1621@dragon.nuxi.com> Message-ID: <20041201042900.A88450@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041201084537.GA1621@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:47:37 -0000 On Wed, 1 Dec 2004, David O'Brien wrote: > There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > NUMA architecture machine regardless of any BIOS settings. I.E. there is > no way to disable that a MP Opteron is a NUMA machine. > The setting of interest is should the BIOS round-robin interleave > physical addresses across the NUMA nodes[*]. The reference AMI BIOS > refers to this as "Node Interleaving". It should be "DISABLED". Or if > the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > the SRAT turns off node interleaving. David, trying very hard to be nice, the S2882's a 'Special Case.' Where special should be taken as 'short bus.' VERY short bus. On the S2882/S2885, and even the S4882, the BIOS specifically says, and I quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got it, SRAT Table Control, which _disables_ interleave completely. Beautiful, huh? The only way to enable interleave on the S2882/S2885 is to specifically turn 'ccNUMA' off; otherwise it's SRAT only, with no interleave. And no, it's not mentioned anywhere on the S2882s. Only on the S4882, which uses a Phoenix 6.0 reference. (Which Tyan, predictably, did not remove the reference lines _or_ fix the typos on.) The S2882s also use a Phoenix, I believe. So in order to enable Interleave, your only method is that switch. What got me peering curiously here is the placement of the hole; there appears to be a 512MB hole, starting at 4024MB. It certainly is similar to the behavior of 2882 I've looked at; hole is about 1/3rd through memory. On the 2.03 BIOS, still no way to control the PCI hole; that feature is reserved for the S4882 apparently, and even then only size. If the hole _is_ at 4024MB, that would put it past 4096MB and the 4GB limit; on the S2882 the bulk of the peripherals are on the PCI32 bus, not a PCI64 bus. Specifically, disk, fxp(4), bge(4), ACPI, and USB. Presuming I am reading the hole correctly, and bearing in mind that I do not have access to my copy of the PCI2.3 spec, ISTR that the entirety of the PCI memory hole must be within the first 4GB of system memory. (I'd appreciate it if someone could sanity check that.) Presuming that it does need to be within the first 4GB of system memory, I'm wondering if what's being seen here is not a BIOS bug. These boards have a real bad track record with regards to them, so it would not be at all surprising, at least to me. -ksaihr From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 10:02:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3403916A4CF for ; Wed, 1 Dec 2004 10:02:03 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B460C43D2D for ; Wed, 1 Dec 2004 10:02:02 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so213318wri for ; Wed, 01 Dec 2004 02:02:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=LBTPHNIruULb3aB62Vzr+pSFmI6zytOA2Lh2eBRjy4UQ5ST5aASIHTQIOtMzTCmRuybMbVFcnr9R9GMqWzOG8bdc8rBtrTCjFYmHufGvULE+E0RNm5hr/fAHcED7R9RAIM9vOw+TZhZKArtP0gWU6wHutYBwR1PcHd9GrkDTJzQ= Received: by 10.54.30.59 with SMTP id d59mr592436wrd; Wed, 01 Dec 2004 02:02:02 -0800 (PST) Received: by 10.54.40.6 with HTTP; Wed, 1 Dec 2004 02:02:02 -0800 (PST) Message-ID: <2fd864e04120102022a1f5a7a@mail.gmail.com> Date: Wed, 1 Dec 2004 02:02:02 -0800 From: Astrodog To: obrien@freebsd.org In-Reply-To: <20041201090024.GC1621@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> <41A80A0F.9030502@gmail.com> <20041201090024.GC1621@dragon.nuxi.com> cc: freebsd-amd64@freebsd.org Subject: Re: Page fault on Tyan K8S Pro (S2882) board X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 10:02:03 -0000 Isn't CPU0 blocked from memory, while CPU1 makes a request (and has it fulfilled?) If not... how'd they manage that? Thats cool as hell. Heh. --- Harrison Grundy On Wed, 1 Dec 2004 01:00:24 -0800, David O'Brien wrote: > On Fri, Nov 26, 2004 at 09:01:03PM -0800, Astrodog wrote: > > Running 1 DIMM in this kind of setup is > > shooting yourself in the foot. If CPU #1 requests something through CPU > > #0, and we're using 1 bank of memory the whole setup..... performance is > > gonna be crap. Both CPUs will be blocked from processing instructions > > while the request is fulfilled. > > That is not at all true -- CPU0 is not blocked because CPU1 is accessing > memory directly attached to CPU0. The memory controller in an Opteron > operates independently of the CPU cache unit and central processing unit > ("core"). All of the the HyperTransport connections (3 of them), the > memory controller, cache unit (2 for dual-core) all attach together thru > a cross-bar switch. > > > > There are known performance issues with the 4+0 memory config... but > > they're still good if you use 2 or 4 DIMMs. > > There aren't performance issues with 4+0 memory configurations -- unless > you also consider it a "performance issue" if one is using DDR333 or > DDR266 memory vs. DDR400. CPU1 has a higher latency to memory than CPU0, > 105ns vs. 70ns; BUT 105ns is still lower than the latency of going thru a > traditional northbridge. > > So its all a trade off of where you want to be on the performance curve. > > -- > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 12:29:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3534516A4CE for ; Wed, 1 Dec 2004 12:29:02 +0000 (GMT) Received: from hotmail.com (bay13-f40.bay13.hotmail.com [64.4.31.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BDE43D66 for ; Wed, 1 Dec 2004 12:29:02 +0000 (GMT) (envelope-from martarese@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Dec 2004 04:29:01 -0800 Message-ID: Received: from 213.22.141.131 by by13fd.bay13.hotmail.msn.com with HTTP; Wed, 01 Dec 2004 12:28:53 GMT X-Originating-IP: [213.22.141.131] X-Originating-Email: [martarese@hotmail.com] X-Sender: martarese@hotmail.com In-Reply-To: <2fd864e04113023364ff4018f@mail.gmail.com> From: "Marta Resende" To: freebsd-amd64@freebsd.org Date: Wed, 01 Dec 2004 12:28:53 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 01 Dec 2004 12:29:01.0131 (UTC) FILETIME=[5654A1B0:01C4D7A1] Subject: Re: Dimm difference ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 12:29:02 -0000 How can i teste that under freebsd? Which method i can use to see if my two ddr cards are working under dual channel? thks >From: Astrodog >Reply-To: Astrodog >To: Marta Resende >Subject: Re: Dimm difference ? >Date: Tue, 30 Nov 2004 23:36:59 -0800 > >If they're the same size and whatnot... they might work. No way to >tell without trying. > > >On Wed, 01 Dec 2004 02:28:39 +0000, Marta Resende >wrote: > > Hey, > > > > i adquire 2 dimm blocks, to put it runnind in amd64, the 2 are 512MB DDR > > PC3200 CL3 (samsung), although, one is 30331-B2 and another is 30331-Z, >they > > are a little bit thifference (dont know where), so they wont wwork as >dual > > channel right ?? > > > > thks > > > > _________________________________________________________________ > > Express yourself instantly with MSN Messenger! Download today it's FREE! > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > > _______________________________________________ > > 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" > > _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 15:50:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D08AB16A4CF for ; Wed, 1 Dec 2004 15:50:35 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id F01DE43D54 for ; Wed, 1 Dec 2004 15:50:34 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from [192.168.1.102] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc12) with ESMTP id <20041201155020014004fga6e>; Wed, 1 Dec 2004 15:50:34 +0000 Message-ID: <41ADE8CC.6080707@pythonemproject.com> Date: Wed, 01 Dec 2004 07:52:44 -0800 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ernst W. Winter" References: <000601c4d778$1cf25f30$2ab21dc2@p22111> <20041201090148.GA13790@lobo.homeunix.org> In-Reply-To: <20041201090148.GA13790@lobo.homeunix.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Lukasz Gryglicki cc: freebsd-amd64@freebsd.org Subject: Re: xmms problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 15:50:36 -0000 Ernst W. Winter wrote: >On Wed, 01 Dec 2004, Lukasz "i8254" frequency 1193182 Hz quality 0 wrote: > > > >>Is there anybody who got xmms working with FreeBSD 5.3 amd64? >>If so please contact me or send me some instructions >> >>Thanks. >> >> > >Yes here it works with: > >----------------------------------------------------------------------- > >Copyright (c) 1992-2004 The FreeBSD Project. >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, >1994 > The Regents of the University of California. All rights >reserved. >FreeBSD 5.3-STABLE #23: Wed Nov 24 10:09:37 igin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 2004 > ewinter@lobo.homeunix.org:/usr/es=0x78bfbff,LM,3DNow+,3DNow>,CX8,APIC,SEP,MTRR,PGE,MCA,CM/usr/src/sys/lobo >ACPI APIC Table: >Timecounter "i8254" frequency 1193182 Hz quality 0 >CPU: AMD Athlon(tm) 64 Processor 3000+ (1802.32-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 > Features=0x78bfbffOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=0xe2500800,LM,3DNow+,3DNow> >real memory = 1073414144 (1023 MB) >avail memory = 1026928640 (979 MB) > >----------------------------------------------------------------------' > >no problems so far, what would you like to know or what can I hlep >with. > >Ernst > >-- >Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > BSD: Are you guys coming, or what? > > >_______________________________________________ >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" > > > Soapbox: I thought it was kind of chickens__t that it was removed from ports. Perhaps it is back in there. Note that this is for 32 bit only. Haven't gotten around to testing it on my AMD +3800 machine. So YMMV. 1. Go to www.xmms.org (or com?) and download tar'd gzip'd file 2. Ungzip it with tar -xzf xmms.tar.gz or xmms.tgz 2.5 Change to xmms directory 3. Su to root (not absolutely neccessary) 4. Type ./configure 5. Type make 6. Type make install (have to be root here, or better su to root) You're done! Access it with XFree86 with xmms command in a window. Mime type to add to browser is audio/x-scpl, program is xmms %s.. Now you can go to www.shoutcast.com or some other streaming audio site and listen to radio stations. www.kfjc.org is my personal favorite. Been listening for 20 years, first on FM, then when I moved via net. Onother good one is www.radiofg.com in Paris, techno, R&B, pop. Xmms pops up audomagically then. Rob. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 17:16:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F383A16A4CE for ; Wed, 1 Dec 2004 17:16:47 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9225043D54 for ; Wed, 1 Dec 2004 17:16:47 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB1HGkwp048950; Wed, 1 Dec 2004 09:16:46 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB1HGkSF048949; Wed, 1 Dec 2004 09:16:46 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 09:16:45 -0800 From: "David O'Brien" To: Astrodog Message-ID: <20041201171645.GA48294@dragon.nuxi.com> References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> <41A80A0F.9030502@gmail.com> <20041201090024.GC1621@dragon.nuxi.com> <2fd864e04120102022a1f5a7a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e04120102022a1f5a7a@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Page fault on Tyan K8S Pro (S2882) board X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 17:16:48 -0000 [ DON'T top post -- it looses context, and usually I won't reply... ] On Wed, Dec 01, 2004 at 02:02:02AM -0800, Astrodog wrote: > On Wed, 1 Dec 2004 01:00:24 -0800, David O'Brien wrote: > > On Fri, Nov 26, 2004 at 09:01:03PM -0800, Astrodog wrote: > > > Running 1 DIMM in this kind of setup is > > > shooting yourself in the foot. If CPU #1 requests something through CPU > > > #0, and we're using 1 bank of memory the whole setup..... performance is > > > gonna be crap. Both CPUs will be blocked from processing instructions > > > while the request is fulfilled. > > > > That is not at all true -- CPU0 is not blocked because CPU1 is accessing > > memory directly attached to CPU0. The memory controller in an Opteron > > operates independently of the CPU cache unit and central processing unit > > ("core"). All of the the HyperTransport connections (3 of them), the > > memory controller, cache unit (2 for dual-core) all attach together thru > > a cross-bar switch. ..snip.. > Isn't CPU0 blocked from memory, while CPU1 makes a request (and has it > fulfilled?) > If not... how'd they manage that? Thats cool as hell. Heh. Not any more than with a traditional northbridge system. The memory controller has a request queue. While it is getting the data from the memory that CPU1 requested, CPU0 can certainly add entries to the request queue during the time the data is becoming ready to read from the DIMM's, etc... Think of it as a "fine-grain locked kernel". The memory controller doesn't have the "Big Giant Lock" such that it can't do a single other thing as soon as CPU1 makes a memory request. Digging deeper, http://www.amd.com/us-en/assets/content_type/DownloadableAssets/MPF_Hammer_Presentation.PDF slides 2628 are good pictures showing who there are actually two pieces to what most call a "memory controller" -- the true memory controller (with queues and scheduling (handling dependencies) etc..) and the DRAM controller (handling the real-world electrical duties). Also you can see the high-level data queues and buffers and how they interconnect with cross-bar switches. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 17:47:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27C9916A4CE for ; Wed, 1 Dec 2004 17:47:22 +0000 (GMT) Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86FAD43D39 for ; Wed, 1 Dec 2004 17:47:21 +0000 (GMT) (envelope-from freebsdnewbie@freenet.de) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout0.freenet.de with esmtpa (Exim 4.43) id 1CZYZT-0000fO-Rx for freebsd-amd64@freebsd.org; Wed, 01 Dec 2004 18:47:19 +0100 Received: from pd9ead756.dip0.t-ipconnect.de ([217.234.215.86] helo=amd64.bsdnet.)4.43 #13) id 1CZYZT-0006gk-BU; Wed, 01 Dec 2004 18:47:19 +0100 Date: Wed, 1 Dec 2004 18:46:13 +0100 From: Manuel =?ISO-8859-1?Q?St=FChn?= To: FreeBSDquestions Message-Id: <20041201184613.585ecace.freebsdnewbie@freenet.de> X-Mailer: Sylpheed version 0.9.99-gtk2-20041024 (GTK+ 2.4.13; amd64-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Wed__1_Dec_2004_18_46_13_+0100_lJ8DEsXQFELA5yDF" Subject: amd64 and boaconstructor X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 17:47:22 -0000 This is a multi-part message in MIME format. --Multipart=_Wed__1_Dec_2004_18_46_13_+0100_lJ8DEsXQFELA5yDF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi. Has anybody /usr/ports/devel/boaconstructor running on an amd64? On my FreeBSD 5.3-p1 amd64 Box, it refuses cooperation. The error message is attached at this mail. Thanks in advance Manuel -- Borges sumus. Resistere inutile est. --Multipart=_Wed__1_Dec_2004_18_46_13_+0100_lJ8DEsXQFELA5yDF Content-Type: text/plain; name="log.txt" Content-Disposition: attachment; filename="log.txt" Content-Transfer-Encoding: quoted-printable 18:22:17: Traceback (most recent call last): = =20 18:22:17: File "/usr/local/share/Boa/Utils.py", line 771, in = =20 18:22:17: lambda event: apply(event.callable, event.args, event.kw) ) = =20 18:22:17: File "/usr/local/share/Boa/Palette.py", line 352, in OnCrea= teNew =20 18:22:17: self.editor.addNewPage(name, controller) = =20 18:22:17: File "/usr/local/share/Boa/Editor.py", line 655, in addNewP= age =20 18:22:17: controller.AdditionalViews, model.imgIdx) = =20 18:22:17: File "/usr/local/share/Boa/Editor.py", line 555, in addModu= lePage =20 18:22:17: modulePage =3D ModulePage(notebook, model, defViews, views, s= pIdx, self) =20 18:22:17: File "/usr/local/share/Boa/EditorUtils.py", line 197, in __= init__ =20 18:22:17: self.addView(View) = =20 18:22:17: File "/usr/local/share/Boa/EditorUtils.py", line 306, in ad= dView =20 18:22:17: panel, self.model.views[viewName] =3D Utils.wxProxyPanel(self= .notebook, view, self.model) 18:22:17: File "/usr/local/share/Boa/Utils.py", line 342, in wxProxyP= anel =20 18:22:17: win =3D apply(Win, (panel,) + args, kwargs) = =20 18:22:17: File "/usr/ports/devel/boaconstructor/work/boa-constructor-= 0.2.3/Views/PySourceView.py", line 90, in __init__ 18:22:17: File "/usr/ports/devel/boaconstructor/work/boa-constructor-= 0.2.3/Views/StyledTextCtrls.py", line 54, in __init__ 18:22:17: File "/usr/local/lib/python2.4/site-packages/wxPython/stc_.= py", line 285, in SetMarginMask 18:22:17: val =3D stc_c.wxStyledTextCtrl_SetMarginMask(self, *_args, **= _kwargs) =20 18:22:17: OverflowError: signed integer is greater than maximum = =20 --Multipart=_Wed__1_Dec_2004_18_46_13_+0100_lJ8DEsXQFELA5yDF-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 18:00:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD53616A4CE; Wed, 1 Dec 2004 18:00:09 +0000 (GMT) Received: from skippyii.compar.com (old.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E93443D31; Wed, 1 Dec 2004 18:00:09 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [69.193.82.185])iB1I7BK2013418; Wed, 1 Dec 2004 13:07:12 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00c601c4d7cf$3652ba90$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Dan Nelson" , "David Gilbert" References: <16811.51043.987275.174410@canoe.dclg.ca> <003801c4d685$81192640$1200a8c0@gsicomp.on.ca> <16811.58127.759026.560570@canoe.dclg.ca> <20041130055611.GN5518@dan.emsphone.com> Date: Wed, 1 Dec 2004 12:57:21 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: freebsd-hackers@freebsd.org cc: freebsd-list@dclg.ca cc: freebsd-amd64@freebsd.org Subject: Re: isp driver not 64 bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:00:10 -0000 ----- Original Message ----- From: "Dan Nelson" To: "David Gilbert" Cc: "Matt Emmerton" ; ; ; Sent: Tuesday, November 30, 2004 12:56 AM Subject: Re: isp driver not 64 bit? > In the last episode (Nov 29), David Gilbert said: > > Well... cam_calc_geometry seems to get called quite a bit. Almost > > everytime you touch the disk, in fact. fsck'ing a partition calls > > it, for instance. Does this not seem excessive to anyone? Call me naive, but shouldn't the only time we need to obtain the geometry is at initial probe time? > > Console access is personally expensive (much driving, for instance), > > but from memory the debugging I put in cam_calc_geometry() would > > print before the correct output from dadone(). Your description > > reminds me of this --- but it's no less vexing that the output from > > dadone() has the correct sector and volume size and the ccg in > > cam_calc_geometry() has bogus data. > > > > I don't know if it's significant, but the correct numbers were: > > > > 279353684 sectors of 512 bytes > > > > The ccg structure comes up with: > > > > 3737169375 sectors of 3737169374 bytes > > > > Not entirely sensible. Interesting that they're close values. > > However, with different things on the stack, the values changed. > > Even more interesting is their hex values: > > DEC0ADDF and DEC0ADDE, aka 0xDEADC0DE. Something's reading memory > after the kernel freed it. Which makes me wonder if one of our 'extra' cam_calc_geometry() calls is being executed from a place where it shouldn't be. -- Matt Emmerton From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 18:15:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84F6116A4CF; Wed, 1 Dec 2004 18:15:51 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E29843D54; Wed, 1 Dec 2004 18:15:51 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB1IFnYp006279; Wed, 1 Dec 2004 10:15:49 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB1IFnt9006278; Wed, 1 Dec 2004 10:15:49 -0800 (PST) (envelope-from sgk) Date: Wed, 1 Dec 2004 10:15:49 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201181549.GA6236@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> <20041201042900.A88450@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201042900.A88450@bahre.achedra.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:15:51 -0000 On Wed, Dec 01, 2004 at 04:47:51AM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Wed, 1 Dec 2004, David O'Brien wrote: > > >There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > >NUMA architecture machine regardless of any BIOS settings. I.E. there is > >no way to disable that a MP Opteron is a NUMA machine. > >The setting of interest is should the BIOS round-robin interleave > >physical addresses across the NUMA nodes[*]. The reference AMI BIOS > >refers to this as "Node Interleaving". It should be "DISABLED". Or if > >the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > >doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > >the SRAT turns off node interleaving. > > David, trying very hard to be nice, the S2882's a 'Special Case.' > Where special should be taken as 'short bus.' VERY short bus. > > On the S2882/S2885, and even the S4882, the BIOS specifically says, and I > quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got > it, SRAT Table Control, which _disables_ interleave completely. Beautiful, > huh? My BIOS does not have "ccNUMA Support" anywhere. During POST I see AMIBIOS 2003(c), American Megatrends, Inc. BIOS Date: 07/07/04 11:11:45 Ver 08.00.10 TYAN High-End Dual AMD Opteron BIOS v2.03 -- Steve From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 18:21:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3CDF16A4CE; Wed, 1 Dec 2004 18:21:04 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACFCA43D49; Wed, 1 Dec 2004 18:21:04 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB1IL3Ar006321; Wed, 1 Dec 2004 10:21:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB1IL30D006320; Wed, 1 Dec 2004 10:21:03 -0800 (PST) (envelope-from sgk) Date: Wed, 1 Dec 2004 10:21:03 -0800 From: Steve Kargl To: "David O'Brien" Message-ID: <20041201182103.GB6236@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201084537.GA1621@dragon.nuxi.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:21:05 -0000 On Wed, Dec 01, 2004 at 12:45:37AM -0800, David O'Brien wrote: > > The setting of interest is should the BIOS round-robin interleave > physical addresses across the NUMA nodes[*]. The reference AMI BIOS > refers to this as "Node Interleaving". It should be "DISABLED". Or if > the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > the SRAT turns off node interleaving. Thanks for the reply. Unfortunately, setting "ACPI SRAT Support" to ENABLE and having "Node Interleaving" set to DISABLE does not help. I still get the panic if hw.physmem="16G". -- Steve From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 18:38:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28DE916A4CE; Wed, 1 Dec 2004 18:38:04 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22EC43D55; Wed, 1 Dec 2004 18:38:03 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB1Ic0K3051028; Wed, 1 Dec 2004 10:38:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB1Ibxtn051027; Wed, 1 Dec 2004 10:37:59 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 10:37:59 -0800 From: "David O'Brien" To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201183759.GB48294@dragon.nuxi.com> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> <20041201042900.A88450@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201042900.A88450@bahre.achedra.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:38:04 -0000 On Wed, Dec 01, 2004 at 04:47:51AM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Wed, 1 Dec 2004, David O'Brien wrote: > > >There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > >NUMA architecture machine regardless of any BIOS settings. I.E. there is > >no way to disable that a MP Opteron is a NUMA machine. > >The setting of interest is should the BIOS round-robin interleave > >physical addresses across the NUMA nodes[*]. The reference AMI BIOS > >refers to this as "Node Interleaving". It should be "DISABLED". Or if > >the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > >doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > >the SRAT turns off node interleaving. > > David, trying very hard to be nice, the S2882's a 'Special Case.' > Where special should be taken as 'short bus.' VERY short bus. > > On the S2882/S2885, and even the S4882, the BIOS specifically says, and I > quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got > it, SRAT Table Control, which _disables_ interleave completely. Beautiful, > huh? The only way to enable interleave on the S2882/S2885 is to > specifically turn 'ccNUMA' off; otherwise it's SRAT only, with no > interleave. I've seen S2882 BIOS's that don't say "ccNUMA" and my S2885 K8W Thunder certainly doesn't. It's BIOS knobs and explanation are: Interleaving allows memory accesses to be spread out over BANKS on the same node, or across NODES, decreasing access contention. o "Bank Interleaving" o "Node Interleaving" On every Operon BIOS (AMI or Phoenix), the SRAT enabling and Node Interleaving are related -- they are mutually exclusive by design as Node Interleaving lets the BIOS setup the physical memory topology vs. enabling the SRAT which then puts it in the OS's court. Enabling the SRAT doesn't need to and shouldn't disable Bank Interleaving. > And no, it's not mentioned anywhere on the S2882s. Nor in the AMI reference BIOS :-(, which is a shame as more information might better clear things up. > Only on > the S4882, which uses a Phoenix 6.0 reference. (Which Tyan, predictably, > did not remove the reference lines _or_ fix the typos on.) The S2882s > also use a Phoenix, I believe. So in order to enable Interleave, your > only method is that switch. Actually the S2882 uses a AMI BIOS, as does all of Tyan's 2P Opteron boards, except the S2885 variant Tyan makes for the Fujitsu Celsius V810. I like the Fujitsu Celsius V810 Phoenix better, wished it was used on all S2885's. > What got me peering curiously here is the placement of the hole; there > appears to be a 512MB hole, starting at 4024MB. It certainly is similar > to the behavior of 2882 I've looked at; hole is about 1/3rd through > memory. On the 2.03 BIOS, still no way to control the PCI hole; that > feature is reserved for the S4882 apparently, and even then only size. How do you want to control the "memory hole"? It is mandatory in order to map in memory mapped I/O devices. > If the hole _is_ at 4024MB, that would put it past 4096MB and the 4GB > limit; on the S2882 the bulk of the peripherals are on the PCI32 bus, not > a PCI64 bus. Specifically, disk, fxp(4), bge(4), ACPI, and USB. > Presuming I am reading the hole correctly, and bearing in mind that I do > not have access to my copy of the PCI2.3 spec, ISTR that the entirety of > the PCI memory hole must be within the first 4GB of system memory. (I'd > appreciate it if someone could sanity check that.) Correct, the "memory hole" must be below the 4GB mark. http://www.amd.com/us-en/assets/content_type/DownloadableAssets/RichBrunnerClusterWorldpresFINAL.pdf slide 25 is AMD's picture for this. The "hole" is of course an area where memory mapped PCI I/O, APIC, APG GART, etc.. are mapped into the memory address space. Thus RAM cannot be addressed using (mapped into) those memory locations. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 19:29:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99FF016A4CE; Wed, 1 Dec 2004 19:29:49 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0102A43D1D; Wed, 1 Dec 2004 19:29:49 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB1JU6UY092853; Wed, 1 Dec 2004 14:30:06 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Wed, 1 Dec 2004 14:30:06 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: "David O'Brien" In-Reply-To: <20041201183759.GB48294@dragon.nuxi.com> Message-ID: <20041201141150.I88450@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041201084537.GA1621@dragon.nuxi.com> <20041201183759.GB48294@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:29:49 -0000 On Wed, 1 Dec 2004, David O'Brien wrote: > I've seen S2882 BIOS's that don't say "ccNUMA" and my S2885 K8W Thunder > certainly doesn't. It's BIOS knobs and explanation are: > Interleaving allows memory accesses to be spread out over BANKS on the > same node, or across NODES, decreasing access contention. > o "Bank Interleaving" > o "Node Interleaving" > On every Operon BIOS (AMI or Phoenix), the SRAT enabling and Node > Interleaving are related -- they are mutually exclusive by design as Node > Interleaving lets the BIOS setup the physical memory topology vs. > enabling the SRAT which then puts it in the OS's court. > Enabling the SRAT doesn't need to and shouldn't disable Bank > Interleaving. Yes, I do indeed stand corrected. Writing emails late at night while tired is something I should probably cut down on. The S2882 I see most often is _not_ a 2.03 BIOS; the 2.03 BIOS refused to even POST with our RAID controller. (Predictably, Tyan's response was 'don't run that BIOS then.') Unfortunately, the S4882 hell is still quite fresh in my mind; the Phoenix 6.0 Ref on those is mutual exclusive. No joke; if SRAT is enabled, actual Bank Interleave is disabled. (The BIOS seems to consider Node/Bank as equal. Not like the S4882 doesn't have enough quirks anyways. :P) Coupled with the 'DDR 400MHz Memmory Detected' line, you can probably guess my opinion of Tyan's BIOS guys at this point. > Nor in the AMI reference BIOS :-(, which is a shame as more information > might better clear things up. Indeed; also better note-taking on my part, but those are on a dead machine right now. ;( > Actually the S2882 uses a AMI BIOS, as does all of Tyan's 2P Opteron > boards, except the S2885 variant Tyan makes for the Fujitsu Celsius V810. > I like the Fujitsu Celsius V810 Phoenix better, wished it was used on all > S2885's. Yeah, I thought they might have used Phoenix because I haven't seen the S2882 rebooted in a good long time. I'd take _anything_ over Tyan's BIOS; it has been nothing but trouble in various ways since day one. > How do you want to control the "memory hole"? It is mandatory in order > to map in memory mapped I/O devices. On the S4882, you have limited control over the PCI Memory Hole. You can set it to Auto, or to a specific size. Auto will size it based on enabled devices in the bios, setting it to a specific value will create a hole of that size. One of those way-too-fine-tuning things. > Correct, the "memory hole" must be below the 4GB mark. > http://www.amd.com/us-en/assets/content_type/DownloadableAssets/RichBrunnerClusterWorldpresFINAL.pdf > slide 25 is AMD's picture for this. The "hole" is of course an area > where memory mapped PCI I/O, APIC, APG GART, etc.. are mapped into the > memory address space. Thus RAM cannot be addressed using (mapped into) > those memory locations. Making me wish I had a way to view PDFs right now. Looking at the presented memory regions: Physical memory chuck(s): 0x0000000000001000 - 0000000000009bfff, 634880 bytes (155 pages) 0x000000000082d000 - 000000000fbfeffff, 4219219968 bytes (1030083 pages) 0x0000000100000000 - 000000003e1fcffff, 12381388800 bytes (3022800 pages) 1000-9bfff is the 640K region. Then a significant gap between 640K and the 4023MB region. Followed by another large gap between the 4023MB region and the 11807MB region. My hex conversion with numbers that large, frankly, sucks, but it looks to me as though the PCI hole is 512MB (e.g.; all onboard devices enabled,) and starting at 4024MB. Which would put the PCI Memory Hole past the 4GB limit. Only explanation for behavior like that, that I can think of, is yet another BIOS bug. -Ketrien I. Saihr-Kenchedra "And I'm going back to bed." From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 20:21:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DC2016A4D6 for ; Wed, 1 Dec 2004 20:21:10 +0000 (GMT) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47C9643D3F for ; Wed, 1 Dec 2004 20:21:09 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr2.xs4all.nl (8.12.11/8.12.11) with ESMTP id iB1KL7tN017692; Wed, 1 Dec 2004 21:21:08 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 8B4A06393; Wed, 1 Dec 2004 21:21:13 +0100 (CET) Date: Wed, 1 Dec 2004 21:21:13 +0100 From: Roland Smith To: James Earl Message-ID: <20041201202113.GA4940@slackbox.xs4all.nl> References: <20041201120130.B680C16A4E8@hub.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline In-Reply-To: <20041201120130.B680C16A4E8@hub.freebsd.org> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-amd64@freebsd.org Subject: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 20:21:10 -0000 --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Seen on the list digest: > Luckily returning my card was fairly painless. Now I just have to wait > a couple days to receive my ATI Radeon 9250. It ships out tomorrow, so > if there's any last words of advice/general info... please speak > now! :) My new AMD64 system is also equipped with a Radeon 9250 (sold under the Saphire brand). The 2D driver for Xorg works fine, the 5.3-RELEASE AGP and radeondrm drivers load OK, but running an OpenGL program fails with an error in radeon_cp_cmdbuf (from syslog): error: [drm:pid564:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 0x560008 I've been looking at the source, and IMHO (not a kernel guru) it might be a 64 bit issue. The radeon_cp_cmdbuf function contains a switch statement that evaluates an integer argument copied from user space via fuword(9), which returns a long value. Since long is 64 bits, and int is 32 bits on AMD64 this might cause trouble? For completeness, my system has an MSI Neo FSR motherboard with a KT8T800 chipset. Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrie5EnfvsMMhpyURAl+WAJ4tpcuKE62jnGkebnRwgU+tsuWpRACcCxst mBfo5AVkAveioGK4mLW3nuM= =vRxv -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 20:34:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB2F916A4CE; Wed, 1 Dec 2004 20:34:30 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4686C43D31; Wed, 1 Dec 2004 20:34:28 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iB1KYQQc060651; Wed, 1 Dec 2004 15:34:27 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Wed, 1 Dec 2004 15:34:25 -0500 User-Agent: KMail/1.6.2 References: <20041201120130.B680C16A4E8@hub.freebsd.org> <20041201202113.GA4940@slackbox.xs4all.nl> In-Reply-To: <20041201202113.GA4940@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200412011534.25235.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: Roland Smith cc: anholt@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 20:34:31 -0000 On Wednesday 01 December 2004 03:21 pm, Roland Smith wrote: > Seen on the list digest: > > Luckily returning my card was fairly painless. Now I just have > > to wait a couple days to receive my ATI Radeon 9250. It ships > > out tomorrow, so if there's any last words of advice/general > > info... please speak now! :) > > My new AMD64 system is also equipped with a Radeon 9250 (sold under > the Saphire brand). The 2D driver for Xorg works fine, the > 5.3-RELEASE AGP and radeondrm drivers load OK, but running an > OpenGL program fails with an error in radeon_cp_cmdbuf (from > syslog): > > error: [drm:pid564:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at > 0x560008 It is known problem for radeon DRI/DRM. > I've been looking at the source, and IMHO (not a kernel guru) it > might be a 64 bit issue. The radeon_cp_cmdbuf function contains a > switch statement that evaluates an integer argument copied from > user space via fuword(9), which returns a long value. Since long is > 64 bits, and int is 32 bits on AMD64 this might cause trouble? I believe that's not the only problem. (CC'ing anholt@) > For completeness, my system has an MSI Neo FSR motherboard with a > KT8T800 chipset. I have 9200 and MSI K8T Neo-FIS2R. Jung-uk Kim > Roland From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 21:04:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4B4D16A4CE; Wed, 1 Dec 2004 21:04:11 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7007943D55; Wed, 1 Dec 2004 21:04:11 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iB1L49YV061498; Wed, 1 Dec 2004 16:04:11 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Wed, 1 Dec 2004 16:04:08 -0500 User-Agent: KMail/1.6.2 References: <20041201120130.B680C16A4E8@hub.freebsd.org> <20041201202113.GA4940@slackbox.xs4all.nl> <200412011534.25235.jkim@niksun.com> In-Reply-To: <200412011534.25235.jkim@niksun.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200412011604.08805.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: Roland Smith cc: anholt@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:04:11 -0000 On Wednesday 01 December 2004 03:34 pm, Jung-uk Kim wrote: > On Wednesday 01 December 2004 03:21 pm, Roland Smith wrote: > > Seen on the list digest: > > > Luckily returning my card was fairly painless. Now I just have > > > to wait a couple days to receive my ATI Radeon 9250. It ships > > > out tomorrow, so if there's any last words of advice/general > > > info... please speak now! :) > > > > My new AMD64 system is also equipped with a Radeon 9250 (sold > > under the Saphire brand). The 2D driver for Xorg works fine, the > > 5.3-RELEASE AGP and radeondrm drivers load OK, but running an > > OpenGL program fails with an error in radeon_cp_cmdbuf (from > > syslog): > > > > error: [drm:pid564:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at > > 0x560008 > > It is known problem for radeon DRI/DRM. > > > I've been looking at the source, and IMHO (not a kernel guru) it > > might be a 64 bit issue. The radeon_cp_cmdbuf function contains a > > switch statement that evaluates an integer argument copied from > > user space via fuword(9), which returns a long value. Since long > > is 64 bits, and int is 32 bits on AMD64 this might cause trouble? > > I believe that's not the only problem. (CC'ing anholt@) Wait! I changed fuword/suword to fuword32/suword32 and it works now! Man, I am stupid. Thanks! Jung-uk Kim > > For completeness, my system has an MSI Neo FSR motherboard with a > > KT8T800 chipset. > > I have 9200 and MSI K8T Neo-FIS2R. > > Jung-uk Kim > > > Roland From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 21:07:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9863516A4CE for ; Wed, 1 Dec 2004 21:07:26 +0000 (GMT) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 260C143D3F for ; Wed, 1 Dec 2004 21:07:26 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-181-47.abhsia.telus.net ([137.186.181.47]) by priv-edtnes46.telusplanet.netESMTP <20041201210725.YGHN3559.priv-edtnes46.telusplanet.net@d137-186-181-47.abhsia.telus.net>; Wed, 1 Dec 2004 14:07:25 -0700 From: James Earl To: Jung-uk Kim In-Reply-To: <200412011534.25235.jkim@niksun.com> References: <20041201120130.B680C16A4E8@hub.freebsd.org> <20041201202113.GA4940@slackbox.xs4all.nl> <200412011534.25235.jkim@niksun.com> Content-Type: text/plain Date: Thu, 02 Dec 2004 14:07:56 -0700 Message-Id: <1102021676.97315.5.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:07:26 -0000 On Wed, 2004-12-01 at 15:34 -0500, Jung-uk Kim wrote: > On Wednesday 01 December 2004 03:21 pm, Roland Smith wrote: > > Seen on the list digest: > > > Luckily returning my card was fairly painless. Now I just have > > > to wait a couple days to receive my ATI Radeon 9250. It ships > > > out tomorrow, so if there's any last words of advice/general > > > info... please speak now! :) > > > > My new AMD64 system is also equipped with a Radeon 9250 (sold under > > the Saphire brand). The 2D driver for Xorg works fine, the > > 5.3-RELEASE AGP and radeondrm drivers load OK, but running an > > OpenGL program fails with an error in radeon_cp_cmdbuf (from > > syslog): > > > > error: [drm:pid564:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at > > 0x560008 > > It is known problem for radeon DRI/DRM. > > > I've been looking at the source, and IMHO (not a kernel guru) it > > might be a 64 bit issue. The radeon_cp_cmdbuf function contains a > > switch statement that evaluates an integer argument copied from > > user space via fuword(9), which returns a long value. Since long is > > 64 bits, and int is 32 bits on AMD64 this might cause trouble? > > I believe that's not the only problem. (CC'ing anholt@) > > > For completeness, my system has an MSI Neo FSR motherboard with a > > KT8T800 chipset. > > I have 9200 and MSI K8T Neo-FIS2R. Even though the radeon manpage doesn't list the 9250 (6.7.0), I was assuming the 9250 is basically the same as a 9200. Is this true? Does your 9200 exhibit the same problems as Roland Smith describes? > > Jung-uk Kim > > > Roland From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 21:21:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FBA316A4CE; Wed, 1 Dec 2004 21:21:12 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D00543D55; Wed, 1 Dec 2004 21:21:12 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iB1LLAON061981; Wed, 1 Dec 2004 16:21:11 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: James Earl Date: Wed, 1 Dec 2004 16:21:10 -0500 User-Agent: KMail/1.6.2 References: <20041201120130.B680C16A4E8@hub.freebsd.org> <200412011534.25235.jkim@niksun.com> <1102021676.97315.5.camel@serious.ab.hsia.telus.net> In-Reply-To: <1102021676.97315.5.camel@serious.ab.hsia.telus.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_GXjrBEUL25trHht" Message-Id: <200412011621.10090.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean cc: anholt@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:21:12 -0000 --Boundary-00=_GXjrBEUL25trHht Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thursday 02 December 2004 04:07 pm, James Earl wrote: > Even though the radeon manpage doesn't list the 9250 (6.7.0), I was > assuming the 9250 is basically the same as a 9200. Is this true? Yes. > Does your 9200 exhibit the same problems as Roland Smith describes? Fixed now and patch attached. BTW, I am using Xorg 6.8.0. Jung-uk Kim --Boundary-00=_GXjrBEUL25trHht Content-Type: text/plain; charset="euc-kr"; name="drm64.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="drm64.diff" --- src/sys/dev/drm/drm_os_freebsd.h.orig Wed Dec 1 16:16:40 2004 +++ src/sys/dev/drm/drm_os_freebsd.h Wed Dec 1 15:59:19 2004 @@ -275,9 +275,9 @@ #define DRM_COPY_TO_USER_UNCHECKED(arg1, arg2, arg3) \ copyout(arg2, arg1, arg3) #define DRM_GET_USER_UNCHECKED(val, uaddr) \ - ((val) = fuword(uaddr), 0) + ((val) = fuword32(uaddr), 0) #define DRM_PUT_USER_UNCHECKED(uaddr, val) \ - suword(uaddr, val) + suword32(uaddr, val) /* DRM_READMEMORYBARRIER() prevents reordering of reads. * DRM_WRITEMEMORYBARRIER() prevents reordering of writes. --Boundary-00=_GXjrBEUL25trHht-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 21:38:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56A8F16A4CE for ; Wed, 1 Dec 2004 21:38:56 +0000 (GMT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id F098B43D39 for ; Wed, 1 Dec 2004 21:38:55 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-191-7.abhsia.telus.net ([137.186.191.7]) by priv-edtnes28.telusplanet.netESMTP <20041201213855.NJDT8955.priv-edtnes28.telusplanet.net@d137-186-191-7.abhsia.telus.net>; Wed, 1 Dec 2004 14:38:55 -0700 From: James Earl To: Jung-uk Kim In-Reply-To: <200412011621.10090.jkim@niksun.com> References: <20041201120130.B680C16A4E8@hub.freebsd.org> <200412011534.25235.jkim@niksun.com> <1102021676.97315.5.camel@serious.ab.hsia.telus.net> <200412011621.10090.jkim@niksun.com> Content-Type: text/plain Date: Thu, 02 Dec 2004 14:39:27 -0700 Message-Id: <1102023567.6015.7.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:38:56 -0000 On Wed, 2004-12-01 at 16:21 -0500, Jung-uk Kim wrote: > On Thursday 02 December 2004 04:07 pm, James Earl wrote: > > Even though the radeon manpage doesn't list the 9250 (6.7.0), I was > > assuming the 9250 is basically the same as a 9200. Is this true? > > Yes. > > > Does your 9200 exhibit the same problems as Roland Smith describes? > > Fixed now and patch attached. BTW, I am using Xorg 6.8.0. Thanks! As soon as I receive my new card I'll give it a try. > > Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 1 22:37:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EA3616A4CE; Wed, 1 Dec 2004 22:37:11 +0000 (GMT) Received: from www1.brozs.net (www1.brozs.net [195.154.177.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D1E843D4C; Wed, 1 Dec 2004 22:37:06 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from localhost (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id 66A8943ED; Wed, 1 Dec 2004 23:35:31 +0100 (CET) Received: from www1.brozs.net ([127.0.0.1]) by localhost (www1.brozs.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00570-02; Wed, 1 Dec 2004 23:35:31 +0100 (CET) Received: from [192.168.10.100] (unknown [192.168.10.100]) by www1.brozs.net (Postfix) with ESMTP id 0C0D143E8; Wed, 1 Dec 2004 23:35:31 +0100 (CET) Message-ID: <41AE4792.8050807@brozs.net> Date: Wed, 01 Dec 2004 23:37:06 +0100 From: Thomas Fagart User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <20041201120130.B680C16A4E8@hub.freebsd.org> <200412011534.25235.jkim@niksun.com> <1102021676.97315.5.camel@serious.ab.hsia.telus.net> <200412011621.10090.jkim@niksun.com> In-Reply-To: <200412011621.10090.jkim@niksun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at brozs.net cc: anholt@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 22:37:11 -0000 Jung-uk Kim wrote: >On Thursday 02 December 2004 04:07 pm, James Earl wrote: > > >>Even though the radeon manpage doesn't list the 9250 (6.7.0), I was >>assuming the 9250 is basically the same as a 9200. Is this true? >> >> > >Yes. > > > >>Does your 9200 exhibit the same problems as Roland Smith describes? >> >> > >Fixed now and patch attached. BTW, I am using Xorg 6.8.0. > > This is working great for me with RV100 Radeon 7000 / Radeon VE and Xorg 6.7.0 Thanks >Jung-uk Kim > > >------------------------------------------------------------------------ > >--- src/sys/dev/drm/drm_os_freebsd.h.orig Wed Dec 1 16:16:40 2004 >+++ src/sys/dev/drm/drm_os_freebsd.h Wed Dec 1 15:59:19 2004 >@@ -275,9 +275,9 @@ > #define DRM_COPY_TO_USER_UNCHECKED(arg1, arg2, arg3) \ > copyout(arg2, arg1, arg3) > #define DRM_GET_USER_UNCHECKED(val, uaddr) \ >- ((val) = fuword(uaddr), 0) >+ ((val) = fuword32(uaddr), 0) > #define DRM_PUT_USER_UNCHECKED(uaddr, val) \ >- suword(uaddr, val) >+ suword32(uaddr, val) > > /* DRM_READMEMORYBARRIER() prevents reordering of reads. > * DRM_WRITEMEMORYBARRIER() prevents reordering of writes. > > >------------------------------------------------------------------------ > >_______________________________________________ >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" > > Thomas From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 08:20:30 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C2B516A4D0 for ; Thu, 2 Dec 2004 08:20:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AA5443D53 for ; Thu, 2 Dec 2004 08:20:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB28KSeQ032642 for ; Thu, 2 Dec 2004 08:20:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB28KSjN032641; Thu, 2 Dec 2004 08:20:28 GMT (envelope-from gnats) Resent-Date: Thu, 2 Dec 2004 08:20:28 GMT Resent-Message-Id: <200412020820.iB28KSjN032641@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, wkwu.amd64@csie.nctu.edu.tw Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C621C16A4CE for ; Thu, 2 Dec 2004 08:18:01 +0000 (GMT) Received: from mailgate.csie.nctu.edu.tw (mailgate.csie.nctu.edu.tw [140.113.209.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id F406A43D49 for ; Thu, 2 Dec 2004 08:17:58 +0000 (GMT) (envelope-from wkwu@csie.nctu.edu.tw) Received: from mailgate.csie.nctu.edu.tw (wkwu@localhost [127.0.0.1]) iB28HxOk038815 for ; Thu, 2 Dec 2004 16:17:59 +0800 (CST) Received: (from wkwu@localhost) by mailgate.csie.nctu.edu.tw (8.13.1/8.13.1/Submit) id iB28HxZP038814; Thu, 2 Dec 2004 16:17:59 +0800 (CST) Message-Id: <200412020817.iB28HxZP038814@mailgate.csie.nctu.edu.tw> Date: Thu, 2 Dec 2004 16:17:59 +0800 (CST) From: wkwu.amd64@csie.nctu.edu.tw To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/74608: mpt hangs 5 minutes when booting X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: wkwu.amd64@csie.nctu.edu.tw List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:20:30 -0000 >Number: 74608 >Category: amd64 >Synopsis: mpt hangs 5 minutes when booting >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Dec 02 08:20:28 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Wei-Kai Wu >Release: FreeBSD 5.3-STABLE amd64 >Organization: Kavalan >Environment: LSILogic 1030 SCSI controller with amd64 box >Description: The booting process hangs about 5 minutes on mpt driver. If I turn the LSILogic 1030 SCSI controller off in the BIOS , it boots quickly. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 08:46:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D08616A4CE for ; Thu, 2 Dec 2004 08:46:52 +0000 (GMT) Received: from mx.sat.corp.rackspace.com (mx.sat.corp.rackspace.com [64.39.1.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDF1643D5E for ; Thu, 2 Dec 2004 08:46:51 +0000 (GMT) (envelope-from freebsd@oranged.to) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) iB28kx0I014658 for ; Thu, 2 Dec 2004 02:46:59 -0600 Received: from [10.2.101.93] (nat55.lon.rackspace.com [212.100.225.55]) (authenticated bits=0) by mail.rackspace.com (8.12.10/8.12.10) with ESMTP id iB28kXd6000660 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Thu, 2 Dec 2004 02:46:47 -0600 Message-ID: <41AED65C.1070301@oranged.to> Date: Thu, 02 Dec 2004 08:46:20 +0000 From: Jimmy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Rackspace-RTS-MailScanner-Information: Please contact the ISP for more information X-MailScanner: WVtbaj07: Found to be clean X-MailScanner-From: freebsd@oranged.to Subject: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:46:52 -0000 Hello, I am currently investigating implementing a solution based around FreeBSD. I have some questions that relate specifically to the AMD-64 port of FreeBSD that I was hoping could be answered easily. I am interested to know how well the FreeBSD 5.3+ system handles the AMD 64 processors in a dual proc configuration. The project that we are working on currently requires large amounts of RAM (16gb). Because of this we are looking down the AMD road using a dual opteron configuration. Is this something that we should look at or should we investigate single processor configurations and distribute the load more evenly between more lower end systems? So in the end my questions are : a) how reliable is the AMD 64 port of FreeBSD b) how good is the multiprocessing AMD 64? c) any advice would be seriously great to have. Thanks in advance James From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 09:39:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0E1916A4CE; Thu, 2 Dec 2004 09:39:07 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A630A43D1D; Thu, 2 Dec 2004 09:39:07 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB29d5Tb020600; Thu, 2 Dec 2004 01:39:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB29d3ax020599; Thu, 2 Dec 2004 01:39:03 -0800 (PST) (envelope-from obrien) Date: Thu, 2 Dec 2004 01:39:03 -0800 From: "David O'Brien" To: Jung-uk Kim Message-ID: <20041202093903.GA17607@dragon.nuxi.com> References: <20041201120130.B680C16A4E8@hub.freebsd.org> <200412011534.25235.jkim@niksun.com> <1102021676.97315.5.camel@serious.ab.hsia.telus.net> <200412011621.10090.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412011621.10090.jkim@niksun.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: anholt@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 09:39:07 -0000 On Wed, Dec 01, 2004 at 04:21:10PM -0500, Jung-uk Kim wrote: > > Does your 9200 exhibit the same problems as Roland Smith describes? > > Fixed now and patch attached. BTW, I am using Xorg 6.8.0. Hi Jung-uk Kim, Committed. Thanks!! -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 17:02:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D24EE16A4CE for ; Thu, 2 Dec 2004 17:02:55 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id D66A843D49 for ; Thu, 2 Dec 2004 17:02:53 +0000 (GMT) (envelope-from mind@doctor.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])4DFC418002A4 for ; Thu, 2 Dec 2004 17:02:50 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 2 Dec 2004 17:02:47 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id 3CFE7790094; Thu, 2 Dec 2004 17:02:46 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [213.59.125.30] by ws1-14.us4.outblaze.com with http for mind@doctor.com; Thu, 02 Dec 2004 12:02:46 -0500 From: "Egor Dmitrenkov" To: freebsd-amd64@freebsd.org Date: Thu, 02 Dec 2004 12:02:46 -0500 X-Originating-Ip: 213.59.125.30 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20041202170246.3CFE7790094@ws1-14.us4.outblaze.com> Subject: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 17:02:55 -0000 Well, I tried to compile GENERIC kernel for my Athlon64 and result was: What should I do? Help plz... -------------------- # cd /usr/src/sys/amd64/conf/ # config GENERIC Kernel build directory is ../compile/GENERIC Don't forget to do a ``make depend'' # cd ../compile/GENERIC # make depend rm -f .olddep if [ -f .depend ]; then mv .depend .olddep; fi make _kernel-depend cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes= -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensi= ons -std=3Dc99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -= I../../../contrib/altq-I../../../contrib/ipfilter -I../../../contrib/pf -I.= ./../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contr= ib/ngatm -D_KERNEL -include opt_global.h -finline-limit=3D8000 --param inli= ne-unit-growth=3D100 --param large-function-growth=3D1000 -mno-align-long-s= trings -mpreferred-stack-boundary=3D2 -ffreestanding ../../../i386/i386/gen= assym.c ../../../i386/i386/genassym.c:38:22: opt_apic.h: No such file or directory In file included from ../../../sys/types.h:44, from ../../../sys/param.h:61, from ../../../i386/i386/genassym.c:42: ./machine/endian.h: In function `__bswap64': ./machine/endian.h:126: warning: right shift count >=3D width of type ./machine/endian.h:126: warning: right shift count >=3D width of type ./machine/endian.h:126: warning: left shift count >=3D width of type ./machine/endian.h:126: warning: left shift count >=3D width of type ./machine/endian.h:126: warning: left shift count >=3D width of type ./machine/endian.h:126: warning: left shift count >=3D width of type ./machine/endian.h:126: warning: left shift count >=3D width of type In file included from ../../../sys/param.h:92, from ../../../i386/i386/genassym.c:42: ../../../sys/time.h: In function `bintime2timespec': ../../../sys/time.h:112: warning: right shift count >=3D width of type ../../../sys/time.h:112: warning: right shift count >=3D width of type ../../../sys/time.h: In function `bintime2timeval': ../../../sys/time.h:129: warning: right shift count >=3D width of type ../../../sys/time.h:129: warning: right shift count >=3D width of type In file included from ../../../sys/systm.h:42, from ../../../i386/i386/genassym.c:43: ./machine/cpufunc.h: In function `rdmsr': ./machine/cpufunc.h:349: warning: left shift count >=3D width of type ./machine/cpufunc.h: In function `rdpmc': ./machine/cpufunc.h:358: warning: left shift count >=3D width of type ./machine/cpufunc.h: In function `rdtsc': ./machine/cpufunc.h:367: warning: left shift count >=3D width of type ./machine/cpufunc.h: In function `wrmsr': ./machine/cpufunc.h:388: warning: right shift count >=3D width of type In file included from ../../../sys/proc.h:59, from ../../../sys/buf.h:263, from ../../../i386/i386/genassym.c:46: ../../../sys/ucontext.h: At top level: ../../../sys/ucontext.h:60: error: field `uc_mcontext' has incomplete type In file included from ./machine/cpu.h:43, from ../../../i386/i386/genassym.c:73: ./machine/frame.h:97: error: width of `' exceeds its type ./machine/frame.h:98: error: width of `' exceeds its type ./machine/frame.h:99: error: width of `' exceeds its type ./machine/frame.h:100: error: width of `' exceeds its type ./machine/frame.h:127: error: width of `' exceeds its type ./machine/frame.h:128: error: width of `' exceeds its type ./machine/frame.h:129: error: width of `' exceeds its type ./machine/frame.h:130: error: width of `' exceeds its type In file included from ./machine/cpu.h:44, from ../../../i386/i386/genassym.c:73: ./machine/segments.h:89: error: width of `sd_hibase' exceeds its type ./machine/segments.h:107: error: width of `gd_hioffset' exceeds its type ./machine/segments.h:160: error: width of `rd_base' exceeds its type ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:90: error: structure has no member named `md_= ldt' ../../../i386/i386/genassym.c:104: error: `NPDEPTD' undeclared here (not in= a function) ../../../i386/i386/genassym.c:105: error: `NPGPTD' undeclared here (not in = a function) ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:114: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:115: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:116: warning: left shift count >=3D width of = type ../../../i386/i386/genassym.c:117: error: `KERNLOAD' undeclared here (not i= n a function) ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:120: error: structure has no member named `pc= b_edi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:121: error: structure has no member named `pc= b_esi' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:122: error: structure has no member named `pc= b_ebp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:123: error: structure has no member named `pc= b_esp' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:124: error: structure has no member named `pc= b_ebx' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:125: error: structure has no member named `pc= b_eip' ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:126: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:135: error: structure has no member named `pc= b_psl' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:137: error: structure has no member named `pc= b_ext' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:139: error: structure has no member named `__= pcb_spare' ../../../i386/i386/genassym.c:142: error: `savefpu' defined as wrong kind o= f tag ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' t= o incomplete type `savefpu' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:144: error: structure has no member named `pc= b_switchout' ../../../i386/i386/genassym.c:147: error: `PCB_VM86CALL' undeclared here (n= ot in a function) ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:151: error: structure has no member named `tf= _eip' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:153: error: structure has no member named `tf= _eflags' ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:160: error: dereferencing pointer to incomple= te type ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:172: error: structure has no member named `mc= _eflags' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:173: error: structure has no member named `mc= _gs' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:195: error: structure has no member named `pc= _common_tss' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:196: error: structure has no member named `pc= _common_tssd' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:197: error: structure has no member named `pc= _tss_gdt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:198: error: structure has no member named `pc= _currentldt' ../../../i386/i386/genassym.c:214: error: `GPRIV_SEL' undeclared here (not = in a function) ../../../i386/i386/genassym.c:216: error: `GBIOSCODE32_SEL' undeclared here= (not in a function) ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTsign' isn't= known ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw0' isn't k= nown ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw1' isn't k= nown ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw2' isn't k= nown ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw3' isn't k= nown ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDsign' isn= 't known ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw0' isn't= known ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw1' isn't= known ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw2' isn't= known ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw3' isn't= known ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDsign' isn'= t known ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw0' isn't = known ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw1' isn't = known ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw2' isn't = known ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw3' isn't = known ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADsign' is= n't known ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw0' isn'= t known ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw1' isn'= t known ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw2' isn'= t known ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw3' isn'= t known ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIsign' isn= 't known ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw0' isn't= known ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw1' isn't= known ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw2' isn't= known ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw3' isn't= known ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIsign' isn= 't known ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw0' isn't= known ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw1' isn't= known ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw2' isn't= known ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw3' isn't= known ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPsign' isn= 't known ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw0' isn't= known ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw1' isn't= known ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw2' isn't= known ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw3' isn't= known ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPsign' isn= 't known ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw0' isn't= known ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw1' isn't= known ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw2' isn't= known ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw3' isn't= known ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXsign' isn= 't known ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw0' isn't= known ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw1' isn't= known ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw2' isn't= known ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw3' isn't= known ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPsign' isn= 't known ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw0' isn't= known ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw1' isn't= known ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw2' isn't= known ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw3' isn't= known ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0sign' is= n't known ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w0' isn'= t known ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w1' isn'= t known ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w2' isn'= t known ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w3' isn'= t known ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLsign' isn= 't known ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw0' isn't= known ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw1' isn't= known ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw2' isn't= known ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw3' isn't= known ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTsign' isn= 't known ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw0' isn't= known ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw1' isn't= known ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw2' isn't= known ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw3' isn't= known ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREsign' i= sn't known ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw0' isn= 't known ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw1' isn= 't known ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw2' isn= 't known ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw3' isn= 't known ../../../i386/i386/genassym.c:144: error: storage size of `PCB_SWITCHOUTsig= n' isn't known ../../../i386/i386/genassym.c:144: error: storage size of `PCB_SWITCHOUTw0'= isn't known ../../../i386/i386/genassym.c:144: error: storage size of `PCB_SWITCHOUTw1'= isn't known ../../../i386/i386/genassym.c:144: error: storage size of `PCB_SWITCHOUTw2'= isn't known ../../../i386/i386/genassym.c:144: error: storage size of `PCB_SWITCHOUTw3'= isn't known ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLsign= ' isn't known ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw0' = isn't known ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw1' = isn't known ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw2' = isn't known ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw3' = isn't known ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPsign' isn'= t known ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw0' isn't = known ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw1' isn't = known ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw2' isn't = known ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw3' isn't = known ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSsign' i= sn't known ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw0' isn= 't known ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw1' isn= 't known ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw2' isn= 't known ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw3' isn= 't known ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4sign' is= n't known ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w0' isn'= t known ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w1' isn'= t known ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w2' isn'= t known ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w3' isn'= t known ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSsign' = isn't known ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw0' is= n't known ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw1' is= n't known ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw2' is= n't known ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw3' is= n't known ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSsign' isn'= t known ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw0' isn't = known ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw1' isn't = known ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw2' isn't = known ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw3' isn't = known ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSsign' i= sn't known ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw0' isn= 't known ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw1' isn= 't known ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw2' isn= 't known ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw3' isn= 't known ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSsign' isn't= known ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw0' isn't k= nown ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw1' isn't k= nown ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw2' isn't k= nown ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw3' isn't k= nown ../../../i386/i386/genassym.c:195: error: storage size of `PC_COMMON_TSSsig= n' isn't known ../../../i386/i386/genassym.c:195: error: storage size of `PC_COMMON_TSSw0'= isn't known ../../../i386/i386/genassym.c:195: error: storage size of `PC_COMMON_TSSw1'= isn't known ../../../i386/i386/genassym.c:195: error: storage size of `PC_COMMON_TSSw2'= isn't known ../../../i386/i386/genassym.c:195: error: storage size of `PC_COMMON_TSSw3'= isn't known ../../../i386/i386/genassym.c:196: error: storage size of `PC_COMMON_TSSDsi= gn' isn't known ../../../i386/i386/genassym.c:196: error: storage size of `PC_COMMON_TSSDw0= ' isn't known ../../../i386/i386/genassym.c:196: error: storage size of `PC_COMMON_TSSDw1= ' isn't known ../../../i386/i386/genassym.c:196: error: storage size of `PC_COMMON_TSSDw2= ' isn't known ../../../i386/i386/genassym.c:196: error: storage size of `PC_COMMON_TSSDw3= ' isn't known ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTsign' = isn't known ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw0' is= n't known ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw1' is= n't known ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw2' is= n't known ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw3' is= n't known ../../../i386/i386/genassym.c:198: error: storage size of `PC_CURRENTLDTsig= n' isn't known ../../../i386/i386/genassym.c:198: error: storage size of `PC_CURRENTLDTw0'= isn't known ../../../i386/i386/genassym.c:198: error: storage size of `PC_CURRENTLDTw1'= isn't known ../../../i386/i386/genassym.c:198: error: storage size of `PC_CURRENTLDTw2'= isn't known ../../../i386/i386/genassym.c:198: error: storage size of `PC_CURRENTLDTw3'= isn't known ../../../i386/i386/genassym.c:214: error: storage size of `KPSELsign' isn't= known ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw0' isn't k= nown ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw1' isn't k= nown ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw2' isn't k= nown ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw3' isn't k= nown ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELsign' isn= 't known ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw0' isn't= known ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw1' isn't= known ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw2' isn't= known ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw3' isn't= known *** Error code 1 Stop in /usr/src/sys/amd64/compile/GENERIC. *** Error code 1 Stop in /usr/src/sys/amd64/compile/GENERIC. #=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 17:56:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45F6416A4CE for ; Thu, 2 Dec 2004 17:56:22 +0000 (GMT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE62043D3F for ; Thu, 2 Dec 2004 17:56:21 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d209-107-108-173.abhsia.telus.net ([209.107.108.173]) by priv-edtnes28.telusplanet.netESMTP <20041202175617.GNNB26658.priv-edtnes28.telusplanet.net@d209-107-108-173.abhsia.telus.net>; Thu, 2 Dec 2004 10:56:17 -0700 From: James Earl To: Jung-uk Kim In-Reply-To: <200412011621.10090.jkim@niksun.com> References: <20041201120130.B680C16A4E8@hub.freebsd.org> <200412011534.25235.jkim@niksun.com> <1102021676.97315.5.camel@serious.ab.hsia.telus.net> <200412011621.10090.jkim@niksun.com> Content-Type: text/plain Date: Fri, 03 Dec 2004 10:56:44 -0700 Message-Id: <1102096604.512.14.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Radeon 9250 (was Re: Matrox G550) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 17:56:22 -0000 On Wed, 2004-12-01 at 16:21 -0500, Jung-uk Kim wrote: > On Thursday 02 December 2004 04:07 pm, James Earl wrote: > > Even though the radeon manpage doesn't list the 9250 (6.7.0), I was > > assuming the 9250 is basically the same as a 9200. Is this true? > > Yes. > > > Does your 9200 exhibit the same problems as Roland Smith describes? > > Fixed now and patch attached. BTW, I am using Xorg 6.8.0. I received my Radeon 9250 and applied your patch. No problems there. But, for some reason glxinfo is reporting: "direct rendering: No". Looking through /var/log/Xorg.0.log see I'm getting some drmOpenDevice errors and another earlier message to the tune of "(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found". http://www.icionline.ca/james/Xorg.0.log Any clues? James > > Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 18:01:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34ACC16A4CF for ; Thu, 2 Dec 2004 18:01:24 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFEF543D3F for ; Thu, 2 Dec 2004 18:01:23 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB2I1N4e012849; Thu, 2 Dec 2004 10:01:23 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB2I1NI5012848; Thu, 2 Dec 2004 10:01:23 -0800 (PST) (envelope-from sgk) Date: Thu, 2 Dec 2004 10:01:23 -0800 From: Steve Kargl To: Jimmy Message-ID: <20041202180123.GA12734@troutmask.apl.washington.edu> References: <41AED65C.1070301@oranged.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AED65C.1070301@oranged.to> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:01:24 -0000 On Thu, Dec 02, 2004 at 08:46:20AM +0000, Jimmy wrote: > > I am interested to know how well the FreeBSD 5.3+ system handles the AMD > 64 processors in a dual proc configuration. The project that we are > working on currently requires large amounts of RAM (16gb). Because of > this we are looking down the AMD road using a dual opteron configuration. FreeBSD/amd64 works well on a dual opteron Tyan K8S Pro system with less than 8 GB of memory. It does not boot if you have more than 8 GB. See the FreeBSD-amd64 list over the last week or 2 for detailed emails continaing the panic messages. > a) how reliable is the AMD 64 port of FreeBSD > b) how good is the multiprocessing AMD 64? > c) any advice would be seriously great to have. If you need 16GB (which I do), I suggest that you avoid FreeBSD/amd64 on the Tyan K8S Pro motherboard. I have experience with other motherboards, so YMMV. As a side note, NetBSD/amd64's installation cdrom boots and finds the 16 GB of memory on my system. I'll be installing NetBSD later today to see how it performs. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 18:25:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55B7616A4CE for ; Thu, 2 Dec 2004 18:25:04 +0000 (GMT) Received: from np.k12.mn.us (np.k12.mn.us [206.146.85.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D6F43D62 for ; Thu, 2 Dec 2004 18:25:03 +0000 (GMT) (envelope-from nmeverde@np.k12.mn.us) Received: from localhost (localhost [127.0.0.1]) by np.k12.mn.us (Postfix) with ESMTP id ED3B5240A7B for ; Thu, 2 Dec 2004 12:34:06 -0600 (CST) Received: from mail.np.k12.mn.us (localhost [127.0.0.1]) by np.k12.mn.us (Postfix) with ESMTP id 107E0240A27 for ; Thu, 2 Dec 2004 12:34:05 -0600 (CST) Received: from 206.146.85.21 (SquirrelMail authenticated user nmeverde); by mail.np.k12.mn.us with HTTP; Thu, 2 Dec 2004 12:34:05 -0600 (CST) Message-ID: <60106.206.146.85.21.1102012445.squirrel@206.146.85.21> In-Reply-To: <20041202170246.3CFE7790094@ws1-14.us4.outblaze.com> References: <20041202170246.3CFE7790094@ws1-14.us4.outblaze.com> Date: Thu, 2 Dec 2004 12:34:05 -0600 (CST) From: nmeverde@np.k12.mn.us To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.4 [CVS] X-Mailer: SquirrelMail/1.4.4 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by AMaViS 0.3.12 Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:25:04 -0000 > Well, I tried to compile GENERIC kernel for my Athlon64 and result was: > What should I do? Help plz... > > -------------------- > > # cd /usr/src/sys/amd64/conf/ > # config GENERIC > Kernel build directory is ../compile/GENERIC > Don't forget to do a ``make depend'' > # cd ../compile/GENERIC > # make depend > rm -f .olddep > if [ -f .depend ]; then mv .depend .olddep; fi > make _kernel-depend > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > -I../../../contrib/dev/acpica > -I../../../contrib/altq-I../../../contrib/ipfilter -I../../../contrib/pf > -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd > -I../../../contrib/ngatm -D_KERNEL -include opt_global.h > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mno-align-long-strings > -mpreferred-stack-boundary=2 -ffreestanding ../../../i386/i386/genassym.c > ../../../i386/i386/genassym.c:38:22: opt_apic.h: No such file or directory > In file included from ../../../sys/types.h:44, > from ../../../sys/param.h:61, > from ../../../i386/i386/genassym.c:42: > ./machine/endian.h: In function `__bswap64': > ./machine/endian.h:126: warning: right shift count >= width of type > ./machine/endian.h:126: warning: right shift count >= width of type > ./machine/endian.h:126: warning: left shift count >= width of type > ./machine/endian.h:126: warning: left shift count >= width of type > ./machine/endian.h:126: warning: left shift count >= width of type > ./machine/endian.h:126: warning: left shift count >= width of type > ./machine/endian.h:126: warning: left shift count >= width of type > In file included from ../../../sys/param.h:92, > from ../../../i386/i386/genassym.c:42: > ../../../sys/time.h: In function `bintime2timespec': > ../../../sys/time.h:112: warning: right shift count >= width of type > ../../../sys/time.h:112: warning: right shift count >= width of type > ../../../sys/time.h: In function `bintime2timeval': > ../../../sys/time.h:129: warning: right shift count >= width of type > ../../../sys/time.h:129: warning: right shift count >= width of type > In file included from ../../../sys/systm.h:42, > from ../../../i386/i386/genassym.c:43: > ./machine/cpufunc.h: In function `rdmsr': > ./machine/cpufunc.h:349: warning: left shift count >= width of type > ./machine/cpufunc.h: In function `rdpmc': > ./machine/cpufunc.h:358: warning: left shift count >= width of type > ./machine/cpufunc.h: In function `rdtsc': > ./machine/cpufunc.h:367: warning: left shift count >= width of type > ./machine/cpufunc.h: In function `wrmsr': > ./machine/cpufunc.h:388: warning: right shift count >= width of type > In file included from ../../../sys/proc.h:59, > from ../../../sys/buf.h:263, > from ../../../i386/i386/genassym.c:46: > ../../../sys/ucontext.h: At top level: > ../../../sys/ucontext.h:60: error: field `uc_mcontext' has incomplete type > In file included from ./machine/cpu.h:43, > from ../../../i386/i386/genassym.c:73: > ./machine/frame.h:97: error: width of `' exceeds its type > ./machine/frame.h:98: error: width of `' exceeds its type > ./machine/frame.h:99: error: width of `' exceeds its type > ./machine/frame.h:100: error: width of `' exceeds its type > ./machine/frame.h:127: error: width of `' exceeds its type > ./machine/frame.h:128: error: width of `' exceeds its type > ./machine/frame.h:129: error: width of `' exceeds its type > ./machine/frame.h:130: error: width of `' exceeds its type > In file included from ./machine/cpu.h:44, > from ../../../i386/i386/genassym.c:73: > ./machine/segments.h:89: error: width of `sd_hibase' exceeds its type > ./machine/segments.h:107: error: width of `gd_hioffset' exceeds its type > ./machine/segments.h:160: error: width of `rd_base' exceeds its type > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:90: error: structure has no member named > `md_ldt' > ../../../i386/i386/genassym.c:104: error: `NPDEPTD' undeclared here (not > in a function) > ../../../i386/i386/genassym.c:105: error: `NPGPTD' undeclared here (not in > a function) > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:114: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:115: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:116: warning: left shift count >= width of > type > ../../../i386/i386/genassym.c:117: error: `KERNLOAD' undeclared here (not > in a function) > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:120: error: structure has no member named > `pcb_edi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:121: error: structure has no member named > `pcb_esi' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:122: error: structure has no member named > `pcb_ebp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:123: error: structure has no member named > `pcb_esp' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:124: error: structure has no member named > `pcb_ebx' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:125: error: structure has no member named > `pcb_eip' > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:126: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:135: error: structure has no member named > `pcb_psl' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:137: error: structure has no member named > `pcb_ext' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:139: error: structure has no member named > `__pcb_spare' > ../../../i386/i386/genassym.c:142: error: `savefpu' defined as wrong kind > of tag > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:142: error: invalid application of `sizeof' > to incomplete type `savefpu' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:144: error: structure has no member named > `pcb_switchout' > ../../../i386/i386/genassym.c:147: error: `PCB_VM86CALL' undeclared here > (not in a function) > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:151: error: structure has no member named > `tf_eip' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:153: error: structure has no member named > `tf_eflags' > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:160: error: dereferencing pointer to > incomplete type > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:172: error: structure has no member named > `mc_eflags' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:173: error: structure has no member named > `mc_gs' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:195: error: structure has no member named > `pc_common_tss' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:196: error: structure has no member named > `pc_common_tssd' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:197: error: structure has no member named > `pc_tss_gdt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:198: error: structure has no member named > `pc_currentldt' > ../../../i386/i386/genassym.c:214: error: `GPRIV_SEL' undeclared here (not > in a function) > ../../../i386/i386/genassym.c:216: error: `GBIOSCODE32_SEL' undeclared > here (not in a function) > ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTsign' > isn't known > ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw0' isn't > known > ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw1' isn't > known > ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw2' isn't > known > ../../../i386/i386/genassym.c:90: error: storage size of `MD_LDTw3' isn't > known > ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDsign' > isn't known > ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw0' > isn't known > ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw1' > isn't known > ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw2' > isn't known > ../../../i386/i386/genassym.c:104: error: storage size of `NPDEPTDw3' > isn't known > ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDsign' > isn't known > ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw0' isn't > known > ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw1' isn't > known > ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw2' isn't > known > ../../../i386/i386/genassym.c:105: error: storage size of `NPGPTDw3' isn't > known > ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADsign' > isn't known > ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw0' > isn't known > ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw1' > isn't known > ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw2' > isn't known > ../../../i386/i386/genassym.c:117: error: storage size of `KERNLOADw3' > isn't known > ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIsign' > isn't known > ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw0' > isn't known > ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw1' > isn't known > ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw2' > isn't known > ../../../i386/i386/genassym.c:120: error: storage size of `PCB_EDIw3' > isn't known > ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIsign' > isn't known > ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw0' > isn't known > ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw1' > isn't known > ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw2' > isn't known > ../../../i386/i386/genassym.c:121: error: storage size of `PCB_ESIw3' > isn't known > ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPsign' > isn't known > ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw0' > isn't known > ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw1' > isn't known > ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw2' > isn't known > ../../../i386/i386/genassym.c:122: error: storage size of `PCB_EBPw3' > isn't known > ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPsign' > isn't known > ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw0' > isn't known > ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw1' > isn't known > ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw2' > isn't known > ../../../i386/i386/genassym.c:123: error: storage size of `PCB_ESPw3' > isn't known > ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXsign' > isn't known > ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw0' > isn't known > ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw1' > isn't known > ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw2' > isn't known > ../../../i386/i386/genassym.c:124: error: storage size of `PCB_EBXw3' > isn't known > ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPsign' > isn't known > ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw0' > isn't known > ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw1' > isn't known > ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw2' > isn't known > ../../../i386/i386/genassym.c:125: error: storage size of `PCB_EIPw3' > isn't known > ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0sign' > isn't known > ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w0' > isn't known > ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w1' > isn't known > ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w2' > isn't known > ../../../i386/i386/genassym.c:126: error: storage size of `TSS_ESP0w3' > isn't known > ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLsign' > isn't known > ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw0' > isn't known > ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw1' > isn't known > ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw2' > isn't known > ../../../i386/i386/genassym.c:135: error: storage size of `PCB_PSLw3' > isn't known > ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTsign' > isn't known > ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw0' > isn't known > ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw1' > isn't known > ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw2' > isn't known > ../../../i386/i386/genassym.c:137: error: storage size of `PCB_EXTw3' > isn't known > ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREsign' > isn't known > ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw0' > isn't known > ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw1' > isn't known > ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw2' > isn't known > ../../../i386/i386/genassym.c:139: error: storage size of `PCB_SPAREw3' > isn't known > ../../../i386/i386/genassym.c:144: error: storage size of > `PCB_SWITCHOUTsign' isn't known > ../../../i386/i386/genassym.c:144: error: storage size of > `PCB_SWITCHOUTw0' isn't known > ../../../i386/i386/genassym.c:144: error: storage size of > `PCB_SWITCHOUTw1' isn't known > ../../../i386/i386/genassym.c:144: error: storage size of > `PCB_SWITCHOUTw2' isn't known > ../../../i386/i386/genassym.c:144: error: storage size of > `PCB_SWITCHOUTw3' isn't known > ../../../i386/i386/genassym.c:147: error: storage size of > `PCB_VM86CALLsign' isn't known > ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw0' > isn't known > ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw1' > isn't known > ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw2' > isn't known > ../../../i386/i386/genassym.c:147: error: storage size of `PCB_VM86CALLw3' > isn't known > ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPsign' > isn't known > ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw0' isn't > known > ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw1' isn't > known > ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw2' isn't > known > ../../../i386/i386/genassym.c:151: error: storage size of `TF_EIPw3' isn't > known > ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSsign' > isn't known > ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw0' > isn't known > ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw1' > isn't known > ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw2' > isn't known > ../../../i386/i386/genassym.c:153: error: storage size of `TF_EFLAGSw3' > isn't known > ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4sign' > isn't known > ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w0' > isn't known > ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w1' > isn't known > ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w2' > isn't known > ../../../i386/i386/genassym.c:160: error: storage size of `SIGF_UC4w3' > isn't known > ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSsign' > isn't known > ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw0' > isn't known > ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw1' > isn't known > ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw2' > isn't known > ../../../i386/i386/genassym.c:169: error: storage size of `UC4_EFLAGSw3' > isn't known > ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSsign' > isn't known > ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw0' isn't > known > ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw1' isn't > known > ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw2' isn't > known > ../../../i386/i386/genassym.c:170: error: storage size of `UC4_GSw3' isn't > known > ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSsign' > isn't known > ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw0' > isn't known > ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw1' > isn't known > ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw2' > isn't known > ../../../i386/i386/genassym.c:172: error: storage size of `UC_EFLAGSw3' > isn't known > ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSsign' > isn't known > ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw0' isn't > known > ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw1' isn't > known > ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw2' isn't > known > ../../../i386/i386/genassym.c:173: error: storage size of `UC_GSw3' isn't > known > ../../../i386/i386/genassym.c:195: error: storage size of > `PC_COMMON_TSSsign' isn't known > ../../../i386/i386/genassym.c:195: error: storage size of > `PC_COMMON_TSSw0' isn't known > ../../../i386/i386/genassym.c:195: error: storage size of > `PC_COMMON_TSSw1' isn't known > ../../../i386/i386/genassym.c:195: error: storage size of > `PC_COMMON_TSSw2' isn't known > ../../../i386/i386/genassym.c:195: error: storage size of > `PC_COMMON_TSSw3' isn't known > ../../../i386/i386/genassym.c:196: error: storage size of > `PC_COMMON_TSSDsign' isn't known > ../../../i386/i386/genassym.c:196: error: storage size of > `PC_COMMON_TSSDw0' isn't known > ../../../i386/i386/genassym.c:196: error: storage size of > `PC_COMMON_TSSDw1' isn't known > ../../../i386/i386/genassym.c:196: error: storage size of > `PC_COMMON_TSSDw2' isn't known > ../../../i386/i386/genassym.c:196: error: storage size of > `PC_COMMON_TSSDw3' isn't known > ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTsign' > isn't known > ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw0' > isn't known > ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw1' > isn't known > ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw2' > isn't known > ../../../i386/i386/genassym.c:197: error: storage size of `PC_TSS_GDTw3' > isn't known > ../../../i386/i386/genassym.c:198: error: storage size of > `PC_CURRENTLDTsign' isn't known > ../../../i386/i386/genassym.c:198: error: storage size of > `PC_CURRENTLDTw0' isn't known > ../../../i386/i386/genassym.c:198: error: storage size of > `PC_CURRENTLDTw1' isn't known > ../../../i386/i386/genassym.c:198: error: storage size of > `PC_CURRENTLDTw2' isn't known > ../../../i386/i386/genassym.c:198: error: storage size of > `PC_CURRENTLDTw3' isn't known > ../../../i386/i386/genassym.c:214: error: storage size of `KPSELsign' > isn't known > ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw0' isn't > known > ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw1' isn't > known > ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw2' isn't > known > ../../../i386/i386/genassym.c:214: error: storage size of `KPSELw3' isn't > known > ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELsign' > isn't known > ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw0' > isn't known > ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw1' > isn't known > ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw2' > isn't known > ../../../i386/i386/genassym.c:216: error: storage size of `BC32SELw3' > isn't known > *** Error code 1 > > Stop in /usr/src/sys/amd64/compile/GENERIC. > *** Error code 1 > > Stop in /usr/src/sys/amd64/compile/GENERIC. > # > -- is there a reason your building the kernel the old school way? read /usr/src/Makefile try this: cd /usr/src/ make TARGET_ARCH=amd64 buildkernel From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 18:37:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 093D616A4CE for ; Thu, 2 Dec 2004 18:37:59 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB36B43D2F for ; Thu, 2 Dec 2004 18:37:58 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 911BFF214C; Thu, 2 Dec 2004 10:37:56 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50023-10; Thu, 2 Dec 2004 10:37:53 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id BBFC1F1888; Thu, 2 Dec 2004 10:37:53 -0800 (PST) From: Sean McNeil To: nmeverde@np.k12.mn.us In-Reply-To: <60106.206.146.85.21.1102012445.squirrel@206.146.85.21> References: <20041202170246.3CFE7790094@ws1-14.us4.outblaze.com> <60106.206.146.85.21.1102012445.squirrel@206.146.85.21> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-kRDZ5lvVUB/Sc9+E82eC" Date: Thu, 02 Dec 2004 10:37:53 -0800 Message-Id: <1102012673.19450.9.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:37:59 -0000 --=-kRDZ5lvVUB/Sc9+E82eC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-12-02 at 12:34 -0600, nmeverde@np.k12.mn.us wrote: > > Well, I tried to compile GENERIC kernel for my Athlon64 and result was: > > What should I do? Help plz... > > [snip] > is there a reason your building the kernel the old school way? > read /usr/src/Makefile >=20 > try this: > cd /usr/src/ > make TARGET_ARCH=3Damd64 buildkernel The old school way should still be supported. The problem, however, appears to be that you are attempting to cross compile an amd64 kernel on an i386 system. I'm guessing that the old school way doesn't support that. Originally, that is exactly what I did - cross from i386 to amd64. I think I did it the new(er) way, though, with: make TARGET_ARCH=3Damd64 buildworld make TARGET_ARCH=3Damd64 buildkernel It has been a long time since I did this and I can't recall completely how I accomplished it. You will have serious headaches if you try to install world on top of an i386 system. Do not attempt unless you know exactly what you are doing. Of course, the best thing to do is to install a fresh copy of FreeBSD from an amd64 version of 5.3. Cheers, Sean --=-kRDZ5lvVUB/Sc9+E82eC Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBr2EByQsGN30uGE4RAjsjAKDc9DXGmDzjoo4VIhrNM8KPTKlrjQCeMemV IBls1utXyxGt5qGQ77Ltqe4= =lCan -----END PGP SIGNATURE----- --=-kRDZ5lvVUB/Sc9+E82eC-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 20:02:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1940716A4CE for ; Thu, 2 Dec 2004 20:02:50 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7348043D46 for ; Thu, 2 Dec 2004 20:02:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB2K1gDK003002; Thu, 2 Dec 2004 12:01:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB2K1ft9003001; Thu, 2 Dec 2004 12:01:41 -0800 (PST) (envelope-from obrien) Date: Thu, 2 Dec 2004 12:01:41 -0800 From: "David O'Brien" To: Egor Dmitrenkov , nmeverde@np.k12.mn.us Message-ID: <20041202200141.GA2774@dragon.nuxi.com> References: <20041202170246.3CFE7790094@ws1-14.us4.outblaze.com> <60106.206.146.85.21.1102012445.squirrel@206.146.85.21> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60106.206.146.85.21.1102012445.squirrel@206.146.85.21> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:02:50 -0000 On Thu, Dec 02, 2004 at 12:02:46PM -0500, Egor Dmitrenkov wrote: > > Well, I tried to compile GENERIC kernel for my Athlon64 and result was: > > What should I do? Help plz... > > -------------------- > > # cd /usr/src/sys/amd64/conf/ > > # config GENERIC > > Kernel build directory is ../compile/GENERIC > > Don't forget to do a ``make depend'' > > # cd ../compile/GENERIC > > # make depend .. > > -mpreferred-stack-boundary=2 -ffreestanding ../../../i386/i386/genassym.c > > ../../../i386/i386/genassym.c:38:22: opt_apic.h: No such file or directory > > In file included from ../../../sys/types.h:44, > > from ../../../sys/param.h:61, > > from ../../../i386/i386/genassym.c:42: > > ./machine/endian.h: In function `__bswap64': > > ./machine/endian.h:126: warning: right shift count >= width of type Something is very weird -- you're trying to compile a 'i386' platform file and not the proper 'amd64' platform file. You show you're trying to build a 64-bit kernel (vs. 32-bit), but let me ask that this is true just to be perfectly clear. On Thu, Dec 02, 2004 at 12:34:05PM -0600, nmeverde@np.k12.mn.us wrote: > > Stop in /usr/src/sys/amd64/compile/GENERIC. > > # > > -- Geez, could you *please* trim some of the uneeded _1030_ lines in the original post when you follow up?!? > is there a reason your building the kernel the old school way? > read /usr/src/Makefile > > try this: > cd /usr/src/ > make TARGET_ARCH=amd64 buildkernel Specifying 'TARGET_ARCH' isn't part of the 'new school way'. Only specify 'TARGET_ARCH' when you are trying to do a cross build. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 20:38:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED31B16A4CF for ; Thu, 2 Dec 2004 20:38:38 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 439F543D3F for ; Thu, 2 Dec 2004 20:38:38 +0000 (GMT) (envelope-from mind@doctor.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])3473A18002A3 for ; Thu, 2 Dec 2004 20:38:38 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 2 Dec 2004 20:38:35 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id 6BF3B790094; Thu, 2 Dec 2004 20:38:35 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [213.59.125.30] by ws1-14.us4.outblaze.com with http for mind@doctor.com; Thu, 02 Dec 2004 15:38:35 -0500 From: "Egor Dmitrenkov" To: obrien@freebsd.org Date: Thu, 02 Dec 2004 15:38:35 -0500 X-Originating-Ip: 213.59.125.30 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20041202203835.6BF3B790094@ws1-14.us4.outblaze.com> cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:38:39 -0000 > On Thu, Dec 02, 2004 at 12:02:46PM -0500, Egor Dmitrenkov wrote: > > > Well, I tried to compile GENERIC kernel for my Athlon64 and result wa= s: > > > What should I do? Help plz... > > > -------------------- > > > # cd /usr/src/sys/amd64/conf/ > > > # config GENERIC > > > Kernel build directory is ../compile/GENERIC > > > Don't forget to do a ``make depend'' > > > # cd ../compile/GENERIC > > > # make depend > .. > > > -mpreferred-stack-boundary=3D2 -ffreestanding ../../../i386/i386/gena= ssym.c > > > ../../../i386/i386/genassym.c:38:22: opt_apic.h: No such file or dire= ctory > > > In file included from ../../../sys/types.h:44, > > > from ../../../sys/param.h:61, > > > from ../../../i386/i386/genassym.c:42: > > > ./machine/endian.h: In function `__bswap64': > > > ./machine/endian.h:126: warning: right shift count >=3D width of type >=20 > Something is very weird -- you're trying to compile a 'i386' platform > file and not the proper 'amd64' platform file. >=20 > You show you're trying to build a 64-bit kernel (vs. 32-bit), but let me > ask that this is true just to be perfectly clear. >=20 Yes, I'm trying to build a 64-bit kernel. >=20 > On Thu, Dec 02, 2004 at 12:34:05PM -0600, nmeverde@np.k12.mn.us wrote: > > > Stop in /usr/src/sys/amd64/compile/GENERIC. > > > # > > > -- >=20 > Geez, could you *please* trim some of the uneeded _1030_ lines in the > original post when you follow up?!? >=20 > > is there a reason your building the kernel the old school way? > > read /usr/src/Makefile > > > > try this: > > cd /usr/src/ > > make TARGET_ARCH=3Damd64 buildkernel >=20 Sorry for flooding, I thought that this info can be useful... Result(last command and errmsg): cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-d= ecls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -= Winli ne -Wcast-qual -fformat-extensions -std=3Dc99 -nostdinc -I- -I. -I/usr/src/= sys -I/ usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/c= ontri b/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/= src/s ys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include = opt_g lobal.h -finline-limit=3D8000 --param inline-unit-growth=3D100 --param larg= e-functio n-growth=3D1000 -mcmodel=3Dkernel -mno-red-zone -mfpmath=3D387 -mno-sse -mn= o-sse2 -mno -mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding= /usr /src/sys/amd64/amd64/genassym.c /usr/src/sys/amd64/amd64/genassym.c:1: error: code model `kernel' not suppo= rted in the 32 bit mode *** Error code 1=20 > Specifying 'TARGET_ARCH' isn't part of the 'new school way'. > Only specify 'TARGET_ARCH' when you are trying to do a cross build. >=20 Please, tell me what should I exactly do...=20 And please don't forget to "cc" me, I'm not yet subscribed to this list. Thanks in advance.=20 > -- > -- David (obrien@FreeBSD.org) --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 20:50:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABDB116A4CE; Thu, 2 Dec 2004 20:50:51 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E61A43D1F; Thu, 2 Dec 2004 20:50:51 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 05246F214C; Thu, 2 Dec 2004 12:50:49 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27278-02; Thu, 2 Dec 2004 12:50:47 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 5D4D9F20CE; Thu, 2 Dec 2004 12:50:47 -0800 (PST) From: Sean McNeil To: Egor Dmitrenkov In-Reply-To: <20041202203835.6BF3B790094@ws1-14.us4.outblaze.com> References: <20041202203835.6BF3B790094@ws1-14.us4.outblaze.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-CqqkHVS2bgfQYV10g6sd" Date: Thu, 02 Dec 2004 12:50:47 -0800 Message-Id: <1102020647.38701.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:50:51 -0000 --=-CqqkHVS2bgfQYV10g6sd Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-12-02 at 15:38 -0500, Egor Dmitrenkov wrote: > Please, tell me what should I exactly do...=20 > And please don't forget to "cc" me, I'm not yet subscribed to this list. > Thanks in advance.=20 Like I said, it is tricky to build an amd64 kernel from an i386 installation and then upgrade your computer. If all you want to do is build the kernel (and not install it), then the make TARGET_ARCH=3Damd64 buildworld buildkernel thing should work. Otherwise, the best thing to do is to install an amd64 base from some place like ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/5.3/ Cheers, Sean --=-CqqkHVS2bgfQYV10g6sd Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBr4AnyQsGN30uGE4RAsYuAKCB0eDGxdgg5VqN7CJyalHHm1osWQCg6sVa ouq/dn+ffUSRmeFirUYS/j4= =5Q6j -----END PGP SIGNATURE----- --=-CqqkHVS2bgfQYV10g6sd-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 20:58:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38E2816A4CE for ; Thu, 2 Dec 2004 20:58:17 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 119E943D2F for ; Thu, 2 Dec 2004 20:58:17 +0000 (GMT) (envelope-from mind@doctor.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])42C85180035F for ; Thu, 2 Dec 2004 20:58:16 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 2 Dec 2004 20:58:11 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id 1C4D1790094; Thu, 2 Dec 2004 20:58:10 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [213.59.125.30] by ws1-14.us4.outblaze.com with http for mind@doctor.com; Thu, 02 Dec 2004 15:58:10 -0500 From: "Egor Dmitrenkov" To: "Sean McNeil" Date: Thu, 02 Dec 2004 15:58:10 -0500 X-Originating-Ip: 213.59.125.30 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20041202205810.1C4D1790094@ws1-14.us4.outblaze.com> cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:58:17 -0000 > On Thu, 2004-12-02 at 15:38 -0500, Egor Dmitrenkov wrote: > > Please, tell me what should I exactly do... And please don't=20 > > forget to "cc" me, I'm not yet subscribed to this list. > > Thanks in advance. >=20 > Like I said, it is tricky to build an amd64 kernel from an i386 > installation and then upgrade your computer. If all you want to do is > build the kernel (and not install it), then the >=20 > make TARGET_ARCH=3Damd64 buildworld buildkernel >=20 Of course I want to install new kernel too. > thing should work. Otherwise, the best thing to do is to install an > amd64 base from some place like >=20 > ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/5.3/ > =20 Is that means that I can't build and install kernel myself even from 2 DVD = set? --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 2 21:08:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E85816A4CE for ; Thu, 2 Dec 2004 21:08:40 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE3B43D5C for ; Thu, 2 Dec 2004 21:08:40 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E6662F2153; Thu, 2 Dec 2004 13:08:39 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27275-06; Thu, 2 Dec 2004 13:08:34 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id F2FA8F1888; Thu, 2 Dec 2004 13:08:33 -0800 (PST) From: Sean McNeil To: Egor Dmitrenkov In-Reply-To: <20041202205810.1C4D1790094@ws1-14.us4.outblaze.com> References: <20041202205810.1C4D1790094@ws1-14.us4.outblaze.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8rr1jTq4fMqQBBLnczLr" Date: Thu, 02 Dec 2004 13:08:33 -0800 Message-Id: <1102021713.40740.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:08:40 -0000 --=-8rr1jTq4fMqQBBLnczLr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-12-02 at 15:58 -0500, Egor Dmitrenkov wrote: > > On Thu, 2004-12-02 at 15:38 -0500, Egor Dmitrenkov wrote: > > > Please, tell me what should I exactly do... And please don't=20 > > > forget to "cc" me, I'm not yet subscribed to this list. > > > Thanks in advance. > >=20 > > Like I said, it is tricky to build an amd64 kernel from an i386 > > installation and then upgrade your computer. If all you want to do is > > build the kernel (and not install it), then the > >=20 > > make TARGET_ARCH=3Damd64 buildworld buildkernel > >=20 >=20 > Of course I want to install new kernel too. >=20 > > thing should work. Otherwise, the best thing to do is to install an > > amd64 base from some place like > >=20 > > ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/5.3/ > > > =20 > Is that means that I can't build and install kernel myself even from 2 DV= D set? Of course you can install the kernel yourself. You have to start with an amd64 installation, however, and it looks like you have an i386 install on that machine. --=-8rr1jTq4fMqQBBLnczLr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBr4RRyQsGN30uGE4RAmzCAJ46CV+FkXYCxEzj58oYIyjbTKB/dQCeMkro y3GoD8hNkgv6CPKwKJd5m1I= =K6dG -----END PGP SIGNATURE----- --=-8rr1jTq4fMqQBBLnczLr-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 00:53:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF6C716A4CE for ; Fri, 3 Dec 2004 00:53:31 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4670543D1D for ; Fri, 3 Dec 2004 00:53:31 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB30rRv3006549; Thu, 2 Dec 2004 16:53:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB30rQhk006548; Thu, 2 Dec 2004 16:53:26 -0800 (PST) (envelope-from obrien) Date: Thu, 2 Dec 2004 16:53:26 -0800 From: "David O'Brien" To: Egor Dmitrenkov Message-ID: <20041203005326.GA6425@dragon.nuxi.com> References: <20041202203835.6BF3B790094@ws1-14.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202203835.6BF3B790094@ws1-14.us4.outblaze.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 00:53:31 -0000 On Thu, Dec 02, 2004 at 03:38:35PM -0500, Egor Dmitrenkov wrote: > > Something is very weird -- you're trying to compile a 'i386' platform > > file and not the proper 'amd64' platform file. > > > > You show you're trying to build a 64-bit kernel (vs. 32-bit), but let me > > ask that this is true just to be perfectly clear. > > > Yes, I'm trying to build a 64-bit kernel. Ok, so now I'm going to assume you're trying to do this on a 32-bit FreeBSD/i386 5.3 system; since there aren't any other details otherwise. First question is why don't you just don't download and install FreeBSD/amd64 5.3 onto your Athlon64 system? However, if you want to build an amd64 kernel on an i386 system (ie, a cross build): # cd /usr/src # rm -rf /usr/obj/* # make cleandir ; make cleandir # make TARGET_ARCH=amd64 buildworld # make KERNCONF=GENERIC TARGET_ARCH=amd64 buildkernel note that the 2nd and 3rd steps aren't typically needed, but I have no idea the state of your /usr/src and /usr/obj dirs. > > On Thu, Dec 02, 2004 at 12:34:05PM -0600, nmeverde@np.k12.mn.us wrote: > > Geez, could you *please* trim some of the uneeded _1030_ lines in the > > original post when you follow up?!? .. > Sorry for flooding, I thought that this info can be useful... >From you it was useful. From nmeverde@np.k12.mn.us it wasn't. > Result(last command and errmsg): > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall .. > /src/sys/amd64/amd64/genassym.c > /usr/src/sys/amd64/amd64/genassym.c:1: error: code model `kernel' not supported > in the 32 bit mode > *** Error code 1 You're still using the i386 32-bit kernel to build an AMD64 kernel. The 32-bit i386 compiler doesn't understand the AMD64-specific compiler switches. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 01:14:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BCE516A4D0 for ; Fri, 3 Dec 2004 01:14:13 +0000 (GMT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.17.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2D8143D49 for ; Fri, 3 Dec 2004 01:14:12 +0000 (GMT) (envelope-from wkwu@FreeBSD.csie.NCTU.edu.tw) Received: from localhost (localhost.csie.nctu.edu.tw [127.0.0.1]) by FreeBSD.csie.NCTU.edu.tw (Postfix) with ESMTP id 8CDED106C47 for ; Fri, 3 Dec 2004 09:14:08 +0800 (CST) Received: from FreeBSD.csie.NCTU.edu.tw ([127.0.0.1]) by localhost (FreeBSD.csie.NCTU.edu.tw [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86676-03 for ; Fri, 3 Dec 2004 09:14:08 +0800 (CST) Received: by FreeBSD.csie.NCTU.edu.tw (Postfix, from userid 10372) id 163FE106C28; Fri, 3 Dec 2004 09:14:08 +0800 (CST) To: FreeBSD-amd64@freebsd.org Newsgroups: mailing.freebsd.amd64 In-Reply-To: Organization: Kavalan X-Newsreader: TIN [UNIX 1.3 unoff BETA 970324; i386 FreeBSD 4.10-STABLE] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> Date: Fri, 3 Dec 2004 09:14:08 +0800 (CST) From: wkwu@FreeBSD.csie.NCTU.edu.tw (James) Subject: Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 01:14:13 -0000 您在 文章內提到: > FreeBSD/amd64 works well on a dual opteron Tyan K8S Pro system > with less than 8 GB of memory. It does not boot if you have > more than 8 GB. See the FreeBSD-amd64 list over the last week or > 2 for detailed emails continaing the panic messages. I use Tyan K8S Pro (BIOS v2.03, factory default) with 16G RAM. It works well on heavy memory load and CPU load. (mysql and others) (Even the BIOS option SRAT on/off both works.) 5.3-STABLE amd64 improves a lot on performance than 5.2.1. Maybe you can tell us what type of your jobs. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 02:42:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B958216A4CE for ; Fri, 3 Dec 2004 02:42:25 +0000 (GMT) Received: from www.microvore.com (www.microvore.com [24.199.42.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B7543D3F for ; Fri, 3 Dec 2004 02:42:25 +0000 (GMT) (envelope-from steve@donegan.org) Received: (from root@localhost) by www.microvore.com (8.11.4/8.11.4) id iB32gOT23178 for freebsd-amd64@freebsd.org; Thu, 2 Dec 2004 18:42:24 -0800 X-Microvore-From: steve@donegan.org X-Microvore-To: freebsd-amd64@freebsd.org X-Microvore-Peer: 1.0.24.3 X-Microvore-Result: RBL=0 SPF=0 MX=1 REV=1 VIRUS=0 UCE=0 HDOMAIN=2 FDOMAIN=0 RECCNT=1 INVRCPT=0 RCPTRATIO=0 X-Microvore-Score: 12 Message-ID: <41AFD279.4080802@donegan.org> Date: Thu, 02 Dec 2004 18:42:01 -0800 From: "Steven P. Donegan" User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Link on FreeBSD.org led me here X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 02:42:25 -0000 Normally a link to a mailing list would have sent me to a subscribe page or instructions - the link on FreeBSD.org didn't do that. So, what is the process for joining the list? At this moment my Tyan 2850/AMD Opteron 2 GHz/2G ECC RAM box is installing FreeBSD current for AMD/64 - seems like it's happy so far. Thanks! From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 04:58:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 512EA16A4CE for ; Fri, 3 Dec 2004 04:58:52 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2793643D41 for ; Fri, 3 Dec 2004 04:58:52 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB34wn9o015898; Thu, 2 Dec 2004 20:58:49 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB34wn06015897; Thu, 2 Dec 2004 20:58:49 -0800 (PST) (envelope-from sgk) Date: Thu, 2 Dec 2004 20:58:49 -0800 From: Steve Kargl To: James Message-ID: <20041203045849.GA15850@troutmask.apl.washington.edu> References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> User-Agent: Mutt/1.4.1i cc: FreeBSD-amd64@freebsd.org Subject: Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 04:58:52 -0000 On Fri, Dec 03, 2004 at 09:14:08AM +0800, James wrote: > ?z?b ??????????: > > FreeBSD/amd64 works well on a dual opteron Tyan K8S Pro system > > with less than 8 GB of memory. It does not boot if you have > > more than 8 GB. See the FreeBSD-amd64 list over the last week or > > 2 for detailed emails continaing the panic messages. > > I use Tyan K8S Pro (BIOS v2.03, factory default) with 16G RAM. > It works well on heavy memory load and CPU load. (mysql and others) > (Even the BIOS option SRAT on/off both works.) What type of memory are you using? Can you send me (off the mailing list) a verbose boot message? I flashed the BIOS from v2.02 to v2.03 with no improvements. > 5.3-STABLE amd64 improves a lot on performance than 5.2.1. > > Maybe you can tell us what type of your jobs. I can't boot with the full 16 GB. I need to set hw.physmem="8G" to boot. The 16 GB is on the motherboard and is detected during POST. FreeBSD simply panics if I try setting hw.physmem to anything above 8 GB. My memory is Cosair PC2700 recommended by Tyan for this motherboard. As far as my jobs, I run numerical simulations of heat transfer in biological tissues and nonlinear acoustics. The numerical techniques are standard and hybrid finite difference solutions to coupled PDEs. I can easily consume the 16 GB if not more memory as I add more realistic physics to the problem. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 05:08:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C02D16A4CE for ; Fri, 3 Dec 2004 05:08:21 +0000 (GMT) Received: from postman.riken.go.jp (postman.riken.go.jp [134.160.33.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03DB543D45 for ; Fri, 3 Dec 2004 05:08:20 +0000 (GMT) (envelope-from sty@iki.fi) Received: (qmail 70344 invoked by uid 1111); 3 Dec 2004 05:08:17 -0000 Received: from sty@iki.fi by postman-smtp2.riken.go.jp by uid 0 with qmail-scanner-1.20 (sweep: 2.18/3.77. Clear:RC:1(134.160.173.1):. Processed in 1.403383 secs); 03 Dec 2004 05:08:17 -0000 Received: from unknown (HELO ?172.16.112.232?) (134.160.173.1) by postman.riken.go.jp with RC4-MD5 encrypted SMTP; 3 Dec 2004 05:08:15 -0000 Message-ID: <41AFF4BF.7070503@iki.fi> Date: Fri, 03 Dec 2004 14:08:15 +0900 From: =?ISO-8859-1?Q?Tommi_L=E4tti?= User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> <20041203045849.GA15850@troutmask.apl.washington.edu> In-Reply-To: <20041203045849.GA15850@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD-amd64@freebsd.org Subject: OT Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:08:21 -0000 Steve Kargl wrote: > As far as my jobs, I run numerical simulations of heat > transfer in biological tissues and nonlinear acoustics. > The numerical techniques are standard and hybrid finite > difference solutions to coupled PDEs. I can easily > consume the 16 GB if not more memory as I add more > realistic physics to the problem. Interesting. Are you using a home-brewn software for analysis or are you running a commercial package? I'm doing some electrophysiology research (in vivo and in vitro) and we're contemplating currently using some Matlab and/or Labview for analyzis. The Lynx produces some 64 channels of data and one run can easily amount a couple of gigs worth of files... which would easily warrant the use of some 2-way+ configurations. Although matlab doesn't thread... -- br, Tommi From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 05:29:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B800116A4CE for ; Fri, 3 Dec 2004 05:29:30 +0000 (GMT) Received: from santiago.pacific.net.sg (santiago.pacific.net.sg [203.120.90.135]) by mx1.FreeBSD.org (Postfix) with SMTP id 971BE43D62 for ; Fri, 3 Dec 2004 05:29:29 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 5387 invoked from network); 3 Dec 2004 05:29:28 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by santiago with SMTP; 3 Dec 2004 05:29:27 -0000 Received: from [192.168.0.109] ([210.24.246.156]) by maxwell2.pacific.net.sg with ESMTP <20041203052927.NVYH12758.maxwell2.pacific.net.sg@[192.168.0.109]>; Fri, 3 Dec 2004 13:29:27 +0800 Message-ID: <41AFF9F9.9020104@pacific.net.sg> Date: Fri, 03 Dec 2004 13:30:33 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Steven P. Donegan" References: <41AFD279.4080802@donegan.org> In-Reply-To: <41AFD279.4080802@donegan.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: Link on FreeBSD.org led me here X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:29:30 -0000 Hi, Steven P. Donegan wrote: > Normally a link to a mailing list would have sent me to a subscribe page > or instructions - the link on FreeBSD.org didn't do that. So, what is > the process for joining the list? > try this link http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL It should show a list of mailling lists. Just click on one of them and you will get a screen to register. Erich From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 05:41:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B490316A4CE for ; Fri, 3 Dec 2004 05:41:39 +0000 (GMT) Received: from web41105.mail.yahoo.com (web41105.mail.yahoo.com [66.218.93.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 8A4C843D5A for ; Fri, 3 Dec 2004 05:41:39 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Received: (qmail 19613 invoked by uid 60001); 3 Dec 2004 05:41:39 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=0zcZzuYQDVpC/m6fZE8Zmf39PM+4gABCY29vv2sYvEukMsraRWPbaShke1HuFIx1tyJOplC7tgfglW0EBLNToQtJERRQq1Cm+9PuBfBemdPD6fhKt2DT+goG495sPuFkbL3yKjCatb2gK+nc8uHWDpffQpKmE/7A9+Io/xpBPdw= ; Message-ID: <20041203054139.19611.qmail@web41105.mail.yahoo.com> Received: from [67.170.88.122] by web41105.mail.yahoo.com via HTTP; Thu, 02 Dec 2004 21:41:39 PST Date: Thu, 2 Dec 2004 21:41:39 -0800 (PST) From: Jeffrey Katcher To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Keyboard not found on Sun W1100z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:41:39 -0000 Just bought one of these things, tried Solaris 10 "OS of the future" and decided to wipe it in disgust. I'm trying to install off the 5.3-RELEASE-amd64-bootonly iso. ISO boots, but USB keyboard is not seen after boot, even after setting hint.atkbd.0.flags="0x1". Any suggestions? From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 06:02:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A58016A4CE for ; Fri, 3 Dec 2004 06:02:57 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5008743D2F for ; Fri, 3 Dec 2004 06:02:57 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB362vmH016236; Thu, 2 Dec 2004 22:02:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB362veW016235; Thu, 2 Dec 2004 22:02:57 -0800 (PST) (envelope-from sgk) Date: Thu, 2 Dec 2004 22:02:56 -0800 From: Steve Kargl To: Tommi L?tti Message-ID: <20041203060256.GA16165@troutmask.apl.washington.edu> References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> <20041203045849.GA15850@troutmask.apl.washington.edu> <41AFF4BF.7070503@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AFF4BF.7070503@iki.fi> User-Agent: Mutt/1.4.1i cc: FreeBSD-amd64@freebsd.org Subject: Re: OT Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 06:02:57 -0000 On Fri, Dec 03, 2004 at 02:08:15PM +0900, Tommi L?tti wrote: > Steve Kargl wrote: > >As far as my jobs, I run numerical simulations of heat > >transfer in biological tissues and nonlinear acoustics. > >The numerical techniques are standard and hybrid finite > >difference solutions to coupled PDEs. I can easily > >consume the 16 GB if not more memory as I add more > >realistic physics to the problem. > > Interesting. Are you using a home-brewn software for analysis or are you > running a commercial package? I use homebrewed in that I write all my own numerical codes in Fortran 90/95. I can profile the code and identify numerical and time consuming bottlenecks where I can spend my time optimizing the algorithms. I have found that I simply cannot get any performance out of any matlab solution (not to mention that matlab restricts one to at most 2 GB of memory). > I'm doing some electrophysiology research (in vivo and in vitro) and > we're contemplating currently using some Matlab and/or Labview for > analyzis. The Lynx produces some 64 channels of data and one run can > easily amount a couple of gigs worth of files... which would easily > warrant the use of some 2-way+ configurations. Although matlab doesn't > thread... If you already have matlab code in house, then check out octave. You can find it in ports/math/octave. I have been able to run most matlab codes given to me by others with little or no changes. octave actually uses the system's memory better than matlab can. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 06:32:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37BD716A4CE for ; Fri, 3 Dec 2004 06:32:33 +0000 (GMT) Received: from web41102.mail.yahoo.com (web41102.mail.yahoo.com [66.218.93.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 0DFBA43D60 for ; Fri, 3 Dec 2004 06:32:33 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Received: (qmail 22549 invoked by uid 60001); 3 Dec 2004 06:32:32 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ZqYDpJYiBNcK7Q3bAqHRWBXqVPqTWo5kcpE1S7XiigqCRgtf0ODhIavK7Jx9V1LtqBnq8jHPvVN8BXAp4Bw/EntCh35/KDCs+o+trX1vZ+ngLbTsEamq3Mka4wpx696jLR00y2QiCd8fKGzIocfdoR2QWCG76Rp7xbsYHcF9Os8= ; Message-ID: <20041203063232.22547.qmail@web41102.mail.yahoo.com> Received: from [67.170.88.122] by web41102.mail.yahoo.com via HTTP; Thu, 02 Dec 2004 22:32:32 PST Date: Thu, 2 Dec 2004 22:32:32 -0800 (PST) From: Jeffrey Katcher To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Sun W1100z Update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 06:32:33 -0000 Still no luck. Is this machine useful for anything other than Linux or Solaris? I disabled legacy USB and even tried booting 5.2.1-RELEASE. It gets to the kernel and I lose keyboard. Tidbit: at keyboard attach time on both I see something like: device_attach: atkbd0 returned 6 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 07:41:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5B7A16A4CE for ; Fri, 3 Dec 2004 07:41:11 +0000 (GMT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.17.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95B7A43D48 for ; Fri, 3 Dec 2004 07:41:11 +0000 (GMT) (envelope-from wkwu@FreeBSD.csie.NCTU.edu.tw) Received: from localhost (localhost.csie.nctu.edu.tw [127.0.0.1]) by FreeBSD.csie.NCTU.edu.tw (Postfix) with ESMTP id 817DF106C0D; Fri, 3 Dec 2004 15:41:03 +0800 (CST) Received: from FreeBSD.csie.NCTU.edu.tw ([127.0.0.1]) by localhost (FreeBSD.csie.NCTU.edu.tw [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49176-09; Fri, 3 Dec 2004 15:41:03 +0800 (CST) Received: by FreeBSD.csie.NCTU.edu.tw (Postfix, from userid 10372) id 0653A106C00; Fri, 3 Dec 2004 15:41:03 +0800 (CST) To: sgk@troutmask.apl.washington.edu, freebsd-amd64@freebsd.org Newsgroups: mailing.freebsd.amd64 In-Reply-To: Organization: Kavalan X-Newsreader: TIN [UNIX 1.3 unoff BETA 970324; i386 FreeBSD 4.10-STABLE] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20041203074103.0653A106C00@FreeBSD.csie.NCTU.edu.tw> Date: Fri, 3 Dec 2004 15:41:03 +0800 (CST) From: wkwu@FreeBSD.csie.NCTU.edu.tw (James) Subject: Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 07:41:11 -0000 您在 文章內提到: > What type of memory are you using? Can you send me (off the > mailing list) a verbose boot message? I flashed the BIOS > from v2.02 to v2.03 with no improvements. I have sent dmesg to you. I use Corsair CM74SD2048RLP-2700 2G ECC Reg. Unfortunately, the CM74SD2048RLP-2700 won't be recommended using on Tyan S4882 motherboard. It will be very unstable although it is much cheaper than CM75SD2048RLP-2700(BGA chip). From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 07:43:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF2D116A4CE; Fri, 3 Dec 2004 07:43:48 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FDD843D4C; Fri, 3 Dec 2004 07:43:48 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iB37hkS7086891; Fri, 3 Dec 2004 01:43:47 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41B01932.90103@jrv.org> Date: Fri, 03 Dec 2004 01:43:46 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41AC70CA.4090805@freebsd.org> <41AFA4DE.4040702@jrv.org> <41AFA5D0.3060006@freebsd.org> In-Reply-To: <41AFA5D0.3060006@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 07:43:48 -0000 Scott Long wrote: >>> Bounce buffers with >4GB were indeed broken in 5.3-RELEASE. I fixed >>> them about a week ago in 5-STABLE and 6-CURRENT. You can work around >>> the breakage in 5.3-R by setting the following in /boot/loader.conf: >>> >>> vm.old_contigmalloc=1 >> >> > You should have rev 1.59.2.2 of /sys/i386/i386/busdma_machdep.c I'm using amd64. That same change appears to be in 1.57.2.2 on amd64. I have that file version. Unfortunate my system still crashes using more than 4GB of RAM. The symptom is a hard lockup, not a panic. This usually happens very quickly after NIC initialization begins. NIC bge(4) needs bounce buffers. My disk controller, twa(4), does not need bounce buffers and seems fine in single user mode with no NIC with 8GB. The system is limited to 4GB of RAM by putting "set hw,physmem=4g" in loader.rc rather than making any hardware changes. The hardware ran 5.2.1 for several months with 8GB so I think the hardware works. There are two CPUs and two DIMMs for each CPU. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 08:52:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B30F716A4CE for ; Fri, 3 Dec 2004 08:52:45 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EE4143D39 for ; Fri, 3 Dec 2004 08:52:45 +0000 (GMT) (envelope-from mind@doctor.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])8F6D318001C2 for ; Fri, 3 Dec 2004 08:52:45 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 3 Dec 2004 08:52:45 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id 7DA90790094; Fri, 3 Dec 2004 08:52:45 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [213.59.125.30] by ws1-14.us4.outblaze.com with http for mind@doctor.com; Fri, 03 Dec 2004 03:52:45 -0500 From: "Egor Dmitrenkov" To: freebsd-amd64@freebsd.org Date: Fri, 03 Dec 2004 03:52:45 -0500 X-Originating-Ip: 213.59.125.30 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20041203085245.7DA90790094@ws1-14.us4.outblaze.com> Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 08:52:45 -0000 > # cd /usr/src > # rm -rf /usr/obj/* > # make cleandir ; make cleandir > # make TARGET_ARCH=3Damd64 buildworld > # make KERNCONF=3DGENERIC TARGET_ARCH=3Damd64 buildkernel >=20 Will this install new kernel and world or build only? --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 09:36:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 700A616A4CE for ; Fri, 3 Dec 2004 09:36:46 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0997443D55 for ; Fri, 3 Dec 2004 09:36:46 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iB39WpZP089506; Fri, 3 Dec 2004 03:32:54 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41B032C3.9020005@jrv.org> Date: Fri, 03 Dec 2004 03:32:51 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Egor Dmitrenkov References: <20041202205810.1C4D1790094@ws1-14.us4.outblaze.com> In-Reply-To: <20041202205810.1C4D1790094@ws1-14.us4.outblaze.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 09:36:46 -0000 Egor Dmitrenkov wrote: >>thing should work. Otherwise, the best thing to do is to install an >>amd64 base from some place like >> >>ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/5.3/ >> >> >> > Is that means that I can't build and install kernel myself even from 2 DVD set? > > You can from an amd64 DVD, but it's tricky from an i386 DVD, perhaps so tricky that it does not work. It's an unusual thing to do, and unusual things don't get tested often and may fail. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 12:24:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DEA616A4CE for ; Fri, 3 Dec 2004 12:24:55 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2551D43D1D for ; Fri, 3 Dec 2004 12:24:55 +0000 (GMT) (envelope-from mind@doctor.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])B798318001B2 for ; Fri, 3 Dec 2004 12:24:54 +0000 (GMT) X-OB-Received: from unknown (205.158.62.178) by wfilter.us4.outblaze.com; 3 Dec 2004 12:24:54 -0000 Received: by ws1-14.us4.outblaze.com (Postfix, from userid 1001) id A6A12790094; Fri, 3 Dec 2004 12:24:54 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [213.59.125.30] by ws1-14.us4.outblaze.com with http for mind@doctor.com; Fri, 03 Dec 2004 07:24:54 -0500 From: "Egor Dmitrenkov" To: freebsd-amd64@freebsd.org Date: Fri, 03 Dec 2004 07:24:54 -0500 X-Originating-Ip: 213.59.125.30 X-Originating-Server: ws1-14.us4.outblaze.com Message-Id: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 12:24:55 -0000 Thanks, I've build the kernel this way: # cd /usr/src/ # make clean # rm -r /usr/obj/* # make TARGET_TECH=3Damd64 buildworld # make TARGET_TECH=3Damd64 buildkernel # make TARGET_TECH=3Damd64 installkernel New kernel freezes at startup right after enumerating hard drives... Should I install world? How? Thanks in advance! --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 13:33:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 819F716A4CE for ; Fri, 3 Dec 2004 13:33:15 +0000 (GMT) Received: from phoenix.severttk.ru (phoenix.severttk.ru [80.92.0.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B1B43D31 for ; Fri, 3 Dec 2004 13:33:13 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from phoenix.severttk.ru (localhost [127.0.0.1]) by phoenix.severttk.ru (Postfix) with SMTP id B8D7BA940 for ; Fri, 3 Dec 2004 16:33:12 +0300 (MSK) Received: from proxy.km.vibrators.ru (vlan101-sv-yar03ra.severttk.ru [80.92.2.130]) by phoenix.severttk.ru (Postfix) with ESMTP id 87A11A93A for ; Fri, 3 Dec 2004 16:33:06 +0300 (MSK) Received: from [192.168.1.36] (reaper [192.168.1.36] (may be forged)) by proxy.km.vibrators.ru (8.13.1/8.13.1) with ESMTP id iB3DX1qK096765; Fri, 3 Dec 2004 16:33:05 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Fri, 3 Dec 2004 16:26:19 +0300 From: Michael Lednev X-Mailer: The Bat! (v2.10.01) Personal X-Priority: 3 (Normal) Message-ID: <924403133.20041203162619@bk.ru> To: "Egor Dmitrenkov" In-Reply-To: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> References: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re[2]: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Michael Lednev List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 13:33:15 -0000 Hello Egor, Friday, December 3, 2004, 3:24:54 PM, you wrote: ED> # cd /usr/src/ ED> # make clean ED> # rm -r /usr/obj/* ED> # make TARGET_TECH=amd64 buildworld ED> # make TARGET_TECH=amd64 buildkernel ED> # make TARGET_TECH=amd64 installkernel hmmm, just like written in handbook ;) ED> New kernel freezes at startup right after enumerating hard drives... ED> Should I install world? How? Thanks in advance! unfortuately amd64 kernels cannot work with i386 world so you definetly need to install amd64 one. the easiest way to accomplish this is to make clean install from cd. -- Best regards, Michael mailto:liettneff@bk.ru From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 16:46:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43DBD16A4CE for ; Fri, 3 Dec 2004 16:46:41 +0000 (GMT) Received: from priv-edtnes56.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B417243D58 for ; Fri, 3 Dec 2004 16:46:40 +0000 (GMT) (envelope-from james@icionline.ca) Received: from d137-186-144-166.abhsia.telus.net ([137.186.144.166]) by priv-edtnes56.telusplanet.netESMTP <20041203164640.HGTL19463.priv-edtnes56.telusplanet.net@d137-186-144-166.abhsia.telus.net>; Fri, 3 Dec 2004 09:46:40 -0700 From: James Earl To: Jeffrey Katcher In-Reply-To: <20041203054139.19611.qmail@web41105.mail.yahoo.com> References: <20041203054139.19611.qmail@web41105.mail.yahoo.com> Content-Type: text/plain Date: Fri, 03 Dec 2004 09:46:40 -0700 Message-Id: <1102092400.617.2.camel@serious.ab.hsia.telus.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Keyboard not found on Sun W1100z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 16:46:41 -0000 On Thu, 2004-12-02 at 21:41 -0800, Jeffrey Katcher wrote: > Just bought one of these things, tried Solaris 10 "OS of the future" and > decided > to wipe it in disgust. I'm trying to install off the > 5.3-RELEASE-amd64-bootonly > iso. ISO boots, but USB keyboard is not seen after boot, even after setting > hint.atkbd.0.flags="0x1". > > Any suggestions? You could try seeing if the BIOS has a USB Keyboard option, or you could just get a little PS2 adapter for it. James From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 16:48:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18B0816A4CE for ; Fri, 3 Dec 2004 16:48:58 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B98DC43D5A for ; Fri, 3 Dec 2004 16:48:57 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 8BAAC2A8DD for ; Fri, 3 Dec 2004 08:48:57 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 34419E2B3 for ; Fri, 3 Dec 2004 08:48:57 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iB3GmtTN059149; Fri, 3 Dec 2004 08:48:55 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iB3GmsON059148; Fri, 3 Dec 2004 08:48:54 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org, Michael Lednev Date: Fri, 3 Dec 2004 08:48:54 -0800 User-Agent: KMail/1.7.1 References: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> <924403133.20041203162619@bk.ru> In-Reply-To: <924403133.20041203162619@bk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412030848.54478.peter@wemm.org> Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 16:48:58 -0000 On Friday 03 December 2004 05:26 am, Michael Lednev wrote: > Hello Egor, > > Friday, December 3, 2004, 3:24:54 PM, you wrote: > > ED> # cd /usr/src/ > ED> # make clean > ED> # rm -r /usr/obj/* > ED> # make TARGET_TECH=amd64 buildworld > ED> # make TARGET_TECH=amd64 buildkernel > ED> # make TARGET_TECH=amd64 installkernel > > hmmm, just like written in handbook ;) > > ED> New kernel freezes at startup right after enumerating hard > drives... ED> Should I install world? How? Thanks in advance! > > unfortuately amd64 kernels cannot work with i386 world so you > definetly need to install amd64 one. the easiest way to accomplish > this is to make clean install from cd. If you are feeling adventurous, this is what I do to convert an i386 install to an amd64 system: * build an amd64 kernel, install it as kernel.amd64 * turn off swap and newfs /dev/ad0s1b (swap partition). dont forget rc.conf and fstab * mount /dev/ad0s1b /mnt * make installworld DESTDIR=/mnt (this puts an amd64 userland in the temporary filesystem that lives in the swap partition) * copy /etc/fstab to /mnt/etc/fstab (and a few others that I dont remember) * reboot * break into loader prompt * type: set vfs.root.mountfrom="ufs:/dev/ad0s1b" * boot -s kernel.amd64 If everything works, then I mount /home (I use /home/src and /home/obj) and make symlinks from the scratch /usr/src and /usr/obj to /home. I mount the old root partition, old /var and /usr etc as /mnt, /mnt/usr, /mnt/var, etc. Then do another 'make installworld DESTDIR=/mnt". Reboot again, still with the amd64 kernel but with the normal root fs. Once its up, turn swap back on and reset rc.conf. Caveat: this is an overview, not a detailed recipe. I have not done this for something like 12 months, so the chances that I've forgotten a key point are fairly good. Don't try this if you're not going to be able to get yourself out of a mess. Historical note: Sun used the 'fs in swap' thing for their OS boot tapes. They'd boot the tape and copy a dd'ed image into swap and mount it. It probably predates that though, but that was the first I heard of it. BTW: the reason why this is necessary is that the 32 bit emulation is aimed at application level syscalls and kernel interfaces. The moment that we get into OS-level binaries, we get exposed to things like the mount interface, sysctl binary data and so on. The task of translating that is huge. Not to mention that static binaries (like /sbin/init) won't run due to the i386_userldt syscalls. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 16:52:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3AE016A4CE for ; Fri, 3 Dec 2004 16:52:22 +0000 (GMT) Received: from web41122.mail.yahoo.com (web41122.mail.yahoo.com [66.218.94.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 82C1C43D53 for ; Fri, 3 Dec 2004 16:52:22 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Received: (qmail 32899 invoked by uid 60001); 3 Dec 2004 16:52:22 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=wM+b99shgVaz0RJWCk4Owpw+r+M6JFodOpoNP397y1uiNimu8fFsOgj/tCdCOooK7HmLMspadi3g3VGy58A508n0SGrT+kGwsWgcvd4iaEc0RvwJGeaKc6zm6a7o3dBh+3B3ADm8JSQWvaTPpnz5N9ouwOs3X67A/zN7rg63Skg= ; Message-ID: <20041203165222.32897.qmail@web41122.mail.yahoo.com> Received: from [67.170.88.122] by web41122.mail.yahoo.com via HTTP; Fri, 03 Dec 2004 08:52:22 PST Date: Fri, 3 Dec 2004 08:52:22 -0800 (PST) From: Jeffrey Katcher To: James Earl In-Reply-To: <1102092400.617.2.camel@serious.ab.hsia.telus.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: Keyboard not found on Sun W1100z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 16:52:22 -0000 --- James Earl wrote: > You could try seeing if the BIOS has a USB Keyboard option, or you could > just get a little PS2 adapter for it. > Thanks for the suggestion. I did try this with no change. From the quickly scrolling console messages, there's something weird about how FreeBSD sees the USB controllers on this thing. I'd capture them, but my other system is a ThinkPad without serial ports. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 17:27:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00EAC16A4CE for ; Fri, 3 Dec 2004 17:27:09 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF22E43D48 for ; Fri, 3 Dec 2004 17:27:08 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 73EEAF2179; Fri, 3 Dec 2004 09:27:08 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16074-09; Fri, 3 Dec 2004 09:27:07 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 3673EF2163; Fri, 3 Dec 2004 09:27:07 -0800 (PST) From: Sean McNeil To: Egor Dmitrenkov In-Reply-To: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> References: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pJwTOX1WCLXmr2RnCl78" Date: Fri, 03 Dec 2004 09:27:07 -0800 Message-Id: <1102094827.22424.7.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:27:09 -0000 --=-pJwTOX1WCLXmr2RnCl78 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-12-03 at 07:24 -0500, Egor Dmitrenkov wrote: > Thanks, I've build the kernel this way: >=20 > # cd /usr/src/ > # make clean > # rm -r /usr/obj/* > # make TARGET_TECH=3Damd64 buildworld > # make TARGET_TECH=3Damd64 buildkernel > # make TARGET_TECH=3Damd64 installkernel >=20 > New kernel freezes at startup right after enumerating hard drives... > Should I install world? How? Thanks in advance! You could try one thing: cp /libexec/ld-elf.so.1 /libexec/ld-elf32.so.1 If this allows you to boot up then you might be able to install the amd64 world on top of the i386 version. This is what I did a long time ago. Unfortunately, from other emails I've seen this is no longer possible as i386 code will not run under amd64 without some changes in the i386 libraries. Sean --=-pJwTOX1WCLXmr2RnCl78 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBsKHryQsGN30uGE4RAmRiAJ43Il2Qz0tniQ/kSnY5y3JYhH10JACdH26B 7lC2e9pTRlbDjFtNFz9VRrU= =aeFT -----END PGP SIGNATURE----- --=-pJwTOX1WCLXmr2RnCl78-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 18:10:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0A3416A4CE for ; Fri, 3 Dec 2004 18:10:42 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF8AB43D2D for ; Fri, 3 Dec 2004 18:10:40 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB3IAdRV028284 for ; Fri, 3 Dec 2004 10:10:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB3IAd9h028283 for freebsd-amd64@freebsd.org; Fri, 3 Dec 2004 10:10:39 -0800 (PST) (envelope-from obrien) Date: Fri, 3 Dec 2004 10:10:38 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20041203181038.GA27940@dragon.nuxi.com> References: <20041203085245.7DA90790094@ws1-14.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203085245.7DA90790094@ws1-14.us4.outblaze.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 18:10:42 -0000 On Fri, Dec 03, 2004 at 03:52:45AM -0500, Egor Dmitrenkov wrote: > > # cd /usr/src > > # rm -rf /usr/obj/* > > # make cleandir ; make cleandir > > # make TARGET_ARCH=amd64 buildworld > > # make KERNCONF=GENERIC TARGET_ARCH=amd64 buildkernel > > > > Will this install new kernel and world or build only? Only build. Not enough information has been given about the environment and exactly what one wants to do; so I gave no instructions about installation. The only clear things was "build an AMD64 kernel on i386 system". -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 18:12:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CF6516A4CE for ; Fri, 3 Dec 2004 18:12:38 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8AD443D2F for ; Fri, 3 Dec 2004 18:12:36 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB3ICMY9028345; Fri, 3 Dec 2004 10:12:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB3ICMxl028343; Fri, 3 Dec 2004 10:12:22 -0800 (PST) (envelope-from obrien) Date: Fri, 3 Dec 2004 10:12:21 -0800 From: "David O'Brien" To: Egor Dmitrenkov Message-ID: <20041203181221.GB27940@dragon.nuxi.com> References: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203122454.A6A12790094@ws1-14.us4.outblaze.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Kernel Build errors X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 18:12:38 -0000 On Fri, Dec 03, 2004 at 07:24:54AM -0500, Egor Dmitrenkov wrote: > Thanks, I've build the kernel this way: > > # cd /usr/src/ > # make clean > # rm -r /usr/obj/* > # make TARGET_TECH=amd64 buildworld > # make TARGET_TECH=amd64 buildkernel > # make TARGET_TECH=amd64 installkernel > > New kernel freezes at startup right after enumerating hard drives... > Should I install world? How? Thanks in advance! NO! One should stop trying to change a 32-bit installed running system into a 64-bit running system. It isn't supported, once mililiter. Download the FreeBSD/AMD64 5.3 ISO from ftp.freebsd.org and do a real 64-bit install. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 18:20:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96D2416A4CE for ; Fri, 3 Dec 2004 18:20:31 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E85C43D1F for ; Fri, 3 Dec 2004 18:20:31 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB3IKU98028617; Fri, 3 Dec 2004 10:20:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB3IKUwN028616; Fri, 3 Dec 2004 10:20:30 -0800 (PST) (envelope-from obrien) Date: Fri, 3 Dec 2004 10:20:29 -0800 From: "David O'Brien" To: Steve Kargl Message-ID: <20041203182029.GD27940@dragon.nuxi.com> References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> <20041203045849.GA15850@troutmask.apl.washington.edu> <41AFF4BF.7070503@iki.fi> <20041203060256.GA16165@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203060256.GA16165@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: FreeBSD-amd64@freebsd.org Subject: Re: OT Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 18:20:31 -0000 On Thu, Dec 02, 2004 at 10:02:56PM -0800, Steve Kargl wrote: > If you already have matlab code in house, then check out octave. > You can find it in ports/math/octave. I have been able to run > most matlab codes given to me by others with little or no changes. Have you used octave on AMD64 by chance? The port is BROKEN="Does not build on amd64 (Shared libraries must be compiled with -fPIC)" Do you have a local patch by chance? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 20:01:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C84D716A4CE for ; Fri, 3 Dec 2004 20:01:46 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D3A543D31 for ; Fri, 3 Dec 2004 20:01:46 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iB3K3Jjm019113; Fri, 3 Dec 2004 12:03:19 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iB3K3J5O019112; Fri, 3 Dec 2004 12:03:19 -0800 Date: Fri, 3 Dec 2004 12:03:19 -0800 From: Brooks Davis To: Jeffrey Katcher Message-ID: <20041203200319.GD20457@odin.ac.hmc.edu> References: <20041203063232.22547.qmail@web41102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KdquIMZPjGJQvRdI" Content-Disposition: inline In-Reply-To: <20041203063232.22547.qmail@web41102.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@FreeBSD.ORG Subject: Re: Sun W1100z Update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 20:01:46 -0000 --KdquIMZPjGJQvRdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 02, 2004 at 10:32:32PM -0800, Jeffrey Katcher wrote: > Still no luck. Is this machine useful for anything other than Linux or > Solaris? >=20 > I disabled legacy USB and even tried booting 5.2.1-RELEASE. It gets to t= he > kernel and I lose keyboard. =20 >=20 > Tidbit: at keyboard attach time on both I see something like: > device_attach: atkbd0 returned 6 Looks like you are lucky enough to have one of thsoe "helpful" systems that does just enough PS/2 emulation that you attach even when they don't exist. :-( You might try setting: hint.atkbdc.0.disabled=3D1 hint.atkbd.0.disabled=3D1 at the loader prompt. In theory that should cause the system to not even try to probe. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --KdquIMZPjGJQvRdI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBsMaHXY6L6fI4GtQRAsmtAJsEfmiOZwsfc64UiUcjvCZ+VYIqPgCgqSP7 dEEI5WgOvgVxM3YYN/eNfGE= =qQQl -----END PGP SIGNATURE----- --KdquIMZPjGJQvRdI-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 20:52:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91ECA16A4D2 for ; Fri, 3 Dec 2004 20:52:35 +0000 (GMT) Received: from web41121.mail.yahoo.com (web41121.mail.yahoo.com [66.218.94.164]) by mx1.FreeBSD.org (Postfix) with SMTP id 5296643D3F for ; Fri, 3 Dec 2004 20:52:35 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Received: (qmail 40054 invoked by uid 60001); 3 Dec 2004 20:52:35 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=AZcu5EGYIduIxj+hP1uf7H84yRnqW5M1ycG7SO5LpQccMbAyKjixV+ynxyXU5NLRh59+d8MOzohbcCtgtbH7+u9VgmfcitUdXW+vsJjbpy/809ZHS7eVvv2I/argiEqXb5jodG8Ap10d31YbWj7iXWMpuZGa1pFtTd44uvj78Dw= ; Message-ID: <20041203205235.40052.qmail@web41121.mail.yahoo.com> Received: from [67.170.88.122] by web41121.mail.yahoo.com via HTTP; Fri, 03 Dec 2004 12:52:35 PST Date: Fri, 3 Dec 2004 12:52:35 -0800 (PST) From: Jeffrey Katcher To: Brooks Davis In-Reply-To: <20041203200319.GD20457@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@FreeBSD.ORG Subject: Re: Sun W1100z Update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 20:52:35 -0000 --- Brooks Davis wrote: > Looks like you are lucky enough to have one of thsoe "helpful" systems > that does just enough PS/2 emulation that you attach even when they > don't exist. :-( You might try setting: > > hint.atkbdc.0.disabled=1 > hint.atkbd.0.disabled=1 > It doesn't probe and I don't see the atkbd messages, but still no keyboard once it reaches sysinstall. Thanks for a good suggestion, Jeff From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 22:29:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41B2B16A4CE for ; Fri, 3 Dec 2004 22:29:37 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 044E243D45 for ; Fri, 3 Dec 2004 22:29:37 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iB3MVBJ4008160; Fri, 3 Dec 2004 14:31:11 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iB3MVB7b008159; Fri, 3 Dec 2004 14:31:11 -0800 Date: Fri, 3 Dec 2004 14:31:11 -0800 From: Brooks Davis To: Jeffrey Katcher Message-ID: <20041203223111.GG20457@odin.ac.hmc.edu> References: <20041203200319.GD20457@odin.ac.hmc.edu> <20041203205235.40052.qmail@web41121.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="doKZ0ri6bHmN2Q5y" Content-Disposition: inline In-Reply-To: <20041203205235.40052.qmail@web41121.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@FreeBSD.ORG Subject: Re: Sun W1100z Update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 22:29:37 -0000 --doKZ0ri6bHmN2Q5y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 03, 2004 at 12:52:35PM -0800, Jeffrey Katcher wrote: > --- Brooks Davis wrote: > > Looks like you are lucky enough to have one of thsoe "helpful" systems > > that does just enough PS/2 emulation that you attach even when they > > don't exist. :-( You might try setting: > >=20 > > hint.atkbdc.0.disabled=3D1 > > hint.atkbd.0.disabled=3D1 > >=20 > It doesn't probe and I don't see the atkbd messages, but still no keyboar= d once > it reaches sysinstall. Hmm, are you seeing a ukbd device in dmesg? It's possiable we aren't matching your keyboard correctly. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --doKZ0ri6bHmN2Q5y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBsOkuXY6L6fI4GtQRAkE4AKDDZCROniNSIYTxys+dIdkf08z8IwCdFxL7 tZ4WiV7wjLNLgMkrLtrq/yc= =z0dc -----END PGP SIGNATURE----- --doKZ0ri6bHmN2Q5y-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 23:36:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EDC816A4CF for ; Fri, 3 Dec 2004 23:36:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDE6C43D46 for ; Fri, 3 Dec 2004 23:36:20 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so8618wra for ; Fri, 03 Dec 2004 15:36:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=qWqMb8Bmfk0wvOmrIinCZwtfaukMbyrpbH7kY5kc9F7VkMG6RPXhUBbVOFiVSRtAjfSe+b13qeF7eeP+mqJkqfMwC+6O7rcWA2CfNjMFMrZqIYi08Y/BXW91zE8xD6V4b2iEEsM5EpADPsIDq6T6H+EOjCOF161akjE5oc2KryQ= Received: by 10.54.36.75 with SMTP id j75mr36685wrj; Fri, 03 Dec 2004 15:36:20 -0800 (PST) Received: by 10.54.40.6 with HTTP; Fri, 3 Dec 2004 15:36:19 -0800 (PST) Message-ID: <2fd864e04120315362c242e3c@mail.gmail.com> Date: Fri, 3 Dec 2004 15:36:19 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20041203223111.GG20457@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041203200319.GD20457@odin.ac.hmc.edu> <20041203205235.40052.qmail@web41121.mail.yahoo.com> <20041203223111.GG20457@odin.ac.hmc.edu> Subject: Re: Sun W1100z Update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 23:36:21 -0000 You might try the patch for the R3000Z Laptop atkbdc issue. It disables the check, and leaves the driver in place. There's an ISO I posted to the list awhile back if you want to try it. --- Harrison Grundy On Fri, 3 Dec 2004 14:31:11 -0800, Brooks Davis wrote: > On Fri, Dec 03, 2004 at 12:52:35PM -0800, Jeffrey Katcher wrote: > > > > --- Brooks Davis wrote: > > > Looks like you are lucky enough to have one of thsoe "helpful" systems > > > that does just enough PS/2 emulation that you attach even when they > > > don't exist. :-( You might try setting: > > > > > > hint.atkbdc.0.disabled=1 > > > hint.atkbd.0.disabled=1 > > > > > It doesn't probe and I don't see the atkbd messages, but still no keyboard once > > it reaches sysinstall. > > Hmm, are you seeing a ukbd device in dmesg? It's possiable we aren't > matching your keyboard correctly. > > > > -- Brooks > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 > > > From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 3 23:56:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A210816A4CE for ; Fri, 3 Dec 2004 23:56:23 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75DFA43D5D for ; Fri, 3 Dec 2004 23:56:23 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0I86001YS7QDW9@VL-MO-MR011.ip.videotron.ca> for freebsd-amd64@freebsd.org; Fri, 03 Dec 2004 18:54:14 -0500 (EST) Date: Fri, 03 Dec 2004 18:54:12 -0500 From: Nicolas Blais To: freebsd-amd64@freebsd.org Message-id: <200412031854.12801.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.1 Subject: Compaq R3000 Series X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 23:56:23 -0000 Hi, I would like to know what the situation is with the Compaq/HP R3000 Series problem at boot with 5-STABLE. Was the patch to at least get it booted commited to -STABLE and/or CURRENT ? I tried the mini-inst iso and it worked fine (without ACPI), but I would like to have a src tree up to date without having to repatch the source everytime I cvsup. I am anxiously waiting to install FreeBSD on both my laptops.... Thank you for your answers, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 00:14:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E3DE16A4CE for ; Sat, 4 Dec 2004 00:14:10 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id C265C43D46 for ; Sat, 4 Dec 2004 00:14:09 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so33130wra for ; Fri, 03 Dec 2004 16:14:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=erHsYdNqxWKBnBHvPmtq2n6hbFhd4ojjy14HTChjoLqmlY51lo+YFQ2/YV/+oZUBDX/d6//n/4uRVjgvLEaIavXHbTZYtJnRlMjnrRDaFzU1RiAq2iDf+RgTN97yHJmUNrshW+DtEJjkG8vzr++vSQvQ0moMbXq7/8DZtSl8QC0= Received: by 10.54.50.6 with SMTP id x6mr53240wrx; Fri, 03 Dec 2004 16:14:08 -0800 (PST) Received: by 10.54.40.6 with HTTP; Fri, 3 Dec 2004 16:14:08 -0800 (PST) Message-ID: <2fd864e04120316146f857c93@mail.gmail.com> Date: Fri, 3 Dec 2004 16:14:08 -0800 From: Astrodog To: Nicolas Blais In-Reply-To: <200412031854.12801.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200412031854.12801.nb_root@videotron.ca> cc: freebsd-amd64@freebsd.org Subject: Re: Compaq R3000 Series X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 00:14:10 -0000 On Fri, 03 Dec 2004 18:54:12 -0500, Nicolas Blais wrote: > Hi, > > I would like to know what the situation is with the Compaq/HP R3000 Series > problem at boot with 5-STABLE. Was the patch to at least get it booted > commited to -STABLE and/or CURRENT ? I tried the mini-inst iso and it worked > fine (without ACPI), but I would like to have a src tree up to date without > having to repatch the source everytime I cvsup. > I am anxiously waiting to install FreeBSD on both my laptops.... > > Thank you for your answers, > Nicolas. > _______________________________________________ > 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" > Stuck with the same wait myself. The fix is, currently, uncommitable since its unknown what effect it would have on some platforms. Or thats the last I heard about it. I'm currently starting on the ACPI stuff, hopefully I'll have an ISO up for that after awhile. Be aware that with ACPI disabled, the machine will kernel panic when any power management stuff is used. (Closing the lid, plugging it in, unplugging, etc) HP/Compaq was not able to direct me to a resource outlining how to disable ACPI on the BIOS, so we're stuck just trying to make it work... any thoughts on that would be mostly appreiated as well. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 00:47:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F054D16A4CE for ; Sat, 4 Dec 2004 00:47:27 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id C765843D2F for ; Sat, 4 Dec 2004 00:47:27 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB40lRhQ020820 for ; Fri, 3 Dec 2004 16:47:27 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB40lRRa020819 for freebsd-amd64@freebsd.org; Fri, 3 Dec 2004 16:47:27 -0800 (PST) (envelope-from sgk) Date: Fri, 3 Dec 2004 16:47:27 -0800 From: Steve Kargl To: freebsd-amd64@freebsd.org Message-ID: <20041204004727.GA20786@troutmask.apl.washington.edu> References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> <20041203045849.GA15850@troutmask.apl.washington.edu> <41AFF4BF.7070503@iki.fi> <20041203060256.GA16165@troutmask.apl.washington.edu> <20041203182029.GD27940@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203182029.GD27940@dragon.nuxi.com> User-Agent: Mutt/1.4.1i Subject: Re: OT Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 00:47:28 -0000 On Fri, Dec 03, 2004 at 10:20:29AM -0800, David O'Brien wrote: > On Thu, Dec 02, 2004 at 10:02:56PM -0800, Steve Kargl wrote: > > If you already have matlab code in house, then check out octave. > > You can find it in ports/math/octave. I have been able to run > > most matlab codes given to me by others with little or no changes. > > Have you used octave on AMD64 by chance? The port is > BROKEN="Does not build on amd64 (Shared libraries must be > compiled with -fPIC)" Do you have a local patch by chance? > I built it outside of the ports system. Simply downloaded the tarball and let configure build the Makefile. octave appears to work, but I haven't really pushed it very hard. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 05:23:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC3B016A4CE for ; Sat, 4 Dec 2004 05:23:37 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ECBD43D5D for ; Sat, 4 Dec 2004 05:23:35 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB45NVt5064218; Fri, 3 Dec 2004 21:23:31 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB45NUA4064217; Fri, 3 Dec 2004 21:23:30 -0800 (PST) (envelope-from obrien) Date: Fri, 3 Dec 2004 21:23:30 -0800 From: "David O'Brien" To: Nicolas Blais Message-ID: <20041204052330.GA62430@dragon.nuxi.com> References: <200412031854.12801.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412031854.12801.nb_root@videotron.ca> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Compaq R3000 Series X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 05:23:38 -0000 On Fri, Dec 03, 2004 at 06:54:12PM -0500, Nicolas Blais wrote: > I would like to know what the situation is with the Compaq/HP R3000 Series > problem at boot with 5-STABLE. Was the patch to at least get it booted > commited to -STABLE and/or CURRENT? If the patch you're refering to the keyboard related patch, no it hasn't. Someone that experiences the problem needs to take the patch that is floating around and make it commitable. This means rather than cutting out the code that the patch does, it is wrapped around a loader tunable so it only gets turned off on these laptops. Or someone needs to go read the code and explain why removing that section makes a difference (ie, understand what is really going on), and make an argument that removing that code is OK for the rest of the world that isn't experiencing the problem. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 06:49:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 455D816A4CE for ; Sat, 4 Dec 2004 06:49:16 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9130F43D41 for ; Sat, 4 Dec 2004 06:49:15 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so6808wri for ; Fri, 03 Dec 2004 22:48:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=qw4hH4nlXm0GcRow4jTOzGofOnHh55UJ+jB7+OhWXK1HNAi+32l8aKUgZ81EJ2hBJvHH7XzRslZ5N6kPnWnQYoESyHTz/Mxd385HltJ4lXZOTKGksUVOQa6cMKpqdhrksPmLAXAZl11FvBN9mih6F+E0cKYF2a2ksGGCM/i7KVI= Received: by 10.54.31.33 with SMTP id e33mr188419wre; Fri, 03 Dec 2004 22:48:58 -0800 (PST) Received: by 10.54.40.6 with HTTP; Fri, 3 Dec 2004 22:48:58 -0800 (PST) Message-ID: <2fd864e04120322487e1f235d@mail.gmail.com> Date: Fri, 3 Dec 2004 22:48:58 -0800 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20041204052330.GA62430@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200412031854.12801.nb_root@videotron.ca> <20041204052330.GA62430@dragon.nuxi.com> Subject: Re: Compaq R3000 Series X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 06:49:16 -0000 On Fri, 3 Dec 2004 21:23:30 -0800, David O'Brien wrote: > On Fri, Dec 03, 2004 at 06:54:12PM -0500, Nicolas Blais wrote: > > I would like to know what the situation is with the Compaq/HP R3000 Series > > problem at boot with 5-STABLE. Was the patch to at least get it booted > > commited to -STABLE and/or CURRENT? > > If the patch you're refering to the keyboard related patch, no it hasn't. > > Someone that experiences the problem needs to take the patch that is > floating around and make it commitable. This means rather than cutting > out the code that the patch does, it is wrapped around a loader tunable > so it only gets turned off on these laptops. > > Or someone needs to go read the code and explain why removing that > section makes a difference (ie, understand what is really going on), and > make an argument that removing that code is OK for the rest of the world > that isn't experiencing the problem. > > -- > -- David (obrien@FreeBSD.org) > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > There are 3 working patches out now, the first being the #if 1 one I used to build that ISO. There's also aparently the flags one, listed on the PR, and the hints one I made awhile back. The code in question, that causes the bug sends a command to the keyboard controller to test the status of the port. The potential bug I can see cropping up with just removing the code is the failure of anything that relies on actually testing the keyboard port. That might extend to some com port console things. To avoid that protential problem for everyone else, and still let R3000Z users actually use their laptops with FreeBSD, without a 2 line fork, I think the flags fix, listed in the PR might be the best solution, atleast for the time being. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 07:24:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F16A16A4CE for ; Sat, 4 Dec 2004 07:24:31 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F65C43D64 for ; Sat, 4 Dec 2004 07:24:31 +0000 (GMT) (envelope-from james@jrv.org) Received: from [127.0.0.1] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iB47OSPP035828 for ; Sat, 4 Dec 2004 01:24:30 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41B1662C.6050907@jrv.org> Date: Sat, 04 Dec 2004 01:24:28 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Success with NIC em(4) / Intel Pro/1000? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 07:24:31 -0000 Has anyone had success with the Intel Pro/1000 NIC, driver em(4), on amd64? I tried one in a Tyan S885 dual CPU system and while the driver detects whether the network cable is installed, no packets seem to pass through the card. The card is a dual-port PWLA8492MT. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 08:03:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5D2316A4CE for ; Sat, 4 Dec 2004 08:03:44 +0000 (GMT) Received: from dglawrence.com (c-24-21-223-117.client.comcast.net [24.21.223.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B9EC43D45 for ; Sat, 4 Dec 2004 08:03:44 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id iB483iYa017560; Sat, 4 Dec 2004 00:03:44 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.1/8.13.1/Submit) id iB483hoF017559; Sat, 4 Dec 2004 00:03:43 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Sat, 4 Dec 2004 00:03:43 -0800 From: "David G. Lawrence" To: "James R. Van Artsalen" Message-ID: <20041204080343.GD3714@opteron.dglawrence.com> References: <41B1662C.6050907@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41B1662C.6050907@jrv.org> cc: freebsd-amd64@freebsd.org Subject: Re: Success with NIC em(4) / Intel Pro/1000? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 08:03:44 -0000 > Has anyone had success with the Intel Pro/1000 NIC, driver em(4), on amd64? Yes, I'm using one in a Tyan S2882. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 08:37:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EEC616A4CE for ; Sat, 4 Dec 2004 08:37:58 +0000 (GMT) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9995443D60 for ; Sat, 4 Dec 2004 08:37:57 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr14.xs4all.nl (8.12.11/8.12.11) with ESMTP id iB48bu4u010737 for ; Sat, 4 Dec 2004 09:37:56 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id DB1E6635E; Sat, 4 Dec 2004 09:38:10 +0100 (CET) Date: Sat, 4 Dec 2004 09:38:10 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041204083810.GA27700@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041203011408.163FE106C28@FreeBSD.csie.NCTU.edu.tw> <20041203045849.GA15850@troutmask.apl.washington.edu> <41AFF4BF.7070503@iki.fi> <20041203060256.GA16165@troutmask.apl.washington.edu> <20041203182029.GD27940@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <20041203182029.GD27940@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: OT Re: AMD64- Solutions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 08:37:58 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 03, 2004 at 10:20:29AM -0800, David O'Brien wrote: > On Thu, Dec 02, 2004 at 10:02:56PM -0800, Steve Kargl wrote: > > If you already have matlab code in house, then check out octave. > > You can find it in ports/math/octave. I have been able to run=20 > > most matlab codes given to me by others with little or no changes. >=20 > Have you used octave on AMD64 by chance? The port is > BROKEN=3D"Does not build on amd64 (Shared libraries must be compiled with= -fPIC)" > Do you have a local patch by chance? I've used the patch to the makefile included below to build it from ports. ------------------------ octave-mak.patch ------------------------ --- Makefile.orig Fri Dec 3 20:36:40 2004 +++ Makefile Sat Dec 4 09:05:08 2004 @@ -23,10 +23,6 @@ =20 .include =20 -.if ${ARCH} =3D=3D "amd64" -BROKEN=3D "Does not build on amd64 (Shared libraries must be compiled wit= h -fPIC)" -.endif - .if ${PORTOBJFORMAT} =3D=3D "elf" GNU_HOST=3D ${ARCH}-portbld-freebsd${OSREL} .else @@ -38,11 +34,15 @@ BLAS_LIBS=3D "-L${LOCALBASE}/lib -lf77blas -lcblas -latlas" USE_GMAKE=3D yes GNU_CONFIGURE=3D yes -USE_REINPLACE=3D yes =20 -CONFIGURE_ARGS=3D --host=3D${GNU_HOST} \ - --with-fftw --with-blas=3D${BLAS_LIBS} --with-lapack=3D-lalapack \ - --enable-shared +CONIGURE_ARGS=3D --host=3D${GNU_HOST} \ + --with-fftw --with-blas=3D${BLAS_LIBS} --with-lapack=3D-lalapack +.if ${ARCH} =3D=3D "amd64" +CONFIGURE_ARGS+=3D --disable-shared +.else +CONFIGURE_ARGS+=3D --enable-shared +.endif + CONFIGURE_ENV=3D CFLAGS=3D"${CFLAGS} -I${LOCALBASE}/include" \ LDFLAGS=3D"${LDFLAGS} -L${LOCALBASE}/lib" \ CPPFLAGS=3D"${CPPFLAGS} -I${LOCALBASE}/include" \ @@ -62,12 +62,6 @@ @${RM} -f ${WRKSRC}/doc/interpreter/octave.info* @${RM} -f ${WRKSRC}/doc/liboctave/liboctave.info* post-install: - ${RM} ${PREFIX}/bin/octave - @${CP} ${FILESDIR}/octave ${WRKDIR} - @${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX},g ; \ - s,%%OCTAVE_VERSION%%,${OCTAVE_VERSION},g' \ - ${WRKDIR}/octave - ${INSTALL_SCRIPT} ${WRKDIR}/octave ${PREFIX}/bin ${INSTALL_DATA} ${WRKSRC}/doc/liboctave/liboctave.info ${PREFIX}/info install-info --entry=3D'* Octave: (octave). Interactive language for nume= rical computations.' $(PREFIX)/info/octave.info $(PREFIX)/info/dir install-info --entry=3D'* LibOctave: (liboctave). C++ class library for O= ctave.' $(PREFIX)/info/liboctave.info $(PREFIX)/info/dir ------------------------ octave-mak.patch ------------------------ --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBsXdyEnfvsMMhpyURAtwyAJ9C4tDGRCfoAb/1mmt4Ao1mE7ualQCeK2dl GQKdjI19Z2hj12LfUyUxeHo= =NzYF -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 03:03:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAFE616A4CE for ; Sat, 4 Dec 2004 03:03:02 +0000 (GMT) Received: from smtp4.info.com.ph (smtp4.info.com.ph [202.57.96.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99EB643D5F for ; Sat, 4 Dec 2004 03:03:01 +0000 (GMT) (envelope-from ian@avescormotors.com) Received: from smtp2.info.com.ph (smtp2.info.com.ph [202.57.96.78]) by smtp4.info.com.ph (8.11.6/8.11.6) with ESMTP id iB43HIB25414 for ; Sat, 4 Dec 2004 11:17:18 +0800 Received: from avescorxc08krm (smtp2.info.com.ph [127.0.0.1]) by smtp2.info.com.ph (8.11.6/8.11.6) with ESMTP id iB4EqZt01981 for ; Sat, 4 Dec 2004 09:52:35 -0500 From: "Ian Bautista" To: Date: Sat, 4 Dec 2004 11:03:14 +0800 Message-ID: <002201c4d9ad$cca48480$6402a8c0@avescorxc08krm> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300 Importance: Normal X-Mailman-Approved-At: Sat, 04 Dec 2004 12:45:06 +0000 Subject: APC usbd X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 03:03:02 -0000 Gentlemen, Does anybody have an idea how to implement apcusbd? From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 14:00:47 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 200E516A4CE for ; Sat, 4 Dec 2004 14:00:47 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4B9B43D6A for ; Sat, 4 Dec 2004 14:00:45 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB4E0jTO036276 for ; Sat, 4 Dec 2004 14:00:45 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB4E0j9H036268; Sat, 4 Dec 2004 14:00:45 GMT (envelope-from gnats) Resent-Date: Sat, 4 Dec 2004 14:00:45 GMT Resent-Message-Id: <200412041400.iB4E0j9H036268@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, Roland Smith Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 501F116A4CE for ; Sat, 4 Dec 2004 13:54:09 +0000 (GMT) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFCAC43D62 for ; Sat, 4 Dec 2004 13:54:08 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) iB4Ds7hx024778 for ; Sat, 4 Dec 2004 14:54:07 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 75EC1635E; Sat, 4 Dec 2004 14:54:23 +0100 (CET) Message-Id: <20041204135423.75EC1635E@slackbox.xs4all.nl> Date: Sat, 4 Dec 2004 14:54:23 +0100 (CET) From: Roland Smith To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Roland Smith List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 14:00:47 -0000 >Number: 74669 >Category: amd64 >Synopsis: The port math/octave is marked BROKEN on amd64 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Dec 04 14:00:45 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Roland Smith >Release: FreeBSD 5.3-RELEASE amd64 >Organization: none >Environment: >Description: The port math/octave is marked BROKEN on amd64. >How-To-Repeat: >Fix: This patch works around the breakage by configuring octave with --disable-shared. This makes for a large executable, but the program works. --- octave-mak.patch begins here --- --- Makefile.orig Fri Dec 3 20:36:40 2004 +++ Makefile Sat Dec 4 10:43:13 2004 @@ -23,10 +23,6 @@ .include -.if ${ARCH} == "amd64" -BROKEN= "Does not build on amd64 (Shared libraries must be compiled with -fPIC)" -.endif - .if ${PORTOBJFORMAT} == "elf" GNU_HOST= ${ARCH}-portbld-freebsd${OSREL} .else @@ -38,11 +34,16 @@ BLAS_LIBS= "-L${LOCALBASE}/lib -lf77blas -lcblas -latlas" USE_GMAKE= yes GNU_CONFIGURE= yes -USE_REINPLACE= yes -CONFIGURE_ARGS= --host=${GNU_HOST} \ - --with-fftw --with-blas=${BLAS_LIBS} --with-lapack=-lalapack \ - --enable-shared +CONIGURE_ARGS= --host=${GNU_HOST} \ + --with-fftw --with-blas=${BLAS_LIBS} --with-lapack=-lalapack +.if ${ARCH} == "amd64" +CONFIGURE_ARGS+= --disable-shared +.else +CONFIGURE_ARGS+= --enable-shared +USE_REINPLACE= yes +.endif + CONFIGURE_ENV= CFLAGS="${CFLAGS} -I${LOCALBASE}/include" \ LDFLAGS="${LDFLAGS} -L${LOCALBASE}/lib" \ CPPFLAGS="${CPPFLAGS} -I${LOCALBASE}/include" \ @@ -62,12 +63,14 @@ @${RM} -f ${WRKSRC}/doc/interpreter/octave.info* @${RM} -f ${WRKSRC}/doc/liboctave/liboctave.info* post-install: +.if ${ARCH} != "amd64" ${RM} ${PREFIX}/bin/octave @${CP} ${FILESDIR}/octave ${WRKDIR} @${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX},g ; \ s,%%OCTAVE_VERSION%%,${OCTAVE_VERSION},g' \ ${WRKDIR}/octave ${INSTALL_SCRIPT} ${WRKDIR}/octave ${PREFIX}/bin +.endif ${INSTALL_DATA} ${WRKSRC}/doc/liboctave/liboctave.info ${PREFIX}/info install-info --entry='* Octave: (octave). Interactive language for numerical computations.' $(PREFIX)/info/octave.info $(PREFIX)/info/dir install-info --entry='* LibOctave: (liboctave). C++ class library for Octave.' $(PREFIX)/info/liboctave.info $(PREFIX)/info/dir --- octave-mak.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: >System: FreeBSD slackbox.xs4all.nl 5.3-RELEASE FreeBSD 5.3-RELEASE #8: Wed Dec 1 22:24:03 CET 2004 rsmith@slackbox.xs4all.nl:/usr/src/sys/amd64/compile/RFS_1 amd64 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 14:30:29 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8FF916A4CE for ; Sat, 4 Dec 2004 14:30:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D260443D5D for ; Sat, 4 Dec 2004 14:30: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.1/8.13.1) with ESMTP id iB4EUTRu040987 for ; Sat, 4 Dec 2004 14:30:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB4EUT4V040986; Sat, 4 Dec 2004 14:30:29 GMT (envelope-from gnats) Date: Sat, 4 Dec 2004 14:30:29 GMT Message-Id: <200412041430.iB4EUT4V040986@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Conrad J. Sabatier" Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Conrad J. Sabatier" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 14:30:30 -0000 The following reply was made to PR amd64/74669; it has been noted by GNATS. From: "Conrad J. Sabatier" To: Roland Smith Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 Date: Sat, 04 Dec 2004 08:27:28 -0600 On Sat, 2004-12-04 at 14:54 +0100, Roland Smith wrote: > >Number: 74669 > >Category: amd64 > >Synopsis: The port math/octave is marked BROKEN on amd64 > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Sat Dec 04 14:00:45 GMT 2004 > >Closed-Date: > >Last-Modified: > >Originator: Roland Smith > >Release: FreeBSD 5.3-RELEASE amd64 > >Organization: > none > >Environment: > >Description: > The port math/octave is marked BROKEN on amd64. > > >How-To-Repeat: > >Fix: > This patch works around the breakage by configuring octave with > --disable-shared. This makes for a large executable, but the > program works. A better fix would be to determine exactly where -fPIC is needed and apply patches where appropriate, but this is fine for a "quick fix". > --- octave-mak.patch begins here --- > --- Makefile.orig Fri Dec 3 20:36:40 2004 > +++ Makefile Sat Dec 4 10:43:13 2004 > @@ -23,10 +23,6 @@ > > .include > > -.if ${ARCH} == "amd64" > -BROKEN= "Does not build on amd64 (Shared libraries must be compiled with -fPIC)" > -.endif -- Conrad J. Sabatier -- conrads@cox.net -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 17:04:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9BB116A4CF; Sat, 4 Dec 2004 17:04:00 +0000 (GMT) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id F018643D60; Sat, 4 Dec 2004 17:03:59 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr6.xs4all.nl (8.12.11/8.12.11) with ESMTP id iB4H3s5p009893; Sat, 4 Dec 2004 18:03:54 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id DF38D63D3; Sat, 4 Dec 2004 18:04:10 +0100 (CET) Date: Sat, 4 Dec 2004 18:04:10 +0100 From: Roland Smith To: "Conrad J. Sabatier" Message-ID: <20041204170410.GA57662@slackbox.xs4all.nl> Mail-Followup-To: "Conrad J. Sabatier" , FreeBSD-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org References: <20041204135423.75EC1635E@slackbox.xs4all.nl> <1102170448.36385.8.camel@dolphin.local.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline In-Reply-To: <1102170448.36385.8.camel@dolphin.local.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner cc: FreeBSD-gnats-submit@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 17:04:01 -0000 --TRYliJ5NKNqkz5bu Content-Type: multipart/mixed; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 04, 2004 at 08:27:28AM -0600, Conrad J. Sabatier wrote: > > A better fix would be to determine exactly where -fPIC is needed and > apply patches where appropriate, but this is fine for a "quick fix". Ok, I've looked into it, and the problem seems to be in the libglob that is included in octave. When libglob.a is linked into liboctave.so, the linking fails because libglob isn't compiled with -fPIC. Included is a new patch for blob's Makefile.in, which should go in files. Also included is a new patch for the ports Makefile, removing the BROKEN state for octave. Unfortunately I can only test this myself on amd64. Could someone confirm that this doesn't hurt on other platforms, especially i386? Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-glob:makefile.in" Content-Transfer-Encoding: quoted-printable --- glob/Makefile.in.orig Sat Dec 4 16:59:54 2004 +++ glob/Makefile.in Sat Dec 4 17:00:04 2004 @@ -25,7 +25,7 @@ =20 CC =3D @CC@ CPPFLAGS =3D @CPPFLAGS@ -CFLAGS =3D @CFLAGS@ +CFLAGS =3D @CFLAGS@ -fPIC =20 # Information determined by configure. DEFS =3D @DEFS@ --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="octave-makefile.patch" Content-Transfer-Encoding: quoted-printable --- Makefile.orig Fri Dec 3 20:36:40 2004 +++ Makefile Sat Dec 4 16:57:35 2004 @@ -23,10 +23,6 @@ =20 .include =20 -.if ${ARCH} =3D=3D "amd64" -BROKEN=3D "Does not build on amd64 (Shared libraries must be compiled wit= h -fPIC)" -.endif - .if ${PORTOBJFORMAT} =3D=3D "elf" GNU_HOST=3D ${ARCH}-portbld-freebsd${OSREL} .else --+QahgC5+KEYLbs62-- --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBse4KEnfvsMMhpyURAuMtAJ0akVnVxG8a/6xngzKy37Z/+wPTVACgnHhW MhTpQR5cIWKl6mUY+ejaSk4= =qk/E -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 17:10:38 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49DA216A4EA for ; Sat, 4 Dec 2004 17:10:38 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7ABB43D1D for ; Sat, 4 Dec 2004 17:10:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB4HAboc060385 for ; Sat, 4 Dec 2004 17:10:37 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB4HAblZ060384; Sat, 4 Dec 2004 17:10:37 GMT (envelope-from gnats) Date: Sat, 4 Dec 2004 17:10:37 GMT Message-Id: <200412041710.iB4HAblZ060384@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Roland Smith Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Roland Smith List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 17:10:38 -0000 The following reply was made to PR amd64/74669; it has been noted by GNATS. From: Roland Smith To: "Conrad J. Sabatier" Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 Date: Sat, 4 Dec 2004 18:04:10 +0100 --TRYliJ5NKNqkz5bu Content-Type: multipart/mixed; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 04, 2004 at 08:27:28AM -0600, Conrad J. Sabatier wrote: > > A better fix would be to determine exactly where -fPIC is needed and > apply patches where appropriate, but this is fine for a "quick fix". Ok, I've looked into it, and the problem seems to be in the libglob that is included in octave. When libglob.a is linked into liboctave.so, the linking fails because libglob isn't compiled with -fPIC. Included is a new patch for blob's Makefile.in, which should go in files. Also included is a new patch for the ports Makefile, removing the BROKEN state for octave. Unfortunately I can only test this myself on amd64. Could someone confirm that this doesn't hurt on other platforms, especially i386? Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-glob:makefile.in" Content-Transfer-Encoding: quoted-printable --- glob/Makefile.in.orig Sat Dec 4 16:59:54 2004 +++ glob/Makefile.in Sat Dec 4 17:00:04 2004 @@ -25,7 +25,7 @@ =20 CC =3D @CC@ CPPFLAGS =3D @CPPFLAGS@ -CFLAGS =3D @CFLAGS@ +CFLAGS =3D @CFLAGS@ -fPIC =20 # Information determined by configure. DEFS =3D @DEFS@ --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="octave-makefile.patch" Content-Transfer-Encoding: quoted-printable --- Makefile.orig Fri Dec 3 20:36:40 2004 +++ Makefile Sat Dec 4 16:57:35 2004 @@ -23,10 +23,6 @@ =20 .include =20 -.if ${ARCH} =3D=3D "amd64" -BROKEN=3D "Does not build on amd64 (Shared libraries must be compiled wit= h -fPIC)" -.endif - .if ${PORTOBJFORMAT} =3D=3D "elf" GNU_HOST=3D ${ARCH}-portbld-freebsd${OSREL} .else --+QahgC5+KEYLbs62-- --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBse4KEnfvsMMhpyURAuMtAJ0akVnVxG8a/6xngzKy37Z/+wPTVACgnHhW MhTpQR5cIWKl6mUY+ejaSk4= =qk/E -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 19:40:35 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 990D216A4CE for ; Sat, 4 Dec 2004 19:40:35 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7410243D60 for ; Sat, 4 Dec 2004 19:40:35 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB4JeZhb077175 for ; Sat, 4 Dec 2004 19:40:35 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB4JeZGP077174; Sat, 4 Dec 2004 19:40:35 GMT (envelope-from gnats) Date: Sat, 4 Dec 2004 19:40:35 GMT Message-Id: <200412041940.iB4JeZGP077174@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Avtar Gill Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Avtar Gill List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 19:40:35 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Avtar Gill To: freebsd-gnats-submit@FreeBSD.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Sat, 4 Dec 2004 14:37:02 -0500 I just tried booting a FreeBSD 5.3 RELEASE iso for the amd64 platform on a Compaq R3320CA laptop and experienced the same boot problem. The laptop shuts down after hanging for a couple minutes at the boot spinner (/-\|). From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 4 22:00:54 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF1DF16A4CE for ; Sat, 4 Dec 2004 22:00:54 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEFA043D5D for ; Sat, 4 Dec 2004 22:00:54 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB4M0sTW090722 for ; Sat, 4 Dec 2004 22:00:54 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB4M0sX7090721; Sat, 4 Dec 2004 22:00:54 GMT (envelope-from gnats) Date: Sat, 4 Dec 2004 22:00:54 GMT Message-Id: <200412042200.iB4M0sX7090721@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "David O'Brien" Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 22:00:54 -0000 The following reply was made to PR amd64/74669; it has been noted by GNATS. From: "David O'Brien" To: Roland Smith Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: amd64/74669: The port math/octave is marked BROKEN on amd64 Date: Sat, 4 Dec 2004 13:59:26 -0800 On Sat, Dec 04, 2004 at 02:54:23PM +0100, Roland Smith wrote: > post-install: > +.if ${ARCH} != "amd64" > ${RM} ${PREFIX}/bin/octave > @${CP} ${FILESDIR}/octave ${WRKDIR} > @${REINPLACE_CMD} -e 's,%%PREFIX%%,${PREFIX},g ; \ > s,%%OCTAVE_VERSION%%,${OCTAVE_VERSION},g' \ > ${WRKDIR}/octave > ${INSTALL_SCRIPT} ${WRKDIR}/octave ${PREFIX}/bin > +.endif Why does building statically vs. dynamically require this change? -- -- David (obrien@FreeBSD.org)