From: "Stephane GARIN" <sgarin@sgarin.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: 2.2.19pre - Kernel Panic: no init found
Date: Sat, 3 Mar 2001 22:50:37 +0100 [thread overview]
Message-ID: <001f01c0a42c$7fc2e810$4601a8c0@oracle.intranet> (raw)
In-Reply-To: <Pine.LNX.4.21.0103031334340.11559-100000@spock.shacknet.nu>
I tried it but no change. I don't have ACPI messages during the boot... I
don't understand why there is this trouble...
-----Message d'origine-----
De : linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]De la part de Jason Madden
Envoyé : samedi 3 mars 2001 20:44
À : linux-kernel@vger.kernel.org
Objet : Re: 2.2.19pre - Kernel Panic: no init found
I get similar messages on 2.4.2 and 2.4.2-ac7 :
...
ACPI: Core Subsystem version [20010208]
ACPI: Subsystem enabled
ACPI: System firmware supports: C2 C3
ACPI: plvl2lat=10 plvl3lat=20
ACPI: C2 enter=143 C2 exit=35
ACPI: C3 enter=858 C3 exit=71
ACPI: Not using ACPI idle
ACPI: System firmware supports: S0 S1 S5
ACPI: If experiencing system slowdowns, pass acpi=no-idle #FROM MEMORY
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 232k freed
Kernel panic: No init found. Try passing init= option to kernel.
The solution was to pass acpi=no-idle on the kernel command line. The same
configuration worked fine with 2.4.1
Jason
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-03-03 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 22:36 2.2.19pre - Kernel Panic: no init found Stéphane GARIN
2001-03-03 19:43 ` Jason Madden
2001-03-03 21:50 ` Stephane GARIN [this message]
[not found] <200103031758.f23HwQn02197@stev.org>
2001-03-06 16:06 ` Stephane GARIN
2001-03-06 16:17 ` Jeremy Jackson
2001-03-06 16:51 ` Stephane GARIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001f01c0a42c$7fc2e810$4601a8c0@oracle.intranet' \
--to=sgarin@sgarin.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.