To: linux-kernel@vger.kernel.org
From: Trevor-Hemsley@dial.pipex.com (Trevor Hemsley)
Date: Mon, 19 Feb 2001 00:40:31
Subject: Re: Proliant hangs with 2.4 but works with 2.2.
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Message-Id: <20010219004729Z129994-513+7797@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org

On Sun, 18 Feb 2001 23:09:17, "lafanga lafanga" <lafanga1@hotmail.com>
wrote:

> I have a Compaq Proliant 1600 server which can be hung on demand with all 
> the 2.4 series kernels I have tried (2.4, 2.4.1 & 2.4.2-pre3). Kernel 2.2.16 
> runs perfectly (from a default RH7.0).
> 
> I have ensured that the server meets the necessary requirements for the 2.4 
> kernels (modutils etc) and I have tried kgcc and various gcc versions. When 
> compiling I have tried default configs and also minimalist configs (with 
> only cpqarray and tlan). I have also ensured that I have the latest current 
> SmartStart CD (4.9) and have setup the firmware for installing Linux.

If you cat /proc/ioports does cpqarray show any registered ioports? I 
think it has a bug that means it doesn't request_region() for the 
ioports it uses and this means that any other driver that tries to 
auto-detect hardware by probing ports can stomp on its toes. This is 
certainly the case for EISA cpqarray controllers which is where I 
found this. I sent a report into arrays@compaq.com or whatever the 
address listed in the maintainers file is but haven't heard anything. 
This bug _may_ only exist for EISA controllers - I couldn't test the 
PCI version since the only machine I have with one in is running that 
other o/s.

-- 
Trevor Hemsley, Brighton, UK.
Trevor-Hemsley@dial.pipex.com
-
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/