mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "오늘과내일 홍석범" <antihong@tt.co.kr>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel panic problem in 2.4.7
Date: Fri, 17 Aug 2001 23:36:35 +0900	[thread overview]
Message-ID: <000e01c1272a$047b8c80$2e402fd3@tt.co.kr> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="ks_c_5601-1987", Size: 1148 bytes --]

Hello.. All

I have operated Redhat 6.2 based system(kernel 2.4.7)  which is Dual CPU and 512M Ram.

A few days ago, this system is down and the messages like below.

Jul 22 14:57:45 www kernel: Kernel panic: CPU context corrupt
Jul 25 19:25:30 www kernel: Kernel panic: CPU context corrupt
Jul 27 23:43:22 www kernel: Kernel panic: CPU context corrupt

this mailling list say that this is CPU Problem(overclocking....but it isn't).
So I changed other CPUs that I think  no problem.

But a few days later. kernel panic occured again.
(The system is 2.4.7)
the messages was 

Kernel panic:Aiee, killing interrupt handler
In interrupt handler - not syncing

This message is occured when the system's load average is a bit high.
(When I Kernel compile or packing with tar.. somthing like that..)

I searched all lists, But I couldn't find the "reason" and "answer".
I would like to know the reason and answer.

Please give me some advice about these problems.

 
 Thanks for your help.
  
 
ý:.žË›±Êâmçë¢kaŠÉb²ßìzwm…ébïîžË›±Êâmébžìÿ‘êçz_âžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣømšSåy«\x1e­æ¶\x17…\x01\x06­†ÛiÿÿðÃ\x0fí»\x1fè®\x0få’i\x7f

             reply	other threads:[~2001-08-17 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 14:36 오늘과내일 홍석범 [this message]
     [not found] <no.id>
2001-08-17 14:51 ` Alan Cox
2001-08-17 15:11 ` Alan Cox
2001-08-17 15:23   ` Alan Cox

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='000e01c1272a$047b8c80$2e402fd3@tt.co.kr' \
    --to=antihong@tt.co.kr \
    --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®