From: Karsten Wiese <fzu@wemgehoertderstaat.de>
To: "Rui Nuno Capela" <rncbc@rncbc.org>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: realtime-preempt patch-2.6.18-rt7 oops
Date: Fri, 3 Nov 2006 12:30:24 +0100 [thread overview]
Message-ID: <200611031230.24983.fzu@wemgehoertderstaat.de> (raw)
In-Reply-To: <42997.194.65.103.1.1162464204.squirrel@www.rncbc.org>
Am Donnerstag, 2. November 2006 11:43 schrieb Rui Nuno Capela:
>
> While on UP kernels everything works great and without major issues to
> report, problem goes here on the SMP/HT one. Simple fact: it hangs,
> freezes in some non-deterministic ways. However, sometimes, it is just a
> matter of a couple of dozen clicks while browsing over those
> funky-ajax-enabled-web2 sites :)
>
> ........
>
> Call Trace:
> [<c011e631>] __activate_task+0x21/0x40
> [<c01209b1>] try_to_wake_up+0x321/0x450
> [<c0144822>] wakeup_next_waiter+0xd2/0x1d0
> [<c0120b59>] wake_up_process_mutex+0x19/0x20
> [<c0300531>] rt_spin_lock_slowunlock+0x41/0x70
> [<c02ff34c>] __schedule+0xc0c/0xee0
> [<c014091a>] hrtimer_interrupt+0x18a/0x250
Does it make a difference, if you build & run with
CONFIG_HIGH_RES_TIMERS disabled?
Karsten
next prev parent reply other threads:[~2006-11-03 11:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 10:43 Rui Nuno Capela
2006-11-03 11:30 ` Karsten Wiese [this message]
2006-11-03 22:55 ` Rui Nuno Capela
2006-11-04 2:08 ` Rui Nuno Capela
2006-11-04 10:54 ` Rui Nuno Capela
2006-11-04 15:08 ` Karsten Wiese
2006-11-05 15:55 ` Rui Nuno Capela
2006-11-05 16:47 ` Rui Nuno Capela
2006-11-05 16:02 ` Daniel Walker
2006-11-05 18:38 ` Rui Nuno Capela
2006-11-05 18:18 ` Daniel Walker
2006-11-06 7:24 ` Mike Galbraith
2006-11-06 9:38 ` Ingo Molnar
2006-11-06 10:02 ` Mike Galbraith
2006-11-06 10:11 ` Ingo Molnar
2006-11-06 10:26 ` Mike Galbraith
2006-11-10 9:31 ` Rui Nuno Capela
2006-11-10 9:33 ` Ingo Molnar
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=200611031230.24983.fzu@wemgehoertderstaat.de \
--to=fzu@wemgehoertderstaat.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rncbc@rncbc.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®