Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 24 Sep 2002 03:34:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 24 Sep 2002 03:34:18 -0400 Received: from AMarseille-201-1-5-7.abo.wanadoo.fr ([217.128.250.7]:1904 "EHLO zion.wanadoo.fr") by vger.kernel.org with ESMTP id ; Tue, 24 Sep 2002 03:34:18 -0400 From: "Benjamin Herrenschmidt" To: "Justin T. Gibbs" , "Marcelo Tosatti" Cc: lkml Subject: Re: 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0 Date: Mon, 23 Sep 2002 09:15:42 +0200 Message-Id: <20020923071542.32214@192.168.4.1> In-Reply-To: <2632550816.1032817396@aslan.btc.adaptec.com> References: <2632550816.1032817396@aslan.btc.adaptec.com> X-Mailer: CTM PowerMail 4.0.1 carbon MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 921 Lines: 22 >No, it is not write posting. It is usually a problem with write >combining/merging and or read prefetch on devices that do not >support this feature. The memory BAR on the aic7xxx chips does >not have the PREFETCH bit set so these types of operations are >forbidden by the spec. The end result are missed writes and >state read data leading to all kinds of driver confusion. > >Often these issues are really register layout dependent. If >you never have to access two registers that are right next to >each other, the chipset can't write combine, etc. Ok, well. Indeed, adding a read on all writes may help here. Does this affect the performances significantly ? Ben. - 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/