Re: Linux 2.2.18pre25
On Fri, 8 Dec 2000, Andrea Arcangeli wrote: # On Fri, Dec 08, 2000 at 06:02:57PM +0100, Martin Kacer wrote: # >Is there any chance to get rid of these VMM failures? # You should apply this patch on top of 2.2.18pre25: # ftp://.../VM-global-2.2.18pre25-7.bz2 Well, I've found that VM-global patch before, of course. Until now, the last version was against pre18. Since I do not know the exact rules for including new things into Alan's tree, I thought that VM-global patch was already included in pre24. Sorry for my lack of experience. ;-)) I should have checked it. As I wrote before, I had no time recently to follow the mailing list carefully and I didn't know exactly what VM-global patch is. # >It seems we need to return back to 2.2.13 for some time. :-( # Definitely no, you only need to apply the above collection of bugfixes. Ok, I can try it, at least. I will let you know about results. Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre25
On Fri, 8 Dec 2000, Alan Cox wrote: # >Is there any chance to get rid of these VMM failures? # By finding them. :-) I am not so familiar with MM in Linux. :^( And do not have enough time for intensive study... Although I would probably like that work... # Are you confident you are not running out of memory. Well, almost sure. This is the log with load records: (according to /proc/meminfo) FTPusers SMBusr load free memfree swap Fri Dec 8 14:35:05 CET 2000 61 35 6.173068 kB 128932 kB Fri Dec 8 14:40:04 CET 2000 59 36 5.052280 kB 130320 kB Fri Dec 8 14:45:03 CET 2000 59 36 5.972896 kB 131448 kB Fri Dec 8 14:50:03 CET 2000 59 35 6.592908 kB 133140 kB Fri Dec 8 14:55:04 CET 2000 53 36 8.822380 kB 133952 kB Fri Dec 8 15:00:03 CET 2000 53 40 6.422728 kB 135064 kB Fri Dec 8 15:05:03 CET 2000 48 39 5.472264 kB 135684 kB Fri Dec 8 15:10:03 CET 2000 48 41 3.903204 kB 135928 kB Fri Dec 8 15:15:03 CET 2000 51 41 5.932628 kB 135700 kB Fri Dec 8 15:20:03 CET 2000 50 45 6.502124 kB 135828 kB Fri Dec 8 15:25:03 CET 2000 56 44 7.922192 kB 136080 kB Fri Dec 8 15:30:03 CET 2000 49 45 10.892072 kB 136176 kB Fri Dec 8 15:35:03 CET 2000 51 42 6.322960 kB 136156 kB Fri Dec 8 15:40:04 CET 2000 54 44 6.922364 kB 136220 kB Fri Dec 8 15:45:03 CET 2000 54 44 6.632852 kB 136348 kB Fri Dec 8 15:50:04 CET 2000 53 46 3.632248 kB 136420 kB Fri Dec 8 15:55:03 CET 2000 59 48 6.513060 kB 136312 kB (crashed during the next 5 minutes) Doesn't seem to have consumed all of swap space. I will try to determine more info the next time - I promise... # Presumably since 2.2.13 works you are 8) I didn't tell it worked. It had worked a long time ago. It is still not tested now. Unfortunately, due to the absence of raid0 module the bootup process destroyed our 140GB partition. It will take some time to make the system running again. :-( Thank for your answer anyway... Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre25
On Thu, 7 Dec 2000, Alan Cox wrote: # Ok we believe the VM crash looping printing error messages is now fixed. # Marcelo finally figured it out and my 8Mb 486 has been running 2.2.18pre # with that fix and stably[1]. Unfortunately, I don't think it is fixed. We maintain a heavy loaded FTP/Samba server here (120+ active connections with very long data transfers in rush hours) and it had the "VM: do_try_to_free_pages failed" problem since 2.2.17 was first installed (there was FreeBSD before that). We aplied 2.2.18pre25 patch yesterday hoping it could solve it. The only difference is that the server reached several hours uptime instead of 40 minutes (with pre24). After two hours of load between 6.00 and 15.00 the console was flooded with those unpopular messages ("VM: ..."). The system was taken down by generation of these messages so quickly, that even none of the messages appeared in syslog! No response to Ctrl-Alt-Del, of course... :-( Just trashing... On Fri, 8 Dec 2000, Andrea Arcangeli wrote: # > Ok we believe the VM crash looping printing error messages is now fixed. # Such bug can't generate crashes. Did you ever reproduced crashes on your 8Mb # 486 with 2.2.18pre24? Our bug can generate them. :-( Maybe it's a different one? ;-) Is there any chance to get rid of these VMM failures? Sorry if I've missed something important recently mentioned here. I had not enough time to follow the lk list carefully. Is there any reliable solution? It seems we need to return back to 2.2.13 for some time. :-( Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre25
On Thu, 7 Dec 2000, Alan Cox wrote: # Ok we believe the VM crash looping printing error messages is now fixed. # Marcelo finally figured it out and my 8Mb 486 has been running 2.2.18pre # with that fix and stably[1]. Unfortunately, I don't think it is fixed. We maintain a heavy loaded FTP/Samba server here (120+ active connections with very long data transfers in rush hours) and it had the "VM: do_try_to_free_pages failed" problem since 2.2.17 was first installed (there was FreeBSD before that). We aplied 2.2.18pre25 patch yesterday hoping it could solve it. The only difference is that the server reached several hours uptime instead of 40 minutes (with pre24). After two hours of load between 6.00 and 15.00 the console was flooded with those unpopular messages ("VM: ..."). The system was taken down by generation of these messages so quickly, that even none of the messages appeared in syslog! No response to Ctrl-Alt-Del, of course... :-( Just trashing... On Fri, 8 Dec 2000, Andrea Arcangeli wrote: # Ok we believe the VM crash looping printing error messages is now fixed. # Such bug can't generate crashes. Did you ever reproduced crashes on your 8Mb # 486 with 2.2.18pre24? Our bug can generate them. :-( Maybe it's a different one? ;-) Is there any chance to get rid of these VMM failures? Sorry if I've missed something important recently mentioned here. I had not enough time to follow the lk list carefully. Is there any reliable solution? It seems we need to return back to 2.2.13 for some time. :-( Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre25
On Fri, 8 Dec 2000, Alan Cox wrote: # Is there any chance to get rid of these VMM failures? # By finding them. :-) I am not so familiar with MM in Linux. :^( And do not have enough time for intensive study... Although I would probably like that work... # Are you confident you are not running out of memory. Well, almost sure. This is the log with load records: (according to /proc/meminfo) FTPusers SMBusr load free memfree swap Fri Dec 8 14:35:05 CET 2000 61 35 6.173068 kB 128932 kB Fri Dec 8 14:40:04 CET 2000 59 36 5.052280 kB 130320 kB Fri Dec 8 14:45:03 CET 2000 59 36 5.972896 kB 131448 kB Fri Dec 8 14:50:03 CET 2000 59 35 6.592908 kB 133140 kB Fri Dec 8 14:55:04 CET 2000 53 36 8.822380 kB 133952 kB Fri Dec 8 15:00:03 CET 2000 53 40 6.422728 kB 135064 kB Fri Dec 8 15:05:03 CET 2000 48 39 5.472264 kB 135684 kB Fri Dec 8 15:10:03 CET 2000 48 41 3.903204 kB 135928 kB Fri Dec 8 15:15:03 CET 2000 51 41 5.932628 kB 135700 kB Fri Dec 8 15:20:03 CET 2000 50 45 6.502124 kB 135828 kB Fri Dec 8 15:25:03 CET 2000 56 44 7.922192 kB 136080 kB Fri Dec 8 15:30:03 CET 2000 49 45 10.892072 kB 136176 kB Fri Dec 8 15:35:03 CET 2000 51 42 6.322960 kB 136156 kB Fri Dec 8 15:40:04 CET 2000 54 44 6.922364 kB 136220 kB Fri Dec 8 15:45:03 CET 2000 54 44 6.632852 kB 136348 kB Fri Dec 8 15:50:04 CET 2000 53 46 3.632248 kB 136420 kB Fri Dec 8 15:55:03 CET 2000 59 48 6.513060 kB 136312 kB (crashed during the next 5 minutes) Doesn't seem to have consumed all of swap space. I will try to determine more info the next time - I promise... # Presumably since 2.2.13 works you are 8) I didn't tell it worked. It had worked a long time ago. It is still not tested now. Unfortunately, due to the absence of raid0 module the bootup process destroyed our 140GB partition. It will take some time to make the system running again. :-( Thank for your answer anyway... Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/