From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: rtc_cmos: error after first write to wakealarm
Date: Fri, 15 Jun 2007 08:33:08 +0200 [thread overview]
Message-ID: <20070615063308.GA18089@dose.home.local> (raw)
Hi,
I have the following strange behaviour with rtc_cmos:
$ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
bash: echo: write error: Device or resource busy
$ rmmod rtc_cmos
$ modprobe rtc_cmos
$ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
$ echo 1181934240 > /sys/class/rtc/rtc0/wakealarm
bash: echo: write error: Device or resource busy
$
The kernel is git eedab661a51966c454e38c17266a531aa58b4a98 (something
after 2.6.22-rc4).
Regards,
Tino
next reply other threads:[~2007-06-15 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 6:33 Tino Keitel [this message]
2007-06-15 6:59 ` rtc_cmos: error after first write to wakealarm Yoichi Yuasa
2007-06-15 7:03 ` Tino Keitel
2007-06-19 12:24 ` [rtc-linux] " Alessandro Zummo
2007-06-19 17:24 ` Tino Keitel
2007-06-22 17:34 ` Alessandro Zummo
2007-06-22 18:45 ` David Brownell
2007-06-22 19:44 ` Tino Keitel
2007-06-23 3:18 ` David Brownell
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=20070615063308.GA18089@dose.home.local \
--to=tino.keitel@gmx.de \
--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