Messages in this thread | | | From | Juergen Vollmer <> | Subject | Allocation of too much memory hangs system, kernel 2.2.* | Date | Sat, 22 May 1999 17:59:52 +0200 |
| |
Hi,
here comes my problem report.
[1.] One line summary of the problem: Allocation of too much memory hangs system, kernel 2.2.*
[2.] Full description of the problem/report: a) An (erronous) program allocates memory in some kind of endless loop. After some while the system hangs. I use the system over an ethernet. The system may be ping'ed, but no other action is possible. CTRL-ALT_DEL form the direct connected keyboard does not work. Since even after 30 minutes, nothing is possible (except ping). Only the power-off botton is able to reactivate the system :-) b) A (correct) program requires a lot of memory, more than available (physical and swap) on another Linux box. The program is executed in an xterm running under KDE 1.1. After some time I'm logged out (i.e. I get KDE's login-screen). On a first view the system seems to work, but sooner or later, one detects that modules can't be loaded. Hence the system must be rebooted.
Using the "old" 2.0.36 kernel,in both cases the programs were aborted after some time and the system continues to work without any problems.
Switching off all swap devises in case a) I get a `Bus error'. After that the systems continues to work, but I can't accesses the NFS-mounted file system any more from the other machine. Rebooting the system is required.
[3.] Keywords (i.e., modules, networking, kernel): Virtual memory, allocating more memory than available.
[4.] Kernel version (from /proc/version): Linux version 2.2.9 (root@joergli) (gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)) #8 Fri May 14 17:51:29 CEST 1999
This happens also in kernel: 2.2.5, 6, 7, and 2.2.8
[5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) -none- [6.] A small shell script or example program which triggers the problem (if possible) -none- [7.] Environment [7.1.] Software (add the output of the ver_linux script here) -- Versions installed: (if some fields are empty or looks -- unusual then possibly you have very old versions) Linux joergli 2.2.9 #8 Fri May 14 17:51:29 CEST 1999 i686 unknown Kernel modules 2.2.2-pre6 Gnu C egcs-2.91.66 Binutils 2.9.1.0.22 Linux C Library x 1 root root 2475225 Apr 4 16:36 /lib/libc.so.6 Dynamic linker ldd (GNU libc) 2.0.7 Procps 1.2.11 Mount 2.9i Net-tools 1.50 Kbd 0.99 Sh-utils 1.12 Modules Loaded nfs lockd sunrpc vmnet vmmon tulip dummy0 serial ntfs nls_iso8859-1 vfat fat
[7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping : 2 cpu MHz : 400.913669 cache size : 512 KB fdiv_bug : no hlt_bug : no sep_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx osfxsr bogomips : 399.77
[7.3.] Module information (from /proc/modules): nfs 29880 1 (autoclean) lockd 30760 1 (autoclean) [nfs] sunrpc 51780 1 (autoclean) [nfs lockd] vmnet 8652 1 vmmon 9868 0 (unused) tulip 26256 1 (autoclean) dummy0 684 1 (autoclean) serial 18324 0 (autoclean) ntfs 35488 1 (autoclean) nls_iso8859-1 2020 1 (autoclean) vfat 11196 1 (autoclean) fat 25120 1 (autoclean) [vfat]
[7.4.] SCSI information (from /proc/scsi/scsi) Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SEAGATE Model: ST39173LW Rev: 6246 Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: DCAS-34330 Rev: S65A Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: IBM Model: DORS-32160 Rev: S82C Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: TEAC Model: CD-R55S Rev: 1.0L Type: CD-ROM ANSI SCSI revision: 02
[7.5.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant):
I have 128 MB main memory and `swapon -s' gives: Filename Type Size Used Priority /dev/sda5 partition 136516 0 999 /dev/sdb1 partition 136516 0 888
(The problem occurs also if I use only one swap device)
[X.] Other notes, patches, fixes, workarounds: setting `ulimit -v ....' in /etc/profile. But this works obviously only on a single user system :-).
Do you need more information? This behaviour can be reproduced and happens always.
With best regards
Juergen Vollmer
------------------------------------------------------------------------------ Dr. Juergen Vollmer, Viktoriastrasse 15, D-76133 Karlsruhe office: vollmer@cocolab.de Tel: +49(721) 9204871 Fax: +49(721) 24874 private: Juergen.Vollmer@acm.org Tel: +49(721) 24874 Fax: +49(721) 24874 WWW: www.cocolab.de/vollmer ------------------------------------------------------------------------------
[unhandled content-type:application/pgp-signature]
| |