Messages in this thread | | | Date | Mon, 28 Jun 2004 15:25:05 -0600 | From | "J. Ryan Earl" <> | Subject | Timer and APIC problems on x86_64 with 2.6.7 |
| |
Though 2.6.7 defaults to using APIC, I still get the following with it turned on from a Via K8T800 chipset:
Jun 27 21:55:29 palace hda: dma_timer_expiry: dma status == 0x24 Jun 27 21:55:39 palace hda: DMA interrupt recovery Jun 27 21:55:39 palace hda: lost interrupt Jun 27 21:57:50 palace hdc: dma_timer_expiry: dma status == 0x24 Jun 27 21:58:00 palace hdc: DMA interrupt recovery
I also saw the following new errors:
Jun 28 03:18:27 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:27 palace warning: many lost ticks. Jun 28 03:18:27 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:27 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:30 palace warning: many lost ticks. Jun 28 03:18:30 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:30 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:30 palace warning: many lost ticks. Jun 28 03:18:30 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:30 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:31 palace warning: many lost ticks. Jun 28 03:18:31 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:31 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:31 palace warning: many lost ticks. Jun 28 03:18:31 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:31 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:32 palace warning: many lost ticks. Jun 28 03:18:32 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:32 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:32 palace warning: many lost ticks. Jun 28 03:18:32 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:32 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:33 palace warning: many lost ticks. Jun 28 03:18:33 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:33 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:33 palace warning: many lost ticks. Jun 28 03:18:33 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:33 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:35 palace warning: many lost ticks. Jun 28 03:18:35 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:35 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:35 palace warning: many lost ticks. Jun 28 03:18:35 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:35 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:38 palace warning: many lost ticks. Jun 28 03:18:38 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:38 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:38 palace warning: many lost ticks. Jun 28 03:18:38 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:38 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:38 palace warning: many lost ticks. Jun 28 03:18:38 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:38 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:38 palace warning: many lost ticks. Jun 28 03:18:38 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:40 palace warning: many lost ticks. Jun 28 03:18:40 palace Your time source seems to be instable or some driver is hogging interupts Jun 28 03:18:40 palace Losing some ticks... checking if CPU frequency changed. Jun 28 03:18:40 palace warning: many lost ticks. Jun 28 03:18:40 palace Your time source seems to be instable or some driver is hogging interupts
I rebooted with "noapic" on the kernel and haven't seen this again...yet... Attaching a small (1KB) .png of CPU usage, notice the system time spike around 3:18AM? This is a 2.6.7 kernel with the x86_64-2.6.7-2 patchset.
-ryan [image] | |