Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 58871 - kernel panic - attempted to kill init
kernel panic - attempted to kill init
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-01-25 22:59 EST by bcandela
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-07 20:46:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bcandela 2002-01-25 22:59:15 EST
Description of Problem:

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

How Reproducible:

Steps to Reproduce:
1. launching linux install from cdrom
2. graphic install, text install, expert install..
3. vmlinuz

Actual Results:
kernel panic - attempted to kill init

Expected Results:

Additional Information:
Comment 1 bcandela 2002-01-25 23:04:31 EST
I'm trying to install linux 7.2 from CDROM
System starts and display the first screen with all install options:
I've tried all possibilities but whenever I do , I get the same result:
After few seconds, I obtain a trace screen with register list and invalid operand 
notification and the message
kernel panic - attempted to kill init then system freezes...

My video card is a Sis730 model on a Matsonic motherboard.

Can yopu help me ?

Comment 2 Arjan van de Ven 2002-01-26 05:12:15 EST
Can you try typing
linux mem=xxxM

where xxx is the amount of memory (in megabytes) you have minus 32 ?
Comment 3 bcandela 2002-02-08 02:20:13 EST
OK Thanks. I've tried linux mem=64M expert and it worked fine. I've 128M memory

B. Candela

Comment 4 Alan Cox 2003-06-07 20:46:35 EDT
Ok marking wontfix as this seems to be a bios issue

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