From owner-freebsd-alpha Fri Nov 10 11:16:45 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A21AE37B4C5; Fri, 10 Nov 2000 11:16:43 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA08566; Fri, 10 Nov 2000 14:16:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAAJGgV22235; Fri, 10 Nov 2000 14:16:42 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 10 Nov 2000 14:16:42 -0500 (EST) To: mjacob@feral.com Cc: John Baldwin , alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? In-Reply-To: References: <14860.13678.594397.310814@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14860.18701.572533.296722@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > 'ata' timeouts occur with abandon during probing PC164 or on XP1000. Does the ata device ever recover? Neither if_fxp or if_dc ever recover. After the first timeout, they're gone for good. This makes me think its some fundimental problem, like leaving an interrupt disabled or something. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message