public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	Markku Savela <msa@burp.tkv.asdf.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11, TSC cannot be used as a timesource.
Date: Sat, 06 Dec 2003 17:21:33 -0500	[thread overview]
Message-ID: <3FD2566D.9020305@wmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0312061701260.1758@montezuma.fsmlabs.com>

Zwane Mwaikambo wrote:
> On Sat, 6 Dec 2003, Dmitry Torokhov wrote:
> 
> 
>>On Saturday 06 December 2003 03:56 pm, Markku Savela wrote:
>>
>>>>From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
>>>>
>>>>On Sat, 6 Dec 2003, Markku Savela wrote:
>>>>
>>>>>I've seen some references to above problem, but no clear answer.
>>>>>The 'ntpd' is complaining a lot...
>>>>>
>>>>>I have ASUS P4S800. Here is some extracts from dmesg (I can provide
>>>>>more complete dump, if anyone wants something specific.)
>>>>
>>>>Does this only happen when running X11?
>>>
>>>Hmm.. possibly. When I boot single user, it does not appear to happen.
>>>
>>
>>Do you have an ACPI battery stat or thermal monitor apps running (I see
>>that you have ACPI active). Does it help it you increase the polling
>>interval? Too many systems spend too much time in SCI handler...
> 
> 
> Yes cat /proc/interrupts might also give some sort of rough indication.


It took over 3 days to trigger it on my system, so booting to  single 
user mode and waiting 5 minutes is not a good marker of deciding if 
that's the case or not.  Also, i dont have SCSI compiled in my kernel at 
all yet this happens. So that idea is out.


Here is my /proc/interrupts
            CPU0
   0:  426319022          XT-PIC  timer
   1:     409358          XT-PIC  i8042
   2:          0          XT-PIC  cascade
   5:          0          XT-PIC  acpi
   8:  136058006          XT-PIC  rtc
  11:   23497500          XT-PIC  uhci_hcd, uhci_hcd, eth0, EMU10K1
  12:   25482865          XT-PIC  bttv0
  14:    1440279          XT-PIC  ide0
  15:     405600          XT-PIC  ide1
NMI:          0
LOC:  426178067
ERR:     554364
MIS:          0



  parent reply	other threads:[~2003-12-06 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06 16:03 2.6.0-test11, TSC cannot be used as a timesource Markku Savela
2003-12-06 16:11 ` Ed Sweetman
2003-12-06 17:53 ` Zwane Mwaikambo
2003-12-06 20:56   ` Markku Savela
2003-12-06 21:00     ` Zwane Mwaikambo
2003-12-06 21:52     ` Dmitry Torokhov
2003-12-06 22:01       ` Zwane Mwaikambo
2003-12-06 22:19         ` Markku Savela
2003-12-06 22:21         ` Ed Sweetman [this message]
2003-12-06 22:26           ` Zwane Mwaikambo

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=3FD2566D.9020305@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msa@burp.tkv.asdf.org \
    --cc=zwane@arm.linux.org.uk \
    /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