linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Finch <A.Finch@lancaster.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Single P4, many IDE PCI cards == trouble??
Date: Wed, 22 Oct 2003 17:36:19 +0100	[thread overview]
Message-ID: <3F96B203.4060808@lancaster.ac.uk> (raw)


  For what it's worth, here is my experience. Hope it helps you, and 
anyone else searching for solutions to the problems I have encountered...


  Our New Server
  ==============

(+ Lessons learnt along the way)
   ++++++++++++++++++++++++++++++

Motherboard: Asus P4S8X-X

CPU:         Intel Pentium 4 2400MHz

Memory:     2 x 512Mb PC2700
  +was supposed to be 3x512Mb but the motherboard can't handle 3xPC2700
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Network:     3Com  3c905C-TX/TX-M [Tornado]

             Do NOT use the onboard LAN - performance is diabolical!
            ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Additional controller cards:

	   2xPromise Ultra133 Tx2 PCI-IDE cards
	   1xPromise Ultra66      PCI-IDE card

   Do note use 3 identical Promise IDE cards, either system will not
   +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  boot or there will be i/o errors!
  ++++++++++++++++++++++++++++

Disks
=====
  (In addition to system disk)

  10 x Maxtor 6Y060L0 60Gb
           attached to onboard ide and Promise Ultra133 cards
  4  x Maxtor 4A250J0 240Gb disk
           attached to Promise Ultra66 cards


Software:

  RedHat 9
  kernel  2.4.20

  Boot parameters modified as follows:

Edit  /boot/grub/menu.lst
and append
  ide2=noautotune ide3=noautotune ide4=noutotune ide5=noautotune
ide6=noautotune ide7=noautotune
to the line
  kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/

  this avoids errors of the type:
  ++++++++++++++++++++++++++++

  hdh: dma_intr: bad DMA status (dma_stat=75)

  when accessing the disks on the Promise cards
					
					
  Thereafter formatted disks/created raid arrays/started raid/made 
filesystem no problem.   Four 240Gb disks formatted as one big disk via 
raid0!
  (/dev/md8 Size=989GB)			
					
Tape drive: Spectra Logic 2000 (a.k.a. TreeFrog) attached via
              Adaptec AIC-7892A SCSI card
             Use mtx version 1.2.17rel to drive the robot, more recent
            versions cause problems (author informed).
					
			

  Alex Finch, Research Fellow, Physics Department, Lancaster University.

  NB ( I am not subscribed to the list so contact me directly for more
information)


             reply	other threads:[~2003-10-22 16:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 16:36 Alex Finch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-29  0:49 Single P4, many IDE PCI cards == trouble?? Nick Urbanik
2003-08-29  9:50 ` Alan Cox
2003-08-29 14:00   ` Nick Urbanik
2003-08-29 14:22     ` lk
2003-08-29 14:38     ` Alan Cox
2003-08-29 21:14       ` Erik Andersen
2003-08-30  3:46       ` Nick Urbanik
2003-09-08  6:13         ` Mike Fedyk
2003-09-08 17:20           ` Joel Jaeggli
2003-08-29 15:13     ` Valdis.Kletnieks
2003-08-31 12:43     ` Hans-Peter Jansen
2003-08-31 15:46       ` joe briggs
2003-08-31 23:41       ` Nick Urbanik
2003-09-06 12:44 ` Steve Bromwich

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=3F96B203.4060808@lancaster.ac.uk \
    --to=a.finch@lancaster.ac.uk \
    --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;
as well as URLs for NNTP newsgroup(s).