From owner-freebsd-smp Sun Feb 15 07:09:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15885 for freebsd-smp-outgoing; Sun, 15 Feb 1998 07:09:21 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from psasolar.psa.pencom.com (psasolar.colltech.com [208.229.236.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15877 for ; Sun, 15 Feb 1998 07:09:19 -0800 (PST) (envelope-from ejon@colltech.com) From: ejon@colltech.com Received: (from ejon@localhost) by psasolar.psa.pencom.com (VER/What/1.0) id JAA19006; Sun, 15 Feb 1998 09:09:05 -0600 (CST) Message-Id: <199802151509.JAA19006@psasolar.psa.pencom.com> Subject: Re: DEC PW 6200 troubles - more info In-Reply-To: <199802142331.QAA20741@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 14, 98 04:31:14 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Sun, 15 Feb 1998 09:09:05 -0600 (CST) Cc: mike@smith.net.au, ken@plutotech.com, ejon@colltech.com, smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Ken, Well, I wanted to hold off replying to your suggestion until I'd checked for the 12th time, but now I'm sure: there is no such option. There's also no issue date for the BIOS either in ROM or on the download page, so I don't know if it's reasonable to expect an update any time soon. Does anyone have any other suggestions on where to go next? Eric Strange sunspot activity caused Kenneth D. Merry to write: > Mike Smith wrote... > > > You're using MP Spec version 1.1, not 1.4. From my own, and other > > > folks' experience, you probably need to enable MP Spec version 1.4 in your > > > BIOS in order for the SMP kernel to work. (This isn't always the case, but > > > with newer motherboards, it definitely seems to be...) > > > > > > So, go into your BIOS, find the option that lets you change the MP > > > Spec version, and change it to 1.4. Send mail back to the list and let us > > > know whether this fixes your problem.. > > > > And if your BIOS doesn't offer such an option? > > Most 440FX and 440LX machines that I've heard of have an option to > switch back and forth between 1.1 and 1.4. He has a Natoma chipset board, > so he most likely does have an option in his bios to switch to MP Spec > version 1.4. Neptune chipset boxes only do 1.1, IIRC, but they do work. > > So, I guess the "right" thing to say is that if you have an option > in your BIOS to enable MP Spec version 1.4, do it. If not, and your > machine doesn't work with an SMP kernel, there's probably some other problem. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > 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 Sun Feb 15 11:30:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12119 for freebsd-smp-outgoing; Sun, 15 Feb 1998 11:30:47 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12105 for ; Sun, 15 Feb 1998 11:30:43 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id MAA18218; Sun, 15 Feb 1998 12:30:20 -0700 (MST) Message-Id: <199802151930.MAA18218@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: ejon@colltech.com cc: ken@plutotech.com (Kenneth D. Merry), mike@smith.net.au, smp@FreeBSD.ORG Subject: Re: DEC PW 6200 troubles - more info In-reply-to: Your message of "Sun, 15 Feb 1998 09:09:05 CST." <199802151509.JAA19006@psasolar.psa.pencom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Feb 1998 12:30:20 -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > Well, I wanted to hold off replying to your suggestion > until I'd checked for the 12th time, but now I'm sure: there is > no such option. > There's also no issue date for the BIOS either in ROM > or on the download page, so I don't know if it's reasonable > to expect an update any time soon. > > Does anyone have any other suggestions on where to > go next? You will have to start debugging the actual code. If possible use ddb to catch the point of error. If it happens too soon in the boot process you will need to start putting printf()s in the code to track down the exact spot of the problem. Once this is done we can consider the fix... -- 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 Sat Feb 21 09:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16175 for freebsd-smp-outgoing; Sat, 21 Feb 1998 09:10:25 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16167 for ; Sat, 21 Feb 1998 09:10:19 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id MAA24450 for ; Sat, 21 Feb 1998 12:08:28 -0500 (EST) Date: Sat, 21 Feb 1998 12:08:28 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-smp@FreeBSD.ORG Subject: make listings 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 One thing I like about this list (which can't, unfortunately, last) is that there's just no need to crosspost to current, because everyone running smp is either running current, and a reasonably recent snap ... smp hasn't had a release yet. Anyhow, on to my question .... which is prompted due to the breakage that's been rampant in current. This isn't a complaint, but I do my buildworld using -j 12 (like most of you probably do), and when there's some breakage, it's usually really difficult to figure out just what went blooey. I often end up doing a rebuild without the -j 12, just so I can get the error listing in some more coherent shape. Does anyone have a trick or pointer to how to handle error control in an smp environment, so that I don't end up having to do the rebuild to get to the reason for an error? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Feb 21 10:39:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27178 for freebsd-smp-outgoing; Sat, 21 Feb 1998 10:39:20 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mhub2.tc.umn.edu (0@mhub2.tc.umn.edu [128.101.131.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27168 for ; Sat, 21 Feb 1998 10:39:11 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-22-b-156.dialup.umn.edu by mhub2.tc.umn.edu; Sat, 21 Feb 98 12:38:56 -0600 Date: Sat, 21 Feb 1998 12:36:25 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: freebsd-smp@FreeBSD.ORG Subject: v1.111 of clock.c missing CLOCK_UNLOCK in i8254_get_timecount() 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 Hi, in v1.111 (980221) of clock.c i8254_get_timecount() breaks SMP. It looks like its just missing a CLOCK_UNLOCK before the write_eflags(). dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Feb 21 16:10:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12674 for freebsd-smp-outgoing; Sat, 21 Feb 1998 16:10:49 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12667 for ; Sat, 21 Feb 1998 16:10:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id BAA09455; Sun, 22 Feb 1998 01:05:57 +0100 (CET) To: dave adkins cc: freebsd-smp@FreeBSD.ORG Subject: Re: v1.111 of clock.c missing CLOCK_UNLOCK in i8254_get_timecount() In-reply-to: Your message of "Sat, 21 Feb 1998 12:36:25 CST." Date: Sun, 22 Feb 1998 01:05:57 +0100 Message-ID: <9453.888105957@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , dave adkins wri tes: > >Hi, > >in v1.111 (980221) of clock.c i8254_get_timecount() breaks SMP. It looks >like its just missing a CLOCK_UNLOCK before the write_eflags(). Yes, I belive this is the right fix. Please report back if you test it! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Feb 21 17:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20059 for freebsd-smp-outgoing; Sat, 21 Feb 1998 17:13:52 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20054 for ; Sat, 21 Feb 1998 17:13:50 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA17150; Sat, 21 Feb 1998 17:13:05 -0800 (PST) To: Poul-Henning Kamp cc: dave adkins , freebsd-smp@FreeBSD.ORG Subject: Re: v1.111 of clock.c missing CLOCK_UNLOCK in i8254_get_timecount() In-reply-to: Your message of "Sun, 22 Feb 1998 01:05:57 +0100." <9453.888105957@critter.freebsd.dk> Date: Sat, 21 Feb 1998 17:13:05 -0800 Message-ID: <17146.888109985@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've committed it and am in the middle of a kernel build on our SMP test box right now. :) > In message , dave adkins w ri > tes: > > > >Hi, > > > >in v1.111 (980221) of clock.c i8254_get_timecount() breaks SMP. It looks > >like its just missing a CLOCK_UNLOCK before the write_eflags(). > > Yes, I belive this is the right fix. Please report back if you test it! > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "Drink MONO-tonic, it goes down but it will NEVER come back up!" > > 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 Sat Feb 21 21:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16110 for freebsd-smp-outgoing; Sat, 21 Feb 1998 21:30:35 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from imo20.mx.aol.com (imo20.mx.aol.com [198.81.17.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16105 for ; Sat, 21 Feb 1998 21:30:33 -0800 (PST) (envelope-from StevenR362@aol.com) From: StevenR362@aol.com Received: from StevenR362@aol.com by imo20.mx.aol.com (IMOv12/Dec1997) id HBBQa03199 for ; Sun, 22 Feb 1998 00:29:55 -0500 (EST) Message-ID: <63382b52.34efb7d6@aol.com> Date: Sun, 22 Feb 1998 00:29:55 EST To: smp@FreeBSD.ORG Mime-Version: 1.0 Subject: SMP options. Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: AOL 3.0 for Windows 95 sub 64 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just got my new smp system running for the first time today. The rslock bug had me thinking that I had bum hardware until I applied John Dyson's patch. Anyways, I have questions as to which if any kernel options are not valid or are mandatory. I could move the rslock panic around and exhibit different simptoms depending on config file flags and options selected. In particular, are options "VM86", and USER_LDT valid with a SMP kernel and is option FAILSAFE mandatory? Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message