From: Stuart MENEFY <stuart.menefy@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: where are initcalls defined?
Date: Mon, 21 Jul 2008 12:39:12 +0000 [thread overview]
Message-ID: <48848370.2050504@st.com> (raw)
In-Reply-To: <488453DB.70101@spesonline.com>
Luca
Luca Santini wrote:
> I'm trying to port kernel 2.6.26 to edosk7760 board.
> my kernel hangs up during initcalls;
> with a little debugging i found that with a minimal config (only ext2 fs
> for example)
> skipping the 71th initcalls my kernel continues to boot until
>
>
> [ 1.665032] No filesystem could mount root, tried: ext2
> [ 1.670330] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(1,0)
>
>
> where can i found the initcalls vector list ?
The initcalls table is built by the linker by concatenating all
the .initcall<level>.init sections. These are created by the
<level>_initcall macros.
The easiest way to debug this sort of problem is to run with the
initcall_debug kernel command line option, which will print the
name of each function before calling it.
Stuart
next prev parent reply other threads:[~2008-07-21 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 9:16 where are initcalls defined? Luca Santini
2008-07-21 12:39 ` Stuart MENEFY [this message]
2008-07-21 13:19 ` Luca Santini
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=48848370.2050504@st.com \
--to=stuart.menefy@st.com \
--cc=linux-sh@vger.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