Bug 143906 - Crash on boot on Virtual PC / Mac OSX
Summary: Crash on boot on Virtual PC / Mac OSX
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 3
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-01 03:35 UTC by Glenn R. Golden
Modified: 2015-01-04 22:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-01 19:26:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Glenn R. Golden 2005-01-01 03:35:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.5 (KHTML, like Gecko) Safari/125.12

Description of problem:
I was able to successfully run the installer (from the Fedora 3 CD-ROM from the January 2005 Linux Magazine) on my Macintosh running Virtual PC 6.1, but when it reboots, it crashes Virtual PC with a message "An unrecoverable processor error has been encountered.".  The last message in the PC window was:

Uncompressing Linux... Ok, booting the kernel.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install
2. Reboot or start up fresh


Actual Results:  Crash as reported above.

Expected Results:  System should have started.

Additional info:

Comment 1 Sitsofe Wheeler 2005-01-01 11:55:24 UTC
This is down to Virtual PC being unable to handle a 4G/4G kernel. I believe the
work around is to install an i586 kernel. This is probably a dup of bug #136018

Comment 2 Dave Jones 2005-01-01 19:26:28 UTC
latest testing kernels have 4g/4g disabled.
Likewise, FC4 has removed this patch.



Note You need to log in before you can comment on or make changes to this bug.