linux-kernel - Re: linux-next-20090220: insmod: -1 Invalid module format

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <499EC428.7080901@rsk.demon.co.uk>
Date:	Fri, 20 Feb 2009 14:54:32 +0000
From:	richard kennedy <richard@....demon.co.uk>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
CC:	sfr@...b.auug.org.au, linux-kernel@...r.kernel.org
Subject: Re: linux-next-20090220: insmod: -1 Invalid module format

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@...oyo) (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


--
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/