'kernel-fixed-upstream'

To answer your questions:
1- I noticed this error after i upgraded from Ubuntu 17.04 to 17.10... namely 
because my server did not boot properly. The reason for it not booting properly 
was not related to this, as i later found out.... so i cannot guarantee that 
this error was not present in Ubuntu 17.04.  But it is worth trying to see if 
this error require your attention. It has to do with Ethernet interfaces 
dedicated to guest VMs.  i will submit a different report on it.

2- i tested v4.15 per your request.  i tested both -generic and -lowlatency, 
both were successful.  However, there is one error that shows up during boot.  
maybe it is related to something else.
[FAILED] Failed to start AppArmor initialization.
See ' sudo systemctl status apparmor.service'
Here is that output:
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-01-04 10:48:43 PST; 3min 
45s ago
     Docs: man:apparmor(7)
           http://wiki.apparmor.net/
  Process: 1198 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
 Main PID: 1198 (code=exited, status=123)

Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in 
/etc/apparmor.d
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app a
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in 
/etc/apparmor.d
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]:    ...fail!
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
Jan 04 10:48:43 kds-vh-srvr systemd[1]: Failed to start AppArmor initialization.
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Unit entered failed 
state.
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Failed with result 
'exit-code'.
lines 1-18/18 (END)

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

Title:
  EDAC sbridge: Failed to register device with error -19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This resembles an error with same title except for error -22.

  I am not savy enough to know if it is the same or different. But since
  it is happening in linux version that is supposedly fixed i thought i
  report it.

  here is some info:
  1- This shows up on loading Ubuntu... repeatable always.
  2- exact error:
  [8.89..] EDAC sbridge: some needed devices are missing
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Failed to register device with error -19
  [FAILED] Failed to start Network Manager Wait Online.
  see 'systemctl status NetworkManager-wait-online.service' for details.
  [****] A Start Job is running for Raise network interfaces (38s / 5min 5s)...

  3- Hardware: HP Proliant DL380 with 4 gigabit Ethernet ports
  2x E52620 cpus
  32Gig RAM

  4- OS: Ubuntu 17.10.  however, this is an update from an installed 17.04.
  sudo lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 17.10
  Release:        17.10
  Codename:       artful

  
  5- Linux:uname -r
  4.13.0-21-generic

  
  6-  Boot: sudo cat /boot/config-4.13.0-21-generic | grep EDAC
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  # CONFIG_EDAC_GHES is not set
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 27 14:37:48 2017
  InstallationDate: Installed on 2017-09-29 (89 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP ProLiant DL380 Gen9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=1d02ee8d-fa4b-4287-991b-8a67bbf54cbf ro quiet intel_iommu=on
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware                             1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-12-23 (4 days ago)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL380 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL380Gen9:pvr:rvnHP:rnProLiantDL380Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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