log out after Clocksource tsc unstable

[dominique]

Binary package hint: firefox-3.5

suddently crash

Oct 21 12:54:53 karmic kernel: [ 24.429620] [drm] Setting GART location based on new memory map
Oct 21 12:54:53 karmic kernel: [ 24.429634] [drm] Loading R100 Microcode
Oct 21 12:54:53 karmic kernel: [ 24.429692] [drm] writeback test succeeded in 2 usecs
Oct 21 12:55:02 karmic kernel: [ 33.352037] eth0: no IPv6 routers present
Oct 21 12:55:52 karmic kernel: [ 83.632072] Clocksource tsc unstable (delta = -227248336 ns)

and this repeat from time to time after one or severa , minutes ,hours

Description: Ubuntu 9.10
Release: 9.10 daily build last update today

linux-image-2.6.31-14

acer travelmate 650

thanks

ProblemType: Bug
Architecture: i386
Date: Wed Oct 21 13:07:26 2009
DistroRelease: Ubuntu 9.10
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu6
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-14-generic i686

[dominique (dominiqueoudin)]

to day same bug

Oct 22 05:58:26 karmic kernel: [ 21.816198] b44: eth0: Link is up at 100 Mbps, full duplex.
Oct 22 05:58:26 karmic kernel: [ 21.816204] b44: eth0: Flow control is off for TX and off for RX.
Oct 22 05:58:26 karmic kernel: [ 21.816467] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 22 05:59:01 karmic pulseaudio[1653]: ratelimit.c: 2 events suppressed
Oct 22 05:59:25 karmic kernel: [ 81.132067] Clocksource tsc unstable (delta = -176555545 ns)

perhaps it's a pulseaudio bug ????

[Micah Gersten (micahg)]

Removing Firefox association...needs reassignment

[Kiriko (kiriko)]

I'm having the same problem with this Clocksource issue. Below are two different entries from /var/log/messages. Just before the system reboots itself an unstable Clocksource is seen.

Like the original reporter this happens within minutes, or hours. Also like the original author I believe this is related to Firefox. My system runs stable with the clock speed of the CPU varying quite often, however when I decide to play with the machine the crash always happens when I'm using Firefox. Please keep in mind it's when I'm using Firefox, not when it's just sitting their idle. Usually happens when I switch tabs, but not always. The crash can occur when typing an address in the location bar, and I'm sure anywhere else Firefox can be used. I do not recall the machine ever crashing when not using Firefox. BTW, this crash happens on a vanilla Firefox in case you wondered.

Nov 8 13:56:06 karmic kernel: [ 39.433126] [drm] Setting GART location based on new memory map
Nov 8 13:56:06 karmic kernel: [ 39.433135] [drm] Loading R300 Microcode
Nov 8 13:56:06 karmic kernel: [ 39.433198] [drm] Num pipes: 1
Nov 8 13:56:06 karmic kernel: [ 39.433205] [drm] writeback test succeeded in 1 usecs
Nov 8 13:57:03 karmic kernel: [ 96.130740] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 8 13:57:03 karmic kernel: [ 96.790207] padlock: VIA PadLock not detected.
Nov 8 13:57:08 karmic kernel: [ 101.660034] Clocksource tsc unstable (delta = -103890963 ns)

Nov 8 14:06:09 karmic kernel: [ 29.415652] [drm] Setting GART location based on new memory map
Nov 8 14:06:09 karmic kernel: [ 29.415662] [drm] Loading R300 Microcode
Nov 8 14:06:09 karmic kernel: [ 29.415724] [drm] Num pipes: 1
Nov 8 14:06:09 karmic kernel: [ 29.415732] [drm] writeback test succeeded in 1 usecs
Nov 8 14:07:03 karmic kernel: [ 83.225063] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 8 14:07:03 karmic kernel: [ 83.813336] padlock: VIA PadLock not detected.
Nov 8 14:07:17 karmic kernel: [ 89.160033] Clocksource tsc unstable (delta = -299960494 ns)

[kkady32 (kkady32)]

i have the same messages:Clocksource tsc unstable (delta = -293719238 ns)

i find this in internet:

"TSC=Time Stamp Counter. Processors have dynamically changed clock speed (ofc to save power). The TSC is supposed to tick at the CPU rate (unless it's a constant_tsc, see /proc/cpuinfo flags, so on frequency change, this ought to happen. The kernel will automatically switch to something else. There's acpi_pm <-(this is what yours has switched to) and, IIRC, pit. This message seems to appear with the newer kernel upgrades."
Check you have installed another clock source like acpi_pm

cat /sys/devices/system/clocksource/clocksource0/available_clocksource

You can try adding the below to your kernel command line. This won't get rid of the unstable line but it will force the kernel to use a more stable clocksource so there should be no trouble switching over anymore (if indeed there is trouble to begin with).

clocksource=acpi_pm (or hpet)

I will make probe but in moment i must see how cann type this command for grub2.
Please the post the results.

[kkady32 (kkady32)]

after setup i become Clocksource tsc unstable (delta = -101708686 ns)
so,for me is better to no set

[Mark (mark-wege)]

hi, I have the above messages about the missing pad lock and the unstable clock-source in my kernel protocol too. I wonder if this bug might be related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/432670 -> regression in karmic thermal control

[Fabio Marconi (fabiomarconi)]

Hello
Is this problem present with the latest updated Karmic's or Lucid's packages?
Thanks in advance
Fabio

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!