On 05/06/2016 04:51 PM, Joseph Salisbury wrote:
> Thomas' patch does resolve the bug. The cpuid info can be seen here:
> https://launchpadlibrarian.net/258234267/cpuid_full.txt
Any chance you could post it raw (cpuid -1 -r)?
Thanks.
-boris
--
You received this bug notification because you are
On 05/06/2016 03:38 PM, Joseph Salisbury wrote:
> On 05/06/2016 03:13 PM, Boris Ostrovsky wrote:
>> On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
>>>
>>> Yuck. That dies with a divide error. And that looks like XEN is supplying
>>> crap
>>> data in
On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
> On Fri, 6 May 2016, Joseph Salisbury wrote:
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
>>
It is now in mainline, commit fd8b79511349.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in Ubuntu:
I was waiting for this patch to be pulled into the mainline before
posting a pointer/commitID here. It's not there yet.
But yes, you need that commit (on top of 3dcf63677d4e) to make kernel
shut up.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hmm, yes, the patch may not work if something (AWS, I guess) keeps
requesting to balloon memory.
Can someone try the attached patch (on top of David's)? I only compile-
tested it.
** Patch added: cancel_balloon.patch
Actually, this (v2) is a slightly better one to try.
** Patch added: cancel_balloon_v2.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4223585/+files/cancel_balloon_v2.patch
--
You received this bug notification because you are a member of Kernel
Packages,
I am not sure the bug should be closed. David's fix made system behavior
tolerable to users (because the error is now only reported once) but the
problem is still there. If possible I'd suggest lowering bug's priority
but keeoping it open.
--
You received this bug notification because you are a
No fix (from me, that is)
I need to be able to reproduce this and this appears to only be
happening in AWS environment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
Matt, can you post config file that you used? I tried a few different
configurations and (again) could not reproduce this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
I am using 4.2 stable tree, configured with default parameters (i.e. no
options to ./configure script):
[root@ovs103 install]# xm info
host : ovs103.us.oracle.com
release: 3.16.0-rc1-pmu-dom0
version: #1 SMP Mon Jul 7 14:09:40 EDT 2014
machine
And this is my guest (14.04 desktop):
Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2
(Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014
(Ubuntu 3.13.0-24.46-generic 3.13.9)
--
You received this bug notification because you are a member of Kernel
So given that you are seeing this on 3.2 guest this would be a different
problem. Having said that, I don't see any errors in dmesg_domu.txt
anyway.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If you don't specify debug and loglevel boot options I think you won't
see these. Of course, the underlying problem would still be there.
Do you observe this on guests with newer kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Can you please post:
1. Guest configuration file
2. boot log from dom0 (please boot loglevel=8)
3. xl dmesg and xl info from dom0
4. boot log from guest (also loglevel=8)
5. dmidecode from guest (I am mostly interested in BIOS object)
-boris
--
You received this bug notification because you
Yes, those would be helpful although now I think understanding EC's BIOS
(seabios I assume?) may be more important. Neither I nor Stefan have
been able to reproduce this problem and it seems that EC does something
in BIOS (and possibly qemu) that may not be available in vanilla Xen,
most
[14Ah 0330 4] Proximity Domain :
[14Eh 0334 2]Reserved1 :
[150h 0336 8] Base Address :0001
[158h 0344 8] Address Length : 1000===
This looks wrong
[160h 0352 4]
This warning implies that SRAT may be wrong. And I just noticed that this may
not be vanilla 4.2:
[0.00] DMI: Xen HVM domU, BIOS 4.2.amazon 01/24/2014
Are we on a custom HVM BIOS? That's where memory is described to domain.
Although NUMA issue may be somewhat orthogonal, it still may
I would like to reproduce this first and for that I will need at least
config file that is used for launching the guest ('memory' and 'maxmem'
for sure but having the whole file would be better) as well as guest's
kernel config file. Knowing what xen boot options are as well as if
there is
And guest kernel config file please.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in Ubuntu:
Confirmed
Can you attach Xen config file and xen boot options?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in
21 matches
Mail list logo
