From: Blizbor <tb670725@ima.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Bug in 2.2 kernels (mysterious hangs after freeing unused memory)
Date: Mon, 08 Jan 2001 22:12:18 +0100 [thread overview]
Message-ID: <5.0.0.25.0.20010108214619.00aaea60@195.117.13.2> (raw)
In-Reply-To: <20010108210920.U3472@arthur.ubicom.tudelft.nl>
In-Reply-To: <5.0.0.25.0.20010107190604.00a44400@195.117.13.2> <5.0.0.25.0.20010107190604.00a44400@195.117.13.2>
At 01-01-08 21:09, you wrote:
>On Sun, Jan 07, 2001 at 07:21:08PM +0100, Blizbor wrote:
>> I have found something weird in kernel 2.2.17.
>> After installation on the Pentium PRO equipped machine,
>> I have moved hard disk to another one, but equipped
>> with AMD-K5 and after encountering problems I moved again
>> this disk to machine equipped with Intel Pentium MMX.
>>
>> On all machines except Pentium PRO boot process was stopping
>> after freeing unused kernel memory.
>
>A kernel compiled and optimised for a PPro does not neccesarily run on
>an AMD K5 or a Pentium MMX.
Yes, I know that.
Kernel was compiled for i386.
Problem was by simplified "init" process handling in kernel
- especially no error handling for them. Problem is not in that
something doesnt run but in that so there aren't information
about error. I didn't expect that kernel do something more
complicated than saying about error. Hanging is not good idea ;)
I've lost few work days to find whats
going on. Problem is lack of one short line displayed on console:
"init process failed, reason: killed by signal 4".
I was really surprised that on installation CD marked as i386,
some stupid guy put binaries for i686.
Exactly six rpm's - three containing kernel (that's OK) and one
containing glibc. Even if "smart guys" wanted to make preformance
boost, they should do that in the safe way. But this is problem of the
RedHat 7 developers. Together with glibc srpms that doesnt have chance
to build on i386 platform due to bugs in specs file. But let we
leave alone RH and their problems with their experimental distribution.
Cheers,
Blizbor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 18:21 Blizbor
2001-01-08 20:09 ` Erik Mouw
2001-01-08 21:12 ` Blizbor [this message]
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=5.0.0.25.0.20010108214619.00aaea60@195.117.13.2 \
--to=tb670725@ima.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®