public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Gardiol <willy@gardiol.org>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-ide@vger.kernel.org>
Subject: Promise and sparc64
Date: Sat, 20 Dec 2003 19:53:49 +0100	[thread overview]
Message-ID: <200312201953.50714.willy@gardiol.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I have got an Ultra5 (sparc based, sun4u) and tried to plug both a Promise 
Ultra100tx2 (pdc20268) and a Promise FastTrack 2000 (pcd20271).

The system boots and the kernel (2.4.23) works, the two UDMA100 disks plugged 
(one per channel) on the promised works in PIO mode.

If i enable DMA on a single drive it WORKS (up to udma2 tested, with hdparm 
- -X66) 
When i enable DMA on the other channel (it does not count which one) i start 
getting many DMA errors (-20 and -22 error codes) and soon the disks hangs 
bringing the system down (but no kernel panic).

Similar, if i enable DMA on one channel then start coping data bethween the 
two channels the systems suffers the same symptoms.

Please note, both the controller and the disks have been used successfully in 
UDMA5 on a x86 system before, and now the disks positively works in mdma2 
using the onboard CMD ide controller of the Ultra5 (does not seems to be able 
to do UDMA at all)

Is this a know issue?


- -- 

! 
 Willy Gardiol - willy@gardiol.org
 www.gardiol.org
 Use linux for your freedom.

  "Linux is like a wigwam: no windows,
   no gates, Apache inside."

  "Linux è come una tenda indiana: niente finestre,
   niente porte, gli Apache dentro.

      Albert Arendsen



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/5Jq9Q9qolN/zUk4RAvTlAKCYfE2rP5bWTqPaD1yhCvpffwcEsQCgnQoF
qS/Dyo0oxVDlM4S3+SHaYTA=
=FIAW
-----END PGP SIGNATURE-----


                 reply	other threads:[~2003-12-20 18:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200312201953.50714.willy@gardiol.org \
    --to=willy@gardiol.org \
    --cc=linux-ide@vger.kernel.org \
    --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