Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Lukas Hejtmanek" <xhejtman@ics.muni.cz>
Cc: "maximilian attems" <max@stro.at>, linux-wireless@vger.kernel.org
Subject: Re: Page allocation failure in 2.6.26-rc2 (iwl4965 driver)
Date: Thu, 5 Jun 2008 11:54:36 +0300	[thread overview]
Message-ID: <1ba2fa240806050154w6bee2f08n80031e09ac12e9ed@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240806041209i5e3fbb35r5667314ea9417379@mail.gmail.com>

On Wed, Jun 4, 2008 at 10:09 PM, Tomas Winkler <tomasw@gmail.com> wrote:
> 2008/6/4 Lukas Hejtmanek <xhejtman@ics.muni.cz>:
>> On Wed, Jun 04, 2008 at 03:04:52PM +0200, maximilian attems wrote:
>>> similar with 2.6.25-rc3-git7 not a regression. happens for me since
>>> early merge of iwlwifi after several resume and suspend cycles + mem
>>> pressure.
>>
>> Jiri Slaby suggested that the iwl driver should not try to alloc 64kB (order
>> 4) using kalloc but vmalloc should be used instead. While not understanding
>> iwl driver internals, I cannot say whether it can be replaced per se.
>>
>
> We my try it but the problem is somewhere else.

Actually I've already posted the patch that fixes allocation. It' just
not in rc2
http://marc.info/?l=linux-wireless&m=121205035427353&w=2

Tomas

  reply	other threads:[~2008-06-05  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 13:03 Page allocation failure in 2.6.26-rc2 (iwl4965 driver) Lukas Hejtmanek
2008-06-04 13:04 ` maximilian attems
2008-06-04 18:43   ` Tomas Winkler
2008-06-04 18:57   ` Lukas Hejtmanek
2008-06-04 19:09     ` Tomas Winkler
2008-06-05  8:54       ` Tomas Winkler [this message]
2008-06-05  9:43         ` Lukas Hejtmanek
2008-06-05 10:43           ` Tomas Winkler

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=1ba2fa240806050154w6bee2f08n80031e09ac12e9ed@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=max@stro.at \
    --cc=xhejtman@ics.muni.cz \
    /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