From owner-freebsd-smp Thu Jun 5 00:30:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00729 for smp-outgoing; Thu, 5 Jun 1997 00:30:01 -0700 (PDT) Received: from caleche.kecl.ntt.co.jp (elysium.kecl.ntt.co.jp [129.60.192.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA00701 for ; Thu, 5 Jun 1997 00:29:58 -0700 (PDT) Received: from localhost by caleche.kecl.ntt.co.jp (8.8.5/kecl2.0/r8v7-M2-nishio) with ESMTP id QAA00626; Thu, 5 Jun 1997 16:29:50 +0900 (JST) To: smp@freebsd.org Subject: bug with SMP_AUTOSTART? X-Mailer: Mew version 1.54 on Emacs 19.34.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19970605162949Y.nishio@elysium.kecl.ntt.co.jp> Date: Thu, 05 Jun 1997 16:29:49 +0900 From: NISHIO Shuichi X-Dispatcher: impost version 0.95+ (Nov. 26, 1996) Lines: 54 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. Some versions of SVR4 have a serious bug in the implementation of the mmap () system call in the kernel; this causes emacs to run correctly the first time, and then crash when run a second time. Contact your vendor and ask for the mmap bug fix; in the mean time, you may be able to work around the problem by adding a line to your operating system description file (whose name is reported by the configure script) that reads: #define SYSTEM_MALLOC This makes Emacs use memory less efficiently, but seems to work around the kernel bug. ---- end citation ---- 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. I'm running 3.0-current with the following hardwares: Tyan S1668ATX P6 200MHz(256K)x2 AHA-2940 x 1 AHA-2940U x 1 AHA-2940UW x 1 DEC DE-500AA x 2 Thank you for any advice, NISHIO Shuichi