On Wed, Jul 7, 2010 at 8:48 AM, Tejun Heo <tj@kernel.org> wrote:
quoted text > Hello,
>
> On 07/07/2010 05:34 PM, Mark Knecht wrote:
>> OK - I don't know if this was you intention but since adding this
>> patch I've not had a single drive missing failure. I've cold booted
>> about 8 times and warm booted at least 20 times. Every one has come up
>> fine. I've even gone so far as to turn off the UPS and sit for 5
>> minutes before cold booting. Still nothing fails right now.
>>
>> I've had this sort of statistical thing happen before where it hasn't
>> failed for days, maybe even weeks, but then it starts failing and
>> fails every time for awhile. Over the past few days working with you
>> I've never had to reboot more than twice to get you a file. Now I've
>> tried 30 times this morning and I've come up with nothing.
>>
>> I will continue to watch the machine and send you the failing dmesg
>> file whenever I finally get it. For now I can only attach the passing
>> file showing the patch is now included.
>
> It seems like SIDPR is a bit more unreliable than the current code can
> handle and the added delay and read could have affected the result.
> Eh... weird. Can you please apply the attached patch instead? The
> only difference is it will print out two SControl values instead of
> one. ie. "XXX SControl after resume = AAA BBB, tries=T". Can you
> please try to boot multiple times and see if AAA and BBB differ
> anytime? If that happens, please attach the boot log. Also, if you
> see one with T > 1, please attach that one too.
>
> Thanks.
>
> --
> tejun
>
4 warm reboots. All 4 said 300 300. However the 4th one only showed an
extra attempt at running the patch code with and also showed Tries =
2. I'm attaching boot #1 and boot #4 for now. I've saved them all if
you need or just want them.
Please note that in all 4 cases all drives were found. Nothing is
missing in any test yet after adding these either of these patches.
I've not tried cold boots yet. That's next.
Cheers,
Mark
