mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@engr.sgi.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD64 Machine hardlocks when using memset
Date: Wed, 30 Mar 2005 23:41:33 -0800	[thread overview]
Message-ID: <20050330234133.59fdafdf.pj@engr.sgi.com> (raw)
In-Reply-To: <424B7ECD.6040905@shaw.ca>

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

  parent reply	other threads:[~2005-03-31  7:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3NTHD-8ih-1@gated-at.bofh.it>
     [not found] ` <3NVqb-1iK-33@gated-at.bofh.it>
2005-03-31  4:32   ` Robert Hancock
2005-03-31  4:38 ` Robert Hancock
2005-03-31  7:25   ` Denis Vlasenko
2005-03-31  8:15     ` Paul Jackson
2005-03-31  9:37       ` Philip Lawatsch
2005-03-31 10:15         ` Paul Jackson
2005-03-31  7:41   ` Paul Jackson [this message]
2005-03-31 11:40     ` Mikael Pettersson
2005-03-31 18:47       ` Paul Jackson
     [not found] ` <3O99L-40N-9@gated-at.bofh.it>
2005-04-01  4:37   ` Robert Hancock
2005-04-01 10:41     ` Denis Vlasenko
2005-04-01 17:27     ` Ray Lee
2005-04-01 19:14       ` Philip Lawatsch
     [not found] <3Ojst-4kX-19@gated-at.bofh.it>
     [not found] ` <3OGIo-7oY-13@gated-at.bofh.it>
     [not found]   ` <3OGIo-7oY-15@gated-at.bofh.it>
     [not found]     ` <3OGIo-7oY-17@gated-at.bofh.it>
     [not found]       ` <3OGIo-7oY-11@gated-at.bofh.it>
     [not found]         ` <3OIh7-cc-1@gated-at.bofh.it>
     [not found]           ` <3OITV-AR-3@gated-at.bofh.it>
     [not found]             ` <3PxjH-812-3@gated-at.bofh.it>
2005-04-06  4:05               ` Robert Hancock
2005-04-06  7:02                 ` Rafael J. Wysocki
2005-04-06  9:31                   ` Philip Lawatsch
2005-04-06 10:59                 ` Philip Lawatsch
2005-04-06 11:15                   ` Arjan van de Ven
2005-04-06 11:22                   ` Philip Lawatsch
     [not found] <3NZDp-4yY-7@gated-at.bofh.it>
     [not found] ` <3NZN4-4EZ-1@gated-at.bofh.it>
     [not found]   ` <3O2rK-6MU-19@gated-at.bofh.it>
     [not found]     ` <3O34n-7oN-19@gated-at.bofh.it>
     [not found]       ` <3O4tp-8tL-3@gated-at.bofh.it>
2005-04-01  1:33         ` Robert Hancock
     [not found] ` <3OmgF-6HV-17@gated-at.bofh.it>
     [not found]   ` <3OmgF-6HV-15@gated-at.bofh.it>
     [not found]     ` <3Oy8m-74-15@gated-at.bofh.it>
2005-04-02  2:32       ` Robert Hancock
2005-04-02  4:11         ` Paul Jackson
2005-04-02  4:50           ` Robert Hancock
2005-04-04 10:45             ` Alan Cox
2005-04-06  8:47             ` Denis Vlasenko
2005-03-30 22:04 Philip Lawatsch
2005-03-31  0:05 ` Matthias-Christian Ott
2005-03-31 14:45 ` Stelian Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050330234133.59fdafdf.pj@engr.sgi.com \
    --to=pj@engr.sgi.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome