From owner-freebsd-hardware Mon Mar 25 9:34:50 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from highland.isltd.insignia.com (highland.isltd.insignia.com [195.74.141.1]) by hub.freebsd.org (Postfix) with ESMTP id 16CF837B417 for ; Mon, 25 Mar 2002 09:34:43 -0800 (PST) Received: from wolf.isltd.insignia.com (wolf.isltd.insignia.com [172.16.1.3]) by highland.isltd.insignia.com (8.11.6/8.11.6) with ESMTP id g2PHYar75157 for ; Mon, 25 Mar 2002 17:34:36 GMT Received: (from news@localhost) by wolf.isltd.insignia.com (8.9.3/8.9.3) id RAA10155 for freebsd-hardware@freebsd.org; Mon, 25 Mar 2002 17:34:36 GMT From: freebsd-hardware-local@insignia.com To: freebsd-hardware@freebsd.org Subject: Re: Very Small Computer Systems Date: Mon, 25 Mar 2002 17:34:35 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 22 Mar 2002 07:57:11 -0600 (CST), tech@tznet.com (Scott Pilz) wrote: > I'm curious, does anyone know where to buy very small (possibly >rack mountable but not needed that badly) computer systems that run good >on BSD for cheap? I realize that the requirements I'm looking for are not >even made anymore (p450, 128mb of ram would be fine) so as far as speed >goes, a low end profile would be fine. Cost is important however - cheaper >the better. I'm running an Asus Terminator Tualatin. Nice and quiet and fairly cheap. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Mar 25 13:39:20 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 08C2637B41B for ; Mon, 25 Mar 2002 13:38:52 -0800 (PST) Received: (from ixian@localhost) by idiom.com (8.9.3/8.9.3) id NAA94852; Mon, 25 Mar 2002 13:38:51 -0800 (PST) X-Authentication-Warning: idiom.com: ixian set sender to ixian@idiom.com using -f MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15519.39147.668043.880532@idiom.com> Date: Mon, 25 Mar 2002 13:38:51 -0800 (PST) From: Eric De Mund To: freebsd-hardware@FreeBSD.ORG Subject: Re: Very Small Computer Systems X-Mailer: VM 6.75 under Emacs 20.4.1 Reply-To: Eric De Mund X-Humans-Reply-To: Eric De Mund X-URL: X-POM: The Moon is Waxing Gibbous (88% of Full) Organization: Ixian Systems, Inc. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Scott Pilz : ] I'm curious, does anyone know where to buy very small (possibly rack ] mountable but not needed that badly) computer systems that run good on ] BSD for cheap? I realize that the requirements I'm looking for are not ] even made anymore (p450, 128mb of ram would be fine) so as far as ] speed goes, a low end profile would be fine. Cost is important however ] - cheaper the better. Jim : ] I'm running an Asus Terminator Tualatin. Nice and quiet and fairly ] cheap. Thanks for this. I found: Personal Computers (barebone and mini barebone systems) http://www.shentech.com/pcpercom.html , and the mini barebone systems look very neat. Now, if I could only find a mini (as opposed to regular) barebone system like the Shuttle SV24 or SV25 that supports AMD processors. Anyone? Also, is anyone here successfully using the VIA C3 "Ezra" processor? I prefer not to use Intel processors, and I do like the idea of passive CPU cooling being sufficient. Regards, Eric -- Eric De Mund | Ixian Systems, Inc. | 53 49 B2 23 AF 6C 20 81 http://www.ixian.com/ead/ | Mountain View, CA | ED DD 4C 81 AA C9 D1 A5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 12:34:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id 8834C37B405 for ; Tue, 26 Mar 2002 12:34:09 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id 806D1D983; Tue, 26 Mar 2002 15:30:56 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 70A60D982 for ; Tue, 26 Mar 2002 15:30:56 -0500 (EST) Date: Tue, 26 Mar 2002 15:30:56 -0500 (EST) From: David Miller To: freebsd-hardware@FreeBSD.ORG Subject: RAID: Adaptec vs Mylex Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Any input from real world users on the subject? I'm most interested in the 3210S and 352. My use would be with RAID 10 support of a busy database server doing zillions of writes/updates. Speed writing small blocks is of the essence. Reliability, robustness, speed are critical factors. It will be hooked up to 10 or 12 15K drives. Input? Thanks, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 12:49:45 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from beck.quonix.net (beck.quonix.net [64.239.136.146]) by hub.freebsd.org (Postfix) with ESMTP id 12B4337B417 for ; Tue, 26 Mar 2002 12:49:41 -0800 (PST) Received: from [192.168.1.100] (pa-steclge-u1-c6b-396.stcgpa.adelphia.net [24.54.121.140]) by beck.quonix.net (8.11.6/8.11.6) with ESMTP id g2QKebv64052; Tue, 26 Mar 2002 12:40:37 -0800 (PST) (envelope-from john@essenz.com) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Tue, 26 Mar 2002 15:46:41 -0500 Subject: Re: RAID: Adaptec vs Mylex From: John Von Essen To: David Miller , Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David, We have used both Mylex and Adaptec RAID Cards. We stopped using Mylex because those cards had drive compatibility problems. Some Quantum 10k drives would work with the Mylex card. Ever since that, we've been using Adaptec 2100S, 3200S, and 2400A Raid cards in our rack servers. In all the servers we have built with Adaptec cards, not one has had a single problem. Some units have been running non-stop for almost two years. So I would definitely recommend going with the Adaptec cards. Not to mention that Adaptec has made a commitment to provide FreeBSD support on their RAID products (i.e. drivers). John Von Essen President, Essenz Consulting (www.essenz.com) EMAIL: john@essenz.com DIRECT PHONE: (800) 248-1736 International: +01 814 861 0922 on 3/26/02 3:30 PM, dmiller@sparks.net wrote: > Any input from real world users on the subject? I'm most interested in > the 3210S and 352. My use would be with RAID 10 support of a busy > database server doing zillions of writes/updates. Speed writing small > blocks is of the essence. > > Reliability, robustness, speed are critical factors. It will be hooked up > to 10 or 12 15K drives. > > Input? > > Thanks, > > --- David > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 12:50:54 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 34A3837B405 for ; Tue, 26 Mar 2002 12:50:50 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g2QKoj104400; Tue, 26 Mar 2002 13:50:45 -0700 (MST) (envelope-from ken) Date: Tue, 26 Mar 2002 13:50:45 -0700 From: "Kenneth D. Merry" To: David Miller Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: RAID: Adaptec vs Mylex Message-ID: <20020326135045.A4301@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from dmiller@sparks.net on Tue, Mar 26, 2002 at 03:30:56PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Mar 26, 2002 at 15:30:56 -0500, David Miller wrote: > Any input from real world users on the subject? I'm most interested in > the 3210S and 352. My use would be with RAID 10 support of a busy > database server doing zillions of writes/updates. Speed writing small > blocks is of the essence. > > Reliability, robustness, speed are critical factors. It will be hooked up > to 10 or 12 15K drives. > > Input? If you want a comparison of the two controllers: http://www.adaptec.com/worldwide/product/markeditorial.html?prodkey=3210_wp&type=Common&cat=%2fCommon%2fRAID+Upgrade The only catch is that the comparison was done with RAID-5, not RAID-10. So the read speed in the benchmarks above may be comparable to RAID-10, but the write speed for RAID-10 should be better. If you want high performance with lots of small chunks of data, I would recommend the Adaptec 5400S. It has a hardware parity engine that speeds up RAID-5 writes significantly. (If you're only doing RAID-10, though, it won't have any effect.) (disclaimer: I work for Adaptec.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 13:33:40 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id E570237B416 for ; Tue, 26 Mar 2002 13:33:33 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id 49A76D983; Tue, 26 Mar 2002 16:30:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 3B939D982; Tue, 26 Mar 2002 16:30:21 -0500 (EST) Date: Tue, 26 Mar 2002 16:30:21 -0500 (EST) From: David Miller To: "Kenneth D. Merry" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: RAID: Adaptec vs Mylex In-Reply-To: <20020326135045.A4301@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 26 Mar 2002, Kenneth D. Merry wrote: > On Tue, Mar 26, 2002 at 15:30:56 -0500, David Miller wrote: > > Any input from real world users on the subject? I'm most interested in > > the 3210S and 352. My use would be with RAID 10 support of a busy > > database server doing zillions of writes/updates. Speed writing small > > blocks is of the essence. > > > > Reliability, robustness, speed are critical factors. It will be hooked up > > to 10 or 12 15K drives. > > > > Input? > > If you want a comparison of the two controllers: > > http://www.adaptec.com/worldwide/product/markeditorial.html?prodkey=3210_wp&type=Common&cat=%2fCommon%2fRAID+Upgrade Mylex has one on their site: (gawd frames are awful) http://www.mylex.com/products/index.html -> competitive analysis -> AcceleRAID 352 vs Adaptec 3200S (choose PDF). Naturally, it show the mylex adapter way out front. > The only catch is that the comparison was done with RAID-5, not RAID-10. Unfortunately, that makes is pretty useless for me. The two analysis look pretty far apart to start with, but when you look at the details they may complement each other pretty well. Mylex wouldn't call attention to it, of course, but area Adaptec beat it in pretty thoroughly was with big blocks, espcecially with sequential IO and write back enabled. That area is what the adaptec benchmark homes right in on, so they're not in violent disagreement. Other differences were in the disk setup - adaptec used 8 drives on four channels. Mylex used 18 drives on two channels. It may be that Mylex can handle more total commands, but if you don't have enough drives it just doesn't matter because the disks are the bottleneck. What I'm trying to sort out is whether there would be any real world performance difference to me in using either of them when updating 20 million 60 byte records in a 160 million row table. > So the read speed in the benchmarks above may be comparable to RAID-10, > but the write speed for RAID-10 should be better. > > If you want high performance with lots of small chunks of data, I would > recommend the Adaptec 5400S. It has a hardware parity engine that speeds > up RAID-5 writes significantly. (If you're only doing RAID-10, though, it > won't have any effect.) I think I really need the performance of raid 10. The database is small enough that space efficiency is not an issue. Lots of little IO's - mostly O's - are what really counts. Occasionally, handling directories with 10K entries is an issue, so I'll probably want write-back enabled. > (disclaimer: I work for Adaptec.) Full disclosure, but not necessary around these parts. Your reputation preceeds you Ken:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 17: 5:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mighty.grot.org (mighty.grot.org [204.182.56.120]) by hub.freebsd.org (Postfix) with ESMTP id 540F437B404 for ; Tue, 26 Mar 2002 17:05:54 -0800 (PST) Received: by mighty.grot.org (Postfix, from userid 515) id 6EF325E9D; Tue, 26 Mar 2002 17:05:48 -0800 (PST) Date: Tue, 26 Mar 2002 17:05:48 -0800 From: Aditya To: freebsd-hardware@freebsd.org Subject: serial console vs. serial terminal Message-ID: <20020327010548.GA78994@mighty.grot.org> Reply-To: Aditya Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://www.grot.org/pubkey.asc X-PGP-Key-ID: 0x6405D8D5 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This has me entirely confused so any hints are very appreciated. I have 3 different types of motherboards running FreeBSD 4-STABLE all in various states of cvsup but none older than 2 weeks ago. Using a null modem cable from one of them I can connect to each of the serial ports and get a login prompt as per what I have for ttyd0 in /etc/ttys: ttyd0 "/usr/libexec/getty std.9600" dialup on secure however, if I connect to them from a Cyclades T2000 terminal server using a cat5 patch cable and a RJ45-DB9F modular adapter I can't type anything in but I do see output (ie. from syslog). The most bizzare thing is if I reboot with: set console=comconsole in /boot/loader.rc it works fine with the Cyclades...that is, booting up, I see: sio0: type 16550A, console rather than: sio0: type 16550A So what is it about explictly setting sio0 to be the console that changes the serial line discipline? Connecting with a regular null modem cable seems to be unaffected in either case. Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 20:13:38 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from cyberspace7.legions.org (mail.legions.org [66.12.11.166]) by hub.freebsd.org (Postfix) with ESMTP id DEEFD37B405 for ; Tue, 26 Mar 2002 20:13:34 -0800 (PST) Received: from localhost (shadows@localhost) by cyberspace7.legions.org (8.11.3/8.10.1) with ESMTP id g2R3vap18879 for ; Tue, 26 Mar 2002 21:57:36 -0600 (CST) Date: Tue, 26 Mar 2002 21:57:35 -0600 (CST) From: shadows To: freebsd-hardware@freebsd.org Subject: Getting Maestro-3i to work in FreeBSD 4.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey guys/girls, Ok here goes. I have a Dell Lattitude CPxJ650GT with a builtin Maestro-3i sound card. I was referencing the following information from http://www.cs.duke.edu/~anderson/freebsd/maestro3xxx/ to get to where I am now. Add the following to your kernel config file: device pcm0 at isa? irq 10 drq 1 flags 0x0 # for non-PnP sound cards device pcm # for PnP/PCI sound cards Then after doing that I believe during the boot sequence I got a message stating to the fact that the driver cannot be loaded through the kernel due to licensing restrictions and to add a line to my loader.conf which was the following snd_maestro3_load="YES" Now when I do a cat /dev/sndstat instead of device not configured I get the following. # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Mar 25 2002 14:26:45 Installed devices: pcm0: at io 0xd800 irq 5 (1p/1r/0v channels duplex) But when I do startx with KDE I get the following message Sound Server Informational Message Error while initializing the sound driver device /dev/desp can't be opened (Device not configured) The sound server will continue, using the null output device Ok well that sucks. So I popped up a shell and did cat /dev/dsp and cat /dev/audio and both say Device not configured? Can anyone tell me what exactly I did wrong if anything and possibly a fix. Would be most Appreciated Thanks Thomas B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 22:29:54 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from testdcc.outblaze.com (202-77-223-23.outblaze.com [202.77.223.23]) by hub.freebsd.org (Postfix) with ESMTP id 4611C37B417 for ; Tue, 26 Mar 2002 22:29:42 -0800 (PST) Received: from ws3.hk5.outblaze.com (202-77-181-90.outblaze.com [202.77.181.90]) by testdcc.outblaze.com (8.12.2/8.12.2) with SMTP id g2R6Temv027721 for ; Wed, 27 Mar 2002 06:29:40 GMT Received: (qmail 9252 invoked by uid 1001); 27 Mar 2002 06:29:40 -0000 Message-ID: <20020327062940.9251.qmail@graffiti.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [66.51.217.108] by ws3.hk5.outblaze.com with http for derekbarrett@graffiti.net; Wed, 27 Mar 2002 14:29:40 +0800 From: "Derek Barrett" To: , "Kenneth D. Merry" Cc: freebsd-hardware@FreeBSD.ORG Date: Wed, 27 Mar 2002 14:29:40 +0800 Subject: Re: RAID: Adaptec vs Mylex X-Originating-Ip: 66.51.217.108 X-Originating-Server: ws3.hk5.outblaze.com X-DCC-Outblaze-Metrics: testdcc.outblaze.com 100; env_From=1 From=1 Message-ID=1 Received=1 Body=1 Fuz1=1 Fuz2=1 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have no experience with Adaptec SCSI, but we chose the Adaptec 2400A (ATA) for a new box because of its friendly compatibility. FreeBSD instantly recognizes the card, and Adaptec has built native FreeBSD management utilities that will pretty painlessly install onto an X desktop. (Well sometimes the instructions are hard to find -- gotta look in the release notes, not the manual -- but once you find them, you can just add a package and run a setup script). One caveat with this card is that, if you chose RAID10, you can only have a stripe size of 64K. So for those of you running a database where you need a smaller block size, like 8 or 16, you would need to run RAID5, which is what we are running, even though we wanted RAID10. Though being a newbie to RAID10, I am thinking that having a smaller stripe size on RAID10 would negate its speed advantage anyway? Does anyone use a smaller stripe size on their RAID10 than 64K? ----- Original Message ----- From: David Miller Date: Tue, 26 Mar 2002 16:30:21 -0500 (EST) To: "Kenneth D. Merry" Subject: Re: RAID: Adaptec vs Mylex > On Tue, 26 Mar 2002, Kenneth D. Merry wrote: > > > On Tue, Mar 26, 2002 at 15:30:56 -0500, David Miller wrote: > > > Any input from real world users on the subject? I'm most interested in > > > the 3210S and 352. My use would be with RAID 10 support of a busy > > > database server doing zillions of writes/updates. Speed writing small > > > blocks is of the essence. > > > > > > Reliability, robustness, speed are critical factors. It will be hooked up > > > to 10 or 12 15K drives. > > > > > > Input? > > > > If you want a comparison of the two controllers: > > > > http://www.adaptec.com/worldwide/product/markeditorial.html?prodkey=3210_wp&type=Common&cat=%2fCommon%2fRAID+Upgrade > > Mylex has one on their site: (gawd frames are awful) > http://www.mylex.com/products/index.html -> competitive analysis -> > AcceleRAID 352 vs Adaptec 3200S (choose PDF). > > Naturally, it show the mylex adapter way out front. > > > > The only catch is that the comparison was done with RAID-5, not RAID-10. > > Unfortunately, that makes is pretty useless for me. > > > The two analysis look pretty far apart to start with, but when you look > at the details they may complement each other pretty well. Mylex wouldn't > call attention to it, of course, but area Adaptec beat it in pretty > thoroughly was with big blocks, espcecially with sequential IO and write > back enabled. > > That area is what the adaptec benchmark homes right in on, so they're not > in violent disagreement. > > Other differences were in the disk setup - adaptec used 8 drives on four > channels. Mylex used 18 drives on two channels. It may be that Mylex can > handle more total commands, but if you don't have enough drives it just > doesn't matter because the disks are the bottleneck. What I'm trying to > sort out is whether there would be any real world performance difference > to me in using either of them when updating 20 million 60 byte records in > a 160 million row table. > > > > So the read speed in the benchmarks above may be comparable to RAID-10, > > but the write speed for RAID-10 should be better. > > > > If you want high performance with lots of small chunks of data, I would > > recommend the Adaptec 5400S. It has a hardware parity engine that speeds > > up RAID-5 writes significantly. (If you're only doing RAID-10, though, it > > won't have any effect.) > > I think I really need the performance of raid 10. The database is small > enough that space efficiency is not an issue. Lots of little IO's - > mostly O's - are what really counts. Occasionally, handling directories > with 10K entries is an issue, so I'll probably want write-back enabled. > > > (disclaimer: I work for Adaptec.) > > Full disclosure, but not necessary around these parts. Your reputation > preceeds you Ken:) > > --- David > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > > -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Mar 26 23:20:40 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from testdcc.outblaze.com (202-77-223-23.outblaze.com [202.77.223.23]) by hub.freebsd.org (Postfix) with ESMTP id A50F437B404 for ; Tue, 26 Mar 2002 23:20:32 -0800 (PST) Received: from ws3.hk5.outblaze.com (202-77-181-90.outblaze.com [202.77.181.90]) by testdcc.outblaze.com (8.12.2/8.12.2) with SMTP id g2R7KUmv029730 for ; Wed, 27 Mar 2002 07:20:30 GMT Received: (qmail 21998 invoked by uid 1001); 27 Mar 2002 07:20:30 -0000 Message-ID: <20020327072030.21997.qmail@graffiti.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [66.51.217.108] by ws3.hk5.outblaze.com with http for derekbarrett@graffiti.net; Wed, 27 Mar 2002 15:20:30 +0800 From: "Derek Barrett" To: "David Miller" Cc: freebsd-hardware@FreeBSD.ORG Date: Wed, 27 Mar 2002 15:20:30 +0800 Subject: Re: RAID: Adaptec vs Mylex X-Originating-Ip: 66.51.217.108 X-Originating-Server: ws3.hk5.outblaze.com X-DCC-Outblaze-Metrics: testdcc.outblaze.com 100; env_From=8 From=8 Message-ID=2 Received=2 Body=2 Fuz1=2 Fuz2=2 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We chose the Adaptec 2400A for its friendly compatibility with FreeBSD. FreeBSD 4.4 and 4.5 have both detected it instantly, and there were no conflicts with another RAID card in our chassis, it liked both. Adaptec seems to be the only company out there that goes out of its way to support ATA RAID for FreeBSD. Of all the companies we looked at, support was marginal at best. Though the SCSI cards had alot more FreeBSD support. The RAID utilities that come with it also have native FreeBSD versions, one is written as a package, and another will install through a setup script. Very handy. 2400A supports RAID0,1,5, and 10. I read today some documentation regarding RAID 0/5, but we only have one Adaptec card right now so I don't know if that is working on this particular this card. Another comment is that their customer service seems to be well done from what I have seen so far. I asked a couple of questions by email last night, and they were responded back today, and the answers they gave me were very helpful and professional. The only thing I was disappointed about was that we could not change the stripe size on RAID10 (which is set to 64K). You can change the stripe size on the RAID0 and RAID5, they go from 8K to 256K. So we are using RAID5 with a 16K stripe size. For you database users using smaller block sizes, it looks like you'd have to stick with RAID5 on this card. Does anyone out there use a small stripe size on their RAID10? Like 8K or 16K? Does going to the small stripe size defeat the purpose of the RAID10, and possibly that's why it is stuck at 64K on this card? (In this case, since there are two RAID 1 arrays within the RAID0, the actual stripe to those becomes 32K, since 64/2 = 32K, but that's still too big for our purposes). > On Tue, 26 Mar 2002 15:30:56 -0500 (EST), "David Miller" > <.ndmiller@sparkset> said: > > Any input from real world users on the subject? I'm most interested in > > the 3210S and 352. My use would be with RAID 10 support of a busy > > database server doing zillions of writes/updates. Speed writing small > > blocks is of the essence. > > > > Reliability, robustness, speed are critical factors. It will be hooked > > up > > to 10 or 12 15K drives. > > > > Input? > > > > Thanks, > > > > --- David > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > > > -- > > derekbarrett@fastmail.fm > > -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 3:59:20 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B7CA037B419 for ; Wed, 27 Mar 2002 03:59:16 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA03875; Wed, 27 Mar 2002 22:59:12 +1100 Date: Wed, 27 Mar 2002 22:59:44 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Aditya Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: serial console vs. serial terminal In-Reply-To: <20020327010548.GA78994@mighty.grot.org> Message-ID: <20020327224559.W4007-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 26 Mar 2002, Aditya wrote: > [Lots deleted...] > So what is it about explictly setting sio0 to be the console that changes the > serial line discipline? Connecting with a regular null modem cable seems to be > unaffected in either case. The relevant difference is probably that clocal is turned on and locked on for the console. clocal makes some modem control signals unnecessary. Null modem cables aren't standard enough to always fake all the necessary control signals like the driver wants. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 5:52: 3 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 5ECC437B400 for ; Wed, 27 Mar 2002 05:52:01 -0800 (PST) Received: from comcast.net (pcp749081pcs.manass01.va.comcast.net [68.49.123.104]) by mtaout45-02.icomcast.net (iPlanet Messaging Server 5.1 (built Feb 6 2002)) with ESMTP id <0GTM00I68X6OLJ@mtaout45-02.icomcast.net> for freebsd-hardware@FreeBSD.ORG; Wed, 27 Mar 2002 08:52:00 -0500 (EST) Date: Wed, 27 Mar 2002 08:46:36 -0500 From: David Carnes Subject: Re: Very Small Computer Systems To: freebsd-hardware@FreeBSD.ORG Cc: Eric De Mund Message-id: <3CA1CD3C.DE5FC59E@comcast.net> MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <15519.39147.668043.880532@idiom.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Shuttle (http://www.shuttleonline.com) has just announced an AMD Athlon XP system, the SS40 (http://www.shuttleonline.com/spec.php3?model=ss40), and a Pentium 4 system, the SS50 (http://www.shuttleonline.com/spec.php3?model=ss50). I have not seen any listing at www.pricewatch.com yet. Hope this helps, Dave Eric De Mund wrote: > , and the mini barebone systems look very neat. Now, if I could only > find a mini (as opposed to regular) barebone system like the Shuttle > SV24 or SV25 that supports AMD processors. Anyone? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 6: 7: 0 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 6715E37B400 for ; Wed, 27 Mar 2002 06:06:48 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 5509616B1C for ; Wed, 27 Mar 2002 15:06:46 +0100 (CET) Received: from LenConrad.Go2France.com [193.252.44.38] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A6EB182E0372; Wed, 27 Mar 2002 15:27:55 +0100 Message-Id: <5.1.0.14.2.20020327080533.03508e98@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 27 Mar 2002 08:06:42 -0600 To: freebsd-hardware@FreeBSD.ORG From: Len Conrad Subject: Re: Very Small Computer Systems In-Reply-To: <3CA1CD3C.DE5FC59E@comcast.net> References: <15519.39147.668043.880532@idiom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Shuttle (http://www.shuttleonline.com) has just announced an AMD Athlon >XP system, the SS40 (http://www.shuttleonline.com/spec.php3?model=ss40) Realtek 8100B 10/100Mb Fast Ethernet LAN Realtek has a bad rep on all the lists I follow Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 6:25:39 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 11A7E37B41B for ; Wed, 27 Mar 2002 06:25:36 -0800 (PST) Received: from [192.168.1.102] (pcp749081pcs.manass01.va.comcast.net [68.49.123.104]) by mtaout02.icomcast.net (iPlanet Messaging Server 5.1 (built Feb 6 2002)) with ESMTP id <0GTM000SYYQNLD@mtaout02.icomcast.net> for freebsd-hardware@FreeBSD.ORG; Wed, 27 Mar 2002 09:25:35 -0500 (EST) Date: Wed, 27 Mar 2002 09:20:11 -0500 From: David Carnes Subject: Re: Very Small Computer Systems In-reply-to: <5.1.0.14.2.20020327080533.03508e98@mail.Go2France.com> To: freebsd-hardware@FreeBSD.ORG Message-id: <1017238812.1862.10.camel@bilge.manss1.va.home.com> MIME-version: 1.0 X-Mailer: Evolution/1.0.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <15519.39147.668043.880532@idiom.com> <5.1.0.14.2.20020327080533.03508e98@mail.Go2France.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org While Realtek would not be my choice for server ethernet, it may be fine for a lightly stressed/home system. In any case, the shuttle systems have 2 PCI slots, so the ethernet card of your choice could be substituted. Dave On Wed, 2002-03-27 at 09:06, Len Conrad wrote: > > >Shuttle (http://www.shuttleonline.com) has just announced an AMD > > Athlon XP system, the SS40 > > (http://www.shuttleonline.com/spec.php3?model=ss40) > > Realtek 8100B > 10/100Mb Fast Ethernet LAN > > Realtek has a bad rep on all the lists I follow > > Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 10:20:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailrtr04.ntelos.net (mailrtr04.ntelos.net [216.12.0.104]) by hub.freebsd.org (Postfix) with ESMTP id 279C337B405 for ; Wed, 27 Mar 2002 10:20:53 -0800 (PST) Received: from thunderbolt.net.cfw.com (thunderbolt.net.cfw.com [216.12.8.195]) by mailrtr04.ntelos.net (8.12.1/8.12.1) with ESMTP id g2RIKqCR021212 for ; Wed, 27 Mar 2002 13:20:52 -0500 Subject: Re: Very Small Computer Systems From: Eric Sproul To: FreeBSD Hardware In-Reply-To: <3CA1CD3C.DE5FC59E@comcast.net> References: <15519.39147.668043.880532@idiom.com> <3CA1CD3C.DE5FC59E@comcast.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 27 Mar 2002 13:20:51 -0500 Message-Id: <1017253252.5037.126.camel@thunderbolt.net.cfw.com> Mime-Version: 1.0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 2002-03-27 at 08:46, David Carnes wrote: > Shuttle (http://www.shuttleonline.com) has just announced an AMD Athlon > XP system, the SS40 (http://www.shuttleonline.com/spec.php3?model=ss40), > and a Pentium 4 system, the SS50 > (http://www.shuttleonline.com/spec.php3?model=ss50). I have not seen > any listing at www.pricewatch.com yet. VIAHardware.com has a preview: http://www.viahardware.com/ss50preview.shtm Improvements over the original SV24 include 2 vertical PCI slots (no more crowded riser card) and front-mounted Firewire port. I'm sure there's more, I just haven't read the whole article yet. :) Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 14:23:58 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from freebsdsystems.com (gw.freebsdsystems.com [216.126.78.90]) by hub.freebsd.org (Postfix) with ESMTP id BE79B37B404 for ; Wed, 27 Mar 2002 14:23:53 -0800 (PST) Received: (qmail 75112 invoked from network); 27 Mar 2002 22:23:52 -0000 Received: from unknown (HELO there) (216.126.94.34) by panda.freebsdsystems.com with SMTP; 27 Mar 2002 22:23:52 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Lanny Baron Organization: FreeBSD Systems; Freedom Technologies Corp. To: Scott Pilz , freebsd-hardware@freebsd.org Subject: Re: Very Small Computer Systems Date: Wed, 27 Mar 2002 17:23:52 -0500 X-Mailer: KMail [version 1.3.2] References: <20020322075520.E21453-100000@mail.tznet.com> In-Reply-To: <20020322075520.E21453-100000@mail.tznet.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020327222353.BE79B37B404@hub.freebsd.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Depends what you call 'cheap'. We have one for 799 + shipping. Lanny Baron On March 22, 2002 08:57 am, Scott Pilz wrote with respect to Very Small Computer Systems: > I'm curious, does anyone know where to buy very small (possibly > rack mountable but not needed that badly) computer systems that run > good on BSD for cheap? I realize that the requirements I'm looking > for are not even made anymore (p450, 128mb of ram would be fine) so > as far as speed goes, a low end profile would be fine. Cost is > important however - cheaper the better. > > I need something that looks "nice" but is very small - if rack > mountable, 1U and not very deep. Any ideas? > > Thanks, > > Scott > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- +~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~ Lanny Baron Proud to be 100% FreeBSD FreeBSD Systems, Inc http://www.FreeBSDsystems.COM 1.877.963.1900 +~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~ And your daily fortune is: Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 17: 4:47 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from merlin.bogen.org (adsl-216-103-84-120.dsl.snfc21.pacbell.net [216.103.84.120]) by hub.freebsd.org (Postfix) with ESMTP id 0763937B405 for ; Wed, 27 Mar 2002 17:04:37 -0800 (PST) Received: from bogen.org (localhost [127.0.0.1]) by merlin.bogen.org (8.11.6/8.11.6) with ESMTP id g2S14Zk00584 for ; Wed, 27 Mar 2002 17:04:36 -0800 (PST) (envelope-from db@bogen.org) Message-ID: <3CA26C23.1040906@bogen.org> Date: Wed, 27 Mar 2002 17:04:35 -0800 From: David Bogen User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020207 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hardware@freebsd.org Subject: 4.5-RELEASE and AMD K6-2 not playing nice together Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Until last evening, one of my home PCs had been running 4.3-STABLE. Before that, this PC ran nearly every RELEASE and/or STABLE from 3.4 forward. The system was rock solid and --never-- crashed. Last night I made the mistake of "upgrading" to 4.5-RELEASE-p2. Since that upgrade, the system has kernel paniced no less than six times in eighteen hours. I can almost make the system crash at will by attempting to rebuild the ports index, though once the system paniced while rebuilding a kernel. I've rebuilt the kernel no less than 4 times to try eliminate any kernel compilation problems and to compile in debugging symbols. The system in question has an AMD K6-2 350Mgz, 64MB RAM, and 384MB swap. The crashes my AMD system is experiencing seem to be centered around the VM subsystem, if gdb and backtraces can be believed. My work system (1.6Mhz PIV, 256MB RAM) runs the exact same release of FreeBSD without a problem. Looking back in the archives of this list, it seems there was a question of whether or not an AMD K6-2 could reliably run 4.5-RELEASE. http://www.freebsd.org/cgi/getmsg.cgi?fetch=34976+36926+/usr/local/www/db/text/2002/freebsd-hardware/20020210.freebsd-hardware Is anyone else seeing this problem? ========================================================================== Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02212a8 stack pointer = 0x10:0xc62acc38 frame pointer = 0x10:0xc62acc40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 18919 (sh) interrupt mask = net bio cam trap number = 12 panic: page fault syncing disks... 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 132 giving up on 127 buffers Uptime: 13m50s dumping to dev #ad/0x20001, offset 393216 dump ata0: resetting devices .. done 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at ../../kern/kern_shutdown.c:474 474 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:474 #1 0xc014a0b3 in boot (howto=256) at ../../kern/kern_shutdown.c:313 #2 0xc014a4ad in panic (fmt=0xc029c1ec "%s") at ../../kern/kern_shutdown.c:582 #3 0xc025a55b in trap_fatal (frame=0xc62acbf8, eva=19) at ../../i386/i386/trap.c:956 #4 0xc025a209 in trap_pfault (frame=0xc62acbf8, usermode=0, eva=19) at ../../i386/i386/trap.c:849 #5 0xc0259d83 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -968894304, tf_esi = 0, tf_ebp = -970273728, tf_isp = -970273756, tf_ebx = -968894304, tf_edx = -1, tf_ecx = 1833400, tf_eax = 25336, tf_trapno = 12, tf_err = 0, tf_eip = -1071508824, tf_cs = 8, tf_eflags = 66182, tf_esp = -1068627960, tf_ss = -969371904}) at ../../i386/i386/trap.c:448 #6 0xc02212a8 in vm_page_lookup (object=0xc63fd8a0, pindex=0) at ../../vm/vm_page.c:516 #7 0xc022025e in vm_object_collapse (object=0xc63fd8a0) at ../../vm/vm_object.c:1137 #8 0xc021f66c in vm_object_deallocate (object=0xc6431c60) at ../../vm/vm_object.c:356 #9 0xc021cacb in vm_map_entry_delete (map=0xc623de80, entry=0xc628b180) at ../../vm/vm_map.c:1823 #10 0xc021cc4d in vm_map_delete (map=0xc623de80, start=0, end=3217031168) at ../../vm/vm_map.c:1926 #11 0xc021ccda in vm_map_remove (map=0xc623de80, start=0, end=3217031168) at ../../vm/vm_map.c:1951 #12 0xc0141fe7 in exec_new_vmspace () #13 0xc013865d in exec_elf_imgact () #14 0xc0141828 in execve () #15 0xc025a811 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134992304, tf_esi = 0, tf_ebp = -1077938156, tf_isp = -970272812, tf_ebx = 134992332, tf_edx = 134992332, tf_ecx = 134992431, tf_eax = 59, tf_trapno = 12, tf_err = 2, tf_eip = 134705924, tf_cs = 31, tf_eflags = 659, tf_esp = -1077938200, tf_ss = 47}) at ../../i386/i386/trap.c:1157 #16 0xc024b735 in Xint0x80_syscall () Cannot access memory at address 0xbfbff814. (kgdb) ========================================================================== Fatal trap 12: page fault while in kernel mode fault virtual address = 0x80b3898 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0257cee stack pointer = 0x10:0xc6438c6c frame pointer = 0x10:0xc6438c88 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 36481 (sh) interrupt mask = none trap number = 12 panic: page fault syncing disks... 130 130 130 129 129 129 128 126 125 123 123 123 123 123 122 122 122 121 121 121 120 119 119 118 118 118 116 116 114 114 113 112 110 109 107 107 107 107 106 103 103 102 102 101 97 97 96 95 95 94 94 91 91 91 90 90 90 89 88 88 88 87 87 87 85 85 85 83 83 83 82 82 82 80 80 79 76 76 74 74 73 73 72 72 70 70 70 69 69 69 68 66 64 64 61 61 61 60 60 59 58 58 58 57 57 57 56 56 56 53 53 52 51 51 50 50 49 48 46 46 46 45 45 42 42 40 40 40 38 37 35 35 34 34 32 31 31 29 28 28 27 27 26 24 24 24 24 23 23 23 22 22 22 21 20 19 19 18 18 18 17 16 16 14 13 13 12 11 11 11 8 7 5 5 5 4 4 3 3 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 41m49s dumping to dev #ad/0x20001, offset 393216 dump ata0: resetting devices .. done 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at ../../kern/kern_shutdown.c:474 474 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:474 #1 0xc014a0b3 in boot (howto=256) at ../../kern/kern_shutdown.c:313 #2 0xc014a4ad in panic (fmt=0xc029c1ec "%s") at ../../kern/kern_shutdown.c:582 #3 0xc025a55b in trap_fatal (frame=0xc6438c2c, eva=134953112) at ../../i386/i386/trap.c:956 #4 0xc025a209 in trap_pfault (frame=0xc6438c2c, usermode=0, eva=134953112) at ../../i386/i386/trap.c:849 #5 0xc0259d83 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 46, tf_esi = 0, tf_ebp = -968651640, tf_isp = -968651688, tf_ebx = 134953088, tf_edx = -970489300, tf_ecx = 0, tf_eax = -2, tf_trapno = 12, tf_err = 0, tf_eip = -1071285010, tf_cs = 8, tf_eflags = 66050, tf_esp = -970489408, tf_ss = -970489408}) at ../../i386/i386/trap.c:448 #6 0xc0257cee in pmap_object_init_pt () #7 0xc021b624 in vm_map_insert (map=0xc62781c0, object=0xc622bb40, offset=0, start=134512640, end=134701056, prot=5 '\005', max=7 '\a', cow=10) at ../../vm/vm_map.c:612 #8 0xc01380e1 in elf_load_section () #9 0xc0138709 in exec_elf_imgact () #10 0xc0141828 in execve () #11 0xc025a811 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 135016784, tf_esi = -1, tf_ebp = -1077937856, tf_isp = -968650796, tf_ebx = 135016660, tf_edx = 135016800, tf_ecx = 135016793, tf_eax = 59, tf_trapno = 12, tf_err = 2, tf_eip = 134705924, tf_cs = 31, tf_eflags = 663, tf_esp = -1077937900, tf_ss = 47}) at ../../i386/i386/trap.c:1157 #12 0xc024b735 in Xint0x80_syscall () Cannot access memory at address 0xbfbff940. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 18: 4:42 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from adsl-63-198-35-122.dsl.snfc21.pacbell.net (adsl-63-198-35-122.dsl.snfc21.pacbell.net [63.198.35.122]) by hub.freebsd.org (Postfix) with ESMTP id 6E34E37B41B for ; Wed, 27 Mar 2002 18:04:31 -0800 (PST) Received: from lbl.gov (localhost.pacbell.net [127.0.0.1]) by adsl-63-198-35-122.dsl.snfc21.pacbell.net (8.11.6/8.11.6) with ESMTP id g2S25qD00630; Wed, 27 Mar 2002 18:05:53 -0800 (PST) (envelope-from j_guojun@lbl.gov) Message-ID: <3CA27A80.BC3D136@lbl.gov> Date: Wed, 27 Mar 2002 18:05:52 -0800 From: "Jin Guojun[ITG]" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-RELEASE i386) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: David Bogen Cc: hardware@FreeBSD.ORG Subject: Re: 4.5-RELEASE and AMD K6-2 not playing nice together References: <3CA26C23.1040906@bogen.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Copyright (c) 1992-2002 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.5-RELEASE #0: Thu Feb 7 16:33:35 PST 2002 root@spode.pacbell.net:/usr/src/sys/compile/MinMax Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D+ Processor (420.00-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0x80000800 real memory = 134201344 (131056K bytes) avail memory = 125943808 (122992K bytes) Preloaded elf kernel "kernel" at 0xc0490000. K6-family MTRR support enabled (2 registers) md0: Malloc disk I am writting this email from a AMD-K2 400 MHz box that runs 4.5 since Feb. 7, 2002. Also, notice that this machine is overclocked to 420MHz. I have many AMD boxes, and not one had problem with 4.5-RELEASE. From your coredump, it seems that you had random memory page missing. This usually means that there is memory related problem on your hardware. Also, there was an earlier released 4.5 (three days prior to the formal release) that contains such problem I have verified. I did diff between that release and the formal release, and many files were different, but I doubt you have that version. So, make world is a possible way to verify this problem under FreeBSD. If you can finish "make world", it normally can demostrate your system is healthy ( not 100% guarantee, but it is a good to detect memory problem ). Helpfullly, this helps, -Jin David Bogen wrote: > > Until last evening, one of my home PCs had been running 4.3-STABLE. > Before that, this PC ran nearly every RELEASE and/or STABLE from 3.4 > forward. The system was rock solid and --never-- crashed. > > Last night I made the mistake of "upgrading" to 4.5-RELEASE-p2. Since > that upgrade, the system has kernel paniced no less than six times in > eighteen hours. I can almost make the system crash at will by > attempting to rebuild the ports index, though once the system paniced > while rebuilding a kernel. I've rebuilt the kernel no less than 4 times > to try eliminate any kernel compilation problems and to compile in > debugging symbols. > > The system in question has an AMD K6-2 350Mgz, 64MB RAM, and 384MB swap. > > The crashes my AMD system is experiencing seem to be centered around the > VM subsystem, if gdb and backtraces can be believed. > > My work system (1.6Mhz PIV, 256MB RAM) runs the exact same release of > FreeBSD without a problem. > > Looking back in the archives of this list, it seems there was a question > of whether or not an AMD K6-2 could reliably run 4.5-RELEASE. > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=34976+36926+/usr/local/www/db/text/2002/freebsd-hardware/20020210.freebsd-hardware > > Is anyone else seeing this problem? > > ========================================================================== > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x13 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc02212a8 > stack pointer = 0x10:0xc62acc38 > frame pointer = 0x10:0xc62acc40 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 18919 (sh) > interrupt mask = net bio cam > trap number = 12 > panic: page fault > > syncing disks... 132 132 132 132 132 132 132 132 132 132 132 132 132 132 > 132 132 132 132 132 132 > giving up on 127 buffers > Uptime: 13m50s > > dumping to dev #ad/0x20001, offset 393216 > dump ata0: resetting devices .. done > 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 > 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 > 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > 474 if (dumping++) { > (kgdb) bt > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > #1 0xc014a0b3 in boot (howto=256) at ../../kern/kern_shutdown.c:313 > #2 0xc014a4ad in panic (fmt=0xc029c1ec "%s") at > ../../kern/kern_shutdown.c:582 > #3 0xc025a55b in trap_fatal (frame=0xc62acbf8, eva=19) > at ../../i386/i386/trap.c:956 > #4 0xc025a209 in trap_pfault (frame=0xc62acbf8, usermode=0, eva=19) > at ../../i386/i386/trap.c:849 > #5 0xc0259d83 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > tf_edi = -968894304, tf_esi = 0, tf_ebp = -970273728, > tf_isp = -970273756, tf_ebx = -968894304, tf_edx = -1, tf_ecx = > 1833400, > tf_eax = 25336, tf_trapno = 12, tf_err = 0, tf_eip = -1071508824, > tf_cs = 8, tf_eflags = 66182, tf_esp = -1068627960, tf_ss = > -969371904}) > at ../../i386/i386/trap.c:448 > #6 0xc02212a8 in vm_page_lookup (object=0xc63fd8a0, pindex=0) > at ../../vm/vm_page.c:516 > #7 0xc022025e in vm_object_collapse (object=0xc63fd8a0) > at ../../vm/vm_object.c:1137 > #8 0xc021f66c in vm_object_deallocate (object=0xc6431c60) > at ../../vm/vm_object.c:356 > #9 0xc021cacb in vm_map_entry_delete (map=0xc623de80, entry=0xc628b180) > at ../../vm/vm_map.c:1823 > #10 0xc021cc4d in vm_map_delete (map=0xc623de80, start=0, end=3217031168) > at ../../vm/vm_map.c:1926 > #11 0xc021ccda in vm_map_remove (map=0xc623de80, start=0, end=3217031168) > at ../../vm/vm_map.c:1951 > #12 0xc0141fe7 in exec_new_vmspace () > #13 0xc013865d in exec_elf_imgact () > #14 0xc0141828 in execve () > #15 0xc025a811 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 134992304, tf_esi = 0, tf_ebp = -1077938156, > tf_isp = -970272812, tf_ebx = 134992332, tf_edx = 134992332, > tf_ecx = 134992431, tf_eax = 59, tf_trapno = 12, tf_err = 2, > tf_eip = 134705924, tf_cs = 31, tf_eflags = 659, tf_esp = > -1077938200, > tf_ss = 47}) at ../../i386/i386/trap.c:1157 > #16 0xc024b735 in Xint0x80_syscall () > Cannot access memory at address 0xbfbff814. > (kgdb) > > ========================================================================== > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x80b3898 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0257cee > stack pointer = 0x10:0xc6438c6c > frame pointer = 0x10:0xc6438c88 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 36481 (sh) > interrupt mask = none > trap number = 12 > panic: page fault > > syncing disks... 130 130 130 129 129 129 128 126 125 123 123 123 123 123 > 122 122 122 121 121 121 120 119 119 118 118 118 116 116 114 114 113 112 > 110 109 107 107 107 107 106 103 103 102 102 101 97 97 96 95 95 94 94 91 > 91 91 90 90 90 89 88 88 88 87 87 87 85 85 85 83 83 83 82 82 82 80 80 79 > 76 76 74 74 73 73 72 72 70 70 70 69 69 69 68 66 64 64 61 61 61 60 60 59 > 58 58 58 57 57 57 56 56 56 53 53 52 51 51 50 50 49 48 46 46 46 45 45 42 > 42 40 40 40 38 37 35 35 34 34 32 31 31 29 28 28 27 27 26 24 24 24 24 23 > 23 23 22 22 22 21 20 19 19 18 18 18 17 16 16 14 13 13 12 11 11 11 8 7 5 > 5 5 4 4 3 3 3 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 > giving up on 1 buffers > Uptime: 41m49s > > dumping to dev #ad/0x20001, offset 393216 > dump ata0: resetting devices .. done > 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 > 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 > 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > 474 if (dumping++) { > (kgdb) bt > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > #1 0xc014a0b3 in boot (howto=256) at ../../kern/kern_shutdown.c:313 > #2 0xc014a4ad in panic (fmt=0xc029c1ec "%s") at > ../../kern/kern_shutdown.c:582 > #3 0xc025a55b in trap_fatal (frame=0xc6438c2c, eva=134953112) > at ../../i386/i386/trap.c:956 > #4 0xc025a209 in trap_pfault (frame=0xc6438c2c, usermode=0, eva=134953112) > at ../../i386/i386/trap.c:849 > #5 0xc0259d83 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > tf_edi = 46, tf_esi = 0, tf_ebp = -968651640, tf_isp = -968651688, > tf_ebx = 134953088, tf_edx = -970489300, tf_ecx = 0, tf_eax = -2, > tf_trapno = 12, tf_err = 0, tf_eip = -1071285010, tf_cs = 8, > tf_eflags = 66050, tf_esp = -970489408, tf_ss = -970489408}) > at ../../i386/i386/trap.c:448 > #6 0xc0257cee in pmap_object_init_pt () > #7 0xc021b624 in vm_map_insert (map=0xc62781c0, object=0xc622bb40, > offset=0, > start=134512640, end=134701056, prot=5 '\005', max=7 '\a', cow=10) > at ../../vm/vm_map.c:612 > #8 0xc01380e1 in elf_load_section () > #9 0xc0138709 in exec_elf_imgact () > #10 0xc0141828 in execve () > #11 0xc025a811 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 135016784, tf_esi = -1, tf_ebp = -1077937856, > tf_isp = -968650796, tf_ebx = 135016660, tf_edx = 135016800, > tf_ecx = 135016793, tf_eax = 59, tf_trapno = 12, tf_err = 2, > tf_eip = 134705924, tf_cs = 31, tf_eflags = 663, tf_esp = > -1077937900, > tf_ss = 47}) at ../../i386/i386/trap.c:1157 > #12 0xc024b735 in Xint0x80_syscall () > Cannot access memory at address 0xbfbff940. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Mar 27 20: 7: 4 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wally.statscout.com (wally.statscout.com [203.39.101.146]) by hub.freebsd.org (Postfix) with ESMTP id 79AFB37B416; Wed, 27 Mar 2002 20:06:51 -0800 (PST) Received: from speedy.statscout.com (speedy.statscout.com [10.1.1.100]) by wally.statscout.com (8.11.6/8.11.3av) with ESMTP id g2R48EA93332; Wed, 27 Mar 2002 14:08:14 +1000 (EST) (envelope-from pak@statscout.com) Received: from there (localhost.statscout.com [127.0.0.1]) by speedy.statscout.com (8.11.6/8.11.6) with SMTP id g2R48FR09068; Wed, 27 Mar 2002 14:08:15 +1000 (EST) (envelope-from pak@statscout.com) Message-Id: <200203270408.g2R48FR09068@speedy.statscout.com> Content-Type: text/plain; charset="iso-8859-1" From: Paul Koch Reply-To: pak@statscout.com To: freebsd-questions@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Compaq DL350/DL360 FreeBSD-4.4/4.5 Release floppy controller problem Date: Wed, 27 Mar 2002 14:08:14 +1000 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, We have two customers who are experiencing floppy disk controller problems on their Compaq DL350 (FreeBSD-4.4 Release) and DL360 (FreeBSD-4.5 Release) servers. Any attempt to access the floppy drive results in the following error messages (eg. tar cvf /dev/fd0 somefile): Mar 26 14:57:40 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:40 statscout /kernel: fdc0: cmd 3 failed at out byte 1 of 3 Mar 26 14:57:40 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:40 statscout /kernel: fdc0: cmd 13 failed at out byte 1 of 4 Mar 26 14:57:40 statscout /kernel: fdc0: Re-enable FIFO failed Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:43 statscout /kernel: fdc0: cmd 8 failed at out byte 1 of 1 Mar 26 14:57:43 statscout /kernel: fdc0: sense intr err reading stat reg 0 Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:43 statscout /kernel: fdc0: cmd 8 failed at out byte 1 of 1 Mar 26 14:57:43 statscout /kernel: fdc0: sense intr err reading stat reg 0 Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:43 statscout /kernel: fdc0: cmd 8 failed at out byte 1 of 1 Mar 26 14:57:43 statscout /kernel: fdc0: sense intr err reading stat reg 0 Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:43 statscout /kernel: fdc0: cmd 8 failed at out byte 1 of 1 Mar 26 14:57:43 statscout /kernel: fdc0: sense intr err reading stat reg 0 Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Mar 26 14:57:43 statscout /kernel: fdc0: cmd 7 failed at out byte 1 of 2 Mar 26 14:57:43 statscout /kernel: fdc0: direction bit not set Syslog gives up logging these messages and the machine becomes quite unresponsive on the console. The following is the dmesg from the DL360. Copyright (c) 1992-2002 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.5-RELEASE #2: Tue Mar 26 15:13:25 EST 2002 root@xxxxxxxx Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1258.22-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 2, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc04c9000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib1: on motherboard pci1: on pcib1 ahc0: port 0x3000-0x30ff mem aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x3400-0x34ff mem aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs ida0: port 0x3800-0x38ff mem 0xf7ed0000-0xf7 ida0: drives=1 firm_rev=1.22 idad0: on ida0 idad0: 69455MB (142245120 sectors), blocksize=512 ti0: <3Com 3c985-SX Gigabit Ethernet> mem 0xf7ec0000-0xf7ec3fff irq 15 at device ti0: Ethernet address: 00:60:08:f6:ed:4c pcib0: on motherboard IOAPIC #1 intpin 6 -> irq 2 pci0: on pcib0 fxp0: port 0x2000-0x203f mem 0xf7c00000-0xf7cf fxp0: Ethernet address 00:02:a5:ab:2f:4a inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 5.0 pci0: (vendor=0x0e11, dev=0xa0f0) at 6.0 irq 5 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2800-0x280f at device 15.1 ta0: at 0x1f0 irq 14 on atapci0 ohci0: mem 0xf5fd0000-0xf5fd0fff irq 2 at device usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib2: on motherboard pci2: on pcib2 pcib7: on motherboard pci7: on pcib7 pci7: (vendor=0x0e11, dev=0xa0f7) at 7.0 irq 10 eisa0: on motherboard mainboard0: on eisa0 slot 0 orm0: