From: "Verkist, Bruno" <Bruno.Verkist@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] LION hangs at init 0 (kernel 2.4.13 on top of SuSE 7.2a IA64 Dev.
Date: Wed, 31 Oct 2001 08:35:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805419@msgid-missing> (raw)
Hi all,
I have an Intel LION (8GB, 2x733MHz C0, BIOS 100, BMC 26) installed with
SuSE 7.2a IA64 Developers Edition (kernel 2.4.4). On top of it I installed
kernel 2.4.13 and the IA64 patch linux-2_4_13-ia64-011024_diff .
Problem: When I reboot the machine with my new 2.4.13 kernel or switch from
runlevel 1 to 0 the system hangs while executing /etc/rc.d/rc0.d/S20halt.
The last messages I see on the screen are
Sending all processes the TERM signal...
Sending all processes the KILL signal...
...
Týping <Ctrl-C>: blogd: Warning: the ioctl TIOCGDEV is not know by the
kernel
After that I have to power cycle my LION (and repair my root file system
after reboot!).
Bruno
Bruno Verkist mailto:Bruno.Verkist@fujitsu-siemens.com
FSC EP PS HE4, Paderborn Tel. +49 5251 8 15365
reply other threads:[~2001-10-31 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590698805419@msgid-missing \
--to=bruno.verkist@fujitsu-siemens.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox