From: Thunder from the hill <thunder@ngforever.de>
To: Seiichi Nakashima <nakasima@kumin.ne.jp>
Cc: linux-kernel@vger.kernel.org, nakasei@fa.mdis.co.jp
Subject: Re: 2.2.21-pre4 hung up
Date: Sat, 09 Mar 2002 16:46:23 -0700 [thread overview]
Message-ID: <3C8A9ECF.F8BB8575@ngforever.de> (raw)
In-Reply-To: <200203092312.AA00022@prism.kumin.ne.jp>
Seiichi Nakashima wrote:
>
> Hi.
>
> I update to linux-2.2.20 + patch-2.2.21-pre4.
> before I used linux-2.2.20 + patch-2.2.21-pre3, and worked fine.
> linux-2.2.21-pre4 is normal end to patch, compile and install, but bootup failuer.
>
> these messages displayed on console, and hung up.
>
> ===== messaged start =====
> Uncompressing Linux... Ok, booting the kernel.
> Linux version 2.2.21pre4 (root@homesv) (gcc version 2.95.3 20010315 (release)) #
> 1 Sun Mar 10 07:31:33 JST 2002
> USER-provided physical RAM map:
> USER: 000a0000 @ 00000000 (usable)
> USER: 05efd000 @ 00100000 (usable)
> Detected 400916 kHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 799.53 BogoMIPS
> Memory: 95824k/98292k abailable (816k kernel code, 412k reserved, 1180k data, 60k init)
> Dentry hash table entries: 16384 (order 5, 128k)
> Buffer cache hash table entries: 131072 (order 7, 512k)
> Page cache hash table entries: 32768 (order 5, 128k)
> CPU: L1 I cache: 16K, L1 D cache: 16K
> Intel machine check architecture supported.
> ===== messages end =====
I remember this was the one-and-zero stuff from last evening or
whenever. Can someone remember? It was just some 0 which had to be 1.
--
begin-base64 755 -
IyEgL3Vzci9iaW4vcGVybApteSAgICAgJHNheWluZyA9CSMgVGhlIHNjcmlw
dCBvbiB0aGUgbGVmdCBpcyB0aGUgcHJvb2YKIk5lbmEgaXN0IGVpbiIgLgkj
IHRoYXQgaXQgaXNuJ3QgYWxsIHRoZSB3YXkgaXQgc2VlbXMKIiB2ZXJhbHRl
dGVyICIgLgkjIHRvIGJlIChlc3BlY2lhbGx5IG5vdCB3aXRoIG1lKQoiTkRX
LVN0YXIuXG4iICA7CiRzYXlpbmcgPX4Kcy9ORFctU3Rhci9rYW5uXAogdW5z
IHJldHRlbi9nICA7CiRzYXlpbmcgICAgICAgPX4Kcy92ZXJhbHRldGVyL2Rp
XAplIExpZWJlL2c7CiRzYXlpbmcgPX5zL2Vpbi8KbnVyL2c7JHNheWluZyA9
fgpzL2lzdC9zYWd0LC9nICA7CiRzYXlpbmc9fnMvXG4vL2cKO3ByaW50Zigk
c2F5aW5nKQo7cHJpbnRmKCJcbiIpOwo=
====
Extract this and see what will happen if you execute my
signature. Just save it to file and do a
> uudecode $file | perl
next prev parent reply other threads:[~2002-03-09 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 23:12 2.2.21-pre4 hung up Seiichi Nakashima
2002-03-09 23:46 ` Thunder from the hill [this message]
2002-03-09 23:48 ` Bruce Harada
2002-03-10 0:59 ` Seiichi Nakashima
2002-03-10 0:03 ` Thunder from the hill
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=3C8A9ECF.F8BB8575@ngforever.de \
--to=thunder@ngforever.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nakasei@fa.mdis.co.jp \
--cc=nakasima@kumin.ne.jp \
/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.