kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Peter D., in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: bios-outdated-2.60
** Tags added: latest-bios-2.60

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

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

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