This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Tim Hartrick, regarding your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882340/comments/5
are you using a pre-3.2 Ubuntu release or can we close this report?
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are
Christoper,
The report was made again the natty 2.6.38-8 kernel. It was
subsequently reproduced on upstream kernels out to 3.2. As I noted in
my previous comment, I worked with the upstream developers to create a
patch that works on the 2.6.38 kernel as well as newer kernels (see
previous
Tim Hartrick:
The report was made again the natty 2.6.38-8 kernel. It was
subsequently reproduced on upstream kernels out to 3.2. As I noted in my
previous comment, I worked with the upstream developers to create a
patch that works on the 2.6.38 kernel as well as newer kernels (see
previous
If the patch has been applied to the 2.6.38 natty line, the 2.6.32 lucid
line and the 3.2.0 precise line, then all the releases that we use have
been fixed. If all those releases have been fixed then from my
perspective the bug can be closed. Of course the 3.0.0 oneric line also
had the bug.
--
Cut from Bug Description.
** Attachment added: log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882340/+attachment/3237750/+files/log
** Description changed:
For 2.6.38-8-server and 2.6.38-10-server running on Dell R610s and R710s
with 50GB of memory we see consistent failure of
Marking Triaged High as mainline tested, known good upstream fix commit
identified, and this problem being a problem with an essential hardware
component (CPU).
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
Tim Hartrick, thank you for reporting this bug and helping make Ubuntu better.
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are
Christopher,
I worked with the upstream developers back in November to generate a
patch for this.
The original commit was from Tejun Heo
a855b84c3d8c73220d4d3cd392a7bee7c83de70e
It was merged into the 3.2 tree at
9b5a4d4f65e260a109eaeea8bbc8062a7c58b55e
--
You received this bug notification
** Tags added: cherry-pick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882340
Title:
Invalid physical address encountered during vmcore_init.
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882340
Title:
Invalid physical address encountered during vmcore_init.
To manage
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test
the latest kernel (Not a kernel in the daily directory). Once you've
tested the
I installed linux-
image-3.1.0-030100rc10-generic_3.1.0-030100rc10.201110200610_amd64.deb
and got essentially the same result.
[ 73.637287] SysRq : Trigger a crash
[ 73.640783] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 73.648611] IP: [813aa2b6]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882340
Title:
Invalid physical address encountered during vmcore_init.
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882340
Title:
Invalid physical address encountered during vmcore_init.
To manage
15 matches
Mail list logo
