From: "John Kacur" <jkacur@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>, "Ingo Molnar" <mingo@elte.hu>
Subject: 2.6.26.3-rt3 bug report
Date: Mon, 25 Aug 2008 00:51:11 +0200 [thread overview]
Message-ID: <520f0cf10808241551x2fe64e9esadf66634b3790c54@mail.gmail.com> (raw)
I haven't seen this one before.
Bad page state in process 'firefox-bin'
page:ffffe20001011f00 flags:0x0100000000000000
mapping:ffffe20001011f18 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Pid: 4180, comm: firefox-bin Tainted: G W 2.6.26.3-rt3 #3
Call Trace:
[<ffffffff80287a72>] bad_page+0x6f/0x9d
[<ffffffff8029184c>] ? inc_zone_page_state+0x5f/0x6b
[<ffffffff80289046>] free_hot_cold_page+0x88/0x1e6
[<ffffffff8028920b>] free_hot_page+0x10/0x12
[<ffffffff8028922a>] __free_pages+0x1d/0x26
[<ffffffff80294b95>] __pte_alloc+0x8e/0x99
[<ffffffff80294cff>] handle_mm_fault+0x15f/0x766
[<ffffffff8045f2d6>] ? rt_mutex_down_read_trylock+0x1ee/0x1f9
[<ffffffff804629d9>] do_page_fault+0x51d/0x92c
[<ffffffff8021251c>] ? native_sched_clock+0x2a/0x72
[<ffffffff8027c930>] ? ftrace_now+0x9/0xb
[<ffffffff80281548>] ? tracing_hist_preempt_start+0xf1/0x10d
[<ffffffff8021251c>] ? native_sched_clock+0x2a/0x72
[<ffffffff8027c930>] ? ftrace_now+0x9/0xb
[<ffffffff804602f9>] error_exit+0x0/0x56
---------------------------
| preempt count: 00000000 ]
| 0-level deep critical section nesting:
----------------------------------------
next reply other threads:[~2008-08-24 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 22:51 John Kacur [this message]
2008-08-25 23:15 ` 2.6.26.3-rt3 bug report John Kacur
2008-08-26 4:14 ` Jon Masters
2008-08-26 5:49 ` Carsten Emde
2008-08-29 14:29 ` John Kacur
2008-08-30 14:29 ` Carsten Emde
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=520f0cf10808241551x2fe64e9esadf66634b3790c54@mail.gmail.com \
--to=jkacur@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).