From: "J. Ryan Earl" <heretic@clanhk.org>
To: discuss@x86-64.org
Cc: linux-kernel@vger.kernel.org
Subject: Timer and APIC problems on x86_64 with 2.6.7
Date: Mon, 28 Jun 2004 15:25:05 -0600 [thread overview]
Message-ID: <40E08CB1.3020500@clanhk.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4436 bytes --]
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
[-- Attachment #2: cpu_usage.png --]
[-- Type: image/png, Size: 7370 bytes --]
reply other threads:[~2004-06-28 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40E08CB1.3020500@clanhk.org \
--to=heretic@clanhk.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox