From: Gregory Brauer <greg@wildbrain.com>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mikael Pettersson <mikpe@it.uu.se>, Roel.Teuwen@advalvas.be
Subject: Re: SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete }
Date: Tue, 19 Dec 2006 09:52:36 -0800 [thread overview]
Message-ID: <458826E4.1030806@wildbrain.com> (raw)
In-Reply-To: <200612191424.kBJEO7bD007303@harpo.it.uu.se>
Mikael Pettersson wrote:
> I was looking briefly at the port mapping issue on 4-port Promise controllers
> yesterday and noticed a bit of programming magic in Promise's driver that
> Linux doesn't do, and which affects two of the four ports. That _could_
> explain your issues.
>
> /Mikael
Just as a note, I filed the issue that this thread is about as a
kernel bug:
http://bugzilla.kernel.org/show_bug.cgi?id=7516
I am also experiencing the port-mapping issue you mention with
the SATA300 TX4, but I believe that the port mapping problem and
the excess status messages are separate and unrelated problems.
Greg
prev parent reply other threads:[~2006-12-19 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 14:24 SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete } Mikael Pettersson
2006-12-19 17:52 ` Gregory Brauer [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=458826E4.1030806@wildbrain.com \
--to=greg@wildbrain.com \
--cc=Roel.Teuwen@advalvas.be \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).