From: Ingo Molnar <mingo@elte.hu>
To: Wen-chien Jesse Sung <jesse@cola.voip.idv.tw>
Cc: linux-kernel@vger.kernel.org
Subject: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-17
Date: Wed, 1 Dec 2004 14:27:10 +0100 [thread overview]
Message-ID: <20041201132710.GA8328@elte.hu> (raw)
In-Reply-To: <41ADBE1C.9010807@cola.voip.idv.tw>
* Wen-chien Jesse Sung <jesse@cola.voip.idv.tw> wrote:
> I redo the test with a vanilla 2.6.10-rc2-mm3-V0.7.31-16 again, and it
> still hangs at hwclock. Here's the complete config file.
ok, could you try the -17 kernel i've just uploaded to the usual place:
http://redhat.com/~mingo/realtime-preempt/
does this fix the lockup?
i believe the lockup is an interesting side-effect of threading IRQ#0:
any code within the kernel that loops on jiffies will produce a lockup,
because it starves the timer IRQ thread.
The RTC driver had two such places, but i also found one in the
IRQ-autodetect code. We want to eliminate such code anyway, and a lockup
is certainly an effective way to detect it ;)
to debug such lockups in the future you can do:
echo 1 > /proc/sys/kernel/debug_direct_keyboard
/sbin/hwclock ...
and use the sysrq keys to get a stack dump of the lockup. NOTE: dont use
the keyboard in this mode for too long, it can lock up.
Ingo
next prev parent reply other threads:[~2004-12-01 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 10:17 Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-15 Wen-chien Jesse Sung
2004-12-01 11:37 ` Ingo Molnar
2004-12-01 11:52 ` Ingo Molnar
2004-12-01 12:50 ` Wen-chien Jesse Sung
2004-12-01 13:27 ` Ingo Molnar [this message]
2004-12-01 16:12 ` [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-17 Wen-chien Jesse Sung
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=20041201132710.GA8328@elte.hu \
--to=mingo@elte.hu \
--cc=jesse@cola.voip.idv.tw \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.