Re: AMD64 Machine hardlocks when using memset

[Paul Jackson <pj@engr.sgi.com>]

Yup - kills my x86_64 too.  I can't stay up for half a minute.
I got a couple of Oops

  Unable to handle kernel paging request at 0000000000002730 RIP:

  Unable to handle kernel paging request at ffff81773ffc6918 RIP:

The first try ended with a sudden reboot.  The second time, I ctrl-C'd
out while I still had a responsive system.

I thought it might be a CPU temperature issue, so downloaded XMBmon
"Mother Board Monitor Program for X Window System", and hacked the
command line mbmon in it to add this memset loop and report the CPU temp
each time around the loop.

My CPU Temp went from its usual 39 C idle, to 45 C during the memset
loop, which are typical temperatures for this PC.  No problem there.

In a couple more tries, I got:
  knotify killed with a SIGSEGV
  artsd killed with a SIGSEGV
  a hard lockup, requiring the big red button
  a second oops at the same ffff81773ffc6918 as above.

My CPU, from /proc/cpuinfo, is:
model name      : AMD Athlon(tm) 64 Processor 3500+

My mainboard is an MSI K8N Neo2 Platinum.  I have 1 GByte of
Corsair XMS DDR400 memory.

I am not overclocking and I am running with standard voltages.

This is on a 2.6.11-rc5 kernel, though I doubt that matters.
I'm guessing it's hardware.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
-
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/