mem=nopentium PANIC: early exception 08 rip 246:10
Bug #553464 reported by
Kamal Mostafa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Low
|
Unassigned |
Bug Description
If I boot Lucid amd64 kernel with "mem=nopentium" (or actually even with "mem=blahblah"), PANIC below occurs immediately (no trace is displayed). i386 kernel does not panic.
Lucid 2.6.32-19-generic #28~pre1 x86_64
PANIC: early exception 08 rip 246:10 error ffffffff81038acb cr2 0
still occurs: maverick 2.6.35-26-generic #46
still occurs: natty 2.6.38-1-generic #28
Changed in linux (Ubuntu): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
tags: | added: maverick natty |
Changed in linux (Ubuntu): | |
assignee: | Kamal Mostafa (kamalmostafa) → nobody |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu Maverick): | |
status: | New → Fix Committed |
tags: | removed: needs-upstream-testing |
tags: | added: verification-done |
To post a comment you must log in.
I should also mention that the machine boots and generally works great without "mem=nopentium" (I wanted to experiment with that option with respect to a suspend/resume problem.