From: richard kennedy <richard@rsk.demon.co.uk>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org
Subject: Re: linux-next-20090220: insmod: -1 Invalid module format
Date: Fri, 20 Feb 2009 14:54:32 +0000 [thread overview]
Message-ID: <499EC428.7080901@rsk.demon.co.uk> (raw)
In-Reply-To: <200902202229.BDD18292.SFOLMOVFOtFJQH@I-love.SAKURA.ne.jp>
Tetsuo Handa wrote:
> I can't load kernel module for linux-next-200902{18,19,20} .
> linux-next-20090217 was OK.
>
> -----
> Linux version 2.6.29-rc5-next-20090220 (root@tomoyo) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #2 SMP PREEMPT Fri Feb 20 21:20:01 JST 2009
> (...snipped...)
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Loading usbcore.ko module
> insmod: error inserting '/lib/usbcore.ko': -1 Invalid module format
> Loading ehci-hcd.ko module
> (...snipped...)
> insmod: error inserting '/lib/ide-gd_mod.ko': -1 Invalid module format
> Waiting for driver initialization.
> stabilized: open /proc/scsi/scsi: No such file or directory
> Scanning and configuring dmraid supported devices
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> init used greatest stack depth: 1344 bytes left
> Kernel panic - not syncing: Attempted to kill init!
> -----
>
> Config is at http://I-love.SAKURA.ne.jp/tmp/config-next-20090220
>
> Regards.
I've just had the same problem.
It seems to be CONFIG_MODVERSIONS that causes this problem. I unset it
in my config & everything works now. I see that you've got it set as
well, so you could try removing it.
regards
Richard
next prev parent reply other threads:[~2009-02-20 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 13:29 Tetsuo Handa
2009-02-20 14:54 ` richard kennedy [this message]
2009-02-20 22:37 ` Tetsuo Handa
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=499EC428.7080901@rsk.demon.co.uk \
--to=richard@rsk.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sfr@canb.auug.org.au \
/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