The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xen (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: xen (Ubuntu Quantal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: xen (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifications about
I went through changes between 3.2 and 3.3, but from the descriptions nothing
was really jumping out. So I fear the only way to isolate it will be a bisect.
It will be taking its time since usually there are about 10-12 iterations if
3.3-rc1 is the first one working. Might be a bit less if it wo
Ok, so something between 3.2 and 3.3 which obviously has not been
considered as stable material. As said, it usually turns out that
3.3-rc1 is ok, too. I'd love to be wrong there but...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/ v3-3-precise boots
but v3-2-39-precise does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clippe
3.3 and 3.4 both boot... Am trying some earlier kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifications about this bug
So the fix is rather somewhere before... still has v3,3 and v3.4 at
least...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifica
Unfortunately -rc1, -rc2 and -rc3 all boot on my machine... Sorry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/470
Title:
Crash in dom0 when accessing clipped RAM
To manage notifications abou
Hm, one change to think of would be 2e2fb75475c2fc74c98100f1468c8195fee49f3b
xen/setup: Populate freed MFNs from non-RAM E820 entries and gaps to E820 RAM
That would be in with v3.5-rc3. A final proof usually needs to bisect
it. To narrow down the attempts there you could try various kernels fro
The LTS backport kernels are mainly hardware enablement options. But the
Precise kernel is still a supported option, so if possible we want bugs
fixed (if possible == if not requiring half of the next kernel
backported).
OK, so that range appears in the 1-1 mappings but seems not to be freed
and t
And the xen dmesg
** Attachment added: "working_xen_dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/470/+attachment/3534589/+files/working_xen_dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Okay - I wasn't sure that it was so clear! I thought there was a plan to
backport the quantal kernel to precise as the LTS, but anyway!
See attached for the xen dmesg and host dmesg from a successful boot
with original Xen and quantal kernel.
** Attachment added: "working_dmesg.log"
https://b
The question can clearly answered with yes. The slight confusion was
that during all the comments it was not clear to me whether the Quantal
kernel was indeed used without or with the dom0_mem option. I took
Mike's comment as if it was only *with* this option. Personally I find
the usage of "unusab
We've already identified that a quantal development kernel (linux-
image-3.5.0-22-generic) works with no dom0_mem option, so I imagine that
the latest kernel would also work - is there a particular version that
you'd like me to try?
If xen upstream thinks the kernel should be fixed, then is questi
One thing for clarification. When using the unpatched xen-hypervisor and
a recent kernel (like v3.8) from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and no dom0_mem option on the affected machine. Does that
still crash the same?
--
You received this bug notification because you are a member
In upstream discussion this seems to be seen as something that should
rather get fixed in the kernel and not the hypervisor. I will see what
ideas come up there and get back with an updated change to test. Stay
tuned...
--
You received this bug notification because you are a member of Ubuntu
Bugs
17 matches
Mail list logo
