Manfred Spraul wrote:
| > Do you have an NTFS disk mounted? I had a similar problem which was
| > "fixed" by not having an NTFS vol mounted. Apparently the ntfs code
| > makes a lot of calls to vmalloc which leads to badness.
| >
| Both modify_ldt and NTFS make lots of calls to vmalloc.
|
| AFAICS this limits the number of concurrently running processes that are
| linked to libpthread to less than 2000 on highmem machines, regardless
| of the actual free memory.
|
| Could you try the attached patch?
| It should permit you to keep the NTFS vol mounted - libpthread doesn't
| need a 64 kB LDT. That should reduce the pressure on the vmalloc area.
|
| The patch applies to both 2.4.16 and 2.5.1
Tried your patch against 2.4.16.
After running updatedb with all my vols mounted (including ntfs) I was
able to start up all applications without trouble, so your patch was
good in that regard. However, ntfs isn't happy. A whole lotta this is
in my syslog:
Dec 17 22:36:55 orf kernel: NTFS: ntfs_getdir_unsorted(): Read failed. Returning error code -95.
Dec 17 22:36:55 orf last message repeated 5 times
Dec 17 22:36:55 orf kernel: NTFS: ntfs_insert_run: ntfs_vmalloc(new_size = 0x1000) failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_process_runs: ntfs_insert_run failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_getdir_unsorted(): Read failed. Returning error code -95.
Dec 17 22:36:55 orf kernel: NTFS: ntfs_insert_run: ntfs_vmalloc(new_size = 0x1000) failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_process_runs: ntfs_insert_run failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_getdir_unsorted(): Read failed. Returning error code -95.
Dec 17 22:36:55 orf kernel: NTFS: ntfs_insert_run: ntfs_vmalloc(new_size = 0x1000) failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_process_runs: ntfs_insert_run failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_insert_run: ntfs_vmalloc(new_size = 0x1000) failed
Dec 17 22:36:55 orf kernel: NTFS: ntfs_process_runs: ntfs_insert_run failed
Leigh Orf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:15 EST