From: Jan Kiszka <jan.kiszka@domain.hid>
To: Rodrigo Rosenfeld Rosas <lbocseg@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] 2.6.17 hang on "will halt now" (possibly SMI related)
Date: Sun, 02 Jul 2006 15:29:25 +0200 [thread overview]
Message-ID: <44A7CA35.5060009@domain.hid> (raw)
In-Reply-To: <200606301654.45844.lbocseg@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Rodrigo Rosenfeld Rosas wrote:
> I began to experience a problem since 2.6.17 when shutting down my PC.
>
> I noticed the problem just after I recompiled my kernel to enable the SMI
> workaround. I, then rebooted the new kernel and when I tried to shutdown the
> system, it stopped on "will halt now" message or something like.
>
> The same behavior is occurring both in home (Pentium-3 550 MHz) and at
> college (P4-1.7GHz). In both systems, Xenomai advised me to enable SMI
> workaround. Actually, at home, the worst latency with the latency test was
> about 20us independently from enabling or not the SMI workaround.
>
> Do someone else experienced a similar problem when upgrading to 2.6.17?
Yep. Should be fixed now, see latest trunk.
It was a deadlock due to clumsy unregistration of the reboot notifier
from its own handler. I think the locking of the kernel changed in
2.6.17 (RCU) and made this fatal.
Jan
PS: 20us on a P-III 550 is a bit too good. I guess some serious load is
missing (cache load, IRQs, ...).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-07-02 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 19:54 [Xenomai-core] 2.6.17 hang on "will halt now" (possibly SMI related) Rodrigo Rosenfeld Rosas
2006-07-02 13:29 ` Jan Kiszka [this message]
2006-07-03 17:37 ` [Xenomai-core] 2.6.17 hang on "will halt now" (possibly SMI related) [SOLVED] Rodrigo Rosenfeld Rosas
2006-07-03 17:45 ` Jan Kiszka
2006-07-03 18:04 ` Rodrigo Rosenfeld Rosas
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=44A7CA35.5060009@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=lbocseg@domain.hid \
--cc=xenomai@xenomai.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.