From owner-freebsd-smp Mon Jan 15 18:28:59 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mx1.colltech.com (ausproxy.colltech.com [208.229.236.19]) by hub.freebsd.org (Postfix) with ESMTP id E044737B6A9 for ; Mon, 15 Jan 2001 18:28:42 -0800 (PST) Received: from mail2.colltech.com (mail2.colltech.com [208.229.236.41]) by mx1.colltech.com (8.9.3/8.9.3/not) with ESMTP id UAA11895 for ; Mon, 15 Jan 2001 20:28:41 -0600 Received: from colltech.com (06-069.024.popsite.net [66.19.1.69] (may be forged)) by mail2.colltech.com (8.9.3/8.9.3/not) with ESMTP id UAA07290 for ; Mon, 15 Jan 2001 20:28:38 -0600 Message-ID: <3A636D37.3C097E35@colltech.com> Date: Mon, 15 Jan 2001 21:35:51 +0000 From: Craig Christophel X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Subject: mtx-def-list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there anywhere I can find a list of which mutex protects which data structure, and what standard for naming is used. I have browsed the kernel code to gain some understanding of this, but before I attempt this, I would like more information if it is avaliable Thanks, Craig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 10:35: 7 2001 Delivered-To: freebsd-smp@freebsd.org Received: from bugtracker.compusa.com (unknown [198.22.121.253]) by hub.freebsd.org (Postfix) with SMTP id D716137B402 for ; Tue, 16 Jan 2001 10:34:37 -0800 (PST) Received: (qmail 81887 invoked by uid 1007); 16 Jan 2001 18:34:52 -0000 Message-ID: <20010116183452.81886.qmail@bugtracker.compusa.com> From: "freebsd" To: freebsd-smp@freebsd.org Subject: problems with smp on compaq 1600 Date: Tue, 16 Jan 2001 18:34:52 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having a problem getting SMP working on a compaq 1600 with 4.2. The last thing i get is no devsw, then it hangs when it try to mount root. /kernel: no devsw (majdev=0 bootdev=0xa0300000) /kernel: Mounting root from ufs:/dev/idad0s2a I'm not sure what i need to look at. Should i also paste kernel config? I just remove the # from the 2 smp lines and built my kernel. btw what does this mean? Extended Table HOSED! =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f4ff0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x9f mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000fc131 signature: 'PCMP' base table length: 452 version: 1.4 checksum: 0x73 OEM ID: 'COMPAQ ' Product ID: 'PROLIANT ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 48 local APIC address: 0xfee00000 extended table length: 76 extended table checksum: 86 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 1 0x10 BSP, usable 6 5 2 0x183fbff 0 0x10 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 ISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 1 9:A 8 23 INT active-lo level 1 9:B 8 22 INT active-lo level 1 7:A 8 30 INT active-lo level 1 13:A 8 18 INT active-lo level 1 13:C 8 18 INT active-lo level 1 13:B 8 26 INT active-lo level 1 13:D 8 26 INT active-lo level 1 11:A 8 17 INT active-lo level 1 11:C 8 17 INT active-lo level 1 11:B 8 25 INT active-lo level 1 11:D 8 25 INT active-lo level 1 10:A 8 16 INT active-lo level 1 10:C 8 16 INT active-lo level 1 10:B 8 24 INT active-lo level 1 10:D 8 24 INT active-lo level 0 18:A 8 21 INT active-lo level 0 18:C 8 21 INT active-lo level 0 18:B 8 29 INT active-lo level 0 18:D 8 29 INT active-lo level 0 16:A 8 20 INT active-lo level 0 16:C 8 20 INT active-lo level 0 16:B 8 28 INT active-lo level 0 16:D 8 28 INT active-lo level 0 15:A 8 19 INT active-lo level 0 15:C 8 19 INT active-lo level 0 15:B 8 27 INT active-lo level 0 15:D 8 27 INT active-lo level 0 20:D 8 34 INT active-lo edge 0 14:A 8 13 INT active-hi edge 9 1 8 1 INT active-hi edge 9 0 8 2 INT active-hi edge 9 3 8 3 INT active-hi edge 9 4 8 4 INT active-hi edge 9 6 8 6 INT active-hi edge 9 7 8 7 INT active-hi edge 9 8 8 8 INT active-hi edge 9 12 8 12 INT active-lo edge 9 13 8 13 INT active-hi edge 9 14 8 14 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 255 0 NMI conforms conforms 9 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 11:46:14 2001 Delivered-To: freebsd-smp@freebsd.org Received: from bugtracker.compusa.com (unknown [198.22.121.253]) by hub.freebsd.org (Postfix) with SMTP id C735737B402 for ; Tue, 16 Jan 2001 11:45:52 -0800 (PST) Received: (qmail 82036 invoked by uid 1007); 16 Jan 2001 19:46:07 -0000 Message-ID: <20010116194607.82035.qmail@bugtracker.compusa.com> References: <20010116183452.81886.qmail@bugtracker.compusa.com> In-Reply-To: <20010116183452.81886.qmail@bugtracker.compusa.com> From: "freebsd" To: freebsd-smp@FreeBSD.ORG Subject: Re: problems with smp on compaq 1600 Date: Tue, 16 Jan 2001 19:46:07 GMT 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 btw, APIC mode is set to Full Table, not Full Table -mapped. > I'm having a problem getting SMP working on a compaq 1600 with 4.2. The > last thing i get is no devsw, then it hangs when it try to mount root. > > /kernel: no devsw (majdev=0 bootdev=0xa0300000) > /kernel: Mounting root from ufs:/dev/idad0s2a > > I'm not sure what i need to look at. > Should i also paste kernel config? I just remove the # from the 2 smp lines > and built my kernel. > btw what does this mean? Extended Table HOSED! > > > =============================================================================== > > MPTable, version 2.0.15 > > ------------------------------------------------------------------------------- > > MP Floating Pointer Structure: > > location: BIOS > physical address: 0x000f4ff0 > signature: '_MP_' > length: 16 bytes > version: 1.4 > checksum: 0x9f > mode: Virtual Wire > > ------------------------------------------------------------------------------- > > MP Config Table Header: > > physical address: 0x000fc131 > signature: 'PCMP' > base table length: 452 > version: 1.4 > checksum: 0x73 > OEM ID: 'COMPAQ ' > Product ID: 'PROLIANT ' > OEM table pointer: 0x00000000 > OEM table size: 0 > entry count: 48 > local APIC address: 0xfee00000 > extended table length: 76 > extended table checksum: 86 > > ------------------------------------------------------------------------------- > > MP Config Base Table Entries: > > -- > Processors: APIC ID Version State Family Model Step > Flags > 1 0x10 BSP, usable 6 5 2 > 0x183fbff > 0 0x10 AP, usable 6 5 2 > 0x183fbff > -- > Bus: Bus ID Type > 0 PCI > 1 PCI > 9 ISA > -- > I/O APICs: APIC ID Version State Address > 8 0x11 usable 0xfec00000 > -- > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID > PIN# > INT active-lo level 1 9:A 8 > 23 > INT active-lo level 1 9:B 8 > 22 > INT active-lo level 1 7:A 8 > 30 > INT active-lo level 1 13:A 8 > 18 > INT active-lo level 1 13:C 8 > 18 > INT active-lo level 1 13:B 8 > 26 > INT active-lo level 1 13:D 8 > 26 > INT active-lo level 1 11:A 8 > 17 > INT active-lo level 1 11:C 8 > 17 > INT active-lo level 1 11:B 8 > 25 > INT active-lo level 1 11:D 8 > 25 > INT active-lo level 1 10:A 8 > 16 > INT active-lo level 1 10:C 8 > 16 > INT active-lo level 1 10:B 8 > 24 > INT active-lo level 1 10:D 8 > 24 > INT active-lo level 0 18:A 8 > 21 > INT active-lo level 0 18:C 8 > 21 > INT active-lo level 0 18:B 8 > 29 > INT active-lo level 0 18:D 8 > 29 > INT active-lo level 0 16:A 8 > 20 > INT active-lo level 0 16:C 8 > 20 > INT active-lo level 0 16:B 8 > 28 > INT active-lo level 0 16:D 8 > 28 > INT active-lo level 0 15:A 8 > 19 > INT active-lo level 0 15:C 8 > 19 > INT active-lo level 0 15:B 8 > 27 > INT active-lo level 0 15:D 8 > 27 > INT active-lo level 0 20:D 8 > 34 > INT active-lo edge 0 14:A 8 > 13 > INT active-hi edge 9 1 8 > 1 > INT active-hi edge 9 0 8 > 2 > INT active-hi edge 9 3 8 > 3 > INT active-hi edge 9 4 8 > 4 > INT active-hi edge 9 6 8 > 6 > INT active-hi edge 9 7 8 > 7 > INT active-hi edge 9 8 8 > 8 > INT active-hi edge 9 12 8 > 12 > INT active-lo edge 9 13 8 > 13 > INT active-hi edge 9 14 8 > 14 > -- > Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID > PIN# > ExtINT conforms conforms 9 0 255 > 0 > NMI conforms conforms 9 0 255 > 1 > > ------------------------------------------------------------------------------- > > MP Config Extended Table Entries: > > Extended Table HOSED! > > > 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 Jan 16 12:59:29 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mail3.mx.voyager.net (mail3.mx.voyager.net [216.93.66.202]) by hub.freebsd.org (Postfix) with ESMTP id E9A9737B402 for ; Tue, 16 Jan 2001 12:59:10 -0800 (PST) Received: from thunder.voyager.net (net-216-93-125-061.hcv.com [216.93.125.61]) by mail3.mx.voyager.net (8.10.2/8.10.2) with ESMTP id f0GKx8R54903 for ; Tue, 16 Jan 2001 15:59:09 -0500 (EST) Message-Id: <5.0.2.1.2.20010116145952.023ed230@pop3.venux.net> X-Sender: mhagerty@pop.voyager.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 16 Jan 2001 15:58:58 -0500 To: freebsd-smp@freebsd.org From: Matthew Hagerty Subject: FBSD-4.2 SMP boot failure, please help... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I have a Compaq Proliant 1600/1600R with two P2-400 matched processors running on FreeBSD-4.2-Release. The machine runs fine with a single processor kernel, but when I try to boot with an SMP kernel it locks up during the boot process. These are the last several lines of the boot-up: Changing APIC ID for IOAPIC # 0 from 0 to 8 on chip Programming 35 pins in IOAPIC # 0 IOAPIC # 0 intpin 2 -> irq 0 IOAPIC # 0 intpin 30 -> irq 2 ... HANG ... I have to power cycle the machine to bring it back up. During power-up the system detects and reports both processors, so they seem to be found. I was looking in the list archives and found many people having problems with Compaq servers, but there did not seem to be any resolutions. Any insight as to what might be causing this would be greatly appreciated. Thank you, Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 13: 3:16 2001 Delivered-To: freebsd-smp@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9387237B402 for ; Tue, 16 Jan 2001 13:02:57 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0GL2tB22490; Tue, 16 Jan 2001 13:02:55 -0800 (PST) Date: Tue, 16 Jan 2001 13:02:55 -0800 From: Alfred Perlstein To: Matthew Hagerty Cc: freebsd-smp@FreeBSD.ORG Subject: Re: FBSD-4.2 SMP boot failure, please help... Message-ID: <20010116130254.V7240@fw.wintelcom.net> References: <5.0.2.1.2.20010116145952.023ed230@pop3.venux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.2.20010116145952.023ed230@pop3.venux.net>; from mhagerty@voyager.net on Tue, Jan 16, 2001 at 03:58:58PM -0500 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew Hagerty [010116 12:59] wrote: > Greetings, > > I have a Compaq Proliant 1600/1600R with two P2-400 matched processors > running on FreeBSD-4.2-Release. The machine runs fine with a single > processor kernel, but when I try to boot with an SMP kernel it locks up > during the boot process. These are the last several lines of the boot-up: > > > Changing APIC ID for IOAPIC # 0 from 0 to 8 on chip > Programming 35 pins in IOAPIC # 0 > IOAPIC # 0 intpin 2 -> irq 0 > IOAPIC # 0 intpin 30 -> irq 2 > ... HANG ... > > I have to power cycle the machine to bring it back up. During power-up the > system detects and reports both processors, so they seem to be found. > > I was looking in the list archives and found many people having problems > with Compaq servers, but there did not seem to be any resolutions. Any > insight as to what might be causing this would be greatly appreciated. Try a -stable snapshot from about a week ago from ftp://releng4.freebsd.org/ -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 13:29:24 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mail12.svr.pol.co.uk (mail12.svr.pol.co.uk [195.92.193.215]) by hub.freebsd.org (Postfix) with ESMTP id 978E637B401 for ; Tue, 16 Jan 2001 13:29:06 -0800 (PST) Received: from modem-103.ununnilium.dialup.pol.co.uk ([62.136.75.103] helo=DEDICATION1) by mail12.svr.pol.co.uk with smtp (Exim 3.13 #0) id 14Idf7-00057l-00 for freebsd-smp@freebsd.org; Tue, 16 Jan 2001 21:29:05 +0000 Message-ID: <000f01c08003$562b4f30$01010a0a@DEDICATIONINET.local> From: "Andy Chantrill" To: Subject: APIC Date: Tue, 16 Jan 2001 21:28:57 -0000 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey, A few questions about smp (I'm new to this gig): i) What is APIC? ii) What is the difference between "APIC" and "APIC -mapped" in my Compaq Proliant BIOS? iii) Which should I be using? Thanks, Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 17:52: 9 2001 Delivered-To: freebsd-smp@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 8358E37B402 for ; Tue, 16 Jan 2001 17:51:51 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id SAA26313; Tue, 16 Jan 2001 18:46:57 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAxbaayZ; Tue Jan 16 18:46:53 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA20200; Tue, 16 Jan 2001 18:51:45 -0700 (MST) From: Terry Lambert Message-Id: <200101170151.SAA20200@usr08.primenet.com> Subject: Re: APIC To: andy@chantrill.freeserve.co.uk (Andy Chantrill) Date: Wed, 17 Jan 2001 01:51:45 +0000 (GMT) Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: <000f01c08003$562b4f30$01010a0a@DEDICATIONINET.local> from "Andy Chantrill" at Jan 16, 2001 09:28:57 PM X-Mailer: ELM [version 2.5 PL2] 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 > Hey, > > A few questions about smp (I'm new to this gig): > > i) What is APIC? Advanced Programmable Interrupt Controller. Your processor has one, for each processor you have, and your I/O chipset has at least one. For more information, you should probably look at the Intel Multiprocessing specification, version 1.4 or better. It's basically Intel's way of getting a patent and externalizing the SMP interprocessor arbitration logic, so tho no clone vendors can create SMP systems which are compatible, without licensing the patent. That's why all the clone vendors got together and created "OpenAPIC". > ii) What is the difference between "APIC" and "APIC -mapped" in > my Compaq Proliant BIOS? You would have to ask Compaq, to be absolutely sure.; it could mean anything, really. > iii) Which should I be using? In general terms, whatever it says you should use for UnixWare is usually conservative enough to work with BSD, which likes to cut things pretty close to the glass (that is, BSD has some pretty high expectations of the hardware having been built to specification correctly). My suggestion would be "leave it alone, unless it doesn't work, in which case, use whatever works, and post about it to this list, so it will be saved in the archives for the next person". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jan 16 20:32:40 2001 Delivered-To: freebsd-smp@freebsd.org Received: from zilla.emergent.com.au (www.emergent.com.au [203.27.68.30]) by hub.freebsd.org (Postfix) with ESMTP id F276637B401 for ; Tue, 16 Jan 2001 20:32:20 -0800 (PST) Received: from apache2 (tide86.microsoft.com [131.107.3.86]) by zilla.emergent.com.au (8.9.3/8.9.3) with SMTP id PAA66492; Wed, 17 Jan 2001 15:32:19 +1100 (EST) (envelope-from cmoran@emergent.com.au) Message-ID: <008d01c0803e$76425440$4ba63c9d@southpacific.corp.microsoft.com> Reply-To: "Christopher F. Moran" From: "Christopher F. Moran" To: , "Terry Lambert" , "Andy Chantrill" References: <200101170151.SAA20200@usr08.primenet.com> Subject: Re: APIC Date: Wed, 17 Jan 2001 15:31:36 +1100 Organization: Emergent Technology 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On my Proliant 1500 I had to use Mapped mode. The system was unstable (on 4.0 & 4.1) in "Full" Cheers, ----- Original Message ----- From: "Terry Lambert" To: "Andy Chantrill" Cc: Sent: Wednesday, January 17, 2001 12:51 PM Subject: Re: APIC > > Hey, > > > > A few questions about smp (I'm new to this gig): > > > > i) What is APIC? > > Advanced Programmable Interrupt Controller. Your processor > has one, for each processor you have, and your I/O chipset > has at least one. > > For more information, you should probably look at the Intel > Multiprocessing specification, version 1.4 or better. > > > It's basically Intel's way of getting a patent and externalizing > the SMP interprocessor arbitration logic, so tho no clone > vendors can create SMP systems which are compatible, without > licensing the patent. That's why all the clone vendors got > together and created "OpenAPIC". > > > > ii) What is the difference between "APIC" and "APIC -mapped" in > > my Compaq Proliant BIOS? > > You would have to ask Compaq, to be absolutely sure.; it could > mean anything, really. > > > iii) Which should I be using? > > In general terms, whatever it says you should use for UnixWare > is usually conservative enough to work with BSD, which likes > to cut things pretty close to the glass (that is, BSD has some > pretty high expectations of the hardware having been built to > specification correctly). > > My suggestion would be "leave it alone, unless it doesn't work, > in which case, use whatever works, and post about it to this > list, so it will be saved in the archives for the next person". > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 6:53:55 2001 Delivered-To: freebsd-smp@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id CCB4637B400 for ; Wed, 17 Jan 2001 06:53:36 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id PAA43156 for freebsd-smp@freebsd.org; Wed, 17 Jan 2001 15:53:35 +0100 (CET) (envelope-from kuku) Date: Wed, 17 Jan 2001 15:53:35 +0100 (CET) From: Christoph Kukulies Message-Id: <200101171453.PAA43156@gilberto.physik.rwth-aachen.de> To: freebsd-smp@freebsd.org Subject: dual CPUs for OpenGL any good? Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sure, this is not a Windows NT group here but I know a lot of expertise hanging around here: We have an application that runs under NT and does a lot of OpenGL. CPU load is high. It's a single process, probably single thread application. I'm wondering if I should invest in CPUs or in Graphics accelerators (video card). Could a monolithic application benefit from multi CPU at all? Could driver code run on a different CPU while the other CPU is running for the application? Comments? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 8:47:38 2001 Delivered-To: freebsd-smp@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0214A37B400 for ; Wed, 17 Jan 2001 08:47:21 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HGlDV22320; Wed, 17 Jan 2001 08:47:13 -0800 (PST) Date: Wed, 17 Jan 2001 08:47:13 -0800 From: Alfred Perlstein To: Christoph Kukulies Cc: freebsd-smp@FreeBSD.ORG Subject: Re: dual CPUs for OpenGL any good? Message-ID: <20010117084713.M7240@fw.wintelcom.net> References: <200101171453.PAA43156@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101171453.PAA43156@gilberto.physik.rwth-aachen.de>; from kuku@gilberto.physik.rwth-aachen.de on Wed, Jan 17, 2001 at 03:53:35PM +0100 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Christoph Kukulies [010117 06:54] wrote: > Sure, this is not a Windows NT group here but I know a lot > of expertise hanging around here: We have an application that runs > under NT and does a lot of OpenGL. CPU load is high. It's a single process, > probably single thread application. I'm wondering if I should invest > in CPUs or in Graphics accelerators (video card). > > Could a monolithic application benefit from multi CPU at all? > Could driver code run on a different CPU while the other CPU is running for > the application? > > Comments? Adding a dedicated gfx CPU (video card) is probably the best idea. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 9:15:36 2001 Delivered-To: freebsd-smp@freebsd.org Received: from bugtracker.compusa.com (unknown [198.22.121.253]) by hub.freebsd.org (Postfix) with SMTP id 83CE137B400 for ; Wed, 17 Jan 2001 09:15:14 -0800 (PST) Received: (qmail 85053 invoked by uid 1007); 17 Jan 2001 17:15:24 -0000 Message-ID: <20010117171524.85052.qmail@bugtracker.compusa.com> References: <5.0.2.1.2.20010116145952.023ed230@pop3.venux.net> In-Reply-To: <5.0.2.1.2.20010116145952.023ed230@pop3.venux.net> From: "freebsd" To: Matthew Hagerty Cc: freebsd-smp@FreeBSD.ORG Subject: Re: FBSD-4.2 SMP boot failure, please help... Date: Wed, 17 Jan 2001 17:15:24 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well looks like my 1600 boots with the SMP kernel as long as APIC mode is set to -mapped also ( this is set via the system configure disk/parition ) bellow is a list of what mptable looks like with mapped. notice the number of INTs went down to 15 (from i think) I'm testing how stable the system by building a kernel over and over again. Any other ideas on what i can do to test it out? MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f4ff0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x9f mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000fc131 signature: 'PCMP' base table length: 260 version: 1.4 checksum: 0x15 OEM ID: 'COMPAQ ' Product ID: 'PROLIANT ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 24 local APIC address: 0xfee00000 extended table length: 76 extended table checksum: 86 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 1 0x10 BSP, usable 6 5 2 0x183fbff 0 0x10 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 ISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-hi edge 9 1 8 1 INT active-hi edge 9 0 8 2 INT active-hi edge 9 3 8 3 INT active-hi edge 9 4 8 4 INT active-hi level 9 5 8 5 INT active-hi edge 9 6 8 6 INT active-hi edge 9 7 8 7 INT active-hi edge 9 8 8 8 INT active-hi level 9 9 8 9 INT active-hi level 9 10 8 10 INT active-hi level 9 11 8 11 INT active-hi edge 9 12 8 12 INT active-lo edge 9 13 8 13 INT active-hi edge 9 14 8 14 INT active-hi level 9 15 8 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 255 0 NMI conforms conforms 9 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Matthew Hagerty writes: > Greetings, > > I have a Compaq Proliant 1600/1600R with two P2-400 matched processors > running on FreeBSD-4.2-Release. The machine runs fine with a single > processor kernel, but when I try to boot with an SMP kernel it locks up > during the boot process. These are the last several lines of the boot-up: > > > Changing APIC ID for IOAPIC # 0 from 0 to 8 on chip > Programming 35 pins in IOAPIC # 0 > IOAPIC # 0 intpin 2 -> irq 0 > IOAPIC # 0 intpin 30 -> irq 2 > ... HANG ... > > I have to power cycle the machine to bring it back up. During power-up the > system detects and reports both processors, so they seem to be found. > > I was looking in the list archives and found many people having problems > with Compaq servers, but there did not seem to be any resolutions. Any > insight as to what might be causing this would be greatly appreciated. > > Thank you, > Matthew > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 10:33:58 2001 Delivered-To: freebsd-smp@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 90AD937B6C4 for ; Wed, 17 Jan 2001 10:33:40 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HIVjL37848; Wed, 17 Jan 2001 10:31:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010116183452.81886.qmail@bugtracker.compusa.com> Date: Wed, 17 Jan 2001 10:33:37 -0800 (PST) From: John Baldwin To: freebsd Subject: RE: problems with smp on compaq 1600 Cc: freebsd-smp@FreeBSD.org Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Jan-01 freebsd wrote: > I'm having a problem getting SMP working on a compaq 1600 with 4.2. The > last thing i get is no devsw, then it hangs when it try to mount root. > > /kernel: no devsw (majdev=0 bootdev=0xa0300000) > /kernel: Mounting root from ufs:/dev/idad0s2a > > I'm not sure what i need to look at. > Should i also paste kernel config? I just remove the # from the 2 smp lines > and built my kernel. > btw what does this mean? Extended Table HOSED! Ok, after comparing the two tables, it looks like you have interrupts on pins higher than 23, which might be the problem. Peter, does -current support 32 APIC ints now? If so, you could try installing a current snapshot as a test to see if it works. If it does, then 5.0 will run in Full mode fine, but 4.x will need the mapped mode. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 11:15:25 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mass.osd.bsdi.com (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 95B6037B404; Wed, 17 Jan 2001 11:15:03 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0HJTag01025; Wed, 17 Jan 2001 11:29:36 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101171929.f0HJTag01025@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: freebsd , freebsd-smp@FreeBSD.org Subject: Re: problems with smp on compaq 1600 In-reply-to: Your message of "Wed, 17 Jan 2001 10:33:37 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jan 2001 11:29:36 -0800 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > btw what does this mean? Extended Table HOSED! It probably means that your APIC table has the traditional off-by-one Compaq error. Note that your situation also looks like the traditional "no clock interrupts" hang. > Ok, after comparing the two tables, it looks like you have interrupts on pins > higher than 23, which might be the problem. Peter, does -current support 32 > APIC ints now? If so, you could try installing a current snapshot as a test to > see if it works. If it does, then 5.0 will run in Full mode fine, but 4.x will > need the mapped mode. Actually, either mode *should* work with 4.x, since we pack intpins down based on their usage, not their pin number (Tor fixed this a while back). I've installed 4.2 on a ProFusion box with a single 64-pin APIC (the RAID controller was on pin 50-something). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 11:21:49 2001 Delivered-To: freebsd-smp@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3145D37B6E1; Wed, 17 Jan 2001 11:21:18 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0HJJNL38932; Wed, 17 Jan 2001 11:19:23 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101171929.f0HJTag01025@mass.osd.bsdi.com> Date: Wed, 17 Jan 2001 11:21:16 -0800 (PST) From: John Baldwin To: Mike Smith Subject: Re: problems with smp on compaq 1600 Cc: freebsd-smp@FreeBSD.org, freebsd Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Jan-01 Mike Smith wrote: >> >> > btw what does this mean? Extended Table HOSED! > > It probably means that your APIC table has the traditional off-by-one > Compaq error. Note that your situation also looks like the traditional > "no clock interrupts" hang. > >> Ok, after comparing the two tables, it looks like you have interrupts on >> pins >> higher than 23, which might be the problem. Peter, does -current support 32 >> APIC ints now? If so, you could try installing a current snapshot as a test >> to >> see if it works. If it does, then 5.0 will run in Full mode fine, but 4.x >> will >> need the mapped mode. > > Actually, either mode *should* work with 4.x, since we pack intpins down > based on their usage, not their pin number (Tor fixed this a while back). > I've installed 4.2 on a ProFusion box with a single 64-pin APIC (the RAID > controller was on pin 50-something). Ok. I wasn't sure about that part. Thanks for clarifying. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 14:18:36 2001 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 422BB37B698; Wed, 17 Jan 2001 14:18:10 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id XAA96703; Wed, 17 Jan 2001 23:18:08 +0100 (CET) Message-Id: <200101172218.XAA96703@midten.fast.no> To: msmith@FreeBSD.ORG Cc: jhb@FreeBSD.ORG, freebsd , freebsd-smp@FreeBSD.ORG Subject: Re: problems with smp on compaq 1600 From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 17 Jan 2001 11:29:36 -0800" References: <200101171929.f0HJTag01025@mass.osd.bsdi.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Wed_Jan_17_23:14:38_2001)--" Content-Transfer-Encoding: 7bit Date: Wed, 17 Jan 2001 23:18:07 +0100 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----Next_Part(Wed_Jan_17_23:14:38_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Actually, either mode *should* work with 4.x, since we pack intpins down > based on their usage, not their pin number (Tor fixed this a while back). > I've installed 4.2 on a ProFusion box with a single 64-pin APIC (the RAID > controller was on pin 50-something). Not based on their usage, but on their presence in the MP table. The number of unique (IOAPIC id, intpin) tuples described in the MP table must be 24 or lower for all interrupts to be properly delivered. One MP table for compaq 1600 seems to have 26 unique (IOPAIC id, intpin) tuples, thus two interrupt routings in the MP table will be silently ignored. A warning should probably be given. For FreeBSD 4.2-STABLE, NHWI and APIC_INTMAPSIZE can probably be increased from 24 to 25 (since NSWI is 7). This is still below 26. A better approach is to defer PCI interrupt assignment until the devices are probed (i.e. towards the usage based packing you mentioned). A patch for -current is enclosed. - Tor Egge ----Next_Part(Wed_Jan_17_23:14:38_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/i386/i386/mpapic.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mpapic.c,v retrieving revision 1.45 diff -u -r1.45 mpapic.c --- sys/i386/i386/mpapic.c 2001/01/10 04:43:46 1.45 +++ sys/i386/i386/mpapic.c 2001/01/17 21:58:46 @@ -177,19 +180,94 @@ /* * Setup the IO APIC. */ + extern int apic_pin_trigger; /* 'opaque' */ -int -io_apic_setup(int apic) + +void +io_apic_setup_intpin(int apic, int pin) { - int maxpin; + int bus, bustype, irq; u_char select; /* the select register is 8 bits */ u_int32_t flags; /* the window register is 32 bits */ u_int32_t target; /* the window register is 32 bits */ u_int32_t vector; /* the window register is 32 bits */ - int pin, level; + int level; target = IOART_DEST; + select = pin * 2 + IOAPIC_REDTBL0; /* register */ + /* + * Always disable interrupts, and by default map + * pin X to IRQX because the disable doesn't stick + * and the uninitialize vector will get translated + * into a panic. + * + * This is correct for IRQs 1 and 3-15. In the other cases, + * any robust driver will handle the spurious interrupt, and + * the effective NOP beats a panic. + * + * A dedicated "bogus interrupt" entry in the IDT would + * be a nicer hack, although some one should find out + * why some systems are generating interrupts when they + * shouldn't and stop the carnage. + */ + vector = NRSVIDT + pin; /* IDT vec */ + io_apic_write(apic, select, + (io_apic_read(apic, select) & ~IOART_INTMASK + & ~0xff)|IOART_INTMSET|vector); + + /* we only deal with vectored INTs here */ + if (apic_int_type(apic, pin) != 0) + return; + + irq = apic_irq(apic, pin); + if (irq < 0) + return; + + /* determine the bus type for this pin */ + bus = apic_src_bus_id(apic, pin); + if (bus == -1) + return; + bustype = apic_bus_type(bus); + + if ((bustype == ISA) && + (pin < IOAPIC_ISA_INTS) && + (irq == pin) && + (apic_polarity(apic, pin) == 0x1) && + (apic_trigger(apic, pin) == 0x3)) { + /* + * A broken BIOS might describe some ISA + * interrupts as active-high level-triggered. + * Use default ISA flags for those interrupts. + */ + flags = DEFAULT_ISA_FLAGS; + } else { + /* + * Program polarity and trigger mode according to + * interrupt entry. + */ + flags = DEFAULT_FLAGS; + level = trigger(apic, pin, &flags); + if (level == 1) + apic_pin_trigger |= (1 << irq); + polarity(apic, pin, &flags, level); + } + + /* program the appropriate registers */ + if (apic != 0 || pin != irq) + printf("IOAPIC #%d intpin %d -> irq %d\n", + apic, pin, irq); + vector = NRSVIDT + irq; /* IDT vec */ + io_apic_write(apic, select, flags | vector); + io_apic_write(apic, select + 1, target); +} + +int +io_apic_setup(int apic) +{ + int maxpin; + int pin; + if (apic == 0) apic_pin_trigger = 0; /* default to edge-triggered */ @@ -197,73 +275,7 @@ printf("Programming %d pins in IOAPIC #%d\n", maxpin, apic); for (pin = 0; pin < maxpin; ++pin) { - int bus, bustype, irq; - - select = pin * 2 + IOAPIC_REDTBL0; /* register */ - /* - * Always disable interrupts, and by default map - * pin X to IRQX because the disable doesn't stick - * and the uninitialize vector will get translated - * into a panic. - * - * This is correct for IRQs 1 and 3-15. In the other cases, - * any robust driver will handle the spurious interrupt, and - * the effective NOP beats a panic. - * - * A dedicated "bogus interrupt" entry in the IDT would - * be a nicer hack, although some one should find out - * why some systems are generating interrupts when they - * shouldn't and stop the carnage. - */ - vector = NRSVIDT + pin; /* IDT vec */ - io_apic_write(apic, select, - (io_apic_read(apic, select) & ~IOART_INTMASK - & ~0xff)|IOART_INTMSET|vector); - - /* we only deal with vectored INTs here */ - if (apic_int_type(apic, pin) != 0) - continue; - - irq = apic_irq(apic, pin); - if (irq < 0) - continue; - - /* determine the bus type for this pin */ - bus = apic_src_bus_id(apic, pin); - if (bus == -1) - continue; - bustype = apic_bus_type(bus); - - if ((bustype == ISA) && - (pin < IOAPIC_ISA_INTS) && - (irq == pin) && - (apic_polarity(apic, pin) == 0x1) && - (apic_trigger(apic, pin) == 0x3)) { - /* - * A broken BIOS might describe some ISA - * interrupts as active-high level-triggered. - * Use default ISA flags for those interrupts. - */ - flags = DEFAULT_ISA_FLAGS; - } else { - /* - * Program polarity and trigger mode according to - * interrupt entry. - */ - flags = DEFAULT_FLAGS; - level = trigger(apic, pin, &flags); - if (level == 1) - apic_pin_trigger |= (1 << irq); - polarity(apic, pin, &flags, level); - } - - /* program the appropriate registers */ - if (apic != 0 || pin != irq) - printf("IOAPIC #%d intpin %d -> irq %d\n", - apic, pin, irq); - vector = NRSVIDT + irq; /* IDT vec */ - io_apic_write(apic, select, flags | vector); - io_apic_write(apic, select + 1, target); + io_apic_setup_intpin(apic, pin); } /* return GOOD status */ Index: sys/i386/i386/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.134 diff -u -r1.134 mp_machdep.c --- sys/i386/i386/mp_machdep.c 2001/01/12 08:24:25 1.134 +++ sys/i386/i386/mp_machdep.c 2001/01/17 22:02:09 @@ -1032,6 +1047,37 @@ } +static void +allocate_apic_irq(int intr) +{ + int apic; + int intpin; + int irq; + + if (io_apic_ints[intr].int_vector != 0xff) + return; /* Interrupt handler already assigned */ + + if (io_apic_ints[intr].int_type != 0 && + (io_apic_ints[intr].int_type != 3 || + (io_apic_ints[intr].dst_apic_id == IO_TO_ID(0) && + io_apic_ints[intr].dst_apic_int == 0))) + return; /* Not INT or ExtInt on != (0, 0) */ + + irq = 0; + while (irq < APIC_INTMAPSIZE && + int_to_apicintpin[irq].ioapic != -1) + irq++; + + if (irq >= APIC_INTMAPSIZE) + return; /* No free interrupt handlers */ + + apic = ID_TO_IO(io_apic_ints[intr].dst_apic_id); + intpin = io_apic_ints[intr].dst_apic_int; + + assign_apic_irq(apic, intpin, irq); + io_apic_setup_intpin(apic, intpin); +} + static void swap_apic_id(int apic, int oldid, int newid) @@ -1272,48 +1318,8 @@ io_apic_ints[x].dst_apic_int, int_vector); } - } - - /* Assign first set of interrupts to intpins on IOAPIC #0 */ - for (x = 0; x < nintrs; x++) { - int_vector = io_apic_ints[x].dst_apic_int; - if (int_vector < APIC_INTMAPSIZE && - io_apic_ints[x].dst_apic_id == IO_TO_ID(0) && - io_apic_ints[x].int_vector == 0xff && - int_to_apicintpin[int_vector].ioapic == -1 && - (io_apic_ints[x].int_type == 0 || - io_apic_ints[x].int_type == 3)) { - assign_apic_irq(0, - io_apic_ints[x].dst_apic_int, - int_vector); - } } - /* - * Assign interrupts for remaining intpins. - * Skip IOAPIC #0 intpin 0 if the type is ExtInt, since this indicates - * that an entry for ISA/EISA irq 0 exist, and a fallback to mixed mode - * due to 8254 interrupts not being delivered can reuse that low level - * interrupt handler. - */ - int_vector = 0; - while (int_vector < APIC_INTMAPSIZE && - int_to_apicintpin[int_vector].ioapic != -1) - int_vector++; - for (x = 0; x < nintrs && int_vector < APIC_INTMAPSIZE; x++) { - if ((io_apic_ints[x].int_type == 0 || - (io_apic_ints[x].int_type == 3 && - (io_apic_ints[x].dst_apic_id != IO_TO_ID(0) || - io_apic_ints[x].dst_apic_int != 0))) && - io_apic_ints[x].int_vector == 0xff) { - assign_apic_irq(ID_TO_IO(io_apic_ints[x].dst_apic_id), - io_apic_ints[x].dst_apic_int, - int_vector); - int_vector++; - while (int_vector < APIC_INTMAPSIZE && - int_to_apicintpin[int_vector].ioapic != -1) - int_vector++; - } - } + /* PCI interrupt assignment is deferred */ } @@ -1486,8 +1492,11 @@ if (INTTYPE(intr) == 0) { /* standard INT */ if (SRCBUSIRQ(intr) == isa_irq) { if (apic_int_is_bus_type(intr, ISA) || - apic_int_is_bus_type(intr, EISA)) + apic_int_is_bus_type(intr, EISA)) { + if (INTIRQ(intr) == 0xff) + return -1; /* unassigned */ return INTIRQ(intr); /* found */ + } } } } @@ -1513,8 +1522,13 @@ && (SRCBUSID(intr) == pciBus) && (SRCBUSDEVICE(intr) == pciDevice) && (SRCBUSLINE(intr) == pciInt)) /* a candidate IRQ */ - if (apic_int_is_bus_type(intr, PCI)) + if (apic_int_is_bus_type(intr, PCI)) { + if (INTIRQ(intr) == 0xff) + allocate_apic_irq(intr); + if (INTIRQ(intr) == 0xff) + return -1; /* unassigned */ return INTIRQ(intr); /* exact match */ + } return -1; /* NOT found */ } Index: sys/i386/include/smp.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/smp.h,v retrieving revision 1.62 diff -u -r1.62 smp.h --- sys/i386/include/smp.h 2000/12/06 01:04:02 1.62 +++ sys/i386/include/smp.h 2001/01/17 21:25:34 @@ -135,6 +135,7 @@ int apic_ipi __P((int, int, int)); int selected_apic_ipi __P((u_int, int, int)); int io_apic_setup __P((int)); +void io_apic_setup_intpin __P((int, int)); void io_apic_set_id __P((int, int)); int io_apic_get_id __P((int)); int ext_int_setup __P((int, int)); ----Next_Part(Wed_Jan_17_23:14:38_2001)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 14:47:53 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 93F7F37B402; Wed, 17 Jan 2001 14:47:35 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0HMlPK06185; Wed, 17 Jan 2001 14:47:31 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101172247.f0HMlPK06185@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tor.Egge@fast.no Cc: msmith@FreeBSD.ORG, jhb@FreeBSD.ORG, freebsd , freebsd-smp@FreeBSD.ORG Subject: Re: problems with smp on compaq 1600 In-Reply-To: <200101172218.XAA96703@midten.fast.no> Date: Wed, 17 Jan 2001 14:47:25 -0800 From: Peter Wemm Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tor.Egge@fast.no wrote: > > Actually, either mode *should* work with 4.x, since we pack intpins down > > based on their usage, not their pin number (Tor fixed this a while back). > > I've installed 4.2 on a ProFusion box with a single 64-pin APIC (the RAID > > controller was on pin 50-something). > > Not based on their usage, but on their presence in the MP table. > > The number of unique (IOAPIC id, intpin) tuples described in the MP > table must be 24 or lower for all interrupts to be properly delivered. > > One MP table for compaq 1600 seems to have 26 unique (IOPAIC id, > intpin) tuples, thus two interrupt routings in the MP table will be > silently ignored. A warning should probably be given. > > For FreeBSD 4.2-STABLE, NHWI and APIC_INTMAPSIZE can probably be > increased from 24 to 25 (since NSWI is 7). This is still below 26. > > A better approach is to defer PCI interrupt assignment until the > devices are probed (i.e. towards the usage based packing you > mentioned). A patch for -current is enclosed. FYI, I increased the limit to 32 on -current but have not committed the patch yet. It can easily go to 64 if it is worth it. This may not be as silly as it sounds since big iron server hardware often has lots of busses and apics. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 14:48:40 2001 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id ABF3E37B401; Wed, 17 Jan 2001 14:48:21 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id XAA97751; Wed, 17 Jan 2001 23:48:20 +0100 (CET) Message-Id: <200101172248.XAA97751@midten.fast.no> To: msmith@FreeBSD.ORG Cc: jhb@FreeBSD.ORG, freebsd@bugtracker.compusa.com, freebsd-smp@FreeBSD.ORG Subject: Re: problems with smp on compaq 1600 From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 17 Jan 2001 23:18:07 +0100" X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Wed_Jan_17_23:48:11_2001)--" Content-Transfer-Encoding: 7bit Date: Wed, 17 Jan 2001 23:48:17 +0100 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----Next_Part(Wed_Jan_17_23:48:11_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit I wrote: > A better approach is to defer PCI interrupt assignment until the > devices are probed (i.e. towards the usage based packing you > mentioned). A patch for -current is enclosed. That patch will fail if there is no ISA/EISA interrupt 0 entry in the MP table. The enclosed additional patch fixes that (assumes that the first patch has been applied). - Tor Egge ----Next_Part(Wed_Jan_17_23:48:11_2001)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit --- mp_machdep.c.orig Wed Jan 17 22:37:59 2001 +++ mp_machdep.c Wed Jan 17 22:39:07 2001 @@ -1304,6 +1304,18 @@ int_vector); } } + + /* Assign ExtInt entry if no ISA/EISA interrupt 0 entry */ + for (x = 0; x < nintrs; x++) { + if (io_apic_ints[x].dst_apic_int == 0 && + io_apic_ints[x].dst_apic_id == IO_TO_ID(0) && + io_apic_ints[x].int_vector == 0xff && + int_to_apicintpin[0].ioapic == -1 && + io_apic_ints[x].int_type == 3) { + assign_apic_irq(0, 0, 0); + break; + } + } /* PCI interrupt assignment is deferred */ } ----Next_Part(Wed_Jan_17_23:48:11_2001)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 15: 0:49 2001 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 8849F37B400; Wed, 17 Jan 2001 15:00:31 -0800 (PST) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id AAA98206; Thu, 18 Jan 2001 00:00:23 +0100 (CET) Message-Id: <200101172300.AAA98206@midten.fast.no> To: peter@netplex.com.au Cc: msmith@FreeBSD.ORG, jhb@FreeBSD.ORG, freebsd@bugtracker.compusa.com, freebsd-smp@FreeBSD.ORG Subject: Re: problems with smp on compaq 1600 From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 17 Jan 2001 14:47:25 -0800" References: <200101172247.f0HMlPK06185@mobile.wemm.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 18 Jan 2001 00:00:22 +0100 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > FYI, I increased the limit to 32 on -current but have not committed the > patch yet. It can easily go to 64 if it is worth it. This may not be as > silly as it sounds since big iron server hardware often has lots of busses > and apics. You did, in revision 1.4 of apic_ipl.h. But 4.2-STABLE still depends on spl*() which limits how much NHWI can be increased. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 16:19:23 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id D5C2337B404 for ; Wed, 17 Jan 2001 16:19:04 -0800 (PST) Received: (qmail 4698 invoked by uid 0); 18 Jan 2001 00:19:03 -0000 Received: from p3ee37c4f.dip.t-dialin.net (HELO 1xp133) (62.227.124.79) by mail.gmx.net (mail02) with SMTP; 18 Jan 2001 00:19:03 -0000 Message-ID: <00ad01c080e4$74016080$0400a8c0@1xp133> From: "Gregor Bittel" To: "FreeBSD-SMP-Mailinglist" Subject: Update: SMP-Mainboards-List. (Supermicro PIIIDR3) Date: Thu, 18 Jan 2001 01:20:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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 Hi, I want just tell you all, that this Board works fine under 4.1-Release, the kernel-settings should be taken from mptable - _with_ the Optional-Settings. Hereīs my config: === # 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=6 # number of busses options NAPIC=2 # number of IO APICs options NINTR=24 # number of INTs === -Gregor. >Iīve probed the >Supermicro-P3DR3, without any success on 4.1-Release, itīs >my brothers new Board). >So I decided to make a new List with all known working >SMP-Boards, who are running under FreeBSD, always updated >with the newest Boards and informations, and how to make it run. > >But - I still need informations, which boards are running, >a dmesg-output and mptable-output. > >I hope, this page should be sometime in future be a HCL >(HardwareCompatibilityList) with helpful informations about >running SMP-Boards under FreeBSD. >Actually, this site is still under development, and is under >http://www.bnv-bamberg.de/home/ba3294/smp/index.htm >available. > > >-Gregor. > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jan 17 23:39:30 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 7BAF337B404 for ; Wed, 17 Jan 2001 23:39:07 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0I7d6K10125 for ; Wed, 17 Jan 2001 23:39:07 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101180739.f0I7d6K10125@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: smp@freebsd.org Subject: DL360 *fun*.. Date: Wed, 17 Jan 2001 23:39:06 -0800 From: Peter Wemm Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Compaq have got some interesting hardware and software in these beasties. First of all, the DL360 that we have has got these cpus: APIC ID Version State Family Model Step Flags 0 0x10 BSP, usable 6 2 1 0x0381 0 0x10 AP, usable 6 8 6 0x383fbff One is clocked at 800MHz, and the other is at 866MHz !!!!! I was unaware that this was possible. But it sure is! This is a serverworks chipset based motherboard. And yes, they really are running at different speeds. So much for the theory about using the TSC for time measurement on the SMP kernel some day. I just thought I'd pass along that bit of info. The second "interesting" problem are the well known mptable bugs. Compaq have got the PIC->apic pin 0 (ExtINT) table entry at the *end* of the table. In the released roms, they have an off-by-one error in the table header that leads to the 'MP extended table HOSED!" message. The fixed rom they gave me has an interesting quirk.. the entries are now out of order! mptable(1) cannot deal with this and gets VERY VERY upset. I fixed mptable and a before-and-after is appended: BEFORE: ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f29c9 signature: 'PCMP' base table length: 356 version: 1.4 checksum: 0x1e OEM ID: 'COMPAQ ' Product ID: 'PROLIANT ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 36 (<<<< Here is where the off-by-one was) local APIC address: 0xfee00000 extended table length: 184 extended table checksum: 106 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x10 BSP, usable 6 2 1 0x0381 0 0x10 AP, usable 6 8 6 0x383fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 ISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 0 5:A 8 21 INT active-lo level 0 5:B 8 20 INT active-lo level 0 5:C 8 21 INT active-lo level 0 5:D 8 20 INT active-lo level 1 6:A 8 23 INT active-lo level 1 6:B 8 22 INT active-lo level 1 6:C 8 23 INT active-lo level 1 6:D 8 22 INT active-lo level 0 1:A 8 19 INT active-lo level 0 1:B 8 18 INT active-lo level 1 4:A 8 17 INT active-lo level 1 5:A 8 24 INT active-hi edge 9 1 8 1 INT active-hi edge 9 0 8 2 INT active-hi edge 9 3 8 3 INT active-hi edge 9 4 8 4 INT active-hi edge 9 5 8 5 INT active-hi edge 9 6 8 6 INT active-hi edge 9 7 8 7 INT active-hi edge 9 8 8 8 INT active-hi edge 9 9 8 9 INT active-hi edge 9 10 8 10 INT active-hi edge 9 11 8 11 INT active-hi edge 9 12 8 12 INT active-lo level 9 13 8 13 INT active-hi edge 9 14 8 14 INT active-hi edge 9 15 8 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 255 0 NMI conforms conforms 9 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! ------------------------------------------------------------------------------- Here is what we get after fixing mptable(1): AFTER: ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f29c9 signature: 'PCMP' base table length: 356 version: 1.4 checksum: 0x1e OEM ID: 'COMPAQ ' Product ID: 'PROLIANT ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 36 local APIC address: 0xfee00000 extended table length: 184 extended table checksum: 106 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x10 BSP, usable 6 2 1 0x0381 0 0x10 AP, usable 6 8 6 0x383fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 ISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 0 5:A 8 21 INT active-lo level 0 5:B 8 20 INT active-lo level 0 5:C 8 21 INT active-lo level 0 5:D 8 20 INT active-lo level 1 6:A 8 23 INT active-lo level 1 6:B 8 22 INT active-lo level 1 6:C 8 23 INT active-lo level 1 6:D 8 22 INT active-lo level 0 1:A 8 19 INT active-lo level 0 1:B 8 18 INT active-lo level 1 4:A 8 17 INT active-lo level 1 5:A 8 24 INT active-hi edge 9 1 8 1 INT active-hi edge 9 0 8 2 INT active-hi edge 9 3 8 3 INT active-hi edge 9 4 8 4 INT active-hi edge 9 5 8 5 INT active-hi edge 9 6 8 6 INT active-hi edge 9 7 8 7 INT active-hi edge 9 8 8 8 INT active-hi edge 9 9 8 9 INT active-hi edge 9 10 8 10 INT active-hi edge 9 11 8 11 INT active-hi edge 9 12 8 12 INT active-lo level 9 13 8 13 INT active-hi edge 9 14 8 14 INT active-hi edge 9 15 8 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 255 0 NMI conforms conforms 9 0 255 1 -- MPTABLE OUT OF ORDER! I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 8 0 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- System Address Space bus ID: 0 address type: I/O address address base: 0x0 address range: 0x3000 -- System Address Space bus ID: 0 address type: I/O address address base: 0x3080 address range: 0xcf80 .... much trimmed .... Note how we go from I/O Ints to Local ints and back to I/O Ints for the last PIC->apic daisy chain entry? -current hangs on this box right now. I will fix it, but I thought I'd pass along the good news about mptable(1). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jan 18 2: 8:11 2001 Delivered-To: freebsd-smp@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 51DE337B401 for ; Thu, 18 Jan 2001 02:07:53 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id DAA27753; Thu, 18 Jan 2001 03:02:55 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAUHaWl2; Thu Jan 18 03:02:53 2001 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id DAA03033; Thu, 18 Jan 2001 03:07:48 -0700 (MST) From: Terry Lambert Message-Id: <200101181007.DAA03033@usr08.primenet.com> Subject: Re: dual CPUs for OpenGL any good? To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Thu, 18 Jan 2001 10:07:48 +0000 (GMT) Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: <200101171453.PAA43156@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 17, 2001 03:53:35 PM X-Mailer: ELM [version 2.5 PL2] 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 > Sure, this is not a Windows NT group here but I know a lot > of expertise hanging around here: We have an application that runs > under NT and does a lot of OpenGL. CPU load is high. It's a single process, > probably single thread application. I'm wondering if I should invest > in CPUs or in Graphics accelerators (video card). > > Could a monolithic application benefit from multi CPU at all? In general, it depends on where you are spending time, and how you are profiling the application. The best profiling you could do would be to ask MSVC++ to add profiling hooks for all function entries. This would provide non-statistical (i.e. _real_) profiling data that would omit kernel wait time from your profiling data. It's pretty trivial to do this with tiny mods to the gprof code. Note: You only get entry data, so if you want entry and exit data, you have to diddle the stack; this is also pretty trivial, since you can diddle the return address, and the option to add the hooks also turns off tail call optimization (where if the last thing in the function being compiled is a call to another function, MSVC++ will JMP to the function instead of calling it; this works because all functions are assumed to be caller-pops). If you are spending time in user space, then you are pretty much lost, unless your "monolithic" application is pseudo-multithreaded (e.g. it uses timers at the same time it is running to do something "in the background", since timer outcalls actually run on any idle kernel thread in NT and 95/98/2000). > Could driver code run on a different CPU while the other CPU is running for > the application? Generally, this happens whether you want it to or not, but you don't get to lock it to a particular CPU, since it happens in the soft ISR code, which runs on a kernel thread. If your lower level driver is taking interrupts, it's probably locked to a single CPU for handing the hardware interrupts anyway, so your load balancing might be broken and actually work out worse, if you depend on hardware interrupt processing (this is the trick NT uses to use 4 CPUs to beat Linux/FreeBSD file serving). Probably your best bet is a GL-aware accelerator card, that will offload your driver (this is what Alfred recommended), but it won't do you any good if all you are ever doing is waiting for I/O from the card telling you it's done, or it's ready for the next set of commands for you to offload (at that point, it's really time to think about a faster card, or even just a slower card with a much better/more concurrent driver). You should really profile everything, and then eliminate the bottlenecks you can, based on the profiling results. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jan 18 10: 3:49 2001 Delivered-To: freebsd-smp@freebsd.org Received: from hedwig.internal.webtrends.com (unknown [206.58.83.57]) by hub.freebsd.org (Postfix) with ESMTP id B53B937B400 for ; Thu, 18 Jan 2001 10:03:30 -0800 (PST) Received: by HEDWIG.internal.webtrends.com with Internet Mail Service (5.5.2653.19) id ; Thu, 18 Jan 2001 10:03:01 -0800 Message-ID: <41B0A5BB45B9D311BB4700508B551D720146173B@mr-mcfeely.internal.webtrends.com> From: Dustin Harris To: "'freebsd-smp@freebsd.org'" Subject: RE: Compaq DL360 Revisited Date: Thu, 18 Jan 2001 10:01:25 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I finally do have my DL360 booting SMP. The fix was either using a stable snapshot from the 16th or using the compaq smartstart software to rebuild the machine as type "Linux OS" instead of "Other", which is what I had been using. I also have the trouble with my CD rom like others have reported, but I don't use the CD really after the install is complete and I'm too happy to have both cpu's working to really care :) --dustin -----Original Message----- From: Dustin Harris [mailto:dustinh@webtrends.com] Sent: Saturday, January 13, 2001 8:34 PM To: 'Mike Smith' Cc: 'freebsd-smp@freebsd.org' Subject: RE: Compaq DL360 Revisited I'm aware that Peter did fix the DL360 for most folks, but I appear to have a different problem. My current test platform is 4.2-RELEASE with Peter's patch applied. I've also attempted this with 4.2-STABLE from late last week which included the patch. You are correct though that I should pester Compaq some more... --dustin > -----Original Message----- > From: Mike Smith [mailto:msmith@freebsd.org] > Sent: Saturday, January 13, 2001 8:39 PM > To: Dustin Harris > Cc: 'freebsd-smp@freebsd.org' > Subject: Re: Compaq DL360 Revisited > > > > I've traced the problem to the following code in mp_machdep.c in the > > function start_ap: > > > > /* wait for pending status end */ > > while (lapic.icr_lo & APIC_DELSTAT_MASK) > > /* spin */ ; > > > > It appears that I just "spin". Any ideas? What else can I > do to help > > troubleshoot this? Thanks. > > The problem with the DL360 is actually a BIOS bug. You should pester > Compaq for an update (they are aware of the problem if you > get through to > the right people), or update to -STABLE on your box (where > Peter Wemm has > committed a workaround). > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > 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 Thu Jan 18 20:18:17 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mx1.colltech.com (ausproxy.colltech.com [208.229.236.19]) by hub.freebsd.org (Postfix) with ESMTP id 0CFF037B401 for ; Thu, 18 Jan 2001 20:17:49 -0800 (PST) Received: from mail2.colltech.com (mail2.colltech.com [208.229.236.41]) by mx1.colltech.com (8.9.3/8.9.3/not) with ESMTP id WAA03911 for ; Thu, 18 Jan 2001 22:17:43 -0600 Received: from colltech.com (05-138.024.popsite.net [66.19.0.138]) by mail2.colltech.com (8.9.3/8.9.3/not) with ESMTP id WAA31183 for ; Thu, 18 Jan 2001 22:17:38 -0600 Message-ID: <3A677B52.514F6E21@colltech.com> Date: Thu, 18 Jan 2001 23:25:07 +0000 From: Craig Christophel X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Subject: Toshiba M500D MP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a question about the system I am using, In the bios I have set the MP level to 1.4 and when I boot 4.2-RELEASE and 5.0-CURRENT 1/16/2001 I see in the mptable command that the MP level is shown at 1.1 and only one APIC shows up, Is this an Issue that I should take up with the manufacuturer to check if the system is really 1.4 compliant or are there some variables/functionality that I can tweak to get this to show correctly. My mptable is below as well as the dmesg and config file. Thanks for your help, Craig. ---- BEGIN MPTABLE ---- =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f5b30 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x80 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f1400 signature: 'PCMP' base table length: 332 version: 1.1 checksum: 0x6b OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 33 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 0x11 BSP, usable 6 8 3 0xfbff 1 0x11 AP, usable 6 8 3 0xfbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 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 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 10 2 10 INT conforms conforms 2 11 2 11 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 0 7:A 2 19 INT active-lo level 0 8:A 2 16 INT active-lo level 0 9:A 2 17 INT active-lo level 0 10:A 2 18 INT active-lo level 0 11:A 2 19 INT active-lo level 0 11:B 2 19 INT active-lo level 0 12:A 2 16 INT active-lo level 1 0:A 2 16 SMI active-lo edge 2 0 2 23 -- 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 ------------------------------------------------------------------------------- # 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=25 # number of INTs =============================================================================== ---- BEGIN DMESG ---- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #1: Thu Jan 18 00:54:11 GMT 2001 root@merlin.at.apt:/usr/src/sys/compile/MERLIN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (696.41-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 335478784 (327616K bytes) avail memory = 322285568 (314732K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc03d8000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 16 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd000-0xd01f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x5000-0x500f at device 7.3 on pci0 vx0: <3COM 3C595 Fast Etherlink III PCI> port 0xd400-0xd41f irq 16 at device 8.0 on pci0 utp/tx[*tx*] address 00:a0:24:71:da:22 vx0: driver is using old-style compatability shims ahc0: port 0xd800-0xd8ff mem 0xe3001000-0xe3001fff irq 17 at device 9.0 on pci0 aic7860: Single Channel A, SCSI Id=7, 3/255 SCBs ahc1: port 0xdc00-0xdcff mem 0xe3000000-0xe3000fff irq 18 at device 10.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: mem 0xe3002000-0xe3002fff irq 19 at device 11.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Pinnacle/Miro TV, Philips PAL I tuner. pci0: (vendor=0x109e, dev=0x0878) at 11.1 irq 19 pcm0: port 0xe000-0xe03f irq 16 at device 12.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 9787MB [19885/16/63] at ata0-master UDMA33 acd0: CD-RW <6X4X32> at ata1-master using WDMA2 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) da3 at ahc1 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) ---- BEGIN CONFIG ---- makeoptions COPTFLAGS="-O -pipe" machine i386 cpu I686_CPU ident MERLIN maxusers 64 options NMBCLUSTERS=4096 options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options PERFMON options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options EXT2FS options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device pcn # AMD Am79C79x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep #device fe0 at isa? port 0x300 # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # Xircom Ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet #soudn device pcm # AHA option options AHC_ALLOW_MEMIO #video capture device smbus device iicbus device iicbb device bktr options BKTR_GPIO_ACCESS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jan 19 5:28:36 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 5A37637B402 for ; Fri, 19 Jan 2001 05:28:18 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0JDQhk13579; Fri, 19 Jan 2001 05:28:08 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101191328.f0JDQhk13579@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Dustin Harris Cc: "'freebsd-smp@freebsd.org'" Subject: Re: Compaq DL360 Revisited In-Reply-To: <41B0A5BB45B9D311BB4700508B551D720146173B@mr-mcfeely.internal.webtrends.com> Date: Fri, 19 Jan 2001 05:26:43 -0800 From: Peter Wemm Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dustin Harris wrote: > I finally do have my DL360 booting SMP. The fix was either using a stable > snapshot from the 16th or using the compaq smartstart software to rebuild > the machine as type "Linux OS" instead of "Other", which is what I had been > using. I also have the trouble with my CD rom like others have reported, > but I don't use the CD really after the install is complete and I'm too > happy to have both cpu's working to really care :) The bug below is that the bios **disables** the local APICs unless you've selected an OS that the software knows is 'SMP aware'. Ie: if you have it on 'Other' or 'DOS' or 'UNIX' it will disable SMP. I was only able to get it eventually working when the OS was set to 'Windows NT' or 'Windows 2000' although I did not try them all. I have no trouble with RELENG_4 - but -current will not find the PCI bridges unless I have acpica active. There appears to be a problem with the pcibios stuff on this machine. Or maybe I should keep changing the OS type until I have checked them all.... :-] This wretched machine has nearly driven me mad. > --dustin > > -----Original Message----- > From: Dustin Harris [mailto:dustinh@webtrends.com] > Sent: Saturday, January 13, 2001 8:34 PM > To: 'Mike Smith' > Cc: 'freebsd-smp@freebsd.org' > Subject: RE: Compaq DL360 Revisited > > > I'm aware that Peter did fix the DL360 for most folks, but I appear to have > a different problem. My current test platform is 4.2-RELEASE with Peter's > patch applied. I've also attempted this with 4.2-STABLE from late last week > which included the patch. > > You are correct though that I should pester Compaq some more... > > --dustin > > > -----Original Message----- > > From: Mike Smith [mailto:msmith@freebsd.org] > > Sent: Saturday, January 13, 2001 8:39 PM > > To: Dustin Harris > > Cc: 'freebsd-smp@freebsd.org' > > Subject: Re: Compaq DL360 Revisited > > > > > > > I've traced the problem to the following code in mp_machdep.c in the > > > function start_ap: > > > > > > /* wait for pending status end */ > > > while (lapic.icr_lo & APIC_DELSTAT_MASK) > > > /* spin */ ; > > > > > > It appears that I just "spin". Any ideas? What else can I > > do to help > > > troubleshoot this? Thanks. > > > > The problem with the DL360 is actually a BIOS bug. You should pester > > Compaq for an update (they are aware of the problem if you > > get through to > > the right people), or update to -STABLE on your box (where > > Peter Wemm has > > committed a workaround). > > > > -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > > > > > > 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 > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jan 19 10:19:44 2001 Delivered-To: freebsd-smp@freebsd.org Received: from mass.osd.bsdi.com (unknown [169.237.8.127]) by hub.freebsd.org (Postfix) with ESMTP id D045A37B404 for ; Fri, 19 Jan 2001 10:19:22 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0JIY2W01141; Fri, 19 Jan 2001 10:34:02 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101191834.f0JIY2W01141@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Craig Christophel Cc: freebsd-smp@freebsd.org Subject: Re: Toshiba M500D MP In-reply-to: Your message of "Thu, 18 Jan 2001 23:25:07 GMT." <3A677B52.514F6E21@colltech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jan 2001 10:34:02 -0800 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In the bios I have set the MP level to 1.4 and when I boot > 4.2-RELEASE and 5.0-CURRENT 1/16/2001 I see in the mptable command that > the MP level is shown at 1.1 and only one APIC shows up, Is this an > Issue that I should take up with the manufacuturer to check if the > system is really 1.4 compliant or are there some variables/functionality > that I can tweak to get this to show correctly. My mptable is below as > well as the dmesg and config file. If the system works, ignore it. The APIC layout looks fine - there will only be one I/O APIC in this sytem. The MPS structure version is OK, though arguably a "bug". -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message