From owner-freebsd-stable Sun Oct 29 20:34:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pikachu.bsp.bc.niigata-u.ac.jp (pikachu.bsp.bc.niigata-u.ac.jp [133.35.85.2]) by hub.freebsd.org (Postfix) with SMTP id ECAC737B479 for <stable@FreeBSD.ORG>; Sun, 29 Oct 2000 20:34:17 -0800 (PST) Received: (qmail 1522 invoked by alias); 30 Oct 2000 13:34:02 +0900 Message-ID: <20001030043402.1512.qmail@pikachu.bsp.bc.niigata-u.ac.jp> To: stable@FreeBSD.ORG Subject: linprocfs causes system down and reboot X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) References: <20001028040054.23707.qmail@pikachu.bsp.bc.niigata-u.ac.jp> <86vgud61zd.wl@ringo.FromTo.Cc> <200010280502.e9S52tB14324@mail.airnet.ne.jp> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 30 Oct 2000 13:34:01 +0900 From: Mamoru Iwaki <iwaki@bc.niigata-u.ac.jp> X-Dispatcher: imput version 20000228(IM140) Lines: 33 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using linprocfs on 4.1.1-STABLE system, % cat /compat/linux/proc/stat or % cat /compat/linux/proc/uptime cause a panic with the following message Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc0933030 stack pointer = 0x10:0xc60dddc8 frame pointer = 0x10:0xc60dde20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 325 (cat) interrupt mask = none trap number = 18 panic: integer divide fault and then the system reboots immediately. At least, this problem has exist since 4.1.1-STABLE around 24 Oct., but around 17 Oct.. This is dangerous because every user can make system down easily. I heard that the CURRENT around 28 Oct. works good with the same operations, so this problem maybe exist only in 4.1.1-STABLE. --- ----- Mamoru IWAKI (iwaki@bc.niigata-u.ac.jp) Graduate School of Science and Technology, Niigata University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message