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 driver, it could be a
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 allocation failed...
This
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
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
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 allocation failed...
This
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 driver, it could be a fine
6 matches
Mail list logo
