Dual xeon
Hi list, We´ve received a xeon dual processor machine, Intel motherboard... What´s the best versionplatform for it ?? i386, ia64 ?? Thanks, Aguiar ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual xeon
At 17:35 2006-03-27, Aguiar Magalhaes wrote: Hi list, We´ve received a xeon dual processor machine, Intel motherboard... What´s the best versionplatform for it ?? i386, ia64 ?? Hi, first of all, from what I know ia64 won't work... That release is for the itanium kinda cpus... You have the choice between amd64 version (it works with processor having the emt64 extensions like the xeon) or the i386 version. If all you need will be compiled from the ports, I highly recommend the amd64 version... If you are planning on installing precompiled binairies you'll find that there is no support nowhere for the amd64 version so I recommend to use i386 Hope this helps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual xeon
On Mon, Mar 27, 2006 at 05:42:21PM -0500, Ian Lord wrote: If you are planning on installing precompiled binairies you'll find that there is no support nowhere for the amd64 version This is completely false. Kris pgp90n4eT7UkV.pgp Description: PGP signature
Re: Dual xeon
At 17:49 2006-03-27, Kris Kennaway wrote: On Mon, Mar 27, 2006 at 05:42:21PM -0500, Ian Lord wrote: If you are planning on installing precompiled binairies you'll find that there is no support nowhere for the amd64 version This is completely false. Sorry I wasn't clear enough... In the commercial vendors... It's really hard to find amd64 versions... Ex: pdflib, zend performance, zend safeguard, etc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual xeon
On Mon, Mar 27, 2006 at 05:52:04PM -0500, Ian Lord wrote: At 17:49 2006-03-27, Kris Kennaway wrote: On Mon, Mar 27, 2006 at 05:42:21PM -0500, Ian Lord wrote: If you are planning on installing precompiled binairies you'll find that there is no support nowhere for the amd64 version This is completely false. Sorry I wasn't clear enough... In the commercial vendors... It's really hard to find amd64 versions... Ex: pdflib, zend performance, zend safeguard, etc But this is true whether or not you use ports or packages on your FreeBSD system. Kris pgp3aCqwFBL4o.pgp Description: PGP signature
Dual-Xeon vs Dual-PIII ... Dual-PIII actually better?
I've had a discussion going on talking about performance issues of one of my servers, and right now the only thing that I've got to work with is the difference in CPUs ... I had started it off thinking it was a software RAID issue, but looking at my Dual-PIII, its not exhibiting near as much load, and the only difference between the two configs is drive sizes (Dual-PIII has 36G Seagate Drives, the Dual-Xeon has 73G ones) and the CPUs ... even the operating system is within days of each other, so either I hit a bad 'cvsup day' for the Dual-Xeon, or I'm missing something as far as Dual-Xeon's is concerned ... vmstat 5 on both machines shows 50% idle CPUs on the Dual-PIII, while the Dual-Xeon shows 90% system busy ... if it were vinum related, I'd expect that they would both be about as busy on the system side ... First question ... is there some way of getting 'finer' data on system usage? What is using up 99% of the %CPU, when it happens? syscalls/sec don't seem to 'jump' much when that happens, hovering around the same on both servers (between 2k and 4k / sec ... I'm going to be doing an OS upgrade on that machine over the next couple of days, to see if maybe I did just get a 'bad kernel', but if someone can suggest something that I can monitor/look at to determine where the sys cpu is being sucked up, that would be appreciated ... thanks Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dual-Xeon vs Dual-PIII (Was: Re: vinum in 4.x poor performer?)
The more I'm looking at this, the less I can believe my 'issue' is with vinum ... based on one of my other machines, it just doesn't *feel* right I have two servers that are fairly similar in config ... both running vinum RAID5 over 4 disks ... one is the Dual-Xeon that I'm finding problematic with 73G Seagate drives, and the other is the Dual-PIII with 36G Seagate drives ... The reason that I'm finding it hard to believe that my problem is with vinum is that the Dual-PIII is twice as loaded as the Dual-Xeon, but hardly seems to break a sweat ... In fact, out of all my servers (3xDual-PIII, 1xDual-Athlon and 1xDual-Xeon), only the Dual-Xeon doesn't seem to be able to perform ... Now, out of all of the servers, only the Dual-Xeon, of course, supports HTT, which I *believe* is disabled, but from dmesg: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #1: Fri Oct 22 15:06:55 ADT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/kernel Timecounter i8254 frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 4026466304 (3932096K bytes) avail memory = 3922362368 (3830432K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee0 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec0 io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec81000 io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec81400 Preloaded elf kernel kernel at 0x80339000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled Using $PIR table, 19 entries at 0x800f2f30 Its showing 4 CPUs ... but: machdep.hlt_logical_cpus: 1 which, from /usr/src/UPDATING indicates that the HTT cpus aren't enabled: 20031022: Support for HyperThread logical CPUs has now been enabled by default. As a result, the HTT kernel option no longer exists. Instead, the logical CPUs are always started so that they can handle interrupts. However, the extra logical CPUs are prevented from executing user processes by default. To enable the logical CPUs, change the value of the machdep.hlt_logical_cpus from 1 to 0. This value can also be set from the loader as a tunable of the same name. Finally ... top shows: last pid: 73871; load averages: 9.76, 9.23, 8.16 up 9+02:02:26 00:57:06 422 processes: 8 running, 413 sleeping, 1 zombie CPU states: 19.0% user, 0.0% nice, 81.0% system, 0.0% interrupt, 0.0% idle Mem: 2445M Active, 497M Inact, 595M Wired, 160M Cache, 199M Buf, 75M Free Swap: 2048M Total, 6388K Used, 2041M Free PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 28298 www 64 0 28136K 12404K CPU2 2 80:59 24.51% 24.51% httpd 69232 excalibur 64 0 80128K 76624K RUN2 2:55 16.50% 16.50% lisp.run 72879 www 64 0 22664K 9444K RUN0 0:12 12.94% 12.94% httpd 14154 www 64 0 36992K 22880K RUN0 55:07 12.70% 12.70% httpd 69758 www 63 0 15400K 8756K RUN0 0:18 11.87% 11.87% httpd 7553 nobody 2 0 158M 131M poll 0 33:19 8.98% 8.98% nsd 70752 setiathome 2 0 14644K 14084K select 2 0:47 8.98% 8.98% perl 71191 setiathome 2 0 13220K 12804K select 0 0:29 8.40% 8.40% perl 70903 setiathome 2 0 14224K 13676K select 0 0:42 7.37% 7.37% perl 33932 setiathome 2 0 21712K 21144K select 0 2:23 4.59% 4.59% perl In this case ... 0% idle, 81% in system? As a comparison the Dual-PIII/vinum server looks like: last pid: 90614; load averages: 3.64, 2.41, 2.69 up 3+08:45:17 00:59:27 955 processes: 12 running, 942 sleeping, 1 zombie CPU states: 63.9% user, 0.0% nice, 32.6% system, 3.5% interrupt, 0.0% idle Mem: 2432M Active, 687M Inact, 563M Wired, 147M Cache, 199M Buf, 5700K Free Swap: 8192M Total, 12M Used, 8180M Free, 12K In PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 90506 scrappy 56 0 19384K 14428K RUN0 0:06 22.98% 16.41% postgres 90579 root57 0 3028K 2156K CPU1 1 0:04 26.23% 14.45% top 90554 pgsql -6 0 12784K 7408K RUN1 0:04
Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
Chandler May wrote: I found this fix on a mailing list archive using Google: http://lists.freebsd.org/pipermail/freebsd-i386/2004-December/001958.html But I have no idea how to apply it. Can anybody help out here? Looks like you've found the right answer there. Unfortunately you've hit Catch22: in order to fix the boot problem, you need to patch the kernel. In order to patch the kernel, you need a running system. In order to get a running system you need to fix the boot problem... Probably your best bet is to pull the disk out of your i7520 box and attach it to some other machine where you can install FreeBSD on it. At the same time try applying the patch from PR i386/74829 and building a kernel with it applied. If you can extract the patch either from the PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=74829) or the e-mail you quoted, then to apply it: # cd /usr/src # patch -p 2 patch.txt Note that extracting the patch may be harder than you expect, as mailing systems and cut'n'paste tend to wrap lines or convert tabs to spaces and other such damage. Then rebuild the GENERIC kernel and install it onto your new drive. Instruction for building a kernel are here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html Don't let your Gentoo experience tempt you into trying to chroot yourself onto the new drive -- while that could certainly be made to work, it's not something that gets done very often so you'ld end up having to debug things as you went along. Just use sysinstall(8) to install on the appropriate disk while it's attached to a spare system, and then boot up your spare system from that drive to do the kernel builds. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor School Rd PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone Tel: +44 1304 617253 Kent, CT14 0JL UK signature.asc Description: OpenPGP digital signature
Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
I found this fix on a mailing list archive using Google: http://lists.freebsd.org/pipermail/freebsd-i386/2004-December/001958.html But I have no idea how to apply it. Can anybody help out here? Chandler On Tue, 28 Dec 2004 22:11:01 -0600, Chandler May [EMAIL PROTECTED] wrote: Yes, it works fine in Gentoo Linux (with the same PS/2 keyboard I am trying to use to install FreeBSD). Chandler On Wed, 29 Dec 2004 08:57:21 +0530, Subhro [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Chandler May Sent: Wednesday, December 29, 2004 8:28 To: freebsd-questions@freebsd.org Subject: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems) Hi! I just recently switched to FreeBSD on my primary computer, an Intel Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, and, if at all possible, I never want to go back. Just a few days ago I set up a dual Intel Xeon Nocona system on the Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on it, but when I tried FreeBSD, the install disk stopped before it had even fully started. When I select Verbose Logging from the start-up menu, it stops immediately after these four lines come up: atkbdc0: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD return status:00aa I've let it run for hours, but it never gets beyond that point. I'm definitely new to FreeBSD, but I'm relatively familiar with computers in general, so the first line of that message tipped me off, and I decided to try to boot it with ACPI disabled. I did, but it still stopped. Here is the last line that was shown before it stopped: cpu0 on motherboard Does anyone know why this is happening and/or has a solution to solve it? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] Looks to me as if the keyboard controller is broken. Does this thing work or worked recently in anything else? Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't start up the FreeBSD install disk on dual Xeon Nocona rig (it works on other systems)
Hi! I just recently switched to FreeBSD on my primary computer, an Intel Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, and, if at all possible, I never want to go back. Just a few days ago I set up a dual Intel Xeon Nocona system on the Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on it, but when I tried FreeBSD, the install disk stopped before it had even fully started. When I select Verbose Logging from the start-up menu, it stops immediately after these four lines come up: atkbdc0: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD return status:00aa I've let it run for hours, but it never gets beyond that point. I'm definitely new to FreeBSD, but I'm relatively familiar with computers in general, so the first line of that message tipped me off, and I decided to try to boot it with ACPI disabled. I did, but it still stopped. Here is the last line that was shown before it stopped: cpu0 on motherboard Does anyone know why this is happening and/or has a solution to solve it? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Chandler May Sent: Wednesday, December 29, 2004 8:28 To: freebsd-questions@freebsd.org Subject: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems) Hi! I just recently switched to FreeBSD on my primary computer, an Intel Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, and, if at all possible, I never want to go back. Just a few days ago I set up a dual Intel Xeon Nocona system on the Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on it, but when I tried FreeBSD, the install disk stopped before it had even fully started. When I select Verbose Logging from the start-up menu, it stops immediately after these four lines come up: atkbdc0: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD return status:00aa I've let it run for hours, but it never gets beyond that point. I'm definitely new to FreeBSD, but I'm relatively familiar with computers in general, so the first line of that message tipped me off, and I decided to try to boot it with ACPI disabled. I did, but it still stopped. Here is the last line that was shown before it stopped: cpu0 on motherboard Does anyone know why this is happening and/or has a solution to solve it? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] Looks to me as if the keyboard controller is broken. Does this thing work or worked recently in anything else? Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
Yes, it works fine in Gentoo Linux (with the same PS/2 keyboard I am trying to use to install FreeBSD). Chandler On Wed, 29 Dec 2004 08:57:21 +0530, Subhro [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Chandler May Sent: Wednesday, December 29, 2004 8:28 To: freebsd-questions@freebsd.org Subject: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems) Hi! I just recently switched to FreeBSD on my primary computer, an Intel Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, and, if at all possible, I never want to go back. Just a few days ago I set up a dual Intel Xeon Nocona system on the Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on it, but when I tried FreeBSD, the install disk stopped before it had even fully started. When I select Verbose Logging from the start-up menu, it stops immediately after these four lines come up: atkbdc0: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD return status:00aa I've let it run for hours, but it never gets beyond that point. I'm definitely new to FreeBSD, but I'm relatively familiar with computers in general, so the first line of that message tipped me off, and I decided to try to boot it with ACPI disabled. I did, but it still stopped. Here is the last line that was shown before it stopped: cpu0 on motherboard Does anyone know why this is happening and/or has a solution to solve it? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] Looks to me as if the keyboard controller is broken. Does this thing work or worked recently in anything else? Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HTT/SMP Dual Xeon systems unstable
On Friday 10 December 2004 09:32 am, [EMAIL PROTECTED] wrote: Hi, I'm sorry for typing this mail for the third time, I'm not sure if the other mails did reach the list. The domain I was using to send emails has just expired. Please cc me, as I'm not subscribed to the list with this email. I have a Dual Xeon 2.4 and a Dual Xeon 2.8 servers running with HyperThreading, ACPI, and SMP enabled. The 2.8 server won't stand for more than 5 days without crashing, and the 2.4 server was up 30 days crashed, now was up 12 days, and crashed. I didn't have a debugging kernel, I'll be building one when the datacenter reboots the server. I also don't have any panic messages.. I have, however, a few questions: - machdep.cpu_idle_hlt - I've seen a lot on google about this sysctl, but still don't fully understand it. What does this sysctl really changes? - HyperThreading - Do I really have a performance increase with HTT turned on? I've heard it can penalize performance because the scheduler isn't optimized for logical CPUs. Does having HTT enabled impacts the stability of the system? - ACPI - I'll be disabling ACPI along with HTT to see if the server doesn't crash for awhile. Is ACPI on 5.3-STABLE (around November 1st, it was pre-release) still a problem? Last but not the least, my 5.3-STABLE version is from a few days before the release. Since I had created a few jails by then, I didn't upgrade the system to use the -RELEASE. Was there any last-standing problem a few days before the release that could be causing my instability problems? Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. There is a problem in the kernel that causes with 3 or more processors (including logical CPUs from HTT). Disabling HTT in the BIOS is probably your best bet as it will get you down to 2 CPUs which should work much better. HTT also isn't but so useful anyways for most workloads. The instability problems have just been fixed in HEAD and will hopefully be MFC'd for 5.4 btw. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HTT/SMP Dual Xeon systems unstable
John Baldwin wrote: There is a problem in the kernel that causes with 3 or more processors (including logical CPUs from HTT). Disabling HTT in the BIOS is probably your best bet as it will get you down to 2 CPUs which should work much better. HTT also isn't but so useful anyways for most workloads. The instability problems have just been fixed in HEAD and will hopefully be MFC'd for 5.4 btw. It looks like I have lucked out so far, because I have this set up with no problems so far. I hope this fix gets to 5.x-stable soon because for my particular workloads HTT helps a lot. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HTT/SMP Dual Xeon systems unstable
Hi, I'm sorry for typing this mail for the third time, I'm not sure if the other mails did reach the list. The domain I was using to send emails has just expired. Please cc me, as I'm not subscribed to the list with this email. I have a Dual Xeon 2.4 and a Dual Xeon 2.8 servers running with HyperThreading, ACPI, and SMP enabled. The 2.8 server won't stand for more than 5 days without crashing, and the 2.4 server was up 30 days crashed, now was up 12 days, and crashed. I didn't have a debugging kernel, I'll be building one when the datacenter reboots the server. I also don't have any panic messages.. I have, however, a few questions: - machdep.cpu_idle_hlt - I've seen a lot on google about this sysctl, but still don't fully understand it. What does this sysctl really changes? - HyperThreading - Do I really have a performance increase with HTT turned on? I've heard it can penalize performance because the scheduler isn't optimized for logical CPUs. Does having HTT enabled impacts the stability of the system? - ACPI - I'll be disabling ACPI along with HTT to see if the server doesn't crash for awhile. Is ACPI on 5.3-STABLE (around November 1st, it was pre-release) still a problem? Last but not the least, my 5.3-STABLE version is from a few days before the release. Since I had created a few jails by then, I didn't upgrade the system to use the -RELEASE. Was there any last-standing problem a few days before the release that could be causing my instability problems? Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. Regards, Hugo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing troubles with Asus NCCH-DL Dual Xeon Board
Problem solved, the Promise controller was the reason for that abnormal rebooting within the BTX loader... disabling it for installation worked fine after installation, enabling the Promise Controller again did also work, FreeBSD is handling the mirrored disks correctly Cheers... now it's time for a beer =) At 17:57 22.10.2004, Contact wrote: I've just got a new machine to play with, for detailed specs of the machine see below... I've tried to install several releases of FreeBSD, 5.2.1 Release and the 5.3 RC1, but after some lines of boot initialisation, the machine just reboots without any further notice Normal Startup and BIOS checks then: Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX Loader BTX Loader 1.00 BTX version is 1.01 console: Internal video/keyboard here comes the REBOOT... I've searched the available mailinglists, but because the mainboard is quite new, I couldn't find anything related... Doe's anyone has any suggestions for solving that problem ? Could it be just a DVD ROM problem with Freebsd ? (I've read something about some incompatibalities...) (although Knopix boots correctly from that DVD ROM and can handle both processors...) Specs: Asus NCCH-DL Mainboard (Award BIOS v6.00PG, ACPI BIOS Revision 1003) Dual Intel Xeon 3.0 GHz 1MB Cache Intel 82875P/6300ESB Chipset (North/Southbridge) 1 x AGP Pro/8x 2 x 64-bit/66MHz PCI-X 2 x 32 bit/33MHz PCI 2 x SATA (support RAID 0/RAID 1) Promise PDC20319 4 x SATA Intel 82547GI Gigabit LAN TI TSB43AB22A IEEE 1394 and some standard Interfaces (like PS/2 keyboard mouseetc) LITE-ON DVD SOHD-167T 9S14 2 x 200 GB Raid over the Promise Controler (2 x ST3200822AS 3.01) 1 x 200 GB on the onboard SATA (ST3200822AS 3.01) Thanxs in advance ! PS: I'd like to thank you all for supporting FreeBSD, it's just the BEST OS ever build ! =) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing troubles with Asus NCCH-DL Dual Xeon Board
I've just got a new machine to play with, for detailed specs of the machine see below... I've tried to install several releases of FreeBSD, 5.2.1 Release and the 5.3 RC1, but after some lines of boot initialisation, the machine just reboots without any further notice Normal Startup and BIOS checks then: Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX Loader BTX Loader 1.00 BTX version is 1.01 console: Internal video/keyboard here comes the REBOOT... I've searched the available mailinglists, but because the mainboard is quite new, I couldn't find anything related... Doe's anyone has any suggestions for solving that problem ? Could it be just a DVD ROM problem with Freebsd ? (I've read something about some incompatibalities...) (although Knopix boots correctly from that DVD ROM and can handle both processors...) Specs: Asus NCCH-DL Mainboard (Award BIOS v6.00PG, ACPI BIOS Revision 1003) Dual Intel Xeon 3.0 GHz 1MB Cache Intel 82875P/6300ESB Chipset (North/Southbridge) 1 x AGP Pro/8x 2 x 64-bit/66MHz PCI-X 2 x 32 bit/33MHz PCI 2 x SATA (support RAID 0/RAID 1) Promise PDC20319 4 x SATA Intel 82547GI Gigabit LAN TI TSB43AB22A IEEE 1394 and some standard Interfaces (like PS/2 keyboard mouseetc) LITE-ON DVD SOHD-167T 9S14 2 x 200 GB Raid over the Promise Controler (2 x ST3200822AS 3.01) 1 x 200 GB on the onboard SATA (ST3200822AS 3.01) Thanxs in advance ! PS: I'd like to thank you all for supporting FreeBSD, it's just the BEST OS ever build ! =) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running FreeBSD/PostgreSQL on high-end dual Xeon box
Thanks guys! After doing some additional reading and your comments I think staying with FreeBSD coupled with a good RAID controller would probably be the least hassle, reliable, and good performing setup. I am looking at a dual Xeon box using an Adpatec 2200S RAID controller with the write buffer backup battery module. We will also probably install 4GB of ram. Now the new question is which RAID level would provide the best balance of performance and reliability... I currently have a similar setup that has RAID 0+1 with one hot spare ready in case of mirror disk failure. I had been considering the same setup, but it might make sense just to use 3 disk RAID5 with hot spare ready. The new RAID controller implementation might not buy us much by using 0+1 vs. 5. Any thoughts? -Kenji On Thu, Jun 03, 2004 at 06:40:07PM -0400, Charles Swiger wrote: On Jun 3, 2004, at 5:42 PM, Kenji M wrote: I am currently specing a 2U dual Xeon server and hope to use RAID 0+1 capability. The question is for PostgreSQL admins... 1) Which RAID controller should we use? You haven't mentioned whether you plan to use SCSI or IDE drives. The PERC RAID controller in Dell's PowerEdge's works quite well for the former, but you might consider the 3ware twe if you're doing IDE. 2) Considering Q1, does it not even make sense to use FreeBSD+PostgreSQL and bite the bullet and go with Linux (assuming it has better hw RAID support) and run PostgreSQL on that using a fancier journaling filesystem. Hmm. What makes you think that a journalling filesystem gains you much when you are running a database? Databases do their own transaction management using two-phase commit and logfiles for rollback in case of a crash using a few very large files, which they'll write to directly using async/directIO (whatever the term you wish to use is), rather than using OS/filesystem buffering -- -Chuck -- + kenji morishige [EMAIL PROTECTED] http://www.kenjim.com + ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running FreeBSD/PostgreSQL on high-end dual Xeon box
Kenji M wrote: I had been considering the same setup, but it might make sense just to use 3 disk RAID5 with hot spare ready. The new RAID controller implementation might not buy us much by using 0+1 vs. 5. Any thoughts? I doubt many databases recommend RAID-5; using RAID 0+1 is likely to be a better choice. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Running FreeBSD/PostgreSQL on high-end dual Xeon box
Hello everyone, first time list leech. I am in the process of speccing out a high end PC to be used as a database server for PostgreSQL. We are currently running MySQL on Linux, but want to migrate our code to PostgreSQL and we are primarily a FreeBSD shop. I am currently specing a 2U dual Xeon server and hope to use RAID 0+1 capability. The question is for PostgreSQL admins... 1) Which RAID controller should we use? 2) Considering Q1, does it not even make sense to use FreeBSD+PostgreSQL and bite the bullet and go with Linux (assuming it has better hw RAID support) and run PostgreSQL on that using a fancier journaling filesystem. Any comments greatly appreciated. -Kenji -- + kenji morishige [EMAIL PROTECTED] http://www.kenjim.com + ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running FreeBSD/PostgreSQL on high-end dual Xeon box
Kenji M [EMAIL PROTECTED] wrote: Hello everyone, first time list leech. I am in the process of speccing out a high end PC to be used as a database server for PostgreSQL. We are currently running MySQL on Linux, but want to migrate our code to PostgreSQL and we are primarily a FreeBSD shop. I am currently specing a 2U dual Xeon server and hope to use RAID 0+1 capability. The question is for PostgreSQL admins... 1) Which RAID controller should we use? Depends on your need. If you don't have outrageous requirements, vinum would work fine as software raid. If you have very high performance requirements, the general consensus on the Postgres lists is that a SCSI raid controller with a large battery-backed cache produces the best performing, most reliable systems. I don't have any specific model numbers, though. 2) Considering Q1, does it not even make sense to use FreeBSD+PostgreSQL and bite the bullet and go with Linux (assuming it has better hw RAID support) and run PostgreSQL on that using a fancier journaling filesystem. I doubt it. If you use battery-backed cache, you have no need of journalling. Even still, you get comparible performance with ufs+softupdates (although it's just a _little_ slower). Now, I've never done plug tests on UFS, but I haven't heard of any UFS filesystems getting beyond the point that PostgreSQL couldn't recover the database. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running FreeBSD/PostgreSQL on high-end dual Xeon box
On Jun 3, 2004, at 5:42 PM, Kenji M wrote: I am currently specing a 2U dual Xeon server and hope to use RAID 0+1 capability. The question is for PostgreSQL admins... 1) Which RAID controller should we use? You haven't mentioned whether you plan to use SCSI or IDE drives. The PERC RAID controller in Dell's PowerEdge's works quite well for the former, but you might consider the 3ware twe if you're doing IDE. 2) Considering Q1, does it not even make sense to use FreeBSD+PostgreSQL and bite the bullet and go with Linux (assuming it has better hw RAID support) and run PostgreSQL on that using a fancier journaling filesystem. Hmm. What makes you think that a journalling filesystem gains you much when you are running a database? Databases do their own transaction management using two-phase commit and logfiles for rollback in case of a crash using a few very large files, which they'll write to directly using async/directIO (whatever the term you wish to use is), rather than using OS/filesystem buffering -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DUAL XEON 2.40Mhz SMP APIC_IO Troubles
Hi!!! I have a ProLiant Dual XEON at 2.4Mhz running FreeBSD 5.0 configured as it follows: machine i386 cpu I686_CPU options SMP options APIC_IO But every time the system boots stop running at kernel message: APIC_IO: Testing 8254 Interrupt Delivery and go freezed forever. Does someone have a tip or solution = Gabor Net/Sys Admin __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
tyan dual xeon 1800 + vmware.2.0.4.1142 Trap 12
hi, i have a production box where i need one w2k server running on top of freebsd 4.7. all tests on single cpu boxes was working great including suspend on shutdown and automatic boot w2k on freebsds startup. now i installed it onto the production box and start vmware via vncserver. i see w2k booting and before the final booting screen disappears where it would switch i get a trap 12 and the box reboots. are there any known problems with smp systems and vmware? single cpu systems works just great. 60 GB real data on the box and no way to play around with it. only chance would be to tell the customer we need 1 adittional box for it. but then i would have to install one linux box there and i want to stay with freebsd because all customer boxes are freebsd. i updated everything to the latest software via ports cvsuped today. man thanks, best regards, karl Feb 6 23:29:29 sv00 syslogd: restart Feb 6 23:29:29 sv00 /kernel: Feb 6 23:29:29 sv00 /kernel: Feb 6 23:29:29 sv00 /kernel: Fatal trap 12: page fault while in kernel mode Feb 6 23:29:29 sv00 /kernel: mp_lock = 0202; cpuid = 2; lapic.id = 0600 Feb 6 23:29:29 sv00 /kernel: fault virtual address = 0x5e3a860 Feb 6 23:29:29 sv00 /kernel: fault code = supervisor read, page not present Feb 6 23:29:29 sv00 /kernel: instruction pointer = 0x8:0xc38e2f3c Feb 6 23:29:29 sv00 /kernel: stack pointer = 0x10:0xe05febb8 Feb 6 23:29:29 sv00 /kernel: frame pointer = 0x10:0xe05febbc Feb 6 23:29:29 sv00 /kernel: code segment = base 0x0, limit 0xf, type 0x1b Feb 6 23:29:29 sv00 /kernel: = DPL 0, pres 1, def32 1, gran 1 Feb 6 23:29:29 sv00 /kernel: processor eflags = interrupt enabled, resume, IOPL = 3 Feb 6 23:29:29 sv00 /kernel: current process = 718 (vmware) Feb 6 23:29:29 sv00 /kernel: interrupt mask = none - SMP: XXX Feb 6 23:29:29 sv00 /kernel: trap number = 12 Feb 6 23:29:29 sv00 /kernel: panic: page fault Feb 6 23:29:29 sv00 /kernel: mp_lock = 0202; cpuid = 2; lapic.id = 0600 Feb 6 23:29:29 sv00 /kernel: boot() called on cpu#2 Feb 6 23:29:29 sv00 /kernel: Feb 6 23:29:29 sv00 /kernel: syncing disks... 67 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 63 Feb 6 23:29:29 sv00 /kernel: P 127.0.0.1:512 from 127.0.0.1:1456 Feb 6 23:29:29 sv00 /kernel: Feb 6 23:01:44 sv00 /kernel: Connection attempt to UDP 127.0.0.1:512 from 127.0.0.1:1456 Feb 6 23:29:29 sv00 /kernel: Feb 6 23:03:44 sv00 su: joch to root on /dev/ttyp1 Feb 6 23:29:29 sv00 /kernel: Feb 6 23:10:04 sv00 shutdown: reboot by jochCPUs Feb 6 23:29:29 sv00 /kernel: cpu_reset: Restarting BSP Feb 6 23:29:29 sv00 /kernel: Copyright (c) 1992-2003 The FreeBSD Project. Feb 6 23:29:29 sv00 /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 6 23:29:29 sv00 /kernel: The Regents of the University of California. All rights reserved. Feb 6 23:29:29 sv00 /kernel: FreeBSD 4.7-STABLE #4: Thu Feb 6 19:47:37 CET 2003 Feb 6 23:29:29 sv00 /kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CTSDUALCPU Feb 6 23:29:29 sv00 /kernel: Timecounter i8254 frequency 1193182 Hz Feb 6 23:29:29 sv00 /kernel: CPU: Intel(R) XEON(TM) CPU 1.80GHz (1799.80-MHz 686-class CPU) Feb 6 23:29:29 sv00 /kernel: Origin = GenuineIntel Id = 0xf24 Stepping = 4 Feb 6 23:29:29 sv00 /kernel: Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM Feb 6 23:29:29 sv00 /kernel: Hyperthreading: 2 logical CPUs Feb 6 23:29:29 sv00 /kernel: real memory = 1073741824 (1048576K bytes) Feb 6 23:29:29 sv00 /kernel: avail memory = 1040289792 (1015908K bytes) Feb 6 23:29:29 sv00 /kernel: Programming 24 pins in IOAPIC #0 Feb 6 23:29:29 sv00 /kernel: IOAPIC #0 intpin 2 - irq 0 Feb 6 23:29:29 sv00 /kernel: Programming 24 pins in IOAPIC #1 Feb 6 23:29:29 sv00 /kernel: Programming 24 pins in IOAPIC #2 Feb 6 23:29:29 sv00 /kernel: FreeBSD/SMP: Multiprocessor motherboard Feb 6 23:29:29 sv00 /kernel: cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 Feb 6 23:29:29 sv00 /kernel: cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 Feb 6 23:29:29 sv00 /kernel: cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee0 Feb 6 23:29:29 sv00 /kernel: cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 Feb 6 23:29:29 sv00 /kernel: io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec0 Feb 6 23:29:29 sv00 /kernel: io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec8 Feb 6 23:29:29 sv00 /kernel: io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec80400 Feb 6 23:29:29 sv00 /kernel: Preloaded elf kernel kernel at 0xc04b9000. Feb 6 23:29:29 sv00 /kernel: Pentium Pro MTRR support enabled Feb 6 23:29:29 sv00 /kernel: md0: Malloc disk Feb 6 23:29:29 sv00 /kernel: Using $PIR table, 14 entries at 0xc00f3f80 Feb 6 23:29:29 sv00 /kernel: npx0: math processor on motherboard Feb 6 23:29:29 sv00 /kernel: npx0:
