From: Randy Dunlap <rdunlap@xenotime.net>
To: piotr@hosowicz.com
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Maybe my frequent kernel building could be of some help to the community? And how to build?
Date: Wed, 17 Mar 2010 10:53:24 -0700 [thread overview]
Message-ID: <4BA11714.3080706@xenotime.net> (raw)
In-Reply-To: <4BA11627.6020308@example.com>
On 03/17/10 10:49, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>
>> The first thing that I would try is enabling CONFIG_DEVTMPFS and
>> CONFIG_DEVTMPFS_MOUNT, rebuild, reboot...
>
> I've rebuilt and it boots fine. Just after booting the kernel it had to
> think for a while and I was afraid that it won't boot at all. But it
> booted.
Good.
> BTW What is this message during building about? Should I worry?
>
> WARNING: modpost: Found 106 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
"Worry" is probably too strong of a word there. Any section mismatch
is a potential kernel Oops, but most of them don't cause problems.
If you do get an Oops or BUG or other problem, please post it to the
linux-kernel mailing list.
--
~Randy
next prev parent reply other threads:[~2010-03-17 17:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:02 Maybe my frequent kernel building could be of some help to the community? And how to build? Piotr Hosowicz
2010-03-16 19:24 ` Randy Dunlap
2010-03-16 19:33 ` Piotr Hosowicz
2010-03-16 19:42 ` Randy Dunlap
2010-03-17 3:24 ` Piotr Hosowicz
2010-03-17 15:07 ` Randy Dunlap
[not found] ` <4BA0F8DE.1050006@example.com>
2010-03-17 15:54 ` Randy Dunlap
2010-03-17 16:03 ` Piotr Hosowicz
2010-03-17 17:49 ` Piotr Hosowicz
2010-03-17 17:53 ` Randy Dunlap [this message]
2010-03-18 15:40 ` Randy Dunlap
2010-03-22 3:31 ` Piotr Hosowicz
2010-03-22 3:48 ` Randy Dunlap
2010-03-22 12:42 ` Piotr Hosowicz
2010-03-22 12:53 ` Piotr Hosowicz
2010-03-24 1:12 ` Piotr Hosowicz
2010-03-24 21:43 ` Randy Dunlap
2010-03-25 11:38 ` Piotr Hosowicz
2010-03-25 17:29 ` Randy Dunlap
2010-03-25 17:37 ` Piotr Hosowicz
2010-03-25 17:40 ` Randy Dunlap
2010-03-25 17:48 ` Piotr Hosowicz
2010-03-25 17:54 ` Randy Dunlap
2010-03-25 18:35 ` Piotr Hosowicz
2010-03-25 22:04 ` Randy Dunlap
2010-03-25 22:15 ` Piotr Hosowicz
2010-03-26 16:46 ` Piotr Hosowicz
2010-03-27 16:37 ` Piotr Hosowicz
2010-03-27 16:39 ` Piotr Hosowicz
2010-04-01 16:02 ` Randy Dunlap
2010-04-01 17:24 ` Piotr Hosowicz
2010-04-01 17:44 ` Piotr Hosowicz
2010-03-29 20:16 ` Is root kernel parameter expected to be the first one or something? Piotr Hosowicz
2010-03-29 20:38 ` Randy Dunlap
2010-03-29 20:41 ` Piotr Hosowicz
2010-03-29 21:33 ` Randy Dunlap
2010-03-29 22:32 ` Piotr Hosowicz
2010-03-29 22:39 ` Randy Dunlap
2010-03-29 22:44 ` Piotr Hosowicz
2010-03-29 22:48 ` Randy Dunlap
2010-03-29 22:55 ` Piotr Hosowicz
2010-03-29 23:06 ` Randy Dunlap
2010-03-29 23:44 ` Piotr Hosowicz
2010-03-30 16:37 ` Piotr Hosowicz
2010-03-30 18:03 ` Piotr Hosowicz
2010-03-30 19:00 ` Piotr Hosowicz
2010-03-31 9:15 ` Piotr Hosowicz
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=4BA11714.3080706@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=piotr@hosowicz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.