[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C483BF4.3090006@kernel.org>
Date: Thu, 22 Jul 2010 14:39:16 +0200
From: Tejun Heo <tj@...nel.org>
To: Mark Knecht <markknecht@...il.com>
CC: Paul Check <paul@...checks.ca>,
Linux Kernel List <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>
Subject: Re: Drives missing at boot
Hello,
On 07/21/2010 10:54 PM, Mark Knecht wrote:
> 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@...table ~ $ 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@...table ~ $
Hmmm... that's weird. Can you please make sure the patch is actually
applied? Adding a printk("XXX patch applied!\n") near other changes
usually is easy enough. Also, can you please apply resume-dbg-1.patch
too and reproduce the failure and post log?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists