linux-kernel - Re: 2.6.28.[45] boot failure: request_module: runaway loop modprobe binfmt-464c

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]

Date:	Tue, 17 Feb 2009 11:01:51 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28.[45] boot failure: request_module: runaway loop modprobe 
	binfmt-464c

On Tue, Feb 17, 2009 at 10:09, Tilman Schmidt <tilman@...p.cc> wrote:
> My workhorse machine (Pentium D 940, Intel DG965QF board,
> mirrored SATA disks), which runs fine with kernel:
> ts@...on:~> uname -a
> Linux xenon 2.6.28.3-testing #1 SMP PREEMPT Mon Feb 2 23:32:07 CET 2009 i686 i686 i386 GNU/Linux
> fails to come up with an identically configured 2.6.28.4 or 2.6.28.5
> kernel. The boot process hangs at about the time the root
> file system is mounted, the last messages being (scribbled
> down manually on a piece of paper, please make allowances):
>
> /dev/RAID/root: recovering journal ... clean
> fsck successful. Mounting root device r/w
> Mounting root /dev/RAID/root
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on dm-0, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c

Are you sure, that you don't have a 32/64 bit mismatch between the
kernel and userspace? Like you miss 32-bit emulation in a 64-bit
kernel, or your modprobe is 64-bit and you are trying to run it on a
32-bit kernel?

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