Rik's VM contains a deadlock somewhere

From: Anton Petrusevich (improvisus@echo.ru)
Date: Mon Sep 18 2000 - 23:48:11 EST

Next message: Keith Owens: "Re: relocation truncated to fit: R_386_PC32"
Previous message: Armand: "relocation truncated to fit: R_386_PC32"
Next in thread: Mike Galbraith: "Re: Rik's VM contains a deadlock somewhere"
Reply: Mike Galbraith: "Re: Rik's VM contains a deadlock somewhere"
Reply: Rik van Riel: "Re: Rik's VM contains a deadlock somewhere"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Linus,

please, check carefully Rik's VM patch, it definitly contains a
deadlock, which can be seen on low-memory computers. Try mem=8m. I
wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
-test9-pre{1,2}). It boots fine(mem=16m), but then stalls begin for some
time and for infinitive time at last. I told Rik about it, he tried to
fix but wasn't successful.

With mem=8m it couldn't finish init scripts even.

-- 
Anton
-
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/

Next message: Keith Owens: "Re: relocation truncated to fit: R_386_PC32"
Previous message: Armand: "relocation truncated to fit: R_386_PC32"
Next in thread: Mike Galbraith: "Re: Rik's VM contains a deadlock somewhere"
Reply: Mike Galbraith: "Re: Rik's VM contains a deadlock somewhere"
Reply: Rik van Riel: "Re: Rik's VM contains a deadlock somewhere"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:19 EST