On Tue, Jan 22, 2008 at 03:45:32PM -0800, Xin LI wrote:Does it cause any problems aside from printing these messages ? What workload do you put on the machine ? The messages came from the failure of the kernel to allocate address space for the kernel stack for a thread being created. Previously, the system would panic encountering this situation. This may happen due to kernel_map address space depletion, for instance, by having a lot (on i386 machines with > 1Gb memory, ~40000) threads.
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Bart Van Assche | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Badalian Vyacheslav | e1000: Question about polling |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
