From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Michael Tasche" <michael.tasche@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crash when loading a module (without executing any code of the module!)
Date: Wed, 30 Jun 2004 14:29:48 -0700 [thread overview]
Message-ID: <20040630142948.08da5d90.rddunlap@osdl.org> (raw)
In-Reply-To: <255262226@web.de>
Hi-
On Wed, 30 Jun 2004 15:41:27 +0200 Michael Tasche wrote:
| Hi,
| currently I'm developping a small kernel module for a hardware (which was developped by a friend of mine), which is
| supposed to load a firmware onto a PCI-card.
|
| The development is done together with the friend, who's developping the firmware.
| We tried the following:
| He compiled a kernel-independent object (containing the firmware) on his system using kbuild
| (Dual-AthlonMP, SuSE 8.2 with kernel.org-kernel 2.6.3, module-init-tools 0.9.14-pre2, gcc 3.3.1,
| ld 2.14.90.0.5 20030722).
| Afterwards I tried to link it to my kernel-module (using the same kbuild makefile with
| firmware.o_shipped) on my machine (Fedora2, 2.6.5-3.1smp, module-init-tools 3.0-pre10, gcc 3.3.3, ld 2.15.90.0.3
| 20040415).
|
| This is what happened:
|
| Unable to handle kernel paging request at virtual address 82d90700
| printing eip:
| 02135657
| *pde = 00000000
| Oops: 0002 [#1]
| PREEMPT SMP
| CPU: 1
| EIP: 0060:[<02135657>] Not tainted
| EFLAGS: 00010246 (2.6.5-3.1smp)
| EIP is at module_unload_init+0xa/0x4d
| eax: 82d90700 ebx: 82c2387c ecx: 82d8f600 edx: 00000000
| esi: 82c38f33 edi: 82c40027 ebp: 000005f0 esp: 763c3f38
| ds: 007b es: 007b ss: 0068
| Process insmod (pid: 1812, threadinfo=763c2000 task=7f3c60b0)
| Stack: 02136dc0 7864cc40 8282a000 00000000 82d8f600 00000000 00000000 00000000
| 00000000 00000000 0000000b 00000000 00000010 00000000 00000000 00000009
| 00000025 00000024 00000026 82c3829c 82c23727 82a94000 0856a008 763c3fc4
| Call Trace:
| [<02136dc0>] load_module+0x53e/0x7fa
| [<021370da>] sys_init_module+0x5e/0x293
|
| Code: 89 81 00 11 00 00 89 81 04 11 00 00 89 c8 c7 80 00 01 00 00
Some of those stack addresses look odd to me.
Please send me your kernel .config file.
| What puzzles me, is that I don't see any of my code in the calltrace. I had a look into the
| kernel-code and it seems to crash, before it even jumps into my code. What am I missing?
| By the way, everything works fine, if I compile the entire module on my machine.
| Some more testing showed, that we do also expierence a crash, if we do everything vice-versa.
|
| Regards,
| Michael
|
| P.S: This was also posted by the driver developer to comp.os.linux.development.system.
Can you post the module source code, or a subset of it that causes
the problem?
--
~Randy
next prev parent reply other threads:[~2004-06-30 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:41 Crash when loading a module (without executing any code of the module!) Michael Tasche
2004-06-30 21:29 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 15:15 Michael Tasche
2004-07-02 15:49 ` Randy.Dunlap
2004-07-05 12:48 Michael Tasche
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=20040630142948.08da5d90.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.tasche@web.de \
/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.