From: Tejun Heo <htejun@gmail.com>
To: Andrew Ryder <tireman@shaw.ca>
Cc: "Gaston, Jason D" <jason.d.gaston@intel.com>, linux-ide@vger.kernel.org
Subject: Re: Sata 4726 Testing
Date: Thu, 10 Jan 2008 15:36:51 +0900 [thread overview]
Message-ID: <4785BD03.10809@gmail.com> (raw)
In-Reply-To: <47855F02.3010407@shaw.ca>
Hello,
Andrew Ryder wrote:
> This might be of interest.. I had turned the drive off for about 20
> minutes, then turned it back on. ata1.03 is now partially there, it is
> recognized as a device, but of 0MB in size.
>
> All of this is done with the 4726 turned on..
>
> Bootlog11.txt -> I unplugged the 4726, waited 10 seconds, and plugged it
> into the second port on the 3124. All 4 drives are there.
>
> Bootlog12.txt -> I unplugged the 4726 again, waited 10 seconds, plugged
> it back into the first (original) port, and ata1.03 is back..
>
> Bootlog13.txt -> I powered the 4726 off, waited 10 seconds, turned it
> back on. The same drive is missing now.
>
> Bootlog14.txt -> I unplugged, waited 10 seconds, and re-plugged the 4726
> into the same port (first eSATA port) and now ata1.03 is recognized and
> accessible.
>
> I'll make sure to turn on the timestamping for you tomorrow. Would want
> me to redo this testing so you can have the timestamps also?
Please swap the third and fourth drive and see whether the problem moves
with the drive or stays with the port. Also, please verify regular
powered on detection (array up and running before detection begins)
always works. 4726 is very quirky (it ate up a LOT of development /
testing time) and I guess we'll have to accept some brokenness.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-01-10 6:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4769A17A.8070806@shaw.ca>
[not found] ` <4769F974.2020905@gmail.com>
2007-12-20 22:23 ` Sata 4726 Testing Andrew Ryder
2007-12-22 13:53 ` Andrew Ryder
2008-01-07 16:12 ` Tejun Heo
2008-01-07 22:28 ` Andrew Ryder
2008-01-08 3:54 ` Tejun Heo
2008-01-08 8:00 ` Andrew Ryder
2008-01-09 5:45 ` Tejun Heo
2008-01-09 17:47 ` Andrew Ryder
2008-01-10 0:53 ` Tejun Heo
2008-01-10 1:58 ` Gaston, Jason D
2008-01-10 3:19 ` Tejun Heo
2008-01-10 16:24 ` Gaston, Jason D
2008-01-10 3:29 ` Tejun Heo
2008-01-09 23:00 ` Andrew Ryder
2008-01-10 4:20 ` Tejun Heo
2008-01-09 23:55 ` Andrew Ryder
2008-01-10 6:36 ` Tejun Heo [this message]
2008-01-11 1:19 ` Andrew Ryder
2008-01-11 7:49 ` Tejun Heo
2008-01-11 23:13 ` Andrew Ryder
2008-01-13 5:10 ` Tejun Heo
2008-01-13 19:01 ` Andrew Ryder
2008-01-14 0:35 ` Tejun Heo
2008-01-19 22:05 ` Andrew Ryder
2008-01-20 3:21 ` Tejun Heo
2008-01-14 19:07 ` Gaston, Jason D
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=4785BD03.10809@gmail.com \
--to=htejun@gmail.com \
--cc=jason.d.gaston@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=tireman@shaw.ca \
/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).