Re: Kernel panic: CPU context corrupt
Selon Thomas CLavier <tclavier@partner.auchan.com>:
| Bonjour,
Salut !
| Depuis quelques jours, sur un serveur en sarge à jour, je trouves
| dans
| la console ce genre de messages :
|
| <verbatim>
| Message from syslogd@localhost at Thu Feb 3 08:50:03 2005 ...
| localhost kernel: CPU 0: Machine Check Exception: 0000000000000004
Erf :)
Tu as quel noyau, sur quel type de CPU ?
| Message from syslogd@localhost at Thu Feb 3 08:50:03 2005 ...
| localhost kernel: Bank 1: d400400000000152 at 000000001f8247c0
|
| Message from syslogd@localhost at Thu Feb 3 08:50:03 2005 ...
| localhost kernel: Bank 2: f60020000000017a at 000000001ee702c0
|
| Message from syslogd@localhost at Thu Feb 3 08:50:03 2005 ...
| localhost kernel: Kernel panic: CPU context corrupt
| Connection to 192.168.12.1 closed by remote host.
| Connection to 192.168.12.1 closed.
| </verbatim>
|
| En fait, la machine reboot toute seul dans les minutes qui suivent le
| kernel panic.
|
| Comment faire pour tracer ce qui merde et savoir quelle appli génère
| cette erreur ?
find /usr/src/linux/ -type f -exec grep -H "Machine Check Exception"
{} \;
Un extrait du Kconfig pour i386 :
Machine Check Exception support allows the processor to notify
the
kernel if it detects a problem (e.g. overheating, component
failure).
The action the kernel takes depends on the severity of the
problem,
ranging from a warning message on the console, to halting the
machine.
Your processor must be a Pentium or newer to support this -
check the
flags in /proc/cpuinfo for mce. Note that some older Pentium
systems
have a design flaw which leads to false MCE events - hence MCE
is
disabled on all P5 processors, unless explicitly enabled with
"mce"
as a boot argument. Similarly, if MCE is built in and creates
a
problem on some new non-standard machine, you can boot with
"nomce"
to disable it. MCE support simply ignores non-MCE processors
like
the 386 and 486, so nearly everyone can say Y here.
Mais il peut y avoir d'autres trucs...
Thomas.
Reply to: