[Bug 8414] Re: AMD64: Cannot access the Hardware Clock via any known method.

Sorry, this bug isn't fixed for me. :( :( :( I'm hoping this will reopen the bug? # hwclock --hctosys --utc --debug hwclock from util-linux-ng 2.13 hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy. No usable clock interface found. Cannot access the Hardware Clock via any known

[Bug 8414] Re: AMD64: Cannot access the Hardware Clock via any known method.

This bug has appeared again for my AMD64 hardware in Gutsy (unsure of Feisty) ** Changed in: util-linux (Ubuntu) Status: Fix Released = Incomplete -- AMD64: Cannot access the Hardware Clock via any known method. https://bugs.launchpad.net/bugs/8414 You received this bug notification

[Bug 179021] Re: KVM: rtc lost some interrupts

FWIW, I'm prepared to help manage this task -- KVM: rtc lost some interrupts https://bugs.launchpad.net/bugs/179021 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.

Rada: If you can't find the option when building the kernel, you should be able to edit the .config file -- When using kqemu, rtc: lost some interrupts at 1024Hz. https://bugs.launchpad.net/bugs/82149 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 179021] KVM: rtc lost some interrupts

). This is a great frustration of not just mine, but many users. It would be great to see the KVM promised totally fulfilled. :) All the best, Raphael Kraus ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- KVM: rtc lost some interrupts https://bugs.launchpad.net/bugs/179021 You