From: Tejun Heo <tj@kernel.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: 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, 07 Jul 2010 07:50:16 +0200 [thread overview]
Message-ID: <4C341598.6040004@kernel.org> (raw)
In-Reply-To: <AANLkTikehTO1j6Gd7Y_g32_P6Yg9KB8Z8qwbNJh10aOU@mail.gmail.com>
Hello,
On 07/06/2010 08:13 PM, Mark Knecht wrote:
> OK - thanks. The patch seemed to install correctly. I then did
>
> make clean
> make && make modules_install
>
> and then a Gentoo command:
>
> modules-rebuild -X rebuild
>
> to pick up any package modules that need to be rebuild when I use a
> new kernel. (X drivers, vmware, etc.)
>
> The kernel boots fine:
>
> mark@c2stable ~ $ uname -a
> Linux c2stable 2.6.34-gentoo-r1 #4 SMP PREEMPT Tue Jul 6 10:35:15 PDT
> 2010 x86_64 Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz GenuineIntel
> GNU/Linux
> mark@c2stable ~ $
>
> I don't know what I'm looking for in the dmesg files but I do see one
> message about a SATA Link being down.
Umm... the patched module isn't being loaded. If patched, it should
be reporting whether it's hard or soft resetting and some other debug
messages. One common mistake is not updating initrd with patched
modules. Is "modules-rebuild -X rebuild" the command for initrd
update?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-07-07 5:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 17:56 Drives missing at boot 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 [this message]
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
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=4C341598.6040004@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
/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