From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 20 04:17:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC26A16A420 for ; Sun, 20 Nov 2005 04:17:33 +0000 (GMT) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF03A43D45 for ; Sun, 20 Nov 2005 04:17:33 +0000 (GMT) (envelope-from marquis@roble.com) Date: Sat, 19 Nov 2005 20:17:33 -0800 (PST) From: Roger Marquis To: freebsd-amd64@freebsd.org In-Reply-To: <20051119120051.39BE216A41F@hub.freebsd.org> Message-ID: <20051119200222.V2029@roble.com> References: <20051119120051.39BE216A41F@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Hardware RAID support? Which controller best to use? 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, 20 Nov 2005 04:17:34 -0000 Olaf Greve wrote: >> I've had far better luck using SATA over SCSI in the recent couple of years. >> We have several machines setup using FreeBSD and 3Ware RAID 0+1 that routinely >> run with no problems and uptimes of 200 to 300 days at a time. > > Very interesting to know. At present, I myself have a 754 socket AMD > Athlon 64 3.2 GHz (IIRC), running FreeBSD 5.4 release AMD-64, with an > Adaptec 2200S U320 SCSI RAID controller with 4 Maxtor Atlas 10KIV 36GB > drives attached to it in RAID-10 mode. So far it works a charm (though I > too had to effectively downgrade it to U160 due to the lack of 64-bits > PCI slots, grrr). For most applications the MTBF of SATA equals that of SCSI and has for several months now. You can run into maintenance problems by not being able to map-out bad blocks under SATA but then drives with those should be swapped out anyhow. Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD or are not mature. Adaptec SCSI RAID is also not as well supported as some of the SATA RAID cards. The critical difference between SATA and SCSI RAID, aside from price, is performance under load. In this department SCSI still outperforms SATA by a substantial margin. Add 15K drives and FCAL and you're talking night and day. Then again, most servers that need this kind of IO run Solaris and also benefit from all the software (Veritas, Legato, ...) built for it. Most FreeBSD servers, OTOH, will do nicely with SATA. ray@redshift.com wrote: >Basically, you just install the card, boot into the RAID bios >using Alt+3 and then you follow a simple menu to build whatever >type of raid you want. Jeez I wish they wouldn't do that, require ctl or alt keys that is. Alt key menus are worthless through a serial console. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 20 04:18:03 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A9D416A420; Sun, 20 Nov 2005 04:18:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E888C43D45; Sun, 20 Nov 2005 04:18:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAK4I19M010936; Sat, 19 Nov 2005 21:18:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <437FF8F9.8000207@samsco.org> Date: Sat, 19 Nov 2005 21:18:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> In-Reply-To: <200511182206.49195.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) 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, 20 Nov 2005 04:18:03 -0000 John Baldwin wrote: > On Friday 18 November 2005 07:18 pm, Matthew Dillon wrote: > >>:So the amd64 snapshot didn't boot but the i386 one did? Interesting. >>:Thanks a lot for investigating this. >>: >>:Scott >> >> Yup. My guess is that the 64-bit boot issue that early in the boot >> sequence is something stupid simple. It looks it from the consistency >> of the crash. > > > Actually, your comments about the stray ICU interrupts led me to it on the way > home tonight. Peter has a hack in amd64 that if you don't include 'device > atpic' in your kernel config (not in GENERIC amd64 by default in HEAD) he > just masks the PICs. However, he doesn't setup handlers for the spurious > interrupts that can still occur (since they are unmaskable). Couple that > with the fact that HEAD (until a few hours ago) didn't print the trap message > for a T_RESERVED trap, and you'll see that your panic on amd64 was caused by > a spurious ICU interrupt. I have part of peter's hack expanded to do a full > reset of the ICUs, and I'll update it for Monday to adjust the base interrupt > such that the spurious ICU vectors get sent to the APIC spurious interrupt > vector. That should fix your issue as well as the same issue reported by > someone else on the amd64@ list recently. > Does this imply that the 'correct' fix involves catching the stray ICU interrupt via a trap handler? How often do these interrupts happen, and therefore what is the performance consequence to having to handle them? Scott From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 20 08:06:55 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C4D216A41F; Sun, 20 Nov 2005 08:06:55 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3765F43D49; Sun, 20 Nov 2005 08:06:55 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAK86USJ026004; Sun, 20 Nov 2005 00:06:30 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAK86S22026001; Sun, 20 Nov 2005 00:06:28 -0800 (PST) Date: Sun, 20 Nov 2005 00:06:28 -0800 (PST) From: Matthew Dillon Message-Id: <200511200806.jAK86S22026001@apollo.backplane.com> To: Scott Long References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> <437FF8F9.8000207@samsco.org> Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) 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, 20 Nov 2005 08:06:55 -0000 :... :> a spurious ICU interrupt. I have part of peter's hack expanded to do a full :> reset of the ICUs, and I'll update it for Monday to adjust the base interrupt :> such that the spurious ICU vectors get sent to the APIC spurious interrupt :> vector. That should fix your issue as well as the same issue reported by :> someone else on the amd64@ list recently. :> : :Does this imply that the 'correct' fix involves catching the stray ICU :interrupt via a trap handler? How often do these interrupts happen, :and therefore what is the performance consequence to having to handle :them? : :Scott I think John has the right fix in mind. You have to catch the stray interrupt vector for every interrupt controller in the system. This means the 8259 stray vector AND the LAPIC stray vector, even if one or both devices is completely disabled. Whether this represents a performance problem depends on the situation. If any interrupts are routed through the 8259 at all then the BIOS misprogramming bug I mentioned earlier will result in each real interrupt also causing a stray interrupt (due to the double INT A cycle). Clearly this is not desirable. If the 8259 is 100% disabled I think the duplicate stray interrupts will go away. Even under perfect conditions a stray interrupt can occur during programming or reprogramming of the 8259. This would not cause a performance issue, just result in an occassional stray. For example, if the 8259 issues an IRQ to the cpu and the IRQ source is masked while the cpu is doing an INT A cycle, the 8259 will return the stray interrupt vector. With regards to the LAPICs the story is slightly better. The stray interrupt vector can be programmed into the LAPIC and the interrupt service routine basically doesn't have to do a thing, not even EOI. A stray LAPIC interrupt can occur in a number of situations but I do not believe any of them would result in the same braindamage that you get from broken 8259 routing. One example of stray generation here would be if you changed the TPR while the LAPIC is responding to the cpu's INT A cycle. One thing this does imply is that we should never, ever overlap the 8259 interrupt vector space with the LAPIC vector space. I wonder if the LAPIC EOI lockup issue might be explained by an 8259 returning its stray vector that is misinterpreted as an LAPIC interrupt. Since there is no way to determine what IRQ an LAPIC EOI is actually servicing (except by checking the ISR to see what bit actually got cleared), any sort of misinterpretation will result in disaster. That means I have some work to do in DragonFly which is still using the separate FAST/SLOW vector code with the LAPIC 'SLOW' interrupts overlapping the 8259 vector space. The 8259's stray interrupt vector is BASE+7 (usually 0x20 + 7). I suspect that BASE+15 might also occur sometimes. The only way to completely avoid getting stray 8259 vectors would be to *NEVER* mess with the interrupt masks. I don't think that CLI/STI would work here, the INT A cycle is almost guarenteed to be decoupled from the instruction stream. In fact, at least on the AMD, the hypertransport layer will do the cycle and queue a pending vector until it can be delivered to the cpu (from my read). That is clearly a problem since we pretty much have to mess with the masks to deal with level interrupt sources. Or to disable the 8259 completely, which is the solution John mentioned to me. -Matt Matthew Dillon From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 20 10:51:00 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D844916A41F; Sun, 20 Nov 2005 10:51:00 +0000 (GMT) (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 754B243D46; Sun, 20 Nov 2005 10:51:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jAKAowLJ099440; Sun, 20 Nov 2005 05:50:58 -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.3/8.13.3) with ESMTP id jAKAoxGh009041; Sun, 20 Nov 2005 05:50:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2609D7302F; Sun, 20 Nov 2005 05:50:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120105059.2609D7302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 05:50:59 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 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, 20 Nov 2005 10:51:01 -0000 TB --- 2005-11-20 09:02:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 09:02:32 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-20 09:02:32 - cleaning the object tree TB --- 2005-11-20 09:02:48 - checking out the source tree TB --- 2005-11-20 09:02:48 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-20 09:02:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 09:09:14 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 09:09:14 - cd /src TB --- 2005-11-20 09:09:14 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-11-20 10:39:33 - generating LINT kernel config TB --- 2005-11-20 10:39:33 - cd /src/sys/amd64/conf TB --- 2005-11-20 10:39:33 - /usr/bin/make -B LINT TB --- 2005-11-20 10:39:33 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 10:39:33 - cd /src TB --- 2005-11-20 10:39:33 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 10:39:33 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netinet6/udp6_usrreq.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_cksum.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_input.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 10:50:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 10:50:58 - ERROR: failed to build lint kernel TB --- 2005-11-20 10:50:58 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 20 16:47:56 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD34616A41F; Sun, 20 Nov 2005 16:47:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E21C43D45; Sun, 20 Nov 2005 16:47:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAKGlllG014242; Sun, 20 Nov 2005 09:47:47 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4380A8B2.2090008@samsco.org> Date: Sun, 20 Nov 2005 09:47:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> <437FF8F9.8000207@samsco.org> <200511200806.jAK86S22026001@apollo.backplane.com> In-Reply-To: <200511200806.jAK86S22026001@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) 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, 20 Nov 2005 16:47:56 -0000 Matthew Dillon wrote: > :... > :> a spurious ICU interrupt. I have part of peter's hack expanded to do a full > :> reset of the ICUs, and I'll update it for Monday to adjust the base interrupt > :> such that the spurious ICU vectors get sent to the APIC spurious interrupt > :> vector. That should fix your issue as well as the same issue reported by > :> someone else on the amd64@ list recently. > :> > : > :Does this imply that the 'correct' fix involves catching the stray ICU > :interrupt via a trap handler? How often do these interrupts happen, > :and therefore what is the performance consequence to having to handle > :them? > : > :Scott > > I think John has the right fix in mind. You have to catch the stray > interrupt vector for every interrupt controller in the system. This > means the 8259 stray vector AND the LAPIC stray vector, even if one or > both devices is completely disabled. > > Whether this represents a performance problem depends on the situation. > If any interrupts are routed through the 8259 at all then the BIOS > misprogramming bug I mentioned earlier will result in each real > interrupt also causing a stray interrupt (due to the double INT A cycle). > Clearly this is not desirable. If the 8259 is 100% disabled I think > the duplicate stray interrupts will go away. > > Even under perfect conditions a stray interrupt can occur during > programming or reprogramming of the 8259. This would not cause a > performance issue, just result in an occassional stray. For example, > if the 8259 issues an IRQ to the cpu and the IRQ source is masked > while the cpu is doing an INT A cycle, the 8259 will return the stray > interrupt vector. > > With regards to the LAPICs the story is slightly better. The stray > interrupt vector can be programmed into the LAPIC and the interrupt > service routine basically doesn't have to do a thing, not even EOI. > A stray LAPIC interrupt can occur in a number of situations but I > do not believe any of them would result in the same braindamage that > you get from broken 8259 routing. One example of stray generation here > would be if you changed the TPR while the LAPIC is responding to the > cpu's INT A cycle. > > One thing this does imply is that we should never, ever overlap the > 8259 interrupt vector space with the LAPIC vector space. I wonder if > the LAPIC EOI lockup issue might be explained by an 8259 returning its > stray vector that is misinterpreted as an LAPIC interrupt. Since there > is no way to determine what IRQ an LAPIC EOI is actually servicing > (except by checking the ISR to see what bit actually got cleared), any > sort of misinterpretation will result in disaster. That means I have > some work to do in DragonFly which is still using the separate FAST/SLOW > vector code with the LAPIC 'SLOW' interrupts overlapping the 8259 > vector space. > > The 8259's stray interrupt vector is BASE+7 (usually 0x20 + 7). I > suspect that BASE+15 might also occur sometimes. The only way to > completely avoid getting stray 8259 vectors would be to *NEVER* mess > with the interrupt masks. I don't think that CLI/STI would work here, > the INT A cycle is almost guarenteed to be decoupled from the > instruction stream. In fact, at least on the AMD, the hypertransport > layer will do the cycle and queue a pending vector until it can be > delivered to the cpu (from my read). > > That is clearly a problem since we pretty much have to mess with the > masks to deal with level interrupt sources. Or to disable the 8259 > completely, which is the solution John mentioned to me. > > -Matt > Matthew Dillon > It turns out that the T_RESERVED trap only gets hit once, when the second CPU is being started. Looks like an easy fix. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 08:35:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A1E416A41F for ; Mon, 21 Nov 2005 08:35:23 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ED1643D75 for ; Mon, 21 Nov 2005 08:35:20 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ee78u-0001E3-00 for ; Mon, 21 Nov 2005 09:35:18 +0100 Message-ID: <438186C3.30608@axis.nl> Date: Mon, 21 Nov 2005 09:35:15 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> In-Reply-To: <20051119200222.V2029@roble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 08:35:23 -0000 Hi all, Thanks a lot for the many replies; over the weekend I have been incommunicado, hence the late reply. I have forwarded the relevant e-mails to the person who asked me for this inquiry, and I think he should have enough information in order to choose a good hardware set-up. I'll try to get him to buy one of those 9500S-4 controllers, and then I can rest assured that I'll be able to set it up without too many surprises. ;) Regarding the benchmarking: I'll try to see if I can run it on my live server, the only issue being of course that the results will be polluted, as I can't really take it off-line (or rather: I don't want to). If the test runs quickly I might temporarily kill Sendmail and Apache to eliminate the majority of the user load, and then run it... I'll have a look-see when I have a bit more time. :) Good: AFAIC, FreeBSD amd64 it is, with the 9500S-4 (in RAID-10 mode probably)! :) Cheers! Olafo PS: I will probably reply off-list to some of the specific MySQL tuning/compilation questions... From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 08:59:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B980D16A41F for ; Mon, 21 Nov 2005 08:59:40 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B4243D45 for ; Mon, 21 Nov 2005 08:59:40 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ee7V6-0004Ve-00 for ; Mon, 21 Nov 2005 09:58:12 +0100 Message-ID: <43818C1F.50203@axis.nl> Date: Mon, 21 Nov 2005 09:58:07 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> In-Reply-To: <20051119200222.V2029@roble.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 08:59:40 -0000 Hi all, Well, the plot thickens and I have another follow-up question after all... I relayed the information I gathered from you all, and the person in charge indicated that he couldn't get the 9500S-4 directly from their normal supplier. They are somewhat pressed for installing the machine very soon, so he asked me if I knew if the Adaptec 2410SA would also work well... The details of this adapter can be found at: http://www.adaptec.com/worldwide/product/proddetail.html?sess=no&language=English+US&prodkey=AAR-2410SA&cat=%2fTechnology%2fSerial+ATA%2fSerial+ATA+RAID+Controllers Surprise, surprise, once again FreeBSD is not mentioned on the list of supported OSes (do people even realise it exists? :( ). Has anyone tried this particular RAID controller, or a different Adaptec SATA one? I myself use Adaptec SCSI RAID controllers (the 2100S and the 2200S), and they are both supported in the generic kernel, but then, that's SCSI... Thanks again; if this adapter isn't any good with FreeBSD amd64 I'll tell them, and will urge them to do their best to find a 9500S (in fact: I'll already make sure to tell him that the list concensus is that the 9500S is preferrable). Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 09:41:12 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BAA316A42D for ; Mon, 21 Nov 2005 09:41:12 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEAC443D53 for ; Mon, 21 Nov 2005 09:41:11 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jAL9f6tL025703 for ; Mon, 21 Nov 2005 10:41:06 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Mon, 21 Nov 2005 10:41:05 +0100 User-Agent: KMail/1.8.92 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1554117.bez677qMA6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511211041.06184.groot@kde.org> X-Spam-Score: -1.399 () BAYES_00,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: Subject: ASUS A8N-VM CSM compatibility 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, 21 Nov 2005 09:41:13 -0000 --nextPart1554117.bez677qMA6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Has anyone used the ASUS A8N-VM CSM motherboard with 6-CURRENT? Manufacture= r's=20 page is=20 http://www.asus.com/products4.aspx?l1=3D3&l2=3D15&l3=3D0&model=3D766&modelm= enu=3D1 .=20 The board is nForce 430 (presuming that's nForce4 with some goodies) and an= =20 integrated GeForce 6150 on PCIe. I take it nForce4 is no longer a problem with 6-CURRENT (back when 5 was st= ill=20 the going concern I sent back nForce4 boards whenever I got them, opting fo= r=20 Via KT800 based stuff instead); any issues to worry about with PCIe video=20 (for X, that is)? =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1554117.bez677qMA6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDgZYydqzuAf6io/4RAnOJAJ96lNONdT8o4fv2RzIOph6siaRiLACfRcY4 X0qYuVSYHcs5YJQEiowVpg0= =ZZ1I -----END PGP SIGNATURE----- --nextPart1554117.bez677qMA6-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 10:37:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A80C816A41F for ; Mon, 21 Nov 2005 10:37:08 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DEEC43D70 for ; Mon, 21 Nov 2005 10:37:07 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ee92n-0003Hm-00 for ; Mon, 21 Nov 2005 11:37:05 +0100 Message-ID: <4381A351.4010101@axis.nl> Date: Mon, 21 Nov 2005 11:37:05 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43818C1F.50203@axis.nl> In-Reply-To: <43818C1F.50203@axis.nl> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 10:37:08 -0000 Hi again, It looks like I was looking in the wrong place when I didn't spot the Adaptec 2410SA RAID controller on the supported hardware list. The controller is mentioned on this page of supported devices: http://www.freebsd.org/releases/6.0R/hardware-amd64.html#DISK Soooo, I guess there are no issues in using that one then (as that one is easier obtainable for the person in charge)... Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 11:02:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E02B16A41F for ; Mon, 21 Nov 2005 11:02:31 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2052043D5D for ; Mon, 21 Nov 2005 11:02:27 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jALB2Rkm089976 for ; Mon, 21 Nov 2005 11:02:27 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jALB2QvL089970 for freebsd-amd64@freebsd.org; Mon, 21 Nov 2005 11:02:26 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 21 Nov 2005 11:02:26 GMT Message-Id: <200511211102.jALB2QvL089970@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 11:02:31 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 fxp0: device timeout, fxp interface dies o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/18] amd64/85081 amd64 TeamSpeak o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 6.0-BETA3 lockups on AMD64 with PREEMPTIO o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/16] amd64/86199 amd64 Missed AMD64 motherboard o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing a [2005/10/14] amd64/87436 amd64 gui does not start on the ATI RS480 M2-IL o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/20] amd64/87748 amd64 can't initialize X o [2005/10/24] amd64/87898 amd64 Failt to init X: can't open device/io o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/19] amd64/89261 amd64 IPSec always causes panics on amd64 59 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 [bge] bge driver for 3Com 3C996B on amd64 o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 [bge] [patch] FreeBSD 5.4 released versio o [2005/06/12] amd64/82178 amd64 missing 32bit subsystem o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported p [2005/07/20] amd64/83806 amd64 Can not compile /usr/src/lib/msun/amd64/f o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/02] amd64/85626 amd64 java/jdk15 compile error o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins 20 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 13:41:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF8F16A41F for ; Mon, 21 Nov 2005 13:41:46 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from nmail.forbis.lt (nmail.forbis.lt [213.226.165.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC26643D45 for ; Mon, 21 Nov 2005 13:41:45 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from andrejp.forbis.lt (largo.forbis.lt [172.17.0.99]) by nmail.forbis.lt (8.13.3/8.13.3) with ESMTP id jALDfhiJ005196 for ; Mon, 21 Nov 2005 15:41:43 +0200 (EET) (envelope-from android@oberon.pfi.lt) To: freebsd-amd64@freebsd.org Date: Mon, 21 Nov 2005 15:41:42 +0200 From: Android Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/8.50 (Linux, build 1358) X-Virus-Scanned: by amavisd-new Subject: gdb konsole system crash 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, 21 Nov 2005 13:41:46 -0000 Hello all! Discovering troubles with kde-apps startup I've faced with interesting effect - starting of gdb konsole (as nonprivileged user) causes system crash. Here is an example: gdb konsole run In my case this method 100% rebooting system in 80 seconds (mysterious network wait). On konsole appears this message: -------------------- android@callisto:~> gdb konsole GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/konsole (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100082] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x50c000 (LWP 100082)] (no debugging symbols found)...(no debugging symbols found)...kbuildsycoca running... -------------------- Then after 80 seconds: [New Thread 0x50c400 (LWP 100128)] and system reboots. Maybe someone has faced with such problem on amd64 platform? Could you try to repeat this situation on other systems, or it's only my computer problem? My system: android@callisto:~> uname -a FreeBSD callisto 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Nov 19 14:31:34 EET 2005 root@callisto:/usr/obj/usr/src/sys/callisto amd64 I'm keeping up my system actual, ports are updating regullary. -- WBR Android Andrew [:] From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 14:57:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BBA216A41F for ; Mon, 21 Nov 2005 14:57:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FE9943D46 for ; Mon, 21 Nov 2005 14:57:05 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jALEuwAc020443; Mon, 21 Nov 2005 07:56:59 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4381E03A.2020509@samsco.org> Date: Mon, 21 Nov 2005 07:56:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43818C1F.50203@axis.nl> In-Reply-To: <43818C1F.50203@axis.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 14:57:08 -0000 Olaf Greve wrote: > Hi all, > > Well, the plot thickens and I have another follow-up question after all... > > I relayed the information I gathered from you all, and the person in > charge indicated that he couldn't get the 9500S-4 directly from their > normal supplier. > > They are somewhat pressed for installing the machine very soon, so he > asked me if I knew if the Adaptec 2410SA would also work well... > > The details of this adapter can be found at: > http://www.adaptec.com/worldwide/product/proddetail.html?sess=no&language=English+US&prodkey=AAR-2410SA&cat=%2fTechnology%2fSerial+ATA%2fSerial+ATA+RAID+Controllers > > > Surprise, surprise, once again FreeBSD is not mentioned on the list of > supported OSes (do people even realise it exists? :( ). > > Has anyone tried this particular RAID controller, or a different Adaptec > SATA one? > > I myself use Adaptec SCSI RAID controllers (the 2100S and the 2200S), > and they are both supported in the generic kernel, but then, that's SCSI... > > Thanks again; if this adapter isn't any good with FreeBSD amd64 I'll > tell them, and will urge them to do their best to find a 9500S (in fact: > I'll already make sure to tell him that the list concensus is that the > 9500S is preferrable). > > Cheers! > Olafo > All Adaptec RAID controllers are supported under FreeBSD. Adaptec doesn't offer formal support for FreeBSD, though, and that is why it's not mentioned on their website. Also, I'd recommend getting the 2810 instead of the 2410 if your budget allows for it. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 15:30:59 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C338416A45D for ; Mon, 21 Nov 2005 15:30:59 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FBCF43D7C for ; Mon, 21 Nov 2005 15:30:53 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jALFUn74072603; Mon, 21 Nov 2005 10:30:49 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <4381E829.9040808@wmptl.com> Date: Mon, 21 Nov 2005 10:30:49 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055639.00aa1490@pop.redshift.com> <4381D4BB.6060700@axis.nl> In-Reply-To: <4381D4BB.6060700@axis.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 15:30:59 -0000 8600 is P-ATA, (aka ATA, aka EIDE - 80pin IDE ribbon, 8 drives, one per channel (no use of master/slave). Quite well supported, but does not use S-ATA drives, and does nto perform nearly as well. To be honest though, havn't used one since like FreeBSD 3.X days myself... -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ Olaf Greve wrote: > Hi Ray and Nathan, > >> | They are somewhat pressed for installing the machine very soon, so >> he | asked me if I knew if the Adaptec 2410SA would also work well... >> >> get the nail gun ready :) > > > Hehehe, I just stepped on the emergency brake and told them your > opinions and urged them strongly to go for then 3ware one. > > The guy told me they can readily get a 3ware 8600 RAID controller. I'll > have a look-see on their page, but do you guys know off-hand whether > that one will fit the bill? > > Cheers, > Olafo > > From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 15:33:09 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5914A16A427 for ; Mon, 21 Nov 2005 15:33:09 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id D976243D45 for ; Mon, 21 Nov 2005 15:33:08 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jALFX62b072668; Mon, 21 Nov 2005 10:33:07 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <4381E8B2.8040304@wmptl.com> Date: Mon, 21 Nov 2005 10:33:06 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051121055639.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055639.00aa1490@pop.redshift.com> <3.0.1.32.20051121062432.00aa1490@pop.redshift.com> In-Reply-To: <3.0.1.32.20051121062432.00aa1490@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 15:33:09 -0000 I have purchased a 9500S-4 from http://www.newegg.com/ before too - just chirping up for them here, delivery was fast and service was good, and they do stock the 3 Ware cards. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ ray@redshift.com wrote: > Don't forget they make a low profile version -LP also, which will work without a > riser card in a 2U if I recall correctly > > Ray > > > At 03:07 PM 11/21/2005 +0100, Olaf Greve wrote: > | Hi Ray and Nathan, > | > | > | They are somewhat pressed for installing the machine very soon, so he > | > | asked me if I knew if the Adaptec 2410SA would also work well... > | > > | > get the nail gun ready :) > | > | Hehehe, I just stepped on the emergency brake and told them your > | opinions and urged them strongly to go for then 3ware one. > | > | The guy told me they can readily get a 3ware 8600 RAID controller. I'll > | have a look-see on their page, but do you guys know off-hand whether > | that one will fit the bill? > | > | Cheers, > | Olafo > | > | > > From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 16:10:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29DC016A41F for ; Mon, 21 Nov 2005 16:10:57 +0000 (GMT) (envelope-from rondzierwa@comcast.net) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF59B43D45 for ; Mon, 21 Nov 2005 16:10:56 +0000 (GMT) (envelope-from rondzierwa@comcast.net) Received: from rmailcenter03.comcast.net ([204.127.197.113]) by comcast.net (rwcrmhc11) with SMTP id <2005112116105601300bvbj0e>; Mon, 21 Nov 2005 16:10:56 +0000 Received: from [69.143.77.148] by rmailcenter03.comcast.net; Mon, 21 Nov 2005 16:10:55 +0000 From: rondzierwa@comcast.net To: freebsd-amd64@freebsd.org Date: Mon, 21 Nov 2005 16:10:55 +0000 Message-Id: <112120051610.24638.4381F18F0006E6240000603E22007456720E999D0A07960B02019D@comcast.net> X-Mailer: AT&T Message Center Version 1 (Dec 17 2004) X-Authenticated-Sender: cm9uZHppZXJ3YUBjb21jYXN0Lm5ldA== Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 16:10:57 -0000 I have an adaptec 2400S raid controller. I use it with 4 200 gig wd drives. It works fine as far as software support goes because to the software it looks like their scsi raid. The problem is that it is DREADFULLY slow. Each of the disks run between 35 and 45 MB/sec on the motherboard's ide controller. when i put them on the 2400 it won't go above 15 in any raid cofiguration. I would have expected some real performance, especially with four of these drives in a raid 0 config, but that was not the case. I still am using the setup, but for a less demanding application. The 2400S is very stable and dependable. It has been in service for over 2 years, and i haven't had any problems with it. I just don't expect much performance from it! Have you looked at he 9550's yet? They look like a significant performance increase over the already fast 9500. ron From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 17:07:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64D6216A425 for ; Mon, 21 Nov 2005 17:07:13 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7D5C43D46 for ; Mon, 21 Nov 2005 17:07:12 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jALH7BhK062407; Mon, 21 Nov 2005 18:07:11 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jALH77g0062404; Mon, 21 Nov 2005 12:07:07 -0500 (EST) (envelope-from cracauer) Date: Mon, 21 Nov 2005 12:07:07 -0500 From: Martin Cracauer To: Christopher Thomas Message-ID: <20051121120706.A62328@seagull.cons.org> References: <437BE280.5080304@srt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <437BE280.5080304@srt.com>; from nicca64@srt.com on Wed, Nov 16, 2005 at 07:53:04PM -0600 Cc: freebsd-amd64@freebsd.org Subject: Re: DFI Lanparty NF4 Ultra-D AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 17:07:13 -0000 Christopher Thomas wrote on Wed, Nov 16, 2005 at 07:53:04PM -0600: > Hello, > > first time poster, long time user. > > System: > DFI Lanparty NF4 ultra-D > AMD64 3500+ > 1GB GeIL DDR400 Dual Channel > Maxtor 12GB 5400RM > Lite-ON CDRW > > Problem: > Can install FBSD 6.0-Release/amd64 and i386 just fine, but upon first > reboot I get. > > Fatal Trap 18: integer divide fault while in kernel mode You need to post more context. I have seen this reported right after the ATA probe, with old harddrives. Since you didn't post I can only assume it's the same for you. If it's that, it seems to be related to ataraid. Try turning off all RAID options in the BIOS. Try DMA off (safe mode boot should do). Try setting the disk geometry in the BIOS manually. On bsdforums.org is another user with a similar harddrive, you might want to check that thread. For what it's worth, I run FreBSD on a DFI LP SLI-DR with no problems, several different harddrives, P-ATA and SATA. Runs great, I like the NForce chipset much better than I expected. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 21:05:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E61216A423 for ; Mon, 21 Nov 2005 21:05:25 +0000 (GMT) (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 779F543DB8 for ; Mon, 21 Nov 2005 21:04:54 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (ap6.matik.com.br [200.152.83.36] (may be forged)) by msrv.matik.com.br (8.13.3/8.13.1) with ESMTP id jALL4sat088202 for ; Mon, 21 Nov 2005 19:04:54 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Mon, 21 Nov 2005 19:04:54 -0200 User-Agent: KMail/1.8.3 References: <200511211041.06184.groot@kde.org> In-Reply-To: <200511211041.06184.groot@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511211904.54575.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: ASUS A8N-VM CSM compatibility 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, 21 Nov 2005 21:05:26 -0000 On Monday 21 November 2005 07:41, Adriaan de Groot wrote: > Has anyone used the ASUS A8N-VM CSM motherboard with 6-CURRENT? 6.0-R yes i found out all amd64 asus mboards are assigning the same base port address= to=20 adaptec controllers and certain NICs (4p-DLink Eth) what renders the mb=20 unbootable. All other components are working well. On the A8V the 5th pci=20 slots cause IRQ conflicts when using. But I do not use X on this boards so = I=20 do not know graphics capabilities. 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 Mon Nov 21 22:19:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 405D616A41F for ; Mon, 21 Nov 2005 22:19:50 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA51843D49 for ; Mon, 21 Nov 2005 22:19:49 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id AFCCBF7C7 for ; Mon, 21 Nov 2005 15:19:46 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 63965F7BB for ; Mon, 21 Nov 2005 15:19:46 -0700 (MST) Date: Mon, 21 Nov 2005 15:19:45 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051121151945.4c0f8b07.kgunders@teamcool.net> In-Reply-To: <4381E03A.2020509@samsco.org> References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43818C1F.50203@axis.nl> <4381E03A.2020509@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Hardware RAID support? Which controller best to use? 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, 21 Nov 2005 22:19:50 -0000 On Mon, 21 Nov 2005 07:56:58 -0700 Scott Long wrote: > Olaf Greve wrote: > > > Hi all, > > > > Well, the plot thickens and I have another follow-up question after all... > > > > I relayed the information I gathered from you all, and the person in > > charge indicated that he couldn't get the 9500S-4 directly from their > > normal supplier. > > > > They are somewhat pressed for installing the machine very soon, so he > > asked me if I knew if the Adaptec 2410SA would also work well... > > > > The details of this adapter can be found at: > > http://www.adaptec.com/worldwide/product/proddetail.html?sess=no&language=English+US&prodkey=AAR-2410SA&cat=%2fTechnology%2fSerial+ATA%2fSerial+ATA+RAID+Controllers > > > > > > Surprise, surprise, once again FreeBSD is not mentioned on the list of > > supported OSes (do people even realise it exists? :( ). > > > > Has anyone tried this particular RAID controller, or a different Adaptec > > SATA one? > > > > I myself use Adaptec SCSI RAID controllers (the 2100S and the 2200S), > > and they are both supported in the generic kernel, but then, that's SCSI... > > > > Thanks again; if this adapter isn't any good with FreeBSD amd64 I'll > > tell them, and will urge them to do their best to find a 9500S (in fact: > > I'll already make sure to tell him that the list concensus is that the > > 9500S is preferrable). > > > > Cheers! > > Olafo > > > > All Adaptec RAID controllers are supported under FreeBSD. Adaptec > doesn't offer formal support for FreeBSD, though, and that is why it's > not mentioned on their website. Also, I'd recommend getting the 2810 > instead of the 2410 if your budget allows for it. This is a bit off topic for this thread but related so thought I'd share. I just had to RMA an LSI card and their support was exemplary. They've got my business for life. Didn't have to deal w/any offshore call centers. Two levels into a phone tree and 30 minutes on the phone w/ the tech confirming the diagnosis and a new one was on the way FedEx Next Day. Sweet;-) -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 21 22:36:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A70F616A41F for ; Mon, 21 Nov 2005 22:36:06 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BEDD43D58 for ; Mon, 21 Nov 2005 22:36:05 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jALMa3Mu016462; Mon, 21 Nov 2005 23:36:03 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Mon, 21 Nov 2005 23:26:18 +0100 User-Agent: KMail/1.8.92 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1991754.ZI8ITg4BsH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511212326.23058.groot@kde.org> X-Spam-Score: -0.464 () BAYES_20,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: Subject: Re: gdb konsole system crash 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, 21 Nov 2005 22:36:06 -0000 --nextPart1991754.ZI8ITg4BsH Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 21 November 2005 14:41, Android wrote: > Hello all! > > Discovering troubles with kde-apps startup I've faced with interesting > effect - > starting of gdb konsole (as nonprivileged user) causes system crash. Wow, you ain't foolin'. I tried this, thinking "I have 5.4-STABLE, KDE=20 compiled by hand from sources, qt 3.3.4 from ports, no way can that go=20 wrong." And so after an hour's fscking, I'm back. It does crash, and quite= =20 impressively. No serial console or other niftiness to help bt though. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1991754.ZI8ITg4BsH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDgkmPdqzuAf6io/4RAmmGAKCT5EJ6zeZgnLbIK4vbgRMZb41bZQCgglmx HPjEeJUYJdLbKfZYiwijbpQ= =hya+ -----END PGP SIGNATURE----- --nextPart1991754.ZI8ITg4BsH-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 00:23:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EEE616A41F; Tue, 22 Nov 2005 00:23:48 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0432543D49; Tue, 22 Nov 2005 00:23:48 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQB00M1YYFMU8I0@vms040.mailsrvcs.net>; Mon, 21 Nov 2005 18:23:47 -0600 (CST) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.4/8.13.1) with ESMTP id jAM0Nf50068635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2005 19:23:45 -0500 Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.4/8.13.4) with ESMTP id jAM0NZOi098709; Mon, 21 Nov 2005 19:23:35 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.4/8.13.4/Submit) id jAM0NW3V098708; Mon, 21 Nov 2005 19:23:32 -0500 Date: Mon, 21 Nov 2005 19:23:32 -0500 From: Mikhail Teterin To: current@freebsd.org Message-id: <200511211923.32834.mi+mx@aldan.algebra.com> Organization: Virtual Estates, Inc. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline X-Virus-Scanned: ClamAV devel-20050525/1181/Mon Nov 21 06:10:32 2005 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Authentication-warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f User-Agent: KMail/1.8.2 Cc: amd64@freebsd.org Subject: recent 7-current broke the devel/tcltls port 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, 22 Nov 2005 00:23:48 -0000 Hello! According the pointyhat's build logs, the port started to fail its self-tests recently -- with a SIGBUS :-( Could someone running 7-current on amd64, please, investigate? I don't have such a system. Thanks! -mi From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 09:07:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2970416A420 for ; Tue, 22 Nov 2005 09:07:19 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1BF743D49 for ; Tue, 22 Nov 2005 09:07:18 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1EeU74-0004IA-00 for ; Tue, 22 Nov 2005 10:06:54 +0100 Message-ID: <4382DFAD.5040603@axis.nl> Date: Tue, 22 Nov 2005 10:06:53 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Subject: FreeBSD 6.0-release AMD64 stability/reliability? 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, 22 Nov 2005 09:07:19 -0000 Hi, Well, the people who are going to order the hardware for the DB server I have been asking some question about have almost made their minds up. It seems indeed they'll go for an SATA 3ware RAID controller... Depending on availability and price locally over here they'll probably choose something from the 8000 or 9000 series. We'll see... Meanwhile: indeed I will be the one who will be installing the OS, and I'm looking at FreeBSD 6.0-release AMD64. Can anyone tell me whether that already is a smart choice for a live DB server (in terms of matureness, stability, reliability, etc.), or whether it would be wiser to stick to FreeBSD 5.4-release AMD64 for this? Also: in case at a later point in time I want to upgrade the complete OS to a more recent version (once they're available), will it be easy to go through the 'buildworld' process? From what I gather this shouldn't be too much of an issue, it's just that I've never done it before... Tnx in advance for any answers, and cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 10:44:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9635E16A41F for ; Tue, 22 Nov 2005 10:44:02 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C7C43D5A for ; Tue, 22 Nov 2005 10:43:59 +0000 (GMT) (envelope-from valerio.daelli@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so973503wxc for ; Tue, 22 Nov 2005 02:43:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=qF29nWAWmlvbfJk0TaXSG7VgyoIES2c+qs1Pvz/bmwak3Z514usPy4p8UlKQpqnPFRuN7xvsMYNieyIbn5NE3YaUrh/VwAdYi6m2BGK9PZ9xQYPWArG4w9Lq5y7QsfHTAUXTU8o/HXzOna3bLOWGBe9xEV9ipX9QBu4uGxUZxUE= Received: by 10.70.23.5 with SMTP id 5mr2585766wxw; Tue, 22 Nov 2005 02:43:58 -0800 (PST) Received: by 10.70.32.20 with HTTP; Tue, 22 Nov 2005 02:43:58 -0800 (PST) Message-ID: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> Date: Tue, 22 Nov 2005 11:43:58 +0100 From: Valerio daelli To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with samba on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 10:44:02 -0000 Hello everybody we have a Sun Fire V20Z with dual Opteron. We use FreeBSD 5.4. We tried both the single processor and the SMP kernel. We experience very high load with samba 3.0.20b and 3.0.14a. This the top of our top command: last pid: 2317; load averages: 1.02, 0.98, 0.65 up 0+00:39:35 11:43:01 127 processes: 2 running, 125 sleeping CPU states: 21.5% user, 0.0% nice, 78.1% system, 0.4% interrupt, 0.0% idle Mem: 91M Active, 383M Inact, 214M Wired, 36K Cache, 214M Buf, 3166M Free Swap: 8192M Total, 8192M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 714 root 122 0 18688K 5700K RUN 13:41 94.24% 94.24% smbd Does anyone have any idea about? Thanks Valerio From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 11:08:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D714B16A41F for ; Tue, 22 Nov 2005 11:08:31 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id E31EF43D95 for ; Tue, 22 Nov 2005 11:08:07 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by xproxy.gmail.com with SMTP id i31so772903wxd for ; Tue, 22 Nov 2005 03:08:07 -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=hGdnKJ5MTlGxCOnaSYsEsaH43G/b+/i76BnxzN/GXeOVWszJM2Ty8O/agmWlS2whhGuVzfoxvPY7NY9N0YjSFlycNP2byN3992eWfsk4lCX5Yp3TXxtfn3KUa9yTI4uO5ktuvSB7jAYgBlaPzHyseLHatG7hn7iYJs3SRadujRU= Received: by 10.65.38.4 with SMTP id q4mr4248019qbj; Tue, 22 Nov 2005 03:08:06 -0800 (PST) Received: by 10.65.192.16 with HTTP; Tue, 22 Nov 2005 03:08:06 -0800 (PST) Message-ID: Date: Tue, 22 Nov 2005 12:08:06 +0100 From: Claus Guttesen To: Valerio daelli In-Reply-To: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: Problem with samba on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 11:08:32 -0000 > we have a Sun Fire V20Z with dual Opteron. > We use FreeBSD 5.4. We tried both the single processor and the SMP kernel= . > We experience very high load with samba 3.0.20b > and 3.0.14a. This the top of our top command: I had (unrelated) problems with samba ver. 3, some files disappeared in the windows explorer, but were present on the samba-server, client-connections stalled. So I downgraded to ver. 2 which works for me. This is on FreeBSD 5.4 release on the amd64-port. So if there aren't fetatures in ver. 3 you need you could try ver. 2 instead. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 12:11:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B221816A41F for ; Tue, 22 Nov 2005 12:11:34 +0000 (GMT) (envelope-from arved@arved.at) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id E674543D6D for ; Tue, 22 Nov 2005 12:11:29 +0000 (GMT) (envelope-from arved@arved.at) Received: from [192.168.3.25] (minimac.arved.de [192.168.3.25]) by 21322530218.direct.eti.at (8.13.4/8.13.4) with ESMTP id jAMCBRCj071596 for ; Tue, 22 Nov 2005 13:11:27 +0100 (CET) (envelope-from arved@arved.at) Mime-Version: 1.0 (Apple Message framework v623) In-Reply-To: <200511212326.23058.groot@kde.org> References: <200511212326.23058.groot@kde.org> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6ee51eee3c204ce1abcfeaf7401677cb@arved.at> Content-Transfer-Encoding: 7bit From: Tilman Linneweh Date: Tue, 22 Nov 2005 13:06:19 +0100 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.623) Subject: Re: gdb konsole system crash 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, 22 Nov 2005 12:11:34 -0000 On Nov 21, 2005, at 23:26, Adriaan de Groot wrote: >> Discovering troubles with kde-apps startup I've faced with interesting >> effect - >> starting of gdb konsole (as nonprivileged user) causes system crash. > > Wow, you ain't foolin'. I tried this, thinking "I have 5.4-STABLE, KDE > compiled by hand from sources, qt 3.3.4 from ports, no way can that go > wrong." And so after an hour's fscking, I'm back. It does crash, and > quite > impressively. No serial console or other niftiness to help bt though. me too, on CURRENT. On the console i only get "kernel trap 9 with interrupts disabled", it does not break into DDB, just hangs. This is CURRENT from yesterday, testes with and without WITNESS/INVARIANTS. Any ideas how i can get more information? regards tilman From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 12:45:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D11A16A41F for ; Tue, 22 Nov 2005 12:45:22 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from nmail.forbis.lt (nmail.forbis.lt [213.226.165.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44C3E43D99 for ; Tue, 22 Nov 2005 12:45:03 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from andrejp.forbis.lt (largo.forbis.lt [172.17.0.99]) by nmail.forbis.lt (8.13.3/8.13.3) with ESMTP id jAMCis4H041446; Tue, 22 Nov 2005 14:44:55 +0200 (EET) (envelope-from android@oberon.pfi.lt) Date: Tue, 22 Nov 2005 14:44:53 +0200 To: "Tilman Linneweh" , freebsd-amd64@freebsd.org References: <200511212326.23058.groot@kde.org> <6ee51eee3c204ce1abcfeaf7401677cb@arved.at> From: Android Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <6ee51eee3c204ce1abcfeaf7401677cb@arved.at> User-Agent: Opera M2/8.50 (Linux, build 1358) X-Virus-Scanned: by amavisd-new Cc: Subject: Re: gdb konsole system crash 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, 22 Nov 2005 12:45:22 -0000 Adriaan, Tilman, thank you a lot for a risky test! Now I know I'm not alone. I've checked it with SMP kernel, with and without hyperthreading - result is the same. What's next to do? I can't think out anything bettert than gdb gdb konsole... (joking) On Tue, 22 Nov 2005 14:06:19 +0200, Tilman Linneweh wrote: > > On Nov 21, 2005, at 23:26, Adriaan de Groot wrote: >>> Discovering troubles with kde-apps startup I've faced with interesting >>> effect - >>> starting of gdb konsole (as nonprivileged user) causes system crash. >> >> Wow, you ain't foolin'. I tried this, thinking "I have 5.4-STABLE, KDE >> compiled by hand from sources, qt 3.3.4 from ports, no way can that go >> wrong." And so after an hour's fscking, I'm back. It does crash, and >> quite >> impressively. No serial console or other niftiness to help bt though. > > me too, on CURRENT. > > On the console i only get "kernel trap 9 with interrupts disabled", it > does not > break into DDB, just hangs. > > This is CURRENT from yesterday, testes with and without > WITNESS/INVARIANTS. > > Any ideas how i can get more information? > > regards > tilman > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > -- WBR Android Andrew [:] From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 13:11:03 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B589916A455; Tue, 22 Nov 2005 13:11:03 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CECD43D86; Tue, 22 Nov 2005 13:10:58 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jAMDAmkn001575; Tue, 22 Nov 2005 15:10:48 +0200 Received: by flame.pc (Postfix, from userid 1001) id E63B5117A2; Tue, 22 Nov 2005 15:10:24 +0200 (EET) Date: Tue, 22 Nov 2005 15:10:24 +0200 From: Giorgos Keramidas To: Mikhail Teterin Message-ID: <20051122131024.GA10161@flame.pc> References: <200511211923.32834.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511211923.32834.mi+mx@aldan.algebra.com> Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port 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, 22 Nov 2005 13:11:03 -0000 On 2005-11-21 19:23, Mikhail Teterin wrote: > Hello! > > According the pointyhat's build logs, the port started to fail its self-tests > recently -- with a SIGBUS :-( > > Could someone running 7-current on amd64, please, investigate? I don't have > such a system. Thanks! Hmm, I just built tcltls here on amd64: * dmesg output % CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class CPU) % Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 % Features=0x78bfbff % AMD Features=0xe2500800 * tcltls build log, final lines % [...] % Tests running in interp: /usr/local/bin/tclsh8.4 % Tests running in working dir: /home/ports/devel/tcltls/work/tls1.5/tests % Only running tests that match: * % Skipping test files that match: l.*.test % Only sourcing test files that match: *.test % Tests began at Tue Nov 22 14:59:07 EET 2005 % tlsIO.test % % Tests ended at Tue Nov 22 14:59:25 EET 2005 % all.tcl: Total 59 Passed 42 Skipped 17 Failed 0 % Sourced 0 Test Files. % Number of tests skipped for each constraint: % 12 doTestsWithRemoteServer % 2 notRoot % 1 testthread % 2 unexplainedFailure % flame# Does this seem ok to you? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 13:15:10 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FD1416A41F for ; Tue, 22 Nov 2005 13:15:10 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D47C43D73 for ; Tue, 22 Nov 2005 13:15:09 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAMDF8jc004234; Tue, 22 Nov 2005 08:15:08 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <438319DB.4070100@wmptl.com> Date: Tue, 22 Nov 2005 08:15:07 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Valerio daelli References: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> In-Reply-To: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Problem with samba on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 13:15:10 -0000 ran into MANY similar issues, turned out to be a combination of the local ldap libraries and bad (cheap) ethernet switches... Seriously ought to consider joining the samba mailing list though, those guys were all great in helping out with our problem. There are numerous issues between domain control and especially so with Microsoft Office products... but the scope of which can be a bit off-topic on the freebsd lists, especially so when the bulk of the commiters/developers working on samba actively participate in its support via their email list. samba@lists.samba.org - Just my two cents, without more details I can't really point you one way or the other, but joining that list should be your first step. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ Valerio daelli wrote: > Hello everybody > we have a Sun Fire V20Z with dual Opteron. > We use FreeBSD 5.4. We tried both the single processor and the SMP kernel. > We experience very high load with samba 3.0.20b > and 3.0.14a. This the top of our top command: > > last pid: 2317; load averages: 1.02, 0.98, 0.65 up 0+00:39:35 11:43:01 > 127 processes: 2 running, 125 sleeping > CPU states: 21.5% user, 0.0% nice, 78.1% system, 0.4% interrupt, 0.0% idle > Mem: 91M Active, 383M Inact, 214M Wired, 36K Cache, 214M Buf, 3166M Free > Swap: 8192M Total, 8192M Free > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 714 root 122 0 18688K 5700K RUN 13:41 94.24% 94.24% smbd > > Does anyone have any idea about? > Thanks > > Valerio > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 14:52:12 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4459D16A420; Tue, 22 Nov 2005 14:52:12 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD01E43D6A; Tue, 22 Nov 2005 14:51:51 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQD00KNR2MC8M31@vms046.mailsrvcs.net>; Tue, 22 Nov 2005 08:51:49 -0600 (CST) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.4/8.13.1) with ESMTP id jAMEpiJX092064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 09:51:47 -0500 Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.4/8.13.4) with ESMTP id jAMEpcKE002288; Tue, 22 Nov 2005 09:51:38 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.4/8.13.4/Submit) id jAMEpS0M002287; Tue, 22 Nov 2005 09:51:28 -0500 Date: Tue, 22 Nov 2005 09:51:28 -0500 From: Mikhail Teterin In-reply-to: <20051122131024.GA10161@flame.pc> To: Giorgos Keramidas Message-id: <200511220951.28429.mi+mx@aldan.algebra.com> Organization: Virtual Estates, Inc. MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline X-Virus-Scanned: ClamAV devel-20050525/1182/Mon Nov 21 14:43:47 2005 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> X-Authentication-warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f User-Agent: KMail/1.8.2 Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port 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, 22 Nov 2005 14:52:12 -0000 > > According the pointyhat's build logs, the port started to fail its > > self-tests recently -- with a SIGBUS :-( > > > > Could someone running 7-current on amd64, please, investigate? I don't > > have such a system. Thanks! > > Hmm, I just built tcltls here on amd64: Thank you, Giorgos and Tilman, for taking the time to test this. Seems like it builds find for you on a fresh 7-current. Kris, can there be something "funny" about the cluster's amd64-machine? -mi > * dmesg output > > % CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class CPU) > % Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 > % > Features=0x78bfbff,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> % AMD > Features=0xe2500800 > > * tcltls build log, final lines > > % [...] > % Tests running in interp: /usr/local/bin/tclsh8.4 > % Tests running in working dir: /home/ports/devel/tcltls/work/tls1.5/tests > % Only running tests that match: * > % Skipping test files that match: l.*.test > % Only sourcing test files that match: *.test > % Tests began at Tue Nov 22 14:59:07 EET 2005 > % tlsIO.test > % > % Tests ended at Tue Nov 22 14:59:25 EET 2005 > % all.tcl: Total 59 Passed 42 Skipped 17 Failed 0 > % Sourced 0 Test Files. > % Number of tests skipped for each constraint: > % 12 doTestsWithRemoteServer > % 2 notRoot > % 1 testthread > % 2 unexplainedFailure > % flame# > > Does this seem ok to you? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 18:20:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB5516A424 for ; Tue, 22 Nov 2005 18:20:55 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5921B43D7C for ; Tue, 22 Nov 2005 18:20:45 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id BB921F7C7 for ; Tue, 22 Nov 2005 11:20:37 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 85746F7BB for ; Tue, 22 Nov 2005 11:20:37 -0700 (MST) Date: Tue, 22 Nov 2005 11:20:36 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051122112036.64cb7d63.kgunders@teamcool.net> In-Reply-To: <4382DFAD.5040603@axis.nl> References: <4382DFAD.5040603@axis.nl> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: FreeBSD 6.0-release AMD64 stability/reliability? 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, 22 Nov 2005 18:20:56 -0000 On Tue, 22 Nov 2005 10:06:53 +0100 Olaf Greve wrote: > Hi, > > Well, the people who are going to order the hardware for the DB server I > have been asking some question about have almost made their minds up. It > seems indeed they'll go for an SATA 3ware RAID controller... Depending > on availability and price locally over here they'll probably choose > something from the 8000 or 9000 series. We'll see... > > Meanwhile: indeed I will be the one who will be installing the OS, and > I'm looking at FreeBSD 6.0-release AMD64. > > Can anyone tell me whether that already is a smart choice for a live DB > server (in terms of matureness, stability, reliability, etc.), or > whether it would be wiser to stick to FreeBSD 5.4-release AMD64 for this? > > Also: in case at a later point in time I want to upgrade the complete OS > to a more recent version (once they're available), will it be easy to go > through the 'buildworld' process? From what I gather this shouldn't be > too much of an issue, it's just that I've never done it before... > > Tnx in advance for any answers, and cheers! > Olafo Olafo: fwiw-- I've been using FreeBSD since 2.x days. During that time I've run into a few minor glitches upgrading. But that is so infrequent that I couldn't even really recount them. Usually a fresh cvsup and a couple 'make cleandir' did the trick. Of course you had to reinstall from scratch to upgrade from UFS1 based system to UFS2, but other than that I can't recall a forced reinstall on a production box. Maintainability and upgradability are one the the hallmark features that make FreeBSD rock! >From my recollection there were a few issues w/early 3.x releases. 4.x were pretty solid from the get go. Of course 5.x was very ambitious and reaching stable status took a bit of doing, during which time 4.x was actively maintained and many 5.x improvements back ported. The path to 5.x stable was atypical and I think the FBSD developers took the opportunity to learn from the experience. FreeBSD's kernel and userland are an integrated and cohesive package rather than separate entities. Overall upgrades are pretty smooth. FreeBSD may run into a glitch or two here and there between major releases but nothing like the horror stories you may have heard about with some other *nix like operating sytems. The point being here that I think FreeBSD has done a damn good job of living up to it's motto. First and foremost FreeBSD provides and excellent server platform. Presently I've got my production machines on 5.4. I'm doing new builds on 6.0. They haven't been actually deployed into production yet due to time constraints of 3rd parties. I've not done any formal benchmarking but my informal assessment is that they "feel" a bit "snappier" than 5.4 on comparable hardware. Release engineering did an excellent job w/the 6.0 release. I suspect Scott's testing proceedures contributed significantly in this regard. Hence, I'm feeling pretty optimistic about 6.0 in production. I've only upgraded one test machine from 5.4 to 6.0. Don't recall encountering any growing pains. Be sure to check /usr/src/UPDATING. I suggest you get yourself a low cost test box that you can use for testing. Clone your production machine config to the extent you are able, but any old workstation will do in a pinch. Then before you upgrade/update anything on the production machine, test on the practice machine first. You may run into undocumented incompatabilites during ports upgrades but once again, these are pretty infrequent. Be sure to keep an eye on /usr/ports/ UPDATING as well. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 20:10:19 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1B7616A420; Tue, 22 Nov 2005 20:10:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B42543D8F; Tue, 22 Nov 2005 20:10:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8FAD51A3C1C; Tue, 22 Nov 2005 12:09:56 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6733351590; Tue, 22 Nov 2005 15:09:55 -0500 (EST) Date: Tue, 22 Nov 2005 15:09:55 -0500 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20051122200953.GB70767@xor.obsecurity.org> References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> <200511220951.28429.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ADZbWkCsHQ7r3kzd" Content-Disposition: inline In-Reply-To: <200511220951.28429.mi+mx@aldan.algebra.com> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Giorgos Keramidas , current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port 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, 22 Nov 2005 20:10:19 -0000 --ADZbWkCsHQ7r3kzd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 09:51:28AM -0500, Mikhail Teterin wrote: > > > According the pointyhat's build logs, the port started to fail its > > > self-tests recently -- with a SIGBUS :-( > > > > > > Could someone running 7-current on amd64, please, investigate? I don't > > > have such a system. Thanks! > > > > Hmm, I just built tcltls here on amd64: >=20 > Thank you, Giorgos and Tilman, for taking the time to test this. Seems li= ke it=20 > builds find for you on a fresh 7-current. >=20 > Kris, can there be something "funny" about the cluster's amd64-machine? Perhaps it's not up-to-date enough. Kris --ADZbWkCsHQ7r3kzd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDg3sQWry0BWjoQKURAg24AKCwQfh7u5FjFPdUOtr6443cIfUfvwCfZ8X4 hWBy6ZugNlkioAUqzSWqbNk= =pChd -----END PGP SIGNATURE----- --ADZbWkCsHQ7r3kzd-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 22 21:49:30 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA05716A41F; Tue, 22 Nov 2005 21:49:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3DD43D68; Tue, 22 Nov 2005 21:49:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4199A1A3C24; Tue, 22 Nov 2005 13:49:30 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 792C251585; Tue, 22 Nov 2005 16:49:29 -0500 (EST) Date: Tue, 22 Nov 2005 16:49:29 -0500 From: Kris Kennaway To: Giorgos Keramidas Message-ID: <20051122214929.GA73316@xor.obsecurity.org> References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <20051122131024.GA10161@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Mikhail Teterin , current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port 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, 22 Nov 2005 21:49:31 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 03:10:24PM +0200, Giorgos Keramidas wrote: > On 2005-11-21 19:23, Mikhail Teterin wrote: > > Hello! > > > > According the pointyhat's build logs, the port started to fail its self= -tests > > recently -- with a SIGBUS :-( > > > > Could someone running 7-current on amd64, please, investigate? I don't = have > > such a system. Thanks! >=20 > Hmm, I just built tcltls here on amd64: Make sure your system is completely up-to-date; this problem is very recent. Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDg5JpWry0BWjoQKURArdfAJ9oiBBT3qHRB7rUMzXOcJwHoRV8vgCg3ZcN ItJUsxXx5Xou4hOTSlTGzbo= =igy/ -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 12:31:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9756016A41F for ; Wed, 23 Nov 2005 12:31:53 +0000 (GMT) (envelope-from buebo@buebo.de) Received: from natnoddy.rzone.de (natnoddy.rzone.de [81.169.145.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2467543D6B for ; Wed, 23 Nov 2005 12:31:51 +0000 (GMT) (envelope-from buebo@buebo.de) Received: from localhost.localdomain (reverse-82-141-49-183.dialin.kamp-dsl.de [82.141.49.183]) by post.webmailer.de (8.13.1/8.13.1) with SMTP id jANCVllZ004314 for ; Wed, 23 Nov 2005 13:31:49 +0100 (MET) Date: Wed, 23 Nov 2005 13:32:04 +0100 From: "Felix 'buebo' Kakrow" To: freebsd-amd64@freebsd.org Message-Id: <20051123133204.99c71bba.buebo@buebo.de> In-Reply-To: References: <27dbfc8c0511220243k357aabaar96516b63203b057f@mail.gmail.com> X-Mailer: Sylpheed version 2.1.1 (GTK+ 2.8.6; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__23_Nov_2005_13_32_04_+0100_mUcdYqdygc6_lRrx" Subject: Re: Problem with samba on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 12:31:53 -0000 --Signature=_Wed__23_Nov_2005_13_32_04_+0100_mUcdYqdygc6_lRrx Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Tue, 22 Nov 2005 12:08:06 +0100 Claus Guttesen wrote: > I had (unrelated) problems with samba ver. 3, some files disappeared > in the windows explorer, but were present on the samba-server, > client-connections stalled. So I downgraded to ver. 2 which works for > me. >=20 > This is on FreeBSD 5.4 release on the amd64-port. So if there aren't > fetatures in ver. 3 you need you could try ver. 2 instead. Just throwing in my 2c worth of wisdom, but afaik samba 2.* has known security problems, so I would not consider this a wise choice. Cheers Felix --Signature=_Wed__23_Nov_2005_13_32_04_+0100_mUcdYqdygc6_lRrx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Enrcypt your mail with GnuPG! iD8DBQFDhGFIh3KJlP+0/PsRAsYHAJ9RBccrkqR+7w4/72Ync1K/83XLAQCgtVLB f6NcvgVbCKEZlu8cIhfr4yI= =NgAY -----END PGP SIGNATURE----- --Signature=_Wed__23_Nov_2005_13_32_04_+0100_mUcdYqdygc6_lRrx-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 16:35:07 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D36916A422 for ; Wed, 23 Nov 2005 16:35:07 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AF3A43D79 for ; Wed, 23 Nov 2005 16:34:44 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.4/8.13.4) with ESMTP id jANGYZAf000421 for ; Wed, 23 Nov 2005 17:34:35 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Wed, 23 Nov 2005 17:34:35 +0100 From: Palle Girgensohn To: amd64@freebsd.org Message-ID: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: 6.0 boot CD does not boot? 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, 23 Nov 2005 16:35:07 -0000 Hi! I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does not boot, it just skips the CD, tried burning a couple of them, none works. i386 image works fine. Any ideas? /Palle From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 16:45:30 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C07716A41F for ; Wed, 23 Nov 2005 16:45:30 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14B8B43D91 for ; Wed, 23 Nov 2005 16:45:07 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr4.xs4all.nl (8.13.3/8.13.3) with ESMTP id jANGj3bo048965; Wed, 23 Nov 2005 17:45:03 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 09FD9B824; Wed, 23 Nov 2005 17:45:03 +0100 (CET) Date: Wed, 23 Nov 2005 17:45:03 +0100 From: Roland Smith To: Palle Girgensohn Message-ID: <20051123164503.GA1416@slackbox.xs4all.nl> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 23 Nov 2005 16:45:30 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 05:34:35PM +0100, Palle Girgensohn wrote: > Hi! >=20 > I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does n= ot=20 > boot, it just skips the CD, tried burning a couple of them, none works.= =20 > i386 image works fine. Any ideas? Did you check the integrity of the iso images by comparing the md5 and sha256 checksums of the downloaded image to the ones mentioned on the ftp site? MD5 (6.0-RELEASE-amd64-bootonly.iso) =3D 4328c66c900ef6e6ddc1daf9dd8b731f MD5 (6.0-RELEASE-amd64-disc1.iso) =3D a4e427adaa2bfef868e2bc62d57fbf8d MD5 (6.0-RELEASE-amd64-disc2.iso) =3D 2f46d344681c1a82b146b3ed1df68e61 SHA256 (6.0-RELEASE-amd64-bootonly.iso) =3D afa6eb02845185d1968cce02e752614= 394f8b9c09fc519ae1b61356c583d6df0 SHA256 (6.0-RELEASE-amd64-disc1.iso) =3D 449b08c98acc73508219e2a19de0787334= fd9237123346b2c7949c3009540170 SHA256 (6.0-RELEASE-amd64-disc2.iso) =3D 25c3e3da1f2e0a0ecb8a23dd78f35f969c= c17eba6072db6a41edab3ecfc2e2d4 Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhJyPEnfvsMMhpyURAsCbAJ0aHxJQi5YYmzKwDqXpgasnMCrsrACePfvV iRiN9Kttq4Sib3OsrOSrA28= =dfR4 -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 17:32:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 110AC16A41F for ; Wed, 23 Nov 2005 17:32:48 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5495E43D46 for ; Wed, 23 Nov 2005 17:32:45 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.4/8.13.4) with ESMTP id jANHWh3v000623; Wed, 23 Nov 2005 18:32:43 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Wed, 23 Nov 2005 18:32:43 +0100 From: Palle Girgensohn To: Roland Smith Message-ID: <9B8DDB5A5F7E3CBB19F014C4@rambutan.pingpong.net> In-Reply-To: <20051123164503.GA1416@slackbox.xs4all.nl> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <20051123164503.GA1416@slackbox.xs4all.nl> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 23 Nov 2005 17:32:48 -0000 --On onsdag, november 23, 2005 17.45.03 +0100 Roland Smith wrote: > On Wed, Nov 23, 2005 at 05:34:35PM +0100, Palle Girgensohn wrote: >> Hi! >> >> I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does >> not boot, it just skips the CD, tried burning a couple of them, none >> works. i386 image works fine. Any ideas? > > Did you check the integrity of the iso images by comparing the md5 and > sha256 checksums of the downloaded image to the ones mentioned on the > ftp site? > > MD5 (6.0-RELEASE-amd64-bootonly.iso) = 4328c66c900ef6e6ddc1daf9dd8b731f > MD5 (6.0-RELEASE-amd64-disc1.iso) = a4e427adaa2bfef868e2bc62d57fbf8d > MD5 (6.0-RELEASE-amd64-disc2.iso) = 2f46d344681c1a82b146b3ed1df68e61 > > > SHA256 (6.0-RELEASE-amd64-bootonly.iso) = > afa6eb02845185d1968cce02e752614394f8b9c09fc519ae1b61356c583d6df0 SHA256 > (6.0-RELEASE-amd64-disc1.iso) = > 449b08c98acc73508219e2a19de0787334fd9237123346b2c7949c3009540170 SHA256 > (6.0-RELEASE-amd64-disc2.iso) = > 25c3e3da1f2e0a0ecb8a23dd78f35f969cc17eba6072db6a41edab3ecfc2e2d4 Yes, the integrity is intact. I am supposed to boot from disc1 as always, right? /Palle From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 17:53:18 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 018F616A41F for ; Wed, 23 Nov 2005 17:53:18 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA7D543D46 for ; Wed, 23 Nov 2005 17:53:17 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id DACADB85A for ; Wed, 23 Nov 2005 12:53:16 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <9B8DDB5A5F7E3CBB19F014C4@rambutan.pingpong.net> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <20051123164503.GA1416@slackbox.xs4all.nl> <9B8DDB5A5F7E3CBB19F014C4@rambutan.pingpong.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 23 Nov 2005 12:53:14 -0500 To: amd64@freebsd.org X-Mailer: Apple Mail (2.746.2) Cc: Subject: Re: 6.0 boot CD does not boot? 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, 23 Nov 2005 17:53:18 -0000 On Nov 23, 2005, at 12:32 PM, Palle Girgensohn wrote: > Yes, the integrity is intact. I am supposed to boot from disc1 as > always, right? works for me[tm]. the boot parts are actually still done in 32 bit mode so that part should be identical. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 18:01:29 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 635C416A423 for ; Wed, 23 Nov 2005 18:01:29 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC21043D58 for ; Wed, 23 Nov 2005 18:01:17 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 7E3E4B85A; Wed, 23 Nov 2005 13:01:11 -0500 (EST) In-Reply-To: <437D0FF6.20009@deadcafe.de> References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 23 Nov 2005 13:01:10 -0500 To: Nathan Vidican X-Mailer: Apple Mail (2.746.2) Cc: amd64@freebsd.org Subject: Re: Sun x2100 Server Compatability 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, 23 Nov 2005 18:01:29 -0000 On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: > Nathan Vidican schrieb: >> Any known issues running FreeBSD/amd64 on a Sun x2100 server? >> Single opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: > > The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without > PS/2 mouse and keyboard ports. So you should look at success > reports for this board. Any more info you found out about this? I'm about to order one of these to test unless I find out otherwise it doesn't work. My only concern is that one of the ethernets is bge and the other is nve which is not known to be that stable, and I need both ports... I suspect it will be ok, though. If push comes to shove I guess installing an intel NIC card would not be out of the question. The rest of the hardware seems to be supported based on chipsets I looked up from kernel boot messages from linux, openbsd, and netbsd posted on the web. curiously i never found a boot message from anyone running freebsd... From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 18:07:51 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6BF316A41F for ; Wed, 23 Nov 2005 18:07:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9D7F43D94 for ; Wed, 23 Nov 2005 18:07:33 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jANI7VJ8037616; Wed, 23 Nov 2005 11:07:31 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4384AFE3.9090106@samsco.org> Date: Wed, 23 Nov 2005 11:07:31 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Palle Girgensohn References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> In-Reply-To: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 23 Nov 2005 18:07:52 -0000 Palle Girgensohn wrote: > Hi! > > I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does > not boot, it just skips the CD, tried burning a couple of them, none > works. i386 image works fine. Any ideas? > > /Palle > Does the bootonly CD boot? Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 18:21:44 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4091616A41F for ; Wed, 23 Nov 2005 18:21:44 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F18543D55 for ; Wed, 23 Nov 2005 18:21:19 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id jANIKpvh054661; Wed, 23 Nov 2005 19:20:55 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 489FAB824; Wed, 23 Nov 2005 19:20:49 +0100 (CET) Date: Wed, 23 Nov 2005 19:20:49 +0100 From: Roland Smith To: Palle Girgensohn Message-ID: <20051123182049.GA3947@slackbox.xs4all.nl> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <20051123164503.GA1416@slackbox.xs4all.nl> <9B8DDB5A5F7E3CBB19F014C4@rambutan.pingpong.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <9B8DDB5A5F7E3CBB19F014C4@rambutan.pingpong.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 23 Nov 2005 18:21:44 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 06:32:43PM +0100, Palle Girgensohn wrote: >=20 >=20 > wrote: >=20 > >On Wed, Nov 23, 2005 at 05:34:35PM +0100, Palle Girgensohn wrote: > >>Hi! > >> > >>I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does > >>not boot, it just skips the CD, tried burning a couple of them, none > >>works. i386 image works fine. Any ideas? > > > >Did you check the integrity of the iso images by comparing the md5 and > >sha256 checksums of the downloaded image to the ones mentioned on the > >ftp site? > > > Yes, the integrity is intact. I am supposed to boot from disc1 as always,= =20 > right? Yes. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhLMBEnfvsMMhpyURAs6NAKCMKvxue2XUwBi2j3Kvbty57xAlMgCffK3f jwTg9YZ4QJT+EefcJ06nYWc= =hu+v -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 18:58:09 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD80516A41F for ; Wed, 23 Nov 2005 18:58:09 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 212FA43D60 for ; Wed, 23 Nov 2005 18:58:08 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jANIw7il053261; Wed, 23 Nov 2005 13:58:07 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <4384BBBF.4030007@wmptl.com> Date: Wed, 23 Nov 2005 13:58:07 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vivek Khera References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> In-Reply-To: <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Sun x2100 Server Compatability 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, 23 Nov 2005 18:58:09 -0000 Vivek Khera wrote: > > On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: > >> Nathan Vidican schrieb: >> >>> Any known issues running FreeBSD/amd64 on a Sun x2100 server? Single >>> opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: >> >> >> The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without >> PS/2 mouse and keyboard ports. So you should look at success reports >> for this board. > > > Any more info you found out about this? I'm about to order one of > these to test unless I find out otherwise it doesn't work. > > My only concern is that one of the ethernets is bge and the other is > nve which is not known to be that stable, and I need both ports... I > suspect it will be ok, though. If push comes to shove I guess > installing an intel NIC card would not be out of the question. > > The rest of the hardware seems to be supported based on chipsets I > looked up from kernel boot messages from linux, openbsd, and netbsd > posted on the web. curiously i never found a boot message from anyone > running freebsd... > > > Same issue here... both NIC's requried, but putting in a good ole Intel/FXP card won't bother me in the least. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 20:06:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86E5316A421 for ; Wed, 23 Nov 2005 20:06:59 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC44A43D98 for ; Wed, 23 Nov 2005 20:06:56 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id F1DE8F7C7 for ; Wed, 23 Nov 2005 13:06:52 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id BB7DCF7BB for ; Wed, 23 Nov 2005 13:06:52 -0700 (MST) Date: Wed, 23 Nov 2005 13:06:51 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051123130651.304604b0.kgunders@teamcool.net> In-Reply-To: <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Sun x2100 Server Compatability 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, 23 Nov 2005 20:06:59 -0000 On Wed, 23 Nov 2005 13:01:10 -0500 Vivek Khera wrote: > > On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: > > > Nathan Vidican schrieb: > >> Any known issues running FreeBSD/amd64 on a Sun x2100 server? > >> Single opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: > > > > The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without > > PS/2 mouse and keyboard ports. So you should look at success > > reports for this board. > > Any more info you found out about this? I'm about to order one of > these to test unless I find out otherwise it doesn't work. > > My only concern is that one of the ethernets is bge and the other is > nve which is not known to be that stable, and I need both ports... I > suspect it will be ok, though. If push comes to shove I guess > installing an intel NIC card would not be out of the question. > > The rest of the hardware seems to be supported based on chipsets I > looked up from kernel boot messages from linux, openbsd, and netbsd > posted on the web. curiously i never found a boot message from > anyone running freebsd... I think these are priced in the low-mid $500 and include low profile cd- rom: The Sun unit looks very attractive though and I'd be very interested in your feedback should you go that route (or even if you don't and go w/ Tyan). Need to get something along these lines my self real soon now...;-) -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 23 21:57:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5824E16A42F for ; Wed, 23 Nov 2005 21:57:32 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id F279143D72 for ; Wed, 23 Nov 2005 21:56:50 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so924296nzp for ; Wed, 23 Nov 2005 13:56:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=lOUiIn41Osjofa7EbxlHguUQQ5Z63Wt5RItkr4zbuPkech9lJFGYB/zNxrovifFe5B3V99Czw7RqTFoWs57Qeb9XMIQlLO03kv7TGZK8f08twsPIxMRHNwH+WcnIeeUhNWnTVo2Wx56l4HCEWKr0AyPNflW1XEvxQCtq99IQkHk= Received: by 10.65.181.10 with SMTP id i10mr1302355qbp; Wed, 23 Nov 2005 13:56:38 -0800 (PST) Received: by 10.65.192.16 with HTTP; Wed, 23 Nov 2005 13:56:38 -0800 (PST) Message-ID: Date: Wed, 23 Nov 2005 22:56:38 +0100 From: Claus Guttesen To: freebsd-amd64 List MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: uid 0 exits on signal 10 when installing perl from ports 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, 23 Nov 2005 21:57:32 -0000 Hi. When I (re)install perl from the ports-collection I get: Nov 23 22:45:53 nydb kernel: pid 26078 (try), uid 0: exited on signal 10 (core dumped) Other than that the system works fine. Did a 'portupgrade -f perl'. FreeBSD 6.0 release on amd64, 2xdual-core opteron, 8 GB ram. Did accton to a file if that is usefull. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 11:49:39 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B855E16A41F for ; Thu, 24 Nov 2005 11:49:39 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53E1143D72 for ; Thu, 24 Nov 2005 11:49:34 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.4/8.13.4) with ESMTP id jAOBnOSt004044; Thu, 24 Nov 2005 12:49:32 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Thu, 24 Nov 2005 12:49:24 +0100 From: Palle Girgensohn To: Scott Long Message-ID: <0F031CB0B6B401C798370EE0@rambutan.pingpong.net> In-Reply-To: <4384AFE3.9090106@samsco.org> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <4384AFE3.9090106@samsco.org> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 24 Nov 2005 11:49:39 -0000 --On onsdag, november 23, 2005 11.07.31 -0700 Scott Long wrote: > Palle Girgensohn wrote: > >> Hi! >> >> I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does >> not boot, it just skips the CD, tried burning a couple of them, none >> works. i386 image works fine. Any ideas? >> >> /Palle >> > > Does the bootonly CD boot? Nope, it does not. It does boot from the i386 CD, though. It is a Dell 2850 with two 64bit Xeon CPUs. I've used amd64 (5.4) on similar machines before. /Palle From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 12:04:51 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66E6116A41F for ; Thu, 24 Nov 2005 12:04:51 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id B825443D8F for ; Thu, 24 Nov 2005 12:03:41 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.4/8.13.4) with ESMTP id jAOC3JWe004173; Thu, 24 Nov 2005 13:03:19 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Thu, 24 Nov 2005 13:03:19 +0100 From: Palle Girgensohn To: Palle Girgensohn , Scott Long Message-ID: <02B26A582766A3C7B98EADEA@rambutan.pingpong.net> In-Reply-To: <0F031CB0B6B401C798370EE0@rambutan.pingpong.net> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <4384AFE3.9090106@samsco.org> <0F031CB0B6B401C798370EE0@rambutan.pingpong.net> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 24 Nov 2005 12:04:51 -0000 --On torsdag, november 24, 2005 12.49.24 +0100 Palle Girgensohn wrote: > > > --On onsdag, november 23, 2005 11.07.31 -0700 Scott Long > wrote: > >> Palle Girgensohn wrote: >> >>> Hi! >>> >>> I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does >>> not boot, it just skips the CD, tried burning a couple of them, none >>> works. i386 image works fine. Any ideas? >>> >>> /Palle >>> >> >> Does the bootonly CD boot? > > Nope, it does not. It does boot from the i386 CD, though. It is a Dell > 2850 with two 64bit Xeon CPUs. I've used amd64 (5.4) on similar machines > before. Umm, no floppies exists for amd64... Can I boot from a i386 CD and then shift to the amd64 CD and contiunue...? From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 13:31:14 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0620F16A41F for ; Thu, 24 Nov 2005 13:31:14 +0000 (GMT) (envelope-from attos.janus@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AA4143D5F for ; Thu, 24 Nov 2005 13:31:13 +0000 (GMT) (envelope-from attos.janus@gmail.com) Received: by zproxy.gmail.com with SMTP id o37so1867237nzf for ; Thu, 24 Nov 2005 05:31:13 -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=k0QAAFDHLLgHczmq1nF4EFZbfK8I2lxnzAooN+G6EaCxuWTZe19Bs4rwEEvBwTRPQrr0N1cPKjyGPUVZPRXjWkiSkyMFFkOy3M7yaXW74dJGvAOueTdMjAKf775XpkHiyEXqKMKDlcSl58UjRQhDBHdXvwEXgPRyMr1ij4uc++k= Received: by 10.65.61.16 with SMTP id o16mr6166904qbk; Thu, 24 Nov 2005 05:31:08 -0800 (PST) Received: by 10.64.150.8 with HTTP; Thu, 24 Nov 2005 05:31:08 -0800 (PST) Message-ID: <5297d6fd0511240531g3e191395ld017cffbdb121df9@mail.gmail.com> Date: Thu, 24 Nov 2005 08:31:08 -0500 From: Attos To: Palle Girgensohn In-Reply-To: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 24 Nov 2005 13:31:14 -0000 Try booting with ACPI disabled. On 11/23/05, Palle Girgensohn wrote: > Hi! > > I downloaded the FreeBSD 6.0 amd64 disk 1 CD, and burnt it, but it does n= ot > boot, it just skips the CD, tried burning a couple of them, none works. > i386 image works fine. Any ideas? > > /Palle > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > -- Attos Janus From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 15:04:46 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A46F116A424 for ; Thu, 24 Nov 2005 15:04:46 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFBD743D53 for ; Thu, 24 Nov 2005 15:04:32 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1398697wxc for ; Thu, 24 Nov 2005 07:04:31 -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=pMiOJJlfxWsnZ1/JyvoobGEREwoitR993BjGfWd1WqQrS7SKOh7fOTgKSEPWJ8v66pD6bx+sEdrZyf6ZMPIfrPfG9aAN28oEZWEibCOSp4wM1kxhPlVDyhYri3J+rUJZlXs/MB7NIW2YskeVjOxIrMJqPA6jF3vuaaNpAE9Rvxs= Received: by 10.70.54.16 with SMTP id c16mr762287wxa; Thu, 24 Nov 2005 04:09:40 -0800 (PST) Received: by 10.70.105.13 with HTTP; Thu, 24 Nov 2005 04:09:40 -0800 (PST) Message-ID: <84dead720511240409p53882bb2p989ae0abb904910@mail.gmail.com> Date: Thu, 24 Nov 2005 17:39:40 +0530 From: Joseph Koshy To: Palle Girgensohn In-Reply-To: <02B26A582766A3C7B98EADEA@rambutan.pingpong.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <4384AFE3.9090106@samsco.org> <0F031CB0B6B401C798370EE0@rambutan.pingpong.net> <02B26A582766A3C7B98EADEA@rambutan.pingpong.net> Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? 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, 24 Nov 2005 15:04:46 -0000 > Umm, no floppies exists for amd64... Can I boot from a i386 CD and then > shift to the amd64 CD and contiunue...? You could boot and install as i386 and cross-build your way into amd64 land= . It's pretty straightforward. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 19:20:03 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E793216A41F for ; Thu, 24 Nov 2005 19:20:02 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83CB743D62 for ; Thu, 24 Nov 2005 19:20: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.3/8.13.3) with ESMTP id jAOJK1cI013363 for ; Thu, 24 Nov 2005 19:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAOJK1pn013362; Thu, 24 Nov 2005 19:20:01 GMT (envelope-from gnats) Resent-Date: Thu, 24 Nov 2005 19:20:01 GMT Resent-Message-Id: <200511241920.jAOJK1pn013362@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, Lanny Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5556116A41F for ; Thu, 24 Nov 2005 19:16:00 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F76C43D67 for ; Thu, 24 Nov 2005 19:15:56 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAOJFrYq051742 for ; Thu, 24 Nov 2005 19:15:53 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAOJFrQV051741; Thu, 24 Nov 2005 19:15:53 GMT (envelope-from nobody) Message-Id: <200511241915.jAOJFrQV051741@www.freebsd.org> Date: Thu, 24 Nov 2005 19:15:53 GMT From: Lanny To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89501: System crashes on install using ftp on local subnet 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, 24 Nov 2005 19:20:03 -0000 >Number: 89501 >Category: amd64 >Synopsis: System crashes on install using ftp on local subnet >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 24 19:20:01 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Lanny >Release: FreeBSD-6.0/AMD64 >Organization: FreeBSD Systems >Environment: Not installed yet, problem arises -during- install >Description: When trying to install either at the console or via redirected serial console, FreeBSD-6.0/AMD64 is crashing during the 'base' part of the install when using ftp on local subnet. ─[ Progress ] ─────────────────┐ │ Extracting base into / directory... │ │ ┌─────────────── ─────────────────────────── ─┐ │ │ │ │ │ └ └─────────────────────────────────────── ─┘ │ └─────────────────────76 2% ──────────────────────┘ Fatal Error: Invalid realloc size of 0! - PRESS ANY KEY TO REBOOTes/sec. It is always around the 76% when this happens. I have tried to install on 15 Servers this week and in almost all cases this happens exactly as shown above. >How-To-Repeat: Install FreeBSD-6.0/AMD64 using 'ftp' as the media. >Fix: I have made Scott Long aware of this and was asked to submit this bug report. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 23:13:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CE9D16A531 for ; Thu, 24 Nov 2005 23:13:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 599F844EE6 for ; Thu, 24 Nov 2005 20:48:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 870561A3C28; Thu, 24 Nov 2005 12:48:33 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D297251590; Thu, 24 Nov 2005 15:48:32 -0500 (EST) Date: Thu, 24 Nov 2005 15:48:32 -0500 From: Kris Kennaway To: Claus Guttesen Message-ID: <20051124204832.GA30182@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64 List Subject: Re: uid 0 exits on signal 10 when installing perl from ports 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, 24 Nov 2005 23:13:27 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 10:56:38PM +0100, Claus Guttesen wrote: > Hi. >=20 > When I (re)install perl from the ports-collection I get: >=20 > Nov 23 22:45:53 nydb kernel: pid 26078 (try), uid 0: exited on signal > 10 (core dumped) >=20 > Other than that the system works fine. It's probably a configure script *try*ing to crash to test some feature or other. Nothing to worry about, if so. Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhicgWry0BWjoQKURAm12AJ9EAVOE78I0Oy52sDIbSBF0lcbh2ACgme19 l5rlaYGd6bERHK6Y2VInTTc= =pFHz -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 23:17:38 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B6C116A57A for ; Thu, 24 Nov 2005 23:17:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32984553A for ; Thu, 24 Nov 2005 22:10:02 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAOMA2rG035127 for ; Thu, 24 Nov 2005 22:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAOMA2sW035115; Thu, 24 Nov 2005 22:10:02 GMT (envelope-from gnats) Resent-Date: Thu, 24 Nov 2005 22:10:02 GMT Resent-Message-Id: <200511242210.jAOMA2sW035115@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, Faris Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37E9016A42C for ; Thu, 24 Nov 2005 22:00:30 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id B148E459DE for ; Thu, 24 Nov 2005 21:37:33 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAOLbXMJ003173 for ; Thu, 24 Nov 2005 21:37:33 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAOLbXXv003172; Thu, 24 Nov 2005 21:37:33 GMT (envelope-from nobody) Message-Id: <200511242137.jAOLbXXv003172@www.freebsd.org> Date: Thu, 24 Nov 2005 21:37:33 GMT From: Faris To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89503: Cant Boot Installation 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: Thu, 24 Nov 2005 23:17:40 -0000 >Number: 89503 >Category: amd64 >Synopsis: Cant Boot Installation Disk >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 24 22:10:02 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Faris >Release: 6.0 AMD 64 >Organization: Heat and Comfort >Environment: No output >Description: Hello, I have downloaded and burned the ISo of 6.0 Amd 64 . Once I load the installation All I see is the main selection table after that everything just freezes. I have a HP laptop with AMD 64 on it 1GB ram Thanks >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 24 23:26:18 2005 Return-Path: X-Original-To: amd64@freeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10C0616A41F for ; Thu, 24 Nov 2005 23:26:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C558543D5D for ; Thu, 24 Nov 2005 23:26:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id AC01F1A3C1A for ; Thu, 24 Nov 2005 15:26:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 166C151592; Thu, 24 Nov 2005 18:26:17 -0500 (EST) Date: Thu, 24 Nov 2005 18:26:16 -0500 From: Kris Kennaway To: amd64@freeBSD.org Message-ID: <20051124232616.GA32023@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: spin lock smp rendezvous held by 0xffffff01250a7980 for > 5 seconds 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, 24 Nov 2005 23:26:18 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I got this on a quad amd64 machine running 6.0-STABLE. At the time it was running 21 simultaneous tar extractions onto a sync-mounted md. panic() at panic+0x1e6 _mtx_lock_spin() at _mtx_lock_spin+0xad pmap_invalidate_range() at pmap_invalidate_range+0xb3 pmap_qremove() at pmap_qremove+0x53 vfs_vmio_release() at vfs_vmio_release+0x1e0 getnewbuf() at getnewbuf+0x368 getblk() at getblk+0x3d9 ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 ffs_write() at ffs_write+0x31b VOP_WRITE_APV() at VOP_WRITE_APV+0xed vn_write() at vn_write+0x228 dofilewrite() at dofilewrite+0x90 kern_writev() at kern_writev+0x54 write() at write+0x4b Unfortunately I can't dump on this machine (and no debugging is currently enabled), but I can try to reproduce it. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhkwYWry0BWjoQKURAglVAKCfvBO5EnAFvMxfb1hGaxPV8MpVHgCgq0mT HomC4GM17aEBB0okCm096Fc= =+WPL -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 11:34:35 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BB5C16A41F for ; Fri, 25 Nov 2005 11:34:35 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B1A843D66 for ; Fri, 25 Nov 2005 11:34:34 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id BF337BDFA; Fri, 25 Nov 2005 12:34:35 +0100 (CET) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 76B37285; Fri, 25 Nov 2005 12:32:21 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 5CC93272; Fri, 25 Nov 2005 12:32:21 +0100 (CET) Date: Fri, 25 Nov 2005 12:32:21 +0100 (CET) From: Sten Spans To: Nathan Vidican In-Reply-To: <4384BBBF.4030007@wmptl.com> Message-ID: References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> <4384BBBF.4030007@wmptl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: amd64@freebsd.org Subject: Re: Sun x2100 Server Compatability 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, 25 Nov 2005 11:34:35 -0000 On Wed, 23 Nov 2005, Nathan Vidican wrote: > Vivek Khera wrote: >> >> On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: >> >>> Nathan Vidican schrieb: >>> >>>> Any known issues running FreeBSD/amd64 on a Sun x2100 server? Single >>>> opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: >>> >>> >>> The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without PS/2 >>> mouse and keyboard ports. So you should look at success reports for this >>> board. >> >> >> > Same issue here... both NIC's requried, but putting in a good ole Intel/FXP > card won't bother me in the least. The x2100 is listed as only having pci-E expansion options ... so a regular pci ethernet card wont fit. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 14:09:43 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB48F16A41F for ; Fri, 25 Nov 2005 14:09:43 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 379BE43D5D for ; Fri, 25 Nov 2005 14:09:41 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jAPE9b2V013339; Fri, 25 Nov 2005 09:09:37 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <43871B20.3050007@wmptl.com> Date: Fri, 25 Nov 2005 09:09:36 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> In-Reply-To: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.711 () J_CHICKENPOX_53,RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 14:09:43 -0000 ray@redshift.com wrote: > Hi Olaf, > > Congrats on getting the 3ware card. Keep in mind you can download the manuals > in PDF from 3ware if you want to get a head start on things. I think when you > build the RAID in under 10 minutes, you'll be very happy you went with 3ware. > The 9500S is an excellent card. > Same - trust me on this one, you got them to make the right decision there as far as S-ATA RAID goes. > | 1-What would you recommend: Fbsd 5.4 or 6.0 (we're speaking about the > | AMD64 version here, and AFAIK they bought a dual core processor (I think > | an Athlon)). I have found mention of the 6.0 version having much better > | multithreading mechanisms, and it being better for DB servers, yet, is > | it already deemed stable enough for a live DB server? Any ideas??? > > My policy is to never be the first kid on the block to test something new - > especially not in production. FreeBSD 5.4 has been hammered on for a long time > and works really well. 5.4 is an evolution of 5.2.1 and 5.3 - all of which are > very mature and very stable. I've been running FreeBSD in production since > version 5.2.1 and have been using FreeBSD since 4.9 (previously we used Redhat > linux for our production servers). Anyway, when I build a machine, here is > exactly what I use: > I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has been kicking it almost as long as 5.4-RELEASE has been out. Most of the experiences I've heard back from other users are saying 6.0, even RC-1 before -RELEASE actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 will help you out, (eg filesystem changes, SMP support, hardware drivers, etc). Considering the newer hardware you've chosen (dual core amd64 cpu) - 6.0 is much better prepared to handle it in the kernel. I've been running 6.0-RC1 on one of the dual opterons we have here now for a couple of months now - performance is great and havn't had a moments downtime yet. Seriously, do not discount 6.0 because it's a '.0' release, really it's not. As Ray pointed out, 5.4 was an evolution of 5.2 - 5.3, etc... what he did not potentially realize, is that 6.0 is of that same evolution. Read the notes as to why the version skipped from 5.4 -> 6.0, and you'll realize that 6.0 was simply a new version number to a release that would have otherwise been say 5.5, the reason for the skip was because of the large number of new capbilities and features. And yes, new features generall can equal new bugs - but if you're not relying upon them and you're doing the same thing you would with a 5.4 machine, then why sacrafice the added filesystem performance and hardware support by not running 6.0? > FreeBSD 5.4 from the 5.4 ISO CD-ROM images. I don't apply any patches or do any > CVS stuff. Just the basic install from the CD's, then tweak the kernel by > stripping out unneeded drivers. > > PHP 4.3.11 or 4.4.1 (built from source) > > APC built from ports (this is optional, but does speed up PHP by a factor of 2) > > MySQL 4.1.15 (built from Source) > > Apache 1.3.33 (built from source) > > I run SSH to access the machines and use the bash shell. > > That's all I ever use. Our SSL stuff is handled by dedicated hardware, so I > don't bother with OpenSSL. If you need a firewall on the actual server (as > opposed to having a router provide it), then use ipf and setup an /etc/ipf.rules > file. > I agree, short of large security patches, stick with a -RELEASE code. In any given production environment stability is key. While cvsup'ing and building the new box everyday to stay current sounds good - it is in practice not good for production servers - if it isn't broke, don't fix it. > As far as 6.0 having better threading, that is quite possible. I personally > haven't performed any benchmarks on 5.4 vs. 6.0. However, keep in mind, a lot > of people get all caught up squeezing the last possible ounce of performance > from machines, when really that's not the best idea. Using a properly setup > FreeBSD machine, you should have no problem handling 2000 to 3000 (if not more) > connections per second. I have several machines here running dual AMD opterons > that have no problem doing 6000 to 7000 httpd connections per second on 1k .html > files and > > Same for the MySQL server, you should be able to easily handle 1000 to 2000 > inserts and 4000 to 5000 simple selects per second from your average dual > Opteron server. > > Even a single Xeon 2.4 Ghz machine can do about 50% to 60% of those numbers > above. The point is that once you reach this level, then usually CPU/server > power isn't your problem. Typically it's bandwidth. Even with 500 connections > per second, it's easy to swamp a 10 or 20 mbit connection. So if you are using > anything less than a full 100/mbit connection, then I wouldn't worry too much > about the threading vs. non-threading stuff. Most applications run multiple > processes, more than they do multiple threads. And like I say, most of the > time, the problem isn't speed of execution, it's bandwidth. Either way, at > least at this point, I would stick with 5.4 myself. I've yet to see a well > configured server run much above a load of 3 or 4 when everything is setup > properly. > > Now if you are setting up the next google or yahoo, then maybe threading has > more of an impact. But even so, keep in mind that multiple threads don't get > you more CPU power. It's still the same number of CPU's executing the code - > albeit perhaps slightly more effectively. Usually at the end of the day, it's > better to not try to squeeze every last ounce of power from the machine. That > will often times result in instability problems. You are usually money and time > ahead by just getting a simple load balancer and tossing a couple of more mildly > tweaked servers into your cluster. Breaking the load across 2 or 3 machines is > always better than trying to tweak out 1 solitary machine to run at 150% of what > it really likes to run at :-) All good points, but at 4000+ connections, updates, etc per second... I/O becomes the issue not so much bandwidth. So long as load were to stay consistent with that many updates, I really wouldn't be worried about bandwidth as much as I would disk storage to handle that. I'm running 15,000RPM Ultra160 SCSI arrays that have hard time dealing with keeping the disk current doing around 10,000 updates/minute accross 4 tables and about 60 fields of data... queries of course are another matter. - Just something to think about, every installation has differing requirements, if you're planning on running a website and having a small office of 15-25 people connecting to mysql from some app - then I wouldn't worry about it. As Olaf pointed out many times in this thread (or related threads) - budget is key with this deal, so I doubt load balancing and plopping another machine in is an option his client really wants to hear about - until they've gotten to a point to justify doing so. Why scare customers away telling them they can buy more, if you just sold them something new why isn't it going to be good enough - guarantee that's not a question you'll want to provoke. > > | 2-Regarding the kernel: I'll have to add in DVD-RW support, so I'll have > | to do a custom kernel compilation anyway. You mentioned I need to use > | SMP support. What would you think would be best; stick with the generic > | base version, and add it SMP support, or SMP kernel config included in > | sys/amd64/conf? > > Are you building a server or a workstation? The "SMP" kernel in amd64/conf is > just the generic (base) kernel with 1 extra line. However you slice it, most > likely you'll end up having to recompile the kernel at some point (for example, > if you need to run a fire wall (ipf), then you are going to have to recompile it > anyway. When you do that, just make sure you don't accidently omit the SMP line > by working strictly off the generic kernel. Look at GENERIC and SMP in amd/conf > and you'll see what I mean. > > All you need to do is add a maxusers line and comment out drivers that aren't > needed. That will get you on the right track. > Same response. Look at the SMP file, it's basically "options smp; include GENERIC"... just copy the GENERIC to your own config, remove the driver(s) you don't require, add 'options SMP' and any other options you may wish - rename the config and go from there. > | 3-What would exactly be the differences in D/L-ing the MySQL (4.1.x) > | source from MySQL and compiling that, vs. rebuilding the ports tree, and > | then 'make - make install'-ing that version? The difference (in > | particular: the advantage) in the former isn't clear to me.... I would > | have guessed the ports version to be tuned for the AMD64 version of > | FBSD, or am I missing out on something here?!? > > Usually building from ports is pretty close to building from source. All the > "make install clean" command does is download the source, then compile it. I've > had problems with the binaries and the ports in the past, so I am just in the > habit of compiling from source. It gives you a little more control and a better > feeling for what's going on if you build it from source. It also takes into > account any tweaks you do in /etc/make.conf and it also let's you do a configure > command with whatever settings you want. The ports collection has been optimized for 'the average install', leveraging performance for functionality in most situations to be ideal. The ports usually have added patches or adjustments to code which integrates them better with FreeBSD, if you're not all that familair with the code you're working with, (in this case mysql), then I'd reccomend you stick with the ports collection. However, that being said - note that the ports collection isn't always up to date, and you may want a differing version of mysql. Follow the documentation on mysql.com and you should be just fine - fairly staght forward install and differs little from doing so via the FreeBSD ports collection. In any production system though, I highly reccomend compiling from source vs downloading binaries - that way nothing has been linked to/from librairies which may or may not be the same on your system. > > | 4-Regarding MySQL: a similar question as for FBSD itself: v5 sounds > | sweet, yet it's only been a few weeks since their first stable release > | has been out there... What do you think would it be better/safer to > | stick with 4.1.x? I'm definitely partial towards the latter as I don't > | think the people involved will need the additional v5 features, but > | then, as an ulterior motive for me it could be sweet to get some > | hands-on experience with v5. ;) > > For production, I would stick with 4.1.15. I'm sure MySQL 5 is very nice, but > as you say, it's only been out for a few weeks. I have not done any > benchmarking between MySQL 4 and 5, so I can't tell you which is faster. > However, in the case of both PHP and Apache, the older version out perform the > later versions hands down (this is why I use apache 1.3.33 and PHP 4.3/4.4). A > lot of times, as code becomes more bloated with additional features, it slows > down and usually moves towards a higher level application. And usually > applications that move to higher levels (which means it's easier for the > programmer to code) sacrifice some amount of speed and incur a larger memory > foot print in the process. That's not always the case, but often times it is. > > In the case of MySQL 5, you would have to look into the features, but most of > the stuff I saw in MySQL didn't strike me as being needed for most > applications/database stuff - at least as far as relating to the average > webserver. As I recall, they added views, procedures and triggers, etc. Most > of that stuff, while nice, isn't going to make or break any web app out there. > Yes, you can use something like procedures to offload some of the code from > something like PHP to MySQL - but is that actually faster? I couldn't tell you > - you'd have to test it first hand to see if it makes a difference. For me, I > benchmark test everything and believe no one :-) So just because MySQL 5 is > new, in my book that doesn't make it faster, better, more stable. It just makes > it new. > > Since MySQL 4.x.x has been working all across the internet for years, that's > good enough for me. As mentioned above, stability (to me) is far more important > than getting 4200 instead of 4000 selects per second. I can always add another > $2000 machine and jump right to ~8000 per second and not have to worry about it :) > I agree, stick with 4.1.x, but for different reasons. Compatability; not sure what you are doing, the size or scope of the database you're dealing with, but if for example you're going to be writting and app in windows which uses the myodbc driver to connect... then you may run into problems with newer versions of mysql. I encountered a LOT of this, when we moved from 3.x up to 4.1, largely because of changes in the client - at least I was aware of that before I started, but I did have to rebuild client librairies on all webservers, and re-install odbc drivers on client machines throughout the building because of it. Might not be something you're willing/ready to undertake for the features you've already mentioned not being required in mysql 5. > Anyway, I think you get the idea. If you have any questions, feel free to let > me know. I'll be happy to help where I can. > > Ray > > > > > > Good luck with it all, just my experience reflecting here - so hope it helps. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 14:48:09 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 710B516A41F for ; Fri, 25 Nov 2005 14:48:09 +0000 (GMT) (envelope-from Faris@heatandcomfort.com) Received: from host217.ipowerweb.com (host217.ipowerweb.com [66.235.203.151]) by mx1.FreeBSD.org (Postfix) with SMTP id ED5F343D46 for ; Fri, 25 Nov 2005 14:47:54 +0000 (GMT) (envelope-from Faris@heatandcomfort.com) Received: (qmail 10925 invoked from network); 25 Nov 2005 14:46:15 -0000 Received: from unknown (HELO ?127.0.0.1?) (66.110.255.248) by host217.ipowerweb.com with SMTP; 25 Nov 2005 14:46:13 -0000 Message-ID: <438723ED.9000200@heatandcomfort.com> Date: Fri, 25 Nov 2005 09:47:09 -0500 From: Faris User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org References: <200511242210.jAOMA2wH035074@freefall.freebsd.org> In-Reply-To: <200511242210.jAOMA2wH035074@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-DCC-ipwdcc-1-Metrics: host217.ipowerweb.com 208; Body=1 Fuz1=1 Fuz2=1 Cc: Subject: Re: amd64/89503: Cant Boot Installation 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, 25 Nov 2005 14:48:09 -0000 Hello, Regarding the problem that I had . Someone else has solved the problem at the link below. I did the same but after installation system wont load http://www.cokane.org/amd64.html#cpq3000 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 14:49:05 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D27D16A42A for ; Fri, 25 Nov 2005 14:49:05 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DE4F43D81 for ; Fri, 25 Nov 2005 14:48:31 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 18so1754153nzp for ; Fri, 25 Nov 2005 06:48:31 -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=e1AFy32lSXUMyu+zoh5hwrePC9H+7W26jg8N6oCaIj77azX2+XEHknksN/WlmJQ2ZACagMmOHG2ThoYcgcqnvWrAtSq7qGWk9E5Gu/xtAJsI/4pQDhumMYlWJpzvy6J5hkK/QR7V8CmNtWkvCrNMFY1fqABHUjkkSBAOdMDdNsU= Received: by 10.65.11.20 with SMTP id o20mr8401351qbi; Fri, 25 Nov 2005 06:48:31 -0800 (PST) Received: by 10.65.192.16 with HTTP; Fri, 25 Nov 2005 06:48:31 -0800 (PST) Message-ID: Date: Fri, 25 Nov 2005 15:48:31 +0100 From: Claus Guttesen To: Nathan Vidican In-Reply-To: <43871B20.3050007@wmptl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <43871B20.3050007@wmptl.com> Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 14:49:05 -0000 > > My policy is to never be the first kid on the block to test something n= ew - > > especially not in production. FreeBSD 5.4 has been hammered on for a l= ong time > > and works really well. 5.4 is an evolution of 5.2.1 and 5.3 - all of w= hich are > > very mature and very stable. I've been running FreeBSD in production s= ince > > version 5.2.1 and have been using FreeBSD since 4.9 (previously we used= Redhat > > linux for our production servers). Anyway, when I build a machine, her= e is > > exactly what I use: > > > > I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has b= een > kicking it almost as long as 5.4-RELEASE has been out. Most of the experi= ences > I've heard back from other users are saying 6.0, even RC-1 before -RELEAS= E > actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 w= ill > help you out, (eg filesystem changes, SMP support, hardware drivers, etc)= . I just phased in a new postgresql db-server based on the 6.0 release. I did stress-test it doing an import, making buildworld and buildkernel, reinstalling ports etc. trying to put as much load on the cpu and disk-io as I could and it behaved fine. Three things changed, I went from four single core opterons to two dual cores, from four to eight GB ram and from FreeBSD 5.4 release to 6.0 release. My timing is not optimal since we're somewhat busy but we need the additional four GB ram. Postgresql only got the minor upgrade from 7.4.8 to 7.4.9. The improved smp- and disk-io (from what I read) under 6.0 and the stability during my testing made me go for this release. I'll let you know on monday how it went. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 14:50:06 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12DC816A422 for ; Fri, 25 Nov 2005 14:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3F7143D49 for ; Fri, 25 Nov 2005 14:50:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPEo5uQ081743 for ; Fri, 25 Nov 2005 14:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPEo5QA081742; Fri, 25 Nov 2005 14:50:05 GMT (envelope-from gnats) Date: Fri, 25 Nov 2005 14:50:05 GMT Message-Id: <200511251450.jAPEo5QA081742@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Faris Cc: Subject: Re: amd64/89503: Cant Boot Installation Disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Faris List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 14:50:06 -0000 The following reply was made to PR amd64/89503; it has been noted by GNATS. From: Faris To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/89503: Cant Boot Installation Disk Date: Fri, 25 Nov 2005 09:47:09 -0500 Hello, Regarding the problem that I had . Someone else has solved the problem at the link below. I did the same but after installation system wont load http://www.cokane.org/amd64.html#cpq3000 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:03:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FDDB16A422 for ; Fri, 25 Nov 2005 16:03:04 +0000 (GMT) (envelope-from apelisse@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD63943D6D for ; Fri, 25 Nov 2005 16:02:55 +0000 (GMT) (envelope-from apelisse@gmail.com) Received: by nproxy.gmail.com with SMTP id l23so334242nfc for ; Fri, 25 Nov 2005 08:02:54 -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:references; b=T4+HJsWkeuK0Ado/YuCycc1ZugZvjDUh/SMbND/qAs9eWVYABgAUMF1xTOB+GLNN7R+Ao6ob2JRVsk55PXJ5asEvFfejFTxBXGJVZg1JB21/XgHE7P8J+nPH76zKs58BQr77Cgs2ObQJ44h6ACaRsqnywenGOGy0UghU2X77Lko= Received: by 10.48.248.14 with SMTP id v14mr217048nfh; Fri, 25 Nov 2005 08:02:54 -0800 (PST) Received: by 10.49.5.1 with HTTP; Fri, 25 Nov 2005 08:02:54 -0800 (PST) Message-ID: <61c746830511250802vcd90a6dkba031548886ff393@mail.gmail.com> Date: Fri, 25 Nov 2005 16:02:54 +0000 From: Antoine Pelisse To: Faris In-Reply-To: <438723ED.9000200@heatandcomfort.com> MIME-Version: 1.0 References: <200511242210.jAOMA2wH035074@freefall.freebsd.org> <438723ED.9000200@heatandcomfort.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/89503: Cant Boot Installation 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, 25 Nov 2005 16:03:04 -0000 There is a fix for this bug and it's documented by atkbd(5) in the Driver Flags section: bit 3 (NO_PROBE_TEST) When this option is given, the atkbd driver will not test the key- board port during the probe routine. Some machines hang during boot when this test is performed. However, this doesn't work on my AMD64 laptop computer and I'm currently trying to pinpoint the actual problem. (seems to be related to the keyboard nonetheless) From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:10:11 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 767AC16A41F for ; Fri, 25 Nov 2005 16:10:11 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1EF43D5E for ; Fri, 25 Nov 2005 16:10:11 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGA8rd097224 for ; Fri, 25 Nov 2005 16:10:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGA8QP097223; Fri, 25 Nov 2005 16:10:08 GMT (envelope-from gnats) Date: Fri, 25 Nov 2005 16:10:08 GMT Message-Id: <200511251610.jAPGA8QP097223@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Antoine Pelisse Cc: Subject: Re: amd64/89503: Cant Boot Installation Disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Antoine Pelisse List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 16:10:11 -0000 The following reply was made to PR amd64/89503; it has been noted by GNATS. From: Antoine Pelisse To: Faris Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/89503: Cant Boot Installation Disk Date: Fri, 25 Nov 2005 16:02:54 +0000 ------=_Part_30189_22148545.1132934574264 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline There is a fix for this bug and it's documented by atkbd(5) in the Driver Flags section: bit 3 (NO_PROBE_TEST) When this option is given, the atkbd driver will not test the key- board port during the probe routine. Some machines hang during boot when this test is performed. However, this doesn't work on my AMD64 laptop computer and I'm currently trying to pinpoint the actual problem. (seems to be related to the keyboard nonetheless) ------=_Part_30189_22148545.1132934574264 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline There is a fix for this bug and it's documented by atkbd(5) in the Driver F= lags section:
     bit 3 (NO_PROBE_TEST)
           When this opti= on is given, the atkbd driver will not test the key-
           board port during the probe routine.  Some machines hang during
           boot when this= test is performed.
However, this doesn't work on my AMD64 laptop computer and I'm currently trying to pinpoint the actual problem. (seems to be related to the keyboard nonetheless)
------=_Part_30189_22148545.1132934574264-- From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:28:36 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A51C16A41F; Fri, 25 Nov 2005 16:28:36 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E31A843D5C; Fri, 25 Nov 2005 16:28:35 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGSZF3097909; Fri, 25 Nov 2005 16:28:35 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGSZWP097905; Fri, 25 Nov 2005 16:28:35 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:28:35 GMT From: Tilman Linneweh Message-Id: <200511251628.jAPGSZWP097905@freefall.freebsd.org> To: cwhann@gmail.com, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/87898: Failt to init X: can't open device/io 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, 25 Nov 2005 16:28:36 -0000 Synopsis: Failt to init X: can't open device/io State-Changed-From-To: open->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 16:27:12 GMT 2005 State-Changed-Why: duplicete of 87748 http://www.freebsd.org/cgi/query-pr.cgi?pr=87898 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:34:47 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EC5816A41F; Fri, 25 Nov 2005 16:34:47 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2294743D5C; Fri, 25 Nov 2005 16:34:47 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGYkgF000494; Fri, 25 Nov 2005 16:34:46 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGYkCV000490; Fri, 25 Nov 2005 16:34:46 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:34:46 GMT From: Tilman Linneweh Message-Id: <200511251634.jAPGYkCV000490@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-amd64@FreeBSD.org, pav@FreeBSD.org Cc: Subject: Re: amd64/86199: Missed AMD64 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 16:34:47 -0000 Synopsis: Missed AMD64 motherboard Responsible-Changed-From-To: freebsd-amd64->pav Responsible-Changed-By: arved Responsible-Changed-When: Fri Nov 25 16:34:20 GMT 2005 Responsible-Changed-Why: pav maintains the list of amd64-motherboards http://www.freebsd.org/cgi/query-pr.cgi?pr=86199 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:42:07 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAE2916A420; Fri, 25 Nov 2005 16:42:07 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 921DB43D5F; Fri, 25 Nov 2005 16:42:07 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGg78S000737; Fri, 25 Nov 2005 16:42:07 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGg7wP000733; Fri, 25 Nov 2005 16:42:07 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:42:07 GMT From: Tilman Linneweh Message-Id: <200511251642.jAPGg7wP000733@freefall.freebsd.org> To: morgothdbma@o2.pl, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/82178: missing 32bit subsystem 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, 25 Nov 2005 16:42:08 -0000 Synopsis: missing 32bit subsystem State-Changed-From-To: open->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 16:41:44 GMT 2005 State-Changed-Why: This was answered by steve, and the topic belongs to freebsd-questions http://www.freebsd.org/cgi/query-pr.cgi?pr=82178 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:46:17 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 261E516A420; Fri, 25 Nov 2005 16:46:17 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C499543D66; Fri, 25 Nov 2005 16:46:16 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGkGvS000850; Fri, 25 Nov 2005 16:46:16 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGkGq3000846; Fri, 25 Nov 2005 16:46:16 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:46:16 GMT From: Tilman Linneweh Message-Id: <200511251646.jAPGkGq3000846@freefall.freebsd.org> To: morgothdbma@o2.pl, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/69709: ACPI enabled then floppy don't work (5.2.1 amd64) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 16:46:17 -0000 Synopsis: ACPI enabled then floppy don't work (5.2.1 amd64) State-Changed-From-To: open->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 16:42:54 GMT 2005 State-Changed-Why: This PR has not enough information. If you write a PR about a hardware problem, you should at least mention what kind of hardware you are using. Additional 5.2.1 is quite outdated, so this problem most likely is fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=69709 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:49:23 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1B4E16A41F; Fri, 25 Nov 2005 16:49:23 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C41743D6B; Fri, 25 Nov 2005 16:49:21 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGnLX0000914; Fri, 25 Nov 2005 16:49:21 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGnLb4000910; Fri, 25 Nov 2005 16:49:21 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:49:21 GMT From: Tilman Linneweh Message-Id: <200511251649.jAPGnLb4000910@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-java@FreeBSD.org Cc: Subject: Re: ports/85626: java/jdk15 compile error 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, 25 Nov 2005 16:49:23 -0000 Synopsis: java/jdk15 compile error Responsible-Changed-From-To: freebsd-amd64->freebsd-java Responsible-Changed-By: arved Responsible-Changed-When: Fri Nov 25 16:48:42 GMT 2005 Responsible-Changed-Why: refile as a ports PR and assign to java ports maintainers. http://www.freebsd.org/cgi/query-pr.cgi?pr=85626 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:57:00 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB57F16A422; Fri, 25 Nov 2005 16:56:59 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A7543D55; Fri, 25 Nov 2005 16:56:21 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGuLPw001191; Fri, 25 Nov 2005 16:56:21 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGuKEx001187; Fri, 25 Nov 2005 16:56:21 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:56:21 GMT From: Tilman Linneweh Message-Id: <200511251656.jAPGuKEx001187@freefall.freebsd.org> To: pikapaxan@yandex.ru, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org Cc: Subject: Re: ports/85081: TeamSpeak 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, 25 Nov 2005 16:57:00 -0000 Synopsis: TeamSpeak State-Changed-From-To: open->feedback State-Changed-By: arved State-Changed-When: Fri Nov 25 16:55:08 GMT 2005 State-Changed-Why: refile as ports PR, this seems to be a ports PR. Which port are you talking about? the teamspeak_server is marked as working only on i386. Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: arved Responsible-Changed-When: Fri Nov 25 16:55:08 GMT 2005 Responsible-Changed-Why: refile as ports PR, this seems to be a ports PR. Which port are you talking about? the teamspeak_server is marked as working only on i386. http://www.freebsd.org/cgi/query-pr.cgi?pr=85081 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 16:57:40 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83D1416A420; Fri, 25 Nov 2005 16:57:40 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3AF543D5D; Fri, 25 Nov 2005 16:57:35 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPGvZ1k001266; Fri, 25 Nov 2005 16:57:35 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPGvZ20001262; Fri, 25 Nov 2005 16:57:35 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 16:57:35 GMT From: Tilman Linneweh Message-Id: <200511251657.jAPGvZ20001262@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-java@FreeBSD.org Cc: Subject: Re: ports/81272: JDK 1.5 port doesn't build. 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, 25 Nov 2005 16:57:40 -0000 Synopsis: JDK 1.5 port doesn't build. Responsible-Changed-From-To: freebsd-amd64->freebsd-java Responsible-Changed-By: arved Responsible-Changed-When: Fri Nov 25 16:57:03 GMT 2005 Responsible-Changed-Why: Refile, this looks like a ports issue. Assign to port maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=81272 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 17:02:51 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FDD416A420; Fri, 25 Nov 2005 17:02:51 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A25343D46; Fri, 25 Nov 2005 17:02:49 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPH2new001520; Fri, 25 Nov 2005 17:02:49 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPH2m3U001516; Fri, 25 Nov 2005 17:02:48 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 17:02:48 GMT From: Tilman Linneweh Message-Id: <200511251702.jAPH2m3U001516@freefall.freebsd.org> To: markus@trippelsdorf.de, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/77629: aMule hardlocks AMD64 system 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, 25 Nov 2005 17:02:51 -0000 Synopsis: aMule hardlocks AMD64 system State-Changed-From-To: open->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 16:59:48 GMT 2005 State-Changed-Why: Close, the problem seems to be resolved by using a different hardware. If the fxp card is still broken on 6.0 and you think this is a driver issue please report with more detailed information about the specific hardware revision http://www.freebsd.org/cgi/query-pr.cgi?pr=77629 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 17:07:19 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3938116A41F; Fri, 25 Nov 2005 17:07:19 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD0243D45; Fri, 25 Nov 2005 17:07:13 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPH7DaB006404; Fri, 25 Nov 2005 17:07:13 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPH7DCK006400; Fri, 25 Nov 2005 17:07:13 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 17:07:13 GMT From: Tilman Linneweh Message-Id: <200511251707.jAPH7DCK006400@freefall.freebsd.org> To: bilbo@hobbiton.org, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/81325: [ath] KLD if_ath.ko: depends on ath_hal - not available, kldload: Unsupported file type 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, 25 Nov 2005 17:07:19 -0000 Synopsis: [ath] KLD if_ath.ko: depends on ath_hal - not available, kldload: Unsupported file type State-Changed-From-To: open->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 17:07:00 GMT 2005 State-Changed-Why: ath_hal is supported on amd64 in FreeBSD 6.0 http://www.freebsd.org/cgi/query-pr.cgi?pr=81325 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 17:35:57 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB83016A420; Fri, 25 Nov 2005 17:35:57 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72A7043D68; Fri, 25 Nov 2005 17:35:57 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPHZvHX008346; Fri, 25 Nov 2005 17:35:57 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPHZvoC008342; Fri, 25 Nov 2005 17:35:57 GMT (envelope-from arved) Date: Fri, 25 Nov 2005 17:35:57 GMT From: Tilman Linneweh Message-Id: <200511251735.jAPHZvoC008342@freefall.freebsd.org> To: mprabu@gmail.com, arved@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/87436: gui does not start on the ATI RS480 M2-IL chipset board with AMD64 processor 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, 25 Nov 2005 17:35:57 -0000 Synopsis: gui does not start on the ATI RS480 M2-IL chipset board with AMD64 processor State-Changed-From-To: analyzed->closed State-Changed-By: arved State-Changed-When: Fri Nov 25 17:35:18 GMT 2005 State-Changed-Why: feedback timeout, one month http://www.freebsd.org/cgi/query-pr.cgi?pr=87436 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 19:00:12 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C33B116A41F for ; Fri, 25 Nov 2005 19:00:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B8A43D5E for ; Fri, 25 Nov 2005 19:00:11 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPJ0Bf4017731 for ; Fri, 25 Nov 2005 19:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPJ0B7b017730; Fri, 25 Nov 2005 19:00:11 GMT (envelope-from gnats) Resent-Date: Fri, 25 Nov 2005 19:00:11 GMT Resent-Message-Id: <200511251900.jAPJ0B7b017730@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, "faris@heatandcomfort.com" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1253116A41F for ; Fri, 25 Nov 2005 18:53:45 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC97843D58 for ; Fri, 25 Nov 2005 18:53:44 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAPIriPs064778 for ; Fri, 25 Nov 2005 18:53:44 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAPIrimQ064777; Fri, 25 Nov 2005 18:53:44 GMT (envelope-from nobody) Message-Id: <200511251853.jAPIrimQ064777@www.freebsd.org> Date: Fri, 25 Nov 2005 18:53:44 GMT From: "faris@heatandcomfort.com" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89546: GEOM error 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, 25 Nov 2005 19:00:12 -0000 >Number: 89546 >Category: amd64 >Synopsis: GEOM error >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 25 19:00:11 GMT 2005 >Closed-Date: >Last-Modified: >Originator: faris@heatandcomfort.com >Release: 6.0 Amd 64 >Organization: Geom Error >Environment: No out put >Description: As with the problem that I had installing the freebsd 6.0 64 bit. I have went to the command prombt and made the next set hint.atkbd.0.flags=0x8 OK boot -v Started booting goot then got stuck on GEOM : Configure ad0s8, start 11285116416 length 80377403904 end 916625203319 any suggestions ? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 19:46:45 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2608C16A41F for ; Fri, 25 Nov 2005 19:46:45 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-webmail.redshift.com (mail-webmail.redshift.com [216.228.2.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FC5E43D5F for ; Fri, 25 Nov 2005 19:46:44 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 58144 invoked by uid 89); 25 Nov 2005 19:46:43 -0000 Received: by simscan 1.1.0 ppid: 58138, pid: 58140, t: 0.1091s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail-webmail.redshift.com with SMTP; 25 Nov 2005 19:46:43 -0000 Message-Id: <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 25 Nov 2005 11:46:40 -0800 To: Nathan Vidican From: ray@redshift.com In-Reply-To: <43871B20.3050007@wmptl.com> References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 19:46:45 -0000 | I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has been | kicking it almost as long as 5.4-RELEASE has been out. Most of the experiences | I've heard back from other users are saying 6.0, even RC-1 before -RELEASE | actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 will Speaking of First-off: That original message was a private message to me and you from Olaf asking for our opinions on FreeBSD, etc. and it was replied to as such (privately) - in my opinion it's very poor form to suddenly cc everything we are discussing off the list back to the FreeBSD without so much as asking. If you want to start a thread about is FreeBSD 5.4 or 6.0 better for production, that's great. But don't use my private messages to people seeking help to do it. Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 19:56:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EB9D16A41F for ; Fri, 25 Nov 2005 19:56:47 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9213A43D66 for ; Fri, 25 Nov 2005 19:56:43 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 7D488F7C7 for ; Fri, 25 Nov 2005 12:56:42 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 59536F7BB for ; Fri, 25 Nov 2005 12:56:42 -0700 (MST) Date: Fri, 25 Nov 2005 12:56:40 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051125125640.6a0f1e88.kgunders@teamcool.net> In-Reply-To: References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> <4384BBBF.4030007@wmptl.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Sun x2100 Server Compatability 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, 25 Nov 2005 19:56:47 -0000 On Fri, 25 Nov 2005 12:32:21 +0100 (CET) Sten Spans wrote: > On Wed, 23 Nov 2005, Nathan Vidican wrote: > > > Vivek Khera wrote: > >> > >> On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: > >> > >>> Nathan Vidican schrieb: > >>> > >>>> Any known issues running FreeBSD/amd64 on a Sun x2100 server? Single > >>>> opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: > >>> > >>> > >>> The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without PS/2 > >>> mouse and keyboard ports. So you should look at success reports for this > >>> board. > >> > >> > >> > > Same issue here... both NIC's requried, but putting in a good ole Intel/FXP > > card won't bother me in the least. > > The x2100 is listed as only having pci-E expansion options ... > so a regular pci ethernet card wont fit. I was wondering about this myself. The Tyan mobo does sport pci slots though. So I wonder if a PCI-Riser and/or low profile pci cards are supported or whether Sun just was a bit too terse with their tech specs? -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 19:59:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C67716A431 for ; Fri, 25 Nov 2005 19:59:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 275FF43D7E for ; Fri, 25 Nov 2005 19:59:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAPJx51R052759; Fri, 25 Nov 2005 12:59:06 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43876D0E.6080503@samsco.org> Date: Fri, 25 Nov 2005 12:59:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roger Marquis References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> In-Reply-To: <20051119200222.V2029@roble.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 25 Nov 2005 19:59:32 -0000 Roger Marquis wrote: [...] > Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD > or are not mature. Adaptec SCSI RAID is also not as well supported > as some of the SATA RAID cards. What? Is this some sort of troll? Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:10:14 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2210316A41F for ; Fri, 25 Nov 2005 20:10:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4584E43D72 for ; Fri, 25 Nov 2005 20:10:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPKA9ID031449 for ; Fri, 25 Nov 2005 20:10:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPKA9j7031448; Fri, 25 Nov 2005 20:10:09 GMT (envelope-from gnats) Resent-Date: Fri, 25 Nov 2005 20:10:09 GMT Resent-Message-Id: <200511252010.jAPKA9j7031448@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, Aaron Wallace Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FF2616A420 for ; Fri, 25 Nov 2005 20:05:53 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7416643D6D for ; Fri, 25 Nov 2005 20:05:52 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAPK5q8h097802 for ; Fri, 25 Nov 2005 20:05:52 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAPK5qTo097801; Fri, 25 Nov 2005 20:05:52 GMT (envelope-from nobody) Message-Id: <200511252005.jAPK5qTo097801@www.freebsd.org> Date: Fri, 25 Nov 2005 20:05:52 GMT From: Aaron Wallace To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89549: [amd64] nve timeouts on 6.0-release 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, 25 Nov 2005 20:10:14 -0000 >Number: 89549 >Category: amd64 >Synopsis: [amd64] nve timeouts on 6.0-release >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 25 20:10:08 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Aaron Wallace >Release: 6.0 Release >Organization: n/a >Environment: >Description: Nvidia nforce4 ethernet controller (nve) gets timeouts during attempts to use ethernet. I can't use the ethernet controller at all. dmesg output follows: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2120.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) avail memory = 1025216512 (977 MB) cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 pcib1: at device 9.0 on pci0 pci1: on pcib1 pci1: at device 7.0 (no driver attached) pci1: at device 7.1 (no driver attached) sym0: <1010-33> port 0xc400-0xc4ff mem 0xfeaff000-0xfeaff3ff,0xfeafc000-0xfeafdfff irq 10 at device 8.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCAN AT BOOT disabled for targets 1 2 4 5 8 9 10 11 12 13 14 15. sym0: SCAN FOR LUNS disabled for targets 0 3 6. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0xc000-0xc0ff mem 0xfeafe000-0xfeafe3ff,0xfeafa000-0xfeafbfff irq 11 at device 8.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: SCAN AT BOOT disabled for targets 1 2 3 4 5 6 8 9 10 11 12 13 14 15. sym1: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15. sym1: [GIANT-LOCKED] sym2: <810a> port 0xbc00-0xbcff mem 0xfe9ff000-0xfe9ff0ff irq 12 at device 10.0 on pci1 sym2: No NVRAM, ID 7, Fast-10, SE, parity checking sym2: [GIANT-LOCKED] nve0: port 0xdc00-0xdc07 mem 0xfebfb000-0xfebfbfff irq 10 at device 10.0 on pci0 nve0: Ethernet address 00:50:70:56:4b:68 miibus0: on nve0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:50:70:56:4b:68 nve0: [GIANT-LOCKED] pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 pcib5: at device 14.0 on pci0 pci5: on pcib5 pci5: at device 0.0 (no driver attached) orm0: at iomem 0xc0000-0xcefff,0xd0000-0xd17ff,0xd2000-0xd5fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2120029028 Hz quality 800 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. acd0: DVDR at ata0-slave UDMA33 (probe32:sym2:0:2:0): phase change 6-7 6@3db87198 resid=4. pass4 at sym2 bus 0 target 2 lun 0 pass4: Fixed Processor SCSI-2 device pass4: 3.300MB/s transfers da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 31, 16bit) da0: 34732MB (71132000 512 byte sectors: 255H 63S/T 4427C) da1 at sym0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) da1: 17510MB (35860910 512 byte sectors: 255H 63S/T 2232C) da2 at sym0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) cd0 at sym1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/da1s1a nve0: link state changed to UP nve0: device timeout (1) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (2) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (3) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (4) nve0: link state changed to DOWN nve0: link state changed to UP >How-To-Repeat: Occurs on any attempt to use nve. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:12:09 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C267016A41F for ; Fri, 25 Nov 2005 20:12:09 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail5.redshift.com (mail5.redshift.com [216.228.2.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F87543D64 for ; Fri, 25 Nov 2005 20:12:03 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 28623 invoked by uid 89); 25 Nov 2005 20:11:59 -0000 Received: by simscan 1.2.0 ppid: 28617, pid: 28620, t: 0.2312s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail5.redshift.com with SMTP; 25 Nov 2005 20:11:59 -0000 Message-Id: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 25 Nov 2005 12:11:59 -0800 To: Nathan Vidican From: ray@redshift.com In-Reply-To: <43871B20.3050007@wmptl.com> References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 20:12:10 -0000 | > My policy is to never be the first kid on the block to test something new - | > especially not in production. FreeBSD 5.4 has been hammered on for a long time | > and works really well. 5.4 is an evolution of 5.2.1 and 5.3 - all of which are | > very mature and very stable. I've been running FreeBSD in production since | > version 5.2.1 and have been using FreeBSD since 4.9 (previously we used Redhat | > linux for our production servers). Anyway, when I build a machine, here is | > exactly what I use: | > | | I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has been | kicking it almost as long as 5.4-RELEASE has been out. Most of the experiences | I've heard back from other users are saying 6.0, even RC-1 before -RELEASE | actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 will | help you out, (eg filesystem changes, SMP support, hardware drivers, etc). | Considering the newer hardware you've chosen (dual core amd64 cpu) - 6.0 is much | better prepared to handle it in the kernel. I've been running 6.0-RC1 on one of | the dual opterons we have here now for a couple of months now - performance is | great and havn't had a moments downtime yet. Seriously, do not discount 6.0 | because it's a '.0' release, really it's not. As Ray pointed out, 5.4 was an | evolution of 5.2 - 5.3, etc... what he did not potentially realize, is that 6.0 | is of that same evolution. Read the notes as to why the version skipped from 5.4 | -> 6.0, and you'll realize that 6.0 was simply a new version number to a release | that would have otherwise been say 5.5, the reason for the skip was because of | the large number of new capbilities and features. And yes, new features generall | can equal new bugs - but if you're not relying upon them and you're doing the | same thing you would with a 5.4 machine, then why sacrafice the added filesystem | performance and hardware support by not running 6.0? Can you provide some specific benchmarks you have run comparing 5.4 to 6.0? I've heard too many people, too many times, pull stats out of the air regarding "the new release". If you have done some specific testing to show that 5.4 is slow than 6.0 - then great. But if you are just going by the seat of your pants, then I think it can be dangerous to assume a new version if faster. In the case of FreeBSD 6.0, it may very well be the case, but I personally have no tested it in production. In cases of things like PHP5 vs. PHP4, 4 is clearly faster. Same for apache. 2.0.52, based on my testing, is clearly slower compared to 1.3.33. If you have stats showing the different between 5.x and 6.x in areas such as disk I/O, CPU load, etc., I for one would appreciate seeing some hard numbers. So far, I haven't had a chance to run any and I'm certainly interested in version 6.0 However, as a system admin for close to 25 years, I still stick by my guns that immediately jumping to the latest release for use in a production machine can be quite risky. If you are just playing around at home, that's one thing. But if 5x9+ uptime is critical, then it's a whole different story. | I agree, short of large security patches, stick with a -RELEASE code. In any | given production environment stability is key. While cvsup'ing and building the | new box everyday to stay current sounds good - it is in practice not good for | production servers - if it isn't broke, don't fix it. Agreed. CVS is great for getting the latest code to test, but I've seen friend constantly doing CVS's and build worlds on servers in production only to have them exhibit strange behavior until the next patch comes out. In fact, not too long ago a buddy of mine updated a machine and ended up having to roll back the OS to a previous version in order to cure some strange crashing problem (which later went away a few patches down the road). | As Olaf pointed out many times in this thread (or related threads) - budget is | key with this deal, so I doubt load balancing and plopping another machine in is | an option his client really wants to hear about - until they've gotten to a | point to justify doing so. Why scare customers away telling them they can buy | more, if you just sold them something new why isn't it going to be good enough - | guarantee that's not a question you'll want to provoke. I haven't seen Olaf's P/L for the year, so I can't really comment. All I can say is some people build clusters some don't :) For those that do, load balancing is a much more viable option in a lot of cases than trying to squeeze every last ounce of performance from a machine. I've been woken up too many times between 1995 and 1999 with machines dead to the world because we tried to tweak every last red cent out of them (running Linux) to do it any more. As far as my opinion on it, in the long run, it's money ahead if you have redundancy, even if the initial jump into it is a little more costly than you want. | Same response. Look at the SMP file, it's basically "options smp; include | GENERIC"... just copy the GENERIC to your own config, remove the driver(s) you | don't require, add 'options SMP' and any other options you may wish - rename the | config and go from there. When I first moved from i386 to AMD64, that one tripped me up but good! :) I was so used to just editing GENERIC, I didn't even look at SMP or realize it was there for about 3 days. | The ports collection has been optimized for 'the average install', leveraging | performance for functionality in most situations to be ideal. The ports usually | have added patches or adjustments to code which integrates them better with | FreeBSD, if you're not all that familair with the code you're working with, (in | this case mysql), then I'd reccomend you stick with the ports collection. | However, that being said - note that the ports collection isn't always up to | date, and you may want a differing version of mysql. Follow the documentation on | mysql.com and you should be just fine - fairly staght forward install and | differs little from doing so via the FreeBSD ports collection. In any production | system though, I highly reccomend compiling from source vs downloading binaries | - that way nothing has been linked to/from librairies which may or may not be | the same on your system. Agreed. | I agree, stick with 4.1.x, but for different reasons. Compatability; not sure | what you are doing, the size or scope of the database you're dealing with, but | if for example you're going to be writting and app in windows which uses the | myodbc driver to connect... then you may run into problems with newer versions | of mysql. I encountered a LOT of this, when we moved from 3.x up to 4.1, largely | because of changes in the client - at least I was aware of that before I | started, but I did have to rebuild client librairies on all webservers, and | re-install odbc drivers on client machines throughout the building because of | it. Might not be something you're willing/ready to undertake for the features | you've already mentioned not being required in mysql 5. Couldn't comment on using the Win API to connect directly to MySQL, but it doesn't sound fun! :) Are you using VC++ to do it or MFC or ? If you have any sample code for that, I'd be interested in seeing it (off list). Anyway, hopefully Olaf doesn't hang himself over there after reading our messages. I think he's on a pretty good track to a nice server from what I've read so far. I still am not a fan of jumping to the latest 'anything' as far as production machines go. Yes, it may work, but I've been burned too many times in the past doing that. If it's not a production environment, then that's a totally different story, but for anything business related or HA, it's usually a risk to be the first ones running something fresh off hacking-room-floor :) Anyway, have a good weekend. Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:23:02 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AB9A16A420 for ; Fri, 25 Nov 2005 20:23:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C101043D60 for ; Fri, 25 Nov 2005 20:23:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAPKMxHM052925; Fri, 25 Nov 2005 13:22:59 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438772A7.2060903@samsco.org> Date: Fri, 25 Nov 2005 13:23:03 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 20:23:02 -0000 ray@redshift.com wrote: > | > My policy is to never be the first kid on the block to test something new - > | > especially not in production. FreeBSD 5.4 has been hammered on for a long time > | > and works really well. 5.4 is an evolution of 5.2.1 and 5.3 - all of which are > | > very mature and very stable. I've been running FreeBSD in production since > | > version 5.2.1 and have been using FreeBSD since 4.9 (previously we used Redhat > | > linux for our production servers). Anyway, when I build a machine, here is > | > exactly what I use: > | > > | > | I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has been > | kicking it almost as long as 5.4-RELEASE has been out. Most of the experiences > | I've heard back from other users are saying 6.0, even RC-1 before -RELEASE > | actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 will > | help you out, (eg filesystem changes, SMP support, hardware drivers, etc). > | Considering the newer hardware you've chosen (dual core amd64 cpu) - 6.0 is much > | better prepared to handle it in the kernel. I've been running 6.0-RC1 on one of > | the dual opterons we have here now for a couple of months now - performance is > | great and havn't had a moments downtime yet. Seriously, do not discount 6.0 > | because it's a '.0' release, really it's not. As Ray pointed out, 5.4 was an > | evolution of 5.2 - 5.3, etc... what he did not potentially realize, is that 6.0 > | is of that same evolution. Read the notes as to why the version skipped from 5.4 > | -> 6.0, and you'll realize that 6.0 was simply a new version number to a release > | that would have otherwise been say 5.5, the reason for the skip was because of > | the large number of new capbilities and features. And yes, new features generall > | can equal new bugs - but if you're not relying upon them and you're doing the > | same thing you would with a 5.4 machine, then why sacrafice the added filesystem > | performance and hardware support by not running 6.0? > > Can you provide some specific benchmarks you have run comparing 5.4 to 6.0? > I've heard too many people, too many times, pull stats out of the air regarding > "the new release". If you have done some specific testing to show that 5.4 is > slow than 6.0 - then great. A benchmark paper is being written right now that shows that for i/o, FreeBSD 6.0 is universally faster and scales better than 5.4. Watch for it to be released fairly soon. It's fine to doubt conventional wisdom, but you too should back up what you're saying. Otherwise, it just amounts to FUD. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:31:34 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9554016A41F for ; Fri, 25 Nov 2005 20:31:34 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail4.redshift.com (mail4.redshift.com [216.228.2.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 082CC43D76 for ; Fri, 25 Nov 2005 20:31:32 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 81681 invoked by uid 89); 25 Nov 2005 20:31:32 -0000 Received: by simscan 1.1.0 ppid: 81676, pid: 81678, t: 0.1122s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail4.redshift.com with SMTP; 25 Nov 2005 20:31:32 -0000 Message-Id: <3.0.1.32.20051125123128.00a61c88@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 25 Nov 2005 12:31:28 -0800 To: Scott Long From: ray@redshift.com In-Reply-To: <438772A7.2060903@samsco.org> References: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: ogreve@millennics.com, amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 20:31:34 -0000 | A benchmark paper is being written right now that shows that for i/o, | FreeBSD 6.0 is universally faster and scales better than 5.4. Watch for | it to be released fairly soon. | | It's fine to doubt conventional wisdom, but you too should back up what | you're saying. Otherwise, it just amounts to FUD. | | Scott Thanks Scott, I'll be interested in seeing it. As far as FUD, like I said before, I'll stick to my guns about not putting the absolute newest OS (or anything else) into production use the second it is released. I know orgs like FreeBSD do a huge amount of testing and I'm constantly impressed by FreeBSD, but I still am very hesitant to rush right into something new. If you want to call that fear, okay. I personally call it caution :) Ray From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:40:08 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69F5F16A41F for ; Fri, 25 Nov 2005 20:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F50343D68 for ; Fri, 25 Nov 2005 20:40:03 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPKe3Vd033541 for ; Fri, 25 Nov 2005 20:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPKe3MG033540; Fri, 25 Nov 2005 20:40:03 GMT (envelope-from gnats) Resent-Date: Fri, 25 Nov 2005 20:40:03 GMT Resent-Message-Id: <200511252040.jAPKe3MG033540@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, Aaron Wallace Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1125116A41F for ; Fri, 25 Nov 2005 20:36:35 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D4143D5F for ; Fri, 25 Nov 2005 20:36:34 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jAPKaYYS005606 for ; Fri, 25 Nov 2005 20:36:34 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jAPKaYKL005605; Fri, 25 Nov 2005 20:36:34 GMT (envelope-from nobody) Message-Id: <200511252036.jAPKaYKL005605@www.freebsd.org> Date: Fri, 25 Nov 2005 20:36:34 GMT From: Aaron Wallace To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) 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, 25 Nov 2005 20:40:08 -0000 >Number: 89550 >Category: amd64 >Synopsis: [amd64] sym0: VTOBUS failed (6.0 Release) >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 25 20:40:02 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Aaron Wallace >Release: 6.0 Release >Organization: n/a >Environment: >Description: Ever since I switched to amd64, I have been having problems with my symbios / lsi logic 21010 scsi card. I tried it initially on an nforce2 chipset, and was getting this error message: panic: sym0 : VTOBUS FAILED! About a year ago someone was helping address the problem, and I thought that a patch he had made (6.0-current at the time) had corrected the problem. I think maybe this was just a matter of luck though, because now the problem seems to have resurfaced, this time on an nforce4 chipset. dmesg output follows: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2120.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) avail memory = 1025216512 (977 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: on acpi0 pci_link5: irq 10 on acpi0 pci_link6: on acpi0 pci_link7: irq 5 on acpi0 pci_link8: irq 11 on acpi0 pci_link9: on acpi0 pci_link10: irq 5 on acpi0 pci_link11: irq 11 on acpi0 pci_link12: on acpi0 pci_link13: on acpi0 pci_link14: on acpi0 pci_link15: on acpi0 pci_link16: irq 0 on acpi0 pci_link17: irq 0 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 16 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 0 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 0 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link26: BIOS IRQ 5 for -2145774616.1.INTA is invalid pci_link21: BIOS IRQ 10 for -2145774616.2.INTA is invalid pci_link27: BIOS IRQ 11 for -2145774616.2.INTB is invalid pci_link23: BIOS IRQ 5 for -2145774616.10.INTA is invalid pci_link24: BIOS IRQ 11 for -2145774616.4.INTA is invalid pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebff000-0xfebfffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfebfe000-0xfebfe0ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 pcib1: at device 9.0 on pci0 pci_link18: BIOS IRQ 21 for 0.10.INTA is invalid pci1: on pcib1 pci1: at device 7.0 (no driver attached) pci1: at device 7.1 (no driver attached) sym0: <1010-33> port 0xc400-0xc4ff mem 0xfeaff000-0xfeaff3ff,0xfeafc000-0xfeafdfff irq 16 at device 8.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCAN AT BOOT disabled for targets 1 2 4 5 8 9 10 11 12 13 14 15. sym0: SCAN FOR LUNS disabled for targets 0 3 6. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0xc000-0xc0ff mem 0xfeafe000-0xfeafe3ff,0xfeafa000-0xfeafbfff irq 17 at device 8.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: SCAN AT BOOT disabled for targets 1 2 3 4 5 6 8 9 10 11 12 13 14 15. sym1: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15. sym1: [GIANT-LOCKED] sym2: <810a> port 0xbc00-0xbcff mem 0xfe9ff000-0xfe9ff0ff irq 18 at device 10.0 on pci1 sym2: No NVRAM, ID 7, Fast-10, SE, parity checking sym2: [GIANT-LOCKED] nve0: port 0xdc00-0xdc07 mem 0xfebfb000-0xfebfbfff irq 21 at device 10.0 on pci0 nve0: Ethernet address 00:50:70:56:4b:68 miibus0: on nve0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:50:70:56:4b:68 nve0: [GIANT-LOCKED] pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 pcib5: at device 14.0 on pci0 pci5: on pcib5 pci5: at device 0.0 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xcefff,0xd0000-0xd3fff,0xd4000-0xd57ff,0xd6000-0xd9fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: Logitech USB Mouse, rev 1.10/6.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. umass0: Generic USB Storage Device, rev 1.10/30.0a, addr 3 Timecounter "TSC" frequency 2120029086 Hz quality 800 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. acd0: DVDR at ata0-slave UDMA33 (probe32:sym2:0:2:0): phase change 6-7 6@3db89198 resid=4. pass4 at sym2 bus 0 target 2 lun 0 pass4: Fixed Processor SCSI-2 device pass4: 3.300MB/s transfers da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 31, 16bit) da0: 34732MB (71132000 512 byte sectors: 255H 63S/T 4427C) da1 at sym0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) da1: 17510MB (35860910 512 byte sectors: 255H 63S/T 2232C) da2 at sym0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) cd0 at sym1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 0 da3: Removable Direct Access SCSI-0 device da3: 1.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da4 at umass-sim0 bus 0 target 0 lun 1 da4: Removable Direct Access SCSI-0 device da4: 1.000MB/s transfers da4: Attempt to query device size failed: NOT READY, Medium not present da5 at umass-sim0 bus 0 target 0 lun 2 da5: Removable Direct Access SCSI-0 device da5: 1.000MB/s transfers da5: Attempt to query device size failed: NOT READY, Medium not present da6 at umass-sim0 bus 0 target 0 lun 3 da6: Removable Direct Access SCSI-0 device da6: 1.000MB/s transfers da6: Attempt to query device size failed: NOT READY, Medium not present (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error Opened disk da3 -> 6 (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:1): SCSI Status: Check Condition (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 (da4:umass-sim0:0:0:1): Medium not present (da4:umass-sim0:0:0:1): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:1): SCSI Status: Check Condition (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 (da4:umass-sim0:0:0:1): Medium not present (da4:umass-sim0:0:0:1): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:1): SCSI Status: Check Condition (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 (da4:umass-sim0:0:0:1): Medium not present (da4:umass-sim0:0:0:1): Unretryable error Opened disk da4 -> 6 (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:2): SCSI Status: Check Condition (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 (da5:umass-sim0:0:0:2): Medium not present (da5:umass-sim0:0:0:2): Unretryable error Opened disk da5 -> 6 (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:2): SCSI Status: Check Condition (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 (da5:umass-sim0:0:0:2): Medium not present (da5:umass-sim0:0:0:2): Unretryable error Opened disk da5 -> 6 (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:2): SCSI Status: Check Condition (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 (da5:umass-sim0:0:0:2): Medium not present (da5:umass-sim0:0:0:2): Unretryable error Opened disk da5 -> 6 (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:3): SCSI Status: Check Condition (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 (da6:umass-sim0:0:0:3): Medium not present (da6:umass-sim0:0:0:3): Unretryable error Opened disk da6 -> 6 (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:3): SCSI Status: Check Condition (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 (da6:umass-sim0:0:0:3): Medium not present (da6:umass-sim0:0:0:3): Unretryable error Opened disk da6 -> 6 (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:3): SCSI Status: Check Condition (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 (da6:umass-sim0:0:0:3): Medium not present (da6:umass-sim0:0:0:3): Unretryable error Opened disk da6 -> 6 Trying to mount root from ufs:/dev/da1s1a Typically, I will either get the message immediately after detection of the sym0 <1010> chip or after acd0 (following scsi bus reset). Of course at either of these points the boot sequence halts and it gives me 15 seconds to reboot. >How-To-Repeat: I've tried several combinations of enabling/disabling various motherboard components, but haven't found the exact recipe to repeat the problem consistently. There is clearly some randomness to the problem because I can boot twice in a row with the same settings and it will work one time and not the other. Some factors that seem to have some influence on the problem are the enabling/disabling of the onboard USB in BIOS and perhaps whether or not I enable or disable ACPI on the boot menu (you can see there are some issues with acpi from dmesg, but I can't tell if this is because of the symbios card or not). When I first booted up with the installation cdrom, I had to disable the onboard USB controller to get it to the install menu - this seemed to work consistently. Then once I started booting up from the hard drive, disabling the onboard USB didn't help. I re-enabled onboard USB and tried it again with ACPI disabled from the boot menu and it failed again. I rebooted one more time with USB enabled and ACPI enabled and it worked - the very same scenario in which it failed immediately after installation. >Fix: So far I don't have a fix to the problem, but would be willing to try any suggestions or patches. I should note here also that my nvidia ethernet controller (nve) isn't working at the moment either, so no networking available atm either. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:50:15 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97CE716A422 for ; Fri, 25 Nov 2005 20:50:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0267143D6E for ; Fri, 25 Nov 2005 20:50:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAPKo6jF033947 for ; Fri, 25 Nov 2005 20:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAPKo67C033946; Fri, 25 Nov 2005 20:50:06 GMT (envelope-from gnats) Date: Fri, 25 Nov 2005 20:50:06 GMT Message-Id: <200511252050.jAPKo67C033946@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Scott Long Cc: Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scott Long List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 20:50:15 -0000 The following reply was made to PR amd64/89550; it has been noted by GNATS. From: Scott Long To: Aaron Wallace Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/89550: [amd64] sym0: VTOBUS failed (6.0 Release) Date: Fri, 25 Nov 2005 13:43:15 -0700 Aaron Wallace wrote: >>Number: 89550 >>Category: amd64 >>Synopsis: [amd64] sym0: VTOBUS failed (6.0 Release) >>Confidential: no >>Severity: serious >>Priority: medium >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Fri Nov 25 20:40:02 GMT 2005 >>Closed-Date: >>Last-Modified: >>Originator: Aaron Wallace >>Release: 6.0 Release >>Organization: > > n/a > >>Environment: >>Description: > > Ever since I switched to amd64, I have been having problems with my symbios / lsi logic 21010 scsi card. I tried it initially on an nforce2 chipset, and was getting this error message: > > panic: sym0 : VTOBUS FAILED! > > About a year ago someone was helping address the problem, and I thought that a patch he had made (6.0-current at the time) had corrected the problem. I think maybe this was just a matter of luck though, because now the problem seems to have resurfaced, this time on an nforce4 chipset. > > dmesg output follows: > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 > root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 Processor 3200+ (2120.03-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 > Features=0x78bfbff > Features2=0x1 > AMD Features=0xe2500800,LM,3DNow+,3DNow> > real memory = 1073676288 (1023 MB) > avail memory = 1025216512 (977 MB) > ioapic0 irqs 0-23 on motherboard > acpi0: on motherboard > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > acpi0: Power Button (fixed) > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > pci_link0: irq 10 on acpi0 > pci_link1: irq 11 on acpi0 > pci_link2: irq 5 on acpi0 > pci_link3: irq 10 on acpi0 > pci_link4: on acpi0 > pci_link5: irq 10 on acpi0 > pci_link6: on acpi0 > pci_link7: irq 5 on acpi0 > pci_link8: irq 11 on acpi0 > pci_link9: on acpi0 > pci_link10: irq 5 on acpi0 > pci_link11: irq 11 on acpi0 > pci_link12: on acpi0 > pci_link13: on acpi0 > pci_link14: on acpi0 > pci_link15: on acpi0 > pci_link16: irq 0 on acpi0 > pci_link17: irq 0 on acpi0 > pci_link18: irq 0 on acpi0 > pci_link19: irq 0 on acpi0 > pci_link20: irq 16 on acpi0 > pci_link21: irq 0 on acpi0 > pci_link22: irq 0 on acpi0 > pci_link23: irq 0 on acpi0 > pci_link24: irq 0 on acpi0 > pci_link25: irq 0 on acpi0 > pci_link26: irq 0 on acpi0 > pci_link27: irq 0 on acpi0 > pci_link28: irq 0 on acpi0 > pci_link29: irq 0 on acpi0 > pci_link30: irq 0 on acpi0 > pci_link31: irq 0 on acpi0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci_link26: BIOS IRQ 5 for -2145774616.1.INTA is invalid > pci_link21: BIOS IRQ 10 for -2145774616.2.INTA is invalid > pci_link27: BIOS IRQ 11 for -2145774616.2.INTB is invalid > pci_link23: BIOS IRQ 5 for -2145774616.10.INTA is invalid > pci_link24: BIOS IRQ 11 for -2145774616.4.INTA is invalid > pci0: on pcib0 > pci0: at device 0.0 (no driver attached) > isab0: at device 1.0 on pci0 > isa0: on isab0 > pci0: at device 1.1 (no driver attached) > ohci0: mem 0xfebff000-0xfebfffff irq 21 at device 2.0 on pci0 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 10 ports with 10 removable, self powered > ehci0: mem 0xfebfe000-0xfebfe0ff irq 22 at device 2.1 on pci0 > ehci0: [GIANT-LOCKED] > usb1: EHCI version 1.0 > usb1: companion controller, 4 ports each: usb0 > usb1: on ehci0 > usb1: USB revision 2.0 > uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub1: 10 ports with 10 removable, self powered > pci0: at device 4.0 (no driver attached) > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 > ata0: on atapci0 > ata1: on atapci0 > pcib1: at device 9.0 on pci0 > pci_link18: BIOS IRQ 21 for 0.10.INTA is invalid > pci1: on pcib1 > pci1: at device 7.0 (no driver attached) > pci1: at device 7.1 (no driver attached) > sym0: <1010-33> port 0xc400-0xc4ff mem 0xfeaff000-0xfeaff3ff,0xfeafc000-0xfeafdfff irq 16 at device 8.0 on pci1 > sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: handling phase mismatch from SCRIPTS. > sym0: SCAN AT BOOT disabled for targets 1 2 4 5 8 9 10 11 12 13 14 15. > sym0: SCAN FOR LUNS disabled for targets 0 3 6. > sym0: [GIANT-LOCKED] > sym1: <1010-33> port 0xc000-0xc0ff mem 0xfeafe000-0xfeafe3ff,0xfeafa000-0xfeafbfff irq 17 at device 8.1 on pci1 > sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > sym1: handling phase mismatch from SCRIPTS. > sym1: SCAN AT BOOT disabled for targets 1 2 3 4 5 6 8 9 10 11 12 13 14 15. > sym1: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15. > sym1: [GIANT-LOCKED] > sym2: <810a> port 0xbc00-0xbcff mem 0xfe9ff000-0xfe9ff0ff irq 18 at device 10.0 on pci1 > sym2: No NVRAM, ID 7, Fast-10, SE, parity checking > sym2: [GIANT-LOCKED] > nve0: port 0xdc00-0xdc07 mem 0xfebfb000-0xfebfbfff irq 21 at device 10.0 on pci0 > nve0: Ethernet address 00:50:70:56:4b:68 > miibus0: on nve0 > ciphy0: on miibus0 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > nve0: Ethernet address: 00:50:70:56:4b:68 > nve0: [GIANT-LOCKED] > pcib2: at device 11.0 on pci0 > pci2: on pcib2 > pcib3: at device 12.0 on pci0 > pci3: on pcib3 > pcib4: at device 13.0 on pci0 > pci4: on pcib4 > pcib5: at device 14.0 on pci0 > pci5: on pcib5 > pci5: at device 0.0 (no driver attached) > acpi_tz0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > orm0: at iomem 0xc0000-0xcefff,0xd0000-0xd3fff,0xd4000-0xd57ff,0xd6000-0xd9fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: Logitech USB Mouse, rev 1.10/6.10, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > umass0: Generic USB Storage Device, rev 1.10/30.0a, addr 3 > Timecounter "TSC" frequency 2120029086 Hz quality 800 > Timecounters tick every 1.000 msec > Waiting 5 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. > acd0: DVDR at ata0-slave UDMA33 > (probe32:sym2:0:2:0): phase change 6-7 6@3db89198 resid=4. > pass4 at sym2 bus 0 target 2 lun 0 > pass4: Fixed Processor SCSI-2 device > pass4: 3.300MB/s transfers > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 160.000MB/s transfers (80.000MHz, offset 31, 16bit) > da0: 34732MB (71132000 512 byte sectors: 255H 63S/T 4427C) > da1 at sym0 bus 0 target 3 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) > da1: 17510MB (35860910 512 byte sectors: 255H 63S/T 2232C) > da2 at sym0 bus 0 target 6 lun 0 > da2: Fixed Direct Access SCSI-3 device > da2: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) > da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) > cd0 at sym1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 0 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > da4 at umass-sim0 bus 0 target 0 lun 1 > da4: Removable Direct Access SCSI-0 device > da4: 1.000MB/s transfers > da4: Attempt to query device size failed: NOT READY, Medium not present > da5 at umass-sim0 bus 0 target 0 lun 2 > da5: Removable Direct Access SCSI-0 device > da5: 1.000MB/s transfers > da5: Attempt to query device size failed: NOT READY, Medium not present > da6 at umass-sim0 bus 0 target 0 lun 3 > da6: Removable Direct Access SCSI-0 device > da6: 1.000MB/s transfers > da6: Attempt to query device size failed: NOT READY, Medium not present > (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da3:umass-sim0:0:0:0): SCSI Status: Check Condition > (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 > (da3:umass-sim0:0:0:0): Medium not present > (da3:umass-sim0:0:0:0): Unretryable error > Opened disk da3 -> 6 > (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da3:umass-sim0:0:0:0): SCSI Status: Check Condition > (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 > (da3:umass-sim0:0:0:0): Medium not present > (da3:umass-sim0:0:0:0): Unretryable error > Opened disk da3 -> 6 > (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da3:umass-sim0:0:0:0): SCSI Status: Check Condition > (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 > (da3:umass-sim0:0:0:0): Medium not present > (da3:umass-sim0:0:0:0): Unretryable error > Opened disk da3 -> 6 > (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 > (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error > (da4:umass-sim0:0:0:1): SCSI Status: Check Condition > (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 > (da4:umass-sim0:0:0:1): Medium not present > (da4:umass-sim0:0:0:1): Unretryable error > Opened disk da4 -> 6 > (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 > (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error > (da4:umass-sim0:0:0:1): SCSI Status: Check Condition > (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 > (da4:umass-sim0:0:0:1): Medium not present > (da4:umass-sim0:0:0:1): Unretryable error > Opened disk da4 -> 6 > (da4:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 > (da4:umass-sim0:0:0:1): CAM Status: SCSI Status Error > (da4:umass-sim0:0:0:1): SCSI Status: Check Condition > (da4:umass-sim0:0:0:1): NOT READY asc:3a,0 > (da4:umass-sim0:0:0:1): Medium not present > (da4:umass-sim0:0:0:1): Unretryable error > Opened disk da4 -> 6 > (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 > (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error > (da5:umass-sim0:0:0:2): SCSI Status: Check Condition > (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 > (da5:umass-sim0:0:0:2): Medium not present > (da5:umass-sim0:0:0:2): Unretryable error > Opened disk da5 -> 6 > (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 > (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error > (da5:umass-sim0:0:0:2): SCSI Status: Check Condition > (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 > (da5:umass-sim0:0:0:2): Medium not present > (da5:umass-sim0:0:0:2): Unretryable error > Opened disk da5 -> 6 > (da5:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 > (da5:umass-sim0:0:0:2): CAM Status: SCSI Status Error > (da5:umass-sim0:0:0:2): SCSI Status: Check Condition > (da5:umass-sim0:0:0:2): NOT READY asc:3a,0 > (da5:umass-sim0:0:0:2): Medium not present > (da5:umass-sim0:0:0:2): Unretryable error > Opened disk da5 -> 6 > (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 > (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error > (da6:umass-sim0:0:0:3): SCSI Status: Check Condition > (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 > (da6:umass-sim0:0:0:3): Medium not present > (da6:umass-sim0:0:0:3): Unretryable error > Opened disk da6 -> 6 > (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 > (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error > (da6:umass-sim0:0:0:3): SCSI Status: Check Condition > (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 > (da6:umass-sim0:0:0:3): Medium not present > (da6:umass-sim0:0:0:3): Unretryable error > Opened disk da6 -> 6 > (da6:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 > (da6:umass-sim0:0:0:3): CAM Status: SCSI Status Error > (da6:umass-sim0:0:0:3): SCSI Status: Check Condition > (da6:umass-sim0:0:0:3): NOT READY asc:3a,0 > (da6:umass-sim0:0:0:3): Medium not present > (da6:umass-sim0:0:0:3): Unretryable error > Opened disk da6 -> 6 > Trying to mount root from ufs:/dev/da1s1a > > Typically, I will either get the message immediately after detection of the sym0 <1010> chip or after acd0 (following scsi bus reset). Of course at either of these points the boot sequence halts and it gives me 15 seconds to reboot. > >>How-To-Repeat: > > I've tried several combinations of enabling/disabling various motherboard components, but haven't found the exact recipe to repeat the problem consistently. There is clearly some randomness to the problem because I can boot twice in a row with the same settings and it will work one time and not the other. Some factors that seem to have some influence on the problem are the enabling/disabling of the onboard USB in BIOS and perhaps whether or not I enable or disable ACPI on the boot menu (you can see the re are some issues with acpi from dmesg, but I can't tell if this is because of the symbios card or not). When I first booted up with the installation cdrom, I had to disable the onboard USB controller to get it to the install menu - this seemed to work consistently. Then once I started booting up from the hard drive, disabling the onboard USB didn't help. I re-enabled onboard USB and tried it again with ACPI disabled from the boot menu and it failed again. I rebooted on e > more time with USB enabled and ACPI enabled and it worked - the very same scenario in which it failed immediately after installation. > >>Fix: > > So far I don't have a fix to the problem, but would be willing to try any suggestions or patches. I should note here also that my nvidia ethernet controller (nve) isn't working at the moment either, so no networking available atm either. > >>Release-Note: >>Audit-Trail: >>Unformatted: > I'm already working on fixing this. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 20:52:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B790716A41F for ; Fri, 25 Nov 2005 20:52:08 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBC0443D4C for ; Fri, 25 Nov 2005 20:51:54 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id C01BAF7C7 for ; Fri, 25 Nov 2005 13:51:49 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 8387EF7BB for ; Fri, 25 Nov 2005 13:51:49 -0700 (MST) Date: Fri, 25 Nov 2005 13:51:48 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051125135148.053d2c80.kgunders@teamcool.net> In-Reply-To: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 25 Nov 2005 20:52:08 -0000 On Fri, 25 Nov 2005 12:11:59 -0800 ray@redshift.com wrote: > | > My policy is to never be the first kid on the block to test something new - > | > especially not in production. FreeBSD 5.4 has been hammered on for a long time [snip] > tested it in production. In cases of things like PHP5 vs. PHP4, 4 is clearly > faster. Same for apache. 2.0.52, based on my testing, is clearly slower I have run across published benchmarks concluding php5 is indeed faster than php4. I've not, however, run across published benchies to the contrary. Not saying they're not out there, nor speaking for the validity of those I have seen, but just pointing out that benchmarks can be misleading, confusing, etc. and of limited use unless you happen to run across one that mimicks your config, or you do them yourself. A couple things that have me leaning toward php5 on a new server are: 1) php5.1 was just released. IIRC, 5.1 was to have Rasmus's blessing as "stable" for the php5 line. 2) php developers (and dev heads in general) are more interested in working on the new, latest stuff than maintaining older releases. Thus, although php5 is newer and likely to have more issues than php4 it may well see superior support in upcoming years from the php team. Witness the php4.4.1/Apache2/mod_rewrite issue. 3) It's one less migration you have to deal w/a year from now when the phb decides they want to run some new killer app that requires the php5... Caveat- given the security history of php I wouldn't use a x.0 release for anything other than playing around. Things usually seem to settle down by an x.1 release though. > compared to 1.3.33. If you have stats showing the different between 5.x and 6.x Regarding Apache- I've taken to running my php stuff via FastCGI under Lighttpd as unprivileged user on high port and then proxying via Apache2. (Some of caching stuff comes in handy. Granted Squid is a better choice for serious use. ) This config pretty much screams performance wise. For various reasons discussed a while back on another thread, best webserver perf is seen under FBSD-i386. The AMD64 stuff absolutely rocks when you get into larger db's needing more ram, etc. Running php under FastCGI also sets you up for inexpensive load balancing solution. Just throw relatively inexpensive single cpu, sata based machines in front of the db server. Anyhow, just throwing this out for what it might be worth. If you've not checked out "Lighty" before you may want to take a gander: Here's the FastCGI stuff: [snip] > | I agree, stick with 4.1.x, but for different reasons. Compatability; not sure > | what you are doing, the size or scope of the database you're dealing with, but > | if for example you're going to be writting and app in windows which uses the > | myodbc driver to connect... then you may run into problems with newer versions > | of mysql. I encountered a LOT of this, when we moved from 3.x up to 4.1, largely > | because of changes in the client - at least I was aware of that before I > | started, but I did have to rebuild client librairies on all webservers, and > | re-install odbc drivers on client machines throughout the building because of > | it. Might not be something you're willing/ready to undertake for the features > | you've already mentioned not being required in mysql 5. I'm seriously considering using mysql-5 for my latest project as well- for similar reasons outlined above. A dul opteron system has got plenty of power to spare for my purposes so squeezing out the last bit hasn't been an issue. I've got 252's, 250's, 246's, and 244 boxes. The 252's are "wickedly fast" but the 244's are still more than adequate for many purposes. [snip] > Anyway, have a good weekend. Ditto:) The point of all this being that there are different perspectives out there on this stuff and one needs to decide what's best for their set of circumstances. AH-- one last thing- if you need to run a firewall check out pf ported from OpenBSD. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 21:43:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B70C916A41F for ; Fri, 25 Nov 2005 21:43:49 +0000 (GMT) (envelope-from sven@dmv.com) Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E04F443D46 for ; Fri, 25 Nov 2005 21:43:48 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-a.dmv.com (mail-gw-cl-a.dmv.com [216.240.97.38]) by smtp-gw-cl-d.dmv.com (8.12.10/8.12.10) with ESMTP id jAPLhjft090586; Fri, 25 Nov 2005 16:43:46 -0500 (EST) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by mail-gw-cl-a.dmv.com (8.12.9/8.12.9) with ESMTP id jAPLhdQU088709; Fri, 25 Nov 2005 16:43:45 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: Scott Long In-Reply-To: <43876D0E.6080503@samsco.org> References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43876D0E.6080503@samsco.org> Content-Type: text/plain Date: Fri, 25 Nov 2005 16:45:19 -0500 Message-Id: <1132955119.10855.2.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.48 on 216.240.97.42 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.38 Cc: Roger Marquis , freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 25 Nov 2005 21:43:49 -0000 On Fri, 2005-11-25 at 12:59 -0700, Scott Long wrote: > Roger Marquis wrote: > > [...] > > > Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD > > or are not mature. Adaptec SCSI RAID is also not as well supported > > as some of the SATA RAID cards. > > What? Is this some sort of troll? > > Scott > _______________________________________________ Hmm, one of my servers may suffer an identity crisis if the LSI statement is true: cat /var/run/dmesg.boot Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #1: Sat May 14 17:37:43 EDT 2005 root@noracct.dmv.com:/usr/obj/usr/src/sys/NORACCT Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2190.62-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 8589934592 (8192 MB) avail memory = 8255700992 (7873 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs amr0: mem 0xfc880000-0xfc8fffff,0xff4f0000-0xff4fffff irq 28 at device 0.0 on pci2 amr0: Firmware 413Z, BIOS H424, 128MB RAM pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master PIO4 amrd0: on amr0 amrd0: 70003MB (143366144 sectors) RAID 0 (optimal) amrd1: on amr0 amrd1: 70003MB (143366144 sectors) RAID 0 (optimal) amrd2: on amr0 amrd2: 420603MB (861394944 sectors) RAID 1 (optimal) Sven From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 21:44:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE0B116A41F for ; Fri, 25 Nov 2005 21:44:26 +0000 (GMT) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9314543D5D for ; Fri, 25 Nov 2005 21:44:26 +0000 (GMT) (envelope-from marquis@roble.com) Date: Fri, 25 Nov 2005 13:44:26 -0800 (PST) From: Roger Marquis To: Scott Long In-Reply-To: <43876D0E.6080503@samsco.org> Message-ID: <20051125131721.K11440@roble.com> References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43876D0E.6080503@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 25 Nov 2005 21:44:27 -0000 Scott Long wrote: >> Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD >> or are not mature. Adaptec SCSI RAID is also not as well supported >> as some of the SATA RAID cards. > > What? Is this some sort of troll? Scott, Are you saying that the mpt drivers are no longer "largely unmaintained" or that there are management and monitoring tools for any Adaptec (U320) card? -- Roger Marquis http://www.roble.net/marquis/ Refs: From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 25 21:54:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D41516A41F for ; Fri, 25 Nov 2005 21:54:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 595EB43D49 for ; Fri, 25 Nov 2005 21:53:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAPLrrJ3053386; Fri, 25 Nov 2005 14:53:53 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438787F6.5050306@samsco.org> Date: Fri, 25 Nov 2005 14:53:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roger Marquis References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43876D0E.6080503@samsco.org> <20051125131721.K11440@roble.com> In-Reply-To: <20051125131721.K11440@roble.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 25 Nov 2005 21:54:01 -0000 Roger Marquis wrote: > Scott Long wrote: > >>> Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD >>> or are not mature. Adaptec SCSI RAID is also not as well supported >>> as some of the SATA RAID cards. >> >> >> What? Is this some sort of troll? > > > Scott, > > Are you saying that the mpt drivers are no longer "largely > unmaintained" A lot of work was put into making the MPT driver fully capable for 6.0. Unfortunately this doesn't look like it was reflected in the 6.0 release notes, but a simple query to the mailing lists could have provided up to date status. > or that there are management and monitoring tools > for any Adaptec (U320) card? > Adaptec contributed a large update to their RAID driver for 6.0. They are in the process of releasing an updated management tool for it, though the Linux management tools continue to work perfectly, as they have for the past 3 years. Again, a simple query could have provided up to date status. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 00:28:41 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5929116A420 for ; Sat, 26 Nov 2005 00:28:41 +0000 (GMT) (envelope-from tfcheng@yahoo.com) Received: from web51007.mail.yahoo.com (web51007.mail.yahoo.com [206.190.38.138]) by mx1.FreeBSD.org (Postfix) with SMTP id B6D0043DA1 for ; Sat, 26 Nov 2005 00:28:36 +0000 (GMT) (envelope-from tfcheng@yahoo.com) Received: (qmail 62365 invoked by uid 60001); 26 Nov 2005 00:28:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qj6eIHTVjoOzwiATUDK6zLbKBwAYX4IBXw496OTnlRTkyFFMtCRy9wZtqCYYyKRCUsa5VKoXaJBH9J2If4F4bZNxkCxQErVOXatA1cwoaP0qKTgTJCorY0XzJe/q3sjCsoTbiSIbfLU4lnIps7OEALCS2Mn1KjHa0zGowUAhMm8= ; Message-ID: <20051126002835.62363.qmail@web51007.mail.yahoo.com> Received: from [69.113.220.22] by web51007.mail.yahoo.com via HTTP; Sat, 26 Nov 2005 08:28:35 CST Date: Sat, 26 Nov 2005 08:28:35 +0800 (CST) From: "T.F. Cheng" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Subject: amd64 kernel making error 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, 26 Nov 2005 00:28:41 -0000 I install freebsd 6.0/amd64 on a sata, while making a custom kernel, I encountered an error: ... linking kernel ld: ffs_softdep.o(.debug_info+0200000008b58): reloc against `.text': error 2 ....mm.... any thoughts? many thanks! TFC Best Regards, Tsu-Fan Cheng _________________________________________________________ 雅虎免费G邮箱－中国第一绝无垃圾邮件骚超大邮箱 http://cn.mail.yahoo.com/?id=77071 From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 01:20:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E95416A41F for ; Sat, 26 Nov 2005 01:20:47 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-smtp.redshift.com (mail-smtp.redshift.com [216.228.2.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id C04F343D6A for ; Sat, 26 Nov 2005 01:20:42 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 67478 invoked by uid 89); 26 Nov 2005 01:20:43 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-smtp.redshift.com with SMTP; 26 Nov 2005 01:20:43 -0000 Message-Id: <3.0.1.32.20051125172037.00a4aa68@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Fri, 25 Nov 2005 17:20:37 -0800 To: Ken Gunderson ,freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <20051125135148.053d2c80.kgunders@teamcool.net> References: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 26 Nov 2005 01:20:47 -0000 | I have run across published benchmarks concluding php5 is indeed faster | than php4. I've not, however, run across published benchies to the | contrary. Not saying they're not out there, nor speaking for the | validity of those I have seen, but just pointing out that benchmarks | can be misleading, confusing, etc. and of limited use unless you | happen to run across one that mimicks your config, or you do them | yourself. I've run benchmarks here (first hand, myself) that show PHP4 is about 10 to 15% faster as I recall. I don't recall if that was using PHP4 as a static compile into apache and PHP5 as a DSO or how I had it all configured (it's been a while), but at least in my testing (and I try to keep apples to apples), PHP4 was quite a bit faster. The benchmarks I ran are spread across a messy excel spreadsheet, but if you want to see them, I'll be happy to e-mail them to you and/or upload them along with my SQL benchmarks. Like I say, as I recall, I tested a simple install of PHP4 against a simple install of PHP5 and PHP4 was the clear winner. Same with Apache 1.3.33 vs 2.0.5x Anyway, I always suggest people run their own benchmarks, in their own environments and not rely so much on what other people (including me) say or what other benchmarks show. You might be surprised that some of the older code runs faster. Also, you'd be shocked how much speed you can get from PHP and Apache if you compile out modules that aren't used. | Regarding Apache- I've taken to running my php stuff via FastCGI under | Lighttpd as unprivileged user on high port and then proxying via | Apache2. (Some of caching stuff comes in handy. Granted Squid is a Lighttpd isn't bad, but if you tweak apache (at least 1.3.33) properly, you can reach the same speed levels. In fact, in the testing I did, a stripped down apache was able to nearly match thttpd. And just for fun, I wrote a 3 or 4 line C++ server to see what the theoretical speed was. All the server did was listen on port 80 - as soon as it got a connect, it sent the web page. It didn't wait for GET or anything like that - just bang, page sent, connection closed. Using that as the "redline" for the machine, I think I was able to get thttpd to about 90% of it and apache 1.3.33 to something like 75 or 80% of it (those are just off-the-top-of-my-head numbers, but you get the idea). | better choice for serious use. ) This config pretty much screams | performance wise. do you have any ab figures for 1k, 5k html or maybe some php programs as far as page loads per second, by any chance? For various reasons discussed a while back on | another thread, best webserver perf is seen under FBSD-i386. The AMD64 | stuff absolutely rocks when you get into larger db's needing more ram, | etc. In the testing I've done (specific to .html and php pages), I seem to remember that i386 did well on small pages (under 1k), but amd64 did better on pages that were 1k and above. Running php under FastCGI also sets you up for inexpensive load | balancing solution. Just throw relatively inexpensive single cpu, sata | based machines in front of the db server. Anyhow, just throwing this | out for what it might be worth. If you've not checked out "Lighty" | before you may want to take a gander: | | | | Here's the FastCGI stuff: | | Thanks! :) I've played with lighttpd. I think I tried using fastcgi, but I can't recall now if I ever got it to work or not. That might have been the one where my eyes glazed over and I gave up :) | I'm seriously considering using mysql-5 for my latest project as well- | for similar reasons outlined above. A dul opteron system has got | plenty of power to spare for my purposes so squeezing out the last bit | hasn't been an issue. I've got 252's, 250's, 246's, and 244 boxes. | The 252's are "wickedly fast" but the 244's are still more than | adequate for many purposes. Yeah, I'm going to play with MySQL 5 soon also. I've been running the Dual Opteron 246's here (single cores). I would love to run some 252's, but since I'm a cheap SOB, I can't bring myself to spend the extra on the CPU's :) Do you happen to know (roughly) how much of a performance boost the 252's give you as compared to the 246's? I think our Tyan S2881 boards will probably support the 250's or the 252's. | Ditto:) The point of all this being that there are different | perspectives out there on this stuff and one needs to decide what's | best for their set of circumstances. I couldn't agree more. At the end of the day, it pays to test everything on your own platform and with your own application in order to determine what works best. What works for Ken isn't always what works for Ray or what works for Olaf or Nathan, etc, etc :) | AH-- one last thing- if you need to run a firewall check out pf ported | from OpenBSD. I built a router using FreeBSD and run ipf on it. I have our load balancers (Radware units) setup in local triangulation. It's nice to have ipf handled on a central machine as opposed to on each server. I was surprised how much of a performance boost you get if you don't run ipf :) Now I just need some of those 252's for the router (it's currently a single Xeon :-\ have a good weekend. Ray From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 07:08:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0BF316A41F for ; Sat, 26 Nov 2005 07:08:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 193DE43D68 for ; Sat, 26 Nov 2005 07:08:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 2E3411A3C27; Fri, 25 Nov 2005 23:08:15 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 89135512B3; Sat, 26 Nov 2005 02:08:14 -0500 (EST) Date: Sat, 26 Nov 2005 02:08:14 -0500 From: Kris Kennaway To: "T.F. Cheng" Message-ID: <20051126070814.GA64709@xor.obsecurity.org> References: <20051126002835.62363.qmail@web51007.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20051126002835.62363.qmail@web51007.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 kernel making error 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, 26 Nov 2005 07:08:17 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 26, 2005 at 08:28:35AM +0800, T.F. Cheng wrote: > I install freebsd 6.0/amd64 on a sata, while making a > custom kernel, I encountered an error: > ... > linking kernel > ld: ffs_softdep.o(.debug_info+0200000008b58): reloc > against `.text': error 2 >=20 > ....mm.... >=20 > any thoughts? many thanks! Your files may have been corrupted somehow (this can happen if e.g. the power failed or the system otherwise crashed during your last kernel build). Try 'make clean' and then retry. Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiAneWry0BWjoQKURAnCsAKCShNdGswDu3ndtKPAV3yNXXPR+LgCghtmn nyzn4TNY7DkYsD5qvPPbtus= =ozO9 -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 07:12:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB6CD16A41F for ; Sat, 26 Nov 2005 07:12:10 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6EFF43D45 for ; Sat, 26 Nov 2005 07:12:07 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ironport.bredband.com ([195.54.107.82] [195.54.107.82]) by mxfep02.bredband.com with ESMTP id <20051126071206.ZSQN9142.mxfep02.bredband.com@ironport.bredband.com> for ; Sat, 26 Nov 2005 08:12:06 +0100 Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30]) by ironport.bredband.com with ESMTP; 26 Nov 2005 08:12:42 +0100 X-BrightmailFiltered: true X-IronPort-AV: i="3.97,379,1125871200"; d="scan'208"; a="13187967:sNHT24779772" Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id CD477678DC; Sat, 26 Nov 2005 08:11:57 +0100 (CET) Message-ID: <43880ABE.3020801@gneto.com> Date: Sat, 26 Nov 2005 08:11:58 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43876D0E.6080503@samsco.org> <20051125131721.K11440@roble.com> In-Reply-To: <20051125131721.K11440@roble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Roger Marquis Subject: Re: Hardware RAID support? Which controller best to use? 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, 26 Nov 2005 07:12:11 -0000 Roger Marquis wrote: > Scott Long wrote: > >>> Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD >>> or are not mature. Adaptec SCSI RAID is also not as well supported >>> as some of the SATA RAID cards. >> >> >> What? Is this some sort of troll? > > > Scott, > > Are you saying that the mpt drivers are no longer "largely > unmaintained" or that there are management and monitoring tools > for any Adaptec (U320) card? In my book "fast LSI SCSI RAID" refers to the amr driver and the MegaRAID cards, not the cheap LSI SCSI boards with IME (Integrated Mirroring Enhanced - RAID 1E) that uses mpt. The amr boards have excellent support in FreeBSD and even official support from LSI. LSI have mgmt tools available for FreeBSD on their web. /Martin From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 07:30:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CADB216A420 for ; Sat, 26 Nov 2005 07:30:03 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D7F143D5C for ; Sat, 26 Nov 2005 07:30:03 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 6FAA7C08BE5; Sat, 26 Nov 2005 03:30:02 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00748-01; Sat, 26 Nov 2005 07:30:02 +0000 (GMT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id F2A4BC089F4; Sat, 26 Nov 2005 03:30:01 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id A59963F051; Sat, 26 Nov 2005 03:30:01 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 9329B3C043; Sat, 26 Nov 2005 03:30:01 -0400 (AST) Date: Sat, 26 Nov 2005 03:30:01 -0400 (AST) From: "Marc G. Fournier" To: Martin Nilsson In-Reply-To: <43880ABE.3020801@gneto.com> Message-ID: <20051126032844.C1053@ganymede.hub.org> References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <43876D0E.6080503@samsco.org> <20051125131721.K11440@roble.com> <43880ABE.3020801@gneto.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Roger Marquis , freebsd-amd64@freebsd.org Subject: Re: Hardware RAID support? Which controller best to use? 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, 26 Nov 2005 07:30:03 -0000 On Sat, 26 Nov 2005, Martin Nilsson wrote: > Roger Marquis wrote: >> Scott Long wrote: >> >>>> Sadly, the fast LSI SCSI RAID drivers either don't exist for FreeBSD >>>> or are not mature. Adaptec SCSI RAID is also not as well supported >>>> as some of the SATA RAID cards. >>> >>> >>> What? Is this some sort of troll? >> >> >> Scott, >> >> Are you saying that the mpt drivers are no longer "largely >> unmaintained" or that there are management and monitoring tools >> for any Adaptec (U320) card? > > In my book "fast LSI SCSI RAID" refers to the amr driver and the MegaRAID > cards, not the cheap LSI SCSI boards with IME (Integrated Mirroring Enhanced > - RAID 1E) that uses mpt. > > The amr boards have excellent support in FreeBSD and even official support > from LSI. LSI have mgmt tools available for FreeBSD on their web. I'm just looking at getting a system with an Intel SRCU42X card in it ... this is supported by the amr driver, so do I automatically assume that this is supported by LSI also, even though it is 'branded' an Intel card? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 11:19:32 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FA7816A41F for ; Sat, 26 Nov 2005 11:19:32 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1791843D58 for ; Sat, 26 Nov 2005 11:19:30 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.40] ([213.112.167.94] [213.112.167.94]) by mxfep02.bredband.com with ESMTP id <20051126111929.BPSG9142.mxfep02.bredband.com@[192.168.245.40]>; Sat, 26 Nov 2005 12:19:29 +0100 Message-ID: <438844C2.3000902@bredband.net> Date: Sat, 26 Nov 2005 12:19:30 +0100 From: Lars Tunkrans User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.12) Gecko/20051118 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sten Spans References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> <4384BBBF.4030007@wmptl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org Subject: Re: Sun x2100 Server Compatability 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, 26 Nov 2005 11:19:32 -0000 Sten Spans wrote: > On Wed, 23 Nov 2005, Nathan Vidican wrote: > >> Vivek Khera wrote: >> >>> >>> On Nov 17, 2005, at 6:19 PM, Daniel Rock wrote: >>> >>>> Nathan Vidican schrieb: >>>> >>>>> Any known issues running FreeBSD/amd64 on a Sun x2100 server? >>>>> Single opteron box, dual GigE, 80GB S-ATA, 1GB Ram, specs as below: >>>> >>>> >>>> >>>> The X2100 is based on a Tyan Tomcat K8E (S2865) mainboard without >>>> PS/2 mouse and keyboard ports. So you should look at success >>>> reports for this board. >>> >>> >>> >>> >> Same issue here... both NIC's requried, but putting in a good ole >> Intel/FXP card won't bother me in the least. > > > The x2100 is listed as only having pci-E expansion options ... > so a regular pci ethernet card wont fit. > > The intention here is to provide a FAST bus for the optional PCI-E infiniband card and PCI-E FibreChannel CARD. The box is inteded as a GRID building block. //Lars From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 19:53:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E850916A41F for ; Sat, 26 Nov 2005 19:53:12 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBE4043D49 for ; Sat, 26 Nov 2005 19:53:06 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id DE131F7C5 for ; Sat, 26 Nov 2005 12:53:05 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id A2D7EF7BB for ; Sat, 26 Nov 2005 12:53:05 -0700 (MST) Date: Sat, 26 Nov 2005 12:53:04 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051126125304.36da08d8.kgunders@teamcool.net> In-Reply-To: <3.0.1.32.20051125172037.00a4aa68@pop.redshift.com> References: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125172037.00a4aa68@pop.redshift.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? 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, 26 Nov 2005 19:53:13 -0000 On Fri, 25 Nov 2005 17:20:37 -0800 ray@redshift.com wrote: > | I have run across published benchmarks concluding php5 is indeed faster > | than php4. I've not, however, run across published benchies to the > | contrary. Not saying they're not out there, nor speaking for the > | validity of those I have seen, but just pointing out that benchmarks > | can be misleading, confusing, etc. and of limited use unless you > | happen to run across one that mimicks your config, or you do them > | yourself. > > I've run benchmarks here (first hand, myself) that show PHP4 is about 10 to 15% > faster as I recall. I don't recall if that was using PHP4 as a static compile > into apache and PHP5 as a DSO or how I had it all configured (it's been a > while), but at least in my testing (and I try to keep apples to apples), PHP4 > was quite a bit faster. There's this out of Source Labs. Can't speak for validity of testing: > The benchmarks I ran are spread across a messy excel spreadsheet, but if you > want to see them, I'll be happy to e-mail them to you and/or upload them along > with my SQL benchmarks. > > Like I say, as I recall, I tested a simple install of PHP4 against a simple > install of PHP5 and PHP4 was the clear winner. > > Same with Apache 1.3.33 vs 2.0.5x > > Anyway, I always suggest people run their own benchmarks, in their own > environments and not rely so much on what other people (including me) say or > what other benchmarks show. You might be surprised that some of the older code > runs faster. Also, you'd be shocked how much speed you can get from PHP and > Apache if you compile out modules that aren't used. One of the superiorities of *BSD compared to some other *nix like OS's out there that include the kitchen sink in a default install... >;^) > | Regarding Apache- I've taken to running my php stuff via FastCGI under > | Lighttpd as unprivileged user on high port and then proxying via > | Apache2. (Some of caching stuff comes in handy. Granted Squid is a > > Lighttpd isn't bad, but if you tweak apache (at least 1.3.33) properly, you can > reach the same speed levels. In fact, in the testing I did, a stripped down > apache was able to nearly match thttpd. And just for fun, I wrote a 3 or 4 line > C++ server to see what the theoretical speed was. All the server did was listen > on port 80 - as soon as it got a connect, it sent the web page. It didn't wait > for GET or anything like that - just bang, page sent, connection closed. Using > that as the "redline" for the machine, I think I was able to get thttpd to about > 90% of it and apache 1.3.33 to something like 75 or 80% of it (those are just > off-the-top-of-my-head numbers, but you get the idea). You're mixing and matching Lighttpd and thttpd here? I was referencing Lighttpd. In either case, your experience seems incongruent with some benchmarks published on the Lighttpd website (but then that's also why you should profile your stuff for your real world;). In case you missed them: These have been online for quite some time now and I've not heard any cries of "foul" from the competition... > | better choice for serious use. ) This config pretty much screams > | performance wise. > > do you have any ab figures for 1k, 5k html or maybe some php programs as far as > page loads per second, by any chance? I didn't save anything I did w/the php stuff- it was just some quick ab's with php4 to satisfy my curiosity. Here's some quick and dirty stuff I put online for a ROR app though: It's turned out to be a fairly popular read by the Typo crowd. > For various reasons discussed a while back on > | another thread, best webserver perf is seen under FBSD-i386. The AMD64 > | stuff absolutely rocks when you get into larger db's needing more ram, > | etc. > > In the testing I've done (specific to .html and php pages), I seem to remember > that i386 did well on small pages (under 1k), but amd64 did better on pages that > were 1k and above. > > Running php under FastCGI also sets you up for inexpensive load > | balancing solution. Just throw relatively inexpensive single cpu, sata > | based machines in front of the db server. Anyhow, just throwing this > | out for what it might be worth. If you've not checked out "Lighty" > | before you may want to take a gander: > | > | > | > | Here's the FastCGI stuff: > | > | > > Thanks! :) I've played with lighttpd. I think I tried using fastcgi, but I > can't recall now if I ever got it to work or not. That might have been the one > where my eyes glazed over and I gave up :) Lighttpd can be a bit challenging at first blush as the docs can be a bit terse in places. Not that it's all that complicated but it's just different from Apache think. The mailing list is very responsive. See the doc I pointed to above for an example of FastCGI config that's easily modified for php app. Basically I just run a really striped down minimal instance of Lighttpd to manage the FastCGI processes. More flexbile and easier to manage that SuExec. > | I'm seriously considering using mysql-5 for my latest project as well- > | for similar reasons outlined above. A dul opteron system has got > | plenty of power to spare for my purposes so squeezing out the last bit > | hasn't been an issue. I've got 252's, 250's, 246's, and 244 boxes. > | The 252's are "wickedly fast" but the 244's are still more than > | adequate for many purposes. > > Yeah, I'm going to play with MySQL 5 soon also. I've been running the Dual > Opteron 246's here (single cores). I would love to run some 252's, but since > I'm a cheap SOB, I can't bring myself to spend the extra on the CPU's :) Do you > happen to know (roughly) how much of a performance boost the 252's give you as > compared to the 246's? I think our Tyan S2881 boards will probably support the > 250's or the 252's. I didn't do anything formal but did run a few Ubench tests. Granted it's a synthetic test but does provide a frame of reference: dual 246's w/4GB DDR 400: Ubench CPU: 222794 Ubench MEM: 200592 -------------------- Ubench AVG: 211693 Same machine except dual 252's: Ubench CPU: 290450 Ubench MEM: 248157 -------------------- Ubench AVG: 269303 The 252's came at a deal I coudn't refuse. Last I looked the 246's were the sweet spot on price/perf though (are the 90nm core versions in the channel yet?? If not then they soon should be and might be worth the wait??). > | Ditto:) The point of all this being that there are different > | perspectives out there on this stuff and one needs to decide what's > | best for their set of circumstances. > > I couldn't agree more. At the end of the day, it pays to test everything on > your own platform and with your own application in order to determine what works > best. What works for Ken isn't always what works for Ray or what works for Olaf > or Nathan, etc, etc :) > > | AH-- one last thing- if you need to run a firewall check out pf ported > | from OpenBSD. > > I built a router using FreeBSD and run ipf on it. I have our load balancers > (Radware units) setup in local triangulation. It's nice to have ipf handled on > a central machine as opposed to on each server. I was surprised how much of a > performance boost you get if you don't run ipf :) Now I just need some of those > 252's for the router (it's currently a single Xeon :-\ One would think that Xeon would be quite sufficient for firewall, eh? You may want to check out PF and Carp. I've been using PF since before Hartmeir's code had been merged into official OBSD dist and never looked back. Also been the hook that converted a few of my Linux buddies to *BSD;) At least for their firewall needs... I'm certainly no guru compared to many on this list and this may be getting a bit off topic for freebsd-amd64. But I have been around the block a time or two and it's all related to performance of various apps/ configs under amd64 so thought I'd contribute my $0.02 in hopes it may be of some benefit to Olaf's adventures in FreeBSD land. Hope I've not wandered too far astray... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 26 23:22:47 2005 Return-Path: X-Original-To: amd64@freeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C1C816A41F for ; Sat, 26 Nov 2005 23:22:47 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9813443D5A for ; Sat, 26 Nov 2005 23:22:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 80CAA1A3C2C for ; Sat, 26 Nov 2005 15:22:46 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5298A51494; Sat, 26 Nov 2005 18:22:45 -0500 (EST) Date: Sat, 26 Nov 2005 18:22:45 -0500 From: Kris Kennaway To: Kris Kennaway Message-ID: <20051126232244.GA83432@xor.obsecurity.org> References: <20051124232616.GA32023@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <20051124232616.GA32023@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: amd64@freeBSD.org Subject: Re: spin lock smp rendezvous held by 0xffffff01250a7980 for > 5 seconds 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, 26 Nov 2005 23:22:47 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 06:26:16PM -0500, Kris Kennaway wrote: > I got this on a quad amd64 machine running 6.0-STABLE. At the time it > was running 21 simultaneous tar extractions onto a sync-mounted md. >=20 > panic() at panic+0x1e6 > _mtx_lock_spin() at _mtx_lock_spin+0xad > pmap_invalidate_range() at pmap_invalidate_range+0xb3 > pmap_qremove() at pmap_qremove+0x53 > vfs_vmio_release() at vfs_vmio_release+0x1e0 > getnewbuf() at getnewbuf+0x368 > getblk() at getblk+0x3d9 > ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 > ffs_write() at ffs_write+0x31b > VOP_WRITE_APV() at VOP_WRITE_APV+0xed > vn_write() at vn_write+0x228 > dofilewrite() at dofilewrite+0x90 > kern_writev() at kern_writev+0x54 > write() at write+0x4b >=20 > Unfortunately I can't dump on this machine (and no debugging is > currently enabled), but I can try to reproduce it. I tried for 24 hours with witness enabled but couldn't reproduce. The same panic happened in the same way when witness was disabled, although the= failure mode was a bit different: Fatal double fault cpuid =3D 3; apic id =3D 03 panic: double fault cpuid =3D 3 KDB: enter: panic [...] mtx_lock_spin() at _mtx_lock_spin+0x6b getit() at getit+0x6f DELAY() at DELAY+0x44 _mtx_lock_spin() at _mtx_lock_spin+0x6b getit() at getit+0x6f DELAY() at DELAY+0x44 _mtx_lock_spin() at _mtx_lock_spin+0x6b getit() at getit+0x6f DELAY() at DELAY+0x44 _mtx_lock_spin() at _mtx_lock_spin+0x6b getit() at getit+0x6f DELAY() at DELAY+0x44 _mtx_lock_spin() at _mtx_lock_spin+0x6b pmap_invalidate_range() at pmap_invalidate_range+0xb3 pmap_qremove() at pmap_qremove+0x53 vfs_vmio_release() at vfs_vmio_release+0x1e0 getnewbuf() at getnewbuf+0x368 getblk() at getblk+0x3d9 ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 ffs_write() at ffs_write+0x31b VOP_WRITE_APV() at VOP_WRITE_APV+0xed vn_write() at vn_write+0x228 dofilewrite() at dofilewrite+0x90 kern_writev() at kern_writev+0x54 write() at write+0x4b syscall() at syscall+0x404 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (4, FreeBSD ELF64, write), rip =3D 0x80070ea6c, rsp =3D 0x7ffff= fffe6a8, rbp =3D 0x52ae00 --- i.e. the first _mtx_lock_spin() tried to acquire the ipi lock and spun, which called DELAY and getit, which tried to acquire the clock lock: mtx_lock_spin(&clock_lock); which *also* spun, and called DELAY...and at that point things went to hell and it recursed until it blew out the stack. I guess the next step is to try INVARIANTS alone in case that catches something. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiO43Wry0BWjoQKURAhsxAJ9KDUyMD0x3Ce/jtB2QDry+kxfyrQCg4inc pO713nUMAEgFuuRg88J+0eI= =cJAh -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3--