[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
For reference, this was Amazon's response on the forum post: https://forums.aws.amazon.com/message.jspa?messageID=561728#561728 Basically "we are not changing, move to current generation instances." Is there some sort of assistance I should request there, or through Amazon support. Has anyone from AWS gotten back to you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 727459] Re: TSC is not reliable under Xen on some Intel CPUs
Full dmesg log as requested ** Attachment added: "full dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+attachment/4164601/+files/full%20dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/727459 Title: TSC is not reliable under Xen on some Intel CPUs Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Lucid: Triaged Status in “linux” source package in Trusty: Triaged Bug description: SRU Justification Impact: When applying the Xen patchset one endif seems to have gone to the wrong place. So instead of not setting sched_clock_stable it is done all the time. Fix: Move endif so the whole code segment is covered. Testcase: Can cause various effects and depends on CPU (see below). Incorrect CPU time but likely also causing the unexplainable process gets stuck or clone/fork issues. --- Ubuntu 10.04.2 LTS Ubuntu 2.6.32-312.24-ec2 2.6.32.27+drm33.12 Linux 2.6.32-312-ec2 #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011 x86_64 GNU/Linux We are experiencing impossibly high (thousands of days) accumulated CPU times for processes in ps and top when using the above kernel on Amazon EC2. Instances running on Intel E5430 are fine, while instances on E5507 all seem to have the problem. Please see also https://bugzilla.kernel.org/show_bug.cgi?id=16314 Thanks, Doug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 727459] Re: TSC is not reliable under Xen on some Intel CPUs
Having the same issue on Trusty 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This is occurring for me on some EC2 instances. Not continuously, but sporadically when launching new instances. I've attached a sample of the dmesg log showing the time jump. ** Attachment added: "Sample dmesg log with time jump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+attachment/4164600/+files/sample%20dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/727459 Title: TSC is not reliable under Xen on some Intel CPUs Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Lucid: Triaged Status in “linux” source package in Trusty: Triaged Bug description: SRU Justification Impact: When applying the Xen patchset one endif seems to have gone to the wrong place. So instead of not setting sched_clock_stable it is done all the time. Fix: Move endif so the whole code segment is covered. Testcase: Can cause various effects and depends on CPU (see below). Incorrect CPU time but likely also causing the unexplainable process gets stuck or clone/fork issues. --- Ubuntu 10.04.2 LTS Ubuntu 2.6.32-312.24-ec2 2.6.32.27+drm33.12 Linux 2.6.32-312-ec2 #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011 x86_64 GNU/Linux We are experiencing impossibly high (thousands of days) accumulated CPU times for processes in ps and top when using the above kernel on Amazon EC2. Instances running on Intel E5430 are fine, while instances on E5507 all seem to have the problem. Please see also https://bugzilla.kernel.org/show_bug.cgi?id=16314 Thanks, Doug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 727459] Re: TSC is not reliable under Xen on some Intel CPUs
Per request, I've updated to the latest kernel, 3.13.0-32-generic, and still have the issue. Updated dmesg attached. ** Attachment added: "dmesg output on 3.13.0-32-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+attachment/4164624/+files/sample%20dmesg%20new.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/727459 Title: TSC is not reliable under Xen on some Intel CPUs Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Lucid: Triaged Status in “linux” source package in Trusty: Triaged Bug description: SRU Justification Impact: When applying the Xen patchset one endif seems to have gone to the wrong place. So instead of not setting sched_clock_stable it is done all the time. Fix: Move endif so the whole code segment is covered. Testcase: Can cause various effects and depends on CPU (see below). Incorrect CPU time but likely also causing the unexplainable process gets stuck or clone/fork issues. --- Ubuntu 10.04.2 LTS Ubuntu 2.6.32-312.24-ec2 2.6.32.27+drm33.12 Linux 2.6.32-312-ec2 #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011 x86_64 GNU/Linux We are experiencing impossibly high (thousands of days) accumulated CPU times for processes in ps and top when using the above kernel on Amazon EC2. Instances running on Intel E5430 are fine, while instances on E5507 all seem to have the problem. Please see also https://bugzilla.kernel.org/show_bug.cgi?id=16314 Thanks, Doug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 727459] Re: TSC is not reliable under Xen on some Intel CPUs
Per your request, created bug #1349883 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/727459 Title: TSC is not reliable under Xen on some Intel CPUs Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Lucid: Triaged Status in “linux” source package in Trusty: Triaged Bug description: SRU Justification Impact: When applying the Xen patchset one endif seems to have gone to the wrong place. So instead of not setting sched_clock_stable it is done all the time. Fix: Move endif so the whole code segment is covered. Testcase: Can cause various effects and depends on CPU (see below). Incorrect CPU time but likely also causing the unexplainable process gets stuck or clone/fork issues. --- Ubuntu 10.04.2 LTS Ubuntu 2.6.32-312.24-ec2 2.6.32.27+drm33.12 Linux 2.6.32-312-ec2 #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011 x86_64 GNU/Linux We are experiencing impossibly high (thousands of days) accumulated CPU times for processes in ps and top when using the above kernel on Amazon EC2. Instances running on Intel E5430 are fine, while instances on E5507 all seem to have the problem. Please see also https://bugzilla.kernel.org/show_bug.cgi?id=16314 Thanks, Doug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/727459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] [NEW] dmesg time wildly incorrect on paravirtual EC2 instances.
Public bug reported: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug ec2-images trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect
Appears to be related to bug #727459 , but I've added a new bug per request. ** Summary changed: - dmesg time wildly incorrect + dmesg time wildly incorrect on paravirtual EC2 instances. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165193/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165191/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165190/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
apport information ** Tags added: apport-collected ** Description changed: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 29 14:41 seq + crw-rw 1 root audio 116, 33 Jul 29 14:41 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning + DistroRelease: Ubuntu 14.04 + Ec2AMI: ami-00dc1368 + Ec2AMIManifest: (unknown) + Ec2AvailabilityZone: us-east-1c + Ec2InstanceType: m1.small + Ec2Kernel: aki-919dcaf8 + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory + Lspci: + + Lsusb: Error: [Errno 2] No such file or directory + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-32-generic N/A + linux-backports-modules-3.13.0-32-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty ec2-images + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm admin ssh sudo + WifiSyslog: + + _MarkForUpload: True ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165189/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' A
[Kernel-packages] [Bug 1349883] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165192/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1349883/+attachment/4165194/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
You're correct on your findings. m1.small, paravirtual guest. I'm in the process of migrating my company's servers from 12.04 to 14.04. It was during this migration that I realized I was seeing syslog- ng logs for October 2014 or later (ie months into the future) on the new 14.04 instances, and I've been seeing it intermittently when launching new instances. Not always, but on some launches, or on some reboots. I think it's either some some sort of race condition, or related to what Amazon hardware the instance is actually spun up on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
To clarify, I'm pretty sure whether this happens depends on the Amazon hardware the instance is being run on. My warning was that, while the instance was currently running on hardware that causes the problem, if it was stopped and then started later, it might not end up on the same hardware, and therefore the bug might not happen that launch. If I have the problem on a running instance, and just reboot it, though, I've always had it again -- I assume Amazon doesn't move the instance if you're just rebooting it. So if an instance is encountering the problem, it'll continue happening no matter how many times you reboot it. But if you shut it down, it might not happen when it's started next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
I've started a thread on the AWS forums about this. https://forums.aws.amazon.com/thread.jspa?threadID=15 If I don't get a response I'll poke our account rep. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
