All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gabor FUNK" <FUNK.Gabor@hunetkft.hu>
To: Denys Dmytriyenko <denis@denix.org>, linux-ide@vger.kernel.org
Cc: Jim Paris <jim@jtan.com>, Mark Lord <liml@rtr.ca>,
	Tejun Heo <htejun@gmail.com>
Subject: Re: sata_sil24 stability and performance
Date: Sun, 2 Mar 2008 10:39:29 +0100	[thread overview]
Message-ID: <005d01c87c4c$0d01f550$4d0fa8c0@M2007> (raw)
In-Reply-To: 20080302061453.GA7291@denix.org

I have/had a similar (hard resetting) problem (2+8 disks, kernel 2.6.24), 
see thread:
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg15950.html

I tried replacing the PSU and also run the system with two 650W PSU-s,
also failed. I also think that PSU shouldn't be the problem as I see they
eat much less in operation than at spinup.

Now I replaced the MB and it runs with a different Gigabyte MB with
the 8 disk in SW RAID6 connected to the 2*4 on board SATA
connectors (these now use 2+4*ata_piix and 2 ahci kernel drivers)
and the 2 system disk is on an add-on Silicon Image SiI 3512 card.

Since the problem is not seen immediately I can't tell whether it is
better now. It is running cp 1 2, cp 2 3... to 2500 or so, with 1GB
files then md5sums them, so far the problem not exhibiting. The
1st copy didn't finish in a day, so accidentally a second one got
started (cron) and yesterday an "md: data-check" also started, so
the system is quite busy now doing disk reads/writes...

G.


----- Original Message ----- 
From: "Denys Dmytriyenko" <denis@denix.org>
To: <linux-ide@vger.kernel.org>
Cc: "Jim Paris" <jim@jtan.com>; "Mark Lord" <liml@rtr.ca>
Sent: Sunday, March 02, 2008 7:14 AM
Subject: Re: sata_sil24 stability and performance


> On Tue, Feb 19, 2008 at 10:32:07AM -0500, Mark Lord wrote:
>> Jim Paris wrote:
>>> ..
>>> As you may have noticed on this list, power supplies are very
>>> frequently a problem.
>> ..
>>
>> Actually, no, I haven't noticed that.  :)
>>
>> I do see them more frequently being suggested as a possible problem,
>> and then after some time and expense on the part of the reporters
>> it nearly always turns out to have been a device driver bug,
>> or (less often) a firmware quirk of the device.
>>
>> Yes, PSUs are often suggested as a problem here,
>> but only rarely has that been true.
>>
>> Especially nowadays, as PSUs are becoming much larger than
>> they historically once were.
>
> Hi again. Thanks for your replies and sorry for bringing this up again.
> I am still trying to resolve those 2 issues I mentioned in the first
> email. While playing with different power options lately, I decided to
> replace the PSU again for a single-rail Silencer 750 EPS12V, which is
> rated at 60A (!) for a single 12V rail. Does anybody have any experience
> with it? Can anyone suggest anything better?
>
> That is assuming the first issue with exceptions and resets is due to
> the power being maxed out...
>
> Meanwhile I would still like to resolve the low performance issue with
> SiI 3124, which shows only 17 MB/s write speed doing "dd if=/dev/zero",
> while Intel ICH7 based PC writes at 44 MB/s sustained rate. I'd really
> appreciate any ideas/suggestions towards solving this issue. Please let
> me know if any other information is needed. I'm attaching the original
> email with logs. Thanks in advance!
>
> -- 
> Denys
> 


  reply	other threads:[~2008-03-02  9:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  2:09 sata_sil24 stability and performance Denys Dmytriyenko
2008-02-19  4:36 ` Jim Paris
2008-02-19  6:39   ` Denys Dmytriyenko
2008-02-19 15:32   ` Mark Lord
2008-03-02  6:14     ` Denys Dmytriyenko
2008-03-02  9:39       ` Gabor FUNK [this message]
2008-03-04  0:02         ` Tejun Heo
2008-03-04  0:22           ` Denys Dmytriyenko
2008-03-04  3:28             ` Tejun Heo
2008-03-04  6:29               ` Denys Dmytriyenko
2008-03-05  8:11                 ` Tejun Heo
2008-03-06  4:14                   ` Denys Dmytriyenko
2008-03-06  4:25                     ` Tejun Heo
2008-03-06  6:55                       ` Denys Dmytriyenko
2008-03-06  7:08                         ` Tejun Heo
2008-03-15 21:43                           ` Denys Dmytriyenko
2008-03-17  3:09                             ` Mark Lord
2008-03-18  0:15                               ` Denys Dmytriyenko
2008-03-18  4:09                                 ` Tejun Heo
2008-03-18  4:53                                   ` Denys Dmytriyenko
2008-03-18  6:40                                     ` Tejun Heo
2008-03-20 22:37                                       ` Denys Dmytriyenko
2008-03-21  0:18                                         ` Tejun Heo
2008-04-14  1:19                                           ` Denys Dmytriyenko
2008-04-14  2:49                                             ` Tejun Heo
2008-04-14 10:55                                             ` Gabor FUNK
2008-03-18  9:14                                     ` Gabor FUNK
2008-03-18 13:06                                       ` Gabor FUNK
2008-03-18 20:05                                   ` Mark Lord
2008-03-18 20:06                                     ` Mark Lord

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='005d01c87c4c$0d01f550$4d0fa8c0@M2007' \
    --to=funk.gabor@hunetkft.hu \
    --cc=denis@denix.org \
    --cc=htejun@gmail.com \
    --cc=jim@jtan.com \
    --cc=liml@rtr.ca \
    --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.