9.2 amd64bit unexpected prob

fisher99 · 03-16-2005, 05:39 PM

During the use of yast the harddrive went into a freenzy for 10 minutes, as if it was doing something major. The system would freeze for about 10 minutes. Then things would be fine, so I checked dmesg to see what was going on.
The following message repeats itself

Call Trace:<ffffffff80155f26>{out_of_memory+54} <ffffffff8015eac0>{try_to_free_pages+448}
<ffffffff80133950>{autoremove_wake_function+0} <ffffffff80157e32>{__alloc_pages+642}
<ffffffff80159e2e>{do_page_cache_readahead+222} <ffffffff80152a40>{page_wake_function+0}
<ffffffff80153981>{filemap_nopage+337} <ffffffff8015fec0>{do_no_page+544}
<ffffffff80161392>{handle_mm_fault+322} <ffffffff8017060d>{do_sync_read+173}
<ffffffff80341949>{thread_return+41} <ffffffff80120587>{do_page_fault+439}
<ffffffff80133950>{autoremove_wake_function+0} <ffffffff8018257c>{poll_freewait+76}
<ffffffff801828c7>{sys_poll+823} <ffffffff8017075c>{vfs_read+284}
<ffffffff80110c91>{error_exit+0}
Badness in out_of_memory at mm/oom_kill.c:252

I am guessing the hardrive freenzy was the production of the above error message.
What does this mean, what is the problem?

BTW dmesg ended with :
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode

Thanks

fisher99 · 03-16-2005, 05:55 PM

OK after some researching I came across the following :

Quote:

> On Thu, Jan 06, 2005 at 06:03:35PM +0100, Richard Ems wrote:
>
>>Hi list, hi Mr. Mantel,
>>
>>the following "badness" happened on a SuSE 9.2 with all actual updates
>>and SuSE's kernel 2.6.8-24.10-smp.
>>The system is a dual AMD Athlon MP 2200+ with 1GB memory and 1GB swap.
>
>
> This is a warning only (2.6.9 had the swap token breakage that triggered
> suprious oom kills, so the warning was meant to get more info), can you
> try with the kernel of the day?
>
> http://ftp.suse.com/pub/projects/ker...86/SL92_BRANCH
>
> It has my latest oom fixes that I recently posted to l-k and it should
> be very reliable for the first time in oom-killer terms.
>
>

I will try it tomorrow evening, it's a production system, so it's not so
easy to "try".
How can I trigger the oom kills? I'm not sure if I can easily reproduce
this! Do you know a memory eater program other than starting lots of
mozilla's, OpenOffices's, etc.?

So it seems it is a kernel thing, when the memory runs out.
My system: AMD-64 3000+, 1GB RAM, 1GBSWAP

What you guys think?