Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S284264AbSAZNFn>; Sat, 26 Jan 2002 08:05:43 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S284717AbSAZNF0>; Sat, 26 Jan 2002 08:05:26 -0500
Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:6134 "EHLO
	host140.cambridge.redhat.com") by vger.kernel.org with ESMTP
	id <S284264AbSAZNFN>; Sat, 26 Jan 2002 08:05:13 -0500
Date: Sat, 26 Jan 2002 13:05:12 +0000 (GMT)
From: Bernd Schmidt <bernds@redhat.com>
X-X-Sender: <bernds@host140.cambridge.redhat.com>
To: <linux-kernel@vger.kernel.org>
Subject: Panic on boot with 2.4.18pre3ac1
Message-ID: <Pine.LNX.4.33.0201261258460.15848-100000@host140.cambridge.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

About every second time I try to boot 2.4.18pre3ac1, the kernel panics
while trying to detect the SCSI hardware.  There's lots of debugging output
which I have't copied to paper, but there's the following messages:

Scratch or SCB Memory Parity Error
[...]
Attempting to queue an ABORT message
[...]
Kernel panic: Loop 1

This did not happen with earlier kernels (I've been using 2.4.10ac10 mostly,
but 2.4.15 didn't seem to have the problem either).


Bernd

-
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/