Ubuntu
linux package

tsc: Fast TSC calibration failed

Bug #1804591 reported by Yoshiba
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

[ 0.000000] APIC: Switch to symmetric I/O mode setup
[ 0.004000] Switched APIC routing to physical flat.
[ 0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.024000] tsc: Fast TSC calibration failed
[ 0.032000] tsc: PIT calibration matches HPET. 1 loops
[ 0.032000] tsc: Detected 3600.039 MHz processor
[ 0.032000] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns
[ 0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156)
[ 0.032000] pid_max: default: 32768 minimum: 301
[ 0.032000] Security Framework initialized
[ 0.032000] Yama: becoming mindful.
[ 0.032000] AppArmor: AppArmor initialized
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: 1438 F.... pulseaudio
 /dev/snd/controlC0: 1438 F.... pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-11-22 (2 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
MachineType: Micro-Star International Co., Ltd. MS-7A39
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-11-generic N/A
 linux-backports-modules-4.18.0-11-generic N/A
 linux-firmware 1.175.1
Tags: cosmic
Uname: Linux 4.18.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
_MarkForUpload: True
dmi.bios.date: 09/28/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.I0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M GAMING PRO (MS-7A39)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A39
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

See original description
Revision history for this message
Yoshiba (yoshibatora) wrote :

dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1804591/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Yoshiba (yoshibatora)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1804591

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yoshiba (yoshibatora) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected cosmic
description: updated
Revision history for this message
Yoshiba (yoshibatora) wrote : CRDA.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : IwConfig.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : Lspci.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : Lsusb.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : ProcModules.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : PulseList.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote : RfKill.txt

apport information

Revision history for this message
Yoshiba (yoshibatora) wrote :

dmesg

description: updated
Revision history for this message
Yoshiba (yoshibatora) wrote :

UdevDb

Revision history for this message
Yoshiba (yoshibatora) wrote :
Revision history for this message
Yoshiba (yoshibatora) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Yoshiba (yoshibatora) wrote :
Download full text (7.4 KiB)

The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am...

Read more...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Yoshiba (yoshibatora) wrote :

4.20.0-042000rc4-generic

Revision history for this message
Yoshiba (yoshibatora) wrote :

dmesg of kernel 4.18.0-11-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg
dmesg of kernel 4.20.0-rc4-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
H I Murphy (him610) wrote :
Download full text (3.1 KiB)

It happened to one of mys systems this morning. The system never got past the logo for the motherboard manufacturer (AsRock). Here is the top part of dmesg down to where the failure message occurred, [code]
0.000000] kernel: Linux version 5.4.0-21-generic (buildd@lcy01-amd64-006) (gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)) #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 (Ubuntu 5.4.0-21.25-generic 5.4.27)
[ 0.000000] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgxubuntu-root ro text
[ 0.000000] kernel: KERNEL supported cpus:
[ 0.000000] kernel: Intel GenuineIntel
[ 0.000000] kernel: AMD AuthenticAMD
[ 0.000000] kernel: Hygon HygonGenuine
[ 0.000000] kernel: Centaur CentaurHauls
[ 0.000000] kernel: zhaoxin Shanghai
[ 0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
[ 0.000000] kernel: BIOS-provided physical RAM map:
[ 0.000000] kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d01fff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x0000000009d02000-0x0000000009ffffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000daaf5fff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000daaf6000-0x00000000dbfe7fff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000dbfe8000-0x00000000dc169fff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000dc16a000-0x00000000dc57dfff] ACPI NVS
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000dc57e000-0x00000000dd0c5fff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000dd0c6000-0x00000000deffffff] usable
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
[ 0.000000] kernel: BIOS-e820: [mem 0x0000000100000000-0x000000041f37ffff] usable
[ 0.000000] kernel: NX (Execute Disable) protection: active
[ 0.000000] kernel: SMBIOS 3.2.1 present.
[ 0.000000] kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M/ac, BIOS P1.50 10/14/2019
[ 0.000000] kernel: tsc: Fast TSC calibration fa...

Read more...

Revision history for this message
Paul Menzel (paulmenzel) wrote :

This is a common problem on AMD Zen systems.

Patches were posted to LKML (Linux Kernel Mailing List) in February 2019, but version 2 still needs to rewrite a comment, and v3 wasn’t posted since then.

[1]: https://lkml.org/lkml/2019/2/14/1145

Revision history for this message
Guilherme G. Piccoli (gpiccoli) wrote :

Thank you Paul for the pointer. I've just sent a ping in that thread..let's see how it goes.
Cheers,

Guilherme

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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