From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261334AbTDHMYV (for ); Tue, 8 Apr 2003 08:24:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261335AbTDHMYU (for ); Tue, 8 Apr 2003 08:24:20 -0400 Received: from deviant.impure.org.uk ([195.82.120.238]:25837 "EHLO deviant.impure.org.uk") by vger.kernel.org with ESMTP id S261334AbTDHMYT (for ); Tue, 8 Apr 2003 08:24:19 -0400 Date: Tue, 8 Apr 2003 13:35:08 +0100 From: Dave Jones To: Andre Hedrick Cc: Alan Cox , Nick Urbanik , Linux Kernel Mailing List Subject: Re: Debugging hard lockups (hardware?) Message-ID: <20030408123501.GA30244@suse.de> Mail-Followup-To: Dave Jones , Andre Hedrick , Alan Cox , Nick Urbanik , Linux Kernel Mailing List References: <20030406203145.GA5783@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 07, 2003 at 08:33:12PM -0700, Andre Hedrick wrote: > That controller is perfectly fine, give it a swing in 2.4 and it rocks. > 2.5 is the problem not the hardware. Exactly the same problem in 2.4. Your words on this subject previously.. "Get over it, you have a hardware problem period! I have drives that do this every time." So which is it ? It does this with every drive I've tried with it, so I'm incredibly sceptical theres a problem with the drives, especially when they work 100% fine on other controllers. Dave