From owner-freebsd-smp Sun Jun 8 05:43:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11393 for smp-outgoing; Sun, 8 Jun 1997 05:43:04 -0700 (PDT) Received: from mailout00.btx.dtag.de (mailout00.btx.dtag.de [194.25.2.148]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA11388 for ; Sun, 8 Jun 1997 05:43:00 -0700 (PDT) Received: from ermail03.btx.dtag.de ([172.16.35.4]) by mailout00.btx.dtag.de with smtp (S3.1.29.1) id ; Sun, 8 Jun 97 14:12 MET DST Received: by ermail03.btx.dtag.de with (S3.1.29.1) id ; Sun, 8 Jun 97 14:12 MET DST Date: Sun, 8 Jun 97 14:01 +0100 From: Sven.Kleese@t-online.de (Sven Kleese) X-Sender: 04069703201-0003@t-online.de (Sven Kleese) Subject: subscribe To: freebsd-smp@FreeBSD.org Message-Id: Sender: owner-smp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-smp Mon Jun 9 21:29:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA08106 for smp-outgoing; Mon, 9 Jun 1997 21:29:33 -0700 (PDT) Received: from mail.uni-muenster.de (MAIL.UNI-MUENSTER.DE [128.176.6.47]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA08087 for ; Mon, 9 Jun 1997 21:29:14 -0700 (PDT) Received: from PC_euleriv.uni-muenster.de (PPPE005.UNI-MUENSTER.DE [128.176.20.5]) by mail.uni-muenster.de (8.7.5/8.7.5) with SMTP id GAA101508 for ; Tue, 10 Jun 1997 06:28:41 +0200 Message-ID: Priority: Normal X-MSMail-Priority: Normal X-Priority: 3 To: freebsd-smp@FreeBSD.ORG MIME-Version: 1.0 From: "Volker Eulering" Date: Mon, 09 Jun 97 11:59:27 PDT Content-Type: text/plain; charset="ISO-8859-1"; X-MAPIextension=".TXT" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA08102 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-smp Tue Jun 10 20:20:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24817 for smp-outgoing; Tue, 10 Jun 1997 20:20:38 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24809; Tue, 10 Jun 1997 20:20:33 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id VAA22994; Tue, 10 Jun 1997 21:20:16 -0600 (MDT) Message-Id: <199706110320.VAA22994@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Jin Guojun[ITG]" cc: brian@mpress.com, hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB In-reply-to: Your message of "Tue, 10 Jun 1997 10:12:31 PDT." <199706101712.KAA24378@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Jun 1997 21:20:16 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > >> Has any one successfully installed FreeBSD on an ASUS P/I-P65UP5 dual Pentium > >> motherboard with C-P55T2D (two 200 MHz Pentium CPU) daughter board? > ... > The motherboards are OK. The problems are in the 3.0-SNAP. > I have filed a few bugs reports which cause kernel crash. > > One is the "dumps on wd0". is this an SMP specific problem? I had the same problem with SMP and "dumps on sd0", never tried it on UP. --- > The other one is weired, use NCR SCSI controllers, add two Quantum Fireball > 3.2 GB SCSI disk drives, the installation works fine. Adding three or more > such disk drives, installation boot process crashes before switch to the > Welcome FreeBSD menu. What I believe is that crashes at same place when > the "dumps on wd0" is used. So, they may be related problem. again, SMP specific? --- > Also, fopen/freopen failed on 3.0-SNAP in many cases. UP, SMP, both? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Tue Jun 10 20:31:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25468 for smp-outgoing; Tue, 10 Jun 1997 20:31:49 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25461 for ; Tue, 10 Jun 1997 20:31:38 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.5/8.7.3) id WAA12900; Tue, 10 Jun 1997 22:30:15 -0500 (CDT) Message-ID: <19970610223015.14169@luke.pmr.com> Date: Tue, 10 Jun 1997 22:30:15 -0500 From: Bob Willcox To: freebsd-smp@freebsd.org Subject: What 100mbps ethernet card(s) to use w/SMP? Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am having a difficult time coming up with an ethernet card that will work on my smp system. The closest I've gotten so far is with an Intel EtherExpress Pro/100B, which only works with UP kernels. With an SMP kernel I get persistent timeouts. The SMC 9332BDT gives similar results on an SMP kernel, but fails differently on a UP kernel. (Following probe at boot, all lights -- including the link integrity indicator -- go off and stay off. The card is completely dead.) The two 3Com cards I tried (3C905 and 3C595) both seemed to be working but pings to local (same 100mbps LAN) systems took almost 1 second and an rcp of a smallish file never completed (I killed it after 10 minutes). For both of these cards a boot-time message printed warning to turn off auto select with the cards DOS utility. Unfortunately, I was unable to get the utility that came with the card to run (the system in question does not have DOS installed on it and the utilities didn't seem to want to run from diskette :-() I can't believe that there are folks out there that are successfully running SMPs on 100mbps LANs. I just can't seem to make any headway on resolving this. System specifics: Hardware: ASUS P/I-P65UP5 w/C-P6ND. 2 150MHz PPro CPUs 64MB RAM ASUS PCI-SC875 (Symbios 53C875 SCSI controller) ASUS SC-200 (Symbios 53C810 SCSI controller) Matrox Melenium graphics adapter Software: FreeBSD-970527-SNAP at first. I then upgraded to FreeBSD-current (as early morning of 06/10). I certainly would appreciate any help you can give. Thanks, -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" From owner-freebsd-smp Tue Jun 10 21:05:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27065 for smp-outgoing; Tue, 10 Jun 1997 21:05:24 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27050 for ; Tue, 10 Jun 1997 21:05:15 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id WAA23218; Tue, 10 Jun 1997 22:03:55 -0600 (MDT) Message-Id: <199706110403.WAA23218@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Bob Willcox cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? In-reply-to: Your message of "Tue, 10 Jun 1997 22:30:15 CDT." <19970610223015.14169@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Jun 1997 22:03:55 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I am having a difficult time coming up with an ethernet card that > will work on my smp system. The closest I've gotten so far is with > an Intel EtherExpress Pro/100B, which only works with UP kernels. > With an SMP kernel I get persistent timeouts. The SMC 9332BDT > gives similar results on an SMP kernel, but fails differently on > a UP kernel. (Following probe at boot, all lights -- including > the link integrity indicator -- go off and stay off. The card is > completely dead.) > ... > I can't believe that there are folks out there that are successfully > running SMPs on 100mbps LANs. I just can't seem to make any headway > on resolving this. > > System specifics: > > Hardware: > ASUS P/I-P65UP5 w/C-P6ND. > 2 150MHz PPro CPUs > 64MB RAM > ASUS PCI-SC875 (Symbios 53C875 SCSI controller) > ASUS SC-200 (Symbios 53C810 SCSI controller) > Matrox Melenium graphics adapter > > Software: > FreeBSD-970527-SNAP at first. I then upgraded to FreeBSD-current > (as early morning of 06/10). I'm running intel 100/Pros @ 100 bps on 2 different P6 SMP boxes, plus 1 P5 SMP box. all talk to one another without complaint. send us an "mptable -dmesg" output, run immediately after booting the problamtic SMP kernel. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Tue Jun 10 22:45:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA02989 for smp-outgoing; Tue, 10 Jun 1997 22:45:24 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA02983 for ; Tue, 10 Jun 1997 22:45:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id WAA06165; Tue, 10 Jun 1997 22:47:04 -0700 (PDT) Message-Id: <199706110547.WAA06165@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Bob Willcox cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? In-reply-to: Your message of "Tue, 10 Jun 1997 22:30:15 CDT." <19970610223015.14169@luke.pmr.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 10 Jun 1997 22:47:04 -0700 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I am having a difficult time coming up with an ethernet card that >will work on my smp system. The closest I've gotten so far is with >an Intel EtherExpress Pro/100B, which only works with UP kernels. >With an SMP kernel I get persistent timeouts. The SMC 9332BDT >gives similar results on an SMP kernel, but fails differently on >a UP kernel. (Following probe at boot, all lights -- including >the link integrity indicator -- go off and stay off. The card is >completely dead.) > >The two 3Com cards I tried (3C905 and 3C595) both seemed to be >working but pings to local (same 100mbps LAN) systems took almost >1 second and an rcp of a smallish file never completed (I killed >it after 10 minutes). For both of these cards a boot-time message >printed warning to turn off auto select with the cards DOS utility. >Unfortunately, I was unable to get the utility that came with the >card to run (the system in question does not have DOS installed on >it and the utilities didn't seem to want to run from diskette :-() Interrupts simply aren't working correctly on your machine. It's not a problem with the cards you're plugging in, it's a problem with interrupt (perhaps APIC) configuration. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-smp Tue Jun 10 22:47:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA03011 for smp-outgoing; Tue, 10 Jun 1997 22:47:15 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA03006 for ; Tue, 10 Jun 1997 22:47:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id WAA06189; Tue, 10 Jun 1997 22:49:12 -0700 (PDT) Message-Id: <199706110549.WAA06189@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Bob Willcox cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? In-reply-to: Your message of "Tue, 10 Jun 1997 22:30:15 CDT." <19970610223015.14169@luke.pmr.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 10 Jun 1997 22:49:12 -0700 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Oh, one more thing: >I can't believe that there are folks out there that are successfully >running SMPs on 100mbps LANs. I just can't seem to make any headway >on resolving this. My dual P6/233 system here with Pro/100B is working fine in MP mode. It has to - I don't have a console on the machine at the moment and the only way I can get into it is over the ethernet. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-smp Wed Jun 11 01:50:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA10874 for smp-outgoing; Wed, 11 Jun 1997 01:50:43 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA10869 for ; Wed, 11 Jun 1997 01:50:39 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id PAA00639 for smp@freebsd.org; Wed, 11 Jun 1997 15:50:24 +0700 Received: by itfs.nsk.su; Wed, 11 Jun 97 16:01:10 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id PAA06786; Wed, 11 Jun 1997 15:36:32 +0700 (NSD) From: nnd@itfs.nsk.su To: smp@freebsd.org Subject: Any chance to use 586-bcopy on SMP ? Date: 11 Jun 1997 08:36:30 GMT Message-ID: <5nlo2e$69s@news.itfs.nsk.su> Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Current 3.0 kernel does'nt use Pentium-enchanced bcopy in case of SMP. I recall that it was connected with some problems in FPU usage in SMP case. Is it feasible to try it today ? On my Gateway GA-586DX with two P-133 famous dd if=/dev/zero of=/dev/null bs=1m count=100 shows ~56MB/s in SMP case vs. ~117MB/s in UP case ;-) N.Dudorov From owner-freebsd-smp Wed Jun 11 06:10:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21575 for smp-outgoing; Wed, 11 Jun 1997 06:10:11 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA21527 for ; Wed, 11 Jun 1997 06:10:00 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.5/8.7.3) id IAA00776; Wed, 11 Jun 1997 08:09:34 -0500 (CDT) Message-ID: <19970611080934.37800@luke.pmr.com> Date: Wed, 11 Jun 1997 08:09:34 -0500 From: Bob Willcox To: Steve Passe Cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? Reply-To: Bob Willcox References: <19970610223015.14169@luke.pmr.com> <199706110403.WAA23218@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: <199706110403.WAA23218@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Jun 10, 1997 at 10:03:55PM -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jun 10, 1997 at 10:03:55PM -0600, Steve Passe wrote: > Hi, > > > I am having a difficult time coming up with an ethernet card that > > will work on my smp system. The closest I've gotten so far is with > > an Intel EtherExpress Pro/100B, which only works with UP kernels. > > With an SMP kernel I get persistent timeouts. The SMC 9332BDT > > gives similar results on an SMP kernel, but fails differently on > > a UP kernel. (Following probe at boot, all lights -- including > > the link integrity indicator -- go off and stay off. The card is > > completely dead.) > > ... > > I can't believe that there are folks out there that are successfully > > running SMPs on 100mbps LANs. I just can't seem to make any headway > > on resolving this. > > > > System specifics: > > > > Hardware: > > ASUS P/I-P65UP5 w/C-P6ND. > > 2 150MHz PPro CPUs > > 64MB RAM > > ASUS PCI-SC875 (Symbios 53C875 SCSI controller) > > ASUS SC-200 (Symbios 53C810 SCSI controller) > > Matrox Melenium graphics adapter > > > > Software: > > FreeBSD-970527-SNAP at first. I then upgraded to FreeBSD-current > > (as early morning of 06/10). > > I'm running intel 100/Pros @ 100 bps on 2 different P6 SMP boxes, plus 1 P5 > SMP box. all talk to one another without complaint. > > send us an "mptable -dmesg" output, run immediately after booting the > problamtic SMP kernel. Ok, here it is: =============================================================================== MPTable, version 2.0.11 looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009f000 searching CMOS 'top of mem' @ 0x0009ec00 (635K) searching default 'top of mem' @ 0x0009fc00 (639K) searching BIOS @ 0x000f0000 MP FPS found in BIOS @ physical addr: 0x000f61b0 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f61b0 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x8d mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f5daa signature: 'PCMP' base table length: 244 version: 1.1 checksum: 0x29 OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 22 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 1 0x11 BSP, usable 6 1 2 0xfbff 0 0x11 AP, usable 6 1 2 0xfbff -- Bus: Bus ID Type 0 PCI 1 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID INT# ExtINT conforms conforms 1 0 2 0 INT conforms conforms 1 1 2 1 INT conforms conforms 1 0 2 2 INT conforms conforms 1 3 2 3 INT conforms conforms 1 4 2 4 INT conforms conforms 1 5 2 5 INT conforms conforms 1 6 2 6 INT conforms conforms 1 7 2 7 INT conforms conforms 1 8 2 8 INT conforms conforms 1 12 2 12 INT conforms conforms 1 14 2 14 INT active-lo level 1 11 2 16 INT active-lo level 1 10 2 17 INT active-lo level 1 9 2 18 INT active-lo level 1 15 2 19 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID INT# ExtINT active-hi edge 1 0 255 0 NMI active-hi edge 1 0 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Useful: #options SMP_AUTOSTART # start the additional CPUs during boot # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs # Currently broken: #options SMP_PRIVPAGES # BROKEN, DO NOT use! # Rogue hardware: # # Tyan Tomcat II: #options SMP_TIMER_NC # # # SuperMicro P6DNE: #options SMP_TIMER_NC # ------------------------------------------------------------------------------- dmesg output: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Wed Jun 11 06:59:24 CDT 1997 root@lando.pmr.com:/usr/src/sys/compile/LANDO-mp FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011 cpu1 (AP): apic id: 0, version: 0x00040011 io0 (APIC): apic id: 2, version: 0x00170011 CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x612 Stepping=2 Features=0xfbff real memory = 67108864 (65536K bytes) avail memory = 63676416 (62184K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.1.1 fxp0: rev 0x01 int a irq 9 on pci0.10.0 fxp0: Ethernet address 00:a0:c9:00:54:cd ncr0: rev 0x02 int a irq 10 on pci0.11.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 2047MB (4194058 512 byte sectors) cd0 at scbus0 target 4 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: asynchronous. can't get the size ncr1: rev 0x03 int a irq 11 on pci0.12.0 ncr1: waiting for scsi devices to settle scbus1 at ncr1 bus 0 sd1 at scbus1 target 0 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: WIDE SCSI (16 bit) enabled sd1: 20.0 MB/s (100 ns, offset 15) 2063MB (4226725 512 byte sectors) vga0: rev 0x01 int a irq 15 on pci0.13.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in matcdc0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface Enabled INTs: 1, 2, 3, 4, 6, 7, 8, 9, 10, 11, imen: 0x00fff021 SMP: All idle procs online. SMP: *** AUTO *** starting 1st AP! SMP: AP CPU #1 LAUNCHED!! Starting Scheduling... SMP: TADA! CPU #1 made it into the scheduler!. SMP: All 2 CPU's are online! fxp0: device timeout fxp0: device timeout fxp0: device timeout fxp0: device timeout fxp0: device timeout fxp0: device timeout =============================================================================== > > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD > -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" From owner-freebsd-smp Wed Jun 11 06:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21911 for smp-outgoing; Wed, 11 Jun 1997 06:14:41 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA21892 for ; Wed, 11 Jun 1997 06:14:31 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.5/8.7.3) id IAA00840; Wed, 11 Jun 1997 08:14:31 -0500 (CDT) Message-ID: <19970611081431.47921@luke.pmr.com> Date: Wed, 11 Jun 1997 08:14:31 -0500 From: Bob Willcox To: dg@root.com Cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? Reply-To: Bob Willcox References: <19970610223015.14169@luke.pmr.com> <199706110547.WAA06165@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: <199706110547.WAA06165@implode.root.com>; from David Greenman on Tue, Jun 10, 1997 at 10:47:04PM -0700 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jun 10, 1997 at 10:47:04PM -0700, David Greenman wrote: > > Interrupts simply aren't working correctly on your machine. It's not > a problem with the cards you're plugging in, it's a problem with interrupt > (perhaps APIC) configuration. Any idea why it would only effect the ethernet adapters and not the scsi adapters? Are there any BIOS setup things to check for that might cause this? > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" From owner-freebsd-smp Wed Jun 11 07:32:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26168 for smp-outgoing; Wed, 11 Jun 1997 07:32:08 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA26159; Wed, 11 Jun 1997 07:32:06 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id HAA18679; Wed, 11 Jun 1997 07:32:01 -0700 Date: Wed, 11 Jun 1997 07:32:01 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706111432.HAA18679@george.lbl.gov> To: smp@csn.net Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB Cc: brian@mpress.com, hardware@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk }> >> Has any one successfully installed FreeBSD on an ASUS P/I-P65UP5 dual Penti }um }> >> motherboard with C-P55T2D (two 200 MHz Pentium CPU) daughter board? }> ... }> The motherboards are OK. The problems are in the 3.0-SNAP. }> I have filed a few bugs reports which cause kernel crash. }> }> One is the "dumps on wd0". } }is this an SMP specific problem? I had the same problem with SMP and }"dumps on sd0", never tried it on UP. This is 3.0 specific problem at SMP mode. }--- }> The other one is weired, use NCR SCSI controllers, add two Quantum Fireball }> 3.2 GB SCSI disk drives, the installation works fine. Adding three or more }> such disk drives, installation boot process crashes before switch to the }> Welcome FreeBSD menu. What I believe is that crashes at same place when }> the "dumps on wd0" is used. So, they may be related problem. } }again, SMP specific? This is dual Pentium problem. It happenes on 2.2.2 and 3.0-SNAP. 2.2.1 and 2.1.7 works OK. }--- }> Also, fopen/freopen failed on 3.0-SNAP in many cases. } }UP, SMP, both? } 3.0 specific problem only. It is regardless # of CPUs or SMP. -Jin From owner-freebsd-smp Wed Jun 11 08:50:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA01032 for smp-outgoing; Wed, 11 Jun 1997 08:50:38 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01026 for ; Wed, 11 Jun 1997 08:50:33 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id KAA05815; Wed, 11 Jun 1997 10:49:43 -0500 (EST) From: "John S. Dyson" Message-Id: <199706111549.KAA05815@dyson.iquest.net> Subject: Re: What 100mbps ethernet card(s) to use w/SMP? In-Reply-To: <19970611081431.47921@luke.pmr.com> from Bob Willcox at "Jun 11, 97 08:14:31 am" To: bob@luke.pmr.com Date: Wed, 11 Jun 1997 10:49:43 -0500 (EST) Cc: dg@root.com, freebsd-smp@FreeBSD.ORG Reply-To: dyson@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-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, Jun 10, 1997 at 10:47:04PM -0700, David Greenman wrote: > > > > Interrupts simply aren't working correctly on your machine. It's not > > a problem with the cards you're plugging in, it's a problem with interrupt > > (perhaps APIC) configuration. > > Any idea why it would only effect the ethernet adapters and not the > scsi adapters? Are there any BIOS setup things to check for that > might cause this? > I had a really wierd networking problem on a new system last week at work. The system had an Intel ethernet adaptor, and was basically a typical PC. I had to reset the bios from scratch and things started working... I have NO idea as to what was going on, but two PCI devices were being mapped to the same IRQ before when the problem manifested itself. When the problem went away, all of the devices had seperate IRQs. John From owner-freebsd-smp Wed Jun 11 09:00:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01651 for smp-outgoing; Wed, 11 Jun 1997 09:00:51 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01636; Wed, 11 Jun 1997 09:00:14 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.5/8.7.3) id KAA01182; Wed, 11 Jun 1997 10:59:19 -0500 (CDT) Message-ID: <19970611105919.30843@luke.pmr.com> Date: Wed, 11 Jun 1997 10:59:19 -0500 From: Bob Willcox To: dyson@FreeBSD.ORG Cc: dg@root.com, freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? Reply-To: Bob Willcox References: <19970611081431.47921@luke.pmr.com> <199706111549.KAA05815@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: <199706111549.KAA05815@dyson.iquest.net>; from John S. Dyson on Wed, Jun 11, 1997 at 10:49:43AM -0500 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Jun 11, 1997 at 10:49:43AM -0500, John S. Dyson wrote: > > On Tue, Jun 10, 1997 at 10:47:04PM -0700, David Greenman wrote: > > > > > > Interrupts simply aren't working correctly on your machine. It's not > > > a problem with the cards you're plugging in, it's a problem with interrupt > > > (perhaps APIC) configuration. > > > > Any idea why it would only effect the ethernet adapters and not the > > scsi adapters? Are there any BIOS setup things to check for that > > might cause this? > > > I had a really wierd networking problem on a new system last week > at work. The system had an Intel ethernet adaptor, and was basically > a typical PC. I had to reset the bios from scratch and things started > working... I have NO idea as to what was going on, but two PCI devices > were being mapped to the same IRQ before when the problem manifested > itself. When the problem went away, all of the devices had seperate > IRQs. Well, I don't have any overlapping of IRQs on this system. (I am running another system with an Intel enet card, 2 3940's & an NCR 810 where the B channel of one of the 3940's is on the same IRQ (9) as the enet card that is working just fine (this a single Pentium 166MHz system running 2.2.2R). -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" From owner-freebsd-smp Wed Jun 11 10:01:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04398 for smp-outgoing; Wed, 11 Jun 1997 10:01:39 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04390 for ; Wed, 11 Jun 1997 10:01:31 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id LAA25474; Wed, 11 Jun 1997 11:00:14 -0600 (MDT) Message-Id: <199706111700.LAA25474@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Bob Willcox Cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? In-reply-to: Your message of "Wed, 11 Jun 1997 08:09:34 CDT." <19970611080934.37800@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Jun 1997 11:00:13 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > version: 1.1 the problem is the 1.1 MP setting. go into the BIOS setup and change it to 1.4. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Wed Jun 11 10:06:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04616 for smp-outgoing; Wed, 11 Jun 1997 10:06:08 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04598; Wed, 11 Jun 1997 10:05:45 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id LAA25497; Wed, 11 Jun 1997 11:05:27 -0600 (MDT) Message-Id: <199706111705.LAA25497@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Jin Guojun[ITG]" cc: smp@csn.net, brian@mpress.com, hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB In-reply-to: Your message of "Wed, 11 Jun 1997 07:32:01 PDT." <199706111432.HAA18679@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Jun 1997 11:05:26 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > }> >> Has any one successfully installed FreeBSD on an ASUS P/I-P65UP5 dual Penti > }um > }> >> motherboard with C-P55T2D (two 200 MHz Pentium CPU) daughter board? > } ... > }> The other one is weired, use NCR SCSI controllers, add two Quantum Fireball > }> 3.2 GB SCSI disk drives, the installation works fine. Adding three or more > }> such disk drives, installation boot process crashes before switch to the > }> Welcome FreeBSD menu. What I believe is that crashes at same place when > }> the "dumps on wd0" is used. So, they may be related problem. > } > }again, SMP specific? > > This is dual Pentium problem. It happenes on 2.2.2 and 3.0-SNAP. 2.2.1 and 2.1.7 > works OK. this can't be right, there is no SMP kernel for 2.2.2 -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Wed Jun 11 10:16:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05200 for smp-outgoing; Wed, 11 Jun 1997 10:16:53 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05195 for ; Wed, 11 Jun 1997 10:16:48 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.8.5/8.7.3) id MAA02177; Wed, 11 Jun 1997 12:16:14 -0500 (CDT) Message-ID: <19970611121614.59831@luke.pmr.com> Date: Wed, 11 Jun 1997 12:16:14 -0500 From: Bob Willcox To: Steve Passe Cc: freebsd-smp@FreeBSD.ORG Subject: Re: What 100mbps ethernet card(s) to use w/SMP? Reply-To: Bob Willcox References: <19970611080934.37800@luke.pmr.com> <199706111700.LAA25474@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: <199706111700.LAA25474@Ilsa.StevesCafe.com>; from Steve Passe on Wed, Jun 11, 1997 at 11:00:13AM -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Jun 11, 1997 at 11:00:13AM -0600, Steve Passe wrote: > Hi, > > > version: 1.1 > > the problem is the 1.1 MP setting. go into the BIOS setup and change it > to 1.4. Great! That was it! Thanks... -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" From owner-freebsd-smp Wed Jun 11 10:28:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05779 for smp-outgoing; Wed, 11 Jun 1997 10:28:37 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA05772; Wed, 11 Jun 1997 10:28:33 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id KAA24005; Wed, 11 Jun 1997 10:28:27 -0700 Date: Wed, 11 Jun 1997 10:28:27 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706111728.KAA24005@george.lbl.gov> To: smp@csn.net Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB Cc: brian@mpress.com, hardware@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk :> }> >> Has any one successfully installed FreeBSD on an ASUS P/I-P65UP5 dual Pe :nti :> }um :> }> >> motherboard with C-P55T2D (two 200 MHz Pentium CPU) daughter board? :> } ... :> }> The other one is weired, use NCR SCSI controllers, add two Quantum Fireball :> }> 3.2 GB SCSI disk drives, the installation works fine. Adding three or more :> }> such disk drives, installation boot process crashes before switch to the :> }> Welcome FreeBSD menu. What I believe is that crashes at same place when :> }> the "dumps on wd0" is used. So, they may be related problem. :> } :> }again, SMP specific? :> :> This is dual Pentium problem. It happenes on 2.2.2 and 3.0-SNAP. 2.2.1 and 2.1 :.7 :> works OK. : :this can't be right, there is no SMP kernel for 2.2.2 Did I say SMP problem? I said it is dual Pentium problem. Again, NOT SMP specific. The rest problems are. -Jin From owner-freebsd-smp Wed Jun 11 10:36:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06275 for smp-outgoing; Wed, 11 Jun 1997 10:36:08 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06270; Wed, 11 Jun 1997 10:36:04 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id LAA25671; Wed, 11 Jun 1997 11:35:48 -0600 (MDT) Message-Id: <199706111735.LAA25671@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Jin Guojun[ITG]" cc: brian@mpress.com, hardware@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB In-reply-to: Your message of "Wed, 11 Jun 1997 10:28:27 PDT." <199706111728.KAA24005@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Jun 1997 11:35:48 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > :> This is dual Pentium problem. It happenes on 2.2.2 and 3.0-SNAP. 2.2.1 and 2.1 > :.7 > :> works OK. > : > :this can't be right, there is no SMP kernel for 2.2.2 > > Did I say SMP problem? I said it is dual Pentium problem. > Again, NOT SMP specific. The rest problems are. thanx, just trying to clarify... about the fopen problem, any specific program demonstrate this? I would thing things would fall over left and right if fopen() had a problem. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Wed Jun 11 10:49:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06822 for smp-outgoing; Wed, 11 Jun 1997 10:49:22 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06806 for ; Wed, 11 Jun 1997 10:49:13 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id LAA25738; Wed, 11 Jun 1997 11:48:56 -0600 (MDT) Message-Id: <199706111748.LAA25738@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: nnd@itfs.nsk.su cc: smp@FreeBSD.ORG Subject: Re: Any chance to use 586-bcopy on SMP ? In-reply-to: Your message of "11 Jun 1997 08:36:30 GMT." <5nlo2e$69s@news.itfs.nsk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Jun 1997 11:48:56 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Current 3.0 kernel does'nt use Pentium-enchanced bcopy > in case of SMP. I recall that it was connected with some > problems in FPU usage in SMP case. Is it feasible to try it > today ? I'm not sure of the exact nature of this problem, can anyone give us a concise description of the probelm with using the FPU bcopy? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Wed Jun 11 11:00:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07250 for smp-outgoing; Wed, 11 Jun 1997 11:00:33 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07245; Wed, 11 Jun 1997 11:00:30 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id LAA25666; Wed, 11 Jun 1997 11:00:27 -0700 Date: Wed, 11 Jun 1997 11:00:27 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706111800.LAA25666@george.lbl.gov> To: smp@csn.net Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB (kern/3827) Cc: brian@mpress.com, bugs@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > about the fopen problem, any specific program demonstrate this? I would > thing things would fall over left and right if fopen() had a problem. It will not happen if the program is small. I am working on it right now. It has the similar symptom as using libc_r under 2.2.1. I am not sure they are related, but they happen when the program growing or some libraries linked. I'd like to fix these two problems A.S.A.P. I am going to spend most of my time diring next a couple of weeks to track down the problem, and/or fix it/them. If you or some one in FreeBSD team can help me or work with me on this fixing, it will be appreciated. Thanks, -Jin From owner-freebsd-smp Wed Jun 11 11:56:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10115 for smp-outgoing; Wed, 11 Jun 1997 11:56:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA10105; Wed, 11 Jun 1997 11:56:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06444; Wed, 11 Jun 1997 11:50:37 -0700 From: Terry Lambert Message-Id: <199706111850.LAA06444@phaeton.artisoft.com> Subject: Re: What 100mbps ethernet card(s) to use w/SMP? To: dyson@FreeBSD.ORG Date: Wed, 11 Jun 1997 11:50:37 -0700 (MST) Cc: bob@luke.pmr.com, dg@root.com, freebsd-smp@FreeBSD.ORG In-Reply-To: <199706111549.KAA05815@dyson.iquest.net> from "John S. Dyson" at Jun 11, 97 10:49:43 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Interrupts simply aren't working correctly on your machine. It's not > > > a problem with the cards you're plugging in, it's a problem with interrupt > > > (perhaps APIC) configuration. > > > > Any idea why it would only effect the ethernet adapters and not the > > scsi adapters? Are there any BIOS setup things to check for that > > might cause this? > > > I had a really wierd networking problem on a new system last week > at work. The system had an Intel ethernet adaptor, and was basically > a typical PC. I had to reset the bios from scratch and things started > working... I have NO idea as to what was going on, but two PCI devices > were being mapped to the same IRQ before when the problem manifested > itself. When the problem went away, all of the devices had seperate > IRQs. Shared PCI interrupts have problems working on some SMP boxes, and always have. The "5th slot" thing is a screwup because it forces sharing (the interrupt lines are typically grabbed in order in the slot, and with only 4 lines, you only have 4 linear orderings, so one of the slots has to duplicate one of the other slots). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-smp Wed Jun 11 14:07:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA17899 for smp-outgoing; Wed, 11 Jun 1997 14:07:08 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA17888; Wed, 11 Jun 1997 14:06:57 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-44.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA04177 (5.67b/IDA-1.5); Wed, 11 Jun 1997 23:05:38 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id XAA07108; Wed, 11 Jun 1997 23:05:21 +0200 (CEST) X-Face: " Date: Wed, 11 Jun 1997 23:05:20 +0200 From: Stefan Esser To: Terry Lambert Cc: stesin@gu.net, bob@luke.pmr.com, matt@3am-software.com, hackers@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Does SMC9332BDT work in 2.2.2R?? References: <19970610101445.26928@mi.uni-koeln.de> <199706101816.LAA02784@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706101816.LAA02784@phaeton.artisoft.com>; from Terry Lambert on Tue, Jun 10, 1997 at 11:16:14AM -0700 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 10, Terry Lambert wrote: > > Why should that cause ANY problems > > for a bus-master card in slot 5 ??? > > > > | It has to do with PCI interrupt sharing. > ********************* > > This was broken in SMP, and seems to have been broken in general > on integration of SMP into the main line source tree. Really ? Don't think so ... There are in fact SMP systems that work with shared PCI interrupts ... > In addition, the card itself might object to interrupt sharing. No. All PCI cards must support shared interrupts, and I have yet to find one that doesn't. (There were a few cards before PCI 2.0, that tried to fully emulate some ISA card and could be made to use edge-triggered interrupts, but even those use level interrupts by default ...) > Finally, does the video card claim a vertical retrace interrupt? > If not, does it do one anyway? If so, the way the poll does not > happen to detect the card responsible on a shared interrupt with > a single attach can also be a problem. All PCI drivers are required to have a test on *this* card being the source of the interrupt as the first action in the interrupt handler. A PCI driver that fails to do so is broken! If the driver does the right thing, then it doesn't matter whether there are retrace interrupts (well, they definitely would reduce system performance, but by less than 20%), and you should be able to see the interrupts in the "systat -vm" screen ... > I realize that the explanations other than the first one rely > on bogus PCI card hardware. Broken PCI card hardware or a driver problem ... But the card in question uses a known good Ethernet chip. If you exclude the possibility that this particular device is defective, then it must be something else ... Regards, STefan From owner-freebsd-smp Wed Jun 11 15:04:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19954 for smp-outgoing; Wed, 11 Jun 1997 15:04:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA19947; Wed, 11 Jun 1997 15:04:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA07206; Wed, 11 Jun 1997 14:57:47 -0700 From: Terry Lambert Message-Id: <199706112157.OAA07206@phaeton.artisoft.com> Subject: Re: Does SMC9332BDT work in 2.2.2R?? To: se@freebsd.org (Stefan Esser) Date: Wed, 11 Jun 1997 14:57:47 -0700 (MST) Cc: terry@lambert.org, stesin@gu.net, bob@luke.pmr.com, matt@3am-software.com, hackers@freebsd.org, smp@freebsd.org In-Reply-To: <19970611230520.22463@mi.uni-koeln.de> from "Stefan Esser" at Jun 11, 97 11:05:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This was broken in SMP, and seems to have been broken in general > > on integration of SMP into the main line source tree. > > Really ? Don't think so ... > There are in fact SMP systems that work with shared PCI interrupts ... This may just be a broken PCI BIOS, then. > > Finally, does the video card claim a vertical retrace interrupt? > > If not, does it do one anyway? If so, the way the poll does not > > happen to detect the card responsible on a shared interrupt with > > a single attach can also be a problem. > > All PCI drivers are required to have a test on *this* card being > the source of the interrupt as the first action in the interrupt > handler. A PCI driver that fails to do so is broken! Isn't this a PCI framework issue, where it should explicitly call a card routine or check a bit in a flag in the card data struct to see if it originated the interrupt? It seems to me that if the PCI driver wasn't written correctly, you'd want it to fail absolutely (so it got caught in the author's testing) instead of under conditions which might not be universal (ie: the authors machine might not exhibit the problem). This seems to be an interface design issue. ...On the other hand, if there is a standard PCI (not card-specific) way of polling to see who interrupted, then it shouldn't involve the driver at all (I don't think there is, given that we don't use the PCI BIOS, right? Seems to me that we need a "did_you_interrupt" entry point for the card instance for the driver to allow procedural polling, instead of calling the driver and expecting it to obey hidden interface assumptions). > If the driver does the right thing, then it doesn't matter whether > there are retrace interrupts (well, they definitely would reduce > system performance, but by less than 20%), and you should be able > to see the interrupts in the "systat -vm" screen ... It should be architecturally impossible for the driver to not do the right thing (ie: they don't fill out the "did_you_interrupt" function pointer in the device instance struct, and they get an error message on boot). This should be explicit in the DDI architecture for PCI devices, not implicit, IMO. > > I realize that the explanations other than the first one rely > > on bogus PCI card hardware. > > Broken PCI card hardware or a driver problem ... > But the card in question uses a known good Ethernet chip. If you > exclude the possibility that this particular device is defective, > then it must be something else ... Yes, I had totally discounted that idea. I thought he had said the card worked in a three PCI slot machine? I guess that still leaves PCI BIOS autodetection/card-mapping bugs. 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-smp Thu Jun 12 07:06:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA28446 for smp-outgoing; Thu, 12 Jun 1997 07:06:50 -0700 (PDT) Received: from sonne.darmstadt.gmd.de (sonne.darmstadt.gmd.de [141.12.62.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA28441 for ; Thu, 12 Jun 1997 07:06:40 -0700 (PDT) From: technik@darmstadt.gmd.de Received: from [141.12.61.25] (i2rh-mac25 [141.12.61.25]) by sonne.darmstadt.gmd.de (8.8.5/8.8.5) with SMTP id QAA03679 for ; Thu, 12 Jun 1997 16:06:28 +0200 (MET DST) X-Sender: technik@mailserver.darmstadt.gmd.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 12 Jun 1997 16:14:19 +0100 To: freebsd-smp@freebsd.org Subject: Infos about FreeBSD Multiprocessorversion. Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ************************************** Hello, I am interested in Infos about FreeBSD Multiprocessorversion. Thank you. Ulrich Ziem. From owner-freebsd-smp Thu Jun 12 09:21:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA05622 for smp-outgoing; Thu, 12 Jun 1997 09:21:35 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA05612 for ; Thu, 12 Jun 1997 09:21:23 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id KAA29318; Thu, 12 Jun 1997 10:21:03 -0600 (MDT) Message-Id: <199706121621.KAA29318@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: technik@darmstadt.gmd.de cc: freebsd-smp@FreeBSD.ORG Subject: Re: Infos about FreeBSD Multiprocessorversion. In-reply-to: Your message of "Thu, 12 Jun 1997 16:14:19 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Jun 1997 10:21:02 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I am interested in Infos about FreeBSD Multiprocessorversion. http://www.freebsd.org/~fsmp/SMP/SMP.html -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-smp Fri Jun 13 13:56:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA19421 for smp-outgoing; Fri, 13 Jun 1997 13:56:50 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA19413; Fri, 13 Jun 1997 13:56:46 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id NAA22863; Fri, 13 Jun 1997 13:56:40 -0700 Date: Fri, 13 Jun 1997 13:56:40 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706132056.NAA22863@george.lbl.gov> To: smp@csn.net Subject: Re: (kern/3827) : was ASUS P/I-P65UP5 with C-P55T2D Cc: bugs@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The problem has been narrowed to a very small program at below. It appears to happen at subroutine level. That is, the open/freopn works in main() program, but fails in subroutine. To replace the subroutine call at line 7 in main(), marked /* replace HERE */, with the body of openread() , then, program works. So, what can cause this problem? ---------------------------------------------- /* openread.c */ #include main(int argc, char **argv) { openread(argc > 1 ? argv[1] : "openread.c"); /* replace HERE */ } openread(char *fn) /* if put body below into main, then it works */ { FILE * fp = stdin; int c; if (!(fp=fopen(fn, "rb"))) exit(1); while( (c = fgetc(fp)) != EOF) fputc(c, stdout); if (!(fp=freopen(fn, "rb", stdin))) exit(2); while (fread(&c, sizeof(c), 1, fp) == 1) fwrite(&c, sizeof(c), 1, stdout); fclose(fp); } ------------------------------------------------ to load: cc -g openread.c -lc_r ------------------------------------------------ xxgdb can't trace this program, but gdb can. It hangs at _thread_sys_sigprocmask() call. Because I am not fimilar with thread_sys_calls(), would some one help me on solving it? Any information, hints, and comments are appreciated. thanks, -Jin ======================================= Below is the gdb tracing: gdb a.out GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (gdb) l 1 /* openread.c */ 2 3 #include 4 5 main(int argc, char **argv) 6 { 7 openread(argc > 1 ? argv[1] : "openread.c"); 8 } 9 10 openread(char *fn) (gdb) b 7 Breakpoint 1 at 0x1594: file openread.c, line 7. (gdb) run Starting program: /export/src/ccs-lib/tools/x11/tuner/FreeBSD/a.out Breakpoint 1, main (argc=1, argv=0xefbfda5c) at openread.c:7 7 openread(argc > 1 ? argv[1] : "openread.c"); (gdb) s openread (fn=0x1580 "openread.c") at openread.c:12 12 FILE * fp = stdin; (gdb) s 15 if (!(fp=fopen(fn, "rb"))) (gdb) s fopen (file=0x1580 "openread.c", mode=0x15b4 "rb") at /usr/src/lib/libc_r/../libc/stdio/fopen.c:57 57 if ((flags = __sflags(mode, &oflags)) == 0) (gdb) s __sflags (mode=0x15b4 "rb", optr=0xefbfda0c) at /usr/src/lib/libc_r/../libc/stdio/flags.c:63 63 switch (*mode++) { (gdb) s 66 ret = __SRD; (gdb) s 67 m = O_RDONLY; (gdb) s 68 o = 0; (gdb) s 69 break; (gdb) s 89 if (*mode == '+' || (*mode == 'b' && mode[1] == '+')) { (gdb) s 93 *optr = m | o; (gdb) s 95 } (gdb) s fopen (file=0x1580 "openread.c", mode=0x15b4 "rb") at /usr/src/lib/libc_r/../libc/stdio/fopen.c:59 59 if ((fp = __sfp()) == NULL) (gdb) s __sfp () at /usr/src/lib/libc_r/../libc/stdio/findfp.c:105 105 if (!__sdidinit) (gdb) s 106 __sinit(); (gdb) s __sinit () at /usr/src/lib/libc_r/../libc/stdio/findfp.c:173 173 __cleanup = _cleanup; /* conservative */ (gdb) s 174 __sdidinit = 1; (gdb) s 175 } (gdb) s __sfp () at /usr/src/lib/libc_r/../libc/stdio/findfp.c:107 107 for (g = &__sglue;; g = g->next) { (gdb) s 108 for (fp = g->iobs, n = g->niobs; --n >= 0; fp++) (gdb) s 109 if (fp->_flags == 0) (gdb) s 108 for (fp = g->iobs, n = g->niobs; --n >= 0; fp++) (gdb) s 109 if (fp->_flags == 0) (gdb) s 108 for (fp = g->iobs, n = g->niobs; --n >= 0; fp++) (gdb) s 109 if (fp->_flags == 0) (gdb) s 108 for (fp = g->iobs, n = g->niobs; --n >= 0; fp++) (gdb) s 111 if (g->next == NULL && (g->next = moreglue(NDYNAMIC)) == NULL) (gdb) s 107 for (g = &__sglue;; g = g->next) { (gdb) s 108 for (fp = g->iobs, n = g->niobs; --n >= 0; fp++) (gdb) s 109 if (fp->_flags == 0) (gdb) s 116 fp->_flags = 1; /* reserve this slot; caller sets real flags */ (gdb) s 117 fp->_p = NULL; /* no current pointer */ (gdb) s 118 fp->_w = 0; /* nothing to read or write */ (gdb) s 119 fp->_r = 0; (gdb) s 120 fp->_bf._base = NULL; /* no buffer */ (gdb) s 121 fp->_bf._size = 0; (gdb) s 122 fp->_lbfsize = 0; /* not line buffered */ (gdb) s 123 fp->_file = -1; /* no file */ (gdb) s 125 fp->_ub._base = NULL; /* no ungetc buffer */ (gdb) s 126 fp->_ub._size = 0; (gdb) s 127 fp->_lb._base = NULL; /* no line buffer */ (gdb) s 128 fp->_lb._size = 0; (gdb) s 130 } (gdb) s fopen (file=0x1580 "openread.c", mode=0x15b4 "rb") at /usr/src/lib/libc_r/../libc/stdio/fopen.c:61 61 if ((f = open(file, oflags, DEFFILEMODE)) < 0) { (gdb) s open (path=0x1580 "openread.c", flags=0) at /usr/src/lib/libc_r/uthread/uthread_open.c:45 45 int mode = 0; (gdb) s 50 _thread_kern_sig_block(&status); (gdb) s _thread_kern_sig_block (status=0xefbfd9ec) at /usr/src/lib/libc_r/uthread/uthread_kern.c:952 952 _thread_sys_sigprocmask(SIG_SETMASK, &sig_to_block, &oset); (gdb) s Hanging HERE !!! From owner-freebsd-smp Fri Jun 13 15:08:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23491 for smp-outgoing; Fri, 13 Jun 1997 15:08:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA23447; Fri, 13 Jun 1997 15:07:33 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA11667; Fri, 13 Jun 1997 14:59:37 -0700 From: Terry Lambert Message-Id: <199706132159.OAA11667@phaeton.artisoft.com> Subject: Re: (kern/3827) : was ASUS P/I-P65UP5 with C-P55T2D To: jin@george.lbl.gov (Jin Guojun[ITG]) Date: Fri, 13 Jun 1997 14:59:36 -0700 (MST) Cc: smp@csn.net, bugs@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199706132056.NAA22863@george.lbl.gov> from "Jin Guojun[ITG]" at Jun 13, 97 01:56:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The problem has been narrowed to a very small program at below. > It appears to happen at subroutine level. That is, the open/freopn works > in main() program, but fails in subroutine. To replace the subroutine call > at line 7 in main(), marked /* replace HERE */, with the body of openread() , > then, program works. So, what can cause this problem? [ ... ] It's looks like you are hanging in the threads scheduler. When you butil your libraries, did you rebuild everything from scratch? If not, that may be your problem. I know that main is "different" in threads, but I don't understand why a subroutine call would cause it to fail when it doesn't fail in main. What happens if you link it without the threaded libc? Does it run OK? (Do you have one? Or are you running the very recently changed stuff?). If it does, there is apparently a hidden stack dependency bug which is being triggered by your code. Check the wrappers for the functions called by the functions you call. It may be that freopen() is not a happy camper in general, on the basis of descriptor locks, and you are only lucking out in main() when it works. Another thig to try is to take stdio out of the equation. I suspect that it is an implementation assumption in stdio that is biting you; it may in fact be a scheduler race which gets drawn out when you go down. If it's a race, make the variables global; if it still fails, you should then be able to migrate the code in and out of the subroutine a tine at a time to localise the error (part of this will be to compile the libc(3) pieces yourself, and migrate their function boundries as well). Sorry I can't give you an "oh, #define FROBOZZ" type soloution. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-smp Fri Jun 13 15:30:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA24413 for smp-outgoing; Fri, 13 Jun 1997 15:30:33 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24312; Fri, 13 Jun 1997 15:29:55 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id PAA01177; Fri, 13 Jun 1997 15:29:51 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id PAA24417; Fri, 13 Jun 1997 15:26:20 -0700 Date: Fri, 13 Jun 1997 15:26:20 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706132226.PAA24417@george.lbl.gov> To: lambert.org!terry@agora.rdrop.com Subject: Re: (kern/3827) : was ASUS P/I-P65UP5 with C-P55T2D Cc: bugs@FreeBSD.ORG, smp@FreeBSD.ORG, smp@csn.net Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk }> The problem has been narrowed to a very small program at below. }> It appears to happen at subroutine level. That is, the open/freopn works }> in main() program, but fails in subroutine. To replace the subroutine call }> at line 7 in main(), marked /* replace HERE */, with the body of openread() , }> then, program works. So, what can cause this problem? } }[ ... ] } }It's looks like you are hanging in the threads scheduler. } }When you butil your libraries, did you rebuild everything from }scratch? If not, that may be your problem. I did not do anything with the libraries. They come with the 3.0-SNAP distribution. }I know that main is "different" in threads, but I don't understand }why a subroutine call would cause it to fail when it doesn't fail }in main. That is the strange part. Our most programs are not failure because they start fopen/freopen at main(), and the complicated programs are invoking the fopen/freopen in subroutines, which typically in threaded subroutines. So, at the beginning, I thought the hanging was related when the program growing in size. So, I wrote a small program -- openread -- in a main() style that works. Then, I tried to make it called from the program failed at fopen/freopen. This needs make openread() to be a subroutine. At this time, the simple program fails. So, it is not the program size issue. Since the openread.c is so small, the only thing I saw is fopen/freopen fails in subroutine. }What happens if you link it without the threaded libc? Does it }run OK? (Do you have one? Or are you running the very recently }changed stuff?). That is not the problem. The problem happens only linked to libc_r, which is defaulted to distribution of 3.0-xxx. Without -lc_r, everything is OK. }If it does, there is apparently a hidden stack dependency bug }which is being triggered by your code. Check the wrappers for }the functions called by the functions you call. It may be }that freopen() is not a happy camper in general, on the basis }of descriptor locks, and you are only lucking out in main() }when it works. } }Another thig to try is to take stdio out of the equation. I }suspect that it is an implementation assumption in stdio that }is biting you; it may in fact be a scheduler race which gets }drawn out when you go down. } }If it's a race, make the variables global; if it still fails, }you should then be able to migrate the code in and out of the }subroutine a tine at a time to localise the error (part of this }will be to compile the libc(3) pieces yourself, and migrate }their function boundries as well). } }Sorry I can't give you an "oh, #define FROBOZZ" type soloution. From owner-freebsd-smp Fri Jun 13 15:40:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA25308 for smp-outgoing; Fri, 13 Jun 1997 15:40:12 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA25170; Fri, 13 Jun 1997 15:39:35 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id PAA01659; Fri, 13 Jun 1997 15:39:26 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id PAA24591; Fri, 13 Jun 1997 15:36:07 -0700 Date: Fri, 13 Jun 1997 15:36:07 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706132236.PAA24591@george.lbl.gov> To: lambert.org!terry@agora.rdrop.com Subject: Re: (kern/3827) : was ASUS P/I-P65UP5 with C-P55T2D Cc: bugs@FreeBSD.ORG, smp@FreeBSD.ORG, smp@csn.net Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > When you butil your libraries, did you rebuild everything from > scratch? If not, that may be your problem. Just following the previous message, do you mean to build libc_r.a? I did this on 2.2.1 platform as manual page says: cd /usr/src/lib/libc_r make depend && make all && make install Is this correct? or I missed something? -Jin