linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Mark Lord <liml@rtr.ca>,
	linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_mv problems on Marvell MV88SX5081
Date: Wed, 18 Oct 2006 16:08:43 -0500	[thread overview]
Message-ID: <453697DB.2060806@atipa.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610181449470.29022@twin.jikos.cz>

Jiri Kosina wrote:
> On Wed, 18 Oct 2006, Mark Lord wrote:
> 
>>> Buffer I/O error on device sda1, logical block 122126336
>> Scroll WAY BACK in the log, and find the error messages which preceeded
>> the first occurance of that one.  (with a bad sector, it is very likely
>> you will see a zillion "Buffer I/O errors", as the SCSI mid-layer is not
>> at all nice about how it handles them).
> 
> Actually the "Buffer I/O error" is the very first error message I am 
> receiving, a few minutes after the driver is initialized and there is some 
> disk activity happening.
> 
> Thanks,
> 

Jiri,

Make sure that you delete the arrays in the highpoint bios before
trying to use the open source driver.

I have seen alot of really funny things on several of the different
hw/sw raid controllers (not just highpoint's) if you attempt to use
a disk that someone has already tagged as raid disks, even on the
same controller it gets interesting if you attempt to use them
non-raid.

I would be interested in knowing if the open source driver can successfully
driver those boards.

                           Roger


      reply	other threads:[~2006-10-18 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 11:19 sata_mv problems on Marvell MV88SX5081 Jiri Kosina
2006-10-18 12:36 ` Mark Lord
2006-10-18 12:53   ` Jiri Kosina
2006-10-18 21:08     ` Roger Heflin [this message]

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=453697DB.2060806@atipa.com \
    --to=rheflin@atipa.com \
    --cc=jeff@garzik.org \
    --cc=jikos@jikos.cz \
    --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 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).