Re: Strange problems...
On Tue, Apr 24, 2001 at 02:08:04PM -0400, Dale Scheetz wrote: > On Tue, 24 Apr 2001, Wichert Akkerman wrote: > > > Previously Dale Scheetz wrote: > > > Anyone have any ideas? > > > > 1. figure out what uses insane amount of memory and apply kill and/or rm > > So, this is a common response from a system that has exhaused both swap > and real memory? Any good candidates in a "standard" system? I don't do > anything now that I haven't done for years, so it's probably one of those > new "features" of Debian, right? ;-) > > I couldn't get top to run while the "event" was occuring, and afterwards > everything looked ok ... hmmm, I do seem to have a problem here. Mem: > reports 64K with about 62K in use. So how come the whole 128 meg is not > being recognized? (it shows up on the memory test at boot) try using `ps vax`, or something similar (the "v" option shows memory usage) ::snip? snip!:: > Thanks, > > Dwarf > -- > _-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_- > _-_- > _- aka Dale Scheetz Phone: 1 (850) 656-9769 _- > _- Flexible Software 11000 McCrackin Road _- > _- e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308_- > _-_- > _-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_- > available at: http://www.polaris.net/~dwarf/ --xsdg -- ___ / PROCRASTINATION: Hard Work Often Pays Off After \ \ Time, but Laziness Always Pays Off Now. / /http://xsdg.hypermart.net|[EMAIL PROTECTED]\ \___/
Re: Strange problems...
* Dale Scheetz | I couldn't get top to run while the "event" was occuring, and afterwards | everything looked ok ... hmmm, I do seem to have a problem here. Mem: | reports 64K with about 62K in use. So how come the whole 128 meg is not | being recognized? (it shows up on the memory test at boot) It might help if you add 'append="mem=128M"' to lilo.conf and rerun lilo. The kernel doesn't always find all the memory, IME. -- Tollef Fog Heen Unix _IS_ user friendly... It's just selective about who its friends are.
Re: Strange problems...
On Tue, 24 Apr 2001, Dale Scheetz wrote: > > I have a resonably new motherboard with 128 meg of memory. My swap space > is 100 meg. I just got a slew of messages at the console like: > > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for acroread... > VM: do_try_to_free_pages failed for acroread... > > and even gpm complained when I tried to highlight the above text. > > Anyone have any ideas? > ok it's been said before, but: it's a problem with linux 2.2.17. upgrade to 2.2.19. btw, though the messages are irritating, they are non-fatal. i had a 2.2.17 box with ~4 months of uptime that got that crap in the logs several times a day.
Re: Strange problems...
Previously Dale Scheetz wrote: > So, this is a common response from a system that has exhaused both swap > and real memory? Any good candidates in a "standard" system? I don't do > anything now that I haven't done for years, so it's probably one of those > new "features" of Debian, right? ;-) Without knowing what it is there is little that we can do. Things have become more bloated though (just look at the pig that is libc) > I couldn't get top to run while the "event" was occuring, and afterwards > everything looked ok ... hmmm, I do seem to have a problem here. Mem: > reports 64K with about 62K in use. So how come the whole 128 meg is not > being recognized? (it shows up on the memory test at boot) That's why there is a magic systemrequest :) > Is there something specific that was fixed between .17 and .19 that would > bear on my problem? The VM system, especially for OOM situations like you had. Wichert -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: Strange problems...
On Tue, 24 Apr 2001, Wichert Akkerman wrote: > Previously Dale Scheetz wrote: > > Anyone have any ideas? > > 1. figure out what uses insane amount of memory and apply kill and/or rm So, this is a common response from a system that has exhaused both swap and real memory? Any good candidates in a "standard" system? I don't do anything now that I haven't done for years, so it's probably one of those new "features" of Debian, right? ;-) I couldn't get top to run while the "event" was occuring, and afterwards everything looked ok ... hmmm, I do seem to have a problem here. Mem: reports 64K with about 62K in use. So how come the whole 128 meg is not being recognized? (it shows up on the memory test at boot) > 2. buy more memory Gag me with a spoon! For the last 5 years I've lived with a 32 meg machine and never had problems. In recent years, however, I've noticed that it gets harder and harder to shoehorn a zImage kernel into the required size. Things get much worse and I just might have to become interested in something more like BSD ;-) I upgraded my machine to this, for me, gigantic size because VMware will not run without at least 100 meg. (Hmmm, it's shut down, but it still has all kinds of drivers installed %#&^@) This is the most recent addition to my toolset, but it has been shut down for days, and was not running durring the event (unless there is more magic here than I thought ;-) > 3. upgrade to a 2.2.19 kernel > I should probably do that anyway... Is there something specific that was fixed between .17 and .19 that would bear on my problem? Thanks, Dwarf -- _-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_- _-_- _- aka Dale Scheetz Phone: 1 (850) 656-9769 _- _- Flexible Software 11000 McCrackin Road _- _- e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308_- _-_- _-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_- available at: http://www.polaris.net/~dwarf/
Re: Strange problems...
Previously Dale Scheetz wrote: > Anyone have any ideas? 1. figure out what uses insane amount of memory and apply kill and/or rm 2. buy more memory 3. upgrade to a 2.2.19 kernel Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: Strange problems...
24.04.2001 pisze Dale Scheetz ([EMAIL PROTECTED]): > I have a resonably new motherboard with 128 meg of memory. My swap space > is 100 meg. I just got a slew of messages at the console like: > > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for WindowMaker... > VM: do_try_to_free_pages failed for acroread... > VM: do_try_to_free_pages failed for acroread... I presume you have kernel version lower than 2.2.19. The kernels up to 2.2.18 have fscked up memory management; upgrade to 2.2.19 and everything should be fine best regards, Jubal -- [ Miros/law L Baran, baran-at-knm-org-pl, neg IQ, cert AI ] [ 0101010 is ] [ BOF2510053411, makabra.knm.org.pl/~baran/, alchemy pany ] [ The Answer ] ``Good-bye. I am leaving because I am bored.'' -- George Saunders' dying words
Strange problems...
I have a resonably new motherboard with 128 meg of memory. My swap space is 100 meg. I just got a slew of messages at the console like: VM: do_try_to_free_pages failed for WindowMaker... VM: do_try_to_free_pages failed for WindowMaker... VM: do_try_to_free_pages failed for WindowMaker... VM: do_try_to_free_pages failed for acroread... VM: do_try_to_free_pages failed for acroread... and even gpm complained when I tried to highlight the above text. Anyone have any ideas? A Noid, Dwarf -- _-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_- _-_- _- aka Dale Scheetz Phone: 1 (850) 656-9769 _- _- Flexible Software 11000 McCrackin Road _- _- e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308_- _-_- _-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_- available at: http://www.polaris.net/~dwarf/
Re: Strange problems when trying to compile kernel 2.2.7
I get a similar problem, but only when compiling pcmcia-source for that kernel package: gcc -MD -O2 -Wall -Wstrict-prototypes -Winline -pipe -D__KERNEL__ -DMODULE -I. ./include -I/usr/src/kernel-source-2.2.7/include -I/usr/src/kernel-source-2.2.7 -c i82365.c In file included from ../include/pcmcia/k_compat.h:81, from i82365.c:25: /usr/src/kernel-source-2.2.7/include/linux/module.h:19: linux/modversions.h: No such file or directory make[4]: *** [i82365.o] Error 1 make[4]: Leaving directory `/usr/src/modules/pcmcia-cs/modules' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/modules/pcmcia-cs' make[2]: *** [build-modules] Error 2 make[2]: Leaving directory `/usr/src/modules/pcmcia-cs' make[1]: *** [kdist_image] Error 2 make[1]: Leaving directory `/usr/src/modules/pcmcia-cs' make: [modules_image] Error 2 (ignored) -- Stefan pgpGJ88WrSZFV.pgp Description: PGP signature
Strange problems when trying to compile kernel 2.2.7
Hello, I installed kernel-source-2.2.7 from potato and tried to compile. I've got several No such file or directory errors. The `make zImage 2>` output is appended. Is the package broken??? Kind regards Andreas. [X] Against war. init/main.c: In function `start_kernel': init/main.c:1166: warning: implicit declaration of function `bigphysarea_init' In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:4: linux/modules/8390.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:7: linux/modules/adb.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:10: linux/modules/af_netlink.ver: No such file or directory /usr/src/kernel-source-2.2.7/include/linux/modversions.h:11: linux/modules/af_spx.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:15: linux/modules/b1pci.ver: No such file or directory /usr/src/kernel-source-2.2.7/include/linux/modversions.h:16: linux/modules/capidrv.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:26: linux/modules/i2c.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:29: linux/modules/ip_gre.ver: No such file or directory /usr/src/kernel-source-2.2.7/include/linux/modversions.h:30: linux/modules/ipip.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:50: linux/modules/paride.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:52: linux/modules/parport_probe.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:55: linux/modules/ppp_deflate.ver: No such file or directory In file included from /usr/src/kernel-source-2.2.7/include/linux/module.h:19, from signal.c:10: /usr/src/kernel-source-2.2.7/include/linux/modversions.h:58: linux/modules/pty.ver: No such file or directory make[2]: *** [signal.o] Error 1 make[1]: *** [first_rule] Error 2 make: *** [_dir_kernel] Error 2
