From: Christian <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: IPv6 module oopsing on 2.5.69
Date: Thu, 29 May 2003 13:07:19 +0200 [thread overview]
Message-ID: <3ED5E9E7.5070602@g-house.de> (raw)
hi,
while booting the ipv6 module gets installed, along with this message in
the log:
prinz kernel: IPv6 v0.8 for NET4.0
prinz kernel: ------------[ cut here ]------------
prinz kernel: kernel BUG at include/linux/module.h:284!
prinz kernel: invalid operand: 0000 [#1]
prinz kernel: CPU: 0
prinz kernel: EIP: 0060:[<e5b983e8>] Tainted: P
prinz kernel: EFLAGS: 00010246
prinz kernel: eax: 00000000 ebx: 00000000 ecx: d8872e40 edx: d916eb80
prinz kernel: esi: 0000003a edi: e5bbfc60 ebp: d916eb80 esp: dc763efc
prinz kernel: ds: 007b es: 007b ss: 0068
prinz kernel: Process modprobe (pid: 917, threadinfo=dc762000 task=d8cb5300)
prinz kernel: Stack: e5bc1800 d916eb80 0000039c df109d70 00000001
0000000a ffffff9f d8872e40
prinz kernel: c025bc90 d8872e40 0000003a 416d9c90 e5bc1060 00000000
dffdadc0 00000003
prinz kernel: c0121765 e5bc1000 dffdadc0 dffdadc0 00000000 c030d698
e5bc1800 00000000
prinz kernel: Call Trace: [<e5bc1800>] [<c025bc90>] [<e5bc1060>]
[<c0121765>] [<e5bc1000>] [<e5bc1800>] [<e498c82d>] [<e5bc2388>]
[<e5bc1800>] [<e498c1bd>] [<e5bbfc48>] [<c01318ff>] [<e5bc1800>]
[<c0109137>]
prinz kernel: Code: 0f 0b 1c 01 78 d0 bb e5 e9 d6 fd ff ff 0f 0b 1e 01
8f d0 bb
IPv6 support is not useable then, a single run of the "ping6" binary
(even without options) gives a segfault. the machine is a Athlon 900,
running debian/testing (glibc 2.3.1), one tainted module (nvidia)
loaded. more info available on demand.
i am a user only, so please don't expect patches from me :-(
Thank you,
Christian.
next reply other threads:[~2003-05-29 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 11:07 Christian [this message]
2003-05-29 11:11 ` IPv6 module oopsing on 2.5.69 ismail (cartman) donmez
2003-05-29 11:20 ` Dave Jones
2003-05-29 11:30 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-29 23:30 ` Christian
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=3ED5E9E7.5070602@g-house.de \
--to=evil@g-house.de \
--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