FYI,
I just confirmed that the 3.5.0-14-generic #19 kernel fixes this issue.
Thanks for your help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered
This bug was fixed in the package linux - 3.5.0-12.12
---
linux (3.5.0-12.12) quantal-proposed; urgency=low
[ Luis Henriques ]
* [Config] Fix typo on control.stub.in
[ Ricardo Salveti de Araujo ]
* [Config] installing omapdrm specific headers for external drivers
- LP:
** Also affects: linux (Ubuntu Quantal)
Importance: Medium
Status: Triaged
** Changed in: linux (Ubuntu Quantal)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Quantal)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
--
You received this bug
@smb @joe
Any news on this bug ? Are we hoping to get that fixed for 12.10 launch
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel
The upstream discussion went stuck on the matter of: why make a
difference between 32bit and 64bit, which nobody could answer. And for
the patch that just makes things right, right now, that got ignored. So
thats the news. There is plumbers coming up soon and I hope that maybe
hpa is there and I
I hope the background was explained well enough in comment #11. For the
experience I just tried a KVM VM 64bit which got 2G of memory. Without the
patch in comment #12 the initial page tables are about 4M big. And neither with
crashkernel= 28M nor with crashkernel=256M I was able to get the
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel panics
To manage notifications about this bug go
Ok, bisection ended up with:
commit 722bc6b16771ed80871e1fd81c86d3627dda2ac8
Author: WANG Cong xiyou.wangc...@gmail.com
Date: Mon Mar 5 15:05:13 2012 -0800
x86/mm: Fix the size calculation of mapping tables
For machines that enable PSE, the first 2/4M memory region still uses
So lets see what upstream thinks about this...
** Patch added: 0001-x86-mm-Limit-2-4M-size-calculation-to-x86_32.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1022561/+attachment/345/+files/0001-x86-mm-Limit-2-4M-size-calculation-to-x86_32.patch
--
You received this bug
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel panics
To manage notifications about this bug go to:
While this probably is not helping much to find the issue, I want to add
that I was able to get a panic once when kexec'ing into the dump kernel
(had to set nomodeset to avoid higher resolution textmode):
PANIC: early exception 0d rip 10:8103ee66 error 77b cr2 0
The RIP points to the
Hm, what I actually wanted to say was points to the retq... of a call
to native_irq_enable call.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered
All cases of RET causing a #GP with an error code != 0, the error code
is a segment selector. Though in the long list of explanation it seems
it could mean the return code segment or the stack segment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@stefan
I just tried it with nomodeset added and didn't get kexec to kick in.
@joseph
I will test those two kernels and let you know the outcome. I would
gladly do the bissection myself in order to learn, but I'm affraid that
building kernels on my laptop will take way too long.
--
You
@joe
v3.4 final: OK
v3.5-rc1: NOK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel panics
To manage notifications about this bug go
@Louis, yes I can confirm the same on my machine. Will start doing a
bisect between the two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when
We can perform a kernel bisect to identify the exact commit that
introduced this regression. First we need to identify the kernel
version that introduced this bug.
Can you test the following kernels and report back which one's have the
bug:
v3.4 final:
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel panics
To manage
Hi Louis,
Would it be possible for you to see if this bug also exists in the
latest mainline kernel[0]? That will tell us if it is already fixed.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/
** Tags added: kernel-da-key
** Tags added: regression-release
** Changed in:
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022561
Title:
Quantal : kexec kernel not triggered when kernel panics
To manage
Hello Joe,
Just tested the most recent mainline kernel : still has the same issue
with the following :
$ uname -a
Linux QuantalSA-crash 3.5.0-030500rc6-generic #201207072135 SMP Sun Jul 8
01:35:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a
21 matches
Mail list logo
