Evan, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/883029/comments/8
regarding this being due to hardware failure. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line an
It seems that this is not a software bug, but was caused by ram that failed
intermittently. I removed two ram dimms and the system is now able to boot
reliably. Thanks for the follow up.
Evan
On Nov 11, 2013 7:31 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
> Evan, thi
Evan, 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? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883029
Title:
boot hangs with PANIC: early exception 0d
To manage notifications about
** Tags added: kernel-needs-upstream-bug-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883029
Title:
boot hangs with PANIC: early exception 0d
To manage notifications about this bug go to:
h
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you are
This issue is still present in 3.1.0-030100rc10-generic. Each boot has about
equal chances of working, hanging on a blank purple screen, or displaying PANIC
0d exception ...
I also noticed that earlyprintk=vga no longer worked with rc10, so I was unable
to compare stack traces.
** Tags removed
I can confirm that this still happens with 3.1.0-999.201110270406_amd64. The
two times it panicked today had a slightly different stack trace from before.
Neither had the line "early_idt_handlers", and once there was the extra line:
"init_currently_empty_zone".
Right before I posted I realized t
I have installed the current mainline kernel (3.1.0-999.201110270406_amd64). I
will be able to test it when I get back next week.
Thanks for the amazingly fast response.
Evan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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 upst
** 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/883029
Title:
boot hangs with PANIC: early exception 0d
To manage notifications about thi
** Attachment added: "printk"
https://bugs.launchpad.net/bugs/883029/+attachment/2576557/+files/printk
** Description changed:
After grub the boot stalls on a blank purple splash screen.
- I then tried booting with earlyprintk=vga,keep and copied down a stack trace,
which I have attached. T
12 matches
Mail list logo
