From owner-freebsd-smp Mon May 11 08:42:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26120 for freebsd-smp-outgoing; Mon, 11 May 1998 08:42:00 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from aurora.sol.net (jgreco@aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26099; Mon, 11 May 1998 08:41:57 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id KAA27052; Mon, 11 May 1998 10:41:58 -0500 (CDT) From: Joe Greco Message-Id: <199805111541.KAA27052@aurora.sol.net> Subject: Time issues in 3.0-C on P55T2P4D To: current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Date: Mon, 11 May 1998 10:41:58 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I've got a 3.0-980331-SNAP box (SMP, dual P200, ASUS P/E P55T2P4D) that I noticed some clock problems with. After talking to PHK, he showed me that there was an interrupt problem (as reported by systat -vm): 15 cow Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt 9 zfod 272 total 1 59 13 74 150 91 1213 271 102 162 36496 wire 50 clk0 irq2 49788 act 64 rtc0 irq8 14.7%Sys 2.2%Intr 5.1%User 0.0%Nice 78.1%Idl 52696 inact 16 pci irq12 | | | | | | | | | | 369740 cache 142 pci irq11 =======+>>> 1292 free pci irq10 daefr sc0 irq1 Note "clk0" and "rtc0". This causes my clocks to never sync up with NTP, presumably because the clock is running really slow. It just sits there and does a step adjust every few minutes. If anyone is interested in more details, please contact me, and I will be happy to provide whatever is needed. ... 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 Mon May 11 09:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01504 for freebsd-smp-outgoing; Mon, 11 May 1998 09:20:20 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01489; Mon, 11 May 1998 09:20:14 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id SAA19515; Mon, 11 May 1998 18:18:32 +0200 (CEST) (envelope-from sos) Message-Id: <199805111618.SAA19515@sos.freebsd.dk> Subject: Re: Time issues in 3.0-C on P55T2P4D In-Reply-To: <199805111541.KAA27052@aurora.sol.net> from Joe Greco at "May 11, 98 10:41:58 am" To: jgreco@solaria.sol.net (Joe Greco) Date: Mon, 11 May 1998 18:18:31 +0200 (CEST) Cc: current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Joe Greco who wrote: This has been so for a long time, but apparently it doesn't affect the system, if you do a vmstat -i you will get the right counts... I havn't investigated further on this, but all intr counts seems to be halfed in systat under SMP... I see no problem with ntp here... > I've got a 3.0-980331-SNAP box (SMP, dual P200, ASUS P/E P55T2P4D) that I > noticed some clock problems with. After talking to PHK, he showed me that > there was an interrupt problem (as reported by systat -vm): > > 15 cow Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt 9 zfod 272 total > 1 59 13 74 150 91 1213 271 102 162 36496 wire 50 clk0 irq2 > 49788 act 64 rtc0 irq8 > 14.7%Sys 2.2%Intr 5.1%User 0.0%Nice 78.1%Idl 52696 inact 16 pci irq12 > | | | | | | | | | | 369740 cache 142 pci irq11 > =======+>>> 1292 free pci irq10 > daefr sc0 irq1 > > Note "clk0" and "rtc0". > > This causes my clocks to never sync up with NTP, presumably because the > clock is running really slow. It just sits there and does a step adjust > every few minutes. > > If anyone is interested in more details, please contact me, and I will be > happy to provide whatever is needed. > > ... 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 > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 11 09:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02243 for freebsd-smp-outgoing; Mon, 11 May 1998 09:26:20 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from aurora.sol.net (jgreco@aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02216; Mon, 11 May 1998 09:26:06 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id LAA27122; Mon, 11 May 1998 11:26:08 -0500 (CDT) From: Joe Greco Message-Id: <199805111626.LAA27122@aurora.sol.net> Subject: Re: Time issues in 3.0-C on P55T2P4D In-Reply-To: <199805111618.SAA19515@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "May 11, 98 06:18:31 pm" To: sos@FreeBSD.ORG Date: Mon, 11 May 1998 11:26:07 -0500 (CDT) Cc: current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG, phk@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In reply to Joe Greco who wrote: > > This has been so for a long time, but apparently it doesn't affect > the system, if you do a vmstat -i you will get the right counts... > > I havn't investigated further on this, but all intr counts seems to > be halfed in systat under SMP... > > I see no problem with ntp here... Okay, I see that... > vmstat -i interrupt total rate clk0 irq2 343036441 99 rtc0 irq8 437761187 127 pci irq12 236113777 68 pci irq11 1220665135 355 pci irq10 702352 0 sc0 irq1 3240 0 Total -2056685164 -599 However, I still get frequent "time resets" under xntpd. May 11 06:59:25 mnemom xntpd[27493]: time reset (step) 0.330688 s May 11 07:40:43 mnemom xntpd[27493]: time reset (step) 0.263977 s May 11 07:45:17 mnemom xntpd[27493]: time reset (step) 0.260552 s May 11 08:45:27 mnemom xntpd[27493]: time reset (step) 0.199847 s Ideas? What should I be checking? I've killed the drift file, the box is connected via 100mbps to a Stratum 2 server, with two off-site S2 servers specified as well. The problem seems to get worse sometimes, and then sometimes not as bad. It's not a real big deal to me, but it'd be nice if it worked. ... 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 Mon May 11 15:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10838 for freebsd-smp-outgoing; Mon, 11 May 1998 15:53:22 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from argo.ripn.net (adbr@argo.ripn.net [195.19.26.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10831 for ; Mon, 11 May 1998 15:53:18 -0700 (PDT) (envelope-from adbr@argo.ripn.net) Received: (from adbr@localhost) by argo.ripn.net (8.8.8/8.8.8) id CAA14832 for freebsd-smp@FreeBSD.ORG; Tue, 12 May 1998 02:57:01 +0400 (MSK/MSD) Message-Id: <199805112257.CAA14832@argo.ripn.net> Subject: help To: freebsd-smp@FreeBSD.ORG Date: Tue, 12 May 1998 02:57:00 +0400 (MSK/MSD) From: Andrei Dobrotsvetov X-Mailer: ELM [version 2.4ME+ PL22 (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 help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 11 20:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18625 for freebsd-smp-outgoing; Mon, 11 May 1998 20:22:47 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from poseidon.hamsterville.ultranet.com (ben@poseidon.hamsterville.ultranet.com [209.6.79.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18613 for ; Mon, 11 May 1998 20:22:39 -0700 (PDT) (envelope-from ben@poseidon.hamsterville.ultranet.com) Received: (from ben@localhost) by poseidon.hamsterville.ultranet.com (8.8.7/8.8.7) id XAA06305 for freebsd-smp@freebsd.org; Mon, 11 May 1998 23:22:13 -0400 (EDT) (envelope-from ben) From: Ben Goodwin Message-Id: <199805120322.XAA06305@poseidon.hamsterville.ultranet.com> Subject: Me = SMP newbie To: freebsd-smp@FreeBSD.ORG Date: Mon, 11 May 1998 23:22:13 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been running FreeBSD 2.2.5-RELEASE for a couple months now, and I have a basic understanding of it all ... I've just swapped motherboards on the machine, giving it a dual-cpu capable pentium-pro motherboard. It has 2 p200's 512k cache sitting in it now. I want to check out SMP in FreeBSD. I'll be new to SMP and to the 3.0 -current/snapshot series. I'm browsing the smp archives, and some online stuff, but the amount of data is so huge I'm afraid to go down this route without some helpful pointers. That's why I'm emailing here :) I'd like to first try an SMP-capable snapshot that's "relatively" stable to get started. That'll involve me figuring out how to get that snapshot (where?), using it (eh, prolly not all that difficult), as well as what I need to do to fiddle with SMP. It looks like there are some nifty commands I can use to detect what my hardware is - I don't really even know - for all I know, what I have won't work. Anyway, pointers would be much appreciated. Thanks! -= Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 11 23:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12118 for freebsd-smp-outgoing; Mon, 11 May 1998 23:30:12 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12103 for ; Mon, 11 May 1998 23:30:07 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA19285; Tue, 12 May 1998 08:29:54 +0200 (CEST) (envelope-from sos) Message-Id: <199805120629.IAA19285@sos.freebsd.dk> Subject: Re: Me = SMP newbie In-Reply-To: <199805120322.XAA06305@poseidon.hamsterville.ultranet.com> from Ben Goodwin at "May 11, 98 11:22:13 pm" To: ben@hamsterville.ultranet.com (Ben Goodwin) Date: Tue, 12 May 1998 08:29:54 +0200 (CEST) Cc: freebsd-smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Ben Goodwin who wrote: > I'd like to first try an SMP-capable snapshot that's "relatively" stable > to get started. That'll involve me figuring out how to get > that snapshot (where?), using it (eh, prolly not all that difficult), > as well as what I need to do to fiddle with SMP. It looks like there > are some nifty commands I can use to detect what my hardware is - I don't > really even know - for all I know, what I have won't work. Anyway, pointers > would be much appreciated. Thanks! Hmm, do you have easy access to the net ?? Then go to current.freebsd.org and pick the latest snap, the latest couble of days has been quiet :) Install it like usual, and you have a UP -current system. When you have that running, build a SMP capable kernel by using the SMP-GENERIC file as master. Compile and install in /kernel, remember to backup the old kernel just in case.. Reboot and you should be running SMP, if your board is supported that is... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 12 21:12:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05002 for freebsd-smp-outgoing; Tue, 12 May 1998 21:12:30 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from poseidon.hamsterville.ultranet.com (poseidon.hamsterville.ultranet.com [209.6.79.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04997 for ; Tue, 12 May 1998 21:12:27 -0700 (PDT) (envelope-from ben@poseidon.hamsterville.ultranet.com) Received: (from ben@localhost) by poseidon.hamsterville.ultranet.com (8.8.8/8.8.8) id AAA07343 for freebsd-smp@freebsd.org; Wed, 13 May 1998 00:12:29 -0400 (EDT) (envelope-from ben) From: Ben Goodwin Message-Id: <199805130412.AAA07343@poseidon.hamsterville.ultranet.com> Subject: Multi-CPU monitor To: freebsd-smp@FreeBSD.ORG Date: Wed, 13 May 1998 00:12:28 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found this in the archives written Dec. 20th 1997. === Jordan K. Hubbard writes: > > I see one listed at 50%, the other at %48. What I'd like is each CPU > > represented individually. Something like: > > CPU0 %user %nice %system ...... etc. > > CPU1 %user %nice %system ...... > > Send us your diffs. That's how things like this happen. :-) It would be better to send any diffs for top to William LeFebvre (wnl@groupsys.com), since he's the maintainer of top. Even the latest version of top (3.5 beta 7) doesn't break it down by CPU for SMP systems (at least not for FreeBSD or Solaris). ==== Did anybuddy ever program a top or something to show both cpu's? I have a program I use on Dec Unix called 'monitor' that shows 'em .. dunno if it's portable, and I'm probably not the right guy to do it :) BTW, I successfully upgraded to 3.0-980426-SNAP (from 225R), compiled an SMP kernel and am up and running on two cpu's successfully! Tyan 1662D motherboard (Pentium Pro 200's, 512k cache each). Most cool. -= Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 12 22:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14542 for freebsd-smp-outgoing; Tue, 12 May 1998 22:33:23 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA14536 for ; Tue, 12 May 1998 22:33:21 -0700 (PDT) (envelope-from barney@databus.databus.com) From: Barney Wolff To: freebsd-smp@FreeBSD.ORG Date: Wed, 13 May 1998 01:30 EDT Subject: Re: Multi-CPU monitor Content-Type: text/plain Message-ID: <355930960.457b@databus.databus.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Top for HP-UX does. Dunno whose code. > It would be better to send any diffs for top to William LeFebvre > (wnl@groupsys.com), since he's the maintainer of top. Even the latest > version of top (3.5 beta 7) doesn't break it down by CPU for SMP > systems (at least not for FreeBSD or Solaris). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 14 10:01:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05442 for freebsd-smp-outgoing; Thu, 14 May 1998 10:01:58 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.portsoft.com (mail.portsoft.com [208.207.3.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05432; Thu, 14 May 1998 10:01:52 -0700 (PDT) (envelope-from tedm@portsoft.com) Received: from DHCP120.portsoft.com (DHCP120.portsoft.com [192.168.1.120]) by mail.portsoft.com (8.8.5/8.8.5) with SMTP id KAA12992; Thu, 14 May 1998 10:00:51 -0700 (PDT) Received: by DHCP120.portsoft.com with Microsoft Mail id <01BD7F1D.35C4A1E0@DHCP120.portsoft.com>; Thu, 14 May 1998 09:46:46 -0700 Message-ID: <01BD7F1D.35C4A1E0@DHCP120.portsoft.com> From: Ted Mittelstaedt To: "tedm@portsoft.com" , "'Garrett Wollman'" Cc: "FreeBSD-gnats-submit@FreeBSD.ORG" , "'FreeBSD SMP mailing list'" , "'FreeBSD FAQ Maintainer'" Subject: RE: kern/6628: Tyan Tomcat III locks SMP-GENERIC kernel on boot Date: Thu, 14 May 1998 09:46:44 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA05434 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh Geeze! I should have played around more with BIOS settings! There is NO setting for "route interrupus via I/O APIC" in the Tyan Tomcat's BIOS. (Is that anything like Coitus Interruptus?) :) However, there IS a BIOS setting for the Tyan board under the "Chipset Features Setup" menu item labeled (innocuously enough): "Chipset Special Features" Enabled/Disabled. Setting this to "Enabled" seems to fix the problem! I hope someone puts this in the hardware FAQ for 3.0! This was on BIOS version 4.01 for the Tomcat IIID - I had to flash the motherboard with current BIOS code. One hiccup on the flashing process - when I flashed it I got to 1F00 and the flash program locked up, but waiting 5 minutes and cold-booting the board seemed fine. I even flashed it twice and it locked up both times in the same location. Pretty hairy when the flash program is sitting there blinking "Do Not Cold Boot While This Program Is Running" messages. The one noticeable difference in the mptable output after flashing the BIOS: version 4.01 of the BIOS changes the version number in the MP Floating Pointer Structure from version 1.1 to 1.4 Ted ---------- From: Garrett Wollman[SMTP:wollman@khavrinen.lcs.mit.edu] Sent: Wednesday, May 13, 1998 2:08 PM To: tedm@portsoft.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/6628: Tyan Tomcat III locks SMP-GENERIC kernel on boot < said: > After compiling the SMP kernel and installing it, a reboot produces a list of > all the devices, then as soon as the second CPU is started the system locks up. I have seen these symptoms on my Intel Buckeyes (BB440FX). I found that there was a setting in the BIOS for ``route interrupus via I/O APIC'' which needed to be set for MP to work. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri May 15 01:20:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05980 for freebsd-smp-outgoing; Fri, 15 May 1998 01:20:21 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05971 for ; Fri, 15 May 1998 01:20:16 -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.8.8/8.8.8) with ESMTP id JAA04638 for ; Fri, 15 May 1998 09:20:18 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <355BFAC4.B61E7CA0@tdx.co.uk> Date: Fri, 15 May 1998 09:20:20 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: smp@FreeBSD.ORG Subject: 8254 APIC broken? with P6DNF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got 3.0-CURRENT running on a dual p-pro SuperMicro P6DNF motherboard, the system works fine, but when it comes up the kernel says: " APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 " I can understand what this means (I think ;-) - And I would guess theres no way of 'fixing' it, apart from the workaround the system's installed, but should I be worried about it? Everything seems to work fine... I'd guess at the end of the day it might be a performance degrading workaround? - But so long as it works ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat May 16 11:09:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14807 for freebsd-smp-outgoing; Sat, 16 May 1998 11:09:45 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14801 for ; Sat, 16 May 1998 11:09:43 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA01998; Sat, 16 May 1998 13:09:35 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805161809.NAA01998@dyson.iquest.net> Subject: Re: 8254 APIC broken? with P6DNF In-Reply-To: <355BFAC4.B61E7CA0@tdx.co.uk> from Karl Pielorz at "May 15, 98 09:20:20 am" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Sat, 16 May 1998 13:09:35 -0500 (EST) Cc: smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've got 3.0-CURRENT running on a dual p-pro SuperMicro P6DNF motherboard, > the system works fine, but when it comes up the kernel says: > > " > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin > 2 > APIC_IO: routing 8254 via 8259 on pin 0 > " > > I can understand what this means (I think ;-) - And I would guess theres no > way of 'fixing' it, apart from the workaround the system's installed, but > should I be worried about it? > > Everything seems to work fine... I'd guess at the end of the day it might be > a performance degrading workaround? - But so long as it works ;-) > I can tell you that I use both a P6DNF and an Intel Providence MB, and am very happy with both (even though the DNF does have a "personality.") John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message