mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trevor-Hemsley@dial.pipex.com (Trevor Hemsley)
To: linux-kernel@vger.kernel.org
Subject: Re: Proliant hangs with 2.4 but works with 2.2.
Date: Mon, 19 Feb 2001 00:40:31	[thread overview]
Message-ID: <20010219004729Z129994-513+7797@vger.kernel.org> (raw)

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

             reply	other threads:[~2001-02-19  0:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19  0:40 Trevor Hemsley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-26 21:11 Arturas V
2001-12-26 22:49 ` Mr. James W. Laferriere
2001-12-27  0:35 ` Gérard Roudier
2001-02-19 17:29 lafanga lafanga
2001-02-19 14:39 lafanga lafanga
2001-02-19 16:17 ` Alan Cox
2001-02-19 10:35 lafanga lafanga
2001-02-19 11:37 ` Alan Cox
2001-02-19  0:04 lafanga lafanga
2001-02-18 23:08 lafanga lafanga
2001-02-18 23:57 ` Johannes Erdfelt
2001-02-19  1:53 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010219004729Z129994-513+7797@vger.kernel.org \
    --to=trevor-hemsley@dial.pipex.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®