[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Problems with merlot* AMD Opteron 6376 systems (Was Re: stable trees (was: [xen-4.2-testing test] 58584: regressions))
- To: "Aravind Gopalakrishnan" <Aravind.Gopalakrishnan@xxxxxxx>, <suravee.suthikulpanit@xxxxxxx>, "Ian Campbell" <ian.campbell@xxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Fri, 26 Jun 2015 15:52:57 +0100
- Cc: Lars Kurth <lars.kurth@xxxxxxxxxx>, StefanoStabellini <stefano.stabellini@xxxxxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, Dario Faggioli <dario.faggioli@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
- Delivery-date: Fri, 26 Jun 2015 14:53:09 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 26.06.15 at 16:34, <ian.campbell@xxxxxxxxxx> 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
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
