* Kernel panic problem in 2.4.7
@ 2001-08-17 14:36 오늘과내일 홍석범
0 siblings, 0 replies; 4+ messages in thread
From: 오늘과내일 홍석범 @ 2001-08-17 14:36 UTC (permalink / raw)
To: linux-kernel
[-- 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_âØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣømSåy«\x1eæ¶\x17
\x01\x06ÛiÿÿðÃ\x0fí»\x1fè®\x0fåi\x7f
^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <no.id>]
* Re: Kernel panic problem in 2.4.7
[not found] <no.id>
@ 2001-08-17 14:51 ` Alan Cox
2001-08-17 15:11 ` Alan Cox
1 sibling, 0 replies; 4+ messages in thread
From: Alan Cox @ 2001-08-17 14:51 UTC (permalink / raw)
To: 오늘과내일 홍석범
Cc: linux-kernel
>
> SGVsbG8uLiBBbGwNCg0KSSBoYXZlIG9wZXJhdGVkIFJlZGhhdCA2LjIgYmFzZWQgc3lzdGVtKGtl
> cm5lbCAyLjQuNykgIHdoaWNoIGlzIER1YWwgQ1BVIGFuZCA1MTJNIFJhbS4NCg0KQSBmZXcgZGF5
> cyBhZ28sIHRoaXMgc3lzdGVtIGlzIGRvd24gYW5kIHRoZSBtZXNzYWdlcyBsaWtlIGJlbG93Lg0K
> DQpKdWwgMjIgMTQ6NTc6NDUgd3d3IGtlcm5lbDogS2VybmVsIHBhbmljOiBDUFUgY29udGV4dCBj
> b3JydXB0DQpKdWwgMjUgMTk6MjU6MzAgd3d3IGtlcm5lbDogS2VybmVsIHBhbmljOiBDUFUgY29u
> dGV4dCBjb3JydXB0DQpKdWwgMjcgMjM6NDM6MjIgd3d3IGtlcm5lbDogS2VybmVsIHBhbmljOiBD
> UFUgY29udGV4dCBjb3JydXB0DQoNCnRoaXMgbWFpbGxpbmcgbGlzdCBzYXkgdGhhdCB0aGlzIGlz
> IENQVSBQcm9ibGVtKG92ZXJjbG9ja2luZy4uLi5idXQgaXQgaXNuJ3QpLg0KU28gSSBjaGFuZ2Vk
> IG90aGVyIENQVXMgdGhhdCBJIHRoaW5rICBubyBwcm9ibGVtLg0KDQpCdXQgYSBmZXcgZGF5cyBs
> YXRlci4ga2VybmVsIHBhbmljIG9jY3VyZWQgYWdhaW4uDQooVGhlIHN5c3RlbSBpcyAyLjQuNykN
> CnRoZSBtZXNzYWdlcyB3YXMgDQoNCktlcm5lbCBwYW5pYzpBaWVlLCBraWxsaW5nIGludGVycnVw
> dCBoYW5kbGVyDQpJbiBpbnRlcnJ1cHQgaGFuZGxlciAtIG5vdCBzeW5jaW5nDQoNClRoaXMgbWVz
> c2FnZSBpcyBvY2N1cmVkIHdoZW4gdGhlIHN5c3RlbSdzIGxvYWQgYXZlcmFnZSBpcyBhIGJpdCBo
> aWdoLg0KKFdoZW4gSSBLZXJuZWwgY29tcGlsZSBvciBwYWNraW5nIHdpdGggdGFyLi4gc29tdGhp
> bmcgbGlrZSB0aGF0Li4pDQoNCkkgc2VhcmNoZWQgYWxsIGxpc3RzLCBCdXQgSSBjb3VsZG4ndCBm
> aW5kIHRoZSAicmVhc29uIiBhbmQgImFuc3dlciIuDQpJIHdvdWxkIGxpa2UgdG8ga25vdyB0aGUg
> cmVhc29uIGFuZCBhbnN3ZXIuDQoNClBsZWFzZSBnaXZlIG1lIHNvbWUgYWR2aWNlIGFib3V0IHRo
> ZXNlIHByb2JsZW1zLg0KDQogDQogVGhhbmtzIGZvciB5b3VyIGhlbHAuDQogIA0KIA0K
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel panic problem in 2.4.7
[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
1 sibling, 1 reply; 4+ messages in thread
From: Alan Cox @ 2001-08-17 15:11 UTC (permalink / raw)
To: 오늘과내일 홍석범
Cc: linux-kernel
If your cpu context corrupt is with a machine check exception report then
your processor took an internal fault reporting trap. So its not a happy
bit of silicon I suspect - be it overclocked, overheated, or even faulty.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel panic problem in 2.4.7
2001-08-17 15:11 ` Alan Cox
@ 2001-08-17 15:23 ` Alan Cox
0 siblings, 0 replies; 4+ messages in thread
From: Alan Cox @ 2001-08-17 15:23 UTC (permalink / raw)
To: Alan Cox
Cc: 오늘과내일 홍석범,
linux-kernel
> If your cpu context corrupt is with a machine check exception report then
> your processor took an internal fault reporting trap. So its not a happy
> bit of silicon I suspect - be it overclocked, overheated, or even faulty.
Beware beta versions of editors 8)
If your CPU context corrupt message is appearing with a machine check
exception report, then you processor took an internal fault reporting trap.
So it's not a happy piece of silicon I suspect - be it overclocked,
overheated or even faulty.
The machine check numbers it prints can be looked up in the processor
manuals to decode the type of fault.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-08-17 15:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-17 14:36 Kernel panic problem in 2.4.7 오늘과내일 홍석범
[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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).