From: reinette chatre <reinette.chatre@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"lkml@Think-Future.de" <lkml@Think-Future.de>,
Linux Kernel-Liste <linux-kernel@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: PROBLEM: iwlagn kernel 2.6.32.3 ooops
Date: Tue, 09 Feb 2010 09:04:52 -0800 [thread overview]
Message-ID: <1265735092.2551.1835.camel@rchatre-DESK> (raw)
In-Reply-To: <20100209165247.GB2512@dhcp-lab-161.englab.brq.redhat.com>
Hi Stanislaw,
On Tue, 2010-02-09 at 08:52 -0800, Stanislaw Gruszka wrote:
>
> > > [250420.677168] Pid: 11584, comm: ip Not tainted 2.6.32.3 #5
> > > [250420.677173] Call Trace:
> > > [250420.677190] [<c10a53f8>] ? __alloc_pages_nodemask+0x518/0x5f0
> > > [250420.677204] [<c1007c20>] ? dma_generic_alloc_coherent+0x0/0x100
> > > [250420.677214] [<c1007c92>] ? dma_generic_alloc_coherent+0x72/0x100
> > > [250420.677224] [<c1007c20>] ? dma_generic_alloc_coherent+0x0/0x100
> > > [250420.677241] [<fca1c9d5>] ? iwl_tx_queue_init+0x285/0x380 [iwlcore]
>
> That is at initialization time. To avoid atomic allocation we can just
> use dma_alloc_coherent instead of pci_alloc_consistent. I'm going to
> prepare a patch.
I do not understand your goal here ... as seen in this trace
pci_alloc_consistent itself already calls dma_alloc_coherent right away.
Reinette
next prev parent reply other threads:[~2010-02-09 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100206170348.GB9411@localhost>
2010-02-08 22:31 ` PROBLEM: iwlagn kernel 2.6.32.3 ooops Andrew Morton
2010-02-08 23:00 ` reinette chatre
2010-02-09 0:40 ` [Ilw] " reinette chatre
2010-02-09 16:52 ` Stanislaw Gruszka
2010-02-09 17:04 ` reinette chatre [this message]
2010-02-10 8:21 ` Stanislaw Gruszka
2010-02-10 13:07 ` [PATCH] iwlwifi: use dma_alloc_coherent Stanislaw Gruszka
2010-02-10 17:47 ` reinette chatre
2010-02-18 12:35 ` lkml
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=1265735092.2551.1835.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkml@Think-Future.de \
--cc=sgruszka@redhat.com \
/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