Description of problem:
After Uncompressing Linux... the following BUG appears:
BUG: Int 6: CR2 00000000
EDI c07357c0 ESI c0945fa0 EBP c076cf58 ESP c076cef4
EBX 00000046 EDX 00000006 ECX c0945fa0 EAX c0945fa0
err 00000000 EIP c044c88c CS 00000060 flg 00000002
Stack: c0430309 00000400 c04302ab c076cfa0 00000000 00000002 00000000 00000000
c07352f0 00000046 c0729460 c08549e5 00000000 00000000 00000000 00000000
00000000 00000000 00000046 c07352f0 c07357c0 c076df78 c044d6d1 00000000
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a Virtual Machine with default settings, 512Mb RAM.
2. Boot from rawhide-KDE4-i686-20080109.4.iso
Crashes almost straight away with BUG.
Boots into KDE 4 desktop.
Processor: Intel Pentium D
Host: Windows Vista / Virtual PC 2007
Can you get the Linux kernel version from that disk?
2.6.24-0.138.rc7.fc9 (mockbuild@) #1 SMP Sun Jan 6 20:35:23 EST 2008
I have exactly the same issue after upgrading the kernel on some FC8 virtual
machines to 126.96.36.199-34-fc8. These are running on Virtual Server 2005 R2. I have
tried this on two different Virtual Server hosts with the same result.
I have a similar problem, but it is with the Fedora 9 install DVD. The crash is
within Virtual PC 2007 on a Pentium 4.
The last few lines of kernel log looks like this:
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Then the Virtual PC crashes with the following message:
"An unrecoverable processor error has occurred. The virtual machine will reset
I'm curious if this still happens with the latest tree. I turned off the page
allocation debugging a few days ago, I wonder if that was tickling bugs in the
pagefault handlers of these emulators.
Fedora 9 beta still fails to boot although the failure mode is different (it's
the same as comment #4).
This bug has nothing to do with KDE, moving to F9KernelBlocker, feel free to
reclassify (F9Target?) if this is not appropriate.
By definition this is a bug in Virtual PC.
Even so, are there not workarounds for hardware bugs in the kernel? (Even if, in
this case, the hardware is virtual).
I will also try it on Virtual Server as it will be easier to follow up with
Moving to target, not a release blocker.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.