linux-kernel - Re: rtc_cmos: error after first write to wakealarm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070615155904.1d1da892.yoichi_yuasa@tripeaks.co.jp>
Date:	Fri, 15 Jun 2007 15:59:04 +0900
From:	Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>
To:	Tino Keitel <tino.keitel@....de>
Cc:	yoichi_yuasa@...peaks.co.jp, linux-kernel@...r.kernel.org,
	rtc-linux@...glegroups.com
Subject: Re: rtc_cmos: error after first write to wakealarm

On Fri, 15 Jun 2007 08:33:08 +0200
Tino Keitel <tino.keitel@....de> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/