From owner-freebsd-smp Mon Aug 2 11:18:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 838FC14D51; Mon, 2 Aug 1999 11:18:21 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA01728; Mon, 2 Aug 1999 11:17:53 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 2 Aug 1999 11:17:53 -0700 (PDT) From: Doug X-Sender: doug@dt011n65.san.rr.com To: William Woods Cc: freebsd-smp@freebsd.org, freebsd-questions@freebsd.org Subject: Re: CPU Useage In-Reply-To: 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 Fri, 30 Jul 1999, William Woods wrote: > Not here, there is only one meter for both CPU's... Well, I feel silly. I thought sure that I saw two cpu meters on xosview, but having checked it now I can see that it only has one. I will see if I can find the meter app that had two later today. Sorry for the confusion, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Aug 2 14:28:32 1999 Delivered-To: freebsd-smp@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B603B14C36 for ; Mon, 2 Aug 1999 14:28:30 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.8.8/8.8.8) with ESMTP id OAA15922 for ; Mon, 2 Aug 1999 14:28:21 -0700 (PDT) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.1) id OAA01822 for smp@freebsd.org; Mon, 2 Aug 1999 14:28:31 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <199908022128.OAA01822@realtime.exit.com> Subject: ASUS P2B-DS versus SMP. To: smp@freebsd.org Date: Mon, 2 Aug 1999 14:28:31 -0700 (PDT) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL43 (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 Well, I went out and bought another PII 400 for my box, flashed my BIOS to 1.009, installed the processor, and built 3.2-stable for SMP. I experienced the same clock problems others have seen. I took a suggestion I saw in -hackers and flashed back to 1.006. Sure enough, the problems went away. I would strongly urge anyone with one of these motherboards who is trying to do SMP to contact ASUS (at tsd@asus.com) and report the problem. Maybe we can actually either get the BIOS fixed, or see what FreeBSD is doing wrong, if anything. (I sent my email to them this morning.) -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Aug 2 14:53:58 1999 Delivered-To: freebsd-smp@freebsd.org Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (Postfix) with ESMTP id 972ED14C8B for ; Mon, 2 Aug 1999 14:53:52 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id XAA00486; Mon, 2 Aug 1999 23:52:56 +0200 (CEST) (envelope-from fn) To: frank@tinker.exit.com Cc: smp@FreeBSD.ORG Subject: Re: ASUS P2B-DS versus SMP. References: <199908022128.OAA01822@realtime.exit.com> From: Frank Nobis Date: 02 Aug 1999 23:52:56 +0200 In-Reply-To: Frank Mayhar's message of "Mon, 2 Aug 1999 14:28:31 -0700 (PDT)" Message-ID: Lines: 21 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.1 (20 Minutes to Nikko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Mayhar writes: > Well, I went out and bought another PII 400 for my box, flashed my BIOS to > 1.009, installed the processor, and built 3.2-stable for SMP. I experienced > the same clock problems others have seen. I took a suggestion I saw in > -hackers and flashed back to 1.006. Sure enough, the problems went away. > I have the P2B-DS running here since a year now. I had BIOS 1.005, 1.007 and 1.008 now. Since then I am runnung current. There has been a short period of the clock problem, but that has gone month ago. Both CPUs are PII400 from the same build. Regards, Frank -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by SMP FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Aug 2 17: 7:28 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id AE3CE14A2D; Mon, 2 Aug 1999 17:07:18 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (usr1-11.cybcon.com [205.147.75.12]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id RAA13623; Mon, 2 Aug 1999 17:06:42 -0700 (PDT) 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 In-Reply-To: Date: Mon, 02 Aug 1999 17:06:54 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Doug Subject: Re: CPU Useage Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hehe, we all make mistakes...dod you find anything? William On 02-Aug-99 Doug wrote: > On Fri, 30 Jul 1999, William Woods wrote: > >> Not here, there is only one meter for both CPU's... > > Well, I feel silly. I thought sure that I saw two cpu meters on > xosview, but having checked it now I can see that it only has one. I will > see if I can find the meter app that had two later today. > > Sorry for the confusion, > > Doug > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message ---------------------------------- E-Mail: William Woods Date: 02-Aug-99 Time: 17:06:29 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 Mon Aug 2 17:17:42 1999 Delivered-To: freebsd-smp@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by hub.freebsd.org (Postfix) with ESMTP id 831CE1509B for ; Mon, 2 Aug 1999 17:17:28 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (housley@localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id UAA01212; Mon, 2 Aug 1999 20:17:08 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <37A63504.3B3EF84D@thehousleys.net> Date: Mon, 02 Aug 1999 20:17:08 -0400 From: "James E. Housley" X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: frank@tinker.exit.com Cc: smp@FreeBSD.ORG Subject: Re: ASUS P2B-DS versus SMP. References: <199908022128.OAA01822@realtime.exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Mayhar wrote: > > Well, I went out and bought another PII 400 for my box, flashed my BIOS to > 1.009, installed the processor, and built 3.2-stable for SMP. I experienced > the same clock problems others have seen. I took a suggestion I saw in > -hackers and flashed back to 1.006. Sure enough, the problems went away. > > I would strongly urge anyone with one of these motherboards who is trying to > do SMP to contact ASUS (at tsd@asus.com) and report the problem. Maybe we > can actually either get the BIOS fixed, or see what FreeBSD is doing wrong, > if anything. (I sent my email to them this morning.) > -- Following multiple suggestions I got stats running on my ASUS P2B-D 3.x-Stable BIOS 1.008 by enabling APM in the bios and adding the following to my kernel. It didn't work until I added the flag 0x0020 # # Notes on APM # The flags takes the following meaning for apm0: # 0x0020 Statclock is broken. # 0x0011 Limit APM protocol to 1.1 or 1.0 # 0x0010 Limit APM protocol to 1.0 # device apm0 at isa? flags 0x0020 Jim. --- James E. Housley PGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Aug 2 22:58:41 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 84F881521D for ; Mon, 2 Aug 1999 22:57:46 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990803055724.SWBT8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com> for ; Mon, 2 Aug 1999 22:57:24 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id AAA25918 for freebsd-smp@freebsd.org; Tue, 3 Aug 1999 00:57:19 -0700 Date: Tue, 3 Aug 1999 00:57:19 -0700 From: Arun Sharma To: freebsd-smp@freebsd.org Subject: xosview and SMP Message-ID: <19990803005719.A25911@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I made some changes to xosview today to make it understand SMP on FreeBSD. However I can't see a way of getting per CPU usage info out of -current. Am I missing something ? Is it possible to do something better than reading kvm ? Is sysctl the right way to do it ? (VM meter seems to use it nicely). If sysctl is the right way, would it be possible to dynamically generate sysctl nodes ? Are there examples of it somewhere ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 1:21:32 1999 Delivered-To: freebsd-smp@freebsd.org Received: from is.lamefree.com (is.lamefree.com [209.84.189.37]) by hub.freebsd.org (Postfix) with ESMTP id B787215248 for ; Tue, 3 Aug 1999 01:21:29 -0700 (PDT) (envelope-from stalker@feerbsd.org) Received: from localhost (stalker@localhost) by is.lamefree.com (8.9.3/8.9.1) with ESMTP id BAA51910; Tue, 3 Aug 1999 01:21:14 -0700 (PDT) Date: Tue, 3 Aug 1999 01:21:14 -0700 (PDT) From: stalker X-Sender: stalker@is.lamefree.com To: "James E. Housley" Cc: frank@tinker.exit.com, smp@FreeBSD.ORG Subject: Re: ASUS P2B-DS versus SMP. In-Reply-To: <37A63504.3B3EF84D@thehousleys.net> 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 FYI to all p2b-d(s) owners, asus has posted the release of the version 1010 bios to their website.. http://www.asus.com.tw/ It says somethin in the release notes about a y2k fix.. stalks On Mon, 2 Aug 1999, James E. Housley wrote: > Frank Mayhar wrote: > > > > Well, I went out and bought another PII 400 for my box, flashed my BIOS to > > 1.009, installed the processor, and built 3.2-stable for SMP. I experienced > > the same clock problems others have seen. I took a suggestion I saw in > > -hackers and flashed back to 1.006. Sure enough, the problems went away. > > > > I would strongly urge anyone with one of these motherboards who is trying to > > do SMP to contact ASUS (at tsd@asus.com) and report the problem. Maybe we > > can actually either get the BIOS fixed, or see what FreeBSD is doing wrong, > > if anything. (I sent my email to them this morning.) > > -- > > Following multiple suggestions I got stats running on my ASUS P2B-D 3.x-Stable BIOS 1.008 by enabling APM in the bios and adding the following to my kernel. It didn't work until I added the flag 0x0020 > > # > # Notes on APM > # The flags takes the following meaning for apm0: > # 0x0020 Statclock is broken. > # 0x0011 Limit APM protocol to 1.1 or 1.0 > # 0x0010 Limit APM protocol to 1.0 > # > device apm0 at isa? flags 0x0020 > > Jim. > --- > James E. Housley PGP: 1024/03983B4D > System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 > Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE > > "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 6:13:48 1999 Delivered-To: freebsd-smp@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E5E3214DDE for ; Tue, 3 Aug 1999 06:13:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 108C41C1E; Tue, 3 Aug 1999 21:12:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: stalker Cc: "James E. Housley" , frank@tinker.exit.com, smp@FreeBSD.ORG Subject: Re: ASUS P2B-DS versus SMP. In-reply-to: Your message of "Tue, 03 Aug 1999 01:21:14 MST." Date: Tue, 03 Aug 1999 21:12:36 +0800 From: Peter Wemm Message-Id: <19990803131236.108C41C1E@overcee.netplex.com.au> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org stalker wrote: > FYI to all p2b-d(s) owners, asus has posted the release of the version > 1010 bios to their website.. http://www.asus.com.tw/ > > It says somethin in the release notes about a y2k fix.. It's that y2k fix that tends to cause all the trouble. As I understand it, something like this happens.. The clock chips have a bunch of counters and a chunk of battery backed up ram. The first few registers correspond to the counters, and the remainder of the address registers correspond to those ram cells. And there's the kicker.. The clocks generally have 2 digit year counters and the century byte is normally in a RAM cell, and the bios does the manual rollover of the centory byte when the end of century happens and the year counter rolls over. (This is the first phase of the y2k fix btw, most original bioses didn't detect the YY year rollover and neglected to update the century.) However, some OS's dont use the BIOS, so this hack doesn't work. Most unixes are included. FreeBSD happens to do the right thing and maintain the century byte, so FreeBSD is normally Y2K fundamentally compliant regardless of whether the underlying bios is or not. IE: if you're running under FreeBSD at the Y2K rollover, everything will work as expected, unless you've got a really old system that doesn't have a century byte at all. (I think the PC and PC/XT were the main class of machines that didn't have this, the AT and beyond all had it as far as I know. Some older clones may be missing it). Anyway, it seems certain Y2K compliancy software checkers were not satisfied with this and decided to test the clock chip directly with the bios interrupts disabled, and therefore disabling the software workaround. Since it's not easy to do this in hardware, most systems did it in software. Normally the first 16 addresses in the clock are counters and the rest are RAM. The century byte is at offset 0x32 (50th byte) and well away from the hardware registers and right in the middle of RAM, and therefore a pest to convert it to a register/counter/whatever. So, the manufacturers came up with a new software workaround... On the 440BX/LX/whatever chipsets and higher, the chip can be programmed to generate a SMI trap when accessing certain registers, which is NOT maskable by software. THey elected to trap all accesses to the realtime clock and cmos registers (it's done by a register window, so it's an all or nothing deal). So, when (say) freebsd reads or writes the hardware realtime clock, a SMI trap is generated. The processor stalls, dumps state, and begins executing the bios in REAL mode to "detect" the y2k rollover and simulate the century byte changing automatically. The y2k testers are fooled since there is no trace of the Bios "patch" happening except that it appears to take a rather long time to read/write the clock registers. And this callout in SMI mode to the bios is what is usually the culprit for screwing up the statclock in newer systems. We do not need the workaround. If you have the option, turn *OFF* the Y2K fixes in your bios - they give you the option for a reason - it's DAMN SLOW! and you most definately need to turn it off after Jan 1 2000. The other thing we can do (luoqi has posted patches) is disable this hack in the BX chipset and get the bios out of our damn hair. (Footnote, I just did some checking.. we actually don't quite do what I suggested above, we in fact totally ignore the century byte. If the YY value is < 70, we assume post-2000. Y2K compliant bioses will patch this on boot anyway.) > stalks > > On Mon, 2 Aug 1999, James E. Housley wrote: > > > Frank Mayhar wrote: > > > > > > Well, I went out and bought another PII 400 for my box, flashed my BIOS t o > > > 1.009, installed the processor, and built 3.2-stable for SMP. I experien ced > > > the same clock problems others have seen. I took a suggestion I saw in > > > -hackers and flashed back to 1.006. Sure enough, the problems went away. > > > > > > I would strongly urge anyone with one of these motherboards who is trying to > > > do SMP to contact ASUS (at tsd@asus.com) and report the problem. Maybe w e > > > can actually either get the BIOS fixed, or see what FreeBSD is doing wron g, > > > if anything. (I sent my email to them this morning.) > > > -- > > > > Following multiple suggestions I got stats running on my ASUS P2B-D 3.x-Sta ble BIOS 1.008 by enabling APM in the bios and adding the following to my k ernel. It didn't work until I added the flag 0x0020 > > > > # > > # Notes on APM > > # The flags takes the following meaning for apm0: > > # 0x0020 Statclock is broken. > > # 0x0011 Limit APM protocol to 1.1 or 1.0 > > # 0x0010 Limit APM protocol to 1.0 > > # > > device apm0 at isa? flags 0x0020 > > > > Jim. > > --- > > James E. Housley PGP: 1024/03983B4D > > System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 > > Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 7:31:31 1999 Delivered-To: freebsd-smp@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1263E14D85 for ; Tue, 3 Aug 1999 07:31:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA04667; Wed, 4 Aug 1999 00:29:51 +1000 Date: Wed, 4 Aug 1999 00:29:51 +1000 From: Bruce Evans Message-Id: <199908031429.AAA04667@godzilla.zeta.org.au> To: peter@netplex.com.au, stalker@feerbsd.org Subject: Re: ASUS P2B-DS versus SMP. Cc: frank@tinker.exit.com, jim@thehousleys.net, smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >However, some OS's dont use the BIOS, so this hack doesn't work. Most >unixes are included. FreeBSD happens to do the right thing and maintain >the century byte, so FreeBSD is normally Y2K fundamentally compliant >regardless of whether the underlying bios is or not. IE: if you're running FreeBSD doesn't use or maintain the century byte, except in some cases when the nonstandard undocumented option USE_RTC_CENTURY is configured. This option should be deleted. There is some chance of conflicting with a BIOS century byte update and/or bumping the century byte twice at the end of 1999. >under FreeBSD at the Y2K rollover, everything will work as expected, unless Here's what will happen: - the rollover will normally occur only in the kernel time variables. - if settimeofday(2) or clock_settime(2) is called after the rollover, then the RTC will be updated. Then the century byte will only be updated if USE_RTC_CENTURY is configured. - otherwise, the RTC will not be changed, so the century byte will not be updated. There is some chance of adjkerntz doing a settimeofday() so that this case doesn't apply. - on reboot, or perhaps when a BIOS call is made, the BIOS may update the century byte. - on boot or powerup, the BIOS may update the century byte. - on boot, FreeBSD will ignore the century byte unless USE_RTC_CENTURY is configured. This will just work until about 2070, except: - some RTC's will mishandle the leap year on 28 Feb 1999. On systems with the RTC set to local time, there is a good chance of adjkerntz doing a settimeofday() which fixes the problem. Is this what is expected? :-) >you've got a really old system that doesn't have a century byte at all. (I >think the PC and PC/XT were the main class of machines that didn't have >this, the AT and beyond all had it as far as I know. Some older clones may >be missing it). All systems with an RTC have the RAM where the century byte is. The issue is whether the BIOS supports it, and whether year 00 is handled as a leap year. >So, the manufacturers came up with a new software workaround... On the >440BX/LX/whatever chipsets and higher, the chip can be programmed to >generate a SMI trap when accessing certain registers, which is NOT maskable >by software. THey elected to trap all accesses to the realtime clock and >cmos registers (it's done by a register window, so it's an all or nothing >deal). So, when (say) freebsd reads or writes the hardware realtime clock, >a SMI trap is generated. The processor stalls, dumps state, and begins >executing the bios in REAL mode to "detect" the y2k rollover and simulate >the century byte changing automatically. The y2k testers are fooled since >there is no trace of the Bios "patch" happening except that it appears >to take a rather long time to read/write the clock registers. Gak! >And this callout in SMI mode to the bios is what is usually the culprit for >screwing up the statclock in newer systems. How does it break the statclock? Handling statclock interrupts in the BIOS would do it. Well, it is not easy determine the statclock status without clearing any interrupt. The SMI handler might have to call or include a statclock handler just to make RTC interrupts work under DOS. >(Footnote, I just did some checking.. we actually don't quite do what I >suggested above, we in fact totally ignore the century byte. If the YY >value is < 70, we assume post-2000. Y2K compliant bioses will patch this >on boot anyway.) Right. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 7:45:51 1999 Delivered-To: freebsd-smp@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 25BF614D85 for ; Tue, 3 Aug 1999 07:45:46 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B05431C1E; Tue, 3 Aug 1999 22:45:26 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: stalker@feerbsd.org, frank@tinker.exit.com, jim@thehousleys.net, smp@FreeBSD.ORG Subject: Re: ASUS P2B-DS versus SMP. In-reply-to: Your message of "Wed, 04 Aug 1999 00:29:51 +1000." <199908031429.AAA04667@godzilla.zeta.org.au> Date: Tue, 03 Aug 1999 22:45:26 +0800 From: Peter Wemm Message-Id: <19990803144526.B05431C1E@overcee.netplex.com.au> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bruce Evans wrote: > >you've got a really old system that doesn't have a century byte at all. (I > >think the PC and PC/XT were the main class of machines that didn't have > >this, the AT and beyond all had it as far as I know. Some older clones may > >be missing it). > > All systems with an RTC have the RAM where the century byte is. The issue > is whether the BIOS supports it, and whether year 00 is handled as a > leap year. Well, 00 (century prefix 20) is a leap year, the next three 00's are not leap years. > >So, the manufacturers came up with a new software workaround... On the > >440BX/LX/whatever chipsets and higher, the chip can be programmed to > >generate a SMI trap when accessing certain registers, which is NOT maskable > >by software. THey elected to trap all accesses to the realtime clock and > >cmos registers (it's done by a register window, so it's an all or nothing > >deal). So, when (say) freebsd reads or writes the hardware realtime clock, > >a SMI trap is generated. The processor stalls, dumps state, and begins > >executing the bios in REAL mode to "detect" the y2k rollover and simulate > >the century byte changing automatically. The y2k testers are fooled since > >there is no trace of the Bios "patch" happening except that it appears > >to take a rather long time to read/write the clock registers. > > Gak! > > >And this callout in SMI mode to the bios is what is usually the culprit for > >screwing up the statclock in newer systems. > > How does it break the statclock? Handling statclock interrupts in the > BIOS would do it. Well, it is not easy determine the statclock status > without clearing any interrupt. The SMI handler might have to call > or include a statclock handler just to make RTC interrupts work under > DOS. I've heard rumors that it resets the rtc 128hz interrupt or somehow disables it if a 128Hz interrupt happens while in SMI mode. > >(Footnote, I just did some checking.. we actually don't quite do what I > >suggested above, we in fact totally ignore the century byte. If the YY > >value is < 70, we assume post-2000. Y2K compliant bioses will patch this > >on boot anyway.) > > Right. I wonder though, should we always write the century back, regardless of the USE_RTC_CENTURY option? If that's not safe (ie: maybe the bios uses century offset by 19, ie: 00 century = 1900, 01 = 2000, etc), then perhaps read the century at startup and change (ie: increment) it at rollover. So, 00 will change to 01, or 19 will change to 20, whatever. > Bruce Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 13:10:56 1999 Delivered-To: freebsd-smp@freebsd.org Received: from roc.jmu.edu (roc.jmu.edu [134.126.10.50]) by hub.freebsd.org (Postfix) with ESMTP id 7137114D4E for ; Tue, 3 Aug 1999 13:10:37 -0700 (PDT) (envelope-from gracebc@jmu.edu) Received: from jmu.edu (host11-213.prestige.net [208.249.158.213] (may be forged)) by roc.jmu.edu (8.8.8/8.8.8) with ESMTP id QAA17763 for ; Tue, 3 Aug 1999 16:10:35 -0400 (EDT) Message-ID: <37A74C6C.F60AC0A0@jmu.edu> Date: Tue, 03 Aug 1999 16:09:16 -0400 From: Brenden Grace X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Subject: 4 way smp? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am not a member of the freeBSD smp list ... does FreeBSD currently support 4 way SMP? I am currently using RedHat 6.0 but was hoping to switch over - I couldnt find this information anywhere on the freeBSD smp web page. please mail responses to : gracebc@jmu.edu thanks -brenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Aug 3 16:14:58 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id BDB6B14CCB for ; Tue, 3 Aug 1999 16:14:56 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-41.cybcon.com [205.147.75.170]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id QAA10570; Tue, 3 Aug 1999 16:14:10 -0700 (PDT) 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 In-Reply-To: <19990803005719.A25911@home.com> Date: Tue, 03 Aug 1999 16:14:25 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Arun Sharma Subject: RE: xosview and SMP Cc: freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmmmmmare you saying the meters now display BOTH CPUs? If so, could you infiorm me as to what you did? I would like to have both CPU's useage displayed. On 03-Aug-99 Arun Sharma wrote: > I made some changes to xosview today to make it understand SMP on > FreeBSD. However I can't see a way of getting per CPU usage info > out of -current. > > Am I missing something ? Is it possible to do something better than > reading kvm ? Is sysctl the right way to do it ? (VM meter seems to > use it nicely). If sysctl is the right way, would it be possible to > dynamically generate sysctl nodes ? Are there examples of it somewhere ? > > -Arun > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message ---------------------------------- E-Mail: William Woods Date: 03-Aug-99 Time: 15:28:47 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 Tue Aug 3 16:40:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 9F32414C46 for ; Tue, 3 Aug 1999 16:40:18 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990803233837.CVWU8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Tue, 3 Aug 1999 16:38:37 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id SAA28371; Tue, 3 Aug 1999 18:38:30 -0700 Date: Tue, 3 Aug 1999 18:38:30 -0700 From: Arun Sharma To: William Woods Cc: freebsd-smp@FreeBSD.ORG Subject: Re: xosview and SMP Message-ID: <19990803183830.A28346@home.com> References: <19990803005719.A25911@home.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=FCuugMFkClbJLl1L X-Mailer: Mutt 0.95.5i In-Reply-To: ; from William Woods on Tue, Aug 03, 1999 at 04:14:25PM -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii On Tue, Aug 03, 1999 at 04:14:25PM -0700, William Woods wrote: > Hmmmmmare you saying the meters now display BOTH CPUs? If so, could > you infiorm me as to what you did? I would like to have both CPU's > useage displayed. It shows as many CPUs as there are on the system, but all of them show the same information - because I don't see a way of getting per CPU usage info from the FreeBSD kernel. If you want to give it a try, use the attached patch. -Arun --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=xosview-bsd-patch --- MeterMaker.cc Mon Jan 25 12:15:26 1999 +++ /usr/ports/sysutils/xosview.mine/work/xosview-1.7.1/bsd/MeterMaker.cc Mon Aug 2 20:26:19 1999 @@ -44,8 +44,12 @@ push(new LoadMeter(_xos)); // Standard meters (usually added, but users could turn them off) - if (_xos->isResourceTrue("cpu")) - push(new CPUMeter(_xos)); + if (_xos->isResourceTrue("cpu")) { + int cpuCount = CPUMeter::countCPUs(); + int start = (cpuCount == 0) ? 0 : 1; + for (int i = start ; i <= cpuCount ; i++) + push(new CPUMeter(_xos, CPUMeter::cpuStr(i))); + } if (_xos->isResourceTrue("mem")) push(new MemMeter(_xos)); --- cpumeter.cc Sun Jan 31 12:18:49 1999 +++ /usr/ports/sysutils/xosview.mine/work/xosview-1.7.1/bsd/cpumeter.cc Mon Aug 2 22:11:18 1999 @@ -16,6 +16,9 @@ // #include // For CPUSTATES #define. BCG #include // For use of atoi BCG +#include +#include +#include #include "general.h" #include "cpumeter.h" #include "kernel.h" // For NetBSD-specific icky kvm_ code. BCG @@ -23,12 +26,12 @@ CVSID("$Id: cpumeter.cc,v 1.16 1999/01/31 20:18:49 bgrayson Exp $"); CVSID_DOT_H(CPUMETER_H_CVSID); -CPUMeter::CPUMeter( XOSView *parent ) +CPUMeter::CPUMeter( XOSView *parent, const char *cpuID) #ifdef XOSVIEW_FREEBSD -: FieldMeterGraph( parent, 5, "CPU", "USR/NICE/SYS/INT/FREE" ){ +: FieldMeterGraph( parent, 5, cpuID, "USR/NICE/SYS/INT/FREE" ){ #define FREE_INDEX 4 #else -: FieldMeterGraph( parent, 4, "CPU", "USR/NICE/SYS/FREE" ){ +: FieldMeterGraph( parent, 4, cpuID, "USR/NICE/SYS/FREE" ){ #define FREE_INDEX 3 #endif for ( int i = 0 ; i < 2 ; i++ ) @@ -124,3 +127,31 @@ cpuindex_ = (cpuindex_ + 1) % 2; } + + +int CPUMeter::countCPUs(void) +{ + int mib[2], ncpu; + size_t len; + + mib[0] = CTL_HW; + mib[1] = HW_NCPU; + len = sizeof(ncpu); + sysctl(mib, 2, &ncpu, &len, NULL, 0); + + return ncpu; +} + +const char *CPUMeter::cpuStr(int num) +{ + static char buffer[32]; + ostrstream str(buffer, 32); + + str << "cpu"; + if (num != 0) + str << (num - 1); + str << ends; + + return buffer; +} + --- cpumeter.h Tue Oct 20 12:37:33 1998 +++ /usr/ports/sysutils/xosview.mine/work/xosview-1.7.1/bsd/cpumeter.h Mon Aug 2 21:43:34 1999 @@ -23,12 +23,14 @@ class CPUMeter : public FieldMeterGraph { public: - CPUMeter( XOSView *parent ); + CPUMeter( XOSView *parent, const char *cpuID = "cpu"); ~CPUMeter( void ); const char *name( void ) const { return "CPUMeter"; } void checkevent( void ); + static int countCPUs(void); + static const char *cpuStr(int num); void checkResources( void ); protected: long cputime_[2][5]; --FCuugMFkClbJLl1L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Aug 4 1:13:13 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id AF4A114DF7 for ; Wed, 4 Aug 1999 01:13:09 -0700 (PDT) (envelope-from thierry.herbelot@alcatel.fr) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id JAA02659; Wed, 4 Aug 1999 09:07:22 +0200 Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id KAA26710; Wed, 4 Aug 1999 10:04:48 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with ESMTP id JAA23780; Wed, 4 Aug 1999 09:49:59 +0200 (MEST) Received: from alcatel.fr by telss1 (8.8.8+Sun/SMI-SVR4) id JAA08526; Wed, 4 Aug 1999 09:58:55 +0200 (MET DST) Message-ID: <37A7F2E5.1047F10C@alcatel.fr> Date: Wed, 04 Aug 1999 09:59:33 +0200 From: Thierry Herbelot Reply-To: thierry.herbelot@alcatel.fr Organization: ALCATEL CIT Nanterre X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Brenden Grace Cc: freebsd-smp@FreeBSD.ORG Subject: Re: 4 way smp? References: <37A74C6C.F60AC0A0@jmu.edu> 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 seen a success report from someone from ikos (www.ikos.com ?) which was using FreeBSD 4.0 on a 4-Proc SMP machine (you may want to have a look at the mailing list archives in www.freebsd.org) TfH PS : you will need a 4-Way SMP motherboard and 4 Xeons Brenden Grace wrote: > > I am not a member of the freeBSD smp list ... > does FreeBSD currently support 4 way SMP? I am currently using RedHat > 6.0 but was hoping to switch over - I couldnt find this information > anywhere on the freeBSD smp web page. > > please mail responses to : gracebc@jmu.edu > thanks > > -brenden > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Aug 4 8:22:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 35ADB14E3B for ; Wed, 4 Aug 1999 08:22:22 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA09170; Thu, 5 Aug 1999 01:21:35 +1000 Date: Thu, 5 Aug 1999 01:21:35 +1000 From: Bruce Evans Message-Id: <199908041521.BAA09170@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@netplex.com.au Subject: Re: ASUS P2B-DS versus SMP. Cc: frank@tinker.exit.com, jim@thehousleys.net, smp@FreeBSD.ORG, stalker@feerbsd.org Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >you've got a really old system that doesn't have a century byte at all. (I >> >think the PC and PC/XT were the main class of machines that didn't have >> >this, the AT and beyond all had it as far as I know. Some older clones may >> >be missing it). >> >> All systems with an RTC have the RAM where the century byte is. The issue >> is whether the BIOS supports it, and whether year 00 is handled as a >> leap year. > >Well, 00 (century prefix 20) is a leap year, the next three 00's are not >leap years. I checked what a 4 year old RTC does. It treats years 1900, 2000 and 2100 as leap years. I guess the CMOS byte is just RAM and doesn't affect leap year handling, and the hardware uses the simple rule `(year % 4) == 0' to determine leap years. >I wonder though, should we always write the century back, regardless of the >USE_RTC_CENTURY option? This would break any systems that use the century byte for something else. I don't know of any supported ones. The Interrupt List (1995 version) says that the byte is the low byte if the Configuration CRC for PS2's. >If that's not safe (ie: maybe the bios uses century offset by 19, ie: 00 >century = 1900, 01 = 2000, etc), then perhaps read the century at startup and >change (ie: increment) it at rollover. So, 00 will change to 01, or 19 will >change to 20, whatever. 19 might be part of a CRC :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Aug 4 8:59:12 1999 Delivered-To: freebsd-smp@freebsd.org Received: from par28.ma.ikos.com (par28.ma.ikos.com [137.103.105.228]) by hub.freebsd.org (Postfix) with ESMTP id 2ABF514C19 for ; Wed, 4 Aug 1999 08:59:08 -0700 (PDT) (envelope-from tich@par28.ma.ikos.com) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by par28.ma.ikos.com (8.8.7/8.8.7) id LAA10271; Wed, 4 Aug 1999 11:58:06 -0400 From: Richard Cownie To: thierry.herbelot@alcatel.fr, Thierry Herbelot , Brenden Grace Subject: Re: 4 way smp? Date: Wed, 4 Aug 1999 11:50:31 -0400 X-Mailer: KMail [version 1.1.0] Content-Type: text/plain Cc: freebsd-smp@FreeBSD.ORG References: <37A7F2E5.1047F10C@alcatel.fr> MIME-Version: 1.0 Message-Id: <99080411580500.10269@par28.ma.ikos.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 04 Aug 1999, Thierry Herbelot wrote: > Hello > > I have seen a success report from someone from ikos (www.ikos.com ?) > which was using FreeBSD 4.0 on a 4-Proc SMP machine (you may want to > have a look at the mailing list archives in www.freebsd.org) > > TfH Yes, 4-way SMP works fine on an Intel SC450NX server (from www.sagelec.com) It was broken in 4.0-CURRENT for a few weeks but should be fine now. I'm running 4.0 only to get support for 4GB DRAM - 4way SMP probably also works fine in 3.2 ? 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 Fri Aug 6 23:26:39 1999 Delivered-To: freebsd-smp@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 5559E14C8F for ; Fri, 6 Aug 1999 23:26:33 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:ULWvn6zdDsMfu5UZZAEPJ/KeAEvudNpB@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id PAA05197; Sat, 7 Aug 1999 15:25:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA10251; Sat, 7 Aug 1999 15:29:40 +0900 (JST) Message-Id: <199908070629.PAA10251@zodiac.mech.utsunomiya-u.ac.jp> To: Nate Williams Cc: freebsd-smp@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP + XDM = keyboard lockup In-reply-to: Your message of "Fri, 23 Jul 1999 10:24:10 CST." <199907231624.KAA07741@mt.sri.com> References: <199907221817.LAA09698@usr05.primenet.com> <199907230402.NAA02136@zodiac.mech.utsunomiya-u.ac.jp> <199907231624.KAA07741@mt.sri.com> Date: Sat, 07 Aug 1999 15:29:39 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> I guess it may not. After init forks and execs getty and xdm, we >> don't know the exact order in which these processes will be scheduled >> to run on which CPU, do we? /etc/ttys does not ensure the order of >> execution. >> >> If xdm happens to run before other getty processes, it may grab a vty >> which will be eventually opened by a getty later. > >Actually, I had forgotten about this. This is true because the line in >/etc/ttys doesn't specify *which* tty for X to use. If we could easily >force X to use that specific tty, it would avoid this problem. > >Nate We can specify the vty number in /usr/X11R6/lib/X11/xdm/Xservers as: :0 local /usr/X11R6/bin/X vt4 can we not? I know this is troublesome in the sense that if we want to change the vty for X, we need to update both /etc/tty and /usr/X11R6/lib/X11/xdm/Xservers ;-< In any case, the race condition regarding xdm and getty which we discussed in this mailing list should be reflected in FAQ. Our FAQ currently has an entry for xdm; it gives you the impression that the race condition exists only when we start xdm from one of rc.* files, and people may think there should be no problem when xdm is started from /etc/ttys. ------------------------------------------------------------------------------ 9.7 How do I start XDM on boot? There are two schools of thought on how to start xdm. One school starts xdm from /etc/ttys using the supplied example, while the other simply runs xdm from rc.local or from a X.sh script in /usr/local/etc/rc.d. Both are equally valid, and one may work in situations where the other doesn't. In both cases the result is the same: X will popup a graphical login: prompt. The ttys method has the advantage of documenting which vty X will start on and passing the responsibility of restarting the X server on logout to init. The rc.local method makes it easy to kill xdm if there is a problem starting the X server. If loaded from rc.local, xdm should be started without any arguments (i.e., as a daemon). xdm must start AFTER getty runs, or else gettty and xdm will con- flict, locking out the console. The best way around this is to have the script sleep 10 seconds or so then launch xdm. A previous version of the FAQ said to add the vt you want X to use to the /usr/X11R6/lib/X11/xdm/Xservers file. This is not necessary: X will use the first free vt it finds. ------------------------------------------------------------------------------ The last paragraph should be modified to something like: "If you are to start xdm from /etc/ttys, there still is a chance of conflict between xdm and getty. One way to avoid this is to add the vt number in the /usr/X11R6/lib/X11/xdm/Xservers file. :0 local /usr/X11R6/bin/X vt4 The above example will direct the X server to run in /dev/ttyv3. Note the number is offset by one. The X server counts the vt from one, whereas the FreeBSD kernel numbers vt from zero." Comments? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Aug 7 4:55:50 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp.shellnet.co.uk (smtp.shellnet.co.uk [194.129.209.14]) by hub.freebsd.org (Postfix) with ESMTP id 3628614CA4; Sat, 7 Aug 1999 04:55:41 -0700 (PDT) (envelope-from flec@flec.co.uk) Received: from STEVENF (eth2-fw1.bolton.shellnet.co.uk [194.129.209.8]) by smtp.shellnet.co.uk (8.9.3/8.9.1-shellnet.stevenf) with SMTP id MAA19691; Sat, 7 Aug 1999 12:54:45 +0100 (BST) Posted-Date: Sat, 7 Aug 1999 12:54:45 +0100 (BST) From: flec@flec.co.uk (Steven Fletcher) To: smp@freebsd.org Cc: scsi@freebsd.org Subject: Crash when trying to install 4.0-19990806-CURRENT Date: Sat, 07 Aug 1999 11:54:45 GMT Message-ID: <37ad1bf1.89142680@194.129.209.14> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all.=20 I'm tryingt to install 4.0-19990806-CURRENT on an Intel SC450NX machine, which currently has a Mylex DAC960 controller (I know these aren't supported yet... but I hope to go via an Adaptec controller or similar. Anyway, as soon as the kern.flp install floppy is plonked in, the following is dumped to the screen and the system stops. int=3D0000000d err=3D00000000 efl=3D00030002 eip=3D0000f273 eax=3D0000fa09 ebx=3D0000faa0 ecx=3D00000001 edx=3D0009fa09 esi=3D00000270 edi=3D000000d1 ebp=3D000003d4 esp=3D000003d0 cs=3Df000 ds=3D9f80 es=3D9f80 fs=3D0040 gs=3D0000 ss=3D9c7d cs:eip=3D0f 01 54 08 2e 0f 01 1e-c2 f1 0f 20 c0 0c 01 0f ss:esp=3D03 00 00 c8 00 c8 80 9f-d1 00 70 02 00 00 e8 03 System halted I give it a three fingered salute and get the following back: DAC960: System BIOS fatal error - INT 15H function 87H (Copy extended memory) failed. At which point even the keyboard stops responding. Does anyone know what's going on here? If anyone can help pleae respond to me directly also, as I am not subscribed to this list. Steven Fletcher - steven@shellnet.co.uk / flec@flec.co.uk Shellnet - http://www.shellnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Aug 7 5:32:50 1999 Delivered-To: freebsd-smp@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 694C014D0B; Sat, 7 Aug 1999 05:32:47 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sat, 7 Aug 1999 08:28:11 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> From: tcobb@staff.circle.net To: jkh@zippy.cdrom.com, freebsd-smp@freebsd.org Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG Subject: RE: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 08:28:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wonder why this is the case, too. However, there have been a series of reports of crashes and freezes in the 3.2 and 4.0 series that have gone unresolved and, in fact, unresponded. I'd like to be able to use FreeBSD in an SMP environment, but it just isn't stable on the box we've built (Supermicro P6DBU, 1GB ECC RAM, dual PIII 550, DPT RAID). Unfortunately, our hosting customer who is running a high-end e-commerce site on this machine isn't excited about being a testbed, they want a solution that works and stays working. --- Our issue may be related to the large memory config, but I'm not getting panics, just freezes, so it is tough to tell. If anyone has any suggestions, I'd love to hear them was I have to get them a working solution in place before next week or I lose this business. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Saturday, August 07, 1999 1:32 AM > To: tcobb@staff.circle.net > Cc: lightningweb@hotmail.com; freebsd-stable@FreeBSD.ORG; > greg@lightningweb.com; jeremy@lightningweb.com; > keith@lightningweb.com; > criter@lightningweb.com > Subject: Re: continued crashes with 3.1-Stable > > > > I think the problem is the SMP. I've been having frequent > > freezes with SMP under heavy webserver load with 3.2-R, > > and 3.2-S. I'm unfortunately led to believe that FreeBSD > > I wonder why this doesn't happen to Yahoo's SMP boxes then. > They run -stable and would be screaming blue murder if their > webservers were doing the same thing. So, for that matter, > would Hotmail. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message