From owner-freebsd-smp Sun Nov 22 23:51:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10187 for freebsd-smp-outgoing; Sun, 22 Nov 1998 23:51:17 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns3.redbacknetworks.com (mail3.redbacknetworks.com [155.53.200.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10146 for ; Sun, 22 Nov 1998 23:51:04 -0800 (PST) (envelope-from sam@redbacknetworks.com) Received: from phred.redbacknetworks.com (phred.redbacknetworks.com [155.53.144.35]) by ns3.redbacknetworks.com (8.8.8/8.8.8) with ESMTP id XAA13669 for ; Sun, 22 Nov 1998 23:50:24 -0800 (PST) Received: (from sam@localhost) by phred.redbacknetworks.com (8.8.5/8.8.5) id XAA13758; Sun, 22 Nov 1998 23:49:44 -0800 (PST) Date: Sun, 22 Nov 1998 23:49:44 -0800 (PST) Message-Id: <199811230749.XAA13758@phred.redbacknetworks.com> From: Sam Pigg To: smp@FreeBSD.ORG Subject: micron netframe quad xeon? Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need to build an smp system with a large amount of memory for network simulation (>=4 gigs ideal). Has anyone had any successful experiences running smp freebsd on quad xeon machines with lots of memory? I'm currently looking specifically at the micron netframe 6200. Thanks for any help, -Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 00:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12900 for freebsd-smp-outgoing; Mon, 23 Nov 1998 00:16:50 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12894 for ; Mon, 23 Nov 1998 00:16:37 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id AAA04459; Mon, 23 Nov 1998 00:17:34 -0800 (PST) Message-Id: <199811230817.AAA04459@root.com> To: Sam Pigg cc: smp@FreeBSD.ORG Subject: Re: micron netframe quad xeon? In-reply-to: Your message of "Sun, 22 Nov 1998 23:49:44 PST." <199811230749.XAA13758@phred.redbacknetworks.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Nov 1998 00:17:34 -0800 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I need to build an smp system with a large amount of memory >for network simulation (>=4 gigs ideal). >Has anyone had any successful experiences running smp freebsd on >quad xeon machines with lots of memory? > >I'm currently looking specifically at the micron netframe 6200. The Netframe 6200 is what will be the next wcarchive, although only a single processor. It's not actually shipping just yet, however - I hope to see the new machine in a few weeks. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 00:52:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16769 for freebsd-smp-outgoing; Mon, 23 Nov 1998 00:52:37 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns3.redbacknetworks.com (mail3.redbacknetworks.com [155.53.200.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16750; Mon, 23 Nov 1998 00:52:28 -0800 (PST) (envelope-from sam@redbacknetworks.com) Received: from phred.redbacknetworks.com (phred.redbacknetworks.com [155.53.144.35]) by ns3.redbacknetworks.com (8.8.8/8.8.8) with ESMTP id AAA13858; Mon, 23 Nov 1998 00:51:50 -0800 (PST) Received: (from sam@localhost) by phred.redbacknetworks.com (8.8.5/8.8.5) id AAA13798; Mon, 23 Nov 1998 00:51:10 -0800 (PST) Date: Mon, 23 Nov 1998 00:51:10 -0800 (PST) Message-Id: <199811230851.AAA13798@phred.redbacknetworks.com> From: Sam Pigg To: freebsd-hardware@FreeBSD.ORG CC: smp@FreeBSD.ORG Subject: tyan S1836DLUAN >512Mb problems Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Trying to use 1 gig of memory on a tyan S1836DLUAN (dual 450 PII's) running 3.0-RELEASE, keep having problems with the system freezing up, rebooting, compiles failing due to signal 11's etc. If I decrease the memory to 512 megs (I'm using those weird micron 256meg simms btw) everything works fine. Tyan claims this motherboard can support up to '1GB SPD SDRAM or SDRAM+ECC in addition to the new 100MHz SDRAMs' This motherboard uses the 440GX chipset, but another system with a tyan S1832DL (440BX chipset) suffers from the same symptoms when >512 megs of ram are installed. any ideas? Thanks, Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 04:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10686 for freebsd-smp-outgoing; Mon, 23 Nov 1998 04:48:43 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10681; Mon, 23 Nov 1998 04:48:40 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA29881; Mon, 23 Nov 1998 07:47:08 -0500 (EST) Date: Mon, 23 Nov 1998 07:47:08 -0500 (EST) From: Chuck Robey To: Sam Pigg cc: freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: tyan S1836DLUAN >512Mb problems In-Reply-To: <199811230851.AAA13798@phred.redbacknetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 23 Nov 1998, Sam Pigg wrote: > > Trying to use 1 gig of memory on a tyan S1836DLUAN (dual 450 PII's) > running 3.0-RELEASE, keep having problems with the system freezing up, > rebooting, compiles failing due to signal 11's etc. If I decrease the > memory to 512 megs (I'm using those weird micron 256meg simms btw) > everything works fine. Tyan claims this motherboard can support up to > '1GB SPD SDRAM or SDRAM+ECC in addition to the new 100MHz > SDRAMs' > > This motherboard uses the 440GX chipset, but another system with > a tyan S1832DL (440BX chipset) suffers from the same symptoms when > >512 megs of ram are installed. Trying to locate memory problems can really be misleading. You aren't sure yet that this isn't a memory problem, I think, and you have to be, before you go to blaming the board. How about swapping out the 512M you have installed now with the 512 you took out, and run that for a little while? It's *possible* you're absolutely right about the board, but I don't think anyone's going to trust that until you've covered the (logically required) bases. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 06:36:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20765 for freebsd-smp-outgoing; Mon, 23 Nov 1998 06:36:33 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from cc.weber.edu (cc.weber.edu [137.190.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20751; Mon, 23 Nov 1998 06:36:30 -0800 (PST) (envelope-from rfleming@cc.weber.edu) Received: from cc.weber.edu ([137.190.3.248]) by cc.WEBER.EDU (PMDF V5.1-7 #7039) with ESMTP id <01J4I72M26GW8Y77PQ@cc.WEBER.EDU>; Mon, 23 Nov 1998 07:35:49 MST Date: Mon, 23 Nov 1998 07:45:56 -0700 From: Rob Subject: Re: tyan S1836DLUAN >512Mb problems To: Sam Pigg Cc: freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Message-id: <36597523.1B3B1114@cc.weber.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.06 [en] (WinNT; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: <199811230851.AAA13798@phred.redbacknetworks.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Trying to use 1 gig of memory on a tyan S1836DLUAN (dual 450 PII's) > running 3.0-RELEASE, keep having problems with the system freezing up, > rebooting, compiles failing due to signal 11's etc. If I decrease the > memory to 512 megs (I'm using those weird micron 256meg simms btw) > everything works fine. Tyan claims this motherboard can support up to > '1GB SPD SDRAM or SDRAM+ECC in addition to the new 100MHz > SDRAMs' > > This motherboard uses the 440GX chipset, but another system with > a tyan S1832DL (440BX chipset) suffers from the same symptoms when > >512 megs of ram are installed. The problem is not with the motherboard. Most of the mother boards that support SMP PII's have the same problem. I was unable to locate where in the configs the problem comes from though. I was testing dual PII 400 when they were first avalible from Compaq with 1.0 gig of 256meg dimms. They are recognized fine by the bios but FreeBSD won't work with it. I tested NT, Novell, and Sco all of which work although no where near as well and the system with 512meg and SMP FreeBSD. Rob. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 08:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04205 for freebsd-smp-outgoing; Mon, 23 Nov 1998 08:45:40 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA04178 for ; Mon, 23 Nov 1998 08:45:35 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 16673 invoked by alias); 23 Nov 1998 16:44:56 -0000 Delivered-To: fixup-smp@FreeBSD.ORG@fixme Received: (qmail 16630 invoked by uid 0); 23 Nov 1998 16:44:54 -0000 Received: from dialupd157.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.98.157) by omahpop1.omah.uswest.net with SMTP; 23 Nov 1998 16:44:54 -0000 Date: Mon, 23 Nov 1998 10:44:55 -0600 (CST) From: "Open Systems Inc." To: Rob cc: Sam Pigg , freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: tyan S1836DLUAN >512Mb problems In-Reply-To: <36597523.1B3B1114@cc.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 23 Nov 1998, Rob wrote: > > This motherboard uses the 440GX chipset, but another system with > > a tyan S1832DL (440BX chipset) suffers from the same symptoms when > > >512 megs of ram are installed. > > The problem is not with the motherboard. Most of the mother boards that > support SMP PII's have the same problem. I was unable to locate where in > the configs the problem comes from though. I was testing dual PII 400 > when they were first avalible from Compaq with 1.0 gig of 256meg dimms. > They are recognized fine by the bios but FreeBSD won't work with it. I > tested NT, Novell, and Sco all of which work although no where near as > well and the system with 512meg and SMP FreeBSD. Erm wasnt there a problem with the PII's with caching a gig of ram or something? Perhaps this is the problem? Chris "If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list. ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.7 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 09:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08243 for freebsd-smp-outgoing; Mon, 23 Nov 1998 09:23:07 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns3.redbacknetworks.com (mail3.redbacknetworks.com [155.53.200.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08231; Mon, 23 Nov 1998 09:23:05 -0800 (PST) (envelope-from sam@redbacknetworks.com) Received: from phred.redbacknetworks.com (phred.redbacknetworks.com [155.53.144.35]) by ns3.redbacknetworks.com (8.8.8/8.8.8) with ESMTP id JAA17350; Mon, 23 Nov 1998 09:22:15 -0800 (PST) Received: (from sam@localhost) by phred.redbacknetworks.com (8.8.5/8.8.5) id JAA14106; Mon, 23 Nov 1998 09:21:34 -0800 (PST) Date: Mon, 23 Nov 1998 09:21:34 -0800 (PST) Message-Id: <199811231721.JAA14106@phred.redbacknetworks.com> From: Sam Pigg To: chuckr@mat.net CC: freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: tyan S1836DLUAN >512Mb problems Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Trying to locate memory problems can really be misleading. You aren't >sure yet that this isn't a memory problem, I think, and you have to be, >before you go to blaming the board. > >How about swapping out the 512M you have installed now with the 512 you >took out, and run that for a little while? It's *possible* you're >absolutely right about the board, but I don't think anyone's going to >trust that until you've covered the (logically required) bases. Sorry I didn't mention it, but I have swapped around the simms, and even got the vendor to provide a new set of 4 256 meg simms. Symptoms manifest themselves with any combination of simms larger than 512 Megs (though exactly 512 works fine). I have heard there was a cacheing issue with the old PII's (<400Mhz?), but these are the new 450's. Thanks, Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 09:28:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09131 for freebsd-smp-outgoing; Mon, 23 Nov 1998 09:28:36 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dingo.cdrom.com (castles354.castles.com [208.214.167.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09110; Mon, 23 Nov 1998 09:28:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA19129; Mon, 23 Nov 1998 09:26:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811231726.JAA19129@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Rob cc: Sam Pigg , freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: tyan S1836DLUAN >512Mb problems In-reply-to: Your message of "Mon, 23 Nov 1998 07:45:56 MST." <36597523.1B3B1114@cc.weber.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 09:26:18 -0800 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Trying to use 1 gig of memory on a tyan S1836DLUAN (dual 450 PII's) > > running 3.0-RELEASE, keep having problems with the system freezing up, > > rebooting, compiles failing due to signal 11's etc. If I decrease the > > memory to 512 megs (I'm using those weird micron 256meg simms btw) > > everything works fine. Tyan claims this motherboard can support up to > > '1GB SPD SDRAM or SDRAM+ECC in addition to the new 100MHz > > SDRAMs' > > > > This motherboard uses the 440GX chipset, but another system with > > a tyan S1832DL (440BX chipset) suffers from the same symptoms when > > >512 megs of ram are installed. > > The problem is not with the motherboard. Most of the mother boards that > support SMP PII's have the same problem. Just a quick point; if you're using an SMP board with only one CPU, make sure that you've got the terminator card in the empty slot... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 16:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11090 for freebsd-smp-outgoing; Mon, 23 Nov 1998 16:41:40 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11082; Mon, 23 Nov 1998 16:41:35 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.6 (PHNE_14041)/8.8.5tis) with ESMTP id QAA00407; Mon, 23 Nov 1998 16:41:36 -0800 (PST) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA066848066; Mon, 23 Nov 1998 16:41:06 -0800 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id QAA07352; Mon, 23 Nov 1998 16:41:05 -0800 (PST) Message-Id: <199811240041.QAA07352@mina.sr.hp.com> To: Sam Pigg Cc: chuckr@mat.net, freebsd-hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: tyan S1836DLUAN >512Mb problems Reply-To: Darryl Okahata In-Reply-To: Your message of "Mon, 23 Nov 1998 09:21:34 PST." <199811231721.JAA14106@phred.redbacknetworks.com> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Mon, 23 Nov 1998 16:41:04 -0800 From: Darryl Okahata Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sam Pigg wrote: > Sorry I didn't mention it, but I have swapped around the simms, and > even got the vendor to provide a new set of 4 256 meg simms. > Symptoms manifest themselves with any combination of simms larger than > 512 Megs (though exactly 512 works fine). [ You mean "DIMMs", not SIMMs". ] Just another possible issue: with the old SIMMs, there was an apparent cottage industry where people would take lots of older (lower- density) memory chips and stuff them onto a board to make a SIMM. The problem with these "lots o'chips" SIMMs was that they'd put a large capacitive load onto the memory bus, with the result that you often couldn't put more than one (pair) into a system. If you did, you ended up with a system that either didn't boot, or crashed intermittently. If you were "lucky", you could "fix" this by tweaking the BIOS to add main memory wait states, but this wasn't particularly nice, as it slowed down the system. The result was that Pentium motherboard manufacturers added comments to their manuals, which basically said not to use SIMMs with more than "N" chips ("N" was something like 18-24 chips -- I don't know, exactly). Now, the question is whether or not there is a similar situation with DIMMs (I don't know, as I'm still stuck in the Pentium I world). If you have DIMMs with "lots o'chips", you might want to see if you can find DIMMs with fewer memory chips. Yes, they'll probably cost much more, but they might be more reliable. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 18:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18420 for freebsd-smp-outgoing; Mon, 23 Nov 1998 18:04:30 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18411 for ; Mon, 23 Nov 1998 18:04:29 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id SAA14864 for ; Mon, 23 Nov 1998 18:05:58 -0800 (PST) Message-Id: <199811240205.SAA14864@root.com> To: smp@FreeBSD.ORG Subject: hangs with SMP From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Nov 1998 18:05:58 -0800 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just started doing some testing of the -current SMP code and had a hard hang a few minutes into a "make -j2 world". The machine seemed quite dead - even the soft power switch didn't work. The hang occured during heavy disk I/O, so it seems like it could be a problem with managing the APIC. The machine is a dual PII/450 on a Tyan S1836DLUAN-GX motherboard. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 18:45:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22413 for freebsd-smp-outgoing; Mon, 23 Nov 1998 18:45:59 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22405 for ; Mon, 23 Nov 1998 18:45:55 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id SAA12859; Mon, 23 Nov 1998 18:45:13 -0800 (PST) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199811240245.SAA12859@GndRsh.aac.dev.com> Subject: Re: hangs with SMP In-Reply-To: <199811240205.SAA14864@root.com> from David Greenman at "Nov 23, 98 06:05:58 pm" To: dg@root.com Date: Tue, 24 Nov 1998 02:45:12 +0000 (GMT) Cc: smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just started doing some testing of the -current SMP code and had a hard > hang a few minutes into a "make -j2 world". The machine seemed quite dead - > even the soft power switch didn't work. The hang occured during heavy disk > I/O, so it seems like it could be a problem with managing the APIC. The > machine is a dual PII/450 on a Tyan S1836DLUAN-GX motherboard. FYI, the ``soft power switch'' normally needs the CPU to respond in order for it to work, however, there is a timeout circuit such that if the switch is held for >4 or so seconds the power supply is told to shut down. I know this won't help you find the SMP bug, but it may atleast allow you to reset the machine without pulling the power plug out of the wall. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Nov 23 21:44:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09688 for freebsd-smp-outgoing; Mon, 23 Nov 1998 21:44:23 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09672 for ; Mon, 23 Nov 1998 21:44:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA02714; Mon, 23 Nov 1998 21:41:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811240541.VAA02714@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Rodney W. Grimes" cc: dg@root.com, smp@FreeBSD.ORG Subject: Re: hangs with SMP In-reply-to: Your message of "Tue, 24 Nov 1998 02:45:12 GMT." <199811240245.SAA12859@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 21:41:56 -0800 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I just started doing some testing of the -current SMP code and had a hard > > hang a few minutes into a "make -j2 world". The machine seemed quite dead - > > even the soft power switch didn't work. The hang occured during heavy disk > > I/O, so it seems like it could be a problem with managing the APIC. The > > machine is a dual PII/450 on a Tyan S1836DLUAN-GX motherboard. > > FYI, the ``soft power switch'' normally needs the CPU to respond in order > for it to work, however, there is a timeout circuit such that if the > switch is held for >4 or so seconds the power supply is told to shut down. Also, the "soft power" switch normally generates an SMI, which is akin to an NMI and very difficult to ignore. You have to have the system pretty solidly wedged (APIC gummed might do it, not sure) before it stops working. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 24 14:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17580 for freebsd-smp-outgoing; Tue, 24 Nov 1998 14:48:11 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17575 for ; Tue, 24 Nov 1998 14:48:09 -0800 (PST) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.8.8/8.8.7) id QAA22099; Tue, 24 Nov 1998 16:46:17 -0600 (CST) (envelope-from pmckenna) From: "Pete McKenna" Message-Id: <9811242246.ZM22097@otto.oss.uswest.net> Date: Tue, 24 Nov 1998 22:46:16 +0000 X-Mailer: Z-Mail (3.2.1 10apr95) To: mike@smith.net.au Subject: SMP Xeon update Cc: smp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike, I was looking through the SMP Archive and haven't seen much recently on the quad Xeon box you had been testing. We are looking for a MRTG box to do our network metrics and it looks like this would hold us for awhile at the rate things are expanding. Can you me update on what's happened and if the onboard controllers are usable. We're are planning on running 3.0 release and only need 2 drives on either an adaptec or the onboard controller (I'm a bit fuzzy on what the onboard controller is) Any input and suggestions would be greatly appreciated. Pete -- Pete McKenna Systems Engineer US WEST - !NTERACT Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 24 15:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22707 for freebsd-smp-outgoing; Tue, 24 Nov 1998 15:31:35 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22702 for ; Tue, 24 Nov 1998 15:31:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01653; Tue, 24 Nov 1998 15:30:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811242330.PAA01653@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Pete McKenna" cc: smp@FreeBSD.ORG Subject: Re: SMP Xeon update In-reply-to: Your message of "Tue, 24 Nov 1998 22:46:16 GMT." <9811242246.ZM22097@otto.oss.uswest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 15:30:18 -0800 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I was looking through the SMP Archive and haven't seen much recently on the > quad Xeon box you had been testing. > > We are looking for a MRTG box to do our network metrics and it looks > like this would hold us for awhile at the rate things are expanding. Can > you me update on what's happened and if the onboard controllers are > usable. We're are planning on running 3.0 release and only need 2 drives > on either an adaptec or the onboard controller (I'm a bit fuzzy on what > the onboard controller is) The box is running quite stable at the moment (3.0-current). I take it you're looking for something with a lot of compute legs? The system we have here is a pre-release Intel box; I don't know if it's actually available for purchase anywhere, and for your needs it's probably very much overspecified (3 PCI busses, 12-bay hotswap disk array). Both Acer and Toshiba were showing systems at Comdex using the same processor array but with only 1 memory card (4GB max) and a smaller I/O arrangement. The Toshiba system was the Magnia 7000; their pages say it comes with a 53C896 (ncr) chipset SCSI controller, so it should be just fine. They were showing it with the AMI MegaRaid, which wouldn't be so good, as we don't support it yet. The Acer system was, I think, an Altos 21000, which looked to be the same system down to the metalwork. Street price on these should be around the $10k mark according to Toshiba. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Nov 24 16:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29058 for freebsd-smp-outgoing; Tue, 24 Nov 1998 16:20:19 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from cannon.ma.ikos.com ([137.103.105.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29043 for ; Tue, 24 Nov 1998 16:20:16 -0800 (PST) (envelope-from tich@cannon.ma.ikos.com) Received: from baker.ma.ikos.com (baker [137.103.105.29]) by cannon.ma.ikos.com (8.9.1/8.8.8) with ESMTP id TAA00341; Tue, 24 Nov 1998 19:20:57 -0500 (EST) From: Richard Cownie Received: (from tich@localhost) by baker.ma.ikos.com (8.8.8/8.8.8) id TAA03668; Tue, 24 Nov 1998 19:20:55 -0500 (EST) Date: Tue, 24 Nov 1998 19:20:55 -0500 (EST) Message-Id: <199811250020.TAA03668@baker.ma.ikos.com> To: mike@smith.net.au, pmckenna@uswest.net Subject: Re: SMP Xeon update Cc: smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been looking into quad-Xeon systems here; the Intel boxes are available from various resellers, the cheapest I found is SAG Electronics (www.sagelec.com). A quad-Xeon box with 2 Xeon-400MHz, 2GB DRAM, and 1 10000rpm 9GB disk comes to about $11500 - counting $1K each for the cpu's and $2K/GB for the DRAM that means the box is < $5K, which seems a pretty good deal. Hope to get the machine in the next couple of weeks, and I'll post a report on how it goes. Richard Cownie (tich@ma.ikos.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 25 06:05:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06415 for freebsd-smp-outgoing; Wed, 25 Nov 1998 06:05:23 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06404 for ; Wed, 25 Nov 1998 06:05:10 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id IAA29741 for freebsd-smp@freebsd.org; Wed, 25 Nov 1998 08:05:00 -0600 (CST) From: Joe Greco Message-Id: <199811251405.IAA29741@aurora.sol.net> Subject: Help, cannot make HP Vectra XU work To: freebsd-smp@freeebsd.org Date: Tue, 24 Nov 1998 14:32:18 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have an HP Vectra XU (2 x PP200, 160MB RAM) that I am having some trouble getting to work under FreeBSD 3.0R SMP. This board worked under one of the late summer 3.0 SNAP's with a smaller amount of memory. If the details are significant, I can dig them up. Using the values specified by "mptable", I built a kernel... but all it does is: ------------------------------------------------------------------------------- Booting 0:da(0,a)kernel @ 0x100000 text=0xe7000 data=0x15000 bss=0x1ac44 symbols=[+0x3bc+0x4+0x13a94+0x4+0x1c5db] total=0x247077 entry point=0x100000 BIOS basemem (638K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #2: Tue Nov 24 14:10:50 CST 1998 root@:/usr/src/sys/compile/SMP-QUORISTAN Timecounter "i8254" frequency 1193182 Hz cost 3529 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 167772160 (163840K bytes) avail memory = 160706560 (156940K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpint 1 -> irq -1 IOAPIC #0 intpint 2 -> irq -1 IOAPIC #0 intpint 3 -> irq -1 IOAPIC #0 intpint 4 -> irq -1 IOAPIC #0 intpint 5 -> irq -1 IOAPIC #0 intpint 6 -> irq -1 IOAPIC #0 intpint 7 -> irq -1 IOAPIC #0 intpint 8 -> irq -1 IOAPIC #0 intpint 9 -> irq -1 IOAPIC #0 intpint 10 -> irq -1 IOAPIC #0 intpint 11 -> irq -1 IOAPIC #0 intpint 12 -> irq -1 IOAPIC #0 intpint 13 -> irq -1 IOAPIC #0 intpint 14 -> irq -1 IOAPIC #0 intpint 15 -> irq -1 [lockup] ------------------------------------------------------------------------------- I then commented out the options specified by MPTABLE and got this far: ------------------------------------------------------------------------------- Booting 0:da(0,a)kernel @ 0x100000 text=0xe7000 data=0x15000 bss=0x1ad44 symbols=[+0x2bc+0x4+0x13a94+0x4+0x1c5db] total=0x247077 entry point=0x100000 BIOS basemem (638K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #1: Tue Nov 24 13:53:35 CST 1998 root@:/usr/src/sys/compile/SMP-QUORISTAN Timecounter "i8254" frequency 1193182 Hz cost 3532 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 167772160 (163840K bytes) avail memory = 160706560 (156940K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpint 1 -> irq -1 IOAPIC #0 intpint 2 -> irq -1 IOAPIC #0 intpint 3 -> irq -1 IOAPIC #0 intpint 4 -> irq -1 IOAPIC #0 intpint 5 -> irq -1 IOAPIC #0 intpint 6 -> irq -1 IOAPIC #0 intpint 7 -> irq -1 IOAPIC #0 intpint 8 -> irq -1 IOAPIC #0 intpint 9 -> irq -1 IOAPIC #0 intpint 10 -> irq -1 IOAPIC #0 intpint 11 -> irq -1 IOAPIC #0 intpint 12 -> irq -1 IOAPIC #0 intpint 13 -> irq -1 IOAPIC #0 intpint 14 -> irq -1 IOAPIC #0 intpint 15 -> irq -1 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 16, version: 0x000f0011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x88 on pci0.0.0 Freeing (NOT implemented) redirected ISA irq 14. Freeing (NOT implemented) redirected ISA irq 9. ahc0: rev 0x00 int a irq 255 on pci0.2.0 create_intr: requested irq255 too high, limit is 23 Freeing (NOT implemented) redirected ISA irq 11. vga0: rev 0x01 int a irq 255 on pci0.11.0 Freeing (NOT implemented) redirected ISA irq 11. de0: rev 0x12 int a irq 255 on pci0.14.0 create_intr: requested irq255 too high, limit is 23 de0: couldn't map interrupt chip1: rev 0x04 on pci0.20.0 chip2: rev 0x04 on pci0.25.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> Freeing (NOT implemented) redirected ISA irq 1. create_intr: requested irq31 too high, limit is 23 ed0 not found at 0x280 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console Freeing (NOT implemented) redirected ISA irq 4. create_intr: requested irq31 too high, limit is 23 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A Freeing (NOT implemented) redirected ISA irq 3. create_intr: requested irq31 too high, limit is 23 sio2: configured irq 5 not in bitmap of probed irqs 0 sio2 not found at 0x3e8 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface Freeing (NOT implemented) redirected ISA irq 7. create_intr: requested irq31 too high, limit is 23 psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in Freeing (NOT implemented) redirected ISA irq 6. create_intr: requested irq31 too high, limit is 23 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy wcd0: 1377/2755Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm data/audio disc loaded, unlocked Freeing (NOT implemented) redirected ISA irq 15. create_intr: requested irq31 too high, limit is 23 npx0 on motherboard npx0: INT 16 interface create_intr: requested irq255 too high, limit is 23 Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 fault virtual address = 0x5f5e5d5c fault code = supervisor write, page not present instruction pointer = 0x8:0xf01b5624 stack pointer = 0x10:0xf0222f64 frame pointer = 0x10:0xf0222f90 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) interrupt mask = <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot <-- ------------------------------------------------------------------------------- The config file I'm using (comment out the four mptable options to get the second boot trial): ------------------------------------------------------------------------------- # # SMP-QUORISTAN -- Smp machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: SMP-QUORISTAN,v 1.17 1998/10/16 04:44:05 peter Exp $ machine "i386" # SMP does NOT support 386/486 CPUs. #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident SMP-QUORISTAN maxusers 160 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: options NCPU=2 # number of CPUs options NBUS=2 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs # Lets always enable the kernel debugger for SMP. #options DDB # SMP shouldn't need x87 emulation, disable by default. #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] #options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem #options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about #options IPFIREWALL_FORWARD #enable xparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default #config kernel root on wd0 config kernel root on da0 controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device de1 device de2 device de3 #device fxp0 #device tl0 #device tx0 #device vx0 #device xl0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr #device cs0 at isa? port 0x300 net irq ? vector csintr pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) ------------------------------------------------------------------------------- The output of "mptable" from a kernel.GENERIC: ------------------------------------------------------------------------------- =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f97e0 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x0d mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f97f0 signature: 'PCMP' base table length: 236 version: 1.1 checksum: 0xe0 OEM ID: 'HP ' Product ID: 'XX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 21 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 1 0x11 BSP, usable 6 1 0 0xfbff 0 0x11 AP, usable 6 1 0 0xfbff -- Bus: Bus ID Type 1 ISA 0 PCI -- I/O APICs: APIC ID Version State Address 16 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT conforms conforms 1 1 255 1 INT conforms conforms 1 0 255 2 INT conforms conforms 1 3 255 3 INT conforms conforms 1 4 255 4 INT conforms conforms 1 5 255 5 INT conforms conforms 1 6 255 6 INT conforms conforms 1 7 255 7 INT conforms conforms 1 8 255 8 INT conforms conforms 1 9 255 9 INT conforms conforms 1 10 255 10 INT conforms conforms 1 11 255 11 INT conforms conforms 1 12 255 12 INT conforms conforms 1 13 255 13 INT conforms conforms 1 14 255 14 INT conforms conforms 1 15 255 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# NMI conforms conforms 1 2 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== ------------------------------------------------------------------------------- This is sort of disappointing, wanted to use this machine as my new Quake/Quake2 server. :-( I'm really not sure what to try next. If anyone has any bright ideas, ... ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Nov 25 08:04:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16891 for freebsd-smp-outgoing; Wed, 25 Nov 1998 08:04:07 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16886 for ; Wed, 25 Nov 1998 08:04:03 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id KAA29981; Wed, 25 Nov 1998 10:03:48 -0600 (CST) From: Joe Greco Message-Id: <199811251603.KAA29981@aurora.sol.net> Subject: Re: Help, cannot make HP Vectra XU work To: freebsd-smp@FreeBSD.ORG Date: Wed, 25 Nov 1998 10:03:48 -0600 (CST) Cc: ken@plutotech.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Try this -- go into the bios, and change the MP Spec version from 1.1 to > 1.4. There's no apparent setting for it. I just tried under BIOS GG.06.07, which is old (and used to work with FreeBSD 3.0S) and just flashed a new one (GG.06.13) which was released a month ago, and there's still no setting for it. Unfortunately, I didn't boot the machine after adding RAM but before swapping drives, so I don't really know if this is being caused by the added RAM or a change in FreeBSD. I can always pull the RAM (or put in the old drive) but both require I open that damn box and it's built like a tank. Either way, I'm sunk... I need the RAM and I don't want to lock myself into using an older version of FreeBSD I won't be able to upgrade, for obvious reasons. Maybe I'll go play with the OS Type. I wonder if OS/2, Win NT, or Win 95 might select it somehow (right now it's set to "Other", and I'd hate to have to specify a "WinSomething" to make this work, heheheh). HP's are strange sometimes. The damn scrolling config utility gives me a headache. Thanks for the hints though. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Nov 26 12:00:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29352 for freebsd-smp-outgoing; Thu, 26 Nov 1998 12:00:09 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29345 for ; Thu, 26 Nov 1998 12:00:07 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id OAA02448 for freebsd-smp@freebsd.org; Thu, 26 Nov 1998 14:00:01 -0600 (CST) From: Joe Greco Message-Id: <199811262000.OAA02448@aurora.sol.net> Subject: Re: Help, cannot make HP Vectra XU work In-Reply-To: <199811251645.RAA19467@midten.fast.no> from "Tor.Egge@fast.no" at "Nov 25, 98 05:45:08 pm" To: Tor.Egge@fast.no Date: Thu, 26 Nov 1998 13:58:41 -0600 (CST) Cc: freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > > INT conforms conforms 1 1 255 1 > ^^^ > > Try this patch: > > Index: sys/i386/i386/mp_machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v > retrieving revision 1.83 > diff -u -r1.83 mp_machdep.c > --- mp_machdep.c 1998/10/10 13:37:16 1.83 > +++ mp_machdep.c 1998/11/25 16:39:29 > @@ -1197,11 +1197,26 @@ > static int > int_entry(int_entry_ptr entry, int intr) > { > + int apic; > + > io_apic_ints[intr].int_type = entry->int_type; > io_apic_ints[intr].int_flags = entry->int_flags; > io_apic_ints[intr].src_bus_id = entry->src_bus_id; > io_apic_ints[intr].src_bus_irq = entry->src_bus_irq; > - io_apic_ints[intr].dst_apic_id = entry->dst_apic_id; > + if (entry->dst_apic_id == 255) { > + /* This signal goes to all IO APICS. Select an IO APIC > + with sufficient number of interrupt pins */ > + for (apic = 0; apic < mp_napics; apic++) > + if (((io_apic_read(apic, IOAPIC_VER) & > + IOART_VER_MAXREDIR) >> MAXREDIRSHIFT) >= > + entry->dst_apic_int) > + break; > + if (apic < mp_napics) > + io_apic_ints[intr].dst_apic_id = IO_TO_ID(apic); > + else > + io_apic_ints[intr].dst_apic_id = entry->dst_apic_id; > + } else > + io_apic_ints[intr].dst_apic_id = entry->dst_apic_id; > io_apic_ints[intr].dst_apic_int = entry->dst_apic_int; > > return 1; Woohoo!! Thank you! My gamers thank you too, even though they probably don't know what FreeBSD is. ;-) Is this a patch likely to make it into FreeBSD, or should I archive this separately for future upgrades? Thank you very much, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Nov 27 14:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01874 for freebsd-smp-outgoing; Fri, 27 Nov 1998 14:35:45 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01869 for ; Fri, 27 Nov 1998 14:35:44 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william.cybcon.com (william@pm3a-24.cybcon.com [205.147.75.153]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id OAA04404 for ; Fri, 27 Nov 1998 14:35:22 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 27 Nov 1998 14:33:30 -0800 (PST) From: William Woods To: freebsd-smp@FreeBSD.ORG Subject: Weird CPU useage Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey guys, I have a dual PP200 with 128 megs mem. When I do a top I get this.....look ath the pecentages...does this make sence? PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 19262 william 105 10 692K 284K CPU1 1 25:11 123.14% 123.14% rc5des 17515 william 105 10 692K 268K RUN 0 45:04 122.22% 122.22% rc5des 3495 william 2 0 20120K 18428K select 0 3:29 1.46% 1.46% XF86_SVGA 162 root 2 0 1268K 760K select 0 3:08 1.07% 1.07% ppp 3516 william 10 0 1844K 1092K nanslp 0 0:34 0.83% 0.83% xosview 16723 william 2 0 4216K 3200K select 1 0:19 0.24% 0.24% xfmail 3509 william 2 0 4768K 3296K select 0 0:22 0.20% 0.20% kpanel 3510 william 2 0 4696K 3292K select 0 0:35 0.10% 0.10% kwm 141 root 2 0 764K 340K select 0 0:20 0.10% 0.10% moused Look at th 1st two readings, rc5...those are a little high arent they for a dual cpu system arent they? How can I be getting >200% CPU useage??? ---------------------------------- E-Mail: William Woods Date: 27-Nov-98 Time: 14:29:13 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Nov 28 05:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11788 for freebsd-smp-outgoing; Sat, 28 Nov 1998 05:01:05 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11783 for ; Sat, 28 Nov 1998 05:01:04 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id FAA05000 for ; Sat, 28 Nov 1998 05:00:55 -0800 (PST) Date: Sat, 28 Nov 1998 05:00:55 -0800 (PST) From: Bill Woods To: smp@FreeBSD.ORG Subject: Weird CPU useage on a dual PP200 - Please help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am running 3.0 -current, 2 day old code, on a dual PP200 with 128meg Ram. The system is NOT overclocked. (This is inmportant) The problem is this, when I run rc5 clients and do a top, I see them both running at >120% cpu useage each...that is too weird. I run two sessions of the client, on for each cpu. Now, just to test this, I wrote a small infinite loop progra (a cpu sucker) just to see how much CPU useage was done, again, a top produced the same thing >120% per cpu. Now this would be all fine and dandy, (faster is better right?), except for ythe heat produced. This weird situation produces a nice ammount of heat. I have a fan in front, one in the back of the case, and each cpu has a fan and heat sink on it. Any ideas would be appreciated. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Nov 28 14:02:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19178 for freebsd-smp-outgoing; Sat, 28 Nov 1998 14:02:54 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns1.digicomsystems.net (ns1.digicomsystems.net [206.148.67.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19170 for ; Sat, 28 Nov 1998 14:02:52 -0800 (PST) (envelope-from jramirez@digicomsystems.net) Received: from engineering.digicomsystems.net (engineering.digicomsystems.net [206.148.67.85]) by ns1.digicomsystems.net (8.9.1/8.9.1) with SMTP id QAA28730 for ; Sat, 28 Nov 1998 16:09:01 -0600 (CST) (envelope-from jramirez@digicomsystems.net) Message-Id: <4.1.19981128160710.00981ef0@ns1.digicomsystems.net> X-Sender: jramirez@ns1.digicomsystems.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 28 Nov 1998 16:07:59 -0600 To: freebsd-smp@FreeBSD.ORG From: "Jeremy L. Ramirez" Subject: mptable listing Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_248607977==_" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --=====================_248607977==_ Content-Type: text/plain; charset="us-ascii" Attached is an mptable listing for a Tyan Tiger 100 S1832DL motherboard..... --=====================_248607977==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="listing" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb570 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x9c mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f6890 signature: 'PCMP' base table length: 268 version: 1.1 checksum: 0xd5 OEM ID: 'INTEL ' Product ID: '440BX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 25 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0x183fbff 1 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 11 2 11 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 2 10 2 16 SMI conforms conforms 2 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=3 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== --=====================_248607977==_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Nov 28 14:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20551 for freebsd-smp-outgoing; Sat, 28 Nov 1998 14:19:21 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from NS1.HomeMortgageUSA.Com (Shell.Bourg.Net [207.229.69.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20543 for ; Sat, 28 Nov 1998 14:19:18 -0800 (PST) (envelope-from gus@Bourg.Net) Received: from localhost (gus@localhost) by NS1.HomeMortgageUSA.Com (8.9.1/8.8.7) with SMTP id OAA14630 for ; Sat, 28 Nov 1998 14:22:23 -0800 (PST) (envelope-from gus@Bourg.Net) Date: Sat, 28 Nov 1998 14:22:23 -0800 (PST) From: Gus Bourg X-Sender: gus@NS1.HomeMortgageUSA.Com To: freebsd-smp@FreeBSD.ORG Subject: 25 pin apic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I read an earlier message regarding 25 interrupt pins. It seems FreeBSD at the moment only supports 24, is that still true? I have a couple of Compaq Proliant 3000s here that I want to get up and running with FreeBSD/SMP, but I get the same error, panic: assign_apic_irq: inconsistent table. Are there any known workarounds for this? Are there plans to support more than 24pins? Thanks! Gus Bourg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Nov 28 15:32:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24966 for freebsd-smp-outgoing; Sat, 28 Nov 1998 15:32:30 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24954 for ; Sat, 28 Nov 1998 15:32:25 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 21177 invoked by uid 1001); 28 Nov 1998 23:32:13 +0000 (GMT) To: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Patches and mptable for Supermicro P6DGU with 440GX chipset X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 29 Nov 1998 00:32:13 +0100 Message-ID: <21175.912295933@verdi.nethelp.no> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I now have FreeBSD-current up and running on a Supermicro P6DGU mother- board with 440GX chipset, 2 x PII-400 and onboard Adaptec 7890 U2W SCSI. Getting FreeBSD up and running was relatively painless, and it seems to be working great so far. The only SMP options I'm currently using are SMP and APIC_IO. Included below are a patch for pci/pcisupport.c to identify the 440GX, and the mptable output for this system. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- --- pcisupport.c.orig Sat Oct 31 11:35:24 1998 +++ pcisupport.c Sun Nov 29 00:05:19 1998 @@ -226,6 +226,12 @@ return ("Intel 82443BX host to AGP bridge"); case 0x71928086: return ("Intel 82443BX host to PCI bridge (AGP disabled)"); + case 0x71a08086: + return ("Intel 82443GX host to PCI bridge"); + case 0x71a18086: + return ("Intel 82443GX host to AGP bridge"); + case 0x71a28086: + return ("Intel 82443GX host to PCI bridge (AGP disabled)"); case 0x12378086: fixwsc_natoma(tag); return ("Intel 82440FX (Natoma) PCI and memory controller"); =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb4f0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xbd mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f24b0 signature: 'PCMP' base table length: 268 version: 1.4 checksum: 0xc3 OEM ID: 'INTEL ' Product ID: '440BX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 25 local APIC address: 0xfee00000 extended table length: 16 extended table checksum: 234 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0x183fbff 1 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 2 10 2 16 INT active-lo level 2 11 2 17 SMI conforms conforms 2 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Nov 28 18:20:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10264 for freebsd-smp-outgoing; Sat, 28 Nov 1998 18:20:40 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from NS1.HomeMortgageUSA.Com (Shell.Bourg.Net [207.229.69.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10259 for ; Sat, 28 Nov 1998 18:20:38 -0800 (PST) (envelope-from gus@Bourg.Net) Received: from localhost (gus@localhost) by NS1.HomeMortgageUSA.Com (8.9.1/8.8.7) with SMTP id SAA19077 for ; Sat, 28 Nov 1998 18:23:51 -0800 (PST) (envelope-from gus@Bourg.Net) Date: Sat, 28 Nov 1998 18:23:51 -0800 (PST) From: Gus Bourg X-Sender: gus@NS1.HomeMortgageUSA.Com To: freebsd-smp@FreeBSD.ORG Subject: Eek! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tried a modification to /usr/src/i386/i386/mp_machdep.c to see if I could get my Compaq box up, and while the kernel didn't panic, I get this: Programming 35 pins in IOAPIC #0 IOAPIC #0 intpint 25 -> irq -1 IOAPIC #0 intpint 26 -> irq -1 IOAPIC #0 intpint 27 -> irq 20 IOAPIC #0 intpint 28 -> irq 19 IOAPIC #0 intpint 29 -> irq 18 IOAPIC #0 intpint 30 -> irq 17 IOAPIC #0 intpint 31 -> irq 16 And then the box just totally locks up. Any ideas? Thanks! Gus Bourg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message