From: "John Kacur" <jkacur@gmail.com>
To: "Carsten Emde" <Carsten.Emde@osadl.org>
Cc: "Jon Masters" <jonathan@jonmasters.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.26.3-rt3 bug report
Date: Fri, 29 Aug 2008 16:29:03 +0200 [thread overview]
Message-ID: <520f0cf10808290729q1d99b915s1543256796c8eeb7@mail.gmail.com> (raw)
In-Reply-To: <48B39969.8060501@osadl.org>
On Tue, Aug 26, 2008 at 7:49 AM, Carsten Emde <Carsten.Emde@osadl.org> wrote:
> Jon Masters wrote:
>> On Tue, 2008-08-26 at 01:15 +0200, John Kacur wrote:
>>> Slightly different form today.
>>> Bad page state in process 'firefox-bin'
>>> page:ffffe20000daa360 flags:0x0100000000000000
>>> mapping:ffffe20000daa378 mapcount:0 count:0
>>> Trying to fix it up, but a reboot is needed
>>> Backtrace:
>>> Pid: 16955, comm: firefox-bin Not tainted 2.6.26.3-rt3 #3
>> Er, does firefox run reliably on a non-RT 2.6.26.3 kernel? This many
>> random calls to bad_page suggests more of a RAM problem.
> Don't think so. Same problem here:
> Bad page state in process 'bonobo-activati'
> page:c18f66fc flags:0x40000000 mapping:c18f670c mapcount:0 count:0
> Trying to fix it up, but a reboot is needed
> Backtrace:
> Pid: 4169, comm: bonobo-activati Not tainted 2.6.26.3-rt3 #2
> [<c0438e52>] ? printk+0x14/0x1a
> [<c026e8ef>] bad_page+0x4e/0x79
> [<c026f3d3>] free_hot_cold_page+0x5b/0x1dc
> [<c026f5a1>] free_hot_page+0xf/0x11
> [<c026f5c3>] __free_pages+0x20/0x2b
> [<c02789a0>] __pte_alloc+0x6f/0x77
> [<c0278a4d>] handle_mm_fault+0xa5/0x56c
> [<c0243a1c>] ? rt_mutex_down_read+0x15c/0x164
> [<c0218759>] do_page_fault+0x2c1/0x674
> [<c021b21d>] ? enqueue_task+0x5a/0x66
> [<c043bb66>] ? __spin_unlock_irqrestore+0x24/0x42
> [<c0241e4f>] ? rt_mutex_adjust_prio+0x1a/0x31
> [<c043bc92>] ? __spin_lock_irqsave+0x1e/0x38
> [<c021f37d>] ? try_to_wake_up+0x176/0x180
> [<c043bb5a>] ? __spin_unlock_irqrestore+0x18/0x42
> [<c0241e4f>] ? rt_mutex_adjust_prio+0x1a/0x31
> [<c0241e61>] ? rt_mutex_adjust_prio+0x2c/0x31
> [<c0241e61>] ? rt_mutex_adjust_prio+0x2c/0x31
> [<c043a8f7>] ? rt_write_slowunlock+0x1cd/0x1d5
> [<c027ccb0>] ? mprotect_fixup+0x238/0x282
> [<c0259384>] ? audit_syscall_exit+0x2b6/0x2d1
> [<c0204a4e>] ? resume_userspace+0x6/0x1c
> [<c0218498>] ? do_page_fault+0x0/0x674
> [<c043bf02>] error_code+0x72/0x78
>
Hi Carsten
Any progress or ideas here?
Thank you
John
next prev parent reply other threads:[~2008-08-29 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 22:51 2.6.26.3-rt3 bug report John Kacur
2008-08-25 23:15 ` John Kacur
2008-08-26 4:14 ` Jon Masters
2008-08-26 5:49 ` Carsten Emde
2008-08-29 14:29 ` John Kacur [this message]
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=520f0cf10808290729q1d99b915s1543256796c8eeb7@mail.gmail.com \
--to=jkacur@gmail.com \
--cc=Carsten.Emde@osadl.org \
--cc=jonathan@jonmasters.org \
--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).