Tainted: G - What does this kernel message mean?

moxfan

Member
Aug 28, 2013
57
3
8
Getting this warning / error twice each second, sending the kern.log and messages files in /var/log on the Proxmox node into over-drive. Is it signalling a potential hardware failure?

Code:
/var/log/kern.log
---
------------[ cut here ]------------
Jul 21 00:26:14 prox1 kernel: WARNING: at kernel/time.c:638 nsec_to_clock_t+0x45/0x50() (Tainted: G        WC ---------------  T)
Jul 21 00:26:14 prox1 kernel: Hardware name: System Product Name
Jul 21 00:26:14 prox1 kernel: Modules linked in: vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst vzcpt nfs fscache vzmon ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables nf_nat_ftp nf_conntrack_ftp xt_state xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_LOG xt_DSCP xt_dscp ipt_REJECT xt_owner ipt_REDIRECT xt_recent vzdquota vzdev vhost_net tun macvtap macvlan kvm_intel kvm vzevent ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse nfsd nfs_acl auth_rpcgss lockd sunrpc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables dummy ipv6 snd_pcsp i915 snd_pcm snd_page_alloc snd_timer drm_kms_helper snd drm i2c_i801 parport_pc soundcore i2c_algo_bit iTCO_wdt serio_raw i2c_core iTCO_vendor_support parport shpchp video output ext3 mbcache jbd btrfs(T) lzo_compress lzo_decompress zlib_deflate sg ahci r8169 mii xhci_hcd [last unloaded: ploop]
Jul 21 00:26:14 prox1 kernel: Pid: 273145, comm: ftdc veid: 100 Tainted: G        WC ---------------  T 2.6.32-23-pve #1
Jul 21 00:26:14 prox1 kernel: Call Trace:
Jul 21 00:26:14 prox1 kernel: [<ffffffff8106f667>] ? warn_slowpath_common+0x87/0xe0
Jul 21 00:26:14 prox1 kernel: [<ffffffff8106f6da>] ? warn_slowpath_null+0x1a/0x20
Jul 21 00:26:14 prox1 kernel: [<ffffffff810775b5>] ? nsec_to_clock_t+0x45/0x50
Jul 21 00:26:14 prox1 kernel: [<ffffffff8105e78b>] ? cpu_cgroup_proc_stat+0x2cb/0x3a0
Jul 21 00:26:14 prox1 kernel: [<ffffffff810fca17>] ? fairsched_show_stat+0x37/0x60
Jul 21 00:26:14 prox1 kernel: [<ffffffff81214b17>] ? show_stat+0x97/0x650
Jul 21 00:26:14 prox1 kernel: [<ffffffff811c4600>] ? single_release+0x0/0x40
Jul 21 00:26:14 prox1 kernel: [<ffffffff8120ae00>] ? proc_reg_open+0x0/0x160
Jul 21 00:26:14 prox1 kernel: [<ffffffff8119b657>] ? __dentry_open.isra.10+0x137/0x350
Jul 21 00:26:14 prox1 kernel: [<ffffffff8119b964>] ? nameidata_to_filp+0x44/0x60
Jul 21 00:26:14 prox1 kernel: [<ffffffff811c4de6>] ? seq_read+0x116/0x370
Jul 21 00:26:14 prox1 kernel: [<ffffffff8120b5eb>] ? proc_reg_read+0x7b/0xc0
Jul 21 00:26:14 prox1 kernel: [<ffffffff8119ef8e>] ? vfs_read+0x9e/0x190
Jul 21 00:26:14 prox1 kernel: [<ffffffff8119f0ca>] ? sys_read+0x4a/0x90
Jul 21 00:26:14 prox1 kernel: [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b
Jul 21 00:26:14 prox1 kernel: ---[ end trace 4f12ca60f156dcd7 ]---
------------[ cut here ]------------
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!