On Mon, 26 Feb 2001, Alan Cox wrote:
> > We can add an allocation flag (__GFP_NO_CRITICAL?) which can be used by
> > sg_low_malloc() (and other non critical allocations) to fail previously
> > and not print the message.
>
> It is just for debugging. The message can go. If anytbing it would be
> We can add an allocation flag (__GFP_NO_CRITICAL?) which can be used by
> sg_low_malloc() (and other non critical allocations) to fail previously
> and not print the message.
It is just for debugging. The message can go. If anytbing it would be more
useful to tack Failed alloc data on the end
We can add an allocation flag (__GFP_NO_CRITICAL?) which can be used by
sg_low_malloc() (and other non critical allocations) to fail previously
and not print the message.
It is just for debugging. The message can go. If anytbing it would be more
useful to tack Failed alloc data on the end of
On Mon, 26 Feb 2001, Alan Cox wrote:
We can add an allocation flag (__GFP_NO_CRITICAL?) which can be used by
sg_low_malloc() (and other non critical allocations) to fail previously
and not print the message.
It is just for debugging. The message can go. If anytbing it would be more
On Sun, 25 Feb 2001, Mike Galbraith wrote:
> The way sg_low_malloc() tries to allocate, failure messages are
> pretty much garanteed. It tries high order allocations (which
> are unreliable even when not stressed) and backs off until it
> succeeds.
>
> In other words, the messages are a red
Well, I Discovered, something strange. I put in a blank new CD-R, so these
errors are not of concern? (In which case why have the kernel log get
spewed with them if they are guaranteed to happen?)
Shawn.
--
Hugged a Tux today? (tm)
On Sun, 25 Feb 2001, Mike Galbraith wrote:
> The way
Well, I Discovered, something strange. I put in a blank new CD-R, so these
errors are not of concern? (In which case why have the kernel log get
spewed with them if they are guaranteed to happen?)
Shawn.
--
Hugged a Tux today? (tm)
On Sun, 25 Feb 2001, Mike Galbraith wrote:
The way
On Sun, 25 Feb 2001, Mike Galbraith wrote:
The way sg_low_malloc() tries to allocate, failure messages are
pretty much garanteed. It tries high order allocations (which
are unreliable even when not stressed) and backs off until it
succeeds.
In other words, the messages are a red
The way sg_low_malloc() tries to allocate, failure messages are
pretty much garanteed. It tries high order allocations (which
are unreliable even when not stressed) and backs off until it
succeeds.
In other words, the messages are a red herring.
-Mike
-
To unsubscribe from this list:
Right now before OOPS:
Mem:62244K av, 61292K used, 952K free, 0K shrd,1496K buff
Swap: 467444K av, 37344K used, 430100K free 29528K cached
I got a lot of things running, several daemons, netscape, and other things. I put
a 400MB swap for now just to help
On Fri, 23 Feb 2001, Shawn Starr wrote:
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
> Feb 23 21:17:47
Em Sat, Feb 24, 2001 at 05:31:55PM -0500, Shawn Starr escreveu:
> Doing so..., Im not sure hot to use ksymoops or where to get that program.
> I just usually use the sysq and dump but its ugly ;-)
http://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/ksymoops-2.4.0.tar.bz2
- Arnaldo
-
To
Doing so..., Im not sure hot to use ksymoops or where to get that program.
I just usually use the sysq and dump but its ugly ;-)
Shawn.
Marcelo Tosatti wrote:
> On Fri, 23 Feb 2001, Shawn Starr wrote:
>
> > Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> > Feb 23
On Fri, 23 Feb 2001, Shawn Starr wrote:
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
> Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
> Feb 23 21:17:47
On Fri, 23 Feb 2001, Shawn Starr wrote:
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
Feb 23 21:17:47 coredump
Doing so..., Im not sure hot to use ksymoops or where to get that program.
I just usually use the sysq and dump but its ugly ;-)
Shawn.
Marcelo Tosatti wrote:
On Fri, 23 Feb 2001, Shawn Starr wrote:
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
Feb 23
Em Sat, Feb 24, 2001 at 05:31:55PM -0500, Shawn Starr escreveu:
Doing so..., Im not sure hot to use ksymoops or where to get that program.
I just usually use the sysq and dump but its ugly ;-)
http://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/ksymoops-2.4.0.tar.bz2
- Arnaldo
-
To
On Fri, 23 Feb 2001, Shawn Starr wrote:
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
Feb 23 21:17:47 coredump
Right now before OOPS:
Mem:62244K av, 61292K used, 952K free, 0K shrd,1496K buff
Swap: 467444K av, 37344K used, 430100K free 29528K cached
I got a lot of things running, several daemons, netscape, and other things. I put
a 400MB swap for now just to help
The way sg_low_malloc() tries to allocate, failure messages are
pretty much garanteed. It tries high order allocations (which
are unreliable even when not stressed) and backs off until it
succeeds.
In other words, the messages are a red herring.
-Mike
-
To unsubscribe from this list:
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 2-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 1-order allocation failed.
Feb 23 21:17:47 coredump kernel: __alloc_pages: 3-order allocation
22 matches
Mail list logo
