rtc_cmos: error after first write to wakealarm

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: rtc_cmos: error after first write to wakealarm
  - From: Yoichi Yuasa <[email protected]>

Prev by Date: Re: [PATCH] cdrom_sysctl_info fix
Next by Date: Re: Instead of GPL License - Why not LKL? (Linux Kernel License)
Previous by thread: Instead of GPL License - Why not LKL? (Linux Kernel License)
Next by thread: Re: rtc_cmos: error after first write to wakealarm
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]