Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Aug 2002 10:24:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Aug 2002 10:24:17 -0400 Received: from pc2-cwma1-5-cust12.swa.cable.ntl.com ([80.5.121.12]:33531 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Tue, 20 Aug 2002 10:24:16 -0400 Subject: Re: hpt374 / BUG(); From: Alan Cox To: jools Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 20 Aug 2002 15:28:51 +0100 Message-Id: <1029853731.22982.28.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 859 Lines: 19 On Tue, 2002-08-20 at 15:10, jools wrote: > I'm using a RocketRAID 404 (hpt374) and a Asus A7v266. > When trying to boot from a 'htp374-enabled' kernel like 2.4.19-ac4 or > 2.4.20-pre2-ac4, i keep getting kernel panic at hpt366.c:1393. > Does anyone know why this happens, or what I might do to correct this > problem? I have tried every patch I can find for the 2.4 kernel. Its hitting a setup check for later chips when it finds them on a 66MHz PCI bus slot. At that point the current code aborts because the 66MHz tables for the HPT374 haven't been verified yet. The status on that bit is an Andre question - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/