All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: stefania magistrali <s.magistrali@selta.it>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: loading modules
Date: Fri, 20 Sep 2002 13:25:23 +0200	[thread overview]
Message-ID: <3D8B05A3.A7BF82C8@opensource.se> (raw)
In-Reply-To: 3D8A1265.D0CC5D33@selta.it


This might be related to a powerpc-specific bug in the busybox
insmod implementation. Try the 0.60.4 release or use this patch:

http://opensource.se/projects/busybox/busybox-0.60.3-insmod_rewrite.patch

/ magnus

stefania magistrali wrote:
>
> Hi all!
> I am working with a PowerPC 860T based board.
> I have a problem with loading modules: I made:
>
> make dep make clean make zImage  make modules  and make modules_install
>
> to create my kernel and modules  , but when I try to load the module
> hdlc.o with insmod, I have a segmentation fault. I am using busybox
> version 0.60.3  and linux version 2.4.19pre6. Here I send the last part
> of the strace sequence of the command "insmod  hdlc"
> Can anyone help me?
> Thanks very much in advance!
> Stefania
>
> query_module(NULL, 0, NULL, 0)          = 0
> query_module(NULL, QM_MODULES, { /* 0 entries */ }, 0) = 0
> mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x30033000
> query_module(NULL, QM_SYMBOLS, 0x30032e08, 16384, 21866) = -1 ENOSPC (No
> space left on device)
> mmap(NULL, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x30037000
> query_module(NULL, QM_SYMBOLS, { /* 961 entries */ }, 961) = 0
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
>

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

  reply	other threads:[~2002-09-20 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 18:07 loading modules stefania magistrali
2002-09-20 11:25 ` Magnus Damm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19 12:44 blesson paul
2002-02-19 18:41 ` Alexandre P. Nunes

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=3D8B05A3.A7BF82C8@opensource.se \
    --to=damm@opensource.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=s.magistrali@selta.it \
    /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.