From: Miles Lane <miles.lane@gmail.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Lee Revell <rlrevell@joe-job.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: 2.6.15-rc1-mm2 -- Bad page state at free_hot_cold_page (in process 'aplay', page c18eef30)
Date: Sun, 20 Nov 2005 22:59:59 -0800 [thread overview]
Message-ID: <a44ae5cd0511202259q71d2ef1fk294277225f848937@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511201915530.8619@goblin.wat.veritas.com>
On 11/20/05, Hugh Dickins <hugh@veritas.com> wrote:
> On Sun, 20 Nov 2005, Lee Revell wrote:
> > (Added alsa-devel to cc:)
> >
> > Will this change have any ill effects on older kernels?
>
> I think not (except 2.6.5 and earlier didn't define __GFP_COMP).
>
> > If not we should fix it in the ALSA tree right?
>
> Probably, but I'm no authority on the ALSA tree.
>
> And suggest you wait a bit, since I haven't yet signed off on the
> patch that piece will be a part of.
>
> And what about the patch at the bottom (which I had CC'ed to Karsten
> Wiese), is that part of the ALSA tree too? That case isn't so easy:
> the get_page makes a difference, and probably it was right not to do
> it before, yet strange it was the only nopage in the tree which didn't
> get_page.
>
> Hugh
>
> > Lee
> >
> > On Sun, 2005-11-20 at 08:05 +0000, Hugh Dickins wrote:
> > > On Sat, 19 Nov 2005, Miles Lane wrote:
> > > > [17179671.700000] Bad page state at free_hot_cold_page (in process
> > > > 'aplay', page c18eef30)
> > > > [17179671.700000] flags:0x80000414 mapping:00000000 mapcount:0 count:0
> > >
> > > Please let me know if it's not fixed by:
> > >
> > > --- 2.6.15-rc1-mm2/sound/core/memalloc.c 2005-11-12 09:01:28.000000000 +0000
> > > +++ linux/sound/core/memalloc.c 2005-11-19 19:03:32.000000000 +0000
> > > @@ -197,6 +197,7 @@ void *snd_malloc_pages(size_t size, gfp_
> > >
> > > snd_assert(size > 0, return NULL);
> > > snd_assert(gfp_flags != 0, return NULL);
> > > + gfp_flags |= __GFP_COMP; /* compound page lets parts be mapped */
> > > pg = get_order(size);
> > > if ((res = (void *) __get_free_pages(gfp_flags, pg)) != NULL) {
> > > mark_pages(virt_to_page(res), pg);
> > > @@ -241,6 +242,7 @@ static void *snd_malloc_dev_pages(struct
> > > snd_assert(dma != NULL, return NULL);
> > > pg = get_order(size);
> > > gfp_flags = GFP_KERNEL
> > > + | __GFP_COMP /* compound page lets parts be mapped */
> > > | __GFP_NORETRY /* don't trigger OOM-killer */
> > > | __GFP_NOWARN; /* no stack trace print - this call is non-critical */
> > > res = dma_alloc_coherent(dev, PAGE_SIZE << pg, dma, gfp_flags);
Thanks, this did fix the problem for me.
Miles
next prev parent reply other threads:[~2005-11-21 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 6:56 Miles Lane
2005-11-20 8:05 ` Hugh Dickins
2005-11-20 18:14 ` Lee Revell
2005-11-20 19:35 ` Hugh Dickins
2005-11-21 6:59 ` Miles Lane [this message]
2005-11-21 11:52 ` Takashi Iwai
2005-11-21 15:46 ` Hugh Dickins
2005-11-21 15:52 ` Russell King
2005-11-21 16:51 ` Hugh Dickins
2005-11-21 16:17 ` Takashi Iwai
2005-11-21 16:25 ` Russell King
2005-11-21 16:41 ` Takashi Iwai
2005-11-21 17:09 ` Hugh Dickins
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=a44ae5cd0511202259q71d2ef1fk294277225f848937@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®