From: "Tony Mars" <tmars@chorushosting.com>
To: linux-smp@vger.kernel.org
Subject: Log file Query
Date: Sun, 21 Apr 2002 14:41:34 -0700 [thread overview]
Message-ID: <NNEEKDPGACDAGGDNNHOOMEGFFEAA.tmars@chorushosting.com> (raw)
In-Reply-To: <20020401113232.A32758@asooo.flowerfire.com>
I found the following in our logfiles for one of our servers that has dual
1.1 GHz Pentium processors and running RedHat 7.2 in smp mode.
Apr 21 12:40:35 webu1 kernel: Unable to handle kernel paging request at
virtual address 35e235a8
Apr 21 12:40:35 webu1 kernel: printing eip:
Apr 21 12:40:35 webu1 kernel: c013d2a9
Apr 21 12:40:35 webu1 kernel: *pde = 00000000
Apr 21 12:40:35 webu1 kernel: Oops: 0000
Apr 21 12:40:35 webu1 kernel: CPU: 0
Apr 21 12:40:35 webu1 kernel: EIP: 0010:[fput+9/224]
Apr 21 12:40:35 webu1 kernel: EIP: 0010:[<c013d2a9>]
Apr 21 12:40:35 webu1 kernel: EFLAGS: 00010286
Apr 21 12:40:35 webu1 kernel: eax: 35e235a0 ebx: 35e235a0 ecx: c215e3e4
edx: c215e3e4
Apr 21 12:40:35 webu1 kernel: esi: e0dd1000 edi: e0dd1008 ebp: eaac0c00
esp: f5a85f50
Apr 21 12:40:35 webu1 kernel: ds: 0018 es: 0018 ss: 0018
Apr 21 12:40:35 webu1 kernel: Process mysqld (pid: 1423, stackpage=f5a85000)
Apr 21 12:40:35 webu1 kernel: Stack: c0261f40 c1ca0a90 00000246 00000286
e0dd1008 e0dd1000 e0dd1008 eaac0c00
Apr 21 12:40:35 webu1 kernel: c014ce75 ef8a0000 f5a85fa8 eaac0c00
c014dbdd f5a85fa8 f5a85fa8 4180b000
Apr 21 12:40:35 webu1 kernel: 00000001 00000000 f5a85fa8 eaac0c00
fffffffc 00000000 00000000 e0dd1000
Apr 21 12:40:35 webu1 kernel: Call Trace: [poll_freewait+53/80]
[sys_poll+909/928] [system_call+51/56]
Apr 21 12:40:35 webu1 kernel: Call Trace: [<c014ce75>] [<c014dbdd>]
[<c010716b>]
Apr 21 12:40:35 webu1 kernel:
Apr 21 12:40:35 webu1 kernel: Code: 8b 6b 08 8b 73 0c 8b 7d 08 f0 ff 4b 14
0f 94 c0 84 c0 0f 84
Is the message above a result of running out of memory?
Tony
parent reply other threads:[~2002-04-21 21:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20020401113232.A32758@asooo.flowerfire.com>]
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=NNEEKDPGACDAGGDNNHOOMEGFFEAA.tmars@chorushosting.com \
--to=tmars@chorushosting.com \
--cc=linux-smp@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