Messages in this thread | | | From | Neil Brown <> | Date | Thu, 30 Aug 2001 12:05:14 +1000 (EST) | Subject | Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?) |
| |
On Wednesday August 29, dbr@greenhydrant.com wrote: > > Now, when you say out-of-memory, do you mean out of memory plus swap? Or > just out of memory?
kmalloc(,GFP_NOIO) failure. i.e. transient out-of-phyical-memory condition. I suspect that kmalloc tends to fail only occasionally as the failure will then to slow allocation requests down, and give the VM system a bit of time to write more stuff out to disc and so free up memory. I am fairly sure that without the patch it will happen again, but maybe not straight away.
NeilBrown
> > Running out of memory is quite common with the kernel always filling up > buffers and cache, but running out of memory+swap is not common (and I know > I didn't hit that in my setup!) > > Thanks for your help, > > -Dave - 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/
| |