On Thu, 26 Apr 2001, Jeff V. Merkey wrote: > I am seeing this as well on 2.4.3 with both _get_free_pages() and > kmalloc(). In the kmalloc case, the modules hang waiting > for memory. Would adding __builtin_return_address(0) to the warning help locate? -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- __alloc_pages: 4-order allocation failed Feng Xian
- Re: __alloc_pages: 4-order allocation failed Marcelo Tosatti
- Re: __alloc_pages: 4-order allocation failed Feng Xian
- Re: __alloc_pages: 4-order allocation fai... Andi Kleen
- Re: __alloc_pages: 4-order allocation... Feng Xian
- Re: __alloc_pages: 4-order alloc... Feng Xian
- Re: __alloc_pages: 4-order alloc... Andi Kleen
- Re: __alloc_pages: 4-order allocation failed Jeff V. Merkey
- Re: __alloc_pages: 4-order allocation failed Mike Galbraith
- Re: __alloc_pages: 4-order allocation failed Szabolcs Szakacsits
- Re: __alloc_pages: 4-order allocation fai... Jeff V. Merkey
- Re: __alloc_pages: 4-order allocation failed Feng Xian
- __alloc_pages: 4-order allocation failed Ho Chak Hung
- Re: __alloc_pages: 4-order allocation failed Jes Sorensen
- Re: __alloc_pages: 4-order allocation failed David Whysong
- Re: __alloc_pages: 4-order allocation failed Marcelo Tosatti