Date: Tue, 2 Mar 2004 14:47:57 -0800
From: Andrew Morton <akpm@osdl.org>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org, Matthew Wilcox <willy@debian.org>
Subject: Re: 2.6.3-mm4 / 2.5 Gb memory / sym53c8xx_2 won't boot
Message-Id: <20040302144757.60a0630c.akpm@osdl.org>
In-Reply-To: <20040302185518.GA2886@middle.of.nowhere>
References: <20040302185518.GA2886@middle.of.nowhere>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1268
Lines: 38

Jurriaan <thunder7@xs4all.nl> wrote:
>
> After upgrading my memory from 1 Gb to 2.5 Gb my 2.6.3-mm4 kernel
> wouldn't boot anymore.
> 
> It hang when detecting the scsi-chip.
> I had in my .config:
> 
> CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
> 
> the default value.
> 
> The scsi bus kept resetting before detecting any devices. Interestingly,
> 2.6.3-mm1 did boot with that .config setting. Once I recompiled
> 2.6.3-mm4 with 
> 
> CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
> 
> it booted (and worked) fine.
> 
> So, something regressed in 2.6.3-mm4 versus 2.6.3-mm1, so the default
> setting didn't work correctly anymore.

I don't know what caused this - there are a few patches in there which
touch the DMA and BIO highmem areas.  Plus always the latest scsi
development tree.

> If there is anything I can test, please let me know.

Could you test Linus's current tree?  The first link at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/.

If this bug hasn't hit Linus's tree yet, it will soon do so...
-
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/