From owner-freebsd-stable Sun Jun 30 14:36:13 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19032 for stable-outgoing; Sun, 30 Jun 1996 14:36:13 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18950 for ; Sun, 30 Jun 1996 14:36:02 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.6.12) with SMTP id OAA00233 for ; Sun, 30 Jun 1996 14:44:43 -0700 (PDT) Date: Sun, 30 Jun 1996 14:44:42 -0700 (PDT) From: Tom Samplonius To: stable@freebsd.org Subject: Problem with 1542 and ZIP drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having problems accessing a ZIP drive under FreeBSD-stable, using a 1542 controller. As soon as I generate some significant disk activity, the following happens: Jun 30 14:40:22 misery /kernel: sd0(aha0:5:0): timed out Jun 30 14:40:22 misery /kernel: adapter not taking commands.. frozen?! Jun 30 14:40:22 misery /kernel: Debugger("aha1542") called. Jun 30 14:40:23 misery /kernel: AGAIN Jun 30 14:40:23 misery /kernel: aha0: MBO 02 and not 00 (free) Jun 30 14:40:32 misery /kernel: sd0(aha0:5:0): timed out Jun 30 14:40:32 misery /kernel: adapter not taking commands.. frozen?! Jun 30 14:40:32 misery /kernel: Debugger("aha1542") called. Jun 30 14:40:32 misery /kernel: Jun 30 14:40:36 misery /kernel: sd0(aha0:5:0): timed out Jun 30 14:40:36 misery /kernel: adapter not taking commands.. frozen?! Jun 30 14:40:36 misery /kernel: Debugger("aha1542") called. Jun 30 14:40:36 misery /kernel: AGAIN Jun 30 14:40:36 misery /kernel: aha0: MBO 02 and not 00 (free) Jun 30 14:40:46 misery /kernel: sd0(aha0:5:0): timed out Jun 30 14:40:46 misery /kernel: adapter not taking commands.. frozen?! Jun 30 14:40:46 misery /kernel: Debugger("aha1542") called. Jun 30 14:40:46 misery /kernel: Any idea of what this is caused by? The only way to get the drive to work at all after this, is to reboot the system. Tom