public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: 3.2-rc2 freezes on boot for AMD K6 - bisected to commit bcb80e53877c2045d9e52f4a71372c3fe6501f6f
Date: Wed, 30 Nov 2011 01:09:57 -0600	[thread overview]
Message-ID: <4ED5D6C5.5050704@lwfinger.net> (raw)
In-Reply-To: <4ED5C640.8030102@linux.vnet.ibm.com>

On 11/29/2011 11:59 PM, Srivatsa S. Bhat wrote:
> On 11/30/2011 10:24 AM, Larry Finger wrote:
>
>> I have an ancient laptop with an AMD-K6 CPU that freezes on boot with
>> 3.2-rc2. The problem was bisected to commit bcb80e53877c2.
>>
>> The cpuinfo for this box is:
>>
>>>> cpu.1: cpuinfo
>> ----- /proc/cpuinfo -----
>>    processor     : 0
>>    vendor_id     : AuthenticAMD
>>    cpu family    : 5
>>    model         : 8
>>    model name    : AMD-K6(tm) 3D processor
>>    stepping      : 12
>>    cpu MHz               : 428.804
>>    cache size    : 64 KB
>>    fdiv_bug      : no
>>    hlt_bug               : no
>>    f00f_bug      : no
>>    coma_bug      : no
>>    fpu           : yes
>>    fpu_exception : yes
>>    cpuid level   : 1
>>    wp            : yes
>>    flags         : fpu vme de pse tsc msr cx8 pge mmx syscall 3dnow
>> k6_mtrr up
>>    bogomips      : 857.60
>>    clflush size  : 32
>>    cache_alignment       : 32
>>    address sizes : 32 bits physical, 32 bits virtual
>>    power management:
>>
>> ----- /proc/cpuinfo end -----
>>
>> This patch is quite simple, thus it appears that rdmsr() is OK, but that
>> rdmsr_safe() is not.
>>
>> I am happy to provide any other info regarding this box.
>>
>
>
> Hi Larry,
>
> Can you please try out the patch posted in
> https://lkml.org/lkml/2011/11/28/178 ?
>
> This patch will be available in mainline kernel from -rc4.
> https://lkml.org/lkml/2011/11/28/457

Srivatsa,

Thanks for the reference. That patch does fix my problem. Too bad that the bad 
commit was not in the subject of that other thread so that I could have found it 
with Google.

Larry


  reply	other threads:[~2011-11-30  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30  4:54 3.2-rc2 freezes on boot for AMD K6 - bisected to commit bcb80e53877c2045d9e52f4a71372c3fe6501f6f Larry Finger
2011-11-30  5:59 ` Srivatsa S. Bhat
2011-11-30  7:09   ` Larry Finger [this message]
2011-12-03 20:43     ` Larry Finger
2011-12-03 23:07       ` Linus Torvalds
2011-12-04  3:15         ` Larry Finger
2011-12-04  6:05         ` Bob Tracy
2011-12-04 13:09         ` Borislav Petkov
2011-12-05  7:28         ` Ingo Molnar
2011-12-05 17:40 ` [tip:x86/urgent] x86: Document rdmsr_safe restrictions tip-bot for Borislav Petkov

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=4ED5D6C5.5050704@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=borislav.petkov@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    /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