From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "Andreas K. Huettel" <mail@akhuettel.de>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [tainted,fglrx] page allocation failure: basic meaning of log messages?
Date: Thu, 3 Apr 2008 10:48:52 -0400 [thread overview]
Message-ID: <20080403144852.GD24239@csclub.uwaterloo.ca> (raw)
In-Reply-To: <alpine.LNX.1.00.0804031318480.10277@localhost>
On Thu, Apr 03, 2008 at 01:22:40PM +0200, Andreas K. Huettel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
> Hi,
>
> #]> Apr 3 09:01:30 bellini hal-system-powe: page allocation failure. order:10, mode:0x4020
> #]> Apr 3 09:01:30 bellini Pid: 327, comm: hal-system-powe Tainted: PF 2.6.24-gentoo-r3 #1
> #]> Apr 3 09:01:30 bellini [<c0140c48>] __alloc_pages+0x2bd/0x2ce
> #]> Apr 3 09:01:30 bellini [<c0140c92>] __get_free_pages+0x39/0x47
> #]> Apr 3 09:01:30 bellini [<f8adcd9e>] firegl_cmmqs_save_fb+0x8e/0x200 [fglrx]
> #]
> #]this messages doesn't mean bug, merely indicate allocation failure.
> #]if any other bad thind doen't happend, you can ignore it.
>
> Swapping like mad without any obvious cause (500M swap in use, 1.5G RAM
> - - which is normally not such a big problem). This however stopped when
> I closed some memory-intensive applications (firefox, vmware).
>
> Since then the machine is running without problems.
firefox 2.x tends to leak memory like crazy in my experience, so it may
be perfectly normal. If you have adobe's flash plugin firefox can leak
very quickly too.
--
Len Sorensen
next prev parent reply other threads:[~2008-04-03 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 9:27 Andreas K. Huettel
2008-04-03 9:34 ` KOSAKI Motohiro
2008-04-03 11:22 ` Andreas K. Huettel
2008-04-03 14:48 ` Lennart Sorensen [this message]
2008-04-03 15:00 ` Peter Zijlstra
2008-04-08 9:39 ` Andreas K. Huettel
2008-04-08 11:19 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080403144852.GD24239@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@akhuettel.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®