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

[Tilman Schmidt]

My workhorse machine (Pentium D 940, Intel DG965QF board,
mirrored SATA disks), which runs fine with kernel:
ts@xenon:~> 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

After a pause of about 15 seconds, there is another set of
messages:

CPA self-test:
 4k 3070 large 219 gb 0 x 3289[c0000000-f77fd000] miss 0
 4k 194558 large 32 gb 0 x 194590[c0000000-f77fd000] miss 0
 4k 194558 large 32 gb 0 x 194590[c0000000-f77fd000] miss 0
ok.

Then, silence. The keyboard remains operative inasmuch as I can
use the SysRq functions to sync and reboot, but otherwise the
system does not go any further. Going back to kernel 2.6.28.3
the system comes up fine again.

The most conspicuous symtpom is of course the five consecutive
"runaway loop" messages I never saw before. But before that,
the order in which the PCI and USB devices are detected also
appears surprisingly changed for a stable release.

I am prepared to bisect this if somebody reminds me how to do
that for stable releases. The tree
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
doesn't seem to have them.

Thanks
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@xxxxxxx
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Attachment: signature.asc
Description: OpenPGP digital signature