From owner-freebsd-smp Sun May 14 15: 4:14 2000 Delivered-To: freebsd-smp@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 348C737B5AB; Sun, 14 May 2000 15:04:08 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id PAA19383; Sun, 14 May 2000 15:03:47 -0700 Date: Sun, 14 May 2000 15:03:46 -0700 From: Arun Sharma To: FreeBSD Current Cc: smp@freebsd.org Subject: kern/18524 - SMP cpu stats Message-ID: <20000514150346.A19366@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone responsible for SMP please look at this PR: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18524 This is necessary for tools like xosview, ktop etc to display per cpu stats. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 15 5:36:16 2000 Delivered-To: freebsd-smp@freebsd.org Received: from thelab.hub.org (nat194.72.mpoweredpc.net [142.177.194.72]) by hub.freebsd.org (Postfix) with ESMTP id 2AC8737B772 for ; Mon, 15 May 2000 05:36:11 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id JAA08861 for ; Mon, 15 May 2000 09:35:32 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 15 May 2000 09:35:32 -0300 (ADT) From: The Hermit Hacker To: freebsd-smp@freebsd.org Subject: May 8th kernel panics (4.0-STABLE) ... 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 Morning all ... Up until May 8th, I've been running a pretty stable machine at home (Abit BP6 motherboard with dual-Celeron, no overclocking) ... Last night, when I went to bed, I left X disabled and found it at the DDB prompt this morning. Typing panic, it generated the following: ========= panic: from debugger mp_lock = 01000002; epuid = 1; lapic_id = 01000000 Debugger ("panic") stopped at in_delayed_cksum+0x61: movl 0x8(%esi), %eax ========= I've CVSup the newest source and will be installing that tonight, but just thought I'd check if this was previously seen/fixed, or something I should try and come up wiht more information on (and how?) ... Thanks ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 16 10:26:58 2000 Delivered-To: freebsd-smp@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 1E45537B5FD for ; Tue, 16 May 2000 10:26:55 -0700 (PDT) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 4DE235DF0; Tue, 16 May 2000 19:27:20 +0200 (CEST) Date: Tue, 16 May 2000 19:27:20 +0200 From: Dave Boers To: Steve Passe Cc: djb@ifa.au.dk, Bruce Evans , smp@FreeBSD.ORG Subject: Re: hlt instructions and temperature issues Message-ID: <20000516192720.A33824@relativity.student.utwente.nl> Reply-To: djb@ifa.au.dk References: <20000507234310.A4505@relativity.student.utwente.nl> <200005072217.QAA00636@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005072217.QAA00636@Ilsa.StevesCafe.com>; from smp@csn.net on Sun, May 07, 2000 at 04:17:10PM -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 07, 2000 at 04:17:10PM -0600, Steve Passe wrote: > [Discussion of stray irq7's] > > Another good experiment would be: > > both channels UDMA33 disabled in BIOS > UDMA66 enabled, hard drive attached > sound card driver removed > sound card removed Don't think I've abandoned the problem: I haven't. I'm going to look into this a.s.a.p. However, since I live in Enschede (the Netherlands), my mind is with the victims of the explosion right now. [1] I'll inform you all of the test results next week or so. Regards, Dave Boers. [1] I'm referring to the explosion of the fireworks depot which destroyed a considerable part of Enschede last saturday. The news has been all over the world, including CNN. -- djb@ifa.au.dk d.j.boers@tn.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 17 18: 1:37 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id 7508137BD32 for ; Wed, 17 May 2000 18:01:29 -0700 (PDT) (envelope-from randyd@tcainternet.com) Received: from tcainternet.com ([208.180.38.164]) by mail.tyler.net (Post.Office MTA v3.5.3 release 223 ID# 0-54929U30000L30000S0V35) with ESMTP id net for ; Wed, 17 May 2000 20:00:46 -0500 Message-ID: <392340E2.91841ED6@tcainternet.com> Date: Wed, 17 May 2000 20:01:22 -0500 From: "Randall D. DuCharme" X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: smp@freebsd.org Subject: FreeBSD 4.0-Release and P6DNF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I just tried installing 4.0-Release on a SuperMicro P6DNF system running 2 Intel 333MHz Overdrive CPUs. A UP kernel runs fine but an SMP kernel panics on boot with.... bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA interrupt panic: resource_list_alloc: resource entry is busy mp_lock = 00000001 cpu_id-0: lapic.id=00000000 I've been through the mailing list archives and there's been tons of problems reported with the SuperMicro boards, but none of the older fixes seem to apply. Suggestions greatly appreciated. Many thanks. RD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 17 18:26: 2 2000 Delivered-To: freebsd-smp@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id 2A5A337BC68 for ; Wed, 17 May 2000 18:25:57 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id TAA76379; Wed, 17 May 2000 19:25:53 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200005180125.TAA76379@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Randall D. DuCharme" Cc: smp@FreeBSD.ORG Subject: Re: FreeBSD 4.0-Release and P6DNF In-reply-to: Your message of "Wed, 17 May 2000 20:01:22 CDT." <392340E2.91841ED6@tcainternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 May 2000 19:25:53 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > Greetings, > > I just tried installing 4.0-Release on a SuperMicro P6DNF system running 2 > Intel 333MHz Overdrive CPUs. A UP kernel runs fine but an SMP kernel panics > on boot with.... > > bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA > interrupt > > panic: resource_list_alloc: resource entry is busy > mp_lock = 00000001 cpu_id-0: lapic.id=00000000 > > > I've been through the mailing list archives and there's been tons of problems > reported with the SuperMicro boards, but none of the older fixes seem to > apply. > > Suggestions greatly appreciated. First step is to run mptable as root on the UP system and post the results here. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 17 18:48:27 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id 2F36737BC9B for ; Wed, 17 May 2000 18:48:19 -0700 (PDT) (envelope-from randyd@tcainternet.com) Received: from tcainternet.com ([208.180.38.164]) by mail.tyler.net (Post.Office MTA v3.5.3 release 223 ID# 0-54929U30000L30000S0V35) with ESMTP id net for ; Wed, 17 May 2000 20:47:30 -0500 Message-ID: <39234BD9.3393D947@tcainternet.com> Date: Wed, 17 May 2000 20:48:10 -0500 From: "Randall D. DuCharme" X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: smp@freebsd.org Subject: Re: FreeBSD 4.0-Release and P6DNF References: <200005180125.TAA76379@Ilsa.StevesCafe.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks Steve, Here's the output: =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb860 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x46 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f7bd0 signature: 'PCMP' physical address: 0x000f7bd0 signature: 'PCMP' base table length: 260 version: 1.4 checksum: 0x8d OEM ID: 'INTEL ' Product ID: '440FX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 24 local APIC address: 0xfee00000 extended table length: 8 extended table checksum: 117 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 3 2 0x183fb ff 1 0x11 AP, usable 6 3 2 0x183fb ff -- Bus: Bus ID Type 0 PCI 1 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 1 0 2 0 INT conforms conforms 1 1 2 1 INT conforms conforms 1 0 2 2 INT conforms conforms 1 3 2 3 INT conforms conforms 1 4 2 4 INT conforms conforms 1 5 2 5 INT conforms conforms 1 6 2 6 INT conforms conforms 1 7 2 7 INT conforms conforms 1 8 2 8 INT conforms conforms 1 10 2 10 INT conforms conforms 1 12 2 12 INT conforms conforms 1 13 2 13 INT conforms conforms 1 15 2 20 INT active-lo level 1 11 2 16 INT active-lo level 1 11 2 17 INT active-lo level 1 14 2 18 INT active-lo level 1 9 2 19 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- bus ID: 1 bus info: 0x01 parent bus ID: 0 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== Hope this helps. RD Steve Passe wrote: > > Hi, > > > Greetings, > > > > I just tried installing 4.0-Release on a SuperMicro P6DNF system running 2 > > Intel 333MHz Overdrive CPUs. A UP kernel runs fine but an SMP kernel panics > > on boot with.... > > > > bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA > > interrupt > > > > panic: resource_list_alloc: resource entry is busy > > mp_lock = 00000001 cpu_id-0: lapic.id=00000000 > > > > > > I've been through the mailing list archives and there's been tons of problems > > reported with the SuperMicro boards, but none of the older fixes seem to > > apply. > > > > Suggestions greatly appreciated. > > First step is to run mptable as root on the UP system and post the results > here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 18 6:41:22 2000 Delivered-To: freebsd-smp@freebsd.org Received: from viper.dmpriest.com (viper.dmpriest.com [195.188.177.3]) by hub.freebsd.org (Postfix) with ESMTP id E0EF837B69C for ; Thu, 18 May 2000 06:41:16 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca.tdx.co.uk [195.188.177.195]) by viper.dmpriest.com (8.9.3/8.9.3/Kp) with ESMTP id OAA80414; Thu, 18 May 2000 14:41:07 +0100 (BST) Message-ID: <3923F2F3.E4C2C364@tdx.co.uk> Date: Thu, 18 May 2000 14:41:07 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.7 [en-gb] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Randall D. DuCharme" Cc: smp@freebsd.org Subject: Re: FreeBSD 4.0-Release and P6DNF References: <392340E2.91841ED6@tcainternet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Randall D. DuCharme" wrote: > > Greetings, > > I just tried installing 4.0-Release on a SuperMicro P6DNF system running 2 > Intel 333MHz Overdrive CPUs. A UP kernel runs fine but an SMP kernel panics > on boot with.... > > bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA > interrupt I've got a P6DNF, and P6DGU - both work fine w/FreeBSD 4.0 / 5.0... I also see the above warning, but I don't get any panic's... > I've been through the mailing list archives and there's been tons of problems > reported with the SuperMicro boards, but none of the older fixes seem to > apply. > > Suggestions greatly appreciated. Just to throw a possible spanner in the works... Many eons ago, our Intel distributor told us that none of the 'overdrive' chips are SMP usable? - Hope this doesn't apply in your case? :( I have 2 x P-Pro 200's w/256k in my board at the moment... I have also read that the M/Board requires a BIOS upgrade in order to work with the newer/overdrive chips - have you tried this? -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 18 7:23:27 2000 Delivered-To: freebsd-smp@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id 5620F37B6E7 for ; Thu, 18 May 2000 07:23:21 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id IAA79672; Thu, 18 May 2000 08:23:17 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200005181423.IAA79672@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Randall D. DuCharme" Cc: smp@FreeBSD.ORG Subject: Re: FreeBSD 4.0-Release and P6DNF In-reply-to: Your message of "Wed, 17 May 2000 20:48:10 CDT." <39234BD9.3393D947@tcainternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 May 2000 08:23:17 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, =============================================================================== > > MPTable, version 2.0.15 > ... > -- > Bus: Bus ID Type > 0 PCI > 1 ISA > -- > I/O APICs: APIC ID Version State Address > 2 0x11 usable 0xfec00000 > -- > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > ExtINT conforms conforms 1 0 2 0 > INT conforms conforms 1 1 2 1 > INT conforms conforms 1 0 2 2 > INT conforms conforms 1 3 2 3 > INT conforms conforms 1 4 2 4 > INT conforms conforms 1 5 2 5 > INT conforms conforms 1 6 2 6 > INT conforms conforms 1 7 2 7 > INT conforms conforms 1 8 2 8 > INT conforms conforms 1 10 2 10 > INT conforms conforms 1 12 2 12 > INT conforms conforms 1 13 2 13 > INT conforms conforms 1 15 2 20 > INT active-lo level 1 11 2 16 > INT active-lo level 1 11 2 17 > INT active-lo level 1 14 2 18 > INT active-lo level 1 9 2 19 ^ ^^ This BIOS is definitaly wrong. It shows your PCI slots as being on the ISA bus. The INTs themselves show up in 'ISA' notation as oppossed to 'PCI' notation, but that is probably because mptable believes them to be ISA (as will the kernel!). Another user reports the same warning, but no PANIC, I suspect that is an issue of what cards are in which PCI slot... Play with different PCI slot positions, try to load a newer BIOS. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 18 17:33:31 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id 0297C37B546 for ; Thu, 18 May 2000 17:33:28 -0700 (PDT) (envelope-from randyd@tcainternet.com) Received: from tcainternet.com ([208.180.38.164]) by mail.tyler.net (Post.Office MTA v3.5.3 release 223 ID# 0-66702U35000L35000S0V35) with ESMTP id net for ; Thu, 18 May 2000 19:32:45 -0500 Message-ID: <39248BD5.2D9F885B@tcainternet.com> Date: Thu, 18 May 2000 19:33:25 -0500 From: "Randall D. DuCharme" X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: smp@freebsd.org Subject: Re: FreeBSD 4.0-Release and P6DNF References: <200005181423.IAA79672@Ilsa.StevesCafe.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks Steve, The BIOS is the latest available for the board. I CVSup'ed the CURRENT sources, built a kernel (and the world) and all is happy.... well at least it runs and doesn't panic on boot. The MPTable output hasn't changed. I'll continue to mess around with it. Thanks again. Steve Passe wrote: > > Hi, > > =============================================================================== > > > > MPTable, version 2.0.15 > > > ... > > -- > > Bus: Bus ID Type > > 0 PCI > > 1 ISA > > -- > > I/O APICs: APIC ID Version State Address > > 2 0x11 usable 0xfec00000 > > -- > > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > > ExtINT conforms conforms 1 0 2 0 > > INT conforms conforms 1 1 2 1 > > INT conforms conforms 1 0 2 2 > > INT conforms conforms 1 3 2 3 > > INT conforms conforms 1 4 2 4 > > INT conforms conforms 1 5 2 5 > > INT conforms conforms 1 6 2 6 > > INT conforms conforms 1 7 2 7 > > INT conforms conforms 1 8 2 8 > > INT conforms conforms 1 10 2 10 > > INT conforms conforms 1 12 2 12 > > INT conforms conforms 1 13 2 13 > > INT conforms conforms 1 15 2 20 > > INT active-lo level 1 11 2 16 > > INT active-lo level 1 11 2 17 > > INT active-lo level 1 14 2 18 > > INT active-lo level 1 9 2 19 > ^ ^^ > > This BIOS is definitaly wrong. It shows your PCI slots as being on the > ISA bus. The INTs themselves show up in 'ISA' notation as oppossed to > 'PCI' notation, but that is probably because mptable believes them to be > ISA (as will the kernel!). Another user reports the same warning, but > no PANIC, I suspect that is an issue of what cards are in which PCI slot... > > Play with different PCI slot positions, try to load a newer BIOS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 18 17:35:55 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id A16EE37BB98 for ; Thu, 18 May 2000 17:35:51 -0700 (PDT) (envelope-from randyd@tcainternet.com) Received: from tcainternet.com ([208.180.38.164]) by mail.tyler.net (Post.Office MTA v3.5.3 release 223 ID# 0-66702U35000L35000S0V35) with ESMTP id net for ; Thu, 18 May 2000 19:35:09 -0500 Message-ID: <39248C65.F70568CF@tcainternet.com> Date: Thu, 18 May 2000 19:35:49 -0500 From: "Randall D. DuCharme" X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: smp@freebsd.org Subject: Re: FreeBSD 4.0-Release and P6DNF References: <392340E2.91841ED6@tcainternet.com> <3923F2F3.E4C2C364@tdx.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, The OverDrive CPUs work fine with Solaris and also with FreeBSD-CURRENT sources. My BIOS is the newest available. I'll continue to mess with it and post any interesting findings. Thanks for your thoughts! Karl Pielorz wrote: > Just to throw a possible spanner in the works... Many eons ago, our Intel > distributor told us that none of the 'overdrive' chips are SMP usable? - Hope > this doesn't apply in your case? :( > > I have 2 x P-Pro 200's w/256k in my board at the moment... > > I have also read that the M/Board requires a BIOS upgrade in order to work > with the newer/overdrive chips - have you tried this? > > -Karl RD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message