From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Ben Castricum" <lk0904@bencastricum.nl>
Cc: <linux-kernel@vger.kernel.org>, dwmw2@infradead.org
Subject: Re: 2.6.30-rc1 problems with firmware loading
Date: Sun, 12 Apr 2009 11:21:15 +0100 [thread overview]
Message-ID: <20090412112115.37fe1141@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <8D207FA0B5B5443FAA8178A23C6CA5B9@Seven>
On Sun, 12 Apr 2009 08:20:21 +0200
"Ben Castricum" <lk0904@bencastricum.nl> wrote:
>
> I seem to have some problems with firmware loading since 2.6.30-rc1. Each
> request seems to time out and reports like these are appearing:
At first glance it looks like the module loading changes are expanding
vmas that don't have an owner (->mm) and are not set no account. So the
VM accounting code in strict overcommit modes doesn't know who to bill
for the pages.
next prev parent reply other threads:[~2009-04-12 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 6:20 2.6.30-rc1 problems with firmware loading Ben Castricum
2009-04-12 10:21 ` Alan Cox [this message]
2009-04-12 16:46 ` Rafael J. Wysocki
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=20090412112115.37fe1141@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk0904@bencastricum.nl \
/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