From: Alex Belits <abelits@phobos.illtel.denver.co.us>
To: linux-kernel@vger.kernel.org
Subject: 2.6.15 -- Bad page state (again)
Date: Thu, 05 Jan 2006 11:01:47 -0700 [thread overview]
Message-ID: <43BD5F0B.7060608@phobos.illtel.denver.co.us> (raw)
This happened on Alpha (Miata, Digital Workstation 500au), with plain
2.6.15 when trying to run esd to talk to ALSA (snd-es18xx). In earlier
versions this did not happen, however sound still did not work properly
-- it was looping with no interrupts counted in /proc/interrupts for
that device. Kernel was built with CONFIG_ALPHA_GENERIC, as opposed to
CONFIG_ALPHA_MIATA because CONFIG_ALPHA_MIATA for some reason disabled
serial interrupts.
--- 8< ---
Jan 4 08:24:19 dvk3 kernel: Bad page state at free_hot_cold_page (in
process 'esd', page fffffc0000481438)
Jan 4 08:24:19 dvk3 kernel: flags:0x0000000000000414
mapping:0000000000000000 mapcount:0 count:0
Jan 4 08:24:19 dvk3 kernel: Backtrace:
Jan 4 08:24:19 dvk3 kernel: fffffc00095d3c88 0000000000000000
fffffc000105b218 0000000000000000
Jan 4 08:24:19 dvk3 kernel: fffffc0001062afc fffffc0000481438
0000000000063309 fffffc0009f9d328
Jan 4 08:24:19 dvk3 kernel: 00000200004ca000 00000000000006d0
fffffc0001062608 fffffc000a6e18c0
Jan 4 08:24:19 dvk3 kernel: fffffc0001072c4c fffffc00016afc00
fffffc0001068038 fffffc0000481438
Jan 4 08:24:19 dvk3 kernel: fffffc0001068278 00000200004d8000
fffffc00089e4000 fffffc00095d3e28
Jan 4 08:24:19 dvk3 kernel: fffffc000892a800 0000000000000000
fffffc000892a800 00000200004d8000
Jan 4 08:24:19 dvk3 kernel: Trace:
Jan 4 08:24:19 dvk3 kernel: [free_hot_cold_page+160/364]
free_hot_cold_page+0xa0/0x16c
Jan 4 08:24:19 dvk3 kernel: [__page_cache_release+236/256]
__page_cache_release+0xec/0x100
Jan 4 08:24:19 dvk3 kernel: [put_page+208/228] put_page+0xd0/0xe4
Jan 4 08:24:19 dvk3 kernel: [free_page_and_swap_cache+112/136]
free_page_and_swap_cache+0x70/0x88
Jan 4 08:24:19 dvk3 kernel: [zap_pte_range+464/644]
zap_pte_range+0x1d0/0x284
Jan 4 08:24:19 dvk3 kernel: [unmap_page_range+396/516]
unmap_page_range+0x18c/0x204
Jan 4 08:24:19 dvk3 kernel: [context_switch+280/372]
context_switch+0x118/0x174
Jan 4 08:24:19 dvk3 kernel: [unmap_vmas+276/544] unmap_vmas+0x114/0x220
Jan 4 08:24:19 dvk3 kernel: [unmap_region+176/364] unmap_region+0xb0/0x16c
Jan 4 08:24:19 dvk3 kernel: [do_munmap+304/352] do_munmap+0x130/0x160
Jan 4 08:24:19 dvk3 kernel: [sys_munmap+128/216] sys_munmap+0x80/0xd8
Jan 4 08:24:19 dvk3 kernel: [entSys+164/192] entSys+0xa4/0xc0
Jan 4 08:24:19 dvk3 kernel:
Jan 4 08:24:19 dvk3 kernel: Trying to fix it up, but a reboot is needed
--- >8 ---
(identical entries followed in the log).
This looks similar to what was reported for 2.6.15-rc1-mm2, except that
this is 2.6.15.
--
Alex Belits
reply other threads:[~2006-01-05 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43BD5F0B.7060608@phobos.illtel.denver.co.us \
--to=abelits@phobos.illtel.denver.co.us \
--cc=linux-kernel@vger.kernel.org \
/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®