From: Tejun Heo <htejun@gmail.com>
To: Thomas Evans <evans02472@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_sil24 / Alpha / 4726 PMP issue ..
Date: Mon, 28 Jan 2008 09:44:28 +0900 [thread overview]
Message-ID: <479D256C.1090507@gmail.com> (raw)
In-Reply-To: <479D0AB5.6070203@gmail.com>
Thomas Evans wrote:
> Tejun and all -
>
> I have a new log - I got somewhat further by setting this bit when
> init'd via HOST_CTRL:
>
> Bit [28]: PERR Rpt Dsbl (R/W) – PERR Report Disable. This bit, when set
> to one, disables reporting of PCI bus
> parity errors to the Command Execution State Machine (such errors would
> otherwise cause the state machine to stop
> and report an error in the Command Error register).
Hmmm... That's strange. If PERR makes a difference, it means PCI bus
side is contributing to the problem but only when PMP is attached while
directly attached drive works just fine?
> This causes the PMP device to be noticed, but the first qc command never
> completes.
>
> Please see the log and see if there is anything obvious.
Thanks but I'm as lost as you are. :-(
--
tejun
next prev parent reply other threads:[~2008-01-28 0:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4794459C.3090200@gmail.com>
2008-01-21 7:26 ` sata_sil24 / Alpha / 4726 PMP issue Tejun Heo
2008-01-21 16:42 ` Thomas Evans
2008-01-21 16:47 ` Thomas Evans
2008-01-22 2:26 ` Tejun Heo
2008-01-23 4:34 ` Thomas Evans
2008-01-23 6:18 ` Tejun Heo
2008-01-24 0:22 ` Thomas Evans
2008-01-24 1:42 ` Tejun Heo
[not found] ` <864c1e490801231823v3e9cf61ds2a0d553ed5b61fb2@mail.gmail.com>
2008-01-24 2:32 ` Tejun Heo
2008-01-24 3:39 ` Thomas Evans
2008-01-24 3:52 ` Tejun Heo
2008-01-24 15:07 ` Thomas Evans
2008-01-24 15:11 ` Tejun Heo
2008-01-24 16:40 ` Thomas Evans
2008-01-24 17:08 ` Tejun Heo
[not found] ` <4798CA71.20707@gmail.com>
[not found] ` <4798CC90.4040707@gmail.com>
[not found] ` <4798CCDF.9070305@gmail.com>
[not found] ` <4798CE10.2050005@gmail.com>
[not found] ` <4798D4A2.7030303@gmail.com>
[not found] ` <47991AD9.6050804@gmail.com>
[not found] ` <47993686.5040405@gmail.com>
[not found] ` <479939E3.4020307@gmail.com>
2008-01-25 6:04 ` Thomas Evans
2008-01-25 17:28 ` Thomas Evans
2008-01-25 17:59 ` Thomas Evans
2008-01-25 18:16 ` Jay Estabrook
2008-01-27 22:50 ` Thomas Evans
2008-01-28 0:44 ` Tejun Heo [this message]
2008-01-28 6:51 ` Thomas Evans
2008-01-29 4:00 ` Thomas Evans
2008-01-29 4:24 ` Tejun Heo
2008-01-29 4:31 ` Thomas Evans
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=479D256C.1090507@gmail.com \
--to=htejun@gmail.com \
--cc=evans02472@gmail.com \
--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).