From: Jani Monoses <jani@iv.ro>
To: linux-kernel@vger.kernel.org
Subject: hwclock causes __might_sleep dump
Date: Mon, 4 Aug 2003 13:58:19 +0300 [thread overview]
Message-ID: <20030804135819.462edada.jani@iv.ro> (raw)
Hi
at system shutdown when hwclock --systohc is called there's a
might_sleep error dump from the kernel in do_page_fault. I found that
the problem is when hwclock uses direct cmos access when there's no RTC
support in kernel and only when hwclock is compiled with -O3
hwclock does an atomic access achieved with __asm__ cli and sti. Is this
a hwclock bug? I suppose the kernel is not responsible for userland
disabling interrupts ... putting delays and printfs in hwclock either
makes the dump show a different backtrace (although still with 2
do_page_faults) or results in no dump at all.
2.6.0-test1 and test2
reply other threads:[~2003-08-04 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030804135819.462edada.jani@iv.ro \
--to=jani@iv.ro \
--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 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).