From: Jure Pecar <pegasus@telemach.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17-rc1 oops
Date: Thu, 27 Dec 2001 19:09:54 +0100 [thread overview]
Message-ID: <20011227190954.6b504c04.pegasus@telemach.net> (raw)
Hi list,
This happened yesterday on our 4-way system with highmem:
ksymoops 0.7c on i686 2.4.17-rc1. Options used
-v /usr/src/linux/vmlinux (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.17-rc1/ (default)
-m /usr/src/linux/System.map (specified)
Warning (compare_maps): mismatch on symbol partition_name , ksyms_base
says c01ee900, vmlinux says c0156eb0. Ignoring ksyms_base entry
Dec 26 09:06:00 castor kernel: invalid operand: 0000
Dec 26 09:06:00 castor kernel: CPU: 0
Dec 26 09:06:00 castor kernel: EIP: 0010:[__free_pages_ok+75/508] Not tainted
Dec 26 09:06:00 castor kernel: EFLAGS: 00010202
Dec 26 09:06:00 castor kernel: eax: 00000840 ebx: c1e1dec0 ecx: c1e1dec0 edx: 00000000
Dec 26 09:06:00 castor kernel: esi: fe2b6fdd edi: 00000000 ebp: 00000000 esp: f1d79ef4
Dec 26 09:06:00 castor kernel: ds: 0018 es: 0018 ss: 0018
Dec 26 09:06:00 castor kernel: Process ps (pid: 32579, stackpage=f1d79000)
Dec 26 09:06:00 castor kernel: Stack: 00000360 fe2b6fdd 00000000 d3778000 e979a700 bffffc7d 00000000 00000000
Dec 26 09:06:00 castor kernel: 00000360 c012e8d8 c011de64 e979a700 00000000 00000360 d8124000 f1d79f44
Dec 26 09:06:00 castor kernel: f1d78000 e979a71c d3778000 e979a700 c1e1dec0 f4c973e0 c0152319 d8124000
Dec 26 09:06:00 castor kernel: Call Trace: [__free_pages+28/32] [access_process_vm+368/432] [proc_pid_environ+85/104]
[proc_info_read+89/296] [sys_read+142/196]
Dec 26 09:06:00 castor kernel: Code: 0f 0b 8b 43 18 a8 80 74 02 0f 0b 80
63 18 eb be 00 e0 ff ff
Using defaults from ksymoops -t elf32-i386 -a i386
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 0f 0b ud2a
Code; 00000002 Before first symbol
2: 8b 43 18 mov 0x18(%ebx),%eax
Code; 00000005 Before first symbol
5: a8 80 test $0x80,%al
Code; 00000007 Before first symbol
7: 74 02 je b <_EIP+0xb> 0000000b Before
first symbol
Code; 00000009 Before first symbol
9: 0f 0b ud2a
Code; 0000000b Before first symbol
b: 80 63 18 eb andb $0xeb,0x18(%ebx)
Code; 0000000f Before first symbol
f: be 00 e0 ff ff mov $0xffffe000,%esi
1 warning issued. Results may not be reliable.
This box is a heavily loaded mail server, running what once was redhat
6.2. When users started complaining, it was around 13h and loadavg was
~400 and still growing. I couldn't even list the processes, hard reset was
the only option to put things back into normal quickly. Luckily I have ext3 :)
Any ideas?
--
Jure Pecar
next reply other threads:[~2001-12-27 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 18:09 Jure Pecar [this message]
2001-12-27 19:53 ` Jure Pecar
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=20011227190954.6b504c04.pegasus@telemach.net \
--to=pegasus@telemach.net \
--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
all inboxes | Powered by JetHome®