* Ingo Molnar <mingo@elte.hu> wrote: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?) Ingo
| Ian Campbell | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Justin Piszcz | Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195... |
| Alan | Re: [RFC] Heads up on sys_fallocate() |
| Matthias Scheler | Re: HEADS UP: timecounters (branch simonb-timecounters) merged into -current |
| David Laight | long usernames |
| Quentin Garnier | Re: Understanding foo_open, foo_read, etc. |
| Jared D. McNeill | Breaking binary compatibility for /dev/joy |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
