From owner-freebsd-smp Thu Jun 5 10:58:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27526 for smp-outgoing; Thu, 5 Jun 1997 10:58:57 -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 KAA27518 for ; Thu, 5 Jun 1997 10:58:52 -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 LAA27587; Thu, 5 Jun 1997 11:58:02 -0600 (MDT) Message-Id: <199706051758.LAA27587@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: NISHIO Shuichi cc: smp@FreeBSD.ORG Subject: Re: bug with SMP_AUTOSTART? In-reply-to: Your message of "Thu, 05 Jun 1997 16:29:49 +0900." <19970605162949Y.nishio@elysium.kecl.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jun 1997 11:58:02 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Hello, > > Yesterday I found that kernels with SMP_AUTOSTART shows wierd > behavior. > > When I try to run Mule-2.3@19.34 (a multi-lingual variant of emacs > 19.34), it works for 2-3 invocation after reboot. Afterwards, it > won't run, just dumps a core. This situation is somewhat similar to > the following description from emacs-19.34's "PROBLEMS" file. > > ---- begin citation ---- > * After running emacs once, subsequent invocations crash. > ... > ---- end citation ---- It might be a mmap issue, but your the first user to report this problem... --- > The worst thing is, that once felt into this core-dumping situation, > disk accesses seems to be corrupted: if I 'cat' a file, it shows > wrong contents, with binaries. If I tried 'cat'ing the same file > several times, it shows different contents every time. > This files are actually not corrupted, and after rebooting, > it shows up normally. > > Using a kernel without SMP_AUTOSTART, and doing > 'sysctl -w kern.smp_active=2' seems to work fine (well, I tried to run > 100 Mules at once, and the system went panic, but this probably is > an another issue). > > The same thing can be seen with every kernels from 8/May to Yesterday. did it work properly b4 may 8? (or was that just the first time you started using SMP_AUTOSTART?) -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD