From owner-freebsd-stable Wed Jun 26 04:58:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03956 for stable-outgoing; Wed, 26 Jun 1996 04:58:56 -0700 (PDT) Received: from solar.tlk.com (root@solar.tlk.com [194.97.84.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03945 for ; Wed, 26 Jun 1996 04:58:47 -0700 (PDT) Received: by solar.tlk.com id ; Wed, 26 Jun 96 13:58 MET DST Message-Id: From: torstenb@solar.tlk.com (Torsten Blum) Subject: Re: new vm code not working well To: tom@uniserve.com (Tom Samplonius) Date: Wed, 26 Jun 1996 13:58:13 +0200 (MET DST) Cc: jacs@gnome.co.uk, stable@freebsd.org In-Reply-To: from Tom Samplonius at "Jun 25, 96 03:39:56 pm" Reply-To: torstenb@tlk.com X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote: > > ncr0 rev 1 int a irq 14 on pci0:1 > > ncr0 waiting for scsi devices to settle > > (ncr0:0:0): "MICROP 1936-21MW1002002 HW0A" type 0 fixed SCSI 2 > > sd0(ncr0:0:0): Direct-Access > > sd0(ncr0:0:0): asynchronous. > > > > sd0(ncr0:0:0): ABORTED COMMAND asc:49,0 Invalid message error > > , retries:4 > > 2882MB (5903825 512 byte sectors) > > I would consider this a big problem. If your swap disk decides to go > south while swapping, your system is screwed. Why are you getting > "Invalid message error" messages? I had the same problem with the same Mircopolis drive. Since this drive has a 5 year warranty I send the drive to Mircopolis and they send me a replacement unit back. The new drive works fine. -tb