linux-kernel - Re: [rtc-linux] 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: <20070622193431.71bed8b5@inspiron>
Date:	Fri, 22 Jun 2007 19:34:31 +0200
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	Tino Keitel <tino.keitel@....de>
Cc:	rtc-linux@...glegroups.com,
	Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>,
	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>
Subject: Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm

On Tue, 19 Jun 2007 19:24:29 +0200
Tino Keitel <tino.keitel@....de> wrote:

> > > 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.
> 
> Isn't it somewhat ridiculous to plan the removal of a feature for
> several months, and then replace it with something that behaves
> differently without any documentation?
> 
> I still wonder how 'cat /sys/class/rtc/rtcX/wakealarm' is expected to
> behave. With 2.6.22-rc5, I get this:
> 
> $ echo 1182351177 > /sys/class/rtc/rtc0/wakealarm 
> $ cat /sys/class/rtc/rtc0/wakealarm
> 2051644873
> 
> There seems to be a constant difference of 869984896 seconds. Is this a
> bug?

 I'll have to check that. Sorry for the delay, i've been a bit busy.


-- 

 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/