public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <A.K.Huettel@tudelft.nl>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	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: Tue, 8 Apr 2008 11:39:38 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.1.00.0804081125140.22515@localhost> (raw)
In-Reply-To: <1207234830.8514.838.camel@twins>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


#]> > #]> 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. 
(...)
#]
#]An order 10 alloc (4 mb contiguous) isn't likely to succeed by any
#]measure. Lumpy reclaim will try very hard and likely cause that swap
#]storm you taked about, but relying on order 10 allocs is insane.


Question - this seems to me not to be a kernel issue (correct me if I'm 
wrong) and thus I'd like to take it to the proper place...
Where should I file this as bug? Is this a hald problem or something more 
complicated?

The swap storm is perfectly reproducible with X/fglrx, compiz and vmware 
workstation running - after resume from suspend2ram it starts. No compiz - 
no problem. No vmware - no problem... Closing vmware -> swapping stops.

If you think this is hopeless since too much closed source software is 
involved, tell me... :-]


Thanks, Andreas




- --
This message is transmitted using 100% recycled electrons.
- --
- ---------------------------------------------------------------------
Dr. Andreas K. Huettel                  tel. +31 15 27 88102  (univ.)
Molecular Electronics and Devices            +31 6 42527466  (mobile)
Kavli Institute of Nanoscience Delft
Delft University of Technology                 A.K.Huettel@tudelft.nl
PO Box 5046, 2600 GA Delft                          mail@akhuettel.de
The Netherlands                     http://www.akhuettel.de/research/
- ---------------------------------------------------------------------
Please use GNUPG or PGP for signed and encrypted email. My public key
can be found at  http://www.akhuettel.de/pgp_key.php

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFH+z1f3ao2Zwy3NWoRA8/iAJ0bLbIFJ9FfHolzuw4eOsNalMhMQACfTBxm
IEKmTD381DwK2Atl4mJB/24=
=jvjl
-----END PGP SIGNATURE-----

  reply	other threads:[~2008-04-08  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  9:27 [tainted,fglrx] page allocation failure: basic meaning of log messages? 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
2008-04-03 15:00       ` Peter Zijlstra
2008-04-08  9:39         ` Andreas K. Huettel [this message]
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=alpine.LNX.1.00.0804081125140.22515@localhost \
    --to=a.k.huettel@tudelft.nl \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=mail@akhuettel.de \
    --cc=peterz@infradead.org \
    /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