Un-assigning myself since I won't have time to work on this bug.
FWIW, there were many changes to the clock code around 2.6.24. All
subscribers to this bug should file separate bugs because clocks are
very HW/chipset specific. So even though they might appear to be the
same problem, they might
I'm marking this bug back to Fix Released, as it is fixed for the
initial reporter (me). In order to keep launchpad clean and to make sure
that we don't mix different bugs, if anybody can still reproduce any
issue, please open a new bug report including all relevant information
you can give. If
I'm reopening this bug, because of the continuous like-complaints on
this issue. Before this bug is closed, we need to know what was fixed,
and how those of us (myself) included can eliminate this closed-bug
from the problems that we're observing.
** Changed in: linux (Ubuntu)
Status: Fix
I also get this message during boot - but from what I read it's not a
problem:
As far as i know Pentium M processors have dynamically changed clock
speed (ofc to save power). That's why kernel notice that TSC is
unstable (it is indeed). [...] I don't think that there is an easy way to fix
it (it
** Attachment added: Fast boot with no pauses...
http://launchpadlibrarian.net/21243691/boot_fast.log
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello,
i got the same problem in my boot process. The message Clocksource tsc
unstable blocked the booting for about 100 seconds and I had 2-3 else
pauses after this... But I could solve the problem with a strange
solution: I put the parameter
clocksource=tsc
Line in menu.lst:
kernel
Hello,
I have the same error as follows - these lines begin at line 438 of the
file, which is nearly the end of it.
[ 117.926535] Marking TSC unstable due to: cpufreq changes.
[ 117.934315] Time: acpi_pm clocksource has been installed.
[ 118.140441] NET: Registered protocol family 10
[
Exactly as reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/270581 .
This problem is present also in the Intrepid Ibex Alpha 6 release.
Bye.
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification
This is a Dell Poweredge 2800, what I've also read is forcing the CPU to
stay at full speed can stop it which would be a ok temporary solution
for me as it's more important the server works, but seems that scaling
isn't available in Server ? Either that or it's handled differntly fromt
he scaling
Ok well that didn't fix it, despite acpi_pm enabled at boot it still
seems to use TSC (Have to pardon my not understanding the inner workings
of this) as I get the following:
Sep 22 12:03:57 host-01 kernel: [ 1007.064201] Clocksource tsc unstable
(delta = 140599784626 ns)
It doesn't give me the
Hi There,
I'm having this exact problem on Hardy Server, but this is fairly
critical for me. The same error is logged:
Sep 20 10:22:25 host-01 kernel: [51281.289424] Clocksource tsc unstable (delta
= 3323063740502 ns)
Sep 20 10:22:25 host-01 kernel: [51281.299403] Time: acpi_pm clocksource has
Ok well jiffies did not work, in cat when I switch ntp back on and ran
date every 5 secs or so I get this:
[EMAIL PROTECTED]:~$ date
Sat Sep 20 10:22:51 BST 2008
[EMAIL PROTECTED]:~$ date
Mon Sep 22 05:40:35 BST 2008
[EMAIL PROTECTED]:~$ date
Mon Sep 22 05:40:35 BST 2008
[EMAIL PROTECTED]:~$ date
Grispa : Can you open a new bug report for linux and describe your bug
with more details?
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi everyone.
I tested Intrepid Ibex today on a Fujitsu Siemens amilo Xa 2528
(datasheet: http://docs.fujitsu-
siemens.com/dl.aspx?id=5cbe3a18-eae7-4f19-a744-bdc34afe341e ).
Besides other problems experienced with previous versions of Ubuntu, this time
I had, during the boot, the clocksource tsc
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Leann Ogasawara : I'm the initial bug reporter. I can confirm that this
bug disappeared in 2.6.26.* and does not happen with 2.6.27 . According
to this, I set the status to fix released. If anybody can reproduce this
problem with intrepid, please set back the status of the bug report to
new.
Leann Ogasawara : I'm the initial bug reporter. I can confirm that this
bug disappeared in 2.6.26.* and does not happen with 2.6.27 . According
to this, I set the status to fix released. If anybody can reproduce this
problem with intrepid, please set back the status of the bug report to
new.
Hi Saivann,
Thanks for testing and the update. The issue with getting this fixed in
Hardy would be isolating the exact patch(es) to backport. With the
limited number of resources on the kernel team we'd likely need your
help with performing a git bisect to isolate the patches. Then it's a
This bug was a deal killer for putting Hardy on my laptop. I can try
again when Intrepid comes out... When is that?
--- On Thu, 8/28/08, Leann Ogasawara [EMAIL PROTECTED] wrote:
From: Leann Ogasawara [EMAIL PROTECTED]
Subject: [Bug 190414] Re: Clocksource tsc unstable add 10 seconds to the boot
Intrepid will release in Oktober 2008.
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Leann Ogasawara : Thanks for your clear answer. Unfortunately, I won't
have time/ressources/knowledge to look for the appropriate patch for
Hardy so as you say, I think that having intrepid fixed will be enough.
Workaround exist anyway and it's not a crasher bug. Thanks.
--
Clocksource tsc
my dmesg log:
[953628.159139] Clocksource tsc unstable (delta = 4686637338 ns)
[953628.169116] Time: acpi_pm clocksource has been installed.
$ uname -a
Linux lab-95 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008 i686 GNU/Linux
does it belongs to the same bug?
--
Clocksource tsc
I have exactly the same problem on my inspiron 1720 (core2duo) under
ubuntu hardy 8.04 :
dmesg | grep Clocksource
[ 23.987505] Clocksource tsc unstable (delta = -26370003969 ns)
cat /proc/version
Linux version 2.6.24-18-rt ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) #1 SMP
clocksource=hpet worked for me (Dell Inspiron 6000)
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've experienced the exact same thing on a HP 8510p.
I've attached my logs if anyone wants to look.
** Attachment added: uname-a.log, version.log, dmesg.log, and lspci-vvnn.log
http://launchpadlibrarian.net/15187505/info.tar.gz
--
Clocksource tsc unstable add 10 seconds to the boot time.
Problem persists.
$ cat /proc/version
Linux version 2.6.24-18-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) #1 SMP Wed May 28 20:27:26 UTC 2008
$ cat /proc/version_signature
Ubuntu 2.6.24-18.32-generic
--
Clocksource tsc unstable add 10 seconds to the boot time.
Oké, thanks for confirming, it doesn't solve it for me either...
@nappsoft: Sorry, I have read over that one...
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which
Things are still the same for me with the new kernel.
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have Kubuntu 8.04 Hardy Heron (KDE 3.5.9) and it has become dead slow
(4mins) at boot (at the reading files needed to boot stage) after a
couple of updates a few days ago. Adding clocksource=hpet to my kernel
line hasn't solved this at all. I've opened up a thread at
clocksource=hpet prevents kernel panic on my Latitude D420.
but something is still happening because in the same situation I loose my right
mouse button. After restarting xserver everything works well again, until I let
my laptop go idle again, where I loose my right button again. Symptom are
I think the problem is that CONFIG_X86_TSC is not set in the kernel
configuration. If it were, the idle functions in
drivers/apci/processor_idle.c would mark the TSC as unstable, preventing
this bug.
--
Clocksource tsc unstable add 10 seconds to the boot time.
Still happens with 2.6.24-17 without clocksource=hpet (as mentioned
above: doesn't happen with 2.6.25)
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is
pjina3 : The bug that you have is bug 192720 which is caused by
b43legacy. All these bugs were duplicates of this one. Thank you for
finding them!
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you
I have the same problem but the two last lines are :
- b43legacy-phy0: Broadcom 4301 WLAN found
- Clocksource tsc unstable (delta = 4687308187 ns)
I try to add the option clocksource=hpet but it not solve the problem
:(
--
Clocksource tsc unstable add 10 seconds to the boot time.
pjina3:
Is there a line below the tsc unstable one? It should tell you what
clocksource it's selecting instead, which is the one you should be
picking - it won't necessarily be hpet. Boot without the clocksource or
quiet arguments and see what it says.
--
Clocksource tsc unstable add 10 seconds
Benjamin Rader:
No, there is'nt but i will try to do that :)
ps. I thinks the bugs below seem to be a duplicate
[URL=https://bugs.launchpad.net/ubuntu/+bug/219498]bug #1219498[/URL]
[URL=https://bugs.launchpad.net/ubuntu/+source/linux/+bug/192720]bug
#192720[/URL]
SAIVANN:
I added clocksource=hpet and erased quiet and after some normal
reboots removed the clocksource=hpet and added the quiet (in the
menu.lst of course)
Now, the same problem again. But just simply removed the quiet from
the boot line in the menu.lst and every thing is normal.
What the
I had the same problem, but not any more, and don't no why?!?
I made the clocksource=hpet trick and erased the QUIET option in the
kernel line at grub, every thing worked ok...not the 30 sec infinite
waiting any more...
But now i have every thing by default and the 30 sec waiting IS GONE,
like
This bug can still be reproduced here in Hardy with all updates.
pixolex : You probably added clocksource=hpet in your
/boot/grub/menu.lst file, so it is used each time your computer boot or
it is fixed for some hardwares only, but I really doubt that it's the
case.
--
Clocksource tsc unstable
and with 'clocksource=hpet' ?
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Amit Kucheria (amitk)
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a
As said previously, clocksource=hpet works correctly for me.
nappsoft : Can your confirm the same?
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
yes clocksource=hpet is working. I'm sorry, it seems like I'd missed
Stéphan Kochen's post!
So there are 3 options to get it to work:
- clocksource=hpet
- compiling the kernel for pentium-m instead of 586
- using 2.6.25 (works as 586 kernel without the clocksource=hpet option)
--
Clocksource
Saïvann: Of course you're right. When I started adding comments here and
did not yet have that much information the bug seemed to be similar to
#197228 which was marked as beeing the same as this one. For sure the
troubles I have seem to be more serious and not be caused by the same
module even
Could you try to boot with notsc option?
Thanks!
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Booting with notsc helps indeed not stopping at this place, but the
troubles follow later! While my system runs perfectly with a pentium-m
kernel it isn't working even with the notsc boot-option using the
ubuntu-kernel.
Now I get 100% cpu and the following messages:
init[1] general protection
So here is some more information from my side. The system hung for more
than 5 minutes today. After that I stopped the boot-process and booted
with my self-compiled 2.6.24 kernel.
Here the last output:
scsi0: ata_piix
scsi1: ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1810 irq
Still the same with linux-image-2.6.24-14-generic
--
Clocksource tsc unstable add 10 seconds to the boot time.
https://bugs.launchpad.net/bugs/190414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
A few more observations:
- As mentioned my old 2.6.24 was working with hard while the hardy
kernel didn't work
So I tried 2.6.24.4 with my 2.6.24 config, which worked. Then I tried it
with config-2.6.24-14-generic what didn't work... Most of the time the
system did not even boot (the same as
nappsoft : Thanks a lot for all the informations you provide. I suspect
that your bug is not the same as the one initially described. According
to what you say, your computer takes more than 5 minutes to boot (or
does not boot at all) and your problem does not seem to be caused by tsc
clocksource
49 matches
Mail list logo
