From owner-freebsd-current Mon Feb 16 20:42:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25276 for freebsd-current-outgoing; Mon, 16 Feb 1998 20:42:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25271 for ; Mon, 16 Feb 1998 20:42:30 -0800 (PST) (envelope-from kingson@geocities.com) Received: from kingson-pc.atext.com (kingson-pc [204.62.245.181]) by kaos.atext.com (8.8.5/8.8.5) with SMTP id UAA21118 for ; Mon, 16 Feb 1998 20:41:56 -0800 (PST) Message-Id: <3.0.32.19691231160000.007b78b0@mailhost.atext.com> X-Sender: kingson@mailhost.atext.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 16 Feb 1998 20:42:47 -0800 To: freebsd-current@FreeBSD.ORG From: Kingson Gunawan Subject: kernel panic on smp system Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need help with kernel 971022 and 980208 SNAPS... The config: dual P2/266 (Tyan m/b) 512MB Ram Adaptec 2940UW 4 SCSI 4GB IBM drives Intel EtherExpress Pro 100B Kernel config: smp, ccd I keep getting this message (system freezes, only a reset button could help)... panic: rslock: cpu: 0, addr: 0xf020ead0, lock: 0x00000001 mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 boot() called on cpu#0 Very reproducible, the processes before the crash: a. 4 nfs remote mount processes (mostly readings). b. 250 perl5 processes that connect to gdbm files (in the ccd volume) and continuous open/close of tcp sockets. The memory and cpu are not too heavily pounded (the perl processes sleep most of the time). Other system resources do not seem to be pounded that bad either. Any idea? Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message