Re: kmod: failed to exec /sbin/modprobe -s -k binfmt-0000, errno=8, 12

Eleonora Autore (ely@ns1.avnet.co.uk)
Mon, 15 Nov 1999 07:44:58 +0000 (GMT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Joe Zbiciak: "Re: Bug in fat-fs code: file date/time wrong"
Previous message: Tigran Aivazian: "Re: info scope doesn't work for modules..."
In reply to: (no name): "Re: kmod: failed to exec /sbin/modprobe -s -k binfmt-0000, errno=8, 12"

> binfmt-0000 happens to me always when I to exec a zero length file. (2.2.x)
> I guess this could be classified as a kernel bug but no idea why you are
> getting it - unless your ramdisk fs is corrupted.
> No idea what it is trying to execute?

if ramdisk was corrupted then 2.2.x wouldn't work either, would it? But
it does. So, it does look like a bug in 2.3.28 (most likely binfmt or
kmod) so I am going to debug it as soon as I get a spare minute.

Regards,
Tigran.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Joe Zbiciak: "Re: Bug in fat-fs code: file date/time wrong"
Previous message: Tigran Aivazian: "Re: info scope doesn't work for modules..."
In reply to: (no name): "Re: kmod: failed to exec /sbin/modprobe -s -k binfmt-0000, errno=8, 12"