From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Markku Savela <msa@burp.tkv.asdf.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11, TSC cannot be used as a timesource.
Date: Sat, 06 Dec 2003 11:11:45 -0500 [thread overview]
Message-ID: <3FD1FFC1.5030100@wmich.edu> (raw)
In-Reply-To: <200312061603.hB6G3CrG012634@burp.tkv.asdf.org>
ok, so we've shown it's not dependent on the number of cpu's you have.
Not dependent on the amd/intel mobo and cpu you have. Not dependendent
on if you're using akpm's test10 patch on test11 or not. So this seems
to be proving to be a real bug.
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.)
>
> Linux version 2.6.0-test11 (root@moth) (gcc version 3.3.2 (Debian)) #2 SMP Thu Dec 4 22:32:52 EET 2003
> ...
> Kernel command line: BOOT_IMAGE=Linux-2 ro root=301
> Initializing CPU#0
> PID hash table entries: 1024 (order 10: 8192 bytes)
> Detected 2400.326 MHz processor.
> ...
> CPU: Hyper-Threading is disabled
> ...
> Intel machine check reporting enabled on CPU#0.
> CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
> CPU#0: Thermal monitoring enabled
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> CPU0: Intel(R) Celeron(R) CPU 2.40GHz stepping 09
> per-CPU timeslice cutoff: 365.75 usecs.
> task migration cache decay timeout: 1 msecs.
> enabled ExtINT on CPU#0
> ...
> Using local APIC timer interrupts.
> calibrating APIC timer ...
> ..... CPU clock speed is 2399.0868 MHz.
> ..... host bus clock speed is 99.0994 MHz.
> Starting migration thread for cpu 0
> CPUS done 2
> ...
> PCI: Using ACPI for IRQ routing
> PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
> PCI: Cannot allocate resource region 4 of device 0000:00:02.1
> radeonfb_pci_register BEGIN
> radeonfb: ref_clk=2700, ref_div=60, xclk=15000 from BIOS
> radeonfb: probed DDR SGRAM 32768k videoram
> radeon_get_moninfo: bios 4 scratch = 2000002
> radeonfb: ATI Radeon VE QY DDR SGRAM 32 MB
> radeonfb: DVI port no monitor connected
> radeonfb: CRT port CRT monitor connected
> radeonfb_pci_register END
> ...
> ACPI: Power Button (FF) [PWRF]
> ACPI: Processor [CPU0] (supports C1)
> ...
> Real Time Clock Driver v1.12
> Linux agpgart interface v0.100 (c) Dave Jones
> agpgart: Detected SiS 648 chipset
> agpgart: Maximum main memory to use for agp memory: 203M
> agpgart: AGP aperture is 64M @ 0xe8000000
> [drm] Initialized radeon 1.9.0 20020828 on minor 0
> ...
> Losing too many ticks!
> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
> Falling back to a sane timesource.
> set_rtc_mmss: can't update from 59 to 0
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-12-06 16:11 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 [this message]
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
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=3FD1FFC1.5030100@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=msa@burp.tkv.asdf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.