Subject: Re: Adaptec 2010S i2o + x86_64 doesn't work
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Markus.Lidel@shadowconnect.com
In-Reply-To: <1113581722.14421.15.camel@zahadum.xs4all.nl>
References: <20050413160352.GA12841@xs4all.net>
	 <1113576775.11116.17.camel@localhost.localdomain>
	 <1113581722.14421.15.camel@zahadum.xs4all.nl>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1113587286.11114.30.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Fri, 15 Apr 2005 18:48:09 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 892
Lines: 21

On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote:
> However, I removed 2 GB from the box as Alan sugggested and now the box
> comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back,
> and booted with the kernel "mem=2048" command line option - that also
> works, the i2o_block driver sees the adaptec controller just fine.
> 
> And I just booted it with "mem=3840M" and that works too.
> 
> So the problem appears to be 4 GB memory in 64 bit mode, on this box.

Or the driver is incorrectly handling 64/32bit DMA limit masks which
would be my first guess here, and would explain why it works on AMD
Athlon64 boxes.

Alan

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