From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 25 23:10:38 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1555E16A417; Sat, 25 Nov 2006 23:10:38 +0000 (UTC) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F3D43D92; Sat, 25 Nov 2006 23:09:41 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net via brakkenstein.nijmegen.internl.net [217.149.193.41] with ESMTP id kAPNAUTx014769 (8.13.4/1.4); Sun, 26 Nov 2006 00:10:30 +0100 (MET) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP id kAPNAUIX013515 (8.13.2/2.02); Sun, 26 Nov 2006 00:10:30 +0100 (MET) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Sun, 26 Nov 2006 00:10:30 +0100 (MET) From: Michiel Boland To: John Baldwin In-Reply-To: <200611131550.50648.jhb@freebsd.org> Message-ID: References: <200611131550.50648.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2006 23:10:38 -0000 On Mon, 13 Nov 2006, John Baldwin wrote: > On Monday 13 November 2006 15:12, Michiel Boland wrote: >>> Yeah, the X4100 has an mpt(4) controller. Mine is running the original > BIOS >>> release (6464), and runs FreeBSD fine. You can try fiddling with the BIOS >>> revision by downloading replacements from Sun's website. >> >> As far as I can see there are no other BIOSes on the Sun website other >> than what the box is already running (ILOM 1.0.7 - I understand ILOM and >> BIOS are linked for 4100s) >> >> I am a bit puzzled why solaris and fedora do not have these problems on >> this hardware. Oh well... > > The real mode breakpoint handler may just ignore breakpoints, or the BIOS > takes a different codepath when it runs in vm86 mode. The code path is the same. The bios calls INT3 if someone tries to load a block with LBA < 16, or LBA 64 or 65. (I think - my asm skills are a bit rusty.) Is there not a way for BTX to ignore these INT3 interrupts? Obviously they are ignored in real mode too. Cheers Michiel From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 26 17:20:10 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5934D16A4AB; Sun, 26 Nov 2006 17:20:10 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3054E43EBD; Sun, 26 Nov 2006 17:17:45 +0000 (GMT) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (xs6.xs4all.nl [194.109.21.6]) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with ESMTP id kAQHIcZR052647; Sun, 26 Nov 2006 18:18:39 +0100 (CET) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (boland37@localhost [127.0.0.1]) by xs6.xs4all.nl (8.13.6/8.13.6) with ESMTP id kAQHIc1B020480; Sun, 26 Nov 2006 18:18:38 +0100 (CET) (envelope-from michiel@boland.org) Received: from localhost (boland37@localhost) by xs6.xs4all.nl (8.13.6/8.13.6/Submit) with ESMTP id kAQHIbMQ020477; Sun, 26 Nov 2006 18:18:38 +0100 (CET) (envelope-from michiel@boland.org) X-Authentication-Warning: xs6.xs4all.nl: boland37 owned process doing -bs Date: Sun, 26 Nov 2006 18:18:37 +0100 (CET) From: Michiel Boland X-X-Sender: boland37@xs6.xs4all.nl To: John Baldwin In-Reply-To: Message-ID: <20061126181325.O13925-100000@xs6.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2006 17:20:10 -0000 Ok here is a patch for /sys/boot/i386/btx/btx/btx.S that will get X4100s to boot. It extends the v86 monitor in the BTX so that it catches INT3 and treats it like any other interrupt. Not sure if it's a great idea, but it's better than nothing at this point. You will need to update the bootblock and /boot/loader since they both appear to be linking in their own copy of BTX. --- btx.S.orig Thu Oct 5 17:30:51 2006 +++ btx.S Sun Nov 26 16:26:12 2006 @@ -510,6 +510,8 @@ je v86popf # Yes cmpb $0xcd,%al # INT imm8? je v86intn # Yes + cmpb $0xcc,%al # INT3? + je v86int3 # Yes cmpb $0xcf,%al # IRET/IRETD? je v86iret # Yes popl %ebx # Restore @@ -651,6 +653,11 @@ reboot: orb $0x1,btx_hdr+0x7 # Set the reboot flag jmp exit # Terminate BTX and reboot +/* + * Emulate INT3 + */ +v86int3: movb $3,%al + jmp v86intn.1 /* * Emulate INT imm8... also make sure to check if it's int 15/87 */ From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 26 21:01:09 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C5A016A407; Sun, 26 Nov 2006 21:01:09 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 584F843D62; Sun, 26 Nov 2006 20:59:59 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id kAQL0sM3015749; Sun, 26 Nov 2006 16:00:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.13.8/8.13.8) with ESMTP id kAQL0sgV066239; Sun, 26 Nov 2006 16:00:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 69704241BF; Sun, 26 Nov 2006 16:00:54 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061126210054.69704241BF@freebsd-stable.sentex.ca> Date: Sun, 26 Nov 2006 16:00:54 -0500 (EST) X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [releng_6_2 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2006 21:01:09 -0000 TB --- 2006-11-26 20:50:43 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2006-11-26 20:50:43 - starting RELENG_6_2 tinderbox run for amd64/amd64 TB --- 2006-11-26 20:50:43 - cleaning the object tree TB --- 2006-11-26 20:50:43 - checking out the source tree TB --- 2006-11-26 20:50:43 - cd /tinderbox/RELENG_6_2/amd64/amd64 TB --- 2006-11-26 20:50:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6_2 src TB --- 2006-11-26 21:00:54 - WARNING: /usr/bin/cvs returned exit code 1 TB --- 2006-11-26 21:00:54 - ERROR: unable to check out the source tree TB --- 2006-11-26 21:00:54 - tinderbox aborted TB --- 0.05 user 0.00 system 610.68 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6_2-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 26 23:18:19 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC29F16A403; Sun, 26 Nov 2006 23:18:19 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D311443D80; Sun, 26 Nov 2006 23:17:19 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id kAQNIFRG057393; Sun, 26 Nov 2006 18:18:15 -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.8/8.13.8) with ESMTP id kAQNIFJg083339; Sun, 26 Nov 2006 18:18:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 46DD373068; Sun, 26 Nov 2006 18:18:15 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20061126231815.46DD373068@freebsd-current.sentex.ca> Date: Sun, 26 Nov 2006 18:18:15 -0500 (EST) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2006 23:18:19 -0000 TB --- 2006-11-26 21:45:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-11-26 21:45:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-11-26 21:45:01 - cleaning the object tree TB --- 2006-11-26 21:46:52 - checking out the source tree TB --- 2006-11-26 21:46:52 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-11-26 21:46:52 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-11-26 21:59:48 - building world (CFLAGS=-O2 -pipe) TB --- 2006-11-26 21:59:48 - cd /src TB --- 2006-11-26 21:59:48 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 26 21:59:51 UTC 2006 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Nov 26 23:17:54 UTC 2006 TB --- 2006-11-26 23:17:55 - generating LINT kernel config TB --- 2006-11-26 23:17:55 - cd /src/sys/amd64/conf TB --- 2006-11-26 23:17:55 - /usr/bin/make -B LINT TB --- 2006-11-26 23:17:55 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-11-26 23:17:55 - cd /src TB --- 2006-11-26 23:17:55 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 26 23:17:55 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> wlan_acl (cleandir) rm -f export_syms wlan_acl.ko wlan_acl.kld ieee80211_acl.o rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> wlan_amrr (cleandir) cd: can't cd to /src/sys/modules/wlan_amrr *** Error code 2 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-11-26 23:18:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-11-26 23:18:14 - ERROR: failed to build lint kernel TB --- 2006-11-26 23:18:14 - tinderbox aborted TB --- 0.93 user 3.34 system 5593.91 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 27 10:10:28 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94CC416A4C9; Mon, 27 Nov 2006 10:10:28 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from kraid.nerim.net (smtp-101-monday.nerim.net [62.4.16.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 804EC43DC2; Mon, 27 Nov 2006 10:09:06 +0000 (GMT) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from [192.168.1.100] (anwadmin.net8.nerim.net [213.41.185.85]) by kraid.nerim.net (Postfix) with ESMTP id CE80340F67; Mon, 27 Nov 2006 11:10:03 +0100 (CET) Message-ID: <456AB9BD.60202@activnetworks.com> Date: Mon, 27 Nov 2006 11:11:09 +0100 From: Remy Nonnenmacher User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.0.1) Gecko/20060308 SeaMonkey/1.0 MIME-Version: 1.0 To: Michiel Boland References: <20061126181325.O13925-100000@xs6.xs4all.nl> In-Reply-To: <20061126181325.O13925-100000@xs6.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kreios@gmail.com, freebsd-amd64@freebsd.org, 000.fbsd@quip.cz Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2006 10:10:28 -0000 Michiel Boland wrote: > Ok here is a patch for /sys/boot/i386/btx/btx/btx.S that will get X4100s > to boot. > > It extends the v86 monitor in the BTX so that it catches INT3 and treats > it like any other interrupt. Not sure if it's a great idea, but it's > better than nothing at this point. > > You will need to update the bootblock and /boot/loader since they both > appear to be linking in their own copy of BTX. > > --- btx.S.orig Thu Oct 5 17:30:51 2006 > +++ btx.S Sun Nov 26 16:26:12 2006 > @@ -510,6 +510,8 @@ > je v86popf # Yes > cmpb $0xcd,%al # INT imm8? > je v86intn # Yes > + cmpb $0xcc,%al # INT3? > + je v86int3 # Yes > cmpb $0xcf,%al # IRET/IRETD? > je v86iret # Yes > popl %ebx # Restore > @@ -651,6 +653,11 @@ > reboot: orb $0x1,btx_hdr+0x7 # Set the reboot flag > jmp exit # Terminate BTX and reboot > > +/* > + * Emulate INT3 > + */ > +v86int3: movb $3,%al > + jmp v86intn.1 > /* > * Emulate INT imm8... also make sure to check if it's int 15/87 > */ > > _______________________________________________ I confirm this patch fixes the same 'BTX Halted' problem on LSI1068 SAS/IME (mpt) on Fujitsu/Siemens RX200-S3. This will probably helps the BTX syndrome on recent LSI bioses on a few machines. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 27 11:09:05 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7694D16A509 for ; Mon, 27 Nov 2006 11:09:05 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFC0D43D6D for ; Mon, 27 Nov 2006 11:07:17 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kARB8HCN091887 for ; Mon, 27 Nov 2006 11:08:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kARB8FiX091883 for freebsd-amd64@FreeBSD.org; Mon, 27 Nov 2006 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Nov 2006 11:08:15 GMT Message-Id: <200611271108.kARB8FiX091883@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2006 11:09:05 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/73775 amd64 Kernel panic (trap 12) when booting with (not from!) P o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Trap 12: Page fa o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not work on amd64 o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/84930 amd64 [msdosfs] something wrong with msdosfs on amd64 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on AMD64 archit o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88299 amd64 swapcontext fails with errno 0 f amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. o amd64/104311 amd64 ports/wine should be installable on amd64 o amd64/105187 amd64 make -j2 buildworld renders FreeBSD 6.2-PRE/AMD64 unus o amd64/105207 amd64 nVidia MCP55 drivers fail to boot on 6.2B3 amd64 o amd64/105513 amd64 Kernel Panic during package installation on 6.2 beta3 o amd64/105531 amd64 gigabyte GA-M51GM-S2G / nVidia nForce 430 - does not d o amd64/105629 amd64 [re] Issue with re driver 65 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/92527 amd64 [ciphy.c] no driver for "CICADA VSC 8201 Gigabit LAN P o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100348 amd64 No hardware support: Marvell 88E8053 Yukon PCI-E Gigab o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 o amd64/104875 amd64 unsupported intel Desktop Board DG965WH o amd64/105129 amd64 Compatibility with Intel D 24 problems total. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 28 13:33:04 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5178516A407 for ; Tue, 28 Nov 2006 13:33:04 +0000 (UTC) (envelope-from Roar.Pettersen@it.uib.no) Received: from alf.uib.no (alf.uib.no [129.177.30.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E39E243D70 for ; Tue, 28 Nov 2006 13:31:34 +0000 (GMT) (envelope-from Roar.Pettersen@it.uib.no) Received: from edprp by alf.uib.no with local-esmtp (Exim 4.34) id 1Gp339-0001rB-22; Tue, 28 Nov 2006 14:31:03 +0100 Date: Tue, 28 Nov 2006 14:31:03 +0100 (CET) From: Roar Pettersen X-X-Sender: edprp@alf.uib.no To: Kris Kennaway In-Reply-To: <20061118190930.GA40317@xor.obsecurity.org> Message-ID: References: <20061118190930.GA40317@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-758783491-1164720663=:18550" Sender: Roar Pettersen Cc: freebsd-amd64@freebsd.org, Roar Pettersen Subject: Re: amd64 6.2-BETA3 unexpexted reboot X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2006 13:33:04 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-758783491-1164720663=:18550 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hello ! > You didn't display the backtrace, the most important bit. > > Are you getting em watchdog timeouts during regular server operation, > or just during dumping? We are only getting dumps, and here is the backtrack : #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff802b48f7 in boot (howto=3D260) at=20 /usr/src/sys/kern/kern_shutdown.c:409 #3 0xffffffff802b4f91 in panic (fmt=3D0xffffff003d9ac4c0 "=B0=A6=BA=3D") at /usr/src/sys/kern/kern_shutdown.c:565 #4 0xffffffff8042b09f in trap_fatal (frame=3D0xffffff003d9ac4c0,=20 eva=3D18446742975233566384) at /usr/src/sys/amd64/amd64/trap.c:660 #5 0xffffffff8042b3bf in trap_pfault (frame=3D0xffffffffa5599790,=20 usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:573 #6 0xffffffff8042b673 in trap (frame=3D {tf_rdi =3D -1098639046240, tf_rsi =3D -1099467664128, tf_rdx =3D 1,= =20 tf_rcx =3D 4, tf_r8 =3D 2560, tf_r9 =3D 3311361, tf_rax =3D 32, tf_rbx =3D= =20 -1098639046104, tf_rbp =3D -1098639046240, tf_r10 =3D 1, tf_r11 =3D 8, tf_r= 12 =3D=20 -1098639046104, tf_r13 =3D -1098476042496, tf_r14 =3D 0, tf_r15 =3D 47,=20 tf_trapno =3D 12, tf_addr =3D 0, tf_flags =3D -1098476042496, tf_err =3D 16= ,=20 tf_rip =3D 0, tf_cs =3D 8, tf_rflags =3D 66050, tf_rsp =3D -1520854952, tf_= ss =3D=20 16}) at /usr/src/sys/amd64/amd64/trap.c:352 #7 0xffffffff8041686b in calltrap () at=20 /usr/src/sys/amd64/amd64/exception.S:168 #8 0x0000000000000000 in ?? () #9 0xffffffff802ff10b in sowakeup (so=3D0xffffff00340289a0,=20 sb=3D0xffffff0034028a28) at /usr/src/sys/kern/uipc_socket2.c:422 #10 0xffffffff80375d32 in raw_append (last=3D0xffffff00340289a0,=20 ip=3D0xffffff00029ed500, n=3D0xffffff003db9c700) at /usr/src/sys/netinet/raw_ip.c:189 #11 0xffffffff80375e67 in rip_input (m=3D0xffffff0030bd7700, off=3D43963648= ) at /usr/src/sys/netinet/raw_ip.c:236 #12 0xffffffff803685cd in encap4_input (m=3D0xffffff0030bd7700, off=3D20) at /usr/src/sys/netinet/ip_encap.c:200 #13 0xffffffff80372350 in ip_input (m=3D0xffffff0030bd7700) at=20 /usr/src/sys/netinet/ip_input.c:785 #14 0xffffffff8033df2a in ether_demux (ifp=3D0xffffff00008a9800,=20 m=3D0xffffff0030bd7700) at /usr/src/sys/net/if_ethersubr.c:830 #15 0xffffffff8033e197 in ether_input (ifp=3D0xffffff00008a9800,=20 m=3D0xffffff0030bd7700) at /usr/src/sys/net/if_ethersubr.c:620 #16 0xffffffff801fd0b9 in em_intr (arg=3D0xffffff00340289a0) at=20 /usr/src/sys/dev/em/if_em.c:3567 #17 0xffffffff8029b129 in ithread_loop (arg=3D0xffffff003da4cc80) at /usr/src/sys/kern/kern_intr.c:682 #18 0xffffffff802998c7 in fork_exit (callout=3D0xffffffff8029afe0=20 , arg=3D0xffffff003da4cc80, frame=3D0xffffffffa5599c50) at=20 /usr/src/sys/kern/kern_fork.c:821 #19 0xffffffff80416bce in fork_trampoline () at=20 /usr/src/sys/amd64/amd64/exception.S:394 #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () # /etc/sysctl.conf # kern.maxfiles=3D16384 kern.maxfilesperproc=3D16384 # kern.ipc.shm_use_phys=3D1 kern.ipc.maxsockbuf=3D4194304 kern.ipc.somaxconn=3D4096 kern.ipc.maxsockets=3D32768 # vfs.vmiodirenable=3D1 # net.inet.tcp.sendspace=3D131072 net.inet.tcp.recvspace=3D131072 net.inet.tcp.syncookies=3D0 net.inet.tcp.inflight.enable=3D0 # net.inet.ip.intr_queue_maxlen=3D2048 net.inet.ip.redirect=3D0 # net.inet.udp.recvspace=3D131072 net.inet.udp.maxdgram=3D131072 # net.inet.icmp.icmplim=3D2000 net.inet.icmp.drop_redirect=3D1 # net.local.stream.recvspace=3D131072 net.local.stream.sendspace=3D131072 # net.isr.direct=3D1 # net.graph.recvspace=3D262144 net.graph.maxdgram=3D262144 --=20 Regards; Roar Pettersen Universitetet i Bergen - The University of Bergen ---559023410-758783491-1164720663=:18550-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 29 19:29:35 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B97016A403 for ; Wed, 29 Nov 2006 19:29:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F2643CA2 for ; Wed, 29 Nov 2006 19:29:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kATJTJuC093331; Wed, 29 Nov 2006 14:29:26 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Michiel Boland Date: Wed, 29 Nov 2006 13:40:00 -0500 User-Agent: KMail/1.9.1 References: <20061126181325.O13925-100000@xs6.xs4all.nl> In-Reply-To: <20061126181325.O13925-100000@xs6.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611291340.00524.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 29 Nov 2006 14:29:26 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2258/Wed Nov 29 07:04:15 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-amd64@freebsd.org Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 19:29:35 -0000 On Sunday 26 November 2006 12:18, Michiel Boland wrote: > Ok here is a patch for /sys/boot/i386/btx/btx/btx.S that will get X4100s > to boot. > > It extends the v86 monitor in the BTX so that it catches INT3 and treats > it like any other interrupt. Not sure if it's a great idea, but it's > better than nothing at this point. Heh. Another thought would be to just ignore them just like we ignore 'hlt' from vm86 mode: Index: btx.S =================================================================== RCS file: /usr/cvs/src/sys/boot/i386/btx/btx/btx.S,v retrieving revision 1.43 diff -u -r1.43 btx.S --- btx.S 5 Oct 2006 15:30:51 -0000 1.43 +++ btx.S 29 Nov 2006 18:38:07 -0000 @@ -499,6 +499,8 @@ je v86cli # Yes cmpb $0xfb,%al # STI? je v86sti # Yes + cmpb $0xcc,%al # INT3? + je v86mon.7 # Yes, ignore movzwl 0x38(%ebp),%ebx # Load V86 SS shll $0x4,%ebx # To offset pushl %ebx # Save -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 29 19:29:35 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1117216A407 for ; Wed, 29 Nov 2006 19:29:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D13FE43C9D for ; Wed, 29 Nov 2006 19:29:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kATJTJuB093331; Wed, 29 Nov 2006 14:29:20 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Michiel Boland Date: Wed, 29 Nov 2006 13:30:55 -0500 User-Agent: KMail/1.9.1 References: <200611131550.50648.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611291330.55892.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 29 Nov 2006 14:29:21 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2258/Wed Nov 29 07:04:15 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-amd64@freebsd.org Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 19:29:35 -0000 On Saturday 25 November 2006 18:10, Michiel Boland wrote: > > On Mon, 13 Nov 2006, John Baldwin wrote: > > > On Monday 13 November 2006 15:12, Michiel Boland wrote: > >>> Yeah, the X4100 has an mpt(4) controller. Mine is running the original > > BIOS > >>> release (6464), and runs FreeBSD fine. You can try fiddling with the BIOS > >>> revision by downloading replacements from Sun's website. > >> > >> As far as I can see there are no other BIOSes on the Sun website other > >> than what the box is already running (ILOM 1.0.7 - I understand ILOM and > >> BIOS are linked for 4100s) > >> > >> I am a bit puzzled why solaris and fedora do not have these problems on > >> this hardware. Oh well... > > > > The real mode breakpoint handler may just ignore breakpoints, or the BIOS > > takes a different codepath when it runs in vm86 mode. > > The code path is the same. The bios calls INT3 if someone tries to load a > block with LBA < 16, or LBA 64 or 65. (I think - my asm skills are a bit > rusty.) > > Is there not a way for BTX to ignore these INT3 interrupts? Obviously they > are ignored in real mode too. Is it ignored in real mode? I had figured the real mode handler would have rebooted the box. If it triggers in real mode then I guess we can just ignore them, at least coming from vm86 mode. I think there is magic to dump the registers but keep going when a breakpoint is triggered in protected mode. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 10:31:45 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B283016A415 for ; Thu, 30 Nov 2006 10:31:45 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2464A43CB9 for ; Thu, 30 Nov 2006 10:31:22 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kAUAVGQU069746 for ; Thu, 30 Nov 2006 07:31:16 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Thu, 30 Nov 2006 07:31:48 -0300 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200611300731.48730.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Subject: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 10:31:45 -0000 Hi there are some rumours out that this board does not boot with SCSI onboard = and=20 SMP. I am getting some with 265 dual-core opterons and I am curious if some= =20 has it running correctly thanks =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 11:32:40 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2576516A40F for ; Thu, 30 Nov 2006 11:32:40 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB2A43CA6 for ; Thu, 30 Nov 2006 11:32:32 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Gpk9b-000Km3-8H; Thu, 30 Nov 2006 11:32:35 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gpk9Y-0003F2-Ri; Thu, 30 Nov 2006 11:32:32 +0000 To: freebsd-amd64@freebsd.org, joao@matik.com.br In-Reply-To: <200611300731.48730.joao@matik.com.br> Message-Id: From: Pete French Date: Thu, 30 Nov 2006 11:32:32 +0000 Cc: Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 11:32:40 -0000 > there are some rumours out that this board does not boot with SCSI onboard > and SMP. I am getting some with 265 dual-core opterons and I am curious if > some has it running correctly Not a rumour - take a look here: http://www.freebsd.org/cgi/query-pr.cgi?pr=105067 Thats my board, but the other reported board was the H8DA8-O -pete. From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 11:41:33 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9EBF16A415 for ; Thu, 30 Nov 2006 11:41:33 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CECDE43DD5 for ; Thu, 30 Nov 2006 11:40:08 +0000 (GMT) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.62) with esmtp (envelope-from ) id <1GpkGo-0002TS-7M>; Thu, 30 Nov 2006 12:40:02 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.62) with esmtpsa (envelope-from ) id <1GpkGo-0007iq-6C>; Thu, 30 Nov 2006 12:40:02 +0100 Message-ID: <456EC30F.70008@zedat.fu-berlin.de> Date: Thu, 30 Nov 2006 12:39:59 +0100 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Thunderbird 1.5.0.8 (X11/20061110) MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 11:41:33 -0000 Pete French wrote: >> there are some rumours out that this board does not boot with SCSI onboard >> and SMP. I am getting some with 265 dual-core opterons and I am curious if >> some has it running correctly > > Not a rumour - take a look here: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=105067 > > Thats my board, but the other reported board was the H8DA8-O > > -pete. I just read your PR and was wondering, because I had similar problems long time ago with FreeBSD 4.X (maybe 3 to 8). That time it was a TYAN Thunder mainboard with a ServerWorks 3 chipset, dual PIII and an additiona LSI Enterprise 1600 RAID controller (also LSI SCSI onboard). Anyhow, with some help from this list I got the box running, changing the NICs from one to another PCI slot and changing IRQs affiliations in BIOS. Regards, Oliver From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 12:08:45 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76B2A16A403 for ; Thu, 30 Nov 2006 12:08:45 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA00C43CEC for ; Thu, 30 Nov 2006 12:08:24 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kAUC8PSs074954 for ; Thu, 30 Nov 2006 09:08:25 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Thu, 30 Nov 2006 10:08:17 -0200 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200611301008.18311.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 12:08:45 -0000 On Thursday 30 November 2006 09:32, Pete French wrote: > Not a rumour - take a look here: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D105067 > > Thats my board, but the other reported board was the > H8DA8-O > In first place thanks for answering. Seems nobody touched=20 your PR ... I also saw other threads describing appearently=20 the same problem. But I got this kind of problem often with=20 SMP and not only with opterons and SCSI but also with=20 athlon dual-cores. But until now I got all resolved with=20 setting the Bios better and sometimes even with changing=20 pci-slot position. Even if it says nothing I have some Tyan Dual opterons and=20 the MBs have the same chipset the Supermicro has and they=20 run fine. But seems nobody runs this supermicro board at all :( But on the amd64 MB list is one tested with 6.0-B saying is=20 working ... =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 12:32:29 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3AF6F16A416 for ; Thu, 30 Nov 2006 12:32:29 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0445A43CC8 for ; Thu, 30 Nov 2006 12:32:21 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Gpl5X-000M6H-Lm; Thu, 30 Nov 2006 12:32:27 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gpl5X-0003Of-Fs; Thu, 30 Nov 2006 12:32:27 +0000 To: freebsd-amd64@freebsd.org, joao@matik.com.br In-Reply-To: <200611301008.18311.joao@matik.com.br> Message-Id: From: Pete French Date: Thu, 30 Nov 2006 12:32:27 +0000 Cc: Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 12:32:29 -0000 > In first place thanks for answering. Seems nobody touched > your PR ... I also saw other threads describing appearently I know - which seems a bit sad as I am actually offering to give away free hardware to help solve it... I rather like the MSI board, but I have t say that I am hapier with the Tyan I replaced it with. > the same problem. But I got this kind of problem often with > SMP and not only with opterons and SCSI but also with Now thats interesting. It ist a speciicly SCSI thing BTW - it seems to be and external disc controller - though the only ones I have which arent SCSI are RAID. > athlon dual-cores. But until now I got all resolved with > setting the Bios better and sometimes even with changing > pci-slot position. You cant do that with the Supermicro board because the SCSI adapter in one the motheroard, so moving it to a different slot is a problem :) But I played around with all the settings I could and neer got it working. The only way for it to go SMP is to remove the SCSI and RAID addapters from the board and boot off the IDE. > Even if it says nothing I have some Tyan Dual opterons and > the MBs have the same chipset the Supermicro has and they > run fine. Indeed - the Tyan I relaced it with has the same chipset! > But on the amd64 MB list is one tested with 6.0-B saying is > working ... The boards can be made to work if you dont have SCSI - but I treat that ist with scepticism. It doesnt necessarily mean it will work for my combination of hardware. -pete. From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 30 13:29:33 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0587116A403 for ; Thu, 30 Nov 2006 13:29:33 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E10843CA8 for ; Thu, 30 Nov 2006 13:29:23 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kAUDTUjN079580 for ; Thu, 30 Nov 2006 10:29:30 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik Date: Thu, 30 Nov 2006 11:29:22 -0200 User-Agent: KMail/1.9.4 Cc: freebsd-amd64@freebsd.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: "Undisclosed.Recipients": ; Message-Id: <200611301129.22932.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 13:29:33 -0000 On Thursday 30 November 2006 10:32, Pete French wrote: > > Now thats interesting. It ist a speciicly SCSI thing BTW > - it seems to be and external disc controller - though > the only ones I have which arent SCSI are RAID. > hmm, perhaps not exactly but an ahd driver thing because I=20 am aware of similare problems with the adaptec card as in=20 certain Asus MBs in combination with certain PCI cards=20 there is a IO address conflictand the board do not boot,=20 and when using memory remapping with 4GB then the ahd=20 driver panics. Using in this cases a LSI adapter the=20 problem goes away.=20 > > You cant do that with the Supermicro board because the > SCSI adapter in one the motheroard, so moving it to a > different slot is a problem :) But I played around with you havn't tried it hard enough :) > all the settings I could and neer got it working. The > only way for it to go SMP is to remove the SCSI and RAID > addapters from the board and boot off the IDE. > you are saying booting from an IDE it works but need to=20 disable the SCSI adaptor? > > But on the amd64 MB list is one tested with 6.0-B > > saying is working ... > > The boards can be made to work if you dont have SCSI - > but I treat that ist with scepticism. It doesnt > necessarily mean it will work for my combination of > hardware. > the reporter says the SCSI works but did not answered my=20 mail until now, but the OS version he used is old =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 03:04:58 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED64616A40F for ; Fri, 1 Dec 2006 03:04:58 +0000 (UTC) (envelope-from kreios@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EEC943CA2 for ; Fri, 1 Dec 2006 03:04:46 +0000 (GMT) (envelope-from kreios@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so2623736wxc for ; Thu, 30 Nov 2006 19:04:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=K2h0bFhB41gnRLHrGOd4UsjFFiTAkrIF9KF6BCM67jIvAH3DMTSF7ad/kgicJkJALpWFhHdgCL+W+ms4NYlORIN1q5gFbX7CqwrSqo/wtRt5DYP4Q4KTvInR7c2Cxw9kDfsZq8htkTdIt/1CvIPD17TTyMwNHd7zRmf+LHObYXc= Received: by 10.90.78.9 with SMTP id a9mr4707017agb.1164942297416; Thu, 30 Nov 2006 19:04:57 -0800 (PST) Received: from ?192.168.1.198? ( [165.91.48.126]) by mx.google.com with ESMTP id 10sm19120189wrl.2006.11.30.19.04.56; Thu, 30 Nov 2006 19:04:57 -0800 (PST) In-Reply-To: <456AB9BD.60202@activnetworks.com> References: <20061126181325.O13925-100000@xs6.xs4all.nl> <456AB9BD.60202@activnetworks.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6602D21E-D1A2-4E13-AB13-305D27888977@gmail.com> Content-Transfer-Encoding: 7bit From: Dave Date: Thu, 30 Nov 2006 21:04:51 -0600 To: Remy Nonnenmacher X-Mailer: Apple Mail (2.752.2) Cc: freebsd-amd64@freebsd.org, 000.fbsd@quip.cz Subject: Re: BTX halted trying to boot X4100 from disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 03:04:59 -0000 On Nov 27, 2006, at 4:11 AM, Remy Nonnenmacher wrote: > Michiel Boland wrote: >> Ok here is a patch for /sys/boot/i386/btx/btx/btx.S that will get >> X4100s >> to boot. >> It extends the v86 monitor in the BTX so that it catches INT3 and >> treats >> it like any other interrupt. Not sure if it's a great idea, but it's >> better than nothing at this point. >> You will need to update the bootblock and /boot/loader since they >> both >> appear to be linking in their own copy of BTX. >> --- btx.S.orig Thu Oct 5 17:30:51 2006 >> +++ btx.S Sun Nov 26 16:26:12 2006 >> @@ -510,6 +510,8 @@ >> je v86popf # Yes >> cmpb $0xcd,%al # INT imm8? >> je v86intn # Yes >> + cmpb $0xcc,%al # INT3? >> + je v86int3 # Yes >> cmpb $0xcf,%al # IRET/IRETD? >> je v86iret # Yes >> popl %ebx # Restore >> @@ -651,6 +653,11 @@ >> reboot: orb $0x1,btx_hdr+0x7 # Set the reboot flag >> jmp exit # Terminate BTX and reboot >> +/* >> + * Emulate INT3 >> + */ >> +v86int3: movb $3,%al >> + jmp v86intn.1 >> /* >> * Emulate INT imm8... also make sure to check if it's int 15/87 >> */ >> _______________________________________________ > > I confirm this patch fixes the same 'BTX Halted' problem on LSI1068 > SAS/IME (mpt) on Fujitsu/Siemens RX200-S3. > > This will probably helps the BTX syndrome on recent LSI bioses on a > few machines. Thanks for the pointer. We where able to get an older version of the LSI MPT BIOS from Sun. If this is something that may be committed and needs testing, let me know soon and I can throw the problem BIOS on the machine and give the patch a try. -- Dave From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 04:20:05 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1770216A47B for ; Fri, 1 Dec 2006 04:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAEA643CA3 for ; Fri, 1 Dec 2006 04:19:52 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB14K45l089324 for ; Fri, 1 Dec 2006 04:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB14K4I8089323; Fri, 1 Dec 2006 04:20:04 GMT (envelope-from gnats) Resent-Date: Fri, 1 Dec 2006 04:20:04 GMT Resent-Message-Id: <200612010420.kB14K4I8089323@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, NIIMI Satoshi Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3133616A415 for ; Fri, 1 Dec 2006 04:12:00 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id E21F443C9D for ; Fri, 1 Dec 2006 04:11:47 +0000 (GMT) (envelope-from sa2c@sa2c.net) Received: by wx-out-0506.google.com with SMTP id s18so2635987wxc for ; Thu, 30 Nov 2006 20:11:58 -0800 (PST) Received: by 10.70.65.8 with SMTP id n8mr7791230wxa.1164946317848; Thu, 30 Nov 2006 20:11:57 -0800 (PST) Received: from berkeley.l.sa2c.net ( [125.192.101.90]) by mx.google.com with ESMTP id h13sm6347758wxd.2006.11.30.20.11.56; Thu, 30 Nov 2006 20:11:57 -0800 (PST) Received: by berkeley.l.sa2c.net (Postfix, from userid 3104) id 6D32C42A1; Fri, 1 Dec 2006 13:11:53 +0900 (JST) Message-Id: <20061201041153.6D32C42A1@berkeley.l.sa2c.net> Date: Fri, 1 Dec 2006 13:11:53 +0900 (JST) From: NIIMI Satoshi To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/106109: amd64: si_addr is not set when sending a signal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: NIIMI Satoshi List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 04:20:05 -0000 >Number: 106109 >Category: amd64 >Synopsis: amd64: si_addr is not set when sending a signal >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 01 04:20:03 GMT 2006 >Closed-Date: >Last-Modified: >Originator: NIIMI Satoshi >Release: FreeBSD 6.2-RC1 i386 >Organization: >Environment: System: FreeBSD berkeley.l.sa2c.net 6.2-RC1 FreeBSD 6.2-RC1 #0: Thu Nov 30 10:03:58 JST 2006 root@berkeley.l.sa2c.net:/usr/obj/usr/src/sys/GENERIC i386 >Description: POSIX style signal handers expect that the faulting address is stored in si_addr member of siginfo_t. But the address is passed to signal handler only as non-portable fourth argument on FreeBSD/amd64. >How-To-Repeat: Following program produces i386: &main=0x80485e8, si_addr=0x80485e8, fourth_arg=0x0 amd64: &main=0x400780, si_addr=0x0, fourth_arg=0x400780 #include #include #include int main(); void handler(int sig, siginfo_t *siginfo, void *context, void *addr) { fprintf(stderr, "&main=%p, si_addr=%p, fourth_arg=%p\n", &main, siginfo->si_addr, addr); exit(1); } int main() { struct sigaction sa; sa.sa_flags = SA_SIGINFO; sigemptyset(&sa.sa_mask); sa.sa_sigaction = (void (*)(int, siginfo_t *, void *))handler; sigaction(SIGBUS, &sa, NULL); sigaction(SIGSEGV, &sa, NULL); *(int *)main = 1; return 0; } >Fix: --- amd64-machdep.diff begins here --- Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/amd64/machdep.c,v retrieving revision 1.664 diff -u -r1.664 machdep.c --- machdep.c 19 Nov 2006 20:54:57 -0000 1.664 +++ machdep.c 1 Dec 2006 03:36:54 -0000 @@ -304,6 +304,7 @@ /* Fill in POSIX parts */ sf.sf_si = ksi->ksi_info; sf.sf_si.si_signo = sig; /* maybe a translated signal */ + sf.sf_si.si_addr = ksi->ksi_addr; regs->tf_rcx = (register_t)ksi->ksi_addr; /* arg 4 in %rcx */ } else { /* Old FreeBSD-style arguments. */ --- amd64-machdep.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 05:23:02 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DDC9416B643; Fri, 1 Dec 2006 05:21:15 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-amd64@freebsd.org, NIIMI Satoshi Date: Fri, 1 Dec 2006 13:21:09 +0800 User-Agent: KMail/1.8.2 References: <20061201041153.6D32C42A1@berkeley.l.sa2c.net> In-Reply-To: <20061201041153.6D32C42A1@berkeley.l.sa2c.net> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200612011321.10109.davidxu@freebsd.org> Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/106109: amd64: si_addr is not set when sending a signal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 05:23:02 -0000 On Friday 01 December 2006 12:11, NIIMI Satoshi wrote: > >Number: 106109 > >Category: amd64 > >Synopsis: amd64: si_addr is not set when sending a signal > >Confidential: no > >Severity: serious > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Dec 01 04:20:03 GMT 2006 > >Closed-Date: > >Last-Modified: > >Originator: NIIMI Satoshi > >Release: FreeBSD 6.2-RC1 i386 > >Organization: > >Environment: > > System: FreeBSD berkeley.l.sa2c.net 6.2-RC1 FreeBSD 6.2-RC1 #0: Thu Nov 30 > 10:03:58 JST 2006 root@berkeley.l.sa2c.net:/usr/obj/usr/src/sys/GENERIC > i386 > > >Description: > > POSIX style signal handers expect that the faulting address is stored > in si_addr member of siginfo_t. > > But the address is passed to signal handler only as non-portable > fourth argument on FreeBSD/amd64. > > >How-To-Repeat: > > Following program produces > i386: &main=0x80485e8, si_addr=0x80485e8, fourth_arg=0x0 > amd64: &main=0x400780, si_addr=0x0, fourth_arg=0x400780 > > #include > #include > #include > > int main(); > > void > handler(int sig, siginfo_t *siginfo, void *context, void *addr) > { > fprintf(stderr, "&main=%p, si_addr=%p, fourth_arg=%p\n", > &main, siginfo->si_addr, addr); > exit(1); > } > > int > main() > { > struct sigaction sa; > > sa.sa_flags = SA_SIGINFO; > sigemptyset(&sa.sa_mask); > sa.sa_sigaction = (void (*)(int, siginfo_t *, void *))handler; > > sigaction(SIGBUS, &sa, NULL); > sigaction(SIGSEGV, &sa, NULL); > *(int *)main = 1; > > return 0; > } > > >Fix: > > --- amd64-machdep.diff begins here --- > Index: machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/amd64/amd64/machdep.c,v > retrieving revision 1.664 > diff -u -r1.664 machdep.c > --- machdep.c 19 Nov 2006 20:54:57 -0000 1.664 > +++ machdep.c 1 Dec 2006 03:36:54 -0000 > @@ -304,6 +304,7 @@ > /* Fill in POSIX parts */ > sf.sf_si = ksi->ksi_info; > sf.sf_si.si_signo = sig; /* maybe a translated signal */ > + sf.sf_si.si_addr = ksi->ksi_addr; > regs->tf_rcx = (register_t)ksi->ksi_addr; /* arg 4 in %rcx */ > } else { > /* Old FreeBSD-style arguments. */ > --- amd64-machdep.diff ends here --- I reviewed the sendsig() in RELENG_6 for AMD64, the si_addr is not set, but is set in i386 version of sendsig(), the originator's patch is wrong, it copied some code from HEAD which is not valid for RELENG_6, the HEAD has fully working siginfo_t in kernel while RELENG_6 does not, the patch should be changed to: > + sf.sf_si.si_addr = regs->tf_addr; David Xu From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 05:32:47 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D73916C88D for ; Fri, 1 Dec 2006 05:30:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 593DB43CA2 for ; Fri, 1 Dec 2006 05:30:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB15UR7P097905 for ; Fri, 1 Dec 2006 05:30:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB15URWx097896; Fri, 1 Dec 2006 05:30:27 GMT (envelope-from gnats) Date: Fri, 1 Dec 2006 05:30:27 GMT Message-Id: <200612010530.kB15URWx097896@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: David Xu Cc: Subject: Re: amd64/106109: amd64: si_addr is not set when sending a signal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Xu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 05:32:47 -0000 The following reply was made to PR amd64/106109; it has been noted by GNATS. From: David Xu To: freebsd-amd64@freebsd.org, NIIMI Satoshi Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/106109: amd64: si_addr is not set when sending a signal Date: Fri, 1 Dec 2006 13:21:09 +0800 On Friday 01 December 2006 12:11, NIIMI Satoshi wrote: > >Number: 106109 > >Category: amd64 > >Synopsis: amd64: si_addr is not set when sending a signal > >Confidential: no > >Severity: serious > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Dec 01 04:20:03 GMT 2006 > >Closed-Date: > >Last-Modified: > >Originator: NIIMI Satoshi > >Release: FreeBSD 6.2-RC1 i386 > >Organization: > >Environment: > > System: FreeBSD berkeley.l.sa2c.net 6.2-RC1 FreeBSD 6.2-RC1 #0: Thu Nov 30 > 10:03:58 JST 2006 root@berkeley.l.sa2c.net:/usr/obj/usr/src/sys/GENERIC > i386 > > >Description: > > POSIX style signal handers expect that the faulting address is stored > in si_addr member of siginfo_t. > > But the address is passed to signal handler only as non-portable > fourth argument on FreeBSD/amd64. > > >How-To-Repeat: > > Following program produces > i386: &main=0x80485e8, si_addr=0x80485e8, fourth_arg=0x0 > amd64: &main=0x400780, si_addr=0x0, fourth_arg=0x400780 > > #include > #include > #include > > int main(); > > void > handler(int sig, siginfo_t *siginfo, void *context, void *addr) > { > fprintf(stderr, "&main=%p, si_addr=%p, fourth_arg=%p\n", > &main, siginfo->si_addr, addr); > exit(1); > } > > int > main() > { > struct sigaction sa; > > sa.sa_flags = SA_SIGINFO; > sigemptyset(&sa.sa_mask); > sa.sa_sigaction = (void (*)(int, siginfo_t *, void *))handler; > > sigaction(SIGBUS, &sa, NULL); > sigaction(SIGSEGV, &sa, NULL); > *(int *)main = 1; > > return 0; > } > > >Fix: > > --- amd64-machdep.diff begins here --- > Index: machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/amd64/amd64/machdep.c,v > retrieving revision 1.664 > diff -u -r1.664 machdep.c > --- machdep.c 19 Nov 2006 20:54:57 -0000 1.664 > +++ machdep.c 1 Dec 2006 03:36:54 -0000 > @@ -304,6 +304,7 @@ > /* Fill in POSIX parts */ > sf.sf_si = ksi->ksi_info; > sf.sf_si.si_signo = sig; /* maybe a translated signal */ > + sf.sf_si.si_addr = ksi->ksi_addr; > regs->tf_rcx = (register_t)ksi->ksi_addr; /* arg 4 in %rcx */ > } else { > /* Old FreeBSD-style arguments. */ > --- amd64-machdep.diff ends here --- I reviewed the sendsig() in RELENG_6 for AMD64, the si_addr is not set, but is set in i386 version of sendsig(), the originator's patch is wrong, it copied some code from HEAD which is not valid for RELENG_6, the HEAD has fully working siginfo_t in kernel while RELENG_6 does not, the patch should be changed to: > + sf.sf_si.si_addr = regs->tf_addr; David Xu From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 08:36:03 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2AFA416A416; Fri, 1 Dec 2006 08:36:03 +0000 (UTC) (envelope-from davidxu@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB10243CBA; Fri, 1 Dec 2006 08:35:48 +0000 (GMT) (envelope-from davidxu@FreeBSD.org) Received: from freefall.freebsd.org (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB18a1JG017705; Fri, 1 Dec 2006 08:36:01 GMT (envelope-from davidxu@freefall.freebsd.org) Received: (from davidxu@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB18a1uH017701; Fri, 1 Dec 2006 08:36:01 GMT (envelope-from davidxu) Date: Fri, 1 Dec 2006 08:36:01 GMT From: David Xu Message-Id: <200612010836.kB18a1uH017701@freefall.freebsd.org> To: sa2c@sa2c.net, davidxu@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/106109: amd64: si_addr is not set when sending a signal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 08:36:03 -0000 Synopsis: amd64: si_addr is not set when sending a signal State-Changed-From-To: open->patched State-Changed-By: davidxu State-Changed-When: Fri Dec 1 08:35:19 UTC 2006 State-Changed-Why: Patch is applied. http://www.freebsd.org/cgi/query-pr.cgi?pr=106109 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 08:40:15 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60C3016A403 for ; Fri, 1 Dec 2006 08:40:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0287143CA2 for ; Fri, 1 Dec 2006 08:40:01 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB18eEVu017811 for ; Fri, 1 Dec 2006 08:40:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB18eEie017808; Fri, 1 Dec 2006 08:40:14 GMT (envelope-from gnats) Date: Fri, 1 Dec 2006 08:40:14 GMT Message-Id: <200612010840.kB18eEie017808@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: amd64/106109: commit references a PR X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 08:40:15 -0000 The following reply was made to PR amd64/106109; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/106109: commit references a PR Date: Fri, 1 Dec 2006 08:34:54 +0000 (UTC) davidxu 2006-12-01 08:34:39 UTC FreeBSD src repository Modified files: (Branch: RELENG_6) sys/amd64/amd64 machdep.c Log: MFC: Store fault address into POSIX siginfo. PR: amd64/106109 Revision Changes Path 1.638.2.11 +1 -0 src/sys/amd64/amd64/machdep.c _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 09:01:15 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6115A16A403 for ; Fri, 1 Dec 2006 09:01:15 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30F9F43CAC for ; Fri, 1 Dec 2006 09:01:00 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kB191BZ4045227; Fri, 1 Dec 2006 06:01:11 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Pete French Date: Fri, 1 Dec 2006 06:01:54 -0300 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200612010601.55291.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 09:01:15 -0000 On Thursday 30 November 2006 09:32, Pete French wrote: > > The boards can be made to work if you dont have SCSI - but I > treat that ist with scepticism. It doesnt necessarily mean it > will work for my combination of hardware. > I had a look at your dmesg output and I am not sure if your board is really= =20 the SuperMicro H8DA8 I mentioned or it is an old one you show a U160 SCSI adaptor (ahc) and it should have an U320 (ahd) also it seems you have the scsi-raid enabled using the ciss driver, did you= =20 tried it with raid disabled (w/o ciss) but scsi enabled? well ... and you're running i386 on it ...=20 =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 11:35:05 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A0E216A407 for ; Fri, 1 Dec 2006 11:35:05 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 532A243CBA for ; Fri, 1 Dec 2006 11:34:51 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Gq6fX-000Gcy-W0; Fri, 01 Dec 2006 11:35:04 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gq6fX-0008AM-Oo; Fri, 01 Dec 2006 11:35:03 +0000 To: joao@matik.com.br In-Reply-To: <200612010601.55291.joao@matik.com.br> Message-Id: From: Pete French Date: Fri, 01 Dec 2006 11:35:03 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 11:35:05 -0000 > I had a look at your dmesg output and I am not sure if your board is really > the SuperMicro H8DA8 I mentioned or it is an old one Ummm, *my* board is not a Supermicro at all - mine is the MSI one. There was another person with the same problem who has the Supermicro board that you asked about though, and had an identical problem to me. Hence me replying to your query. > well ... and you're running i386 on it ... It behaves the same under amd64 - at the time I was asked to run i386 on it and to get it debugged under that first and then try on amd64, so the dmesg output in the PR is from i386. But it does the same thing when running amd64 - I tried all combinations at the time. -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 12:03:53 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 034A716A417 for ; Fri, 1 Dec 2006 12:03:53 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12DE743CAB for ; Fri, 1 Dec 2006 12:03:37 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kB1C3o5q061737; Fri, 1 Dec 2006 09:03:50 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Pete French Date: Fri, 1 Dec 2006 10:03:42 -0200 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200612011003.42748.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 12:03:53 -0000 On Friday 01 December 2006 09:35, Pete French wrote: > > I had a look at your dmesg output and I am not sure if > > your board is really the SuperMicro H8DA8 I mentioned > > or it is an old one > > Ummm, *my* board is not a Supermicro at all - mine is the > MSI one. There was another person with the same problem > who has the Supermicro board that you asked about though, > and had an identical problem to me. Hence me replying to > your query. > ook, I see > > well ... and you're running i386 on it ... > > It behaves the same under amd64 - at the time I was asked > to run i386 on it and to get it debugged under that first > and then try on amd64, so the dmesg output in the PR is > from i386. But it does the same thing when running amd64 > - I tried all combinations at the time. > in your case, first thing I would do is compiling a kernel=20 without ciss and disable serial, parallel, ide and usb and=20 take the fxp out to see what happens because I am not sure=20 if the ciss driver is a good friend of ahc at all ... but=20 probably you tried that already =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 12:31:39 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9AF4F16A4B3 for ; Fri, 1 Dec 2006 12:31:39 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83CFE43CB6 for ; Fri, 1 Dec 2006 12:31:24 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Gq7YH-000HwJ-3d; Fri, 01 Dec 2006 12:31:37 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gq7YG-0008NS-SI; Fri, 01 Dec 2006 12:31:36 +0000 To: joao@matik.com.br In-Reply-To: <200612011003.42748.joao@matik.com.br> Message-Id: From: Pete French Date: Fri, 01 Dec 2006 12:31:36 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 12:31:39 -0000 > ook, I see yes, sorry for the slight confusion there! > in your case, first thing I would do is compiling a kernel > without ciss and disable serial, parallel, ide and usb and > take the fxp out to see what happens because I am not sure > if the ciss driver is a good friend of ahc at all ... but > probably you tried that already I can't remember if I tried that specific combination, but I did strip out a lot of drivers at the time to verify that it really was the disc controllers on the PCI bus causing the problem. I even went and borrowed an IDE drive to make sure it booted a GENERIC kernel just on the board with no controllers plugged in. That worked, as does booting from the IDE with the controllers plugged in, but not compiled into the kernel. I can't do anymore testing as I replaced the board, and the original is now sitting in a box waiting for someone to say "yes, I want to wrk on the problem" so I can post it to them :-) I am interested in your comments regarding ciss and ahc by the way - this is my standard configuartion for machines more or less - boot from a SCSI drive in an Adaptec controller, with all the data on a Compaq RAID card. I've been running this way since right back with the ida drivers under FreeBSD 3.3 or so, and have never had any trouble with them. -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 13:16:32 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37B3E16A403 for ; Fri, 1 Dec 2006 13:16:32 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 759E143C9D for ; Fri, 1 Dec 2006 13:16:17 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kB1DGTXL067209; Fri, 1 Dec 2006 10:16:29 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Pete French , freebsd-amd64@freebsd.org Date: Fri, 1 Dec 2006 11:16:21 -0200 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200612011116.21669.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 13:16:32 -0000 On Friday 01 December 2006 10:31, you wrote: > I am interested in your comments regarding ciss and ahc > by the way - this is my standard configuartion for > machines more or less - boot from a SCSI drive in an > Adaptec controller, with all the data on a Compaq RAID > card. I've been running this way since right back with > the ida drivers under FreeBSD 3.3 or so, and have never > had any trouble with them. I do not use raid at all but I remember once I needed it and=20 funny - just looked up in my logbook to be sure - it was a=20 MSI MB with SMP which didn't boot ... only as UP it came=20 up. But, it was a S939 athlon64 dualcore, it hung exactly=20 there as well: trying to boot from ... So I stripped all=20 off, disabled the onboard sata raid and it came up normally=20 as SMP and with the ahd driver =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 14:48:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DFA7F16A4A7 for ; Fri, 1 Dec 2006 14:48:22 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B96D43CC3 for ; Fri, 1 Dec 2006 14:47:13 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Gq9fL-000M9r-Qq; Fri, 01 Dec 2006 14:47:03 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Gq9fL-000A3O-0U; Fri, 01 Dec 2006 14:47:03 +0000 To: freebsd-amd64@freebsd.org, joao@matik.com.br In-Reply-To: <200612011116.21669.joao@matik.com.br> Message-Id: From: Pete French Date: Fri, 01 Dec 2006 14:47:03 +0000 Cc: Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 14:48:23 -0000 > I do not use raid at all but I remember once I needed it and > funny - just looked up in my logbook to be sure - it was a > MSI MB with SMP which didn't boot ... only as UP it came up. You know, I am starting to go off MSI as a motherboard supplier the more of these stories I hear! :-) -pete. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 17:20:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 051E016A403 for ; Fri, 1 Dec 2006 17:20:22 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D19643CAF for ; Fri, 1 Dec 2006 17:20:05 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id kB1HKIhU085497 for ; Fri, 1 Dec 2006 14:20:18 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Fri, 1 Dec 2006 15:20:10 -0200 User-Agent: KMail/1.9.4 References: <200611300731.48730.joao@matik.com.br> In-Reply-To: <200611300731.48730.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200612011520.10730.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: Supermicro H8DA8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 17:20:22 -0000 On Thursday 30 November 2006 08:31, JoaoBR wrote: > Hi > there are some rumours out that this board does not boot > with SCSI onboard and SMP. I am getting some with 265 > dual-core opterons and I am curious if some has it > running correctly > I believe this answer I just got from Supermicro support=20 might be interesting for others too: =A0>=A0=A0=A0=A0=A0=A0=A0If you configure the on-board SCSI controller as=20 NONE HOST RAID then I believe there is not issue install=20 =46ree BSD OS. But if you configuration as Host Raid or Add=20 the AOC-LPZCR1 or 2 Zero Channel Raid card and=20 configuration as hardware then it may run into problem=20 issue with kernel image driver for the controller support=20 open source OS kernel. I still will post an update soon I get the MB and checked it=20 out. =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 18:14:42 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5BE3F16A403; Fri, 1 Dec 2006 18:14:42 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-71-245-104-192.ptldor.fios.verizon.net [71.245.104.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE67443CB4; Fri, 1 Dec 2006 18:14:24 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.8/8.13.6) with ESMTP id kB1IEdo4031252; Fri, 1 Dec 2006 10:14:39 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.8/8.13.4/Submit) with UUCP id kB1IEd1q031249; Fri, 1 Dec 2006 10:14:39 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id SAA07107; Fri, 1 Dec 2006 18:13:17 GMT Message-Id: <200612011813.SAA07107@sopwith.solgatos.com> To: freebsd-amd64@freebsd.org, freebsd-drivers@freebsd.org Date: Fri, 01 Dec 2006 10:13:17 +0000 From: Dieter Cc: Subject: nforce4 disk I/O X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 18:14:42 -0000 I thought I tested disk I/O in the past and got full write speed to 4 drives at once, but now I get a slowdown if writing to more than one disk at once. FreeBSD 6.0 FFS with soft updates nvidia nforce 4 ultra 4 SATA drives 1 PATA drive 1 PATA CD/DVD (idle) Doing dd from /dev/zero to 1 drive, I get about 7 MB/s. Doing dd from /dev/zero to 2 drives, I get about 8 MB/s total. Doing dd from /dev/zero to 3 drives, I get about 8-9 MB/s total. Reading from one drive doesn't hurt the read or write speed to a second drive. I'm also getting things like one process that is I/O bound writing to a disk will significantly slow down a CPU bound process writing to a different disk, and the CPU becomes over 50% idle. I wonder if there is contention for a lock that only happens when writing? Does the driver hold a lock while waiting for the disk to say "yes I wrote that sector" ? atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xcc00-0xcc0f mem 0xfebfb000-0xfebfbfff irq 10 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xb800-0xb80f mem 0xfebfa000-0xfebfafff irq 11 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 acd0: DVDR at ata0-master UDMA66 ad2: 305245MB at ata1-master UDMA100 ad4: 238475MB at ata2-master SATA150 ad6: 238475MB at ata3-master SATA150 ad8: 238475MB at ata4-master SATA150 ad10: 305245MB at ata5-master SATA150 cd0 at ata0 bus 0 target 0 lun 0 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 18:41:04 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8DFB416A51A for ; Fri, 1 Dec 2006 18:41:02 +0000 (UTC) (envelope-from rsato@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id E671D43CC4 for ; Fri, 1 Dec 2006 18:40:43 +0000 (GMT) (envelope-from rsato@mac.com) Received: from mac.com (smtpin05-en2 [10.13.10.150]) by smtpout.mac.com (Xserve/8.12.11/smtpout05/MantshX 4.0) with ESMTP id kB1IexEg016255 for ; Fri, 1 Dec 2006 10:40:59 -0800 (PST) Received: from [172.18.5.178] (c-24-7-120-117.hsd1.ca.comcast.net [24.7.120.117]) (authenticated bits=0) by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id kB1IeuWr012457 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 1 Dec 2006 10:40:58 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <7C42C53F-1D3F-4C05-8A83-DD185FF1F703@mac.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-amd64@freebsd.org From: Randy Sato Date: Fri, 1 Dec 2006 10:40:54 -0800 X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Subject: 6.2 RC1 on HP xw6400 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 18:41:04 -0000 I am trying to install freebsd on my new HP xw6400, but the installer immediately panics with the message "panic: No BIOS smap info from loader!" I have seen other postings of similar problems, but no solutions. Please tell me if I am SOL or if there is something that can be done to run freebsd on this box, or at least install it to see how well it works. I have installed freebsd 6.2 RC1 i386, but all is not peachy there either. Just for my info, I was hoping to cross compile an amd64 universe to see if I could get that to work, but no joy. I built world and the kernel using TARGET_ARCH=amd64. I was hoping to end up with the same panic as the installer, but instead the kernel almost immediately prints some error messages, but they are gone before I can read them and the machine reboots. Is it possible to cross compile then run an amd64 kernel and world starting from i386? This machine came with Red Hat installed, and I installed the freebsd i386 on the last primary partition and I installed the freebsd boot manager. Unfortunately when I press anything other than F4, the machine just beeps and will not boot anything else. Thanks in advance for any words of wisdom. Randy From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 20:06:11 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF09D16A415 for ; Fri, 1 Dec 2006 20:06:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF3843CF5 for ; Fri, 1 Dec 2006 20:05:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kB1K4g0p014319; Fri, 1 Dec 2006 15:04:45 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Fri, 1 Dec 2006 15:02:14 -0500 User-Agent: KMail/1.9.1 References: <7C42C53F-1D3F-4C05-8A83-DD185FF1F703@mac.com> In-Reply-To: <7C42C53F-1D3F-4C05-8A83-DD185FF1F703@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612011502.14504.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 01 Dec 2006 15:04:46 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2269/Fri Dec 1 13:17:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Randy Sato Subject: Re: 6.2 RC1 on HP xw6400 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 20:06:11 -0000 On Friday 01 December 2006 13:40, Randy Sato wrote: > I am trying to install freebsd on my new HP xw6400, but the installer > immediately panics with the message "panic: No BIOS smap info from > loader!" Umm, your box really should have an SMAP. Can you run the 'smap' command from recent 6.x or HEAD from the loader prompt? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 20:16:08 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BE3AD16A4D0; Fri, 1 Dec 2006 20:16:08 +0000 (UTC) (envelope-from rsato@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5CBC43CB1; Fri, 1 Dec 2006 20:15:45 +0000 (GMT) (envelope-from rsato@mac.com) Received: from mac.com (smtpin05-en2 [10.13.10.150]) by smtpout.mac.com (Xserve/8.12.11/smtpout12/MantshX 4.0) with ESMTP id kB1KG1gC005871; Fri, 1 Dec 2006 12:16:01 -0800 (PST) Received: from [172.18.5.178] (c-24-7-120-117.hsd1.ca.comcast.net [24.7.120.117]) (authenticated bits=0) by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id kB1KFxLP018559 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 1 Dec 2006 12:16:00 -0800 (PST) In-Reply-To: <200612011502.14504.jhb@freebsd.org> References: <7C42C53F-1D3F-4C05-8A83-DD185FF1F703@mac.com> <200612011502.14504.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <274F1939-D2A6-4092-A9BB-06F38834114C@mac.com> Content-Transfer-Encoding: 7bit From: Randy Sato Date: Fri, 1 Dec 2006 12:15:57 -0800 To: John Baldwin X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-amd64@freebsd.org Subject: Re: 6.2 RC1 on HP xw6400 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 20:16:08 -0000 I can't provide the exact output because I am not in front of the machine at this time, but I did that from the 6.2 RC1 amd64 install CD and I am pretty sure the output was a few blank lines. I am sure the output was nothing that led me to believe that it should boot. Randy On Dec 1, 2006, at 12:02 PM, John Baldwin wrote: > On Friday 01 December 2006 13:40, Randy Sato wrote: >> I am trying to install freebsd on my new HP xw6400, but the installer >> immediately panics with the message "panic: No BIOS smap info from >> loader!" > > Umm, your box really should have an SMAP. Can you run the 'smap' > command from > recent 6.x or HEAD from the loader prompt? > > -- > John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 22:16:14 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 904C216A40F for ; Fri, 1 Dec 2006 22:16:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BBF743C9D for ; Fri, 1 Dec 2006 22:15:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kB1MGCmI015194; Fri, 1 Dec 2006 17:16:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Fri, 1 Dec 2006 17:11:56 -0500 User-Agent: KMail/1.9.4 References: <20061118190930.GA40317@xor.obsecurity.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612011711.57009.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Fri, 01 Dec 2006 17:16:13 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2269/Fri Dec 1 13:17:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Roar Pettersen , Kris Kennaway Subject: Re: amd64 6.2-BETA3 unexpexted reboot X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 22:16:14 -0000 On Tuesday 28 November 2006 08:31, Roar Pettersen wrote: > Hello ! > > > You didn't display the backtrace, the most important bit. > > > > Are you getting em watchdog timeouts during regular server operation, > > or just during dumping? > > We are only getting dumps, and here is the backtrack : This panic might be fixed by this: mohans 2006-11-22 23:06:27 UTC FreeBSD src repository Modified files: (Branch: RELENG_6_2) sys/kern uipc_socket.c Log: Fix a race in soclose() where connections could be queued to the listening socket after the pass that cleans those queues. This results in these connections being orphaned (and leaked). The fix is to clean up the so queues after detaching the socket from the protocol. Thanks to ups and jhb for discussions and a thorough code review. Approved by: re Revision Changes Path 1.242.2.6.2.1 +23 -23 src/sys/kern/uipc_socket.c -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 1 22:44:53 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E85AD16A416 for ; Fri, 1 Dec 2006 22:44:53 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6046743CA7 for ; Fri, 1 Dec 2006 22:44:35 +0000 (GMT) (envelope-from sa2c@sa2c.net) Received: by wx-out-0506.google.com with SMTP id s18so2857975wxc for ; Fri, 01 Dec 2006 14:44:51 -0800 (PST) Received: by 10.70.90.17 with SMTP id n17mr9593254wxb.1165013091331; Fri, 01 Dec 2006 14:44:51 -0800 (PST) Received: from ?192.168.1.2? ( [125.192.101.90]) by mx.google.com with ESMTP id h17sm37369300wxd.2006.12.01.14.44.50; Fri, 01 Dec 2006 14:44:51 -0800 (PST) Message-ID: <4570B05F.9040207@sa2c.net> Date: Sat, 02 Dec 2006 07:44:47 +0900 From: NIIMI Satoshi MIME-Version: 1.0 To: David Xu References: <200612010836.kB18a1uH017701@freefall.freebsd.org> In-Reply-To: <200612010836.kB18a1uH017701@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/106109: amd64: si_addr is not set when sending a signal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2006 22:44:54 -0000 On 2006/12/01 17:36, David Xu wrote: > Synopsis: amd64: si_addr is not set when sending a signal > > State-Changed-From-To: open->patched > State-Changed-By: davidxu > State-Changed-When: Fri Dec 1 08:35:19 UTC 2006 > State-Changed-Why: > Patch is applied. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=106109 Thanks. csup'ed to RELENG_6 and it works as expected. -- NIIMI Satoshi From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 02:50:11 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E64C16A40F for ; Sat, 2 Dec 2006 02:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 150D943CB7 for ; Sat, 2 Dec 2006 02:49:49 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB22o6uv061488 for ; Sat, 2 Dec 2006 02:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB22o642061487; Sat, 2 Dec 2006 02:50:06 GMT (envelope-from gnats) Resent-Date: Sat, 2 Dec 2006 02:50:06 GMT Resent-Message-Id: <200612020250.kB22o642061487@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, Alex Vasylenko Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E21916A403 for ; Sat, 2 Dec 2006 02:42:36 +0000 (UTC) (envelope-from lxv@omut.org) Received: from mail.omut.org (mail.omut.org [216.218.215.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A810443C9D for ; Sat, 2 Dec 2006 02:42:18 +0000 (GMT) (envelope-from lxv@omut.org) Received: from blackbox.omut.org (blackbox.intranet [10.10.10.12]) by mail.omut.org (8.13.8/8.13.8) with ESMTP id kB22gXd1010009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 1 Dec 2006 18:42:34 -0800 (PST) (envelope-from lxv@omut.org) Received: from blackbox.intranet (localhost [127.0.0.1]) by blackbox.omut.org (8.13.8/8.13.8) with ESMTP id kB22gVWv018666 for ; Fri, 1 Dec 2006 21:42:33 -0500 (EST) (envelope-from lxv@blackbox.intranet) Received: (from lxv@localhost) by blackbox.intranet (8.13.8/8.13.8/Submit) id kB22gURW018665; Fri, 1 Dec 2006 21:42:30 -0500 (EST) (envelope-from lxv) Message-Id: <200612020242.kB22gURW018665@blackbox.intranet> Date: Fri, 1 Dec 2006 21:42:30 -0500 (EST) From: Alex Vasylenko To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/106186: panic in swap_pager_swap_init (amd64/smp/6.2-pre) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Vasylenko List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 02:50:11 -0000 >Number: 106186 >Category: amd64 >Synopsis: panic in swap_pager_swap_init (amd64/smp/6.2-pre) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 02 02:50:06 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Alex Vasylenko >Release: FreeBSD 6.2-PRERELEASE amd64 >Organization: >Environment: System: FreeBSD blackbox.intranet 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Fri Dec 1 20:36:12 EST 2006 root@:/usr/obj/usr/src/sys/GENERIC-AMD64-C amd64 >Description: I tried to upgrade an amd64x2 box from "FreeBSD 6.1-STABLE #36: Mon Sep 4 11:22:15 EDT 2006" to "FreeBSD 6.2-PRERELEASE #1: Mon Nov 13 10:01:57 EST 2006" and found that a newly built kernel panics on boot as follows: SMP: AP CPU #1 Launched! panic: failed to create swap_zone. cpuid = Trying to mou0 KDB: enter: nt root from ufpanic [thread pid 40 tid 100040 ] Stopped at kdb_enter+0x2f db> where Tracing pid 40 tid 100040 td 0xffffff003b9e24c0 kdb_enter() at kdb_enter+0x2f panic() at panic+0x291 swap_pager_swap_init() at swap_pager_swap_init+0x20c vm_pageout() at vm_pageout+0x17c fork_exit() at fork_exit+0x86 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffa753bd00, rbp = 0 --- old dmesg: http://www.omut.org/~lxv/bbox-dmesg-20060824 new dmesg (-v): http://www.omut.org/~lxv/bbox-dmesg-20061113-v kernel config: http://www.omut.org/~lxv/bbox-GENERIC-BBOX >How-To-Repeat: >Fix: There are several known workarounds: - GENERIC (UP) kernel works fine; - my kernel (a stripped down SMP) with "options SMP" removed works; - my kernel with SMP enabled and either -v or -d (followed by cont) works. ... and the best one discovered by another person who also experiences this issue: - have FireWire-related drivers removed from kernel configuration file (firewire/sbp/fwe) >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 03:40:13 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BAB916A407 for ; Sat, 2 Dec 2006 03:40:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A660343CBE for ; Sat, 2 Dec 2006 03:39:46 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB23e4AZ066287 for ; Sat, 2 Dec 2006 03:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB23e4KA066286; Sat, 2 Dec 2006 03:40:04 GMT (envelope-from gnats) Resent-Date: Sat, 2 Dec 2006 03:40:04 GMT Resent-Message-Id: <200612020340.kB23e4KA066286@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, Alan Amesbury Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4EAD916A407 for ; Sat, 2 Dec 2006 03:32:37 +0000 (UTC) (envelope-from amesbury@paulaner.oitsec.umn.edu) Received: from mail.oitsec.umn.edu (mail.oitsec.umn.edu [128.101.238.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2749043C9D for ; Sat, 2 Dec 2006 03:32:19 +0000 (GMT) (envelope-from amesbury@paulaner.oitsec.umn.edu) Received: from localhost (localhost [127.0.0.1]) by mail.oitsec.umn.edu (Postfix) with ESMTP id 360515642C for ; Fri, 1 Dec 2006 21:32:36 -0600 (CST) Received: from mail.oitsec.umn.edu ([127.0.0.1]) by localhost (mail.oitsec.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ml7Y2spmZmqQ for ; Fri, 1 Dec 2006 21:32:34 -0600 (CST) Received: from paulaner.oitsec.umn.edu (paulaner.oitsec.umn.edu [160.94.247.212]) by mail.oitsec.umn.edu (Postfix) with ESMTP id C083D5642B for ; Fri, 1 Dec 2006 21:32:34 -0600 (CST) Received: by paulaner.oitsec.umn.edu (Postfix, from userid 1169) id B308545060; Fri, 1 Dec 2006 21:32:34 -0600 (CST) Message-Id: <20061202033234.B308545060@paulaner.oitsec.umn.edu> Date: Fri, 1 Dec 2006 21:32:34 -0600 (CST) From: Alan Amesbury To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/106194: 'systat -if' display bug X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alan Amesbury List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 03:40:13 -0000 >Number: 106194 >Category: amd64 >Synopsis: 'systat -if' display bug >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 02 03:40:03 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Alan Amesbury >Release: FreeBSD 6.1-RELEASE-p10 amd64 >Organization: University of Minnesota >Environment: System: FreeBSD [REDACTED].umn.edu 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #1: Thu Oct 12 14:14:54 CDT 2006 root@[REDACTED].umn.edu:/usr/obj/usr/src/sys/[REDACTED-NONGENERIC] amd64 This is a Dell PowerEdge 850 with HTT enabled. The kernel's slightly modified from GENERIC. >Description: For large amounts of total data, FreeBSD/amd64's 'systat -if' changes units and appears to report in bits. This is an example screenshot: /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /10 Load Average |||| Interface Traffic Peak Total lo0 in 0.000 KB/s 0.000 KB/s 9.832 KB out 0.000 KB/s 0.000 KB/s 9.832 KB bge1 in 90.720 MB/s 101.412 MB/s 2903082122259256.000 b out 0.000 KB/s 0.000 KB/s 0.244 KB bge0 in 0.025 KB/s 0.395 KB/s 286.027 MB out 0.065 KB/s 0.451 KB/s 406.052 MB The host in question has been up about 50 days, so it's hard to say exactly when this display bug gets tickled. I'm pretty sure it's displaying in bits because a) the small "b" is a good hint, and more importantly b) there's no way this host has seen 2600+TB in only 50 days. 362885265282407 bytes (or around 330TB) is a believeable number, however. >How-To-Repeat: Pass multiple terabytes through an interface. Watch systat's counter. >Fix: I'm not sure, but I think this might have something to do with the stuff around line 123 of src/usr.bin/systat/ifstat.c,v 1.2 2004/03/09 11:57:27 dwmalone Exp The FreeBSD/i386 version doesn't exhibit this behavior, but the counter appears to simply wrap at 4GB anyway. I suspect that's a limitation of the architecture, though. Please let me know if you need additional information. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 12:09:59 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 431E016A415 for ; Sat, 2 Dec 2006 12:09:59 +0000 (UTC) (envelope-from michael@heinz.dinsnail.net) Received: from heinz.dinsnail.net (heinz.dinsnail.net [217.160.166.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2790143CC6 for ; Sat, 2 Dec 2006 12:09:33 +0000 (GMT) (envelope-from michael@heinz.dinsnail.net) Received: from heinz.dinsnail.net (heinz.dinsnail.net [127.0.0.1]) by heinz.dinsnail.net (8.13.8/8.13.7) with ESMTP id kB2C9die000604; Sat, 2 Dec 2006 13:09:39 +0100 Received: (from michael@localhost) by heinz.dinsnail.net (8.13.8/8.13.7/Submit) id kB2C9dTf000603; Sat, 2 Dec 2006 13:09:39 +0100 Date: Sat, 2 Dec 2006 13:09:39 +0100 From: Michael Weiser To: freebsd-amd64@freebsd.org Message-ID: <20061202120938.GC31623@dinsnail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 X-MailScanner: Found to be clean X-MailScanner-From: michael@heinz.dinsnail.net Subject: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 12:09:59 -0000 Hello, my trusty P-III died on me last week and I've bought an Athlon 64 replacement. I'm quite sure I'll get my installed FreeBSD-CURRENT to run on it in 32bit mode (i386). But to fully exploit the architecture I'd like to run it in 64bit mode (amd64). Now I'm wondering: Can I avoid reinstalling the system with amd64 binaries by cross-compiling world and kernel for amd64 on the installed i386 FreeBSD-CURRENT? I'm thinking like this: - make buildkernel ARCH=amd64 (or the like) - make installkernel - boot the 64bit kernel with the old 32bit userland - make buildworld - make installworld - mergemaster I'm not sure: - how to get a compiler that can produce an amd64 kernel with make buildkernel - if the 32bit userland will run on a 64bit kernel - if make buildworld for amd64 will work with a 32bit userland Is something like this supposed to work? Has anyone done it? Thanks in advance. -- bye, Micha Don't panic! From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 13:27:35 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B07C16A407 for ; Sat, 2 Dec 2006 13:27:35 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id D197A43C9D for ; Sat, 2 Dec 2006 13:27:13 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so2366939uge for ; Sat, 02 Dec 2006 05:27:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sBB1xlhZOjUN/jPPlAyS/aAQHJY5Ykn/0sKMl6rwPDRujP7kH/fPsF1rxjJYAexxz8HX+z8RDRlsiBTTXpllDNKxpD0WNeMCnMkLfHteegB+UXvZoKAHYJEoJk0DYeR59wxr36mox8PA16mRlUJfBtd4twLc/V4p7UrXcOs3lJ8= Received: by 10.78.181.13 with SMTP id d13mr5889292huf.1165066052720; Sat, 02 Dec 2006 05:27:32 -0800 (PST) Received: by 10.78.132.13 with HTTP; Sat, 2 Dec 2006 05:27:32 -0800 (PST) Message-ID: <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> Date: Sat, 2 Dec 2006 18:57:32 +0530 From: "Joseph Koshy" To: "Michael Weiser" In-Reply-To: <20061202120938.GC31623@dinsnail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061202120938.GC31623@dinsnail.net> Cc: freebsd-amd64@freebsd.org Subject: Re: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 13:27:35 -0000 > Can I avoid reinstalling the system with amd64 binaries by > cross-compiling world and kernel for amd64 on the installed > i386 FreeBSD-CURRENT? Yes, it is possible, do check the archives for the details. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 15:07:12 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F36616A403; Sat, 2 Dec 2006 15:07:12 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4934B43CA6; Sat, 2 Dec 2006 15:06:51 +0000 (GMT) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5DDF4.dip.t-dialin.net [84.165.221.244]) by redbull.bpaserver.net (Postfix) with ESMTP id B4F7F2E078; Sat, 2 Dec 2006 16:07:09 +0100 (CET) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by outgoing.leidinger.net (Postfix) with ESMTP id 6BDAB5B4C6C; Sat, 2 Dec 2006 16:06:48 +0100 (CET) Date: Sat, 2 Dec 2006 16:07:40 +0100 From: Alexander Leidinger To: current@freebsd.org Message-ID: <20061202160740.55046cc3@Magellan.Leidinger.net> Followup-To: current@freebsd.org X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.864, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: amd64@freebsd.org Subject: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 15:07:12 -0000 Hi, the linux module is now usable on amd64 (thanks to kib@ and his commit to the kernel linker in HEAD). I now want to sync amd64 GENERIC with i386 GENERIC. This means removing the linux stuff from amd64 GENERIC. Anyone using the GENERIC kernel on amd64 would have to load the modules, e.g., in loader.conf, like everyone else on i386. While all involved people agree with me, the consensus was to give people a chance to provide *strong* reasons to not do it. If some committers give a "go ahead" or "no objection" I will do this tomorrow, else I will wait some days (3-6). Bye, Alexander. -- 'Everything will be all right. From History's point of view, that is. There really isn't any other.' (Mort) http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 15:09:57 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 723D216A407; Sat, 2 Dec 2006 15:09:57 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26CD843CA2; Sat, 2 Dec 2006 15:09:35 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id C99891720B; Sat, 2 Dec 2006 16:10:41 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx0.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwNSXA2HS7T0; Sat, 2 Dec 2006 16:10:23 +0100 (CET) Received: by mx0.rink.nu (Postfix, from userid 1000) id 7036C17209; Sat, 2 Dec 2006 16:10:23 +0100 (CET) Date: Sat, 2 Dec 2006 16:10:23 +0100 From: Rink Springer To: Alexander Leidinger Message-ID: <20061202151023.GF13014@rink.nu> References: <20061202160740.55046cc3@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="c7hkjup166d4FzgN" Content-Disposition: inline In-Reply-To: <20061202160740.55046cc3@Magellan.Leidinger.net> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 15:09:57 -0000 --c7hkjup166d4FzgN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 02, 2006 at 04:07:40PM +0100, Alexander Leidinger wrote: > the linux module is now usable on amd64 (thanks to kib@ and his commit > to the kernel linker in HEAD). I now want to sync amd64 GENERIC > with i386 GENERIC. This means removing the linux stuff from amd64 > GENERIC. Anyone using the GENERIC kernel on amd64 would have to load > the modules, e.g., in loader.conf, like everyone else on i386. This sounds reasonable to me. --=20 Rink P.W. Springer - http://rink.nu "It's you isn't it? THE BASTARD OPERATOR FROM HELL!" "In the flesh, on the phone and in your account..." - BOFH #3 --c7hkjup166d4FzgN Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIJawYJKoZIhvcNAQcCoIIJXDCCCVgCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BuIwggObMIIDBKADAgECAhAiuN7bs9pg6t3I0n6G5OOTMA0GCSqGSIb3DQEBBQUAMGIxCzAJ BgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNjExMDgwOTI2 NTNaFw0wNzExMDgwOTI2NTNaMIHSMREwDwYDVQQEEwhTcHJpbmdlcjEaMBgGA1UEKhMRUmlu ayBQZXRlciBXeWNoZXIxIzAhBgNVBAMTGlJpbmsgUGV0ZXIgV3ljaGVyIFNwcmluZ2VyMRsw GQYJKoZIhvcNAQkBFgxtYWlsQHJpbmsubnUxHzAdBgkqhkiG9w0BCQEWEHJpbmtAZnJlZWJz ZC5vcmcxIDAeBgkqhkiG9w0BCQEWEXJpbmtAaWwuZm9udHlzLm5sMRwwGgYJKoZIhvcNAQkB Fg1yaW5rQHN0YWNrLm5sMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxryGDfel YzzENX7wodkbVY1NALfaiPfNEG10YjD8ZWdK9zkN26Tc878Shbqapq0KYFD8TACGfEhKoMvo qbf0PHAS/gNYr81Arqa9FRPUfzvtDE/cMbhvI+p7ufBITyYnPJp9MUD72iT+DohRR2ISVi3i NAEgDuSbYYNxctnvXqU6O6EPy3mzoFPDoiOQwBfVtFrjxBbND9BUK2bjtUyGt4x8I/Vulzrt qLPTokva+b97DHRgbCA/aLLYIrU6QoqOFJ8GrAbro/FZLYh4m1oJk3FEHVQOKkk7xzIaFmmP QGJRL8m6nrIZFTrQ+X2wmzfLD55K/UiqbekOuMiWbY9EbwIDAQABo10wWzBLBgNVHREERDBC gQxtYWlsQHJpbmsubnWBEHJpbmtAZnJlZWJzZC5vcmeBEXJpbmtAaWwuZm9udHlzLm5sgQ1y aW5rQHN0YWNrLm5sMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEFBQADgYEAIfIcieRjePBA wjZqvOdGpyPcNDnK/ubeQSTV5Y4AHWxm1sXhQxB/XrQ3RVdz1qDnBRL1AjkEBAl8e9+am4s6 D6TaSlmJeNXn6ZPJTQecisz3M+AKiMckShM3oAeUi0ktn1yNYR+hz5aQN612XT5OZRYznJVZ kPf1DiA2RVVyz+MwggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQG EwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNV BAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2Vz IERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkq hkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAw WhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1 bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElz c3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUE cJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH 5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBly YLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJo dHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNV HQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0G CSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYv wPQcUCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3 h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYICUTCCAk0CAQEwdjBiMQsw CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoG A1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECECK43tuz2mDq3cjS fobk45MwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3 DQEJBTEPFw0wNjEyMDIxNTEwMjNaMCMGCSqGSIb3DQEJBDEWBBQDZ2hpL4Gp1gW8LwKoHHgX DytxoTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASCAQAH qQVrC/fy7me7E5vy4XTeLq+l0gaF3JE0bZaxtoAzU/GyvOWpBlnNuFeFI/+/pj14o+QQs9ZW BeTD5O4t0UpWZhavq21vaU68MitJMZwAwaJZvDi7qgLZKQIYRqarAbtgdU6heiXF/xypneYo 8zqVwMjlzgj/o492x68ZXKhiKiYOHM4h1/59D9YuK49bDevNpPLd5gn0PKT8g/Pr1gOsIhb+ +dxWp1udHKD/NzDQI01hHimu8eSmk/MXq0r22mLolYio5ZDqdavlNjNxyFzH03z1dXlgxzNJ y8bCj7NQ/S+YbSfIqI684hlcqUw4ZrSEILAjrj2vKAXksamTIpG4 --c7hkjup166d4FzgN-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 17:01:22 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 92A0B16A407 for ; Sat, 2 Dec 2006 17:01:22 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E9F343CA7 for ; Sat, 2 Dec 2006 17:00:58 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id F0AA06B77; Sat, 2 Dec 2006 20:01:18 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id CE75B65B4; Sat, 2 Dec 2006 20:01:18 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id kB2H1O7D032146; Sat, 2 Dec 2006 20:01:24 +0300 (MSK) (envelope-from ru) Date: Sat, 2 Dec 2006 20:01:24 +0300 From: Ruslan Ermilov To: Joseph Koshy Message-ID: <20061202170124.GD31897@rambler-co.ru> References: <20061202120938.GC31623@dinsnail.net> <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gE7i1rD7pdK0Ng3j" Content-Disposition: inline In-Reply-To: <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-amd64@freebsd.org Subject: Re: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 17:01:22 -0000 --gE7i1rD7pdK0Ng3j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 02, 2006 at 06:57:32PM +0530, Joseph Koshy wrote: > >Can I avoid reinstalling the system with amd64 binaries by > >cross-compiling world and kernel for amd64 on the installed > >i386 FreeBSD-CURRENT? >=20 > Yes, it is possible, do check the archives for the details. >=20 We've been doing this "upgrade" last week; compared to the last time I checked it, the 32-bit compatibility only improved, so the whole process was much simpler, and basically was like this: - cross-compile amd64 world and kernel on i386 - install the amd64 kernel - reboot with the amd64 kernel and i386 world into single user mode. At this point, the dynamically linked i386 binaries could not be used because ld-elf32.so.1 is not yet available, so we used /rescue binaries to do what's needed (re-mount root file system r/w, mount other file systems, etc.) - after that, we installed the amd64 world by faking it into thinking that it's running on the i386 box and cross-install to amd64 (because object directories are layed out for this during the build): env MACHINE_ARCH=3Di386 MACHINE=3Di386 \ make TARGET_ARCH=3Damd64 \ DESTDIR=3D/ installworld - after that, run mergemaster(8) to update /etc, and you should be able to boot into amd64 multiuser mode. I wouldn't recommend this procedure for those not familiar with the internals of the build process. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --gE7i1rD7pdK0Ng3j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFcbFkqRfpzJluFF4RAn9sAKCSSDahfSZsB8dXEBTIKB1fm39psACcCPel PUDOYJl/dtkRR3jxE6qiMgs= =/hnF -----END PGP SIGNATURE----- --gE7i1rD7pdK0Ng3j-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 17:10:16 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 487C316A412 for ; Sat, 2 Dec 2006 17:10:16 +0000 (UTC) (envelope-from mwm-dated-1165943423.41c24b@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 935B943CAC for ; Sat, 2 Dec 2006 17:09:48 +0000 (GMT) (envelope-from mwm-dated-1165943423.41c24b@mired.org) Received: (qmail 99408 invoked by uid 1001); 2 Dec 2006 17:10:23 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Sat, 02 Dec 2006 12:10:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17777.45950.536177.528750@bhuda.mired.org> Date: Sat, 2 Dec 2006 12:10:22 -0500 To: Ruslan Ermilov In-Reply-To: <20061202170124.GD31897@rambler-co.ru> References: <20061202120938.GC31623@dinsnail.net> <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> <20061202170124.GD31897@rambler-co.ru> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-amd64@freebsd.org Subject: Re: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 17:10:16 -0000 In <20061202170124.GD31897@rambler-co.ru>, Ruslan Ermilov typed: > On Sat, Dec 02, 2006 at 06:57:32PM +0530, Joseph Koshy wrote: > > >Can I avoid reinstalling the system with amd64 binaries by > > >cross-compiling world and kernel for amd64 on the installed > > >i386 FreeBSD-CURRENT? > > > > Yes, it is possible, do check the archives for the details. > > > We've been doing this "upgrade" last week; > compared to the last time I checked it, the > 32-bit compatibility only improved, so the > whole process was much simpler, and basically > was like this: I went through it a month or so ago. I'll add one bit of advice: Drop in a spare disk and dual boot during the transition. My system disk was mirrored, and I turned that off and set up one of the two as amd64 during the transition, then turned the mirror back on when it was done. That also makes the cross-compile installation process easier, as you can mount the second disk on your i386 system and just just install to it. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 17:13:14 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A43D716A417 for ; Sat, 2 Dec 2006 17:13:14 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC89243CA6 for ; Sat, 2 Dec 2006 17:12:52 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 027F8731F; Sat, 2 Dec 2006 20:13:13 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id EC8347319; Sat, 2 Dec 2006 20:13:12 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id kB2HDIbF032401; Sat, 2 Dec 2006 20:13:18 +0300 (MSK) (envelope-from ru) Date: Sat, 2 Dec 2006 20:13:18 +0300 From: Ruslan Ermilov To: Mike Meyer Message-ID: <20061202171318.GA32377@rambler-co.ru> References: <20061202120938.GC31623@dinsnail.net> <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> <20061202170124.GD31897@rambler-co.ru> <17777.45950.536177.528750@bhuda.mired.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <17777.45950.536177.528750@bhuda.mired.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-amd64@freebsd.org Subject: Re: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 17:13:14 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 02, 2006 at 12:10:22PM -0500, Mike Meyer wrote: > In <20061202170124.GD31897@rambler-co.ru>, Ruslan Ermilov typed: > > On Sat, Dec 02, 2006 at 06:57:32PM +0530, Joseph Koshy wrote: > > > >Can I avoid reinstalling the system with amd64 binaries by > > > >cross-compiling world and kernel for amd64 on the installed > > > >i386 FreeBSD-CURRENT? > > >=20 > > > Yes, it is possible, do check the archives for the details. > > >=20 > > We've been doing this "upgrade" last week; > > compared to the last time I checked it, the > > 32-bit compatibility only improved, so the > > whole process was much simpler, and basically > > was like this: >=20 > I went through it a month or so ago. I'll add one bit of advice: >=20 > Drop in a spare disk and dual boot during the transition. My system > disk was mirrored, and I turned that off and set up one of the two as > amd64 during the transition, then turned the mirror back on when it > was done. >=20 > That also makes the cross-compile installation process easier, as you > can mount the second disk on your i386 system and just just install to > it. >=20 That's not sexy; with two disks you can install amd64 bits on a spare disk under i386 without problems, boot from the new disk, and so on, but this would not be called the "in-place upgrade from i386 to amd64" then. ;) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFcbQuqRfpzJluFF4RAitEAJ9S0KZfky6oeK/CjI2+bJQewk43dgCfSd9l nmRdCSKI1lO0Ph+7ZL+GJ3Y= =nCne -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 17:30:59 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E31CB16A416 for ; Sat, 2 Dec 2006 17:30:59 +0000 (UTC) (envelope-from mwm-dated-1165944672.5f9d4a@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id B9B1043CA3 for ; Sat, 2 Dec 2006 17:30:37 +0000 (GMT) (envelope-from mwm-dated-1165944672.5f9d4a@mired.org) Received: (qmail 99655 invoked by uid 1001); 2 Dec 2006 17:31:12 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Sat, 02 Dec 2006 12:31:12 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17777.47200.238259.933313@bhuda.mired.org> Date: Sat, 2 Dec 2006 12:31:12 -0500 To: Ruslan Ermilov In-Reply-To: <20061202171318.GA32377@rambler-co.ru> References: <20061202120938.GC31623@dinsnail.net> <84dead720612020527k644f67d1h36c715a2cbfd4c53@mail.gmail.com> <20061202170124.GD31897@rambler-co.ru> <17777.45950.536177.528750@bhuda.mired.org> <20061202171318.GA32377@rambler-co.ru> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-amd64@freebsd.org Subject: Re: Cross compile world on i386 to x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 17:31:00 -0000 In <20061202171318.GA32377@rambler-co.ru>, Ruslan Ermilov typed: > On Sat, Dec 02, 2006 at 12:10:22PM -0500, Mike Meyer wrote: > > In <20061202170124.GD31897@rambler-co.ru>, Ruslan Ermilov typed: > > > On Sat, Dec 02, 2006 at 06:57:32PM +0530, Joseph Koshy wrote: > > > > >Can I avoid reinstalling the system with amd64 binaries by > > > > >cross-compiling world and kernel for amd64 on the installed > > > > >i386 FreeBSD-CURRENT? > > > > > > > > Yes, it is possible, do check the archives for the details. > > > > > > > We've been doing this "upgrade" last week; > > > compared to the last time I checked it, the > > > 32-bit compatibility only improved, so the > > > whole process was much simpler, and basically > > > was like this: > > > > I went through it a month or so ago. I'll add one bit of advice: > > > > Drop in a spare disk and dual boot during the transition. My system > > disk was mirrored, and I turned that off and set up one of the two as > > amd64 during the transition, then turned the mirror back on when it > > was done. > > > > That also makes the cross-compile installation process easier, as you > > can mount the second disk on your i386 system and just just install to > > it. > > > That's not sexy; with two disks you can install amd64 bits > on a spare disk under i386 without problems, boot from the > new disk, and so on, but this would not be called the > "in-place upgrade from i386 to amd64" then. ;) Yup, not sexy at all. There's almost no danger of leaving your system unbootable, and being able to trivially back it out if you decide to for some reason (like a critical application not working on amd64) is like wearing suspenders and a belt. I admit, I probably wouldn't have done that if I didn't have a mirrored system disk, but since I could do it without actually touching the hardware... http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 19:43:03 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D898816A407; Sat, 2 Dec 2006 19:43:03 +0000 (UTC) (envelope-from bsam@bsam.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EFBF43CA6; Sat, 2 Dec 2006 19:42:38 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru ([83.239.48.149]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id kB2JgdiP041812; Sat, 2 Dec 2006 22:42:50 +0300 (MSK) Received: from bsam by bsam.ru with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GqajD-0000DP-5c; Sat, 02 Dec 2006 22:40:51 +0300 To: Alexander Leidinger References: <20061202160740.55046cc3@Magellan.Leidinger.net> From: Boris Samorodov Date: Sat, 02 Dec 2006 22:40:51 +0300 In-Reply-To: <20061202160740.55046cc3@Magellan.Leidinger.net> (Alexander Leidinger's message of "Sat, 2 Dec 2006 16:07:40 +0100") Message-ID: <68623948@bsam.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Boris Samorodov Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 19:43:04 -0000 On Sat, 2 Dec 2006 16:07:40 +0100 Alexander Leidinger wrote: > the linux module is now usable on amd64 (thanks to kib@ and his commit > to the kernel linker in HEAD). Cvsupped a couple of hours ago my amd64-current, rebuilt/reinstalled world/kernel. The kernel is GENERIC without COMPAT_LINUX32, LINPROCFS, LINSYSFS. But linux.ko hadn't been built. Should I cvsup once more or did I miss something? I'd tested kib@ patches (about two weeks ago) and noticed that linux kernel module can't be unloaded _after_ mounting/unmounting linprocfs, linsysfs or linux devfs. Can anybody confirm? > I now want to sync amd64 GENERIC > with i386 GENERIC. This means removing the linux stuff from amd64 > GENERIC. Anyone using the GENERIC kernel on amd64 would have to load > the modules, e.g., in loader.conf, like everyone else on i386. Quite reasonable. > While all involved people agree with me, the consensus was to give > people a chance to provide *strong* reasons to not do it. > If some committers give a "go ahead" or "no objection" I will do this > tomorrow, else I will wait some days (3-6). No objection from my part (though I'm only a ports committer). Thanks for taking care of it. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 20:21:03 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76CAB16A412; Sat, 2 Dec 2006 20:21:03 +0000 (UTC) (envelope-from bsam@bsam.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83E9D43CA3; Sat, 2 Dec 2006 20:20:40 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru ([83.239.48.204]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id kB2KKh4T045050; Sat, 2 Dec 2006 23:20:53 +0300 (MSK) Received: from bsam by bsam.ru with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GqbK2-0000DV-U2; Sat, 02 Dec 2006 23:18:54 +0300 To: Alexander Leidinger References: <20061202160740.55046cc3@Magellan.Leidinger.net> <68623948@bsam.ru> From: Boris Samorodov Date: Sat, 02 Dec 2006 23:18:54 +0300 In-Reply-To: <68623948@bsam.ru> (Boris Samorodov's message of "Sat, 02 Dec 2006 22:40:51 +0300") Message-ID: <93587377@bsam.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Boris Samorodov Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 20:21:03 -0000 On Sat, 02 Dec 2006 22:40:51 +0300 Boris Samorodov wrote: > Should I cvsup once more Yep, I noticed that I have 1.513 for src/sys/modules/Makefile while it should be 1.514. Sorry for the noice here. /me going to re-cvsup. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 20:42:53 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7ABC216A40F; Sat, 2 Dec 2006 20:42:53 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7407743CA5; Sat, 2 Dec 2006 20:42:29 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id kB2Kgn3k063126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Dec 2006 21:42:49 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id kB2Kgn95063125; Sat, 2 Dec 2006 21:42:49 +0100 (CET) Date: Sat, 2 Dec 2006 21:42:49 +0100 From: Divacky Roman To: Alexander Leidinger Message-ID: <20061202204249.GA61777@stud.fit.vutbr.cz> References: <20061202160740.55046cc3@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061202160740.55046cc3@Magellan.Leidinger.net> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 20:42:53 -0000 On Sat, Dec 02, 2006 at 04:07:40PM +0100, Alexander Leidinger wrote: > Hi, > > the linux module is now usable on amd64 (thanks to kib@ and his commit > to the kernel linker in HEAD). I now want to sync amd64 GENERIC > with i386 GENERIC. This means removing the linux stuff from amd64 > GENERIC. Anyone using the GENERIC kernel on amd64 would have to load > the modules, e.g., in loader.conf, like everyone else on i386. > > While all involved people agree with me, the consensus was to give > people a chance to provide *strong* reasons to not do it. > > If some committers give a "go ahead" or "no objection" I will do this > tomorrow, else I will wait some days (3-6). go for it... among other things this enables MUCH easier testing of patches on amd64 for ordinary people (not having to reboot the system) roman From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 20:50:05 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0ED0816A40F for ; Sat, 2 Dec 2006 20:50:05 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3AAB43CA6 for ; Sat, 2 Dec 2006 20:49:41 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so3721251nfc for ; Sat, 02 Dec 2006 12:50:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=gb4jIkmdTKz/6uJBnOMG4OA4PSfTMkTDRxtGnWTXGejlMCNsVDxb8T7YhH068Uq4lBMzdQl58yXcO3jXouzzhmMWqjBpuHP0KGAVYzjwmkNDIgDHbV0m+4wCRc9lObsuO4aip8FiJ0F26lCM4iSmfGz1YGKYFt1JFi+eEZ0GXsg= Received: by 10.78.158.11 with SMTP id g11mr6130068hue.1165092602594; Sat, 02 Dec 2006 12:50:02 -0800 (PST) Received: by 10.78.167.16 with HTTP; Sat, 2 Dec 2006 12:49:57 -0800 (PST) Message-ID: Date: Sat, 2 Dec 2006 23:49:57 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Divacky Roman" In-Reply-To: <20061202204249.GA61777@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061202160740.55046cc3@Magellan.Leidinger.net> <20061202204249.GA61777@stud.fit.vutbr.cz> X-Google-Sender-Auth: 65dfd3cf8638d97b Cc: amd64@freebsd.org, Alexander Leidinger , Kostik Belousov , current@freebsd.org Subject: Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 20:50:05 -0000 On 12/2/06, Divacky Roman wrote: > On Sat, Dec 02, 2006 at 04:07:40PM +0100, Alexander Leidinger wrote: > > Hi, > > > > the linux module is now usable on amd64 (thanks to kib@ and his commit > > to the kernel linker in HEAD). I now want to sync amd64 GENERIC > > with i386 GENERIC. This means removing the linux stuff from amd64 > > GENERIC. Anyone using the GENERIC kernel on amd64 would have to load > > the modules, e.g., in loader.conf, like everyone else on i386. > > > > While all involved people agree with me, the consensus was to give > > people a chance to provide *strong* reasons to not do it. > > > > If some committers give a "go ahead" or "no objection" I will do this > > tomorrow, else I will wait some days (3-6). > > go for it... among other things this enables MUCH easier testing of > patches on amd64 for ordinary people (not having to reboot the system) I concur :-) Thanks, Alexander! Thanks, Kostik! From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 2 23:20:45 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA04B16A415; Sat, 2 Dec 2006 23:20:45 +0000 (UTC) (envelope-from bsam@bsam.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3301543CC0; Sat, 2 Dec 2006 23:20:18 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru ([83.239.48.150]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id kB2NKGQS061352; Sun, 3 Dec 2006 02:20:30 +0300 (MSK) Received: from bsam by bsam.ru with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1Gqe7o-0000DK-V1; Sun, 03 Dec 2006 02:18:28 +0300 To: Alexander Leidinger References: <20061202160740.55046cc3@Magellan.Leidinger.net> <68623948@bsam.ru> From: Boris Samorodov Date: Sun, 03 Dec 2006 02:18:28 +0300 In-Reply-To: <68623948@bsam.ru> (Boris Samorodov's message of "Sat, 02 Dec 2006 22:40:51 +0300") Message-ID: <15016603_-_@bsam.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Boris Samorodov Cc: amd64@freebsd.org, current@freebsd.org Subject: [panic] Re: small heads-up: Syncing amd64 GENERIC with i386 GENERIC (removing LINUX stuff) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 23:20:45 -0000 On Sat, 02 Dec 2006 22:40:51 +0300 Boris Samorodov wrote: > On Sat, 2 Dec 2006 16:07:40 +0100 Alexander Leidinger wrote: > > the linux module is now usable on amd64 (thanks to kib@ and his commit > > to the kernel linker in HEAD). > Cvsupped a couple of hours ago my amd64-current, rebuilt/reinstalled > world/kernel. The kernel is GENERIC without COMPAT_LINUX32, LINPROCFS, > LINSYSFS. But linux.ko hadn't been built. Should I cvsup once more or > did I miss something? > I'd tested kib@ patches (about two weeks ago) and noticed that linux > kernel module can't be unloaded _after_ mounting/unmounting linprocfs, > linsysfs or linux devfs. Can anybody confirm? OK, after cvsup and rebuild/install kernel I do: # kldload linux # kldload linsysfs # kldunload linsysfs and get a reprodusable panic: ----- Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffffa33a2584 stack pointer = 0x10:0xffffffffa0ff4a50 frame pointer = 0x10:0xffffffffa0ff4a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 717 (kldunload) panic: from debugger cpuid = 0 Uptime: 35s Physical memory: 1012 MB Dumping 155 MB: 140 124 108 92 76 60 44 28 12 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) where #0 doadump () at pcpu.h:172 #1 0xffffffff8043c3e9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:411 #2 0xffffffff8043be7b in panic (fmt=0xffffffff8069d087 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:567 #3 0xffffffff801acd87 in db_panic (addr=0, have_addr=0, count=0, modif=0x0) at /usr/src/sys/ddb/db_command.c:433 #4 0xffffffff801ad229 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xffffffff801af133 in db_trap (type=-1593882688, code=0) at /usr/src/sys/ddb/db_main.c:222 #6 0xffffffff804624f8 in kdb_trap (type=9, code=0, tf=0xffffffffa0ff49a0) at /usr/src/sys/kern/subr_kdb.c:502 #7 0xffffffff8064abd1 in trap_fatal (frame=0xffffffffa0ff49a0, eva=18446742975218145296) at /usr/src/sys/amd64/amd64/trap.c:692 #8 0xffffffff8064b191 in trap (frame= {tf_rdi = -2137684416, tf_rsi = -1098491406320, tf_rdx = 0, tf_rcx = 683, tf_r8 = -2140136456, tf_r9 = -1098491406320, tf_rax = 0, tf_rbx = -2401050962867404578, tf_rbp = -1593882000, tf_r10 = 0, tf_r11 = 0, tf_r12 = -1556469664, tf_r13 = -1098768417664, tf_r14 = 0, tf_r15 = 0, tf_trapno = 9, tf_addr = 0, tf_flags = -2143094431, tf_err = 0, tf_rip = -1556470396, tf_cs = 8, tf_rflags = 66182, tf_rsp = -1593882016, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:500 #9 0xffffffff8063309b in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #10 0xffffffffa33a2584 in ?? () #11 0xffffffffa33a2860 in ?? () #12 0xffffffffa33a2860 in ?? () #13 0xffffffffa0ff4aa0 in ?? () #14 0xffffffff804a692e in vfs_modevent (mod=0xffffffff80958640, type=1020221456, data=0xffffffffa33a2860) at /usr/src/sys/kern/vfs_init.c:257 (kgdb) ----- WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve