mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Niclas Gustafsson <niclas.gustafsson@codesense.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Patricia Gaughen <gone@us.ibm.com>
Subject: Re: Failing back to INSANE timesource :) Time stopped today.
Date: Wed, 14 Apr 2004 11:36:44 -0700	[thread overview]
Message-ID: <1081967804.4705.105.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1081932857.17234.37.camel@gmg.codesense.com>

On Wed, 2004-04-14 at 01:54, Niclas Gustafsson wrote:
> Now it happened again, with my newly compiled kernel, I've attached the
> config file and dmesg for this kernel.
> 
> Watching the /proc/interrupts with 10s apart after the "stop".
> 
> [root@s151 root]# more /proc/interrupts
>            CPU0
>   0:   66413955  local-APIC-edge  timer
>   2:          0          XT-PIC  cascade
>   9:          1   IO-APIC-level  acpi
>  10:          0   IO-APIC-level  ohci_hcd
>  14:         24    IO-APIC-edge  ide0
>  20:      31244   IO-APIC-level  aic7xxx
>  22:   19652139   IO-APIC-level  eth0
> NMI:          0
> LOC:   67379568
> ERR:          0
> MIS:          0
> 
> And some 10-15 min later:
> 
> [root@s151 root]# cat /proc/interrupts
>            CPU0
>   0:   66413964  local-APIC-edge  timer
>   2:          0          XT-PIC  cascade
>   9:          1   IO-APIC-level  acpi
>  10:          0   IO-APIC-level  ohci_hcd
>  14:         24    IO-APIC-edge  ide0
>  20:      31245   IO-APIC-level  aic7xxx
>  22:   19754446   IO-APIC-level  eth0
> NMI:          0
> LOC:   68366976
> ERR:          0
> MIS:          0

Wow, clearly something is going wrong with interrupt delivery. You only
received 9 timer interrupts in 10 seconds!

> Worth noticing is the extreme increase in interrupts and context
> switches on the last output line from vmstat, however if this is a true
> picture of what happened or not I cannot say. Maybe this is just a
> result of timing problems?
> 
> However I see an increase in network activity just before the stop, the
> system goes from 2 Mbps output to about 55 Mbps on the last read. (Also
> read from this machine so I don't know about it's validity)

Yea, those values are both junk as the X/sec ratio is totally skewed. 

> Where can I see what the system is currently using as a timing source
> (TSC/HPET/PIT etc.)?

Note the "Using tsc for high-res timesource" in your dmesg. 

I'm working now to reproduce this w/ a 2G system here in our lab, and
just for completeness, could you also send me your BIOS revision number?

thanks
-john



  reply	other threads:[~2004-04-14 18:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  9:21 Niclas Gustafsson
2004-04-08 12:20 ` Niclas Gustafsson
2004-04-08 22:58 ` john stultz
2004-04-13  8:25   ` Niclas Gustafsson
2004-04-14  8:54   ` Niclas Gustafsson
2004-04-14 18:36     ` john stultz [this message]
2004-04-15  8:46       ` Niclas Gustafsson
2004-04-15 14:47     ` Maciej W. Rozycki
2004-04-15 16:57       ` Niclas Gustafsson
2004-04-20  9:21         ` Niclas Gustafsson
2004-04-20 12:40           ` Maciej W. Rozycki
2004-04-20 21:18             ` john stultz
2004-04-21 14:20               ` Maciej W. Rozycki
2004-04-19 16:40       ` john stultz

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=1081967804.4705.105.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=gone@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niclas.gustafsson@codesense.com \
    /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

all inboxes | Powered by JetHome®