All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
	Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
	suravee.suthikulpanit@amd.com,
	Ian Campbell <ian.campbell@citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	StefanoStabellini <stefano.stabellini@eu.citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Problems with merlot* AMD Opteron 6376 systems (Was Re: stable trees
Date: Fri, 26 Jun 2015 15:36:11 -0400	[thread overview]
Message-ID: <558DA9AB.5060808@oracle.com> (raw)
In-Reply-To: <558D8369020000780008A5E4@mail.emea.novell.com>

On 06/26/2015 10:52 AM, Jan Beulich wrote:
>>>> On 26.06.15 at 16:34, <ian.campbell@citrix.com> wrote:
>> I did this using rdmsr from mst-tools instead, running on a native
>> kernel gave:
>>
>> # for i in $(seq 0 31) ;do rdmsr -p $i MSR_K8_TOP_MEM2; done
>> 0
>> [...]
>> 0

Is MSR_K8_TOP_MEM2 defined somewhere in the shell?

Just to make sure, could you use explicit address, i.e.

     for i in $(seq 0 31) ;do rdmsr -p $i 0xc001001d; done

(and if they are still all zeroes, can you read 0xc0010010 (SYSCFG) as 
well?)

-boris


> Uniformly uncachable for everything above 4Gb then. And I suppose
> you already checked that there's no BIOS update available?
>
> I'm not sure if it would be reasonable for us to work around this.
> Suravee, Aravind - do you (or colleagues of yours) have any
> experience with systems mis-configured like this one?
>
> Otoh I'm then pretty confused by your E820 clipping experiment not
> having yielded any better results. I'm starting to suspect two
> problems...
>
> Jan
>

  parent reply	other threads:[~2015-06-26 19:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16  3:43 [xen-4.2-testing test] 58584: regressions - trouble: blocked/broken/fail/pass osstest service user
2015-06-17  8:53 ` stable trees (was: [xen-4.2-testing test] 58584: regressions) Jan Beulich
2015-06-17 10:26   ` Ian Jackson
2015-06-17 13:16     ` Stefano Stabellini
2015-06-18 11:37     ` Jan Beulich
2015-06-18 14:22       ` Ian Campbell
2015-06-19  9:51         ` Jan Beulich
2015-06-19 11:07           ` Ian Campbell
2015-06-24  9:06             ` Ian Campbell
2015-06-24  9:38               ` Problems with merlot* AMD Opteron 6376 systems (Was Re: stable trees (was: [xen-4.2-testing test] 58584: regressions)) Ian Campbell
2015-06-24 12:29                 ` Dario Faggioli
2015-06-24 12:41                   ` Jan Beulich
2015-06-24 13:15                     ` Dario Faggioli
2015-06-24 13:28                       ` Jan Beulich
2015-06-24 13:54                         ` Dario Faggioli
2015-06-26 10:37                 ` Ian Campbell
2015-06-26 10:49                   ` Jan Beulich
2015-06-26 11:16                     ` Ian Campbell
2015-06-26 12:37                       ` Ian Campbell
2015-06-26 12:59                         ` Jan Beulich
2015-06-26 14:44                           ` Ian Campbell
2015-06-26 14:53                             ` Jan Beulich
2015-06-26 12:20                   ` Jan Beulich
2015-06-26 14:34                     ` Ian Campbell
2015-06-26 14:52                       ` Jan Beulich
2015-06-26 16:23                         ` Ian Campbell
2015-06-26 19:36                         ` Boris Ostrovsky [this message]
2015-06-26 20:07                           ` Problems with merlot* AMD Opteron 6376 systems (Was Re: stable trees Ian Campbell
2015-06-29 10:23                             ` Ian Campbell
2015-06-29 13:13                               ` Boris Ostrovsky
2015-07-06  9:38                                 ` Jan Beulich
2015-06-24  9:45               ` stable trees (was: [xen-4.2-testing test] 58584: regressions) Jan Beulich

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=558DA9AB.5060808@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xenproject.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 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.