[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
Marking this bug as Fix Released per the previous comment. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
As requested, I've tested the Intrepid Ibex 8.10 Alpha 5 live-cd with kernel 2.6.27 on the same machine as my report on 2007-04-02 (Dell C521, AMD64, nForce4). I can report that with kernel version 'Linux ubuntu 2.6.27-2-generic #1 SMP Thu Aug 28 17:18:43 UTC 2008 x86_64' and KVM version '1:72+dfsg- 1ubuntu2' the problem with spurious kernel messages about lost interrupts when using KVM is now _gone_. The virtualized operating systems are stable (survive some random web browsing and a compilation of git), and the only message I got in the kernel logs about KVM were these two lines: [ 823.003552] kvm: 8793: cpu0 unhandled rdmsr: 0x417 [ 824.618630] kvm: emulating exchange as write But, again, no messsages about 'rtc: lost some interrupts at 1024Hz.' Here are some of the relevant sections of the kernel log on this machine: [0.00] ACPI: PM-Timer IO Port: 0x1008 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, version 0, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) [0.00] ACPI: IRQ9 used by override. [0.00] ACPI: IRQ14 used by override. [0.00] ACPI: IRQ15 used by override. [0.00] Setting APIC routing to flat [0.00] ACPI: HPET id: 0x10b9a201 base: 0xfeff [0.00] Using ACPI (MADT) for SMP configuration information [0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs [...] [0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash -- console-setup/layoutcode=be [0.00] Initializing CPU#0 [...] [0.00] TSC calibrated against PM_TIMER [0.00] Detected 2204.602 MHz processor. [0.004000] spurious 8259A interrupt: IRQ7. [...] [0.004000] hpet clockevent registered [0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 4409.20 BogoMIPS (lpj=8818408) [...] [0.005640] using C1E aware idle routine [0.007178] ACPI: Core revision 20080609 [0.009141] ACPI: Checking initramfs for custom DSDT [0.364022] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1 [0.368023] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [0.368023] ...trying to set up timer (IRQ0) through the 8259A ... [0.368023] . (found apic 0 pin 0) ... [0.376023] ... failed. [0.376023] ...trying to set up timer as Virtual Wire IRQ... [0.376023] . failed. [0.376023] ...trying to set up timer as ExtINT IRQ... [0.418551] . works. [0.418553] CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 02 [0.418559] Using local APIC timer interrupts. [0.420029] APIC timer calibration result 12526194 [0.420032] Detected 12.526 MHz APIC timer. [...] [0.526943] ACPI: EC: Look up EC in DSDT [0.568739] ACPI: Interpreter enabled [0.568747] ACPI: (supports S0 S1 S3 S4 S5) [0.568810] ACPI: Using IOAPIC for interrupt routing [0.620451] ACPI: PCI Root Bridge [PCI0] (:00) [...] [1.264670] hpet0: at MMIO 0xfeff, IRQs 2, 8, 31 [1.264685] hpet0: 3 32-bit timers, 2500 Hz [1.268054] Switched to high resolution mode on CPU 0 [1.268212] Switched to high resolution mode on CPU 1 [1.271622] tracer: 1286 pages allocated for 65536 entries of 80 bytes [1.271632]actual entries 65586 [...] [1.271926] ACPI: RTC can wake from S4 [...] [2.248322] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0 [2.248360] rtc0: alarms up to one year, y3k, hpet irqs -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
Hi Guys, Looking at the Ubuntu kernel git trees for both Hardy and the upcoming Intrepid Ibex the CONFIG_HPET_EMULATE_RTC kernel config option looks to be enabled for both kernels: [EMAIL PROTECTED]:~/ubuntu-hardy/debian/config$ grep -rn CONFIG_HPET_EMULATE_RTC * amd64/config:960:CONFIG_HPET_EMULATE_RTC=y i386/config.server:632:CONFIG_HPET_EMULATE_RTC=y i386/config.virtual:164:CONFIG_HPET_EMULATE_RTC=y i386/config.generic:632:CONFIG_HPET_EMULATE_RTC=y [EMAIL PROTECTED]:~/ubuntu-intrepid/debian/config$ grep -rn CONFIG_HPET_EMULATE_RTC * amd64/config:984:CONFIG_HPET_EMULATE_RTC=y i386/config:1055:CONFIG_HPET_EMULATE_RTC=y Austin mentioned his issue was resolved with the Hardy kernel. Can anyone else confirm with either the Hardy or Intrepid kernel? Thanks. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
I am reassigning this to the 'linux' task to make sure that the config is changed ** Changed in: linux (Ubuntu) Sourcepackagename: kqemu = linux Status: Incomplete = New -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
Well, the problems I was having with the zaptel package and having interrupts not work right have completely gone in Hardy. I don't know about the original bug in kqemu. Has anyone tested it with 2.6.24 in Hardy? ** Changed in: kqemu (Ubuntu) Status: New = Incomplete -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
Hi, I know this forum is Ubuntu-specific, but I'm dealing with the same problem on Debian. I've installed the linux-source-2.6.22 package, but there's no Provide RTC interrupt setting in the Processor type menu. Any ideas? -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
I had the same problem with a 2.6.20 kernel on a Dell PowerEdge 2950 server (running on two Intel quadcore 64 bit xeons) running Ubuntu Feisty. I can confirm that the problem disappeared after recompiling the kernel with Provide RTC interrupt. Thanks for your help. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
The machine I saw this problem on is currently running Fedora 7 (kernel version 2.6.21-1.3228.fc7 to be precise), and it still shows the same problem when running KVM (version 0.24), *with* CONFIG_HPET_EMULATE_RTC enabled. However, there clearly is a rate-limiting patch in said kernel, as the rtc: lost some interrupts at 1024Hz message is only repeated about three times and then never appears again. Bill, Does vmware server, or any of the virtualized devices, use kqemu??? No it/they don't, but the methods used to virtualize the timer in the guests are comparable, so that's why you're seeing the same errors. There's nothing wrong with kqemu or vmware server, but rather in your BIOS (have you tried updating it yet?). I have read (on http://lwn.net/Articles/240080/), that there will be an option in 2.6.23 to *forcibly* enable the HPET timer even if your BIOS doesn't initialize it, but it seems limited to Intel chipsets from what I can gather. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
This bug affects the zaptel package. The ztdummy is non-functional with this bug. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
I have tried setting the CONFIG_HPET_EMULATE_RTC option and I still get these messages. Below is cat /proc/drivers/rtc: rtc_time: 10:50:40 rtc_date: 2007-06-11 rtc_epoch : 1900 alarm : 00:00:00 DST_enable : no BCD : yes 24hr: yes square_wave : no alarm_IRQ : no update_IRQ : no periodic_IRQ: no periodic_freq : 1024 batt_status : okay Which clearly shows the problem. Periodic IRQ is not set. The RTC driver test example out of the Documentation/rtc.txt file gives: RTC Driver Test Example. Counting 5 update (1/sec) interrupts from reading /dev/rtc: and then just sits there never to end. Is this the same for everyone else here. (I also have AMD64 x2 with nForce 4 m/b). (My problem doesn't appear on boot, but does when I install the ztdummy driver from the zaptel modules which I need to run asterisk). -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
OK. Something went wrong with my compile and the HPET_EMULATE_RTC option works. But why is this not enabled in the standard kernel? Surely there is no harm and a lot of good in doing so. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
I just saw this thread come by in the upstream mailing list http://thread.gmane.org/gmane.comp.emulators.kvm.devel/2325 (kvm-dev): It turned out, this option needs to be enabled: Processor type and features --- [*] Provide RTC interrupt (or CONFIG_HPET_EMULATE_RTC=y in .config). With it enabled, I don't have these messages anymore, and performance is much much better. I'll try rebuilding the Ubuntu supplied kernel with this option tomorrow and report back this weekend. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82149] Re: When using kqemu, rtc: lost some interrupts at 1024Hz.
I'm having exactly the same problem on a Dell Dimension C521, containing an nForce 4 motherboard and an AMD64 X² processor with (k)qemu (compiled from source) and KVM (0.16 through 0.18). The kernel log is flooded with 'rtc: lost some interrupts at 1024Hz' messages, quickly filling up the /var partition. Moreover, KVM is not really stable on this machine. However, when not using qemu or KVM, the machine is solid as a rock, and no messages about lost interruptes are reported. I'm not sure this is related, but on boot, I also get this warning from the kernel: [ 14.506009] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 14.686363] Using local APIC timer interrupts. [ 14.731677] result 12526120 [ 14.731679] Detected 12.526 MHz APIC timer. When looking in this machine's BIOS (this being a Dell of course), there is no option to influence the timer source (disable/enable HPET). Googling on 'rtc: lost some interrupts at 1024Hz' reveals that it's quite a common problem. -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
