← Back to team overview

kernel-packages team mailing list archive

[Bug 1550839] Re: wakealarm is cleared on boot unless hpet disabled

 

Peter D., thank you for reporting this and helping make Ubuntu better.

As per
http://www.asrock.com/mb/AMD/970%20Pro3%20R2.0/?cat=Download&os=BIOS an
update to your computer's buggy, insecure, and outdated BIOS is
available (2.60). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-2.60

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: linux (Ubuntu)
   Importance: Medium => Low

-- 
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/1550839

Title:
  wakealarm is cleared on boot unless hpet disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wiley Werewolf 15.10 and Xenial Xerus 16.04 (alpha) clear
  /sys/class/rtc/rtc0/wakealarm during the bootup process, unless
  "hpet=disable" is given as a boot parameter.  (Tested on Xenia, not
  tested on Wiley.)

  Trusty Tahr 14.04 is well behaved, without the hpet parameter.

  Background; the main installation runs MythTV which sets and uses the
  wake alarm.  A test boot into a newer OS clears the alarm and MythTV
  on Trusty does not wake up to record the next scheduled TV program.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.2.1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  psd        1154 F.... pulseaudio
   /dev/snd/controlC0:  psd        1154 F.... pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Feb 28 12:28:59 2016
  HibernationDevice: RESUME=UUID=2f3325b3-f04c-4c61-98b8-d4a23624b37a
  InstallationDate: Installed on 2016-02-03 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202)
  IwConfig:
   enp5s0    no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: \vmlinuz ro root=LABEL=XX quiet splash bootdegraded=true video=vesa:off  hpet=disable initrd=\initrd.img
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware                           1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: 970 Pro3 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd01/08/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550839/+subscriptions


References