From: pellegrini@mpcnet.com.br (Jeronimo Pellegrini)
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre10 Oops
Date: Thu, 20 Jun 2002 15:42:17 -0300 [thread overview]
Message-ID: <20020620184217.GA4077@mpcnet.com.br> (raw)
Hi.
Got an Oops a few minutes ago with plain 2.4.19-pre10, compiled for
Athlon/K7. If you need more info, tell me!
J.
ksymoops 2.4.5 on i686 2.4.19-pre10. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.19-pre10/ (default)
-m /boot/System.map-2.4.19-pre10 (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.
Jun 20 15:15:56 localhost kernel: Unable to handle kernel paging request at virtual address 10854a66
Jun 20 15:15:56 localhost kernel: bfa95f90
Jun 20 15:15:56 localhost kernel: *pde = 00000000
Jun 20 15:15:56 localhost kernel: Oops: 0002
Jun 20 15:15:56 localhost kernel: CPU: 0
Jun 20 15:15:56 localhost kernel: EIP: 0010:[<bfa95f90>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Jun 20 15:15:56 localhost kernel: EFLAGS: 00010202
Jun 20 15:15:56 localhost kernel: eax: 10854a66 ebx: c38d6c40 ecx: c38d6000 edx: 10854a66
Jun 20 15:15:56 localhost kernel: esi: cffe8800 edi: ca7ae000 ebp: 00000002 esp: c3e4be90
Jun 20 15:15:56 localhost kernel: ds: 0018 es: 0018 ss: 0018
Jun 20 15:15:56 localhost kernel: Process ps (pid: 10617, stackpage=c3e4b000)
Jun 20 15:15:56 localhost kernel: Stack: c01460de c38d6c40 00004300 c014e955 00004300 ca7ae000 c543f640 c543f640
Jun 20 15:15:56 localhost kernel: c014efd4 cffe8800 ca7ae000 00000002 c12ce440 c543f640 c543f640 c12cd1c0
Jun 20 15:15:56 localhost kernel: ffffffff c543f6a1 c014dc49 c12ce440 c543f640 fffffff4 c12ce440 c013c7e3
Jun 20 15:15:56 localhost kernel: Call Trace: [get_empty_inode+142/160] [proc_pid_make_inode+21/192] [proc_pid_lookup+356/464] [proc_root_lookup+57/80] [real_lookup+83/192]
Jun 20 15:15:56 localhost kernel: Code: Bad EIP value.
>>EIP; bfa95f90 Before first symbol <=====
>>eax; 10854a66 Before first symbol
>>ebx; c38d6c40 <_end+358919c/1050a55c>
>>ecx; c38d6000 <_end+358855c/1050a55c>
>>edx; 10854a66 Before first symbol
>>esi; cffe8800 <_end+fc9ad5c/1050a55c>
>>edi; ca7ae000 <_end+a46055c/1050a55c>
>>esp; c3e4be90 <_end+3afe3ec/1050a55c>
1 warning issued. Results may not be reliable.
--
next reply other threads:[~2002-06-20 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 18:42 Jeronimo Pellegrini [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-01 20:10 2.4.19-pre10 oops Kurt Roeckx
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=20020620184217.GA4077@mpcnet.com.br \
--to=pellegrini@mpcnet.com.br \
--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.