9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work
Date: Wed,  6 Feb 2008 15:04:40 -0500	[thread overview]
Message-ID: <86fe18cae58b72e94b51df4965c3a7dc@quanstro.net> (raw)
In-Reply-To: <b8b797315d63f0bb91f292917d5c0039@gmx.de>

> Now this is very interesting! A friend gave me an Adaptec (it really is an SiL) 2xSATA
> PCI controller [1] for testing, and i was able to generate I/O errors just by reading from
> both drives in paralel! Does anybody run multiple SATA drives in IDE-mode without
> problems under Plan9?
>
> [1] pci -v
> 0.20.0:	disk 01.80.01 1095/3112  15 0:0000fb01 16 1:0000fa01 16 2:0000f901 16 3:0000f801 16 4:0000f701 16 5:fdffd000 512
> 	Silicon Image, Inc. SiI 3112 SATALink/SATARaid Controller
>
> cinap

yes.  i have a cpu server with an nforce-based motherboard and two sata
hard drives recognized as ide.  i have never had a problem with the ide
emulation on this motherboard.

i think there is insufficient evidence to jump to the conclusion that plan 9
has trouble with >1 sata drive accessed via ide emulation.  if linux uses
ide emulation with the same ata commands & transfer sizes, do you get
the same errors?  (do you notice any performance funnies?)

we have a sata protcol analyzer.  we've seen some mighty interesting things
with it.  for instance, some hard drive firmware generates sata protocol violations
when pushed hard.  and some hard drive firmware generates sata protocol
violations with very little load.  generally hard drives, when they do this
send a few data FISes but forget to finish the transaction.  this causes the
chipset to wait forever.  this can look  something like what you are seeing.
on the other hand, there are reports of via chipsets having trouble dealing
with concurrent access and we have also seen chipsets generating sata protocol
violations.

it could be that the linux driver has exactly this problem but notices
that it's hung up and has a few tricky moves to get the device unstuck.

- erik


  reply	other threads:[~2008-02-06 20:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  1:31 [9fans] usb ohci support arrives geoff
2008-02-06  2:16 ` Michael Andronov
2008-02-06  4:01 ` lucio
2008-02-06 12:55 ` [9fans] usb ohci support arrives -- caution Richard Miller
2008-02-06 16:18 ` [9fans] usb ohci support arrives C H Forsyth
2008-02-06 16:23   ` Juan M. Mendez
2008-02-06 17:23 ` [9fans] usb ohci support arrives -- another caution Richard Miller
2008-02-06 17:58   ` Sape Mullender
2008-02-06 19:08     ` Richard Miller
2008-02-06 19:23     ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work cinap_lenrek
2008-02-06 20:04       ` erik quanstrom [this message]
2008-02-06 22:29         ` cinap_lenrek
2008-02-06 22:40           ` erik quanstrom
2008-02-06 23:26             ` cinap_lenrek
     [not found] <54b639a7eb08c31e4ef2a6d9fd7b6a62@quanstro.net>
2008-02-08  9:35 ` Kernel Panic
2008-02-08 14:55   ` erik quanstrom
2008-02-08 14:56   ` Robert Raschke
2008-02-08 15:27     ` Robert Raschke
  -- strict thread matches above, loose matches on Subject: below --
2008-02-05 22:13 cinap_lenrek
2008-02-06  8:41 ` Kernel Panic
2008-02-06  9:45   ` erik quanstrom
2008-02-06 10:43     ` Kernel Panic
2008-02-06 11:03       ` erik quanstrom
2008-02-05  8:18 Kernel Panic
2008-02-05  8:54 ` Lorenzo Fernando Bivens de la Fuente
2008-02-05 13:20 ` erik quanstrom
2008-02-05 19:48 ` Robert Raschke
2008-02-06  2:01 ` arisawa

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=86fe18cae58b72e94b51df4965c3a7dc@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).