Re: kernel: __alloc_pages: 1-order allocation failed

Daniel Phillips
2001-08-29T18:00:35Z

On August 29, 2001 06:14 pm, Andrew Kay wrote:
> > OK, it's not a bounce buffer because the allocation isn't __GFP_WAIT
(0x10).
> > It's GFP_ATOMIC and there are several hundred of those throughout the
kernel so
> > I'm not going to try to guess which one. Could you please pass a few of
your
> > backtraces through ksymoops make them meaningful?
> > Daniel
>
> I'm not sure I did this right, but here is my attempt. I ran a
> 'ksymoops' and gave it a couple of the errors. The parts that look
> somewhat recognizable are the sk98lin, which is a Syskonnect gig over
> copper card. It is the only module I have running on the system.

Close, but see the warning where it tells you your System.map doesn't match
your running kernel. Try symlinking /boot/System.map to the System.map in
the source tree you built from.

> Warning: You did not tell me where to find symbol information. I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc. ksymoops -h explains the options.

I'm willing to guess at this point that this atomic failure is not a bug, the
only bug is that we print the warning message, potentially slowing things
down. I'd like to see a correct backtrace first.

Do you detect any slowdown in your system when you're getting these messages?
I wouldn't expect so from what you've described so far.

--
Daniel