linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gabor FUNK" <FUNK.Gabor@hunetkft.hu>
To: Denys Dmytriyenko <denis@denix.org>, Tejun Heo <htejun@gmail.com>
Cc: Mark Lord <liml@rtr.ca>,
	linux-ide@vger.kernel.org, Jim Paris <jim@jtan.com>,
	Richard Bland <r.bland@espo.org>
Subject: Re: sata_sil24 stability and performance
Date: Mon, 14 Apr 2008 12:55:43 +0200	[thread overview]
Message-ID: <01ee01c89e1e$4c488e10$4d0fa8c0@M2007> (raw)
In-Reply-To: 20080414011913.GA19751@denix.org

Since you brought it up, several days ago I got informed,
that the "original problem" (exception/hard resetting port)
could be related to kernel option IRQBALANCE.
See more at:
http://forums.gentoo.org:80/viewtopic-t-641372-highlight-.html

As Dmytri and me as well both replaced the MB finally which
now runs fine, we will probably not going to "play" again with
this, but if anyone runs into this in the near future, this can be a
thing to try. I can imagine that this could've helped, as in my
case failing was purely limited one controller [*4 disks] at the
time, eg. no other disk on other controller, nor just only one
or some disk on a controller, but all disks on only 1 controller.

And if anyone have any theoretical imagination why it could be
the cause - and where to fix :-] - don't hesitate to write...

Cheers,

G.



----- Original Message ----- 
From: "Denys Dmytriyenko" <denis@denix.org>
To: "Tejun Heo" <htejun@gmail.com>
Cc: "Mark Lord" <liml@rtr.ca>; "Gabor FUNK" <FUNK.Gabor@hunetkft.hu>; 
<linux-ide@vger.kernel.org>; "Jim Paris" <jim@jtan.com>
Sent: Monday, April 14, 2008 3:19 AM
Subject: Re: sata_sil24 stability and performance


> Tejun et al,
>
> I wanted to thank you all for the support you provided. I ended up 
> replacing
> MoBo+CPU to Intel based ones (and previously mentioned single-rail PSU) 
> and
> now everything works rock solid for over a week now! Thanks again.
>
>> > BTW, issuing "smartctl -a" on a drive in standby, throws this 
>> > exception:
>> >
>> > Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 
>> > 0x0 action 0x2 frozen
>> > Mar 20 18:16:53 [kernel] ata10.00: cmd 
>> > b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>> > Mar 20 18:16:53 [kernel]          res 
>> > 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>> > Mar 20 18:16:53 [kernel] ata10: soft resetting port
>> > Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 
>> > SControl 300)
>> > Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
>> > Mar 20 18:16:54 [kernel] ata10: EH complete
>> > Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware 
>> > sectors (500108 MB)
>> > Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
>> > Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
>> > Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read 
>> > cache: enabled, doesn't support DPO or FUA
>>
>> Which kernel version and how did you put the drive into sleep?
>
> This timeout exception is still there - 2.6.24.4, drive goes to sleep on
> timeout of 30 minutes (hdpram -S 241)
>
> -- 
> Denys
> 


  parent reply	other threads:[~2008-04-14 10:57 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
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 [this message]
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='01ee01c89e1e$4c488e10$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 \
    --cc=r.bland@espo.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;
as well as URLs for NNTP newsgroup(s).