mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Check" <paul@thechecks.ca>
To: "Mark Knecht" <markknecht@gmail.com>
Cc: "Tejun Heo" <tj@kernel.org>,
	"Linux Kernel List" <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Drives missing at boot
Date: Wed, 21 Jul 2010 17:22:51 -0400	[thread overview]
Message-ID: <13ec35777817500abfcc6c8da0224351.squirrel@thechecks.ca> (raw)
In-Reply-To: <AANLkTinxDjPCk46eItZrXziTbf6efqvNNNTbkZDXIbns@mail.gmail.com>

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@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@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@c2stable ~ $
>
> Sorry,
> Mark
>



  reply	other threads:[~2010-07-21 21:22 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 17:56 Mark Knecht
2010-07-03 15:20 ` Mark Knecht
2010-07-03 16:01 ` Tejun Heo
2010-07-03 16:06   ` Mark Knecht
2010-07-03 16:13     ` Tejun Heo
2010-07-03 16:42       ` Mark Knecht
2010-07-05  6:30         ` Tejun Heo
2010-07-05 16:56           ` Mark Knecht
2010-07-06  6:33             ` Tejun Heo
2010-07-06 18:13               ` Mark Knecht
2010-07-07  5:50                 ` Tejun Heo
2010-07-07 15:34                   ` Mark Knecht
2010-07-07 15:48                     ` Tejun Heo
2010-07-07 16:15                       ` Mark Knecht
2010-07-07 16:19                         ` Tejun Heo
2010-07-07 16:27                           ` Mark Knecht
2010-07-07 17:06                       ` Mark Knecht
2010-07-07 17:26                         ` Tejun Heo
2010-07-07 17:32                           ` Mark Knecht
2010-07-19 19:31                           ` Mark Knecht
2010-07-19 21:01                             ` Tejun Heo
2010-07-20  3:14                               ` Paul Check
2010-07-20 14:14                                 ` Tejun Heo
2010-07-20 14:53                                   ` Mark Knecht
2010-07-20 16:16                                     ` Mark Knecht
2010-07-21 20:54                                   ` Mark Knecht
2010-07-21 21:22                                     ` Paul Check [this message]
2010-07-22 12:39                                     ` Tejun Heo
2010-08-02 22:07                                       ` Mark Knecht
2010-08-03 18:41                                         ` Randy Dunlap
2010-08-03 18:47                                           ` Mark Knecht
2010-08-03 18:55                                             ` Randy Dunlap
2010-08-04 16:16                                               ` Mark Knecht
2010-08-03 18:49                                           ` Jim Paris
2010-08-03 18:53                                             ` Mark Knecht
2010-07-20 20:52                                 ` Mark Knecht
2010-07-20 21:19                                   ` Paul Check
2010-07-20 21:26                                     ` Mark Knecht
2010-07-20 23:05                                       ` Paul Check
2010-07-03 18:56     ` Stan Hoeppner
2010-07-03 19:21       ` Mark Knecht
2010-07-03 19:42         ` Stan Hoeppner
2010-07-03 19:57           ` Mark Knecht
2010-07-03 22:31             ` Mark Knecht
2010-07-04  1:25               ` Thomas Fjellstrom
2010-07-05  6:19               ` Tejun Heo
2010-07-05 16:48                 ` Mark Knecht
2010-07-05 23:59                   ` Robert Hancock
2010-07-06  4:16                     ` Mark Knecht
2010-07-06  6:13                       ` Stan Hoeppner
2010-07-06 11:26                       ` Sander
2010-07-06  6:32                   ` Tejun Heo

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=13ec35777817500abfcc6c8da0224351.squirrel@thechecks.ca \
    --to=paul@thechecks.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=tj@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

Powered by JetHome