From: Norbert Kiesel <nkiesel@tbdnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] 2.5.74-bk4 in __lookup_hash
Date: Sun, 6 Jul 2003 22:11:52 -0700 [thread overview]
Message-ID: <20030707051152.GA641@tbdnetworks.com> (raw)
Hi,
still get the same oops during boot (started with -bk3). System
continues booting and seems to be usable anyway.
ksymoops 2.4.8 on i686 2.5.74-bk4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.5.74-bk4/ (default)
-m /boot/System.map-2.5.74-bk4 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel NULL pointer dereference at virtual address 00000000
00000000
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<00000000>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: c0316260 ebx: fffffff4 ecx: c665553c edx: c665553c
esi: c77dc070 edi: c6655ac0 ebp: c669ff70 esp: c669ff08
ds: 007b es: 007b ss: 0068
Stack: c015f0f4 c77dc070 c6655ac0 c669ff70 ffffffd8 c6655520 00008242 c669ff70
c015f8d9 c669ff78 c6655520 c669ff70 00000000 c669ff78 00000001 00000002
c66da640 00008241 400098b8 c77dd000 c669e000 c014fdde c77dd000 00008242
Call Trace: [<c015f0f4>] [<c015f8d9>] [<c014fdde>] [<c01502ab>] [<c010ae4b>]
Code: Bad EIP value.
>>EIP; 00000000 Before first symbol
>>eax; c0316260 <proc_link_inode_operations+0/4c>
>>ebx; fffffff4 <__kernel_rt_sigreturn+1bb4/????>
>>ecx; c665553c <__crc_acpi_get_timer+32c02d/7a74fb>
>>edx; c665553c <__crc_acpi_get_timer+32c02d/7a74fb>
>>esi; c77dc070 <__crc_class_device_remove_file+640d35/8b48b2>
>>edi; c6655ac0 <__crc_acpi_get_timer+32c5b1/7a74fb>
>>ebp; c669ff70 <__crc_acpi_get_timer+376a61/7a74fb>
>>esp; c669ff08 <__crc_acpi_get_timer+3769f9/7a74fb>
Trace; c015f0f4 <__lookup_hash+a4/e0>
Trace; c015f8d9 <open_namei+2e9/430>
Trace; c014fdde <filp_open+3e/70>
Trace; c01502ab <sys_open+5b/90>
Trace; c010ae4b <syscall_call+7/b>
1 warning and 1 error issued. Results may not be reliable.
next reply other threads:[~2003-07-07 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 5:11 Norbert Kiesel [this message]
2003-07-07 5:22 ` [OOPS] 2.5.74-bk4 in __lookup_hash William Lee Irwin III
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=20030707051152.GA641@tbdnetworks.com \
--to=nkiesel@tbdnetworks.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 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.