From owner-freebsd-smp Mon Jun 14 14:24:43 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id C3BD815228; Mon, 14 Jun 1999 14:24:27 -0700 (PDT) (envelope-from james@ehlo.com) Received: from vrfy.ehlo.com (HSE-TOR-ppp21683.sympatico.ca [209.226.66.241]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id RAA00351; Mon, 14 Jun 1999 17:27:18 -0400 (EDT) Received: from james by vrfy.ehlo.com with local (Exim 2.12 #3) id 10teAp-0007oJ-00; Mon, 14 Jun 1999 17:21:43 -0400 Date: Mon, 14 Jun 1999 17:21:43 -0400 From: James FitzGibbon To: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: CPU states at 0.0% on 3.2-R SMP box ? Message-ID: <19990614172141.A30011@ehlo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Organization: EHLO Solutions Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Back in march of this year there was a thread in -questions and -smp about SMP boxes showing all CPU states at 0.0% and processes continuing to take up CPU time but not do any actual work. The responses to people's questions were usually along the lines of "Try 3.1-RELEASE, it should be fixed there". I've just installed 3.2-RELEASE on a Dual Xeon-450 ASUS board, and am seeing the same problem. I've tried using an aout version of /sbin/init, as was suggested by someone on the old thread, but that didn't solve anything. Is there a definate answer about this ? My boss says that when he last tried FreeBSD on this box, it was very unstable, and he corelates the wacky top behaviour with this instability. Hence, as long as top acts wacky, I can't move this box into production. I'm trying to find out if this is merely a presentation/lookup problem or if the CPU cycles really aren't being sliced up properly between processors. If anyone has more information, I'd really appreciate hearing it. Alternatively, if anyone who knows the SMP code wants to hack around on a box that exhibits this problem, I'd be glad to give you access. TIA. -- j. James FitzGibbon (JF647) james@ehlo.com EHLO Solutions Voice/Fax +1 416 410-0100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 14 14:35: 9 1999 Delivered-To: freebsd-smp@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 6437914C03; Mon, 14 Jun 1999 14:35:00 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id OAA01124; Mon, 14 Jun 1999 14:35:37 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (2670 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Mon, 14 Jun 1999 14:34:56 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id OAA55831; Mon, 14 Jun 1999 14:34:55 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906142134.OAA55831@sigma.veritas.com> From: Aaron Smith To: James FitzGibbon Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? In-reply-to: Your message of "Mon, 14 Jun 1999 17:21:43 EDT." <19990614172141.A30011@ehlo.com> Date: Mon, 14 Jun 1999 14:34:55 -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org this is a problem with an rtc interrupt being lost, which apparently wedges up all further rtc interrupts. i solved it by searching the mailing list archives and located this post: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=54158+0+archive/1999/freebsd-smp/19990607.freebsd-smp (in case the URL doesn't work for some reason it's by bob wilcox from may 20, the patch is supposedly from tor egge(?) and it patches clkintr). once i applied the patch i never saw any weirdness. apparently this is a temporary workaround? can somebody explain more fully? what cost am i paying for a patch named "BROKEN_RTC_KLUDGE"? Aaron Smith On Mon, 14 Jun 1999 17:21:43 EDT, James FitzGibbon writes: >Back in march of this year there was a thread in -questions and -smp about >SMP boxes showing all CPU states at 0.0% and processes continuing to take up >CPU time but not do any actual work. The responses to people's questions >were usually along the lines of "Try 3.1-RELEASE, it should be fixed there". > >I've just installed 3.2-RELEASE on a Dual Xeon-450 ASUS board, and am seeing >the same problem. I've tried using an aout version of /sbin/init, as was >suggested by someone on the old thread, but that didn't solve anything. > >Is there a definate answer about this ? My boss says that when he last >tried FreeBSD on this box, it was very unstable, and he corelates the wacky >top behaviour with this instability. Hence, as long as top acts wacky, I >can't move this box into production. > >I'm trying to find out if this is merely a presentation/lookup problem or if >the CPU cycles really aren't being sliced up properly between processors. >If anyone has more information, I'd really appreciate hearing it. >Alternatively, if anyone who knows the SMP code wants to hack around on a >box that exhibits this problem, I'd be glad to give you access. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 14 16:40:56 1999 Delivered-To: freebsd-smp@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id B7D7A14E3E; Mon, 14 Jun 1999 16:40:45 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=adv) by post.mail.nl.demon.net with smtp (Exim 2.02 #1) id 10tgLM-00076Y-00; Mon, 14 Jun 1999 23:40:44 +0000 Message-ID: <009c01beb6bf$7e7ecac0$0b00000a@adv.oldserver.demon.nl> From: "Marc Schneiders" To: "James FitzGibbon" , , Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? Date: Tue, 15 Jun 1999 01:41:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org James FitzGibbon wrote: >Back in march of this year there was a thread in -questions and -smp about >SMP boxes showing all CPU states at 0.0% and processes continuing to take up >CPU time but not do any actual work. The responses to people's questions >were usually along the lines of "Try 3.1-RELEASE, it should be fixed there". > >I've just installed 3.2-RELEASE on a Dual Xeon-450 ASUS board, and am seeing >the same problem. I've tried using an aout version of /sbin/init, as was >suggested by someone on the old thread, but that didn't solve anything. > My guess is that this is a problem that was fixed in 3.1 (which I am running on a dual Pentium Pro box and top is doing fine, e.g. right now 0.0% user/99.2% nice/0.4% system/0.4% interrupt/0.0% idle) and apparently reappeared in 3.2. Marc Schneiders To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 15 5:20:18 1999 Delivered-To: freebsd-smp@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 0A4FA152C1 for ; Tue, 15 Jun 1999 05:20:16 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id IAA21478 for ; Tue, 15 Jun 1999 08:20:15 -0400 (EDT) Received: from thehousleys.net (housley@localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id IAA03226 for ; Tue, 15 Jun 1999 08:20:12 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <376644FB.B8F67072@thehousleys.net> Date: Tue, 15 Jun 1999 08:20:12 -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: smp@FreeBSD.org Subject: MY New SMP system -- comments, suggestions, statements Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Over the weekend I setup my new server. Asus P2B-D w/256Meg ECC RAM and mirrored IDE via ccd. The compiling of the kernel went without problems. It might be nice to have a file re-enforcing the number of APIC's, BUSES, IRQ for the common motherboards. I was also slightly surprized when my vga, both NICs showed up on IRQs 16, 18 & 19 respectively, wasn't expecting that. I have APM disabled in the BIOS and not in the kernel. I needed to add "KLUDGE_RTC_BROKEN" to make top work. The source code is kept current via CTM. It is the code from about June 8 (or about). I have watched to ctm's and haven't seen chagnes in the code I haven't applied. PS. It is a nice MB, thanks to all for the input a couple of weeks ago when I asked. 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 Tue Jun 15 8:36: 8 1999 Delivered-To: freebsd-smp@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 7DD1814A2F; Tue, 15 Jun 1999 08:36:04 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id KAA00220; Tue, 15 Jun 1999 10:35:50 -0500 (CDT) From: Joe Greco Message-Id: <199906151535.KAA00220@aurora.sol.net> Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? To: james@ehlo.com, freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, aaron-fbsd@mutex.org Date: Tue, 15 Jun 1999 10:35:47 -0500 (CDT) 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 > this is a problem with an rtc interrupt being lost, which apparently wedges > up all further rtc interrupts. i solved it by searching the mailing list > archives and located this post: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=54158+0+archive/1999/freebsd-smp/19 > 990607.freebsd-smp > > (in case the URL doesn't work for some reason it's by bob wilcox from may > 20, the patch is supposedly from tor egge(?) and it patches clkintr). > > once i applied the patch i never saw any weirdness. > > apparently this is a temporary workaround? can somebody explain more fully? > what cost am i paying for a patch named "BROKEN_RTC_KLUDGE"? > > Aaron Smith I would advise that you first try adding the line device apm0 at isa? flags 0x20 # Advanced Power Management to your kernel config. I was one of the people with a flock of P2B-DS's that exhibited this behaviour, and on the machines I've done this on, it has magically fixed itself. (I'd attribute this to somebody but I forget who recommended it) ... 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 Tue Jun 15 9: 9:13 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (Postfix) with ESMTP id 07DF715083; Tue, 15 Jun 1999 09:09:06 -0700 (PDT) (envelope-from james@ehlo.com) Received: from vrfy.ehlo.com (HSE-TOR-ppp21683.sympatico.ca [209.226.66.241]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id MAA04000; Tue, 15 Jun 1999 12:06:55 -0400 (EDT) Received: from james by vrfy.ehlo.com with local (Exim 2.12 #3) id 10tvfx-0008Ve-00; Tue, 15 Jun 1999 12:03:01 -0400 Date: Tue, 15 Jun 1999 12:03:01 -0400 From: James FitzGibbon To: Joe Greco Cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org, aaron-fbsd@mutex.org Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? Message-ID: <19990615120256.H32341@ehlo.com> References: <199906151535.KAA00220@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906151535.KAA00220@aurora.sol.net>; from Joe Greco on Tue, Jun 15, 1999 at 10:35:47AM -0500 Organization: EHLO Solutions Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Joe Greco (jgreco@ns.sol.net) [990615 11:33]: > I would advise that you first try adding the line > > device apm0 at isa? flags 0x20 # Advanced Power Management > > to your kernel config. I was one of the people with a flock of P2B-DS's > that exhibited this behaviour, and on the machines I've done this on, it > has magically fixed itself. Much thanks - that seems to have fixed the problem. The machine was performing extremely sluggishly before I put the apm0 device in, but now it is reporting CPU states accurately and is responsive to boot. -- j. James FitzGibbon (JF647) james@ehlo.com EHLO Solutions Voice/Fax +1 416 410-0100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 15 10: 7:59 1999 Delivered-To: freebsd-smp@freebsd.org Received: from is.lamefree.com (is.lamefree.com [209.144.220.37]) by hub.freebsd.org (Postfix) with ESMTP id ED7E9151F9; Tue, 15 Jun 1999 10:07:55 -0700 (PDT) (envelope-from stalker@is.lamefree.com) Received: from localhost (stalker@localhost) by is.lamefree.com (8.9.3/8.9.1) with ESMTP id KAA08879; Tue, 15 Jun 1999 10:06:36 -0700 (PDT) Date: Tue, 15 Jun 1999 10:06:36 -0700 (PDT) From: Stalker To: James FitzGibbon Cc: Joe Greco , freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, aaron-fbsd@mutex.org Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? In-Reply-To: <19990615120256.H32341@ehlo.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 Is it necessary to have APM enabled in the bios for this device to fix the problem? thanks, jeff stalker@feerbsd.org On Tue, 15 Jun 1999, James FitzGibbon wrote: > * Joe Greco (jgreco@ns.sol.net) [990615 11:33]: > > > I would advise that you first try adding the line > > > > device apm0 at isa? flags 0x20 # Advanced Power Management > > > > to your kernel config. I was one of the people with a flock of P2B-DS's > > that exhibited this behaviour, and on the machines I've done this on, it > > has magically fixed itself. > > Much thanks - that seems to have fixed the problem. The machine was > performing extremely sluggishly before I put the apm0 device in, but now it > is reporting CPU states accurately and is responsive to boot. > > -- > j. > > James FitzGibbon (JF647) james@ehlo.com > EHLO Solutions Voice/Fax +1 416 410-0100 > > > 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 Jun 15 12: 3:51 1999 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 71DD614D2D for ; Tue, 15 Jun 1999 12:03:36 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id VAA96921; Tue, 15 Jun 1999 21:02:10 +0200 (CEST) Message-Id: <199906151902.VAA96921@midten.fast.no> To: jgreco@ns.sol.net Cc: james@ehlo.com, freebsd-smp@FreeBSD.ORG, aaron-fbsd@mutex.org Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? From: Tor.Egge@fast.no In-Reply-To: Your message of "Tue, 15 Jun 1999 10:35:47 -0500 (CDT)" References: <199906151535.KAA00220@aurora.sol.net> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Tue_Jun_15_20:53:50_1999)--" Content-Transfer-Encoding: 7bit Date: Tue, 15 Jun 1999 21:02:10 +0200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----Next_Part(Tue_Jun_15_20:53:50_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > I would advise that you first try adding the line > > device apm0 at isa? flags 0x20 # Advanced Power Management That disables the RTC interrupt and causes hardclock() to call statclock(). Some bioses seems to trap direct accesses to the RTC chip in order to pass Y2K tests (Some Y2K test programs access the RTC chip directly). When the CPU accesses IO port 0x70, the power management chip generates an SMI, and the physical RTC chip is accessed from inside SMM. This method sometimes fails when using an SMP kernel. A workaround is to disable the trap SMI for access to IO port 0x70. When using an SMP kernel on Asus P2B-DS mainboard with BIOS revision 1007 or newer, you either have to disable use of RTC interrupts or disable the trap SMIs. - Tor Egge ----Next_Part(Tue_Jun_15_20:53:50_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/pci/pcisupport.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v retrieving revision 1.86.2.8 diff -u -r1.86.2.8 pcisupport.c --- pcisupport.c 1999/05/26 16:39:42 1.86.2.8 +++ pcisupport.c 1999/06/06 20:31:02 @@ -213,7 +213,87 @@ tag->secondarybus = tag->subordinatebus = secondarybus + 1; } +#ifdef SMP static void +fix_82371ab_power_management(pcici_t tag) +{ + int pmba; + int devctl; + int devctl_changed; + int devrese; + int devresg; + +#define PMBA_CONFIG_OFFSET 0x40 +#define PMBA_TO_IO(addr) (addr & 0xffc0) +#define DEVRESE_OFFSET 0x68 +#define DEVRESG_OFFSET 0x70 +#define DEVRES_MONITOR_ENABLE (1 << 20) +#define DEVCTL_IO_OFFSET 0x2c +#define DEVCTL_TRAP_DEV12 (1 << 24) +#define DEVCTL_TRAP_DEV13 (1 << 25) +#define RTC_IOADDR 0x70 + + pmba = pci_cfgread(tag, PMBA_CONFIG_OFFSET, 4); + + devctl = inl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET); + devctl_changed = 0; + + devrese = pci_cfgread(tag, DEVRESE_OFFSET, 2) | + (pci_cfgread(tag, DEVRESE_OFFSET + 2, 1) << 16); + + if ((devrese & DEVRES_MONITOR_ENABLE) != 0 && + ((devrese >> 16) & 15) <= 7 && + (devrese & 0xffff) == RTC_IOADDR && + (devctl & DEVCTL_TRAP_DEV12) != 0) { + + devrese &= ~DEVRES_MONITOR_ENABLE; + devctl &= ~DEVCTL_TRAP_DEV12; + devctl_changed = 1; + + pci_cfgwrite(tag, DEVRESE_OFFSET, 2, (devrese & 0xffff)); + pci_cfgwrite(tag, DEVRESE_OFFSET + 2, 1, + (devrese >> 16) & 0xff); + + printf("Disabled Device 12 trap SMI for access to RTC chip\n"); + } + + devresg = pci_cfgread(tag, DEVRESG_OFFSET, 2) | + (pci_cfgread(tag, DEVRESG_OFFSET + 2, 1) << 16); + + if ((devresg & DEVRES_MONITOR_ENABLE) != 0 && + ((devresg >> 16) & 15) <= 7 && + (devresg & 0xffff) == RTC_IOADDR && + (devctl & DEVCTL_TRAP_DEV13) != 0) { + + devresg &= ~DEVRES_MONITOR_ENABLE; + devctl &= ~DEVCTL_TRAP_DEV13; + devctl_changed = 1; + + pci_cfgwrite(tag, DEVRESG_OFFSET, 2, (devresg & 0xffff)); + pci_cfgwrite(tag, DEVRESG_OFFSET + 2, 1, + (devresg >> 16) & 0xff); + + printf("Disabled Device 13 trap SMI for access to RTC chip\n"); + } + + if (devctl_changed != 0) { + outl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET, devctl); + } + +#undef PMBA_CONFIG_OFFSET +#undef PMBA_TO_IO +#undef DEVRESE_OFFSET +#undef DEVRESG_OFFSET +#undef DEVRES_MONITOR_ENABLE +#undef DEVCTL_IO_OFFSET +#undef DEVCTL_TRAP_DEV12 +#undef DEVCTL_TRAP_DEV13 +#undef RTC_IOADDR +} +#endif + + +static void fixwsc_natoma(pcici_t tag) { int pmccfg; @@ -284,6 +364,9 @@ case 0x71108086: return ("Intel 82371AB PCI to ISA bridge"); case 0x71138086: +#if defined(SMP) + fix_82371ab_power_management(tag); +#endif return ("Intel 82371AB Power management controller"); case 0x71808086: return ("Intel 82443LX host to PCI bridge"); ----Next_Part(Tue_Jun_15_20:53:50_1999)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 15 12:25:30 1999 Delivered-To: freebsd-smp@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A056A14FF5 for ; Tue, 15 Jun 1999 12:25:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA07238; Tue, 15 Jun 1999 21:22:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Tor.Egge@fast.no Cc: jgreco@ns.sol.net, james@ehlo.com, freebsd-smp@FreeBSD.ORG, aaron-fbsd@mutex.org Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? In-reply-to: Your message of "Tue, 15 Jun 1999 21:02:10 +0200." <199906151902.VAA96921@midten.fast.no> Date: Tue, 15 Jun 1999 21:22:26 +0200 Message-ID: <7236.929474546@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think that this kind of surgery should be avoided. It is far too much hazzle to be worth the effort. If the bios traps RTC access, we shouldn't use it for statistics anyway, since it will no longer have decent properties for statistical sampling. Poul-Henning In message <199906151902.VAA96921@midten.fast.no>, Tor.Egge@fast.no writes: >----Next_Part(Tue_Jun_15_20:53:50_1999)-- >Content-Type: Text/Plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >> >> I would advise that you first try adding the line >> >> device apm0 at isa? flags 0x20 # Advanced Power Management > >That disables the RTC interrupt and causes hardclock() to call statclock(). > >Some bioses seems to trap direct accesses to the RTC chip in order to >pass Y2K tests (Some Y2K test programs access the RTC chip directly). > >When the CPU accesses IO port 0x70, the power management chip >generates an SMI, and the physical RTC chip is accessed from inside >SMM. > >This method sometimes fails when using an SMP kernel. A workaround is >to disable the trap SMI for access to IO port 0x70. > >When using an SMP kernel on Asus P2B-DS mainboard with BIOS revision >1007 or newer, you either have to disable use of RTC interrupts or >disable the trap SMIs. > >- Tor Egge > > >----Next_Part(Tue_Jun_15_20:53:50_1999)-- >Content-Type: Text/Plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Index: sys/pci/pcisupport.c >=================================================================== >RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v >retrieving revision 1.86.2.8 >diff -u -r1.86.2.8 pcisupport.c >--- pcisupport.c 1999/05/26 16:39:42 1.86.2.8 >+++ pcisupport.c 1999/06/06 20:31:02 >@@ -213,7 +213,87 @@ > tag->secondarybus = tag->subordinatebus = secondarybus + 1; > } > >+#ifdef SMP > static void >+fix_82371ab_power_management(pcici_t tag) >+{ >+ int pmba; >+ int devctl; >+ int devctl_changed; >+ int devrese; >+ int devresg; >+ >+#define PMBA_CONFIG_OFFSET 0x40 >+#define PMBA_TO_IO(addr) (addr & 0xffc0) >+#define DEVRESE_OFFSET 0x68 >+#define DEVRESG_OFFSET 0x70 >+#define DEVRES_MONITOR_ENABLE (1 << 20) >+#define DEVCTL_IO_OFFSET 0x2c >+#define DEVCTL_TRAP_DEV12 (1 << 24) >+#define DEVCTL_TRAP_DEV13 (1 << 25) >+#define RTC_IOADDR 0x70 >+ >+ pmba = pci_cfgread(tag, PMBA_CONFIG_OFFSET, 4); >+ >+ devctl = inl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET); >+ devctl_changed = 0; >+ >+ devrese = pci_cfgread(tag, DEVRESE_OFFSET, 2) | >+ (pci_cfgread(tag, DEVRESE_OFFSET + 2, 1) << 16); >+ >+ if ((devrese & DEVRES_MONITOR_ENABLE) != 0 && >+ ((devrese >> 16) & 15) <= 7 && >+ (devrese & 0xffff) == RTC_IOADDR && >+ (devctl & DEVCTL_TRAP_DEV12) != 0) { >+ >+ devrese &= ~DEVRES_MONITOR_ENABLE; >+ devctl &= ~DEVCTL_TRAP_DEV12; >+ devctl_changed = 1; >+ >+ pci_cfgwrite(tag, DEVRESE_OFFSET, 2, (devrese & 0xffff)); >+ pci_cfgwrite(tag, DEVRESE_OFFSET + 2, 1, >+ (devrese >> 16) & 0xff); >+ >+ printf("Disabled Device 12 trap SMI for access to RTC chip\n"); >+ } >+ >+ devresg = pci_cfgread(tag, DEVRESG_OFFSET, 2) | >+ (pci_cfgread(tag, DEVRESG_OFFSET + 2, 1) << 16); >+ >+ if ((devresg & DEVRES_MONITOR_ENABLE) != 0 && >+ ((devresg >> 16) & 15) <= 7 && >+ (devresg & 0xffff) == RTC_IOADDR && >+ (devctl & DEVCTL_TRAP_DEV13) != 0) { >+ >+ devresg &= ~DEVRES_MONITOR_ENABLE; >+ devctl &= ~DEVCTL_TRAP_DEV13; >+ devctl_changed = 1; >+ >+ pci_cfgwrite(tag, DEVRESG_OFFSET, 2, (devresg & 0xffff)); >+ pci_cfgwrite(tag, DEVRESG_OFFSET + 2, 1, >+ (devresg >> 16) & 0xff); >+ >+ printf("Disabled Device 13 trap SMI for access to RTC chip\n"); >+ } >+ >+ if (devctl_changed != 0) { >+ outl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET, devctl); >+ } >+ >+#undef PMBA_CONFIG_OFFSET >+#undef PMBA_TO_IO >+#undef DEVRESE_OFFSET >+#undef DEVRESG_OFFSET >+#undef DEVRES_MONITOR_ENABLE >+#undef DEVCTL_IO_OFFSET >+#undef DEVCTL_TRAP_DEV12 >+#undef DEVCTL_TRAP_DEV13 >+#undef RTC_IOADDR >+} >+#endif >+ >+ >+static void > fixwsc_natoma(pcici_t tag) > { > int pmccfg; >@@ -284,6 +364,9 @@ > case 0x71108086: > return ("Intel 82371AB PCI to ISA bridge"); > case 0x71138086: >+#if defined(SMP) >+ fix_82371ab_power_management(tag); >+#endif > return ("Intel 82371AB Power management controller"); > case 0x71808086: > return ("Intel 82443LX host to PCI bridge"); > >----Next_Part(Tue_Jun_15_20:53:50_1999)---- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 15 14: 5: 1 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.30.145]) by hub.freebsd.org (Postfix) with ESMTP id 9D034155D3 for ; Tue, 15 Jun 1999 14:04:56 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id XAA19542 for ; Tue, 15 Jun 1999 23:04:55 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA14440 for ; Tue, 15 Jun 1999 23:04:54 +0200 Date: Tue, 15 Jun 1999 23:04:54 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: freebsd-smp@FreeBSD.ORG Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? In-Reply-To: <199906151902.VAA96921@midten.fast.no> Message-ID: <9906152259030.14354-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <9906152259032.14354@liquid.tpb.net> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tor.Egge@fast.no wrote: > Some bioses seems to trap direct accesses to the RTC chip in order to > pass Y2K tests (Some Y2K test programs access the RTC chip directly). This looks very familiar to what's on ASUS's web pages re differences between BIOS revisions 1008 and 1009 for the P2B-D and P2B-DS boards. (Drat. Now that I actually go looking for it I can't find any mention of revision 1009 anywhere except on their ftp site.) -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 15 21: 6:34 1999 Delivered-To: freebsd-smp@freebsd.org Received: from storm.twcol.com (storm.twcol.com [204.210.251.99]) by hub.freebsd.org (Postfix) with ESMTP id 03CDA154B5 for ; Tue, 15 Jun 1999 21:06:31 -0700 (PDT) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp219142.columbus.rr.com [208.169.219.142]) by storm.twcol.com (8.9.1/8.9.1) with ESMTP id AAA00348; Wed, 16 Jun 1999 00:11:41 -0400 (EDT) Message-ID: <376722B4.1C711B4A@columbus.rr.com> Date: Wed, 16 Jun 1999 00:06:12 -0400 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: N Cc: freebsd-smp@FreeBSD.ORG Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? References: <9906152259030.14354-100000@liquid.tpb.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From http://www.asus.com.tw/Products/Motherboard/bios_slot1.html P2B-DS (ATX, onboard SCSI, Dual porcessors) - BIOS Upgrade and Road Map : bxds108b.zip P2B-DS BIOS Ver. 1008B. 04/16/99 1.Onboard AHA 7890 BIOS updated to v2.11. bxds1009.zip P2B-DS BIOS Ver. 1009. 05/10/99 1.Microcode update for Intel PentiumŪ III 550 CPU upgraded to revision 005. 2.Fix for serial port failure running Windows 2000. 3.Added keyboard wakeup item with three choices of key combinations for models with W977 I/O chip. 4.Fix for CPU clock detection error when speed > 512MHz. 5.Upgraded L2 cache reference code to Revision 3.4. 6.Added microcode update support for PIII C0 stepping. (550MHz part) -- Danny J. Zerkel "Sursum ad Absurdum" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 16 5:36: 7 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.30.146]) by hub.freebsd.org (Postfix) with ESMTP id 7FB21151F8 for ; Wed, 16 Jun 1999 05:36:03 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id OAA07332 for ; Wed, 16 Jun 1999 14:35:59 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id OAA18082 for ; Wed, 16 Jun 1999 14:35:58 +0200 Date: Wed, 16 Jun 1999 14:35:58 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: freebsd-smp@FreeBSD.ORG Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? In-Reply-To: <376722B4.1C711B4A@columbus.rr.com> Message-ID: <9906161432320.17876-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ ASUS P2B-DS motherboards developing symptoms as in Subject with certain BIOS revisions ] > From http://www.asus.com.tw/Products/Motherboard/bios_slot1.html Sorry, this isn't what I meant either. There was a text about the AMI2000 Y2K compliancy test program that used to complain and a fix was incorporated, but as said I can't find it anymore. www.asus.com (note no .tw) doesn't even list BIOS revision 1009, nor does it mention the P2Z series (but admittedly they are very recent). -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 16 15: 1:45 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id A440F14CB5; Wed, 16 Jun 1999 15:01:37 -0700 (PDT) (envelope-from james@ehlo.com) Received: from vrfy.ehlo.com (HSE-TOR-ppp21683.sympatico.ca [209.226.66.241]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id SAA25376; Wed, 16 Jun 1999 18:00:58 -0400 (EDT) Received: from james by vrfy.ehlo.com with local (Exim 2.12 #3) id 10uNeX-0009gA-00; Wed, 16 Jun 1999 17:55:25 -0400 Date: Wed, 16 Jun 1999 17:55:25 -0400 From: James FitzGibbon To: Stalker Cc: Joe Greco , freebsd-questions@freebsd.org, freebsd-smp@freebsd.org, aaron-fbsd@mutex.org Subject: Re: CPU states at 0.0% on 3.2-R SMP box ? Message-ID: <19990616175525.A36384@ehlo.com> References: <19990615120256.H32341@ehlo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Stalker on Tue, Jun 15, 1999 at 10:06:36AM -0700 Organization: EHLO Solutions Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Stalker (stalker@is.lamefree.com) [990615 13:03]: > Is it necessary to have APM enabled in the bios for this device to fix the > problem? I have an ASUS board and have the "Power Management" option disabled, but it still works fine. -- j. James FitzGibbon (JF647) james@ehlo.com EHLO Solutions Voice/Fax +1 416 410-0100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 17 3:51:43 1999 Delivered-To: freebsd-smp@freebsd.org Received: from root.azovstal.com.ua (azovstal.com.ua [195.206.225.58]) by hub.freebsd.org (Postfix) with ESMTP id 1827614C1A for ; Thu, 17 Jun 1999 03:51:28 -0700 (PDT) (envelope-from brozgol@azovstal.com.ua) Received: from brozgol (brozgol.asctp.azov.stal [10.2.1.54]) by root.azovstal.com.ua (8.9.2/8.9.2) with SMTP id NAA84374 for ; Thu, 17 Jun 1999 13:51:18 +0300 (EEST) (envelope-from brozgol@azovstal.com.ua) Message-ID: <000801beb8af$88e0bd10$3601020a@brozgol.asctp.azov.stal> From: "Andrew Brozgol" To: Subject: SMP panics: can't support type 2 default yet Date: Thu, 17 Jun 1999 13:52:45 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear SMP Gurus: Can you help me? I have HP NetServer LM with 2xP66 and AIC-7770. mptable reports: ======================================= MPTable, version 2.0.15 ------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fed20 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0xa1 mode: Virtual Wire -------------------------------------------------- MP default config type: 2 bus: EISA, APIC: 82489DX ---------------------------------------------------- # 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=1 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =========================================== When I tried to run 3.1 SMP kernel with the above options it reported: panic: sorry, can't support type 2 default yet Is really SMP default configuration not supported with 3.1? Thanks, Andrew Brozgol To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 18 11:44:28 1999 Delivered-To: freebsd-smp@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id E647514F30 for ; Fri, 18 Jun 1999 11:44:22 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA45043 for ; Fri, 18 Jun 1999 11:44:22 -0700 (PDT) Date: Fri, 18 Jun 1999 11:44:21 -0700 (PDT) From: Julian Elischer To: smp@freebsd.org Subject: Call to arms..-SMP 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 Ok we've been working on improving some facets of FreeBSD's file IO however we are trailing Linux in this area, because they have recently managed to mode a number of important kernel modules out from under the Giant Lock (TM). Most noticable in this case are: 1/ File reads and writes for file data that is in memory (in the cache). Effectively they have the copyout() or uiomove (or whatever they use) drop the GKL so that more than one processor can do data moving at a time. 2/ In the Networking layer, they have changed things to allow more than one processor to do packet processing. BSDI have also done some of this. their approach has been very interesting: e.g. re: interrupts, They define a thread for each interrupt source (e.g. irq6,irg7, etc.) When the interrupt occurs they save regs and transfer to the stack associated with that thread. However all extra thread context switching is delayed (in the hope that it wont have to be done). If a lock is encountered, the rest of the context switch is done, and the thread sleeps. (and control is passed back to the holder of the lock (if they are runnable) or the original process. Lazy evaluation of the interrupt thread context switch.. very cunning.. Maybe something BDE could look at.. he's definitly the most qualified for that stuff. spls go away entirely after locks are ubiquitous. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 18 14:47:45 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dyson.iquest.net. (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (Postfix) with ESMTP id 2458414D66 for ; Fri, 18 Jun 1999 14:47:42 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from toor@localhost) by dyson.iquest.net. (8.9.3/8.9.3) id QAA00721; Fri, 18 Jun 1999 16:47:39 -0500 (EST) (envelope-from toor) Message-Id: <199906182147.QAA00721@dyson.iquest.net.> Subject: Re: Call to arms..-SMP In-Reply-To: from Julian Elischer at "Jun 18, 1999 11:44:21 am" To: julian@whistle.com (Julian Elischer) Date: Fri, 18 Jun 1999 16:47:39 -0500 (EST) Cc: smp@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (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 Julian Elischer said: > > They define a thread for each interrupt source (e.g. irq6,irg7, etc.) > > When the interrupt occurs they save regs and transfer to the stack > associated with that thread. However all extra thread context > switching is delayed (in the hope that it wont have to be done). > If a lock is encountered, the rest of the context switch is done, and the > thread sleeps. (and control is passed back to the holder of the lock (if > they are runnable) or the original process. > > Lazy evaluation of the interrupt thread context switch.. very cunning.. > Maybe something BDE could look at.. he's definitly the most qualified for > that stuff. > > spls go away entirely after locks are ubiquitous. > Wow, that is *exactly* the approach in the typical realtime kernel. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 1:47:19 1999 Delivered-To: freebsd-smp@freebsd.org Received: from wwdg.com (mail.wwdg.com [209.181.65.217]) by hub.freebsd.org (Postfix) with ESMTP id 89FE314CB3; Sat, 19 Jun 1999 01:47:16 -0700 (PDT) (envelope-from dvwd@wwdg.com) Received: (from web@localhost) by wwdg.com (8.8.5/8.8.0) id CAA06195; Sat, 19 Jun 1999 02:52:23 -0600 Date: Sat, 19 Jun 1999 02:52:23 -0600 Message-Id: <199906190852.CAA06195@wwdg.com> From: dvwd@wwdg.com To: freebsd-questions@freebsd.org Full-Name: Dave Wood Cc: freebsd-smp@freebsd.org Subject: Multi processor support? Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the (very) few items i can find on the freebsd web pages it looks like 3.2 supports MP. Does it do it automagicly? How can I tell if it's working and using both cpu's in my system? Also, is there any way to control what processes happen on which cpu? Are there any man/how to pages for setting up SMP? Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 2:24:54 1999 Delivered-To: freebsd-smp@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 8904414CF0 for ; Sat, 19 Jun 1999 02:24:40 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id JAA23962; Sat, 19 Jun 1999 09:24:35 GMT Message-ID: <376B6143.7B4628E3@tdx.co.uk> Date: Sat, 19 Jun 1999 10:22:11 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: dvwd@wwdg.com Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Multi processor support? References: <199906190852.CAA06195@wwdg.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org dvwd@wwdg.com wrote: > > >From the (very) few items i can find on the freebsd web pages it looks like 3.2 supports MP. Does it do it automagicly? How > can I tell if it's working and using both cpu's in my system? The 3.2 kernel does support SMP - but you'll need to compile your own kernel (this option is disabled by default in the GENERIC kernel). > Also, is there any way to control what processes happen on > which cpu? AFAIK there is no way to control the affinity of processes under FreeBSD at present... > Are there any man/how to pages for setting up SMP? So long as your board is good/supported - it's pretty simple... Look at the GENERIC kernel under 3.2 - and uncomment a couple of lines :) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 2:43:30 1999 Delivered-To: freebsd-smp@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 508F514D3D; Sat, 19 Jun 1999 02:43:26 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=adv) by post.mail.nl.demon.net with smtp (Exim 2.02 #1) id 10vHen-0006ik-00; Sat, 19 Jun 1999 09:43:25 +0000 Message-ID: <005401beba38$5ccfa6c0$0b00000a@adv.oldserver.demon.nl> From: "Marc Schneiders" To: , Cc: Subject: Re: Multi processor support? Date: Sat, 19 Jun 1999 11:44:44 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org dvwd@wwdg.com wrote: >From the (very) few items i can find on the freebsd web pages it looks like 3.2 supports MP. Does it do it >automagicly? No, you have to compile a kernel with SMP enabled. This is easy though. Info on the first page mentioned below. >How can I tell if it's working and using both cpu's in my system? > Dmesg will thell you when the second CPU is up in the air. Top shows you which CPU is doing what. (In 3.1 in any case, which I am still using.) >Also, is there any way to control what processes happen on >which cpu? I don't think so. See, however the first page given below, where all the information is. > >Are there any man/how to pages for setting up SMP? > http://www.freebsd.org/~fsmp/SMP/SMP.html has all the important info, including how to do it. http://www.sit.wisc.edu/~sakai/html/mycomputer.html page of a happy user with a benchmark comparison between one and two CPU kernels. Good luck! Marc Schneiders To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 11:59:13 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.ivm.net (mail.ivm.de [195.78.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 340E214E04 for ; Sat, 19 Jun 1999 11:58:19 -0700 (PDT) (envelope-from ap@bnc.net) Received: from gemini.bnc.net (gemini.bnc.net [195.247.233.33]) by mail.ivm.net (8.8.8/8.8.8) with ESMTP id UAA30771 for ; Sat, 19 Jun 1999 20:58:10 +0200 X-To: Received: (from ap@localhost) by gemini.bnc.net (8.9.3/8.9.1) id UAA00556 for freebsd-smp@freebsd.org; Sat, 19 Jun 1999 20:57:43 +0200 (CEST) (envelope-from ap) Date: Sat, 19 Jun 1999 20:57:43 +0200 From: Achim Patzner To: freebsd-smp@freebsd.org Subject: P2B-DS and its statclock/APM/whatever Message-ID: <19990619205743.A511@bnc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, you got me. As I had a scheduled downtime today, I upgraded the BIOS of my beloved gemini.bnc.net from 1006 to 1009. Guess what: No matter how I'm configuring APM BIOS settings or the apm0 device, my top is looking like this now: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 338 root 10 0 4628K 1448K nanslp 0 0:01 0.00% 0.00% wcol 507 ap 2 0 1284K 992K select 0 0:01 0.00% 0.00% screen-3.7. 535 ap 2 0 1136K 936K select 0 0:00 0.00% 0.00% top 511 ap 10 0 1552K 1316K wait 0 0:00 0.00% 0.00% mutt Grmbl. systat -vmstat isn#t working either. I guess I'm going to downgrade tomorrow. Achim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 12:43:58 1999 Delivered-To: freebsd-smp@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 0058115231 for ; Sat, 19 Jun 1999 12:43:53 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id MAA01949; Sat, 19 Jun 1999 12:41:13 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (4292 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sat, 19 Jun 1999 12:40:28 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id MAA94507; Sat, 19 Jun 1999 12:40:28 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906191940.MAA94507@sigma.veritas.com> From: Aaron Smith To: Achim Patzner Cc: freebsd-smp@FreeBSD.ORG Subject: Re: P2B-DS and its statclock/APM/whatever In-reply-to: Your message of "Sat, 19 Jun 1999 20:57:43 +0200." <19990619205743.A511@bnc.net> Date: Sat, 19 Jun 1999 12:40:27 -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 19 Jun 1999 20:57:43 +0200, Achim Patzner writes: >Ok, you got me. As I had a scheduled downtime today, I upgraded the BIOS of >my beloved gemini.bnc.net from 1006 to 1009. Guess what: No matter how I'm >configuring APM BIOS settings or the apm0 device, my top is looking like >this now: > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND > 338 root 10 0 4628K 1448K nanslp 0 0:01 0.00% 0.00% wcol don't downgrade, just try this patch from Tor Egge. it worked great for my P2B-DS (bios rev 1008). Aaron ----Next_Part(Tue_Jun_15_20:53:50_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/pci/pcisupport.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v retrieving revision 1.86.2.8 diff -u -r1.86.2.8 pcisupport.c --- pcisupport.c 1999/05/26 16:39:42 1.86.2.8 +++ pcisupport.c 1999/06/06 20:31:02 @@ -213,7 +213,87 @@ tag->secondarybus = tag->subordinatebus = secondarybus + 1; } +#ifdef SMP static void +fix_82371ab_power_management(pcici_t tag) +{ + int pmba; + int devctl; + int devctl_changed; + int devrese; + int devresg; + +#define PMBA_CONFIG_OFFSET 0x40 +#define PMBA_TO_IO(addr) (addr & 0xffc0) +#define DEVRESE_OFFSET 0x68 +#define DEVRESG_OFFSET 0x70 +#define DEVRES_MONITOR_ENABLE (1 << 20) +#define DEVCTL_IO_OFFSET 0x2c +#define DEVCTL_TRAP_DEV12 (1 << 24) +#define DEVCTL_TRAP_DEV13 (1 << 25) +#define RTC_IOADDR 0x70 + + pmba = pci_cfgread(tag, PMBA_CONFIG_OFFSET, 4); + + devctl = inl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET); + devctl_changed = 0; + + devrese = pci_cfgread(tag, DEVRESE_OFFSET, 2) | + (pci_cfgread(tag, DEVRESE_OFFSET + 2, 1) << 16); + + if ((devrese & DEVRES_MONITOR_ENABLE) != 0 && + ((devrese >> 16) & 15) <= 7 && + (devrese & 0xffff) == RTC_IOADDR && + (devctl & DEVCTL_TRAP_DEV12) != 0) { + + devrese &= ~DEVRES_MONITOR_ENABLE; + devctl &= ~DEVCTL_TRAP_DEV12; + devctl_changed = 1; + + pci_cfgwrite(tag, DEVRESE_OFFSET, 2, (devrese & 0xffff)); + pci_cfgwrite(tag, DEVRESE_OFFSET + 2, 1, + (devrese >> 16) & 0xff); + + printf("Disabled Device 12 trap SMI for access to RTC chip\n"); + } + + devresg = pci_cfgread(tag, DEVRESG_OFFSET, 2) | + (pci_cfgread(tag, DEVRESG_OFFSET + 2, 1) << 16); + + if ((devresg & DEVRES_MONITOR_ENABLE) != 0 && + ((devresg >> 16) & 15) <= 7 && + (devresg & 0xffff) == RTC_IOADDR && + (devctl & DEVCTL_TRAP_DEV13) != 0) { + + devresg &= ~DEVRES_MONITOR_ENABLE; + devctl &= ~DEVCTL_TRAP_DEV13; + devctl_changed = 1; + + pci_cfgwrite(tag, DEVRESG_OFFSET, 2, (devresg & 0xffff)); + pci_cfgwrite(tag, DEVRESG_OFFSET + 2, 1, + (devresg >> 16) & 0xff); + + printf("Disabled Device 13 trap SMI for access to RTC chip\n"); + } + + if (devctl_changed != 0) { + outl(PMBA_TO_IO(pmba) + DEVCTL_IO_OFFSET, devctl); + } + +#undef PMBA_CONFIG_OFFSET +#undef PMBA_TO_IO +#undef DEVRESE_OFFSET +#undef DEVRESG_OFFSET +#undef DEVRES_MONITOR_ENABLE +#undef DEVCTL_IO_OFFSET +#undef DEVCTL_TRAP_DEV12 +#undef DEVCTL_TRAP_DEV13 +#undef RTC_IOADDR +} +#endif + + +static void fixwsc_natoma(pcici_t tag) { int pmccfg; @@ -284,6 +364,9 @@ case 0x71108086: return ("Intel 82371AB PCI to ISA bridge"); case 0x71138086: +#if defined(SMP) + fix_82371ab_power_management(tag); +#endif return ("Intel 82371AB Power management controller"); case 0x71808086: return ("Intel 82443LX host to PCI bridge"); ----Next_Part(Tue_Jun_15_20:53:50_1999)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 13: 5:57 1999 Delivered-To: freebsd-smp@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 1721B14BFE for ; Sat, 19 Jun 1999 13:05:50 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (uucp@localhost) by posgate.acis.com.au (8.9.2/8.9.2/Debian/GNU) with UUCP id FAA26940; Sun, 20 Jun 1999 05:56:45 +1000 (EST) Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245]) by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id WAA15493; Sat, 19 Jun 1999 22:00:04 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Sat, 19 Jun 1999 21:52:52 +1000 (EST) From: Andrew MacIntyre To: Andrew Brozgol Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP panics: can't support type 2 default yet In-Reply-To: <000801beb8af$88e0bd10$3601020a@brozgol.asctp.azov.stal> Message-ID: X-X-Sender: andymac@bullseye.apana.org.au MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 17 Jun 1999, Andrew Brozgol wrote: > I have HP NetServer LM with 2xP66 and AIC-7770. > > mptable reports: {...} > MP default config type: 2 > > bus: EISA, APIC: 82489DX {...} > panic: sorry, can't support type 2 default yet I'm not an SMP guru, but you appear not to have received any responses to your query. I have an LM60 uniprocessor box running 2.2.7-R nicely, so the basic hardware should be OK. The problem is most likely that FreeBSD's SMP support has been mostly developed on PCI based systems, rather than EISA-only systems like the Netserver LM series. I'm guessing that the "MP default config type" of 2 indicates an EISA-only SMP system, or possibly more particularly the EISA APIC. In any case, the current SMP support is incapable of supporting both CPUs in your system :-(. Given the fading availability of EISA systems, and the development effort required to move FreeBSD's SMP from the current modest design to a more sophisticated design, I doubt that the core SMP developers will be motivated to add support for this older hardware. You may be able to learn more about the "default config type" by refering to mptable's source, and possibly by searching for MP specification documentation on Intel's web site. If you do, and end up being able to supply patches to add such support to the source tree, I'm sure the patches would be welcome. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 Fido: Andrew MacIntyre, 3:620/243.18 | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 19:31:37 1999 Delivered-To: freebsd-smp@freebsd.org Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (Postfix) with SMTP id 446B615121 for ; Sat, 19 Jun 1999 19:31:33 -0700 (PDT) (envelope-from mike@hyperreal.org) Received: (qmail 6462 invoked by uid 12); 20 Jun 1999 02:31:34 -0000 Message-ID: <19990620023134.6461.qmail@hyperreal.org> From: mike@hyperreal.org Subject: working SMP motherboard for hardware list To: freebsd-smp@freebsd.org Date: Sat, 19 Jun 1999 19:31:34 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL51 (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, Not sure if this is who to send this to, but I have a possible addition to the SMP working motherboard list at http://www.freebsd.org/~fsmp/SMP/hardware.html: Micronics M54Pe revision B http://www.micronics.com/Micronics/support/archives/pentium.htm#prod_210A ...works fine with SMP kernel and default config, FreeBSD 3.2-RELEASE! Enjoy. - Mike ______________________________________________________________________ Mike Brown / Hyperreal | Director, Hyperreal Music Archive PO Box 61334 | http://www.hyperreal.org/music/ Denver CO 80206-8334 USA | Software Engineer, www.netIgnite.com =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: EBDA physical address: 0x0009fc30 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x5a mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x0009fc44 signature: 'PCMP' base table length: 260 version: 1.1 checksum: 0x1e OEM ID: 'INTEL ' Product ID: '430 NX EISA ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 24 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 0x10 BSP, usable 5 2 12 0x03bf 1 0x10 AP, usable 5 2 12 0x03bf -- Bus: Bus ID Type 0 ISA 1 EISA 2 PCI -- 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 active-hi edge 0 0 2 0 INT conforms conforms 0 1 2 1 INT conforms conforms 0 0 2 2 INT conforms conforms 0 3 2 3 INT conforms conforms 0 4 2 4 INT conforms conforms 0 5 2 5 INT conforms conforms 0 6 2 6 INT conforms conforms 0 7 2 7 INT conforms conforms 0 8 2 8 INT conforms conforms 0 9 2 9 INT conforms conforms 0 10 2 10 INT conforms conforms 0 11 2 11 INT conforms conforms 0 12 2 12 INT conforms conforms 0 13 2 13 INT conforms conforms 0 14 2 14 INT conforms conforms 0 15 2 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 0 0 255 0 NMI active-hi edge 0 0 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 =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 20:46:45 1999 Delivered-To: freebsd-smp@freebsd.org Received: from host.windsor.igs.net (host.windsor.igs.net [206.248.3.2]) by hub.freebsd.org (Postfix) with ESMTP id E894D14F22 for ; Sat, 19 Jun 1999 20:46:34 -0700 (PDT) (envelope-from kazuk@windsor.igs.net) Received: from puter02 (cisco413.windsor.igs.net [207.210.5.62]) by host.windsor.igs.net (8.8.5/8.7.3) with SMTP id XAA27303 for ; Sat, 19 Jun 1999 23:46:49 -0400 (EDT) Message-ID: <000801bebad0$219f3b40$0146fea9@puter02> From: "Kazuk Family" To: Subject: smp- stable Date: Sat, 19 Jun 1999 23:51:07 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BEBAAE.999AFDE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BEBAAE.999AFDE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is there support for SMP in the 3.2 stable release of freebsd?? Thanks, David Kuzak ------=_NextPart_000_0005_01BEBAAE.999AFDE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Is there support for SMP in the 3.2 = stable release=20 of freebsd??
 
Thanks,
David Kuzak
------=_NextPart_000_0005_01BEBAAE.999AFDE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 19 21:31:11 1999 Delivered-To: freebsd-smp@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E2F14C84 for ; Sat, 19 Jun 1999 21:31:04 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id WAA09099; Sat, 19 Jun 1999 22:30:48 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906200430.WAA09099@panzer.plutotech.com> Subject: Re: smp- stable In-Reply-To: <000801bebad0$219f3b40$0146fea9@puter02> from Kazuk Family at "Jun 19, 1999 11:51:07 pm" To: kazuk@windsor.igs.net (Kazuk Family) Date: Sat, 19 Jun 1999 22:30:48 -0600 (MDT) Cc: freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Kazuk Family wrote... > Is there support for SMP in the 3.2 stable release of freebsd?? Yes. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message