log out because of "clocksource unstable" (tsc)

Bug #364825 reported by turbooster
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I hope this isn't a duplicate of Bug #273313:

I upgraded from Intrepid to Jaunty and now every hour or so my PC (DELL Vostro 1000 w/ Turion 64) logs out. dmesg says:
"Clocksource tsc unstable (delta = -301051707 ns)"
I read that it is possible to add 'notsc' to kernel line (did so but I haven't rebooted yet. Anyway it worked before and should work by default).
I didn't notice a longer boot time as mentioned in Bug #261794 or Bug #190414

Will report if notsc changed anything. And will try clocksource=... shenanigans then.
Setting the governor to performance is not an option. It's a laptop after all...

cat /sys/devices/system/clocksource/clocksource0/current_clocksource
acpi_pm

cat /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm jiffies tsc

uname -a
Linux TurbosLaptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

What Information do you guys need?

Revision history for this message
turbooster (comacritter) wrote :
description: updated
tags: added: clocksource jaunty tsc upgrade
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please run the command

apport-collect -p linux 364825

to automatically attach needed information.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
turbooster (comacritter) wrote :

I tried to do just that but granted read-only rights only. How to revert that? I tried purging apport-collect and reinstalling it.
Is there some kind of cache I can delete? Didn't find in /var/cache

Revision history for this message
Andreas Moog (ampelbein) wrote :

See in ~/.cache/apport/launchpad.credentials

Revision history for this message
turbooster (comacritter) wrote : apport-collect data

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom davfs2 dialout fuse lpadmin netdev plugdev sambashare vboxusers

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 364825] Re: log out because of "clocksource unstable" (tsc)

On Tue, Apr 21, 2009 at 09:21:51PM -0000, Andreas Moog wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it without more information.
> Please run the command
>
> apport-collect -p linux 364825
>
> to automatically attach needed information.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at
> https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

I don't think this command actually works the way one might expect. You
need to run:

apport-collect -p linux-image-`uname -r` NNNNNN

in order for the kernel's apport hook to be run. The documentation (which
is actually at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies) is
incorrect in this regard and needs to be fixed.

See https://launchpad.net/bugs/350131

--
 - mdz

Revision history for this message
turbooster (comacritter) wrote : apport-collect data

Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=a817b98d-b245-43ad-81ea-5156bf1cfff8
MachineType: Dell Inc. Vostro 1000
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
PackageArchitecture: i386
ProcCmdLine: root=UUID=bf916ce7-2537-4b72-bdbf-a8d9d3dbe627 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom davfs2 dialout fuse lpadmin netdev plugdev sambashare vboxusers

Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :
Revision history for this message
turbooster (comacritter) wrote :

You were right I guess ;)

Revision history for this message
turbooster (comacritter) wrote :

update:
My "/sys/devices/system/clocksource/clocksource0/current_clocksource" is now hpet and the error seems to be gone.
I tried tsc as well but everything went SloMo from there (litterally: All the GNOME menus faded in at half the usual speed and after a minute or so the computer would hang and only REISUB and K worked ).
I have still got "APIC error on CPU0: 40(40)" in my syslog, but that's due to a bug in the BIOS I guess (see http://ubuntuforums.org/showthread.php?t=671780)
Was hpet the default in Intrepid? It was only after upgrading that this "error" ocurred.

Revision history for this message
turbooster (comacritter) wrote :

update #2:
the error is NOT gone with hpet. Still logging out every now and then.

Revision history for this message
turbooster (comacritter) wrote :

i didn't have a logout since a week or so. Closed although APIC error still exists.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Closing per the last comment.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.