All of lore.kernel.org
 help / color / mirror / Atom feed
From: tom_gall@vnet.ibm.com
To: Martin Costabel <costabel@wanadoo.fr>
Cc: linuxppc-dev@lists.linuxppc.org, dwayne@us.ibm.com
Subject: Re: modprobe and exec format error
Date: Thu, 27 Jul 2000 17:46:30 +0000	[thread overview]
Message-ID: <39807576.3F77B13A@vnet.ibm.com> (raw)
In-Reply-To: 397F6686.20E2D953@wanadoo.fr


Hi Martin,

Martin Costabel wrote:
>
> tom_gall@vnet.ibm.com wrote:
> >
> > Hi All,
> >
> >   Here's a strange one...
> >
> >   I'm bringing up a 2.4.0-testX kernel (Paul's latest PMac tree) and the kernel
> > does come up quite a ways (tho how far is a bit hard to tell as things scroll by
> > and scroll lock doesn't work)
>
> If you compile MagicSysRq support in, you can stop scrolling by
> "SysRq-0" (that is F13 + zero).
>
> > I get the following repeated item on my screen ... so imagine this line times N
> >
> > /sbin/modprobe -s -k binfmt_4c46 errno=8
> >
> > Well errno 8 is Exec format error as I recall...    time to upgrade modutils?
> >
> > Anyone with any suggestions or have seen this one before?
>
> Yeah, seen this before:
> http://lists.linuxppc.org/listarcs/linuxppc-dev/200007/msg00327.html
> and my solution:
> http://lists.linuxppc.org/listarcs/linuxppc-dev/200007/msg00345.html

Thanks much for the pointers.

I am experiencing this with Cort's current development kernel tree. Based on the
previous posting you had in theory all I needed to do was just grab a fresh
kernel which I did this morning. The same problem surfaced. So something is
definately wrong with the Cort's 2.4.0-test5 tree.

I took a gander at elf.h. The only change I see is



2.3.99-pre9

#define elf_check_arch(x) ((x) == EM_PPC)

2.4.0-test5-Cort

#define elf_check_arch(x) ((x)->e_machine == EM_PPC)

This appearantly is used 3 times fs/binfmt_elf.c

2.3.99-pre9

if (!elf_check_arch(interp_elf_ex->e_machine))

2.4.0-test5-Cort

if (!elf_check_arch(&elf_ex))

So while the code changed it would appear to be consistant at least....

Guess I'll have to keep digging!

> I'm curious what your reason was for getting this.

Me too!

Regards,

Tom

--
Tom Gall - PowerPC Linux Team    "Where's the ka-boom? There was
Linux Technology Center           supposed to be an earth
(w) tom_gall@vnet.ibm.com         shattering ka-boom!"
(w) 507-253-4558                 -- Marvin Martian
(h) tgall@uswest.net
http://oss.software.ibm.com/developerworks/opensource/linux

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-07-27 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-26 22:06 modprobe and exec format error tom_gall
2000-07-26 22:30 ` Martin Costabel
2000-07-27 17:46   ` tom_gall [this message]

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=39807576.3F77B13A@vnet.ibm.com \
    --to=tom_gall@vnet.ibm.com \
    --cc=costabel@wanadoo.fr \
    --cc=dwayne@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.