hwclock will set the date to 2/2/2080 with given 2/2/80

Bug #1714229 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

On node lodygin, run:
sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

Will set the date to 2/2/2080. Thus it failed the hwclock test, which expect the output of 1980

This only happen on lodygin, other testing nodes (hainzel, rumford, rizzo, fozzie) are good.

This issue has been tested on Xenial and Zesty, they will all behave in the same way.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Aug 31 11:27 seq
 crw-rw---- 1 root audio 116, 33 Aug 31 11:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
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:
Date: Thu Aug 31 11:36:37 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: AMD Corporation Speedway
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-93-generic N/A
 linux-backports-modules-4.4.0-93-generic N/A
 linux-firmware 1.157.11
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: RSW1001E
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Speedway
dmi.board.vendor: AMD Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
dmi.product.name: Speedway
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: AMD Corporation

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Po-Hsu Lin (cypressyew)
tags: added: artful
Revision history for this message
Kim Naru (kim-naru) wrote :

I confirmed your findings. What I found was that on AMD systems going back even to Llano, you can’t change a date in the 20th century. However I had no issues changing date from 2018 to 2015. Though the bug is present, the fact it only happens with date from the last century would suggest it is a minor issue. Would you agree?

-thanks
-kim

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello Kim,

we will change the test case to set hwclock to 2004, once the patch got merged in the test suite, I will close this bug with "Won't fix".

Thanks

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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