From owner-aic7xxx Thu Dec 4 03:54:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA14966 for aic7xxx-outgoing; Thu, 4 Dec 1997 03:54:33 -0800 (PST) (envelope-from owner-aic7xxx) Received: from vrtx.co.uk (vr1-workhorse1.vrtx.net [195.224.63.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14950 for ; Thu, 4 Dec 1997 03:54:24 -0800 (PST) (envelope-from james@vrtx.net) Received: from localhost (james@localhost) by vrtx.co.uk (8.8.5/8.7.3) with SMTP id LAA03161 for ; Thu, 4 Dec 1997 11:53:47 GMT Date: Thu, 4 Dec 1997 11:53:47 +0000 (GMT) From: A James Lewis To: aic7xxx@FreeBSD.ORG Subject: Re: kernel stack corruption...aiee... In-Reply-To: <199712041000.CAA00530@shell.wco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have bios 1.21 and am also having problems, continuous SCB retries and errors on kernels 31 and 32 but only when my scanner is connected James On Thu, 4 Dec 1997, Tanvir Hassan wrote: > I have a 2940AU with 1.21 bios. I just got the Slackware 3.3 Linux and when > I installed it I got constant kernel stack corruption errors. So I went > to the web to download other kernels to see if I could get an older more > stable kernel so I could build a newer kernel. Well, ALL of them get > the kernel stack corruption! > > I saw in a newsgroup that other people in the aic7xxx linux realm have gotten > these stack corruptions, so I assume it is a buggy scsi driver. I noticed > that there have been several bug fixes (off by 1 memory overwrite, serious > memory overwrite problems in aic7xxx_proc.c, etc) to the 2.0.32 kernel > but I cannot build because my kernel has stack corruptions and cannot > build itself (Help! I've fallen and I can't "make zImage"! :-). > > Where can I get a 2.0.32 kernel that might fix my problem? Or are the > bug fixes a red herring and I have more serious problems in my computer? > > TIA > > -- > Tanvir > James Vortex Internet 20 years ago, people were switching from UNIX to VMS... Now, everybody is switching from UNIX to Windows NT... Am I the only one who sees what is happening here?