All of lore.kernel.org
 help / color / mirror / Atom feed
From: "F. P. Beekhof" <fpbeekhof@gmail.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Mikael Pettersson <mikpe@it.uu.se>,
	linux-ide@vger.kernel.org
Subject: Re: Machine check exception
Date: Wed, 27 Jul 2011 23:30:08 +0200	[thread overview]
Message-ID: <4E308360.8080302@gmail.com> (raw)
In-Reply-To: <4E307AF3.40109@gmail.com>

Note: after a suspend/resume cycle, the register value is back at 8, so 
I have to run the commands again to set it to 100008

# rdmsr -x 0xc001001f
100008
(suspend / resume)
# rdmsr -x 0xc001001f
8


On 07/27/2011 10:54 PM, F. P. Beekhof wrote:
> On 07/27/2011 07:03 PM, Borislav Petkov wrote:
>> On Wed, Jul 27, 2011 at 05:31:56PM +0200, F. P. Beekhof wrote:
>>> $ sudo rdmsr 0xc001001f
>>> 8
>>>
>>> Is there anything else I can do ?
>>
>> Ok, I'd like you to try something out:
>>
>> Boot into runlevel 1: you need this because you get the MCE before
>> you've done starting apache. For that, add a "1" to your kernel command
>> line and boot. When you get the prompt, type in your root pwd and do
>>
>> wrmsr 0xc001001f $(( $(rdmsr -u 0xc001001f) | (1<< 20) ))
>>
>> Then do
>>
>> rdmsr -x 0xc001001f
>>
>> to verify that the write has succeeded. It should say
>>
>> 0x00100008.
>>
>> then exit the prompt to continue to runlevel 2 to see whether this
>> setting fixes your MCE issue.
>>
>> This is for now,
>> thanks.
>>
>
> Ok, writing the register worked.
>
> Now we just need to wait, these crashes occur at random moments.
> Sometimes there is 5 minutes between two crashes, sometimes a few days...
>
> I'll post an update as soon as I have more information.
>
> Thanks for helping out!
>


  reply	other threads:[~2011-07-27 21:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 11:05 Machine check exception F. P. Beekhof
2011-07-27 13:03 ` Borislav Petkov
2011-07-27 15:31   ` F. P. Beekhof
2011-07-27 17:03     ` Borislav Petkov
2011-07-27 20:54       ` F. P. Beekhof
2011-07-27 21:30         ` F. P. Beekhof [this message]
2011-07-28  7:47           ` Borislav Petkov
2011-07-31  8:22             ` F. P. Beekhof
2011-07-31 12:09               ` Borislav Petkov
2011-07-31 15:56                 ` F. P. Beekhof
2011-08-01  8:48                   ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2008-10-05 17:41 Machine Check Exception Matteo Croce
2003-12-03 11:05 machine check exception Nicholas Mucci
2003-12-03 13:05 ` Russell Coker
2003-12-03 13:19   ` Stephen Smalley
2002-12-15 20:22 Machine Check Exception Felix von Leitner
2002-12-15 20:39 ` Jan-Benedict Glaw
2002-12-16 19:55 ` Felipe W Damasio

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=4E308360.8080302@gmail.com \
    --to=fpbeekhof@gmail.com \
    --cc=bp@amd64.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.