From: Sander <sander@humilis.net>
To: Mark Lord <liml@rtr.ca>
Cc: sander@humilis.net, Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@osdl.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.xx: sata_mv: another critical fix
Date: Wed, 3 May 2006 20:39:43 +0200 [thread overview]
Message-ID: <20060503183943.GA31435@favonius> (raw)
In-Reply-To: <4458DE81.6040603@rtr.ca>
Mark Lord wrote (ao):
> Sander wrote:
> >The message "PCI ERROR; PCI IRQ cause=0x40000100" gives no result in
> >Google. Could this be a broken or miss-seated controller?
>
> Yes. Those bits mean: "no target response within 4 PCI clock cycles".
>
> In English, I believe the translation is "dead/disconnected controller".
Thank you for explaining the error and the translation.
I'll try to re-seat it then, and replace it when that fails.
With kind regards, Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2006-05-03 18:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 0:57 [git patch append] sata_mv fix Jeff Garzik
2006-03-21 5:00 ` [PATCH] 2.6.xx: sata_mv: another critical fix Mark Lord
2006-03-21 12:13 ` Sander
2006-03-21 13:51 ` Mark Lord
2006-03-21 15:37 ` Sander
2006-03-21 18:33 ` Linus Torvalds
2006-03-21 19:15 ` Sander
2006-03-21 19:22 ` Mark Lord
2006-03-21 19:35 ` Linus Torvalds
2006-03-21 20:44 ` Sander
2006-03-21 20:59 ` Linus Torvalds
2006-03-21 21:09 ` Jeff Garzik
2006-03-21 21:19 ` Linus Torvalds
2006-03-21 21:37 ` Jeff Garzik
2006-03-22 5:48 ` Sander
2006-03-22 9:00 ` Sander
2006-03-22 14:50 ` Mark Lord
2006-03-22 17:09 ` Sander
2006-03-22 17:53 ` Eric D. Mudama
2006-03-22 18:01 ` Sander
2006-03-22 17:55 ` Mark Lord
2006-03-28 4:34 ` Mark Lord
2006-05-03 12:16 ` Sander
2006-05-03 12:42 ` Mark Lord
2006-05-03 13:32 ` Sander
2006-05-03 16:46 ` Mark Lord
2006-05-03 18:39 ` Sander [this message]
2006-03-22 2:12 ` Jeff Garzik
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=20060503183943.GA31435@favonius \
--to=sander@humilis.net \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).