From owner-freebsd-hardware Sun Sep 13 14:46:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07571 for freebsd-hardware-outgoing; Sun, 13 Sep 1998 14:46:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07555 for ; Sun, 13 Sep 1998 14:45:59 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id XAA26382 for ; Sun, 13 Sep 1998 23:45:43 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id XAA09324 for ; Sun, 13 Sep 1998 23:45:42 +0200 (MET DST) Received: (qmail 24862 invoked by uid 666); 13 Sep 1998 21:46:03 -0000 Message-ID: <19980913234603.A24841@hal.mpn.cp.philips.com> Date: Sun, 13 Sep 1998 23:46:03 +0200 From: Jos Backus To: hardware@FreeBSD.ORG Subject: Re: Buslogic/Mylex HAs References: <19980913174350.C23834@hal.mpn.cp.philips.com> <199809131736.LAA05042@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809131736.LAA05042@panzer.plutotech.com>; from Kenneth D. Merry on Sun, Sep 13, 1998 at 11:36:21AM -0600 X-Files: The Truth is out there! Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 13, 1998 at 11:36:21AM -0600, Kenneth D. Merry wrote: > That's not good. Did you send anything to the SCSI list about this? I > don't remember seeing anything said about it. No, I didn't. This is a system we need at work to burn CD's. At first we suspected some interaction with NFS so we took NFS out of the kernel, but the problem persisted. In the end we decided to do a reinstall using the 2.2.7-RELEASE CD-ROM, because we need this system to work. So unfortunately I'm no longer able to reproduce the problem :-( Side note: we tried to coerce the system into producing a core dump using dumpon, without success. We did get it to panic into ddb though. Wish I had written down the call stack /me slaps forehead <*thwap*> > I've seen panics on -stable and -current with cdda2wav; they seem to be > related to shared memory usage. It'll probably take someone more familiar > with the VM system to sort them out, though. The problem doesn't seem to > be directly attributable to CAM, but it my be exacerbated by CAM. This problem (at least this panic) isn't particularly new, it would seem; the archives show messages referring to it dating back as far as 1995. So purely intuitively, without being hampered by any relevant knowledge on this topic, I tend to agree ;-) > It looks like cdrecord uses shared memory as well, so the panic may be > similar. Can you send me a stack trace? Sorry :-( Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message