From: Paul Check on
I missed your hardware. I have an ASUS PT 6 Deluxe V2 board with 4 drives.
I think they are 1TB each, Seagate SATA drives. P

> On Mon, Jul 19, 2010 at 8:14 PM, Paul Check <paul(a)thechecks.ca> wrote:
>> Hey Tejun: I guess this is the same patch that you sent me to fix my
>> issue
>> with missing drives.  Good news: I've been through about 10 reboots now
>> and no problems.  Based on my prior experience, I'd say with the old
>> setup, 10 clean boots in a row was probably less than a 1% event.  So,
>> it
>> seems that this has fixed my problem.
>>
>> Thanks!
>>
>> Regards, Paul
>>
>
> Hey Paul. Glad it worked for you as it did for me.
>
> Was your hardware in any way similar to mine?
>
> - Mark
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Mark Knecht on
On Tue, Jul 20, 2010 at 2:19 PM, Paul Check <paul(a)thechecks.ca> wrote:
> I missed your hardware. I have an ASUS PT 6 Deluxe V2 board with 4 drives.
> I think they are 1TB each, Seagate SATA drives.  P
>

What processor? I've got the Core i7-980X. I've wondered if this
problem showed up for me because possibly the 12 thread processor
moves through some part of boot setup pretty quickly.

Mine is an Asus Rampage II Extreme with five 500GB drives.

Whatever the reason great thanks to Tejun for fixing it. I keep
wanting to add an 'r' to his last name to get 'Hero'!

Cheers,
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Paul Check on
Oh, yeah, my processor is the i7 975. That's 4 cores 8 threads, right?
Yes, nice work Tejun, thanks. I'll have to run custom kernels until this
gets fed into Debian. P

> On Tue, Jul 20, 2010 at 2:19 PM, Paul Check <paul(a)thechecks.ca> wrote:
>> I missed your hardware. I have an ASUS PT 6 Deluxe V2 board with 4
>> drives.
>> I think they are 1TB each, Seagate SATA drives.  P
>>
>
> What processor? I've got the Core i7-980X. I've wondered if this
> problem showed up for me because possibly the 12 thread processor
> moves through some part of boot setup pretty quickly.
>
> Mine is an Asus Rampage II Extreme with five 500GB drives.
>
> Whatever the reason great thanks to Tejun for fixing it. I keep
> wanting to add an 'r' to his last name to get 'Hero'!
>
> Cheers,
> Mark
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Mark Knecht on
On Tue, Jul 20, 2010 at 7:14 AM, Tejun Heo <tj(a)kernel.org> wrote:
> Helo,
>
> On 07/20/2010 05:14 AM, Paul Check wrote:
>> Hey Tejun: I guess this is the same patch that you sent me to fix my issue
>> with missing drives.  Good news: I've been through about 10 reboots now
>> and no problems.  Based on my prior experience, I'd say with the old
>> setup, 10 clean boots in a row was probably less than a 1% event.  So, it
>> seems that this has fixed my problem.
>
> Yeap, it's the same one.  I'm forwarding the patch upstream now but,
> Mark, please let me know the test result.
>
> Thanks.
>
> --
> tejun
>

Tejun,
Looks like I had a failure today. First one in weeks and only the
3rd or 4th boot with this newer patch file. One of the two drives
making a RAID0 wasn't found so /dev/md11 (constructed from /dev/sdd
and /dev/sde) couldn't be started. I did a cold reboot and the drive
was found.

If it matters, and it probably doesn't, the failure came on a boot
which had a scheduled fsck to do of /dev/md5 - my main / drive. I
don't see how that would make a difference but I figure why leave the
info out. That's why the times are so much larger in the dmesg file.
(I think)

dmesg attached. I patched the Gentoo kernel if it makes a
difference, same as I did with the earlier patch.

mark(a)c2stable ~ $ uname -a
Linux c2stable 2.6.34-gentoo-r2 #1 SMP PREEMPT Sun Jul 18 14:09:48 PDT
2010 x86_64 Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz GenuineIntel
GNU/Linux
mark(a)c2stable ~ $

Sorry,
Mark
From: Paul Check on
That's unfortunate. FYI I have continued to be trouble free, but my
processor is a bit weaker than Mark's, although I would find it surprising
that this would cause a problem. Also, FYI Mark, I have 12GB of Corsair
RAM, and have it bumped up to the Intel XMP profile.

P

> On Tue, Jul 20, 2010 at 7:14 AM, Tejun Heo <tj(a)kernel.org> wrote:
>> Helo,
>>
>> On 07/20/2010 05:14 AM, Paul Check wrote:
>>> Hey Tejun: I guess this is the same patch that you sent me to fix my
>>> issue
>>> with missing drives.  Good news: I've been through about 10 reboots
>>> now
>>> and no problems.  Based on my prior experience, I'd say with the old
>>> setup, 10 clean boots in a row was probably less than a 1% event.  So,
>>> it
>>> seems that this has fixed my problem.
>>
>> Yeap, it's the same one.  I'm forwarding the patch upstream now but,
>> Mark, please let me know the test result.
>>
>> Thanks.
>>
>> --
>> tejun
>>
>
> Tejun,
> Looks like I had a failure today. First one in weeks and only the
> 3rd or 4th boot with this newer patch file. One of the two drives
> making a RAID0 wasn't found so /dev/md11 (constructed from /dev/sdd
> and /dev/sde) couldn't be started. I did a cold reboot and the drive
> was found.
>
> If it matters, and it probably doesn't, the failure came on a boot
> which had a scheduled fsck to do of /dev/md5 - my main / drive. I
> don't see how that would make a difference but I figure why leave the
> info out. That's why the times are so much larger in the dmesg file.
> (I think)
>
> dmesg attached. I patched the Gentoo kernel if it makes a
> difference, same as I did with the earlier patch.
>
> mark(a)c2stable ~ $ uname -a
> Linux c2stable 2.6.34-gentoo-r2 #1 SMP PREEMPT Sun Jul 18 14:09:48 PDT
> 2010 x86_64 Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz GenuineIntel
> GNU/Linux
> mark(a)c2stable ~ $
>
> Sorry,
> Mark
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/