From owner-aic7xxx Tue Oct 20 08:59:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00167 for aic7xxx-outgoing; Tue, 20 Oct 1998 08:59:12 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from smtp1.andrew.cmu.edu (SMTP1.ANDREW.CMU.EDU [128.2.10.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00143 for ; Tue, 20 Oct 1998 08:59:03 -0700 (PDT) (envelope-from gobbel@andrew.cmu.edu) Received: from gigan (CREAMOFWHEAT-25.SLIP.ANDREW.CMU.EDU [128.2.120.25]) by smtp1.andrew.cmu.edu (8.8.5/8.8.2) with SMTP id LAA17538; Tue, 20 Oct 1998 11:58:35 -0400 (EDT) Date: Tue, 20 Oct 1998 11:58:35 -0400 (EDT) From: Randy Gobbel Reply-To: Randy Gobbel Subject: Endianness?? problem in 2.1.125 kernel To: aic7xxx@FreeBSD.ORG cc: Randy Gobbel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just ran across a message to the LinuxPPC list from someone who is unable to boot due to sequencer RAM parity errors in a 2.1.125 kernel. I ran into the same problem a week ago or so. I managed to locate the assembler for the sequencer code (where has it gone?) and rebuilt the sequencer file, and somewhere in all my gyrations the problem went away. It seems to me this might be an endianness problem--though I don't see how, given that the sequencer code is supplied in a C source file--but in any case, I thought I should at least mention it. Sorry about the lack of detail. I'm not sure how to reproduce this problem, but it struck me as significant that another PowerPC Linux user had run into the same problem that I encountered. -Randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-aic7xxx" in the body of the message