** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
davidetkarine, this bug report is being closed due to the last comment
https://bugs.launchpad.net/fedora/+source/linux/+bug/975544/comments/14
regarding the message noted in the Bug Description is as designed. For
future reference you can manage the status of your own bugs by clicking
on the
The original reporter is seeing this issue on a laptop (as well as the
most recent comment), where the cpus do not have the nonstop_tsc flag in
/proc/cpuinfo.
This means the TSCs may halt when the cpus enter low-power c-states, and
thus are not appropriate for use for system timekeeping. Thus
This happened to me today.
Linux sato 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
I was looking in my logs because for the last few days it takes my
Thinkpad T60 80 seconds to reach the GRUB menu whereas before it took 10
seconds. Not sure if it's
I can confirm this on ubuntu 12.10 with kernel v3.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To manage notifications
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
** Also affects: linux (Fedora)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To
I've tested with the
linux-image-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb
and
linux-headers-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb
package and the message is still present
** Tags removed: needs-upstream-testing
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To manage
I marked this bug as incomplete since you do not have a way to reproduce
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To
This bug still happen at each boot time.
2012/4/11 Joseph Salisbury joseph.salisb...@canonical.com
I marked this bug as incomplete since you do not have a way to reproduce
it.
--
You received this bug notification because you are subscribed to the bug
report.
Thanks, that is good to know. We can test a few things since you can
reproduce the bug.
Would it be possible for you to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
Hello how can i complete it ?
2012/4/9 Joseph Salisbury joseph.salisb...@canonical.com
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/975544
Title:
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To manage
I notice this bug in a log message while looking for the reason why this
message appears at boot time :'sparse file not allowed'
2012/4/7 Joseph Salisbury joseph.salisb...@canonical.com
Do you have a way to reproduce this bug, or did you just notice the
message in your logs?
** Changed in:
** Attachment added: kern.log
https://bugs.launchpad.net/bugs/975544/+attachment/3019089/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975544
Title:
Marking TSC unstable due to check_tsc_sync_source failed
To manage
Do you have a way to reproduce this bug, or did you just notice the
message in your logs?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
