2.4.18-pre8-K2: Kernel panic: CPU context corrupt

2.4.18-pre8-K2: Kernel panic: CPU context corrupt

Post by Dieter Nütze » Sun, 10 Feb 2002 07:50:11






> >  > Feb  7 23:45:31 steel kernel: CPU 0: Machine Check Exception:
> >  > 0000000000000004
> >  > Feb  7 23:45:31 steel kernel: Bank 4: b200000000040151
> >  > Feb  7 23:45:31 steel kernel: Kernel panic: CPU context corrupt

> >  Machine checks are indicative of hardware fault.
> >  Overclocking, inadequate cooling and bad memory are the usual causes.

> no overclocking, memtest passed (1 pass, 1 hour), native intel cooler.
> Space radiation, maybe 8)

We run it over night in our lab, to be sure...

Good luck!

-Dieter
--
Dieter Ntzel
Graduate Student, Computer Science

University of Hamburg

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.18-pre8-K2: Kernel panic: CPU context corrupt

Post by Pavel Mache » Tue, 12 Feb 2002 06:40:09


Hi!

Quote:>  > Feb  7 23:45:31 steel kernel: CPU 0: Machine Check Exception: 0000000000000004
>  > Feb  7 23:45:31 steel kernel: Bank 4: b200000000040151
>  > Feb  7 23:45:31 steel kernel: Kernel panic: CPU context corrupt

>  Machine checks are indicative of hardware fault.
>  Overclocking, inadequate cooling and bad memory are the usual
> causes.

Maybe you should print something like

Machine Check Exception: .... (hardware problem!)

so that we get less reports like this?
                                                                        Pavel
--
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.18-pre8-K2: Kernel panic: CPU context corrupt

Post by Dave Jone » Tue, 12 Feb 2002 06:50:10



> >  > Feb  7 23:45:31 steel kernel: CPU 0: Machine Check Exception: 0000000000000004
> >  > Feb  7 23:45:31 steel kernel: Bank 4: b200000000040151
> >  > Feb  7 23:45:31 steel kernel: Kernel panic: CPU context corrupt
> >  Machine checks are indicative of hardware fault.
> >  Overclocking, inadequate cooling and bad memory are the usual
> > causes.
> Maybe you should print something like
> Machine Check Exception: .... (hardware problem!)
> so that we get less reports like this?

When I get around to finishing the diagnosis tool, I'll add
something like "Feed to decodemca for more info".

--
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.18-pre8-K2: Kernel panic: CPU context corrupt

Post by Alan Co » Tue, 12 Feb 2002 10:00:11


Quote:> > Maybe you should print something like
> > Machine Check Exception: .... (hardware problem!)
> > so that we get less reports like this?

> When I get around to finishing the diagnosis tool, I'll add
> something like "Feed to decodemca for more info".

For a lot of processors the MCE values are not documented. Strangely for
once Intel are the good guys and AMD seem to be sitting on the docs.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Very High Load on Disk Activity in 2.4.18 (and 2.4.18-pre8)

Hello,

I'm experiencing a strange effect. As soons as there is some higher disk
activity (untarring the linux kernel is enough, which really should be no
problem) the system load gets really high (some times over 10) but the CPU
is 100% idle (reported by top).

Usually the system freezes for some minutes (but is still replying to pings)
and is after this period (when disk I/O is finished) fully usable again.

There are no error messages in all logfiles and nothing seems to be wrong
except of this _really_ annoying 3-10 minute freezes under high activity.

I definatly have no idea what to do. I'm very shure that my SCSI-wiring
and the other hardware ist ok. There a no error messages or warnings in
"dmesg" or the normal system logs.I run various Hardwaretest, all are ok.

I read about similar problems in earlier Version of 2.4.x Kernels but these
are reported to be fixed. Are any Problems in the Mylex drivers or the
kernels VM known (and hopefully work arounds) that can cause this
behaviour?

thanks in advance and sorry for my bad englisch.

regards

jan schreiber

More info about the machine:

- Mylex Accleraid 352 (flashed to latest firmware)
- Intel Pentium III 1,2 GHz, 512 MB Ram, Intel i815 Chipset
- 10 36 GB SCSI drives connected (8 on Channel 0, 2 on channel 1), no other
devices connected
- Build one RAID-5 Drive out of 9 disks, the 10 disk is spare
- three primary Partitons (512 MB swap, 2 GB system , rest data partiton
(approx 270 Gb)
- Running SuSE 8.0 Pro
- Kernel 2.4.18 (from suse, built a new vanilla 2.4.18 and pre8 with same
results)
- using reiserfs 3.6 on all Partitons (except swap of course)

Mit freundlichen Gruessen
cionix GmbH

Jan Schreiber
Gesch?ftsfhrer | chief executive officer

_____________________________________
cionix GmbH
Bredower Str. 45       D-14612 Falkensee

Tel: [+49] ?3322.2336-10
Fax: [+49] ?3322.2336-11


_____________________________________

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. floppy linux

3. USB lockup in 2.4.18-pre8 <-- typo 2.4.19-pre8

4. looking for the Solaris 2.x System Administration I class material

5. 2.4.18-pre8 + 2.4.17-pre8-ac3 + rmap12c + XFS Results

6. Linux restricted shell (rsh)

7. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5

8. FAQ on curses

9. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5 (2nd try =) )

10. fs/ufs/super.c, kernel 2.4.18-pre8

11. RHN Update to Kernel 2.4.18-24 Kernel Panic

12. BANK 4: b2000000000040151<0> kernel panic: CPU context corrupt