From: Jarek Luberek <jarek@swipnet.se>
To: linux-kernel@vger.kernel.org
Cc: jarek@swipnet.se
Subject: Oops in 2.4.9
Date: Fri, 17 Aug 2001 08:25:39 +0200 [thread overview]
Message-ID: <200108170625.f7H6PdV00943@marvin.linux-dude.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
I saw this oops in my dmesg log:
The systems is a dual PIII 450, ide disks, reiserfs root file system. Suse
7.1. GeForce256 but X was not working at the time (maybe this was
the reason)
Greetings,
Jarek
[-- Attachment #2: oops.log --]
[-- Type: text/plain, Size: 2058 bytes --]
invalid operand: 0000
CPU: 1
EIP: 0010:[<c012b968>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 0000001f ebx: c12d8a14 ecx: 00000046 edx: 01000000
esi: c44f1cc4 edi: 00000000 ebp: 00000000 esp: c3803ed0
ds: 0018 es: 0018 ss: 0018
Process kdm (pid: 1130, stackpage=c3803000)
Stack: c0227486 c022755a 00000051 c12d8a14 c44f1cc4 00000000 00000000 00000000
c12d8a14 c12d8a14 c01235e3 c12d8a14 c012c1c3 c0123841 c12d8a14 c3803f44
00000000 00000001 c44f1cc4 00000000 c12d8a14 c3803f44 c012392d c44f1c20
Call Trace: [<c01235e3>] [<c012c1c3>] [<c0123841>] [<c012392d>] [<c0146ce6>]
[<c0145126>] [<c013e430>] [<c013e508>] [<c0106d23>]
Code: 0f 0b 83 c4 0c 8d 76 00 8b 43 18 a8 20 74 19 6a 53 68 5a 75
>>EIP; c012b968 <__free_pages_ok+a8/30c> <=====
Trace; c01235e3 <remove_inode_page+3b/48>
Trace; c012c1c3 <__free_pages+1b/1c>
Trace; c0123841 <truncate_list_pages+145/1c8>
Trace; c012392d <truncate_inode_pages+69/ac>
Trace; c0146ce6 <iput+a2/194>
Trace; c0145126 <d_delete+62/a0>
Trace; c013e430 <vfs_unlink+168/198>
Trace; c013e508 <sys_unlink+a8/120>
Trace; c0106d23 <system_call+33/38>
Code; c012b968 <__free_pages_ok+a8/30c>
00000000 <_EIP>:
Code; c012b968 <__free_pages_ok+a8/30c> <=====
0: 0f 0b ud2a <=====
Code; c012b96a <__free_pages_ok+aa/30c>
2: 83 c4 0c add $0xc,%esp
Code; c012b96d <__free_pages_ok+ad/30c>
5: 8d 76 00 lea 0x0(%esi),%esi
Code; c012b970 <__free_pages_ok+b0/30c>
8: 8b 43 18 mov 0x18(%ebx),%eax
Code; c012b973 <__free_pages_ok+b3/30c>
b: a8 20 test $0x20,%al
Code; c012b975 <__free_pages_ok+b5/30c>
d: 74 19 je 28 <_EIP+0x28> c012b990 <__free_pages_ok+d0/30c>
Code; c012b977 <__free_pages_ok+b7/30c>
f: 6a 53 push $0x53
Code; c012b979 <__free_pages_ok+b9/30c>
11: 68 5a 75 00 00 push $0x755a
13 warnings issued. Results may not be reliable.
next reply other threads:[~2001-08-17 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 6:25 Jarek Luberek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-22 6:19 Oops in 2.4.9 Luca Montecchiani
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=200108170625.f7H6PdV00943@marvin.linux-dude.com \
--to=jarek@swipnet.se \
--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