| 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
| ||
|
Date: Tue, 19 Jun 2007 14:24:04 +0200 From: Alessandro Zummo <alessandro.zummo@...ertech.it> To: rtc-linux@...glegroups.com Cc: tino.keitel@....de, Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>, linux-kernel@...r.kernel.org Subject: Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm On Fri, 15 Jun 2007 09:03:19 +0200 Tino Keitel <tino.keitel@....de> wrote: > > > 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. > > Ah, ok. > > Where is the documentation that describes that I have to disable it > first, and how to do this? A migration document for /proc/acpi/alarm > users would be nice, too. Well, I guess there is no documentation. Maybe we could add a dev_warn with an explicit message. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it - 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/
Powered by blists - more mailing lists