From: Christopher Mulcahy <cmulcahy@avesi.com>
To: Vincent Jorrand <vjorrand@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: sata_nv exceptions in 2.6.20.3
Date: Thu, 22 Mar 2007 10:38:03 -0400 [thread overview]
Message-ID: <460294CB.6060909@avesi.com> (raw)
In-Reply-To: <756092.42594.qm@web31805.mail.mud.yahoo.com>
Robert Hancock thought this was a hardware problem.
He was right.
I switched around cables on the hot-swap backplane, figuring that I
would determine whether I had a bad cable or a bad backplane ( hoping
for a bad cable ) and the problem went away. One of the cables wasn't
seated properly apparently. ( It was a tight 1U box with very
aggressive twist-ties that I had to cut to switch them around, so this
wasn't immediately obvious.
I would make sure that all cables are seated properly, and try a
different cable if the problem persists.
Vincent Jorrand wrote:
> I saw your email in the kernel dev mailing and I think I have the same problem, but since I am not a kernel developer, or running the bleeding edge kernels, I was not sure whether it was appropriate for me to post on the list.
>
>
>
> My hard drive is a Seagate Barracudas ( 7200.10, 750GB, ST3750640AS ), very similar to yours. It is brand new (less than a month old)
> I also get the:
> CPB flags CMD err, flags-0x11
> error in /var/log/messages.
>
> I am running kernel 2.6.20-1.2925.fc6
>
> Did you figure out a way to fix the problem?
>
> Vincent
>
>
>
>
>
>
>
>
next parent reply other threads:[~2007-03-22 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <756092.42594.qm@web31805.mail.mud.yahoo.com>
2007-03-22 14:38 ` Christopher Mulcahy [this message]
[not found] <fa.Avx6sndie+sm3ZWe+AEeEHpfxd8@ifi.uio.no>
2007-03-20 23:51 ` sata_nv exceptions in 2.6.20.3 Robert Hancock
2007-03-20 20:48 Christopher Mulcahy
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=460294CB.6060909@avesi.com \
--to=cmulcahy@avesi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vjorrand@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox