linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <yiding_wang@agilent.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.5.72 module loading issue
Date: Tue, 22 Jul 2003 16:27:24 -0600	[thread overview]
Message-ID: <334DD5C2ADAB9245B60F213F49C5EBCD05D55220@axcs03.cos.agilent.com> (raw)

I am still struggling on the fc driver module working on new 2.5.72/2.6 kernel and wish someone can shed some lights here.

The driver is working great for 2.4.x Linux and is modified to reflect all SCSI layer change in 2.5.72.  I have RH9.0 and installed 2.5.72 on the same system.  Driver compiled under 2.5.72 OK.  The module utilities are upgraded to 0.9.13-pre.

Now first problem I have is to module loading fails on "insmod mymodule.o".  Message:
 
"No module found in object"
"Error inserting 'mymodule.o': -1 Invalid module format"

By checking the trace, following are the failed part: 
... ...
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=49530, ...}) = 0
... ...
brk(0)                                  = 0x804a000
brk(0x804b000)                          = 0x804b000
brk(0)                                  = 0x804b000
create_module(umovestr: Input/output error 0, 0)                     = -1 ENOSYS (Function not implemented)
open("mymodule.o", O_RDONLY)             = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=345047, ...}) = 0
mmap2(NULL, 345047, PROT_READ, MAP_SHARED, 3, 0) = 0x40017000
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - something is wrong here
init_module("ELF", 0x543d7No module found in object) = -1  ENOEXEC (Exec format error))         = -1 ENOEXEC (Exec format error)
... ...
exit_group(1)                           = ?

Noticed that kernel build module has *.mod.c file created, I tried to include those part in but the result is the same.  

This is a SCSI HBA driver and init_module() is not required (ref. to qlogic, adaptec and buslogic drivers).

Also I tried to load kernel build driver module BusLogic.o and qla1280.o with "insmod", it gives error almost the same except the message are different.  
"BusLogic: no version message, tainting kernel"
"Error inserting 'BusLogic.o': -1  No such device

In init_module call, it has init_module("ELF". 0x1a5b4BusLogic" no version magic, tainting kernel.) = -1  ENODEV (No such device).

It looks like something is missing from migrating my driver module from 2.4.x to 2.5.x.

What is new requirement for module building and loading with "insmod" on 2.5.72 compare with the requirement in 2.4.x?  

Many thanks!

Eddie



Also the init_module call 
 

             reply	other threads:[~2003-07-22 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 22:27 yiding_wang [this message]
2003-07-23  3:14 ` 2.5.72 module loading issue Randy.Dunlap
2003-07-23  6:29 yiding_wang
2003-07-24 17:11 yiding_wang
2003-07-24 21:08 ` Sam Ravnborg
2003-07-24 23:27   ` Randy.Dunlap

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=334DD5C2ADAB9245B60F213F49C5EBCD05D55220@axcs03.cos.agilent.com \
    --to=yiding_wang@agilent.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).