[lkml]   [2001]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Bug in 2.2 kernels (mysterious hangs after freeing unused memory)
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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.037 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site