← Back to team overview

kernel-packages team mailing list archive

[Bug 1522472] Re: Black screen on boot after updating Trusty

 

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.5-rc2

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

Title:
  Black screen on boot after updating Trusty

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Current release: Ubuntu 14.04.3 LTS
  Current version: v3.13.0.68.74
  Expected behavior: System boots to GUI showing chromium-browser
  What happened: Booted to black screen

  After updating my linux kernel from v3.13.0.32.38 to v3.13.0.68.74, my
  system does not boot into the GUI properly anymore. X11 starts up and
  I have confirmed that I can interact with the screen that should be
  there via keyboard (using chromium logs, I can confirm that I can open
  new tabs with CTRL+T), but the screen is completely black. If I
  restart nodm, X11 restarts and comes up as it should. If I simply
  switch to the vivid kernel (v3.19.0.33.20) on the same system the
  problem goes away and the system boots properly every time, as well as
  the system working fine until I update just the linux-generic package.

  Other possibly useful information:
  - Every time the system boots to a black screen, plymouth does not appear while booting nor can I TTY switch to it after booting (instead the TTY it should be on is a black screen with a blinking cursor), which is opposite of the behavior observed when the system boots properly.
  - Attached Xorg.0.log (produced from a bad boot).
  --- 
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Jan 15 11:11 seq
   crw-rw---- 1 root audio 116, 33 Jan 15 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  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
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c64ce442-021a-4873-934f-770057560a1d
  InstallationDate: Installed on 2015-05-21 (238 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.3)
  IwConfig:
   p3p1      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=5dff8d1e-9793-45ca-80fa-24207ce6e69e ro nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-68-generic N/A
   linux-backports-modules-3.13.0-68-generic  N/A
   linux-firmware                             1.127.19
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-68-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Aptio CRB
  dmi.board.vendor: AMI Corporation
  dmi.board.version: A.6
  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.:bvr5.6.5:bd12/15/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrA.6: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/1522472/+subscriptions