From: Thomas Schlichter <thomas.schlichter@web.de>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Oops in register_proc_table (2.6.1-mm4)
Date: Fri, 16 Jan 2004 19:17:16 +0100 [thread overview]
Message-ID: <200401161917.20713.thomas.schlichter@web.de> (raw)
In-Reply-To: <20040115225948.6b994a48.akpm@osdl.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1811 bytes --]
Hi Andrew,
I just saw following Oops in my Kernel messages. I didn'd have this with -mm3.
NET: Registered protocol family 10
Unable to handle kernel paging request at virtual address 000927c0
printing eip:
c012ba17
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c012ba17>] Not tainted VLI
EFLAGS: 00010246
EIP is at register_proc_table+0x47/0x120
eax: 00000000 ebx: e106c9ec ecx: ffffffff edx: 000927c0
esi: 00000000 edi: 000927c0 ebp: c012b130 esp: de4ddd7c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 1936, threadinfo=de4dc000 task=de9e3900)
Stack: e1061159 000081a4 de6e5c40 81a40000 de6e5c40 e106d480 00000000 de6e5c40
00000000 c012ba7c e10617fc 0000416d de6e5cc0 416d0000 de6e5cc0 e106d640
00000000 de6e5cc0 00000000 c012ba7c e1061862 0000416d dffccac0 416dddec
Call Trace:
[<c012ba7c>] register_proc_table+0xac/0x120
[<c012ba7c>] register_proc_table+0xac/0x120
[<c012ba7c>] register_proc_table+0xac/0x120
[<c012bb4e>] register_sysctl_table+0x5e/0x80
[<e105d347>] ipv6_sysctl_register+0x17/0x20 [ipv6]
[<e0e9018b>] inet6_init+0x18b/0x2d0 [ipv6]
[<c013b62b>] sys_init_module+0x17b/0x1670
[<c0152cd6>] vma_link+0x76/0xc0
[<c015423c>] do_mmap_pgoff+0x38c/0x6f9
[<c015e109>] filp_close+0x59/0xa0
[<c015e1ab>] sys_close+0x5b/0xa0
[<c02df843>] syscall_call+0x7/0xb
Code: 33 85 f6 0f 84 9b 00 00 00 8b 53 04 85 d2 89 d7 74 ea 8b 73 18 85 f6 75
0b 8b 43 14 85 c0 0f 84 cb 00 00 00 31 c0 b9 ff ff ff ff <f2> a
e f7 d1 49 85 f6 0f b7 43 10 89 cd 66 89 44 24 0e 74 6d 66
<7>request_module: failed /sbin/modprobe -- net-pf-10. error = 11
If this is not enough information to track down the problem I can provide
my .config of any other information, of course.
Best regards
Thomas Schlichter
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-16 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 6:59 2.6.1-mm4 Andrew Morton
2004-01-16 9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 18:46 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 19:20 ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
2004-01-16 17:32 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
[not found] ` <200401161449.i0GEnoAv026627@fire-1.osdl.org>
2004-01-16 17:03 ` 2.6.1-mm4 Andrew Morton
2004-01-16 17:14 ` 2.6.1-mm4 (compile stats) John Cherry
2004-01-16 17:37 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 17:58 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 18:17 ` Thomas Schlichter [this message]
2004-01-17 2:22 ` 2.6.1-mm4 Adrian Bunk
2004-01-19 11:00 ` 2.6.1-mm4 same sound oops as mm3 Helge Hafting
2004-01-19 11:46 ` 2.6.1-mm4 Luiz Fernando Capitulino
2004-01-20 0:26 ` 2.6.1-mm4 Thomas Molina
2004-01-20 0:57 ` 2.6.1-mm4 Andrew Morton
2004-01-20 2:13 ` 2.6.1-mm4 Thomas Molina
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=200401161917.20713.thomas.schlichter@web.de \
--to=thomas.schlichter@web.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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