On Thu, 5 Jul 2001, David Whysong wrote:
> Jes Sorensen ([EMAIL PROTECTED]) wrote:
>
> >You ran out of memory, ie. there were no more free blocks of 16
> >consecutive pages available in the system. This is what happens on a
> >system with little memory or which is loaded with memory intensive
Jes Sorensen ([EMAIL PROTECTED]) wrote:
>You ran out of memory, ie. there were no more free blocks of 16
>consecutive pages available in the system. This is what happens on a
>system with little memory or which is loaded with memory intensive
>applications.
I'm seeing the same thing here on a ma
>>>>> "Ho" == Ho Chak Hung <[EMAIL PROTECTED]> writes:
Ho> Hi, I got the error __alloc_pages: 4-order allocation failed in a
Ho> module that uses and frees a lot of pages. Basically, I am trying
Ho> implement a page cache for the module. First, I keep all
Hi,
I got the error __alloc_pages: 4-order allocation failed in a module that uses and
frees a lot of pages.
Basically, I am trying implement a page cache for the module. First, I keep allocating
pages using page_cache_alloc() until it fails, then I free a whole bunch of pages
using freepages
On Thu, Apr 26, 2001 at 08:00:12PM +0200, Szabolcs Szakacsits wrote:
>
> On Thu, 26 Apr 2001, Jeff V. Merkey wrote:
The request should fail after two or three attempts rather than hang
the entire system waiting for memory.
Jeff
>
> > I am seeing this as well on 2.4.3 with both _get_free_pages
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.
One possible source of this hang is due to the change below in
2.4.3, non GPF_ATOMIC and non-recursive allocat
The problem is I didn't see those error message on 2.4.2 or 2.4.0, only on
2.4.3. That's the reason I posted the question here. Maybe I will try
2.4.4
Thanks all for you guys!
Alex
On Thu, 26 Apr 2001, Feng Xian wrote:
>
> Yes I am running nvidia module. i tried nv, X use less memory but nv
>
On Thu, Apr 26, 2001 at 09:50:15AM -0400, Feng Xian wrote:
>
> Yes I am running nvidia module. i tried nv, X use less memory but nv
> doesn't give me the NV_GLX extension, xlock will crash for some 3d mode.
In this case you should report any kernel problems you see to NVidia
first, except if you
Yes I am running nvidia module. i tried nv, X use less memory but nv
doesn't give me the NV_GLX extension, xlock will crash for some 3d mode.
Alex
On Thu, 26 Apr 2001, Andi Kleen wrote:
> On Thu, Apr 26, 2001 at 08:09:06AM -0400, Feng Xian wrote:
> > It looks like the X consumes most of the me
On Thu, Apr 26, 2001 at 08:09:06AM -0400, Feng Xian wrote:
> It looks like the X consumes most of the memory (almost used up all the
> physical memory, more than 100M), it uses NVidia driver. I was also
> running pppoe but that took less memory.
You're probably using the NVidia provided driver mo
3 on a Dell dual PIII machine with 128M memory.
>
> 2.4.3 has many known flaws; why not try a pre-2.4.4 kernel?
>
> > __alloc_pages: 4-order allocation failed.
>
> these happen when someone tries to allocate large contiguous blocks.
>
> > and sometime the system will
On Wed, 25 Apr 2001, Marcelo Tosatti wrote:
>
>
> On Wed, 25 Apr 2001, Feng Xian wrote:
>
> > Hi,
> >
> > I am running linux-2.4.3 on a Dell dual PIII machine with 128M memory.
> > After the machine runs a while, dmesg shows,
> >
> > __alloc_pages:
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
.
> After the machine runs a while, dmesg shows,
>
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 3-order allocation failed.
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 4-order allocation failed.
>
On Wed, 25 Apr 2001, Feng Xian wrote:
> Hi,
>
> I am running linux-2.4.3 on a Dell dual PIII machine with 128M memory.
> After the machine runs a while, dmesg shows,
>
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 3-order allocation failed.
> __alloc_p
Hi,
I am running linux-2.4.3 on a Dell dual PIII machine with 128M memory.
After the machine runs a while, dmesg shows,
__alloc_pages: 4-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 4-order allocation failed.
__alloc_pages: 4-order allocation failed
16 matches
Mail list logo
