All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Reinhard <tracer@robotech.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Problem with concurrent SATA-Writes
Date: Thu, 02 Jun 2005 00:40:38 +0200	[thread overview]
Message-ID: <429E3966.2050208@robotech.de> (raw)
In-Reply-To: <429DF174.2000002@pobox.com>



Jeff Garzik wrote:
> Yes, I think this is the third time I've read your email.  You can stop 
> posting it now.
> 
> Sometimes we just don't have time to read and respond to every support 
> request.  If you absolutely require support, please use a paid support 
> channel like SuSE or Red Hat.
Sorry if I annoyed or bothered You or any other one on the list.

I didn't expect that You or any other immediately care about my problems 
and solve them or already have a solution. I could try to fix the driver 
myself but as it seems to be a SIL-specific Problem I need the help or 
some hints from someone who has the (nda-)docs. Maybe they already noted 
this as an errata for which some kind of quirk is needed.

I worked-around the problem by putting the discs on a different 
controller. It seems that this only happens with these Samsung-drives on 
this controller.

Just in case you face this or a similar Problem in the future or find 
the time to investigate it...

BTW: with the siimage driver the transfer-rate is low (20MB/s instead of 
45MB/s) but at least it's working.

BTW2: same with 2.6.12-rc5-mm2


	Tobias




  reply	other threads:[~2005-06-01 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 17:13 Problem with concurrent SATA-Writes Tobias Reinhard
2005-06-01 17:33 ` Jeff Garzik
2005-06-01 22:40   ` Tobias Reinhard [this message]
2005-06-02 21:57     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 17:16 Tobias Reinhard
2005-05-31 19:00 ` Lennart Sorensen
2005-05-31 19:49   ` Tobias Reinhard
2005-05-27 16:12 Tobias Reinhard

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=429E3966.2050208@robotech.de \
    --to=tracer@robotech.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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 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.