TSC unstable switching to hpet
1
Current clocksource is hpet, which simply does not work with the applications I am trying to run and acpi_pm gives the same errors. I need TSC to work. I already disabled intel_pstate and set failover to acpi_pm. What else can I try to make TSC work again?
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083468] TSC deadline timer enabled
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083475] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083778] ... version: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083838] ... bit width: 48
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083900] ... generic registers: 4
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083961] ... value mask: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084023] ... max period: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084086] ... fixed-purpose events: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084146] ... event mask: 000000070000000f
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085580] x86: Booting SMP configuration:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085642] .... node #0, CPUs: #1
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099367] TSC synchronization [CPU#0 -> CPU#1]:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099489] Measured 493618680 cycles TSC warp between CPUs, turning off TSC clock.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.008000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
kernel timestamp
asked May 5 '15 at 13:49
user2280032user2280032
612
add a comment |
1
Current clocksource is hpet, which simply does not work with the applications I am trying to run and acpi_pm gives the same errors. I need TSC to work. I already disabled intel_pstate and set failover to acpi_pm. What else can I try to make TSC work again?
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083468] TSC deadline timer enabled
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083475] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083778] ... version: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083838] ... bit width: 48
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083900] ... generic registers: 4
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083961] ... value mask: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084023] ... max period: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084086] ... fixed-purpose events: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084146] ... event mask: 000000070000000f
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085580] x86: Booting SMP configuration:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085642] .... node #0, CPUs: #1
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099367] TSC synchronization [CPU#0 -> CPU#1]:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099489] Measured 493618680 cycles TSC warp between CPUs, turning off TSC clock.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.008000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
kernel timestamp
asked May 5 '15 at 13:49
user2280032user2280032
612
add a comment |
1
1
1
Current clocksource is hpet, which simply does not work with the applications I am trying to run and acpi_pm gives the same errors. I need TSC to work. I already disabled intel_pstate and set failover to acpi_pm. What else can I try to make TSC work again?
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083468] TSC deadline timer enabled
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083475] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083778] ... version: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083838] ... bit width: 48
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083900] ... generic registers: 4
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083961] ... value mask: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084023] ... max period: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084086] ... fixed-purpose events: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084146] ... event mask: 000000070000000f
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085580] x86: Booting SMP configuration:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085642] .... node #0, CPUs: #1
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099367] TSC synchronization [CPU#0 -> CPU#1]:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099489] Measured 493618680 cycles TSC warp between CPUs, turning off TSC clock.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.008000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
kernel timestamp
asked May 5 '15 at 13:49
user2280032user2280032
612
Current clocksource is hpet, which simply does not work with the applications I am trying to run and acpi_pm gives the same errors. I need TSC to work. I already disabled intel_pstate and set failover to acpi_pm. What else can I try to make TSC work again?
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083468] TSC deadline timer enabled
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083475] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083778] ... version: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083838] ... bit width: 48
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083900] ... generic registers: 4
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.083961] ... value mask: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084023] ... max period: 0000ffffffffffff
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084086] ... fixed-purpose events: 3
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.084146] ... event mask: 000000070000000f
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085580] x86: Booting SMP configuration:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.085642] .... node #0, CPUs: #1
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099367] TSC synchronization [CPU#0 -> CPU#1]:
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.099489] Measured 493618680 cycles TSC warp between CPUs, turning off TSC clock.
May 4 17:49:18 Ubuntu-1404-trusty-64-minimal kernel: [ 0.008000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
kernel timestamp
kernel timestamp
asked May 5 '15 at 13:49
user2280032user2280032
612
asked May 5 '15 at 13:49
user2280032user2280032
612
asked May 5 '15 at 13:49
user2280032user2280032
612
asked May 5 '15 at 13:49
user2280032user2280032
612
asked May 5 '15 at 13:49
user2280032user2280032
612
612
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
Your situation looks a bit different than mine, proceed with caution. I am saying that I do not know if it is a good idea for you to force the use of tsc or not. You should try to understand why you got the unstable message in the first place, before attempting to override.
You can force the use of tsc with a command line option in grub.
First, save a copy of your current grub file:
sudo cp /etc/default/grub /etc/default/grub.original
Then use your preferred editor, in sudo mode (I use nano):
sudo nano /etc/default/grub
And modify the GRUB_CMDLINE_LINUX_DEFAULT line:
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
Save the file and then:
sudo update-grub
Reboot.
Example, before change (/var/log/kern.log excerpt):
May 5 07:06:36 test-smy kernel: [ 11.222717] Clocksource tsc unstable (delta = 88022463 ns)
May 5 07:06:36 test-smy kernel: [ 11.300602] Switched to clocksource pit
May 5 07:06:36 test-smy kernel: [ 11.383987] 8139too: 8139too Fast Ethernet driver 0.9.28
Example, after change:
May 5 07:27:02 test-smy kernel: [ 11.672507] Clocksource tsc unstable (delta = 91987678 ns)
May 5 07:27:02 test-smy kernel: [ 12.149995] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
And:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Reference
By the way, this can not possibly be related to intel_pstate driver enabled or disabled.
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output fromgrep "model name" /proc/cpuinfoto your question (one line of the output will be enough).
– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
|
show 2 more comments
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f618612%2ftsc-unstable-switching-to-hpet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Your situation looks a bit different than mine, proceed with caution. I am saying that I do not know if it is a good idea for you to force the use of tsc or not. You should try to understand why you got the unstable message in the first place, before attempting to override.
You can force the use of tsc with a command line option in grub.
First, save a copy of your current grub file:
sudo cp /etc/default/grub /etc/default/grub.original
Then use your preferred editor, in sudo mode (I use nano):
sudo nano /etc/default/grub
And modify the GRUB_CMDLINE_LINUX_DEFAULT line:
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
Save the file and then:
sudo update-grub
Reboot.
Example, before change (/var/log/kern.log excerpt):
May 5 07:06:36 test-smy kernel: [ 11.222717] Clocksource tsc unstable (delta = 88022463 ns)
May 5 07:06:36 test-smy kernel: [ 11.300602] Switched to clocksource pit
May 5 07:06:36 test-smy kernel: [ 11.383987] 8139too: 8139too Fast Ethernet driver 0.9.28
Example, after change:
May 5 07:27:02 test-smy kernel: [ 11.672507] Clocksource tsc unstable (delta = 91987678 ns)
May 5 07:27:02 test-smy kernel: [ 12.149995] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
And:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Reference
By the way, this can not possibly be related to intel_pstate driver enabled or disabled.
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output fromgrep "model name" /proc/cpuinfoto your question (one line of the output will be enough).
– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
|
show 2 more comments
0
Your situation looks a bit different than mine, proceed with caution. I am saying that I do not know if it is a good idea for you to force the use of tsc or not. You should try to understand why you got the unstable message in the first place, before attempting to override.
You can force the use of tsc with a command line option in grub.
First, save a copy of your current grub file:
sudo cp /etc/default/grub /etc/default/grub.original
Then use your preferred editor, in sudo mode (I use nano):
sudo nano /etc/default/grub
And modify the GRUB_CMDLINE_LINUX_DEFAULT line:
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
Save the file and then:
sudo update-grub
Reboot.
Example, before change (/var/log/kern.log excerpt):
May 5 07:06:36 test-smy kernel: [ 11.222717] Clocksource tsc unstable (delta = 88022463 ns)
May 5 07:06:36 test-smy kernel: [ 11.300602] Switched to clocksource pit
May 5 07:06:36 test-smy kernel: [ 11.383987] 8139too: 8139too Fast Ethernet driver 0.9.28
Example, after change:
May 5 07:27:02 test-smy kernel: [ 11.672507] Clocksource tsc unstable (delta = 91987678 ns)
May 5 07:27:02 test-smy kernel: [ 12.149995] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
And:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Reference
By the way, this can not possibly be related to intel_pstate driver enabled or disabled.
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output fromgrep "model name" /proc/cpuinfoto your question (one line of the output will be enough).
– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
|
show 2 more comments
0
0
0
Your situation looks a bit different than mine, proceed with caution. I am saying that I do not know if it is a good idea for you to force the use of tsc or not. You should try to understand why you got the unstable message in the first place, before attempting to override.
You can force the use of tsc with a command line option in grub.
First, save a copy of your current grub file:
sudo cp /etc/default/grub /etc/default/grub.original
Then use your preferred editor, in sudo mode (I use nano):
sudo nano /etc/default/grub
And modify the GRUB_CMDLINE_LINUX_DEFAULT line:
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
Save the file and then:
sudo update-grub
Reboot.
Example, before change (/var/log/kern.log excerpt):
May 5 07:06:36 test-smy kernel: [ 11.222717] Clocksource tsc unstable (delta = 88022463 ns)
May 5 07:06:36 test-smy kernel: [ 11.300602] Switched to clocksource pit
May 5 07:06:36 test-smy kernel: [ 11.383987] 8139too: 8139too Fast Ethernet driver 0.9.28
Example, after change:
May 5 07:27:02 test-smy kernel: [ 11.672507] Clocksource tsc unstable (delta = 91987678 ns)
May 5 07:27:02 test-smy kernel: [ 12.149995] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
And:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Reference
By the way, this can not possibly be related to intel_pstate driver enabled or disabled.
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
Your situation looks a bit different than mine, proceed with caution. I am saying that I do not know if it is a good idea for you to force the use of tsc or not. You should try to understand why you got the unstable message in the first place, before attempting to override.
You can force the use of tsc with a command line option in grub.
First, save a copy of your current grub file:
sudo cp /etc/default/grub /etc/default/grub.original
Then use your preferred editor, in sudo mode (I use nano):
sudo nano /etc/default/grub
And modify the GRUB_CMDLINE_LINUX_DEFAULT line:
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
Save the file and then:
sudo update-grub
Reboot.
Example, before change (/var/log/kern.log excerpt):
May 5 07:06:36 test-smy kernel: [ 11.222717] Clocksource tsc unstable (delta = 88022463 ns)
May 5 07:06:36 test-smy kernel: [ 11.300602] Switched to clocksource pit
May 5 07:06:36 test-smy kernel: [ 11.383987] 8139too: 8139too Fast Ethernet driver 0.9.28
Example, after change:
May 5 07:27:02 test-smy kernel: [ 11.672507] Clocksource tsc unstable (delta = 91987678 ns)
May 5 07:27:02 test-smy kernel: [ 12.149995] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
And:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
Reference
By the way, this can not possibly be related to intel_pstate driver enabled or disabled.
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
edited May 5 '15 at 15:01
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
answered May 5 '15 at 14:45
Doug SmythiesDoug Smythies
7,44631631
7,44631631
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output fromgrep "model name" /proc/cpuinfoto your question (one line of the output will be enough).
– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
|
show 2 more comments
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output fromgrep "model name" /proc/cpuinfoto your question (one line of the output will be enough).
– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
This did not work sadly. I should mention TSC is not in available_clocksource, it is completely disabled and refuses to even be an option. There is something else which prevents TSC from being available.
– user2280032
May 5 '15 at 15:28
What is your processor? add the output from
grep "model name" /proc/cpuinfo to your question (one line of the output will be enough).– Doug Smythies
May 5 '15 at 15:49
What is your processor? add the output from
grep "model name" /proc/cpuinfo to your question (one line of the output will be enough).– Doug Smythies
May 5 '15 at 15:49
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
Currently running a complete hardware check. It's a 3930k afaik.
– user2280032
May 5 '15 at 16:44
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
O.K. that's odd. The issue on my computer is that it is extremely old (I use it for minimum requirements testing for Server edition, which it is even below that). Your processor is very modern and should not suffer from unstable TSC.
– Doug Smythies
May 5 '15 at 17:59
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
All of the other machines I could check are running tsc just fine, it's just this one not behaving itself. I already tried half a dozen distros and updated the kernels and installed any drivers I could get my hands on. I am starting to think that it is an actual hardware fault.
– user2280032
May 5 '15 at 18:06
|
show 2 more comments
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f618612%2ftsc-unstable-switching-to-hpet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
