All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff Nguyen" <jeff@aslab.com>
To: "Trent Piepho" <xyzzy@speakeasy.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <jim@rubylane.com>, <linux-kernel@vger.kernel.org>,
	<linux-raid@vger.kernel.org>
Subject: Re: Update on Promise 100TX2 + Serverworks IDE issues -- 2.2.20
Date: Tue, 2 Apr 2002 18:08:44 -0800	[thread overview]
Message-ID: <15b401c1dab4$7bf2c240$6502a8c0@jeff> (raw)
In-Reply-To: <E16sZPj-0002vm-00@the-village.bc.nu>

There are ATAPI devices using UDMA25 such as HP 9300i. These UDMA25
devices are the problem maker on OSB4. Unless DMA is disabled, the system
will lock up when accessing the drive.

If you have UDMA33 ATAPI devices, they work great in OSB4.

Jeff

----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Trent Piepho" <xyzzy@speakeasy.org>
Cc: <jim@rubylane.com>; <linux-kernel@vger.kernel.org>;
<linux-raid@vger.kernel.org>
Sent: Tuesday, April 02, 2002 5:18 PM
Subject: Re: Update on Promise 100TX2 + Serverworks IDE issues -- 2.2.20


> > I think the serverworks IDE is only mode4, not even UDMA33.  I heard a
lot of
> > bad things about it, and removed all the IDE drives from our serverworks
> > system's controller.
>
> Serverworks OSB4 IDE will do UDMA33 but seems to have problems with
certain
> combinations of drives, controllers and unknown influences. The newer CSB5
> seems to work beautifully
>
> -
> 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/
>


  reply	other threads:[~2002-04-03  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 23:38 Update on Promise 100TX2 + Serverworks IDE issues -- 2.2.20 jim
2002-04-03  0:48 ` Trent Piepho
2002-04-03  1:18   ` Alan Cox
2002-04-03  2:08     ` Jeff Nguyen [this message]
2002-04-03  2:58       ` Alan Cox
2002-04-03  2:58         ` jim
2002-04-04  1:32           ` Re[2]: " Nerijus Baliunas
2002-04-04 10:03             ` Andre Hedrick
2002-04-03  3:10   ` jim
     [not found] <Pine.LNX.4.10.10204022311020.24257-100000@tom2.baremetal.com>
2002-04-03 14:52 ` jim

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='15b401c1dab4$7bf2c240$6502a8c0@jeff' \
    --to=jeff@aslab.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jim@rubylane.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=xyzzy@speakeasy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.