Re: rtc_cmos: error after first write to wakealarm

On Fri, 15 Jun 2007 08:33:08 +0200
Tino Keitel <[email protected]> wrote:

> 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
> $

If the alarm has already been enabled, you cannot set the next alarm. 
You should disable first.

Yoichi

-
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: Tino Keitel <[email protected]>

• References:
  • rtc_cmos: error after first write to wakealarm
    • From: Tino Keitel <[email protected]>

• Prev by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
• Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
• Previous by thread: rtc_cmos: error after first write to wakealarm
• 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]