Cliff Carson, 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 added: needs-bisect regression-release

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

Title:
  Blank screen 90 sec boot delay

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tried to document this problem under bug 1559595 but have been
  requested to submit a new bug.

  Been having an intermittent problem booting (started on 16.04 and
  continues across multiple system rebuilds and 16.10) where just after
  entering my PW the screen goes blank for about 90 seconds.  After that
  interval the normal desktop appears and all is well.  Will supply a
  journal boot log of a failing boot (boot_0704.txt) and a normal boot
  log (boot_0704_good.txt).  Do see in the failing log and all others
  that I have looked at a gnome-session timeout (time 06:16:41).  Don't
  see this type of entry in the good log but haven't examined many non-
  failure logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-30-generic 4.4.0-30.49
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  cliff      3761 F.... pulseaudio
   /dev/snd/controlC2:  cliff      3761 F.... pulseaudio
   /dev/snd/controlC1:  cliff      3761 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul  5 06:19:34 2016
  HibernationDevice: RESUME=UUID=51013622-8d36-45f8-89d8-8dc36d3b5ac5
  InstallationDate: Installed on 2016-05-30 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160529)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=375f8904-0bcb-4f0b-bd19-2a200ca1db5a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-30-generic N/A
   linux-backports-modules-4.4.0-30-generic  N/A
   linux-firmware                            1.158
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2012
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599110/+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

Reply via email to