From: Tejun Heo <htejun@gmail.com>
To: Andreas John <aj@net-lab.net>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Conke Hu <conke.hu@gmail.com>, Neil Brown <neilb@suse.de>
Subject: Re: [PATCH] ahci.c: fix ati sb600 sata IRQ_TF_ERR
Date: Fri, 07 Sep 2007 10:24:17 +0900 [thread overview]
Message-ID: <46E0A841.3090300@gmail.com> (raw)
In-Reply-To: <46DDE7E7.5030605@net-lab.net>
[restoring cc list, please don't drop them]
Andreas John wrote:
> Hi,
> sorry for replying not quicker, but I just wanted to re-test all the
> theories.
>
> 1. I was not able to reproduce the problem with 2.6.22 ubuntu gutsy
> (amd64 and i386). I ran checkarray --all many many times together with
> dds, but didnt tigger the bug. (even with a second new board!)
>
> 2. The only explaination I have is that the sata connector on the HDD
> itself had some "plaque" on it (production?)
>
> 3. The 1.5GB Sata jumper made no difference - that was our 1st try.
Hmmm.... Well, probably caused by faulty hardware or cosmic rays. :-P
> 4. I think the board can do MSI, as the test above shows
Not sure. IRQ messages don't seem to indicate MSI is in use. Have you
enabled it in the kernel config?
> 5. I still dont know _why_ the problem ocurred. By now I have about 5
> machines in production - no crash. Another two observations:
> a) If mdX is sync'ing, the machines somestimes locks up for 5-100 secs
Does kernel say anything during this lock up?
> b) If you hotplug a hdd (pull out) you get a sata "frozen" line in the
> log. Then e.g. md0 sets the disk to faulty, but the same disk (other
> partition) is still marked active on md1. It gets removeed, on 1st
> access on md1. Is that the intended behavior? Or should I file a bug?
> Where? Neil?
Currently, there's no mechanism to notify unplug to md inside the
kernel. It can probably done via udev trick or some such. Cc'd Neil
for advice.
Thanks.
--
tejun
parent reply other threads:[~2007-09-07 1:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <46DDE7E7.5030605@net-lab.net>]
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=46E0A841.3090300@gmail.com \
--to=htejun@gmail.com \
--cc=aj@net-lab.net \
--cc=conke.hu@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=neilb@suse.de \
/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).