From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Hugh Dickins <hugh@veritas.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1-mm2 0x414 Bad page states
Date: Sat, 19 Nov 2005 15:30:59 +1100 [thread overview]
Message-ID: <437EAA83.6010808@yahoo.com.au> (raw)
In-Reply-To: <200511182142.17432.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Rafael J. Wysocki wrote:
> Hi,
>
> On Friday, 18 of November 2005 21:12, Dominik Brodowski wrote:
>
>>[4294995.698000] Bad page state at free_hot_cold_page (in process 'gaim', page c15eb020)
>>[4294995.698000] flags:0x80000414 mapping:00000000 mapcount:0 count:0
>>[4294995.698000] vm_flags:0x800fb snd_pcm_mmap_data_open+0x0/0x11 snd_pcm_mmap_data_nopage+0x0/0xa7
>
>
> I've got pretty much the same:
>
> Nov 18 21:23:22 albercik kernel: Bad page state at free_hot_cold_page (in process 'artsd', page ffff8100019613b8)
> Nov 18 21:23:22 albercik kernel: flags:0x4000000000000414 mapping:0000000000000000 mapcount:0 count:0
> Nov 18 21:23:22 albercik kernel: vm_flags:0x800fb snd_pcm_mmap_data_open+0x0/0x20 [snd_pcm] snd_pcm_mmap_data_nopage+0x0/0x150 [snd_pcm]
> Nov 18 21:23:22 albercik kernel: Backtrace:
These look like they want the following patch. Does it help?
--
SUSE Labs, Novell Inc.
[-- Attachment #2: snd-pcm-refcount.patch --]
[-- Type: text/plain, Size: 1068 bytes --]
Index: linux-2.6/sound/core/pcm_native.c
===================================================================
--- linux-2.6.orig/sound/core/pcm_native.c 2005-10-09 18:28:51.000000000 +1000
+++ linux-2.6/sound/core/pcm_native.c 2005-11-19 15:29:59.000000000 +1100
@@ -2949,8 +2949,7 @@ static struct page * snd_pcm_mmap_status
return NOPAGE_OOM;
runtime = substream->runtime;
page = virt_to_page(runtime->status);
- if (!PageReserved(page))
- get_page(page);
+ get_page(page);
if (type)
*type = VM_FAULT_MINOR;
return page;
@@ -2992,8 +2991,7 @@ static struct page * snd_pcm_mmap_contro
return NOPAGE_OOM;
runtime = substream->runtime;
page = virt_to_page(runtime->control);
- if (!PageReserved(page))
- get_page(page);
+ get_page(page);
if (type)
*type = VM_FAULT_MINOR;
return page;
@@ -3066,8 +3064,7 @@ static struct page *snd_pcm_mmap_data_no
vaddr = runtime->dma_area + offset;
page = virt_to_page(vaddr);
}
- if (!PageReserved(page))
- get_page(page);
+ get_page(page);
if (type)
*type = VM_FAULT_MINOR;
return page;
next prev parent reply other threads:[~2005-11-19 4:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:15 2.6.15-rc1-mm2 0x414 Bad page states Hugh Dickins
2005-11-18 20:12 ` Dominik Brodowski
2005-11-18 20:42 ` Rafael J. Wysocki
2005-11-19 4:30 ` Nick Piggin [this message]
2005-11-19 4:33 ` Nick Piggin
[not found] ` <Pine.LNX.4.61.0511182214200.4797@goblin.wat.veritas.com>
2005-11-19 19:57 ` Hugh Dickins
2005-11-19 22:42 ` Dominik Brodowski
2005-11-20 10:14 ` Marc Koschewski
2005-11-21 13:02 ` Christian Kujau
[not found] ` <20051122211625.165F114CB@hornet.berlios.de>
2005-11-22 21:32 ` Hugh Dickins
[not found] ` <20051122231603.2209814DA@hornet.berlios.de>
2005-11-23 11:07 ` Dave Airlie
2005-11-23 20:33 ` 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=437EAA83.6010808@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rjw@sisk.pl \
/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