8.0RC2 amd64 - kernel panic running make buildworld

Mark Atkinson atkin901 at gmail.com
Thu Nov 12 15:58:12 UTC 2009

Andriy Gapon wrote:
> on 11/11/2009 22:13 Mark Atkinson said the following:
>> Well, you're about at the point I am now with my HP dl385g5, only
>> turning off superpages would result in a successful buildworld.   Mine
>> would often machine check during gas compilation as well.
> Mark,
> you mentioning MCA was magic moment for me.
> I was debugging a problem which seemed to be quite different, but now I think that
> it converges to the problem discussed in this thread (if indeed it's the same
> problem for all reporters).

I'm not sure it's exactly the same.  I only know a couple of things

- my memory tests good.
- turning off superpages allows this machine to function properly.

I suspect there's a problem with one of the following:

- the bios of my machine
- the on die memory controller/intructions of the cpu
- the motherboard electrical interface to memory or bus in some shape or

> Or perhaps there is something like Event Log in BIOS.  Maybe it
> even gets something useful.
> Could you please check?

Yes.  When you receive a MCE on the HP machines the bios notices and
prints a message on the next bootup, something like "an unhandled memory
error has occured since last power on."

In my current job, which works with hardware, we'll occasionally see
MCEs during development.  It's easy to say the memory is bad, and it is
the first thing we replace to test.  However it can also be the
electrical interface to the hardware which may or may not be
fixable/worked around in firmware.  I have also witnessed the software
initializing or controlling the hardware may result in a unhandled
condition spurring an MCE.

> About my problem - it seems that I was working from the opposite end.  I have been
> using head/CURRENT with pg_ps_enabled=1 for quite a while now.  And then I decided
> to try hw.mca.enabled=1 and after that I started having the same symptoms as
> described here.  Unfortunately, I never did get Machine Check trap, it's always
> something that looks like CPU halt and then reset by watchdog (if it is enabled).
> So, for me:
> superpages and no machine check - works
> machine check and no superpages - works
> machine check and superpages - problem

That's not quite the same for sure, definitely try replacing the memory
first if you haven't already.

All the best,


More information about the freebsd-current mailing list