From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: cperkins@OCF.Berkeley.EDU
Subject: Re: x86_64 invalid opcode
Date: Thu, 04 May 2006 17:43:41 -0600 [thread overview]
Message-ID: <445A91AD.3010908@shaw.ca> (raw)
In-Reply-To: <68Sjn-7MD-19@gated-at.bofh.it>
chris perkins wrote:
> hi - i'm running the 2.6.16.13 x86_64 kernel on an athlon 64 and
> periodically get invalid opcode and general protection faults. the
> system continues to run for about 10 minutes following this and then
> crashes. i've had similar problems with previous 2.6 kernels but
> unfortunately don't have a capture of the output. below is the syslog
> output and my .config... has anyone else seen anything similar?
> thanks,
> chris perkins
This could be caused by problems with your RAM, have you tried running
memtest86?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-05-04 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <68Sjn-7MD-19@gated-at.bofh.it>
2006-05-04 23:43 ` Robert Hancock [this message]
2006-05-04 20:00 x86_64 invalid opcode chris perkins
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=445A91AD.3010908@shaw.ca \
--to=hancockr@shaw.ca \
--cc=cperkins@OCF.Berkeley.EDU \
--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