All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yaroslav Halchenko <kernel@onerussian.com>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	woodys@xandros.com
Subject: Re: Highpoint SATA RAID (khe khe) status -- oopses, crashes, etc
Date: Fri, 28 Apr 2006 15:20:17 -0400	[thread overview]
Message-ID: <20060428192017.GH17639@washoe.onerussian.com> (raw)
In-Reply-To: <20060427053528.GB17639@washoe.onerussian.com>

Hi Woody and the others,

Is there anything else we could try to make this damn hpt366 work to
somewhat better extent? now 700kBps is too slow -- I just gave up
waiting while it would rebuild RAID1 on those two drives. and that also
slowed down another RAID present in the system (nice Areca one)

> Alan Cox's newest and greatest ide-on-sata falls back to the 33MHz
> timings
Isn't what it the libata implementation which oopsed? May be I should
try older "Support for SATA", but kernel menu item says that it
conflicts with libata SATA driver, so I am not sure how stable that
solution will be either... but I know that on 2.6.7 there were no
problem detecting the beast

I am not much of a kernel hacker that is why my question is so vague...
but many be I can be of some help if pointed to the right direction

Thank you in advance
-- 
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07105
Student  Ph.D. @ CS Dept. NJIT

  parent reply	other threads:[~2006-04-28 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65zwE-61W-35@gated-at.bofh.it>
2006-04-26 19:41 ` Highpoint SATA RAID (khe khe) status -- oopses, crashes, etc Woody Suwalski
2006-04-27  5:35   ` Yaroslav Halchenko
2006-04-27 16:49     ` Yaroslav Halchenko
2006-04-27 17:12       ` Yaroslav Halchenko
2006-04-28 19:20     ` Yaroslav Halchenko [this message]
2006-04-25 17:23 Yaroslav Halchenko
2006-04-26 19:06 ` Yaroslav Halchenko

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=20060428192017.GH17639@washoe.onerussian.com \
    --to=kernel@onerussian.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=woodys@xandros.com \
    /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.