Hi,
I'm running a dual PIII, 3GB box (2.4.0.SuSE and 2.4.4.SuSE) getting the error
above, despite the fact the ~700MB are still available. In conjunction w/ the
log message I get fork failures (out of memory)...
I'm running 5500 processes having devices open and doing IP. Many of the
processes
On 23 Jan 2001, Yann Dupont wrote:
> I remember sawing that those errors were due to improperly written
> drivers . Is the buslogic driver or tape driver are to blame here ?? Or
> maybe this is a vm balancing issue ?
Could you please send the output of "Alt+SysRq+m" (kernel must be compiled
wit
I had thoses errors messages on 2.4.1-pre9 :
__alloc_pages: 2-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
(ad nauseum)
I was doing backups on scsi streamers using tar ;
The files are on a md0 array, file system is reiserfs;
the
On Sun, Jan 07 2001, Rik van Riel wrote:
> > __alloc_pages: 3-order allocation failed.
>
> This debugging check should probably be removed around
> 2.4.5, in the mean time it is much too useful to track
> down badly behaving device drivers ;)
It need not be a badly written dri
On Sun, 7 Jan 2001, John O'Donnell wrote:
> What does this message mean in my dmesg output?
>
> __alloc_pages: 3-order allocation failed.
It means something in the kernel is trying to allocate an
area of 8 physically contiguous pages, but that wasn't
available so the allocat
What does this message mean in my dmesg output?
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
reset_xmit_timer sk=c5b3a680 1 when
Hi Rik,
A simple test seems to show problems with page allocator.
a) take a 6G RAM machine
b) take a 70G harddisk
c) mke2fs on it
observe lots of "0-order allocation failures" while looking at
/proc/meminfo reveals that I still have 5.1G of free memory (presumably
some of it in NORMAL zone, n
On Thu, 2 Nov 2000, Anthony Towns wrote:
> On Wed, Nov 01, 2000 at 01:42:17PM -0800, Dunlap, Randy wrote:
> > > Is this bug in the usb-driver (usb-uhci), in the camera's driver
> > > (cpia_usb) or in the v4l?
> > ~~
> > Could there be a memory leak as well? But I e
"Pasi Kärkkäinen" wrote:
>
> I added show_stack(0); to the mm/page_alloc.c :
>
> /* No luck.. */
> printk(KERN_ERR "__alloc_pages: %lu-order allocation failed.\n", order)
> show_stack(0);
> return NULL;
>
> Then, when the first stack-dump came to kern.log, I gave
Rik van Riel; Forever shall I be.;
> [EMAIL PROTECTED]
> Subject: Re: 3-order allocation failed
>
>
> On Wed, Nov 01, 2000 at 01:42:17PM -0800, Dunlap, Randy wrote:
> > > Is this bug in the usb-driver (usb-uhci), in the camera's driver
> > > (cpia_usb) or in t
On Wed, Nov 01, 2000 at 01:42:17PM -0800, Dunlap, Randy wrote:
> > Is this bug in the usb-driver (usb-uhci), in the camera's driver
> > (cpia_usb) or in the v4l?
> ~~
> Could there be a memory leak as well? But I expect that
> it's simply that memory is just fragme
> __alloc_pages: 2-order allocation failed.
> > > > __alloc_pages: 2-order allocation failed.
> > > > __alloc_pages: 5-order allocation failed.
> > > > __alloc_pages: 4-order allocation failed.
> > > > __alloc_pages: 3-order allocation failed.
>
.
> > > __alloc_pages: 5-order allocation failed.
> > > __alloc_pages: 4-order allocation failed.
> > > __alloc_pages: 3-order allocation failed.
> > > __alloc_pages: 2-order allocation failed.
> > > __alloc_pages: 5-order allocation failed.
> > >
>
.
> > > __alloc_pages: 5-order allocation failed.
> > > __alloc_pages: 4-order allocation failed.
> > > __alloc_pages: 3-order allocation failed.
> > > __alloc_pages: 2-order allocation failed.
> > > __alloc_pages: 5-order allocation failed.
> > >
>
c_pages: 4-order allocation failed.
> > __alloc_pages: 3-order allocation failed.
> > __alloc_pages: 2-order allocation failed.
> > __alloc_pages: 5-order allocation failed.
> >
> > Any ideas?
>
> I'm getting __alloc_pages: 7-order allocation failed.
> all t
es: 2-order allocation failed.
> __alloc_pages: 5-order allocation failed.
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 3-order allocation failed.
> __alloc_pages: 2-order allocation failed.
> __alloc_pages: 5-order allocation failed.
>
>
> Any ideas?
>
On Thu, 26 Oct 2000 23:52:02 +1100,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>[ You could put a show_stack(0) in here, but I believe ksymoops
> doesn't understand show_stack() output ].
It does, and extracts the "Call Trace:" data. The stack is not printed
by ksymoops because it does not have
ailed.
> __alloc_pages: 4-order allocation failed.
> __alloc_pages: 3-order allocation failed.
> __alloc_pages: 2-order allocation failed.
> __alloc_pages: 5-order allocation failed.
>
> Any ideas?
Nope - USB problem. I suggest you apply this:
--- linux-2.4.0-test10-pre5/mm/pa
on failed.
__alloc_pages: 5-order allocation failed.
__alloc_pages: 4-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 5-order
"Pasi Kärkkäinen" wrote:
>
> I'm using 2.4.0-test10-pre5 on a PIII (compiled with gcc 2.7.2.3) and
> ...
gcc-2.7.2.3 miscompiles kernel/module.c and it has been decided that
this will not be worked around. The new baseline gcc release for x86
is gcc-2.91.66 (otherwise known as egcs-1.1.2).
-
To
ges
to the syslog:
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order
21 matches
Mail list logo
