linux-kernel - Re: [linux-pm] sleepy linux self-test

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: <20080203051953.GA21183@elte.hu>
Date:	Sun, 3 Feb 2008 06:19:53 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Brownell <david-b@...bell.net>
Cc:	Pavel Machek <pavel@....cz>, linux-pm@...ts.linux-foundation.org,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] sleepy linux self-test


* Ingo Molnar <mingo@...e.hu> wrote:

> > is "wakealarm" something generally available on PC RTCs? I'll try to 
> > look into the BIOS setup, maybe it's just disabled ...
> 
> ok, there was indeed a "RTC Alarm: disabled" option in the BIOS. But 
> no matter how many of those resume-alarm options i enabled, the kernel 
> thinks there's no time capability:
> 
>  [   23.541565] Calling initcall 0xc0c49e00: be_sleepy+0x0/0x170()
>  [   23.547840] PM: no wakelarm-capable RTC
>  [   23.549566] initcall 0xc0c49e00: be_sleepy+0x0/0x170() returned 0.
> 
> i could set date/time of wakeup alarm in the BIOS, so i suspect the 
> chip itself is capable of it. Bootlog and kernel config attached. 
> (maybe i misconfigured something?)

i didnt have all RTC drivers enabled (it was a randconfig .config i 
started out with) - but this did not appear to cure the problem. New 
bootlog and new config attached.

	Ingo

View attachment "config" of type "text/plain" (52730 bytes)

Download attachment "boot.log.bz2" of type "application/x-bzip2" (41783 bytes)